Transformation Chain Application Splitting for Dynamic Adaptation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing computing systems lack the ability to dynamically and efficiently adapt and customize applications in response to environmental events, such as user interactions, leading to delayed incorporation of user feedback and limited customization options.

Innovation Solution

The system employs transformation chains, which are interconnected sets of nodes that can be dynamically combined and split, allowing for the creation of customized applications by instantiating and operating portion transformation chain classes in response to environmental events, enabling sharing and delegation of application components without losing control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If applications are predetermined and drafted in advance, then application stability and structure are maintained, but adaptability to user feedback and environmental events deteriorates

Engineering Contradiction:
Improveadaptability to user feedbackVSAvoidapplication structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The application is divided into multiple transformation chains that can be independently created, modified, and executed. Each transformation chain represents a discrete functional unit that can be dynamically assembled based on environmental events and user feedback, allowing the application to adapt without complete restructuring.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The application structure transitions from static predetermined functionality to dynamic adaptability. Transformation chains can be created, modified, and executed in real-time based on environmental events, user interactions, and feedback, enabling the application to evolve its functionality during operation rather than being fixed at design time.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If applications are customized for particular users, then user-specific functionality is improved, but system complexity and control management worsen

Engineering Contradiction:
Improvecustomization capabilityVSAvoidcontrol management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Transformation chains are designed as universal, reusable components that can be instantiated multiple times with different configurations. The same transformation chain template can serve multiple users and purposes by accepting parameterized inputs and outputs, eliminating the need to create entirely separate custom applications for each user while maintaining customization capability.

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

3Adaptability or versatility

If user feedback is incorporated into applications, then application functionality is improved, but time delay and response speed worsen

Engineering Contradiction:
Improvefunctionality improvementVSAvoidfeedback incorporation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

Transformation chains are pre-configured with templates and structures that define their functionality in advance. When user feedback or environmental events trigger modifications, the system can rapidly instantiate new instances or adjust parameters of these pre-prepared transformation chains rather than creating functionality from scratch, significantly reducing the time required to incorporate feedback.

Inventive Principle:
Principle #10Preliminary action

4Ease of operation

If applications are shared with other entities, then collaboration and accessibility are improved, but control and security management worsen

Engineering Contradiction:
Improvesharing capabilityVSAvoidcontrol security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

Different transformation chains within an application can have different sharing permissions and access controls assigned to them. The system allows fine-grained control where specific transformation chains can be shared with certain entities while maintaining restricted access to others, enabling collaboration on specific functionalities while preserving security and control over sensitive operations.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10198252B2Transformation chain application splitting
Publication Date: 2019.02.05 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10198252B2 patent drawing
  • US10198252B2 patent drawing
  • US10198252B2 patent drawing

AI summary

The splitting of an application in response to detected environmental events (such as user input). Such splitting may be performed for purposes of sharing the application. The application is a transformation chain instance. From the detected environmental event(s), it is determined that a portion transformation chain class is to be created from the larger transformation chain class of the application. In response, the portion transformation chain class is created, instantiated and operated. A sharing mechanism may be used to allow the split portion of the application to be shared with other entities without losing control.