LRP · Open Standard for Real-Time Cartographic Intelligence · v3.0

The protocol layer
that makes maps real.

The LiveRoad Protocol (LRP) is a neutral, privacy-by-design open standard for verified real-time road event intelligence — manufacturer-agnostic, governance-neutral, and permanently open. A Toyota sensor can inform a BMW navigation system, contribute to a HERE map tile, and trigger a municipal alert — without proprietary intermediaries.

3.0
Academic Paper Version
3
Architecture Layers
7
Threat Vectors Modelled
2025
Avctoris Registration
The Protocol Gap

Sensors see everything. Maps still lag behind.

Vehicles, cameras, IoT sensors and connected infrastructure perceive road reality every second. Yet global cartography runs on data refreshed in hours or days. The bottleneck is not detection — it is the absence of a neutral protocol between sensors and maps. The Internet did not grow by building better websites; it grew by standardising the protocol beneath them. LRP applies that logic to cartographic intelligence.

Three-Layer Architecture

Edge. Engine. Consumer.

A clean separation of concerns: contribution, validation, and consumption. Each layer is independently specified, independently implementable, and independently auditable.

EDGE LAYER
Contribution & Signing
Any vehicle, sensor, camera, or device can contribute road events. Cryptographic contributor certification (ECC-based) ensures authenticity without exposing identity. Privacy-by-design from the first byte.
EDGE · PRIVACY
ENGINE LAYER
Consensus & Trust
Multi-source weighted confidence aggregation with Byzantine fault tolerance. Bayesian-calibrated trust scores per contributor. Hierarchical spatial indexing via Uber H3. The validation core of the protocol.
CONSENSUS · BFT
CONSUMER LAYER
Verified Event Feed
Standardised API delivering verified, time-stamped, geo-indexed road events to navigation systems, OEM platforms, public infrastructure, and insurers — under uniform terms, with no vendor lock-in.
API · INTEROP
EVENT TAXONOMY
Universal Event Model
A single, extensible taxonomy covering surface conditions, transient hazards, traffic anomalies, infrastructure failures, and environmental events. Aligned with ETSI ITS, SAE J2735, DATEX II, and NGSI-LD.
DATA MODEL
TRUST MODEL
Formal Reputation Specification
Each contributor carries a calibrated trust score updated via Bayesian inference on validated outcomes. Sybil-resistant, time-decaying, and provably bounded under adversarial assumptions.
FORMAL SPEC
PRIVACY ARCHITECTURE
No Identity Exposure
Contributions are pseudonymous and unlinkable across sessions. No raw telemetry leaves the edge. Designed for GDPR, UNECE WP.29 R155/156, and ISO 20078 compliance from day one.
PRIVACY · LEGAL
Positioning

LRP does not compete with maps.
It is what makes maps real.

LRP is positioned alongside — not against — ETSI ITS, C-V2X, SAE J2735, DATEX II, NGSI-LD, SensorThings API, ISO 20078, UNECE WP.29 R155/156, Catena-X, and Gaia-X. Where those standards govern communication, supply chains, or static geometry, LRP governs the missing layer: verified, real-time road event intelligence shared across competing ecosystems.

Manufacturer-AgnosticAny OEM, supplier, or platform can contribute and consume.
Governance-NeutralFederated under the LRP Ecosystem Partnership (LEP).
Privacy-by-DesignNo identity exposure. No raw telemetry leakage.
Permanently OpenCC BY 4.0 + Foundation Covenant. No licensing fee.
Governance · LEP & Federation

Federated. Auditable. Open.

The LRP is stewarded by the LRP Ecosystem Partnership (LEP), a federated body operating under the Foundation Covenant. Authorship and intellectual origin belong to Michel Martins de Araujo, registered and timestamped in 2025 via Avctoris. Published under Creative Commons Attribution 4.0 International with Foundation Covenant.

LRP 1.0
LRP 1.0
Reference Pilot Deployment
500 vehicles, 90 days. Empirical anchoring of the parameterised performance model across conservative, baseline, and aggressive scenarios. First public Edge / Engine / Consumer reference implementations.
Reference Impl.Pilot MetricsPublic SDK
LRP 1.1
LRP 1.1
Trust Model Hardening
Bayesian trust calibration refinements, Sybil-resistance audits, expanded threat model coverage across the seven canonical attack vectors. Independent security review.
TrustSecurity AuditThreat Model
LRP 2.0
LRP 2.0
Federation & Cross-Region
Federated LEP instances across regions. Cross-region consensus protocols. Regulatory alignment with EU and Asia-Pacific frameworks. First OEM-grade production deployments.
FederationRegulatoryOEM-Grade
LRP 2.1
LRP 2.1
Public Infrastructure Integration
Native integration with municipal road authorities, insurers, and emergency response systems. Standardised data-sharing agreements. The full neutral protocol layer in operation.
Public SectorInsurersEmergency Response
Request the Academic Paper

Build the layer
that maps depend on.

The LRP v3.0 Academic Paper specifies the full protocol — architecture, trust model, threat model, governance, regulatory and economic framework. Request a copy or contribute to the reference implementation.

Request the Paper← Back to the Foundation