AUTOSAR – An Open Standardized Software Architecture For .

AUTOSAR –An open standardized software architecturefor the automotive industrySimon Fürst, BMW1st AUTOSAR Open Conference &8th AUTOSAR Premium Member ConferenceOctober 23rd, 2008, Cobo Center, Detroit, MI, USA

Document Information and Change HistoryDocument OwnerHeiko DörrDocument ResponsibilitySCDocument Version1.5Document filenameAUTOSAR TutorialDocument Status Draft Ready for Approval Final Document Change History2DateVersionChanged byChange Description30.05.20070.1Heiko DörrInitial creation and proposal for content10.08.20070.2Heiko DörrReady for approval16.08.20070.3Heiko DörrComments by Mr. Bunzel entered17.08.20070.4Heiko DörrSection on Methodology updated after discussion with member of WPII1.2; Section on Exploitation removed; Ready for approval by SC23.08.071.0Heiko DörrTutorial approved by SC31.08.071.1Heiko DörrPM memberships updated according to slide provided by admin07.04.081.2Heiko DörrCP updated, readability improved07.05.081.3Heiko DörrBus state managers added to BSW modules slide03.07.20081.4Heiko DörrSelected slides from ATI added (Animated use case for distributedscenario, Validator 2), Schedule updated01.10.20081.5Heiko DörrSelection of slides for presentation at 8th PM conferenceOct. 23rd 2008AUTOSAR Tutorial

Document Information and Change HistoryDocument Change History3DateVersionChanged byChange Description22.10.20081.51Simon FürstReviewOct. 23rd 2008AUTOSAR Tutorial

Automotive Systems and SW Engineering4Oct. 23rd 2008AUTOSAR Tutorial

Automotive Open System ArchitectureCooperate on standards – compete on implementationNon functionallegal requirementsVehicle familymanagementResource efficiencyDriver assistanceDriving dynamicsSafety functions(active/passive)Comfort functions5Oct. 23rd 2008AUTOSAR Tutorial

AUTOSAR Managing Complexityby Exchangeability and Reuse of Software ComponentsOEM bExchangeabilitybetweensupplier‘ssolutionsOEM aPlatform b.1Platform b.2Platform b.nPlatform a.1Platform a.2Platform onsSupplier A¾ Chassis¾ Safety¾ Body/Comfort¾ MultimediaSupplier B¾ Chassis¾ Safety¾ Telematics¾ MultimediaSupplier C¾ Body/Comfort¾ Powertrain¾ Telematics¾ MultimediaOEM fOEM ePlatform f.1Platform f.2Platform f.nOct. 23rd 2008Platform c.1Platform c.2Platform c.nOEM dPlatform d.1Platform d.2Platform d.nExchangeabilityPlatform e.1Platform e.2Platform e.n6OEM cAUTOSAR Tutorialbetween vehicleplatforms

AUTOSARProject Objectives and Main Working Topics¾ Implementation andstandardization of basicsystem functions as an OEMwide “Standard Core“ solution¾ Scalability to different vehicleand platform variants¾ Transferability offunctions throughoutnetwork¾ Integration offunctional modulesfrommultiple suppliers7Oct. 23rd 2008¾ Maintainability throughout thewhole “Product Life Cycle“Architecture¾ Increased use of “Commercialoff the shelf hardware“¾ Software updatesand upgrades overvehicle lifetimeApplicationMethodologyInterfaces¾ Consideration ofavailability and safetyrequirements¾ RedundancyactivationAUTOSAR Tutorial

AUTOSARMain Working ectureApplicationMethodologyInterfaces8¾ Architecture:Software architecture including a complete basic orenvironmental software stack for ECUs – the so calledAUTOSAR Basic Software – as an integration platform forhardware independent software applications.¾ Methodology:Exchange formats or description templates to enable aseamless configuration process of the basic software stackand the integration of application software in ECUs and itincludes even the methodology how to use this framework.¾ Application Interfaces:Specification of interfaces of typical automotive applicationsfrom all domains in terms of syntax and semantics, whichshould serve as a standard for application software.Oct. 23rd 2008AUTOSAR Tutorial

Technical scope of ervicesIndustry-wideconsolidation of‚existing‘ basicsoftware designs9Oct. 23rd 2008Meta ModelExchangeFormatsConfigurationConceptVirtual FunctionBus NetworkManagementDiagnosticsComm.ServicesGatewayOS DriversDriversAUTOSAR TutorialBus systems

Benefits from AUTOSAR OEM overlapping reuse of software modulesMaintaining ability to compete on innovative functions,enlarged design flexibility Simplification of the integration task Reduction of total SW development costsOEMSupplier Reduction of version proliferationDevelopment partitioning among suppliersIncrease of efficiency in functional developmentNew business models possible Tool providerCommon interfaces with developmentprocesses Seamless, manageable, task optimized(time dependent) tool landscapeNew marketentrant10Oct. 23rd 2008AUTOSAR Tutorial Transparent and definedinterfaces enable newbusiness models

Project Setup Phase II11Oct. 23rd 2008AUTOSAR Tutorial

AUTOSAR – Partnership upplier)Supplier)(OEMOrganizationalcontrolcontrol OrganizationalTechnicalcontributionscontributions TechnicalAdministrativecontrolcontrol ationInformation Groups s fofWorkingWorkingGroupsGroups s InvolvementTechnicalcontributionscontributions ation AccessSupport Roles DevelopmentMembers ofinalizedfinalizeddocumentsdocuments d Utilization12Oct. 23rd 2008AUTOSAR Tutorial

AUTOSAR – Core Partners and MembersStatus: 10th October 20089 Core Partner6 Development Member85 Associate Member55 Premium MemberGeneralOEMGenericTier 1StandardSoftwareUp-to-date status see: http://www.autosar.org13Oct. 23rd 2008AUTOSAR TutorialTools andServicesSemiconductors

AUTOSAR Phase II 2007 – 2009¾ AUTOSAR Development Partnership continues¾ Identical Core Partners¾ Exploitation and maintenance Already in 2008 the first cars on the road with AUTOSAR technology inside All Core Partners have planned the introduction of AUTOSAR products until 2010 Establish conformance test specifications and process¾ Further development and amendment of the standard, e.g. Functional safety features Support for multi core microcontrollers Vehicle & application mode management Debugging and error handling Variant handling Timing model Standardization of application interfaces14Oct. 23rd 2008AUTOSAR Tutorial

Top Level Schedule for AUTOSAR in phase IIPhase II (2007 – 2009)Basic Software & RTESpecification R3.0Finalizat.Maintain R3.0 SpecificationsSpecification R3.1Finalizat.Maintain R3.1 SpecificationsConcepts R4.0Specification R4.0CT Pilot Conformance Test PreparationCT Spec 2nd setCT Spec 1st setValidator 2CT 3rd setMaint. R4.0CT 4th setMaintain CTSValidation R4.0 (BSW/RTE Methodology)Methodology and TemplatesMethodology & Templates R3.0 Finalizat.Methodology & Templates R4.0Maint. R4.0Application InterfacesSpecification Appl. Interfaces R3.0Finalizat.28.09.07 21.12.07Specification 3.0 ReadyRelease 3.01H 20072H 2007200715Oct. 23rd 2008Specification Application Interfaces R4.030.05.0827.06.08Release 3.1Specification 3.1 Ready1H 200812.12.08AUTOSAR Tutorial27.11.0924.07.09Spec R4.0 MS3 Ready Validation & CT 4.02H 20082008Maint. R4.01H 2009Release 4.02H 20092009

AUTOSAR Phase IIWork Package Breakdown StructureWork PackagesII-1II-2Software reArchitectureWPII-1.1.1SoftwareArchitectureand OSWPII-1.1.2Vehicle andApplicationMode Mgmt.WPII-1.1.3WPII-1.1.4DebuggingError HandlingII-2.1Basic SoftwareWPII-2.1.1COM onMaintenance n ofAppl. InterfacesWPII-3.1Basic SoftwareValidationCommunicationand Change andRelease Mgmt.WPII-10.1Body andComfortWPII-5.3Maintenance 0PowertrainWPII-2.1.3WPII-1.1.5MCALVFB and Safety16Oct. 23rd 2008WPII-10.4Occupants andPedest. ecificationWPII-10.5MM / T / HMIAUTOSAR Tutorial

Use Cases of AUTOSAR Results¾ Exchange of SW-Components¾ Re-use of SW components for different platforms shown by uses casespedal managementfront light management17Oct. 23rd 2008AUTOSAR Tutorial

Use Case ‘Pedal Management’ view for one ECU¾Implementation of functions independent on distribution on different ECUas communication will be done via ECU-individual AUTOSAR-RTE exclusivelyvoid distribute v(void){ Rte Write p v(rte i, v) }distribute v()void v warn(void){ Rte Read p v(rte i, v) }18Oct. 23rd 2008AUTOSAR Tutorial

Use Case ‘Pedal Management’ view for two ECUsdistribute v()e.g. FlexRay, CAN, etc.Technical benefits19Oct. 23rd 2008 Reuse of Intellectual PropertyIncrease in design flexibilitySimplification of the integration taskReduction of SW development costsAUTOSAR Tutorial

Use case ‘Front-Light Management’ in AUTOSARLightRequestFront-Light Managercheck switch ()switch event(event)switch event(event)request light(type, mode)request light(type, mode)get keyposition()set light(type, mode)SwitchEventAUTOSAR Int.AUTOSAR InterfaceAUTOSAR InterfaceHeadlightset light(type, mode)set current ( )AUTOSAR InterfaceAUTOSAR tingSystemStd. aceServicesCommunicationECUAbstractionStd. InterfaceStd. InterfaceStd. InterfaceComplexDeviceDriversStandardized InterfaceDIOPWMCAN DriverMicrocontroller AbstractionECU-Hardware20Oct. 23rd 2008AUTOSARInterfaceAUTOSAR Tutorial

Exchange of type of front-lightSwitchEventLightRequestFront-Light Managercheck switch ()switch event(event)switch event(event)request light(type, mode)request light(type, mode)get keyposition()set light(type, mode)AUTOSAR Int.AUTOSAR InterfaceAUTOSAR InterfaceHeadlightXenonlightset light(type, mode)set current ( )AUTOSAR InterfaceAUTOSAR tingSystemStd. aceServicesCommunicationECUAbstractionStd. InterfaceStd. InterfaceStd. InterfaceComplexDeviceDriversStandardized InterfaceDIOPWMDIOCAN DriverMicrocontroller AbstractionECU-Hardware21Oct. 23rd 2008AUTOSARInterfaceAUTOSAR Tutorial

Distribution on ECUsSwitchEventLightRequestLightRequestFront-Light Managercheck switch ()switch event(event)switch event(event)request light(type, mode)request light(type, mode)get keyposition()set light(type, mode)AUTOSAR Int.AUTOSARAUTOSAR InterfaceInterfaceAUTOSAR InterfaceXenonlightset light(type, mode)set current ( )AUTOSAR InterfaceAUTOSAR tingSystemStd. aceServicesCommunicationECUAbstractionStd. InterfaceStd. InterfaceStd. InterfaceComplexDeviceDriversStandardized InterfaceDIOPWMDIOCAN DriverMicrocontroller AbstractionECU-Hardware22Oct. 23rd 2008AUTOSARInterfaceAUTOSAR Tutorial

Use case ‘Front-Light Management’ in AUTOSARLightRequestFront-Light Managercheck switch ()switch event(event)switch event(event)request light(type, mode)request light(type, mode)get keyposition()set light(type, mode)SwitchEventXenonlightset light(type, mode)set current ( )AUTOSAR InterfaceAUTOSAR InterfaceAUTOSAR RTEAUTOSAR RTEAUTOSAR RTEStd. unicationCommunicationECUAbstractionStd. InterfaceStd. InterfaceStd. InterfaceStd. InterfaceStd. InterfaceStd. InterfaceAUTOSAR Int.AUTOSAR InterfaceStandardized InterfaceDIOCAN DriverMicrocontroller AbstractionECU-HardwareStandardized InterfaceCAN DriverOct. 23rd 2008CAN DriverPWMMicrocontroller AbstractionMicrocontroller AbstractionECU-HardwareECU-HardwareCAN Bus23Standardized InterfaceAUTOSAR Tutorial

AUTOSAR Key TopicsAUTOSAR provides three main areas of results:¾ Architecture:Software architecture including a complete basic (environmental) software stack for anECU as an integration platform for hardware independent SW applications¾ Methodology:Exchange formats (templates) to enable a seamless configuration process of the basicsoftware stack and the integration of application software in ECUs¾ Application Interfaces:Specification of application interfaces as a standard for application software modules24Oct. 23rd 2008AUTOSAR Tutorial

Main Concepts: Architecture¾ Basic Software modules¾ Run time environment and communication¾ Results of sample implementation in „Validator 2“25Oct. 23rd 2008AUTOSAR Tutorial