Parameter Subtree Iterator for Server Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current communication protocols between a server device and customer devices, such as the TR-069 Management Protocol, face issues with network load and latency due to inefficient data retrieval methods, particularly when dealing with large arrays of parameters, leading to scalability concerns and excessive bandwidth usage.

Innovation Solution

The method involves instantiating an iterator on the customer device for a parameter-sub-tree, allowing for efficient data retrieval by specifying a start and end value, reducing the need for unnecessary data transmission and improving response times by managing a subrange of parameter values.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If the existing TR-069 protocol methods are used to retrieve parameter values, then complete parameter data can be obtained, but network load and bandwidth usage increase excessively

Engineering Contradiction:
Improveparameter data completenessVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The patent segments the parameter retrieval process into two distinct phases: a configuration phase where the ACS transmits the complete parameter-sub-tree structure and iterator definitions to the CPE, and an execution phase where the CPE performs local iteration and transmits only the specific parameter values requested. This segmentation allows the network to carry minimal data during the execution phase, resolving the contradiction between obtaining complete parameter data and reducing network bandwidth consumption.

Inventive Principle:
Principle #1Segmentation

2Loss of information

If all parameter values in a parameter-sub-tree are transmitted, then the server device receives complete data, but response time and latency increase

Engineering Contradiction:
Improveparameter data completenessVSAvoidcommunication response time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent extracts only the necessary parameter values from the complete parameter-sub-tree at the CPE side. The iterator mechanism allows the ACS to specify which parameters are needed, and the CPE extracts and transmits only those specific values rather than all parameters in the sub-tree. This extraction approach maintains data completeness for requested parameters while significantly reducing transmission time and latency.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If the parameter retrieval method supports large arrays of parameters, then comprehensive device management is achieved, but scalability becomes problematic due to network load

Engineering Contradiction:
Improvedevice management capabilityVSAvoidsystem scalability
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent introduces dynamic iterators that can be configured at runtime to adapt to different parameter retrieval needs. The ACS can dynamically create iterators with specific start and end values for array parameters, allowing flexible querying of large parameter sets without transmitting unnecessary data. This dynamic approach enables comprehensive device management capability while maintaining system scalability by keeping network traffic proportional to actual information needs.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8473623B2Method for managing a communication between a server device and a customer device
Publication Date: 2013.06.25 ALCATEL LUCENT SA
  • US8473623B2 patent drawing
  • US8473623B2 patent drawing

AI summary

A method is described for managing a communication between a server device and a customer device. The method comprises interchanging between the server device and the customer device one or more parameter messages that are comprising a parameter description for a parameter name. The parameter description does consist of an hierarchical tree-like structure of characters with each level separated by a predefined character (dot). The method further comprises a step of instantiating by an instantiating device of the customer device, an iterator associated to an index, for a next level of a parameter-sub-tree being part of the global parameter description, and a step of recalling an object array for the parameter-sub-tree with the next level having different values for its index starting with a predefined start-value and ending with a predefined end-value.