Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
SAE J2352-1998: Validating Mayday System Architectures Through Industry Survey
In 1997, the SAE In-Vehicle Systems Interface Committee conducted a survey of Mayday system manufacturers to determine whether the emerging SAE J2313 message set architecture aligned with commercial designs. The results, published as SAE J2352-1998, provided critical insights into the state of in-vehicle emergency call technology and helped shape standardization efforts for interoperable Mayday systems.
Survey Background and Purpose
The survey targeted hardware manufacturers of Mayday systems—devices that automatically or manually initiate an emergency call from a vehicle. Of thirteen identified companies, six participated fully. The primary goal was to confirm that the generic system model proposed in SAE J2313 matched real-world implementations. Questions covered deployment type, location technology, user interface, services, call taking, and interfaces needing standards.
Scope Note: The survey focused on vehicle and on-board system operations, not service providers or Public Safety Answering Points (PSAPs). Complementary studies by organizations like NENA would be needed for a complete end-to-end perspective.
Key Findings on Mayday System Design
The survey responses revealed a consistent alignment with the generic system architecture. The following table summarizes the answers to the core questionnaire items.
| Question | Summary of Answers |
|---|---|
| Type of deployment | 5 private, 1 private/public partnership |
| Complies with generic system model | All 6 said yes |
| Location determination technology | 4 GPS only, 2 GPS + dead reckoning |
| Driver/user in-vehicle interface | 5 push button, 3 dialed sequence, 4 automatic trigger, 0 voice command |
| User services provided | Roadside assistance (5), theft protection (4), route guidance (3), remote door (3), concierge (2), service locator (3) |
| How services are accessed | 4 by voice, 5 by pressing buttons |
| Call takers (answer point type) | 3 use own, 3 use outside/PSAPs |
| Can call taker 3-way with PSAP and vehicle | 4 yes, 2 no |
| Does system provide non-voice data | 3 yes, 3 no |
| Interface with traffic management agencies directly | 4 yes, 1 no |
| Interfaces that could benefit from standards | In-vehicle electronics (4), PSAP procedures (2), cellular system (2), vehicle message set (2) |
Notably, all respondents confirmed that their system architectures complied with the generic model used for the J2313 message set. This validation gave confidence that the message set would be applicable across commercial designs. Engineering design insight: The consensus among manufacturers indicated that the technical approach underlying the message set—being architecture-neutral—posed no significant concerns.
GPS was the dominant location technology, though several implementers supplemented it with dead reckoning to overcome limitations like signal loss or multipath. Most recognized GPS limitations as a response center issue, but the trend was toward integrating more robust positioning.
Engineering Insights and Trends
Several important themes emerged from the survey that have implications for ongoing and future standardization.
User Interface Diversity and Standardization Potential
While push-button activation was most common, automatic triggering (e.g., via airbag sensors) was emerging. This raised liability concerns that SAE and NENA had not yet fully addressed. The variety of interfaces suggests that standardizing the user interaction—so drivers can activate emergency calls consistently across vehicles—could be beneficial. The ITS Human Factors committee was flagged as a potential lead.
⚠️ Liability Considerations: Automatically dialing 911 or attaching to the vehicle’s supplemental restraint system (SRS) introduces liability risks. At the time of the survey, neither SAE nor NENA had developed policies for these operational choices.
Call Taking and Data Integration
The split between private call takers and PSAPs, along with the three-way calling capability, highlighted the need for procedural standards at local jurisdiction levels. Non-voice data was offered by half the respondents, but its value depends on PSAP capability to receive it. Direct interface with traffic management centers was common, but the depth of integration varied.
Future Trends: Multi-Function Devices and Modular Services
Verbal comments from manufacturers predicted an increase in multi-function telematics devices that include Mayday as one of several services. The survey also indicated that consumers might eventually choose their service providers independently from equipment purchase, driving further diversification of service offerings.
Frequently Asked Questions
What location technologies were prevalent in 1997 Mayday systems?
GPS was used by all respondents, with dead reckoning added in two cases to address GPS drawbacks. The industry recognized that location determination is a critical component and that standards must accommodate evolving technologies.
Why is user interface standardization important for Mayday systems?
Because drivers may operate different vehicles, a consistent activation method reduces confusion and potentially faster emergency response. The survey showed a mix of push buttons, dialed sequences, and automatic triggers, supporting the argument for human factors research into standardized interfaces.
What were the main liability concerns identified in the survey?
Automatically triggered Mayday calls (e.g., via SRS) could lead to accidental activations or false alarms, and direct dialing of 911 without proper call-taking procedures raised unresolved liability issues. Standardization of interfaces and procedures was seen as a path to mitigate these risks.
How did the survey influence the SAE J2313 message set development?
By confirming that the generic system architecture was consistent with commercial designs, the survey validated the technical direction of the message set. It also pointed to areas—like in-vehicle electronics interfaces and PSAP procedures—where additional standards were needed.
🛠️ These findings from the 1997 survey remain relevant as a foundation for understanding the early challenges and design trade-offs in emergency call systems. They continue to inform discussions on interoperability, liability, and the evolution of telematics.
