OBD Dongle Segmentation for Vehicle App Versatility

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current vehicular technologies face limitations in supporting data-dominant, latency-sensitive, and computationally-heavy applications due to resource constraints, lack of programmability, unreliable wireless connectivity, and security/privacy concerns, which restrict the development and deployment of customized applications in vehicles.

Innovation Solution

A programmable on-board diagnostics (OBD)-connected dongle, referred to as SmartCore, that provides computational and storage resources within the vehicle, utilizing external devices and cloud servers to host applications, with a middleware framework for update management, data collection, application management, and access control to ensure interoperability, security, and privacy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If external computational resources (Cloud/smartphone) are used to support vehicular applications, then application functionality is improved, but reliability and response time deteriorate due to wireless connectivity limitations

Engineering Contradiction:

Improveapplication functionalityVSAvoidconnectivity reliability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system segments the application execution environment into multiple locations: in-vehicle (dongle and vehicle computing resources), external (smartphone and Cloud). This segmentation allows the system to leverage external resources for enhanced functionality while maintaining the ability to execute critical functions locally, thus resolving the contradiction between versatility and reliability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary architecture that bridges in-vehicle and external computing resources. The dongle acts as a mediator, managing resource allocation and application execution across different environments. This intermediary structure enables seamless integration of external resources while ensuring local control and reliability.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If wireless connectivity is used for data transmission, then application flexibility is improved, but data transmission cost and power consumption increase

Engineering Contradiction:

Improveapplication flexibilityVSAvoidpower consumption

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The system applies local quality by executing data-intensive and computationally-heavy application components locally within the vehicle using the dongle and vehicle computing resources. This local execution eliminates the need for continuous wireless data transmission, thereby reducing power consumption while maintaining application flexibility through the ability to leverage external resources when needed.

Inventive Principle:

Principle #3Local quality

3Adaptability or versatility

If add-on dongles are deployed for vehicular applications, then application deployment capability is improved, but security and privacy protection deteriorate

Engineering Contradiction:

Improveapplication deployment capabilityVSAvoidsecurity vulnerabilities

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent implements self-service security mechanisms where the dongle and vehicle systems autonomously manage security protocols, authentication, and data protection. The system includes built-in security features that automatically enforce access control policies and protect sensitive information without requiring external intervention, thus enhancing security while maintaining deployment flexibility.

Inventive Principle:

Principle #25Self-service

4Speed

If in-vehicle processing is implemented for real-time applications, then response time is improved, but computational resource requirements increase

Engineering Contradiction:

Improveresponse timeVSAvoidcomputational resources

Core Design Contradiction:

SpeedVSPower

Solution Approach 1:

The system merges multiple computing resources within the vehicle ecosystem, including the dongle, vehicle's built-in computing units, and available smartphone resources. This consolidation creates a pooled computational environment that provides sufficient processing power for real-time applications while optimizing resource utilization and reducing the burden on any single component.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS10939262B2System and method for bringing programmability and connectivity into isolated vehicles

Publication Date: 2021.03.02 THE TRUSTEES OF PRINCETON UNIV

AI summary

According to various embodiments, a system for vehicular application development is disclosed. The system includes a programmable on-board diagnostics (OBD)-connected dongle for providing computational and storage resources to a vehicle and hosting one or more applications in the vehicle. The dongle is configured to utilize one or more external devices, cloud servers, and add-on modules to provide additional resources for the applications and enable control of the applications. The dongle is implemented with a middleware that enables intended operations of the dongle.