Unified Data Composition Client for Conflict Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing shared data across disparate sources is a daunting and time-consuming task due to the need to open and use multiple applications, which often leads to data inconsistencies and conflicts.

Innovation Solution

A computing system with a client that can access and manage data from multiple independent sources to create a data composition, identifying shared and unshared data portions, and propagate changes while resolving conflicts, using APIs and schemas to handle data interactions and relationships.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple applications are used to access shared data from disparate sources, then data accessibility is improved, but data consistency and ease of operation deteriorate due to manual management overhead

Engineering Contradiction:
Improvedata accessibilityVSAvoidmanual management overhead
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent merges multiple data sources and their management interfaces into a single unified application. The system combines data from disparate sources (e.g., Outlook contacts, Excel spreadsheets, database records) into one integrated user interface, eliminating the need to switch between multiple applications while maintaining data accessibility from all sources.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal data management application that performs multiple functions: accessing data from various sources, displaying unified views, detecting conflicts, and managing updates. This single application replaces multiple specialized applications, providing versatility in data access while simplifying operation through a consistent interface.

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

2Adaptability or versatility

If multiple applications are used to manage shared data, then data accessibility is improved, but time consumption increases due to switching between applications

Engineering Contradiction:
Improvedata accessibilityVSAvoidtime consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

By combining multiple data access functions into one application, the system eliminates time lost to switching between applications. Users can access and manage data from all sources within a single interface, significantly reducing the time required for data management tasks.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary actions by pre-loading and caching data from multiple sources when available, and by establishing data relationships in advance. This reduces the time required to retrieve and reconcile data during actual use, as the framework is already in place for rapid data access and conflict detection.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If manual data management is used across multiple applications, then flexibility in accessing different data formats is improved, but data integrity deteriorates due to conflicts and inconsistencies

Engineering Contradiction:
Improveflexibility in accessing different data formatsVSAvoiddata integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements feedback mechanisms that automatically detect conflicts and inconsistencies when data from multiple sources is accessed or updated. The unified application monitors data changes across sources, identifies conflicts (such as duplicate contacts or conflicting information), and provides feedback to users for resolution, thereby maintaining data integrity while preserving flexibility in data format access.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary layer (the unified application framework) between the user and multiple data sources. This intermediary standardizes data access, transforms various data formats into a unified representation, and mediates conflicts before data is presented to or stored from sources, ensuring integrity without sacrificing format flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of operation

If a unified data management system is implemented, then ease of operation and data consistency are improved, but device complexity increases

Engineering Contradiction:
Improvedata management simplicityVSAvoidsystem architecture complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the complex unified data management system into distinct functional modules: data access modules for each source, a conflict detection module, a data reconciliation module, and a user interface module. This segmentation allows the complex functionality to be organized into manageable components, making the system easier to implement, maintain, and understand while providing a simple unified interface to users.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8738584B2Context-aware management of shared composite data
Publication Date: 2014.05.27 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8738584B2 patent drawing
  • US8738584B2 patent drawing
  • US8738584B2 patent drawing

AI summary

Embodiments provide information composition management features and functionality to manage composite information, but are not so limited. In an embodiment, a computing system can include functionality to provide a composition of informational data that can be used to identify and manage aspects of shared and other data that can be associated with distinct information sources. In one embodiment, a computing platform includes a client that can be configured to access and use information of a plurality of independent sources to create a data composition that includes aspects of shared and unshared data portions and manage data changes of the data composition including managing issues associated with one or more of the plurality of independent sources. Other embodiments are described and available.