EPISODE

2.7.1 Statement No 1, dated 22nd March 1996

An urgent statement from the EPISODE Project, Management Committee,
regarding RDS-TMC standardisation

1. Introduction

It is a considerable surprise to members of the EPISODE Project Management Committee that, within a few weeks of being contracted by the European Commission, the project has to issue this urgent statement to highlight significant problems regarding the standardisation of RDS-TMC.

2. Background

As a result of the 3rd Framework RTD programme three vital issues regarding RDS-TMC were identified as requiring further work and appropriate standardisation before large scale implementation. These were:

management and deployment of the location databases;

a "networking layer" for RDS-TMC to facilitate the continuous reception of TMC from a diversity of transmitters and broadcasters over large areas; and

development of "service id" permitting a wide range of service providers to offer complementary and competing services and permitting the motorist to drive across Europe with continuous TMC services.

These needs were clearly identified and were the subject of a meeting at the AA in Basingstoke, UK. RDS experts were requested at that meeting to look for solutions including future proofing RDS-TMC and to ensure data capacity for the "networking" and "service" layers could be found and integrated with the existing broadcast/service requirements.

The work required to develop these additional layers was specifically planned into the 4th Framework activities and is identifiable as a workpackage in the FORCE project, for example. In support of this Members of the RDS Forum, responding to the shortcomings of the RDS-TMC coding highlighted in 1995 have been working on the so called Open Data Applications (ODA) enhancement to the RDS standard which is now at draft 2.1 stage and prepared for RDS Forum ratification in May 1996, when it will enter the CENELEC unique voting process. The ODA proposal offers significant opportunities for the 4th Framework RTD programme to develop, in the coming months, many features associated with the "network" and "service" layers required for RDS-TMC.

3. Problem

In the period between the 3rd and 4th Framework RTD programmes a sort of vacuum has arisen, during which certain parties are attempting to force agreements regarding these very detailed data coding issues related to RDS-TMC, without appropriate consultation.

A number of meetings have been held apparently under the FORCE/ECORTIS banner to discuss the extensions to the RDS-TMC specification. These meetings have been called with great urgency, appear not to be formal Work Package discussions and they have not included full representation of FORCE partners, some experts from CEN TC 278, the RDS Forum standards experts and EPISODE liaison representatives. The aim of these meetings seems to be to rapidly establish de facto standards, possibly patented, prior to the commencement of work under the 4th Framework Programme. Simultaneously we observe that the urgency to standardise RDS-TMC in the CEN TC 278 SWG 4.1 was suddenly reduced.

4. Commentary

The requirements in RDS-TMC coding, to implement the "network" and "service" layers identified, need to be developed in an orderly manner involving a broad group of experts as mentioned above, since any development of this type has a major impact on the broadcast infrastructure and receiver designs.

The ad hoc meetings under the FORCE/ECORTIS umbrella do not fulfil these requirements on representation, neither has it given proper consideration to the work undertaken by the RDS Forum in producing the Open Data Applications structure.

The EPISODE project recognises that there may be commercial, economic and political reasons that mean the ODA mechanism for RDS-TMC cannot be implemented immediately, yet it does provide a mechanism by which the new layers may be incorporated efficiently. Proposals being pursued by the FORCE/ECORTIS ad hoc group leave us very concerned about capacity and timing requirements for RDS and, as we presently understand them, are unacceptable.

FORCE has a work package to deal with these problems with the correct representation and mandates for all necessary liaison. Similarly the EPISODE project has a mandate to liase with that work package activity. Work of the formal FORCE work package is being compromised by these ad hoc meetings.

5. Recommendation

Clearly the situation must urgently be resolved. We recommend the following action:

that the EC is requested to intervene immediately to prevent these meetings from producing de facto and inadequate standards.

that the FORCE project should be given time and encouraged to develop, by consultation and consensus, adequate and future proof standards.

The EBU-EPISODE project Management Committee hopes this urgent statement will assist the European Commission, for all parties, to resolve the outstanding issues.

Issue date November 15, 2004
Copyright © 1996, 1997, 1998 EBU. All rights reserved.