CirightV2XV2X — Connected Mobility

V2X — Connected Mobility

Vehicle and road-user taxonomy.

Industry fit for cars, trucks/buses, motorcycles, bicycles, scooters and pedestrians — with supported versus configuration-specific limits labeled honestly.

On this page

Vehicles

Industry fit for cars, trucks/buses, motorcycles, bicycles, scooters and pedestrians — with supported versus configuration-specific limits labeled honestly.

  • Taxonomy
  • Industry fit
  • Unequipped users
  • Configuration limits

Page contract

What, who, boundaries and next step.

What it is
Vehicle and road-user taxonomy with industry fit and unequipped-user limitations.
Who needs it
OEM, fleet and micromobility buyers mapping actors to scenarios.
Problem / intended benefit
Unequipped road users and configuration-specific limits are often omitted.
Ciright responsibility
Scenario packaging and enterprise records.
Keyra responsibility
Device/person relationships for authorized participants.
Demonstrated
Taxonomy coverage on this page.
Proposed / Unverified
Any statement that every road user is protected by a Ciright deployment.
Evidence
Category coverage in content; qualification Unverified.

Prerequisites

  • Actor list for the target use case
  • Honesty about unequipped participants

Limitations

  • B2V ambiguity across sources — bicycle vs building meanings must be spelled per record

Open use cases

Road users & infrastructure actors

Meaningful coverage, including unequipped limits.

Optional interactive explorers, if added later, use synthetic data only. A static equivalent is available at /v2x/explorer — “Illustrative simulation — not live road data.”

  • Equipped car
  • Truck / bus
  • Motorcycle
  • Bicycle
  • Scooter
  • Pedestrian
  • Roadside unit
  • Network service

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.