Mobile App Secure Content Delivery via Third-Party Manager

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Enterprises face challenges in securely delivering content to customers' mobile devices due to legacy processing systems and the perceived difficulty and cost of outsourcing, which often requires manual customer actions and changes to existing applications and devices.

Innovation Solution

A method and system that utilize a third-party content delivery manager to generate and deliver secure content, such as barcode boarding passes, directly to mobile applications using a unique address, allowing seamless integration without requiring customers to enter data or make selections, and enabling offline storage and access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If enterprises retain legacy processing systems for secure content delivery, then security requirements are met, but system complexity and cost increase

Engineering Contradiction:

ImprovesecurityVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a mobile device as an intermediary component between the legacy enterprise system and the customer. The mobile device receives secure content from the enterprise system and presents it to the customer, thereby maintaining security requirements while simplifying the overall system architecture and enabling outsourcing of content delivery functions.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of manufacture

If enterprises outsource content delivery to third-party, then expertise gap is addressed, but customer acceptance decreases due to manual actions required

Engineering Contradiction:

Improveoutsourcing feasibilityVSAvoidcustomer operation

Core Design Contradiction:

Ease of manufactureVSEase of operation

Solution Approach 1:

The mobile device application automatically performs content delivery without requiring manual customer actions. The system retrieves secure content from the enterprise, processes it through the mobile device, and delivers it to the customer seamlessly, eliminating the need for customers to perform manual operations while enabling third-party outsourcing.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The mobile device application is pre-configured with enterprise identifiers and delivery parameters before the actual content delivery occurs. This preliminary setup enables automatic content retrieval and delivery without requiring customer intervention during the transaction, thereby maintaining ease of operation while enabling outsourcing.

Inventive Principle:

Principle #10Preliminary action

3Reliability

If physical identification documents are generated, then secure content delivery is achieved, but environmental waste and processing time increase

Engineering Contradiction:

Improvesecure content deliveryVSAvoidprocessing time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces the mechanical process of generating and delivering physical identification documents with an electronic system. Secure content is delivered digitally through the mobile device application, eliminating the need for physical document generation, printing, and handling, thereby reducing processing time and environmental waste while maintaining security.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentEP2566208B1Third-party content delivery via a unique mobile application address

Publication Date: 2019.10.23 NCR VOYIX CORP

Figure 1
Figure 2
Figure 3

AI summary

A method of delivering secure content is described. The method comprises: obtaining a unique address for a mobile application that is processing on a first device of a user (step 310); receiving a request from a content service to deliver customized secure content to the user on the first device (step 320); acquiring the customized secure content for the user based on the unique address and the request (step 330); and delivering the customized secure content to the mobile application using the unique address (step 340).