| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 58<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 60<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
| 63<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
| 65<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
| 66<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
| 67<\/td>\n | 3 Terms, definitions, abbreviated terms and conventions 3.1 Terms and definitions 3.2 Abbreviated terms 3.3 Notation and conventions 4 ODAs in the public domain 4.1 ODAs in the group type A 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 5 Protocol to stream RDS on bearers different from FM (NFM) <\/td>\n<\/tr>\n | ||||||
| 68<\/td>\n | Annexes Annex A (normative) Coding of RadioText Plus (RT+) tagging information for 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 | ||||||
| 69<\/td>\n | A.3 RT+ tag <\/td>\n<\/tr>\n | ||||||
| 70<\/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 | ||||||
| 71<\/td>\n | A.4.3 Structures of RT+ messages <\/td>\n<\/tr>\n | ||||||
| 72<\/td>\n | A.4.4 Receiver data model <\/td>\n<\/tr>\n | ||||||
| 73<\/td>\n | A.5 RT+ coding for RT A.5.1 General 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 | ||||||
| 74<\/td>\n | 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 | ||||||
| 75<\/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 | ||||||
| 76<\/td>\n | A.5.4 Clearing of RT+ messages <\/td>\n<\/tr>\n | ||||||
| 77<\/td>\n | Table A.2 \u2013 Code list and ‘RT+ class’ description of RT content types <\/td>\n<\/tr>\n | ||||||
| 80<\/td>\n | A.6 Broadcasting conventions A.7 Receiving conventions A.8 Marking <\/td>\n<\/tr>\n | ||||||
| 81<\/td>\n | Annex B (normative) Coding of RadioText Plus(RT+) tagging information for RadioText in the eRT ODA of Annex C Table B.1 \u2013 RT+ information elements for eRT <\/td>\n<\/tr>\n | ||||||
| 82<\/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 Figure C.1 \u2013 Bit allocation for group 3A (message bits and AID) Table C.1 \u2013 eRT information elements <\/td>\n<\/tr>\n | ||||||
| 83<\/td>\n | C.2.3 Coding of the eRT text string Figure C.2 \u2013 Coding of the message bits of the application group type A <\/td>\n<\/tr>\n | ||||||
| 84<\/td>\n | C.2.4 UTF-8 decoding problems when used with RT+ C.3 Broadcasting conventions C.4 Receiving conventions C.5 Marking <\/td>\n<\/tr>\n | ||||||
| 85<\/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 | ||||||
| 86<\/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 | ||||||
| 87<\/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 | ||||||
| 88<\/td>\n | D.2.3 AF method A D.2.4 AF method B <\/td>\n<\/tr>\n | ||||||
| 90<\/td>\n | D.2.5 Convention for identification of the AF method used <\/td>\n<\/tr>\n | ||||||
| 91<\/td>\n | Annex E (normative) Station logo transmission coded in group type C E.1 Objective to be achieved E.2 Application identification code of this ODA E.3 Station logo requirements E.3.1 File type E.3.2 Logo resolution, file ID, file version and file size Table E.1 \u2013 File ID station logo options <\/td>\n<\/tr>\n | ||||||
| 92<\/td>\n | E.3.3 File transport E.3.4 Display mode E.3.5 Link of the logo with the PI code <\/td>\n<\/tr>\n | ||||||
| 93<\/td>\n | Annex F (normative) ODA app \u2013 Slideshow transmission coded in C-group type F.1 Objectives to be achieved F.2 Application identification code of this ODA F.3 Image requirements F.3.1 File type F.3.2 Resolution and file size <\/td>\n<\/tr>\n | ||||||
| 94<\/td>\n | F.4 Text character coding F.5 Slide structure and file elements used Figure F.1 \u2013 Components used in the slideshow <\/td>\n<\/tr>\n | ||||||
| 95<\/td>\n | Figure F.2 \u2013 Structure of the [PREVIEW] text file Figure F.3 \u2013 Structure of the [URLS] text file Table F.1 \u2013 Start position of each file element within [PREVIEW] <\/td>\n<\/tr>\n | ||||||
| 96<\/td>\n | F.6 Slide carousel used by the broadcaster, file updating and file transmission F.7 File transport F.7.1 General F.7.2 Identification of the files Table F.2 \u2013 Start position of each file element within [URL] <\/td>\n<\/tr>\n | ||||||
| 97<\/td>\n | F.8 Directory trigger group F.8.1 Function F.8.2 Specification Figure F.4 \u2013 Directory trigger group Table F.3 \u2013 File numbering system used <\/td>\n<\/tr>\n | ||||||
| 98<\/td>\n | F.9 Receiver display mode options Table F.4 \u2013 Parameters used in the directory trigger group <\/td>\n<\/tr>\n | ||||||
| 99<\/td>\n | Annex G (normative) Internet connection options coded in C-group type G.1 Objective to be achieved G.2 Application identification code of this ODA G.3 Choice of the ODA channel number G.4 Coding of IP address with port number G.4.1 General G.4.2 IPv4 coding <\/td>\n<\/tr>\n | ||||||
| 100<\/td>\n | G.4.3 IPv6 coding Figure G.1 \u2013 Coding of IPv4 address with port number Table G.1 \u2013 Address type code Table G.2 \u2013 Link ID code of IP connection <\/td>\n<\/tr>\n | ||||||
| 101<\/td>\n | G.4.4 IP address and port number coded as URL text Figure G.2 \u2013 URL text coding to connect to an application data server <\/td>\n<\/tr>\n | ||||||
| 102<\/td>\n | Annex H (normative) ODA tool \u2013 RDS data mode NFM H.1 Objective to be achieved H.2 Specification of the NFM protocol Figure H.1 \u2013 NFM message format <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Tracked Changes. 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 |