V2X — Connected Mobility
Vehicle, roadside, retrofit and micromobility engineering.
Configuration boundaries for onboard, roadside and VRU equipment. Exact profiles remain Unverified until product evidence is attached.
On this page
Hardware
Configuration boundaries for onboard, roadside and VRU equipment. Exact profiles remain Unverified until product evidence is attached.
- Onboard
- Roadside
- Retrofit
- Micromobility
Page contract
What, who, boundaries and next step.
- What it is
- Engineering families for onboard, roadside, retrofit and micromobility equipment — configuration boundaries only.
- Who needs it
- Hardware and systems engineers evaluating discussable configurations.
- Problem / intended benefit
- Prior concept names are not shipping SKUs; dimensions, BOM and qualification must not be invented.
- Ciright responsibility
- Packaging and enterprise integration of approved configurations.
- Keyra responsibility
- Hardware-rooted trust modules where Keyra is in scope.
- Demonstrated
- Named coverage families with Unverified readiness.
- Proposed / Unverified
- Stock, prices, orderable SKUs, range, latency and certification dates.
- Evidence
- Offering manifest; all hardware families Unverified pending product records.
Prerequisites
- Configuration ID from product owner before any compatibility claim
- Separate component qualification from website copy
Limitations
- No universal compliance logo
- No certified-worldwide claim
- Supplier silicon ownership is not Ciright ownership
Evidence posture
Demonstrated versus proposed.
Every material claim requires configuration scope, source/version, owner and review date before it can leave Unverified. Industry explanations (including 5GAA direct/network context) are not Ciright hardware proof.
Take a reliable next step.
Public education stays readable. Protected accounts, pilot records and privileged functions require Keyra verification. General corporate inquiry assurance policy is preserved until product/security owners change it.