scope:

The present document is part of the MirrorLink^® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms.

MirrorLink is a single protocol that defines how a MirrorLink enabled Client device (typically the consumer's in-vehicle infotainment system) and a MirrorLink enabled Server device (typically the consumer's mobile device) communicate and provide an integrated consumer experience, where the MirrorLink Server is creating the consumer experience, running MirrorLink applications, whose user interfaces are presented via the MirrorLink Client. Consumers will only interact with the MirrorLink Client device, leaving the MirrorLink Server device stored away, allowing for responsible interactions, while the vehicle is in motion.

The MirrorLink protocol enables mobile device's consumer experience to be projected on the in-vehicle infotainment system. It enables the consumer to use the controls of the infotainment system to manipulate the mobile device. By using applications, following application-level requirements, either for use in drive or non-drive situations, consumers will see an experience optimized for the current situation.

Whereas the MirrorLink protocol specifies a consumer experience, it is open to implementation specific decisions and variations from Client and Server manufacturers. Differentiation in the consumer experience and supported features is encouraged. However, MirrorLink does need to be predictable and recognizable to the consumer. It is also critical for a MirrorLink brand recognition.

The present document specifies the basic consumer experience, for which MirrorLink stands for and many of the features MirrorLink enables. The present document intends to focus on the consumer experience level and does not intend to replace any requirements of the other technical specifications. Whether or not a MirrorLink Client or Server device follow the requirements defined within the present document will be mainly evaluated and tested through IOP testing, as outlined in more detail in the IOP test specification [1].