In‑vehicle product teams have all felt it over the past couple of years: the days of "one CE certificate for the whole world" are gone.
A smart‑cockpit product targeting the global market – the certification list runs to over a dozen items. CarPlay, Android Auto, HiCar, NG eCall mandatory, DAB+ digital broadcast, Wi‑Fi Alliance, BQB Bluetooth, UN R155 cybersecurity, China GB 44495, plus national RF mandatory certifications for every country. Each has its own timeline and compliance requirements – missing any window can delay the whole‑vehicle SOP.
Three core certificates for the head unit – these should be started earliest.
1. Apple CarPlay
CarPlay is an Automotive sub‑project under Apple's MFi licensing programme – the underlying system is MFi – but it uses the Automotive Partner Programme dedicated channel.
Myths: mandatory CarPlay 2.0 in 2026, mandatory DSM interface, mandatory 5 GHz wireless CarPlay – Apple has not issued any such blanket‑rule announcements. Facets 3 is a test‑tool iteration – it is stricter – but there is no publicly announced 2026 mandatory‑upgrade requirement. Wireless CarPlay supports 2.4 GHz + 5 GHz dual‑band – it's not 5 GHz only.
Front‑load whole‑product CarPlay – from Partner access to certificate – 6–9 months is normal. Aftermarket wireless dongles are faster. The 30 ms latency figure is an industry lab experience value – not an Apple public hard metric – but many fail it in practice.
Wireless CarPlay projects require BQB and Wi‑Fi Alliance certification first – this is a commercial‑project access prerequisite – not a statutory regulation – but labs indeed won't accept wireless CarPlay testing without them. Timelines: BQB + Wi‑Fi must be scheduled before CarPlay.
2. Android Auto
Google's system. After the 2026 rule upgrade, testing is fully automated – no manual intervention. Five fixed steps: application/signing, development/self‑test, authorised‑lab L‑Testing, remediation/retest, Google final review. Test suites: CTS, Qsuite, VRRT, Plugbot USB stability, AOAP protocol. Aftermarket wireless products add Wi‑Fi interference and link‑stability tests.
From kick‑off to certificate: 6–10 months – wired vs. wireless difference is small – wireless adds 1–2 months. Android Auto is a commercial‑agreement cycle – there is no mandatory annual certification renewal – agreements can be re‑signed, it's not product‑certificate expiry.
Android Auto does not mandate BQB and Wi‑Fi certificates – but Bluetooth discovery speed and Wi‑Fi link bandwidth are assessed in testing – without certificates, you may fail at the test stage.
3. HUAWEI HiCar
Since V6.0 became fully mandatory, requirements have significantly upgraded: 84 new test cases, three features made mandatory. Sample quantities: based on Huawei project assessment – not fixed bench sets + vehicle. Equivalent‑test eligibility: determined by Huawei – it's not automatic based on scenario compliance. Chip changes or major system architecture changes generally disqualify equivalence.
The three certifications are independent – but hardware design can be shared. The same head‑unit mainboard can do CarPlay and Android Auto – underlying hardware and stacks are reusable – just pass each test separately. Build the hardware platform first – then run the three certifications in parallel – much more efficient.
二、Emergency Communication Certifications
The EU has mandated eCall for all new vehicle types since April 2018. In 2026, the requirement is NG eCall under Regulation (EU) 2015/758. Testing follows EN 16454 and EN 16072 – covering in‑vehicle system testing and PSAP compatibility.
Common confusion: eCall is a technical item under whole‑vehicle EC type approval – only the whole vehicle can get EC type approval. A T‑BOX component cannot obtain an eCall type‑approval certificate alone – it can only provide test reports to the OEM. NG‑eCall mandatory date: for EU M1 new vehicle types after 31 December 2026, NG‑eCall is mandatory – old eCall is no longer accepted for new models.
Russia and EAEU: the equivalent is the ERA‑GLONASS system – similar test framework – but communication protocols and backend access are different – vehicles sold to the EAEU market need separate certification.
三、Digital Broadcast Certification
DAB+ digital audio broadcast – the mandate is not EU‑wide. It's based on individual member‑state legislation – e.g., UK, Norway, Denmark. There is no EU‑level requirement that all new vehicles must have DAB+. Certification follows ETSI EN 300 401 – testing receiver sensitivity, interference resistance, service following, and emergency‑broadcast triggering.
DAB+ intersects with whole‑vehicle EMC certification. The in‑vehicle receiver's performance in the whole‑vehicle electromagnetic environment is the criterion – so you need to account for whole‑vehicle factors at the pre‑test stage.
四、Wireless Communication Certification Systems
In‑vehicle wireless functionality is more complex than a phone: Wi‑Fi, Bluetooth, 4G/5G cellular, V2X, NFC – each has its own certification.
·Wi‑Fi Alliance and BQB – two independent systems. Wi‑Fi – mainstream certification path: 4–6 weeks from application to certificate (lab man‑hours only – excluding pre‑remediation and scheduling).
·BQB Bluetooth – in‑vehicle scenarios mostly use EPL listing with already‑certified modules. EPL requires the module's DID to be Component type – End‑Product type DIDs cannot be used for whole‑product EPL listing.
·FCC Part 68 – applies to traditional PSTN wired terminals connecting to the public telephone network. In‑vehicle cellular 4G/5G T‑BOX does not use Part 68 – it follows FCC Part 22/24/27. This is a common confusion – Part 68 is for wired phones – not in‑vehicle cellular modules.
五、Cybersecurity and Information Security Certifications
The biggest change area in recent years.
1. UN R155: a UN regulation – only binding in countries that have adopted it as their national type‑approval framework – not automatically mandatory worldwide. Mandatory for new vehicle types from July 2022 – covering all new‑production vehicles from July 2024. China's vehicle‑announcement and CCC systems do not directly mandate UN R155 – China uses GB 44495.
2. ISO 21434: an engineering process standard. UN R155 mandates CSMS system audit – it does not mandate a third‑party ISO 21434 certificate. A company‑built system satisfying R155 is sufficient – no need to obtain a separate ISO 21434 certificate.
3. China GB 44495-2024: standard publication date 1 January 2026 – but per Amendment No.1, new announcement applications are mandatory from 1 July 2026 – existing production models from 1 January 2028. Similar to UN R155 – but not equivalent – no mutual recognition.
4. EN 18031: cybersecurity standard under RED Article 3.3 – applies only to radio equipment with connectivity capability. Whole‑vehicle automotive head units are excluded – they are not within scope. Only standalone external wireless accessories – not vehicle‑integrated – are subject to EN 18031.
六、Country‑Specific Market Access
Each region has its own mandatory certifications: US FCC ID, Canada ISED, EU CE RED, China CCC and SRRC, Brazil ANATEL, Japan MIC, Korea KC, Thailand NBTC, Malaysia SIRIM. Each additional target market adds another line to the list. Modular design can reduce this complexity – if the wireless module already has certification in the target market – the whole product can take a simplified path.
七、How to Schedule
1.Define target markets.
2.Pull the full certification list.
3.Schedule by dependency.
·Hardware and safety certifications first: BQB, Wi‑Fi Alliance, CE RED safety, FCC ID, UN R155 CSMS – these are foundational – start before product finalisation.
·Middle layer: phone‑projection certifications – CarPlay, Android Auto, HiCar – depend on foundational results but have long lead times – allow sufficient buffer.
·Regional access: eCall, DAB+, CCC, ANATEL – some can run in parallel with foundational RF and safety certifications – not necessarily serial.
Practical advice: don't try to do everything at once. Phase by market – get the first target market's mandatory items done – then add other markets after product launch. Your certification team won't be overwhelmed – and cash‑flow pressure is lower.
Certificate lifecycle management is ongoing:
·CarPlay and Android Auto – commercial‑agreement renewals – not certificate expiry.
·BQB changes – require updates.
·UN R155 – annual surveillance.
·CCC – 5‑year renewal – plus unannounced inspections.
Put a full calendar together – don't miss any window.
For connected vehicle certification panorama, contact BlueAsia at 13534225140 (King) or email king.guo@cblueasia.com.
