DOCSLIB.ORG

GENIVI Document TR00029 GENIVI Lifecycle Domain Overview Technical Report Version

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
GENIVI Document TR00029 GENIVI Lifecycle Domain Overview Technical Report Version 1 2 GENIVI Alliance 3 GENIVI Document TR00029 4 GENIVI Lifecycle Domain Overview 5 Technical Report 6 Version 1.0 7 2014-08-14 8 Sponsored by: 9 GENIVI Alliance 10 Abstract: 11 This document is an export of the GENIVI Wiki Lifecycle Domain. It provides an overview of the 12 architecture and requirements for the complete Lifecycle Domain 13 Keywords: 14 GENIVI, Lifecycle 15 License: 16 This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. 17 18 19 20 GENIVI Alliance. 2400 Camino Ramon, Suite 375, San Ramon, CA 94583, USA http://www.genivi.org 1 Copyright © 2014, Company ABC, Company XYZ. 2 All rights reserved. 3 The information within this document is the property of the copyright holders and its use and disclosure are 4 restricted. Elements of GENIVI Alliance specifications may be subject to third party intellectual property 5 rights, including without limitation, patent, copyright or trademark rights (and such third parties may or may not 6 be members of GENIVI Alliance). GENIVI Alliance and the copyright holders are not responsible and shall not 7 be held responsible in any manner for identifying, failing to identify, or for securing proper access to or use of, 8 any or all such third party intellectual property rights. 9 GENIVI and the GENIVI Logo are trademarks of GENIVI Alliance in the U.S. and/or other countries. Other 10 company, brand and product names referred to in this document may be trademarks that are claimed as the 11 property of their respective owners. 12 This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. 13 The full license text is available at http://creativecommons.org/licenses/by-sa/4.0 14 The above notice and this paragraph must be included on all copies of this document that are made. 15 GENIVI Alliance 16 2400 Camino Ramon, Suite 375 17 San Ramon, CA 94583, USA GENIVI Alliance. 2400 Camino Ramon, Suite 375, San Ramon, CA 94583, USA http://www.genivi.org 1 Revision History 2 Document revision history Date Version Author Description 2014- 1.0 David Yates Initial revision exported from the GENIVI Wiki on the 08-14 14th Sept 2014 3 GENIVI Alliance. 2400 Camino Ramon, Suite 375, San Ramon, CA 94583, USA http://www.genivi.org 1. SysInfraEGLifecycleDef . 2 1.1 SysInfraEGLifecycleClosedItems . 8 1.2 SysInfraEGLifecycleExecPrjctBootManager . 11 1.2.1 Node Startup Controller Description . 12 1.2.2 SysInfraEGLifecycleExecPrjctBootManagerArchitectureOverview . 13 1.2.3 SysInfraEGLifecycleExecPrjctBootManagerDBusInterfaces . 15 1.2.3.1 ReviewBootManagerDBusInterfaces . 17 1.2.4 SysInfraEGLifecycleExecPrjctBootManagerDependencies . 19 1.2.5 SysInfraEGLifecycleExecPrjctBootManagerExcaliburSchedule . 19 1.2.6 SysInfraEGLifecycleExecPrjctBootManagerFunctionalScope . 21 1.2.7 SysInfraEGLifecycleExecPrjctBootManagerInternalArchitecture . 22 1.2.8 SysInfraEGLifecycleExecPrjctBootManagerMinutes20120611 . 23 1.2.9 SysInfraEGLifecycleExecPrjctBootManagerMinutes20120618 . 24 1.2.10 SysInfraEGLifecycleExecPrjctBootManagerMinutes20120625 . 25 1.2.11 SysInfraEGLifecycleExecPrjctBootManagerMinutes20120702 . 26 1.2.12 SysInfraEGLifecycleExecPrjctBootManagerMinutes20120709 . 26 1.2.13 SysInfraEGLifecycleExecPrjctBootManagerMinutes20120716 . 26 1.2.14 SysInfraEGLifecycleExecPrjctBootManagerMinutes20120813 . 27 1.2.15 SysInfraEGLifecycleExecPrjctBootManagerRequirements . 28 1.2.16 SysInfraEGLifecycleExecPrjctBootManagerTestScenarios . 32 1.2.17 SysInfraEGLifecycleExecPrjctBootManagerTrackingInJIRA . 33 1.2.18 SysInfraEGLifecycleExecProjectBootManagerLegacyApps . 33 1.2.19 SysInfraEGLifecycleExecProjectBootManagerSystemdInteraction . 34 1.2.20 SysInfraEGMinutes20120529 . 35 1.3 SysInfraEGLifecycleExecPrjctNodeResMgmt . 37 1.4 SysInfraEGLifecycleExecPrjctNSM . 38 1.4.1 Node State Manager Description . 40 1.5 SysInfraEGLifecycleSubsysDoc . 40 1.5.1 SysInfraEGLifecycleConcept . 43 1.5.1.1 SysInfraEGLifecycleBootMgmtSOW . 47 1.5.2 SysInfraEGLifecycleConceptBootmanagementSplit . 54 1.5.2.1 SysInfraEGLifecycleConceptBootmanagementShutdown . 55 1.5.2.2 SysInfraEGLifecycleConceptBootmanagementStartup . 57 1.5.3 SysInfraEGLifecycleConceptCgroupsInput . 62 1.5.4 SysInfraEGLifecycleConceptMultiNode . 63 1.5.5 SysInfraEGLifecycleConceptRefinement . 64 1.5.6 SysInfraEGLifecycleConceptSystemBorder . 65 1.5.7 SysInfraEGLifecycleDesignStructDef . 66 1.5.8 SysInfraEGLifecycleDesignWhiteBoxUcRealization . 68 1.5.9 SysInfraEGLifecycleFABlackBoxUcRealization . 71 1.5.10 SysInfraEGLifecycleNSMData . 71 1.5.11 SysInfraEGLifecycleRAUsecases . 77 1.5.12 SysInfraEGLifecycleRequirements . 79 1.5.13 SysInfraEGSystemd . 106 1.5.13.1 SysInfraEGSystemdPOC . 120 SysInfraEGLifecycleDef Subdomain Lifecycle Scope of work item Navigation within this subdomain Management of work item Execution Projects Risks, issues and open questions Subdomain documentation List of all persons contributed to EG SI Lifecycle Wiki Overview of Wiki pages Presentations for Lifecycle Dublin San Jose Paris Shanghai Barcelona San Diego Misc. Presentations Scope of work item The scope of this work package is a full development activity of Lifecycle. That means starting with studying the past / history of this package; specify the system- and software architecture; doing the design and implementation of the common parts including the integration and test. Finally the Lifecycle system architecture specification parts will be located in the GENIVI compliance architecture model. The software and the design specification you can find in the implementation model section of the GENIVI model. However, additionally the interfaces will be delivered as header file independent if there will be a common implementation or not. The functional scope of Lifecycle: The current activity will cover: Power-, Node state-, Boot- and Resource management specified in detail. Interfaces to/of Thermal- and Supply management. Thermal- and Supply management itself will be handled as a black box only. Additionally the architecture is taking in account different deployments (one- and multi-node architectures). Please find more details at the concept description and following pages. Navigation within this subdomain At the bottom of each page linked arrows are located which helps to navigate within this subdomain. It provides the red-line for reading the pages. Management of work item If you have some remarks or concerns, you see some problems or you have just a question please fill in your item in the first table. If you want to address some action, assigned or not, please use the second table. These tables reflect our main status / activities. Execution Projects Node Startup Controller WIKI page of the Node Startup Controller Project Project Node State Mangement WIKI page of the Node State Management Project Project Risks, issues and open questions The column options are: Category: Risk, Issue, Question ID Category Submitter Topic Answer Replied by (Name,Company) (Name,Company) 1 Question Torsten To release the Christian Muck, Hildebrand, compliant Alexander Wenzel (BMW) BMW Continental lifecycle Manfred Bathelt (BMW) requirements it Christian Muck (BMW) is necessary to Fabien Hernandez (PSA) know who are the mandatory reviewers. 2 Question David Yates, In the The term "middleware" can be replaced with "GENIVI". It is Holger Behrens, Continental requirements also assumed that middleware doesn't provide a GUI. Wind River the term "Middleware" is used - what does this refer to in the context of GENIVI? 3 Question David Yates, What is the Consumers Holger Behrens, Continental GENIVI - Interpretation depends on the HW partitioning in question. In Wind River definition of case there is an automotive/vehicle controller, or some parts of the terms the PSM are running on the vehicle controller (OSEK), while "Consumer" platform state handling is done on both CPUs (OSEK and and "Device" Linux) by a bunch of SW components - aka. consumed as used in the Device - here my interpretation is that for example the PSM Requirements? part running on the vehicle controller could potentially power-up/down the CPU running Linux (aka. system), or the CD/DVD drive (aka. device), based on platform state. 4 Information AMM, Paris During the Following the meeting we have looked into whether this would David Yates, presentation be possible and come to the conclusion that currently this is Continental on the Node not possible as we use the ordering of the registration during State Manager start-up to define the ordering for shutdown. (AMM, Paris) it was suggested Perhaps in the future something can be improved here.
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]