Master-Slave Operation Synchronization Across Multiple Windows

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computer systems require separate operations for each window, document, or database, making it inefficient to execute corresponding operations across multiple maps, windows, or databases simultaneously, such as scrolling or modifying geographic displacements, which can be time-consuming and inconvenient.

Innovation Solution

A system utilizing an event handler to automatically execute operations on multiple windows, documents, or databases by designating a master operation that is relayed to corresponding slave operations, allowing for simultaneous execution across multiple platforms, regardless of their open or closed state, using a matrix of corresponding operations to determine the appropriate actions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If separate operations are executed for each window, document, or database, then each operation can be performed independently and precisely, but the time required and operational complexity increase significantly when multiple corresponding operations need to be performed

Engineering Contradiction:
Improveoperational efficiencyVSAvoidtime for repetitive operations
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent combines multiple separate operations into a single master operation that is executed once and automatically propagated to multiple slave windows, documents, or databases. This merging approach eliminates the need to perform identical operations separately in each target, directly addressing the time loss and productivity issues by executing corresponding operations simultaneously across all targets through a single user action.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces an intermediary mechanism (the system's operation propagation engine) that receives the master operation and automatically translates it into corresponding slave operations. This intermediary layer handles the complexity of operation translation and coordination between master and slave elements, allowing the user to perform operations once while the system automatically executes them across multiple targets without manual intervention.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If manual separate operations are performed on multiple maps, windows, or databases, then each operation can be controlled individually, but the process becomes time-consuming and inconvenient when synchronization is required

Engineering Contradiction:
Improveuser convenienceVSAvoidtime for synchronized operations
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent merges multiple manual operations into a single master operation that the user executes once. The system then automatically propagates this operation to all designated slave elements (maps, windows, databases), eliminating the need for users to manually perform identical operations in each target. This directly improves ease of operation while reducing the time required for synchronized updates across multiple elements.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements self-service functionality where the system automatically handles the propagation and execution of operations across multiple targets without requiring manual intervention. Once the user initiates a master operation, the system autonomously translates and executes corresponding operations on all slave elements, freeing the user from repetitive manual tasks and improving both convenience and time efficiency.

Inventive Principle:
Principle #25Self-service

3Productivity

If corresponding operations are executed manually on multiple documents or databases, then each operation can be performed with full control, but the complexity of coordinating operations across multiple platforms increases

Engineering Contradiction:
Improveoperation execution speedVSAvoidcoordination complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary coordination mechanism that manages the complexity of operating across multiple platforms. This intermediary layer (the operation propagation engine) handles the translation, mapping, and synchronization of operations between master and slave elements across different applications and databases, shielding the user from coordination complexity while enabling high-speed operation execution across all targets.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent uses copying to propagate operations from the master element to slave elements. The system creates copies of the master operation and adapts them to each slave target's specific requirements. This copying mechanism enables rapid operation execution across multiple platforms while the system handles the complexity of adapting operations to different contexts, thereby improving productivity without increasing user-facing complexity.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS7552187B2System and method for automatically executing corresponding operations on multiple maps, windows, documents, and/or databases
Publication Date: 2009.06.23 TOMTOM NORTH AMERICA INC
  • US7552187B2 patent drawing
  • US7552187B2 patent drawing
  • US7552187B2 patent drawing

AI summary

A system and method for causing a master operation that is executed on a master map, window, document, or database to also be automatically executed in its corresponding form on one or more slave maps, windows, documents, and/or databases. Embodiments of the invention can operate with masters and slaves that are initially either open or closed or both, depending on the operator's desires and the current state of the computing device. Embodiments of the invention are capable of opening masters and/or slaves that are closed. In some embodiments, the event handler capable of receiving the selections of master and slave(s) is part of the operating system and in other embodiments it is separate from the operating system. All embodiments operate with one master and with one or more slaves. In certain embodiments, the master and/or one or more slaves and/or the operation will be selected by default.