Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Exhibit 4.6-1 CID Edge Interface Message Header Structure<br />
Sequence Name Data Type Range Description<br />
1 Header<br />
[..]<br />
1.1 Transtype<br />
1.2 date-time DATETIM<br />
E<br />
1.3 Normalorenhanced<br />
1.4<br />
Transstatus<br />
UBYTE 0=Reserved<br />
1=PICC Initialized<br />
2=PICC Issued<br />
3=PICC Negative<br />
Listed/Disabled<br />
4=Value Product<br />
Add/Deduct<br />
5=Pass Product Load<br />
6= Pass Product<br />
Remove<br />
7=Product/ s<br />
Validation/Use<br />
UBYTE 0 - Normal Transaction<br />
1 - Data Enhancement<br />
Transaction<br />
UBYTE 0=Normal<br />
1=Not confirmed by<br />
PICC<br />
Type <strong>of</strong> Transaction:<br />
1-Transmitted on PICC Initialization<br />
2-Transmitted on PICC Issue<br />
3-Transmitted on PICC Negative<br />
Listing<br />
4-Transmitted on Value add, deduct,<br />
or Autoload/Auto-unload<br />
5-Transmitted on Product Load or<br />
Autoload<br />
6-Transmitted on Product un-load or<br />
Auto-unload<br />
7-Transmitted on Product/s [Pass<br />
&/or SV/Purse] Validations & Uses<br />
Device’s Date and Time <strong>of</strong> this<br />
transaction. Seconds since Jan 1 1970<br />
Indicates a Data Enhancement<br />
transaction.<br />
This contains the<br />
transmission <strong>of</strong> the PICC’s previous<br />
Transaction Details<br />
Status <strong>of</strong> the transaction. This field can<br />
be used to identify whether the write<br />
to the card was confirmed or not.<br />
Optional - not available for an<br />
Enhancement Transaction<br />
The body <strong>of</strong> a message consists <strong>of</strong> a series <strong>of</strong> sub-groups. Each sub-group contains<br />
individual data elements with similar functional characteristics such as the CID Details<br />
and the Location Details as listed in Appendix C.<br />
4.6.4 Message Types<br />
CID Edge Interfaces currently defines the following six message types that can serve<br />
a model for device to backend data exchange:<br />
• PiccUse<br />
• PiccPurseLoad<br />
• PiccPassLoad<br />
• PiccInitialize<br />
• PiccNegativeList<br />
• PiccAutoLoadUnloadList<br />
Page 49<br />
as