Vehicle Software Access Control Using Local SBOM Updates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing software management systems struggle to dynamically manage software vulnerabilities and user contracts in vehicles, leading to discrepancies and potential security risks due to centralized management and communication delays.

Innovation Solution

Implementing an information processing method that manages software by storing a Software Bill of Materials (SBOM) locally in vehicles, allowing real-time updates and access control based on user contracts, using authentication units to verify user permissions, and maintaining separate lists for operable and inoperable software.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If centralized software management is used, then software updates and vulnerability assessments can be controlled, but communication delays and discrepancies occur between the management server and vehicle devices

Engineering Contradiction:

Improvesoftware management accuracyVSAvoidcommunication delay

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the centralized software management system into distributed components: the management server handles policy decisions while local devices maintain independent software information lists and perform autonomous vulnerability assessments. This segmentation eliminates communication delays for time-critical operations while the server provides centralized coordination for updates and policy enforcement.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by having local devices continuously update their software information lists and perform vulnerability assessments before the management server can respond. The device proactively detects software additions, determines contract status, and updates operational status locally, eliminating waiting time for server communication while maintaining centralized control for actual software distribution.

Inventive Principle:

Principle #10Preliminary action

2Measurement precision

If software information is updated in real-time locally, then accurate vulnerability assessment is achieved, but system complexity increases

Engineering Contradiction:

Improvevulnerability detection accuracyVSAvoidlocal software management complexity

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The patent applies self-service by enabling local devices to autonomously manage their own software information lists without requiring complex centralized coordination for each update. The device independently detects software additions, queries contract status from stored information, determines operational status, and updates its local vulnerability assessment, significantly reducing system complexity while maintaining real-time accuracy.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent implements feedback mechanisms where the local device continuously monitors its software inventory and compares it against stored contract information, receiving feedback from the management server only when actual software updates are deployed. This feedback loop maintains accurate vulnerability detection without requiring complex continuous communication, simplifying the system while ensuring precision.

Inventive Principle:

Principle #23Feedback

3Adaptability or versatility

If all software is made operable, then user functionality is maximized, but security risks increase without proper access control

Engineering Contradiction:

Improvesoftware functionalityVSAvoidsecurity vulnerability

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies dynamics by making the software operational status adaptive rather than static. The system dynamically determines whether software should be operable based on real-time conditions: contract status verification, vulnerability assessment results, and security policy requirements. This dynamic approach allows maximum functionality when safe while automatically restricting access when vulnerabilities or contract violations are detected, balancing adaptability and security.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent implements preliminary anti-action by performing vulnerability assessments and contract verification before allowing software to become operable. The system proactively identifies security risks and contract violations, preventing potentially harmful software from executing. This preliminary security check blocks vulnerable software in advance while allowing safe software to operate, maximizing functionality within security constraints.

Inventive Principle:

Principle #9Preliminary anti-action

Data Source

PatentUS20260057077A1Information processing method, information processing device, and non-transitory computer-readable recording medium

Publication Date: 2026.02.26 PANASONIC INTELLECTUAL PROPERTY MANAGEMENT CO LTD

AI summary

An information processing method executed using a computer in a vehicle that switches whether or not each of equipped functions is to be made operable, depending on whether or not a user of the vehicle has a contract for the function. The information processing method includes: detecting a new addition of software for operating one or more functions; determining whether or not the user has a contract for the function operated by the software, the new addition of which has been detected; acquiring software information corresponding to the software for which it is determined that the user has a contract; and updating a software information list of functions operable in the vehicle by adding the acquired software information.