ITU‑T (ITU Telecommunication Standardization Sector) focuses on communication network architecture and protocol specifications – separate from ITU‑R, which handles spectrum allocation – don't confuse them.
Connected‑vehicle V2X and co‑operative autonomous driving work is mainly led by Study Group 21 (SG21) – under Question Q10/21 – with SG13 and SG20 providing supporting co‑ordination. ITU‑T outputs are Recommendations – not mandatory standards for certification – they serve as legislative references for countries – and are aligned with 3GPP, ISO, and UN WP.29.
Be cautious of industry claims about "ITU releasing brand‑new connected‑vehicle standards" – Recommendations are a long way from mandatory enforcement.
2. Clarifying Two Easily Confused 2026 Developments
2.1 C‑V2X in IMT‑2030 – belongs to ITU‑R, not ITU‑T
The inclusion of C‑V2X in the IMT‑2030 framework is a ITU‑R WP5D output – not an ITU‑T standard update.
The practical significance: C‑V2X direct communication is now part of the unified wide‑area mobile communication plan. For terminal manufacturers, this is a reference direction for long‑term RF front‑end and protocol‑stack evolution – but it is not a protocol specification for product compliance.
2.2 In‑vehicle encryption and HSM – regional access requirements
EU M/590 is a standardisation mandate to ETSI and CEN – not legally binding – it does not mandate terminal encryption levels.
In‑vehicle HSM and encryption requirements come from UN R155 and domestic vehicle safety standards – regional market‑access requirements – not ITU‑T standard changes.
3. ITU‑T 2026‑2028 Work‑In‑Progress Recommendations
ITU‑T has research projects on co‑operative driving and perception‑data exchange. F.CAV documents belong to ISO/ETSI – not ITU‑T.
Currently, these are still at the research stage – not directly usable as certification evidence – mainly affecting future interoperability and test methods. Teams working on perception algorithms should track draft progress.
Software‑defined vehicle gateways and flying‑vehicle service platforms are also in ITU‑T's research scope – expected to take shape 2026‑2028. Engaging at the draft stage is far cheaper than post‑publication compliance rework.
4. Practical Significance for Companies
Distinguish ITU‑T Recommendations from target‑market mandatory regulations – don't treat research‑stage drafts as enforceable compliance clauses.
For cross‑border product development, ITU‑T's main value is providing a common interoperability baseline – enabling test‑result reuse across regions – reducing multi‑market development costs.
At project kick‑off: RF and IMT evolution → ITU‑R – network protocols and interoperability → ITU‑T – real market access → national mandatory regulations.
5. Alignment with Domestic Mandatory Standards
ITU‑T provides international reference recommendations. China's GB 44495 (vehicle cybersecurity) and GB 44496 (software upgrades) are independent mandatory national standards – reviewed with the vehicle announcement.
The two systems do not conflict – ITU‑T focuses on communication‑level interoperability – national standards focus on vehicle‑level security and full‑lifecycle software‑version management. Export models must assess both – they cannot substitute for each other.
6. Common Misconceptions
·Attributing ITU‑R's IMT‑2030 framework outputs to ITU‑T standard updates.
·Treating EU M/590 as a mandatory regulation for vehicle terminals.
·Confusing ISO/ETSI F.CAV documents with ITU‑T Recommendations.
·Using ITU‑T Recommendations directly as certification evidence – ignoring statutory access requirements.
7. Practical Recommendations
Assign someone to track SG21 draft updates quarterly – do not re‑architect products based on non‑enacted frameworks.
Priority at project definition:
·Target‑market mandatory safety regulations.
·3GPP protocol baselines.
·ITU‑T interoperability Recommendations.
Plan in‑vehicle HSM, encryption, and protocol stacks early – late‑stage changes are costly.
BlueAsia supports V2X communication and multi‑country vehicle access assessment – clarifying compliance boundaries between ITU‑T, ITU‑R, UN regulations, and domestic standards – reducing later rework risk.
For 2026 ITU‑T connected vehicle standards, contact BlueAsia at 13534225140 (King) or email king.guo@cblueasia.com.
Related News
