JP2013178600A - Electronic ticket system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce the used memory capacitance/communication data amount of a ticket examination gate by selecting ticket information to be distributed to the thicket examination gate even if a station that a passenger enters/leaves is not known, while improving affinity with devices introduced at present and without damaging passenger convenience, by providing a long-distance ticket in the form of an IC card to the passenger who does not have or utilize a mobile phone integrated with an IC card.SOLUTION: A ticketless server estimates one or more stations that a passenger may utilize, on the basis of information of a ticket and a received utilization history of the passenger, and distributes the information of the thicket to a station server of a station. The station server distributes the distributed ticket information to a ticket examination gate and when pass information of the passenger is acquired, the ticket examination gate writes information of the ticket onto the IC card of the passenger.

Description

  The present invention relates to an electronic ticket system.

  Mobile Suica and EX-IC exist for long-distance ticketless. For example, in the technology described in Patent Document 1, tickets are distributed in advance via a mobile phone, the minimum necessary check is performed at the time of entry, and the passenger company server is inquired and authenticated while boarding. Methods are sometimes disclosed that do not allow exit.

Japanese Patent Application No. 2001-1541111

  In the technique described in Patent Document 1, it is necessary to distribute a ticket to a mobile phone in advance. For this reason, the technique described in Patent Document 1 does not describe a technique for distributing ticket information to a passenger who does not use a mobile phone integrated with an IC card.

  Further, as a technique for distributing ticket information without using a mobile phone integrated with an IC card, there is an EX-IC technique, for example. In EX-IC, ticket information is distributed to the ticket gates of the stations that enter and exit. However, if this is applied to a conventional line, it is necessary to distribute ticket information to a wide range of stations without knowing which station is entering or leaving. For this reason, there is a problem that the amount of data to be distributed becomes enormous.

  In order to solve the above problem, the ticketless server estimates one or more stations used by the passenger based on the ticket information and the received passenger usage history, and distributes the ticket information to the station server of the station. Then, the station server distributes the distributed ticket information to the ticket checker, and when the ticket checker acquires the passing information of the passenger, the ticket server writes the ticket information on the IC card of the passenger.

  The ticket information stored in the ticket gate can be reduced while the ticket information is distributed to passengers who do not use the mobile phone integrated with the IC card.

It is an example which shows a system configuration. It is a figure which shows an example of the hardware constitutions of an operation management apparatus. It is an example of the flow of the flow of ticket information. It is a figure which shows an example of the delivery ticket selection flow at the time of entrance. It is a figure which shows an example of the narrowing-down flow of the delivery area at the time of entrance. It is a figure which shows an example of the narrowing-down flow of a delivery card. It is a figure which shows an example of the selection processing flow of the ticket at the time of admission delivered to a ticket gate. It is a figure which shows an example of the delivery ticket selection flow at the time of appearance. It is a figure which shows an example of the narrowing-down flow of the delivery area at the time of participation. It is a figure which shows an example of the selection processing flow of the ticket at the time of admission delivered to a ticket gate. It is a figure which shows an example of the screen which confirms the state of the ticket which a passenger has, and sets the utilization of a ticket.

A case where the present invention is applied to purchasing a long-distance ticket will be described as an example. FIG. 1 is a system configuration diagram of an electronic ticket system.
The ticketless server 1 holds a member management table 1051 that manages (stores) ticketless members, a ticket usage condition table 1052 that manages usage conditions of tickets to be handled, and a ticket table 1053 that manages information on tickets to be handled. The ticketless server 1 is connected to the management terminal 7 where the operator 11 sets the ticket usage conditions, the operation terminal 5 where the passenger purchases the ticket, and the ID management server 2 which manages the ticket gate system. Ticket management unit 1002 that performs ticket reservation / settlement based on a request from the operation terminal 5 and distribution of ticket information / ticket use conditions to the ID management server 2; reference / addition / deletion / change of ticketless member Has a function of a member management unit 1003 for

  The ID management server 2 includes a fare table 2051 for managing fares between stations, an IC card management table 2053 for managing ID / balance / type of IC cards, an IC card usage history 2052, and an ID of an IC card using the same day ticket. The ticket use IC card table 2054 is held, and is connected to each station server 3. Here, the ticket is, for example, a medium-long distance ticket, and the IC card is a short-distance ticket. The ID management server 2 accumulates the use history of the IC card notified from each station server at regular intervals by communicating with the ticketless server 1, the communication unit 2001 communicating with each station server 3, and responding to the request from the ticketless server 1 The history management unit 2002 that refers to the history information, the ticket information mediation unit 2003 that transfers the ticket information distributed from the ticketless server 1 to each station server 3, and the passing information of the passenger 10 that is notified from the station server 3 It has a function of a passage information mediation unit 2004 for transferring to the ticketless server 1.

  The station server 3 is a server installed at each station, and includes a fare table 3051 for managing the fare between stations, a ticket use condition table 3052 distributed from the ticketless server 1, a ticket table 3053, and ticket information as ticket gates. The distribution schedule table 3054 for managing the schedule to be distributed to the station is connected to the station employee terminal 6 for referring to and adjusting the ticket information for the inquiry from the passenger, and the ticket gate 4 for determining entrance / exit. The station server 3 includes the ID management server 2, the station employee terminal 6, a communication unit 3001 that communicates with the ticket gate 4, a ticket reception unit 3004 that receives ticket information from the ticketless server 1, and a ticket to the ticket gate 4 It holds the functions of a ticket distribution unit 3002 that distributes information, and a passage notification unit 3003 that acquires that the passenger has passed from the ticket gate and notifies the ticketless server. It is assumed that the fare table 3051 and the ticket use condition table 3052 are distributed to the station server 3 at each station when the operator 11 sets the fare table 3051 and the ticket use condition table 3052.

  One or more ticket gates 4 are installed in the ticket gate, connected to the station server 3 via a network, and hold a fare table 4051, a ticket use condition table 4052, and a ticket table 4053 distributed from the station server 3. The ticket gate 4 includes a communication unit 4001 that communicates with the station server 3, a settlement unit 4003 that settles a fare between an entrance station and a departure station, and a ticket selection that selects a ticket to be used when a plurality of tickets exist. Unit 4004, a ticket receiving unit 4005 that receives ticket information from the station server 3, a passage notification unit 4006 that notifies the station server that the IC card 8 that the passenger has touched the ticket gate, and an IC card 8 that the passenger has. An IC card read / write unit 4007 that detects touching and writes necessary information, and a gate operation unit 4008 that operates the gate in cases where illegal boarding or a collected fare is insufficient for SF (Stored Fares).

  The ticketless server 1, the ID management server 2, and the station server 3 use a server or a personal computer, the operation terminal 5 uses a personal computer or a mobile phone, the station employee terminal uses a PC with an IC card reader / writer, and the management terminal uses a personal computer. The system can be configured by using Felica for the IC card 8.

  FIG. 2 shows the hardware configuration of the ticket gate. A fare table 4051, a ticket use condition table 4052, a storage device 452 that holds the ticket table 4053, a communication device 454 controlled by the communication unit 4001, a settlement unit 4003, a ticket selection unit 4004, a ticket reception unit 4005, and a passage notification unit 4006 A control device 453 that operates, a display device 455 that displays ticket information and a settlement amount / balance when passing through a ticket gate, an IC card reader / writer 456 operated by an IC card read / write unit 4007, and a gate 451 controlled by a gate operation unit 4008 Consists of.

  This will be described below using a specific example. In using this system, the operator 11 sets the fare tables 2051, 3051, and 4051 and the ticket use condition tables 1052, 3052, and 4052. The operator 11 sets a fare table 2051 from an ID management server management terminal (not shown) connected to the ID management server 2 via a network. At the timing when the fare table 2051 is updated, the fare table 3051 of the station server 3 and the fare table 4051 of the ticket gate 4 are mirrored. The fare table 2051 is a table that defines the fare between two stations, and is composed of a station 1, a station 2, and a fee. For example, when the fare from the station X to the station Y is 300 yen, the station 1 “station X”, the station 2 “station Y”, and the charge “300” are set. Further, the operator 11 sets the ticket use condition table 1052 from the management terminal 7. At the timing when the ticket use condition table 1052 is updated, the ticket use condition table 3052 of the station server 3 and the ticket use condition table 4052 of the ticket gate 4 are mirrored. The ticket use condition table 1052 describes type IDs and use conditions. For example, in the case of the type ID “ticket”, “use ticket when the boarding section completely includes the ticket section” is used as the use condition, and in the case of type ID “express ticket”, the use condition is “train "When the ticket check is performed in" and "When passing the express gate" are set.

  Further, when using this system, the passenger 10 performs a member registration operation from the operation terminal 5, and sets a user ID and a password that uniquely indicate the passenger 10 and an ID of an IC card to be used to the ticketless server 1. The ticketless server 1 receives the user ID, password, and IC card ID, and registers the information in the member table 1051 by the member management unit 1003. In addition, when the passenger 10 purchases a ticket, the passenger 10 inputs a user ID and a password from the operation terminal 5 and transmits them to the ticketless server. The ticketless server 1 passes the received information to the member management unit 1003, and the member table It is assumed that the user ID and password managed in 1051 are collated and authenticated.

  FIG. 3 shows the overall flow of the ticketless system. Passenger A with an IC card of ID “C” is a ticket from station X to station Y on October 31, 2011, and train P from station X to station Y is 12:00 and arrives at 13:00 Details of the processing will be described using an example of purchasing and using an express ticket for seat Q.

  At the time of purchase (T1), the passenger 10 performs a ticket purchase operation with the operation terminal 5 (T11). In the case of a ticket type ID, use date, section, fee, and designated ticket, the train number and seat are ticketless servers. (T12), the ticket management unit 1002 secures the ticket and stores it in the ticket table 1053. The ticket table 1053 includes a ticket ID that uniquely identifies a ticket, an IC card ID, a type ID that indicates a ticket type, a usage date that indicates a business day on which the ticket can be used, an interval 1 that indicates an end point of the ticket interval, an interval 2, The ticket fee is composed of a fee, train number, seat, departure time, arrival time, and ticket status. The illustrated ticket is “T0001” for the ticket ID, “C” for the IC card ID, and “ticket” for the type ID. ”,“ October 31, 2011 ”, section 1“ station X ”, section 2“ station Y ”, fee“ 8000 yen ”, ticket status“ undelivered ”, and NULL are stored in other fields. The On the other hand, the limited express ticket is “T0002” as the ticket ID, “C” as the IC card ID, “limited express ticket” as the type ID, “October 31, 2011” as the usage date, section 1 “station X”, section 2 “ Station Y ", fare" 11000 yen ", train number" P ", seat" Q ", departure time" 12:00 ", arrival time" 13:00 ", and ticket status" undelivered "are stored.

  In the ticket distribution (T2) when entering the station server, for example, the ticket management unit 1002 is activated at night such as AM 2:00 or when the passenger 10 purchases a ticket. The “delivery” ticket is delivered to the station server 3 (T21). Details of the distribution process will be described later. When the distribution is completed, the ticket status of the record in the ticket table 1053 is changed to “distributed”. At this time, the intermediary ID management server 2 stores the ID information of the IC card using the ticket in the ticket use IC card table 2054 from the received ticket information. That is, the ticketless server estimates one or more stations used by the passenger based on the ticket information and the received passenger usage history, and distributes the ticket information to the estimated station server. In the ticket distribution (T3) when entering the ticket gate, the ticket distribution unit 3002 is activated when the station server 3 receives the entrance ticket from the ticketless server 1, and the ticket type, the passenger's SF balance, and the past movement history are displayed. Based on the determination of the necessity of distribution of ticket information to the ticket gate 4 and the distribution schedule are determined (T31), and the ticket is distributed (T32). That is, the station server distributes the distributed ticket information to the ticket checker, and when the ticket checker acquires the passing information of the passenger, the ticket server writes the ticket information on the IC card of the passenger. Details of the determination of whether or not ticket information is to be distributed and the determination of the distribution schedule will be described later.

  When the passenger enters (T4), the passenger 10 is activated when the IC card 8 touches the ticket gate 4 (T41), the IC card read / write unit 4007 reads the IC card ID (T42), and the ticket table 4007 is referred to. If the ticket corresponding to the IC card ID exists in the ticket gate, the IC card read / write unit 4007 writes the ticket information, the entrance station, and the entry time, and otherwise the entry information and the entry time to the IC card 8. (T43). Thereafter, the passage notification unit 4006 notifies the station server 3 of the success or failure of writing the IC card ID and ticket information of the passenger 10 (T44), and the station server 3 that has received the notification by the passage notification unit 3003 is the ID management server. 2 is notified of the success or failure of writing the IC card ID and ticket information. The ID management server 2 notifies the ticketless server 1 of the ticket information writing success information and the ticket information writing failure information that the IC card is registered in the ticket use IC card table 2054 (T45). Upon receiving the notification, the ticketless server 1 activates the ticket management unit 1002 and updates the status of the ticket table 1053 to “successful IC card entry” when writing is successful and “IC card entry failure” when it fails. . That is, if the ticket checker cannot write the ticket information to the passenger's IC card, the ticket management machine notifies the ID management server, and the ID management server receives the ticket information received from the ticketless server among the IC cards that are not allowed to write the ticket information. A certain IC card is notified to the ticketless server.

  In the participation ticket distribution (T5) to the station server, the ticket management unit 1002 is activated at the timing when the ticketless server 1 receives the passage notification, or at regular intervals such as 5 minutes, and the participation ticket is sent to the station server 3. Then, it is delivered (T51). That is, the ticketless server acquires the passenger's departure station from the ticket information, and distributes the ticket information to one or more stations including the departure station. Details of the distribution process will be described later.

  Ticket distribution (T6) upon entry to the ticket gate is activated when the station server 3 receives a ticket from the ticketless server 1, determines whether or not ticket information needs to be distributed to the ticket gate 4 (T61), and the ticket Is distributed (T62). That is, the station server distributes the distributed ticket information to the ticket checker, and when the ticket checker acquires the passing information of the passenger, the ticket server writes the ticket information on the IC card of the passenger. Note that details of the determination as to whether ticket information needs to be distributed will be described later. When the passenger 10 participates (T7), it is activated when the passenger 10 touches the ticket card 4 with the IC card 8 (T71), and the IC card read / write unit 4007 stores the IC card ID and ticket information written on the IC card. Read (T72), if the IC card has a ticket, obtain ticket information. If the IC card does not have a ticket, refer to the ticket table 4007 to obtain a ticket corresponding to the IC card ID, and select a ticket. The part 4004 refers to the ticket use condition table 4052 to determine whether or not to use the ticket, the settlement part 4003 calculates the settlement amount, and writes the result to the IC card (T73). For example, if the order of stations on a certain route is W station-X station-Y station-Z station, and passenger A who has a ticket from X station to Y station enters at W station and enters at Z station, Since the condition “the boarding section is included in the ticket section” is satisfied, the ticket is determined to be used. Refer to the fare table 4051 for the charges from the W station to the X station and the charges from the Y station to the Z station. The total is subtracted from the SF of the IC card 8. On the other hand, if passenger A enters at Y station and exits at Z station, it does not satisfy the ticket usage conditions, so it is determined that the ticket will not be used, and the fare table 4051 shows the fare from Y station to Z station. The information is obtained by reference and is subtracted from the SF of the IC card 8, and if a ticket is entered, the information is deleted. If the SF balance is insufficient, the gate of the ticket gate is closed. If it is not possible to determine whether to use the ticket, the gate of the ticket gate is closed and the passenger 10 is notified to go to the manned window.

  After that, the passage notification unit 4006 notifies the station server 3 of the passenger ID as a passage notification of the passenger 10 (T74), and the station server that received the notification by the passage notification unit 3003. 3 sends a pass notification to the ticketless server 1 via the ID management server 2 (T75). Upon receiving the notification, the ticketless server 1 activates the ticket management unit 1002 and changes the state of the ticket table 1053 to “used” when the ticket is used, and “unused” when the ticket is not used. Update.

  FIG. 4 shows an example of the processing flow of ticket distribution (T2) upon entry to the station server. In step S211, all tickets having a usage date of today and a ticket status “undelivered” are acquired from the ticket table 1053. In S212, the IC card attribute and usage history are requested to the ID management server 2 for all the IC card IDs associated with the acquired ticket. Upon receiving the request, the ID management server activates the history management unit 2002, acquires the IC card attribute from the IC card management table 2053, and the usage history from the movement history table 2052 using the IC card ID as a key. Here, it is assumed that the movement history table 2052 includes an IC card ID that uniquely identifies an IC card, an entry date / time, an entry date / time, an entrance station, an exit station, a fee, and a balance. The IC card management table 2053 stores an IC card ID and a credit card number associated with the IC card. Note that the usage history period to be acquired may be limited to a certain period such as the last six months, or may be the entire period in which data is accumulated.

  In step S213, the area for distributing ticket information is narrowed down. Details will be described with reference to FIG. In step S <b> 2131, the history management unit 2002 counts the number of times for each station and time zone that has entered and exited based on the acquired IC card usage history. As a result, frequently used stations and time zones are extracted and stored as frequently used station information and frequently used time zone information for each entry / exit. For example, during the past 6 months, passenger A has entered the W station from 7 am to 8 am 120 times, from 20 to 9 am, has entered the W station 20 times, and from 9 am to 10 am 3 times, 3 times from X station, 0 times from Y station, 120 times from Z station between 8:00 and 9:00, 120 times from 9:00 to 10:00 If the number of appearances is 20 times, and the number of participations between 10 am and 11 am is 3 times, it can be seen that the frequency of entering W station between 7 am and 8 am and Z station between 8 am and 9 am is high. , “W station” “7 to 8 o'clock” as the frequently used station / time zone information for admission, “Z station” “8 o'clock to 9 o'clock” as the frequently used station / time zone information for entry Is set. By selecting such a frequently used station as a ticket distribution destination, it is possible to increase the hit rate of the station through which the passenger 10 passes at the time of entry, and to reduce the number of tickets distributed at the time of participation.

  In step 2132, the hitting station of the most recent use history is referred to, and the hitting station is selected as a ticket delivery destination, thereby increasing the hit ratio of the station through which the passenger A passes.

  Alternatively, a station management table that manages latitude and longitude corresponding to a station (not shown) may be referred to, and a station located within a certain distance from the participating station may be extracted and added to the ticket distribution destination. For example, when passenger A enters W station at 36.0 degrees north latitude and 135.5 degrees east longitude, passenger A is expected to ride from 36.001 degrees north latitude and 135.0001 degrees east longitude. As a result, it is possible to increase the hit rate of the station through which the passenger 10 passes and to reduce the number of tickets to be delivered when entering.

  Alternatively, a station that can be connected by a bus corresponding to a station (not shown) is referred to, a station that can be reached by bus from the participating station may be extracted and added to the ticket distribution destination. For example, if U station that can be reached by a route bus from W station is managed in this table, and there is a bus use history immediately after X station in the most recent railway use history, ticket to U station Distribute information. Thereby, the hit rate of the entrance station of the passenger 10 when there is a bus change can be increased, and the number of tickets distributed at the time of participation can be reduced.

  Alternatively, if the total number of users at each station for a certain period is extracted from the movement history table 2052 of the ID management system 2 and the number of users at stations near the boarding station of the ticket is small, it can be added to the ticket distribution destination. good. As a result, for example, when taking a limited express train from a rural station with a small number of users to a city station, the hit rate of the station that passes when the passenger 10 enters the country station is increased, and the number of tickets to be distributed at the time of participation Can be reduced.

  In step S214, the IC card for distributing the ticket information is narrowed down and the priority is set. Details will be described with reference to FIG. In step S <b> 2141, it is determined whether or not the initial boarding fare is less than or equal to the SF balance obtained from the latest usage history. If it is less than the initial fare, you will not be able to enter the ticket gate at the time of entry, and you will have to insert the IC card into the checkout machine. You can write it at this time, so you can exclude it from the distribution target and set the priority to “None” To do. If it is equal to or higher than the initial boarding fare, the process proceeds to step S2142. In step S2142, it is determined from the data acquired from the IC card management table whether the IC card is associated with a credit card. If you are tied to a credit card, you can pay additional or refund via credit even if you miss or overcharge, so set the priority to distribute ticket information to “Low” (S2144). On the other hand, if it is not associated with a credit card, there is a possibility that a charge may be missed, so the priority for distributing ticket information is set to “high” (S2143). As a result, it is possible to preferentially distribute passenger tickets that are likely to miss charges.

  Alternatively, the priority may be set to “medium” for an IC card in which the SF balance obtained from the latest history information is higher than the charge of the ticket to be distributed, since the possibility of missing the charge is low.

  In step 216, the ticket information, the frequently used station / time zone information obtained in step S213, and the priority set in step S214 are transmitted to all the station servers 3.

  FIG. 7 shows an example of a processing flow of ticket distribution (T3) when entering the ticket gate. This process is started according to the schedule set by the operator such as once when ticket information is received from the ID management server or once every hour, and the following process is performed for all passengers holding the distributed tickets. Do. In step S311, with reference to the ticket information distributed from the ID management server and the frequently used station / time zone information for each user, the station where the ticket is distributed is a station frequently used by passengers holding tickets. Determine if. In the case of a frequently used station, the start time of a frequently used time zone is set as the distribution time (S312). Otherwise, no time is set as the delivery time. In the case of the W station in the passenger A, since the use frequency of 8:00 to 9:00 is high, 8:00 is set as the distribution time.

  In step S313, it is determined whether or not the designated ticket is included in the distributed ticket. When the designated ticket is not included in the ticket, the delivery time is not updated. When the designated ticket is included in the ticket, the required time from the station to the ticketing station is acquired from a standard time table between stations (not shown) that stores the standard required time between the two stations (S314) and operated in advance. The station departure time set in time for the designated ticket issuing time is calculated by subtracting the margin time set by the person 11 (S315). For example, when the required time from W station to X station is set to 30 minutes and the margin time is set to 15 minutes, the departure time of W station in time for the 12:00 train is calculated as 11:30 minutes.

  In step S316, the station departure time is compared with the delivery time set in S312. If the station departure time is earlier than the delivery time, the station departure time is set as the delivery time (S317). In the above example, the station departure time is not updated because it is later than the distribution time determined from the usage frequency.

  In step S318, the distribution time is compared with the current time. If the current time has passed the distribution time, the ticket information is immediately distributed to the ticket gate (T32). Otherwise, the ticket ID and delivery time are written in the delivery schedule table 3054. In the above example, when passenger A has purchased a ticket by the previous day, 8:00 is set as the delivery time. When passenger A purchases a ticket at 8:30 on the day, ticket information is distributed to the ticket gate.

  If the number of tickets to be distributed simultaneously is large, the tickets are distributed to the ticket checker in the order of the highest priority, the number set in advance by the operator 11 or the number of ticket information with the priority “high”. .

FIG. 8 is a diagram illustrating an example of the process of participating ticket distribution (T5) to the station server.
In step S511, all the tickets whose usage date is today and whose ticket status is “IC card entry failure” are acquired from the ticket table 1053. In S512, for all the IDs of the IC card associated with the acquired ticket, the ID management server 2 is requested for the attribute of the IC card and the latest usage history. Upon receiving the request, the ID management server activates the history management unit 2002 and acquires the most recent usage history from the movement history table 2052 and the IC card attribute from the IC card management table 2053 using the IC card ID as a key.

  In step 514, the distribution stations are narrowed down. Details are shown in FIG. In step S5141, the ticket use condition is acquired from the ticket use condition table 1052. In step 5142, all the getting-off station candidates that match the ticket usage conditions are acquired based on the ticket usage conditions and the station where it was determined that the ticket could not be written. For example, in the above example, if the station is lined with V station-W station-X station-Y station-Z station-Z1 station-Z2 station-Z3 station after Z station, the ticket for X station-Y station is If the ticket cannot be written after entering at the station W, the Z station, the Z1 station, the Z2 station, and the Z3 station are targeted for distribution.

In step 515, narrowing down by IC card is performed. The details of this processing are the same as the processing described in FIG.
In step 517, for all the station servers 3, the ticket information, the stations that may be entered using the ticket acquired in step S514, the priority set in step S515, and the SF balance are displayed. Send.

  FIG. 10 shows a flow for selecting a ticket to be sent from the station server to the ticket gate at the time of participation in the ticket distribution at the time of entry to the ticket gate (T6). In step S611, the fare table 3051 is referred to, and the fare from the nearest station in the ticket section to the station is calculated. For example, when this processing is performed at Z station, when calculating the fare for a ticket between X station and Y station, a fee between Y station and Z station is calculated.

  In step S612, the calculated fare is compared with the SF balance. When the SF balance is small, the ticket is not delivered to the ticket gate because the balance is insufficient and the ticket gate 4 cannot be passed. In this case, the settlement is performed when the IC card 8 is inserted into the settlement machine. If the SF balance is large, a ticket is distributed (S613).

  With these processes, the number of tickets that must be distributed to the entire ticket gate can be reduced by distributing tickets roughly at the time of entry.

  FIG. 11 shows an example of a screen for confirming the status of the ticket held by the passenger and setting the use of the ticket on the operation terminal 5. This screen is generated when the passenger 10 operates the operation terminal 5 and acquires the ticket information of the passenger from the ticket table 1053 of the ticketless server 1. The screen includes a ticket ID 501, a use date 502, a ticket type 503, a departure station 504, a destination station 505, a ticket status 506, and an operation button 507 for determining whether or not the ticket is used on that day. The When this operation button is pressed, the ticket gate at each station is notified that the ticket is to be used for the ticket, and the ticket selection unit 4004 forcibly uses the ticket without referring to the ticket use condition table 4052.

  According to the present embodiment, a long-distance ticket is provided with an IC card for passengers who do not have or use a mobile phone integrated with an IC card, and has high compatibility with currently installed devices, and The ticket information to be distributed to the ticket gate can be selected even when the entry / exit station is not known in advance without reducing the convenience of the passenger, and the amount of memory used and the amount of communication data of the ticket gate can be reduced.

1: ticketless server, 2: ID management server, 3: station server, 4: ticket gate, 5: operation terminal, 78: IC card, 10: passenger

Claims (13)

The ticketless server estimates one or more stations used by the passenger based on the ticket information and the received use history of the passenger, and distributes the ticket information to the estimated station server of the station. ,
The station server distributes the distributed ticket information to a ticket gate,
The ticket gate writes the ticket information into the passenger's IC card when the passenger's passage information is acquired. When the ticket checker fails to write the ticket information to the passenger IC card, it notifies the ID management server,
The ID management server notifies the ticketless server of an IC card with ticket information received from the ticketless server among IC cards that are not permitted to write ticket information,
The ticketless server acquires the passenger's departure station from the ticket information, and distributes the ticket information to a station server of one or more stations including the departure station,
The station server distributes the distributed ticket information to a ticket gate,
2. The electronic ticket system according to claim 1, wherein the ticket checker writes the ticket information on the passenger's IC card when acquiring the passing information of the passenger. 3.   The electronic ticket system according to claim 2, wherein the ticket information includes location information.   4. The electronic ticket system according to claim 3, wherein a station with high use frequency is selected as the location information.   4. The electronic ticket system according to claim 3, wherein a station that participated immediately before is selected as the location information.   4. The electronic ticket system according to claim 3, wherein a station in the vicinity of the station that participated immediately before is selected as the location information.   The electronic ticket system according to claim 2, wherein a station to be distributed is selected as the location information on the basis of the number of visitors to and from an entrance station and a nearby station.   The electronic ticket system according to claim 1, wherein a station that is likely to participate using a purchased ticket is selected as the second attribute of the electronic ticket.   The electronic ticket system according to claim 1, wherein the electronic ticket information includes time information.   The electronic ticket system according to claim 2, wherein IC card information is included as the electronic ticket information or the ticket information.   11. The electronic ticket system according to claim 10, wherein presence / absence of an alternative fee collection unit is used as the IC card information.   The electronic ticket system according to claim 10, wherein a balance is used as the IC card information. The ticketless server estimates one or more stations used by the passenger based on the ticket information and the received passenger usage history, and distributes the ticket information to the estimated station server of the station. Steps,
The station server delivering the delivered ticket information to a ticket gate;
An electronic ticket distribution method comprising: a step of writing the ticket information to the passenger IC card when the ticket gate acquires the passenger passage information.

Images