AUTONOMOUS & CONNECTED VEHICLES
Bluetooth and the road to a keyless future From hands-free calling to tire pressure monitoring systems, Bluetooth has
Efforts are underway to let smartphones double as car keys.
revolutionized the way we interact with our vehicles and how the vehicle itself communicates with other technology systems and services. So, what’s next?
ERIK PETERS DIALOG SEMICONDUCTOR
Improved internet connectivity and other technological advancements have resulted in the rising popularity of car rental services such as Zipcar, Turo and Getaround, among others. Further enhancing the user experience for car rental services and owned vehicles alike will be the introduction of fully digital keys. Powered by Bluetooth, digital keys will replace traditional key fobs, allowing individuals to use their mobile devices to unlock and lock their vehicles, adjust cabin temperature and more, with the added layer of security and transparency of real-time location tracking and instant connectivity that Bluetooth provides. As a result, accessing, starting and securing your car will be easier than ever before.
OEM backend TSM OEM proprietary
OEM proprietary
SE provider proprietary
Mobile UI TUI TEE
NFC
42
DESIGN WORLD — EE NETWORK
Dialog — A&CV HB 08-19_v2.indd 42
SE provider
SE provider agent
Secure element (eSE, UICC)
8 • 2019
A diagram provides a high-level architecture highlighting the focus of the Car Connectivity Consortium including the interfaces to be standardized. Here, TSM stands for Trusted Service Manager. It enables service providers (OEMs) to distribute and manage their contactless applications remotely by allowing access to the (embedded) secure element in smart devices. Mobile UI is an interface between OEM/TSM and the smart device. This is also known as the OEM application. Secure Element is secure storage on smart device. It can be in the form of an embedded Secure Element or UICC Secure Element. SE Provider is the owner of the SE which provides SE access to a TSM. An SE Provider Agent is an SE access interface for the SE Provider. It may be accessed by the SE provider via a proprietary interface/functions. TU is Trusted User Interface. It is usually part of the TEE, Trusted Execution Environment. This is a secure application environment on the host application processor.
eeworldonline.com | designworldonline.com
8/9/19 10:31 AM
