Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Designing Interoperable ITS Messages with the SAE J2540‑3 National Names Phrase List
The SAE J2540‑3 (2019) National Names Phrase List provides a standardized table of textual messages for expressing street and road names in Intelligent Transportation Systems (ITS). By assigning numeric indices to common name components—prefixes, main names, suffixes—the standard enables efficient message encoding while preserving full interoperability across devices, languages, and media. This article explains the purpose, structure, and engineering considerations behind this stabilized standard.
Overview and Purpose
The National Names Phrase List is designed for use in all Advanced Traveler Information Systems (ATIS) and other ITS standards. It follows the encoding and decoding rules of SAE J2540, ensuring that phrase indices can be mapped to local text in different languages or graphical representations. The list includes elements such as direction prefixes (e.g., “North”), main street names (e.g., “Oak”), and road type suffixes (e.g., “Street”). By indexing these components, messages can represent complex street names with just a few numbers, reducing bandwidth requirements and simplifying data processing.
This standard supersedes the 2002 edition and has been stabilized; implementers are responsible for verifying references and checking for newer technologies. The official tables are maintained in the ITS data registry and should be obtained from there for the most current version.
How It Works: Indexed Phrase Encoding
The core idea is that a small set of textual phrases covers the vast majority of street names used in traffic messages. Each phrase is assigned a unique numeric index. A street name like “North Oak Street” can be transmitted as the index sequence [3, 45, 78] (prefix, main, suffix). The receiver then looks up each index in its own localized table to produce the appropriate wording (still “North Oak Street” in English, but perhaps “Norte Roble Calle” in Spanish).
The table below shows example entries from the standard. Note that the actual indices and phrases are defined in the official registry.
| Index | Phrase | Type |
|---|---|---|
| 3 | North | Prefix |
| 45 | Oak | Main name |
| 78 | Street | Suffix |
| 16 | East | Prefix |
| 201 | Main | Main name |
| 89 | Avenue | Suffix |
The encoding follows the rules of SAE J2540, which governs how indices are separated from free text, how mixed sequences are handled, and how tables are registered. Systems that implement these rules can exchange messages reliably, even when the devices have different language or media capabilities.
Design Insights and Best Practices
🔍 Engineering Insight – The indexed phrase approach drastically reduces message payload size, especially for repetitive street name components. It also facilitates internationalization: the same numeric message can be displayed in any language for which a localized table exists. This is critical for cross-border ITS applications and multi‑lingual regions.
When using the National Names Phrase List, keep these points in mind:
- Use the latest tables – The ITS data registry is the authoritative source. Outdated tables may lack newly added phrases or conflict with current implementations.
- Follow SAE J2540 strictly – Any deviation in encoding or decoding can break interoperability. Pay particular attention to token delimiters and mixed free‑text sequences.
- Be aware of regional limitations – The standard list covers common North American street names; regional augmentations may be needed for local thoroughfares or unique naming conventions.
⚠️ RDS Limitation – This phrase list is not recommended for use in Radio Data System (RDS) channels due to severe bandwidth restrictions. For such low‑capacity media, consider alternative encoding strategies or a smaller, dedicated subset of phrases.
Frequently Asked Questions
How are street names encoded using indices?
The standard assigns numeric indices to common street name components (prefixes, main names, suffixes). To encode a street name, you send the sequence of indices for each component. The receiver maps each index to its local text representation, following SAE J2540 string rules.
What role does SAE J2540 play?
SAE J2540 defines the overarching rules for handling strings and look‑up tables in ATIS. It specifies how indices are separated from free text, how mixed sequences are structured, and how tables are registered and maintained. All implementations of the National Names Phrase List must comply with these rules to ensure cross‑device interoperability.
Can the phrase list be adapted for different languages?
Yes. The table structure allows each region or language to define its own mapping from indices to local text. The indices themselves remain the same, so a message sent from one country can be correctly displayed in another language as long as both sides use the same index set.
Where can I obtain the most recent set of tables?
The latest tables are maintained in the ITS data registry, jointly managed by SAE and other standards organizations. Always download the official tables from that registry to ensure you have the current, harmonized version.
By understanding and correctly applying the SAE J2540‑3 National Names Phrase List, ITS engineers can build systems that communicate street names reliably, efficiently, and across diverse languages and technologies.
