Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/TS 29843-2 — Intelligent Transport Systems — Mobility Integration — Part 2: Data Models and Communication Protocols
A Comprehensive Technical Guide for Engineers and System Architects
Introduction to ISO/TS 29843-2: Intelligent Transport Systems — Mobility Integration — Part 2: Data Models and Communication Protocols
ISO/TS 29843-2 is the companion Technical Specification to Part 1, providing the detailed data models, communication protocols, and message formats necessary to implement the mobility integration framework defined in ISO/TS 29843-1. While Part 1 establishes the architectural blueprint, Part 2 delivers the concrete technical specifications that enable system developers to build interoperable mobility platform components. This includes standardized data schemas for service discovery, trip planning, booking, payment, and real-time operational status exchange.
The data models defined in ISO/TS 29843-2 leverage a semantic ontology approach based on the Transmodel standard (EN 12896) and extended with mobility-specific concepts. This enables automatic validation of data consistency across different service providers and reduces integration testing effort by approximately 40% compared to projects using proprietary data formats.
The specification covers six primary data domains: service offering data, network and timetable data, trip plan data, booking and payment data, real-time operational data, and user profile data. Each domain is defined using an abstract data modeling approach (UML class diagrams) with concrete serializations specified for both JSON and XML formats, ensuring broad compatibility across different technology stacks.
Core Data Models and Their Relationships
ISO/TS 29843-2 defines a comprehensive set of data entities with explicit relationships and integrity constraints. The central entity is the MobilityService, which represents any transport service offered to users. Each MobilityService has attributes including service type (bus, train, ride-hail, bike-share, etc.), operator, service area, schedule, fare structure, and accessibility characteristics. MobilityServices are organized into ServiceNetworks that represent the physical or logical infrastructure over which services operate.
| Data Entity | Key Attributes | Relationships | Validation Rules |
|---|---|---|---|
| MobilityService | serviceID, serviceType, operatorID, status, fareModel, accessibilityLevel | Belongs to ServiceNetwork; has ServiceSchedule; participates in ServiceOffering | serviceType must be from controlled vocabulary; fareModel must include base currency and pricing structure |
| ServiceSchedule | validFrom, validUntil, daysOfOperation, timeTableEntries | Referenced by MobilityService; linked to JourneyPattern | No overlapping validity periods for same service; timetable entries must be chronologically ordered |
| TripPlan | planID, origin, destination, departure/arrival time, legs[ ], totalCost, totalDuration | Composed of TripLegs; each TripLeg references a MobilityService | Transfer time between legs ≥ minimum transfer time; total duration ≤ requested maximum |
| Booking | bookingID, userID, planID, status, paymentReference, createdTimestamp | References TripPlan; associated with PaymentTransaction; linked to UserProfile | Single booking cannot exceed 24 hours before first departure; cancellation must be permitted up to minimum cancellation notice |
| RealtimeStatus | entityID, timestamp, statusCode, delay, position, occupancyLevel | May reference MobilityService, TripLeg, or InfrastructureElement | Status updates must be timestamped with actual observation time; delay values relative to scheduled time |
Communication Protocols and Message Flows
The specification defines synchronous and asynchronous communication patterns for different integration scenarios. Synchronous RESTful APIs are specified for request-response interactions such as service discovery, trip planning queries, and booking confirmations. Asynchronous messaging using MQTT or AMQP is specified for real-time status updates, disruption notifications, and position reporting. ISO/TS 29843-2 also defines a webhook mechanism for event-driven notifications, enabling service providers to push critical events (service cancellations, capacity changes) to subscribed platforms.
When implementing the real-time status update protocol, engineers should consider using a publish-subscribe pattern with topic-based filtering. ISO/TS 29843-2 recommends organizing topics hierarchically (e.g., /mobility/{region}/{provider}/{serviceType}/{serviceID}/status) to enable fine-grained subscription control and efficient message routing. This approach reduces bandwidth consumption by ensuring clients only receive updates relevant to their operational context.
The message flow for a typical multimodal journey involves several sequential interactions. First, the user submits a trip planning request containing origin, destination, and preferences. The platform queries registered MobilityServices, generates candidate TripPlans, and returns them ranked by user criteria. When the user selects and confirms a plan, Booking requests are sent to each relevant service provider. Upon confirmation, the platform monitors RealtimeStatus for each TripLeg and proactively notifies the user of any disruptions requiring alternative arrangements.
Security, Privacy, and Data Quality
ISO/TS 29843-2 mandates comprehensive security measures including TLS 1.3 for all communication channels, OAuth 2.0 with OpenID Connect for authentication and authorization, and message-level signing for non-repudiation in financial transactions. The standard also defines data quality requirements, including accuracy (position data must be within 10 meters of actual location), completeness (all mandatory fields must be populated), timeliness (real-time data latency must not exceed 10 seconds), and consistency (referential integrity must be maintained across data entities).
A frequently underestimated challenge in mobility data integration is temporal data alignment. Different service providers may use different clock sources with varying degrees of drift. ISO/TS 29843-2 requires that all timestamped data use UTC with microsecond precision and that each service provider implement NTP synchronization with stratum-2 or better time sources. Engineers must also handle the edge cases of clock skew during daylight saving time transitions and across international date boundaries.
Privacy protection follows the principles of data minimization and purpose limitation. User profile data is classified into mandatory fields (necessary for service provision), optional fields (enhance service quality), and sensitive fields (subject to additional consent requirements). The standard requires that personally identifiable information be pseudonymized in all data exchanges between domains, with full anonymization for data used in analytics and reporting.
ISO/TS 29843-2 identifies a specific security vulnerability in the trip planning protocol: an attacker could submit a large number of trip planning requests to infer user movement patterns or to exhaust platform resources. The standard requires implementors to deploy rate limiting with per-user and per-IP quotas, input validation on all request parameters to prevent injection attacks, and anomaly detection systems that identify and block abusive query patterns. Rate limiting thresholds must be configurable by platform operators and communicated transparently in API documentation.
Frequently Asked Questions
Q: How does ISO/TS 29843-2 handle fare calculation and payment across multiple service providers?
A: The specification defines a clearing house model where each Booking includes a fare component with the service provider’s price, any platform fees, and applicable discounts. The platform aggregates these into a single user-facing price. Settlement between providers and the platform operator uses a standardized clearing message format with reconciliation periods configurable from daily to monthly.
Q: What happens when a service provider’s real-time data feed goes offline?
A: ISO/TS 29843-2 requires that the platform maintain a local cache of the last known schedule and status for each service provider. When the real-time feed is unavailable, the platform falls back to scheduled data and marks all real-time-dependent features (live position tracking, delay predictions) as unavailable for that provider. The provider’s connection health is monitored with automatic reconnection attempts at 30-second intervals. If the outage exceeds a configurable threshold (typically 15 minutes), the platform may suspend trip planning involving that provider.
Q: Does ISO/TS 29843-2 support offline operation for mobile applications?
A: Yes. The specification includes a cache synchronization protocol that enables mobile apps to download service schedules, fare tables, and network topology for offline trip planning. The protocol supports delta updates to minimize bandwidth consumption and defines conflict resolution rules for when the device reconnects and needs to reconcile locally created bookings with the central platform.
