´óÏó´«Ã½

In RAD we don't just work on interesting stuff ourselves, we also help others within the ´óÏó´«Ã½ to as well. RAD, along with the Research and Development's Innovation Culture team, have been working to roll out One in Ten across a number of areas within the ´óÏó´«Ã½.

What is One in Ten? One in Ten is a way of gathering ideas and prototype proposals from colleagues - you may have read some my posts regarding this previously (eg Innovation and the red button )

It allows ´óÏó´«Ã½ staff to explore and investigate ideas that otherwise may have not been looked at as part of the usual workstream. The ideas explored may be things that are beneficial to ´óÏó´«Ã½ audiences or to the ´óÏó´«Ã½'s processes and systems. Recently our colleagues from the TV platforms team held a One in Ten day for ´óÏó´«Ã½ staff to hack and develop ideas. The day was themed "Games, consoles, quizzes and TV platforms" - Susan Richards from that team has written an update here

Ruhel Ali is a development producer working in the RAD and Innovation Culture teams.

• Bookmark with:
• |
• |
• |
• |
• - What's this?

Hi. I'm a software engineer in RAD and I've been doing some work on which I'd like to share with you. As James Cridland and Nick Piggott explain in their article, RadioDNS - making your radio more intelligent, RadioDNS represents a way for broadcasters to provide an enhanced radio listening experience through a new set of internet services, which can be used by any AM, VHF/FM, or DAB radio that also has an internet connection or with internet streaming radio. These services include RadioVIS, which allows display of an image slideshow and text messages, RadioEPG, which provides an electronic programme guide, and RadioTAG, which allows the listener to tag or bookmark radio content, or give feedback directly to the radio station. The RadioDNS , currently under development, are open for all device manufacturers and broadcasters to use, with a view towards future standardisation.

Radio Station DNS Lookup

A radio station broadcasting on FM includes digital data in the form of that allows the radio receiver to identify the station and display the station name. As an example, the following example shows the station information broadcast for ´óÏó´«Ã½ Radio 1. The PI and ECC codes are obtained from the RDS data.

For ´óÏó´«Ã½ Radio 1, broadcast on , the station identifier information is:

RadioDNS describes how these parameters can be used to construct a fully-qualified domain name (FQDN) that identifies the station, in this case 09880.c201.ce1.fm.radiodns.org for FM, or 0.c221.ce15.ce1.dab.radiodns.org for DAB. A DNS lookup returns the canonical name (CNAME) for this FQDN:

nslookup -type=CNAME 09880.c201.ce1.fm.radiodns.org

Non-authoritative answer:
09880.c201.ce1.fm.radiodns.org  canonical name = bbc.co.uk

Availability of services is advertised through the use of DNS , as shown in the following table:

Capital FM have a RadioVIS visualisation service available for use with their . To access this, we construct the appropriate FQDN from the RDS data and broadcast frequency: 09580.c586.ce1.fm.radiodns.org. The CNAME is found by DNS lookup to be vis.media-ice.musicradio.com, and a service record query against this hostname shows that the RadioVIS service is available at vis.musicradio.com, port 80.

nslookup -type=SRV _radiovis._tcp.vis.media-ice.musicradio.com

Non-authoritative answer:
_radiovis._tcp.vis.media-ice.musicradio.com     SRV service location:
          priority       = 0
          weight         = 100
          port           = 80
          svr hostname   = vis.musicradio.com

vis.musicradio.com      internet address = 194.70.58.122

Visualisation using RadioVIS

The RadioVIS protocol is an extension of the , which can be served by a such as . In order to demonstrate RadioVIS within the ´óÏó´«Ã½ I set up a local RadioVIS server for Radio 1 and developed a client application to display the content.

The server uses ActiveMQ running on , with content from the DAB LiveText feed for Radio 1 and the trial DAB slideshow service. The server provides two topics that clients can subscribe to, one for text messages and one for image URLs, which allows the client to be able to choose which notifications to receive. The topic names are constructed from the same station identification broadcast parameters we already used to construct the station FQDN, so for Radio 1 FM these would be:

After establishing a connection, the client sends a SUBSCRIBE Stomp message to subscribe to a topic.

SUBSCRIBE
destination: /topic/fm/ce1/c201/98.80/text
ack: auto

^@

Once subscribed, the client then periodically receives text messages and image URLs from the server, in the form of Stomp MESSAGE frames, where the body of the message body contains the specific message.

Text Messages

The TEXT message is used to display text on the radio receiver, such as programme and presenter names, or currently playing song and artist. Messages can be up to 128 characters in length.

TEXT <message>

Example:

MESSAGE
destination: /topic/fm/ce1/c201/98.80/text
message-id: ID:radiovis-50431-1232528810717-4:6:-1:1:1741

TEXT On air now: The Chris Moyles Show^@

Slideshow Images

The SHOW message is used to display slideshow images. The message contains the URL of the image, which the client can download via HTTP, and optional hyperlink URL to be associated with the image. If given, the trigger_time indicates when the image should be displayed, or NOW to display immediately.

SHOW <image_url>[,<link_url>] [<trigger_time>]

Example:

MESSAGE
destination: /topic/fm/ce1/c201/98.80/image
message-id: ID:radiovis-50431-1232528810717-4:6:-1:1:1742

SHOW https://localhost/slide.jpg,https://bbc.co.uk/radio1/ NOW^@

The RadioVIS demo application was developed in Python, using the GUI library and Jason R. Briggs's module. We are planning to release this application as open source software soon.

For more information about RadioDNS, or to join the RadioDNS developer discussion group, please visit .

Thanks to Sean O'Halpin and Giacomo Schimmings from ´óÏó´«Ã½ Audio and Music, and Nick Piggott, Andy Buckingham, Adam Fox and Ben Poor at Global Radio for their help during this project.

Chris Needham is a Software Engineer in the RAD team.

• Bookmark with:
• |
• |
• |
• |
• - What's this?

Hi everyone. You're reading the first post on the new blog from the people working in RAD. We're a new, small team within ´óÏó´«Ã½ Future Media and Technology. I'm George Wright and I head up RAD. I have, and will continue to, blog on the main ´óÏó´«Ã½ Internet blog ( available here )

RAD works on near term prototypes, products and services across all digital platforms. We're part of a wider group encompassing Mobile, Audio and Music, and are based in London, W1. Our colleagues in Audio and Music already have an excellent blog at Radio Labs, as does the Journalism team, and we hope to emulate their approach to sharing new ideas and gain insight into your thoughts using the Web.

RAD completed recruitment and opened its doors in November 2008. We have a remit which stretches across all digital platforms and content areas, trying to help shape the ´óÏó´«Ã½'s thinking, encourage liaision with longer term research (both internally, within the ´óÏó´«Ã½'s fantastic R&D department, and externally, be it with academic partners, mainstream code releases or brand new startups), and release code and output which delivers new ways of tackling problems like distribution for AV content, service discovery, UI and UX for new platforms, and much more.

Whilst RAD was in gestation, we worked on new products and services, some of which have already been mentioned on the ´óÏó´«Ã½'s internet blog - our P2P-Next work, or the Ubuntu/ Totem collaboration. We'll be going into more detail about these releases on this blog.

We use agile methods to develop software. We've made some tweaks to the more formal ways of delivering using - lots of the people and companies we work with are external to the ´óÏó´«Ã½, and so traditional physical standups won't work. We hope to share some of this thinking with you on here.

Our products are categorised into 3 phases - Alpha, Beta and Release Candidate. Very little of what we produce is designed for end users as a finished product, so we hope our categorisation lets you know what to expect. Alpha is the least fully formed - may barely run without crashing, but is functional and will provide learning. We'll explain these categories in more depth in a later blog.

We'll be posting fairly frequently to this blog, with a combination of code drops, new thinking, and general thoughts about our work.

George Wright runs the RAD (Rapid Application Development) team in ´óÏó´«Ã½ Future Media and Technology.

• Bookmark with:
• |
• |
• |
• |
• - What's this?