1、SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirelyvoluntary, and its applicability and suitability for any particular use, including any patent infringement arising therefro
2、m, is the sole responsibility of the user.”SAE reviews each technical report at least every five years at which time it may be reaffirmed, revised, or cancelled. SAE invites your written comments and suggestions.Copyright 2002 Society of Automotive Engineers, Inc.All rights reserved. No part of this
3、 publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying,recording, or otherwise, without the prior written permission of SAE.TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada)Tel: 724-776-4970 (o
4、utside USA)Fax: 724-776-0790Email: custsvcsae.orgSAE WEB ADDRESS: http:/www.sae.orgSURFACEVEHICLE400 Commonwealth Drive, Warrendale, PA 15096-0001STANDARDJ2540-1ISSUEDJUL2002Issued 2002-07RDS Phrase Lists TABLE OF CONTENTS1. Scope . 22. References . 22.1 Applicable Publications 22.2 Related Publicat
5、ions . 23. Definitions. 34. Overview 35. Operating Concepts . 35.1 Use in RDS Transmission Media 35.2 Use in General ITS Messages 45.3 Use in Operator Consoles 45.4 Formats of Tables 55.5 Supported Vocabularies and Alphabets . 55.6 Registering a Table within ITS 56. Tables . 56.1 The Non-Nested RDS
6、Table. 56.2 The Nested RDS Table 1096.3 The Non-Nested RDS Extended Phrases Table 2146.4 Table Registration Values 228Table 1 Header Elements of the Non-Nested RDS Table . 6Table 2 Body Elements of the Non-Nested RDS Table (in ASCII) 6Table 3 Body Elements of the Non-Nested RDS Table (in Modified AS
7、CII) . 36Table 4 Header Elements of the Nested RDS Table, Local Table 109Table 5 Body Elements of the Nested RDS Local Table (in ASCII) 110Table 6 Body Elements of the Nested RDS Local Table (in Modified ASCII) 111Table 7 Header Elements of the Nested RDS Table, CEN Table . 116Table 8 Body Elements
8、of the Nested RDS CEN Table (in ASCII) . 116Table 9 Body Elements of the Nested RDS CEN Table (in Modified ASCII). 144Table 10 Header Elements of the Non-Nested RDS Extended Phrases Table. 214SAE J2540-1 Issued JUL2002-2-Table 11 Body Elements of the Non-Nested RDS Extended Phrases Table (in ASCII)2
9、14Table 12 Body Elements of the Non-Nested RDS Extended Phrases Table (in Modified ASCII) .219Table 13 Table Registration Values.2281. ScopeThis SAE Standard provides a table of textual messages meeting the requirements for expressing“Radio Data Systems” (RDS) phrases commonly used in the ITS indust
10、ry. They can be used both over theRDS subcarrier transmission media as part of a 37-bit long “Group 8a message” as well as being used toprovide a common content list of phrases used in a wide number of other media and applications.This document SHALL define the normative index values to be used, ext
11、ending the CEN established list toprovide phrases needed by US practitioners. This standard provides non-normative textual phrases whichMAY be used by implementers to ensure intelligible results. This document SHALL follow the formats andrules established in SAE J2540 in the expressions, manipulatio
12、ns, and use of such tables.It should be pointed out that within the rules established by this document a variety of final table are allconsidered “compliant” with the document, and may vary as fits the needs of implementers.2. References2.1 Applicable PublicationsThe following publications form a pa
13、rt of this specification to the extent specifiedherein. Unless otherwise indicated, the latest version of SAE publications shall apply.2.1.1 SAE PUBLICATIONSAvailable from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001. SAEJ2369Standards for ATIS Message Sets Delivered Over Reduced Bandwidth
14、 MediaSAE J2354Message Sets for Advanced Traveler Information System (ATIS)SAE J2540Messages for Handling Strings and Look-Up Tables in ATIS StandardsSAE J2540-2ITIS Phrase Lists 2.2 Related PublicationsThe following publications are provided for information purposes only and are not arequired part
15、of this document. Unless otherwise indicated, the latest version of SAE publications shall apply.2.2.1 SAE PUBLICATIONSAvailable from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001.SAE J1746Draft ISP-Vehicle Location Referencing StandardSAE J2313On-Board Land Vehicle Mayday Reporting Interfa
16、ceSAE J2353Data Dictionary for Advanced Traveler Information Systems (ATIS)SAE J2374Information Report based on Location Reference Message Specification, Revision B (MDI)SAE J2540-3National Names Phrase List 2.2.2 GATS PUBLICATIONSAvailable from the GATS forum or from CEN TC278.GATS Message Set; Mai
17、n Part Main2034.pdf 05.08.99GATS Message Set; Annex 2 - Basic Information Elements A2_2033.pdf 05.08.992.2.3 FHWA PUBLICATIONSAvailable from Lee Simmons, FHWA, HVH-1 Room 3400, 400 7th Street SW,Washington, D.C. 20590.National ITS Architecture, Federal Highway Administration, U.S. Department of Tran
18、sportation, Version2.0, September 1998.SAE J2540-1 Issued JUL2002-3-2.2.4 ITE PUBLICATIONSAvailable from ITE, 525 School Street SW, Suite 410, Washington, DC 20024.Message Sets for External Traffic Management Center Communication (MS/ETMC2) TM2.01 Rev. 1.2February 1, 20012.2.5 CEN PUBLICATIONSAvaila
19、ble from CEN, 36 rue de Stassart, B-1050 Brussels, Belgium.Traffic and Traveller1 Information (TTI) TTI Messages via Traffic Message Coding- Part I: Codingprotocol for Radio Data Systems Traffic Message Channel (RDS-TMS) using ALERT-C, ISO/DIS14819-1, August 1999Traffic and Traveller Information (TT
20、I) TTI Messages via Traffic Message Coding- Part 2: Event andInformation codes for Traffic Message Channel (TMC), PrENV 12313-2, Version 1.0, June 19962.2.6 W3C PUBLICATIONSAvailable from W3C, www.wc3.org“Hypertext Transfer Protocol - HTTP/1.1 “, W3C - June 1999, RFC 2616, available at http:/www.w3.
21、org/Protocols/rfc2616/rfc2616.txt “HTML 4.0 Specification”, W3C - December 1997, revised 24 April 1998 available at http:/www.w3.org/TR/1998/REC-html40-19980424 HTML 4.0 Guidelines for Mobile Access W3C Note - 15 March 1999 available at http:/www.w3.org/TR/NOTE-html40-mobile Character Model for the
22、World Wide Web, World Wide Web Consortium Working Draft 29-November-1999available at http:/www.w3.org/TR/1999/WD-charmod-19991129/3. DefinitionsThe definitions found in SAE J2540 are incorporated herein.4. OverviewThis document provides a set of phrases intended to describe traffic incident situatio
23、ns of interestto the traveler. It is used in both the RDS media (where typically only a single message is allowed) as well asin other ITS message (where the allowed use typically involves the use of multiple indexes and inserted freetext). It also serves as a “prompting” text phrase in many traffic
24、systems operator console designs, which whensent may involve further translations.5. Operating ConceptsThis section outlines the use of the contents of the table messages and data elementstructures and provides an overview of the operational exchange used in message transactions.5.1 Use in RDS trans
25、mission mediaWhen used in RDS media the RDS phrase an 11-bit index values which iscontained in a 37-bit long message. This message format does not allow more than one index or any use oftext in its definitions. Consult the RDS documents and SAE J2540 for further information. The media itselfdoes not
26、 support the downloading of tables, and as a broadcast medium it is of course one-way, so it does notsupport the SAE J2540 message set for translating tables index into full strings. Hence, from a SASE J2540 point of view the theString element of the message is a “just-1-index” type. Thetable is not
27、 downloadable and is sparsely numbered in nature. Depending on which table set is used (two arepresented in Section 6) it may be either of the type which “can-reorder” (the US tables) or “never-ReOrder”(the CEN tables).In any event, the use of these phrases in an RDS message produces a single 11-bit
28、 index to represent thesingle phrase in question.1. European spelling of Traveler.SAE J2540-1 Issued JUL2002-4-5.2 Use in General ITS MessagesWhen used in general messages there are a number of patterns which areallowed to meeting user and data issuer needs. Consult SAE J2540 for a complete discussi
29、on of this,including the rules for using tokens to separate indexes from text. Conceptually two major types of use arefound:a. Strings which are mostly free text with the occasional index-phrases inserted as needed b. Strings which are mostly sequences of index-phrases with occasional free text inse
30、rted as needed In the case of the RDS table used in these types of messages, the actual phrases can be considered “startingpoints” from which additional information can be appended. Used in conjunction with the extended phrases,fairly complex descriptions can be created without the need for free tex
31、t. Typically this sort of use involves aninitial RDS phrase, followed by one or more of the extended phrases for example, RDS index # 983 “Spilledload on roadway. Caution” could be enhanced by the use of RDS Extended Phrase #170 which is “in theturning lane” .The reader will observe that many of the
32、 extended phrases terms have already been added to the RDS tablesas a way to embody these concepts for RDS medium users who cannot send the extended phrases. Newsystems should use the ITIS phrases to accomplish the same purpose but with even greater flexibility. Regardless of which specific table is
33、 used or which format of string content ordering is used, implementersSHALL follow the rules and process of SAE J2540 to insure that successful encoding and decoding of the datashall occur by any party using this document.In anticipation of making SAE ATIS messages more like those found in the rest
34、of ITS (notably TMDD in thiscase), it is recommended that implementers group message content into three distinct areas of “description ofthe event,” “cause of the event” and “advice regarding what to do” and append all three areas into a singletextual stream when the bearer message does not provide
35、separate areas for each of these. Further, betweenthe first and second items the phrase “Due to: “ should be inserted and between the last two the phrase“Advice: “ should be inserted. It is anticipated that future revisions of the ATIS standard will provide threedistinct places to insert SAE strings
36、 to be labeled description, cause and advice and that the last two will beoptional in nature. When mapping message content from another ITS message which supports this three-partconstruction to one which does not, the previous recommendation SHOULD be followed. 5.3 Use in Operator ConsolesThe RDS ph
37、rases (and to a lesser degree the extended phrase) have a longhistory of use in expression building aids and operator prompts in many console designs. This document doesnot specifically address this type of use with any requirements. Some general observations can be given.If the intended output of t
38、he operator data entry is text carried in any sort of ITS message, then considerationshould be given to the eventual encoding into tables of the type described here and in SAE J2540.Specifically, if free text is added “inside” such a phrase then the phrase is no longer identical to that used in thet
39、ables. For example, if an operator were presented with an RDS prompt that read “ Spilled load on roadway.Caution” and then inserted text to modify it as “Spilled load of Color TVs on roadway. Caution” and appendedcode 1472 “people on roadway” - the resulting codes that would be output would not be #
40、172 and #1472 withthe text “Color TVs “ as might be expected. Rather it is more likely that “Spilled load of Color TVs on roadway.Caution” would be sent as free text followed by index #1472. This is fine for some uses, and problematic forothers.1In general implementers should be aware that free text
41、, while offering the widest possible range of expression,is also at times hard to sort and classify by automated means. Some users (this is more the case with ITISphrases than in RDS) will want to parse the codes seen and ignore or take action based on them.Implementers should try to facilitate this
42、, even if their own user base will not be sorting on this.1. The astute reader will observe that the RDS phrases like #210 “Spilled Load” or a number of others could e used to good effect as well.SAE J2540-1 Issued JUL2002-5-Finally, consider the last paragraph in 5.2 regarding anticipated changes t
43、o existing ATIS (and other) ITSmessages to better clarify event description from cause and advice information. 5.4 Formats of TablesThe tables are presented in two ways, a non-nested set of tables and a nested set oftables. In both cases English textual expression are used. Implementers needing to k
44、eep track of CEN variants may wish to use the nested tables. Implementersoperating only in the US market can safely use the non-nested tables. In all cases, specific end using deviceswhich may have additional restrictions (e.g., small screen size), may need to develop tables that fit theirrequiremen
45、ts.Table nesting has not been used for simplicity. Some saving in memory space can be obtained at the expenseof more complex table expansion processing which can be obtained by this method. All strings are made up of“simple text” formatting. The value of entries which are found in the CEN table are
46、established as non-changing static values. The USadditions are subject to possible change in the future as CEN adopts them as well. This can be handled in anumber of ways, consult SAE J2540 for the methodologies used in revising table entries. 5.5 Supported Vocabularies and AlphabetsThe tables are e
47、xpressed in both ASCII and Modified ASCIIcharacter sets. As no diacritical marks are used, there was no need to use the Latin_1 character sets orUnicode.Example software algorithms to convert into and out of the modified ASCII character set can be found in SAEJ2369 Sections 10 and 11.5.6 Registering
48、 a Table within ITSThe presented tables are registered as per SAE J2540 as tables for nationaluse.Implementers wishing to further modify these entries (for example adding a new entry they feel is needed)SHALL follow the procedures outlined in SAE J2540 Section 5.7 and 5.8 and create such a table in
49、theregistration range appropriate for their use. It is recommend that such tables nest to the tables presented hererather than duplicate the information in a flat table of their own creation. 6. TablesThe messages of this standard support the distribution of tables to end using devices. They areintended to be implemented by any host media which can support them in cooperation with other messageswhich support the bulk of the ATIS content (see SAE J2354 and J2369). Some media will not be able tosupport table distribution (and are limited therefore
