Mobile Device Application Activation via Protocol-Based Safety Entity Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile devices face challenges in managing the activation of application programs when multiple safety entities, which store identical applications, are present, requiring a method to efficiently select and activate the appropriate application while ensuring security and user experience.

Innovation Solution

A method and mobile device architecture that utilize a communication manager to identify and activate application programs based on transmission protocols, with a default safety entity selection mechanism and cyclic ordering for fallback options, ensuring seamless activation and user experience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple safety entities store identical application programs, then security and redundancy are improved, but the complexity of managing application activation increases

Engineering Contradiction:
ImprovesecurityVSAvoidapplication activation management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system enables self-service by allowing the mobile device to automatically identify and activate application programs from appropriate safety entities without user intervention. The device autonomously manages the complexity of multiple safety entities through automatic protocol identification and entity selection, while users simply need to install applications once.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent implements multi-functionality by creating a universal application program management system that works across multiple safety entities with different transmission protocols (NFC, Bluetooth, WiFi). The system universally handles application installation, activation, and fallback operations across diverse safety entities, eliminating the need for separate management mechanisms for each protocol or entity.

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

2Ease of operation

If the system automatically selects a default safety entity for application activation, then operation simplicity is improved, but the risk of activation failure increases

Engineering Contradiction:
Improveapplication activationVSAvoidactivation success
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent applies beforehand cushioning by implementing a fallback mechanism that prepares alternative safety entities in advance. When the default safety entity fails to activate an application, the system automatically tries other safety entities in a predetermined sequence, cushioning against activation failure before it occurs and ensuring continuous operation.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

The system implements feedback by monitoring the activation status of application programs and automatically responding to activation failures. When a default safety entity fails to activate an application, the system receives feedback about the failure and automatically adjusts by trying alternative safety entities, creating a closed-loop control system that ensures activation success.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If the system supports multiple transmission protocols (NFC, Bluetooth, WiFi), then adaptability is improved, but the complexity of protocol identification and entity selection increases

Engineering Contradiction:
Improveprotocol supportVSAvoidprotocol identification
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies taking out by extracting and isolating the protocol identification function into a separate, dedicated module within the mobile device. This extracted component specifically handles protocol identification and safety entity selection, separating this complex task from the general application management system and making it easier to manage and maintain.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system implements preliminary action by pre-establishing the correspondence relationships between safety entities and transmission protocols before actual application activation occurs. The mobile device maintains pre-configured information about which safety entities support which protocols, allowing rapid identification and selection without complex real-time analysis when activation is needed.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2980698B1Starting an application on a mobile device
Publication Date: 2019.05.01 CHINA UNIONPAY
  • EP2980698B1 patent drawingFigure 1
  • EP2980698B1 patent drawingFigure 2
  • EP2980698B1 patent drawingFigure 3

AI summary

The invention relates to management of programs on a mobile device, and in particular, to a method for activating application programs on a mobile device, and a mobile device based on this method. The method for activating application programs on a mobile device according to an embodiment of the invention comprises the following steps: receiving an application request from a device which is located outside the mobile device; identifying a transmission protocol associated with the application request; and if there are a plurality of safety entities in the mobile device which support the transmission protocol and store application programs associated with the application request, activating an application program associated with the application request in a default safety entity.