|
Wicket Common Features:
Wickets utilize ISO 15693 standard RFID tags having a guaranteed
unique 64-bit UserID value to uniquely identify each manufactured
tag. If all of the possible values were used it mean that everyone
on this planet could have about 4 billion numbers to themselves....
so, we won't be running out anytime soon. IDX encrypts and stores
data on each Wicket for the sole purpose of enabling the Wicket
Reader to authenticate it as a true Wicket as a first line of
defense against counterfeiting attempts that are particularly
important in stored value applications. Each Wicket has multiple
blocks of data which many be written and read by the Wicket Reader
according to the application needs. Wickets have no batteries or
electrical contacts to power them, but derive their electrical power
to operate the onboard chip from the RF field emitted from the
Wicket Reader. Wickets are laminated cards having the RFID tag inlay
in the center, a layer of Teslin on either side for custom graphics
and to provide exceptional anti-tear and crack physical properties,
and a polyester or PVC cover layer on each side for rigidity.
Account Based Wickets:
The function of an Account Based Wicket is to primarily provide the
UserID to a system which will use it to access information about the
customer in a network connected server database. Account Based
Wickets have 64 blocks of 32 bits each that can be read or written
to with the Wicket Reader via commands received from the OEMs
equipment. There is no special protection afforded these blocks of
data.
Stored Value Wickets:
The function of a Stored Value Wicket is to provide a
secure means of storing customer account information right on the
Wicket. Stored Value Wickets utilize an enhanced variety of the ISO
15693 standard RFID tags that have provide facility for a hidden
32bit password on each Wicket that must be used known by a reader
when attempting to communicate with the RFID tag in order to access
its data. For Wickets, IDX has used an encryption algorithm that
results in the hidden password for each Wicket being different to
prevent the possibility that someone could change data on a Wicket
by using just any ISO 15693 reader purchased in the market. To
prevent someone from counterfeiting Wickets using a Wicket Reader,
each Wicket Reader requires a computed challenge-response handshake
with the controller for the Wicket Reader to authenticate the
controller before it will accept a command to write to a Stored
Value Wicket.
More To Be Posted Here Soon - Click Button Above For More
Information.
|
