Pusher Puller Objects Automate SNMP Data Transfer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for managing and configuring large wireless networks are complicated due to the increased number of components, and existing user interface management software is limited in creating effective interfaces for pushing and pulling data between databases and user applications.

Innovation Solution

The implementation of 'pushers' and 'pullers' as software objects that automate data writing and reading over networks, specifically for SNMP MIB data, which can be invoked by applications or automatically by a page management framework, encapsulating network I/O activities and allowing data modification in any thread while updating components in Event Dispatch threads.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual data management methods are used in large wireless networks, then system control is possible, but management complexity and time consumption increase dramatically

Engineering Contradiction:
Improvenetwork management efficiencyVSAvoidsystem management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces pushers and pullers as intermediary software objects that mediate between the user interface and the SNMP MIB database. These intermediaries automate data transfer operations, eliminating the need for manual data management while reducing system complexity. The pusher object pushes data from the UI to the database, and the puller object pulls data from the database to the UI, providing an automated intermediary layer that resolves the contradiction between manageability and complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements self-service through automated pusher and puller objects that independently manage data synchronization between the user interface and database. These objects automatically execute data transfer operations without requiring manual intervention, enabling the system to serve itself in data management tasks. This self-service mechanism dramatically improves productivity while reducing the complexity of manual management operations.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If data loading operations are performed in the user interface thread, then data transfer is simple, but the user interface becomes blocked during data loading

Engineering Contradiction:
ImproveUI responsivenessVSAvoidthread management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the data loading operation into separate threads independent of the user interface thread. The pusher and puller objects execute data transfer operations in dedicated background threads, separating the data loading function from the UI rendering function. This segmentation allows the UI to remain responsive while data loading occurs concurrently in separate threads, resolving the contradiction between operational simplicity and UI responsiveness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The pusher and puller objects serve as intermediary components that handle thread management and data transfer coordination. They mediate between the UI thread and background data loading threads, managing the complexity of multi-threaded operations while keeping the UI simple to use. The intermediaries abstract the thread management complexity away from the UI, allowing developers to maintain simplicity while achieving responsive behavior.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If automated pusher and puller objects are implemented, then data transfer is automated and UI remains responsive, but software object complexity increases

Engineering Contradiction:
Improvedata transfer automationVSAvoidsoftware architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The pusher and puller objects are designed as universal, multi-functional software components that can be applied to various data transfer scenarios in SNMP MIB management. Rather than creating custom data transfer logic for each UI element, the same pusher and puller objects serve multiple functions across different parts of the system. This universality reduces overall software architecture complexity by providing reusable, standardized objects that automate data transfer throughout the system.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent employs parameter changes to configure and control the pusher and puller objects for different data transfer scenarios. By adjusting parameters such as target OID, data type, and update frequency, the same basic object structure can adapt to various automation requirements without increasing fundamental complexity. This parameter-based configuration allows automated data transfer to be achieved while maintaining manageable software architecture through standardized object templates.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8027362B2Methods and systems for pushing and pulling network data in user interface design
Publication Date: 2011.09.27 SYMBOL TECHNOLOGIES LLC
  • US8027362B2 patent drawing
  • US8027362B2 patent drawing
  • US8027362B2 patent drawing

AI summary

A network management system is provided for allowing a user to interface with network management data provided by a network agent via a network. Application level logic obtains and formats the network management data to thereby create a display presented to the user. A library of software processing structures for sharing data with the network agent is provided, and an abstraction layer distinct from the library is configured in communication with the application level logic. The abstraction layer includes a pusher feature configured to facilitate the writing of data from the application level logic to the network agent and a puller feature configured to facilitate the reading of data from the network agent to the application level logic. The abstraction layer uses the library to communicate with the network agent via the network while isolating the application level logic from the library.