1 / 17

Technical Considerations of Application Certification

Technical Considerations of Application Certification. Dr. Jörg Brakensiek Principal Architect, Nokia Chair of the Technical Work Group, CCC. Overview. MirrorLink® Concept Deployment Advertisement Meta Information Adaptation & Control. MirrorLink ® Concept. Once connected,

joella
Download Presentation

Technical Considerations of Application Certification

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Technical Considerations of Application Certification Dr. Jörg Brakensiek Principal Architect, Nokia Chair of the Technical Work Group, CCC

  2. Overview • MirrorLink® Concept • Deployment • Advertisement • Meta Information • Adaptation & Control

  3. MirrorLink®Concept Once connected, no need to touch or look at your phone

  4. MirrorLink®Concept Common API Discovery & Events Display & Control Audio Security App Certs Data Access Connectivity

  5. 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

  6. Deployment of MirrorLink® Applications User App Developer App Guidelines Design App Store Upload Submit Test Lab Enjoy App Test Results App Install Certificate Database Smartphone Head-Unit Retrieve Certificate

  7. Deployment of MirrorLink® Applications Application Store Application Certificates • X.509 • Self-signed  CCC signed Certificate Retrieval • HTTP GET • Application Identifier Check Validity of Certificate • Protocol: OCSP • Update available • Revoked • OK (still valid) Uniquely identifies an application and its version Self App CCC CCC Certificate Database Smartphone App ID Validity Head-Unit

  8. Application Certificates – Deep Dive Subject (App Identifier) Certified App Information Signature Algorithm OCSP Info Signature • Signature Algorithm: sha512WithRSAEncryption • Issuer: O = Car Connectivity Consortium • CN = ACMS CA • Valid from: ‎‎May 16 ‎2013 3:26:44 AM • Valid to: ‎ July 23 2023 3:26:44 AM • Subject: CN = <App ID> • 1.3.6.1.4.1.41577.2.1: • <certificate> • ... • </certificate> • X509v3 Authority Information Access: • OCSP - URI:http://acms.carconnectivity.org/OCSP • Signature: [...] Certificate Issuer Validity Period

  9. Advertising MirrorLink® Applications • MirrorLink Specifics • User connects the Phone with the Head-Unit • Phone contains certified Applications • User uses Application’s User Interface

  10. Advertising MirrorLink®Applications Phone Call Are you alive Launch Nokia Music I am Alive Terminate Nokia Drive Who are you

  11. 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)

  12. 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

  13. Application’s Meta Information • Prevent Launch of not-allowed applications • Block prohibited content on the Head-Unit Screen

  14. Application’s UI Adaptation • Adaptation Needs for Apps • 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 CommonAPI

  15. 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

  16. Conclusion – App View on MirrorLink • Deployment • Established Channels • Advertisement • Handled by Smartphone • Meta Information • Contained within X.509 Certificates • Adaptation & Control • Accessible via Common API

  17. MirrorLink, Automotive App Development made Easy Thank You

More Related