Terrestrial Vehicle Telemetry for ROTE / Harm Quotient / Trans-Tax

 

A TECHNICAL PROPOSAL

Terrestrial Vehicle Telemetry for ROTE / Harm Quotient / Trans-Tax

Carrying the MoRTH-Mandated Secure Vehicle-Cloud Link Without a NavIC Dependency

 

Prepared by: Hemen Parekh

Date: 12 August 2026

Reference: Companion note to the ROTE (Reduction of Transport Emissions) / Harm Quotient / Trans-Score / Trans-Tax framework, and to the ROTE simulation submitted to Prof. V. Kamakoti, IIT Madras (June 2025)

1. Background and Problem Statement

The Harm Quotient / Trans-Score / Trans-Tax framework — developed since November 2018 and formalised as the ROTE (Reduction of Transport Emissions) simulation submitted to IIT Madras in June 2025 — has, from its earliest formulations (“Dear Shri Gadkariji: Let GPS-Based Toll Tax Lead to Harm-Quotient Based Trans-Tax”, Nov 2023) assumed NaVIC-GPS as the positioning layer feeding the Harm Quotient calculation. The Chennai simulation itself is specified around NaVIC satellite tracking of 1,000 vehicles.

That assumption needs revisiting. As of March 2026, NavIC's active constellation fell to three functioning satellites for Positioning, Navigation & Timing (PNT) services — below the minimum of four required for a standalone position fix — following failure of the last onboard atomic clock on IRNSS-1F. Replacement launches (NVS-03 onward) have been repeatedly delayed by propulsion and pyro-valve failures, and no firm restoration date has been committed. A Harm Quotient engine that assumes an uninterrupted NaVIC fix is, at present, standing on unstable ground.

At the same time, a separate regulatory development strengthens the framework rather than threatening it: MoRTH's new connected-vehicle cybersecurity rules — AIS-189 (Cybersecurity Management System) and AIS-190 (Software Update Management System) — take effect 1 October 2026 and mandate secure embedded electronics, validated software, and authenticated, recorded, real-time data exchange between every new connected vehicle and cloud backends. This is, in effect, the government mandating the always-on sensor-to-cloud infrastructure the Harm Quotient framework has called for since the 2017 Internet-of-Vehicles vision — independent of which positioning source feeds it.

This note proposes that the positioning input to Harm Quotient / Trans-Score be carried over this MoRTH-mandated secure terrestrial channel — vehicle sensors, cellular network, and the driver's paired handset — rather than over a NaVIC link. The Trans-Score and Trans-Tax logic above it does not change at all.

2. Objective

To replace only the positioning/telemetry-transport layer beneath Harm Quotient — currently specified as NaVIC-GPS — with a terrestrial equivalent that rides on the AIS-189/AIS-190 secure vehicle-cloud channel already being mandated from October 2026, without altering the Harm Quotient matrix, the Trans-Score index, or the Trans-Tax credit/debit logic.

3. What Actually Needs Replacing — and What Doesn't

The Harm Quotient / Trans-Score / Trans-Tax framework has three layers. Only the bottom one is satellite-dependent:

•      Trans-Tax (unchanged) — the credit/debit logic: Trans-Score ≥ 75 earns a monthly credit (originally specified as ₹200), Trans-Score ≤ 25 attracts a monthly penalty (originally ₹500), 26–74 is neutral. Settled via the RFID/FASTag-linked e-wallet already proposed.

•      Trans-Score (unchanged) — the monthly 0–100 eco-behavioural index aggregated from Harm Quotient readings across the vehicle's usage.

•      Harm Quotient (positioning input replaced) — the per-vehicle pollution footprint, weighted by energy source, vehicle age, capacity, location, time of use and driving conditions. Location and driving-conditions weightage is the part that was to be fed by NaVIC-GPS. This is the only element this note addresses.

In other words: this is a swap of the sensor-to-cloud transport layer, not a redesign of the Harm Quotient matrix, the Trans-Score index or the Trans-Tax settlement mechanism.

4. Proposed Terrestrial Architecture — Five Layers

Layer 1 — In-Vehicle Sensor Fusion

The AIS-189/AIS-190-mandated secure electronics already capture the raw inputs Harm Quotient needs:

•      ECU odometer reading — precise cumulative distance, tamper-evident by design once signed at the chip level under AIS-189.

•      Accelerometer and gyroscope (IMU) — dead-reckoning of heading and speed changes between fixes, feeding the “driving conditions” weightage.

•      OBD-II telemetry — speed, RPM, engine load and fuel consumption, feeding the energy-source and vehicle-age weightages directly.

Layer 2 — V2V / V2I Mesh Corroboration

Vehicles already carrying C-V2X or DSRC radios for collision-avoidance ADAS exchange short signed pings of relative distance, heading and timestamp with nearby vehicles. This corroborates the odometer/IMU trace independently — if a vehicle's claimed speed or route is not supported by any peer vehicle, the Harm Quotient reading for that segment is flagged before it reaches the Trans-Score aggregation. Roadside V2I units at key junctions extend this where vehicle density is low.

Layer 3 — Paired Mobile and Cellular Network

The driver's handset, Bluetooth-paired to the vehicle's telematics unit as AIS-190 already assumes for OTA updates, supplies a second, carrier-generated location estimate — Cell-ID and Timing Advance, 5G NR Positioning where supported, and known Wi-Fi access points. Because this fix originates with the carrier rather than the vehicle owner's own equipment, it is a source the vehicle occupant cannot manipulate — the same anti-tampering property NaVIC-GPS was expected to provide, without the constellation dependency.

Layer 4 — Map-Matching / Zone-Classification Engine

Operated by the telecom or telematics service provider under the AIS-189 secure-channel requirement, this layer fuses odometer/IMU dead-reckoning, V2V corroboration and the cellular fix, and snaps the result onto the road network to classify road class, location weightage and time-of-use band — exactly the inputs the Harm Quotient matrix already specifies. Output is a signed Harm Quotient reading, not a raw location trace.

Layer 5 — Harm Quotient / Trans-Score / Trans-Tax Engine

Unchanged from the existing framework: Harm Quotient readings aggregate into the monthly Trans-Score (0–100); Trans-Score bands trigger the Trans-Tax credit or penalty; settlement runs through the RFID/FASTag-linked e-wallet, exactly as proposed since 2019 and as simulated for the Chennai ROTE pilot.

 

5. Data Integrity and Anti-Tampering

A single NaVIC fix had no built-in mechanism to detect spoofing or a disconnected/shielded receiver. The terrestrial design instead requires independent witnesses to agree before a Harm Quotient reading is accepted into the Trans-Score calculation:

1.    Each OBD-II/ECU reading is cryptographically signed at the chip level — a natural extension of the AIS-189 secure-electronics requirement — preventing after-the-fact edits to logged distance.

2.    Readings are hash-chained in sequence (the same tamper-evidence principle used in the EVBAT blockchain voting audit trail proposal), so any retroactive alteration breaks the chain and is immediately detectable.

3.    V2V peer corroboration flags any reading whose claimed speed or route is not supported by nearby vehicles' independent observations.

4.    The cellular position fix is generated and held by the carrier, outside the vehicle owner's control, and serves as a fourth cross-check.

6. Privacy Safeguards

Only the signed Harm Quotient reading — road class, zone, distance and time band — passes to the Trans-Score aggregation. Raw continuous location traces are processed and discarded at the map-matching layer (Layer 4) and never stored centrally, limiting exposure as a surveillance instrument while preserving everything the Trans-Score calculation needs.

7. Comparison — NaVIC-Dependent vs Terrestrial Hybrid Positioning Layer

Parameter	NaVIC-GPS (as originally specified)	Terrestrial Hybrid (Proposed)
Positioning source	Single external satellite fix	Odometer + V2V mesh + cellular network (three independent sources)
Availability today	Degraded — NavIC below minimum operational satellites since March 2026	Fully available on infrastructure already being mandated by AIS-189/190
Tamper resistance	Low — a single spoofed or shielded fix goes undetected	High — requires multiple sources to agree before a Harm Quotient reading is accepted
Regulatory alignment	No existing mandate for NaVIC-linked vehicle sensors	Rides directly on the AIS-189/AIS-190 secure vehicle-cloud mandate, effective 1 Oct 2026
Privacy exposure	Continuous raw location trace typically transmitted	Only the aggregated Harm Quotient reading transmitted
Dependency risk	Single point of failure (satellite constellation health)	No single point of failure; degrades gracefully
Cost to implement	New satellite-linked receivers per vehicle	Reuses AIS-189/190 electronics, OBD-II, ADAS V2V radios, and the driver's own handset

8. Known Limitation

On long, sparsely-populated rural highway stretches, both cell-tower resolution and V2V corroboration weaken due to lower tower and vehicle density. The pragmatic response is a tertiary fallback to GPS (which, unlike NavIC, remains fully operational) purely as a cross-check in these low-density stretches — not a redesign of the Harm Quotient positioning layer around satellite dependency.

9. Implementation Path — Aligned to the Existing ROTE Roadmap

This terrestrial positioning layer is a drop-in substitution within the four-phase roadmap already proposed for ROTE; no phase needs restructuring:

1.    Phase 1 (2026–27) — Chennai pilot: run the 1,000-vehicle, 24-month ROTE simulation already submitted to Prof. V. Kamakoti at IIT Madras, substituting the terrestrial positioning layer (Layers 1–4 above) for the NaVIC-GPS input, and validate Harm Quotient accuracy against known road segments.

2.    Phase 2 (2027–28) — Expand to Mumbai, Delhi, Bangalore and Hyderabad at 10,000 vehicles each, refining Trans-Score weightages using the richer terrestrial corroboration data.

3.    Phase 3 (2028–29) — National rollout timed to the AIS-189/AIS-190 mandate: since every new connected vehicle from October 2026 already carries the required secure electronics, the Harm Quotient firmware can be embedded at the factory gate rather than retrofitted.

4.    Phase 4 (2029–30) — Full operationalisation: Trans-Tax collection live nationwide via the RFID/FASTag-linked e-wallet, with the terrestrial positioning layer carrying the load NaVIC-GPS was originally intended to carry.

10. Closing Note

The Harm Quotient / Trans-Score / Trans-Tax framework does not need to wait for NavIC's constellation to be restored, and does not need to be redesigned. Only its positioning input changes — from a single satellite fix to three mutually-corroborating terrestrial sources, carried over the very secure vehicle-cloud channel MoRTH is already mandating from 1 October 2026. If anything, the AIS-189/AIS-190 rules make this the moment to embed Harm Quotient logic into vehicle firmware at the factory gate, exactly as argued in ‘Pigovian Trans Tax? We Are One Step Closer.’