EN 16803: what Kshana supports evidence for

EN 16803 is a paid standard. Only its part structure and the clause numbers visible in public catalogue material are used here: Part 3 clause 6 and Annex A. Requirement wording is not reproduced and the paraphrases come from the public scope descriptions. A licence holder can extend the table clause by clause.

Every row says which Kshana outputs support evidence for the requirement and what is left over. Nothing here says a framework is met or that any product has been rated or approved by anyone. Run kshana compliance-report on your own result files to see which rows your runs actually evidence; see README.md.

Source documents#

Space - Use of GNSS-based positioning for road Intelligent Transport Systems (ITS) - Part 1: Definitions and system engineering procedures for the establishment and assessment of performances: EN 16803-1:2020 (catalogue: valid from 2 October 2020, replacing the 2016 edition). https://www.evs.ee/en/evs-en-16803-1-2020. Read 2026-10-09: catalogue scope text only; the standard is paid and was not read.
Space - Use of GNSS-based positioning for road Intelligent Transport Systems (ITS) - Part 2: Assessment of basic performances of GNSS-based positioning terminals: EN 16803-2:2020 (catalogue: valid from 2 October 2020). https://www.evs.ee/en/evs-en-16803-2-2020. Read 2026-10-09: catalogue scope text only; the standard is paid and was not read.
Space - Use of GNSS-based positioning for road Intelligent Transport Systems (ITS) - Part 3: Assessment of security performances of GNSS-based positioning terminals: EN 16803-3:2020 (catalogue: valid from 2 October 2020). https://www.evs.ee/en/evs-en-16803-3-2020. Read 2026-10-09: catalogue scope text only; the standard is paid and was not read. The catalogue text names clause 6 (recorded versus simulated signals) and Annex A (a high-level categorisation of attacks) and nothing else by number; the catalogue gives no committee name, so none is stated here.

Mapping#

Reference	What it asks (paraphrased)	Kshana outputs that support evidence for it	Gap
EN 16803-1 (definitions and system engineering procedures)	Defines the road-ITS architecture, performance features and metrics, and a method to compare test environments. Sets no requirements.	Reproducible run provenance	Clause numbers are not publicly visible. A licence holder should map Kshana's output fields to the metric definitions.
EN 16803-2 (basic performance of GNSS-based terminals)	Replay-based laboratory test procedures for availability, continuity, accuracy, integrity and time to first fix of the position output. Sets no minimum values.	Holdover and coasting; Integrity monitoring and protection levels	Kshana's exported motion can drive a replay; the standard's procedure, its recorded-signal handling and its metric computation are not reproduced here and need the licensed text.
EN 16803-3, clause 6	Distinguishes recorded signals from simulated signals in the security tests.	Receiver-log trust assessment	Kshana neither records nor simulates a signal. It exports motion and events and scores the receiver's log.
EN 16803-3, Annex A	A high-level categorisation of attacks on GNSS: interference, jamming, meaconing and spoofing.	Jamming link-budget effects; Spoofing and meaconing detection	Kshana's scenarios name attack classes in the same broad terms; a clause-level crosswalk needs the licensed Annex.