IEC TR 63114: Intelligent Transport Systems — Public Transport Service Discovery for Mobile Applications

1. Introduction to IEC TR 63114

IEC TR 63114 provides a technical framework for service discovery mechanisms in public transport intelligent transport systems (ITS). As urban mobility ecosystems grow increasingly complex, passengers and transport operators need seamless methods to discover available services — including real-time vehicle locations, seat availability, fare information, accessibility options, and intermodal connections — directly through mobile applications.

This technical report defines the architectural principles, communication protocols, and data models required for mobile applications to dynamically discover public transport services across heterogeneous networks and administrative domains. It addresses both client-server and peer-to-peer discovery paradigms, with a strong emphasis on scalability, low latency, and interoperability with existing standards such as SIRI (Service Interface for Real-time Information), Transmodel, and the IEEE 1512 series for incident management.

2. Service Discovery Architecture and Protocol Stack

The standard defines a three-layer discovery architecture. At the lowest level, the transport network layer handles connectivity via cellular (4G/5G), Wi-Fi, or dedicated short-range communications (DSRC). Above this, the service registry layer provides a directory service based on a lightweight service location protocol (SLP) profile optimized for mobile clients. At the top, the application layer delivers service metadata in JSON or Protocol Buffers format over HTTPS or MQTT.

Service discovery queries use a hierarchical service type taxonomy. Top-level categories include transit information (vehicle location, estimated time of arrival), fare management (ticketing, payment options), trip planning (intermodal routing, schedule integration), and accessibility (wheelchair access, audio announcements). Each service type is associated with a standardized service template that defines the required and optional data fields.

3. Mobile Application Integration and API Design

IEC TR 63114 recommends a RESTful API design for mobile service discovery, with GET endpoints for service listing (/services), service details (/services/{id}), and service health (/services/{id}/health). Responses are cached on the client side using HTTP ETags and Cache-Control headers, with a minimum cache lifetime of 60 seconds for dynamic data and up to 24 hours for static metadata such as routes and schedules.

The report also describes a publish-subscribe mechanism using MQTT for real-time updates. Clients subscribe to topics structured as /transport/{city}/{agency}/{service_type}/{vehicle_id}, receiving notifications when service parameters change — for example, a bus’s estimated arrival time is updated or a service disruption is reported.

4. Engineering Insights and Implementation Guidance

Scalability is the primary engineering concern. The service registry must handle discovery requests from thousands of concurrent mobile clients during peak hours. The report recommends a stateless registry architecture with horizontal scaling behind a load balancer, using a distributed database (e.g., Cassandra or DynamoDB) for service state persistence.

Security considerations include authentication of service providers (using OAuth 2.0 client credentials), authorization of service consumers (API key or JWT-based), and encryption of all service metadata in transit (TLS 1.3). Privacy-sensitive data such as passenger location history must be anonymized before being stored or transmitted.

Interoperability testing is emphasized throughout the report. A reference implementation and conformance test suite are described, enabling transport authorities to validate their service discovery implementations against the standard before deployment.

5. Frequently Asked Questions