AUTomotive Open System ARchitecture (AUTOSAR) An Industry-wide Initiative to Manage the Complexity of Emerging E/E Architectures

Transcription

1 The Fully Networked Car ITU-T Workshop on ICT in Vehicles 2-4 March, th Geneva International Motor Show AUTomotive Open System ARchitecture () An Industry-wide Initiative to Manage the Complexity of merging / Architectures Dr. Thomas Scharnhorst Vehicle System lectronics, Volkswagen AG lektrik-/lektronik-ntwicklung lektronikstrategie

2 React faster and more precise than humans to avert imminent danger (SP, ABS, Airbag,...) Vehicle personalization (N-Zones air condition, Keyless ntry,...) Vehicle Assistance Comfort Growing vehicle complexity nvironment Legal Requirements Driver Assistance OBD diagnosis Reduction of polluting exhausts and fuel consumption Relieve driver and enhance driver s focus (SVA, LVA, ACC, navigation) lektrik-/lektronik-ntwicklung lektronikstrategie page 1 Growth of vehicle electronics complexity is driven by four main objectives.

3 A large number of CUs are networked in a recent car (2005). Headlight levelling Rain/light sensor Dynamic Bending Light ngine management Wiper module Steering booster Comfort Instrument cluster Start/Stop System ABS/SP Gateway Transmission Sunroof Driver s door Adaptive Cruise Control Back door Keyless ntry Parking distance control system lectrical system l. Parking Brake lektrik-/lektronik-ntwicklung lektronikstrategie page 2 Air condition Steering column

4 The number of networked CUs increased 2-3fold with the introduction of the current generation of VW cars. Touareg Phaeton D1 40 Golf A (CAN, SUB-CAN, LIN) Number of networked CUs 45 Passat B6 25 Passat B5GP Passat B5 Golf A lektrik-/lektronik-ntwicklung lektronikstrategie Golf A4 Golf A4, Polo A page

5 ! Infotainment! Power Management! Human-Machine- lektrik-/lektronik-ntwicklung lektronikstrategie! Continuously rising number of CUs! CUs with networked functions increase system complexity! Management of the complexity requires thinking on a system level Systems ngineering. page 4 A new generation of vehicles introduced in marks the transition from single components to a functional network.

6 While progress has been made with respect to some components, system quality is unsatisfying. Field failures Airbag CU* Defects per 100 cars 100% 80% 60% 40% 20% 0% Source: Bosch * referred to 1999 = 100 % lektrik-/lektronik-ntwicklung lektronikstrategie page 5 ~constant number of defects per function electronic functions JD Power IQS ratings: defects per 100 vehicles, October 2003, sum of Features and Controls, Sound System, HVAC Source: JD Power & Associates; McKinsey and Company

7 Management of the grown complexity requires professional system engineering supported by standardization. Industry-wide standardization Automotive Open System Architecture () stablishment of an open standard for automotive / architectures Standardization and re-use Scalability Transferability of functions Improved maintenance and software updates lektrik-/lektronik-ntwicklung lektronikstrategie Functional Functional Requirements Requirements Specification xperience SystemDesign Design System Architecture Architecture Specification Mapping Mapping tocus CUs to Supplier Development CU CU Development Development Results Final Final acceptance acceptance Systemtest test System Integration Integration test test Test Test SoFa WiFa KAF Intensive tests Reference Station HiL System ngineering

8 Starting conditions were insufficient to manage the growing / complexity at the end of the 1990s. Industry is fragmented. ach manufacturer uses his own standards. For OMs, electronic components are black boxes. lektrik-/lektronik-ntwicklung lektronikstrategie page 7 Completely different solutions for identical customer functions. Long-term use of proven electronic components is economically not feasible.

9 aims to improve complexity management of integrated / architectures through increased reuse and exchangeability of SW modules. OM 1 OM n OM 2 Platform 2.1 Platform 2.2 Platform 2.n Platform 1.1 Platform 1.2 Platform 1.n Transferability between manufactureres Supplier A " Chassis " Safety " Body/Comfort " Multimedia Supplier B "Chassis "Safety "Telematics " Multimedia Supplier C "Body/Comfort " Powertrain "Telematics " Multimedia Transferability between vehicle platforms Platform m.1 Platform m.2 Platform m.n OM m Transferability between suppliers Platform m.1 Platform m.2 Platform m.n lektrik-/lektronik-ntwicklung lektronikstrategie page 8

10 was launched in 2002 to establish an open standard for automotive / architectures. First talks between BMW, Bosch, Continental Teves, DaimlerChrysler, Volkswagen, and later Siemens VDO stablishment of a technical team lektrik-/lektronik-ntwicklung lektronikstrategie Official formation of the (AUTomotive Open System ARchitecture) partnership Ford, Peugeot Citroën, and Toyota become Core Members page 9 General Motors joins as a Core Member 08/02 11/02 08/ /03 12/04

11 integrates existing and emerging industry electronics standards. MSR Manufacturer-Supplier Relationship ASAM ODX 2002 ASAM/ODX AUTomotive Open System ARchitecture Media Orientated System Transport Hersteller Initiative FlexRayHIS Local interconnect network 2001 lektrik-/lektronik-ntwicklung lektronikstrategie 2006 page 10 OSK/VDX

12 The standard is jointly developed by core partners and premium members and supported by additional roles. Core Partner (OM & Tier 1 Supplier) # Strategy # Organizational control # Technical contributions # Administration # Approval of external Information # Leadership and contribution in working groups Premium Members # Leadership of working groups # Involvement in working groups # Technical contributions # Access to current information Associate Members # Access to finalized documents # Implementation of standards Support Roles: # Development Members # Attendees Organization similar to FlexRay lektrik-/lektronik-ntwicklung lektronikstrategie page 11

13 Worldwide, OMs and suppliers participate in. 10 Core Partners Development Members Attendees 7 Associate Members 35 Premium Members General OM Generic Tier 1 Standard Tools Semiconductors lektrik-/lektronik-ntwicklung lektronikstrategie page 12

14 The core partners manage the project and maintain organizational control. Project Organization Support Functions xecutive Board Administration Steering Committee PL Team System Team Working Groups Spokesperson Basic SW Architecture Team Technical Manager Project Control Office Technical Office lektrik-/lektronik-ntwicklung lektronikstrategie page 13

15 Approximately 200 full time equivalent employees are working for. stimated full time equivalents in the project organization (total ~ 200 FT) WP Active WP Speaker System Team PL-Team Steering Committee Support Functions WP Passive lektrik-/lektronik-ntwicklung lektronikstrategie page 14

16 To achieve the objectives, has to address the main topics: software integration, basic software, and functional APIs. Project Objectives Topics # Consideration of availability and safety requirements # Redundancy activation # Scalability to different vehicle and platform variants # Implementation and standardization of basic system functions as an OM wide Standard Core solution # Transferability of functions throughout network # Integration of functional modules from multiple suppliers # Maintainability throughout the whole Product Life Cycle # Increased use of Commercial off the shelf hardware # updates and upgrades over vehicle lifetime lektrik-/lektronik-ntwicklung lektronikstrategie page 15 # Methods of Integration # Basic # Functional APIs

17 The CU software architecture comprises the layers Application, Run Time nvironment (RT), and Basic. Application Operating System Inteface Actuator Runtime nvironment (RT) Services Sensor Communication Basic CU-Hardware... CU Abstraction Microcontroller Abstraction Application Complex Device Drivers CU Firmware Standard lektrik-/lektronik-ntwicklung lektronikstrategie page 16

18 applications contain functional software components. Application Operating System Inteface Actuator Sensor Runtime nvironment (RT) Services Communication Basic CU-Hardware... CU Abstraction Microcontroller Abstraction Application Complex Device Drivers CU Firmware Standard lektrik-/lektronik-ntwicklung lektronikstrategie page 17

19 The Run Time nvironment (RT) forms the central communication layer. Application Operating System Inteface Actuator Sensor Runtime nvironment (RT) Services Communication Basic CU-Hardware... CU Abstraction Microcontroller Abstraction Application Complex Device Drivers CU Firmware Standard lektrik-/lektronik-ntwicklung lektronikstrategie page 18

20 The Basic supplies standardized interfaces to access the infrastructure. Application Operating System Inteface Actuator Sensor Runtime nvironment (RT) Services Communication Basic CU-Hardware... CU Abstraction Microcontroller Abstraction Application Complex Device Drivers CU Firmware Standard lektrik-/lektronik-ntwicklung lektronikstrategie page 19

21 The use case Front Light Management illustrates the interaction of components within the architecture. Switch event check_switch () switch_event (event) Light Request switch_event (event) request_light (type, mode) Front-Light Manager request_light (type, mode) get_keyposition ( ) set_light (type, mode) set_dboard(type,mode) SW- n Application... API 2 Complex Device Driver CU-Hardware HW independent Services (e.g. State- Machines, Subscribing) RT set_light(...) Headlight Abstraction Basic (standardized) standardized DIO PWM ADC HW dependent Services (NVRAM, Timer, fault memory etc.) SPAL Microcontroller Abstraction get_keyposition ( ) set_dboard (type,mode) HW dependent Services (NVRAM, Timer, fault memory etc.) standardized COM Driver API 1 API 0 standardized interface Operating Systems lektrik-/lektronik-ntwicklung lektronikstrategie page 20

22 Replacing the headlight by another type has only minimal impact on the components involved in the use case. Switch event check_swtich () switch_event (event) Light Request switch_event (event) request_light (type, mode) Front-Light Manager request_light (type, mode) get_keyposition ( ) set_light (type, mode) set_dboard(type,mode) SW- n Application... API 2 Complex Device Driver CU-Hardware HW independent Services (e.g. State- Machines, Subscribing) RT set_light(...) Xenon-light Headlight Abstraction Basic (standardized) standardized DIO PWM DIO ADC HW dependent Services (NVRAM, Timer, fault memory etc.) SPAL Microcontroller Abstraction get_keyposition ( ) set_dboard (type,mode) HW dependent Services (NVRAM, Timer, fault memory etc.) standardized COM Driver API 1 API 0 standardized interface Operating Systems lektrik-/lektronik-ntwicklung lektronikstrategie page 21

23 Following the Method, the / architecture is derived from the formal description of software and hardware components. Using Descriptions as input, the Virtual Functional Bus validates the interaction of all components and interfaces before actual software implementation. The Method supports the generation of an / architecture. lektrik-/lektronik-ntwicklung lektronikstrategie page page 22 22

24 The standard will be completed and available to OM product development in /03 09/04 11/05 08/06 12/03 06/05 02/06 Milestones Initiation of Partnership Project plan created and agreed Structure & Basis Specification concept (specification and preparation of a de-facto standard) is feasible and in plan lektrik-/lektronik-ntwicklung lektronikstrategie Concept and first specification are created and executability is approved Standardization Implementation of the SW-s architecture Realization of Run Time nvironment feasible and on track compatibility of selected SW modules is approved. First tools and generators are available WP10 / WP20 page 23 Test- & Integrationprocess valuated test and integration process (product oriented) specifications are tested and verified on an application Phases

25 contributes elements to the integrated Systems ngineering approach. Concept & Architecture R/RM, model-based development, architecture evaluation Integration Simulation, test against requirements Process PCO, Version Management Deterministic Behaviour Modularity and Transferability of Functions lektrik-/lektronik-ntwicklung lektronikstrategie Systems ngineering and Architecture page 24 Standard. of Basic Standardization of s Central System Functions Power Management, Diagnosis

26 Conclusion 1 Fast growth of the complexity of automotive / architectures is a major challenge with respect to product quality Through interconnection of subsystems, new system properties emerge which have to be understood and controlled. Systems ngineering is an integrated approach which covers the development process and the complete product life cycle. enables management of the growing / complexity with respect to technology and economics. pushes the paradigm shift from an CU based to a function based approach in automotive software development. lektrik-/lektronik-ntwicklung lektronikstrategie page 25

27 Vielen Dank für Ihre Aufmerksamkeit lektronikstrategie lektrik-/lektronik-ntwicklung Thank you for your attention page 26