• Implementing the international automotive safety standard ISO 26262 is now a must-have for automotive E&E development. However, due to its vast array of safety requirements, there is a possibility that responses will vary among companies. Because it is a safety domain, the industry must achieve a certain level of depth and effort for this response. Therefore, we will discuss interpretation and response policies in this non-competitive safety domain and provide technical perspectives that can be shared by the industry.
• ISO 21448 (SOTIF), a safety standard for autonomous driving technology, has been published, but its description is much more abstract than ISO 26262, making it difficult to understand what each company should implement and to what extent. Therefore, we will explore appropriate interpretations and response directions that take international trends into account.
• Furthermore, work on the next versions of ISO 26262 and ISO 21448 (SOTIF) has begun, and we will promote responses that will avoid difficulties at the time of publication, including anticipating changes.
• With the recent development of autonomous driving technology, several safety standards have been issued. Following SOTIF, we will also consider standards essential for safety demonstration, such as ISO/PAS 8800 and UL 4600, and will continue our analysis.

• Support the formation of standard interpretations and the promotion of field activities by adding and revising the guide created in the first edition of ISO 26262, focusing on changes in the software, hardware, and communications domains of ISO 26262 2nd Edition.
• With the publication of ISO 26262 3rd Edition scheduled for next year, and various changes being discussed, we will proactively discuss responses based on the DIS version.
• Support the formation of a common interpretation and implementation of SOTIF ISO 21448.
• Analysis of ANSI/UL 4600 and correlation research between ISO 26262 and SOTIF.

• ISO 26262:2018 Part 9: Developing concepts and procedures for dependent failure analysis
• ISO 26262:2018 Part 5: Clarifying concepts for hardware element evaluation and handling of SEOOC components
• Applying formal verification techniques to software functional safety activities and examining use cases
• Identifying patterns involving gateways and clarifying the constraints that exist for communication protection in each pattern
• Creating case studies using SOTIF templates (Clause 5-11)
• Creating a guide for deepening understanding of SOTIF and investigating methods for problem-solving
• Creating case studies using SOTIF templates
• Analyzing ANSI/UL 4600: Research papers correlating ISO 26262 and SOTIF

• SOTIF Activity Template/Explanatory Manual Updated
• Functional Safety Standards Usage Guide Ver. 3.1 Published
• Technical Document on the Application of Formal Verification Techniques to Functional Safety Verification Ver. 1.0
• Technical Documents: 1 Technical Document (AVPS Functional Safety Analysis) Ver. 1.0
• Research Results of the Paper "Methods for Effective and Efficient Safety Proof of Autonomous Vehicles"

To work on standardization activities on car electronic technology, and or promotion and dissemination of new concepts and technologies originating from Japan, by making proposals from JASPAR to AUTOSAR, and avoid the conflicts between the two organizations.

• For the next release of AUTOSAR Classic & Adaptive Platforms, conduct scouting of proposal items from JASPAR and participating companies, and support new concept creation and proposal activities.
• Participate in the AUTOSAR Open Conference and other meetings to grasp the latest trends, and plan or support meetings with AUTOSAR as necessary.

• Conduct research on new concepts for R25‑11 and beyond, and share the findings with the relevant JASPAR working groups.
• Support the review of new proposals from the OTA WG and the Next‑Generation High‑Speed LAN WG.
• Hold a collaborative meeting with the AUTOSAR Steering Committee (June 2025).
• Deliver a collaborative presentation with AUTOSAR at the AUTOSAR Open Conference (June 2025).
• Host the AUTOSAR JASPAR Japan Day (July 2025).
• Introduce AUTOSAR‑related technologies such as automotive APIs to the API Technology WG (Feb 2025).
• Online meeting between JASPAR API WG – AUTOSAR was organized (July 2025).
• AUTOSAR presented Automotive API performance analysis result (API demonstration at AOC 2025 @ Bruges) to JASPAR API WG.
  
• JASPAR article (JASPAR’s long journey with AUTOSAR) is published on AUTOSR China Hub WeChat (October 2025).
• https://mp.weixin.qq.com/s/eczTgEtG88N74t2vUHzRvQ

• Monitor AUTOSAR developments (such as new concepts for R26‑11 and beyond) and share/propose them to the relevant JASPAR WGs.
• Support JASPAR’s proposals for the next AUTOSAR releases (R26‑11 and later).
• Host the AUTOSAR JASPAR Japan Day.

To collaborate with related organizations, and to research and standardization of connectivity in SDV as activity of Ext-linkage/Outreach.

• Organize challenges in the area of connectivity based on SDV-related use cases and related technological trends, formulate guidelines, and work with relevant organizations to develop standard specifications.
• Identify issues related to the diffusion of digital keys and work together with related organizations to resolve them.
• Preparation of Card-type Digital key (DK-Card) specification and validation of implementation challenges with PoC and proposal to related organizations

• A Practical Guide to Connectivity Utilization in SDV Supporting Vehicle Services Ver.1.1
• Implementation Guidelines for Card Type Digital Key Ver.1.1
• Card Type Digital key PoC development
• Visited MWC2026 in order to research on SDV related technical trend
• Attended GSMA Digital Nation Summit Open Gateway roundtable and discuss network API
• Participate in CCC Digital Key activities and introduce JASPAR‘s efforts (Card Type Digital key)
• CCC Plugfest event hosting (2026/3)
• Cooperative activities with various standardization organizations (AECC, GSMA, Bluetooth SIG, Wi-Fi Alliance, CCC, NFC Forum, etc.)
• Webiner for A Practical Guide to Connectivity Utilization in SDV Supporting Vehicle Services Ver.1.1

• Connectivity development Guidelines in SDV(2026/09)
• Connectivity for SDV PoC development(2027/3)
• Implementation Guidelines for Card Type Digital Key(2026/10)

To identify common elemental technologies required for LAN architectures in the SDV era, to specify their functional and performance requirements, and to contribute to international standardization. In addition, to define functional and performance requirements for the electrical and optical physical layers, as well as for SDN, TSN, and RCP (Remote Control Protocol), with a view toward control system applications.

• (Activity No.1) Study of future LAN architectures, network security, and E/E architecture.
• (Activity No.2) Definition of the SDN architecture and specification of functional and performance requirements, and incorporation into OPEN specifications.
• (Activity No.3) Definition of Automotive TSN profiles and its incorporation into IEEE 802.1 standards.
• (Activity No.4) Definition of schema-based specifications for RCP and incorporation into OPEN specifications.
• (Activity No.5) Definition of the JASPAR high-speed communication strategy and its incorporation into IEEE 802.3 standards.
• (Activity No.6) Definition of optical communication design guidelines and incorporation into OPEN specifications.
• (Activity No.7) Definition of high-speed electrical communication design guidelines and incorporation into OPEN specifications.
• (Activity No.8) Definition of 10 Mb/s electrical communication design guidelines and incorporation into OPEN specifications.

• Architecture Definition of Automotive SDN Ver.2.0
• TSN Profiles for In-Vehicle Ethernet Ver.4.0
• Multi-Giga Optical Wiring Requirements Definition Ver.1.0
• TSN research Report Ver.2.0
• JASPAR In-Vehicle Ethernet Network Research Report Ver.5.0
• Automotive Requirements for 10BASE‑T1S Report Ver.1.0
• Technical Discussion with AUTOSAR SC(May, 2025)
• Presentation of the WG activities at Nikkei Ethernet seminar(July. 2025) and Automotive Ethernet Congress (March, 2026)
• Contribution to IEEE Plenary Session(July, Nov. 2025 and March, 2026) and OPEN Alliance (Oct. 2025 and March, 2026)
• Contribution to Monthly Optronics Magazine (Feb. 2026)

• Architecture Definition of Automotive SDN Ver.3.0
• TSN Profiles for In-Vehicle Ethernet Ver.5.0
• Schema-Based RCP Application Profile (Tentative) Ver.1.0
• Optical Ethernet Design Guidelines (Tentative) Ver.1.0
• JASPAR Multi-Giga Electric Recommended Routing Design Standard Ver.2.0
• 10BASE‑T1S Wiring and Routing Guidelines Ver.1.0
• SDV LAN Architecture Definition Document (Tentative) Ver.1.0
• Physical Layer Strategy Report(Tentative) Ver.1.0
• JASPAR In-Vehicle Ethernet Network Research Report Ver.6.0, Ver.7.0
• Automotive Requirements for 10BASE‑T1S Report Ver.2.0, Ver.3.0

To promote standardization to provide customers with safe and security services, and grow the potential for new connectivity values.

• Investigating and studying of candidate standardization items in the cooperation realm
• Cooperating with JAMA, JSAE and governments
• Harmonizing with European and American industrial organizations

• Defined Information security specifications and evaluation rules
• Reflected JASPAR standard specifications in AUTOSAR R20-11

• Standardization roadmap for Information Security (2027/03)

To define and validate technical requirements for cybersecurity based on automotive use cases.

• Creating next-generation cybersecurity guide and reference case studies for BEV and SDV.
• Creating implementation examples when complying with A‑SPICE for CS based on the ISO/SAE 21434 process.

• Defined requirements of cybersecurity countermeasure technology for vehicle equipment.
• Validated cybersecurity development process for automotive system and vehicle equipment.

• Next-generation cybersecurity guide for BEV and SDV Draft version
• Gap Analysis Document between ISO/SAE 21434 and Automotive SPICE for CS

To identify challenges and to define requirements for ECU software updating using OTA techniques

• Investigation of OTA related topics
• Requirement analysis of System and Process as End-to-End OTA service
• Cooperation with JAMA, JSAE and AUTOSAR

• Publication of process/product requirements considering with UN-R156
• Software management requirements for SDV era
• Implemention exmaple to apply AUTOSAR/SOFD for OTA
• Cooperation with JAMA, JSAE, J-AUTO-ISAC and AUTOSAR

• Guide to the Software Management Framework
• Assessment Report on the Application of SOVD OTA
• OTA Safety and Security Guide for the Promotion of OTA Adoption

To improve the efficiency of application development and revitalize the market, a standard API across OEMs will be introduced from Japan.

"API design and implementation" and related "use case consideration", "PoC development" and "process definition"

Development of an API enabling comprehensive access to vehicle signals based on COVESA VSS (Vehicle Signal Specification), along with the establishment of a foundational environment to promote its utilization. In addition, preparation of tutorials and documentation to provide an environment that users can “immediately start using.”

1. API Implementation / Activity Infrastructure Development
   • Development of a vehicle API based on the COVESA VSS standard vehicle data model
   • Establishment of the activity foundation, including architecture design, API design guidelines, and development processes
2. API Validation (Proof of Concept)
   • Use case–driven studies and validation through the development of real applications
   • Identification of issues and improvement areas related to the API and platform, and enhancements to increase practical usability
3. Preparation for Open-Source Release (Initial release planned for April 2026)
   • Development of OSS processes, formulation of community strategies, and preparation for collaboration with external organizations
   • Creation of tutorials and sample programs to promote adoption

Following the initial release in April 2026, we will promote development activities with a strategic focus on the following scopes to facilitate the adoption of the product and its integration into the development lifecycle.

1. Expansion and Refinement of API & Infrastructure
   • We will conduct ongoing proof-of-concept (PoC) testing, primarily with OEMs and Tier 1 suppliers. Based on the feedback gathered, we will implement functional enhancements and quality improvements, with updates scheduled every six months.
   • Target Deliverables: * Signal API, Eclipse Kura (Data Broker)
2. Enhancement of the Development Environment (SDK for Application)
   • We will provide Application development support environments utilizing the Yoriito API.
   • Target Deliverables:Vehicle API and dependent library groups , Emulator images, SDK specifications.