SmartDeviceLink

Features

In-vehicle core

• Manages the physical discovery and logical transport connection to a mobile device application
• Can support white-labeled, multi-function but single application use cases, as well as single app, single function use cases
• Provides a consistent interface for applications to understand the capabilities of an in-vehicle head unit
• Manages and maintains the state of connected mobile applications and notifies applications of appropriate state changes
• Wraps in-vehicle services such as buttons, displays, voice, menu systems, audio controls and other common vehicle inputs and outputs to a common messaging format and API
• Is expandable to allow for specific OEM or head unit manufacturer APIs or messaging
• Creates a template- and meta-based UI that creates consistent developer experiences regardless of the actual HMI representation

  Mobile proxy components

• Provides a common, abstracted interface to the In-Vehicle Infotainment system to integrate to SmartDeviceLink-enabled mobile applications
• Is available for Android and iPhone applications
• Supports TCP, Bluetooth and Apple-specific protocol implementations for transport, and can be expanded to include other transports
• Simplifies transport discovery, connection, and protocol use
• Is expandable to allow for specific-OEM or head unit manufacturer APIs or messaging

  Step By Step Concept of SDL

• Smart device and car connect via standard protocols like bluetooth and wifi.
• Application will make requests to the vehicle and the vehicle responds. Application appears to be running inside the vehicle, but all business logic is contained on mobile device.
• User interacts with their vehicle and vehicle notifies application of any system or user events
• Application reacts by sending requests to modify application behavior or appearance in the vehicle.