JP2005115593A - Method and system for ticketing electronic ticket - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To avoid risks of missing collecting fares of a transport facility by reducing time and labor of fare payment of an employee by an electronic ticket and procedure of business trip fare adjustment performed between a corporation and the employees. <P>SOLUTION: A system for ticketing an electronic ticket is for giving and receiving information via a communication network between the transport facilities contracted beforehand, a corporation or the like, and a credit card company, and for performing processing such as fare payment when the employees of the corporation or the like use the transport facilities by using the electronic tickets. In the system for ticketing the electronic ticket, the electronic ticket includes a function to execute a service application of the transport facilities and a corporate SF card to mount company codes for uniquely identifying the corporation or the like and card holder codes for uniquely identifying the employees of the corporation or the like. The service application of the transport facilities have a function to perform processing such that, when it is identified that the corporate SF card has been used at a ticket examination machine, the corporate SF card holds fare values just for a specified period on the premise that the corporation or the like is credited by the card company. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an electronic ticket ticketing method and system, and more particularly, to a method for paying a fare by an electronic ticket of an employee of a company and a business trip expense settlement procedure.

  Generally, prepaid SF (Stored Fare) cards, in which a value (value) of about several thousand yen is recorded in advance and reduced each time the card is used, are prevalent. For this, we used an IC card such as Suica provided by JR and used a value card and then recharged it, and a magnetic card such as a passnet that can be used on private railways and trains. There are two types, “disposable”.

  In addition to paying off-line values using a card, several methods have already been filed for obtaining information and paying online. For example, “fare settlement system and its settlement method and computer program for fare settlement system (Patent Document 1)”, “railway fee automatic debiting system and railroad fee automatic debiting method (Patent Document 2)” use debit settlement, It makes it possible to pay cashlessly. In addition, “Boarding fare settlement system, settlement card and settlement method (Patent Document 3)” and “Fare billing method and fare billing system and machine-readable recording medium recording a program (Patent Document 4)” include a ticket gate, A method has also been filed in which user IDs are recorded in a transportation system, and later, the fare is settled and collected by postpayment.

  In addition, the “PiTaPa” card, which is scheduled to be introduced in FY2003 by the “Surutsu KANSAI Council”, which is part of 42 Kansai transportation systems, is postpaid.

Japanese Patent Laid-Open No. 2003-006688

JP 2001-297344 JP Japanese Patent Laid-Open No. 10-162183 JP 2002-133453 A

When the prepaid electronic ticket as described in Patent Document 1 or Patent Document 2 is used, the following problems are involved.
(1) The prepaid card has an upper limit. For this reason, for office workers who frequently use transportation, it takes time and labor to recharge, buy, and settle the shortage balance.
(2) It takes processing time to exchange credit telegrams online and in real time between the ticket gate and the financial institution server when passing through the ticket gate.

  In addition, as described in Patent Document 3 and Patent Document 4, if the user ID is temporarily stored in a ticket gate or a transportation server, and sent to a financial institution in a batch and settled, the processing time can be reduced. The problem can be cleared, but using post-payment with these methods entails some risk for transportation.

  In general, companies pay for the commuter pass, and employees purchase commuter passes individually from transportation. There seems to be room for reduction of window work.

The present invention has been made in view of such circumstances, and the purpose of the present invention is to make it possible to process fare payment work for individual employees such as commuter passes between transportation facilities and companies, and to use commuter passes. The purpose is to provide a method and a system for reducing window work in transportation such as issuance.
Another object of the present invention is to reduce the labor for paying the fare by the employee's electronic ticket, that is, the labor for charging or purchasing a new card, and the time for confirming the payment ability of the person each time it is used. It is to provide a method and system.

Another object of the present invention is to provide a method and system for reducing the time and effort required for the travel expense settlement procedure between a company and an employee.
It is another object of the present invention to provide a method and system that assists in avoiding the fretting risk of fare collection for transportation.
Another object of the present invention is to provide a method and system for reducing a transfer fee when a corporation transfers money to an employee's account for travel expenses.

The above-mentioned purpose is to exchange information via a communication network between a pre-contracted transportation system, company, etc. and a credit card company, and employees of the company, etc. use the transportation system using an electronic ticket. An electronic ticket ticketing system for processing fare payments, etc.
The electronic ticket is a card that uniquely identifies a function of executing a transportation service application, a company code that uniquely identifies the company, etc., and an employee of the company, etc. with respect to the electronic ticket ticketing system Including a corporate SF card with a holder code, and when the transportation service application identifies that the corporate SF card has been used in a ticket gate, the credit card company assumes credit to the company, etc. This is achieved by having the function of processing such that the corporate SF card retains the fare value for a predetermined period.

The above-mentioned purpose is also to transfer information through a communication network between a pre-contracted transportation system, company, etc. and a credit card company, and employees of the company, etc. use the electronic ticket for the transportation system. An electronic ticket ticketing system for processing fare payments when using
The electronic ticket is a card that uniquely identifies a function of executing a transportation service application, a company code that uniquely identifies the company, etc., and an employee of the company, etc. with respect to the electronic ticket ticketing system Including a corporate SF card with a holder code, and when the transportation service application identifies that the corporate SF card has been used in a ticket gate, the credit card from the card company to the company, etc. A function for processing the corporate SF card so as to hold a fare value for a predetermined period on the assumption of a predetermined charge amount of the company, a function for acquiring and storing usage data in the ticket gate for the corporate SF card, A function for acquiring and storing company or private use segregation information from employees of the company, etc. regarding the use data, and the company use Transmitting the use data on the companies is achieved by having a function for periodically clearing process.

The above purpose is also when information is exchanged between pre-contracted transportation facilities, companies, etc. and credit card companies, and employees of the companies, etc. use the transportation facilities using electronic tickets. An electronic ticket ticketing method for processing fare payments,
The electronic ticket is a card that uniquely identifies a function of executing a transportation service application, a company code that uniquely identifies the company, etc., and an employee of the company, etc. with respect to the electronic ticket ticketing system Including a corporate SF card with a holder code, and when the business support server of the transportation system identifies that the corporate SF card has been used in a ticket gate, the credit card company credits the company, etc. As a premise, this is achieved by processing so that the corporation SF card holds the fare value for a predetermined period.

Note that the present invention can be applied not only to companies but also to various corporations, government offices, and organizations. In addition, for an organization such as a large company with over 10,000 employees, it is considered that there is an “accounting system” within the company for each reasonable unit such as a business unit or region. In this case, the “accounting system” is also credited within its limit according to the company, and the system of the present invention can be operated. Therefore, these are collectively referred to as “businesses”.
In addition, since “corporate etc.” bears the cost of the commuter pass, it includes officers and public servants, so these are collectively referred to as “employees”.

  According to the present invention, it is possible to process a fare payment for each employee's commuter pass, etc., between the transportation facility and the company at one time, and to reduce the window business in the transportation facility such as commuter pass issuance. In addition, it is possible to reduce the labor for paying the fare by an electronic ticket for employees and the travel expense settlement procedure with a company, etc., and to avoid the risk of collecting the fare for transportation. In addition, it is possible to reduce the transfer fee that was incurred when the company transferred money to the employee's account for travel expenses.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
First, the configuration of an electronic ticket ticketing system according to an embodiment of the present invention will be described with reference to FIG.
In order to carry out the present invention, the transportation facility includes an information processing device (business support server) 4011 and one or more ticket gates 4012. A company has an information processing apparatus (accounting system) 4013 for processing accounting work, and an employee of the company has an information processing apparatus (employee system) 4014 and an IC card (corporate SF card) 4015. The credit card company has an information processing device (card company system) 4016.

  A company makes a contract with a transportation agency and a credit card company in advance, and executes a program for executing a transportation service application, a program for executing a credit card company service application, a code for uniquely identifying the company, and an individual. A corporate SF card 4015 loaded with a code for uniquely identifying an employee who is a user (card holder) is distributed to each employee. However, the corporate SF card function here does not charge the fare value in advance, but stores the corporate code and cardholder code for which a contract for using this service is made, so that the corporate SF card function can be transferred to the ticket gate of the transportation facility. It refers to the function of identifying a card and processing it as if it had a fare value.

  The transportation business support server 4011 has at least an input device 40111, an output device 40112, a CPU, and a memory unit, and has a program for executing a service application. As a means or function for executing this program, at least an alert line calculation unit 40113 for calculating a timing for requesting a recharge to a company, a use log management unit 40114 for managing a use log of a transportation facility, and a use log storage Unit 40117, a usage log screen generation unit 40115 that generates a screen for displaying a usage log for a user, a customer data management unit 40116 that manages information on companies and individual users, and a customer data storage unit 40118. Have.

  The ticket gate machine 4012 of the transportation facility has means or functions necessary for executing the service application as the ticket gate machine 4012. That is, at least an input means 40121 for receiving information from the corporate SF card 4015, an output means 40122 for displaying usage status and operation status to the user, a communication control unit 40123 for controlling communication with the business support server 4011, fare calculation Traffic application control unit 40124 that performs user confirmation processing, usage log management unit 40125 and usage log storage unit 40127 that manage usage logs, whether the user is a corporate SF card 4015 user or general user, and corporate SF card The user information storage unit 40126 for identifying whether the company is permitted to use.

An enterprise business support, that is, an accounting system 4013 has at least an input means 40131, an output means 40132, a CPU, and a memory unit, and has a program for executing a transportation service application. As a means or function for executing this program, at least a travel expense application data management unit 40133 and a travel expense application data storage unit 40135 for processing travel expense application data transmitted from employees, an employee data management unit for managing employee data 40134 and an employee data storage unit 40136.
The company employee system 4014 has the necessary means or functions to execute the business support application. That is, at least an input unit 40141, an output unit 40142, a CPU, and a memory unit are included.

  The IC card 4015 includes at least an input unit 40151, an output unit 40152, a CPU, and a memory unit, and has a program for executing a service application. As means or functions necessary for executing this service application, at least the credit settlement processing unit 40153 corresponding to the credit settlement processing, the card holder information storage unit 40154 for storing user data, and the exchange with the ticket checker 4012 are controlled. The ticket application processing unit 40155, the business support server 4011, and the ticket checker 4012 have a card ID storage unit 40156 that stores a card ID for identifying the card. Since the corporate SF card 4015 is assumed to be used in a ticket gate of a transportation facility, a non-contact type is more desirable if importance is attached to convenience and processing speed.

  The card company system 4016 includes at least an input unit 40161, an output unit 40162, a CPU, and a memory unit, and has a program for executing a service application. As a means or function necessary for executing this service application, at least a corporate credit review processing unit 40163 for performing credit review processing of a company and a customer information storage unit 40164 for managing contracted company and cardholder information are provided. .

  According to the electronic ticket ticketing system of the present embodiment, between the business support server 4011 and the ticket gate 4012 of the transportation system contracted in advance, the accounting system 4013 and the employee system 4014 of the company, and the system 4016 of the credit card company Information is exchanged via a communication network, and processing of fare payments, etc., when employees of a company use a transportation system using an electronic ticket including a corporate SF card. When a transportation service application identifies that a corporate SF card has been used on the ticket gate 4012, the corporate SF card retains the fare value for a specified period on the premise of credit from the card company to the company, etc. It has the function to process.

Next, FIG. 1 shows a basic processing flow of an embodiment of the present invention.
The company makes a contract with a transportation system and a credit card company in advance, and distributes the corporate SF card 4015 to each employee.
The accounting system 4013 presents to the business support server 4011 the amount promised to be paid in the future when using the corporate SF card 4015 (total charge amount), and requests permission to use the corporate SF card 4015 (step 1021).
The business support server requests the card company system 4016 to examine that the company that has requested the use permission has the ability to pay the total charge presented (step 10411).

  The card company system 4016 performs a credit examination process for the requested company (step 1051), and notifies the result to the business support server 4011 (step 1052).

  If the received credit review result is OK (step 10412), the business support server 4011 sets an amount of money that is considered appropriate as the timing when the application for the next reuse permission is required for the company (step 10412). 10413), the contract company charge amount data 801 is updated (step 10414), and the accounting system 4013 is notified that the use permission has been granted (step 10415). On the other hand, when the credit examination result is NG in step 10412, the use system refusal is notified to the accounting system 4013 (step 10421).

When the corporate SF card 4015 passes through the ticket gate 4012, it transmits a card ID that uniquely identifies the company to which the card holder belongs and the user (step 1011).
The ticket checker 4012 acquires and accumulates the received card ID and information such as the date and time of use and the boarding / exiting station as a usage log in the usage log storage unit 40127 (step 1031), and periodically supports business support for usage log information in batches. Transmit to the server 4011 (step 1032).

  The business support server 4011 accumulates the usage amount of the corporate SF card 4015 for each company from all the usage log information received from one or more ticket gates 4012 (step 1046). Here, if the business support server 4011 determines that it is a settlement date (step 40417), it performs a settlement process between the company and the card company (step 10418). If the withdrawal balance after subtracting the usage amount from the amount charged first falls below the alert line set in step 10413 (step 10419), the corresponding company's accounting system 4013 is notified to reapply for usage permission. (Step 10420).

  Note that the “alert line” of the company does not necessarily have a fixed value, and the “alert line” may be temporarily raised or lowered depending on the business form of the company. In addition, the “alert line” determination process may be omitted for a specific excellent company.

  When the accounting system 4013 receives the reuse permission application request notification and inputs the reuse permission application process (step 1022), the accounting system 4013 returns to step 1021.

Here, the contract company charge amount data 801 used in step 1046 will be described with reference to FIG.
The contract company charge amount data 801 includes at least a company ID 7011 that uniquely identifies the contracted company, a latest charge date 8011 that indicates the date of the most recent use permission application, and a charge amount 8012 that indicates the amount charged on that date. And the withdrawal balance 8013 calculated from the usage amount for each company accumulated in Step 1046, the latest confirmation date 8014 indicating the date when the usage amount for each company was calculated and the withdrawal balance was confirmed, and set for each company Including alert line 8015.

  The alert line is calculated in advance as a% (a: constant) of the total charge presented by the company in the first time, and thereafter, from the slope of the decrease in the balance of withdrawal and the number of days required for the credit card company system to be examined. A method of guessing can be considered. For example, if the total charge amount is 3 million yen, the number of days required for the examination process is 3 days, and the reduction trend of the withdrawal balance is 100,000 yen / day, the withdrawal balance is 300,000 yen (100,000 x 3 days), Or, for safety, (30 + α) 10,000 yen is used as an alert line.

The business support server 4011 assigns a company ID to the contracted company, and manages data related to the company in the customer data storage unit 40118.
The contract company data 701 will be described with reference to FIG.
The contract company data 701 includes at least a company ID 7011 assigned by the business support server 4011 to uniquely identify the company, a company name 7012 indicating the name of the company, a reading 7013 of the company name 7012, an address, a telephone number, and the like. It includes a contact 7014 and a contract date 7015 indicating the date on which the company has contracted.

The business support server 4011 manages the data related to the individual user who owns the card in the customer data storage unit 40118 as in the case of the company.
The user data 901 will be described with reference to FIG.
User data 901 includes at least a card ID 5011 for uniquely identifying the card, a name 9012 of the card holder, a reading 9013 of the name 9012, a contact 9014 such as the address and telephone number of the card holder, and the card It includes the gender 9015 of the holder, the date of birth 9016 of the card holder, and periodical information 9017 regarding the use of the card as a commuter pass. The card ID 5011 includes a company ID 7011 and a personal ID 9011. The regular information 9017 includes at least a departure station name 90171 and a destination station name 90172 indicating a regular section, an identification code 90173 for identifying a type such as a commuting period or a school period, and a commuter pass expiration date 90174.

Next, the flow of the fare settlement process by the employee holding the corporate SF card 4015 will be described with reference to FIG.
The employee system 4014 accesses the business support server 4011 via the communication network using the card ID mounted in the corporate SF card 4015 (step 2011). If the business support server 4011 determines that the connection is with a legitimate user, the business support server 4011 extracts a usage log corresponding to the card ID and displays it by the usage log screen generation unit 40115 (step 2031). For each item of the usage log displayed from the employee system 4014, a code for separating whether it is for company use or private use is input (step 2012).

  Employee system 4014 transmits travel expense payment application data for the company to accounting system 4013 (step 2013). On the other hand, if business support server 4011 determines that it is the payment date (step 2032), Based on the received data, only the information authorized for company use is transmitted to the accounting system 4013 (step 2033). The accounting system 4013 collates the received information from the employee system 4014 with the information from the business support server 4011 (step 2021), and determines that there is inappropriate data in the travel expense application data (step 2022). A travel expense application data correction request is sent to the employee system 4014 (step 2023). If it is determined in step 2022 that the travel expense application data is correct, the received data is approved, or if there is a correction request, the correction request information is sent to the business support server. Transmit to 4011 (step 2024).

  Based on the data received from the accounting system 4013, the business support server 4011 sorts the usage log into corporate or private use, and transmits the result to the card company system 4016 (step 2034). The card company system 4016 calculates company data as bills for companies and private data as bills for individuals, creates billing statement data, and performs a batch billing process for each user's financial institution account. Perform (step 2041).

Here, the usage log screen displayed on the employee system 4014 in step 2031 and step 2012 will be described with reference to FIG.
The usage log screen 1001 includes at least a card ID part 10011 indicating a card ID to be displayed, a target period part 10012 indicating a period to be displayed, a usage log detail part 10013, and a comment part 10014 for the operator. The button unit 10015 assists the screen switching operation. The usage log detail part 10013 has a check box part 100131 for inputting a check for sorting at least corporate or private use, a use date 100132 using a transportation facility, and an entrance time indicating a time when the ticket gate is passed for boarding. 100133, boarding station 100134, exit time 100135 indicating the time of passing the ticket gate for getting off, getting-off station 100136, fare 100137 charged, and periodic application 100138 indicating whether or not the period is applied.

FIG. 11 shows a confirmation screen 1101 in which only company usage logs are extracted based on data entered on the usage log screen 1001.
The confirmation screen 1101 includes at least a card ID part 10011 indicating a card ID to be displayed, a target period part 10012 indicating a period to be displayed, a company usage log detail part 11011, and a comment for the operator. Section 10014, a total amount display section 11012 indicating the accumulated fare of the usage log for company use, and a button section 10015 for assisting the screen switching operation. The company use log detail section 11011 includes at least a transportation use date 100132, an entry time 100133, a boarding station 100134, an exit time 100135, a departure station 100136, a fare 100137, and a periodic application 100138.

  The button unit 10015 includes a download button 100151 for downloading the extracted data so that the user can reuse the electronic data when he / she later performs a business trip expense adjustment procedure for the company. The format of the data to be downloaded is preferably a format that can be linked to the accounting system and travel expense settlement system adopted by the company.

Next, a processing flow when the user passes through the ticket gate 4012 will be described with reference to FIG.
When the card information is transmitted from the corporate SF card 4015 to the ticket gate 4012 (step 3011 = corresponding to step 1011 in FIG. 1), the ticket gate 4012 identifies that the card is a corporate SF card from the received card ID ( Step 3021). If it is determined to be a corporate SF card, it is determined that the company of the corporate SF card holder is permitted to use (step 3022). If it is determined that the usage is permitted, boarding / exit including information such as transit time and passing station Information is transmitted to the corporate SF card 4015 (step 3023). The ticket gate 4012 stores the acquired card ID and boarding / alighting information in the usage log storage unit 40127 (step 3024 = corresponding to step 1031 in FIG. 1). On the other hand, if it is determined in step 3021 that the card is not a corporate SF card, or if it is determined in step 3022 that use is not permitted, processing similar to that performed by an ordinary user is performed (step 3025).

When the ticket gate machine 4012 determines that the stored usage log is set to be uploaded to the business support server 4011 (step 3026), the accumulated usage log information is sent to the business support server 4011 in batches (step 3027). (Corresponds to step 1032 in FIG. 1).
The business support server 4011 stores the received usage log information in the usage log storage unit 40117 (step 3031), and totals the usage amount for each company ID and each user ID (step 10416 = corresponds to step 10416 in FIG. 1). ).

Here, the data stored in the usage log storage unit 40126 of the ticket gate 4012 in step 3024 will be described with reference to FIG.
The usage log 501 includes at least a card ID 5011 for identifying a user's card using the ticket gate 4012, a date and time 5012 for using the ticket gate 4012, and an entrance / exit identification code for identifying whether the user has entered or exited the home. 5013, a use station name 5014, and a regular use code 5015 for determining whether or not a regular use has been applied.

Next, the data stored in the usage log storage unit 40117 of the business support server 4011 in step 3031 will be described with reference to FIG.
The usage log 601 includes at least a card ID 5011, a boarding station 6011 of the user of the card, an entrance time 6012 indicating the time of passing through the ticket gate 4012, an exit station 6013, an exit time 6014, a regular use code 5015, Includes fare 6015 for moving from boarding station 6011 to alighting station 6013.

  According to this example, the fare payment service for employees such as commuter passes was processed in a batch between the company and the transportation system using a corporate SF card, so the transportation system should contact individual employees. Compared to the case of dealing with, work can be greatly reduced. On the other hand, for companies, there is an advantage that it is possible to reduce a transfer fee when transferring money to an individual employee's account for travel expenses.

  In addition, by using the corporate SF card, the employee can reduce the labor for paying the fare, that is, the labor for charging or purchasing a new card, and the time for confirming the payment ability of the person each time it is used.

  In addition, by using the usage log information for each corporate ID and user ID of the corporate SF card generated by the business support server, the time and effort required for the travel expense settlement procedure between the company and the employee can be reduced. it can.

  In addition, for transportation facilities, by using a corporate SF card based on the credit review of the company by the credit card company, it is possible to avoid the risk of processing fare collection in spite of adopting a kind of post-pay method. There is.

  As another embodiment of the electronic ticket ticketing system of the present invention, it is also conceivable that the use of the corporate SF card 4015 is limited to the company only, and the fare paid is all borne by the company. In this case, it is not necessary for each employee to check the usage log and perform the company / private distribution process, so that it is possible to greatly reduce the time and effort of the travel expense application / payment process.

  When this method is adopted, after payment between the transportation system and the company, the burden between the company and the employee is apportioned, or the employee's job title and time of use (day of week, weekday / holiday, time of day), etc. By setting usage conditions and setting condition data in the ticket gate 4012, it may be possible to restrict the use of cards that do not meet the conditions when passing through the ticket gate, for example, by rejecting the usage.

    Also, in the above embodiment of the present invention, if the corporate SF card is damaged such as lost or stolen, and the card holder passes the damage notification to the transportation, the transportation is applicable to prevent unauthorized use of the corporate SF card. You can perform processing to deny the use of the card at the ticket gate. However, there is a possibility that the card holder may be damaged after notifying that the cardholder is lost or stolen and before the transportation system processes the use refusal.

  Therefore, as another embodiment of the electronic ticket ticketing system of the present invention, it is conceivable to verify the identity of the card holder every time it passes through the ticket gate in order to prevent unauthorized use more reliably. This can be realized, for example, by passing the data indicating the identity of the card holder to the corporate SF card when the card holder passes the ticket gate 4012 and verifying that it is the identity of the card holder every time it is used. The data indicating the identity of the cardholder may be a personal identification number, but considering the congestion at the ticket gate and the trouble of the cardholder, biometric authentication such as a troublesome fingerprint entered by the cardholder Can be considered.

  If it is difficult to perform such an authentication process using only a corporate SF card (IC card 4015) that has only input means using a dedicated system, read the personal authentication data in the card holder and send / receive data to / from the corporate SF card. It is also possible to perform a card holder identity authentication process using a portable terminal capable of the above.

The configuration of an electronic ticket ticketing system according to another embodiment of the present invention that realizes this method will be described with reference to FIG. (The following description will be mainly based on a different part from the embodiment of FIG. 1.)
The portable terminal 4017 has at least a CPU, a memory unit, input means 40172 for reading personal authentication data such as fingerprint data, and output means 40171 for displaying a processing status such as an error or reading, and an IC as a function for executing a service application A card processing control unit 40173 that controls communication with the card 4015 is included. Further, the IC card 4015 has at least an input means 40151, an output means 40152, a CPU, and a memory unit. As a function, at least a credit settlement processing unit 40153 that performs credit settlement processing, a card holder information storage unit that stores user data 40154, a ticket application processing unit 40155 that controls the exchange with the ticket gate 4012, a business support server 4011 and a card ID storage unit 40156 for storing a card ID for identifying the card by the ticket gate 4012, and authentication of the card holder An authentication processing unit 40157 is included.

  When personal authentication data is input from the input means 40172 to the portable terminal 4017 when the card holder passes the ticket gate 4012, the card processing control unit 40173 sends the input personal authentication data to the authentication processing unit 40157 of the IC card 4015. hand over. The authentication processing unit 40157 collates the personal authentication data stored in the card holder information storage unit 40154 in advance with the received personal authentication data, and passes the collation result to the ticket AP processing unit 40155. The ticket AP processing unit 40155 passes the verification result together with the card ID 5011 and the like to the ticket AP control unit 40124 of the ticket gate 4012. If the verification result is OK, it is processed normally, and if it is NG, it is rejected and cannot pass through the ticket gate 4012.

  In addition, when using a portable terminal with an external input means as described above, each time it passes through the ticket gate 4012, it must also be sent to the ticket gate 4012 together with data for separating whether it is for corporate use or private use. Is also possible. For example, when the mobile terminal 4017 has an input means such as a button for separating whether it is for company use or private use, and when the purpose of use of the card holder transportation is clear, when passing through the ticket gate 4012 In this method, discrimination data is input / transmitted using a button of the mobile terminal 4017.

  By carrying out this process, the transportation system 4011 can hold data for identifying whether each usage log is for company use or private use, and since the data assigned to company use / private use is displayed on the screen of step 2031 in advance, The card holder can reduce labor for company / private discrimination and input performed in the fare settlement process shown in FIG.

It is a figure explaining the basic processing flow in one Embodiment of this invention. It is a figure explaining the travel expense adjustment process flow in one Embodiment of this invention. It is a figure explaining the processing flow at the time of a ticket gate machine in one Embodiment of this invention. It is a figure explaining the system configuration in one embodiment of the present invention. It is a figure explaining the structure of the utilization log data which the ticket gate machine in one Embodiment of this invention manages. It is a figure explaining the structure of the utilization log data which the business support server in one Embodiment of this invention manages. It is a figure explaining the structure of the contract company data which the business support server in one Embodiment of this invention manages. It is a figure explaining the structure of the contract company charge amount data which the business support server manages in one Embodiment of this invention. It is a figure explaining the structure of the user data which a business support server manages in one Embodiment of this invention. It is a figure explaining the utilization log screen displayed on an employee system in one Embodiment of this invention. It is a figure explaining the confirmation screen displayed on an employee system in one Embodiment of this invention. As another embodiment of the present invention, it is a diagram illustrating an example of a system configuration in the case where a person authentication function is added to the ticket gate passage processing in FIG.

Explanation of symbols

501 ... Usage log, 601 ... Usage log, 701 ... Contracted company data, 801 ... Contracted company charge amount data, 901 ... User data, 1001 ... Usage log screen, 1101 ... Confirmation screen, 4011 ... Business support server for transportation, 4012 ... Ticket gate, 4013 ... Corporate information processing device (accounting system), 4014 ... Employee system, 4015 ... IC card (corporate SF card), 4016 ... Card company system, 4017 ... Mobile terminal, 40111 ... Input device, 40112 ... Output device, 40113 ... Alert line calculation unit, 40114 ... Usage log management unit, 40115 ... Usage log screen generation unit, 40116 ... Customer data management unit, 40117 ... Usage log storage unit, 40118 ... Customer data storage unit, 40121 ... Input Means, 40122 ... Output means, 40123 ... Communication control section, 40124 ... Traffic application control section, 40125 ... Usage log management section, 40126 ... User information storage section, 40127 ... Usage log storage section, 40131 ... Input means, 40132 ... Output Means, 40133 ... Travel expense application data management section, 40134 ... Employee data management section, 40135 ... Travel expense application data storage section, 40136 ... Employee data storage section, 40153 ... Credit payment processing section, 40154 ... Card holder information storage section, 40155 ... Passenger ticket application Processing unit, 40156 ... Card ID storage unit, 40157 ... Authentication processing unit, 40163 ... Business credit examination processing unit, 40164 ... Customer information storage unit, 40173 ... Card processing control unit.

Claims (6)

Fares when information is exchanged via a communication network between a pre-contracted transportation system, company, etc. and a credit card company, and employees of the company, etc. use the transportation system using an electronic ticket An electronic ticket ticketing system for processing payments, etc.
The electronic ticket is a card that uniquely identifies a function of executing a transportation service application, a company code that uniquely identifies the company, etc., and an employee of the company, etc. with respect to the electronic ticket ticketing system Including a corporate SF card with a holder code,
When the transportation service application identifies that the corporate SF card has been used in a ticket gate, the corporate SF card retains the fare value for a predetermined period on the premise of credit from the card company to the company, etc. An electronic ticket ticketing system characterized by having a function of processing as if it were. Fares when information is exchanged via a communication network between a pre-contracted transportation system, company, etc. and a credit card company, and employees of the company, etc. use the transportation system using an electronic ticket An electronic ticket ticketing system for processing payments, etc.
The electronic ticket is a card that uniquely identifies a function of executing a transportation service application, a company code that uniquely identifies the company, etc., and an employee of the company, etc. with respect to the electronic ticket ticketing system Including a corporate SF card with a holder code,
When the service application of the transportation facility identifies that the corporate SF card has been used in a ticket gate, the corporate SF card is premised on credit from the card company to the company and the predetermined charge amount of the company. Functions to hold the fare value for a predetermined period, the function to acquire and store the usage data in the corporate SF card ticket gate, and the corporate data from employees of the company etc. regarding the usage data Alternatively, the electronic ticket ticketing has a function of acquiring and storing private use separation information and a function of transmitting the use data for the company to the company and periodically performing a clearing process. system. Fares when information is exchanged via a communication network between a pre-contracted transportation system, company, etc. and a credit card company, and employees of the company, etc. use the transportation system using an electronic ticket An electronic ticket ticketing system for processing payments, etc.
The electronic ticket is a card that uniquely identifies a function of executing a transportation service application, a company code that uniquely identifies the company, etc., and an employee of the company, etc. with respect to the electronic ticket ticketing system Including a corporate SF card with a holder code,
When the transportation service application identifies that the corporate SF card has been used in a ticket gate, the corporate SF card retains the fare value for a predetermined period on the premise of credit from the card company to the company, etc. A function to process as it is, a function to acquire and store usage data in the ticket gate of the corporate SF card, and a usage amount for each employee of the company, etc. is calculated periodically from the stored information An electronic ticket ticketing system characterized by having a function. Fares when information is exchanged via a communication network between a pre-contracted transportation system, company, etc. and a credit card company, and employees of the company, etc. use the transportation system using an electronic ticket An electronic ticket ticketing system for processing payments, etc.
The electronic ticket is a function for executing a transportation service application, a function for executing a credit card company service application, a company code for uniquely identifying the company, etc., with respect to the electronic ticket ticketing system, Including corporate SF cards with cardholder codes that uniquely identify employees of companies, etc.
The corporate accounting system collates the information corresponding to the company's portion of the employee received from the transportation service application with the travel expense settlement information received from the employee, and sends the result to the transportation service application. Electronic ticket ticketing system characterized by having a function. Information is exchanged between pre-contracted transportation facilities, companies, etc. and credit card companies, and processing such as fare payment when employees of the companies, etc. use the transportation facilities using electronic tickets An electronic ticket ticketing method for performing
The electronic ticket is a card that uniquely identifies a function of executing a transportation service application, a company code that uniquely identifies the company, etc., and an employee of the company, etc. with respect to the electronic ticket ticketing system Including a corporate SF card with a holder code,
When the business support server of the transportation system identifies that the corporate SF card has been used in a ticket gate, the corporate SF card provides a fare value for a predetermined period on the premise of credit from the card company to the company. An electronic ticket ticketing method, wherein the ticket is processed so as to be held. Information is exchanged between pre-contracted transportation facilities, companies, etc. and credit card companies, and processing such as fare payment when employees of the companies, etc. use the transportation facilities using electronic tickets A corporate SF card used in an electronic ticket ticketing system for performing,
A program that executes the service application of the transportation facility, a program that executes the service application of the credit card company, a code that uniquely identifies the company, and an employee who is an individual user (card holder) The code is installed,
Assuming credit from the card company to the company, etc., the employee has a function of being processed so as to hold a fare value for a predetermined period when used in the ticket gate of the transportation facility. Corporate SF card.

Images