Network Node HARQ Conflict Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed data storage systems face conflicts in meeting simultaneous requirements for consistency, availability, and partition tolerance, as well as other contradictory storage needs such as Fast Read and Fast Write, leading to synchronization issues and compromises in performance and scalability.

Innovation Solution

A method and apparatus that receive storage requests from multiple applications, detect conflicting requirements, and resolve them by dividing applications into groups with non-conflicting needs or reducing the relevance of conflicting requirements, allowing for optimized storage requests based on each group's requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the same data storage is used for multiple applications with different requirements, then data sharing is achieved, but conflicting storage requirements cannot be fulfilled simultaneously

Engineering Contradiction:
Improvedata sharing capabilityVSAvoidstorage requirement fulfillment
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the data storage system into multiple virtual storage spaces, each tailored to specific application requirements. The network node divides the data set into different logical partitions that can be independently configured with different storage parameters (consistency level, availability, partition tolerance), allowing each application group to access storage with optimized characteristics for its needs.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by assigning different storage characteristics to different portions of the data or different access patterns. Each virtual storage space can have customized properties (synchronous/asynchronous updates, read/write priorities) that match the specific requirements of the applications accessing it, rather than applying uniform storage behavior across all applications.

Inventive Principle:
Principle #3Local quality

2Reliability

If more nodes are involved to improve consistency, then data consistency is improved, but latency increases

Engineering Contradiction:
Improvedata consistencyVSAvoidresponse latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements dynamic consistency levels where the network node can adjust the number of nodes involved in consensus operations based on the specific data item and application requirements. For frequently accessed data with relaxed consistency requirements, fewer nodes are involved, reducing latency. For critical data requiring strong consistency, more nodes participate in the consensus process.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of consistency level dynamically. Different virtual storage spaces or different operations on the same storage can operate at different consistency levels (e.g., strong consistency vs. eventual consistency), allowing the system to optimize between consistency and latency by selecting appropriate parameter settings for each use case.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If synchronous updates are applied to all nodes, then consistency is guaranteed, but latency becomes high

Engineering Contradiction:
Improvedata consistencyVSAvoidupdate latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements periodic or batched update synchronization instead of continuous synchronous updates. Data can be updated asynchronously at individual nodes and then synchronized periodically or in batches with other nodes, reducing the latency impact while maintaining eventual consistency. This is particularly useful for applications that can tolerate eventual consistency.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system applies partial synchronous updates where only the necessary subset of nodes is updated synchronously based on the consistency requirements of the specific operation. For operations with lower consistency requirements, fewer nodes are involved in the synchronous update process, reducing overall latency while maintaining adequate consistency for the application's needs.

Inventive Principle:
Principle #16Partial or excessive action

4Reliability

If data is replicated across multiple nodes for availability, then availability is improved, but synchronization issues arise

Engineering Contradiction:
Improvedata availabilityVSAvoidsynchronization complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a coordinator or mediator component in the network node that manages synchronization between replicated data across multiple nodes. This intermediary handles conflict resolution, version control, and coordination of updates, simplifying the synchronization process and reducing the complexity that would otherwise be distributed across all nodes. The mediator enables high availability through replication while managing the synchronization overhead centrally.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9825735B2Network node and method therein for HARQ processes in a D2D communication
Publication Date: 2017.11.21 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US9825735B2 patent drawing
  • US9825735B2 patent drawing
  • US9825735B2 patent drawing

AI summary

In accordance with an example embodiment of the present invention, disclosed is a method and an apparatus thereof for handling a conflict resolution between storage requirements of multiple applications sharing the same data. A conflict resolution function resolves the conflicts in several steps and the result is either a coordinated merge of the different applications' storage requirements in multiple groups according to their needs and/or a controlled reduction of the relevance of some of the storage requirements for some applications.