IEC 62106:2000

INTERNATIONAL IEC
STANDARD
First edition
2000-01
Specification of the radio data system (RDS)
for VHF/FM sound broadcasting
in the frequency range
from 87,5 to 108,0 MHz
Reference number
Numbering
As from 1 January 1997 all IEC publications are issued with a designation in the
60000 series.
Consolidated publications
Consolidated versions of some IEC publications including amendments are

available. For example, edition numbers 1.0, 1.1 and 1.2 refer, respectively, to the
base publication, the base publication incorporating amendment 1 and the base

publication incorporating amendments 1 and 2.

Validity of this publication
The technical content of IEC publications is kept under constant review by the IEC,
thus ensuring that the content reflects current technology.
Information relating to the date of the reconfirmation of the publication is available
in the IEC catalogue.
Information on the subjects under consideration and work in progress undertaken
by the technical committee which has prepared this publication, as well as the list
of publications issued, is to be found at the following IEC sources:
• IEC web site*
• Catalogue of IEC publications
Published yearly with regular updates
(On-line catalogue)*
• IEC Bulletin
Available both at the IEC web site* and as a printed periodical
Terminology, graphical and letter symbols
For general terminology, readers are referred to IEC 60050: International
Electrotechnical Vocabulary (IEV).
For graphical symbols, and letter symbols and signs approved by the IEC for
general use, readers are referred to publications IEC 60027: Letter symbols to be
used in electrical technology, IEC 60417: Graphical symbols for use on equipment.
Index, survey and compilation of the single sheets and IEC 60617: Graphical symbols
for diagrams.
* See web site address on title page.

INTERNATIONAL IEC
STANDARD
First edition
2000-01
Specification of the radio data system (RDS)
for VHF/FM sound broadcasting
in the frequency range
from 87,5 to 108,0 MHz
 IEC 2000  Copyright - all rights reserved
No part of this publication may be reproduced or utilized in any form or by any means, electronic or
mechanical, including photocopying and microfilm, without permission in writing from the publisher.
International Electrotechnical Commission 3, rue de Varembé Geneva, Switzerland
Telefax: +41 22 919 0300 e-mail: inmail@iec.ch IEC web site http://www.iec.ch
Commission Electrotechnique Internationale
PRICE CODE
XF
International Electrotechnical Commission
For price, see current catalogue

62106 © IEC:2000 - 2 -
INTERNATIONAL ELECTROTECHNICAL COMMISSION

SPECIFICATION OF THE RADIO DATA SYSTEM (RDS) FOR VHF/FM SOUND

BROADCASTING IN THE FREQUENCY RANGE FROM 87,5 TO 108,0 MHZ

FOREWORD
1) The IEC (International Electrotechnical Commission) is a worldwide organization for standardization comprising all national electrotechnical
committees (IEC National Committees). The object of the IEC is to promote international co-operation on all questions concerning standardization
in the electrical and electronic fields. To this end and in addition to other activities, the IEC publishes International Standards. Their preparation
is entrusted to technical committees; any IEC National Committee interested in the subject dealt with may participate in this preparatory work.
International, governmental and non-governmental organizations liaising with the IEC also participate in this preparation. The IEC collaborates
closely with the International Organization for Standardization (ISO) in accordance with conditions determined by agreement between the two
organizations.
2) The formal decisions or agreements of the IEC on technical matters express, as nearly as possible, an international consensus of opinion on the
relevant subjects since each technical committee has representation from all interested National Committees.
3) The documents produced have the form of recommendations for international use and are published in the form of standards, technical
specifications, technical reports or guides and they are accepted by the National Committees in that sense.
4) In order to promote international unification, IEC National Committees undertake to apply IEC International Standards transparently to the
maximum extent possible in their national and regional standards. Any divergence between the IEC Standard and the corresponding national or
regional standard shall be clearly indicated in the latter.
5) The IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any equipment declared to be in conformity
with one of its standards.
This International Standard IEC 62106 has been prepared by the IEC Subcommittee 100A: Multimedia end-user equipment,
of the Technical Committee 100: Audio, video and multimedia systems and equipment.
This standard is based on the European CENELEC Standard EN 50067:1998 prepared by the RDS Forum, using an earlier
specification [8] that was originally developed within the European Broadcasting Union. It was submitted to the National
Committees for voting under the Fast Track Procedure as the following documents:
FDIS Report on voting
100A/134A/FDIS 100A/139/RVD
Full information on the voting for the approval of this standard can be found in the report indicated in the above table.
Attention is drawn to the fact that there may be Intellectual Property Rights (IPR) in relation to certain provisions of this

standard. IPR holders should notify the IEC of their claims.
This publication has not been drafted in complete accordance with the ISO/IEC Directives, Part 3.
Annexes B, C, G, H, K, L and Q are for information only.
Annexes A, D, E, F, J, M, N, and P form an integral part of this standard.

- 3 - 62106 © IEC:2000
CONTENTS
page
0 S cope . 6

1 Modulation characteristics of the data channel (physical layer) . 6

1.1 Subcarrier frequency . 6

1.2 Subcarrier phase . 6

1.3 Subcarrier level . 8

1.4 Method of modulation . 8

1.5 Clock-frequency and data-rate . 8
1.6 Differential coding . 8
1.7 Data-channel spectrum shaping . 9
2 Baseband coding (data-link layer) . 12
2.1 Baseband coding structure . 12
2.2 Order of bit transmission . 12
2.3 Error protection . 13
2.4 Synchronization of blocks and groups . 14
3 Message format (session and presentation layers) . 15
3.1 Addressing . 15
3.1.1 Design principles . 15
3.1.2 Principal features . 15
3.1.3 Group types . 17
3.1.4 Open data channel / Applications Identification . 19
3.1.4.1 Use of Open data applications . 19
3.1.4.2 Open data applications - Group structure . 20
3.1.5 Coding of the Group types . 21
3.1.5.1  Type 0 groups: Basic tuning and switching information . 21
3.1.5.2  Type 1 groups: Programme-item number and slow labelling codes . 23
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
(Group type 10B)  . 34
3.1.5.15 Type 11 groups: Open data application . 35
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

62106 © IEC:2000 - 4 -
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 D es cription of f eatures . 54
5 M arking . 57

- 5 - 62106 © IEC:2000
ANNEXES
page
Annex A (normative) - Offset words to be used for group and block synchronization . 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

Anne x 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

62106 © IEC:2000 - 6 -
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 therefore has to 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 (Autofahrer-Rundfunk-Information) 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(.

- 7 - 62106 © IEC:2000
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
amplitude/frequency characteristic of filter F is, therefore, not the same as that given in figure 3.
Figure 2 - Block diagram of a typical radio-data receiver/decoder

62106 © IEC:2000 - 8 -
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
recommended best compromise is ± 2.0 kHz ). The decoder/demodulator shall 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
m aximum deviation due to the radio-data subcarrier is ± 1.2 kHz and that due to the unmodulated ARI subcarrier shall 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 New input New output
(at time t ) (at time t ) (at time t )
i-1 i i
0 0 0
0 1 1
1 0 1
1 1 0
where t is some arbitrary time and t is the time one message-data clock-period earlier, and where the message-data clock-
i i-1
rate is equal to 1187.5 Hz.
) 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).

- 9 - 62106 © IEC:2000
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
Previous input New input New output

(at time t ) (at time t ) (at time t )
i-1 i i
0 0 0
0 1 1
1 0 1
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:
e(t)�/(t)�/(t�t /2)
(1)
d
and a logic 0 at source gives:
e(t)�� /(t)�/(t� t /2)
(2)
d
These impulse-pairs are then shaped by a filter H (f), to give the required band-limited spectrum where:
T
�ft
d
cos if 0� f� 2/t
d
(3)
H (f) �
T
0 if f > 2/t
d
and here
s
t �
d
1187.5
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.
62106 © IEC:2000 - 10 -
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 s ingle 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.
1.0
0.8
0.6
0.4
0.2
0 480 960 1440 1920 2400 Hz
Frequency
Figure 3 - Amplitude response of the specified transmitter or receiver data-shaping filter
1.0
0.8
0.6
0.4
0.2
0 480 960 1440 1920 2400 Hz
Frequency
Figure 4 - Amplitude response of the combined transmitter and receiver data-shaping filters
H
H ,
,
Relative amplitude (f)
O
Relative amplitude (f)
T
- 11 - 62106 © IEC:2000
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

62106 © IEC:2000 - 12 -
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
chec kword. 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
m m m m m m m m m m m m m m m m c' c' c' c' c' c' c' c' c' c'
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 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
o
(m.s.b.) transmitted first (see figure 9). Thus the last bit transmitted in a binary number or address has weight 2 .
The data transmission is fully synchronous and there are no gaps between the groups or blocks.

- 13 - 62106 © IEC:2000
One group = 104 bits   87.6 ms

Block 1 Block 2 Block 3 Block 4

First transmitted bit of group B TP Last transmitted bit of group
o
t t
1 2
Checkword Checkword Checkword Checkword
Group
+ + + +
PI code type PTY     PI
offset A offset B offset C or C' offset D
code
Offset C = version A
Offset C' = version B
Least signifiant bit
Most signifiant bit
Traffic
A A A A B prog. PT PT PT PT PT
3 2 1 0 0 4 3 2 1 0
code
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)
7. t ‹ t : Block 1 of any particular group is transmitted first and block 4 last
1 2
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:
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
transmitted at the end of the block which it protects.

62106 © IEC:2000 - 14 -
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.
- 15 - 62106 © IEC:2000
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 =
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.
b) B = 1: the PI code is inserted in block 1 and block 3 of all group types. This will be called version B,
e.g. 0B, 1B, etc.
62106 © IEC:2000 - 16 -
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.
- 17 - 62106 © IEC:2000
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.

Table 3 - Group types
Group type code/version Flagged in

Group
type 1A Description
type
A A A A B
3 2 1 0 0 groups
0 A 00000 Basic tuning and switching information only (see 3.1.5.1)

0 B 00001 Basic tuning and switching information only (see 3.1.5.1)

1A 00010 Programme Item Number and slow labelling codes only (see
3.1.5.2)
1B 00011 Programme Item Number (see 3.1.5.2)
2 A 00100 RadioText only (see 3.1.5.3)
2 B 00101 RadioText only (see 3.1.5.3)
3 A 00110 Applications Identification for ODA only (see 3.1.5.5)
3 B 00111 Open Data Applications
4 A 01000 Clock-time and date only (see 3.1.5.6)
4 B 01001 Open Data Applications
5 A 01010 Transparent Data Channels (32 channels) or ODA (see 3.1.5.8)
5 B 01011 Transparent Data Channels (32 channels) or ODA (see 3.1.5.8)
6 A 01100 In House applications or ODA (see 3.1.5.9)
6 B 01101 In House applications or ODA (see 3.1.5.9)
7 A 01110 Y Radio Paging or ODA (see 3.1.5.10 and annex M)
7 B 01111 Open Data Applications
8 A 10000 Y Traffic Message Channel or ODA (see 3.1.5.12)
8 B 10001 Open Data Applications
9 A 10010 Y Emergency Warning System or ODA (see 3.1.5.13)
9 B 10011 Open Data Applications
10 A 10100 Programme Type Name
10 B 10101 Open Data Applications
11 A 10110 Open Data Applications

11 B 10111 Open Data Applications
12 A 11000 Open Data Applications
12 B 11001 Open Data Applications
13 A 11010 Y Enhanced Radio Paging or ODA (see annex M)
13 B 11011 Open Data Applications
14 A 11100 Enhanced Other Networks information only (see 3.1.5.19)
14 B 11101 Enhanced Other Networks information only (see 3.1.5.19)
15 A 11110 Defined in RBDS [15] only
15 B 11111 Fast switching information only (see 3.1.5.20)
Note: Mark “Y” indicates that group type 1A will be transmitted for the identification of the application, using block 3 of group type 1A (see Figure 14).

62106 © IEC:2000 - 18 -
The appropriate repetition rates for some of the main features are indicated in table 4:

Table 4 - Main feature repetition rates

Main Features Group types Appropriate

which contain repetition
rate per sec.
this information
Programme Identification (PI) code all 11.4 )
Programme Type (PTY) code all 11.4 )
Traffic Programme (TP) identification code all 11.4 )

Programme Service (PS) name ) 0A, 0B 1

Alternative frequency (AF) code pairs 0A 4
Traffic announcement (TA) code 0A, 0B, 14B,15B 4
Decoder identification (DI) code 0A, 0B, 15B 1
Music Speech (MS) code 0A, 0B, 15B 4
RadioText (RT) message 2A, 2B 0.2 )
Enhanced other networks information (EON) 14A up to 2 )
) Valid codes for this item will normally be transmitted with at least this repetition rate whenever the transmitter carries a
normal broadcast programme.
) A total of 16 type 2A groups are required to transmit a 64 character RadioText message and therefore, to transmit this
message in 5 s, 3.2 type 2A groups will be required per second.
) The maximum cycle time for the transmission of all data relating to all cross-referenced programme services shall be less
than 2 min.
) PS shall only be used for identifying the programme service and it must not be used for other messages giving sequential
information.
A total of four type 0A groups are required to transmit the entire PS name and therefore four type 0A groups will
be required per second. The repetition rate of the type 0A group may be reduced if more capacity is needed for other
applications. But a minimum of two type 0A groups per second is necessary to ensure correct functioning of PS and AF
features. However, with EON receivers search tuning is affected by the repetition rate of type 0 groups (TP/TA, see
3.2.1.3). It shall be noted that in this case transmission of the complete PS will take 2 s. However, under typical reception
conditions the introduction of errors will cause the receiver to take 4 s or more to acquire the PS name for display.
The following mixture of groups is suitable to meet the repetition rates noted above.
Table 5 - Group repetition rates
Typical proportion
Group types Features of groups of this
type transmitted
0A or 0B PI, PS, PTY, TP, AF ), TA, DI, MS 40%

1A or 1B PI, PTY, TP, PIN 10%
2A or 2B PI, PTY, TP, RT 15% )
14A or 14B PI, PTY, TP, EON 10%
Any other Other applications 25%
) Type 0A group only
) Assuming that type 2A groups are used to transmit a 32-character RadioText message. A mixture of type 2A
and 2B groups in any given message shall be avoided (see 3.1.5.3)

- 19 - 62106 © IEC:2000
3.1.4 Open data channel / Applications Identification

3.1.4.1 Use of Open Data Applications

Open Data Applications (ODA) are not explicitly specified in this standard. They are subject to a registration
proces s and registered applications are listed in the EBU/RDS Forum - ODA Directory (see annex L), which references
appropriate standards and normative specifications. These specifications may however be public (specification in the public

domain) or private (specification not in the public domain). The terms public and private do not imply the degree of access

to services provided by an application, for example a public service may include encryption.

An ODA may use type A and/or type B groups, however it must not be designed to operate with a specific group

type. The specific group type used by the ODA in any particular transmission is signalled in the Applications Identification

(AID) carried in type 3A groups (see 3.1.5.4). Table 6 shows the type A and type B groups that may be allocated to ODA.
Group types not shown in table 6 are not available for ODA.
Table 6 - ODA group availability signalled in type 3A groups
Group Application Availability for Open Data Applications
type group type
code
00000 Special meaning: Not carried in associated group
3B 00111 Available unconditionally
4B 01001 Available unconditionally
5A 01010 Available when not used for TDC
5B 01011 Available when not used for TDC
6A 01100 Available when not used for IH
6B 01101 Available when not used for IH
7A 01110 Available when not used for RP
7B 01111 Available unconditionally
8A 10000 Available when not used for TMC
8B 10001 Available unconditionally
9A 10010 Available when not used for EWS
9B 10011 Available unconditionally
10B 10101 Available unconditionally
11A 10110 Available unconditionally

11B 10111 Available unconditionally
12A 11000 Available unconditionally
12B 11001 Available unconditionally
13A 11010 Available when not used for RP
13B 11011 Available unconditionally
11111 Special meaning: Temporary data fault (Encoder status)

62106 © IEC:2000 - 20 -
3.1.4.2 Open Data Applications - Group structure

Open Data Applications shall use the format shown in figure 10 for ODA type A groups and in figure 11 for

ODA type B groups.
B TP
o
Checkword Checkword Checkword Checkword
Group
+ type + + +
PI code PTY
offset A code offset B offset C offset D

Format and application of these message
bits may be assigned unilaterally by each operator
X 0
X X X
in conformity with section 3.1.4
Figure 10 - ODA type A groups
Format and application of these message
bits may be assigned unilaterally by each operator
in conformity with section 3.1.4
B TP
o
Checkword Checkword Checkword Checkword
Group
+ type + + +
PI code PTY
PI code
offset A code offset B offset C' offset D

X X X X 1
Figure 11- ODA type B groups
- 21 - 62106 © IEC:2000
3.1.5 Coding of the Group types

3.1.5.1 Type 0 groups: Basic tuning and switching information

The repetition rates of type 0 groups must be chosen in compliance with 3.1.3.

Figure 12 shows the format of type 0A groups and figure 13 the format of type 0B groups.

M/S
B TP TA DI segment
o
Checkword Checkword Checkword Checkword
Group
Alternative Alternative
Programme service
+ type + + +
PI code PTY
frequency frequency name segment
offset C
offset A code offset B offset D

a a a a a a a a b b b b b b b b b b b b b b b b
0 0 0 0 0 DI C C
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
1 0 7 6 5 4 3 2 1 0
d 0 0 2
Decoder
d 0 1 3 4
control
d 1 0 5 6
bits 1
d 1 1 7 8
Prog. service name and DI
Character numbers
segment address
Figure 12 - Basic tuning and switching information - Type 0A group
M/S
B TP TA DI segment
o
Checkword Group Checkword Checkword Checkword
Programme service
+ + + +
type
PI code PTY PI code
name segment
offset A code offset B offset C' offset D

0 0 0 0 1 DI C C b b b b b b b b b b b b b b b b
1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
d 0 0 1 2
Decoder
d 0 1 4
control
d 1 0 5 6
bits
d 1 1 7 8
Prog. service name and DI
Character numbers
segment address
Figure 13 - Basic tuning and switching information - Type 0B group
Type 0A groups are usually transmitted whenever alternative frequencies exist. Type 0B groups without any type
0A groups may be transmitted only when no alternative frequencies exist.
There are two methods (A and B) for transmission of alternative frequencies (see 3.2.1.6.2).
The Programme Service name comprises eight characters, intended for static display on a receiver. It is the
primary aid to listeners in programme service identification and selection. The use of PS to transmit text other than a singl e
eight character name is not permitted (see also 3.2.2). Transmission of a PS name usually takes four type 0A groups, but
to allow an instant display of the PS when a receiver pre-set is selected, the PS name is often stored for subsequent recall
from memory when a programme service is selected. For this reason PS shall generally be invariant.

62106 © IEC:2000 - 22 -
If a broadcaster wishes to transmit longer Programme Service names, programme-related information or any

other text, then RadioText provides this feature.

Notes on Type 0 groups:
1. Version B differs from version A only in the contents of block 3, the offset word in block 3,
and, of course, the version code B

2. For details of Programme Identification (PI), Programme Type (PTY) and Traffic

Programme (TP) code, see figure 9, 3.2.1 and annexes D and F.

3. TA = Traffic announcement code (1 bit) (see 3.2.1.3).

4. MS = Music Speech switch code (1 bit) (see 3.2.1.4).

5. DI= Decoder-identification control code (4 bits) (see 3.2.1.5). This code is transmitted as 1 bit in each

type 0 group. The Programme Service name and DI segment address code (C and C ) serves to locate
1 0
these bits in the DI codeword. Thus in a group with C C = "00" the DI bit in that group is d . These
1 0 3
code bits are transmitted most significant bit (d ) first.
6. Alternative frequency codes (2 x 8 bits) (see 3.2.1.6).
7. Programme Service name (for display) is transmitted as 8-bit characters as defined in the 8-bit code-
tables in annex E. Eight characters (including spaces) are allowed for each network and are
transmitted as a 2-character segment in each type 0 group. These segments are located in the displayed
name by the code bits C and C in block 2. The addresses of the characters increase from left to right
1 o
in the display. The most significant bit (b ) of each character is transmitted first.
- 23 - 62106 © IEC:2000
3.1.5.2 Type 1 groups: Programme Item Number and slow labelling codes

Figure 14 shows the format of type 1A groups and figure 15 the format of type 1B groups.

When a Programme Item Number is changed, a type 1 group shall be repeated four times with a separation of
about 0.5 s. The unused bits in block 2 (type 1B only) are reserved for future applications.

Where Radio Paging is implemented in RDS, a type 1A group will be transmitted in an invariable sequence,

regularly once per second, except at each full minute, where it is replaced by one type 4A group.

B TP
o
Checkword Checkword Checkword Checkword
Group
Slow labelling
Programme item
+ type + + +
PI code PTY
codes number code
offset A code offset B offset C offset D

5 bits
Radio Paging Codes
4 3 2 1 0 4 3 2 1 0 5 4 3 2 1 0
(see Annex M)
0 0 0 1 0
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
day hour minute
b b b b b b b b b b b b b b b b
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0  2 1  0  11 10 9 8  7  6  5 4  3  2  1  0
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

2) 3)
(0) LA 0 0 0 Paging Extended Country Code

4)
(1) 0 0 1 TMC identification
LA
.
5)
(2) 1 0 Paging identification
LA 0
.
.
6)
(3) Language codes
LA 0 1 1
not assigned
(4)
LA 1 0 0
not assigned
(5) LA 1 0 1
7)
For use by broadcasters
(6) LA 1 1 0
8)
Identification of EWS channel
(7) 1 1
LA 1
Variant Code
1)
Linkage Actuator
) The Linkage Actuator is defined in the "Method for Linking RDS Programme Services" (see 3.2.1.8.3).
) Normally set to zero except when used for the Operator Code in Radio Paging with the Enhanced Paging Protocol, defined in annex M
(see M.3.2.2 and M.3.2.4).
) Extended country codes are defined separately (see annex D).
) TMC system information is separately specified by the CEN standard ENV 12313-1 (see 3.1.5.12). This identification is not required if
ODA is used for coding TMC.
)  The Paging Identification is defined in the "Multi Operator / Area paging" section (see annex M).
) Language codes are defined separately (see annex J)
) The coding of this information may be decided unilaterally by the broadcaster to suit the application. RDS consumer receivers shall
entirely ignore this information.
) The Emergency Warning Systems (EWS) are defined separately (see 3.2.7).
Figure 14 - Programme Item Number and slow labelling codes - Type 1A group

62106 © IEC:2000 - 24 -
B TP
o
Checkword Checkwo
...