SDLP Architecture

SDLP combines the best ideas from two connectivity technologies: iviLink and Smart Device Link. The goal of bringing them together is to combine the flexibility of Profiles with SDL as a transport layer. This creates a unified standard ready to be used by the entire industry.
The SDLP implementation for mobile device supports both SDL/AppLink and iviLink applications. iviLink applications are a set of apps that have been developed for the iviLink solution and now migrated to SDLP. These applications are part of Luxoft AllView demo project.

Profiles

Profiles is the “glue” which connects SDLP core with system specific architecture. In order to connect a mobile app with Head Unit a pair of profiles has to be developed: internal profile for the application and a profile that will be deployed on the Head Unit.
Profile lib serves as a connectivity layer with iviLink applications on a mobile device. Profile manager on a Head Unit controls profiles load, unload and update.
Profiles implement 2 main tasks for the system:
  • Abstraction of system HMI from SDLP core. Profile can be adjusted according to a system specific API so that no refactoring has to be done to enable the support of SDLP.
  • Definition of connectivity logic. Profiles on both sides define how data will be received, processed and presented to the user. And since Profile can contain executable code, it can implement functionality on the Head Unit if even the phone is not connected.
Profiles are also updatable. A New pair of profiles can be developed with an updated version of a mobile app. The next time when a phone is connected, the Head Unit will recognize that new profiles exist and the Profile Manager will install it. Once new functionality is installed via profiles, it’s always available on the Head Unit.
An OEM decides if profiles developed by 3rd party companies will be allowed on the IVI system or if only own OEM profiles will be granted.

Symmetrical Approach

Unlike other technology on the market, SDLP provides a symmetrical approach when a mobile device is not the only source of information for the screen of IVI but the Profile on the Head Unit can decide which data will be presented on screen of the mobile device. This symmetrical approach offers significant advantages compared to an asymmetrical approach, for example:
  • Support of apps acting as additional screen inside the car. Such an app can be installed on the rear seat passenger’s tablet and act as a rear seat entertainment device.
  • Using a mobile device as additional screen for the app. A Front seat passenger can receive complimentary information from IVI Navigation and assist the driver with road orientation (e.g. list of gas stations, tourist attractions and restaurants nearby).

Security

SDLP has the support of various security mechanisms. Basic security is provided by RSA authentication. Whereas SDLP inherits policies concept from SDL which means only the certified application will have access to the Head Unit. Finally, the technology architecture also allows easy integration of OEM-dependent security concepts (e.g. verification from the Cloud).

SDLP Integration To Your System

SDLP is a highly customizable solution. Here are the 2 connectivity paradises that SDLP can implement:

Business Logic Is Split Between Mobile Apps and IVI


Business Logic Is Developed Within Mobile App. IVI Screen Is Used To Present Data From Mobile App To The User

  • Infotainment system has full range of functionality which is available even if the phone is not connected.
  • Car unit features may include radio, diagnostics information, car settings and even navigation.
  • Application on mobile device will extend these features (e.g. possibility to store diagnostics data in mobile app for later view) and add additional infotainment capabilities.
  • Head Unit and mobile apps are developed independently from each other. Only data exchange is implemented via SDLP so that systems can interact with each other.
Advantage:

Suitable for the premium system which has a lot of functionality on HU side. This will help OEM to maintain diversification features and HMI while still supporting mobile apps integration.

  • Infotainment system provides limited functionality. Most of the features are implemented inside apps on mobile device.
  • App generates graphical information and uses SDLP to output it on the screen of Head Unit.
  • Head Unit has only basic functionality and have limited possibilities to work independently from mobile device.
Advantage:

This approach is suitable for entry level systems. In this case Head Unit can perform only simple functions without mobile device connectivity (e.g. radio). All the main functionality will be incorporated into the mobile device. This approach allows easy functionality update. It’s enough just to update mobile app to receive a new set of functions in the Head Unit.

Excited about iviLink?

Delve deep into iviLink`s SDK and explore the possibilities!
-and-
Sign up for iviLink News
to always be up-to-date
Contact us