Observed position remains separate from calculated match; the location runtime owns qualification and expiry.
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.
Ambiguity, tunnel, sequence gap and expired dead reckoning hold dependent progression instead of inventing a lane or road.
A qualified reference position is not proof of physical arrival, lane-level localization or safety-function availability.
Producer and consumer responsibilities are explicit.
A product can appear on both sides when it transforms one authority into another; each transformation retains its own evidence.
Producers
HW-01Line-fit TCUHardware systemHW-02AIS-140 / Fleet TrackerHardware systemHW-04In-dash Navitainment & IVIHardware systemFW-01Location RuntimeEmbedded softwareConsumers
FW-02Navigation RuntimeEmbedded softwareFW-04Connectivity & Telemetry AgentEmbedded softwareFW-07eHorizon & ADAS Map RuntimeEmbedded softwareSAAS-01Connected Vehicle CloudSaaS & cloudSAAS-02InTouch & Fleet Control TowerSaaS & cloudAPP-01Embedded NavigationNative applicationAPP-05Fleet & Operations PortalNative applicationChoose transport after semantics are fixed.
The program can select one or more transports without changing the source authority or failure contract.
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
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.