Partial Personalization for Mobile App Updates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing mobile payment systems face inefficiencies and increased network traffic during application updates, requiring full re-personalization of sensitive account information, which is inconvenient and resource-intensive, especially during simultaneous updates across large user bases.

Innovation Solution

A partial personalization process that stores personalization profiles for multiple versions of mobile applications, allowing for the generation of tailored scripts containing only the necessary updates, reducing the information and processing required for each update, and enabling updates without user authentication for previously provisioned devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full re-personalization is performed during application updates, then security and authentication are ensured, but network traffic increases and throughput decreases during high-traffic update periods

Engineering Contradiction:

Improveauthentication securityVSAvoidupdate throughput

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The personalization data is segmented into two parts: (1) static personalization information that remains unchanged during updates, and (2) dynamic personalization information that needs updating. Only the dynamic portion is transmitted during updates, while the static portion is reused from the previous provisioning, thereby reducing network traffic while maintaining security.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The complete personalization profile is provisioned in advance during the initial authentication process. When an update occurs, the system performs a differential analysis to identify only the changes needed, rather than re-transmitting the entire personalization data set. This preliminary provisioning enables efficient incremental updates.

Inventive Principle:

Principle #10Preliminary action

2Manufacturing precision

If full re-personalization is performed during application updates, then complete personalization information is ensured, but processing time and computational resources increase

Engineering Contradiction:

Improvepersonalization completenessVSAvoidupdate processing time

Core Design Contradiction:

Manufacturing precisionVSLoss of time

Solution Approach 1:

The system extracts only the specific personalization elements that have changed between application versions. By identifying and isolating the differential data elements, the system avoids processing and transmitting unchanged personalization information, thereby reducing processing time while ensuring that all necessary updates are applied.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of performing complete re-personalization, the system applies partial personalization updates containing only the necessary changes. This partial action approach is sufficient to maintain personalization completeness while significantly reducing computational overhead and processing time.

Inventive Principle:

Principle #16Partial or excessive action

3Loss of information

If full personalization profiles are transmitted during updates, then all personalization information is provided, but network traffic and data transmission volume increase

Engineering Contradiction:

Improvepersonalization information completenessVSAvoidnetwork traffic volume

Core Design Contradiction:

Loss of informationVSQuantity of substance

Solution Approach 1:

The personalization update transmission is optimized by applying local quality differentiation: unchanged personalization elements are marked for local reuse on the device, while only the changed elements are transmitted remotely. This selective transmission approach ensures information completeness while minimizing network traffic volume.

Inventive Principle:

Principle #3Local quality

4Reliability

If authentication is required for every update, then security is maintained, but user convenience and update speed decrease

Engineering Contradiction:

Improvesecurity authenticationVSAvoidupdate convenience

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

Authentication is performed in advance during the initial personalization provisioning process. The authenticated session and authorization tokens are stored securely on the device. Subsequent update operations utilize these pre-established credentials, eliminating the need for repeated authentication while maintaining security through the use of secure token-based verification.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11720337B2Methods and systems for partial personalization during application update

Publication Date: 2023.08.08 VISA INTERNATIONAL SERVICE ASSOCIATION

AI summary

Embodiments of the present invention are directed at methods and systems for providing a partial personalization process. For example, personalization profiles associated with multiple versions of the application may be stored at a provisioning system and the provisioning system may determine the appropriate partial provisioning information to update the application for each migration notification. Partial personalization information that is to be updated for the updated version of the application may be generated and installed to enable new functionality and/or update the information contained within an updated application without requiring re-personalization of all personalized information.