Binary File Transfer Network Management System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional telecom network management systems (NMS) are inefficient, reactive, and prone to overload during high network activity, with vendor-specific components and complex protocol conversions leading to reduced transparency, flexibility, and increased costs.
Innovation Solution
A system that transfers binary network management data files between a network management system server and remote network elements, using periodic routines to update control and status files, eliminating the need for intermediate messaging protocols and enabling direct access to network parameters through a graphical user interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If conventional messaging and command based protocols (SNMP, TL1, CMIP) are used for network management communications, then network management operations can be performed, but system complexity increases due to multiple protocol conversion stages and vendor-specific implementations
Solution Approach 1:
The patent extracts and eliminates the intermediate protocol conversion layers (SNMP, TL1, CMIP, MIBs) from the network management architecture. By directly transferring binary network management data files between the NMS server and network elements, the system removes the complex messaging and command protocols that caused vendor-specific implementations and integration difficulties, while preserving full network management operational capability
Solution Approach 2:
The patent introduces a direct binary file transfer mechanism as a new intermediary that replaces the traditional protocol-based messaging system. This new intermediary (direct binary transfer) eliminates the need for multiple protocol conversion stages and vendor-specific translation layers, reducing system complexity while maintaining network management functionality
2Reliability
If event-triggered messaging is used for network management transactions, then responsive network management is achieved, but system performance degrades during high network activity and event bursts
Solution Approach 1:
The patent implements periodic file transfer routines that systematically move network management data between the NMS server and network elements at scheduled intervals. This periodic action replaces the reactive event-triggered messaging, providing consistent performance regardless of network activity levels while maintaining reliable network management through regular status updates and configuration synchronizations
Solution Approach 2:
The patent establishes continuous network management operations through persistent file transfer routines that continuously synchronize configuration files, status files, and alarm data between the NMS server and network elements. This continuous action eliminates the impulsive, start-stop nature of event-triggered messaging, ensuring steady system performance during both normal and high-load conditions
3Ease of operation
If vendor-specific Management Information Bases (MIBs) and protocol conversions are implemented, then network management functionality is achieved, but transparency from user interface to network element hardware is reduced
Solution Approach 1:
The patent extracts and removes the layers of vendor-specific MIBs and protocol conversions that obscure the direct path between the user interface and network element hardware. By implementing direct binary file transfers, the system eliminates these intermediate translation layers, restoring full transparency while preserving all necessary network management functionalities through the binary data structures
Data Source
AI summary
Telecommunication network management operations are performed based on accessing network management data (NMD) files via GUIs and general purpose computers including a network management system (NMS) server, and automatic routines for transferring binary NMD files between the general purpose computers and remote network elements (NEs) being managed. A system user produces configuration files at the NMS server for NEs using a network management GUI, and the hardware of NEs automatically complete the network management operations indicated by the NMD files transferred to them from the NMS server and produce their status files to the NMS server. The network management GUI displays network status based on the latest NE status files at the NMS server. This provides direct, binary file transfer based NMS communication that avoids the complexity and restrictions of intermediate messaging protocols or transaction languages and conversions thereof.