EN ISO 14819-6:2006

Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Symbols and abbreviations
5 Notation
6 Application description
   6.1 Introduction to RDS group bit pattern and notation
   6.2 RDS-TMC and Open Data Application
   6.3 Summary of TMC data elements in type 8A groups
7 Principles of the Encryption and Conditional Access
   methodology
8 Encryption by the service provider
   8.1 Service provider's requirements
   8.2 Use of type 8A groups for RDS-TMC encryption
   8.3 Encryption Administration group
   8.4 Encrypting location codes
9 Access to decrypted services by a terminal
   9.1 Terminal manufacturer's basic requirements
   9.2 Activation of a terminal
   9.3 Identifying an encrypted RDS-TMC service
   9.4 Decrypting location codes
10 Introduction of Encrypted services
   10.1 Terminal responses
   10.2 De facto strategy valid only for service providers
        wishing to generate revenue, prior to general
        availability of encryption
   10.3 Actions for existing providers of unencrypted TMC
        services
   10.4 Actions for potential providers of TMC services
   10.5 Timescales
Bibliography

ISO 14819-6:2006 establishes a method of encrypting certain elements of the ALERT-C coded data carried in the RDS-TMC type 8A data group, such that without application by a terminal or receiver of an appropriate keys, the information conveyed is virtually worthless.Before a terminal is able to decrypt the data, the terminal requires two "keys". The first is given in confidence by the service provider to terminal manufacturers with whom they have a commercial relationship; the second is broadcast in the "Encryption Administration Group," which is also a type 8A group. This specification explains the purpose of the two keys and how often and when the transmitted key may be changed.Before an individual terminal may present decrypted messages to the end-user, it must have been activated to do so. Activation requires that a PIN code be entered. The PIN code controls access rights to each service and subscription period, allowing both lifetime and term business models to co-exist.The specification also describes the considerations for service providers wishing to introduce an encrypted RDS-TMC service, migrating from either a "free-to-air" service based on public "Location Tables" or a commercial service based on a proprietary Location Table.Finally, "hooks" have been left in the bit allocation of the type 8A group to allow extension of encryption to other RDS-TMC services.