AUTOSAR – Automotive Open System Architecture

1 111 dicembre 2008 Alessandra Mitidieri Automotive open System Architecture Cooperate on standards, compete on implementation. 4W Automotive SPIN Italia211 dicembre 2008 AgendaAUTOSAR HistoryPartnership Structure and MembersAUTOSAR Main Topics and BenefitsAUTOSAR ArchitecturePresent statusFuture plans and developmentsAUTOSAR in FGA24W Automotive SPIN Italia311 dicembre 2008 About AUTOSARAUTOSAR(AUTomotiveOpen System Architecture ) is an open and standardized Automotive software Architecture , jointly developed by automobile manufacturers, suppliers and tool developers. 4W Automotive SPIN Italia411 dicembre 2008 Exchangeability and Reuse of Software Components34W Automotive SPIN Italia511 dicembre 2008 AUTOSAR HistoryJuly, 2003-After an initial discussion on the common challenge and objectives (Aug. 2002) the partnership between the Core Partners was formally signed off.

2 The Core partners were initially BMW, Bosch, Continental, DaimlerChrysler, Volkswagen and Siemens VDO than joined by Ford Motor Company (Nov. 2003), and Toyota (Dec. 2003) and General Motors (Nov. 2004).December, 2004 FGA became AUTOSAR Premium Member4W Automotive SPIN Italia611 dicembre 2008 AUTOSAR website44W Automotive SPIN Italia711 dicembre 2008 Partnership Structure4W Automotive SPIN Italia811 dicembre 2008 Core Partners and Members54W Automotive SPIN Italia911 dicembre 2008 AUTOSAR BenefitsOEMS upplierToolProviderOEM overlapping reuse of software modulesMaintaining ability to compete on innovative functionsSimplification of the integration taskReduction of total SW development costsReduction of version proliferationDevelopment partitioning among suppliersIncrease of efficiency in functional developmentNew business models possibleCommon interfaces with development processesSeamless, manageable, task optimized (time dependent)

3 Tool landscape4W Automotive SPIN Italia1011 dicembre 2008 Basic AUTOSAR Approach Functional software is described formally in terms of Software Components (SW-Cs).Using Software Component Descriptions as input, the Virtual Functional Bus validates the interaction of all components and interfaces before software of Software Components to AUTOSAR Methodology supportsthe generation of an E/E the AUTOSAR Methodology, the E/E Architecture is derived from theformal description of software and hardware Automotive SPIN Italia1111 dicembre 2008 Intra- and Inter-ECU Communication4W Automotive SPIN Italia1211 dicembre 2008 AUTOSAR ArchitectureMicrocontrollerBasic Software LayerApplication LayerAUTOSARR untime Environment (RTE)74W Automotive SPIN Italia1311 dicembre 2008 AUTOSAR ArchitectureComplexDriversMicrocontrolle rMicrocontroller Abstraction LayerServices LayerApplication LayerAUTOSAR Runtime Environment (RTE)

4 ECU Abstraction Layer4W Automotive SPIN Italia1411 dicembre 2008 AUTOSAR Architecture84W Automotive SPIN Italia1511 dicembre 2008 Microcontroller Abstraction LayerComplexDriversMicrocontrollerMicroc ontroller Abstraction LayerApplication LayerRTEECU Abstraction LayerThe Microcontroller Abstraction Layer is the lowest software layer of the Basic contains internal drivers, which are software modules with direct access to the C internal peripherals and memory mapped C external :Make higher software layers independent of CProperties:Implementation: C dependentUpper Interface: standardizable and C independent4W Automotive SPIN Italia1611 dicembre 2008 ECU Abstraction LayerThe ECU Abstraction Layer interfaces the drivers of the Microcontroller Abstraction Layer. It also contains drivers for external offers an API for access to peripherals and devices regardless of their location ( C internal/external) and their connection to the C (port pins, type of interface)Task: Make higher software layers independent of ECU hardware layoutProperties:Implementation: C independent, ECU hardware dependentUpper Interface: C and ECU hardware independent, dependent on signal typeComplexDriversMicrocontrollerMicroco ntroller Abstraction LayerApplication LayerRTEECU Abstraction LayerECU Abstraction Layer94W Automotive SPIN Italia1711 dicembre 2008 Services LayerThe Services Layer is the highest layer of the Basic Software which also applies for its relevance for the application software.

5 While access to I/O signals is covered by the ECU Abstraction Layer, the Services Layer offersOperating System functionalityVehicle network communication and management servicesMemory services (NVRAM management)Diagnostic Services (including UDS communication, error memory and fault treatment)ECU state managementTask:Provide basic services for application and basic software :Implementation: partly C, ECU hardware and application specificUpper Interface: C and ECU hardware independentComplexDriversMicrocontroller Microcontroller Abstraction LayerApplication LayerRTEECU Abstraction LayerServices LayerECU Abstraction Layer4W Automotive SPIN Italia1811 dicembre 2008 RTEThe RTE is a layer providing communication services to the application software ( AUTOSAR Software Components and/or AUTOSAR Sensor/Actuator components).The RTE is the implementation of the Virtual Functional Bus (VFB) concepts.

6 It realizes the communication betweensoftware-components (SWCs) and between SWC and basic software (BSW) the RTE the software Architecture style changes from layered to component style . The AUTOSAR Software Components communicate with other components (inter and/or intra ECU) and/or services via the :Make AUTOSAR Software Components independent from the mapping to a specific ECUP roperties:Implementation: ECU and application specific (generated individually for each ECU)Upper Interface: completely ECU independentComplexDriversMicrocontroller Microcontroller Abstraction LayerApplication LayerAUTOSAR Runtime Environment (RTE)ECU Abstraction LayerServices LayerECU Abstraction Layer104W Automotive SPIN Italia1911 dicembre 2008 AUTOSAR Architecture : Standard InterfacesECU-HardwareAUTOSAR Runtime Environment (RTE) SoftwareStandardizedInterfaceAUTOSARI nterfaceAUTOSARI nterfaceAUTOSARI nterfaceMicrocontrollerAbstractionAUTOSA RS oftwareComponentECUF irmwareStandardSoftwareStandardizedAUTOS ARI nterfaceServicesStandardizedInterfaceECU A bstractionAUTOSARI nterfaceStandardizedInterfaceComplexDevi ceDriversAUTOSARI nterfaceAPI 2 VFB & RTErelevantStandardizedInterfaceCommunic ationStandardizedInterfaceStandardizedIn terfaceOperatingSystemAPI 1 RTErelevantAPI 0 StandardizedIntefaceAPI 3 PrivateInterfaces inside Basic SoftwarepossibleInterface4W Automotive SPIN Italia2011 dicembre 2008 AUTOSAR ValidationRelease and been validated developing two validators, mainly focused on approch for BSW validation was focusing on.

7 Exchangeability of implementations from differentimplementersCheck of interoperability of the modules in the stack (does the APIs fit together?)Check whether the specifications are unambiguousReleases , and been validated by each : the results of the validation are expected to be incorporated into the Release Automotive SPIN Italia2111 dicembre 2008 AUTOSAR Validation ResultsAUTOSAR harmonizesalready existing basic software solutions and closes gapsfor a seamless basic software aims at finding the best solution for each requirementand not finding the highest common decompositionof the AUTOSAR layered Architecture into some 50 modules has proven to be functionaland AUTOSAR specificationsfor the modules of the layered Architecture have been successfully implemented and Automotive SPIN Italia2211 dicembre 2008 Next Steps: AUTOSAR release (Nov.)

8 2009)ArchitectureArchitectural improvement in terms of error handling and multicoresupportCommunication stack evolution related to FlexRay and diagnostic over for functional enhancement of BSW mode improvement developing conformance tests specifications and level: Continuous development in the 5 different domainsBody and comfortPowertrainChassis controlOccupants and pedestrian safetyMM / T / HMIM ethodology and templates enhancementTiming specificationVariant handling124W Automotive SPIN Italia2311 dicembre 2008 Next Steps: Time plan of AUTOSAR phase III4W Automotive SPIN Italia2411 dicembre 2008 FGA in AUTOSAR ConsortiumWork PackagesFunctional and and Pedest. and Test Architecture Architecture and andApplication Mode Software / T / ArchitectureII-2SW and Test SpecificationII-3 ValidationII-5 Maintenance of ReleasesCommunication and ExploitationCoordination of Appl.

9 And Release of and starts working in AUTOSAR consortium as Premium Member at the end of 2004 with 10 active and passive members in some Work MembersPassive Members134W Automotive SPIN Italia2511 dicembre 2008 FGA AUTOSAR Strategy+30%70%SWC s in-house development in Body Electronics, Infotainment, Climate Control and Chassy s reuse and standardization in manycar projectsManagement of some BSW stacks:CommunicationDiagnosisCentralized development of cited SWC s stacksCentralized distribution of cited SWC s stacksOptimization of validation phases100% AUTOSAR compatibility for some ECU SuppliersApplication SoftwareBasic Software4W Automotive SPIN Italia2611 dicembre 2008 AUTOSAR : Application SW developmentBody Computer - FGA Software Modules0246810122007200820092010 SOPN ModulesSmallCompac tFlorence AUTOSAR Body Computer Project 6 SW modules nowadays in production, including Alfa e Stop&Start 11 SW modules in production fullyoperational (2010) 14 SW modules involved on 3 architectures 81% of application software developed byFGA fully operational 100% reuse of software deliberato 80% minimum reuse in different carsFuture developments on different systems/environments 3 modules in Chassis Control Systems environment Instrument Panel Cluster: an enquiry is going on with Suppliers Climate Control System : possible synergy with already developed SW modules by Interiors144W Automotive SPIN Italia2711 dicembre 2008 Thank you!

10 Alessandra Mitidieri 011 0035423