Nothing wastes time like sending samples only to have Huawei reject your application due to missing documents – then you lose two weeks and your lab slot. Here’s a stage‑by‑stage list to get it right first time.
Must include: model, hardware version, supported HiCar version (wired/wireless/both), resolution, audio output, USB interface specs. Huawei is strict on functional descriptions – “supports wireless projection” without detailing protocols will be rejected. Follow their template.
1.1 Hardware Description
Main SoC, Wi‑Fi module (for wireless), USB PHY, audio codec – Huawei needs to confirm performance.
1.2 Feature List – Critical
List every HiCar feature: basic projection, audio pass‑through, touch control, voice assistant, multi‑screen. Whatever you list must be tested – omissions cause terminal re‑testing.
2. OEM Front‑Load Vehicle Path
For OEMs: higher documentation – vehicle integration plan, HiCar integration design, full‑vehicle EMC report. Sample requirement: two bench sets + one production vehicle. Don’t use aftermarket templates.
2.1 Aftermarket Head Units and Dongles
Submit via Huawei’s DevicePartner platform – classified as front‑load, aftermarket, or dongle. Required: application form, spec sheet, RF and EMC reports.
Important: HiCar is completely independent of Apple MFi, iAP2, or CarPlay Entitlements – no shared channels or authorisations.
2.2 Three Equivalence Paths
·Full initial – new product, full testing.
·Equivalence A – minor hardware changes, partial re‑test + samples.
·Equivalence B – only cosmetic/UI changes – document‑only, no samples.
Choose correctly to avoid wasted effort.
3. Test Plan Document
Describe expected performance for each test item – USB timing, wireless connection flow, audio‑video sync, touch latency – Huawei will compare against actual results.
3.1 Interface Protocol Document
Detail USB enumeration, AOAP handshake, 802.11 P2P establishment, audio routing, video transport. Note: wireless HiCar uses Bluetooth BLE discovery + 802.11 P2P, not generic Wi‑Fi Direct – don’t confuse them.
3.2 RF Performance Report
For wireless products: Tx power, Rx sensitivity, antenna gain, throughput, isolation.
Caveat: If you export to EU/Korea, Huawei will check for accredited third‑party RF reports – internal debugging reports are not sufficient.
3.3 EMC Report
For automotive: CISPR‑25 (vehicle components) – not CISPR‑32 (household IT). Existing CE/FCC reports are accepted if they cover Huawei’s required items; otherwise, supplement.
4. Firmware Version and Change Rules
The submitted firmware must match your internal test records.
·UI animations, colours, wallpapers – if no change to Bluetooth/Wi‑Fi/HiCar authentication/audio‑video/touch – can be documented only.
·Any change to audio routing, Wi‑Fi reconnection, Bluetooth pairing timing – even if RF hardware unchanged – requires re‑testing of affected functional cases.
4.1 Software Architecture Description
Show the software layers (application, middleware, drivers, OS) and where the HiCar stack fits.
4.2 Cybersecurity Documents (from 2026)
Products with network capability need a cybersecurity risk assessment. Reports from EN18031 or UN R155 can be reused only if they cover aftermarket telematics threat analysis and OTA verification – a whole‑vehicle security report alone is not enough.
5. Sample Quantities – Three Categories
·Aftermarket dongle/head unit full initial – 3 production samples.
·Front‑load OEM – 2 bench sets + 1 road‑ready vehicle.
·Equivalence B – no samples, only documents.
Samples must be from mass‑production batches.
5.1 Antennas and Cables
Wireless products – supply the same antennas as retail packaging. Wired products – supply the retail USB cable (lab’s generic cable won’t be used).
5.2 Test Phone List
Huawei provides a list – mandatory models and recommended. Missing a mandatory model causes re‑test (2–3 weeks). If you claim support for a recommended model in marketing, you must test it – otherwise you can skip it. Always confirm the list version before submission.
6. Test Report Package
Includes all pass/fail records, data, and anomaly logs. Two major rejection causes: incomplete test coverage and parameter mismatch with documents.
6.1 Technical Documents (Final)
Final spec sheet, test plan, interface protocol, firmware version note, cybersecurity file – all must match the actual submitted samples.
6.2 Declaration of Conformity
Signed by legal representative, committing that the product meets Huawei HiCar specifications and that design changes will be notified.
For HiCar certification documentation, contact BlueAsia at 13534225140 (King) or king.guo@cblueasia.com.
Related News
