KR20110031047A - Interconnect accounting system for compatible traffic card and management method therefore - Google Patents

Interconnect accounting system for compatible traffic card and management method therefore Download PDF

Info

Publication number
KR20110031047A
KR20110031047A KR1020090088765A KR20090088765A KR20110031047A KR 20110031047 A KR20110031047 A KR 20110031047A KR 1020090088765 A KR1020090088765 A KR 1020090088765A KR 20090088765 A KR20090088765 A KR 20090088765A KR 20110031047 A KR20110031047 A KR 20110031047A
Authority
KR
South Korea
Prior art keywords
settlement
information
transaction
mutual
card
Prior art date
Application number
KR1020090088765A
Other languages
Korean (ko)
Inventor
이기한
Original Assignee
한국건설교통기술평가원
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 한국건설교통기술평가원 filed Critical 한국건설교통기술평가원
Priority to KR1020090088765A priority Critical patent/KR20110031047A/en
Priority to PCT/KR2009/005662 priority patent/WO2011034231A1/en
Publication of KR20110031047A publication Critical patent/KR20110031047A/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/14—Payment architectures specially adapted for billing systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/18—Payment architectures involving self-service terminals [SST], vending machines, kiosks or multimedia terminals
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/22—Payment schemes or models
    • G06Q20/28—Pre-payment schemes, e.g. "pay before"
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F19/00—Complete banking systems; Coded card-freed arrangements adapted for dispensing or receiving monies or the like and posting such transactions to existing accounts, e.g. automatic teller machines
    • G07F19/20—Automatic teller machines [ATMs]

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Finance (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Computer Security & Cryptography (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Devices For Checking Fares Or Tickets At Control Points (AREA)

Abstract

PURPOSE: A mutual calculation system about a compatible traffic card and an operation method of a mutual calculation system are provided to enable a user conveniently use various transportation unit using one compatible traffic card by enabling a card issuing provider and a card calculating business owner to pay and calculate a usage charges. CONSTITUTION: An own company calculation server collects transaction history information by the traffic card from a traffic card terminal(S100). The own company calculation server classifies the collected transaction history information(S110). The own company calculation server receives mutual calculation approval breakdown information from another company calculation server(S250). The own company service performs mutual calculation according to the transaction history information(S270).

Description

Interconnect Accounting System For Compatible Traffic Card and Management Method therefore}

The present invention relates to a mutual settlement system and operation method for compatible nationally compatible transit cards, and more specifically, to the compatible transit card payment details traded in a transit card terminal, based on common standard settlement items of operators. The present invention relates to a mutual settlement system and a method of operating a mutual settlement system for mutual settlement between transportation card operators.

Currently, the card payment method by prepaid or postpaid transportation card is becoming more common than payment by cash when using public transportation such as bus, subway, and railway. However, since different transportation card payment, charging, and settlement systems have been established for each region or operator, it is impossible for the transportation card payment, charging, and settlement systems to be compatible with each other. Depending on each operator, there are inconveniences of having multiple transportation cards when using public transportation.In addition, operators have a burden of overlapping investment in transportation card payment, charging, and settlement system, and furthermore, the common and stable transportation card Difficulties arise in establishing payment, charging and settlement systems.

In order to solve the above problems, a nationally compatible transportation card system is required, and in 2006, the prepaid IC card standard, which is the transportation card standard, was enacted as the Industrial Standard Specification (KS), and the KS standard enacted the technical basis for national transportation card compatibility. Is being prepared. Nevertheless, the national compatibility of the transportation card system, which was constructed differently between regions and operators, is continuing to be sluggish as before.

Therefore, the present invention is a part of the “One Card All Pass standard technology development and test bed operation project” led by the Ministry of Construction and Transportation, the railroad card company KORAIL, the bus and subway card company, KFTC, the highway card company Based on the development of a compatible transportation card standard and a transportation card terminal compatible with each other, the three companies can settle mutual payments according to common standard settlement items for payments when transactions are made by compatible transportation cards. You are trying to build a settlement system.

An object of the present invention is to issue a card by developing a system and a method of operating the system that can mutually settle the use price for card transaction details according to a common standard settlement item based on a compatible transit card that is compatible with the whole country. With the mutual compatibility and settlement of the public transportation payment bills between the operators and the businesses that are subject to card payments, it is possible to use various public transportations with one compatible transportation card, thereby relieving inconvenience in using public transportation. It is to promote the use of public transportation.

Another object of the present invention, when the user uses a compatible transportation card is compatible with the payment issuance and settlement between the card issuer and the operators that are the card payment target, the conventional traffic card settlement system established differently for each region or operator The aim is to prevent problems such as overlapping investment between operators and to establish a common national technical standard to contribute to the stable transportation card system.

Another object of the present invention is that the user can use a variety of public transportation means with a single compatible transportation card, it is easy to collect and aggregate data such as usage patterns and frequency by public transportation means through mutual settlement system between operators Therefore, it aims to contribute to the efficient and appropriate planning and implementation of national public transport policies.

The present invention relates to a mutual settlement system and an operating method for a compatible transportation card. First, the mutual settlement system for a traffic card according to the present invention collects transaction history information by a traffic card from a separate traffic card terminal, classifies the collected transaction history information according to a traffic card issuer, and classifies the transaction details. Transmitting the transaction card information issued by the third party based on the standard settlement item among the information, and sending the mutual settlement request information on the transaction card transaction information issued by the third party to the third party settlement server, which is settled by the third party settlement server If it is determined that the return reason information exists, the mutual settlement approval information and the mutual settlement approval information according to the standard settlement item are received from the third-party settlement server in response to the mutual settlement request information, and the third-party settlement server setstles the transaction history information. If it is determined that the reason for return does not exist, a mutual settlement request is made from a third-party settlement server. Receiving a mutual settlement disapproved the information in response to a security, its accounting server to perform a mutual settlement; Based on the mutual settlement request information received from the company's settlement server, it is determined whether or not the preset settlement transfer reason information is present in the transaction history information received from the company's settlement server, and approved mutual settlement in response to the mutual settlement request information. A third-party settlement server that transmits mutual settlement approval information or mutual settlement approval impossibility information according to the information and standard settlement items to its settlement server; And a network connecting the company settlement server and the third party settlement server.

Next, the operation method of the mutual settlement system according to the present invention comprises the steps of the company's settlement server collects transaction details information from a separate transportation card terminal, and classifies the collected transaction details by transportation card issuer; As a result of the classification in step ⒜, when the transaction information is provided by the third-party issuance card, the company's settlement server sends the mutual settlement request information about the transaction history information and the transaction history information according to the standard settlement item to the third party settlement server. Step i to; And the third party settlement server transmits the transaction history information and the mutual settlement request information to the third party settlement server in step ,, and as the third party settlement server determines that the settlement transfer reason information does not exist, the mutual settlement request information from the third party settlement server. In case of receiving mutual settlement approval information and mutual settlement approval information based on standard settlement items in response to the transaction, the transaction details are based on mutual settlement approval information received by the company's settlement server and mutual settlement approval information based on standard settlement items. Incorporating the information into mutual settlement; It includes.

In addition, after the above step, the settlement server sends the transaction history information and the mutual settlement request information to the settlement server of the third party, and as a result, the settlement server determines that the settlement transfer reason information exists. In the case where the mutual settlement approval impossible information is received in response to the information, the settlement server may further include a step 하는 excluding the transaction history information from the mutual settlement.

In addition, based on the mutual settlement approval information received by the company's settlement server from the third party settlement server and the mutual settlement approval information according to the standard settlement item, the transaction history information subject to the mutual settlement approval to the separate financial server after the step 상기 above. Transmitting payment request information for; It is preferable to further include.

In this case, the standard settlement items are classified, file name, data serial number, unique number, card company code, card number, transaction amount, amount before transaction, amount after transaction, error code, transportation code, transaction type, NC, ID PSAM , TRT PSAM , PP IEP , ID EP , NT IEP , NI PP , NT PSAM , MTOT PSAM , ALG IEP , SINDC, ID CENTER , VK PSAM _ KDINDC , VK PSAM _ KDINDS , SINDS, Ride / Unload Departure Date, Arrival Code, Arrival Date, Terminal Number, Transit Division, Transit Time, Transit Time, Route ID, Route Number, Transport Operator ID, Transport Operator Name, Vehicle Number ID, Vehicle Registration Number, Hours of Use, Distance Card type, employee number, general COUNTER, general transaction amount, university student COUNTER, university student transaction amount, student COUNTER, student transaction amount, child COUNTER, child transaction amount, other COUNTER, other transaction amount, departure station name, destination station name, reprocessing , Any one or more of a PNR number, a return number, an original number and a date and time of handling It is desirable.

In this case, the settlement transfer reason information may include field error information including data values not specified in the standard settlement item; Double occurrence error information when the card number, the boarding date and time, and the boarding station ID classification code are the same; Sales date error with the date and time of future ride, error amount of usage amount incurred by 1 won unit fee; company settlement server sends BL (Black list) to other company's settlement server, and company settlement server receives BL code of third party settlement server BL error information, which is an error for a transaction that occurred 48 hours after receiving the message; Effective use date, which is an error for a transaction that is valid for more than 60 days from the date of use, based on the ride date and time when the boarding data alone or when the boarding and getting off data exist simultaneously. Error information; And card number error information for a case where the card number is not 20 digits in total or the card issuer itself defines an error for the card number if it does not conform to the card identification code system. It is preferable to include any one or more of these.

According to the present invention, as a mutual settlement system compatible with the payment and settlement of the use price payment between the card issuer and the card settlement provider that is the card payment target is established, the user can conveniently pay various public transportation means with one compatible transport card. Therefore, it has the effect of promoting and encouraging the use of public transportation.

In addition, according to the present invention, it is possible to prevent overlapping investment in the transportation card settlement system established differently for each region or operator through the mutual settlement system between the operators, the mutual settlement system is a common settlement expertise between the compatible transportation card operators As it is built and operated on the basis of this, it contributes to the stable operation of the common transportation card system.

In addition, according to the present invention, as the user can use a variety of public transport such as bus, subway, railroad with one compatible transportation card, it is possible to accurately grasp the frequency of use and payment history for each public transportation means, When establishing a policy on public transport at the national level, the mutual settlement system enables easy analysis of users' usage patterns or frequencies by public transportation, which contributes to efficient and appropriate policy establishment and implementation.

Before describing the details for carrying out the present invention, it should be noted that configurations that are not directly related to the technical gist of the present invention are omitted within the scope of not distracting the technical gist of the present invention. In addition, the terms or words used in the present specification and claims are intended to comply with the technical spirit of the present invention based on the principle that the inventor can define the concept of appropriate terms in order to best explain the invention. It should be interpreted as a concept.

Hereinafter, before explaining the mutual settlement system for the compatible traffic card according to the present invention in detail , the compatible traffic card in the present invention will be described.

In the present invention, the compatible transportation card is a “One Card All” led by the Ministry of Construction and Transportation in order to solve the user's inconvenience and overlapping investment of the operator due to the transportation card payment, payment and settlement system which is differently established for each region or each business operator. As part of the "Pass Standard Technology Development and Test Bed Operation Project", the compatible high pluses were made to be compatible with the railroad card company KORAIL, the bus and subway card company, the KFTC, and the highway card company HiPlus. (Hiplus) transportation card, compatible X-cash transportation card and compatible K-cash transportation card.

In the case of the compatible transportation card, an ADF (Add Data Field) called CONFIG DF is required for transportation compatibility in the Card Operation System (COS) in order to enable mutual payment, settlement, and settlement between transportation card operators. The CONFIG DF stores additional information such as transit information, transit information, entrance information, and the like, and optionally high pass-related information, and provides it to the outside when transacting with a traffic card. In addition, the compatible transit card has an internal command system and card standard in accordance with the KS-6923 standard and the KS-6924 standard.

However, the transportation card that is the subject of mutual settlement according to the present invention is not limited to the compatible transportation card according to the "One Card All Pass standard technology development and test bed operation business" described above, and has a separate settlement server. It is also applicable to mutual settlement between transportation card operators.

Hereinafter, the standard settlement item and the settlement return reason information in the mutual settlement system and the mutual settlement system operating method for the compatible transportation card according to the present invention will be described in detail.

First, the standard settlement item is an item defined for mutual settlement processing between transportation card operators, and can be largely divided into common information item, standard information item, and transaction detail item. First, the common information item is composed of division, file name, data serial number, unique number, card company code, card number, transaction amount, amount before transaction, amount after transaction, error code, transportation code and transaction type. Next, the standard information items are NC, ID PSAM , TRT PSAM , PP IEP , ID EP , NT IEP , NI PP , NT PSAM , MTOT PSAM , ALG IEP , SINDC, ID CENTER , VK PSAM _ KDINDC , VK PSAM _ KDINDS It also consists of SINDS. Lastly, the transaction details include the boarding / unloading classification, departure code, departure date, arrival code, arrival date, terminal number, transfer segment, transfer frequency, transit time, route ID, route number, transit company ID, and transit company name. , Vehicle number ID, vehicle registration number, time of use, distance used, card type, worker number, general COUNTER, general transaction amount, university student COUNTER, university student transaction amount, student COUNTER, student transaction amount, postmark COUNTER, postmark transaction amount, etc. It consists of COUNTER, other transaction amount, departure station name, arrival station name, reprocessing classification, PNR number, return number, original number and handling date and time. Hereinafter, each item in the standard settlement item will be described in detail.

The division item has a format A, has a length of one digit, and is defined as 'D' for the standard settlement item.

The file name item has a format of N and has a length of 8 digits. Details of the file name item are shown in Table 1 below.

Figure 112009057663303-PAT00001

(In Table 1, 'mmdd' value in the file name indicates a value obtained by subtracting 1 day from the date of transmission and reception when the transaction history information is transmitted and received according to the standard settlement item between the company's settlement server and the company's settlement server. Write the date of transmission / reception of the data.)

In addition, the data serial number item has a format N, has a length of 8 digits, and starts with '00000001'. In addition, the unique number item has a format of N, has a length of 20 digits, and consists of 8 digits of the transaction date and 12 digits of SEQ. The card company code item has a format of N and has a length of two digits, '13' for a KORAIL issued transportation card, '14' for a KFTC issued transportation card, and '15 for a high plus issued traffic card. To be defined. In addition, the card number item has an AN format and has a length of 20 digits, and a prepaid card includes 20 card numbers, and a postpaid card includes 16 card numbers and 4 blank spaces. In addition, the transaction amount item is N, has a length of 8 digits, and means the balance before the prepaid card request amount, and means the amount of the ticket at the time of purchasing multiple rail tickets on the KORAIL side.

In addition, the amount before the transaction item type is N, has a length of 8 digits, and means the balance after processing the prepaid card request amount. The amount of the post-transaction amount item is N and has a length of 8 digits, and means a balance after processing a prepaid card request amount.

In addition, the error code item is of type N, has a length of 4 digits, the ledger unregistered error code is '1001', the passenger error code is '1002', the ride amount error code is '1003', date and time error Code is '1004', Import request amount error code is '1005', Balance error code is '1006', VAN double occurrence error code is '1007', Card number error code is '0002', Field error code is '0004' ', Card company's double occurrence error code is' 0006', sales date error code is' 0007 ', processing request date error code is' 0008', BL error code is' 0011 ', effective date error code is' 0012', card The number error code is defined as '0013', the authentication error code as '0014' and other error codes as '0099'.

In addition, the transportation code item has an AN format and has a length of 6 digits, in the item '080800' for KORAIL, '010102' for airport railroad, '060205' for KFTC-related transportation, High Plus related transportation is defined as '070700'. Details of the transportation code item are shown in Table 2 below.

Figure 112009057663303-PAT00002

In addition, the transaction type item is of type N, has a length of one digit, in the item '0' for purchase, '1' for canceling the last transaction, '2' for KORAIL railway ticket refund, and purchase Transaction cancellation is defined as '9'.

In addition, the NC item is of type N, has a length of 8 digits, and means a total transaction collection frequency. And the ID PSAM The item is of type N, has a length of 16 digits, and represents an identifier of the PSAM. And the TRT PSAM The item is of type N, has a length of two digits, means a transaction type, '00' for purchase transactions, '01' for value store transactions, '02' for canceled transactions and error transactions, and parameter updates. In the case of '03'.

Also, the PPIEP The item is of type N and has a length of 6 digits, Identification of the transportation card operator. And the IDEP The item is of type AN, has a length of 10 digits, and means a serial number of an electronic money identifier. And NTIEP The item is the number of transactions of electronic money, the format is N, and it is 10 digits long. And the NIPPThe item is of type N, has a length of 5 digits, and represents the number of individual transaction purchases of electronic money. And NTPSAMThe item is of type N, has a length of 10 digits, and means a serial number according to the number of individual transactions in the PSAM (Purcharge Secure Application Module). And, the MTOTPSAMThe item is of type N, has a length of 10 digits, and the total amount of PSAM transactions. it means. And the ALGIEP The item is of type N, has a length of two digits, and represents an algorithm identification of the transportation card..The SINDS item has an AN format, has a length of 8 digits, and indicates a SIGN value of a SAM signature or prepaid card. And the IDCENTER The item is of type N, has a length of two digits, and represents the identity of an electronic money company. And the VKPSAM _ KDINDC The item is of type N and has a length of 2 digits, and means a version of KDINDC, which is a key used when generating a signature for verifying individual transaction details in the KFTC.PSAM _ KDINDSThe item is of type N, has a length of two digits, and refers to a version of KDINDS, which is a key used to generate signatures for verification of individual transactions in the KFTC. In addition, the SINDS item has an AN format, has a length of 8 digits, and indicates an individual transaction PSAM generation signature required by the high plus side.

In addition, in the case of the riding / getting off category, the format is AN, has a length of one digit, and when using buses and subways, the boarding is defined as 'R', the boarding is 'A', the boarding and unloading is defined as 'N', On the one side, it is defined as 'P' for ticket purchase, 'T' for bank transfer refund, 'C' for return charges, and 'F' for other mixed payments and issuance. In the case of '1', other roads are defined as '0'.

In addition, the departure code item, the type is AN, has a length of 10 digits, means a station code when using the subway, a station code when using the bus, the corresponding office number on the high-plus side, 6 digits and the departure station on the Korail side It is composed of four blank spaces and described. In addition, the departure date and time item, the format is N, has a length of 14 digits, means the ride date and time when using the subway, bus and rail, the entrance date and time on the high-plus side, the data in the format 'YYYYMMDDhhmmss' Is indicated.

In addition, the arrival code item has an AN format, has a length of 10 digits, a subway station getting off code, a bus station getting off a code, a high pass side transit office number, and a railway station 6 digits and a blank It is composed and described in four digits. In addition, the arrival date and time item, the format is N, has a length of 14 digits, the time of getting off when using the subway and bus, the time of passing through the office on the high-plus side, the arrival date and time on the Korail side, in the form of 'YYYYMMDDhhmmss' Mark the data.

In addition, the terminal number item is based on the terminal number of the getting off when the terminal is composed of a pair, the format is AN, has a length of 10 digits, the terminal number when using the subway and bus, reserved code when using the railway '0' and means a TID consisting of 4 digits of reverse number and 5 digits of counter number.

In addition, the transfer category is a type A, has a length of one digit, and when using the subway, bus, railway is defined as 'Y' when transferring, 'N' when non-transfer. On the high-plus side, it is defined as a numerical value according to the vehicle type classification, '1' for vans and passenger cars with 16 seats or less, '2', 33 for vans with load capacity of 2.5 tons and 17 to 32 passengers. '3' for vans and vans up to 3.5 tons in weight and '4' for trucks with three-axes with a load weight of 10 tons or less and less than 20 tons. '5' is defined as '6' for passenger cars and vans below 1000cc. The transfer frequency item has a format of N, has a length of 1 digit, and is defined as '0' on the Korail side. The transit time required item has a format of N, has a length of 4 digits, a data representation format according to 'mmss', and is defined as '0000' on the Korail side.

In addition, the route ID item has a format of N, has a length of 3 digits, and is configured and described on the KORAIL side by 2 digits of the train type and 1 digit of the cabin type. In addition, the line number item is AN, has a length of 6 digits, means a bus line number on a bus, and configures and describes a train number 5 digits and a blank 1 digit on the KORAIL side. In addition, the transport operator ID item has a format of N, has a length of 4 digits, consists of 2 digits of a division and 2 digits of a business serial number, and the 2 digits of the region is a region in Table 2 Same as the division code, and the two-digit manufacturer serial number is the same as the engine division code in Table 2 above, for example, '0007' for High Plus, '0008' for KORAIL and '0006' for KFTC It is defined as In addition, the name of the transportation operator name is AN, and has a length of 4 digits, and is defined as 'Korrail Networks' for KORAIL, 'HP' for High Plus, and 'Gold vacancy' for KFTC. In addition, the vehicle number ID item has a format of AN, has a length of 10 digits, the purchase date is written on the high-plus side, the railroad member number is written on the Korail side, and is processed as a blank if there is no railroad member number. The vehicle registration number item has an AN format, has a length of 12 digits, and records the actual return amount in the vehicle registration number item on a bus or the Korail side.

In addition, the usage time item has a format of N, has a length of 6 digits, and indicates data as 'hhmmss' on the bus and the Korail side. In addition, the use distance item has a format of N, has a length of 3 digits, and means a use distance when using a bus or on a Korail side. The card type item has a format of N, has a length of one digit, the general is defined as '0', the university student is '1', the teenager is '2', the child is '3', and the other is '4'. The employee number item has a format of N, has a 5-digit length, describes the ticket release serial number on the Korail side, and is an essential item on the HighPlus side.

In addition, the item of the departure station name is AN, having a length of 16 digits, the name of the departure station when using the subway, the name of the departure stop when using the bus, the name of the entrance office on the high plus side, and the name of the riding station on the Korail side. In addition, the arrival station name item is AN, having a length of 16 digits, the name of the station getting off when using the subway, the name of the station getting off when using the bus, the name of the exit office on the high plus side, and the name of the station getting off on the Korail side. The reprocessing item is of type A, has a length of one digit, and is defined as 'N' on the Korail side.

In addition, the college student COUNTER item, student COUNTER item, postmark COUNTER item, other COUNTER item and general COUNTER item is of type N and has a length of one digit. The college student transaction amount item, student transaction amount item, postmark transaction amount item, and other transaction amount item are of type N and have a length of 6 digits. The general transaction amount is N and has a length of 6 digits, and means the amount of use of subways and buses, the amount of tolls on the high-plus side and the amount of the ticket on the KORAIL side.

In addition, the PNR number item has an AN format, has a length of 15 digits, and means a rail journey number on the Korail side. The return number item and the original ticket number item have a format of N and have a length of 18 digits, and on the KORAIL side, the counter number is composed of 5 digits, 8 digits of release date and 5 digits of serial number. In addition, the handling date and time item is of type N, has a length of 14 digits, and indicates a release date and a return date and time.

Hereinafter, the settlement reason return information will be described in detail. The settlement reason return information defines an error that may occur in mutual settlement between the settlement server and the third party settlement server. The settlement reason return information may include field error information, double occurrence error information, usage amount error information, and BL (Black list) error information; Valid date error information, and card number error information.

At this time, the field error information occurs when the transaction value information transmitted from the company settlement server to the third party settlement server includes data values not specified in the above standard settlement item.

At this time, the double occurrence error information is generated when the card number, boarding date and time, and boarding station ID classification code are the same in transaction history information transmitted from the settlement server to the other company's settlement server.

At this time, the sales date error information is generated when the ride date and time is future in the transaction history information transmitted from the company's settlement server to the other company's settlement server.

At this time, the use amount error information is generated when a one-unit unit fee occurs in transaction history information sent from the settlement server to the third party settlement server.

At this time, the BL error information is in the transaction history information sent from the company's settlement server to the third party settlement server, the company settlement server sends a BL (Black list) to the third party settlement server, the company settlement server is the third party settlement server Occurs when a transaction occurs 48 hours after receiving the BL confirmation code.

In more detail, the BL data is data written by a traffic card operator to block a payment of a traffic card at a traffic card terminal, and is stored in a BL transmitter of a settlement server. The BL transmitter transmits BL data to a third-party settlement server. Preferably, the BL transmitter transmits BL data to the third-party settlement server and then confirms that the BL data is received from the settlement server.

In addition, the BL data is composed of a card company code item, a card number item, a BL number item, a registration / release classification item, and a card classification item. First, the card company code item and the card number item have the same description and definition as the card company code item and the card number item in the standard settlement item described above. In addition, the BL number item has a format of AN and is a serial number assigned to a traffic card that is blocked by the traffic card terminal because the BL corresponds to the BL defined by the traffic card provider, and has a length of 10 digits. In addition, the registration / release category is an AN and whether or not the traffic card corresponds to BL, has a length of one digit, '1' for BL registration, '0' for BL release define. Finally, the card classification item is N, has a length of one digit, and is defined as '0' in general, '1' in adolescents, and '2' in children.

At this time, the valid date error information is the transaction data sent from the company's settlement server to the other company's settlement server. When the date of getting off the card is the date of use of the card, it occurs in the case of a transaction for which the effective use date is more than 60 days from the date of use of the card.

In this case, the card number error information may not correspond to the card classification code system in transaction history information sent from the settlement server to the third party settlement server, and the card number is not 20 digits in total, or other card issuers themselves. This error occurs when the card number is an error.

Hereinafter, a mutual settlement system for a compatible traffic card according to the present invention will be described in detail. The mutual settlement system for a compatible transportation card according to the present invention includes a company settlement server, a third party settlement server, and a network.

First, the company settlement server collects transaction history information by a traffic card from a separate traffic card terminal, and classifies the collected transaction history information according to a traffic card issuer.

As a result of this classification, when the transaction information is generated by the company's issued transportation card, the settlement process is performed.

On the other hand, if it corresponds to transaction information generated by a third-party issued traffic card, it performs a function of transmitting mutual settlement request information on the third-party issued traffic card transaction history information and the third-party issued traffic card transaction history information according to the standard settlement item. .

Next, the third-party settlement server determines whether the settlement transfer reason information exists for the transaction history information according to the standard settlement item received from the company settlement server according to the mutual settlement request information received from the company settlement server. do.

As a result of the determination, if the settlement return reason information does not exist for the transaction details, the third-party settlement server transmits mutual settlement approval information as a response to the mutual settlement request information to the company settlement server. Performs the function of transmitting the mutual settlement approval details information according to the standard settlement item.

On the other hand, if the settlement return reason information is set for the transaction information, the third-party settlement server transmits the mutual settlement approval impossible information in response to the mutual settlement request information to the company settlement server , the transaction history information Should be excluded from mutual settlement.

Finally, the network serves to connect between the company's settlement server and the third-party settlement server, preferably a wired Internet network or VPN according to the TCP / IP protocol.

In addition, the VPN (Virtual Private Network) is a security test of the National Intelligence Service considering security and safety when interconnecting its settlement server and a third-party settlement server through a network, and performs encryption and decryption functions during data transmission and reception. do.

It will be described in detail below on the basis of the accompanying drawings for the company's own settlement server in the mutual settlement system according to the present invention. In the case of Figure 1 is a detailed configuration of the company's settlement server in the mutual settlement system for the compatible transportation card according to the present invention.

The company settlement server comprises a transaction information collecting unit, the first transaction information exchange unit, the settlement information receiving unit, preferably comprises a BL transmission unit or a transaction history settlement unit.

First, the transaction information collection unit collects transaction history information generated by a traffic card from a separate traffic card terminal and performs a function of classifying whether the transaction information is collected by a company or a third party according to the card issuer. do.

Next, when the first transaction information exchange unit classifies according to the traffic card issuer in the transaction information collection unit, and the transaction history information by the third-party issued traffic card, the transaction information is settled according to a standard settlement item. Send to the server, and transmits the mutual settlement request information for the third-party issued traffic card transaction history information. In addition, it is preferable to perform the function of transmitting the BL data received from the BL transmitter to a third party settlement server.

Next, when the settlement information receiver determines that the settlement transfer reason information does not exist in the transaction history information, the settlement information receiving unit receives mutual settlement approval information and mutual settlement approval information information according to the standard settlement item from the settlement server. Perform the function. On the other hand, if it is determined that the settlement transfer reason information for the transaction history information in the third-party settlement server, the mutual settlement approval impossibility information is received from the third-party settlement server.

Next, the BL transmitter stores the BL list data therein and transmits the data to the third party settlement server through the first transaction information exchanger.

In this case, the BL data is data created by the card issuer to block compatible transport card payments in the card terminal, and the BL data is used to determine whether there is BL error information in the reason for returning the settlement.

In addition, it is preferable that the third-party settlement server having received the BL data from the BL transmitter transmits a BL reception confirmation code for confirming the fact that the BL data has been received to the company's settlement server.

Lastly, the transaction history settlement unit is provided to the mutual settlement approval information and the standard settlement item from the third party settlement server in the case where settlement transfer reason information does not exist in the transaction history information transmitted from the company settlement server to the third party settlement server. When receiving the mutual settlement approval history information according to, the mutual settlement is performed by sending the payment request information for the transaction details information to a separate financial server.

Hereinafter, the third-party settlement server in the mutual settlement system according to the present invention will be described in detail based on the accompanying drawings. 2 is a detailed configuration diagram of a third-party settlement server in the mutual settlement system for the compatible transportation card according to the present invention.

The third-party settlement server is composed of a second transaction information exchange unit and a transaction information verification unit.

First, the second transaction information exchange unit receives the mutual settlement request information on the transaction history information and the transaction history information according to the standard settlement item from the company settlement server, and delivers it to the transaction information verification unit. In addition, when BL data is received from the company's settlement server, the BL data is transferred to the transaction information verification unit to be used when determining the presence of BL error information among settlement transfer reason information.

Next, the transaction information verification unit. According to the mutual settlement request information received from the company's settlement server, it performs a function to determine whether or not the predetermined settlement transfer reason information for the transaction history information according to the standard settlement item received from the company's settlement server.

In this case, when the transaction information verification unit determines that the settlement return reason information does not exist in the received transaction history information, the third party settlement server mutually settles in response to the mutual settlement request information received from the company settlement server. Mutual settlement approval details information based on the approval information and the standard settlement item are transmitted to the company settlement server via the second transaction information exchange unit.

On the other hand, when the transaction information verification unit determines that the settlement return reason information in the received transaction history information, the third-party settlement server mutual settlement in response to the mutual settlement request information received from the company settlement server The non-approval information is transmitted to the company's settlement server via the second transaction information exchange unit, and the transaction details are excluded from mutual settlement.

In addition, when receiving the BL data from the BL transmitter in the settlement server, the third-party settlement server preferably transmits a BL reception confirmation code to the settlement server to confirm that the BL data has been received.

Hereinafter, a method for operating a mutual settlement system for a compatible transportation card according to the present invention will be described in detail with reference to the accompanying drawings. 3 is a detailed flowchart of the procedure of the mutual settlement system for the compatible traffic card according to the present invention.

First, in the step 자사, the company's settlement server goes through the process (S100) of collecting transaction history information by the traffic card from the traffic card terminal, the company settlement server for the collected transaction history information according to the card issuer Classify (S110).

Next, according to the classification result in step ,, in the case of transaction history information for the transportation card issued by the company, the company settlement server performs the own settlement of the transaction history information in the company settlement server. (S130).

On the other hand, according to the classification result in step ⒜, in the case of transaction history information for the transportation card issued by the third party, in the step (b), the company's settlement server is a third party settlement server issued by a third party according to the standard settlement item Transaction history information by the traffic card and mutual settlement request information for the transaction history information is transmitted (S150).

Accordingly, the third party settlement server determines whether the settlement transfer reason information exists for the transaction history information according to the received mutual settlement request information.

At this time, when the third party settlement server determines that the settlement return reason information does not exist in the transaction history information, the company settlement server receives mutual settlement approval information in response to the mutual settlement request information from the third party settlement server and In accordance with the standard settlement item, mutual settlement approval information is received (S250). Accordingly, in step ⒞, when the company settlement server receives mutual settlement approval information based on mutual settlement approval information and standard settlement item, the settlement server includes the settlement settlement according to the corresponding transaction details information (S270). In addition, it is preferable that the settlement server further includes the settlement step of transmitting payment request information on the transaction details information to a separate financial server after the above step (v).

In addition, when the third party settlement server determines that the settlement return reason information exists for the transaction history information, the company settlement server receives the mutual settlement approval impossible information in response to the mutual settlement request information from the third party settlement server ( S210). Accordingly, in step ,, when the company settlement server receives the mutual settlement approval impossibility information, the transaction settlement information is excluded from the mutual settlement (S230).

In the operation method of the mutual settlement system according to the present invention, Preferably, in the step 자사, the company's settlement server transaction details that occur until 02:00 of the next day in the traffic card transaction history information generated in the traffic card terminal Including and including the transaction history information occurred on the settlement date.

In addition, the settlement date transaction history information generated by the company's issued transportation card is processed by the transportation card terminal.

On the other hand, with respect to the settlement date transaction history information by the third-party issued transportation card in the traffic card terminal, in the step 자사, the company's settlement server is settled with the mutual settlement request information for the transaction history information based on the standard settlement item It is desirable to send it to the third party settlement server by 15:00 the next day.

Next, the third party settlement server receives the settlement date transaction history information and the mutual settlement request information for the transaction history information from the settlement server, and determines whether settlement return reason information exists.

At this time, when the third party settlement server determines that the settlement transfer reason information does not exist in the settlement date transaction history information received from the settlement server, the settlement server in the step (i) provides the mutual settlement request information from the settlement server of the third party. In response, the mutual settlement approval information and the mutual settlement approval information according to the standard settlement item are received and received by 12:00 on the next day of the transmission date of the transaction history information and the mutual settlement request information. After step ,, the company's settlement server transmits the payment request information for the settlement date transaction history information to the separate financial server until 12:00 on the next day of the reception date of the transaction history information and the mutual settlement request information. It is preferable to perform mutual settlement.

In this case, when it is determined that the settlement transfer reason information exists in the settlement date transaction history information received from the settlement server by the third party settlement server, the settlement server in response to the mutual settlement request information is received from the settlement server of the third party. In response to the mutual settlement approval impossibility information is preferably received until 12:00 of the next day of the transaction history information and the mutual settlement request information transmission date, it is desirable to exclude from mutual settlement.

Hereinafter, the mutual settlement system for the compatible transportation card according to a preferred embodiment of the present invention will be described in detail based on the accompanying drawings. 4 is an overall configuration diagram of a mutual settlement system for a compatible transportation card according to a preferred embodiment of the present invention.

The mutual settlement system for a compatible transportation card according to a preferred embodiment of the present invention is a high plus settlement server 100, KORAIL settlement server 300, KFTC settlement server 500, VPN 700 and the Internet network ( 900).

First, the VPN 700 is connected to each of the high plus settlement server 100, the Korail settlement server 300 and the financial settlement account settlement server 500 and the Internet network 900, the VPN 700 is the Internet In the case where the settlement server and the other company's settlement server are connected to each other through the network 500, the National Intelligence Service has taken the security test in consideration of security and safety. Perform the function.

Next, the Internet network 900 is connected to the VPN 700 connected to the high plus settlement server 100, the VPN 700 connected to the KORAIL settlement server 300 and the KFTC settlement server 500. The connected VPN 700 to a mutual network. At this time, the Internet network 900 is a wired Internet network based on the TCP / IP protocol, considering the security and safety when connecting to the network of the third party settlement server, between the VPN 700 connected to each settlement server in a dedicated line It is preferable to connect.

The high plus settlement server 100 is a traffic card terminal installed in a highway office, etc., the Korail settlement server 300 is a traffic card terminal installed at a railway station, etc., and the KFTC settlement server 500 is a traffic card terminal installed at a bus and subway station. Collect transaction details from compatible transit cards.

In addition, the high plus settlement server 100, KORAIL settlement server 300 and the financial settlement agency settlement server 500, the transaction history information for the compatible transportation card issued by the company out of the collected transaction history information and the company Classify transaction details for compatible transportation cards issued by other companies.

As a result of classifying transaction details of compatible transit cards collected through a transit card terminal, if the transaction history information for compatible transit cards issued by the company is applicable, the high plus settlement server 100 and Korail The settlement server 300 and the KFTC settlement server 500 perform their own settlement.

Meanwhile, as a result of classifying the transaction history for the compatible transportation card collected through the company's transportation card terminal, if the transaction history information for the compatible transportation card issued by a third party is applicable, first, The positive settlement server 100 is a third party Korail settlement server 300 or the financial settlement agency settlement server 500, the Korail settlement server 300 is a third party high plus settlement server 100 or the financial settlement agency settlement server 500 The KFTC settlement server 500 transmits the transaction history information according to the standard settlement item and the mutual settlement request information about the transaction history information to the high plus settlement server 100 or the KORAIL settlement server 300 which are other companies. In addition, the high-plus settlement server 100 transmits the BL data stored in the BL transmission unit in the server to the KORAIL settlement server 300 and the KFTC settlement server 500 to determine BL error information among settlement transfer reason information. To use.

Next, the high plus settlement server 100, the KORAIL settlement server 300 and the KFTC settlement server 500 are included in the transaction history information according to the standard settlement item for the company-issued compatible transportation card received from the settlement server of the third party. It is determined whether the preset settlement transfer reason information exists.

As a result of the determination, when settlement return reason information exists in the transaction history information, the high plus settlement server 100, the KORAIL settlement server 300, and the KFTC settlement server 500 settle the third party that transmits the transaction history information. In response to the mutual settlement request information, the server transmits non-reciprocal settlement approval information and excludes the corresponding transaction details from mutual settlement.

On the other hand, if it is determined that the settlement return reason information does not exist in the transaction history information, the high plus settlement server 100, KORAIL settlement server 300 and the KFTC settlement server 500 may determine the transaction history information. Mutual settlement approval information is transmitted to the third-party settlement server in response to mutual settlement request information, and the mutual settlement approval details information according to the standard settlement item is transmitted and included in the mutual settlement. In addition, the high plus settlement server 100, KORAIL settlement server 300 and the KFTC settlement server 500 performs mutual settlement by transmitting payment request information about the corresponding transaction details information to a separate financial server. .

As described above, the present invention has been described and illustrated with reference to a preferred embodiment for illustrating the spirit of the present invention, but the present invention is not limited to the above-described configuration and operation as shown. In addition, those skilled in the art will appreciate that many changes and modifications can be made without departing from the scope of the technical idea of the present invention. Therefore, inventions which have been subjected to all appropriate changes and modifications and inventions belonging to the equivalents of the present invention should also be regarded as belonging to the present invention.

In the case of Figure 1 is a detailed configuration of the company's settlement server in the mutual settlement system for the compatible transportation card according to the present invention.

2 is a detailed configuration diagram of a third-party settlement server in the mutual settlement system for the compatible transportation card according to the present invention.

3 is a detailed flowchart of the procedure of the mutual settlement system for the compatible traffic card according to the present invention.

4 is an overall configuration diagram of a mutual settlement system for a compatible transportation card according to a preferred embodiment of the present invention.

Claims (13)

In the mutual settlement system for transportation cards, Collect transaction history information by traffic card from separate transportation card terminal, classify the collected transaction history information according to traffic card issuer, and transfer the transaction card information issued by other companies from the classified transaction history information into standard settlement item. If the third party's settlement server determines that the settlement return reason information exists for the transaction history information, the mutual settlement request information for the transportation card transaction history information issued by the third party is transmitted to the third party settlement server. In response to the settlement request information, if the mutual settlement approval information and the mutual settlement approval information according to the standard settlement item are received, and the third party settlement server determines that the settlement transfer reason information does not exist for the transaction history information, the third party settlement server In response to the mutual settlement request information, receiving mutual settlement approval impossible information, No. Settlement its servers to perform the settlement; Based on the mutual settlement request information received from the company's settlement server, it is determined whether or not the preset settlement transfer reason information is present in the transaction history information received from the company's settlement server, and approved mutual settlement in response to the mutual settlement request information. A third-party settlement server that transmits mutual settlement approval information or mutual settlement approval impossibility information according to the information and standard settlement items to its settlement server; And And a network connecting the company settlement server and the third party settlement server. The network of claim 1, wherein the network is Mutual settlement system for a traffic card, characterized in that any one or more of the Internet network and a virtual private network (VPN). The method of claim 1, wherein the standard settlement item is classified, file name, data serial number, unique number, card company code, card number, transaction amount, amount before transaction, amount after transaction, error code, transportation code, transaction type, NC , ID PSAM , TRT PSAM , PP IEP , ID EP , NT IEP , NI PP , NT PSAM , MTOT PSAM , ALG IEP , SINDC, ID CENTER , VK PSAM _ KDINDC , VK PSAM _ KDINDS , SINDS, Ride / Unload Departure Code, Departure Date, Arrival Code, Arrival Date, Terminal Number, Transfer Category, Transit Time, Transit Time, Route ID, Route Number, Transport Operator ID, Transport Operator Name, Vehicle Number ID, Vehicle Registration Number, Hours of Use, Usage distance, card type, working number, general COUNTER, general transaction amount, university student COUNTER, university student transaction amount, student COUNTER, student transaction amount, child COUNTER, child transaction amount, other COUNTER, other transaction amount, departure station name, destination station name, Reprocessing division, PNR number, return number, original number and date of handling Mutual settlement system for the transportation card comprises a phase. 4. The method of claim 3, wherein the settlement reason return information Field error information containing data values not specified in the standard settlement item; Double occurrence error information when the card number, the date and time of boarding and the boarding and discharging station ID classification code are the same; Sales date error in which the ride date and time is the future date and time, the usage amount error information incurred by the unit fee; BL error information, which is an error for a transaction occurring 48 hours after the first settlement server sends a BL (Black list) to the third party settlement server and the first settlement server receives the BL reception confirmation code of the third party settlement server; Effective use date, which is an error for a transaction that is valid for more than 60 days from the date of use, based on the ride date and time when the boarding data alone or when the boarding and getting off data exist simultaneously. Error information; And card number error information that is an error when the card number is not 20 digits in total or the card issuer itself defines an error for the card number if it does not conform to the card identification code system. Mutual settlement system for a traffic card comprising any one or more of. The method of claim 4, wherein the company settlement server A transaction information collection unit for collecting transaction history information on the traffic card from a separate traffic card terminal and classifying the transaction history information according to whether a compatible traffic card is issued by the company or a third party; The transaction history information of the third party issued transportation card among the transaction history information classified in the transaction history collection unit based on the standard settlement item, and the mutual settlement request information for the transaction history information to the third party settlement server 1 transaction information exchange unit; And a settlement information receiver for receiving mutual settlement approval information or mutual settlement approval impossibility information according to mutual settlement approval information and standard settlement item for transaction history information previously transmitted from a third-party settlement server; Mutual settlement system for a traffic card comprising a. The method of claim 5, wherein the company settlement server, A BL transmitter for storing BL (Black list) data and transmitting the stored BL data to the first transaction information exchanger to transmit to the third party settlement server; Mutual settlement system for a traffic card further comprising a. According to claim 6, The company settlement server, Received from a third-party settlement server Based on mutual settlement approval information and mutual settlement approval details information based on standard settlement items Transaction history settlement unit for transmitting the payment request information to a separate financial server; Mutual settlement system for a traffic card further comprising a. The method of claim 4, wherein the third-party settlement server A second transaction information exchanger receiving transaction history information and mutual settlement request information or BL data for the transaction history information according to a standard settlement item from the company settlement server, and transferring the transaction history information and BL data to the transaction information verification unit; And      If it is determined that the settlement transfer reason information does not exist in the transaction history information and the mutual settlement request information transmitted from the second transaction information exchange unit, the mutual settlement approval information and the response to the mutual settlement request information received from the settlement server Mutual settlement approval history information according to the standard settlement item is transmitted to the company's settlement server via the transaction information exchange unit, and if the third party settlement server determines that the settlement transfer reason information exists, the mutual settlement request information received from the settlement server A transaction information verification unit for transmitting mutually non-approval approval information in response to the second transaction information exchange unit to the company settlement server; Mutual settlement system for a traffic card comprising a. In the operation method of mutual settlement system for transportation card, Collecting, by the settlement server, transaction details from a separate traffic card terminal, and classifying the collected transaction details by traffic card issuer; 결과 If the result of the classification in step, corresponds to transaction details information by a third party issuance card, the company's settlement server sends the mutual settlement request information on the transaction history information and transaction history information according to the standard settlement item to the third party settlement server. Transmitting; And 결과 As a result of sending transaction details and mutual settlement request information to the third-party settlement server in the step 함에 above, the third-party settlement server determines that the settlement transfer reason information does not exist, and thus the mutual settlement request information from the third-party settlement server. In case of receiving mutual settlement approval information and mutual settlement approval information based on standard settlement items in response to the transaction, the transaction details are based on mutual settlement approval information received by the company's settlement server and mutual settlement approval information based on standard settlement items. Including the information in mutual settlement; Operation method of the mutual settlement system for a traffic card comprising a. The method of claim 9, wherein after the step ⒝, ⒟ As a result of sending transaction details and mutual settlement request information to the third-party settlement server, the settlement server determines that the reason for the return of settlement information exists, and in response to mutual settlement request information from the settlement server of the third party. When the settlement approval impossible information is received, the settlement server excluding the transaction history information from the mutual settlement; Operation method of the mutual settlement system for the traffic card further comprising a The method of claim 9, wherein after the step ⒞, 결제 Based on the mutual settlement approval information received from the third-party settlement server and the mutual settlement approval information according to the standard settlement item, the settlement server sends the payment request information about the transaction details subject to the mutual settlement approval to the separate financial server. Making; Operation method of the mutual settlement system for a traffic card further comprising a. The method of claim 10 or 11, wherein the settlement transfer reason information is Field error information containing data values not specified in the standard settlement item; Double occurrence error information when the card number, the boarding date and time, and the boarding station ID classification code are the same; Sales date error in which the ride date and time is the future date and time, the usage amount error information incurred by the unit fee; BL error information, which is an error about a transaction that occurs after 48 hours after the settlement server sends a BL list to the third party settlement server and the settlement server receives the BL reception confirmation code of the third party settlement server; Effective use date, which is an error for a transaction that is valid for more than 60 days from the date of use, based on the ride date and time when the boarding data alone or when the boarding and getting off data exist simultaneously. Error information; And card number error information that is an error when the card number is not 20 digits in total or the card issuer itself defines an error for the card number if it does not conform to the card identification code system. Operating method of the mutual settlement system for a traffic card, characterized in that it comprises any one or more of. The method of claim 10 or 11, wherein the standard settlement items are classified, file name, data serial number, unique number, card company code, card number, transaction amount, amount before transaction, amount after transaction, error code, transportation code, Transaction Type, NC, ID PSAM , TRT PSAM , PP IEP , ID EP , NT IEP , NI PP , NT PSAM , MTOT PSAM , ALG IEP , SINDC, ID CENTER , VK PSAM _ KDINDC , VK PSAM _ KDINDS , SINDS, Ride / Get off, departure code, departure date, arrival code, arrival date, terminal number, transfer section, transfer number, transit time, route ID, route number, transit company ID, transit company name, vehicle ID, vehicle registration number , Hours of Use, Distance, Card Type, Employee Number, General COUNTER, General Transaction Amount, College Student COUNTER, College Student Amount, Student COUNTER, Student Amount, Child COUNTER, Child Transaction Amount, Other COUNTER, Other Transaction Amount, Starting Station Name , Station name, reprocessing classification, PNR number, return number, original number and date of handling ; Operating method of the mutual settlement system for a traffic card, characterized in that it comprises any one or more of.
KR1020090088765A 2009-09-18 2009-09-18 Interconnect accounting system for compatible traffic card and management method therefore KR20110031047A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
KR1020090088765A KR20110031047A (en) 2009-09-18 2009-09-18 Interconnect accounting system for compatible traffic card and management method therefore
PCT/KR2009/005662 WO2011034231A1 (en) 2009-09-18 2009-10-01 Interconnection payment system for a compatible transportation card, and method for operating an interconnection payment system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020090088765A KR20110031047A (en) 2009-09-18 2009-09-18 Interconnect accounting system for compatible traffic card and management method therefore

Publications (1)

Publication Number Publication Date
KR20110031047A true KR20110031047A (en) 2011-03-24

Family

ID=43758821

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020090088765A KR20110031047A (en) 2009-09-18 2009-09-18 Interconnect accounting system for compatible traffic card and management method therefore

Country Status (2)

Country Link
KR (1) KR20110031047A (en)
WO (1) WO2011034231A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101536580B1 (en) * 2013-08-27 2015-07-15 삼성에스디에스 주식회사 Fare payment method and apparatus thereof
KR20180000946A (en) * 2016-06-24 2018-01-04 주식회사 엘지씨엔에스 Traffic charge server and method for calculating traffic charge thereby

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20030020189A (en) * 2001-09-03 2003-03-08 윤학범 Integrated electronic money system
KR100470731B1 (en) * 2002-06-10 2005-03-10 한국전자통신연구원 An Integrated Payment System and its Method of Toll and Parking Fee using various Contactless IC cards for Electronic Money
KR100519828B1 (en) * 2003-08-01 2005-10-06 에스케이 텔레콤주식회사 Pass Card Issue System by Using White List and Method Thereof
KR20080017878A (en) * 2006-08-23 2008-02-27 (주)로직아이텍 System operation for account management of prepaid smart card

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101536580B1 (en) * 2013-08-27 2015-07-15 삼성에스디에스 주식회사 Fare payment method and apparatus thereof
KR20180000946A (en) * 2016-06-24 2018-01-04 주식회사 엘지씨엔에스 Traffic charge server and method for calculating traffic charge thereby

Also Published As

Publication number Publication date
WO2011034231A1 (en) 2011-03-24

Similar Documents

Publication Publication Date Title
US10810594B2 (en) Delayed transit fare assessment
RU2421812C2 (en) Method and system for use contactless payment cards in transport system
US7731086B2 (en) System and method for mass transit merchant payment
US8386376B2 (en) System and method using enhanced authorization data to reduce travel-related transaction fraud
KR101218693B1 (en) System for payment and adjustment compatibility type traffic card and method therefore
US8954344B2 (en) Methods of offline fare collection for open-loop and hybrid card systems
JP3468744B2 (en) Automatic fare adjustment system
JP2020074138A (en) System and method for providing, reloading, and redeeming stored value card for use in transit application
JP2002042182A (en) Ticket processing system and terminal device for it
KR20110031047A (en) Interconnect accounting system for compatible traffic card and management method therefore
KR102016621B1 (en) A method for determination, payment, and adjustment of traffic charge based on remote authorization for transaction
Cunningham Smart card applications in integrated transit fare, parking fee and automated toll payment systems-the MAPS concept
Sethi et al. Nationwide Electronic Toll Collection Interoperability
JP2905685B2 (en) Automatic ticket gate system
WO2019087315A1 (en) Information relay device, information relay method, and program
JPH02136990A (en) Ticket examination system
AU2012203879A1 (en) Method and system for using contactless payment cards in a transit system

Legal Events

Date Code Title Description
A201 Request for examination
E902 Notification of reason for refusal
AMND Amendment
E601 Decision to refuse application
AMND Amendment