Asking what standard CarPlay follows is the wrong starting point. It is not a regulator-issued access scheme in the way CE or FCC is. Apple's MFi pages list CarPlay, digital car keys and vehicle infotainment among the MFi technologies, and CarPlay belongs to that system.
There are three layers to the basis: documents at the protocol layer, the platform and laboratories at the test layer, and the licence agreement at the contract layer. Only when all three are satisfied does it make sense to speak of legitimately carrying the CarPlay mark.
Aftermarket head units, wired-to-wireless adapters and dongles go through the MFi accessory programme. The company signs a non-disclosure agreement, pays an annual fee, builds in an Apple-authorised authentication component, and runs testing on Apple's automated platform.
Factory head units are not governed by the accessory programme at all. The rules, the component approach and the commercial terms are negotiated separately. When an OEM customer is directed onto the accessory route, the direction is wrong. On CarPlay projects, BlueAsia cuts the first slice at exactly this question of which route applies.
One point is regularly written the wrong way round: the claim that a factory installation does not need to implement iAP2 because it does not go through MFi does not hold. iAP2 is CarPlay's link and session protocol, and control commands and audio and video streams all travel over it. What genuinely splits in two is authentication - aftermarket projects use Apple's authorised standard component, while the factory route's hardware authentication is settled between Apple and the carmaker.
Wired CarPlay sits on iAP2, the iPod Accessory Protocol 2, and not on AirPlay. In a wireless installation, iAP2 handles Bluetooth pairing, Wi-Fi negotiation and control signalling, while AirPlay carries only the audio and video transport layer. Call it an AirPlay protocol family and the search for documents goes off in the wrong direction.
The specification text is published on the MFi portal. The main body is the accessory interface specification, with a CarPlay addendum on top, and both sit under the non-disclosure agreement and may not be passed on.
Aftermarket accessories have to use an Apple-certified authentication component, which completes the encrypted handshake with the iPhone. Without that part, the product cannot legally be sold.
The factory route does not use that standard component approach, and how hardware authentication is implemented is agreed between Apple and the vehicle manufacturer. Applying the aftermarket component rules to a carmaker is another common error.
Formal testing has to be carried out at an Apple-authorised laboratory, against Apple's automated test suite, with cases generated by the system and judged by machine. Apple does not accept conclusions from a manufacturer's own in-house testing, but the party submitting samples can be the manufacturer itself, provided the MFi process has been completed. When arranging a submission, confirm the laboratory's authorisation and its available slot first.
At the self-test stage the toolchain supplied by Apple is used, and it is not the same thing as the self-certification tooling for ordinary audio accessories. Treating the two as one wastes a round.
The following come from the MFi licence agreement and apply to aftermarket projects; factory commercial terms are negotiated separately between the carmaker and Apple.
The grant is limited, non-exclusive, personal, non-sublicensable and non-transferable. It therefore cannot be bought or sold as an asset, nor borrowed across entities.
Certification materials are submitted in two batches: one when the first prototype is complete, and another once the prototype is production ready, and that second one no later than thirty days before commercial production, sale or distribution begins.
Apple has full discretion over whether a product plan is approved, and sourcing components before approval is at the applicant's own risk. Where a product fails testing, sales and distribution have to stop immediately.
On a wireless CarPlay link, the Wi-Fi side goes through Wi-Fi Alliance certification, and the Bluetooth side has to complete the Bluetooth SIG's qualification process. In the alliance's own words that process is called the Bluetooth Qualification Process, declarations and listings are made on its qualification platform, and the product receives a Design Number, or DN. Numbers issued before 1 July 2024 were called QDIDs, which is now a historical term. Using the Bluetooth word mark on the device, the packaging or promotional material depends on that step, and the product name and model have to match what is sold. Both of these are issued by industry associations and are not the same thing as Apple's authorisation; neither substitutes for the other.
CarPlay Ultra is on the road only in Aston Martin vehicles for now. Hyundai, Kia and Genesis have signed up but have not announced models or timing.
Existing models whose hardware qualifies can be opened up by the manufacturer through a software update, which is how Aston Martin rolled it out. That is not a general rule, though - whether other brands can be upgraded depends on the manufacturer's own plans.
Contact: King Email: king.guo@cblueasia.comAddress: Building C, Hongjingda Industrial Park, No. 107 Beihuan Road, Shiyan Street, Bao'an District, Shenzhen, China BlueAsia delivers more than service!
Related News
