Distributed Application Lifecycle Management System

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current solutions for managing distributed applications across multiple devices are complex and often require end-users to manually configure and install necessary applications, leading to sub-optimal user experiences due to missing components and compatibility issues, especially in devices without user interfaces or under NSP management.

Innovation Solution

A distributed application life-cycle management system that receives information about installed applications, determines missing or recommended applications and devices, and informs users, automatically installing required components while providing direct links for one-click purchase, leveraging existing protocols like TR-069 and user interface-centered application stores.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual configuration and installation of distributed applications is implemented, then users have control over installation process, but user experience deteriorates due to complexity and missing components

Engineering Contradiction:

Improveuser experienceVSAvoidconfiguration complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The system performs self-service by automatically detecting installed applications, determining dependencies, and installing required components without user intervention. The backend system autonomously manages the distributed application lifecycle, eliminating manual configuration while maintaining system control.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

A backend system acts as an intermediary between users and distributed applications. This intermediary automatically manages application dependencies, coordinates installations across multiple devices, and handles compatibility checks, thereby simplifying user interaction while managing complexity centrally.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If automatic installation system is implemented, then ease of operation improves, but system complexity increases

Engineering Contradiction:

Improveinstallation automationVSAvoidbackend system complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The backend system serves as an intermediary that centralizes complex automation logic. It manages dependency resolution, coordinates installations across devices, and handles protocol communications (TR-069, OMA-DM), thereby providing automatic installation functionality while containing complexity within the backend rather than distributed across multiple devices.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The backend system performs multiple functions including dependency management, installation coordination, protocol handling, and compatibility verification. This multi-functional approach consolidates complexity into a single system that serves the entire distributed application ecosystem.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If distributed application management is implemented across multiple devices, then application functionality improves, but compatibility issues increase

Engineering Contradiction:

Improvedistributed application functionalityVSAvoidcompatibility reliability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements feedback mechanisms where the backend continuously monitors installed applications, detects dependency issues, and adjusts installation plans accordingly. This feedback loop ensures compatibility by verifying that each application component works correctly with its dependencies before and during the distribution process.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The backend performs preliminary actions by pre-analyzing application dependencies, determining required components, and planning installation sequences before actual deployment. This preliminary preparation ensures compatibility by identifying and resolving potential conflicts before they manifest in the distributed system.

Inventive Principle:

Principle #10Preliminary action

4Adaptability or versatility

If devices without user interfaces are managed, then device versatility improves, but user awareness deteriorates

Engineering Contradiction:

Improvedevice coverageVSAvoiduser awareness

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The backend system acts as an intermediary that bridges the information gap for devices without user interfaces. It manages applications on headless devices (broadband gateways, set-top boxes) and communicates installation status and requirements through interfaces that users can access (application stores, notification systems), thereby maintaining user awareness despite device limitations.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10229207B2Solution for distributed application life-cycle management

Publication Date: 2019.03.12 THOMSON LICENSING SA

AI summary

A solution for managing applications in a network is proposed. A distributed application management system receives information about a first application installed on a first device in the network and determines whether a second application is required or recommended for the first device or for a second device in the network or whether a further device is required or recommended for the network based on the received information. A device management system then informs a user about a required or recommended second application or a required or recommended further device.