Network Device Output Filtering via Schema Enumeration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of network devices, such as routers, results in intricate configuration and management tasks, leading to overwhelming data output that burdens users with unnecessary information, inefficient data transmission, and resource usage.

Innovation Solution

A schema enumeration module correlates XML data with unique element numbers, enabling a filtering module to selectively filter and render relevant data based on user-specified criteria, reducing output to only pertinent information and optimizing network bandwidth.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If network devices output complete and detailed data in response to operational commands, then data completeness and accuracy are improved, but data transmission efficiency and user experience deteriorate due to overwhelming volume of unnecessary information

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

Solution Approach 1:

The patent applies preliminary action by pre-defining XML schemas that describe the structure and semantics of data elements before data generation. The schema enumeration module pre-processes operational commands to identify which schema elements are relevant, filtering data at the source before transmission. This eliminates the need to transmit complete raw data sets, reducing network bandwidth consumption while maintaining data completeness for relevant parameters.

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If network devices provide comprehensive data output, then information accuracy is improved, but ease of operation deteriorates due to overwhelming data volume requiring user sifting

Engineering Contradiction:
Improveinformation accuracyVSAvoiddata retrieval efficiency
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent extracts only the relevant data elements needed by the user from the complete data set. The filtering module uses the XML schema and field identifiers to extract specific portions of data, removing unnecessary information before transmission. This maintains accuracy of the extracted data while dramatically improving ease of operation by delivering only the information the user needs without requiring sifting through overwhelming volumes of irrelevant data.

Inventive Principle:
Principle #2Taking out (Extraction)

3Loss of information

If network devices transmit all generated data, then data availability is improved, but device complexity in terms of data processing and transmission management increases

Engineering Contradiction:
Improvedata availabilityVSAvoiddata transmission management
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary filtering module that sits between the data generation process and the transmission mechanism. This intermediary uses the pre-defined XML schema to automatically filter and select relevant data elements based on field identifiers, eliminating the need for complex manual data transmission management. The schema acts as a mediator that translates user needs into automated filtering decisions, reducing device complexity while maintaining data availability for relevant parameters.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9495428B1Filtering output from operational commands executed on a network device
Publication Date: 2016.11.15 HEWLETT PACKARD ENTERPRISE DEV LP
  • US9495428B1 patent drawing
  • US9495428B1 patent drawing
  • US9495428B1 patent drawing

AI summary

In general, techniques are described to enable selective viewing of data output in response to a command. The techniques provide generic mechanisms to filter output solicited by commands supported by current and future implementations of an interface. An example device receives from a client device an input comprising an operational command a selection request that specifies a field identifier. A schema enumeration module of the device assigns a unique element number to each element of a class of elements defined by a schema, forming an enumerated schema. An interface of the device receives data conforming to a data description language, and a filtering module filters the textual output by mapping the field identifier specified in the selection request to a unique element number of the enumerated schema. A rendering module renders the filtered data into filtered textual output. The device transmits the filtered textual output to the client device.