V2X — Connected Mobility
Offering evidence, standards applicability and unavailable dependencies.
On this page
Readiness
Configuration-scoped readiness labels. Geography and standard versions recorded only when evidenced.
- Evidence matrix
- Standards / region
- Dependencies
- Unavailable items
Page contract
What, who, boundaries and next step.
- What it is
- Configuration-scoped readiness labels, standards/region applicability and unavailable dependencies.
- Who needs it
- Buyers distinguishing discussable engineering from production products.
- Problem / intended benefit
- Readiness labels get detached from exact configurations.
- Ciright responsibility
- Maintains public readiness wording against Core/product records.
- Keyra responsibility
- Evidence for Keyra-scoped trust claims.
- Demonstrated
- Consistent label vocabulary on this site.
- Proposed / Unverified
- Any Production label without configuration evidence.
- Evidence
- Offering manifest readiness column.
Prerequisites
- Product-owner approved record before leaving Unverified
Limitations
- Availability is a separate business fact from engineering discussability
Labels in use
Proposed → Production, plus Unverified.
- Onboard / Vehicle Trust ModuleUnverified
Source aliases: K-VTM, Vehicle Trust Module. Public materials only when evidence owner approves.
- Roadside infrastructureUnverified
Source aliases: Roadside unit engineering. Public materials only when evidence owner approves.
- Motorcycle and micromobilityUnverified
Source aliases: K-M2V, K-VRU, K-B2V (disambiguate). Public materials only when evidence owner approves.
- Hardware-rooted trustUnverified
Source aliases: Trust Core, Trust Connect. Public materials only when evidence owner approves.
- Person / vehicle / device relationshipsDocumented design
Source aliases: Relationship model. Public materials only when evidence owner approves.
- Credential lifecycleUnverified
Source aliases: V2X certificate acceptance. Public materials only when evidence owner approves.
- Participating telecom integrationProposed integration
Source aliases: SIM / eSIM / iSIM. Public materials only when evidence owner approves.
- Enterprise operationsDocumented design
Source aliases: Enterprise orchestration. Public materials only when evidence owner approves.
- Charging / parking / tolling / maintenance (separately authorized)Unverified
Source aliases: Adjacent services. Public materials only when evidence owner approves.
- Sansar explanation / trainingUnverified
Source aliases: Sansar. Public materials only when evidence owner approves.
- Developers / integrationUnverified
Source aliases: Developer interfaces. Public materials only when evidence owner approves.
- Engineering and pilotsProposed integration
Source aliases: Pilot design. Public materials only when evidence owner approves.
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.