Table of Contents - APTAStandards.com

More documents

Recommendations

Info

• Front-end devices 4.7.2 Applicability to UTFS Effort TransLink modate the unique fare and business le structures of at least 26 participating transit agencies. It currently supports majority of the fare t t the US public transit industry. Of all the ocuments analyzed, this specification is the only one that is based on an actual d ® is the first smart card based regional transit fare payment system in the United States. The system is designed to accom ru produc ypes that are available in d implementation. There is a one to one match between most of the TransLink UD an WP 4 message types. ERG stated that the APTA-000 specifications analyzed in the Section 4.9 of this document will supercede the Phase I TransLink document analyzed below, and represent the foundation of the Translink Phase II messages. 4.7.3 Common Message Structure The TransLink ® message structure consists of a header followed by a UD record, which contains the tr ansaction specific usage data as illustrated in Figure 4.7-1. The structure is designed to allow bat ch transmission of multiple card transactions or event data under a sin gle header. The UD record consists of 18 sub fields, which include both financial and non-financial transaction data and support VEI data structures by utilizing VEI log file dialogs. Header Version Header Header Length Card SN Transaction Sequence Batch Sequence Contract ID Operator ID Exhibit 4.7-1 TransLink ® Usage Data Records Header UD RECORD Contract SN 4.7.4 Message Types Security Module ID Contract Sequence # Device ID Contract Sync # Payment Method Key UD UD Version NO Transaction Qualifier MAC Header Version Amount Operator ID Sequence # Date and Time Location Balance UD Type Last Add Value Summary The TransL ink transactions fall into one of the following six UD types: ® • Fare Transaction • Add Value Transaction • Card Management Events • Device Events • Audit Register Snapshots UD Sub- Type Card Sync No UD Version Each UD type is further divided into subtypes within them as listed in Appendix B. Page 52 Fare Category Usage Data Destination Location MAC MAC
4.7.4.1 Transaction Data The “Fare Transaction” UD record is generated by card reader devices and can be considered the equivalent of the “Farecard Usage Transaction” as proposed by the WG4. Different subtypes of the Fare Transaction record are defined as follows: • Single-tag fare payment, ride destination unknown • Dual-tag entry transaction, maximum fare deducted (purse debit) • Dual-tag exit transaction, fare adjustment (purse rebate) • Dual-tag entry transaction, no fare deduction • Dual-tag exit transaction, fare payment • Single-tag fare payment, known ride destination Two record subtypes are defined for a single-tag system. One subtype is generated when the reader does not know the destination, and the other subtype is generated when the reader device obtains the destination location from either the driver console or the patron. Using a card in a dual-tag system results in two Fare Transaction UD records being genera ted. A dual-tag entry transaction (maximum fare deducted) record is generated at the start of a ride on an open two-tag system, with a matching dual-tag exit transaction (fare adjustment) record being generated at then end of the ride. Similarly, a dual-tag entry transaction (no fare deduction) record will be generated at the start of a ride on a closed-barrier two-tag system, matched by a dual-tag exit transaction (fare payment) record at the end of the ride. An “Add Value Transaction” UD record, the equivalent of WG4 proposed Add Value Transaction Data message, is generated by all devices that add value to TransLink cards. The following record subtypes reflect the variances in the payment method: • Cash payment at a Ticket Office Terminal (TOT) or Add Value Machine (AVM) • Check payment at a TOT • Credit card payment at a TOT or AVM • Debit card payment at a TOT or AVM • Periodic Autoload at a reader device • ThresholdAutoload at a reader device • Remote re-load at a reader device • Remote load of a new pass or ride book at a reader device Tra L udit register snapshots. Audit gisters are non-resettable counters and accumulators used within the TransLink ® ns ink it ® also provides a separate message type for a re system to give an independent method of verifying UD completeness. Different aud register snapshot subtypes are defined as follows: • CID audit registers Page 53
Page 1 and 2:
SMART CARD STANDARDS AND SPECIFICAT
Page 3 and 4:
4.4.7 Security Requirements........
Page 5 and 6: Document History Revision Reason Fo
Page 7 and 8: Acronym List UTFS Universal Transit
Page 9 and 10: technology to achieve interoperabil
Page 11 and 12: This report encompasse s the review
Page 13 and 14: Identify S m art Card Indust ry S t
Page 15 and 16: The standards and specifications th
Page 17 and 18: These standards and specifications
Page 19 and 20: Although there is no “one-to-one
Page 21 and 22: 4.1.4.2 Card Management Data The st
Page 23 and 24: with ISO/IEC 7816-6, there is no re
Page 25 and 26: these messages constitutes a file.
Page 27 and 28: Phone interviews and/or email corre
Page 29 and 30: The ITSO message body consists of i
Page 31 and 32: Exhibit 4.2-2 Product Types Type Co
Page 33 and 34: Capability Values or RFU Product Pr
Page 35 and 36: opted to contract these services ou
Page 37 and 38: e given careful consideration for a
Page 39 and 40: - Transaction date and time - Trans
Page 41 and 42: cardholder related data as in the c
Page 43 and 44: CLIENT Exhibit 4.3-9 OFX Security S
Page 45 and 46: may well be eliminated if, and when
Page 47 and 48: Exhibit 4.4-4 Condition Dialogue St
Page 49 and 50: 4.4.7 Security Requirements The Mes
Page 51 and 52: Application Retailer Product Retail
Page 53 and 54: Exhibit 4.6-1 CID Edge Interface Me
Page 55: 4.6.8 Timing and Routing The CID Ed
Page 59 and 60: 4.7.4.3 System and Device Data The
Page 61 and 62: Following the authentication proces
Page 63 and 64: Data” transaction messages propos
Page 65 and 66: Field Name Description reading the
Page 67 and 68: 4.8-7 Product Transactions Usage Me
Page 69 and 70: 4.8.4.5 Peer-to-Peer Clearing and S
Page 71 and 72: standard does not mandate the compl
Page 73 and 74: Item Number Exhibit 4.9-2 Part 1 Fi
Page 75 and 76: 4.9.4.2 PICC Scheme Control Message
Page 77 and 78: • Registration • Negative List
Page 79 and 80: 5.0 FINDINGS This section presents
Page 81 and 82: Exhibit 5-2 illustrates the relevan
Page 83 and 84: Required. This set of specification
Page 85 and 86: Project/Specification/Standard Spon
Page 87 and 88: APPENDIX B COMPLETED CRITERIA FORMS
Page 89 and 90: ISO/IEC 8583 Criteria Transaction D
Page 91 and 92: TRANSLINK ® Criteria Transaction D
Page 93 and 94: RIS PART 4 Criteria Transaction Dat
Page 95 and 96: ITSO DATA ELEMENTS Message Type Dat
Page 101 and 102: Amount Net Reconciliation Receiving
Page 103 and 104: TRANSLINK Message Type Data Element
Page 105 and 106: Autoload non-purse counter remote l
Page 107 and 108:
card status failure reason Business
Page 109 and 110:
RIS PART 4: FOR A LIST OF DATA OBJE
show all

Table of Contents - APTAStandards.com

Create successful ePaper yourself

Delete template?

Save as template?