For automakers planning to launch smart vehicles and in-vehicle equipment into overseas markets, GMS certification is an indispensable step that cannot be bypassed. This certification not only determines whether a vehicle can legally use Google's in-vehicle services but also directly impacts the product's competitiveness and user experience in international markets.
I. GMS Certification: The "Passport" for Smart Vehicles to Enter the Global Market
GMS stands for Google Mobile Services; its counterpart for in-vehicle applications is Google Automotive Services (GAS), which encompasses core Google automotive applications such as Google Play, Google Maps, Google Assistant, and YouTube. These services represent essential offerings for overseas users, analogous to platforms like WeChat and Alipay in China.
The Android Automotive OS (AAOS) is an open-source, free operating system; however, pre-installing the GAS suite requires Google's authorization. Vehicle devices that have not completed GMS certification cannot legally use Google services, resulting in weak competitiveness in overseas markets and difficulty in gaining recognition from consumers and distribution channels. Leading automakers such as General Motors, Ford, Volvo, and Polestar have all adopted AAOS and completed GMS certification.
II. Certification Agreements: MADA and EDLA
GMS certification primarily involves two types of protocols, categorized according to device type:
The criteria for determination are straightforward: devices that do not include a battery or have screens larger than 18 inches must undergo EDLA certification. The vast majority of in-vehicle infotainment screens exceed 18 inches in size and do not include a battery; therefore, they must complete GMS certification using the EDLA protocol. Additionally, there is the GAS protocol (Google Automotive Services), which is specifically designed for in-vehicle device applications seeking GMS certification and serves as the exclusive protocol for the automotive domain.
As of June 2026, the MADA certification requires Android version 16 or higher, while the EDLA certification requires Android version 15 or higher and must be completed by January 2027. Automotive devices typically run on the AAOS platform, and their version rollout schedule should closely align with Google's official release timeline.
Core Test Suite (xTS)
In-vehicle GMS certification requires compliance with a series of rigorous tests defined by Google, collectively known as the xTS Test Suite. These tests cover multiple dimensions, including the compatibility of in-vehicle systems, underlying hardware adaptation, the completeness of Google service functionality, and system security. All tests must be conducted either in an actual vehicle environment or on a Hardware-in-the-Loop (HiL) test bench to ensure that all in-vehicle components – from software to hardware – fully meet Google's standard requirements.
Important Note: The in-vehicle EDLA certification must successfully pass all the aforementioned test items. It is recommended to conduct a comprehensive pre-test before submitting the device for formal certification; this approach can effectively mitigate over 80% of common issues and significantly reduce the risk of failure during the formal testing phase.
Post-certification maintenance
Passing certification does not mean a one-time solution; automakers must establish a continuous maintenance mechanism:
SMR (Security Maintenance Release): The EDLA on-board equipment requires security patches to be updated every 3 months, with a total of 8 maintenance updates over a 2-year period; this imposes stringent requirements on the OTA update capability for already sold vehicles.
MR (Maintenance Version): The in-vehicle software version has been updated; all tests must be re-performed.
LR (Major Version Upgrade): Upgrading from Android 15 to 16 requires retesting according to the new standards. Major version upgrades for AAOS are typically planned in sync with the annual model refresh cycle.
III. Certification Cycle and Process
The Google Mobile Services (GMS) certification cycle typically ranges from 6 to 8 weeks (the EDLA protocol cycle is slightly longer than the MADA cycle), depending on how quickly the R&D team resolves testing issues (failures). Google recommends that manufacturers reserve a full 12–18 month certification timeline. The core process is as follows:
1. Sign the GAS/EDLA Agreement and submit a certification request to Google.
2. Confirm that the selection of hardware components (such as the SoC [e.g., Qualcomm Snapdragon automotive-grade chip], display, microphone, and power amplifier) complies with Google's CDD requirements.
3. Integrate the GMS package with security patches, and prepare a prototype (full vehicle or HiL test bench).
4. The laboratory conducts preliminary testing and provides feedback on identified issues.
5. The R&D team fixes the issue and submits a new version of the software.
6. Official submission to the 3PL laboratory for testing
7. Google's final review; upon approval, authorization is granted.
IV. Zhongle Certification: Professional Support for the Global Expansion of On-board GMS Solutions
Zhongle Certification specializes in Google-certified services such as GMS, EDLA, MADA, and GAS. With extensive practical experience in the automotive sector, the company provides automotive manufacturers and Tier 1 suppliers with pre-selection evaluations for hardware components, full-process pre-testing support, and one-stop overseas expansion solutions. These services cover mainstream domestic connectivity standards—including ICCOA Carlink—and address the dual compliance requirements for both domestic and international markets, thereby facilitating the successful global market entry of smart vehicles and in-vehicle equipment.
Tel: 13417442373(Wechat)
E-mail: finny.zhou@zhongletest.com
Teams:nancy.le@zhongletest.com
