Vehicle Payment App Version Synchronization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Users face difficulties in making electronic payments through vehicle head units due to software version mismatches between the vehicle's payment app and the server, leading to frequent service disruptions and user discomfort.

Innovation Solution

An apparatus and server system that actively manages version information, allowing electronic payments by comparing and synchronizing the payment app's version with the server's version, providing notifications for updates, and generating user interfaces for supported payment scenarios, enabling payments even when the vehicle's software is not upgraded.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the server frequently upgrades service versions to improve functionality, then service capability is improved, but compatibility with vehicle payment apps deteriorates

Engineering Contradiction:

Improveservice capabilityVSAvoidcompatibility

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments version information into multiple dimensions: service version, payment app version, and compatibility version. This segmentation allows the system to independently manage server service upgrades while maintaining compatibility tracking for different payment app versions, thus resolving the contradiction between improving service capability and maintaining compatibility.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by pre-establishing a version management mechanism that proactively checks and manages version compatibility before payment operations occur. The system pre-loads compatible payment app versions and their corresponding service version requirements, enabling seamless operation without real-time compatibility conflicts.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If the vehicle payment app is updated frequently to match server versions, then compatibility is improved, but ease of operation deteriorates

Engineering Contradiction:

ImprovecompatibilityVSAvoiduser convenience

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent implements self-service by enabling the system to automatically manage version compatibility without requiring user intervention. The version management module autonomously identifies compatible payment app versions, manages updates in the background, and ensures compatibility without burdening users with update operations, thus maintaining both compatibility and ease of operation.

Inventive Principle:

Principle #25Self-service

3Reliability

If version checking is performed before each payment operation, then compatibility is ensured, but productivity deteriorates

Engineering Contradiction:

Improvecompatibility assuranceVSAvoidpayment speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by performing version compatibility checks in advance and caching the results. The system pre-loads and stores version information and compatibility data before actual payment operations, so that during payment execution, the system can quickly retrieve cached compatibility information without performing time-consuming version checks, thus ensuring both compatibility assurance and payment speed.

Inventive Principle:

Principle #10Preliminary action

4Adaptability or versatility

If the system supports multiple payment app versions simultaneously, then adaptability is improved, but device complexity increases

Engineering Contradiction:

Improveversion supportVSAvoidversion management

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the version management system into distinct functional modules: a version information acquisition module that collects version data, a compatibility determination module that assesses compatibility, and a payment execution module that processes transactions. This modular segmentation allows the system to support multiple payment app versions while keeping each module's complexity manageable and well-defined.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS20230169488A1Apparatus and server for electronic payment, and method for electronic payment using the same

Publication Date: 2023.06.01 HYUNDAI MOTOR CO LTD

AI summary

According to an embodiment of the present disclosure, an electronic payment apparatus may include a head unit for providing a user interface (UI) of a payment app that makes an electronic payment and a controller that activates the payment app based on a fact that first version information of the payment app is identical to first version information of a service version stored in a server, makes a request for a franchisee list, at which it is possible to make a payment with the payment app, to the server based on a fact that the payment app is activated, makes a request for UI information of a target store selected from the franchisee list to the server, generates a UI based on the UI information received from the server, and makes the electronic payment based on the UI displayed on the head unit.