EUROPEAN STANDARD
`NORME EUROPÉENNE
`
`EUROPÄISCHE NORM
`
`EN 50067
`
`April 1998
`
`ICS 33.160.20
`
`Supersedes EN 50067:1992
`
`Descriptors: Broadcasting, sound broadcasting, data transmission, frequency modulation, message, specification
`
`English version
`
`Specification of the radio data system (RDS) for
`VHF/FM sound broadcasting in the frequency range
`from 87,5 to 108,0 MHz
`
`Spécifications du système de radiodiffusion de
`données (RDS) pour la radio à modulation de
`fréquence dans la bande de 87,5 à 108,0 MHz
`
`Spezifikation des Radio-Daten-Systems
`(RDS) für den VHF/FM Tonrundfunk im
`Frequenzbereich von 87,5 bis 108,0 MHz
`
`This CENELEC European Standard was approved by CENELEC on 1998-04-01. CENELEC members are
`bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving
`this European Standard the status of a national standard without any alteration.
`Up-to-date lists and bibliographical references concerning such national standards may be obtained on
`application to the Central Secretariat or to any CENELEC member.
`This European Standard exists in three official versions (English, French, German). A version in any other
`language made by translation under the responsibility of a CENELEC member into its own language and
`notified to the Central Secretariat has the same status as the official versions.
`CENELEC members are the national electrotechnical committees of Austria, Belgium, Czech Republic,
`Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway,
`Portugal, Spain, Sweden, Switzerland and United Kingdom.
`
`CENELEC
`
`European Committee for Electrotechnical Standardization
`Comité Européen de Normalisation Electrotechnique
`Europäisches Komitee für Elektrotechnische Normung
`Central Secretariat: rue de Stassart 35, B - 1050 Brussels
`
`© 1998 - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members
`and the European Broadcasting Union.
`
`Ref. No. EN 50067:1998 E
`
`EN 50067
`
`Specification of the radio data system (RDS)
`
`Jaguar Land Rover
`Exhibit 1029
`Page 001
`
`(cid:3)(cid:3)
`

`

`Page 2
`EN 50067:1998
`
`FOREWORD
`
`The Radio Data System RDS was developed by the European Broadcasting Union (EBU) Member countries who
`collaborated towards an internationally agreed standard for such a system. The Specification of the RDS System was
`initially published by the EBU in 1984 as doc.Tech 3244 [8] and is also the subject of ITU-R Recommendation BS.643-2.
`
`This revised text, which is published by the European Committee for Electrotechnical Standardization
`(CENELEC), was prepared by the RDS Forum in close collaboration with the Technical Committee 207 of CENELEC,
`and in close collaboration with experts from the EBU. In addition, certain elements of text have been revised to accord with
`experience gained with the RDS System and changes in broadcasting practice since the Specification was published. It is,
`nevertheless, expected that receivers produced to accord with this Specification will be compatible with RDS broadcasts
`which conform with previous editions of this Specification.
`
`Attention is drawn to the fact that there may be Intellectual Property Rights (IPR) in relation to certain provisions
`of this standard. The technical experts of TC 207 were unable to fully identify such claims due to the complicated legal
`issues involved. IPR holders should notify CENELEC of their claims.
`
`This document was submitted to the Unique Acceptance Procedure and was approved by CENELEC as EN 50067
`on 1998-04-01.
`
`The following dates were fixed:
`
`- latest date by which the EN has to be implemented
` at national level by publication of an identical national standard
`(dop)
` or by endorsement
`
`- latest date by which the national standards conflicting
` with the EN have to be withdrawn
`(dow)
`
`1998-12-01
`
`1998-12-01
`
`This European Standard replaces EN 50067:1992.
`
`This version of the specification includes several significant enhancements to the RDS features: Open Data
`Applications, Programme Type Name, EWS and Enhanced Paging Protocol. These are a fully backwards compatible set
`of additions. A receiver implemented in accordance with EN 50067: 1992 but receiving a transmission in accordance with
`this standard, whilst not able to respond to the enhancements, will not significantly under perform.
`
`This standard is also drafted to facilitate a world-wide standard by working towards harmonisation with the US
`NRSC RBDS standard.
`
`Jaguar Land Rover
`Exhibit 1029
`Page 002
`
`

`

`Page 3
`EN 50067:1998
`
`CONTENTS
`
`page
`0 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
`
` 6
`1 Modulation characteristics of the data channel (physical layer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`1.1 Subcarrier frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
`1.2 Subcarrier phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
`1.3 Subcarrier level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
`1.4 Method of modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` 8
`1.5 Clock-frequency and data-rate
`1.6 Differential coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` 8
`1.7 Data-channel spectrum shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
`
`2 Baseband coding (data-link layer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`2.1 Baseband coding structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`2.2 Order of bit transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`2.3 Error protection
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`2.4 Synchronization of blocks and groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`
` 12
` 12
` 12
` 13
` 14
`
`3 Message format (session and presentation layers)
` 15
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` 15
`3.1 Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` 15
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`3.1.1 Design principles
` 15
`3.1.2 Principal features
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` 17
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`3.1.3 Group types
` 19
`3.1.4 Open data channel / Applications Identification
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`3.1.4.1 Use of Open data applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
`3.1.4.2 Open data applications - Group structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` 21
`3.1.5 Coding of the Group types
`3.1.5.1 Type 0 groups: Basic tuning and switching information . . . . . . . . . . . . . . . . . . . 21
`. . . . . . . . . . 23
`3.1.5.2 Type 1 groups: Programme-item number and slow labelling codes
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`3.1.5.3 Type 2 groups: RadioText
` 25
`3.1.5.4 Type 3A groups: Applications Identification for Open Data . . . . . . . . . . . . . . .
` 27
`3.1.5.5 Type 3B groups: Open data application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` 28
`3.1.5.6 Type 4A groups: Clock-time and date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` 28
`3.1.5.7 Type 4B groups: Open data application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` 29
`3.1.5.8 Type 5 groups : Transparent data channels or ODA . . . . . . . . . . . . . . . . . . . . .
` 29
`3.1.5.9 Type 6 groups : In house applications or ODA . . . . . . . . . . . . . . . . . . . . . . . . . . 30
`3.1.5.10 Type 7A groups: Radio paging or ODA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
`3.1.5.11 Type 7B groups : Open data application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
`3.1.5.12 Type 8 groups: Traffic Message Channel or ODA . . . . . . . . . . . . . . . . . . . . . . . . 32
`3.1.5.13 Type 9 groups: Emergency warning systems or ODA . . . . . . . . . . . . . . . . . . . . 33
`3.1.5.14 Type 10 groups: Programme Type Name (Group type 10A) and Open data
` 34
`(Group type 10B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` 35
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`3.1.5.15 Type 11 groups: Open data application
`3.1.5.16 Type 12 groups: Open data application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
`3.1.5.17 Type 13A groups: Enhanced Radio paging or ODA . . . . . . . . . . . . . . . . . . . . . . 36
`3.1.5.18 Type 13B groups : Open data application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
`3.1.5.19 Type 14 groups: Enhanced Other Networks information . . . . . . . . . . . . . . . . . . . 38
`3.1.5.20 Type 15A groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
`3.1.5.21 Type 15B groups: Fast tuning and switching information . . . . . . . . . . . . . . . . . . 39
`
`Jaguar Land Rover
`Exhibit 1029
`Page 003
`
`

`

`Page 4
`EN 50067:1998
`
`page
`3.2 Coding of information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
`3.2.1 Coding of information for control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
`3.2.1.1 Programme Identification (PI) codes and Extended Country Codes (ECC) . . . .
` 40
`3.2.1.2 Programme-type (PTY) codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
`3.2.1.3 Traffic-programme (TP) and traffic-announcement (TA) codes . . . . . . . . . . . . . . 40
`3.2.1.4 Music Speech (MS) switch code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
`3.2.1.5 Decoder Identification (DI) and Dynamic PTY Indicator (PTYI) codes . . . . . . . 41
`3.2.1.6 Coding of Alternative Frequencies (AFs) in type 0A groups . . . . . . . . . . . . . . . . 41
`3.2.1.7 Programme-item number (PIN) codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
`3.2.1.8 Coding of Enhanced Other Networks information (EON)
`. . . . . . . . . . . . . . . . .
` 46
`3.2.2 Coding and use of information for display
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` 50
`3.2.3 Coding of clock-time and date (CT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` 50
`3.2.4 Coding of information for Transparent data channels (TDC) . . . . . . . . . . . . . . . . . . . . . . . .
` 50
`3.2.5 Coding of information for In House applications (IH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` 50
`3.2.6 Coding of Radio paging (RP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` 51
`3.2.6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
`3.2.6.2 Identification of paging networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
`3.2.7 Coding of Emergency Warning Systems (EWS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` 53
`
`44 Description of features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
`
`5 Marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`
` 57
`
`Jaguar Land Rover
`Exhibit 1029
`Page 004
`
`

`

`Page 5
`EN 50067:1998
`
`ANNEXES
`
`Annex A (normative) - Offset words to be used for group and block synchronization . . . . . . . . . . . . . . . . . . . . . . .
`
`page
` 59
`
`Annex B (informative) - Theory and implementation of the modified shortened cyclic code . . . . . . . . . . . . . . . . . . 60
`
`Annex C (informative) - Implementation of group and block synchronization using the modified shortened cyclic
`code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
`
`Annex D (normative) - Programme identification codes and Extended country codes . . . . . . . . . . . . . . . . . . . . . . .
`
` 69
`
`Annex E (normative) - Character definition for Programme Service name, Programme Type Name,
`RadioText and alphanumeric Radio paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
`
`Annex F (normative) - Programme Type codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
`
`Annex G (informative) - Conversion between time and date conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
`
`Annex H (informative) - Specification of the ARI system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`
` 83
`
`Annex J (normative) - Language identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`
` 84
`
`Annex K (informative) - RDS logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`
` 86
`
`Annex L (informative) - Open data registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
`
`Annex M (normative) - Coding of Radio Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
`
`Annex N (normative) - Country codes and Extended country codes for countries outside the
` European Broadcasting Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
`
`Annex P (normative) - Index of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
`
`Annex Q (informative) - Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
`
`Jaguar Land Rover
`Exhibit 1029
`Page 005
`
`

`

`Page 6
`EN 50067:1998
`
`0 Scope
`
`The Radio Data System, RDS, is intended for application to VHF/FM sound broadcasts in the range 87.5 MHz
`to 108.0 MHz which may carry either stereophonic (pilot-tone system) or monophonic programmes. The main objectives
`of RDS are to enable improved funtionality for FM receivers and to make them more user-friendly by using features such
`as Programme Identification, Programme Service name display and where applicable, automatic tuning for portable and
`car radios, in particular. The relevant basic tuning and switching information shall therefore be implemented by the type
`0 group (see 3.1.5.1), and it is not optional unlike many of the other possible features in RDS.
`
`1 Modulation characteristics of the data channel (physical layer)
`
`The Radio Data System is intended for application to VHF/FM sound broadcasting transmitters in the range 87.5
`to 108.0 MHz, which carry stereophonic (pilot-tone system) or monophonic sound broadcasts (see ITU-R
`Recommendation BS.450-2).
`
`It is important that radio-data receivers are not affected by signals in the multiplex spectrum outside the data
`
`channel.
`
`The system can be used simultaneously with the ARI system (see annex H), even when both systems are broadcast
`from the same transmitter. However, certain constraints on the phase and injection levels of the radio-data and ARI signals
`must be observed in this case (see 1.2 and 1.3).
`
`The data signals are carried on a subcarrier which is added to the stereo multiplex signal (or monophonic signal
`as appropriate) at the input to the VHF/FM transmitter. Block diagrams of the data source equipment at the transmitter and
`a typical receiver arrangement are shown in figures 1 and 2, respectively.
`
`1.1 Subcarrier frequency
`
`During stereo broadcasts the subcarrier frequency will be locked to the third harmonic of the 19-kHz pilot-tone.
`Since the tolerance on the frequency of the 19-kHz pilot-tone is ± 2 Hz (see ITU-R Recommendation BS.450-2), the
`tolerance on the frequency of the subcarrier during stereo broadcasts is ± 6 Hz.
`
`During monophonic broadcasts the frequency of the subcarrier will be 57 kHz ± 6 Hz.
`
`1.2 Subcarrier phase
`
`During stereo broadcasts the subcarrier will be locked either in phase or in quadrature to the third harmonic of the
`19 kHz pilot-tone. The tolerance on this phase angle is ± 10(, measured at the modulation input to the FM transmitter.
`
`In the case when ARI and radio-data signals are transmitted simultaneously, the phase angle between the two
`subcarriers shall be 90( ± 10(.
`
`Jaguar Land Rover
`Exhibit 1029
`Page 006
`
`

`

`Page 7
`EN 50067:1998
`
`Figure 1: Block diagram of radio-data equipment at the transmitter
`
`*
`
`
`The overall data-shaping in this decoder comprises the filter F and the data-shaping inherent in the biphase symbol decoder. The
`1
`amplitude/frequency characteristic of filter F is, therefore, not the same as that given in figure 3.
`1
`
`Figure 2: Block diagram of a typical radio-data receiver/decoder
`
`Jaguar Land Rover
`Exhibit 1029
`Page 007
`
`

`

`Page 8
`EN 50067:1998
`
`1.3 Subcarrier level
`
`The deviation range of the FM carrier due to the unmodulated subcarrier is from ± 1.0 kHz to ± 7.5 kHz. The
`1
`recommended best compromise is ± 2.0 kHz ). The decoder/demodulator should also operate properly when the deviation
`of the subcarrier is varied within these limits during periods not less than 10 ms.
`
`In the case when ARI (see annex H) and radio-data signals are transmitted simultaneously, the recommended
`maximum deviation due to the radio-data subcarrier is ± 1.2 kHz and that due to the unmodulated ARI subcarrier should
`be reduced to ± 3.5 kHz.
`
`The maximum permitted deviation due to the composite multiplex signal is ± 75 kHz.
`
`1.4 Method of modulation
`
`The subcarrier is amplitude-modulated by the shaped and biphase coded data signal (see 1.7). The subcarrier is
`suppressed. This method of modulation may alternatively be thought of as a form of two-phase phase-shift-keying (psk)
`with a phase deviation of ± 90(.
`
`1.5 Clock-frequency and data-rate
`
`The basic clock frequency is obtained by dividing the transmitted subcarrier frequency by 48. Consequently, the
`basic data-rate of the system (see figure 1) is 1187.5 bit/s ± 0.125 bit/s.
`
`1.6 Differential coding
`
`The source data at the transmitter are differentially encoded according to the following rules:
`
`Table 1: Encoding rules
`
`Previous output
`(at time t )
`i-1
`
`New input
`(at time t )
`i
`
`New output
`(at time t )
`i
`
`0
`
`0
`
`1
`
`1
`
`0
`
`1
`
`0
`
`1
`
`0
`
`1
`
`1
`
`0
`
`where t is some arbitrary time and t
` i
`
`
`
`
` i-1
`rate is equal to 1187.5 Hz.
`
` is the time one message-data clock-period earlier, and where the message-data clock-
`
`1
`
`)
`
`With this level of subcarrier, the level of each sideband of the subcarrier corresponds to half the
`nominal peak deviation level of ± 2.0 kHz for an "all-zeroes" message data stream (i.e. a
`continuous bit-rate sine-wave after biphase encoding).
`
`Jaguar Land Rover
`Exhibit 1029
`Page 008
`
`

`

`Thus, when the input-data level is 0, the output remains unchanged from the previous output bit and when an
`input 1 occurs, the new output bit is the complement of the previous output bit.
`
`In the receiver, the data may be decoded by the inverse process:
`
`Table 2: Decoding rules
`
`Page 9
`EN 50067:1998
`
`Previous input
`(at time t )
`i-1
`
`New input
`(at time t )
`i
`
`New output
`(at time t )
`i
`
`0
`
`0
`
`1
`
`1
`
`0
`
`1
`
`0
`
`1
`
`0
`
`1
`
`1
`
`0
`
`The data is thus correctly decoded whether or not the demodulated data signal is inverted.
`
`1.7 Data-channel spectrum shaping
`
`The power of the data signal at and close to the 57 kHz subcarrier is minimized by coding each source data bit as
`a biphase symbol.
`
`This is done to avoid data-modulated cross-talk in phase-locked-loop stereo decoders, and to achieve compatibility
`with the ARI system. The principle of the process of generation of the shaped biphase symbols is shown schematically in
`figure 1. In concept each source bit gives rise to an odd impulse-pair, e(t), such that a logic 1 at source gives:
`
`and a logic 0 at source gives:
`
`e(t) (t) (t td /2)
`
`e(t) (t) (cid:8) (t td /2)
`
`These impulse-pairs are then shaped by a filter H (f), to give the required band-limited spectrum where:
`T
`
`and here
`
`HT(f)
`
`%ftd
`4
`
`cos
`
`0
`
`if 0 (cid:6) f (cid:6) 2/td
`if f > 2/td
`
`td
`
`1
`1187.5
`
`s
`
`(1)
`
`(2)
`
`(3)
`
`The data-spectrum shaping filtering has been split equally between the transmitter and receiver (to give optimum
`performance in the presence of random noise) so that, ideally, the data filtering at the receiver should be identical to that
`of the transmitter, i.e. as given above in equation (3). The overall data-channel spectrum shaping H (f) would then be 100%
`o
`cosine roll-off.
`
`Jaguar Land Rover
`Exhibit 1029
`Page 009
`
`

`

`Page 10
`EN 50067:1998
`
`The specified transmitter and receiver low-pass filter responses, as defined in equation (3) are illustrated in
`figure 3, and the overall data-channel spectrum shaping is shown in figure 4.
`
`The spectrum of the transmitted biphase-coded radio-data signal is shown in figure 5 and the time-function of a
`single biphase symbol (as transmitted) in figure 6.
`
`The 57 kHz radio-data signal waveform at the output of the radio-data source equipment may be seen in the
`photograph of figure 7.
`
`480
`
`960
`
`1440
`
`1920
`2400 Hz
`Frequency
`
`1.0
`
`0.8
`
`0.6
`
`0.4
`
`0.2
`
`Relative amplitude, HO(f)
`
`0
`
`0
`
`Figure 3: Amplitude response of the specified transmitter or receiver data-shaping filter
`
`480
`
`960
`
`1440
`
`1920
`2400 Hz
`Frequency
`
`1.0
`
`0.8
`
`0.6
`
`0.4
`
`0.2
`
`Relative amplitude, HT (f)
`
`0
`
`0
`
`Figure 4: Amplitude response of the combined transmitter and receiver data-shaping filters
`
`Jaguar Land Rover
`Exhibit 1029
`Page 010
`
`

`

`Page 11
`EN 50067:1998
`
`Figure 5: Spectrum of biphase coded radio-data signals
`
`Figure 6: Time-function of a single biphase symbol
`
`Figure 7: 57 kHz radio-data signals
`
`Jaguar Land Rover
`Exhibit 1029
`Page 011
`
`

`

`Page 12
`EN 50067:1998
`
`2 Baseband coding (data-link layer)
`
`2.1 Baseband coding structure
`
`Figure 8 shows the structure of the baseband coding. The largest element in the structure is called a "group" of
`104 bits each. Each group comprises 4 blocks of 26 bits each. Each block comprises an information word and a
`checkword. Each information word comprises 16 bits. Each checkword comprises 10 bits (see 2.3).
`
`Group = 4 blocks = 104 bits
`
`Block 1
`
`Block 2
`
`Block 3
`
`Block 4
`
`Block = 26 bits
`
`Information word
`
`Checkword + offset word
`
`Information word = 16 bits
`
`Checkword = 10 bits
`
`m15 m14 m13 m12 m11 m10 m9 m8 m7 m6 m5 m4 m3 m2 m1 m0
`
` c'9 c'8 c'7 c'6 c'5 c'4 c'3 c'2 c'1 c'0
`
`Figure 8: Structure of the baseband coding
`
`2.2 Order of bit transmission
`
`All information words, checkwords, binary numbers or binary address values have their most significant bit
`(m.s.b.) transmitted first (see figure 9). Thus the last bit transmitted in a binary number or address has weight 2 .o
`
`The data transmission is fully synchronous and there are no gaps between the groups or blocks.
`
`Jaguar Land Rover
`Exhibit 1029
`Page 012
`
`

`

`Page 13
`EN 50067:1998
`
`One group = 104 bits 87.6 ms
`
`Block 1
`
`Block 2
`
`Block 3
`
`Block 4
`
`First transmitted bit of group
`
`BoTP
`
`t1
`
`PI code
`
`Checkword
`+
`offset A
`
`Group
`type
`code
`
`PTY
`
`Checkword
`+
`offset B
`
`
`Most signifiant bit
`
`Least signifiant bit
`
`Last transmitted bit of group
`
`Checkword
`+
`offset C or C'
`
`
`
`Checkword
`+
`offset D
`
`t2
`
`PI
`
`Offset C = version A
`Offset C' = version B
`
`A 3
`
`A 2
`
`A 1
`
`A 0
`
`B 0
`
`Traffic
`prog.
`code
`
`PT 4
`
`PT 3
`
`PT 2
`
`PT 1
`
`PT 0
`
`4 - bit group type code
`
`0 = version A
`1 = version B
`
`Notes to figure 9:
`
`1. Group type code = 4 bits (see 3.1)
`2. B = version code = 1 bit (see 3.1)
`o
`3. PI code = Programme Identification code = 16 bits (see 3.2.1.1 and annex D)
`4. TP = Traffic Programme Identification code = 1 bit (see 3.2.1.3)
`5. PTY = Programme Type code = 5 bits (see 3.2.1.2 and annex F)
`6. Checkword + offset "N" = 10 bits added to provide error protection and block and group synchronization
`information (see 2.3 and 2.4 and annexes A,B and C)
`t ‹ t : Block 1 of any particular group is transmitted first and block 4 last
`1 2
`
`7.
`
`Figure 9: Message format and addressing
`
`2.3 Error protection
`
`Each transmitted 26-bit block contains a 10-bit checkword which is primarily intended to enable the
`receiver/decoder to detect and correct errors which occur in transmission. This checkword (i.e. c' , c' , ... c' in figure 8)
`9
`8
`
`o
`is the sum (modulo 2) of:
`
`10
`a) the remainder after multiplication by x and then division (modulo 2) by the generator polynomial g(x), of
`the 16-bit information word,
`
`b ) a 10-bit binary string d(x), called the "offset word",
`
`where the generator polynomial, g(x) is given by:
`
`10
` 8
` 7
` 5
` 4
` 3
`g(x) = x + x + x + x + x + x + 1
`
`and where the offset values, d(x), which are different for each block within a group (see 2.4) are given in annex A.
`
`The purpose of adding the offset word is to provide a group and block synchronisation system in the
`receiver/decoder (see 2.4). Because the addition of the offset is reversible in the decoder the normal additive error-
`correcting and detecting properties of the basic code are unaffected.
`
`The checkword thus generated is transmitted m.s.b. (i.e. the coefficient of c' in the checkword) first and is
`9
`transmitted at the end of the block which it protects.
`
`Jaguar Land Rover
`Exhibit 1029
`Page 013
`
`

`

`Page 14
`EN 50067:1998
`
`The above description of the error protection may be regarded as definitive, but further explanatory notes on the
`generation and theory of the code are given in annexes B and C .
`
`The error-protecting code has the following error-checking capabilities [3, 4] :
`
`a) Detects all single and double bit errors in a block.
`b) Detects any single error burst spanning 10 bits or less.
`c) Detects about 99.8% of bursts spanning 11 bits and about 99.9% of all longer bursts.
`
`The code is also an optimal burst error correcting code [5] and is capable of correcting any single burst of span
`5 bits or less.
`
`2.4 Synchronisation of blocks and groups
`
`The blocks within each group are identified by the offset words A, B, C or C' and D added to blocks 1, 2, 3, and
`4 respectively in each group (see annex A).
`
`The beginnings and ends of the data blocks may be recognized in the receiver decoder by using the fact that the
`error-checking decoder will, with a high level of confidence, detect block synchronisation slip as well as additive errors.
`This system of block synchronisation is made reliable by the addition of the offset words (which also serve to identify the
`blocks within the group). These offset words destroy the cyclic property of the basic code so that in the modified code,
`cyclic shifts of codewords do not give rise to other codewords [6, 7].
`
`Further explanation of a technique for extracting the block synchronisation information at the receiver is given
`in annex C.
`
`Jaguar Land Rover
`Exhibit 1029
`Page 014
`
`

`

`Page 15
`EN 50067:1998
`
`3 Message format (session and presentation layers)
`
`3.1 Addressing
`
`3.1.1 Design principles
`
`The basic design principles underlying the message format and addressing structure are as follows:
`
`a) The messages which are to be repeated most frequently, and for which a short acquisition time is required e.g.
`Programme Identification (PI) codes, in general occupy the same fixed positions within every group. They
`can therefore be decoded without reference to any block outside the one which contains the information.
`
`b) There is no fixed rhythm of repetition of the various types of group, i.e. there is ample flexibility to interleave
`the various kinds of message to suit the needs of the users at any given time and to allow for future
`developments.
`
`c) This requires addressing to identify the information content of those blocks which are not dedicated to the
`high-repetition-rate information.
`
`d) Each group is, so far as possible, fully addressed to identify the information content of the various blocks.
`
`e) The mixture of different kinds of message within any one group is minimized, e.g. one group type is reserved
`for basic tuning information, another for RadioText, etc. This is important so that broadcasters who do not
`wish to transmit messages of certain kinds are not forced to waste channel capacity by transmitting groups
`with unused blocks. Instead, they are able to repeat more frequently those group types which contain the
`messages they want to transmit.
`
`f) To allow for future applications the data formatting has been made flexible. For example, a number of group
`types (see table 6) may be used for Open Data Applications (see 3.1.4 and 4.9).
`
`3.1.2 Principal features
`
`The main features of the message structure have been illustrated in figure 9. These may be seen to be:
`
`1) The first block in every group always contains a Programme Identification (PI) code.
`
`2) The first four bits of the second block of every group are allocated to a four-bit code which specifies the
`application of the group. Groups will be referred to as types 0 to 15 according to the binary weighting A = 3
`8, A = 4, A = 2, A = 1 (see figure 9). For each type (0 to 15) two "versions" can be defined. The
` 2
`
`
` 1
`
`
` 0
`"version" is specified by the fifth bit (B ) of block 2 as follows:
`o
`
`a) B = 0: the PI code is inserted in block 1 only. This will be called version A, e.g. 0A, 1A, etc.
`0
`
`b) B = 1: the PI code is inserted in block 1 and block 3 of all group types. This will be called version B,
`0
`e.g. 0B, 1B, etc.
`
`Jaguar Land Rover
`Exhibit 1029
`Page 015
`
`

`

`Page 16
`EN 50067:1998
`
`In general, any mixture of type A and B groups may be transmitted.
`
`3) The Programme Type code (PTY) and Traffic Programme identification (TP) occupy fixed locations in block
`2 of every group.
`
`The PI, PTY and TP codes can be decoded without reference to any block outside the one that contains the
`information. This is essential to minimize acquisition time for these kinds of message and to retain the advantages of the
`short (26-bit) block length. To permit this to be done for the PI codes in block 3 of version B groups, a special offset word
`(which we shall call C') is used in block 3 of version B groups. The occurrence of offset C' in block 3 of any group can
`then be used to indicate directly that block 3 is a PI code, without any reference to the value of B in block 2.
`0
`
`Jaguar Land Rover
`Exhibit 1029
`Page 016
`
`

`

`3.1.3 Group types
`
`It was described above (see also figure 9) that the first five bits of the second block of every group are allocated
`to a five-bit code which specifies the application of the group and its version, as shown in table 3.
`
`Page 17
`EN 50067:1998
`
`Table 3: Group types
`
`Group
`type
`
`Group type code/version
`
`A
`
`3
`
`A
`
`2
`
`A
`
`1
`
`A
`
`0
`
`B
`
`0
`
`Flagged in
`type 1A
`groups
`
`Description
`
`0 A
`
`0 B
`
`1A
`
`1B
`
`2 A
`
`2 B
`
`0
`
`0
`
`0
`
`0
`
`0
`
`0
`
`0
`
`0
`
`0
`
`0
`
`0
`
`0
`
`0
`
`0
`
`0
`
`0
`
`1
`
`1
`
`0
`
`0
`
`1
`
`1
`
`0
`
`0
`
`0
`
`1
`
`0
`
`1
`
`0
`
`1
`
`0
`
`Basic tuning an