CEN/TR 16219:2011

Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviations
5 Background and Context
6 ITS Applications
7 Architecture
8 Requirements of Applications
9 Integration of VAS with EFC
10 Prerequisites for supporting VAS
11 Opportunities for improving the environment
   for VAS
Annex A (informative) - Examples of approaches
        to VAS based on EFC
Annex B (informative) - Example for a regulatory
        framework architecture
Bibliography

1.1 Definition of VASValue Added Services, VAS, is a term that was coined in the telecommunications industry for services that gobeyond core service, such as mobile voice communications. Such additional services are intended to addvalue for the consumers in order to encourage them to use the telecommunications service more often and toadd an additional revenue stream for the Service Provider.In the context of EFC, a VAS in this strict sense is a telematics service offered to the Service User by meansof an EFC OBE. This service might directly be consumed by the driver in the vehicle, or might, particularly inthe case of heavy vehicles, be targeted at the freight operator and be consumed in a back office. Suchservices can be fleet management services like track-and-trace, payment services such as paying petrolautomatically at the pump, or regulatory applications such as Electronic Licence Plate or access control. Suchadditional services and applications create additional value to the user, either by the value the new servicecreates to him, or in the case of regulatory services, by combining several functionalities in a single device,thus removing the need to install and maintain several pieces of equipment simultaneously.In a wider sense, the operator of the EFC service can draw additional benefit from the data collected by theEFC system. Data from EFC OBE gives a good account of the traffic situation on the charged network, andmay be utilised for statistical purposes, for traffic planning or even in real-time for traffic information purposes.The scope of this TR covers both the original meaning of VAS, namely both additional services to the user ofthe core EFC service and additional value created for the operator of the charging system.1.2 CoverageThe TR analyses all telematics applications that have the potential to be delivered as a VAS to EFC. Theanalysis covers the requirements of the VAS applications and the fit to the resources offered by the EFCsystem. It also analyses prerequisites in terms of business and technical system architecture in order toenable VAS to be delivered, including questions of control and governance, security aspects and privacyissues.The TR does not analyse commercial viability. Cost to benefit ratio and market potential for VAS areconsidered to be out of scope.The TR analyses the potential and pre-conditions for EFC equipment to serve as platforms for a diverse rangeof VAS. The VAS are considered to be add-ons to EFC equipment. The TR does not analyse the reversesituation, namely the situation where an EFC application is added to a telematics platform that has beendeployed for another core service, such as the suitability of navigation systems to serve as platforms for EFC.