Table of Contents - APTAStandards.com

4.7.4.3 System and Device Data
The data that customizes TransLink e in
le
re
® device software operation to support the devic
a specific operational context is referred to as “Configuration Data” (CD). The CD
includes all software components that are transferred to the device as downloadab
files including device application software executable images and parameters. There a
three main types of CD:
• Common CD
• Device specific CD
• Operator specific CD
Common CD contains data elements that apply to all TransLink devices for all
perators in the system such as system parameters and hotlists. System parameters
a
®
o
have potentially different values for different operators. All devices supporting
particular operator will be loaded with the same system parameters.
Device specific CD depends as much on a devices internal software design, as on the
external
functional requirements it supports. A sample of the device specific CD
payloads is as follows:
• TOT, AVM, DC, HCR and CID parameters
• Action List
• Contracts
• Transfers
• Calendar
• Fare Patterns
• Fare Code Matrix
• Fare Table
• Max Fare Table
• Routes
• Zone Table
• UI Resources
4.7.4.4 Event Data
TransLink ® system generates device event UD records in response to non-card related
device actions and changes of state. Event data messages consist of three subtypes:
• Subtype 1 – Simple event with no additional information
• Subtype 5 – Device event with status information
• Subtype 16 – Device event with additional data
Subtype 1 is designed to report only the event code together with the standard UD
record header in order to specify the event. Device simple events are usually non-
Page 55