SmartDeviceLink (SDL) is a standard set of protocols and messages that connect applications on a smartphone to a vehicle head unit. This messaging enables a consumer to interact with their application using common in-vehicle interfaces such as a touch screen display, embedded voice recognition, steering wheel controls and various vehicle knobs and buttons. There are three main components that make up the SDL ecosystem.
- The Core component is the software which Vehicle Manufacturers (OEMs) implement in their vehicle head units. Integrating this component into their head unit and HMI based on a set of guidelines and templates enables access to various smartphone applications.
- The optional SDL Server can be used by Vehicle OEMs to update application policies and gather usage information for connected applications.
- The iOS and Android libraries are implemented by app developers into their applications to enable command and control via the connected head unit.
The SmartDeviceLink (SDL) server handles authentication, data collection, and basic configurations for SDL connected vehicles. In general, these tasks are accomplished using JSON documents called Policy Tables, which the SDL Core component uses to validate messaging with connected applications. The Policy Tables are configured on the SDL server, downloaded through the SDL Proxy and passed along to SDL Core.
This implementation of SDL Server is a reference to help developers understand how SDL works. It is NOT meant to be a production server.
A quick guide to setup SDL server can be found at SmartDeviceLink.com
All documentation can be found at SmartDeviceLink.com.
If you have a suggestion or bug please submit an issue. You can submit code using a pull request, but please follow the contributing guidelines.