Vehicle Service Proxy for Variant-Aware Feature Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vehicle service delivery systems face challenges in scalability and reliability due to varying vehicle variants, and developing applications for each variant requires significant resources, while existing communication architectures struggle with priority management and synchronization across different vehicle configurations.

Innovation Solution

A vehicle variant-aware service mesh architecture that utilizes a proxy component to manage network and security functionalities, incorporating priority management, configuration, and calibration components to ensure secure and scalable communication across different vehicle variants, using a publish-subscribe model with Ethernet protocol.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If service applications are developed for each vehicle variant, then service coverage and reliability are improved, but development resources and system complexity increase significantly

Engineering Contradiction:
Improveservice delivery reliabilityVSAvoidapplication development complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal service proxy architecture that can handle multiple vehicle variants through a single application. The proxy component retrieves configuration data specific to each vehicle variant and routes service requests appropriately, allowing one application to serve multiple vehicle types without requiring separate applications for each variant.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The service proxy acts as an intermediary between the service application and the vehicle network. It receives service requests, determines the target vehicle variant, retrieves appropriate configuration data, and routes requests to the correct ECUs. This mediator approach simplifies the application structure while maintaining reliable service delivery across variants.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If configuration data is retrieved for each vehicle variant, then service accuracy is improved, but network communication overhead and response time increase

Engineering Contradiction:
Improvefeature identification accuracyVSAvoidconfiguration retrieval time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary retrieval of configuration data when the service application is first instantiated or when vehicle variant information becomes available. This pre-fetching of configuration data reduces the need for repeated retrievals during service operations, thereby reducing network overhead and response time for subsequent service requests.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The configuration data is stored locally in the vehicle's memory after being retrieved from the remote server. Once retrieved, the data is cached and reused for multiple service requests without needing repeated network communications, thus maintaining high identification accuracy while minimizing network overhead and response time.

Inventive Principle:
Principle #3Local quality

3Reliability

If service requests are monitored and validated, then system security is improved, but processing overhead and system complexity increase

Engineering Contradiction:
Improvesystem securityVSAvoidrequest validation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The service proxy serves as a security intermediary that validates all incoming service requests before routing them to ECUs. It checks whether the requested feature exists in the target vehicle variant by comparing against configuration data, and blocks invalid requests. This centralized validation approach improves security without requiring complex validation logic in each service application or ECU.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Speed

If Ethernet protocol is used for vehicle network communication, then communication speed and bandwidth are improved, but network management complexity and security requirements increase

Engineering Contradiction:
Improvenetwork communication speedVSAvoidnetwork management complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The service proxy acts as a network intermediary that manages Ethernet communication between service applications and ECUs. It handles protocol-specific concerns such as message routing, error handling, and security validation, thereby simplifying network management despite the complexity of Ethernet protocol requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts network management functions from the service applications and concentrates them in the service proxy component. This separation of concerns allows service applications to focus on business logic while the proxy handles Ethernet protocol management, security validation, and configuration data handling, thereby reducing overall system complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12470426B2Vehicle variant-aware services
Publication Date: 2025.11.11 FORD GLOBAL TECH LLC
  • US12470426B2 patent drawing
  • US12470426B2 patent drawing
  • US12470426B2 patent drawing

AI summary

A system includes a processor to execute instructions to, upon instantiation of a control application in a vehicle, retrieve (a) configuration data specifying one or more features available to the control application in the vehicle, and (b) settings data specifying one or more current settings for the control application; monitor a vehicle network for request from a remote device for a selected feature of the control application in the vehicle; determine from the configuration data whether the selected feature is included in the one or more features available to the control application in the vehicle; and, if the selected feature is included, actuate a component in the vehicle based on the selected feature and the settings data.