Service Endpoint Data Synchronization via Feed Intermediary

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data synchronization methods are complex and often require specific data interchange formats and networking topologies, making it difficult to share and synchronize data between multiple endpoints efficiently, especially when endpoints have intermittent connectivity or lack resources for implementing synchronization functionality.

Innovation Solution

The approach involves adding synchronization data to a feed that contains data items, with at least one endpoint providing synchronization-related services to other endpoints, allowing for bidirectional synchronization using protocols like RSS, and offloading synchronization tasks to a service endpoint for endpoints with limited resources or intermittent connectivity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If specific data interchange formats and synchronization rules are implemented, then data synchronization reliability is improved, but device complexity and ease of operation deteriorate

Engineering Contradiction:
Improvedata synchronization reliabilityVSAvoidsynchronization implementation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a service endpoint that acts as an intermediary between client endpoints, providing synchronization services through standardized web service interfaces. This mediator handles the complex synchronization logic, data format conversion, and conflict resolution, while client endpoints only need to perform simple operations like adding or removing items. The service endpoint receives requests from multiple client endpoints, performs the necessary synchronization processing, and returns results, thereby resolving the contradiction between reliable synchronization and simple implementation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If synchronization functionality is implemented on each endpoint, then synchronization capability is improved, but ease of operation and device complexity worsen for resource-constrained devices

Engineering Contradiction:
Improvesynchronization capabilityVSAvoidimplementation difficulty
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The service endpoint provides self-service synchronization capabilities to client endpoints through standardized web service interfaces. Client endpoints can independently perform synchronization operations by sending requests to the service endpoint and receiving responses, without requiring complex local synchronization implementations. The service endpoint automatically handles data exchange, conflict resolution, and state synchronization, allowing resource-constrained devices to achieve synchronization capability with minimal implementation effort.

Inventive Principle:
Principle #25Self-service

3Stability of the object's composition

If complex synchronization rules and data exchange protocols are enforced, then data consistency is improved, but productivity and ease of operation deteriorate

Engineering Contradiction:
Improvedata consistencyVSAvoiddata sharing efficiency
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

The patent employs universal web service protocols (SOAP, REST, XML, JSON) that can handle multiple synchronization scenarios and data types through a single standardized interface. The service endpoint provides multi-functional capabilities including data exchange, conflict resolution, state synchronization, and format conversion all through the same protocol framework. This universality maintains data consistency through standardized rules while improving productivity by eliminating the need for custom protocol implementations for different synchronization scenarios.

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

4Reliability

If specific networking topologies like hub and spoke are required, then synchronization control is improved, but adaptability and ease of operation worsen

Engineering Contradiction:
Improvesynchronization controlVSAvoidnetwork topology flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The service endpoint acts as a flexible intermediary that can operate in various network topologies. It provides centralized synchronization control when needed (acting as the hub in hub-and-spoke arrangements) while also supporting peer-to-peer scenarios where multiple service endpoints can collaborate. The standardized web service interfaces allow client endpoints to connect to the service endpoint through any network topology without requiring specific topology enforcement, achieving both reliable control and network flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7933296B2Services for data sharing and synchronization
Publication Date: 2011.04.26 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7933296B2 patent drawing
  • US7933296B2 patent drawing
  • US7933296B2 patent drawing

AI summary

Systems and methods for sharing and synchronizing data using the addition of synchronization data to a feed that contains data items, and at least a node or endpoint that provides synchronization-related services to other endpoints, are disclosed. Such systems and methods, and client and service endpoints, may use the added synchronization data in multiple ways to share data, incorporate changes consistently, and resolve conflicts.