With the commercial launch of HarmonyOS NEXT, this year's HUAWEI HiCar ecosystem access standards have seen a major overhaul. Those working on front‑load head‑unit projects have clearly felt the difference – the test baselines and review requirements are now significantly different from previous years.

Previously, HiCar certification was version‑based – products were tested against the SDK version they adapted. In 2026, the review baseline has shifted to a combined approach: HiCar 6.0 technical specifications + HarmonyOS NEXT adaptation requirements – no longer relying on a single version number. The official baseline SDK version is 6.0.96.16 – new certification submissions must be based on this version or higher. From 1 July 2026, new projects will no longer accept SDK versions 5.0 or earlier. Products already certified under V5 can retain access – following renewal rules during the certificate validity period.

HarmonyOS NEXT native adaptation has become a basic condition for new‑project pre‑review. If the product cannot implement the interactive logic of Super Device and Card Desktop – applications are likely to be rejected at the pre‑review stage. Adaptation work cannot be left until later – from the start of the project, hardware selection, overall software architecture, and interaction design must all be planned around HarmonyOS native connectivity requirements.

1. Security Architecture – Major Upgrades, Multiple Metrics Now in Focus

1.1 Zero‑trust interconnect security framework

This year's certification introduces a zero‑trust interconnect security approach – covering three dimensions: identity trust, device trust, and data trust. After the phone and head unit connect – all instructions from the mobile side must undergo identity verification and permission authentication. The old approach of "once the link is up, trust is assumed" no longer applies – the entire security mechanism shifts to continuous verification throughout the connection.

·Interconnect data encryption: uniformly requires AES-256.

·Encryption/decryption and key storage: must be isolated within a TEE (Trusted Execution Environment).

Products still using early hardware solutions – to build TEE isolation – will likely need to re‑architect the security subsystem. In recent years, many solutions relied on software modules for security – now the focus is on chip‑level security support. Solutions without dedicated security processing units will find it much harder to pass review – only a few may pass through specialised technical difference assessments.

1.2Annual security penetration assessment

After obtaining HiCar access, companies must commission a Huawei‑recognised third party to issue a security assessment report annually. Failure to submit a valid report on time affects ongoing qualification. This requirement took effect in 2026 – and is mandatory.

Penetration assessment scope has expanded – covering head units, in‑vehicle gateways, and remote terminals. Distinguish: powertrain components (BMS, drive controllers, on‑board chargers) – their safety regulations fall under whole‑vehicle access – not within the HiCar interconnect assessment scope. The assessment report is not just a formality – high‑risk vulnerabilities must be closed‑loop remediated – with remediation plans and validation results submitted for review.

1.3Functional safety and in‑vehicle data compliance

Many OEMs set ISO 26262 ASIL‑B as a component delivery standard for front‑load projects – but this is not a HiCar certification threshold – companies should plan based on overall vehicle requirements. For data compliance, reference GB/T 41871. Sensitive user data (location, call logs) must be encrypted and isolated within the TEE during transmission and storage – with users able to view and delete their own usage records.

Data collection strictly follows the minimum‑necessary principle – cannot collect data unrelated to the service. All collection activities must be fully traceable – with complete data‑use and deletion processes. Data compliance has moved from a "nice‑to‑have" to a critical part of the review.

  2. Functional Testing – Stricter Standards – Reserve Hardware Headroom

2.1UWB contactless positioning (optional)

For models with digital keys and contactless proximity unlock – new UWB positioning tests apply. Requirements:

·Positioning error <15 cm.

·Proximity wake‑up success rate >99.5%.

Simply having a UWB chip doesn't guarantee compliance – the algorithm must reliably identify the owner's position in a complex in‑vehicle electromagnetic environment. Lab conditions are relatively easy – real‑vehicle conditions test the entire solution – UWB antenna placement, base‑station layout, and interference‑filtering algorithms – each detail requires iterative tuning. Products without contactless key functionality – do not require UWB positioning tests.

2.2 Multi‑screen collaboration and in‑vehicle voice interaction (front‑load high‑end)

For cockpit solutions supporting multi‑screen collaboration:

·Three‑screen sync (HUD, instrument, centre console): screen sync latency <10 ms – end‑to‑end projection latency <8 ms.

·AR navigation overlay must be smooth – no stutter or offset.

·If video decode compute and bandwidth are insufficient at the selection stage – software cannot compensate later.

Front‑load cockpits with native voice‑assistant integration must support AI multi‑mic noise reduction – pass Cantonese and Sichuan dialect recognition tests – voice wake‑up response <800 ms. Dialect recognition requires sufficient training data – when selecting a voice supplier, confirm they have the relevant test resources. Aftermarket devices that only relay phone voice signals – do not need dialect recognition tests.

2.3Basic wireless connection metrics

For models with high‑end multi‑screen and contactless features:

·Must support Wi‑Fi 6E.

·Connection establishment <2 seconds.

·Auto‑reconnect success rate >99.8%.

·Wide‑temperature stability and in‑vehicle interference resistance are also assessed.

Clarification: -40°C to 85°C wide‑temperature operation is a general automotive component requirement – basic wired HiCar devices and simple wireless dongles do not need Wi‑Fi 6E. For in‑vehicle electromagnetic immunity, reference CISPR 25 – select the appropriate level based on product positioning.

Ultimately, these metrics constrain the entire hardware platform – Wi‑Fi front‑end, UWB positioning chip, video decode unit – performance headroom must be confirmed at the selection stage. Consumer‑grade components generally cannot meet automotive wide‑temperature and long‑term interference requirements.

  3. Certification Process – Key Changes

3.1Manufacturer self‑test review standards raised

Huawei requires manufacturers to complete self‑testing – submitting self‑test records and key‑scenario logs. It does not require screenshots for every test case – just key scenario evidence per the specification. Missing materials = application rejected – but no need to store unlimited screenshots.

Authorised labs can provide specification interpretation, test‑case confirmation, and log‑format checks – but self‑testing itself remains the manufacturer's responsibility. Some outsource full self‑testing – reviewers can detect anomalies in log patterns – such materials will not be accepted.

3.2Equivalent‑test fast track

Huawei offers an equivalent‑test fast track. Meeting the basic scenario conditions does not automatically grant eligibility – companies must submit an equivalent‑test application – the authorised lab issues a technical difference analysis – and Huawei makes the final eligibility decision.

Common confusion: the lab is only responsible for technical difference assessment – not approval. The final decision on whether equivalence is granted rests with Huawei's review team – the lab's assessment report is not an approval conclusion.

3.3Project timeline reference

·Front‑load cockpit devices: formal lab testing 4–8 weeks.

·Aftermarket head‑unit screens and wireless dongles: 3–4 weeks.

This only covers lab testing – excluding self‑test remediation, document revisions, and Huawei final review. Full project timelines are generally longer – budget and schedule accordingly. In 2026, Huawei has tightened post‑market software version management – annual maintenance and version‑change review timelines must also be factored in. HiCar 6.0 series certificates are valid for 1 year – companies must complete annual qualification maintenance on time.

  4. Practical Approach for Companies

4.1Validate hardware platforms early

Metrics like UWB positioning accuracy, multi‑screen sync latency, and Wi‑Fi RF performance – verify at the selection stage. If performance shortfalls are only discovered after prototypes are built – hardware rework is extremely costly.

Headroom: video decode bandwidth, AI compute, UWB processing – reserve 20–30% margin. Lab ideal conditions differ significantly from real‑vehicle environments – insufficient margin leads to real‑vehicle performance failures.

4.2Corporate qualification access – must be self‑managed

The first step in a HiCar project is Huawei Developer Alliance enterprise registration. Third‑party labs cannot handle platform qualification on your behalf. Many clients mistakenly assume labs can do account registration and qualification filing – in reality, labs only provide testing support – platform onboarding must be handled by the company itself.

4.3Choose authorised labs wisely

Different labs have different strengths – some excel at front‑load OEM projects – others at aftermarket peripherals. When comparing:

·Past project cases for similar products.

·Retest ratios.

·Whether peak‑season scheduling aligns with your milestones.

Huawei does not set uniform pricing – labs set their own fees – Huawei only controls test standards and process compliance. Quotes vary significantly – don't only look at price – evaluate project planning, scheduling guarantees, and remediation support capability.

For 2026 HUAWEI HiCar certification, contact BlueAsia at 13534225140 (King) or email king.guo@cblueasia.com.