V2X — Connected Mobility
Scenario index for engineering evaluation.
On this page
Use cases
Substantive scenario families for discovery — illustrative unless a configuration-specific evidence record says otherwise.
- Scenario index
- Audience mapping
- Evidence status
- Next steps
Page contract
What, who, boundaries and next step.
- What it is
- Scenario index for engineering evaluation — illustrative unless evidence says otherwise.
- Who needs it
- All five audience cohorts selecting a relevant scenario family.
- Problem / intended benefit
- Scenarios are often presented as production-ready without configuration evidence.
- Ciright responsibility
- Scenario indexing and next-step routing.
- Keyra responsibility
- As required for protected pilot records.
- Demonstrated
- Scenario families listed for discussion.
- Proposed / Unverified
- Any dated deployment or market share claim.
- Evidence
- Claim register forbids inventing performance numbers.
Prerequisites
- Audience and region
- Equipment inventory at a non-sensitive level
Limitations
- Illustrative unless configuration evidence is attached
- Intersection awareness
Equipped vehicles and roadside units exchanging cooperative messages — illustrative.
- Work-zone coordination
Temporary roadside context with explicit unequipped-worker limitations.
- Campus / depot operations
Constrained geography for pilot design discussions.
- Micromobility / VRU
Motorcycle, bicycle, scooter and pedestrian contexts; B2V meaning must be disambiguated per record.
- Fleet diagnostics (network path)
Enrollment, updates and diagnostics over approved connectivity — not direct-path safety.
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.