ENV 12313-4-2000 en Traffic and Traveller Information (TTI) - TTI Messages Via Traffic Message Coding - Part 4 Coding Protocol for Radio Data System - Traffic Message Channel (RDS-.pdf

《ENV 12313-4-2000 en Traffic and Traveller Information (TTI) - TTI Messages Via Traffic Message Coding - Part 4 Coding Protocol for Radio Data System - Traffic Message Channel (RDS-.pdf》由会员分享，可在线阅读，更多相关《ENV 12313-4-2000 en Traffic and Traveller Information (TTI) - TTI Messages Via Traffic Message Coding - Part 4 Coding Protocol for Radio Data System - Traffic Message Channel (RDS-.pdf（43页珍藏版）》请在麦多课文档分享上搜索。

1、STD-BSI DD ENV L2313-9-ENGL 2000 1b24bb7 0853038 524 M DRAFT FOR DEVELOPMENT Tkaffic and Tkaveller Information (TTI) - IT1 Messages via Tkaffic Message Coding - Part 4: Coding Protocol for Radio Data System - Tkaffic Message Channel (RDS-TMC) - RDS-TMC using ALERT Plus with ALERT C ICs 35.240.60 NO

2、COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW DD ENV 12313-4:2000 DD ENV 1231342000 been prepared under the &dion of the Electrotechnicai Sector Committee, was published under the authority of the Standards Committee and comes into effect on 15 July 2000 Amd. No. Q BSI 07-2000

3、ISBN O 580 32749 3 National foreword D& Comments This Draft for Development is the officiai Enghh ianguage version of ENV 1231342000. This publication is not to be regarded as a British Standard. It is being issued in the Draft for Development series of publications and is of a provisional nature be

4、cause the level of innovation on this subject is currently high It should be applied on this provisional basis, so that information and experience of its practical application may be obtained Comments arising from the use of this DraR for Development are requested ao that UK experience can be report

5、ed to the European organization responsible for ils conversion into a European Standard. A review of this publication will be initiated 2 years after its publication by the European organization so that a decision can be taken on its status at the end of its three-year life. The commencement of the

6、review period will be notified by an announcement in Update Stundud. According to the replies received by the end of the review period, the responsible BSI committee will decide whether to support the conversion into a European Standard, to extend the life of the prestandard or to withdraw it. Comme

7、nts should be sent in writing to the Secretary of BSI Technical Committee EPL4278, Road transport informatics, at 389 Chiswwick High Road, London W4 4AL, giving the document reference and clause number and proposing, where possible, an appropriate revision of the text. A list of organizations repres

8、ented on this committee can be obtained on request to its secrem. Cross-references The British Standards which implement intedonal or European publications referred to in this document may be found in the BSI Stan- Catalogue under the section entitled Tnternational Standards Correspondence Index”, o

9、r by using the “Find” facility of the BSI Standards Electronic Catalogue. A British Standard does not purport to include ail the necessary provisions of a contract. Users of British Standards are responsible for their correct application. Compliance with a British Standard does not of itself confer

10、immunity from legal obligations. Summary of pages This document comprises a front cover, an inside front cover, the ENV title page, pages 2 to 40, an inside back cover and a back cover. The BSI copyright notice displayed in this document indicates when the document was last issued STD-BSI DD ENV L23

11、13-q-ENGL 2000 Lb24bb7 0853OiiO LA2 EUROPEAN PRESTANDARD ENV 123134 PRNORME EUROPENNE EUROPISCHE VORNORM April 2000 ICs 35.240.60 English version Traffic and Traveller Information (TTI) - TTI Messages via Traffic Message Coding - Part 4: Coding Protocol for Radio Data System - Traffic Message Channe

12、l (RDS-TMC) - RDS-TMC using ALERT Plus with ALERT C This European Prestandard (ENV) was approved by CEN on 26 April 1999 as a prospective standard for provisional application. The period of validity of this ENV is limited initially to three years. After ho years the members of CEN will be requested

13、to submit their comments, particularly on the question whether the ENV can be converted into a European Standard. CEN members are required to announce the existence of this ENV in the same way as for an EN and to make the ENV available promptly at national level in an appropriate form. It is permiss

14、ible to keep conflicting national standards in force (in parallel to the ENV) until the final decision about the possible conversion of the ENV into an EN is reached. CEN members are the national standards bodies of Austria, Belgium, Czech Republic, Denmark, Finland, France, Gemany, Greece, Iceland,

15、 Ireland, Italy, Luxembourg, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland and United Kingdom. EUROPEAN COMMEE FOR STANDARDIZATION COMITE EUROPEEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG Central Secretariat: rue de Stassart, 36 B-1050 Brussels 2000 CEN All rights of exploitation

16、in any form and by any means reserved worldwide for CEN national Members. Ref. No. ENV 12313-4:2000 E Page 2 ENV 12313-4:2000 CONTENTS LIST CONTENTS LIST FOREWORD INTRODUCTION 1. SCOPE 1.1 Application 1.2 Presentation 1.3 Service management 1.4 Transmission 2. NORMATIVE REFERENCES 3. APPLICATION 3.1

17、 Content of the TMC “travel service“ 3.2 TMC terminai 3.3 Event-orientated information (ALERT C) 3.4 Status-orientated information (ALERT Plus) 3.5 Strategic and tactical information 3.6 Geographic relevance 3.7 Transmitted message priority 4. PRESENTATION 4.1 Event-orientated messages 4.2 Status-or

18、ientated messages 4.2.1 Message format (variant : 4 bits) 4.2.2 Collection (1 1 or 12 bits) 4.2.3 Statuses (20 or 21 bits) 4.2.4 Coding mechanism 2 4 4 6 6 8 9 9 10 10 10 10 10 11 12 13 13 STD-BSI DD ENV 12313-9-ENGL 2000 Lb29bbS 0853092 T55 Page 3 ENV 12313-4:2000 5. SERVICE MANAGEMENT 5.1 Introduc

19、tion 5.1.1 Pure ALERT C service 5.1.2 Added value services (ALERT C and ALERT Plus) 5.2 System messages (32 bits) 5.2.1 Service layer information 5.2.2 Network layer information 6. TRANSMISSION 6.1 System messages 6.1.1 Type 1A groups 6.1.2 Type 5A groups 6.1.3 Type 3A groups 6.1.4 Type 8A groups 6.

20、2 Immediate repetition 6.3 Event-orientated messages (ALERT C) 6.4 Status-orientated messages (ALERT Plus) 20 20 21 21 24 24 25 32 33 33 34 35 36 37 38 38 6.5 Summary 40 Page 4 ENV 12313-4:2000 FOREWORD This European Prestandard has been prepared by FORCEECORTIS WP 13.6 expert team on ALERT Plus cod

21、ing protocol and location referencing and by Technical Committee CENEC 278 “Road transport and traffic telematics“, the secretariat of which is held by NNL According to the CENKENELEC Internal Regulations, the national standards organizations of the following countries are bound to announce this Eur

22、opean Prestandard: Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland and the United Kingdom. INTRODUCTION The ALERT Plus function is a compatible extension of the ALERT C functio

23、n and makes it possible to use RDS-TMC broadcast status-orientated information. This information is related to: 0 the road traffic, such as level of service or travel time, 0 the car park occupancy, 0 the public transport, such as travel time, frequency or headway. Other status-orientated informatio

24、n have still to be considered, such as the information about snow on the road, water height, wind force, pollution, lost due to traffic condition . The coding mechanisms are the same. This function constitutes an additional response to the information needs of road users, particularly in dense urban

25、 areas, by taking into account the constraints which affect the road network or the public transport operators. The ALERT Plus broadcasting protocol provides an information coding technique which allows the recipient to recover the broadcast information in its entirety. The transmitted messages cont

26、ain dynamic data (statuses) which can only be interpreted with reference to static data (locations.). To facilitate broadcasting, locations are grouped together in addresses called collections. Both transmitter and receiver must be aware of all elements. There are many functional responsibilities as

27、sociated with the provision of an RDS- TMC service, ranging from road based data collection, to message compilation and finally transmission. Because it was noted that the functional responsibilities and their names were not commonly understood, the key functions are defined in the ENV 12313-1, ALER

28、T C Protocol, date. These definitions are also useful to understand the standard described in this document. However they have to be completed by the following definition which characterises a functional responsibility of importance for the ALERT Plus function: Road Network Operator: STD-BSI DD ENV

29、12313-4-ENGL 2000 m Lb24bb9 0853OLi4 28 m Page 5 ENV 12313-4:2000 A public or private authority responsible for part of the road network of a country. Without making assumptions regarding the agreements which data service provider may enter into with road network operators, the standard allows infor

30、mation to be broadcast in unscrambled or scrambled form using either the public collections which belong to road network operators, if such collections exist, or private collections. The present pre-standard describes the broadcasting of dynamic data. All parts referring to location referencing are

31、dealt separately by CEN TC278 SWG7.3 and are not included in this document. Two approaches are generally distinguished in the RDS-TMC world: The first approach is based on the idea of an universal ALERT C service. This is possible if a continuous and inter-operable network of ALERT C free-access ser

32、vices is in place in a country or around a continent. A good example could be the RDS- TMC Pan-European Service code, are possible. Its structure is shown in Figure 8. The values of the public conversion table are dependant on the average traffic of the target road network. Therefore a unique conver

33、sion table is impossible. Its definition is then linked with the ALERT Plus location table number (ALTN) and subsequently with the ALERT Plus collection table number (ACTN). It is the public road authoritys responsibility to actually edit the reference code conversion table according to the traffic

34、behaviour on the target road network. In case of scrambled service, it is the service providers responsibility to edit the table. El I Figure 8: conversion table for travel time STD-BSI DD ENV L2313-Y-ENGL 2000 D Lb24bb7 0853057 qb m Page 18 ENV 12313-4:ZOOO The is computed on the basis of the lengt

35、h of the road section or the journey and for the road section or the journey. average travel time = length / average speed These two parameters, length and average speed, are contained in the location table for each road section or journey. Figure 9 illustrates how to decode a travel time. 4 bits 4

36、bits 4 bits 4 bits 4 bits 4 bits 72 bits variant first second third fourth fifth collection O001 = 7 O110 1 O01 o1 o1 O01 1 O01 o number EXAMPLE CONVERSION TABLE FOR TRAVEL TIME Travel time Travel time coding decodin No information No information Code L % TRAVEL TIME 620% TRAVEL TIME 209“ (length *

37、% travel time) / average speed Figure 9: decoding of travel times In Figure 9 the third status transmitted in the message is equal to 5 (binary value 0101). By means of the conversion table for travel time, it is possible to interpret this information as follows. In the location table we find the an

38、d the length of the location associated the status in the third position: average speed = 25 km/h length = 145 m We are able to compute the average travel time: average travel time = length / average speed = 2 1 seconds By means of the %travel time (620%) we can then calculate the travel time: trave

39、l time = ( average travel time * %travel time ) / 100 = 2 minutes 9 seconds STD-BSI DD ENV L23L3-q-ENGL 2000 W Lb29bbS 0853058 332 = O 1 2 3 4 Page 19 ENV 12313-4:2000 No information available Car park full Car park full soon Very high car park occupancy High car Dark OccuDancv When the terminal doe

40、s not receive a code for a particular location it considers that no travel time or speed information is available. 4.2.4.3 Status type: car park occupancy The location type is the ALERT C service. This is possible if a continuous and interoperable network of ALERT C non-encrypted services is in plac

41、e in a country or in Europe. A good example could be the RDS- TMC Pan-European Service i approach or to the approach. 5.2.1.1 Service IDentifier (SID) The SID is relevant for both approaches. It identifies the data service provider which is not necessarily identical with the broadcaster operating on

42、 the same transmitter. This enables service providers to mark their service and to allow receivers to search for and tune to those specific or marked service. A SID is a 6 bits-code. SID?s should uniquely be assigned on national level, therefore SID is linked to CC & ECC. Because SID code O identifi

43、es a general service, only 63 SID?s can be assigned per country. Two different SIDs can be broadcast referencing respectively: ALERT-C information (SID conveyed on 3A groups, see O), ALERT Plus information (SID conveyed in 8A groups, see O). In case of a pure ALERT Plus service, only the second SID

44、is transmitted. This double definition brings more flexibility and allows a pure ALERT Plus service to be broadcast without confusing ALERT C reception devices. In case of a mixed service, the two SID?s could be identical. 5.2.1.2 Service Provider Name (SPN) Only one static eight characters SPN shal

45、l be transmitted in the TMC-channel and is under the responsibility of the data service provider. This name is generally not identical to the Program Service Name (PS). If the SPN is not transmitted then it is assumed that the SPN is the same as the PS. STD-BSI DD ENV l2313-q-ENGL 2000 LbZqbb9 08530

46、bq blb = Page 25 ENV 12313-4:2000 5.2.1.3 ALERT C Location Table Number (LTN) This number is transmitted in order to correctly interpret the location transmitted, since various location tables exist. Rules and change of LTN are more precisely described in the ENV 123 13- 1, ALERT C Protocol, date. 5

47、.2.1.4 Messages specific to pure ALERT C services The information supplied is: o the Alternative Frequency Indicator (AFI) 0 the Message Geographical scope (MSG), 0 and the Mode of Transmission Parameters. These elements are more relevant for pure ALERT C services and are described in the ENV 12313-

48、1, ALERT C Protocol, date. 5.2.1.5 Additional messages for added value services 5.2.1.5.1 The ALERT Plus Collection Table Number is transmitted in order to correctly interpret the collection transmitted, since various collection tables may exist. Each collection number is stored in the ALERT Plus Co

49、llection Table and points to a set of location numbers stored in an ALERT Plus Location Table. ALERT Plus Collection Table Number (ACTNl This ALERT Plus Location Table has also a number. It is called the ALERT Plus Location Table Number (ALTN). It is broadcast in the same way as the ACTN. The ALTN not only refers to the ALERT Plus tables but also to the ALERT C table used to transmit possible encrypted events. The ACTN is a 6-bits code and is assigned by the data service provider. The ALTN is a 8-bits code. It means that each data service provider has 64 ACTN at his