Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com Table of Contents - APTAStandards.com
• A number of entities • Proprietary scheme data transmission systems Every message consists of 12 standard fields with a total of 34 bytes and a set of additional fields based on the type of message. Listed below are the main ITSO message types: • ITSO Shell • IPE Administration • Card Issue Records • ITSO ID • Stored Value • Charge to account • Loyalty • Predefined ticket and journey ticket • Refund • Journey Record • Exception • Miscellaneous 4.2.4.1 Transaction Data Stored value use and load transactions are treated different than the non-stored value load transactions. In general, pass and ticket-book loads are treated as new product creations and require addition of product type specific data to the message. The ITSO product ty pes are illustrated in Exhibit 4.2-2. Page 26
Exhibit 4.2-2 Product Types Type Code IPE (Product) Title 0 Private Entry within ITSO Directory 16 ITSO ID 2 Stored Value 3 Loyalty Type 1 4 Charge to Account 17 Loyalty Type 2 22 Pre-defined Ticket (Area Based) 6 Pre-defined ticket with days selection and action list capability 23 Pre-defined specif ic journey ticket 7 Pre-defined specif ic journey ticket with multi-ride and action list capability 24 Pre-defined specific journey ticket including reservation and restrictions 8 Pre-defined specific journey ticket including reservation and restrictions with action list capability 25 Travel related Voucher 9 Travel related Vouc her with multi-use and action list capability 26 Open system tolling 10 Open system tolling with multi-use and action list capability In non-stored value product usage and loads, the messages are structured in the following sequence: • Common data (required) • Stored Use data (Present when the product supports free transfers) • Product Specific Data (presence dependent on product type) Product specific data includes the following additional elements to the 53-byte long common data that is required in the message as described in Exhibit 4.2-3. Exhibit 4.2-3 Product Specific Data Product Type Additional Bytes 6,22 37 and 2 Variable Length fields 7,23 59 8, 24 57 and 2 variable length fields 9, 25 34 10,26 26 4.2.4.2 Card Management Data The ITSO Shell is the ITSO application with a file structure, directory entries and a security schema loaded onto the smart card platform. The ITSO Shell transactions fall into one of the following four groups: • Creating an ITSO Shell • Activating an ITSO Shell Page 27
- 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: The ITSO message body consists of i
- 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
- Page 79 and 80: 5.0 FINDINGS This section presents
Exhibit 4.2-2 Product Types<br />
Type Code IPE (Product) Title<br />
0 Private Entry within ITSO Directory<br />
16 ITSO ID<br />
2 Stored Value<br />
3 Loyalty Type 1<br />
4 Charge to Account<br />
17 Loyalty Type 2<br />
22 Pre-defined Ticket (Area Based)<br />
6 Pre-defined ticket with days selection and action list capability<br />
23 Pre-defined specif ic journey ticket<br />
7 Pre-defined specif ic journey ticket with multi-ride and action list capability<br />
24 Pre-defined specific journey ticket including reservation and restrictions<br />
8 Pre-defined specific journey<br />
ticket including reservation<br />
and restrictions<br />
with action list capability<br />
25 Travel related Voucher<br />
9 Travel related Vouc her with multi-use and<br />
action list capability<br />
26 Open system tolling<br />
10 Open system tolling with multi-use and action list capability<br />
In non-stored value product usage and loads, the messages are structured<br />
in the<br />
following sequence:<br />
• Common data (required)<br />
• Stored Use data (Present when the product supports free transfers)<br />
• Product Specific Data (presence dependent on product type)<br />
Product specific data includes the following additional elements to the 53-byte long<br />
<strong>com</strong>mon data that is required in the message as described<br />
in Exhibit 4.2-3.<br />
Exhibit 4.2-3 Product Specific Data<br />
Product Type Additional Bytes<br />
6,22 37 and 2 Variable Length fields<br />
7,23 59<br />
8, 24 57 and 2 variable length fields<br />
9, 25 34<br />
10,26 26<br />
4.2.4.2 Card Management Data<br />
The ITSO Shell is the ITSO application with a file structure, directory entries and a<br />
security schema loaded onto the smart card platform. The ITSO Shell transactions fall<br />
into one <strong>of</strong> the following four groups:<br />
• Creating an ITSO Shell<br />
• Activating an ITSO Shell<br />
Page 27
Change language