Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com Table of Contents - APTAStandards.com
4.9 REGIONAL INTEROPERABILITY STANDARD (RIS) PART 4 4.9.1 Description of the Standard RIS, the smart card based Regional Interoperability Standard for Electronic Transit Fare Payments, has been developed for Port Authority of New York and New Jersey (PANY/NJ), and currently consists of four parts. Part-1 is the User Guide and provides an overview of the RIS system approach. Part-2 of the RIS establishes the physical and electrical requirements for a Proximity Integrated Circuit Card (PICC) and a Card Interface Device (CID). Part-3 addresses the data structure of a PICC at a technical specification level of detail. RIS Part 4 defines standards for the exchange of messages between the Regional Clearing House (RCH) and other computer systems required to interface to it. Other computer systems include transit agency fare collection systems, card reload agent payment systems, transit benefits operators’ transaction processing systems, and card issuers’ card management systems. The message protocols and formats defined and standardized in RIS Part 4 cover the following exchange of data: • All messages originating from the RCH for management and accounting of all cards under its control. • Receipt of all issuance and fare payment-related transactional data generated within or for the benefit of a regional program for smart card-based electronic fare payments. • Settlement of transactions between multiple RCHs for instances where a PICC from one region is used to perform a fare payment-related transaction in a different region. RIS Part 4 messages are primarily designed to transmit card data objects defined in RIS Part 3 and provide flexibility for transmitting four additional non-RIS Part 3 objects. 4.9.2 Applicability to UTFS Effort Overall RIS Part 4 is a well-documented standard that is applicable to WP 4 efforts. The standard provides a conceptual fare system model where functions and responsibilities of a regional clearinghouse and system participants are defined. The establishment of this model is a crucial prerequisite to the WP 4 standard development effort. Following are the key advantages of the standard. • Direct support for WP1 card data structure due to its compliance with RIS Part 3 • Availability for APTA WP4 to adapt RIS Part 4 defines the requirements for messages to and from the RCH(s). Although the RIS Part 4 can be applied to messages generated by CIDs, in its current form, the Page 66
standard does not mandate the compliance of transactions originating from Tier 1 devices. Following are some of the disadvantages of RIS Part 4. • Limited support for data elements (objects) not compliant with WP1 data formats • In a draft form and not implemented 4.9.3 Com mon Message Structure RIS messages consist of four parts as shown in Exhibit 4.8-1. The total message length varies based on the number of objects included in Part 3 of the message. Each individual mes sage is iden tified by the “Message Identifier” and contains the message specific mandatory and optional data objects as designated by the object map. The details of these messages have been described in the following sections. 4.9.3.1 PART 1 Exhibit 4.9-1 RIS Message Structure T he Part 1 consists of fixed number of fields within each message category described in Section 4.9.4. The “Message Identifier” determines type of the message such as “Product Activation” or “Use of Stored Value”. 4.9.3.2 PART 2 The Part 2 includes message authentication data represented by the “AuthenticationDataGroup”. This group contains the data elements that will be required by the receiver to authenticate the message or series of messages. 4.9.3.3 PART 3 Exhibit 4.9-9 AuthenticationDataGroup MessageAuthCode MACKeyID AlgorithmID, optional MACHashID, optional This part contains the standard RIS object map and the objects required to be included in a specific transaction. The purpose of the object map is similar to the “bitmap” in ISO/IEC 8583, as explained in section 4.1.1. The Object Map is an 8 Byte, (64 Bit) binary Page 67
- 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 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: 4.8.4.5 Peer-to-Peer Clearing and S
- 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 97 and 98: ITSO DATA ELEMENTS Message Type Dat
- Page 99 and 100: 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
4.9 REGIONAL INTEROPERABILITY STANDARD (RIS) PART 4<br />
4.9.1 Description <strong>of</strong> the Standard<br />
RIS, the smart card based Regional Interoperability Standard for Electronic Transit Fare<br />
Payments, has been developed for Port Authority <strong>of</strong> New York and New Jersey<br />
(PANY/NJ), and currently consists <strong>of</strong> four parts. Part-1 is the User Guide and provides<br />
an overview <strong>of</strong> the RIS system approach. Part-2 <strong>of</strong> the RIS establishes the physical and<br />
electrical<br />
requirements for a Proximity Integrated Circuit Card (PICC) and a Card<br />
Interface Device (CID). Part-3 addresses the data structure <strong>of</strong> a PICC at a technical<br />
specification level <strong>of</strong> detail. RIS Part 4 defines standards for the exchange <strong>of</strong> messages<br />
between the Regional Clearing House (RCH) and other <strong>com</strong>puter systems required to<br />
interface to it. Other <strong>com</strong>puter systems include transit agency fare collection systems,<br />
card<br />
reload agent payment systems, transit benefits operators’ transaction processing<br />
systems, and card issuers’ card management systems.<br />
The message protocols and formats defined and standardized in RIS Part 4 cover the<br />
following exchange <strong>of</strong> data:<br />
• All messages originating from<br />
the RCH for management and accounting <strong>of</strong> all<br />
cards under its control.<br />
• Receipt <strong>of</strong> all issuance and fare payment-related transactional<br />
data generated<br />
within or for the benefit <strong>of</strong> a regional<br />
program for smart card-based electronic<br />
fare payments.<br />
• Settlement <strong>of</strong> transactions between multiple RCHs<br />
for instances where a PICC<br />
from one region is used to perform a fare payment-related transaction in a<br />
different<br />
region.<br />
RIS Part 4 messages are primarily designed to transmit card data objects defined in RIS<br />
Part 3 and provide flexibility for transmitting<br />
four additional non-RIS Part 3 objects.<br />
4.9.2 Applicability to UTFS Effort<br />
Overall RIS Part 4 is a well-documented standard that is applicable to WP 4 efforts.<br />
The<br />
standard provides a conceptual fare system model where functions and responsibilities<br />
<strong>of</strong> a regional clearinghouse and system participants are defined. The establishment <strong>of</strong><br />
this model is a crucial prerequisite to the WP 4 standard development effort. Following<br />
are<br />
the key advantages <strong>of</strong> the standard.<br />
• Direct support<br />
for WP1 card data structure due to its <strong>com</strong>pliance with RIS Part 3<br />
• Availability for APTA WP4 to adapt<br />
RIS Part 4 defines the requirements for messages to and from the RCH(s). Although the<br />
RIS Part 4 can be applied to messages generated by CIDs, in its current form, the<br />
Page 66
Change language