Meta description: Huawei HiFind certification, as far as it can be established publicly. We cover ecosystem onboarding, BLE extended advertising, sample submission and how access is maintained, and set out where the Bluetooth 5.0 threshold and single-beacon positioning limits actually fall.
HiFind reverse car-finding is a capability inside Huawei's automotive BU ecosystem, the smart automotive solutions side of the business, and it is handled by the automotive team rather than the digital power line. There is no standalone HiFind certification document, SDK or test specification published on the Huawei Developer Alliance, and most of what circulates online is second-hand material recirculated between posts.
For a car-maker project, the first task is to pin down the interface contact and the requirements in force that quarter before any schedule discussion starts. What follows separates the parts that can be confirmed publicly from the parts that reflect vendor practice and remain unverified.
A company already inside Huawei's automotive ecosystem that adds a HiFind product line usually does not repeat the full qualification review. Product-level acceptance is a separate matter, though: each product is assessed on its own and the product databases do not talk to each other, so getting product A through does not carry product B along with it.
Product access generally carries no direct certification fee, although individual commercial agreements may set out revenue sharing tied to the product. That sits in a different budget line from testing and acceptance costs, and the two should be planned separately. Entity qualification looks at the business licence and the actual controlling relationship, and shell companies or arrangements held through a proxy tend to be refused, which makes it worth cleaning up the shareholding structure early rather than late.
The Bluetooth version is not negotiable. BLE extended advertising arrived with Bluetooth 5.0. Baseband implementations at 4.2 and below simply cannot support it, and no custom firmware will conjure the capability, so a chip in that class should be ruled out at selection stage.
Where distance and bearing come from. The head unit broadcasts a BLE extended advertising beacon. A Huawei phone receives it and, using a private protocol together with multi-sensor fusion on the phone, works out distance and bearing. Raw RSSI on its own will not do the job: in an underground car park, multipath interference pushes the error wide, so antenna position, gain and advertising parameters have to be tuned as one set.
One point that is easy to miss: HiFind packs private beacon data into the extended advertising packet. Meeting the hardware requirements is only the entry condition, and the protocol stack still has to adapt to Huawei's private content.
There is no single published testing fee for this programme. The sensible order is to stabilise BLE advertising and power consumption domestically first, then go through Huawei's authorised channel, because arriving with known problems usually wastes the trip. Who performs the testing, and whether HiCar's authorised laboratories can be reused, has to be confirmed with the automotive team; there is no fixed laboratory list published at the moment.
Sample counts follow the product form. Front-installation work leans on benches plus a complete vehicle, while aftermarket units start at one set. Recording advertising intervals and power curves during pre-testing means intake can be checked against real data and a full round of correspondence avoided.
Product acceptance carries no preset expiry date. Whether the access stays valid hangs on two things: renewal of the top-level automotive ecosystem cooperation agreement when it falls due, and fresh acceptance if the RF hardware or the beacon protocol changes materially. Keeping the framework agreement alive while changing the hardware protocol still means going through acceptance again. HiCar's certificate validity rules belong to a different scheme with different origins, and applying them here puts the renewal milestone in the wrong place.
Bluetooth 5.0 is the hard threshold for extended advertising. Chips below that level do not support it natively, and emulating extended advertising through custom firmware carries real stability risk, so hardware with native support is the safer selection.
A single beacon does not deliver bearing. One BLE beacon can only output distance-related information; direction has to come from somewhere else. HiFind uses a single vehicle beacon together with the Huawei handset's IMU and sensor fusion, which means no multi-beacon layout in the vehicle and no Bluetooth AoA. Multi-beacon triangulation is a different indoor positioning approach altogether, and the two should not be mixed at design stage.
Four questions are worth settling with the automotive team before a schedule is drawn. Which entity signs the commercial agreement, and whether the shareholding structure is clean enough to pass qualification review. Whether the chipset supports extended advertising natively at Bluetooth 5.0, since a firmware workaround is not a foundation to build a product line on. Whether the existing HiCar authorised laboratory can be reused, or a different channel applies. And what the current interface contact requires in writing, rather than what the last circulated summary claimed.
Where a project needs HiFind pre-verification and Bluetooth BQB on the same hardware, BlueAsia runs both workstreams against a single sample set and keeps the interface questions with the Huawei automotive team as they arise.
Contact: King
Email: king.guo@cblueasia.com
Address: Building C, Hongjingda Industrial Park, No. 107 Beihuan Road, Shiyan Street, Bao'an District, Shenzhen, China BlueAsia delivers more than service!
相关新闻
