a specification proposed by jaspar has been adopted … a specification proposed by jaspar has been...

Japan Automotive Software Platform and Architecture

JASPAR General Incorporated Association

A specification proposed by JASPAR has been adopted for AUTOSAR.


1. Introduction

An RTE profile specification proposed by JASPAR has been adopted for the Automotive Open System Architecture (AUTOSAR).

JASPAR proposed the RTE profile specification to AUTOSAR. This specification maintains the performance and minimizes resource requirements (ROM and RAM size) for existing small ECUs so that they are able to use AUTOSAR. The resource-light RTE profile was formally adopted in the

AUTOSAR R4.1.1 specification.

2/13


1.1 Collaboration between AUTOSAR and JASPAR

JASPAR undertakes implementation and testing for automotive applications of the Automotive Open System Architecture (AUTOSAR).

JASPAR and AUTOSAR have regular meetings and share information about their activities.

3/13

Automotive Open System Architecture (AUTOSAR): A European standards organization led by BMW, Bosch, and others for the modularization and standardization of automotive software

Japan Automotive Software Platform and Architecture (JASPAR): An industry body led by Japanese manufacturers such as Toyota, Honda, Nissan that seeks to standardize automotive software, communications, and hardware

Propose

• Formulate specification• Define as international standard

AUTOSAR specification

• Implementation and verification• Investigate and test issues and countermeasures


2. Analysis of AUTOSAR carried out by JASPAR

Advantages and Disadvantages with AUTOSAR specification identified by JASPAR

Advantages: Standardization and modularization of control softwareDisadvantages: Higher power consumption, performance degradation

4/13

Allows software modularization Easy reconfiguration of

other ECUs

Wider scope of application and greater redundancy means more

resources required and performance degradation

AUTOSAR Software Architecture

General-purpose functions

IINon-competitive area

OEM-specific functionsII

Competitive area

Advantages

Respond promptly to

customer needs

Standardization through use of Basic Software, hardware

virtualization

Disadvantages

This significantly influences small ECUs which are common in automotive systems

Easy porting of software to other products

Need to support wide range of ECU functions means more resources required and performance degradation if a wrong profile is adopted


3. Background to JASPAR’s Proposal to AUTOSAR

JASPAR believes it necessary to achieve a balance of efficiency and reusability so that the advantages of AUTOSAR can be extended to small ECUs

5/13

JASPAR concept

Reusability, Functionality

Efficiency

LowLow

HighLegacy methods

Best balance

AUTOSAR

High

BSW specification development activity by JASPAR(FY2007 to FY2009)Achieve a balance between legacy methods and AUTOSAR


3.1 Objective of JASPAR’s Proposal to AUTOSAR

JASPAR developed a specification to present to AUTOSAR that sought to utilize AUTOSAR on existing small ECUs without compromising its reusability advantages.

Define concrete solutions in the form of a specification (JASPAR RTE Profile Specification)

Optimization of functions (profile)Reduce the number of API of AUTOSAR BSWs depending on the target domain (system)

6/13


Profile based on representative patterns

JASPAR profile

S0

S1

FULL

[1] Body control profile

[2] Powertrain control profile

[3] Chassis control profile

[4] Safety control profile

3.2 JASPAR’s Proposal to AUTOSAR (Profile)

How did we optimize functions?Select/limit AUTOSAR functions by application domain

Classify AUTOSAR functions based on domain size

7/13


3.3 JASPAR’s Proposal to AUTOSAR (Profile)

JASPAR profile [1] Body control profile(Body and Comfort)

[2] Powertrain control profile(Powertrain)

[3] Chassis control profile(Chassis Control)

[4] Safety control profile(Safety Systems)

Typical ECUs A/C, lightsDoor control

EngineTransmission

ABSESP

X-by-Wire ECU

Typical microcontrollers 16-bit32-bit (low end)

32-bit (mid-range) 32-bit (mid-range) 32-bit (high-end)

Communication bus MS-CAN HS-CAN, FlexRay HS-CAN, FlexRay FlexRay

Schedule pack － FlexRay-RTB FlexRay-RTB FlexRay-FTB

JASPAR RTE profile S0 S1 S1 S1 FULL

JASPAR communication profile

S0 S1 S1 S1 FULL

JASPAR OS profile S0A (no OS)/S0 (OS)

S1 S1 S1 FULL(AUTOSAR SC2)

Comma (,): Choice or bothHS: High speed, MS: Medium speed, RTB: Real time bus, FTB: Fault tolerant bus, S#: Subset #

Example use of JASPAR profile specification to allow use on small ECUs

Develop profile specifications for actual products

8/13


JASPAR activity on BSW specification proposal for AUTOSAROverview presentation of JASPAR profile specification to management in May 2010

Agreement in principle on incorporating JASPAR BSW specification in AUTOSAR R4.1 specification

Overview presentation and QA session held at engineers’ meeting in September 2010Approval received from AUTOSAR engineers and project managersAgreement on JASPAR submitting a detailed specification with the aim of inclusion in the AUTOSAR R4.1.1 specification

Detailed presentation of JASPAR BSW specification at engineers’ meeting in Feb. 2011Proposal to engineers, decision to accept RTE profile

Formal adoption of RTE profile in AUTOSAR R4.1.1 specificationAUTOSAR R4.1.1 specification issued in March 2013

4.1 Proposal Development by JASPAR

9/13


4.2 Adoption by AUTOSAR

10/13

Formal adoption of RTE profile in AUTOSAR R4.1.1 specification

RTE/VFB Chapter 11 “VFB Features and Profiles” addedBecame possible to select functions by defining profileFunctions selected in profile listed in function list

AUTOSAR profile

(Extract from AUTOSAR VFB specification R4.1.1)

Updates from R4.0.3 to R4.1.1

AUTOSAR VFB specification R4.1.1:http://www.autosar.org/

Specifications →Release 4.1 →Main →Auxiliary Material 6 → AUTOSAR_EXP_VFB (pdf, 1180 kb)


5. Conclusion

The JASPAR proposal has widened the scope for application of AUTOSAR to a wider range of vehicles.

11/13


6. Future Activities

JASPAR will promote the use of standards to spread work loads and facilitate global deployment

Use of AUTOSAR technologiesUse of technologies including specification descriptionProvision of development environments and use of management techniques

Future approach of JASPAR regarding AUTOSARContinue to contribute to AUTOSAR activities by reviewing specifications for next-generation software and making proposals

12/13


End

13/13

a specification proposed by jaspar has been adopted … a specification proposed by jaspar has been...

Documents