JP3636686B2 - Automatic ticket gate, automatic ticket gate system, recording medium, management device, and prepaid management method - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to an automatic ticket gate system used in public transportation.
[0002]
[Prior art]
Currently, prepaid tickets using a magnetic card (a type of prepaid card) are issued and used. Such a prepaid ticket is often issued as a dedicated card by each transportation company. For example, there is a prepaid ticket with a premium that allows passengers to ride for an amount obtained by adding a unique premium amount to the prepaid amount on the premise of prepaid fee. The following points can be cited as the differences between the cards issued by each business operator.
1) Some cards have premiums and some do not.
2) Even if a premium is set, the size of the premium usually differs depending on the card.
3) There are cards that can be used by companies other than the issuing company.
[0003]
In this way, there is a difference depending on the type of prepaid ticket, but since the user selects the card to be used by himself, the remaining amount of the card can be clearly recognized, and if the remaining amount of the card is insufficient, the difference can be paid in cash. it can.
On the other hand, there is a need for a common ticket that can use public transportation anytime, anywhere with a single card. Such a common ticket can be easily realized, for example, by allowing use of a prepaid ticket issued by a certain institution.
[0004]
[Problems to be solved by the invention]
However, in reality, many operators want to issue their own prepaid tickets, and it is difficult to abolish the premium from the user's standpoint.
The problem with the common use of prepaid tickets is that there is a difference in the premium rate allowed by operators participating in the commonization. For example, even if a prepaid ticket without a premium of a certain company can be used in the transportation of a company that issues a prepaid ticket with a premium, there is no problem apart from the trouble of settlement.
[0005]
However, if a prepaid ticket with a premium can be used in the transportation of an operator that has no premium, the operator who issued the prepaid ticket with a premium will suffer a loss. This is because the user can use the prepaid ticket sales amount for the carrier's transportation system that has no premium, and the premium portion can be used for the carrier's transportation system that provides this premium. Therefore, issuing a prepaid ticket with a premium may only increase the number of free rides.
[0006]
In addition, the prepaid ticket with the current premium is integrated with the prepaid amount and the premium amount, and there are the following problems when trying to move to a common ticket while retaining the features of the current prepaid ticket .
For example, a common use that stores prepaid amounts (prepaid amounts) with different premium rates in a common ticket, and makes payments from the prepaid amount and an amount according to the premium rate for operators that allow the premium rate Considering the system, conventionally, an area to be stored for each premium rate must be provided, and a prepaid amount must be stored for each premium rate of a business operator to use.
[0007]
However, such a common ticket not only takes time to process due to its complicated data structure, but is also difficult for the user to understand. For example, it is assumed that 5,000 yen is paid in advance by Company A, and 5,000 yen is paid in advance by Company B. A ticket for Company A has no premium and a ticket for Company B has a premium. Company A's ticket has been used up, but even if B's ticket is still around 3,000 yen, the premium Company B's ticket cannot be used by Company A, so for users You will feel inconvenience. That is, if the user is aware that the remaining amount remains, it may be misunderstood as a malfunction of the card (common ticket).
[0008]
The present invention has been made in view of the above points, and in an automatic ticket gate system that can use a common ticket, eliminates the inconvenience on the user side that may occur with the use of a common ticket with different premium rates depending on the operator. It is possible to provide an automatic ticket gate system that does not cause a loss due to commonality for business operators.
[0009]
[Means for Solving the Problems]
  The automatic ticket gate of the present invention is an automatic ticket gate that accepts a common ticket used in common among a plurality of public transportation facilities, and business identification information for identifying a business for which a prepaid fee has been paid, Corresponding to the business operator identification information, prepaid management information including a premium remaining amount in which a premium amount determined for each business operator is set as an initial value and a prepaid balance in which a prepayment fee is set as an initial value is stored. When a user performs a predetermined operation on the automatic ticket gate using a predetermined common ticket and the fare is fixed,To collect the fare,The automatic ticket gatePreviousRead the prepaid management information from the common ticketReading unit and, Whether the premium balance is available from the prepaid management information,If it is determined that the premium balance is available, the prepaid balance and the rate based on the premium balance for the fare are discounted, and the amount obtained by subtracting the discount from the fare is calculated from the prepaid balance. Subtract and further subtract the discount from the premium balance, and update the prepaid management information of the common ticket using the prepaid balance and premium balanceAndIf it is determined that the premium balance is not available, the amount corresponding to the fare is subtracted from the prepaid balance, and if there is a premium balance, the discount is further subtracted from the premium balance, and the prepaid balance And the prepaid management information of the common ticket using the remaining premium amountHaving a ticket information update unitIt is characterized by.
[0011]
In addition, the automatic ticket gate of the present invention is further provided to a clearing center that performs processing related to clearing of charges between transport operators based on prepaid management information of common tickets used by each user, to other transport operators. Predetermined information including the amount to be charged is transmitted.
[0012]
The automatic ticket gate system according to the present invention is an automatic ticket gate system using the automatic ticket gate according to claim 3, wherein the automatic ticket gate system transmits the prepaid management information to the common boarding when a fee is paid in advance by a user. And a ticket issuing machine that stores the information including the prepaid management information to the clearing center, and the clearing center receives the predetermined information sent from the automatic ticket checker and the ticket issuing machine, It is characterized by performing a clearing process related to a charge clearing between transport operators using the ticket gate system.
[0013]
  The ticket of the present invention isIt can be used as the common ticket for the automatic ticket gate according to any one of claims 2 to 4.A ticket using a magnetic card or IC card, Business identification information for identifying a business for which a prepaid fee has been paid, and a premium balance in which a premium amount determined for each business is set as an initial value corresponding to the business identification information, Prepaid information including a prepaid balance for which a prepaid charge is set as an initial value and a prepaid date is added to the prepaid management information and stored each time the charge is prepaid by the user.
[0014]
In addition, when the premium remaining amount is available, the operator that the user paid in advance has set a premium (there is a premium remaining amount), and the operator is responsible for the public transportation used by the user. This is a case where it coincides with a business operator or a business operator who uses the premium in common with the business operator (concludes a common use agreement). This match determination is performed based on the operator identification information.
[0015]
  The management device of the present invention relates to a prepaid ticket that each user uses in common on multiple routes., Including presence / absence of premium for each company, premium rate, deposit amount, remaining amount, accumulated usage amountA management device that centrally manages prepaid management information, and when a user uses the route of an operator that provides premiums, depending on the cumulative amount used on the route of the operator,Depending on the presence of premium and premium rate,Computation means for calculating a premium return amount to be returned to the user, and update means for updating the prepaid management information of the user based on a calculation result of the calculation means.
[0016]
In addition, the management device of the present invention manages, as the prepaid management information, remaining amount information for each business operator, accumulated usage amount information, and premium return amount information, and the calculation means uses route information used by the user from the outside. And the boarding fare information are added, and the total usage fare information of the operator corresponding to the route on which the user boarded is added to calculate a new total usage fare, A premium refund amount is obtained based on the new accumulated usage amount, and the updating means updates the remaining amount information by subtracting the boarding fare from the remaining amount information of the operator, and also includes a calculation result of the calculating unit. The accumulated usage information and premium return amount information are updated based on the information.
[0017]
In the management apparatus according to the present invention, the calculation unit obtains the premium return amount based on a premium return amount charge system preset for each business operator.
[0018]
Moreover, the management device of the present invention is characterized in that, when the remaining amount corresponding to one of the operators is exhausted, the updating means updates the remaining amount information by subtracting the boarding fare from the other remaining amount.
[0019]
  The prepaid management method of the present invention relates to a prepaid ticket that each user uses in common on multiple routes., Including presence / absence of premium for each company, premium rate, deposit amount, remaining amount, accumulated usage amountThis is a prepaid management method for centrally managing prepaid management information, and when a user uses the route of a business providing a premium, according to the accumulated usage amount on the route of the business,Depending on the presence of premium and premium rate,The method includes a step of calculating a premium return amount to be returned to the user, and a step of updating the prepaid management information of the user based on a result of the calculation step.
[0020]
Moreover, the recording medium of the present invention records all or part of the prepaid management information managed by the management device according to any one of claims 6 to 9, and can be used as the prepaid ticket. Recording medium.
[0021]
An automatic ticket gate system according to the present invention is used by a management device according to any one of claims 6 to 9, a depositing machine that transmits deposit information received by a user to the management device, and a user. An automatic ticket gate system having an automatic ticket gate for transmitting route information and boarding fare information to the management device, wherein the management device receives the payment information received from the deposit machine or the automatic ticket gate Based on the information, the prepaid management information of the corresponding user is updated, and part or all of the updated prepaid management information is transmitted to the depositing machine or the automatic ticket gate, and the depositing machine or the automatic ticket gate is transmitted. Is characterized in that the information received from the management device is recorded in the user's prepaid ticket.
[0022]
  In addition, the present inventionPrepaid tickets areUsed in an automatic ticket gate system that uses a prepaid ticket that can be used in common on a first route providing premium and a second route not providing premium in an automatic ticket gate, Using IC cardA prepaid ticket, a first accumulated amount of the prepaid amount deposited on the first route on the first route, and a second on the second route of the prepaid amount deposited on the first route And the common remaining amount obtained by adding the first remaining amount of the prepaid amount deposited on the first route and the second remaining amount of the prepaid amount deposited on the second route, The remaining amount is made available on the first and second routes, and the cashback amount returned to the user calculated according to the first accumulated usage amount is added to the common remaining amount. Features.
[0023]
  In addition, the present inventionPrepaid tickets areEach time a prepaid ticket is used, the first and second remaining amounts, the first and second accumulated usage amounts, and the common remaining amount are received from the outside and updated.
[0024]
  In addition, the present inventionPrepaid tickets areRemaining amount calculation for calculating the first and second remaining amounts and the common remaining amount based on the deposit amount input from the depositing machine on the first and second routes and the withdrawal amount input from the automatic ticket gate on each route. A return amount calculating means for calculating a cashback amount to be returned to a user in accordance with the first accumulated usage amount, and a calculated cashback amount as the common amount. An addition means for adding to the remaining amount is provided.
[0025]
  In addition, the present inventionPrepaid tickets areThe remaining amount calculating means rewrites the first remaining amount with a common remaining amount when the common remaining amount <the first remaining amount, and then calculates the first accumulated usage amount by the return amount calculating unit. And
[0026]
  In addition, the present inventionPrepaid tickets areTransmission means for transmitting the first and second remaining amounts, the first and second accumulated usage amounts, the common remaining amount and the cash back amount to the management center is provided.
[0027]
  In addition, the present inventionPrepaid tickets areIt is used as the prepaid ticket in an automatic ticket gate system that uses a prepaid ticket that can be used in common on a first route that provides a premium and a second route that does not provide a premium in an automatic ticket gate. Ru, Prepaid tickets using IC cardsThe first use accumulated amount on the first route of the prepaid amount deposited on the first route and the second use on the second route of the prepaid amount deposited on the first route. The accumulated amount and a common remaining amount obtained by adding the first remaining amount of the prepaid amount deposited on the first route and the second remaining amount of the prepaid amount deposited on the second route are recorded, and the common remaining amount is recorded. It is made available on the first and second routes, and the premium return amount returned to the user calculated according to the first accumulated amount is added to the first remaining amount. Features.
[0028]
  In addition, the present inventionPrepaid tickets areEach time the prepaid ticket is used, the first and second accumulated usage amounts, the first and second remaining amounts, the common remaining amount, and the premium return amount are received from the outside and updated.
[0029]
  In addition, the present inventionPrepaid tickets areRemaining amount calculation for calculating the first and second remaining amounts and the common remaining amount based on the deposit amount input from the depositing machine on the first and second routes and the withdrawal amount input from the automatic ticket gate on each route. Means, a return amount calculating means for obtaining the first accumulated total amount and calculating a premium return amount to be returned to the user in accordance with the first accumulated amount, and calculating the calculated premium return amount And adding means for adding to the remaining amount of 1.
[0030]
  In addition, the present inventionPrepaid tickets areTransmission means for transmitting the first and second remaining amounts, the first and second accumulated usage amounts, the common remaining amount and the premium return amount to the management center is provided.
[0031]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
In the description of the present embodiment, the description of the parts common to the conventional automatic ticket gate system is omitted.
[0032]
First, terms used in the first embodiment and the second embodiment described later are defined.
Prepaid amount: This is the amount of the prepaid common ticket sold.
Premium amount: An extra amount when a prepaid common ticket is issued, and serves as a source of discount. For businesses that do not set this premium amount, the premium amount is “0”.
Prepaid balance: One prepaid common ticket, depending on the user's use, the amount corresponding to the fare from the prepaid amount (the amount obtained by subtracting the discount amount from the fare or the fare depending on whether the premium can be used or not) ) Minus the balance.
[0033]
Premium balance: A prepaid common ticket, which is a balance obtained by subtracting the discount amount from the premium amount according to the use of the user. In this embodiment, the discount amount is determined according to the fare, premium remaining amount, and prepaid remaining amount (described later), but is not limited to this. For example, the discount amount is obtained by multiplying the fare by a certain discount rate. You may do it.
Card balance: A prepaid common ticket, the sum of the prepaid balance and the premium balance.
[0034]
The standardization of prepaid tickets can be solved by concluding a common agreement between transport operators, but a premium processing method that allows each operator to agree is required. In the present embodiment, this premium processing is performed according to the following rules.
[0035]
1) The prepaid amount will be applied to the fare billed amount.
2) The premium amount will be applied to the discounted fare. This discount is
Discount amount = Fare × Premium balance ÷ (Prepaid balance + Premium balance)
Asking.
3) In combination with the business operator that issued the prepaid common ticket (issue business operator), for the business operator of the group that uses the same premium, the amount obtained by subtracting the discount from the fare is The amount charged to the issuing company.
4) For business operators in a group different from the above group, the fare itself is the amount charged to the business operator who issued the prepaid common ticket from that business operator.
With the above processing, when the prepaid common ticket is used, the prepaid balance is reduced by the amount charged and the premium balance is reduced by the discount amount.
[0036]
Next, the configuration of the automatic ticket gate system according to the present embodiment will be described with reference to FIG. FIG. 1 is a diagram showing a configuration of an automatic ticket gate system according to a first embodiment of the present invention.
[0037]
Reference numeral 1 denotes a prepaid common ticket using a magnetic card. This prepaid common ticket 1 stores prepaid ticket information (prepaid management information) as an example in the portion 1a in FIG.
This prepaid ticket information is information including at least the date of ticketing, the carrier identification information for identifying the transportation carrier that has received the prepayment, and the above-mentioned prepaid balance and premium balance. In the form, it is assumed that the balance of the card is further included.
[0038]
Reference numeral 2 denotes a ticket issuing machine that issues a prepaid common ticket 1 according to a prepaid fee separately determined for each business operator. The ticket issuing machine 2 sets the date of ticketing and the carrier identification information as the prepaid ticket information recorded in the prepaid common ticket 1, and further sets the prepaid amount as the initial value of the prepaid balance, A premium amount separately determined by the issuer is set as an initial value. In addition, other information set separately is set. Further, the ticket issuing machine 2 transmits the clearing center sending data including the prepaid ticket information set in the prepaid common ticket 1 to the clearing center 4 described below.
[0039]
Reference numeral 3 is an automatic ticket gate that accepts the prepaid common ticket 1 and other tickets of the present embodiment. The automatic ticket gate 3 is the same as the conventional automatic ticket gate except for the following configuration.
This automatic ticket gate 3 includes a reading unit (not shown) for reading prepaid ticket information from the prepaid common ticket 1 inserted by the user, and prepaid ticket information according to the use by the user by a procedure described later. A ticket information updating unit (not shown) for updating the ticket, and a sending unit (not shown) for sending the clearing center sending data including information (charged amount, etc.) on the fee clearing according to use to the clearing center 4 It has.
[0040]
In the case where the automatic ticket gate 3 is used instead of a fee box, for example, on a shared bus with a fixed fare, the single ticket gate 3 performs processing at the time of entry and entry at the same time. In addition, transmission of usage information from the automatic ticket gate 3 loaded on the shared bus to the clearing center 4 may be performed wirelessly. For example, after the shared bus returns to the garage, it is transmitted in a lump. May be. In addition, for example, in the case of a transportation system such as a train, the fare for the user is determined when the user inserts the prepaid common ticket 1 into the automatic ticket gate 3 at the time of participation, such as a shared fare sharing bus Then, the timing will be determined separately by the operator.
[0041]
Reference numeral 4 is a clearing center, which receives clearing center sending data sent from the ticket issuing machine 2 and the automatic ticket gate 3 of each transportation company, prepaid ticket information (part 4 sign in FIG. 1) and a clearing billing chart (figure 1 is updated, and data processing for fee settlement between transportation operators is performed based on this settlement billing table, and settlement information (billing amount, etc.) regarding fee settlement is transmitted to each transportation operator. Each transportation company performs accounting processing such as billing, depositing, and payment for clearing based on this clearing information.
[0042]
Next, processing in the automatic ticket gate 3 will be described with reference to the flowchart of FIG.
[0043]
When the prepaid common ticket 1 is inserted into the automatic ticket gate 3 by the user, the reading unit reads prepaid ticket information and predetermined information (such as information on the entrance station) from the prepaid common ticket 1 (step information) S101).
Then, the fare for the user is obtained (step S102).
Next, the ticket information updating unit determines whether the prepaid balance included in the prepaid ticket information remains (step S103). If it is determined that there is no prepaid balance remaining, the prepaid balance is insufficient. An alarm indicating that it is in effect is issued (step S104).
[0044]
If it is determined in step S103 that the prepaid balance remains, the ticket information update unit determines whether the premium can be used from the business operator identification information and the premium balance included in the prepaid ticket information. Here, it is determined whether the business operator corresponding to the business operator identification information matches the business operator of the transportation facility equipped with the automatic ticket gate 3 (or the business operator that has concluded a common use agreement). By judging whether there is a balance, it is judged whether the premium can be used.
If it is determined by the above determination whether or not the premium is available, the ticket information updating unit calculates the billed amount and the discounted amount according to this determination (step S105).
[0045]
Then, a prepaid balance obtained by subtracting the discount amount from the fare from the prepaid balance and a premium balance obtained by subtracting the discount from the premium balance are calculated (step S106). At this time, if the prepaid balance is a negative value, these are set to “0”, and the difference is calculated as an insufficient amount (step S107). If there is no shortage, the shortage amount is set to “0”.
[0046]
Next, it is determined whether there is a shortage (shortage amount = 0) (step S108). If it is determined that there is a shortage, a warning is sent to inform the user to that effect (step S104).
If it is determined in step S108 that there is no shortage, the transmission unit prepares clearing center sending data and transmits it to the clearing center 4 (step S109).
Then, the ticket information update unit updates the prepaid balance and the premium balance of the prepaid ticket information stored in the prepaid common ticket 1 (step S110).
[0047]
Next, processing in the automatic ticket gate 3 will be described with a specific example.
[0048]
[Example 1]
The example shown in FIG. 3 is an example when the prepaid common ticket 1 with a prepaid amount of 1,000 yen and a premium amount of 100 yen is used to get on only the same group bus (fare 210 yen). In this example, the discount amount is 20 yen and the charge amount is 190 yen for the first to fifth rides. In the sixth time, the billed amount is 210 yen, but the prepaid balance is 50 yen, resulting in a shortage of 160 yen. This shortage is settled with cash or the like when getting off, for example.
[Example 2]
The example shown in FIG. 4 is a prepaid common ticket 1 with a prepaid amount of 1,000 yen and a premium amount of 100 yen, and rides alternately on the same group of buses (fare 210 yen) and different groups of railways (fare 170 yen). This is an example.
In this example, the premium can be used for the first, third and fifth bus rides of the same group, so there is a discount of 20 yen and the invoice amount is 190 yen.
[0049]
Since the 2nd, 4th and 6th railways are in other groups, the discount using the premium balance is invalid, and only the prepaid balance is used, and the fare is reduced from this prepaid balance. In addition, the amount corresponding to the discount amount is reduced from the premium balance. In addition, the amount equivalent to the discount amount is deducted from the premium balance here. In general, the premium amount is given by the prepayment fee for the operator (operator group) that issued this ticket. This is because it is assumed that everything is operated under the operator.
[0050]
The sixth time, 90 yen out of the 170 yen charge will be paid from the prepaid balance, and 80 yen will be insufficient.
In this case, as a result, the prepaid common ticket 1 for buses with a prepaid amount 570 yen and premium 60 yen and the prepaid amount 430 yen, prepaid common ticket 1 for railways without premium are issued. Become.
[0051]
[Example 3]
The example shown in FIG. 5 is an example of a case where the prepaid common ticket 1 with a prepaid amount of 1,000 yen and a premium amount of 100 yen is boarded only on a different group of railways (fare 170 yen).
In this example, since the first to sixth times are all used in the railway, all discounts due to the premium balance are invalid and only the prepaid balance is used.
The sixth time, 150 yen out of the billed 170 yen is paid from the prepaid balance, and 20 yen is insufficient.
In this case, as a result, the prepaid common ticket 1 having a prepaid amount of 1,000 yen and no premium is issued.
[0052]
[Liquidation between business operators]
The business operator who has used the prepaid common ticket 1 can request settlement from the business operator who issued the prepaid common ticket 1. The clearing of the prepaid common ticket 1 is performed only for the amount paid from the prepaid balance, and the premium is unrelated to the clearing. In the present embodiment, the clearing center 4 is used to centrally manage the usage results at the clearing center 4, and the amount received and paid for each company is calculated here for clearing. The payment associated with the use of the prepaid ticket 1 can be efficiently performed. In addition, when there are few participating companies, you may perform the payment of a prepaid ticket by the relative system in which two companies each carry out relative.
[0053]
Next, details of the automatic ticket gate system according to the second embodiment of the present invention will be described with reference to FIG.
[0054]
In the present embodiment, a prepaid ticket is shared by using an IC card. The present embodiment is an extension of the concept of sharing by the prepaid common ticket 1 using the magnetic card of the first embodiment described above. The prepaid common ticket 1 'according to the present embodiment can be regarded as storing a plurality of prepaid common tickets 1 described in the first embodiment in one IC card. The “charge” of the prepaid common ticket 1 ′ used in the following description refers to the prepaid ticket information recorded in the prepaid common ticket 1 at the time of ticketing in the first embodiment as one record (prepaid information). It is to be stored in the card. In addition, the present embodiment has a card information that includes a sum (SF balance) of the prepaid balance of records (prepaid information) corresponding to a plurality of prepaid common tickets 1 and a plurality of prepaid common tickets 1 stored in the IC card. The point of view is basically the same as that of the first embodiment except that a point for controlling the use order of the first record is added.
[0055]
Next, the configuration of the automatic ticket gate system according to the present embodiment will be described.
[0056]
Reference numeral 1 'denotes a prepaid common ticket using an IC card. In this prepaid common ticket 1 ', in addition to the prepaid ticket information described in the first embodiment, card identification information (not shown) for identifying this IC card as card information, all The SF remaining amount that is the sum of the remaining prepaid amounts is stored. The prepaid ticket information stored in the prepaid common ticket 1 ′ corresponds to the prepaid ticket information described in the first embodiment additionally stored as one record for each charge (FIG. (See part 1'a)
[0057]
However, in this embodiment, the prepaid ticket information includes at least a charge date that is a date when the user is charged and a group name for identifying a business group that has a common use agreement. , Information including charge business information (business identification information) for identifying the business that has received the deposit by charge, and the above-mentioned prepaid balance and premium balance. If a premium is set among the operators of the operator group that has concluded the common use agreement, this premium can be used in common.
In the present embodiment, the following charging machine 2 ′ and automatic ticket gate 3 ′ set and update the data stored in the prepaid common ticket 1 ′ as described later. These processes may be performed using an embedded microprocessor.
[0058]
Reference numeral 2 'denotes a charging machine (ticketing machine) that sets prepaid ticket information and SF balance in the prepaid common ticket 1' according to a prepaid fee separately determined for each business operator. The charging machine 2 ′ sets the charge date at the time of charging, the charge carrier information, and the group name as the prepaid ticket information stored in the prepaid common ticket 1 ′, and the prepaid amount as the initial value of the prepaid balance And the premium amount separately determined by the issuer is set as the initial premium balance. Further, the total amount of the remaining prepaid stored in the prepaid common ticket 1 'is set as the SF remaining amount, and other separately determined information is set. Further, the charging machine 2 'transmits the clearing center sending data including the prepaid ticket information set in the premium common ticket 1' to the clearing center 4 described below.
[0059]
A sign 3 'is an automatic ticket gate that accepts the prepaid common ticket 1' and other tickets of the present embodiment. The automatic ticket gate 3 ′ is inserted by the user or, in the case of non-contact reading, a reading unit (not shown) for reading prepaid ticket information from the prepaid common ticket 1 ′ held by the user. Sending the Clearing Center including a ticket information updating unit (not shown) that updates prepaid ticket information according to the use by the user, and information (charged amount, etc.) related to the fee settlement according to the use according to the procedure described later It has a transmission part (not shown) which transmits data to the following clearing center 4. The automatic ticket gate 3 'is the same as the automatic ticket gate 3 of the first embodiment except for the operations described below.
Further, the clearing center 4 shown in FIG. 6 is the same as that of the first embodiment, and the description thereof is omitted.
[0060]
Here, the details of the calculation method of the discount amount, billing amount, prepaid balance, premium balance, shortage amount, and SF balance performed by the ticket information update unit will be described.
[0061]
(1) If the prepaid ticket information includes a record that includes an available premium balance: Discount amount = Min {Premium balance, fare x premium balance ÷ (prepaid balance + premium balance)}
・ Invoice amount = Fare-Discount amount
・ Prepaid balance = Max {0, Prepaid balance-amount charged}
・ Premium balance = Premium balance-Discount amount
・ Insufficient amount = Max {0, amount charged-SF balance}
・ SF remaining amount = Max {0, SF remaining amount-amount charged}
[0062]
(2) If the prepaid ticket information does not contain a record that includes the available premium balance:-Discount amount = Min {Premium balance, fare x premium balance / (prepaid balance + premium balance)}
・ Billing amount = Fare
・ Prepaid balance = Max {0, Prepaid balance-amount charged}
・ Premium balance = Premium balance-Discount amount
・ Insufficient amount = Max {0, amount charged-SF balance}
・ SF remaining amount = Max {0, SF remaining amount-amount charged}
As described above, the discount amount, the billing amount, the prepaid balance, the premium balance, the shortage amount, and the SF balance are calculated.
[0063]
Next, details of the operation of the automatic ticket gate system of the present embodiment will be described.
First, the operation of the charging machine 2 'will be described with reference to the flowchart of FIG.
[0064]
First, the charging machine 2 'reads prepaid ticket information from the prepaid common ticket 1' (step S201).
Then, it is determined whether or not there is a record in which the prepaid balance and the premium balance are “0” in the prepaid ticket information (step S202).
If it is determined in step S202 that there is a record having a prepaid balance and a premium balance of “0”, the record is deleted (step S203).
[0065]
Next, it is determined whether there is a free area in the storage area for storing prepaid ticket information (step S204).
If it is determined in step S204 that there is an empty area, the prepaid information is added to and stored in the prepaid ticket information of the prepaid common ticket 1 '(step S205).
Then, the sum of all the prepaid balances in the prepaid ticket information is calculated, and this value is set as the SF balance of the card information and updated (step S206).
Then, separately determined clearing center sending data including prepaid ticket information is transmitted to the clearing center 4 (step S207).
If it is determined in step S204 that there is no free space, the user is notified of this (step S208).
[0066]
In the signs 1′a and 4a in FIG. 6, an IC card (prepaid common ticket 1 ′) and the clearing center 4 when the transportation company A and the transportation company B are charged 1000 yen and 5000 yen respectively. An example of retained data is shown.
In the IC card and clearing center 4 shown in this figure, as the card information, the remaining SF of 6000 yen, as the prepaid ticket information, the group name (group A, group B), the charge carrier information (transport carrier A , Transportation company B), charge date (October 14, 00, October 10, 00), prepaid balance (1000 yen, 5000 yen) and premium balance (100 yen, 0 yen) It is stored corresponding to the business. In the clearing center 4, the charged amount is set in the column of the deposit amount corresponding to the charge operator in which the deposit amount deposited with each charge operator and the amount charged between the operators are set (see FIG. 6 reference 4b part).
[0067]
Next, the operation of the automatic ticket gate 3 'will be described with reference to the flowchart of FIG.
[0068]
  When the user performs a predetermined operation such as inserting the prepaid common ticket 1 ′ into the automatic ticket gate 3 ′ at the time of participation or the like, the reading unit reads the prepaid ticket information, the card information, and other predetermined information. (Step S301).
  Then, the fare is calculated (step S302). Information used for calculating the fare (information recorded on a general ticket such as information for identifying an entrance station) is stored in the prepaid common ticket 1 'in the same manner as a general ticket. If it is determined in step S308 below that there is a shortage (deficit amount> 0), The process is moved to step 311.
[0069]
Next, it is determined whether the SF remaining amount is positive (SF remaining amount> 0) (step S303).
If it is determined in step S303 that the SF balance is positive, the ticket information update unit searches the prepaid ticket information for a record to be processed according to the following rules (step S304).
Here, there is a premium balance that can be used for a business operator who operates this automatic ticket gate 3 'or a business operator of the same group that has a common use agreement with this business operator. In this case, the oldest record (prepaid information) is searched in the order of charging. If there is no corresponding record in this search, the oldest record is searched for in the charge order with a record having no premium remaining amount. In this search, if there is no corresponding record, the oldest record is searched for in the charge order with a record having a premium remaining amount (in this case, this premium cannot be used).
[0070]
Next, as described above, the discount amount and the invoice amount are calculated from the prepaid balance, the premium balance, and the fare calculated in step S302 (step S305).
Then, as described above, the prepaid balance and the premium balance are calculated (step S306), and the deficiency is obtained (step S307).
[0071]
Next, it is determined whether the prepaid balance and the premium balance are insufficient (whether the shortage> 0) (step S308).
If it is determined in step S308 that there is no shortage (deficit amount = 0), the transmission unit charges the charge amount calculated in step S305, the charge carrier information corresponding to the record, and the traffic used by the user. Clearing center transmission data including information for identifying the business operator of the institution and card identification information is prepared and transmitted to the clearing center 4 (step S309).
Then, the boarding ticket information updating unit updates the prepaid boarding ticket information and the SF remaining amount of the prepaid common boarding ticket 1 '(step S310).
[0072]
  If it is determined in step S308 that the deficit amount is> 0, clearing center sending data including a charge amount that can be charged to the charge provider corresponding to the record is prepared (step S311).S302Move to, and start reprocessing to make the shortage a new fare.
  Further, if it is determined in step S303 that the remaining SF amount is 0, an alarm is issued to notify that the remaining SF amount is insufficient (step S312).
[0073]
Next, the clearing process in the clearing center 4 will be described with reference to the flowchart shown in FIG.
[0074]
First, clearing center sending data sent from the charging machine 2 'and the automatic ticket gate 3' is collected (step S401).
Then, based on the card identification information included in the clearing center sending data, the prepaid ticket information of each prepaid common ticket 1 ′ stored in the clearing center 4 is searched (step S402), and the prepaid ticket information is updated. (Step S403).
Further, it is determined whether the data type of the clearing center sending data (whether it is sent from the charging machine 2 'or sent from the automatic ticket gate 3') (step S404). The clearing center transmission data includes information for identifying the transmission source of this data.
[0075]
If it is determined in step S404 that the ticket has been sent from the automatic ticket gate 3 ', the billing amount column of the clearing bill is updated based on the billing amount included in the clearing center transmission data (step S405). ).
If it is determined in step S404 that the data is sent from the charging machine 2 ′, it is based on the charge amount (initial value of the prepaid balance) included in the clearing center transmission data sent from the charging machine 2 ′. Then, the deposit deposit column in the clearing bill is updated (step S406).
The processing in steps S402 to S407 is repeated until it is determined in step S407 that the processing has been completed for all collected clearing center transmission data.
[0076]
Next, a third embodiment of the present invention will be described.
First, conventional problems relating to the present embodiment will be described. In addition, this conventional
The problem is overlapped with the contents described in [Prior Art] and [Problems to be Solved by the Invention], but will be briefly described here.
In addition, the “prepaid common ticket” in the first and second embodiments is referred to as “SF (Stored Fare) card (fare storage card)” in the following description. The present embodiment relates to claims 6-12.
[0077]
The SF card composed of the current magnetic card has a premium and a non-premium. Assume that the business operator A issues an SF card X without a premium, and the business operator B issues an SF card Y with a premium. In this case, it is unlikely that A and B allow the shared use of the card. This is because if the SF card Y can be used on the route A, the user purchases only the premium SF card Y and uses both the route A and the route B. This is because a fare discount that does not occur in A originally occurs and B will bear the discount, and B suffers damage.
[0078]
In the case of an SF card composed of an IC card, it is desirable that a single card can be commonly used as a card X without a premium and a card Y with a premium. In order to meet this demand, for example, two pockets (areas) are provided in an IC card, SF-X (card X storage fare) is charged (paid) in the first pocket, and SF-X is stored in the second pocket. It is conceivable to charge Y (stored fare for card Y), pay with SF-X when using route A, and pay with SF-Y when using route B.
[0079]
However, this method has a simple mechanism, but the following problems occur.
For example, assume that the user charges each pocket with 5000 yen as SF-X and 5000 yen (total 10,000 yen) as SF-Y. When this user exclusively uses the route A, the remaining amount of SF-X decreases rapidly. Even if the user is willing to charge 10,000 yen, the IC card becomes unusable on route A when the user spends more than 5000 yen, and the user is suspicious. In addition, when there are a large number of premiums having different premium rates, each pocket must be charged separately, which affects the capacity and processing speed of the IC card.
Therefore, the third embodiment solves the above problem, and allows one card to be used on a plurality of routes regardless of whether a premium is present or not, and a high-speed processing. It is aimed.
[0080]
In the present embodiment, an IC card is used as an SF card as a prepaid ticket that is a recording medium according to the present invention. When the SF card is used on a route with a premium, a predetermined amount is determined according to the accumulated usage amount of the card. The amount of money will be returned (cashback). Therefore, the amount of cash back is substantially a premium. In addition, each user's SF card (IC card) is managed by the management center, and processing such as calculation of the refund amount is performed not by the IC card but by the management center. Further, as a specific method of cash back, for example, a method of adding the return amount to the remaining amount of the IC card by an automatic ticket gate or a depositing machine (charge machine) is used.
[0081]
Next, handling of SFs having a plurality of SF types (presence / absence of premium, premium rate) will be described. In the following description, the SF card is referred to as an IC card or simply a card as necessary.
In this embodiment,
(1) The SF card has one SF pocket.
(2) When SF is charged to the card by the deposit machine, the deposit amount is added to the SF pocket, and the card ID, deposit amount, deposit place, deposit date, and SF type are detailed information on deposit (hereinafter referred to as deposit). It is sent to the management center.
(3) The deposit details are managed as one record for each charge in the management center.
(4) When a user uses a card, the withdrawal amount is subtracted from the SF pocket, and the card ID, withdrawal amount, withdrawal place, withdrawal date, and SF type are detailed information on withdrawals (hereinafter referred to as the withdrawal amount). Is referred to as a withdrawal statement).
[0082]
(5) The management center determines a record in which the withdrawal amount is to be subtracted in the following order based on the withdrawal details.
(1) The record that is most advantageous to the user is the record to be subtracted. This is because a record is created for each SF type each time the battery is charged, and therefore, from which record the amount to be withdrawn is subtracted.
{Circle around (2)} When there are a plurality of records that are most advantageous to the user, the oldest record of the deposit date is set as the subtraction target record.
[0083]
Next, premium handling will be described.
Here, two types of SF cards, that is, a rail card used in a railway and a bus common card used in a bus will be described as an example.
The current railway card has no premium, and the bus common card has a premium. There are three types of bus common cards, 1000 yen, 3000 yen, and 5000 yen, with premiums of 100 yen, 360 yen, and 850 yen, respectively. Currently, the railway card cannot be used on the bus, and the bus common card cannot be used on the railway.
[0084]
In the present embodiment, the SF card is converted into an IC card to issue a railroad SF (hereinafter referred to as SF-P) instead of the railroad card, and a bus common SF (hereinafter referred to as SF) instead of the bus common card. -B)).
[0085]
Next, basic rules of SF-P and SF-B will be described.
(1) Both SF-P and SF-B can be used on both railways and buses.
{Circle around (2)} SF-P is preferentially used when using a railway, and SF-B is preferentially used when using a bus.
(3) Use of SF-B on the bus is eligible for premium return.
(4) Use of SF-B on railways is not eligible for premium return.
(5) Premiums will be returned by SF-B cash back.
(6) The relationship between the accumulated usage amount of SF-B and the refund amount is determined based on the current premium rate.
(7) Premium return (in this case, cash back) is carried out at a predetermined timing according to the accumulated amount used.
(8) The premium refund amount (cashback amount, the same applies hereinafter) when SF-B is used only on railways is zero.
(9) The premium refund amount when SF-B is used only on a bus is the same as the current amount.
[0086]
Next, several methods for determining the premium refund amount will be described.
(1) The same premium rate as the current bus common card is set, and as shown in FIG. 10, O = (0,0), P = (1100,100), Q = (3360,360), R = Return amount is determined using a primary calculation formula represented by a line graph passing through four points (5850, 850).
[0087]
In FIG. 10, the horizontal axis represents the accumulated usage amount, and the vertical axis represents the accumulated cumulative amount. When the user uses 1100 yen on the bus, the accumulated refund amount up to that time is 100 yen, 360 yen when using 3360 yen, 850 yen when using 5850 yen, and x yen when using Then, each Y yen is the accumulated amount of refund. That is, y yen is returned according to the accumulated usage amount x yen, and this return amount is realized as a discounted fare by premium.
In addition, when using a railway (train), there is no premium, so the premium corresponding to the amount used on the railway is abandoned.
[0088]
{Circle around (2)} Using the following calculation formula (1), a return standard table showing the relationship between the accumulated use amount and the return amount is created, and the return amount is obtained from this table.
Q = cumulative usage amount, P = return amount.
Q = aP + b => P = (Q-b) / a (1)
However, in the case of 0 ≦ Q ≦ 1100 a = 0.0909 b = 0
When 1100 <Q ≦ 3360 a = 0.150 b = −26
In the case of 3360 <Q ≦ 5850 a = 0.1968 b = −301
[0089]
An example of the return criteria table created using the above formula (1) is shown in FIG.
In this example, every time the accumulated usage amount reaches a predetermined amount, the corresponding return amount is returned.
Alternatively, it may be returned every time the accumulated usage amount increases by a certain amount (for example, 1000 yen). In the formula (1), the refund amount is in yen including fractions, but in reality, about 10 yen is considered appropriate.
[0090]
Next, specific examples will be described.
Note that the refund amount in this example is calculated by the above formula (1), for example, and does not necessarily match the refund amount in FIG.
It is assumed that the user charges the SF card with 3000 yen as SF-P and 5000 yen as SF-B. Assuming that the accumulated amount used on the railway is U and the accumulated amount used on the bus is V, the premium refund amount is as follows.
(1) In the case of U = 6000 yen and V = 2000 yen ⇒200 yen corresponding to the accumulated usage amount of 2000 yen is returned.
(2) In the case of U = 6000 yen and V = 2200 yen (200 yen is the refunded amount) ⇒ (230-200) yen is returned corresponding to the accumulated usage amount of 2200 yen.
(3) In the case of U = 5000 yen and V = 3000 yen ⇒320 yen corresponding to the accumulated use amount of 3000 yen is returned.
(4) In the case of U = 5000 yen and V = 3320 yen (320 yen is the refunded amount) ⇒ (360-320) yen is returned corresponding to the accumulated usage amount of 3320 yen.
[0091]
Next, an automatic ticket gate system according to a third embodiment of the present invention will be described with reference to the drawings.
FIG. 12 is a block diagram showing the configuration of the automatic ticket gate system according to this embodiment.
In FIG. 12, 10 is an SF card comprising an IC card, 20 is a depositing machine, 30 is an automatic ticket gate (including a toll box on the bus), and 40 is a management center (management apparatus). In the actual system, the depositing machine 20 and the automatic ticket gate 30 are provided at bus stops, railway stops, stations, in-cars, etc., but in the figure they are represented by one for simplification. ing.
[0092]
Although not shown, the SF card 10, the depositing machine 20, the automatic ticket gate 30 and the management center 40 are provided with a CPU, various processing units controlled by the CPU, a communication unit, a memory unit, and the like. Yes.
[0093]
The SF card 10 has a card information table 11. In the card information table 11, the card ID, SF remaining amount (total usable amount of each SF), return ID (control information for SF return), trip information (information necessary for fare calculation: where to get on, get off Etc.).
[0094]
The depositing machine 20 creates a detailed description (hereinafter simply referred to as a single description) 21 at the time of depositing and transmits it to the management center 40. In the case description 21, the card ID (the ID of the SF card that has been deposited), the type (separate payment / withdrawal of the SF card), the amount (the amount of money to be deposited, the amount of money to be withdrawn), and the creation location (one statement has been created Business), and the date of creation (the date of creation of the details).
[0095]
The management center 40 is provided with an SF management table 41, a return reference table 42, and an SF return table 43.
The SF management table 41 includes a card ID (used card ID), a deposit date (SF charge date), a deposit location (a company that performed SF charge), and an SF type (presence / absence of premium, premium rate) Etc.), deposit amount (charged amount), remaining amount (SF remaining amount of the card), accumulated usage amount (cumulative SF usage amount at companies that can use premium), previous refund amount (or up to the previous time) It may be the accumulated amount of refunds).
[0096]
In the return standard table 42, for example, return amounts for a plurality of accumulated usage amounts as shown in FIG. 11 are described.
In the SF return table 43, a card ID (the card ID) and a return amount (SF amount to be returned = premium return amount) are described.
[0097]
Next, the operation of the above configuration will be described along the procedures (1) to (9) shown in FIG.
(1) First, when the user inserts the SF card 10 into the depositing machine 20 and performs a deposit operation, a predetermined amount is charged to the SF card 10. Charging is performed by adding the amount of money to the SF remaining amount in the card information table 11.
(2) The depositing machine 20 reads the card information table 11 after charging, creates a deposit details 21 based on this, and sends it to the management center 40. The management center 40 records the deposit details 21. To the SF management table 41.
[0098]
(3) When the user actually uses the SF card 10 and passes through the automatic ticket checker 30, the automatic ticket checker 30 subtracts the fare at that time from the SF balance in the card information table 11 as the amount to be paid.
(4) The automatic ticket gate 30 creates a withdrawal details 31 including the SF remaining amount after subtraction, and transmits it to the management center 40. Based on this, the management center 40 updates the SF remaining amount and the accumulated usage amount of the card in the SF management table 41.
[0099]
(5) The management center 40 determines the return amount from the return reference table 42 based on the updated accumulated usage amount. As a method of determining the refund amount, for example, a difference between the current accumulated return amount and the previous accumulated cumulative amount is obtained, and when this difference is positive, the value is determined as the refund amount.
(6) The SF return table 43 of the determined return amount is described.
(7) Update the previous return amount in the SF management table 41 based on the SF return table 43 after the description.
[0100]
(8) The determined return amount is transmitted to the automatic ticket gate 30.
(9) The automatic ticket gate 30 adds the refund amount to the SF balance in the card information table 11 of the SF card 10.
[0101]
Next, each process in the management center 40 will be described with reference to flowcharts.
First, the deposit process will be described with reference to the flowchart of FIG. This depositing process is performed when the SF card 10 is charged by the depositing machine 20 in the procedures (1) and (2).
In FIG. 13, the deposit details 21 sent from the depositing machine 20 is read (step S <b> 1, hereinafter, step is omitted). Next, it is determined whether the money is withdrawn or withdrawn (S2), and in the case of withdrawal, a later-described withdrawal process is performed (S3). In the case of depositing, a record is added to the SF management table 41 (S4), and the process ends.
[0102]
As described above, the SF management table 41 can be updated based on the deposit details 21 from the deposit machine 20. Note that the record of the SF management table 41 is generated when the receipt details 21 with the type of receipt is received, and is deleted when the remaining amount = 0.
[0103]
FIG. 14 is a flowchart of the withdrawal process according to S3. This withdrawal process is performed for the procedures (3) and (4) when the SF card 10 is used and withdrawal is performed. In the following description, as the use place (route) of the SF card 10, a premium valid route (for example, a bus route) is B, and a premium invalid route (for example, a railway route) is A. Also, SF-B is Y and SF-P is X.
[0104]
In FIG. 14, first, it is determined whether the use place (use route) of the SF card 10 is A or B (S11).
In the case of B, the presence / absence of the Y remaining amount is checked (S12), and if there is a Y remaining amount, it is checked whether the Y remaining amount is equal to or greater than the amount to be paid (S13). If it is greater than the withdrawal amount, the withdrawal amount is used as the usage amount, the usage amount is subtracted from the Y balance amount, and the value is updated as the Y balance amount (S14). Next, after confirming whether the place of use is B (S16), the accumulated usage amount + used amount is obtained, and the value is updated as the accumulated usage amount (S17). Next, it is checked whether or not the usage amount and the withdrawal amount match (S18). In this case, since they match, the processing is terminated.
[0105]
In the case of No in S13, that is, when the Y remaining amount is insufficient for the amount to be paid, the Y remaining amount is updated to zero using the Y remaining amount as a usage amount (S15). In S18 after S16 and S17, the used amount does not match the withdrawn amount. Therefore, the used amount is subtracted from the withdrawn amount to obtain an insufficient amount (S19). After confirming (here B), the Y balance is confirmed in S12. In this case, since the Y remaining amount is zero in S15, S12, No, the process proceeds to S20, and the above shortage (the amount of money determined in S19) is taken out from the X remaining amount.
[0106]
Further, when the use place is A in S11, the process proceeds to S20. In S20, the presence / absence of an X remaining amount is checked. If there is an X remaining amount, it is checked whether the X remaining amount is equal to or greater than the amount to be paid (S21). If it is equal to or greater than the withdrawal amount, the withdrawal amount is used as the usage amount, the usage amount is subtracted from the X residual amount, and the value is updated as the X residual amount (S22). Then, the process ends through S18.
[0107]
If it is determined as A in S11 and No in S21, that is, if the remaining amount of X is insufficient for the amount to be paid, the remaining amount of X is used and the remaining amount of X is updated to zero (S23). In S18, the amount used does not match the amount to be withdrawn, so in S19, the amount of money is subtracted from the amount to be used to determine the shortage, and this amount is used as the amount to be returned to S11. In step S20, the Y balance is confirmed. In this case, since the X balance is zero in S23, the process proceeds from S20, No to S12, and the missing amount (the withdrawal amount determined in S19) is taken out from the Y balance. In the case of taking out the shortage of the X remaining amount from the Y remaining amount, it becomes No in S16, and the process is ended through S18 and Yes. In addition, the SF card 10 can be used if there is at least one remaining balance of X balance and Y balance, and cannot be used if there is no balance.
[0108]
Next, the return process will be described with reference to the flowchart of FIG. This return processing is performed for the procedures (5) to (9).
In FIG. 15, first, the next record is read to check whether the record has a premium (S32). (S33). It is checked whether the value obtained by subtracting the previous refund amount from the accumulated return amount is positive (S34). If it is positive, the SF return table 43 is created (S35) and transmitted to the automatic ticket gate 30. The above processing is performed for each record up to the last record (S37).
[0109]
According to the above, the SF management table 41 is checked at a predetermined interval, the accumulated usage amount of the return standard table 42 that does not exceed the accumulated usage amount of the record, and the corresponding accumulated return amount are obtained. An SF return table 43 can be created for a record with a positive difference from the amount and sent to the automatic ticket gate 30 determined for each card ID.
[0110]
In the present embodiment described above, cash back by premium return is performed by adding to the remaining amount of the SF card 10 from the depositing machine 20 at the time of depositing, but cash back may be performed by the automatic ticket gate 30. In some cases, other methods such as bank transfer can be used regardless of the depositing machine 20 or the automatic ticket gate 20.
[0111]
Moreover, although the refund is performed every time the deposit is made, it may be returned when the number of deposits or withdrawals reaches a predetermined number, or may be returned when the accumulated amount of the refund reaches a predetermined amount.
Further, the refund amount is calculated each time based on the above formula (1) and the graph of FIG. 10, or is calculated using the return standard table 42 created based on the formula (1) and the graph of FIG. be able to.
In addition, although the management of the SF card 10 is performed at the management center 40, it may be performed on an IC card that is the SF card 10.
[0112]
According to the present embodiment described above, one SF card can be used in common on a plurality of routes regardless of the presence / absence of a premium and the premium rate. If there is a premium, the fare discount can be realized by preferentially withdrawing money from SF-B and performing a premium return (cashback) at an appropriate timing. Moreover, when there is no premium, it can withdraw with priority from SF-P.
In addition, even if one of SF-B remaining amount (Y remaining amount) and SF-P remaining amount (X remaining amount) disappears, the other can be used, so the user can use the SF card until the amount charged to the card is almost used up. 10 can be used effectively.
Further, by managing the SF card 10 at the management center 40, high-speed processing can be realized even when there are many SF types such as the presence / absence of a premium and the premium rate.
[0113]
Next, a fourth embodiment of the present invention will be described.
This embodiment is for an automatic ticket gate system in which there is a business operator A that operates a railway route without premium and a business operator B that operates a bus route with premium, for example, and performs premium return by a cash back method. This relates to the common use of SF cards. The present embodiment relates to claims 13-17.
[0114]
In the present embodiment, the management center A issues and manages SF without a premium charged by the operator A, and issues and manages SF with premium charged by the operator B at the management center B. ing. The basic roles of the management centers A and B are SF card management such as ID management, SF balance management, and history management. In addition, the common use of the SF card means that each business center under the management of the management centers A and B can charge the SF card issued by each management center and can use the SF in common.
[0115]
Next, common use of cards and premium return (in this case, cashback) will be described.
The relationship between the common use of cards by the carriers A and B and the premium is as follows.
-The SF charged by the operator A is not eligible for the premium regardless of whether it is used by the operator A or the operator B.
-The SF charged by the operator B is eligible for a premium if used by the operator B, but is not eligible for a premium if used by the operator A.
The premium refund amount (cashback amount) is not fixed at the time of charging, and depends on the amount of money spent on the business operator B using SF charged on the business operator B route (for example, bus route).
[0116]
・ The premium refund amount (cashback amount) is
(1) When SF charged by the operator B and used by the operator B reaches a certain amount
(2) When the SF balance charged by operator B becomes zero
To confirm. Since the rate at which the SF charged by the business operator B is used by the business operator B is not known in advance, the premium return amount is determined by the accumulated value of the usage amount. If the premium return amount is proportional to the usage amount, it is not necessary to distinguish between (1) and (2). However, it is usually considered that the return amount increases as the usage amount increases.
[0117]
FIG. 16 is a block diagram showing an automatic ticket gate system according to this embodiment.
In FIG. 16, 40A is a management center by the business operator A, and 40B is a management center by the business operator B. In the following description, the management center 40A is simply referred to as management center A, and the management center 40B is simply referred to as management center B.
50A is a management DB (database, hereinafter referred to as DBA) of the management center A, and 50B is a management DB (hereinafter referred to as DBB) of the management center B. In these DBA and DBB, tables and the like which will be described later necessary for the above-described management are created and held.
[0118]
10A is an SF card issued by the management center A (hereinafter referred to as card A), 10B is an SF card issued by the management center B (hereinafter referred to as card B), and both the card A and the card B are business operators A, Can be used in common on route B. Reference numeral 20 denotes a deposit machine, and 30 denotes an automatic ticket gate. The depositing machine 20 and the automatic ticket gate 30 include those of the business operator A and those of the business operator B, but they are represented by one in the drawing. The automatic ticket gate 30 is a toll box installed in the car in the case of a bus route.
[0119]
Next, the procedure and processing from the deposit to the cards A and B to the cash back by this system will be described. Cards A and B are prepaid tickets composed of IC cards. Further, as a means for calculating the cash back amount, which will be described later, for example, a cash back management table describing the cash back amount with respect to the accumulated usage amount on the bus route such as the return standard table 42 in FIG. The cash back process to be calculated may be performed every time the automatic ticket checker 30 or the depositing machine 20 is passed. The cashback management table may be provided in the automatic ticket gate 30, the deposit machine 20, or the IC card.
[0120]
First, data structures such as prepaid tickets and tables created in each procedure will be described.
FIG. 18 shows the data structure of cards A and B as prepaid tickets (corresponding to claim 13). here,
Card ID: Card unique number
SF balance (A + B): Total SF balance (common balance)
SF balance (B): SF balance charged with B
Usage amount (B → A): Cumulative usage amount of SF charged in B at A (Premium not eligible)
Usage amount (B → B): Cumulative usage amount of SF charged at B at B (premium target)
In the case of card A, the first two items are subject to processing, and in the case of card B, all five items are subject to processing.
[0121]
FIG. 19 shows a table created in the management center.
FIG. 19A is an SF charge table for each business operator. here,
Charge amount at operator A1: Total amount of SF charged by operator A1 under management center A
Charge amount at operator A2: Total amount of SF charged by operator A2 under management center A
Charge amount at business operator B1: Total amount of SF charged by business operator B1 under management center B
Charge amount at operator B2: Total amount of SF charged at operator B2 under management center B
It is.
[0122]
FIG. 19B is an SF usage amount table by business. here,
SF usage amount (A → A): Cumulative usage amount of SF charged by the business under the management of the management center A by the business under the management of the management center A
SF usage amount (A → B): Cumulative usage amount of SF charged by the business under the management of the management center A by the business under the management of the management center B
SF usage amount (B → A): Cumulative usage amount of SF charged by the business under the management of the management center B by the business under the management of the management center A
SF usage amount (B → B): Cumulative usage amount of SF charged by the business under the management of the management center B by the business under the management of the management center B
It is.
[0123]
FIG. 20A shows a deposit-specific statement A created at the time of charging by the business operator A. here,
Card ID: Unique number of the card charged with SF
Operator name: The operator of the route charged SF
Charging date and time: Date and time when SF was charged
Charge amount: SF amount charged
It is.
[0124]
FIG. 20 (b) is a deposit-specific statement B created at the time of charging by the operator B,
Card ID: Unique number of the card charged with SF
Operator name: The operator of the route charged SF
Charging date and time: Date and time when SF was charged
Charge amount: SF amount charged
Cashback amount: Cashback amount determined when SF is charged
It is.
[0125]
FIG. 20 (c) shows a withdrawal single statement A created at the time of use by the business operator A. here,
Card ID: Unique number of the card using SF (issuer can be either management center A or B)
Business name: Business of route using SF
Use date: Date and time when SF was used
Usage amount: SF amount used (withdrawal amount)
SF balance (A + B): SF total amount after using SF (common balance)
It is.
[0126]
FIG. 20 (d) is a withdrawal single statement B created at the time of use by the business B,
Card ID: Unique number of the card using SF (issuer can be either management center A or B)
Business name: Business of route using SF
Use date: Date and time when SF was used
Usage amount: SF amount used (withdrawal amount)
SF balance (A + B): SF total amount after using SF (common balance)
SF remaining amount (B): The remaining amount of SF (B) after using SF
Amount used (B → A): SF used by operator A (B)
Amount used (B → B): SF used by company B (B)
Cashback amount: Cashback amount determined when using SF
It is.
[0127]
In addition to the above, in the management center B, a cashback amount table describing the total amount of cashback performed by the operator B is created.
[0128]
Next, the procedure at the operator A (railway line) will be described along SP1 to SP14 in FIG.
(1) Charge to Card A (10A)
(SP1) The deposit amount is charged to the SF remaining amount (A + B) of the card A from the depositing machine 20 of the business operator A.
(SP2) The depositing machine 20 creates a deposit amount description A (FIG. 20A) and sends it to the management center A.
(SP3) The management center A updates the DBA (management DB 50A) on the basis of the deposit amount specification A.
[0129]
(2) Charge to card B (10B)
(SP4) The deposit amount is charged to the SF remaining amount (A + B) of the card B from the depositing machine 20 of the business operator A.
(SP5) The depositing machine 20 creates a deposit-specific statement A and sends it to the management center A.
(SP6) The management center A sends a deposit-specific statement A to the management center B.
(SP7) The management center B updates the DBB (management DB 50B) on the basis of this deposit amount description A.
[0130]
(3) Withdrawal from card A
(SP8) The withdrawal amount is deducted from the SF remaining amount (A + B) of the card A by the automatic ticket gate 30 of the business operator A.
(SP9) The automatic ticket gate 30 creates a withdrawal one-time statement A and sends it to the management center A.
(SP10) The management center A updates the DBA on the basis of the withdrawal details A.
[0131]
(4) Withdrawal from card B
(SP11) The withdrawal amount is deducted from the SF remaining amount (A + B) of the card A by the automatic ticket gate 30 of the business operator A.
(SP12) The automatic ticket checker 30 creates a withdrawal one statement A and sends it to the management center A.
(SP13) The management center A sends the above withdrawal one statement A to the management center B.
(SP14) The management center B updates the DBB on the basis of the withdrawal details A.
[0132]
Next, the procedure at the operator B (bus route) will be described along SP31 to SP52 in FIG.
(1) Charge to card A
(SP31) The deposit machine 20 of the business operator B performs SF remaining amount correction processing and cash back processing (1) described later.
(SP32) The deposit amount is charged from the depositing machine 20 to the SF remaining amount (A + B) and SF (B) of the card A.
(SP33) The depositing machine 20 creates a deposit amount description B (FIG. 20C) and sends it to the management center B.
(SP34) If there is no record corresponding to the card ID in the DBB, the management center B creates a new record.
(SP35) The management center B updates the DBB based on the new record.
(SP36) The management center B sends the deposit details statement B to the management center A.
(SP37) The management center A updates the DBA on the basis of the deposit details statement B.
[0133]
(2) Charge to card B
(SP38) The deposit machine 20 of the business operator B performs SF remaining amount correction processing and cash back processing (1) described later.
(SP39) The deposit amount is charged to the SF remaining amount (A + B) and SF (B) of the card B from the depositing machine 20.
(SP40) The depositing machine 20 creates a deposit-specific statement B and sends it to the management center B.
(SP41) The management center B updates the DBB based on the deposit amount description B.
[0134]
(3) Withdrawal from card A
(SP42) The charge box (automatic ticket gate) 30 of the business operator B performs cash back processing (1) described later.
(SP43) The charge box 30 deducts the withdrawal amount from the SF remaining amount (A + B) and SF (B) of the card A.
(SP44) The charge box 30 performs a cash back process (2) described later.
(SP45) The charge box 30 creates a withdrawal one statement B and sends it to the management center B.
(SP46) The management center B updates the DBB on the basis of the withdrawal one specification B.
(SP47) The management center B sends the above withdrawal one statement B to the management center A.
(SP48) The management center A updates the DBA based on the withdrawal one specification B.
[0135]
(4) Withdrawal from card B
(SP49) The charge box (automatic ticket gate) 30 of the business operator B performs a cash back process (1) described later.
(SP50) The charge box 30 deducts the withdrawal amount from the SF remaining amount (A + B) and SF (B) of the card B.
(SP51) The charge box 30 performs a cash back process (2) described later.
(SP52) The fee box 30 creates a withdrawal one-statement statement B and sends it to the management center B.
(SP53) The management center B updates the DBB based on the withdrawal one specification B.
[0136]
Next, the SF remaining amount correction process will be described.
When charging on the route of the operator B, the SF amount charged on the route of the operator B before that and used on the route of the operator A can be calculated. This SF amount is
When SF (B)> SF (A + B) SF (B) -SF (A + B)
When SF (B) ≦ SF (A + B) 0
It is. Both card A and card B subtract SF (B) by this amount to correct the remaining SF (B).
[0137]
FIG. 22A is a flowchart showing SF remaining amount correction processing.
First, in S41, it is checked whether SF (A + B) ≧ SF (B). If No, the difference Δ = SF (B) −SF (A + B) is obtained in S42, SF (B) −Δ⇒SF (B) is obtained in S43, and the usage amount (B → A) is obtained in S44. ) + Δ⇒Updated with usage amount (B → A), and the process is terminated. The process is also ended when the answer is Yes in S41.
[0138]
When charging on the route of the operator A, the SF remaining amount that is in the relationship of SF (B)> SF (A + B) may change to the relationship of SF (B) ≦ SF (A + B) after charging. There are two ways to relate this problem. The first method is to perform SF remaining amount correction processing when charging on the route of the operator A. In the second method, upon receipt of the deposit receipt statement A, the management center A decreases the SF usage amount B → A in the SF usage amount table of FIG. → A is increased by Δ. By this measure, a contradiction between the remaining SFs on the card can be resolved.
[0139]
In addition, if the second method is adopted, for example, when there is a system that uses an IC card only on a railway line, when the system is changed so that the IC card can be shared on a bus line, This is advantageous in that it is not necessary to repair the deposit machine on the side and the automatic ticket gate.
[0140]
SF (B) may become 0 as a result of the remaining amount correction or withdrawal prior to the charge at operator B, but this was calculated according to the usage amount because the SF charged at operator B was used up Cash back the amount. FIG. 21 shows an example of the relationship between the accumulated usage amount and the cashback amount. The formula of each straight line in FIG. 21 is as illustrated.
[0141]
FIG. 24 shows a specific example of the SF remaining amount correction process.
As shown in (1), if there is a card B charged by the operator B with 3000 yen, the initial data of this card B is
(1) Common balance (SF balance) = 3000 yen
(2) Bus balance = 3000 yen
(3) Accumulated bus usage = 0 yen
It becomes. It is assumed that the railway line (operator A) is not charged and the balance of the railway is 0 yen.
[0142]
In this state, assuming that the bus of the business operator B is 180 yen, as shown in (2), the common remaining amount = 2820 yen, the remaining bus amount = 2820 yen, and the accumulated bus use amount = 180 yen. Next, if you ride the train for 300 yen, the common balance will be 2520 yen as shown in (3), but since the bus is not used, the remaining balance of the bus is 2820 yen and the accumulated bus usage is 180 yen. .
[0143]
Next, suppose you get a 200 yen bus. In this case, in (3), the bus has already used 300 yen from the bus deposit, and 300 yen out of the remaining amount of the bus cannot be used. I do. Next, as shown in (5), the bus usage amount of 200 yen is subtracted from the common remaining amount and the remaining bus amount, respectively, so that the common remaining amount = 2320 yen, the remaining bus amount = 2320 yen, and the accumulated bus usage amount = 380 yen.
[0144]
In the rewriting process, when the IC card (card B) passes through the fee box 30 or the depositing machine 20, the common remaining amount is compared with the remaining amount of the bus, and when the remaining amount is less than the remaining amount of the bus, rewriting is performed.
[0145]
Next, FIG. 22B is a flowchart showing the cache back process (1).
In S45, it is checked whether SF (B) = 0. If it is 0, the cashback amount α is obtained from the usage amount (B → A) in S46. Then, in S47, it is updated as SF (A + B) + α⇒SF (A + B), and in S48, it is updated as SF (B) + α⇒SF (B), and then the process is terminated. Moreover, a process is complete | finished also when it is No at S45.
[0146]
Next, the cache back process (2) will be described.
When the SF charged by the operator B is used, if the usage amount at B exceeds a certain amount, the amount corresponding to the certain amount is cashed back. The fixed amount is, for example, 5850 yen with reference to the current bus common card, and the cash back amount in that case is 850.
[0147]
FIG. 23 is a flowchart showing the cash back process (2).
In S51, it is checked whether SF (B → B) ≧ amount. If Yes, the cashback amount α is set as the upper limit in S52, and then the amount used (B → B) −the amount ⇒the amount used (B) in S53. → Update as B). Next, in S54, SF (A + B) + α⇒SF (A + B) is updated, and in S55, SF (B) + α⇒SF (B) is updated, and the process ends. If NO in S51, it is checked whether SF (B) = 0 in S56. If 0, the cashback amount α is obtained from the usage amount (B → A) in S57, and then the process of S54 is performed. . Also, if the answer is No in S56, the process proceeds to S54.
[0148]
Information such as the common balance, balance, and accumulated usage amount obtained by each of the above processes is sequentially transmitted to the management centers A and B via the charge box 30 and the depositing machine 20. Each management center can perform management processing and the like based on the received information. Further, the amount to be cashed back is returned in the form of being added to the common balance of the IC card when passing through the charge box 30 or the depositing machine 20.
[0149]
In this embodiment, the cash back process is performed by the depositing machine and the automatic ticket gate. For this purpose, the accumulated usage amount as a means for calculating the cash back amount is included in the depositing machine and the automatic ticket gate. A cashback management table describing the cashback amount for the card is provided, and the cashback amount calculated based on this table is transmitted to the IC card and added to the common remaining amount. Further, each time the IC card passes through the deposit machine and the automatic ticket gate, it receives each data including the common remaining amount shown in FIG. 18 and updates them (corresponding to claim 14).
[0150]
Further, the cash back management table may be provided in the IC card, and the cash back processing may be performed in the IC card. In that case, every time the IC card passes the deposit machine and the charge box, a cashback amount is calculated, and a process of adding it to the common remaining amount is performed. At the same time, each data shown in FIG. 18 is updated based on the deposit amount at the deposit machine, the withdrawal amount at the automatic ticket gate, and the like (corresponding to claim 15). Furthermore, SF remaining amount correction processing is performed as necessary (corresponding to claim 16). Each information such as the result of cash back processing in the IC card is transmitted to the management center (corresponding to claim 17).
[0151]
When cash back processing is performed at the management center, search processing for specifying the card (the card currently being handled) is required. However, when cash back processing is performed with an IC card as described above, this is the case. Search processing can be omitted.
[0152]
In addition, when the cashback management table is provided in the IC card, the depositing machine 20 or the automatic ticket gate (charge box) 30, the management centers A and B transmit the IC card, the depositing machine 20 and the automatic ticket gate 30. Based on the information, the card ID, the deposit amount for each company, the accumulated usage amount for each company, and the like are managed.
[0153]
In the present embodiment described above, the case where the number of operators managed by the management centers A and B is one each has been described. However, even when there are more premium types, that is, each management center A and B manages. When the number of business operators is 2 or more, the number of management centers is 3 or more, and there are multiple premium rates, a management center is provided according to each type, and can be easily realized by the same concept as described above. .
[0154]
Next, a fifth embodiment of the present invention will be described. In addition, this Embodiment respond | corresponds to Claims 18-21.
The present embodiment is not a cash back method described above, but a premium return method. While the cashback method returns the amount itself to the common balance, the premium refund method discounts the fare by refunding the premium amount corresponding to the accumulated usage amount on the bus route to the remaining SF amount on the bus route It is a method to perform. The basic procedure and processing are almost the same as the cash back method. The data structure of the prepaid ticket is substantially the same as that shown in FIG. 18 (corresponding to claim 18).
[0155]
The premium return system according to the present embodiment includes an IC card management system and a management center management system.
In the IC card management method, the premium return process is performed by providing a premium management table indicating the premium amount corresponding to the accumulated amount used by the business with a premium in the IC card as the premium return amount calculation means. The calculated premium refund amount is added to the SF remaining amount on the bus route, and the common remaining amount, the SF remaining amount on each route, and the accumulated usage amount are updated based on the deposit amount and withdrawal amount. (Corresponding to Claim 20), these processing results are transmitted to the management center (corresponding to Claim 21).
[0156]
The premium management table may be provided in the deposit machine 20 or the automatic ticket gate 30. In that case, each time the IC card passes through the depositing machine and the automatic ticket gate, each data in the card is updated (corresponding to claim 19). Further, the management center manages the card ID, the deposit amount, the accumulated usage amount, etc. based on the information from the IC card, the deposit machine, and the automatic ticket gate.
[0157]
In the management system in the management center, a premium management table is provided in a management center of a business with a premium, and the management center manages a common remaining amount, a deposit amount, a cumulative usage amount, and the like for each business. Then, a payment details statement indicating the card ID, usage amount, business name, etc. is transmitted from the IC card to the management center via the deposit machine or the automatic ticket gate. In addition, a withdrawal details statement is sent from the depositing machine or automatic ticket gate to the management center. Information such as a card ID, a premium amount, and a business name is transmitted from the management center to the IC card via a deposit machine and an automatic ticket gate.
[0158]
Each embodiment described above solves the problem in the common use of a prepaid ticket (SF card), but the present invention is applied to a prepaid card generally used, a reading device thereof, and the like. Thus, it is clear that the present invention can be applied to common use of prepaid cards other than prepaid tickets. That is, the prepaid card shared by the present invention can be used for other services (shopping at a store, etc.).
[0159]
【The invention's effect】
As described above in detail, according to the present invention, as long as the prepaid amount remains, the user can use a plurality of public transportation facilities using a single common ticket, For a person, it is possible to prevent a loss that may occur due to commonality associated with the presence or absence of a premium or a difference in premium rate.
Further, according to the present invention, for a user, any one of the prepaid charges using a single common ticket storing prepaid information corresponding to a plurality of prepaid charges for a plurality of transportation operators. As long as it remains, a plurality of public transportation systems can be used, and for the business operators, loss that may occur due to the presence or absence of premiums or due to differences in premium rates can be prevented.
Further, according to the present invention, prepaid information corresponding to a plurality of pre-payments for a plurality of transportation operators is stored and used in one common ticket, so the number of conventional ticket vending machines can be reduced. It becomes.
In addition, in the case of the cash back method, the cash backed amount can be used in common on each route regardless of whether there is a premium or not.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of an automatic ticket gate system according to a first embodiment of the present invention.
FIG. 2 is an operation flowchart of the automatic ticket gate according to the embodiment.
FIG. 3 is an example for explaining processing of the automatic ticket gate according to the embodiment;
FIG. 4 is an example for explaining processing of the automatic ticket gate according to the embodiment;
FIG. 5 is an example for explaining processing of the automatic ticket gate according to the embodiment;
FIG. 6 is a block diagram showing a configuration of an automatic ticket gate system according to a second embodiment of the present invention.
FIG. 7 is an operation flowchart of the charging machine of the embodiment.
FIG. 8 is an operation flowchart of the automatic ticket gate according to the embodiment.
FIG. 9 is a flowchart for explaining a clearing process in the clearing center according to the embodiment;
FIG. 10 is a graph for explaining in principle the third embodiment of the present invention;
FIG. 11 is a configuration diagram showing an example of a return criterion table used in the embodiment.
FIG. 12 is a block diagram showing a configuration of an automatic ticket gate system according to the embodiment.
FIG. 13 is a flowchart showing a deposit process of the management center in the same embodiment.
FIG. 14 is a flowchart showing a withdrawal process of the management center in the same embodiment.
FIG. 15 is a flowchart showing a return process of the management center in the embodiment.
FIG. 16 is a block diagram showing a configuration and an operation procedure of an automatic ticket gate system according to a fourth embodiment of the present invention.
FIG. 17 is a block diagram showing another operation procedure in the same embodiment;
FIG. 18 is a block diagram showing a data structure of the IC card in the same embodiment.
FIG. 19 is a configuration diagram showing a data structure of a SF charge amount table for each business in the embodiment;
FIG. 20 is a configuration diagram showing a data structure of a deposit-specific statement and a withdrawal-specific statement for each business in the embodiment;
FIG. 21 is a graph showing the relationship between the accumulated usage amount and the cashback return amount in the same embodiment.
FIG. 22 is a flowchart showing SF remaining amount correction processing and cash back processing (1) in the embodiment;
FIG. 23 is a flowchart showing a cash back process (2) in the embodiment;
FIG. 24 is a block diagram showing a specific example of SF remaining amount correction processing in the embodiment;
[Explanation of symbols]
1, 1 '... Prepaid ticket
2 ... Ticketing machine
2 '... Charge machine
3, 3 '... Automatic ticket gate
4 ... Liquidation Center
10 ... SF card (prepaid common ticket)
11 ... Card information table
20 ... Deposit machine
21 ... Detailed information on deposit
30 ... Automatic ticket gate
31 ... Details of one withdrawal
40 ... Management Center
41 ... SF management table
42 ... Return standard table
43 ... SF return table
10A ... Card A
10B ... Card B
40A ... Management Center A
40B ... Management Center B
50A ... Management database A
50B ... Management database B

Claims (4)

In an automatic ticket gate that accepts a common ticket used in common among multiple public transportation systems,
Business identification information for identifying a business for which a prepaid fee has been paid, a premium balance in which a premium amount determined for each business is set as an initial value corresponding to the business identification information, and an initial When a user performs a predetermined operation on the automatic ticket checker using a predetermined common ticket storing prepaid management information including a prepaid balance in which a prepaid fee is set as a value, the fare is determined In order to collect
The automatic ticket gate
A reading unit that reads the prepaid management information from the common ticket;
It is determined whether the premium balance can be used from the prepaid management information. If it is determined that the premium balance is usable, the discount amount is calculated based on the prepaid balance and the premium balance for the fare. And subtracting the amount obtained by subtracting the discount amount from the fare from the prepaid balance, further subtracting the discount amount from the premium balance, and updating the prepaid management information of the common ticket using the prepaid balance and the premium balance, If it is determined in the above determination that the premium balance is not available, the amount corresponding to the fare is subtracted from the prepaid balance, and if there is a premium balance, the discount amount is further subtracted from the premium balance, and the prepaid balance And the prepaid management information of the common ticket using the premium balance Automatic ticket gate, characterized in that it comprises a ticket information updating unit for updating the. The automatic ticket gate
Based on the prepaid management information of the common ticket used by each user, the predetermined information including the amount billed to other transportation operators is transmitted to the clearing center that performs processing related to fee settlement between transportation operators The automatic ticket gate according to claim 1, wherein: An automatic ticket gate system using the automatic ticket gate according to claim 2 , wherein the automatic ticket gate system includes:
When prepaid by a user, the prepaid management information is stored in the common ticket, and the ticket issuing machine transmits predetermined information including the prepaid management information to the clearing center,
The Clearing Center is
An automatic ticket gate system that receives predetermined information sent from the automatic ticket gate and the ticket issuing machine, and performs a clearing process related to a fee settlement between a transportation company using the automatic ticket gate system. A ticket using a magnetic card or an IC card that can be used as the common ticket for the automatic ticket gate according to claim 2 ,
Operator identification information to identify the operator for which the prepayment fee was paid,
Corresponding to the operator identification information, a premium remaining amount in which a premium amount determined for each operator is set as an initial value,
Prepaid balance with prepayment set as initial value,
Prepaid information, including prepaid date and
Each time a prepayment is made by a user, the ticket is added to and stored in the prepaid management information.

Images