IEC 62106-6:2018 contains the technical specifications for Open Data Applications in the public domain. This document is maintained by the RDS Forum Office. The RDS Forum Office applies an easy procedure for registering new Open Data Applications, to ensure that they can be used without the need to change the RDS standard. The ODA feature permits defining new applications that can be decoded on a receiver. The receiver needs to the adequate software handler for the specific AID, which identifies the application. Receivers that have not implemented the software handler needed for decoding are not affected by ODA data received for any of the applications already defined and specified. The procedure for registering a new ODA is described in IEC 62106-3. IEC 62106-6:2018 together with IEC 62106-1, IEC 62106-2, IEC 62106-3, IEC 62106-4 and IEC 62106-5, cancels and replaces IEC 62106:2015, and constitutes a technical revision. This edition includes the following significant technical changes with respect to IEC 62106:2015: \u2022 Provision has been made to carry RDS on multiple data-streams (RDS2); \u2022 New are AF coding below 87,5 MHz (down to 64,0 MHz) using ODA-AID 0x6365; \u2022 RT+ can now be used simultaneously for RT and eRT, each having its own RT+ ODA; \u2022 Data-streams 1, 2 and 3 are exclusively UTF-8 coded. For backwards compatibility, UCS-2 encoded eRT on data-stream 0 is retained.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 4<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
| 6<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | 1 Scope 2 Normative references 3 Terms, definitions, abbreviated terms and conventions 3.1 Terms and definitions 3.2 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | 3.3 Notation and conventions 4 ODAs in the public domain 4.1 ODAs in the 37-bit ODA application group structure 4.1.1 Traffic Message Channel (TMC) 4.1.2 Other public ODAs 4.2 ODAs in the group type C structure for the upper data-streams 1, 2 and 3 <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | Annex A (normative)Coding of RadioText Plus (RT+) tagging informationfor RadioText in group type 2A\/B A.1 General A.2 Terms used Tables Table A.1 \u2013 RT+ information elements for RT <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | A.3 RT+ tag <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | A.4 RT+ information elements and data model A.4.1 General A.4.2 List of RT content types <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | A.4.3 Structures of RT+ messages <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | A.4.4 Receiver data model <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | Figures Figure A.1 \u2013 Example 1: RT+ information of the category ‘Item’ (see Table A.2) will be attached to the programme elements Item 1 and Item 2 Figure A.2 \u2013 Example 2: RT+ information of the category ‘Item’ will be attached to the programme elements Item 1 and Item 2, but not to the programme element News Figure A.3 \u2013 Example 3: RT+ information of the category ‘Item’ will be attached only to the programme element Item 1, but not to the programme element Talk <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | A.5 RT+ coding for RT A.5.1 General A.5.2 RT+ identification (group type 3A) Figure A.4 \u2013 Bit allocation for group 3A (message bits and AID) <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | A.5.3 Coding of the RT+ tag Figure A.5 \u2013 Coding of the message bits of the application group <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | A.5.4 Clearing of RT+ messages <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | Table A.2 \u2013 Code list and ‘RT+ class’ description of RT content types (1 of 3) <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | A.6 Broadcasting conventions A.7 Receiving conventions A.8 Marking <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | Annex B (normative)Coding of RadioText Plus(RT+) tagging information for RadioTextin the eRT ODA of Annex C Table B.1 \u2013 RT+ information elements for eRT <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | Annex C (normative)Coding of enhanced RadioText (eRT) C.1 General C.2 Coding eRT in ODA groups C.2.1 General C.2.2 eRT identification (Group type 3A) and coding of the text string Table C.1 \u2013 eRT information elements <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | C.2.3 Coding of the eRT text string Figure C.1 \u2013 Bit allocation for group 3A (message bits and AID) <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | C.2.4 UTF-8 decoding problems when used with RT+ Figure C.2 \u2013 Coding of the message bits of the application group type A <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | C.3 Broadcasting conventions C.4 Receiving conventions C.5 Marking <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | Annex D (normative)Coding of AF lists in the frequency range 64,1 MHz to 107,9 MHz: ODA-AF D.1 Objective to be achieved D.2 Description of the coding process D.2.1 ODA-AF identification (group type 3A) Figure D.1 \u2013 New ODA-AF \u2013 group type 3A <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | D.2.2 AF coding in the application group Figure D.2 \u2013 New ODA-AF application group \u2013 group type A Table D.1 \u2013 9-bit AF code table for VHF Band I (64,0 MHz to 88,0 MHz) Table D.2 \u2013 9-bit AF code table for VHF Band II (87,5 MHz to 108 MHz) <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | Table D.3 \u2013 9-bit special meanings code table Table D.4 \u2013 LF\/MF code table \u2013 ITU regions 1 and 3 (9 kHz spacing) Table D.5 \u2013 MF code table \u2013 ITU region 2 (10 kHz spacing) <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | D.2.3 AF method A D.2.4 AF method B <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | D.2.5 Convention for identification of the AF method used <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Radio data system (RDS). VHF\/FM sound broadcasting in the frequency range from 64,0 MHz to 108,0 MHz – Compilation of technical specifications for Open Data Applications in the public domain<\/b><\/p>\n |