The Fully Networked Car ITU-T Workshop on ICT in Vehicles

advertisement
The Fully Networked Car
ITU-T Workshop on ICT in Vehicles
2-4 March, 2005
75th Geneva International Motor Show
AUTomotive Open System ARchitecture (AUTOSAR)
An Industry-wide Initiative to Manage the Complexity of Emerging E/E
Architectures
Dr. Thomas Scharnhorst
Vehicle System Electronics, Volkswagen AG
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
EE
React faster and more precise
than humans to avert imminent
danger
(ESP, ABS, Airbag, ...)
Vehicle personalization
(N-Zones air condition, Keyless
Entry, ...)
Vehicle Assistance
Comfort
Growing
vehicle
complexity
Environment
Legal Requirements
Driver Assistance
OBD diagnosis
Reduction of polluting exhausts
and fuel consumption
Relieve driver and enhance
driver‘s focus
(SVA, LVA, ACC, navigation)
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
EE
page 1
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Growth of vehicle electronics complexity is driven by four main objectives.
A large number of ECUs are networked in a recent car (2005).
Headlight levelling
Rain/light sensor
Dynamic Bending Light
Engine management
Wiper module
Steering booster
Comfort
Instrument cluster
Start/Stop System
ABS/ESP
Gateway
Transmission
Sunroof
Driver‘s door
Adaptive Cruise Control
Back door
Keyless Entry
Parking distance
control system
Electrical system
El. Parking Brake
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
EE
page 2
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Air condition
Steering column
The number of networked ECUs increased 2-3fold with the introduction of the
current generation of VW cars.
Touareg
Phaeton D1
40
Golf A5
35
30
(CAN, SUB-CAN, LIN)
Number of networked ECUs
45
Passat B6
25
Passat B5GP
20
15
10
Passat B5
Golf A4
5
0
1996
1997
1998
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
Golf A4
Golf A4,
Polo A04
1999
EE
2000
2001
page 3
2002
2003
2004
2005
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
50
!
Infotainment
!
Power Management
!
Human-Machine-Interface
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
EE
!
Continuously rising number of
ECUs
!
ECUs with networked functions
increase system complexity
!
Management of the complexity
requires thinking on a system
level – ‚Systems Engineering‘.
page 4
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
A new generation of vehicles introduced in 2001-2003 marks the transition
from single components to a functional network.
While progress has been made with respect to some components, system
quality is unsatisfying.
Defects per
100 cars
~constant number of
defects per function
75
100%
80%
50
60%
40%
electronic
functions
25
20%
0%
0
1999
2000
2001
Source: Bosch
2002
2003
* referred to 1999 = 100 %
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
2004
EE
50
100
150
200
250
300
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
page 5
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Field failures
Airbag ECU*
Management of the grown complexity requires professional system
engineering supported by standardization.
Industry-wide standardization
Automotive Open System
Architecture
(AUTOSAR)
Establishment of an open
standard for automotive
E/E architectures
• Standardization and
re-use
• Scalability
• Transferability of
functions
• Improved maintenance
and software updates
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
Functional
Functional
Requirements
Requirements
Specification
Experience
SystemDesign
Design
System
Architecture
Architecture
Specification
Mapping
Mapping
toECUs
ECUs
to
Supplier
Development
EE
ECU
ECU
Development
Development
Results
Final
Final
acceptance
acceptance
Systemtest
test
System
Integration
Integration
test
test
Test
Test
• SoFa
• WiFa
• KAF
• Intensive tests
• Reference Station
• HiL
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
System Engineering
Starting conditions were insufficient to manage the growing E/E complexity at
the end of the 1990s.
Completely different solutions
for identical customer
functions.
For OEMs, electronic
components are black boxes.
Long-term use of proven electronic components is economically not feasible.
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
EE
page 7
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Each manufacturer uses his own
standards.
Industry is fragmented.
AUTOSAR aims to improve complexity management of integrated E/E
architectures through increased reuse and exchangeability of SW modules.
Platform m.1
Platform m.2
Platform m.n
Platform 1.1
Platform 1.2
Platform 1.n
Supplier A
" Chassis
" Safety
" Body/Comfort
" Multimedia
Transferability
between manufactureres
Supplier B
" Chassis
" Safety
" Telematics
" Multimedia
Transferability
between suppliers
OEM m
OEM 2
Supplier C
" Body/Comfort
" Powertrain
" Telematics
" Multimedia
Platform 2.1
Platform 2.2
Platform 2.n
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
Transferability
between vehicle platforms
EE
page 8
Platform m.1
Platform m.2
Platform m.n
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
OEM n
OEM 1
AUTOSAR was launched in 2002 to establish an open standard for automotive
E/E architectures.
First talks between BMW,
Bosch, Continental
Teves, DaimlerChrysler,
Volkswagen, and later
Siemens VDO
Ford, Peugeot Citroën, and
Toyota become Core Members
Establishment of a
technical team
08/02
General Motors joins as a
Core Member
11/02
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
11..12/03
08/03
EE
page 9
12/04
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Official formation of the
AUTOSAR (AUTomotive Open
System ARchitecture)
partnership
AUTOSAR 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 Software
FlexRayHIS
Local interconnect network
2001
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
2006
EE
page 10
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
OSEK/VDX
Core Partner
(OEM & 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
Support Roles:
# Development
Members
# Attendees
Associate Members
# Access to finalized documents
# Implementation of standards
Organization similar to FlexRay
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
EE
page 11
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
The AUTOSAR standard is jointly developed by core partners and premium
members and supported by additional roles.
Worldwide, OEMs and suppliers participate in AUTOSAR.
Development
Members
10 Core Partners
Attendees
35 Premium Members
General
Generic
Standard
OEM
Tier 1
Software
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
EE
page 12
Tools
Semiconductors
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
7 Associate
Members
The AUTOSAR core partners manage the project and maintain organizational
control.
Project Organization
Support Functions
Steering Committee
Spokesperson
Administration
Project Control
Office
PL Team
Technical Office
System Team
Basic SW
Architecture Team
Working Groups
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
Technical Manager
EE
page 13
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Executive Board
Approximately 200 full time equivalent employees are working for AUTOSAR.
7
3
10
15
WP Active
WP Speaker
System Team
PL-Team
7
13
Steering Committee
Support Functions
WP Passive
145
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
EE
page 14
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Estimated full time equivalents in the project organization (total ~ 200 FTE)
To achieve the objectives, AUTOSAR has to address the main topics:
software integration, basic software, and functional APIs.
Project Objectives
#
Consideration of availability and safety requirements
#
Redundancy activation
#
Scalability to different vehicle and platform variants
#
Implementation and standardization of basic system
functions as an OEM wide “Standard Core“ solution
#
#
#
Methods of Software
Integration
Transferability of functions throughout network
#
Basic Software
Integration of functional modules from multiple
suppliers
#
Functional APIs
#
Maintainability throughout the whole “Product Life Cycle“
#
Increased use of “Commercial off the shelf hardware“
#
Software updates and upgrades over vehicle lifetime
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
EE
page 15
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Topics
The AUTOSAR ECU software architecture comprises the layers Application,
AUTOSAR Run Time Environment (RTE), and Basic Software.
Actuator
Software
Component
Sensor
Software
Component
AUTOSAR
Interface
AUTOSAR
Interface
AUTOSAR
Interface
AUTOSAR
Software
..............
Application
Software
Component
AUTOSAR
Interface
AUTOSAR
Software
Component
AUTOSAR Runtime Environment (RTE)
Standardized
Interface
Standardized
Inteface
Operating
System
Standardized
AUTOSAR
Interface
Standardized
Interface
Services
Communication
Standardized
Interface
Standardized
Interface
Microcontroller
Abstraction
ECU-Hardware
Elektronikstrategie
EE
ECU
Abstraction
Standardized
Interface
Standardized
Interface
Basic Software
Elektrik-/Elektronik-Entwicklung
AUTOSAR
Interface
page 16
AUTOSAR
Interface
Complex
Device
Drivers
Interface
ECU
Firmware
Standard
Software
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Application
Software
Component
AUTOSAR applications contain functional software components.
Actuator
Software
Component
Sensor
Software
Component
AUTOSAR
Interface
AUTOSAR
Interface
AUTOSAR
Interface
AUTOSAR
Software
..............
Application
Software
Component
AUTOSAR
Interface
AUTOSAR
Software
Component
AUTOSAR Runtime Environment (RTE)
Standardized
Interface
Standardized
Inteface
Operating
System
Standardized
AUTOSAR
Interface
Standardized
Interface
Services
Communication
Standardized
Interface
Standardized
Interface
Microcontroller
Abstraction
ECU-Hardware
Elektronikstrategie
EE
ECU
Abstraction
Standardized
Interface
Standardized
Interface
Basic Software
Elektrik-/Elektronik-Entwicklung
AUTOSAR
Interface
page 17
AUTOSAR
Interface
Complex
Device
Drivers
Interface
ECU
Firmware
Standard
Software
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Application
Software
Component
The Run Time Environment (RTE) forms the central communication layer.
Actuator
Software
Component
Sensor
Software
Component
AUTOSAR
Interface
AUTOSAR
Interface
AUTOSAR
Interface
AUTOSAR
Software
..............
Application
Software
Component
AUTOSAR
Interface
AUTOSAR
Software
Component
AUTOSAR Runtime Environment (RTE)
Standardized
Interface
Standardized
Inteface
Operating
System
Standardized
AUTOSAR
Interface
Standardized
Interface
Services
Communication
Standardized
Interface
Standardized
Interface
Microcontroller
Abstraction
ECU-Hardware
Elektronikstrategie
EE
ECU
Abstraction
Standardized
Interface
Standardized
Interface
Basic Software
Elektrik-/Elektronik-Entwicklung
AUTOSAR
Interface
page 18
AUTOSAR
Interface
Complex
Device
Drivers
Interface
ECU
Firmware
Standard
Software
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Application
Software
Component
The AUTOSAR Basic Software supplies standardized interfaces to access the
infrastructure.
Actuator
Software
Component
Sensor
Software
Component
AUTOSAR
Interface
AUTOSAR
Interface
AUTOSAR
Interface
AUTOSAR
Software
..............
Application
Software
Component
AUTOSAR
Interface
AUTOSAR
Software
Component
AUTOSAR Runtime Environment (RTE)
Standardized
Interface
Standardized
Inteface
Operating
System
Standardized
AUTOSAR
Interface
Standardized
Interface
Services
Communication
Standardized
Interface
Standardized
Interface
Microcontroller
Abstraction
ECU-Hardware
Elektronikstrategie
EE
ECU
Abstraction
Standardized
Interface
Standardized
Interface
Basic Software
Elektrik-/Elektronik-Entwicklung
AUTOSAR
Interface
page 19
AUTOSAR
Interface
Complex
Device
Drivers
Interface
ECU
Firmware
Standard
Software
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Application
Software
Component
The use case ‘Front Light Management’ illustrates the interaction of
components within the AUTOSAR architecture.
Switch event
Light Request
Front-Light Manager
check_switch ()
switch_event
(event)
switch_event (event)
request_light
(type, mode)
request_light (type, mode)
get_keyposition ( )
set_light (type, mode)
set_dboard(type,mode)
SW-Component
n
Application
Software
...
AUTOSAR
Interface
AUTOSAR RTE
AUTOSAR
Interface
set_light(...)
Headlight
Abstraction
HW independent
Services
(e.g. StateMachines,
Subscribing)
AUTOSAR
Interface
get_keyposition ( )
set_dboard (type,mode)
HW dependent
Services
(NVRAM, Timer,
fault memory
etc.)
HW dependent Services
(NVRAM, Timer,
fault memory
etc.)
Complex
Device
Driver
API 0
standardized
Interface
standardized Interface
DIO
PWM
ADC
SPAL
Microcontroller Abstraction
ECU-Hardware
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
EE
page 20
COM Driver
standardized interface
AUTOSAR
Interface
Basic Software (standardized)
API 1
Operating
Systems
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
API 2
Replacing the headlight by another type has only minimal impact on the
components involved in the use case.
Switch event
Light Request
Front-Light Manager
check_swtich ()
switch_event
(event)
switch_event (event)
request_light
(type, mode)
request_light (type, mode)
get_keyposition ( )
set_light (type, mode)
set_dboard(type,mode)
SW-Component
n
Application
Software
...
AUTOSAR
Interface
AUTOSAR RTE
AUTOSAR
Interface
set_light(...)
Xenon-light
Headlight
Abstraction
HW independent
Services
(e.g. StateMachines,
Subscribing)
AUTOSAR
Interface
get_keyposition ( )
set_dboard (type,mode)
HW dependent
Services
(NVRAM, Timer,
fault memory
etc.)
HW dependent Services
(NVRAM, Timer,
fault memory
etc.)
Complex
Device
Driver
API 0
standardized
Interface
standardized Interface
DIO
PWM
DIO
ADC
SPAL
Microcontroller Abstraction
ECU-Hardware
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
EE
page 21
COM Driver
standardized interface
AUTOSAR
Interface
Basic Software (standardized)
API 1
Operating
Systems
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
API 2
Following the AUTOSAR Method, the E/E architecture is derived from the
formal description of software and hardware components.
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Using „Software Component
Descriptions“ as input, the „Virtual
Functional Bus“ validates the
interaction of all components and
interfaces before actual software
implementation.
The AUTOSAR Method supports the
generation of an E/E architecture.
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
EE
page
22
page 22
The AUTOSAR standard will be completed and available to OEM product
development in 2006.
09/04
11/05
12/03
Initiation of
Partnership
06/05
Structure & Basis
Specification
Project plan
created
and agreed
Standardization
Implementation of the
AUTOSAR
SW-Components
architecture
AUTOSAR Concept and first
specification are created and
executability is approved
AUTOSAR concept (specification
and preparation of a de-facto
standard) is feasible and in plan
Elektronikstrategie
Realization of Run Time
Environment feasible and on
track
EE
02/06
page 23
Milestones
Test- & Integrationprocess
AUTOSAR compatibility of selected
SW modules is approved. First
tools and generators are available
WP10 / WP20
Elektrik-/Elektronik-Entwicklung
08/06
Phases
AUTOSAR
specifications are
tested and verified
on an application
Evaluated test and integration
process (product oriented)
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
05/03
AUTOSAR contributes elements to the integrated Systems Engineering
approach.
Concept & Architecture
Integration
RE/RM, model-based development,
architecture evaluation
PCO, Version Management
Systems Engineering
and Architecture
Deterministic
Behaviour
Standard. of Basic Software
Standardization of Interfaces
Modularity and Transferability of Functions
Central System Functions
Power Management, Diagnosis
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
EE
page 24
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Process
Simulation, test against requirements
1
Fast growth of the complexity of automotive E/E architectures is a major
challenge with respect to product quality.
2
Through interconnection of subsystems, new system properties emerge
which have to be understood and controlled.
3
Systems Engineering is an integrated approach which covers the
development process and the complete product life cycle.
4
AUTOSAR enables management of the growing E/E complexity with respect
to technology and economics.
5
AUTOSAR pushes the paradigm shift from an ECU based to a function
based approach in automotive software development.
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
EE
page 25
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Conclusion
Dr. Thomas Scharnhorst: 75th Geneva International Motor Show .2005-03-03
Vielen Dank für Ihre Aufmerksamkeit
Elektrik-/Elektronik-Entwicklung
Elektronikstrategie
EE
Thank you for your attention
page 26
Download