IF-02 · Vehicle interface

Qualified location and map match

Carry observed position, dead-reckoning state, map-match alternatives, confidence and expiry into navigation, telemetry and safety consumers.

Name the source—and name what it cannot prove.

The same message can be observation, projection, plan, receipt or physical evidence. This contract keeps those meanings separate.

Authority

Observed position remains separate from calculated match; the location runtime owns qualification and expiry.

Degraded behavior

Ambiguity, tunnel, sequence gap and expired dead reckoning hold dependent progression instead of inventing a lane or road.

Outcome boundary

A qualified reference position is not proof of physical arrival, lane-level localization or safety-function availability.

Choose transport after semantics are fixed.

The program can select one or more transports without changing the source authority or failure contract.

GNSS/NMEA or platform locationStable IPC/C APITelemetry event

Compatibility vector

  • schema or ABI version
  • producer release
  • consumer release
  • policy and entitlement revision
  • content/configuration revision
  • territory/platform profile

Acceptance evidence

  • contract compatibility
  • nominal and negative scenarios
  • ordering, replay and idempotency
  • latency, capacity and resource bounds
  • security, privacy and role enforcement
  • offline, recovery and rollback
  • target or operational acceptance
OEM program workshop

Freeze the Qualified location and map match contract before integration.

Allocate owners, transport, schema, releases, policy, content, degradation, replay and target acceptance in one controlled baseline.