4.3 Autopass Data Formats

4.3 Autopass Data Formats

4.3 AutoPASS Data Formats DOCUMENT STATUS Document number: 4.3 – AutoPASS Data Formats Status Version Description Final 1.1 Authorisation Name Date Signature Author Per Einar Pedersli 02.03.2017 Norwegian Public Roads Kåre Inge Viken Administration 02.03.2017 DOCUMENT REVISION HISTORY Version Date Author Main changes 1.0 02-03- Per Einar New document 2017 Pedersli 1.1 14-01- Kåre Inge Agreement changed with contract when regarding OBU 2018 Viken customers. Minor corrections. 1.2 31-10- Kåre Inge Some corrections marked yellow. New information 2018 Viken regarding whitelist. | Document 4.3 AutoPASS Data Formats Version 1.1 Date 14.01.2018 Page 2 of 38 Table of contents DOCUMENT STATUS .................................................................................................................................... 2 1 ABOUT THIS DOCUMENT ................................................................................................................... 4 2 GENERAL SYSTEM OVERVIEW ......................................................................................................... 5 3 BRIEF INFORMATION REGARDING EXISTING FORMATS ........................................................... 6 3.1 Brief information about the different formats ..................................................................................... 7 4 APPENDIX OVERVIEW ......................................................................................................................... 9 5 OVERVIEW OF CHANGES ................................................................................................................. 10 6 DISTRIBUTION AND HANDLING ..................................................................................................... 11 6.1 Information about ACT, TST and AIT ............................................................................................... 11 6.2 Information about Whitelist (NSL, HGV and HGVC) ....................................................................... 12 6.3 Information about Blacklist (NAT) .................................................................................................... 13 6.4 Information about Alarms/Event messages (ALM) ........................................................................... 15 7 ROADSIDE ............................................................................................................................................ 16 7.1 General format rules at Roadside ..................................................................................................... 18 7.2 Format specifications - Roadside ...................................................................................................... 19 8 AUTOPASS TOLL COLLECTOR (TC) ................................................................................................ 20 8.1 Format specifications – TC ............................................................................................................... 21 9 AUTOPASS TOLL SERVICE PROVIDER (TSP) ................................................................................ 22 9.1 Format specifications – TSP ............................................................................................................. 23 10 AUTOPASS IP ................................................................................................................................... 24 10.1 Format specifications – AutoPASS IP ............................................................................................... 26 11 AUTOPASS FERRY .......................................................................................................................... 28 12 AUTOPASS HUB ............................................................................................................................... 29 12.1 Format specifications – AutoPASS HUB .......................................................................................... 31 13 EASYGO HUB ................................................................................................................................... 33 13.1 Format specifications – EasyGo HUB Interface to AutoPASS/ACFC HUB ..................................... 34 14 ACFC HUB ......................................................................................................................................... 35 14.1 Format specifications – ACFC HUB Interface to AutoPASS HUB ................................................... 36 15 AUTOPASS SERVICE LAYER ........................................................................................................ 37 16 ANPR & MANUAL IMAGE PROVIDERS ...................................................................................... 38 | Document 4.3 AutoPASS Data Formats Version 1.1 Date 14.01.2018 Page 3 of 38 1 About this document This document is the main document for all information exchange between the different system solutions for toll charge collection in Norway. The document describes what information is exchanged, and refers to all other relevant documents. | Document 4.3 AutoPASS Data Formats Version 1.1 Date 14.01.2018 Page 4 of 38 2 General system overview The figure below illustrates the new system solutions for toll collection in Norway. This document has format descriptions for interfaces illustrated with the blue arrows. | Document 4.3 AutoPASS Data Formats Version 1.1 Date 14.01.2018 Page 5 of 38 3 Brief information regarding existing formats Most of the formats are described in two documents. These two documents does have an overlap when it comes to definitions of the same formats. This is due to the fact that EasyGo is a joint venture between several countries, and most of these formats are also used by the Norwegian AutoPASS community. The following is a illustration of the overlap, and should serve as a guideline for which document should be used when. Some formats may differ from the "EasyGo Specification". The 203 – Technical requirements data format and interface specifications, can be found here. | Document 4.3 AutoPASS Data Formats Version 1.1 Date 14.01.2018 Page 6 of 38 3.1 Brief information about the different formats ACT (Actor table) Contains information about all actors in AutoPASS and the EasyGo partnership (TC and TSP). Example of information in this table: Actor ID, Actor name, Address, Phone, IBAN / BIC. Data is maintained at AutoPASS IP and in the EasyGo partnership. AutoPASS specification is equal to the EasyGo specification on this format. TST (Toll station table) Contains information about all the toll stations in AutoPASS and the EasyGo partnership. Example of information: Actor ID, Actor name, Location names, Network Information. Data is maintained at AutoPASS IP and in the EasyGo partnership. AutoPASS specification is equal to the EasyGo specification on this format. AIT (Accepted issuer table) - Roadside Contains information about valid issuers and tag series. Data is maintained at AutoPASS IP and in the EasyGo partnership. AutoPASS specification is equal to the EasyGo specification on this format. NSL (Norwegian status file / OBE status file) - Roadside Contains information about valid Norwegian contracts. This format is a simpler version of the whitelist (HGV) for use on the roadside. Example of data in the table: Tag number, exemption, low balance. The file is generated at AutoPASS IP. Tariff-fil / Price file - Roadside Contains prices, opening hours / days. Used primarily to display the right price on VMS signs at the roadside. The file is generated at AutoPASS IP. Transaction-file - Roadside Contains information about registered passages from one or more toll stations. The file is generated at the roadside. | Document 4.3 AutoPASS Data Formats Version 1.1 Date 14.01.2018 Page 7 of 38 Picture-file - Roadside Contains images related to the passages in the Transaction-file. The file is generated at the roadside. Picture-Text file - Roadside Contains explanation of the different signal codes. This information is added to the image (Picture-file) on the roadside. The file is generated at the roadside. Exception Messages - Roadside Contains information with exception messages from the roadside. The file is generated at the roadside. TIF (Transit information file) Contains information about transactions (passages) with vehicle/passage/price-data. Example of data in the table: Actor ID, Tag number, Toll Station/Lane. The file is generated at AutoPASS IP for AutoPASS and at a EasyGo TC for EasyGo transactions. There is an ongoing process to get EasyGo to use the same format specification. Whitelist (HGV) Contains information about customers / vehicles that have a contract with an issuer. Example of data in the table: Actor ID, Tag number, Vehicle Group, Euro Class. New contracts as well as changes to contracts are made by TSP. The whole table is managed by AutoPASS IP. AutoPASS specification is equal to the EasyGo specification on this format. Whitelist complete (HGVC) Same as Whitelist (HGV) but Contains all valid AutoPASS and EsyGO contracts. NAT (Not accepted table, Black list ) AutoPASS blacklist is generated at AutoPASS HUB and forwarded to EasyGo Hub, this is only used in EasyGo. This list contains all the AutoPASS tags that are not valid. The whole table is managed by AutoPASS IP. AutoPASS specification is equal to the EasyGo specification on this format. ALM (Alarm Format) Contains information about alarms from AutoPASS IP, Roadside, EasyGo HUB and AutoPASS HUB | Document 4.3 AutoPASS Data Formats Version

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    213 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us