ISO/TS 25114:2010 — Intelligent Transport Systems Probe Data Reporting Management (PDRM)

Standardized Framework for Efficient Probe Vehicle Data Collection and Communications Management

Managing the Data Avalanche from Connected Vehicles

Modern intelligent transport systems (ITS) rely on fleets of probe vehicles — ordinary cars, trucks, and taxis equipped with GPS, speed sensors, and communication devices — that continuously report traffic conditions, travel times, and road incidents. The challenge is not data collection per se, but efficient data management: wireless communications airtime is expensive and scarce, and transmitting every sensor reading from every vehicle in real time is economically and technically infeasible. ISO/TS 25114:2010 addresses this challenge by defining Probe Data Reporting Management (PDRM) — a standardized framework that allows a landside processing centre to issue targeted instructions to probe vehicles, controlling what data is collected, when, where, and under what conditions it is reported. This approach reduces communication costs while ensuring that the data needed for traffic management remains available, and it can scale to millions of vehicles without overwhelming network infrastructure.

PDRM transforms probe vehicles from passive data broadcasters into intelligent, remotely configurable sensing nodes. Instead of “dumbly” transmitting everything, they respond to smart instructions that filter, prioritize, and schedule data transmissions, dramatically reducing communications costs.

PDRM Reference Architecture

The standard defines a comprehensive reference architecture built on the framework of ISO 22837 (Vehicle probe data for wide area communications). Key components include:

  • Referenced data repository — The central landside system that stores and processes probe data.
  • Onboard data source — Vehicle sensors (GPS, speed, heading, temperature, etc.) that generate raw probe data.
  • PDRM generator — The landside component that creates PDRM instructions based on current data needs.
  • Probe data element generation — Onboard processing that formats raw sensor data into standardized probe data elements.
  • PDRM transmitter/receiver — Communications interface for sending instructions to vehicles and receiving probe messages.
  • Reporting condition — The logical criteria that determine when a probe vehicle should generate and transmit data.

The architecture is designed to be technology-agnostic, supporting any communications medium (cellular, Wi-Fi, dedicated short-range communications) and any onboard sensor configuration.

PDRM Component Location Function
PDRM Generator Landside centre Creates reporting instructions based on traffic management needs
PDRM Transmitter Landside centre Sends encoded PDRM messages to probe vehicles
PDRM Receiver Onboard vehicle Receives and decodes PDRM instructions
Probe Data Element Generator Onboard vehicle Formats sensor data into standardized elements
Probe Message Generator Onboard vehicle Assembles probe data elements into transmittable messages

Common Data Elements and Instruction Types

Standardized Data Framework

The standard establishes a common data framework that ensures interoperability across different vehicle manufacturers and system operators. Key common data elements include PDRStopTime, PDRStartTime, Heading, NumInstructions, NumRegions, Region type definitions, ReportingFrequency, RoadwayHeading, VehicleHeading, and VehicleType. Each element has a precisely defined data type and semantics, enabling consistent interpretation across diverse implementations.

PDRM Instruction Categories

Three fundamental instruction types are defined:

  • Data capture instructions — Specify which probe data elements should be collected and reported.
  • Threshold instructions — Define reporting triggers based on threshold values (e.g., report when speed exceeds 80 km/h).
  • Delta instructions — Define reporting triggers based on change in value (e.g., report when heading changes by more than 10 degrees).

These instructions can be combined and nested to create sophisticated data collection strategies. For example, a traffic management centre might issue a delta instruction for speed monitoring within a specific geographic region, combined with a threshold instruction that only activates reporting when average speeds drop below 40 km/h — effectively identifying congestion events without wasting bandwidth on normal-flow traffic. The standard also supports start/stop all reporting, start/stop specific data element reporting, and a generic scheme for conveying criteria for reporting specific probe data elements.

The combination of threshold and delta instructions enables highly efficient event-driven reporting: vehicles only transmit when something significant happens, rather than flooding the network with periodic status updates.

XML-Based Message Encoding and Geographic Scoping

PDRM instructions are encoded in XML (Extensible Markup Language), providing platform-independent readability and extensibility. Each instruction can be scoped by three dimensions: a time period (duration of validity), a geographic region (polygon or corridor definition), and a roadway heading (direction of travel). This three-dimensional scoping allows a traffic management centre to issue highly granular instructions — for example, “all vehicles travelling northbound on Highway 101 between exits 15 and 20 should report average speed every 30 seconds for the next 2 hours.”

Privacy is a critical concern: the standard emphasizes that probe messages must not contain any information that could identify the specific vehicle or its occupants, directly or indirectly. Anonymization is built into the data framework, not added as an afterthought.

Frequently Asked Questions

Q: What is the primary purpose of PDRM?
A: PDRM enables a landside traffic management centre to remotely control what data probe vehicles collect and when they report it, optimizing the use of wireless communications bandwidth while ensuring that the right data is available for traffic monitoring and management decisions.
Q: How does PDRM reduce communications costs?
A: By using threshold-based and delta-based instructions, vehicles only transmit data when significant events occur or when parameters exceed defined thresholds, rather than continuously broadcasting all sensor readings. The standard’s three-dimensional scoping (time, geography, heading) further reduces unnecessary transmissions.
Q: Is PDRM specific to any particular communications technology?
A: No. The architecture is technology-agnostic and supports any communications medium including cellular networks, Wi-Fi, and dedicated short-range communications (DSRC).
Q: Does the standard address data privacy concerns?
A: Yes. ISO/TS 25114 explicitly requires that probe messages must not contain any information that could identify the specific vehicle or its occupants. Anonymization is built into the data framework design.

In conclusion, ISO/TS 25114:2010 remains a foundational standard for intelligent transport systems, providing the essential PDRM framework that enables efficient, scalable, and privacy-aware probe data collection from connected vehicle fleets worldwide. As vehicle connectivity and autonomous driving technologies advance, the importance of standardized data reporting management will only continue to grow, making this standard increasingly relevant for next-generation mobility systems and smart city infrastructure deployments. Traffic authorities and automotive manufacturers alike benefit from the interoperability that PDRM standardization provides.

Leave a Reply

Your email address will not be published. Required fields are marked *