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.TO PLACE A DOCUMENT ORDER: +1 (724) 776-4970 FAX: +1 (724) 776-0790SAE WEB ADDRESS http:
3、/www.sae.orgCopyright 2002 Society of Automotive Engineers, Inc.All rights reserved. Printed in U.S.A.SURFACEVEHICLE400 Commonwealth Drive, Warrendale, PA 15096-0001STANDARDJ2540-3ISSUEDJAN2002Issued 2002-01National Names Phrase List ForewordThis document is the list of phrases and textual entries f
4、or use in describing commonly occurring streetnames in ITS systems. It is intended for use in all ATIS systems along with the SAE J2540 string rules, but is alsoused in other ITS standards as well. The tables are structured to be in conformance with SAE J2540.TABLE OF CONTENTS1. Scope . 22. Referenc
5、es . 22.1 Applicable Publications 22.1 Related Publications . 23. Definitions. 24. Overview 25. Operating Concepts . 35.1 Use in General ITS Messages 35.2 Use in RDS Systems 35.3 Use in the GRID LRMS Profile . 35.4 Use in the ISP to Vehicle LRMS Profile 35.5 Use in the Map Fragments . 45.6 Use in th
6、e Descriptive Text. 45.7 Formats of Tables 45.8 Supported Vocabularies and Alphabets . 45.9 Registering a Table within ITS 46. Tables . 46.1 The Non-Nested ITIS Table 56.2 Table Registration Values 6Table 1 Header Elements of the National names Table 5Table 2 Partial List of Body Elements of the Nat
7、ional Names Table . 5Table 3 Header Elements of the National Names Tables, First 255 Entries . 6Table 4 Table Registration Values 6SAE J2540-3 Issued JAN2002-2-1. ScopeThis SAE Standard provides a table of textual messages meeting the requirements for expressing thenames of street and roads and some
8、 basic building blocks for phrases commonly used in the ITS industry.The tables provided herein are taken from SAE J2369, and follow the rules of SAE J2540 and therefore allow alocal representation in various different languages, media expressions, etc. to allow true international use ofthese phrase
9、s. The phrases are predominantly intended to provide a means to express street names includingpre and post fixes ( North Oak Street is an example name with a prefix “North” and main portion “Oak” and asuffix “Street”). Other phrases exist for other specific specialty areas of ITS, and all such phras
10、es follow a setof encoding and decoding rules outlined in SAE J2540 to ensure that the use of these phrases in messagesremain interoperable between disparate types of user equipment.Implementers are cautioned to obtain the most recent set of tables by means of the ITS data registry, aprocess which i
11、nvolves the SAE and other standards setting organizations and which is intended to maintainand enhance the level of harmonization between ITS standards set by each of the organizations.This document SHALL define the normative index values to be used to provide phrases needed by ITSpractitioners when
12、 expressing the names of streets using indexed methods. This document SHALL follow theformats and rules established in SAE J2540 in the expressions, manipulations, and use of such tables.2. References2.1 Applicable PublicationsThe following publications form a part of this specification to the exten
13、t 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.SAE J2354Message Sets for Advanced Traveler Information System (ATIS)SAE J2369Standards for ATIS Message Sets
14、Delivered Over Reduced Bandwidth MediaSAE J2540 DraftMessages for Handling Strings and Look-Up Tables in ATIS Standards2.2 Related PublicationsThe following publications are provided for information purposes only and are not arequired part of this specification.SAE J1746ISP-Vehicle Location Referenc
15、ing StandardSAE J2313On-Board Land Vehicle Mayday Reporting InterfaceSAE J2374Information Report based on Location Reference Message Specification3. DefinitionsThe definitions found in SAE J2540 and SAE J2369 are incorporated herein.4. OverviewThis document provides a set of phrases intended to desc
16、ribe the names of streets of interest tothe traveler. It is intended to be used in all ATIS message set standards, and is expected to be also used in anumber of other ITS industry standards as well. The specific rules of use can be found in the standard describing the message which uses these phrase
17、s. Thisdocument defines the phrases themselves. The SAE J2540 document defines the use of the phrases inpractice, while each using standards defines the placement of the phrases in a message and any additionalrestrictions which are needed. Thus, all uses of the phrases adhere to the rule set defined
18、 in SAE J2540, butnot all messages, or all media, allow support for the full set of possible features. Consult the specific standardfor complete rules and restrictions with regard to using the phrases. SAE J2540-3 Issued JAN2002-3-5. Operating ConceptsThis section outlines the use of the contents of
19、 the table messages and data elementstructures and provides an overview of the operational exchange used in message transactions.5.1 Use in General ITS messagesThe basic concept of the ITIS phrases is that a collection of short textualphrases can be used the vast majority of the time to express comm
20、on traffic situations and can be easily codedand therefore standardized as a sequence of numbers. Various uses of these numbers can then occur at thereceived end. For the purposes of a preliminary operating concept, we will consider that they are simplyreconstituted into the same textual phrases at
21、the receiver.The purpose of this document is simply to establish the best possible set of such phrases, specifically for theuse in describing street names. Systems using the cross street methods, sending map fragments, orotherwise using such names in descriptions will benefit from using this standar
22、d. Devices which are morelimited in memory capacity will probably not make use of this standard (which requires just under 32k ofmemory space to hold the list itself).When used in general messages there are a number of patterns which are allowed in order to meet user anddata issuer needs. Consult SA
23、E J2540 for a complete discussion of this, including the rules for using tokens toseparate indexes from text. Conceptually two major types of uses are found:a. Strings which are mostly free text with the occasional index-phrases inserted as needed b. Strings which are mostly sequences of index-phras
24、es with occasional free text inserted as needed The latter is most common for descriptive textual use (such as incidents) and SHOULD be preferred when datacreation implementers have a choice. The latter SHOULD be preferred when encoding street names.Implementers of data reception equipment should be
25、 prepared to accept any valid J2540 format.The list itself can be regionally augmented as needed so that the vast majority of all street names to be issuedare capable of being encoded in only a few index sequences. Regardless of which format of string content ordering is used, implementers SHALL fol
26、low the rules andprocess of SAE J2540 to insure that successful encoding and decoding of the data shall occur by any partyusing this standard.5.2 Use in RDS systemsThis table of lists is NOT recommended for use in RDS systems. The restrictedbandwidth of such systems makes it very unlikely that any f
27、orm of vehicle cross street type of message wouldbe carried on it.5.3 Use in the GRID LRMS ProfileThe GRID profile is a compressed LRMS format which contains an offsetfrom a known local point and one or more optional street names. The use of this list SHALL be as specified inSAE J2369 for GRID profi
28、les. Note that GRID entries can be expanded and translated into and out of the ISPto Vehicle profile (ISPV) as needed. Note that SAE J2369 allows only a subset of the properties of SAEJ2540. Notably, it only allows four tables, and of these all but the single local table are predefined. Note also th
29、at exception tokens are used to achieve capitalization and spacing in this message type, thus aphrase like “Main” is derived with a preceding exception token of 0xEF which indicates by the last two bitse.g, 0b11 that the first letter is to be capitalized and a trailing space is to be added. Refer to
30、 SAE J2369Tables 7 to 9 for further information.5.4 Use in the ISP to Vehicle LRMS ProfileThe ISPV profile is the preferred format for sending data to mobileusers developed by the SAE Map database committee. It contains sets of location data (Lat - long) and one ormore optional street names. The str
31、eet names can be expressed in “free text” (table type #0) or using themethods of SAE J2540 and this list. Note that ISPV entries can be expanded and translated into and out ofthe GRID profile as needed. SAE J2540-3 Issued JAN2002-4-5.5 Use in the Map FragmentsSome SAE messages allow for the creation
32、 of ad hoc small maps to be sent.Such fragments can be used to construct small maps used for providing information on detours, on routes, ofprimary roadways conditions, etc. When used in constructing a “map fragment“ using the GRID formats, thislist SHALL be used to express any street names required
33、, if the receiving device can be presumed to haveaccess to this table. 5.6 Use in the Descriptive TextWhen used in constructing phrases which contain the name of a street, this listMAY be used if the receiving device can be presumed to have access to this list. Some devices will not, and ifthe index
34、 translation messages of SAE J2540 are provided, is MAY be acceptable to use index in such cases.In general, such a use would include the combined use of the street name where the event occurred andphrases taken from the ITIS lists to provide the description (e.g., “Roadway Closed at Main Street use
35、 OakStreet exit”). Note that exception tokens are used to achieve capitalization and spacing in this message type.5.7 Formats of TablesThe tables are presented as a non-nested set of tables. Common American Englishtextual expressions are used throughout. All strings are made up of “simple text” form
36、atting.The names on this list were originally generated by an exhaustive sort and counting performed on the USTIGER Census data for America. Top occurring names were kept, while less frequently occurring names(including very common but regional names) were eliminated. The first 255 entries were then
37、 computed to bethe most common pre and post fix words (Drive, West, Pkwy, Road, etc.) and also commonly occurringincident phrases (e.g., accident, until, spilled, etc.). Consult J2369 for more information. The table is presented as a single list, however the first 255 entries can be used in a “stand
38、alone” mode ifdesired. See Tables 74 and 75 of SAE J2369 for further information on this use. When stored this way, theshorter table has a unique table number and table header, see Tables 3 and 4 in Section 6. Table nesting has not been used for simplicity. As this table contains simple root words,
39、nesting opportunitiesare slight as compared to other tables. Some slight saving in memory space can be obtained at the expenseof more complex table expansion processing which can be obtained by this method. 5.8 Supported Vocabularies and AlphabetsThe tables are expressed in both ASCII and Modified A
40、SCIIcharacter 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.9 Registering a Table within ITSThe presented tab
41、les are registered as per SAE J2540 as tables for nationaluse. Implementers SHALL NOT further modify these entries (for example adding a new entry). Any modificationshall be done by use of local tables and SHALL follow the procedures outlined in SAE J2540 Sections 5.7 and5.8 and SHALL create such a
42、table in the registration range appropriate for their use. 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 ITS m
43、essage content (see SAE J2354 and SAE J2369 as well as others). Somemedia will not be able to support table distribution (and are limited therefore to the static use of such tables).SAE J2540-3 Issued JAN2002-5-6.1 The Non-Nested ITIS TableThe table message is the message used to convey the complete
44、 data of a tableto the end-using device. It contains both the table header and the table entries and is defined as follows.ATIS applications in conformance with this and other SAE standards will require this table to successfullydecode the strings found in them. The header for this table SHALL be de
45、fined as follows in Table 1.The body for this table is a dense type table and SHALL be defined as found in SAE J2369 Appendix A.1Listof National Table Entries and Encodings. The termination character for each entry shall be the value 0x00.The CRC value shall be as specified per Section 7.18 of SAE J
46、2540. A portion of this table is printed in Table2. The first 255 entries of the same table may also be used in a standalone mode. The resulting table header forthis is provided as follows. The CRC value shall be as specified per Section 7.18 of SAE J2540. TABLE 1HEADER ELEMENTS OF THE NATIONAL NAME
47、S TABLEHeader Element Value Commentaryregistration 0x10 Table Registration ValueFlags 0x00 Local-Table-Flagsstart-index 0x00 Index-Startstop-index 0x00 Index-Stop,count 0x00 Index-Counttype 0x00,00,00 Textualthis-table 0x00,00,00 Table-Entrytable-1 0x00,00,00 Table-Entrytable-2 0x00,00,00 Table-Entr
48、ytable-3 0x00,00,00 Table-Entrytable-4 0x00,00,00 Table-Entrycrc As below Values are given below for each tableTABLE 2PARTIAL LIST OF BODY ELEMENTS OF THE NATIONAL NAMES TABLEIndex Value String Compression Table Entry1 :0x 01 accident accident 82-63-A9-9A-742 :0x 02 ahead ahead 61-A4-833 :0x 03 aler
49、t alert 85-9B-744 :0x 04 Alley Alley 41-B8-65-795 :0x 05 Alt Alt 41-6C-746 :0x 06 Alternate Alternate 41-6C-E8-DB-8A-657 :0x 07 Arroyo Arroyo 41-72-DC-79-6F8 :0x 08 available available 61-76-84-B4-62-B6Break (200 pages removed)50 :0x 13BE54zephyr zephyr 7A-65-70-68-79-7250 :0x 13BF55zimmerman zimmerman 7A-AD-BC-72-BB-6E50 :0x 13C056zinnia zinnia 7A-AE-C4-6150 :0x 13C157zion zion 7A-AF-6E50 :0x 13C258zoar zoar 7A-6F-8850 :0x 13C359zuni zuni 7A-F0-69SAE J2540-3 Issued JAN2002-6-The h
