Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Field Name Description<br />
reading the SamId and DeviceId data arriving in<br />
the header.<br />
Udsn UD sequence number. The UDSN will reset back<br />
to 0 when it increments past 0xFFFFFFFF.<br />
Transac tion Status Indicates if the UD transaction is a normal<br />
or test<br />
transaction. Test transactions are ignored.<br />
UdTyp e Main UD group that defines the type <strong>of</strong><br />
transaction.<br />
UdSubtype Sub UD groups within UD.<br />
4.8.3.3 Variant Data<br />
Variant<br />
Data consist <strong>of</strong> a group <strong>of</strong> selected data structures to form the body <strong>of</strong> a<br />
message. The message type determines the kind and quantity <strong>of</strong> data structures to exist<br />
in a message.<br />
For example a “Product Purse Use” Message contains the following data<br />
structures<br />
from the Exhibit 4.8-2:<br />
• SysComHdr_t<br />
• SysPiccCom_t<br />
• SysApplicationCom_t • DevUdPurseCommonHdr_t<br />
• SysFinDetails_t<br />
• DevUdPurseLavHdr_t • SysSecurityHdr_t 4.8.4 Message Types<br />
As in the TransLink system, ERG specifications break transaction data into types and<br />
subtypes to provide the system with a unique level <strong>of</strong> message identification.<br />
Messages fall into one <strong>of</strong> the following<br />
seven main transaction types (UdType), as<br />
illustrated<br />
in Exhibit 4.8-5. Each transaction group contains further message types<br />
(UDSubType)<br />
within them.<br />
Page 61