DOCSLIB.ORG

Lifecycle Subsystem Readout GENIVI EG-SI Architect – Mentor 2015-10-22 09:00 | Open Projects Track (Slides by David Yates – Continental)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Lifecycle Subsystem Readout GENIVI EG-SI Architect – Mentor 2015-10-22 09:00 | Open Projects Track (Slides by David Yates – Continental) Gianpaolo Macario Lifecycle Subsystem Readout GENIVI EG-SI Architect – Mentor 2015-10-22 09:00 | Open Projects Track (slides by David Yates – Continental) GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 1 5-Oct-15 This work is licensed under a Creative Commons Attribution-Share Alike 4.0 (CC BY-SA 4.0) Agenda • Introduction, goals of session • Lifecycle Manifest • Startup/Shutdown • Health Management • Lifecycle Use cases • Open Source Status & Roadmap • Links • Wrap Up & Questions GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 2 5-Oct-15 This work is licensed under a Creative Commons Attribution-Share Alike 4.0 (CC BY-SA 4.0) Lifecycle Overview 1*: Get internal states •Events: State chart State change notification • Phone session • Diag,SWL,Coding Plug in for: State chart session ADC, Supply Plug in for power • State change protocol handling PMIC Management HMI, Phone,… • (register for shutdown, get SWL/Update Node State states,handshake for Management Diagnostics state changes) Reaction on conditions Events: Turn off display, drives, mute audio,… • Good • Ctrls • Poor 1* Plug in for: State chart • Bad Sensors, Events: Node observing for CPU load, Devices Thermal • Full operational memory, appl. crash Management • Error startup Get states Node Resource Reaction on conditions PF-Events: Set LUC config Turn on fan, reduce audio volume,… • Last User Last-User-Context • Clamp Sts Boot config Resource Plug in for: • User ID Management Wakeup reason, Product-Event Power • Button WU Boot Limitation node / vehicle • Bus WU Management Ctrl network Management Raw-Events • Vehicle Network GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 3 5-Oct-15 This work is licensed under a Creative Commons Attribution-Share Alike 4.0 (CC BY-SA 4.0) Lifecycle Manifest Package Product Component Platform Component Node State Node State Node Startup Machine Manager Controller Supply Manager systemd Supply Node State Boot Management Management Management Thermal Power Resource cgroup service Management Management Management Thermal Manager Node Health Power Event Node Resource Monitor Collector Mgr GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 4 5-Oct-15 This work is licensed under a Creative Commons Attribution-Share Alike 4.0 (CC BY-SA 4.0) Status and Roadmap Kronos Leviathan Miranda N? Cgroup Adopted component, systemd specific specific specific specific (Kernel) provided by the OSS community Node Startup GENIVI funded OSS component specific specific specific specific (implemented by Codethink) Controller Node OSS Component specific specific specific specific State Manager (implemented and maintained by Continental) Node Product specific library n/a n/a n/a n/a State Machine Node Implemented by Continental placeholder abstract abstract specific Resource Mgr (OSS release upcoming) Node OSS Component specific specific specific specific Health Monitor (implemented and maintained by Continental) GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 27-Oct-15 Copyright © GENIVI Alliance 2014 5 Startup/Shutdown Management takes care about Boot Management Startup Management takes care about Node State Management Shutdown Management Why do we have this split? systemd stops and unloads all components during its shutdown concept. This requires a lot of time to make them functional again in the event of a cancel shutdown. An IVI system must be able to resume operation without losing any context and without the need for a reboot. Therefore Node State Management will only call registered consumers in the shutdown phase. This event notification will drive the components into a stable state and ensure that everything has been stored which will be needed for the next startup. With this approach components would not be shutdown which is required for certain exceptions like the flash file system. Therefore additionally the shutdown management concept will include/use the systemd shutdown concept , where appropriate for legacy/critical components. GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 6 5-Oct-15 This work is licensed under a Creative Commons Attribution-Share Alike 4.0 (CC BY-SA 4.0) Shutdown preparation in Startup Phase Before systemd kernel Runlevel replacement GENIVI extensions initrd Start NSM via systemd A Mandatory targets B (Base System & Early Features) C BASE_RUNNING (during NSC init) focussed.target (last user context) LUC_RUNNING unfocussed.target(s) Manager Node State FULLY_RUNNING J FULLY_ lazy.target OPERATIONAL GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 7 5-Oct-15 This work is licensed under a Creative Commons Attribution-Share Alike 4.0 (CC BY-SA 4.0) Shutdown Execution Consumer J Consumer I Writing LUC Node Startup Consumer H Controller systemd app1.service Consumer G Consumer F Node Startup Consumer E systemd Controller app2.service Consumer D Writing LUC Manager Consumer C Node Node State Consumer B Node Startup Consumer A systemd Shutdown.target Controller (flash file systems) Enables: 1. Shutdown activities are trigger able without unloading the components. 2. Legacy components can be shut down in their traditional way. 3. Full flexibility on where to integrate systemd based shutdown units. GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 8 5-Oct-15 This work is licensed under a Creative Commons Attribution-Share Alike 4.0 (CC BY-SA 4.0) Unit Files Unit] Description=Application launcher daemon After=mnt-appdata.mount What can be seen in this example is that the executable al-daemon will be run with the command options “–start –v”. It will notify systemd when it has [Service] completed its initialization. Type=notify ExecStart=/usr/bin/al-daemon --start -v With regards to dependencies, it can only be started after mnt- PIDFile=/tmp/al-daemon.pid appdata.mount is available and it is wanted by unfocussed.target. TimeoutStartSec=2 This means that whenever unfocussed.target is required this unit will be WatchdogSec=10 included. Restart=on-failure The application will complete initialization within 2 seconds and wants to StartLimitInterval=15 be monitored during runtime. The application will be deemed to have failed StartLimitBurst=5 if it has not sent a heartbeat (sd_notify) within 10 seconds. If it fails more StartLimitAction= reboot than 5 times within a period of 15 seconds then systemd will assume a critical failure and initiate a system restart [Install] WantedBy=unfocussed.target GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 9 5-Oct-15 This work is licensed under a Creative Commons Attribution-Share Alike 4.0 (CC BY-SA 4.0) Interfaces The Node State Manager (NSM) will provides 2 D-Bus interfaces – org.genivi. NodeStateManager.Consumer – org.genivi. NodeStateManager.LifecycleControl The “Consumer” interface is publicly available in the system and should be used by any applications that are interested in the information that the NSM maintains. The “LifecycleControl” interface will contain functions that are secured via DBUS policies to restrict their usage. There should be a minimal subset of applications with access. These interfaces are documented in the GENIVI UML Model (Enterprise Architect trunk) under GENIVI Model -> Logical View -> SW Platform Components -> Node State Manager -> Interfaces and the use cases shown in parallel today from the model can be found under GENIVI Model -> Logical View -> Use Case Realizations -> Lifecycle For those without access to EA you can also find exported versions of the model that are regularly updated in the wiki GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 10 5-Oct-15 This work is licensed under a Creative Commons Attribution-Share Alike 4.0 (CC BY-SA 4.0) System Startup The Node Application Mode (NAM) is a Node specific data item that is used to define the functionality level (systemd runlevel) that should be achieved in the current Lifecycle. Only one of the following example modes can be active at any one time : – Parking – Factory – Transport – SWL The data item will be updated in the Persistence via the Node State Manager when requested through the secured method SetApplicationMode available under org.genivi.NodeStateManager.LifecycleControl The data item will be read early in the startup sequence by a Lifecycle Support Library that will then define the target file to be started by systemd To see how the update method should be used please see use case (“WB – NSM – Updating the Node Application Mode”) GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 11 5-Oct-15 This work is licensed under a Creative Commons Attribution-Share Alike 4.0 (CC BY-SA 4.0) System Shutdown • The ShutdownReason is a node-specific D-Bus property available under the org.genivi.NodeStateManager.Consumer interface • Updated via the NSM when an event in the system triggers the shutting down of the system (i.e Thermal Management reports a dangerously high temperature) • Consumers that want to be notified when the node will be shutdown must use the interface Consumers.RegisterShutdownClient and must provide their own method called LifecycleRequest that will be called by the NSM in the event of a shutdown (or cancel shutdown) • Additionally they must specify the type of shutdown they are registering
Load more

Recommended publications
  • Linux Automotive Security “Safer and More Secure”
    Linux Automotive Security “Safer and more secure” Authors Fulup Ar Foll [email protected] José Bollo [email protected] Abstract Cars are expensive pieces of equipment, yet they represent a huge mass market. Adding Internet connectivity to previous elements generates perfect conditions for the growth of a viable business model on attacking “Connected Cars”. It is already well understood that cars will be connected and connected cars will be attacked. While it's still too early to predict with certainty how “Connected Cars” will be impacted by security flaws, making the assumption that a car should be at least as secure as a TV, a set-top-box or a smart phone should make sense to everyone. This white paper focuses on how Linux best practices security mechanisms that could be used today and within the next couple of years to make connected cars safer and more secure. Version 1.0 January 2016 Linux Automotive Security Table of contents 1.Introduction...................................................................................................3 2.Make Sure You Run the Right Code...................................................................4 2.1.Before Booting............................................................................................4 2.2.When Booting.............................................................................................5 2.3.After Booting...............................................................................................5 3.Keeping Secrets Secret...................................................................................6
    [Show full text]
  • <Document Title>
    DATE OSS Disclosure Document th CM_CI1 11 feb 2021 OSS Licenses used in RN_AIVI Project This document is provided as part of the fulfillment of OSS license conditions and does not require users to take any action before or while using the product. Page 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS PRIVATE LIMITED. Without their consent, it may not be reproduced or given to third parties DATE OSS Disclosure Document th CM_CI1 11 feb 2021 Table of Contents Contents 1 List of used Open Source Components. ............................................................................................... 6 2 Appendix - License Text ................................................................................................................. 56 2.1 BSD-4-Clause (University of California-Specific) ............................................................. 56 2.2 Academic Free Licensev. 2.1 ............................................................................................. 57 2.3 Academic Free License v1.1 .............................................................................................. 59 2.4 Apache License 1.1 ........................................................................................................... 60 2.5 Apache License 2.0 ........................................................................................................... 62 2.6 Apple Public Source License 1.1 ....................................................................................... 65 2.7
    [Show full text]
  • Strong Momentum Continues by Egil Juliussen The
    GENIVI: Strong Momentum Continues By Egil Juliussen The GENIVI Alliance had its membership meeting in Shanghai in mid-October. IHS Automotive was invited as part of their analyst track and was asked to give perspectives on HMI and apps for auto infotainment. This is the fourth time we have attended and given a presentation at the GENIVI Alliance meeting. We have previously been asked to do presentations on Software Security and HTML5 Infotainment Impact. Does this mean that GENIVI is now focusing on HMI technologies and/or a HMI framework? This impression will update a previous version that was done in November 2011 and will focus on the following topics: • What is new with GENIVI? • How does GENIVI compete with other OS platforms? • What is the outlook for GENIVI success? What is new with GENIVI? The GENIVI Alliance is a non-profit organization that is developing a software platform for in-vehicle infotainment (IVI) systems that uses Open Source Software (OSS) business model. The software platform is based on the Linux operating system (Version 2.6 Kernel) and additional middleware that are needed for running automotive infotainment applications in head-units, telematics and navigation systems. The GENIVI platform can be based on any Linux distribution, but a major goal of GENIVI is to avoid fragmentation of Linux in automotive systems—hence the compliance program. To assure a high level of compatibility between Linux versions, GENIVI released its first edition of the compliance testing program in August 2011 after 14-months of development. The second version of the compliance testing program was announced this spring and the third compliance version was announced in Shanghai this October.
    [Show full text]
  • Pressemitteilung
    Pressemitteilung Zur sofortigen Veröffentlichung GENIVI Alliance stellt Konformitätsprogramm für Mitglieder vor Erste fünf GENIVI-konforme Lösungen anerkannt SAN RAMON, Kalifornien, USA - 2. August 2011 - The GENIVI Alliance, ein Branchenverband der Automobil- und Unterhaltungselektronikindustrie, der sich für die Entwicklung und Einführung einer offenen Referenzplattform für Infotainment in Fahrzeugen (IVI – In-Vehicle Infotainment) einsetzt, stellte heute sein neu entwickeltes Konformitätsprogramm für seine Mitgliedsunternehmen vor. Dieses Programm ist das Ergebnis 14-monatiger akribischer Forschungs- und Untersuchungsbemühungen von GENIVI-„Expertengruppen“ – mit umfassender Beteiligung aller Mitglieder – zur Aufstellung einer Bandbreite detaillierter technischer Anforderungen. Die GENIVI-Miglieder Canonical, Mentor Graphics, MontaVista und Wind River sowie die Linux Foundation sind die ersten mit „GENIVI-konform“ anerkannten Angeboten, was sie für OEM- Ausschreibungen mit GENIVI-konformen Produkten qualifiziert. „Dieses Programm verkörpert den natürlichen Ablauf innerhalb der GENIVI Alliance von zielgerichteten Anforderungen über identifizierte Komponenten, die diesen Anforderungen gerecht werden, bis hin zu einer kompakten wiederverwendbaren Plattform“, sagte Steve Crumb, Executive Director der GENIVI Alliance. „Das Programm klärt, was von Mitgliedern erwartet wird, die konforme Softwarelösungen anbieten wollen.“ „Jaguar Land Rover und andere Automobil-OEMs und GENIVI-Mitglieder geben jetzt die GENIVI-Konformität in ihren Ausschreibungen
    [Show full text]
  • Hypervisors in the Vehicle: a Standards-Based Approach to Virtualization
    Hypervisors in the vehicle: A standards-based approach to virtualization A report based on the webinar by Automotive World and GENIVI Alliance. The webinar which was broadcast in February of ! ! is still available for download " see #$%. It however had some poor audio &uality in some parts. A better recordin' is now available at #$% but some may still prefer to 'et this information in written form. The document is not an e(act transcript of the webinar) but it is close. The content and messa'e is the same, and the information is presented here to'ether with the correspondin' presentation slides from the webinar) with the followin' adjustments: , -ommon spo.en e(pressions have been e(chan'ed for more typical written lan'ua'e to reach more typical written &uality. , /inor clarifications and some lost details have been added. , A few chapters are e(tended and elaborate on details that did not 0t within the time of the webinar , For the 1&A session, more thou'htful and complete answers to 'iven &uestions can be 'iven, now that there is time to formulate the answers. Also) the section presented by Tero 3alminen from 4pen3yner'y has a 'ood &uality audio in the recordin') and is not included in te(t form in this document. The 0rst part of the presentation was done by Gunnar Andersson 5GENIVI Technical 6ead7) who is also the author of this text. We promised to address a &uestion in this webinar : 8Is there a need for a more standards-based approach for deployin' hypervisors in the vehicle?: , to ensure that automotive requirements are met, , to reduce risk and concerns amon' adopters of virtualization) , to promote portability, , and to minimize system integration effort.
    [Show full text]
  • Trademarks and Licenses Trademarks and Licenses
    Trademarks and Licenses Trademarks and Licenses Bluetooth® Wireless Technology The Bluetooth Wireless Technology word mark and logos are registered trademarks owned by Bluetooth Wireless Technology SIG, Inc. HD Radio™ Technology Program Info Program Info provides song name, artist, station ID, and other relevant data to the receiver. Digital Sound HD Radio broadcasts deliver crystal clear digital audio quality to consumers. HD2/HD3 Adjacent to traditional main stations are HD2/HD3 Channels, providing new original formats on the FM dial. Artist Experience: Visual images, such as album art and station logos, of over-the-air broadcasts from HD Radio stations. 171 Specification Specification AV product specification Operating Temper -20 ℃ ~ +65 ℃ Common Storage Temperature -30 ℃ ~ +75 ℃ Supported Profile HFP 1.6, A2DP 1.2, AVRCP 1.5, PBAP 1.1 Supported Bluetooth 3.0 Specification Bluetooth Frequency Range 2402 MHz ~ 2480 MHz Number of Channels 79 AM ME : 522 kHz~1620 kHz SA : 522 kHz~1620 kHz Tuning Range ESA : 531 kHz~1602 kHz MX : 530 kHz~1710 kHz Sensitivity 35 dBuV Signal-to-noise ratio Minimum 45 dB Radio FM ME : 87.5 MHz~108.0 MHz SA : 87.5 MHz~108.0 MHz Tuning Range ESA : 87.5 MHz~108.0 MHz MX : 87.5 MHz~107.9 MHz Sensitivity 12 dBuV Frequency response 30 Hz ~ 10000 Hz Signal-to-noise ratio Minimum 45 dB ↟ Designs and specifications are subject to change without prior notice. WiFi Frequency Range(FCC) : 2412-2462MHz 5180-5240MHz 5745-5825MHz Frequency Range( CE ) : 2412-2472MHz 5180-5240MHz 5745-5825MHz Specification : IEEE802.11 a/b/g/n/ac Supported Bandwidth : 20MHz, 40MHz, 80MHz 172 Open Source Software Notice Open Source Software Notice This product contains the open source software detailed below.
    [Show full text]
  • Communiqué De Presse
    Communiqué de presse Pour publication immédiate GENIVI Alliance dévoile son programme de conformité des membres Les cinq premières solutions de conformité présentées par GENIVI sont approuvées SAN RAMON (Calif.) – Le 2 août 2011 – GENIVI Alliance, une association de l'industrie automobile et des produits électroniques grand public, leader dans le développement et l'adoption d'une plate-forme référentielle d'infodivertissement embarqué source ouverte (répondant à l'acronyme américain IVI, "In-Vehicle Infotainment"), a annoncé aujourd’hui la disponibilité de son Programme de Conformité nouvellement créé au service de ses sociétés membres. Ce programme jalon est le résultat de 14 mois de recherches et d’investigations laborieuses de la part des « groupes d’experts » de GENIVI – composés d’une large représentation des divers membres – qui ont défini un ensemble détaillé d’exigences techniques. Les membres de GENIVI : Canonical, Mentor Graphics, MontaVista et Wind River, ainsi que la Fondation Linux, sont les premiers à recevoir l’approbation de conformité GENIVI pour leurs offres, ce qui les qualifie maintenant à recevoir des appels d’offres de la part des équipementiers exigeant des produits conformes aux normes GENIVI. « Ce programme incarne le flux naturel au sein de GENIVI, allant des exigences alignées, aux éléments identifiés répondant à ces exigences, à une plateforme complète et réutilisable » a dit Steve Crumb, Directeur général de GENIVI Alliance. « Le programme établit clairement ce qui est attendu de la part des membres désireux de fournir des solutions logicielles conformes. » « Jaguar Land Rover et d’autres équipementiers automobiles membres de GENIVI mentionnent à présent la conformité GENIVI dans leurs appels d’offres (RFP – Request for Proposal) relatifs aux futurs systèmes IVI », a déclaré Matt Jones, Chef de l’Infodivertissement chez Jaguar Land Rover et Vice-président de GENIVI.
    [Show full text]
  • Car Multimedia Scope: EU 18.2.3 Document Type
    Baseline Car Multimedia Privileged & Confidential Scope: EU_18.2.3 Document Type: Disclosure Document Revision: 1.1 Date: 19/07/2018 Author: Chetan Jayatheertha Baseline Car Multimedia Privileged & Confidential History: Rev. Part Description Date Name 1.0 Complete Initial Version 23/04/2018 Chetan Jayatheertha 1.1 Complete Final Version 19/07/2018 Chetan Jayatheertha Baseline Car Multimedia Privileged & Confidential Table of Contents 1 Overview ................................................................................................................................................................................................................. 9 2 OSS Licenses used in the project ................................................................................................................................................................... 9 3 Package details for OSS Licenses usage .................................................................................................................................................... 12 3.1 ACL .................................................................................................................................................................................................................. 12 3.2 Alsa Libraries .............................................................................................................................................................................................. 12 3.3 Alsa Plugins ................................................................................................................................................................................................
    [Show full text]
  • LXCBENCH Understanding the Capabilities of Linux Containers in IVI Applications Through Benchmarking
    LXCBENCH Understanding the capabilities of Linux Containers in IVI applications through benchmarking Gianpaolo Macario Mentor Embedded – Linux Services GENIVI – EG-SI Architect Automotive Linux Summit Fall Edinburgh, UK – October 2013 mentor.com/embedded Android is a trademark of Google Inc. Use of this trademark is subject to Google Permissions. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Agenda The problem statement LXC: The technology How LXC may address some IVI use cases The GENIVI LXCBENCH Incubation Project Summary Who am I? Gianpaolo Macario Architect, Mentor Graphics – ESD – Linux Services System Architect, GENIVI Alliance Past System Architect, Magneti Marelli – Infotainment & Telematics Experiences: IT Manager, COMAU – Robotics Business Unit Software Consultant, GlobalValue (a Fiat/IBM Italy JV) … Linux and Open Source user and developer since 1993 (linux-0.99pl13) Very proud of my first contribution to Linux Kernel early in 1995 (linux-1.3.13) My social life: http://it.linkedin.com/in/gmacario/ https://twitter.com/gpmacario Embedded Industry Trends Hardware Consolidation – SoC – Subsystems – Systems Benefits – Reducing BOM and power consumption – Increasing performance and capacity of the system Concerns – Complexity of the system design, development, debugging Example 1: Consolidation GENIVI/AUTOSAR Most IVI systems have traditionally split the system architecture on separate CPUs/MCUs: Infotainment domain: GENIVI Linux software stack, graphical resources, etc Automotive domain:
    [Show full text]
  • COLLABORA JOINS GENIVI ALLIANCE UK Open Source
    COLLABORA JOINS GENIVI ALLIANCE UK open source software consultancy adds weight to industry group that enables quicker route to market for in-vehicle entertainment Cambridge, United Kingdom, October 12, 2011 -- UK-based multimedia and open source turnkey solutions company Collabora has today announced it has become an Associate Member of the GENIVI Alliance. The GENIVI Alliance gathers companies from the entire In-Vehicle Infotainment (IVI) industry, including: software, consumer electronics and communication, and major vehicle manufacturers including BMW, Hyundai Motor Group, PSA Peugeot-Citroen, Jaguar Land Rover, General Motors and Renault. Collabora will contribute to make GENIVI an open source platform with best of breed multimedia support and ease of deployment. "GENIVI is a critical organisation in enabling a quick route to market for new and innovative in-vehicle entertainment solutions," said Rob McQueen, Collabora co- founder and CTO. "We are regarded as one of the foremost open source consultancies and as the company behind leading multimedia technologies like the GStreamer multimedia framework, the Telepathy and Farstream real-time communications stack and with the Rygel DLNA implementation, we are convinced we can help propel GENIVI forward as a cutting edge platform." The GENIVI platform is built on top of the Linux kernel, GStreamer, D-bus, Webkit and other open source technologies in which Collabora is a major contributor. Collabora engineers have been contributing to the Linux community for more than six years, becoming one of the most widely-respected and effective open source consulting companies. The company is seen as a pioneer for its work in system infrastructure on open source platforms in fields such as multimedia, web technologies and Inter process communications (IPC).
    [Show full text]
  • GENIVI Alliance Past and Present
    CHANGING THE IN-VEHICLE INFOTAINMENT LANDSCAPE Graham Smethurst – GENIVI Alliance President, BMW General Manager Copyright © 2010 GENIVI Alliance, All Rights Reserved. GENIVI and the GENIVI logo are trademarks of the GENIVI Alliance. THE MOTIVATION BEHIND GENIVI - THE NEED FOR CHANGE. The investigation phase started in mid-2006, following the realisation that the delivery of increased functionality in automotive infotainment solutions, particularly in the area of device and services connectivity, was becoming unsustainable. The development and validation costs were spiralling upward as the amount of software required rocketed. At the same time, infotainment in the car had become important and a differentiator in the car-buying decisions. The successes of companies like Apple with its powerful developer kit and app-store model, Google with its connected services, and Personal Navigation Device leaders like TomTom created a situation where car drivers and passengers wanted to access the same functionality in their car. OEM Automotive infotainment had become a difficult equation to resolve, faced with the challenges of complexity and cost, aggressive competition from the consumer sector, and an apparently insatiable customer appetite for functionality in the car strongly influenced by the ―high street‖. At the heart of any automotive solution is the ―headunit‖. This device is the most complex component in a modern automobile by software volume. In a high-end device, approximately 70% of the total code in a car will be in that single device. The headunit is no longer just a radio; it provides the logical interface between the car and consumer space. Increasingly, the functionality it delivers defines the user experience in the car.
    [Show full text]
  • Security Architecture Overview 19 October, 2016 | Access Control, DAC, MAC, LSM and More
    Security Architecture Overview 19 October, 2016 | Access Control, DAC, MAC, LSM and more... Gunnar Andersson Lead Architect, GENIVI Alliance This work is licensed under a Creative Commons Attribution-Share Alike 4.0 (CC BY-SA 4.0) GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries. Copyright © GENIVI Alliance 2016. Abstract and introduction Abstract Main topic: A secure system is more than access control , but this is where we build our foundation (after a trusted boot process). It has been the primary topic of interest in the open-source systems we have compared in the past (Tizen IVI, AGL, Apertis, Android...) which makes it relevant to discuss from a GENIVI standards point of view. Copyright © GENIVI Alliance 2016 CC BY-SA 4.0 | AMM Fall 2016 3 Purpose •Set the stage for the following case-studies in this presentation track, and make a few concrete proposals • Warning: Some very basic principles will be covered. For the security experts in the room, realize that the purpose is not always to teach something new to you • For efficient collaboration, getting everyone “on the same page” is worth covering some basics. This should facilitate further collaboration. Copyright © GENIVI Alliance 2016 CC BY-SA 4.0 | AMM Fall 2016 4 Questions (as promised in Abstract) • What does the GENIVI architecture say so far about different patterns and options for controlling access to data and resources? Copyright © GENIVI Alliance 2016 CC BY-SA 4.0 | AMM Fall 2016 5 Questions • What are the basic expectations of system
    [Show full text]