🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS IEC 62106-6:2023 – TC

BS IEC 62106-6:2023 – TC

$246.62

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

Published By Publication Date Number of Pages
BSI 2023 104
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

PDF Catalog

PDF Pages PDF Title
58 undefined
60 CONTENTS
63 FOREWORD
65 INTRODUCTION
66 1 Scope
2 Normative references
67 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)
68 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 – RT+ information elements for RT
69 A.3 RT+ tag
70 A.4 RT+ information elements and data model
A.4.1 General
A.4.2 List of RT content types
71 A.4.3 Structures of RT+ messages
72 A.4.4 Receiver data model
73 A.5 RT+ coding for RT
A.5.1 General
Figures
Figure A.1 – 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 – 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 – 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
74 A.5.2 RT+ identification (group type 3A)
Figure A.4 – Bit allocation for group 3A (message bits and AID)
75 A.5.3 Coding of the RT+ tag
Figure A.5 – Coding of the message bits of the application group
76 A.5.4 Clearing of RT+ messages
77 Table A.2 – Code list and ‘RT+ class’ description of RT content types
80 A.6 Broadcasting conventions
A.7 Receiving conventions
A.8 Marking
81 Annex B (normative) Coding of RadioText Plus(RT+) tagging information for RadioText in the eRT ODA of Annex C
Table B.1 – RT+ information elements for eRT
82 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 – Bit allocation for group 3A (message bits and AID)
Table C.1 – eRT information elements
83 C.2.3 Coding of the eRT text string
Figure C.2 – Coding of the message bits of the application group type A
84 C.2.4 UTF-8 decoding problems when used with RT+
C.3 Broadcasting conventions
C.4 Receiving conventions
C.5 Marking
85 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 – New ODA-AF – group type 3A
86 D.2.2 AF coding in the application group
Figure D.2 – New ODA-AF application group – group type A
Table D.1 – 9-bit AF code table for VHF Band I (64,0 MHz to 88,0 MHz)
Table D.2 – 9-bit AF code table for VHF Band II (87,5 MHz to 108 MHz)
87 Table D.3 – 9-bit special meanings code table
Table D.4 – LF/MF code table – ITU regions 1 and 3 (9 kHz spacing)
Table D.5 – MF code table – ITU region 2 (10 kHz spacing)
88 D.2.3 AF method A
D.2.4 AF method B
90 D.2.5 Convention for identification of the AF method used
91 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 – File ID station logo options
92 E.3.3 File transport
E.3.4 Display mode
E.3.5 Link of the logo with the PI code
93 Annex F (normative) ODA app – 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
94 F.4 Text character coding
F.5 Slide structure and file elements used
Figure F.1 – Components used in the slideshow
95 Figure F.2 – Structure of the [PREVIEW] text file
Figure F.3 – Structure of the [URLS] text file
Table F.1 – Start position of each file element within [PREVIEW]
96 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 – Start position of each file element within [URL]
97 F.8 Directory trigger group
F.8.1 Function
F.8.2 Specification
Figure F.4 – Directory trigger group
Table F.3 – File numbering system used
98 F.9 Receiver display mode options
Table F.4 – Parameters used in the directory trigger group
99 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
100 G.4.3 IPv6 coding
Figure G.1 – Coding of IPv4 address with port number
Table G.1 – Address type code
Table G.2 – Link ID code of IP connection
101 G.4.4 IP address and port number coded as URL text
Figure G.2 – URL text coding to connect to an application data server
102 Annex H (normative) ODA tool – RDS data mode NFM
H.1 Objective to be achieved
H.2 Specification of the NFM protocol
Figure H.1 – NFM message format

Related products

BS IEC 62106-6:2023 - TC
$246.62