JP5000349B2 - Transfer ticket issue system - Google Patents

Description

  The present invention relates to a railway business of a transfer destination with a transfer ticket issued to a passenger using an IC ticket represented by Suica (registered trademark) and a mobile phone with a ticket function represented by Mobile Suica. It is related with the technique which enables boarding of the train of a transfer destination quickly by making it possible to pass the automatic ticket gate of a person's station. In addition, by setting an expiration date on the transfer ticket, unauthorized use of the transfer ticket can be prevented, and when the delay is recovered, it can be promptly guided to the original railway operator. Furthermore, a transfer ticket issuance system that makes it possible to pass through the ticket gates smoothly when using the next railway operator by registering the entry record when a delay occurs and when using the destination railway operator. It is about.

  Conventionally, when a train operator's route has troubled train operation due to a failure of a railway device, a personal injury, etc., the station staff guides passengers to the transfer operator at the ticket gate of the railway operator's station. In addition, a transfer ticket is distributed to each passenger. At this time, since there is a line of passengers for the transfer ticket at the station ticket gate, it takes a lot of time to move to the line of the railway operator of the transfer destination, and the passenger suffers further delay.

  In addition, when a delay occurs, the station ticket gates are crowded with passengers, so there are many passengers who participate as they are without passing through the automatic ticket gates of the railway operators' stations. At this time, the next time you get on the train, if the IC ticket is not registered in the station ticket, you will not be able to pass the automatic ticket gate. I cannot get on the train promptly.

Previously, IC tickets were limited to use at stations in the Tokyo metropolitan area of East Japan Railway, as well as stations, station stores, and affiliated stores in specific areas in the region.・ It is expected to be available on buses. Here, in the transfer transportation method and the transfer transportation system described in Patent Document 1, when a delay occurs, the delay information and the information of the railway carrier of the transfer destination are transferred from the related department including the command section of the railroad operator. Is registered in the database of the server, and means for notifying the information to a mobile phone owned by the passenger using electronic mail and means for issuing a transfer ticket are provided.
JP 2005-262913 A

  However, in the technology described in Patent Document 1, the service is limited to users who have a mobile phone, and the transfer ticket downloaded to the mobile phone is presented at the ticket gate of the transfer operator's station. Because the ticket gates at the transfer destination station have a line of passengers to present the transfer ticket, it is impossible to get on the transfer train quickly due to waiting, resulting in a delay. It will be.

Also, when moving to the transfer destination railway operator, if you do not pass the automatic ticket gate of the station where the delay occurred, the entry record will not be registered in the IC ticket, so when you board the next train I cannot pass through the automatic ticket gate. Therefore, it is necessary to have the attendant record registration at the ticket gate, and it is not possible to get on the train promptly.
The purpose of the present invention is to solve such problems of the prior art, and it is possible to pass through the automatic ticket gate of the destination railway operator's station with the transfer ticket issued by the railway operator. By doing so, the passenger can be promptly guided to the transfer destination train. In addition, even if the situation is confused due to delays, the transfer transfer allows you to register the entry record correctly and save the trouble of registering the entry record at the ticket gate next time, so that you can get on the train quickly. The purpose is to provide a ticket issuing system.

  In order to achieve the above object, the present invention is a transfer transport ticket issuing system that allows a transfer ticket issued by a railway operator to pass through an automatic ticket gate at a station of a transfer destination railway operator, When using a mobile phone with a ticket function or an IC ticket at the transfer operator's station, check the expiration date of the transfer ticket with reference to the delay information and pass the ticket gate Permission means to be permitted and the validity changed to the mobile phone used by the passenger when there is a change in the delay situation and the expiration date of the transfer ticket is changed for the passenger who issued the transfer ticket When the delay information registered when a delay occurs is updated by the expiration date notifying means for notifying the time limit by e-mail and the terminal device of the railway operator, the updated delay information is electronically transmitted to the mobile phone used by the passenger. on mail Characterized in that it comprises an update notification means for knowledge.

The transfer ticket issuing system of the present invention has the following effects.
・ It is possible to pass through the automatic ticket gate using a transfer ticket, and there is no need to present a transfer ticket at the ticket gate at the station of the transfer destination, so passengers can be quickly guided to the transfer destination route. .
-Passengers who do not have a mobile phone with a ticket function can be quickly guided to the destination route.
・ By setting an expiration date, it is possible to prevent unauthorized use of a transfer ticket and to promptly return to the original railway operator's route when delay is restored.
-By registering the entry record, it is not necessary to register the entry record at the ticket gate when you get on the next train, so passengers can get on the train promptly.

Hereinafter, an embodiment of a transfer ticket issuing system to which the present invention is applied will be described.
As shown in FIG. 1, the transfer ticket issuing system in this embodiment includes a delay information notification device 11, an IC ticket management server 12, an operation management terminal 13, a command station terminal 14, a plurality of station terminals 15, and a ticket function. An attached mobile phone 16, an automatic ticket gate 17, and an IC ticket 18 are provided.

  The delay information notification device 11 has a function of managing delay information input from the operation management terminal 13, the command station terminal 14, and each station terminal 15, and a function of distributing the delay information to passengers and automatic ticket gates of each station. Have. The delay information notification device 11 includes a Web server that accepts operations from the terminals 13 to 15, an expiration date notification unit that distributes an e-mail to the mobile phone 16 with a ticket function, and a mail server as an update notification unit, It has a database server that manages the data. A customer information table 19 and a delay information target table 20 are registered in the database server.

The IC ticket management server 12 is a server that manages information related to the cellular phone 16 with a ticket function or the IC ticket 18, and a customer information table 21 is registered therein. Here, the customer information table 21 managed by the IC ticket management server 12 and the customer information table 19 managed by the database server of the delay information notification device 11 are synchronized.
The operation management terminal 13 has a function of registering delay information and a function of updating delay information. The command station terminal 14 is a terminal provided in the command station of the transportation facility. Each station terminal 15 is a terminal disposed at each station of the railway operator.

An example of the mobile phone 16 with a ticket function is a mobile Suica. Mobile Suica is application software on mobile phones owned by passengers, and is provided by East Japan Railway Company. The automatic ticket gate 17 is a device provided at each station.
An example of the IC ticket 18 is Suica (registered trademark). Suica (registered trademark) is an IC carded ticket issued by East Japan Railway that can be used as a boarding card / electronic money.

  Note that the delay information notification device 11 and the mobile phone 16 with a ticket function are connected to each other via a mobile phone network 22 and the Internet 23 as networks. Then, the delay information is delivered from the delay information notification device 11 via the Internet 23 and the mobile phone network 22 to the mobile phone 16 with a ticket function. The delay information notification device 11 and the automatic ticket gate 17 are connected to each other via a railway operator intranet 24 as a network so as to be able to communicate with each other. The automatic ticket gate 17 is connected to the delay information notification device 11 via the railway operator intranet 24. The automatic ticket gate 17 is connected to the mobile phone 16 with a ticket function or the IC ticket 18 at the time of the ticket gate. Inquiries about transfer tickets and check of participation records are performed.

Next, configurations of various tables such as the customer information table 19 and the delay information target table 20 registered in the database server of the delay information notification apparatus 11 will be described.
As shown in FIG. 2, the table elements constituting the customer information table 19 include a customer ID, a password, an email address, a regular section FROM, a regular section TO, a transfer ticket issuance request flag, and customer information. In the customer ID, the ID of a passenger who uses the mobile phone 16 with a ticket function or the IC ticket 18 is stored. The password of the passenger is stored in the password.

  The e-mail address stores the destination to which the delay information and the information related to the transfer ticket are transmitted. In the regular section FROM and the regular section TO, information on the station name of the section is stored in the case of a passenger using a commuter pass. The transfer ticket issuance request flag stores information on delay information and whether or not delivery of information on the transfer ticket is desired. And customer information, such as a passenger's name, a postal code, an address, and a telephone number, is stored in customer information.

  Here, in the case of a passenger other than the use of a commuter pass, data is not stored in the regular section FROM and the regular section TO. In the transfer ticket issuance request flag, Y is stored for passengers who wish to distribute delay information and information related to transfer transport tickets, and N is stored if not desired. The information stored in the customer information table 19 is synchronized with the customer information table 21 managed by the IC ticket management server 12.

The table elements that make up the boarding history table 25 include customer ID, boarding transportation ID, boarding route name, regular boarding flag, boarding date / time, boarding station, boarding transportation ID, boarding route name, boarding date / time, boarding station, transfer There is a transport ticket issued flag.
In the customer ID, the ID of a passenger who uses the mobile phone 16 with a ticket function or the IC ticket 18 is stored. In the boarding transportation ID and boarding route name, information about the ID of the boarding transportation and the route name is stored.

  In the regular boarding flag, information regarding whether or not the boarding with the commuter pass is stored. The boarding date and time and the boarding station store information about the date and time of entering the station and the station that entered the boarding station. In the getting-off transportation ID and getting-off route name, information on the ID of the getting-off transportation and the route name is stored. In the getting-off date / time and the getting-off station, the date and time when the station was entered and information on the station that entered the station are stored. The transfer transport ticket issued flag stores information regarding whether or not a transfer transport ticket has been issued. These records in the boarding history table 25 are registered when the boarding station automatic ticket gate passes.

  Here, as for the regular boarding flag, Y is stored in the case of a passenger using a commuter pass, and N is stored otherwise. In addition, information is not stored in the disembarkation transportation ID, disembarkation route name, disembarkation date and time, and disembarkation station in the case of a passenger who has not passed the automatic ticket gate of the disembarkation station, and information is stored in the case of a passenger who has passed through Is done. In the transfer ticket issued flag, Y is stored when the transfer ticket is issued, N is stored when the transfer ticket is not issued, and what is stored when there is no delay before and after boarding. Is not stored. The customer ID is associated with a customer ID that is a table element of the customer information table 19.

The table elements constituting the transfer ticket table 26 include customer ID, transportation ID, route name, transfer section FROM, transfer section TO, expiration date, and e-mail address.
The customer ID stores the ID of the passenger who issued the transfer ticket. In the transportation ID and route name, information on the transportation facility ID and the route name of the transfer destination route is stored. In the transfer section FROM and the transfer section TO, information about the station in the transfer section is stored. In order to expire, information related to the expiration date of the transfer ticket is stored. The mail address stores the delivery address of the transfer ticket.

The records of the transfer ticket table 26 are generated when delay information is registered in the delay information target table 20.
In addition, the same address as the mail address of the customer information table 19 is stored in the mail address of the transfer ticket table 26. The customer ID is associated with the customer ID in the boarding history table 25.

The table elements constituting the delay information target table 20 include an occurrence date and time, an origin transportation ID, an origin route name, an occurrence section FROM, an occurrence section TO, a delay reason, a recovery possibility, and a delay release flag.
The date and time of occurrence stores the date and time when the delay occurred. In the generation source transportation ID and the generation source route name, information on the transportation organization ID and the route name of the route in which the delay has occurred is stored.

In the generation section FROM and the generation section TO, information regarding a section in which a delay occurs is stored. The delay reason stores information on the reason why the delay has occurred. Information related to the expected recovery time of the delay is stored in the expected recovery. The delay release flag stores information regarding whether or not the delay has been recovered.
The records of the delay information target table 20 are generated when delay occurs and the delay information is registered by the operation management terminal 13, the command station terminal 14, and each station terminal 15 using the delay information notification device 11.

  Here, in the delay cancellation flag, Y is stored when the delay is recovered, and N is stored otherwise. Further, in the expected recovery of the delay information target table 20, information related to the same time as the expiration date of the transfer ticket table 26 is stored. When the delay is recovered, information “9999/10/10 00: 00: 00000” is stored in the expected recovery of the delay information target table 20 and the expiration date of the transfer ticket table 26.

The table elements of the transfer transportation target section table 27 include a transportation ID, a target section FROM, and a target section TO.
The transportation system ID stores the transportation system ID of the route that carries out transfer transportation when a delay occurs. In the target section FROM and the target section TO, information related to the section in which transfer transportation is performed is stored.
The record of the transfer transportation object section table 27 is registered in advance.

Table elements of the transfer destination transport table 28 include a transportation ID, a target section FROM, a target section TO, a target transportation ID, a target route name, a target section FROM, and a target section TO.
The transportation system ID stores the transportation system ID of the route that carries out transfer transportation when a delay occurs. In the target section FROM and the target section TO, information related to the section to be transferred is stored.

In the target transportation ID and target route name, information on the transportation facility ID of the transfer destination route and the route name is stored. In the target section FROM and the target section TO, information related to the section where transfer transportation is performed by this transportation is stored.
Records of the transfer destination transport table 28 are registered in advance. Here, the transportation ID, the target section FROM, and the target section TO of the transfer destination transport table 28 are respectively associated with the transport ID, the target section FROM, and the target section TO of the transfer transport target section table 27.

  Next, the operation of the transfer ticket issuing system configured as described above will be described. The following processing is executed under the control of a CPU (Central Processing Unit) as a control means (not shown) of the delay information notification device 11 based on a program or the like stored in a memory or the like (not shown).

First, when a delay occurs at a predetermined station, the delay information notification device 11 is notified of any information from any one of the operation management terminal 13, the command station terminal 14, and each station terminal 15. Then, the delay information notification device 11 generates a record of the delay information target table 20.
Then, when the passenger uses the mobile phone 16 with a ticket function or the IC ticket 18 to check the ticket at the transfer carrier station, the automatic ticket checker 17 refers to the delay information target table 20. Thus, the transfer ticket is checked and the entry record is checked with respect to the mobile phone 16 with the ticket function or the IC ticket 18.

If the automatic ticket checker 17 checks the expiration date of the transfer ticket and determines that the expiration date has not passed, the passenger is permitted to pass the ticket gate. On the other hand, if it is determined that the expiration date has passed, the passenger is not permitted to pass the ticket gate.
If the entry record is not registered in the cellular phone 16 with ticket function or the IC ticket 18, the entry record is registered in the cellular phone 16 with ticket function or the IC ticket 18 by the automatic ticket gate 17. .

If there is a change in the status of delay for the passenger who issued the transfer ticket, and the expiration date of the transfer ticket is changed, the information such as the changed expiration date is notified of the delay information. The electronic mail is notified from the mail server of the apparatus 11 to the mobile phone 16 with a ticket function used by the passenger. The e-mail is notified to the e-mail address registered in the customer information table 19.
Further, the mail server of the delay information notification device 11 has the delay information registered in the delay information target table 20 when a delay occurs by any one of the operation management terminal 13, the command station terminal 14, and each station terminal 15 of the railway operator. When updated, the updated delay information is notified by e-mail to the mobile phone 16 with a ticket function used by the passenger.

Next, processing when registering a transfer ticket record in the transfer ticket table 26 when a delay occurs after boarding will be described.
As shown in FIG. 3, first, information such as the time when the delay occurs is stored in the delay information target table 20 of the delay information notification device 11 from any one of the terminals 13 to 15 (step S301). .
Next, from the transfer transport target section table 27, the transport section ID is the same as the source transport section ID of the delay information record registered in step S301, and the generation section FROM and generation section TO of the delay information record are the target section FROM. A record included in the target section TO is acquired (step S302).

Here, when any of the following conditions is satisfied, it is determined that the generation section FROM and the generation section TO are included in the target section FROM and the target section TO.
・ When the occurrence section FROM is included between the target section FROM and the target section TO ・ When the generation section TO is included between the target section FROM and the target section TO

Next, records satisfying any of the above conditions are acquired one by one from the transfer transport target section table 27, and the following processing is repeated (step S303). If the record cannot be acquired from the transfer transportation target section table 27, the transfer transportation ticket record registration process is terminated (step S304).
On the other hand, if a record can be acquired from the transfer transportation target section table 27 in step S304, the same traffic as the transportation ID of the transfer transportation target section record acquired in step S303 from the transfer destination transport table 28. A record corresponding to the same target section FROM as the target section FROM and the same target section TO as the target section TO is acquired (step S305).

  Next, records satisfying the above conditions are acquired one by one from the transfer destination transport table 28, and the processes from step S307 to S315 are repeated (step S306). If a record cannot be acquired from the transfer destination transport table 28, the process returns to step S303 (step S307).

  On the other hand, when a record can be acquired from the transfer destination transport table 28 in step S307, the transportation ID of the transfer transport target section record acquired in step S303 is obtained for each customer ID from the boarding history table 25. The same transportation ID, no transportation ID is stored in the getting-off transportation ID, no route name is stored in the getting-off route name, no date and time is stored in the getting-off date, A record having the latest boarding date and time is acquired from the records in which the station name is not stored (step S308).

Next, records satisfying this condition are acquired one by one from the boarding history table 25, and the processes of steps S310 to S315 are repeated (step S309). When a record cannot be acquired from the boarding history table 25, the process returns to step S306 (step S310).
On the other hand, if a record can be acquired from the boarding history table 25 in step S310, a record having the same customer ID as the customer ID of the boarding history record acquired in step S309 is acquired from the customer information table 19 (step S311).

When the transfer ticket issue request flag of the customer information record acquired in step S311 is not Y, the process returns to step S309 (step S312).
If the transfer ticket issuance request flag is Y in step S312, the transfer ticket issued flag of the boarding history record acquired in step S309 is changed to N (step S313).

  Next, the customer ID of the customer information record acquired in step S311 is set to the customer ID of the transfer ticket table 26, and the transfer destination transport record acquired in step S306 to the transfer ID, route name, transfer section FROM, and transfer section TO. The target transportation facility ID, target route name, target section FROM, target section TO, the expected recovery date of the delay information record registered in step S301 at the expiration date, and the mail address of the customer information record acquired in step S311 as the mail address, respectively Store and register the record of the transfer ticket table 26 (step S314).

Next, a process for registering a transfer ticket record in the transfer ticket table 26 when a delay occurs before boarding will be described.
As shown in FIG. 4, first, in order to get on a train, a passenger passes the automatic ticket gate of a station (step S401). Next, the delay information notification device 11 checks whether or not a transfer ticket issued on the mobile phone 16 with a ticket function or the IC ticket 18 is desired, and if it does not wish to issue a transfer ticket Proceed to step S406 (step S402).

  On the other hand, when it is desired to issue a transfer transportation ticket in step S402, the same origination transportation ID as the transportation ID of the route of the boarding station from the delay information target table 20, and the delay release flag is N. A record that is not is acquired (step S403). Next, when a record cannot be acquired from the delay information target table 20, the process proceeds to step S405 (step S404). From the transfer transportation target section table 27, a record having the same transportation ID as the source transportation ID of the delay information record acquired in step S403 and including the generation section of the delay information record in the target section is acquired ( Step S406).

Here, when any of the following conditions is satisfied, it is determined that the occurrence section is included in the target section.
-When the occurrence section FROM is included between the target section FROM and the target section TO-When the generation section TO is included between the target section FROM and the target section TO, records that meet the above conditions are transferred from the transfer transport target section table 27 to 1 Each case is acquired, and the processing of steps S408 to S411 is repeated (step S407).
In step S407, when a record cannot be acquired from the transfer transport target section table 27, the process proceeds to step S405 (step S408).

From the transfer destination transport table 28, the same transport ID as the transport ID of the transfer target section record acquired in step S407, which corresponds to the same target section FROM as the target section FROM and the same target section TO as the target section TO A record to be acquired is acquired (step S409).
Records corresponding to the above conditions are obtained one by one from the transfer destination transport table 28, and the processes of steps S411 and S412 are repeated (step S410).
If no record can be acquired from the transfer destination transport table 28 in step S410, the process returns to step S407 (step S411).

  On the other hand, when the record can be acquired from the transfer destination transport table 28, the customer ID registered in the mobile phone 16 with the ticket function or the IC ticket 18 is added to the customer ID of the transfer transport ticket table 26, and the transportation ID , Route name, transfer section FROM, transfer section TO, target transport agency ID of transfer destination transport record acquired in step S410, target route name, target section FROM, target section TO, delay information acquired in step S403 on the expiration date The record recovery expectation is stored in the e-mail address with the e-mail address registered in the mobile phone 16 with the ticket function or the IC ticket 18 as the e-mail address, and the record of the transfer ticket table 26 is registered (step S412).

  In step S404, when the record can be acquired from the delay information target table 20, the customer ID registered in the mobile phone 16 with the ticket function or the IC ticket 18 is added to the customer ID in the boarding history table 25. If the mobile phone 16 with the ticket function or the IC ticket 18 is treated as a commuter pass, enter Y for the institution ID and the transport facility ID and route name of the station that passed the automatic ticket gate in the train name. If not, N is stored, the date and time of boarding, the date and time of passing the automatic ticket gate to the boarding station and the station name, and N when the process of step S411 is performed in the transfer ticket issued flag, Records in the table 25 are registered (step S405).

Next, a process for transmitting the registered transfer ticket table 26 record to the mobile phone 16 with a ticket function used by the passenger as a transfer ticket will be described.
As shown in FIG. 5, first, a record in which an address is stored in the mail address instead of the expiration date 9999/01/01 00: 00: 00000 is acquired from the transfer transport ticket table 26 (step S501). Next, records satisfying the above conditions are acquired one by one from the transfer transport ticket table 26, and the processes in steps S503 to S508 are repeated (step S502). If the record cannot be acquired from the transfer ticket table 26, the transfer ticket transmission process is terminated (step S503).

  In step S503, when the record can be acquired from the transfer ticket table 26, the transfer ticket is generated from the information of the transfer ticket record acquired in step S502, and the mobile phone 16 with the ticket function used by the passenger is used. (Step S504). If the transmission is successful, the process proceeds to step S506. If the transmission is unsuccessful, the process proceeds to step S507 to retry transmission (step S505). If transmission fails and the number of retries is 3 or more, the process returns to step S502 (step S507). On the other hand, when the number of retries is less than 3, the number of retries is incremented by 1, and the process returns to step S504 to transmit the transfer transportation ticket again (step S508).

  If the transfer transportation ticket is successfully transmitted in step S505, the customer ID and the transportation transportation ID are the same as the customer ID and transportation ID of the transportation ticket record acquired in step S502. The date and time when the boarding date is the latest date and time, the data is not stored in the disembarking transport ID, the disembarking route name, the disembarking date and time, and the disembarking station. ID, alighting route name, alighting date and time, and alighting station, the boarding transportation function ID, the boarding route name, the time and date of boarding, and the boarding station are stored and Y is updated in the transfer ticket issued flag, and a ticketing function is provided. The participation record is also registered in the mobile phone 16 (step S506).

Next, when the delay recovery expected time is changed, or when the delay situation is changed, such as when the delay is recovered and the transfer is canceled, the record of the transfer ticket table 26 is changed, Processing for notifying the contents of the change to the mobile phone 16 with a ticket function used by the passenger will be described.
As shown in FIG. 6, first, the delay information is changed for the record of the delay information target table 20 (step S601).

  Using the process of step S601 as a trigger, from the transfer ticket table 26, a record in which the transportation source ID of the delay information record changed in step S601 and the same transportation ID and expiration date as the expected recovery before the change are stored are stored. Obtain (step S602). Then, records satisfying the above conditions are acquired one by one from the transfer transportation ticket table 26, and the processing of steps S604 to S611 is repeated (step S603). When the record cannot be acquired from the transfer ticket table 26, the delay state change notification process is terminated (step S604).

  On the other hand, if the record can be acquired from the transfer ticket table 26 and no address is stored in the e-mail address in the transfer ticket record acquired in step S603, the process proceeds to step S610 (step S605). In step S605, if an address is stored in the e-mail address in the transfer ticket record, a transfer ticket is generated from the information in the transfer ticket record acquired in step S603, and the passenger changes the delay status. It transmits to the mobile telephone 16 with a ticket function to utilize (step S606). Next, if the transfer ticket is successfully transmitted, the process proceeds to step S610. If the transfer ticket is unsuccessful, the process proceeds to step S608 to retry the transmission (step S607).

  If transmission of the transfer ticket has failed and the number of retries is 3 or more, the process returns to step S603 (step S608). On the other hand, when the number of retries is less than 3, the number of retries is incremented by 1, and the process returns to step S606 to transmit the transfer transportation ticket again (step S609).

  If there is a change in the recovery expectation of the delay information record changed in step S601, or if the delay is recovered and transfer transportation is canceled, the process proceeds to step S611. Otherwise, the process returns to step S603 (step S610). ). In the transfer ticket record acquired in step S603, if there is a change in the recovery expectation of the delay information record, the expiration date is set to the same time as the expected recovery, and if the transfer is canceled, the expiration date is 9999. / 01/01 00: 00: 00000 is stored and updated (step S611).

Next, with the mobile phone 16 with a ticket function (for example, Mobile Suica), the check processing when passing through the automatic ticket gate of the station of the railway operator of the transfer destination or when the next train is boarded Will be described.
As shown in FIG. 7, if the expiry date of the transfer ticket registered in the mobile phone 16 with a ticket function is within the expiry date, the process proceeds to step S709, and if not, the process proceeds to step S702 (step S701).

Here, it is determined that the transfer ticket is within the expiration date when the following conditions are met.
-The transfer destination transportation ID of the transfer ticket registered in the mobile phone 16 with the ticket function is the same as the transport ID of the railway operator of the station that passed the automatic ticket gate-The mobile phone 16 with the ticket function The expiry date of the transfer ticket registered in is the same as or later than the date and time at the time of passing through the automatic ticket gate ・ The expiry date of the transfer ticket registered on the mobile phone 16 with the ticket function is 9999 / 01/01 00:00: not 00000

If the above conditions are not met, it is determined whether or not there is an entry record in the mobile phone 16 with a ticket function. If it is determined that there is no entry record, the process proceeds to step S703. The process proceeds to step S708 (step S702).
If it is determined that there is no entry record, a record having the same customer ID as the customer ID registered in the mobile phone 16 with a ticket function and the latest boarding date and time is acquired from the boarding history table 25 (step S703). ).
If the boarding history of the boarding history record acquired in step S703 is not included in the delay generation route, the ticket gate is not allowed (step S705), and if the boarding history is included in the delay generation route, the process proceeds to step S706. (Step S704).

  Here, when Y or N is stored in the transfer ticket issued flag of the boarding history record acquired in step S703, it is determined that the boarding history is included in the delay occurrence route. Stores the transportation ID, route name, boarding date / time, and boarding station name of the train operator of the train that is currently on boarding in the getting-off transportation ID, boarding route name, boarding date / time, and boarding station of the boarding history record acquired in step S703. Then, it is updated (step S706). An entry record is registered in the cellular phone 16 with a ticket function (step S707).

After the entry record check process, the fare of the train currently on board is charged, and the process proceeds to step S713 (step S708).
If it is determined in step S701 that the transfer ticket is within the expiration date, it is determined whether or not there is an entry record in the mobile phone 16 with a ticket function, and if it is determined that there is no entry record, a step is performed. The process proceeds to S710 (step S709).

In the record of the boarding history table 25, the customer ID is the same as the customer ID registered in the mobile phone 16 with the ticket function, and the getting-off date / time of the record, the getting-off route name, the getting-off date / time and the getting-off station of the record having the latest boarding date In addition, the transport agency ID, route name, boarding date and time, and boarding station name of the railway operator of the train currently on board are stored and updated (step S710).
Next, an entry record is registered in the cellular phone 16 with a ticket function (step S711). Y is stored and updated in the transfer ticket issued flag of the boarding history record updated in step S706 and step S710 (step S712). The ticket gate is allowed (step S713).

Next, with IC ticket 18 (for example, Suica (registered trademark)), the check processing when passing through the automatic ticket gate of the station of the railway operator of the transfer destination or when the next train is boarded Will be described.
As shown in FIG. 8, first, it is determined whether or not there is a valid transfer ticket. If there is a valid transfer ticket, the process proceeds to step S809. If there is no valid transfer ticket, step S802 is performed. (Step S801).

Here, in the record of the transfer ticket table 26, the customer ID is the same as the customer ID registered in the IC ticket 18, and the transport ID is the same as the transport operator ID of the railway operator of the station that has passed the automatic ticket gate. If there is an expiry date that is the same as or later than the date and time after passing through the automatic ticket gate and there is an expiry date record that is not 9999/01/01 00: 00: 00000, a valid transfer ticket Judge that there is.
If the above conditions are not met, it is determined whether or not there is an entry record in the IC ticket 18. If it is determined that there is no entry record, the process proceeds to step S803. If there is an entry record, step S808 is performed. (Step S802).

A record having the same customer ID as the customer ID registered in the IC boarding ticket 18 and having the latest boarding date and time is acquired from the boarding history table 25 (step S803). If the boarding history of the boarding history record acquired in step S803 is not included in the delay occurrence route, the ticket gate is not allowed (step S805), and if included, the process proceeds to step S806 (step S804).
Here, when Y or N is stored in the transfer ticket issued flag of the boarding history record acquired in step S803, it is determined that the boarding history is included in the delay occurrence route.

Store the transport ID, route name, boarding date / time and boarding station name of the train operator of the train currently on boarding in the getting-off transportation ID, boarding route name, boarding date / time and boarding station of the boarding history record acquired in step S803. Then, it is updated (step S806). Next, an entry record is registered in the IC ticket 18 (step S807). After the entry record check process, the fare of the train currently on board is charged, and the process proceeds to step S813 (step S808).
If it is determined in step S801 that there is a valid transfer ticket, it is determined whether or not there is an entry record in the IC ticket 18, and if it is determined that there is no entry record, the process proceeds to step S810 ( Step S809).

  In the record of the boarding history table 25, the current customer ID is the same as the customer ID registered in the IC ticket 18, and the date and time when the boarding date and time, the boarding date and time, and the boarding station of the latest boarding date and time are displayed. Store and update the transportation agency ID, route name, boarding date and time, and boarding station name of the railway operator of the train to be boarded (step S810). Then, the participation record is registered in the IC ticket 18 (step S811). Y is stored and updated in the transfer ticket issued flag of the boarding history record updated in step S806 and step S810 (step S812). The ticket gate is allowed (step S813).

As described above, the transfer ticket issuing system in the present embodiment has the following effects.
・ It is possible to pass through the automatic ticket gate using a transfer ticket, and there is no need to present a transfer ticket at the ticket gate at the station of the transfer destination, so passengers can be quickly guided to the transfer destination route. .
-Passengers who do not have the mobile phone 16 with a ticket function can be quickly guided to the transfer destination route.

・ By setting an expiration date, it is possible to prevent unauthorized use of a transfer ticket and to promptly return to the original railway operator's route when the delay is restored.
-By registering the entry record, it is not necessary to register the entry record at the ticket gate when you get on the next train, so passengers can get on the train promptly.

The above embodiment may be modified as follows.
In the above embodiment, the e-mail is distributed to the mobile phone 16 with a ticket function, but the e-mail may be distributed to a mobile phone that is not registered in advance with a ticket function.

1 is a system configuration diagram showing an embodiment of the present invention. Each block diagram of the table which this system uses. The flowchart which shows the outline | summary of the process which registers a transfer ticket with respect to the passenger who has already boarded the train. The flowchart which shows the outline | summary of the process which registers a transfer ticket with respect to the passenger who has not boarded the train yet. The flowchart which shows the outline | summary of the process which transmits a transfer ticket to the mobile telephone 16 with a ticket function used by a passenger. The flowchart which shows the outline | summary of the process which transmits the change of the condition of a delay to the mobile telephone 16 with a boarding ticket function which a passenger uses, and reflects in a transfer ticket table. The flowchart which shows the outline | summary of the process which registers an entry record, when there is no entry record at the time of a ticket gate with respect to the passenger using the mobile telephone 16 with a ticket function. The flowchart which shows the outline | summary of the process which registers an entry record, when there is no entry record at the time of a ticket gate with respect to the passenger using the IC ticket 18.

Explanation of symbols

DESCRIPTION OF SYMBOLS 11 ... Delay information notification apparatus, 12 ... IC ticket management server, 13 ... Operation management terminal, 14 ... Command station terminal, 15 ... Each station terminal, 16 ... Mobile telephone with a ticket function, 17 ... Automatic ticket gate, 18 ... IC ticket.

Claims (3)

A transfer ticket issuing system that allows an automatic ticket gate of a railway company station that is a transfer destination to pass through a transfer ticket issued by a railway company,
When using a mobile phone with a ticket function or an IC ticket at the transfer destination's station, check the expiration date of the transfer ticket with reference to the delay information and allow the ticket to pass Permission means to
E-mail notification of the expiration date changed to the mobile phone used by the passenger when there is a change in the delay status and the expiration date of the transfer ticket has been changed for the passenger who issued the transfer ticket An expiration date notification means,
An update notification means for notifying the updated delay information by e-mail to the mobile phone used by the passenger when the delay information registered at the time of occurrence of the delay is updated by the terminal device of the railway operator;
A transfer ticket issuing system comprising: It is a transfer ticket issuing system that issues a transfer ticket to passengers who are not regularly used,
When passing through the automatic ticket gate of the transfer destination railway operator's station, determine whether the route of the railway operator belonging to the station registered in the entry record is included in the delay occurrence route that occurred in the past A determination means;
When it is determined by the determination means that the route is included in the delay generation route, when the ticket gate is used using a mobile phone with a ticket function or an IC ticket, the expiration date of the transfer ticket is referred to the delay information. Permission means to check and allow passage of the ticket gate,
E-mail notification of the expiration date changed to the mobile phone used by the passenger when there is a change in the delay status and the expiration date of the transfer ticket has been changed for the passenger who issued the transfer ticket An expiration date notification means,
An update notification means for notifying the updated delay information by e-mail to the mobile phone used by the passenger when the delay information registered at the time of occurrence of the delay is updated by the terminal device of the railway operator;
A transfer ticket issuing system comprising: When a passenger moves to the transfer destination railway operator in the event of a delay, the ticket entry record will be recorded on the mobile phone with a ticket function or IC ticket without passing through the automatic ticket gate of the station where the delay occurred. The transfer transportation ticket issuing system according to claim 1 or 2 to be registered,
When passengers perform ticket gates at the transfer operator's station, or when ticketing at the railway operator's station at the destination, the entry record is registered on the mobile phone with a ticket function or IC ticket If there is not, it is determined whether the route of the railway operator belonging to the station registered in the admission record with reference to the delay information is included in the delay occurrence route that occurred in the past, and Means for registering an entry record in a mobile phone with a ticket function or an IC ticket if it is determined that it is included;
For passengers using a mobile phone with a ticket function, a means of registering entry records when a transfer ticket is issued;
A transfer ticket issuing system comprising:

Images