Service Version Selection for Secure Element Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In mobile commerce environments, determining the appropriate version of a service to install on a mobile device or secure element is challenging due to compatibility issues between service versions and secure elements, leading to inefficient or incorrect functionality.

Innovation Solution

A system and method that uses a rules engine to determine the preferred service version for a secure element profile, comparing it with the existing version loaded on the element, and transmitting commands to either install the existing or preferred version, ensuring compatibility and resource efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple versions of a service are released to incorporate updates, fix bugs, or apply security patches, then service functionality and security are improved, but compatibility issues with different secure elements arise

Engineering Contradiction:
Improveservice functionalityVSAvoidcompatibility with secure elements
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system dynamically determines which service version to install by evaluating compatibility between the service version and the specific secure element type. The rules engine adapts the installation decision based on real-time assessment of secure element capabilities, service version requirements, and existing service versions, rather than using a static version selection approach.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of service version selection based on the secure element profile. By evaluating compatibility parameters between service versions and secure element types, the system selects the appropriate service version that optimizes both functionality and compatibility for each specific secure element.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If the latest service version is installed on all mobile devices, then service updates and security patches are applied, but resource usage and storage requirements increase

Engineering Contradiction:
Improvesecurity patchesVSAvoidstorage on secure element
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

Instead of uniformly installing the latest service version on all devices, the system applies local quality by selecting service versions tailored to each secure element's specific capabilities and constraints. This ensures each secure element receives the most appropriate version that meets security requirements while optimizing storage usage for that particular device.

Inventive Principle:
Principle #3Local quality

3Measurement precision

If service version compatibility is manually verified for each secure element, then compatibility accuracy is improved, but installation time and complexity increase

Engineering Contradiction:
Improvecompatibility determinationVSAvoidinstallation time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs self-service by automatically evaluating service version compatibility with secure elements through a rules engine. The compatibility assessment is conducted autonomously without manual intervention, using predefined rules that evaluate secure element profiles, service version requirements, and existing service versions to determine the optimal installation decision.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses feedback from the rules engine evaluation process to automatically determine compatibility. The rules engine provides feedback on whether a service version is compatible with a secure element based on evaluated parameters, enabling automated installation decisions without manual verification while maintaining high compatibility accuracy.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9286049B2Systems, methods, and computer program products for managing service installation
Publication Date: 2016.03.15 GOOGLE LLC
  • US9286049B2 patent drawing
  • US9286049B2 patent drawing
  • US9286049B2 patent drawing

AI summary

Systems, methods, and computer program products are provided for managing installation of services on a secure element having a secure element profile. A request to install a service on the secure element is received. There is a determination of a preferred version of the service corresponding to the secure element profile of the secure element. There is also a determination of an existing version of the service loaded on the secure element. Using a rules engine, there is a determination of whether to install on the secure element either the existing version of the service or the preferred version of the service. A command is transmitted to either (a) install the existing version of the service or (b) delete the existing version of the service and load and install the preferred version of the service, based on the determination using the rules engine.