Wireless Data Synchronization Using Priority and Dependency Levels

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing solutions for synchronizing data between a mobile device and a network node are inadequate for devices with a large number of collections, as they rely on limited priority levels, leading to haphazard ordering and potential data loss when collections become dependent on each other.

Innovation Solution

The introduction of a dependency field within the priority level scheme, allowing each priority level to be subdivided into dependency levels, ensuring correct synchronization order by exchanging priority and dependency values during synchronization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a limited number of priority levels (e.g., 1-10) are used to order collections during synchronization, then the system remains simple and easy to implement, but it cannot accommodate devices with a large number of collections or collections with dependency relationships

Engineering Contradiction:
Improvenumber of collectionsVSAvoidpriority level structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The priority level is segmented into two independent fields: a priority field (providing 10 levels) and a dependency field (providing 255 levels). This segmentation allows the system to handle a much larger number of collections (up to 2550 combinations) while keeping each individual field simple and manageable.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The solution adds another dimension to the ordering system by introducing the dependency field as a secondary sorting criterion. Instead of extending the priority levels in one dimension, the patent creates a two-dimensional ordering structure where collections are first sorted by priority level, then by dependency level within each priority group.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If collections with the same priority level are synchronized in haphazard order, then the synchronization process is simple, but data loss may occur when collections have dependency relationships

Engineering Contradiction:
Improvesynchronization orderVSAvoidordering mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The dependency field is assigned to each collection in advance, establishing the correct synchronization order before the actual synchronization process begins. This preliminary assignment ensures that dependent collections are properly ordered relative to their dependencies, preventing data loss.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The network node uses the dependency field values as feedback to determine the correct synchronization order. When multiple collections share the same priority level, the node compares their dependency field values and synchronizes them in ascending order of dependency, ensuring that collections dependent on lower-numbered collections are synchronized after those collections.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8473637B2Method and apparatus for extended ordering over a wireless network of collections using priority and dependency levels
Publication Date: 2013.06.25 MALIKIE INNOVATIONS LTD
  • US8473637B2 patent drawing
  • US8473637B2 patent drawing
  • US8473637B2 patent drawing

AI summary

A method and system for extended ordering of collections of data for synchronization over a wireless network, each collection having an existing priority level, the method having the steps of: adding, to each collection, a dependency field having a dependency value; exchanging the priority level and dependency value for each collection; and ordering synchronization of the collections based on priority levels and dependency values of the collections.