ADASIS

ADASIS
Name	ADASIS
Type	Standard / Protocol
Industry	Automotive industry; Transport; Intelligent Transport Systems
Initial release	1990s–2000s

ADASIS

ADASIS is a family of interface specifications designed to provide a standardized communication link between digital map databases and Advanced Driver Assistance Systems used in Automotive industry and Intelligent Transport Systems applications. The specifications enable exchange of lane-level, sign, and manoeuvre guidance data between map suppliers, navigation systems, and driver assistance controllers, facilitating functions such as lane keeping, speed assistance, and predictive powertrain control. ADASIS complements standards from other bodies to support interoperable in-vehicle systems and cloud services across manufacturers and suppliers.

Overview

ADASIS defines a set of message formats and update mechanisms enabling a navigation or map server to provide lane-accurate attributes, sign information, and recommended maneuvers to vehicle automation and driver assistance functions. The specification is intended to interoperate with digital map formats from major map providers and align with standards from bodies such as ISO and UNECE. It supports the distribution of dynamic and static map elements that are crucial for Advanced driver-assistance systems such as lane departure warning and adaptive cruise control, and for higher levels of automation exemplified by projects from SAE International discussions.

History and Development

ADASIS emerged from collaborative efforts in the 1990s and 2000s among European automotive manufacturers, map suppliers, and standardization organizations to harmonize the interface between navigation and vehicle control functions. Early work drew on projects and consortia involving companies like Daimler AG, BMW, Volkswagen Group, and map vendors that coordinated through forums associated with ERTICO and pan-European initiatives. As digital cartography evolved alongside initiatives such as Tele Atlas and HERE Technologies, ADASIS evolved through successive revisions to accommodate lane-level geometry, traffic sign semantics, and dynamic update mechanisms influenced by research at institutions including TU Delft and KTH Royal Institute of Technology.

Technical Architecture and Protocols

The ADASIS architecture specifies client–server semantics where an in-vehicle ADAS client requests route- and lane-specific attributes from a navigation or map server. Messages are structured to convey map link identifiers, lane topology, permitted maneuvers, and sign attributes with timing and confidence metadata. ADASIS interfaces can operate over CAN bus backbones like CAN FD or automotive Ethernet technologies including Automotive Ethernet variants, leveraging transport layers standardized by groups such as AUTOSAR and IEEE 802.3. The protocol defines update rates, priority schemes, and fall-back behaviors to ensure deterministic delivery for safety-relevant functions, while aligning with data models from standards like ISO 26262 for functional safety considerations.

Operational Modes and Use Cases

ADASIS supports multiple operational modes, including embedded on-board navigation, map-on-chip architectures used by suppliers such as Continental AG and Bosch, and cloud-assisted deployments employed by services like TomTom and HERE Technologies. Use cases include lane-level turn advisory for navigation systems, predictive speed profile delivery for adaptive cruise control, regulatory sign provision for intelligent speed assistance mandated by regional bodies such as the European Commission, and high-definition map feeding for experimental automated driving pilots by OEMs like Volvo Cars and Ford Motor Company.

Implementation and Standards Compliance

Implementations of ADASIS must map ADASIS semantic elements to proprietary or open map schemas maintained by companies such as HERE Technologies, TomTom, and OpenStreetMap-based suppliers. Compliance activities often intersect with standardization work by UNECE WP.29, functional safety assessments under ISO 26262, and cybersecurity considerations outlined in ISO/SAE 21434. Toolchains for conversion and validation are provided by automotive suppliers and specialist integrators, with test suites typically referencing message timing and content conformance drawn from consortium agreements and normative annexes maintained by industry groups like CEN.

Industry Adoption and Deployments

ADASIS has seen adoption among European OEMs and tier-1 suppliers where interoperability between navigation and ADAS stacks is prioritized. Pilot and production deployments have been reported in conjunction with map updates provided by HERE Technologies and TomTom, integration work by suppliers such as Valeo and Magneti Marelli, and trials in regional testbeds coordinated by initiatives like C-Roads and European ITS deployments. Research partnerships with universities and labs, including TNO and Fraunhofer Society institutes, have accelerated feature sets for lane-level accuracy and harmonized update mechanisms across heterogeneous fleets.

Challenges and Future Directions

Challenges for ADASIS adoption include harmonizing semantic definitions across disparate map providers, ensuring real-time delivery over heterogeneous vehicle networks, and meeting stringent safety and cybersecurity requirements driven by regulators like UNECE. The rise of high-definition mapping and increasing use of edge/cloud hybrid architectures prompts evolution of ADASIS to support richer datasets, frequent incremental updates, and integration with perception stacks from suppliers such as Mobileye. Future directions include tighter alignment with AUTOSAR Adaptive Platform interfaces, support for coordinated fleet-level map updates in connected vehicle ecosystems championed by platforms like Car-to-X communications projects, and enhanced meta-data for automated driving features under development by OEM consortia including ACEA.

Category:Automotive standards