Technical Considerations of Application Certification

Report
Technical Considerations of
Application Certification
Dr. Jörg Brakensiek
Principal Architect, Nokia
Chair of the Technical Work Group, CCC
Overview
1. MirrorLink®
Concept
2. Deployment
3. Advertisement
4. Meta Information
5. Adaptation &
Control
MirrorLink® Concept
Once connected,
no need to touch or
look at your phone
Connectivity
Data
Access
App Certs
Security
Audio
Display &
Control
Discovery
& Events
MirrorLink® Concept
Common API
MirrorLink® Concept
Most of the MirrorLink Protocol is transparent to the
Application Developers
• UI Mirroring
• Eventing
• Audio streaming
MirrorLink Features important for Application Developers
•
Application Deployment
•
Advertising Applications
•
Controlling the MirrorLink Session
Deployment of MirrorLink® Applications
Submit
App
Enjoy
App
Guidelines
Test Lab
Upload
Test Results
Certificate
Database
User
Design
App Developer
Retrieve Certificate
App Store
App
Smartphone
Install
Head-Unit
Deployment of MirrorLink® Applications
Application
Store
Uniquely identifies an
application and its
version
Self
App
ID
Validity
CCC Certificate
Database
CCC
Head-Unit
• X.509
• Self-signed  CCC signed
Certificate Retrieval
App
Smartphone
Application Certificates
• HTTP GET
• Application Identifier
Check Validity of Certificate
•
•
•
•
Protocol: OCSP
Update available
Revoked
OK (still valid)
Application Certificates – Deep Dive
Signature
Signature Algorithm: sha512WithRSAEncryption
Algorithm
Issuer: O = Car Connectivity Consortium
Certificate Issuer
CN = ACMS CA
Valid from: May 16 2013 3:26:44 AM
Validity Period
Valid to: July 23 2023 3:26:44 AM
Subject: CN = <App ID>
Subject (App Identifier)
1.3.6.1.4.1.41577.2.1:
<certificate>
Certified
...
App Information
</certificate>
X509v3 Authority Information Access:
OCSP Info
OCSP - URI:http://acms.carconnectivity.org/OCSP
Signature
Signature: [...]
Advertising MirrorLink® Applications
MirrorLink Specifics
• User connects the Phone with the Head-Unit
• Phone contains certified Applications
• User uses Application’s User Interface
Advertising MirrorLink® Applications
Phone Call
Are you alive
I am Alive
Who are you
Nokia Music
Launch
Nokia Drive
Terminate
Advertising MirrorLink® Applications
MirrorLink Promise
• All CCC Certified Applications will be advertised from
Smartphones and made accessible from Head-Units
Application’s Certificate contains Advertisement info
• Basic Information
– Name, Description, URL, Provider, Icons
• Meta Information
– App & Content category, Audio Support, Orientation support
• Certification Information
– Locales for Drive & Park mode (result from test labs)
Application’s Meta Information
Head-Unit provides
App Menu to launch
MirrorLink apps
App’s user interface is
mirrored using VNC
protocol
Vehicle’s state (Drive
or Park) defines,
which apps are
allowed
Application’s Meta Information
Prevent Launch of notallowed applications
Block prohibited
content on the
Head-Unit Screen
Application’s UI Adaptation
Adaptation Needs for Apps
Common
API
•
•
•
•
Head-Unit Screen Size / Resolutions
Head-Unit Control Concepts
Head-Unit MirrorLink Feature Set
Smartphone MirrorLink Feature Set
Made available via Smartphone’s
Common API
Controlling a MirrorLink® Session
Application have Control over MirrorLink Session
•
Trigger Head-Unit’s Virtual Keyboard
•
Send Notifications to Head-Unit
•
Switch Framebuffer Orientation
•
Subscribe to Data Services
Application respond to MirrorLink Session Events
•
Switch between Drive & Park Mode
•
Switch Framebuffer Orientation
Voice Commands
Conclusion – App View on MirrorLink
1.
2.
3.
4.
Deployment
– Established Channels
Advertisement
– Handled by Smartphone
Meta Information
– Contained within X.509 Certificates
Adaptation & Control
– Accessible via Common API
MirrorLink, Automotive App Development made Easy
THANK YOU

similar documents