People doing HiCar certification often get confused. Huawei's official material list looks short – but when the review actually happens, items are missing, documents are returned for correction – two or three months disappear. Where's the problem? The official list is the skeleton – in practice, every file has hidden hard requirements – you only find out how deep the water is when you fall in.
I'll break down the submission details for every core HiCar certification document under the 2026 V6.0 protocol. Many of these requirements are not written in public documents – they're lessons learned from having documents returned by reviewers repeatedly during actual certification runs.
Before entering the formal certification process, Huawei has a partnership‑access stage. This stage doesn't look at product technical details – it looks at whether your company is eligible to do HiCar integration.
1.1 Business licence copy (scanned). Scope review looks at business relevance – not keyword matching. Companies doing aftermarket integration or R&D design – with scopes like "electronics R&D" or "software development" – can pass. Missing the word "automotive" won't automatically cause rejection. But if your scope says "catering services" or "education consulting" – that's a different story.
1.2 Huawei Developer Alliance enterprise account registration credentials and signed HiCar Ecosystem MOU. These are the partnership threshold – no MOU, no certification application. The MOU is signed online via the Huawei Developer Alliance platform – electronic signature is legally effective – no need to print and stamp. But your legal team should review the confidentiality and IP clauses.
1.3 Quality system: there's a common misunderstanding. An ISO 9001 certificate is a plus – but it's not a hard requirement for access. Equivalent quality‑control evidence can also work. IATF 16949 is industry practice for front‑load OEMs – HiCar access rules do not list it as mandatory – not having it won't automatically kill the project. When reviewing certificates, don't just look at the cover – if the certification scope is unrelated to your product, you'll be questioned.
2. Product Technical Documents
This is the core review material – and the highest‑rejection area. Huawei is increasingly strict on the authenticity and traceability of technical documentation.
2.1 Product specification sheet. Hardware configuration must be clear – memory, storage, processor model, interface types, wireless module model – don't just write "supports Bluetooth and Wi‑Fi." Software architecture – head‑unit system version, HiCar SDK version – for new projects submitted after 1 July 2026, V6.0.0 or above is mandatory. Existing projects already running on older versions may continue with V5 – it's not a blanket cut‑off. Functional descriptions must go down to the protocol‑level implementation.
2.2 Circuit schematics and PCB layout. Critical component locations, antenna positions, and encryption‑chip locations must be clearly visible. Schematics must match the physical board – reviewers randomly cross‑check – inconsistencies = direct return.
2.3 HiCar SDK integration documentation. Use Huawei's V6.0 template – download from DevicePartner. Include software architecture diagrams, SDK module call relationships, and API interface lists. Only Linux head units using specific compilation environments and custom build chains need to attach the SDK compilation‑toolchain import declaration – not all Linux head units require it.
2.4 Software/hardware resource constraint table – V6.0.0. This is the critical pre‑certification self‑check document – CPU usage, memory usage, storage usage, USB bandwidth, Bluetooth link bandwidth – all real data.
3. Self‑Test Stage Materials
Huawei requires manufacturers to run test cases themselves before sending to the lab. Note: not all test cases must unconditionally pass. Features your product doesn't support can be marked "not applicable" – with sufficient justification – Huawei will accept it. Don't force‑run all cases unnecessarily.
3.1 Self‑test report. Use the HUAWEI HiCar Vehicle Access Acceptance Self‑Test Report V6.0.0 template. Each test record must include screenshots, logs, or video evidence – blurry or unreadable ones won't be accepted. Self‑test execution count, pass count, failures, and failure reasons – all must be itemised.
Test tools – download from DevicePartner: head‑unit side PCM stream capture tool, Bluetooth verification tool, audio‑stutter source files, voice corpus, video‑smoothness test tool, projection‑clarity test tool, and HarmonyOS 4.x + 6.x phone log capture tools. Note: V6.0.0 self‑test baseline is HarmonyOS 4.x + 6.x – HarmonyOS 5 is not the primary test baseline. Tools are meant to be used – results must be attached to the self‑test report.
3.2 Equivalent test application form. This applies to projects where hardware is unchanged – only minor software version iterations. New hardware models cannot use equivalence – don't apply just because the project is new. The form must be submitted in advance – Huawei must approve before equivalent testing can proceed.
4. Lab Acceptance Stage Materials
After entering lab acceptance testing – front‑load and aftermarket sample requirements are not the same.
4.1 Aftermarket products generally don't require full test benches – provide mass‑production samples. Samples must run stable production firmware – no engineering prototypes.
4.2 Front‑load projects require full functional benches – screen, power supply, microphone array, speaker, steering‑wheel controls, GPS antenna, and all cables – missing any one = rejection.
4.3 Whole‑vehicle submission: 1 vehicle + 1 bench set. Vehicle software/hardware must match mass‑production configuration – no pilot‑build vehicles. Temporary plates: valid for at least 90 days – test area covering the lab's city. Insurance: compulsory + commercial. In‑vehicle SIM card: at least 500MB/month traffic.
4.4 Product nameplate and serial number list. Nameplate information must match technical documents. Sample serial numbers and production‑nameplate serial numbers are two different things – the production Model ID is tied to the model, not to an individual sample's serial number – don't confuse them.
5. HiCar Certification – Review and Issuance Materials
Lab testing passing is not the end – Huawei still does a final document review.
5.1 Acceptance test report – issued by Huawei‑authorised labs – using the HUAWEI HiCar Vehicle Access Acceptance Test Report (Lab Version) V6.0.0 template. The lab issues the report and evidence materials.
5.2 Model ID application form and launch promotion feedback form. Model ID is Huawei's assigned identifier for each certified product model. This form is not submitted after all testing is complete – it must be completed during the certification application stage – don't get the timing wrong.
5.3 Paper documents – technical documents, application forms, equivalent‑test application forms – must be stamped with the company seal. Online e‑signed MOUs and agreements do not require physical stamps. Company name and unified social credit code must be consistent across all documents.
6. Wireless Products – Additional Materials
HiCar certification itself does not mandate BQB or Wi‑Fi Alliance certificates – not having them won't directly terminate the HiCar process.
However: in actual testing, Bluetooth discovery speed and Wi‑Fi link bandwidth are mandatory test items. If the module or whole product lacks basic compliance certification and RF metrics don't meet requirements – testing fails. Practical recommendation: complete Bluetooth BQB and Wi‑Fi Alliance certification before HiCar certification. For BQB EPL listing – the module's DID can be Component or Subsystem type – both support whole‑product EPL listing. Only an End‑Product Primary DID cannot be used for another whole product's EPL. Wi‑Fi Alliance certification ensures band coverage matches HiCar requirements.
7. HiCar Certification – Document Preparation Timeline
·Qualification documents: 1–2 weeks – provided certificates are valid and not expired.
·Technical documents: 2–4 weeks – depends on R&D team efficiency.
Self‑test stage – cannot be generalised. Teams already familiar with V6.0 templates – aftermarket adapter products – 2–4 weeks. Brand‑new development – complex front‑load cockpit projects – can run to several months. Don't use aftermarket timelines to estimate front‑load schedules.
Before submitting all documents: run a full self‑check. Company name, product model, and configuration parameters must be consistent across all documents. Version numbers, dates, and stamps must not be missing. One document wrong – the entire package is returned.
For HUAWEI HiCar certification documentation, contact BlueAsia at 13534225140 (King) or email king.guo@cblueasia.com.
相关新闻
