QRF logo Quantum Routing Framework (QRF)

Quantum Routing Framework (QRF)

Stable, real-time (low-latency), scalable routing for connected vehicles at city scale — runs on standard PC hardware.

Observed in NS-3 evaluations: 10k urban (Stability ≈ 0.96, PDR ≈ 0.94); synthetic stress (core decision time ≈ 1 ms for a single route; full harness ≈ 55 s / 50 routes ≈ 1.10 s/route).

Reproducible runs • CSV exports • Acceptance tests available on request • POC required prior to licensing (OEMs, Tier‑1s & integrators)

Runs on standard PC hardware Scales to million-node stress tests Patent Pending

Stability

≈ 0.96observed (10k-node scenario)

Consistent routes under rapid topology change.

Delivery

≈ 0.94PDR (10k nodes)

Robust delivery across dense, mobile topologies.

Scale

1Mnode stress tests

Algorithmic decision time ≈ ≤ 1 ms in stress setups.

Design Principles

QRF applies a lightweight, adaptive decision core with feedback-driven tuning to sustain stability under high mobility. The system is modular and aligns with common V2X stacks.

Adaptive routing core; no accelerators required.
Baseline comparisons available against established protocols.
Reproducible runs with exported CSV metrics.

Deployment

Evaluation build is available upon request. POC evaluation is required prior to licensing. Source code is available only under mutually executed NDA/LOI with agreed commercial terms.

Details provided on request under NDA.

Overview

Below is a concise view of the information typically provided in evaluation packs. This page contains no downloads.

Key Metrics (Condensed)

Metric Scenario Observed Notes
Stability Urban 10k ≈ 0.96 Consistent routes under rapid topology change
Packet Delivery Ratio Urban 10k ≈ 0.94 Robust delivery in dense, mobile topologies
Algorithmic Decision Time Stress (synthetic) ≈ 1 ms Single-route core micro-benchmark (excludes I/O/logging)
Scale Stress (synthetic) up to 1M nodes City-scale readiness
Full Stress Harness Stress (synthetic) ~55 s / 50 routes (≈1.10 s/route) Includes orchestration, I/O, logging, export
Hardware Baseline Evaluation Standard PC-class No accelerators required

Integration Fit

  • Interfaces align with common V2X stacks and simulation harnesses.
  • No accelerators required; runs on standard PC hardware.
  • Supports reproducible NS‑3‑based evaluation with offline datasets.

Evaluation Process

  1. Define acceptance KPIs and scenarios jointly.
  2. Provide an NS-3 Poc evaluation build under NDA/LOI (on-prem or secure environment).
  3. Execute Poc runs; collect CSV metrics and summaries (reproducible).
  4. Review results and discuss licensing options if targets are met.

Acceptance Tests (Outline)

Scenario A — Urban 10k

Primary scenario with dense mobility.

  • KPI: Stability ≥ 0.92; PDR ≥ 0.90
  • Outputs: CSV metrics, summary visuals

Scenario B — Stress

Synthetic stress setup to evaluate scaling.

  • KPI: Core micro-benchmark ≤ 1 ms (single route); full harness ≈ 1.10 s/route
  • Outputs: CSV metrics, scaling curve

IP & Confidentiality

  • Status: Patent Pending — provisional application filed.
  • Source code available only under mutually executed NDA/LOI.
  • Poc evaluation is conducted under NDA/LOI.
  • Artifact: evaluation-only build (under NDA).

Contact

For scheduling a technical review.