Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com Table of Contents - APTAStandards.com
4.2.2 Applicability to UTFS Effort The ITSO specifications are very applicable to the UTFS WP4 efforts for the following reasons: • Detailed coverage for all the components involved in a fare collection system • Transit industry specific messages and data elements • Smart card oriented architecture • Availablity to APTA • Easily adaptable by APTA Despite its advantages, ITSO does have some disadvantages: • ITSO has not been implemented in a public transit environment • ITSO defines Security Access Module (ISAM) currently provided through a single vendor • No support for clearing and settlement messages • Adoption of specification may cause impact on other APTA Workpackage efforts 4.2.3 Common Message Structure ITSO uses the ISO/IEC/ENV 14904 model for the data messages described in the specification. Message Header: The ITSO message header (including the frame header) contains: • Message sender identification • Message recipient identification • Unique message identifier • Starting and ending sequence numbers • Stored Value deductions and additions • Message Authentication Code (MA Message Body and Transaction Data Blocks: The message body consists of ITSO Transaction Data Blocks, each of which includes the following data elements: • Sequence Number • Date and time stamp • Data, or transaction record • MAC Certificate based on the first three fields of the data block Page 24
The ITSO message body consists of individual transaction blocks, each one representing a single business transaction, or device event as illustrated in Exhibit 4.2-1. Message Header Message Frame ITSO Message Header Exhibit 4.2-1 ITSO Message Structure Frame Header Message Body Seq Time Stamp Data MAC Transaction Data Blocks Message Code Count of Destinations Destinations Data Content The data portion of the transaction data blocks is dependent upon the message type and c an be configured to send to multiple destinations. This provision allows flexibility to separate “on-us” and “not on-us” transactions at the card reader level, and route them to their respective destinations if desired. Individual transaction data blocks can transmit multiple transactions, essentially acting as a file or batch transfer of information. Listed below are the parts of the Data or the transaction record component of the transaction data block: • Message Code • Count of destinations • Destinations • Data content The actual data elements are contained within the data content component of the tr ansaction record. 4.2.4 Message Types The ITSO specification provides the data flows and processes for card issuer, product owner, and retailer and transit service provider. The specification provides for data to be directed to any of the following entities: • A single entity (HOPS) Page 25
- 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: Phone interviews and/or email corre
- 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 and 56: 4.6.8 Timing and Routing The CID Ed
- Page 57 and 58: 4.7.4.1 Transaction Data The “Far
- 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
4.2.2 Applicability to UTFS Effort<br />
The ITSO specifications are very applicable to the UTFS WP4 efforts for the following<br />
reasons: • Detailed coverage for all the <strong>com</strong>ponents involved in a fare collection system<br />
• Transit industry<br />
specific messages and data elements<br />
• Smart card oriented architecture<br />
• Availablity to APTA<br />
• Easily adaptable by APTA<br />
Despite its advantages, ITSO does have some disadvantages:<br />
• ITSO has not been implemented in a public transit environment<br />
• ITSO defines Security Access<br />
Module (ISAM) currently provided through a<br />
single vendor<br />
• No support for clearing and settlement messages<br />
• Adoption <strong>of</strong> specification may cause impact on other APTA Workpackage efforts<br />
4.2.3 Common Message Structure<br />
ITSO<br />
uses the ISO/IEC/ENV 14904 model for the data messages described in the<br />
specification. Message Header:<br />
The ITSO message header (including the frame header) contains:<br />
• Message sender identification<br />
• Message recipient identification<br />
• Unique message<br />
identifier<br />
• Starting and ending<br />
sequence numbers<br />
• Stored Value<br />
deductions and additions<br />
• Message Authentication<br />
Code (MA<br />
Message Body and Transaction Data Blocks:<br />
The message body consists <strong>of</strong> ITSO Transaction Data Blocks, each <strong>of</strong> which includes the<br />
following data elements:<br />
• Sequence Number<br />
• Date and time stamp<br />
• Data, or transaction record<br />
• MAC Certificate based on the first three fields <strong>of</strong> the data block<br />
Page 24
Change language