Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/TS 29843-1 — Intelligent Transport Systems — Mobility Integration — Part 1: Framework and Reference Architecture
A Comprehensive Technical Guide for Engineers and System Architects
Introduction to ISO/TS 29843-1: Intelligent Transport Systems — Mobility Integration — Part 1: Framework and Reference Architecture
ISO/TS 29843-1 establishes the foundational framework and reference architecture for mobility integration within Intelligent Transport Systems. Part 1 of this two-part Technical Specification defines the overarching principles, system boundaries, functional domains, and information flows necessary to create a seamless, multimodal mobility ecosystem. It addresses the growing need for standardized integration of diverse mobility services — including public transit, ride-hailing, car-sharing, micro-mobility, and traditional private transport — into a coherent, user-centric mobility platform.
The reference architecture in ISO/TS 29843-1 employs a layered approach separating infrastructure, service provision, and user interaction domains. Engineers implementing mobility platforms should map each functional component to the appropriate layer to ensure clean interfaces and maintainable system evolution as new mobility services emerge.
The specification defines four primary functional domains: the Mobility Service Domain (MSD), the Transport Infrastructure Domain (TID), the Data Exchange Domain (DED), and the User Interaction Domain (UID). Each domain encapsulates specific capabilities with well-defined interfaces to adjacent domains. This architectural separation enables independent evolution of each domain while maintaining overall system coherence through standardized communication protocols and data models.
Core Functional Domains and Interfaces
ISO/TS 29843-1 provides detailed specifications for each functional domain and the interfaces between them. The Mobility Service Domain encompasses all mobility service providers — from public transit authorities to private mobility operators. The Transport Infrastructure Domain covers physical infrastructure elements including roads, parking facilities, charging stations for electric vehicles, and traffic management systems. The Data Exchange Domain functions as the semantic middleware that enables service discovery, trip planning, booking, payment, and real-time status exchange across domains.
| Functional Domain | Core Capabilities | Interface Standards | Data Exchange Requirements |
|---|---|---|---|
| Mobility Service Domain (MSD) | Service registration, availability management, booking handling, fare calculation | Open API specification (RESTful), GTFS-compatible schedule data | Real-time availability updates ≤5 second latency, transactional booking acknowledgment ≤2 seconds |
| Transport Infrastructure Domain (TID) | Traffic signal status, parking availability, EV charging status, road condition monitoring | DATEX II, NTCIP, OCPI for EV charging | Infrastructure status updates ≤10 second latency, historical data batch retention ≥24 months |
| Data Exchange Domain (DED) | Service registry, semantic mediation, identity management, clearing and settlement | OAuth 2.0 / OpenID Connect for authentication, JSON-LD for semantic interoperability | Transaction logging with full audit trail; data anonymization for privacy compliance |
| User Interaction Domain (UID) | Multimodal trip planning, personalized recommendations, unified payment, accessibility support | WAI-ARIA for accessibility, Progressive Web App standards | User preference storage (opt-in only), trip history ≤90 days for non-authenticated users |
Multimodal Trip Planning and Execution
A central feature of ISO/TS 29843-1 is the multimodal trip planning framework. The specification defines a standard trip request format that captures origin, destination, time constraints, user preferences (cost minimization, time minimization, accessibility requirements, environmental impact), and mobility service constraints. The framework supports both single-provider trips and complex multi-leg journeys combining different mobility services.
When implementing multimodal trip planning according to ISO/TS 29843-1, engineers must handle the critical challenge of temporal validity — the offered trip plan must be executable within the time window during which all constituent services (e.g., a specific bus departure, a car-share reservation, a train connection) remain available. This requires real-time reservation locking mechanisms and fallback re-planning when services become unavailable.
The trip execution phase defines protocols for real-time journey tracking, service handover between different mobility providers at interchange points, and exception handling when services are delayed or cancelled. The specification requires that the platform maintain awareness of the user’s current journey status and proactively provide alternative arrangements when disruptions occur, with maximum re-planning latency of 15 seconds.
Cities that have implemented mobility platforms aligned with ISO/TS 29843-1 principles report an average 12-18% modal shift from private car use to sustainable mobility options within the first two years of operation. The key enabler is the reduction of friction in multimodal journeys — single sign-on, unified payment, and real-time coordination across services reduce the cognitive and transactional overhead that previously discouraged users from combining different mobility modes.
Data Governance and Interoperability
The specification establishes comprehensive data governance principles including data ownership, usage rights, privacy protection, and quality management. Each data-producing entity retains ownership of its data, while the Data Exchange Domain manages access rights based on a role-based permission model. ISO/TS 29843-1 mandates support for three data sharing categories: open data (publicly available), shared data (available under defined terms between authorized parties), and protected data (access restricted by regulation or commercial sensitivity).
A critical implementation risk in mobility integration platforms is the cascading failure scenario where a failure in one service provider’s system propagates through the Data Exchange Domain and affects the entire mobility ecosystem. ISO/TS 29843-1 requires that the DED implement bulkhead isolation patterns — each service provider connection operates within a dedicated resource boundary with strict circuit-breaking thresholds. If a provider exceeds latency or error rate thresholds, that provider is automatically isolated without degrading service from other providers.
Frequently Asked Questions
Q: How does ISO/TS 29843-1 relate to Mobility as a Service (MaaS) frameworks?
A: ISO/TS 29843-1 provides the technical foundation that enables MaaS implementations. While MaaS is a business and service concept focused on user experience and service integration, this Technical Specification defines the specific protocols, data models, and architectural patterns needed to make MaaS technically feasible across different jurisdictions and mobility providers.
Q: Does ISO/TS 29843-1 require a centralized platform architecture?
A: No. The reference architecture supports both centralized and federated deployment models. In a federated model, each mobility provider hosts its own service domain, and the Data Exchange Domain operates as a distributed network using blockchain or similar consensus mechanisms for transaction integrity. The specification deliberately avoids mandating a specific deployment topology to accommodate different regulatory environments and market structures.
Q: What accessibility requirements does ISO/TS 29843-1 impose?
A: The specification requires that all user-facing interfaces comply with WAI-ARIA guidelines and support multiple interaction modalities (touch, voice, switch control). Trip planning must accommodate accessibility constraints including wheelchair-accessible vehicles, step-free access at interchange points, and sufficient transfer times for users with reduced mobility. Mobility service providers must publish accessibility metadata alongside their service availability data.
