V2X — Connected Mobility
What V2X connects — and what it does not.
On this page
How it works
Plain-language V2V, V2I, V2N and V2P; direct versus network paths; equipment prerequisites; FAQ without certification claims.
- V2V / V2I / V2N / V2P
- Direct PC5 path
- Network/application path
- Prerequisites
Page contract
What, who, boundaries and next step.
- What it is
- Plain-language explanation of V2V, V2I, V2N and V2P, plus direct versus network paths.
- Who needs it
- Technical and commercial evaluators who need vocabulary without assuming Ciright profile support.
- Problem / intended benefit
- Communications technology, trust architecture, application use case and commercial service are often conflated.
- Ciright responsibility
- Documents enterprise orchestration on the network path only.
- Keyra responsibility
- Identity and authorization for protected network-path operations.
- Demonstrated
- Conceptual separation of paths in this documentation.
- Proposed / Unverified
- Any claim that Ciright hardware supports a specific LTE-V2X/NR-V2X regional profile.
- Evidence
- Industry references recorded in R3 source register; Ciright configuration evidence Unverified.
Prerequisites
- Applicable radio/message/trust profile for any direct-path discussion
- Approved connectivity for network-path enrollment and fleet services
Limitations
- 5GAA direct/network explanation is industry context, not Ciright proof
- No automatic interoperability among regional profiles
- Direct path must not depend on Ciright cloud, Keyra login, SS7/SMS, billing or human approval
- V2V / V2I / V2N / V2P
Vehicle-to-vehicle, vehicle-to-infrastructure, vehicle-to-network and vehicle-to-person (or VRU) describe who communicates — not which Ciright SKU ships.
- Direct path
Compatible nearby endpoints exchange direct V2X messages under the applicable radio/message/trust profile without synchronous Ciright cloud dependencies.
- Network / application path
Approved connectivity and backhaul support enrollment, credential operations, diagnostics, updates, fleet services and enterprise integration.
Two paths
Direct and network stay distinct.
Direct path
Compatible nearby endpoints exchange direct V2X messages under the applicable radio/message/trust profile. It must not gain synchronous dependencies on Ciright cloud, Keyra login, SS7/SMS, billing, human approval or a carrier-core round trip.
Network / application path
Approved connectivity and backhaul support permitted enrollment, credential operations, diagnostics, updates, fleet services and enterprise integration.
FAQ
- Does Ciright cloud participate in direct V2X messaging?
- No. Direct-path message exchange must not depend on Ciright cloud or Keyra login.
- Is a SIM a V2X radio?
- No. Subscriber connectivity is part of the network/application path, not the direct radio.
- Does this website control vehicles or signals?
- No. There is no live braking, steering, traffic-signal or infrastructure actuation from this site.
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.