A specification proposed by JASPAR has been adopted for AUTOSAR.

Size: px

Start display at page:

Download "A specification proposed by JASPAR has been adopted for AUTOSAR."

Spencer Greene
6 years ago
Views:

1 Japan Automotive Software Platform and Architecture A specification proposed by JASPAR has been adopted for AUTOSAR. JASPAR General Incorporated Association

2 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).

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

3 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. Automotive Open System Architecture (AUTOSAR): A European standards organization led by BMW, Bosch, and others for the modularization and standardization of automotive software Propose 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 Formulate specification Define as international standard Implementation and verification Investigate and test issues and countermeasures AUTOSAR specification 3/13

2. Analysis of AUTOSAR carried out by JASPAR Advantages and Disadvantages with AUTOSAR specification identified by JASPAR Advantages: Standardization and modularization of control software

4 2. Analysis of AUTOSAR carried out by JASPAR Advantages and Disadvantages with AUTOSAR specification identified by JASPAR Advantages: Standardization and modularization of control software Disadvantages: Higher power consumption, performance degradation AUTOSAR Software Architecture Easy porting of software to other products OEM-specific functions II Competitive area Advantages Respond promptly to customer needs Allows software modularization Easy reconfiguration of other ECUs General-purpose functions II Non-competitive area Standardization through use of Basic Software, hardware virtualization Need to support wide range of ECU functions means more resources required and performance degradation if a wrong profile is adopted This significantly influences small ECUs which are common in automotive systems Disadvantages Wider scope of application and greater redundancy means more resources required and performance degradation 4/13

5 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 BSW specification development activity by JASPAR(FY2007 to FY2009) Achieve a balance between legacy methods and AUTOSAR High Legacy methods Efficiency Best balance AUTOSAR Low Low Reusability, Functionality JASPAR concept High 5/13

6 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

7 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 JASPAR profile Profile based on representative patterns [4] Safety control profile FULL [2] Powertrain control profile [3] Chassis control profile S1 [1] Body control profile S0 7/13

8 3.3 JASPAR s Proposal to AUTOSAR (Profile) Develop profile specifications for actual products Example use of JASPAR profile specification to allow use on small ECUs JASPAR profile [1] Body control profile [2] Powertrain control profile [3] Chassis control profile [4] Safety control profile (Body and Comfort) (Powertrain) (Chassis Control) (Safety Systems) Typical ECUs A/C, lights Engine ABS X-by-Wire ECU Door control Transmission ESP Typical microcontrollers 16-bit 32-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 (AUTOSA R SC2) HS: High speed, MS: Medium speed, RTB: Real time bus, FTB: Fault tolerant bus, S#: Subset # Comma (,): Choice or both 8/13

9 4.1 Proposal Development by JASPAR JASPAR activity on BSW specification proposal for AUTOSAR Overview 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 2010 Approval received from AUTOSAR engineers and project managers Agreement 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 Proposal to engineers, decision to accept RTE profile Formal adoption of RTE profile in AUTOSAR R4.1.1 specification AUTOSAR R4.1.1 specification issued in March /13

10 4.2 Adoption by AUTOSAR Formal adoption of RTE profile in AUTOSAR R4.1.1 specification Updates from R4.0.3 to R4.1.1 RTE/VFB Chapter 11 VFB Features and Profiles added Became possible to select functions by defining profile Functions selected in profile listed in function list AUTOSAR profile (Extract from AUTOSAR VFB specification R4.1.1) AUTOSAR VFB specification R4.1.1: Specifications Release 4.1 Main Auxiliary Material 6 AUTOSAR_EXP_VFB (pdf, 1180 kb) 10/13

11 5. Conclusion The JASPAR proposal has widened the scope for application of AUTOSAR to a wider range of vehicles. 11/13

12 6. Future Activities JASPAR will promote the use of standards to spread work loads and facilitate global deployment Use of AUTOSAR technologies Use of technologies including specification description Provision of development environments and use of management techniques Future approach of JASPAR regarding AUTOSAR Continue to contribute to AUTOSAR activities by reviewing specifications for next-generation software and making proposals 12/13

13 End 13/13

Automotive Networks Are New Busses and Gateways the Answer or Just Another Challenge? ESWEEK Panel Oct. 3, 2007

Automotive Networks Are New Busses and Gateways the Answer or Just Another Challenge? ESWEEK Panel Oct. 3, 2007 Automotive Networks complex networks hundreds of functions 50+ ECUs (Electronic Control Unit)