Application Integration via State Sync and Consolidation Layer

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Integrating features of independently developed computer applications, such as an issue tracking system (ITS) and an incident management system (IMS), is computationally expensive and time-consuming, often resulting in inferior functionality due to the need for manual replication of features.

Innovation Solution

A unified frontend system is created, with one application acting as a primary and the other as secondary, allowing seamless interaction and data synchronization between the two systems without replicating functionalities, using a consolidation system to manage communication and data exchange.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If features are manually replicated from one computer application to another, then integration is achieved, but computational cost and time consumption increase significantly

Engineering Contradiction:

Improveintegration capabilityVSAvoidintegration time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent uses event copying and state replication mechanisms where event data structures are copied from the source application to the target application. The consolidation system receives event data, copies relevant fields and parameters, and transmits them to the target application, enabling feature integration without manual replication of entire functionality.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The consolidation system acts as an intermediary between the source and target applications. It receives event data from the source application, processes and standardizes the data format, and forwards it to the target application. This mediator approach eliminates the need for direct integration between applications, reducing both time and computational overhead.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If features are manually replicated from one computer application to another, then integration is achieved, but computational resources are excessively consumed

Engineering Contradiction:

Improveintegration capabilityVSAvoidcomputational overhead

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts only the essential event data fields and parameters needed for integration from the source application. The consolidation system identifies and extracts relevant information (event type, source application identifier, target application identifier, and associated data) while leaving unnecessary computational overhead in the source application. This selective extraction reduces computational resources required for integration.

Inventive Principle:

Principle #2Taking out (Extraction)

3Adaptability or versatility

If two independently developed applications are integrated, then feature compatibility is improved, but technical complexity of integration increases

Engineering Contradiction:

Improvefeature compatibilityVSAvoidintegration complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The consolidation system implements a universal event data structure that can handle multiple event types from different applications. The standardized event format (including event type, source application identifier, target application identifier, and associated data fields) serves as a multi-functional interface that accommodates various integration scenarios, reducing the complexity of integrating independently developed applications.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Adaptability or versatility

If features are developed from scratch in the target application, then functionality is achieved, but development time and quality replication become problematic

Engineering Contradiction:

Improvefeature functionalityVSAvoidfeature quality

Core Design Contradiction:

Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The patent implements preliminary action by pre-defining standardized event data structures and formats in the consolidation system. Event templates and data schemas are established beforehand, ensuring that when events are transmitted from the source to the target application, they maintain consistent quality and structure. This preliminary standardization eliminates the need to re-develop features from scratch while preserving quality.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12547479B2Systems and methods for integrating computer applications

Publication Date: 2026.02.10 ATLASSIAN PTY LTD

AI summary

Computer-implemented methods and systems for integrating computer applications are disclosed. One method includes querying a primary computer application for current state of a newly created object; receiving the current state of the object, and generating object data for a secondary computer application based on the current state of the object. The method further includes communicating an object creation request to a secondary computer application, the object creation request including the generated object data, receiving a secondary computer application object identifier from the secondary computer application upon creation of the object at the secondary computer application, and communicating the secondary computer application object identifier to the primary computer application for storing in a record of the object created at the primary computer application.