Centralized Server for Vehicle Application Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems lack a centralized mechanism to safely and intelligently manage and control the extension of mobile phone applications onto a vehicle's head unit, particularly in terms of accessing and prioritizing resources based on vehicle conditions and user authentication.

Innovation Solution

A network device maps application operation modes to vehicle conditions and compares application identifiers to determine which vehicle interface resources to grant access to, using client and server software to authenticate users and applications, and manage resource access dynamically based on vehicle status and priority rankings.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Illumination intensity

If mobile phone applications are extended to the vehicle head unit, then user interface quality is improved, but system security and control complexity worsen

Engineering Contradiction:
Improveuser interface qualityVSAvoidsystem security
Core Design Contradiction:
Illumination intensityVSReliability

Solution Approach 1:

A centralized server acts as an intermediary between mobile applications and the vehicle head unit, authenticating applications and granting selective access to interface resources. The server receives authentication requests from applications, verifies credentials, and returns authorization decisions, thereby securing the system while enabling controlled access to high-quality vehicle interface resources.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If applications are granted access to vehicle interface resources, then application functionality is improved, but resource management complexity worsens

Engineering Contradiction:
Improveapplication functionalityVSAvoidresource management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The complex resource management logic is extracted from the vehicle head unit and relocated to a centralized server. The server maintains a mapping of application operation modes to vehicle conditions and makes centralized decisions about resource allocation, simplifying the head unit's role to executing authorization decisions while enabling sophisticated application functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system dynamically changes resource access parameters based on vehicle conditions and application requirements. The server compares application identifiers against stored mappings and adjusts granted access levels according to current vehicle state, enabling flexible functionality while centralizing management complexity.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If centralized server control is implemented, then application access control is improved, but network dependency worsens

Engineering Contradiction:
Improveapplication access controlVSAvoidnetwork dependency
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The centralized server provides multiple functions including authentication, authorization, and resource allocation through a single network-based platform. This universal approach simplifies access control operations while consolidating network dependencies into a single manageable system rather than distributing complexity across multiple components.

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

Data Source

PatentEP2488942B1Centralized management of motor vehicle software applications and services
Publication Date: 2020.04.22 AIRBIQUITY INC
  • EP2488942B1 patent drawingFigure 1
  • EP2488942B1 patent drawingFigure 2A
  • EP2488942B1 patent drawingFigure 2B

AI summary

In one example, a network device (22) stores a mapping (15) of application operation modes to vehicle conditions including at least a first condition of the vehicle powered but not moving and a second condition of the vehicle moving. The network device (22) receives a wirelessly transmitted request for a particular application (40) to utilize an interface (21) powered by the vehicle. The network device (22) compares an application number from the request to the mapping (15) and identifies a portion of the vehicle interface (21) according to the comparison. The network device (22) signals control software (30B) on the vehicle to permit the particular application (40) to access only the identified portion of the vehicle interface.