Comparison of GATS Messages to SAE ATIS Standards: Harmonization Insights for Global Telematics

The Global Automotive Telematics Standard (GATS) represents a comprehensive message set designed for deployment on GSM-based mobile phone systems in European markets. Meanwhile, the SAE ATIS family of standards (J2313, J2353, J2354, J2369, J2374) defines comparable traveler information services for U.S. deployments. SAE J2539-2019 provides a detailed function-by-function comparison of these two approaches, highlighting harmonization opportunities for world ATIS. This article summarizes the key findings and offers engineering guidance for aligning U.S. and European telematics standards.

Overview of GATS and SAE ATIS Standards

SAE J2539 was developed by the SAE ATIS Committee to support deliberations on world ATIS harmonization. It covers a wide range of services including MAYDAY, interactive and broadcast traffic information, navigation, floating car data (vehicle probes), parking, transit, weather, and general information services. The standard is stabilized as of 2019, meaning it is no longer actively maintained, but it remains a valuable reference for understanding the landscape of telematics standards.

⚠️ Important Note: SAE J2539 is stabilized and not subjected to periodic reviews. Users must verify the continued suitability of referenced standards and consider newer technologies. However, the document offers timeless insights into the alignment between GATS and SAE ATIS.

Key Service-by-Service Comparison

The GATS implementation of ITS functions was compared against corresponding SAE standards. The table below summarizes the major areas of comparison:

ServiceSAE ATIS StandardGATS EquivalentKey Observations
MAYDAYJ2313GATS MAYDAY messagesGATS includes more comprehensive data elements tailored for GSM networks, such as specific location and vehicle data.
Interactive TrafficJ2354GATS interactive traffic messagesGATS utilizes EDIFACT message types, while SAE ATIS uses ASN.1; differences in tagging and data structures.
Broadcast TrafficJ2369GATS broadcast traffic messagesBoth address reduced bandwidth; GATS offers more detailed event and status messages.
NavigationJ2354GATS navigation messagesLocation referencing formats differ (e.g., SAE J2374 based vs. GATS LRMS); harmonization needed.
ParkingJ2354GATS parking messagesGATS provides richer data structures for parking lot availability and pricing.
TransitJ2354, J2369, NTCIPGATS transit messagesGATS includes specific transit information messages (e.g., schedule, route data).
WeatherJ2354, J2369GATS weather messagesSimilar coverage but different encoding methods.

This comparison reveals that while the functional scope is largely overlapping, GATS often introduces richer data types and different encoding approaches that could enhance U.S. deployments.

🛠️ Engineering Design Insights and Recommendations

Engineers designing ATIS systems for international markets should consider both U.S. SAE standards and GATS. Key areas where harmonization can simplify cross-regional deployment include:

  • Language support and character encoding.
  • Basic data elements and common dictionaries (e.g., using EDIFACT concepts).
  • Tagging formats and location referencing (e.g., aligning J2374 with LRMS).
  • Service-specific messages for MAYDAY, traffic, parking, and other functions.
💡 Harmonization Opportunity: Adopting common concepts from GATS, such as enriched location referencing and standardized EDIFACT message types, can significantly reduce integration complexity when deploying telematics services that operate across U.S. and European markets.

The standard includes recommendations for changes to U.S. ATIS, emphasizing the adoption of GATS features like expanded data elements and harmonized naming conventions. These insights can guide future revisions of SAE standards.

Frequently Asked Questions

1. What is GATS and how does it relate to SAE ATIS?

GATS (Global Automotive Telematics Standard) is a European message set designed for GSM mobile phone systems. SAE ATIS standards define similar traveler information services for the U.S. market. SAE J2539 compares the two to identify harmonization paths.

2. Why is harmonization between U.S. and European telematics standards important?

Harmonization ensures that telematics devices and services can interoperate globally. With increasing international travel and connected vehicle deployments, common standards reduce development costs and improve user experience.

3. What are the main differences in message sets for services like MAYDAY and traffic information?

While both standards cover similar functions, GATS often uses EDIFACT encoding and includes more detailed data elements (e.g., for vehicle status in MAYDAY). Location referencing methods also differ, impacting interoperability.

4. How should engineers approach using SAE J2539 given its stabilized status?

Engineers should treat J2539 as a historical reference and comparative analysis. It is not a current working standard, but its recommendations can inform system design. Always check for the latest versions of referenced SAE and GATS documents.

By understanding the parallels and divergences between GATS and SAE ATIS, engineers can build more robust and globally compatible telematics systems. While SAE J2539 is no longer updated, its analysis remains a cornerstone for harmonization efforts.

📥 Standard Documents Download

🔒
Please wait 10 seconds, the download links will appear after the ad loads

Leave a Reply

Your email address will not be published. Required fields are marked *