RDS/RBDS Tagged Program Ancillary ODA proposal

Transcription

1 RDS/RBDS Tagged Program Ancillary ODA proposal Revision.4 (preliminary) 11/9/24 Prepared by: Seth Stroh Senior Engineer, the radio experience RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 1 of 17

2 The Tagged Program Ancillary ODA Specified herein is an efficient, versatile and extensible system for the transmission of program ancillary data in VHF/FM terrestrial radio broadcast. The system is realized in the creation of an RDS/RBDS Open Data Application (ODA) and thereby makes use of (is fully compatible with) existing infrastructure (ODA enabled RDS generators) as well as the RDS chipsets commonly used in consumer radio receivers. The specified system is in many ways analogous to the ID3v2 tagging system developed around and popularized by Internet audio and thus the name: the Tagged Program Ancillary (TPA) ODA. The most significant benefit of TPA over traditional RDS data casting is clear delineation of each data element (in example: the artist name, song title, composer, etc.) Additional benefits of TPA include the ability to exceeded traditional RDS information carrying limitations (64 character fixed length radiotext), the ability to flag visibility of individual data elements, and extended functions to improve display update performance in receivers. Note that to process and display data sent using an ODA, a radio receiver must be designed with advance knowledge of that ODA. As such, data sent using the TPA best serves as an enabler for a new generation of radio equipped consumer electronic devices. The transmission of an ODA does not in any way preclude the use of traditional RDS features (such as radiotext or PS) and compatibility with existing receivers is also thereby assured. Central to any ODA is the RDS group type 3A, the application identification for open data. The generic form of group type 3A is depicted in the following illustration: TP Checkword Group Checkword Checkword Checkword PI code + type PTY + Message bits + Application ID + offset A code offset B offset C offset D 1 1 A A A A B Application Group Type Code Figure 1: Application identification for Open data (group type 3A) Group type 3A is essentially a notification to the receiver that this broadcast carries data for a particular ODA. The Application ID, sent in block 4 of the 3A group, uniquely identifies the ODA being broadcast. If the data to be broadcast is no greater than 16 bits in length, that data can be transmitted using a single 3A group. In this first case, the actual data is sent in block 3, the message bits. If the data to be broadcast is greater than 16 bits in length, the first 16 bits are sent in block 3 of the 3A group and any data beyond those first 16 bits is sent in a second group known as the application group type. Selection of application group type is left to the broadcaster in order to prevent group allocation conflicts when several different ODA are carried on a single broadcast. The receiver examines the 5 least significant bits of group 3A block 2, the application group type code, to determine the group used for transmission of any data beyond the first 16 message bits. If this second group is not used, the application group type code is set to. For reasons of efficiency, the TPA requires the selection of a type A group for data transmission. Group type 11A and 12A are unconditionally available for use by open data applications. Additional group types are often available but are subject to the usage of specific RDS/RBDS features by the broadcaster. (In example, group type 5A is available for use by an open data application if the transparent data channel is not in use by the broadcaster. Group type 6A is available if the in-house application is not in use. Group type 7A is available if the radio paging service is not in use. Group type 8A is available if the traffic message channel is not in use, etc.) RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 2 of 17

3 The TPA makes use of group type 3A in two distinct ways: to transmit an extended function or to announce the transmission of a data element. Usage is indicated by the state of a flag, the XF or extended function flag, carried in the block 3 message bits of the 3A group. For the transmission of an extended function, the XF flag is set to 1 and the TPA defines the remainder of the message bits as depicted in the following illustration: TP Checkword Group Checkword Checkword Checkword PI code + type PTY + Message bits + Application ID + offset A code offset B offset C offset D 1 1 Application group type code XD function data XI function index Sequence number 1 XF (extended function) flag Figure 2.1: Application identification for TPA extended functions (group type 3A) The extended function message bits are described as follows: XF, the extended function flag, is always set to 1 when transmitting an extended function. XI, the extended function index, is a 4 bit binary number (a nibble) identifying the specific function the receiver should execute. The 4 bit index allows a maximum of 16 extended functions to be defined by the TPA. XD, the extended function data, is an 8 bit binary number (a byte) passed as a parameter to the identified function. In the case of a function that does not require a parameter the XD byte is set to. The sequence number is a 3 bit binary number (a counter) that is incremented each time there is a significant change in the TPA data being transmitted. Specifically, the sequence number is incremented at the start of each new broadcast event. (For a typical music station, a broadcast event is defined as the start of a new song, the start of an advertisement, etc.) A 3 bit sequence number allows for a count range of to The sequence number wraps around to when incremented past 7. Should a receiver experience intermittent dropout of the RDS signal, the sequence number of the next 3A group successfully decoded can be examined to determine if a new event started during the dropout condition. At this time, there are no extended functions defined requiring more than 16 bits of data. As such, the application group type code is set to in figure 2.1. Two extended functions are defined in this version of the TPA specification: XI- ( ) is the radiotext check function. For this function, XD carries a CRC-8 of the radiotext message currently being broadcast. The receiver may use this CRC to validate its own radiotext buffer. The CRC-8 is calculated over the entire length of the radiotext buffer. The TPA allows association between data elements and the radiotext buffer (a data elements may be defined as a substring of the radiotext buffer.) By transmitting a CRC of the entire radiotext message, the receiver gains confidence that its own radiotext buffer is valid and that it can correctly associated the radiotext with TPA data elements received. This mechanism also allows for faster display updates as a receiver might otherwise wait for a complete repetition of the data to validate reception. XI-1 ( 1 ) is an explicit clear display function. XD is unused by this function and should be set to. This function is a notification to the receiver that the broadcast event has changed and that it should clear its display of potentially stale data. This function is normally sent once at the start of a new event. Should it be missed due to loss of signal, the receiver may examine the sequence number to detect the start of a new broadcast event. RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 3 of 17

4 For announcement of data element transmission, the XF flag is set to and the TPA defines the remainder of the group 3A message bits as depicted in the following illustration: TP Checkword Group Checkword Checkword Checkword PI code + type PTY + Message bits + Application ID + offset A code offset B offset C offset D 1 1 n n n n Application group type code Element ID Element length (groups in transmission) Sequence number XF (extended function) flag ED (element descriptor) flag EV (element visibility) flag Figure 2.2: Application identification for TPA data element announcement (group type 3A) The data element announcement message bits are described as follows: XF, the extended function flag, is always set to when transmitting a data element announcement. Element ID is a 6 bit binary number identifying element type announced by the TPA transmission. (In example, an Element ID of announces a song title data element.) The 6 bit Element ID allows a maximum of 64 element types to be defined by the TPA. A list of element types currently defined by the TPA is presented in the next section. Element length is a 4 bit binary number (a nibble) indicating the number of additional groups (application groups) required to define the specific data element announced by this transmission. The element data itself is contained in these additional groups. As such, the TPA will transmit at least one additional group (beyond the 3A announcement group) to define an announced data element. An element length of indicates that 1 application group will be sent in defining this element. An element length of indicates that 16 application groups will be sent which is the largest supported transmission length. The application group type code indicates the group used to transmit the element data. Because the TPA always requires at least one group (beyond the 3A announcement group) to define a data element, the application group type code will always be set for an announced data element. The TPA requires a type A group for element data transmission but the actual group selection is left to the broadcaster as discussed in the introduction. The sequence number is a 3 bit binary number (a counter) that is incremented at the start of each new broadcast event. (A complete discussion of sequence number is included in the previous section on extended functions.) EV, the element visibility flag, is normally set to 1 and indicates to the receiver that the announced data element should be viewable by the end user. In certain circumstances a broadcaster may with to transmit a data element that is not directly meaningful to the end user. In this exception case, the EV flag is set to and the receiver is not to display this data element. ED, the element descriptor flag, is normally set to and indicates that the default descriptor text should be used by the receiver in describing the data element. The default descriptor text for each element type is presented in the next section as part of the element ID list. A receiver makes use of the element descriptor text as part of its menu system allowing the end user to easily select (by name) the data elements they prefer to display. The default descriptor text is normally implemented as a ROM lookup table within the receiver. [Continued ] RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 4 of 17

5 [ED flag continued] In certain circumstances the broadcaster may wish to override the default descriptor text for a particular element type. (In example, a unique commerce ID number might be transmitted as part of the TPA data. It is useful to convey the type of ID, such as ISRC, that is being transmitted. This is accomplished by sending an alternate descriptor as part of the element data.) To override a default descriptor, the ED flag is set to 1 and the alternate descriptor text is sent as part of the element definition. In this exception case, the first byte of element data is a CRC-8 and the second byte indicates the length of the alternate element descriptor. The actual element descriptor text starts at the 3rd byte and, finally, the element definition follows the descriptor text. A receiver with extremely limited memory resources can ignore the alternate descriptor text by using the descriptor length byte to skip that text. In the nominal case (ED flag set to ) the length byte and the descriptor text are omitted from the sequence. See the example section for specific illustration of this concept. For the application group used in transmitting the element data, the TPA defines the message bits as depicted in the following illustration: TP PI code Checkword Group Checkword Checkword Checkword + type PTY + Message bits + Message bits + offset A code offset B offset C' offset D Application grouptypecode A/Bflag Segment address n n n n c c c c b b b b b b b b C C1 C2 C3 1 C4 C5 C6 C C6 C61 C62 C63 Figure 2.3: Application group type for TPA data element transmission (group type na) The actual element data is transmitted in segments (one segment per application group) using a data format analogous to radiotext, as transmitted in the 2A group. A maximum of 16 segments can be transmitted in defining a data element and 4 characters are defined per segment. The maximum length of a data element is therefor 64 characters. The A/B flag is set equal to the least significant bit of the sequence number from the 3A group announcing this data element. As such, the A/B flag builds an additional association between application groups and the announcement groups transmitted by the TPA. As with the sequence number, the receiver may use the A/B flag as an indication that the broadcast event has changed. The segment address is a 4 bit binary number (a nibble) indicating the data segment being transmitted. The segment address always starts at and increments by 1 for each additional segment required in defining the element. The total number of segments required to define an element is indicated by the element length in the announcing 3A group. A gap in the segment address sequence is a good indication to the receiver that part of the element data has been lost. RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 5 of 17

6 Data element details Because the radiotext message typically contains at least some of the data elements to be transmitted by the TPA, the TPA allows an association to be made between data elements and radiotext. (That is to say, data elements may be defined as substrings of the radiotext message.) This method of element definition decreases the bandwidth required by the TPA if a good portion of the required data can be extracted from the radiotext message. Alternately, data elements can be defined entirely by TPA transmissions and in this case radiotext may serve as a completely independent message channel. See the examples section for specific illustration of each method. In either case, the first character of element data is always a CRC-8 byte calculated across the remainder of the characters in the element definition. (The maximum usable length of a data element is therefor 63 characters.) Any unused characters in the last segment of a data element are null () padded. If an alternate descriptor is sent (this is the exception case, ED flag set to 1 ) the second byte of the element data indicates the length of the descriptor text. The descriptor text starts at the 3rd byte of and is followed by the actual element definition. In this case, the CRC-8 calculation is inclusive of the descriptor length byte, the descriptor text, and the element definition. If an alternate descriptor is not sent (this is the nominal case, ED flag set to ) the element definition starts at the second byte and the CRC-8 calculation is only inclusive of the element definition. The element definition itself may consist of a text string transmitted within the TPA, an association to the radiotext message (a substring), or a combination of these two. To limit the amount of parsing required on the part of the receiver, association to the radiotext message is limited to a single substring per data element! A radiotext substring within a data element is instantiated by the ASCII STX control character. (This is decimal value 2.) This control character is chosen so as not to conflict with the selection of international font tables. The control character is followed by two parameter bytes: the start position within the radiotext message and the length of the substring to be extracted. The MSB of each parameter byte is set (equivalent to adding 128 to the start position and the length) in order to create an easily identified byte sequence. Additional text may appear before, after, or on both sides of the substring within a data element. Data element types Data elements are assigned a 6 bit binary ID number in the range of $ ( ) to $3F ( ). The following table gives assignment to 15 of the 64 possible element types. The remaining 49 element types are available for future assignment. Each entry in the element type table consists of the following: ID, default descriptor, level, ID3, ID3v2 frame description, and notes as to the intended use of this element type. ID is the 6 bit ID number (in hexdecimal) assigned to the element. The default descriptor is a default text string used by a receiver to describe the element when an alternate descriptor is not broadcast as part of the element definition. Level is the transmission priority of this element type. (Level 1 items are transmitted first followed by level 2, etc.) ID3 is a reference to the ID3v2 frame of rough equivalence to this element type. The entries in the element table are arranged into logical groups. A group is a set of related items that a listener might switch between on a radio display. (For example: title to subtitle to genre ) The elements within each group are sorted starting with the most relevant at level 1. By prioritizing the transmission of elements by level, a receiver with limited memory resources will fill its internal buffers with the most relevant elements first. Advanced elements such as URLs or unique ID numbers are sent last with the assumption that an advanced receiver capable of processing these elements will have the memory available to do so. By design, level 1 items are the most likely elements to be utilized by broadcasters. In most instance level 2 and particularly level 3 could be considered trivia information that is useful for certain types of content such as live recordings or covers. RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 6 of 17

7 Default descriptor Level 1 ID3 ID3v2 frame description ID Notes Notes Title Level 1 TIT2 Title, song name or content description Music programming: the main content title (the song title) Other programming: the title of a particular episode Subtitle Level 2 TIT3 Subtitle or description refinement 4 Music programming: refinement of the main title (typically used for live performance details) Other programming: title refinement (the subject of an episode) Genre Level 3 TCON Content type or genre 8 Music programming: identifies the genre of a particular piece of music Artist / Host Level 1 TPE2 Band or orchestra 1 Music programming: the primary identifier of the performing artist (the band or group name) Other programming: the name of the show host (as in an interview or call-in show) Soloist / Guest Level 2 TPE1 Lead artist or soloist 5 Music programming: a guest artist or soloist involved with a particular piece of music Other programming: the name of the show guest (as in an interview) Original Artist Level 3 TOPE Original artist or performer 9 Music programming: for a cover of a song, this identifies the original artist Album / Show Level 1 TALB Album or show title 2 Music programming: identifies a physical recording associated with a piece of music Other programming: the name of the show (as opposed to the episode title) Publisher Level 2 TPUB The publisher or record label 6 Music programming: identifies the record label associated with a physical recording Original Album Level 3 TOAL Original album or show title A Music programming: for a cover or remix of a song, this identifies the original recording Composer Level 1 TCOM Composer 3 Music programming: identifies composer(s) of a piece (useful for classical and popular music) Conductor Level 2 TPE3 Title, song name, or content description 7 Music programming: identifies the conductor (most commonly associated with classical music) Remix Level 3 TPE4 Interpreted or remixed by B Music programming: identifies the person responsible for a remix or interpretation of a piece Commerce ID Level 4 UFID Unique identifier (a key into a database or similar) C All programming types: a unique content ID number for use in future commerce applications WWW Level 4 WROS Official radio station homepage E All programming types: a URL where the listener can find more information about the broadcast Station Name Level 4 TIT2 Title, song name, or content description F All programming types: the radio station name (improved version of PS, not limited to 8 characters) RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 7 of 17

8 Example 1: Jazz, all elements defined by radiotext reference Now playing Dave Brubeck Quartet Take Five from the CD Time Out ODA transmission: 3A AGT = CRC = XX XF = 1 XI = 1 Function (clear) 3A AGT = CRC = XX XF = 1 XI = Function (RT CRC) 3A AGT = 11A ID = XF = EV = 1 ED = EL = Element (title) 11A XX 2 A1 89 3A AGT = 11A ID = 1 XF = EV = 1 ED = EL = Element (artist) 11A XX 2 8C 94 3A AGT = 11A ID = 2 XF = EV = 1 ED = EL = Element (album) 11A XX 2 B7 88 Note: XX indicates a CRC-8 value to be filled in Example radio display: Title Take Five Artist / Host Dave Brubeck Quartet Album / Show Time Out Transmission metrics: Metrics include PS, RT and ODA Times for sequence Times for sequence Tuned in during event (best case) seconds 2.83 seconds Tuned in during event (worst case) 8.32 seconds seconds RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 8 of 17

9 Example 2: Popular, elements defined by radiotext and TPA No w Playing: Da vid Bo wie, Fame' 9 ( remi x) on 13. 7, The Mountain ODA transmission: 3A AGT = CRC = XX XF = 1 XI = 1 Function (clear) 3A AGT = CRC = XX XF = 1 XI = Function (RT CRC) 3A AGT = 12A ID = XF = EV = 1 ED = EL = Element (title) 12A XX 2 9A 8F 3A AGT = 12A ID = 1 XF = EV = 1 ED = EL = Element (artist) 12A XX 2 8D 8B 3A AGT = 12A ID = 2 XF = EV = 1 ED = EL = 3 Element (album) 12A XX + Changesbowie + 3A AGT = 12A ID = 3 XF = EV = 1 ED = EL = 5 Element (composer) 12A XX + Alomar, Bowie, Lennon + 3A AGT = CRC = XX XF = 1 XI = Function (RT CRC) 3A AGT = 12A ID = 5 XF = EV = 1 ED = EL = 2 Element (guest) 12A XX + John Lennon 3A AGT = 12A ID = A XF = EV = 1 ED = EL = 3 Element (orig. album) 12A XX + Young Americans 3A AGT = 12A ID = B XF = EV = 1 ED = EL = 2 Element (remix by) 12A XX + Jon Gass + 3A AGT = 12A ID = F XF = EV = 1 ED = EL = Element (station ID) 12A XX 2 B4 8C Note: XX indicates a CRC-8 value to be filled in Example radio display: (level 1 refinement on all lines) Title Fame 9 (remix) Artist / Host David Bowie Album / Show Changesbowie Alternate radio display: (level 2 refinement on line 2, level 3 refinement on line 3) Title Fame 9 (remix) Soloist / Guest John Lennon Original Album Young Americans Transmission metrics: Metrics include PS, RT and ODA Times for sequence Times for sequence Level 1 Tuned in during event (best case) Tuned in during event (worst case) RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 9 of 17

10 Example 3: Popular, elements defined by radiotext and TPA, UFID with descriptor radiotext buffer Now playing U2 The Wanderer with Johnny Cash from the CD Zooropa ODA transmission: 3A AGT = CRC = XX XF = 1 XI = 1 Function (clear) 3A AGT = CRC = XX XF = 1 XI = Function (RT CRC) 3A AGT = 11A ID = XF = EV = 1 ED = EL = Element (title) 11A XX 2 8F 8C 3A AGT = 11A ID = 1 XF = EV = 1 ED = EL = Element (artist) 11A XX 2 8C 82 3A AGT = 11A ID = 2 XF = EV = 1 ED = EL = Element (album) 11A XX 2 B9 87 3A AGT = 11A ID = 5 XF = EV = 1 ED = EL = Element (guest) 11A XX 2 A1 8B 3A AGT = 11A ID = 6 XF = EV = 1 ED = EL = 3 Element (publisher) 11A XX + Island Records + 3A AGT = CRC = XX XF = 1 XI = Function (RT CRC) 3A AGT = 11A ID = 8 XF = EV = 1 ED = EL = 1 Element (genre) 11A XX + Rock + 3A AGT = 11A ID = C XF = EV = ED = 1 EL = 4 Element (unique ID) 11A XX 4 + ISRC + GBAAN Note: XX indicates a CRC-8 value to be filled in Example radio display: (level 1 refinement on all lines) Title The Wanderer Artist / Host U2 Album / Show Zooropa Alternate radio display: (level 2 refinement on lines 2 and 3) Title Fame 9 (remix) Soloist / Guest Johnny Cash Publisher Island Records Transmission metrics: Metrics include PS, RT and ODA Times for sequence Times for sequence Level 1 Tuned in during event (best case) Tuned in during event (worst case) RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 1 of 17

11 Example 4: element usage for non-music programming Art B ell Coast to Coast: Einstein & Science with Dr Michio Kaku ODA transmission: 3A AGT = CRC = XX XF = 1 XI = 1 Function (clear) 3A AGT = CRC = XX XF = 1 XI = Function (RT CRC) 3A AGT = 12A ID = XF = EV = 1 ED = EL = Element (title) 12A XX A AGT = 12A ID = 1 XF = EV = 1 ED = EL = Element (host) 12A XX A AGT = 12A ID = 2 XF = EV = 1 ED = EL = Element (show) 12A XX E 3A AGT = 12A ID = 5 XF = EV = 1 ED = EL = Element (guest) 12A XX 2 B1 8E Note: XX indicates a CRC-8 value to be filled in Example radio display: (level 1 refinement on all lines) Title Einstein & Science Artist / Host Art Bell Album / Show Coast to Coast Alternate radio display: (level 2 refinement selected for line 2) Title Einstein & Science Soloist / Guest Dr Michio Kaku Album / Show Coast to Coast Transmission metrics: Metrics include PS, RT and ODA Times for sequence Times for sequence Tuned in during event (best case) seconds 3.53 seconds Tuned in during event (worst case) 8.32 seconds seconds RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 11 of 17

12 Example 5: Classical, elements defined by radiotext and TPA, ~64 chars each radiotext buffer Now playi ng Mozart: Violin Co ncerto No. 5 i n A Major, K. 219 ODA transmission: 3A AGT = CRC = XX XF = 1 XI = 1 Function (clear) 3A AGT = CRC = XX XF = 1 XI = Function (RT CRC) 3A AGT = 11A ID = XF = EV = 1 ED = EL = Element (title) 11A XX 2 94 A6 3A AGT = 11A ID = 1 XF = EV = 1 ED = EL = 7 Element (artist) 11A XX + Vienna Philharmonic Orchestra + 3A AGT = 11A ID = 3 XF = EV = 1 ED = EL = Element (composer) 11A XX 2 8C 86 3A AGT = CRC = XX XF = 1 XI = Function (RT CRC) 3A AGT = 11A ID = 4 XF = EV = 1 ED = EL = 1 Element (subtitle) 11A XX + Adagio + 3A AGT = 11A ID = 5 XF = EV = 1 ED = EL = 4 Element (soloist) 11A XX + Gidon Kremer ( ) + 3A AGT = 11A ID = 5 XF = EV = 1 ED = EL = 3 Element (conductor) 11A XX + N. Harnoncourt + Note: XX indicates a CRC-8 value to be filled in Example radio display: (level 1 refinement on all lines) Title Violin Concerto No. 5 in A Major, K.219 Artist / Host Vienna Philharmonic Orchestra Composer Mozart Alternate radio display: (level 2 refinement on all lines) Subtitle Adagio Soloist / Guest Gidon Kremer (Violin) Conductor N. Harnoncourt Transmission metrics: Metrics include PS, RT and ODA Times for sequence Times for sequence Level 1 Tuned in during event (best case) seconds seconds seconds Tuned in during event (worst case) seconds seconds seconds RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 12 of 17

13 Example 5: Classical, elements defined by radiotext and TPA, ~64 chars each best worst best Sequence "1.1.1" Sequence "1.2.2" Level Level title link to RT Time Grp Seg Notes Time Grp Seg Notes.88 B "".88 B "".175 2A.175 2A.263 3A display clear.263 2A 1.35 B "1".35 3A display clear.438 2A A RT CRC.525 3A RT CRC.525 B "1".613 B "1".613 2A A A A element (title).788 3A element (title).876 B "11" end of PS cycle A K.219".963 2A B "1" A title link to RT "Violin Concerto No. 5 in A Major, K.219" A B "" A A A element (artis A element (artist / host) A artist def "Vie 1.41 B "1" 1.41 B "11" end of PS cyc A A A artist def "Vienna Philharmonic Orchestra" A B "1" A 1 artist def A A 2 artist def A 1 artist def B "" B "11" end of PS cycle A A A A 2 artist def A 3 artist def B "" A 4 artist def A B "1" A 3 artist def A A B "1" A B A A 5 artist def A 4 artist def A 6 artist def B "1" B "1" A A A C A 5 artist def A D B "11" end of PS cycle A 7 artist def A B A element (com A 6 artist def B "11" end of PS cyc 3.24 B "" A E A C A F end of first RT A 7 artist def A composer RT RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 13 of 17

14 title link to RT 3.53 B "1" A RT CRC A D B "" A element (composer) A B "1" A A E A element (subt A composer RT link "Mozart" A subtitle def "A 4.29 B "11" end of PS cycle 4.29 B "1" A F end of first RT cycle L1 best A A RT CRC A B "" A 1 subtitle def A A element (solo A element (subtitle) B "1" B "1" A A A A subtitle def "Adagio" A soloist def "G B "1" A 1 soloist def A B "11" end of PS cyc A 1 subtitle def A B "11" end of PS cycle 5.8 2A A A 2 soloist def A element (soloist / guest) A 3 soloist def B "" B "" A A A soloist def "Gidon Kremer (Violin)" A B "1" A 4 soloist def A A element (cond A 1 soloist def 5.78 B "1" B "1" A A A A B A 2 soloist def A conductor def B "11" end of PS cycle A 1 conductor def A B "1" A 3 soloist def A C B "" A D A A 2 conductor def A 4 soloist def A 3 conductor def B "1" B "11" end of PS cyc A A E A element (conductor) A F end of second B "1" A RT CRC 7.6 2A A 7.6 3A element (title) A conductor def "N. Harnoncourt" 7.94 B "" B "11" end of PS cycle A A B A A 1 conductor def A K.219" B "" A element (artis A C B "1" A 2 conductor def A 2 RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 14 of 17

15 7.77 B "1" A A D A artist def "Vie A 3 conductor def best A 1 artist def 7.97 B "1" 7.97 B "1" A E A A RT CRC A B "11" end of PS cycle A 2 artist def A F end of second RT cycle A 3 artist def A element (title) 8.48 B "11" end of PS cyc B "" A A A A title link to RT "Violin Concerto No. 5 in A Major, K.219" A 4 artist def B "1" A 5 artist def A B "" A element (artist / host) A B "1" A A A 6 artist def A artist def "Vienna Philharmonic Orchestra" A 7 artist def B "11" end of PS cycle B "1" A A A A 1 artist def A B B "" A element (com A A composer RT A 2 artist def B "1" 9.89 B "1" A C A A D A 3 artist def A RT CRC 1.72 B "1" A element (subt A B "11" end of PS cyc A 4 artist def A E B "11" end of PS cycle A F end of third R A A subtitle def "A A 5 artist def A 1 subtitle def B "" B "" A A A 6 artist def A B "1" A element (solo A A soloist def "G A 7 artist def B "1" B "1" A A A A A element (composer) A 1 soloist def B "11" end of PS cycle A 2 soloist def A B B "1" A composer RT link "Mozart" L1 worst A B "" A A C A 3 soloist def A RT CRC A 4 soloist def RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 15 of 17

16 B "1" B "11" end of PS cyc A D A A element (subtitle) A B "1" A element (cond A E A conductor def A subtitle def "Adagio" B "" B "11" end of PS cycle A A F end of third RT cycle A A 1 subtitle def A 1 conductor def B "" A 2 conductor def A B "1" A element (soloist / guest) A A B "1" A B A A 3 conductor def A soloist def "Gidon Kremer (Violin)" B "1" A A 1 soloist def B "11" end of PS cycle A A 2 soloist def B "" A A 3 soloist def B "1" A A 4 soloist def B "1" A A element (conductor) B "11" end of PS cycle A A conductor def "N. Harnoncourt" B "" A A 1 conductor def B "1" A A 2 conductor def B "1" A A A 3 conductor def worst RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 16 of 17

17 RDS/RBDS Tagged Program Ancillary ODA proposal (the radio experience) Page 17 of 17