V2X Protocol & Safety Strategy

[melaniereis]

Summary / Description

Investigate the foundations of V2X (PC5/ITS-G5) and define the communication strategy for the DrivaPi system. This research is critical to ensure we establish a reliable, low-latency "chain of trust" from the emergency vehicle to our internal system without introducing unsafe behaviors.

Type / Category

• task
• bug
• docs
• infra
• spike / research

Dependencies

Blocked by

• # (None)

Sub-issues

• # (to be defined)

Tasks

• Map the data flow: Origin (Emergency Vehicle) -> Medium (V2X/Radio) -> Destination (STM32 Gateway).
• Define "Relevance Logic": Establish the criteria for when an emergency signal is considered a safety threat (e.g., proximity, vector calculation).
• Validate STM32 processing capacity for real-time signal filtering (ThreadX context).

Acceptance Criteria (AC)

List concrete, testable criteria that must be true for this issue to be accepted.

• Architectural Decision Record (ADR) or similar detailing the communication strategy and filtering logic.
• Definition of the communication protocol between the V2X module and the STM32.

Definition of Done (DoD)

Checklist describing repository/process conditions for merging (docs updated, tests added, CI green, etc.).

• Code reviewed and approved
• CI checks pass
• Documentation updated (if applicable)

How to validate / Test steps

Review the ADR documentation to ensure the logic covers the "Relevance" criteria and technical feasibility.

---