Hierarchical Storage Entity Selection for Network Data Distribution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current telecommunications networks face challenges in efficiently storing and distributing digital data due to high resource requirements for central architectures and instability in peer-to-peer architectures, which lead to increased traffic and limited access capabilities.

Innovation Solution

A method and device that select a data storage entity based on hierarchical levels within the network, considering factors like geographical location, data popularity, and cost, allowing for dynamic redistribution of data to optimize storage and delivery, and a communication method that updates storage lists based on access requests and threshold values to manage network load effectively.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If data is stored at a central level in hierarchical architectures, then content distribution management is improved, but resource requirements and memory usage increase significantly

Engineering Contradiction:
Improvecontent distribution managementVSAvoidmemory resources
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent segments the storage function across multiple hierarchical levels (central level, intermediate levels, and terminal level) rather than concentrating all storage at the central level. This allows content distribution management to be maintained while distributing the memory burden across many nodes, with each node storing only the data relevant to its level and local users.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by allowing different hierarchical levels to store different types of data based on their specific needs and capabilities. Terminal devices store locally-generated and frequently-accessed content, intermediate nodes store regional content, and the central level stores global content, optimizing memory usage at each level.

Inventive Principle:
Principle #3Local quality

2Quantity of substance

If data is stored at terminal level in peer-to-peer architectures, then resource requirements are reduced, but traffic increases and configuration stability decreases

Engineering Contradiction:
Improvememory resourcesVSAvoidconfiguration stability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent introduces intermediary nodes at intermediate hierarchical levels that act as mediators between central storage and terminal devices. These intermediaries provide stable anchor points in the network hierarchy, improving configuration stability while still allowing terminal devices to maintain local storage capabilities and reduce overall memory requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Quantity of substance

If data is stored at terminal level, then memory resources are optimized, but access capability and data rate are limited by terminal capabilities

Engineering Contradiction:
Improvememory resourcesVSAvoiddata access capability
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent adds the hierarchical dimension to the storage architecture, creating multiple levels (central, intermediate, terminal) that can serve different access scenarios. This allows the system to optimize for both memory efficiency and access capability by routing requests to the appropriate hierarchical level based on data location, access frequency, and terminal capabilities.

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

4Productivity

If hierarchical storage is implemented, then content distribution is optimized, but device complexity increases

Engineering Contradiction:
Improvecontent distribution efficiencyVSAvoidnetwork architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements self-service mechanisms where each node in the hierarchical architecture autonomously manages its own storage decisions based on local conditions and received requests. Nodes independently determine what data to store and serve based on their hierarchical level, local user needs, and available resources, reducing the complexity of centralized control while maintaining efficient content distribution.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10063614B2Method for obtaining a storage identifier in a hierarchical level of storage in a network for storing data
Publication Date: 2018.08.28 ORANGE SA
  • US10063614B2 patent drawing
  • US10063614B2 patent drawing
  • US10063614B2 patent drawing

AI summary

The method performed by a receiver entity in a hierarchical network, the entity having knowledge of the hierarchical levels of nodes of the network is disclosed. In one aspect, the method comprises, on reception of a request to store data as sent by a sender unit:a step of selecting at least one storage entity for storing the data, the selection step taking account at least of the hierarchical level of the storage entity in the network; anda step of sending information to the sender unit enabling it to obtain the identifier of the data storage entity.