V2X — Connected Mobility
Participating connectivity and SIM / eSIM / iSIM options.
Operator dependencies and limits for the network path. A SIM is not a direct radio; subscriber secrets are not V2X signing keys.
On this page
Telecom
Operator dependencies and limits for the network path. A SIM is not a direct radio; subscriber secrets are not V2X signing keys.
- Connectivity
- SIM / eSIM / iSIM
- Operator dependencies
- Limits
Page contract
What, who, boundaries and next step.
- What it is
- Participating connectivity and SIM/eSIM/iSIM options with operator dependencies.
- Who needs it
- Carriers and enterprise connectivity owners.
- Problem / intended benefit
- SIM credentials are confused with V2X trust credentials and direct radios.
- Ciright responsibility
- Documents operator dependencies and enterprise integration.
- Keyra responsibility
- Keeps subscriber authentication distinct from V2X certificate acceptance.
- Demonstrated
- Conceptual separation on this site.
- Proposed / Unverified
- Carrier compatibility matrices without evidence.
- Evidence
- Telecom offering family readiness: Proposed integration.
Prerequisites
- Operator agreement for any network-path service
- Separation of subscriber secrets from application signing keys
Limitations
- A SIM is not a direct radio
- Do not reuse subscriber network secrets as application signing keys
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.