EML-NML Configuration Synchronization via Shared FTP and Parallel XML Splitting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for full configuration synchronization between EML and NML in EML-NML management systems face inefficiencies due to excessive network handshake interaction time, difficulties in splitting XML files, lack of configuration data sharing among NMSes, and limited parallelism in synchronization processes, especially with large configuration data sets.

Innovation Solution

A method and system that divide full configuration synchronization into three parallel processes using IIOP/SOAP protocols, with asynchronous XML file generation and storage on a shared FTP server, allowing for efficient file splitting and sharing, and reducing network interaction time by utilizing a shared FTP server for data transfer and implementing a background parallel processing mechanism.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If interface-based synchronization (get All Managed Element) is used, then configuration data can be synchronized between NMS and EMS, but excessive network handshake interaction time is required when configuration becomes large

Engineering Contradiction:
Improveconfiguration synchronizationVSAvoidnetwork handshake interaction time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces an FTP server as an intermediary component to mediate the configuration data transfer between NMS and EMS. Instead of direct NMS-EMS interface interactions, the system uses FTP server as a middle ground where configuration data is uploaded and downloaded, thereby reducing the network handshake overhead between NMS and EMS while maintaining synchronization reliability

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the configuration data transfer function from the traditional NMS-EMS interface interaction and separates it into an independent FTP-based file transfer process. This extraction allows the configuration synchronization to proceed through a dedicated file transfer mechanism rather than through repeated interface handshakes, significantly reducing the time loss associated with network protocol interactions

Inventive Principle:
Principle #2Taking out (Extraction)

2Loss of time

If get inventory configuration method is used, then network handshake time is reduced, but XML files become huge leading to slow NMS resolution and processing difficulties

Engineering Contradiction:
Improvenetwork handshake timeVSAvoidNMS resolution speed
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The patent segments the large XML configuration files into smaller partitioned files based on device types or configuration modules. Instead of transferring and processing one huge XML file, the system divides it into manageable chunks that can be resolved and processed more quickly by the NMS, thereby maintaining fast network handshake while improving resolution productivity

Inventive Principle:
Principle #1Segmentation

3Reliability

If get inventory configuration method is used, then configuration data can be transferred, but NMSes cannot share configuration data efficiently

Engineering Contradiction:
Improveconfiguration data transferVSAvoidconfiguration data sharing
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent merges the configuration data storage and sharing function into a centralized FTP server that serves multiple NMS instances. Instead of each NMS maintaining separate configuration data, the system combines all configuration files in a shared FTP repository, allowing multiple NMSes to access and share configuration data efficiently while maintaining data transfer reliability

Inventive Principle:
Principle #5Merging (Combining)

4Adaptability or versatility

If flexible synchronization conditions are allowed, then NMSes can request various configuration data, but it is difficult to improve the degree of parallelism during full configuration synchronization

Engineering Contradiction:
Improvesynchronization conditionsVSAvoidparallelism degree
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements dynamic synchronization conditions where the FTP server and NMS can adaptively determine which configuration files need to be transferred based on change detection and file timestamps. This dynamic approach maintains versatility in handling different synchronization scenarios while enabling parallel processing by allowing multiple independent file transfer operations to proceed simultaneously without rigid conditional constraints

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP3026860B1Method and system for transmission management of full configuration synchronization between EML-nml
Publication Date: 2020.02.19 FIBERHOME TELECOMMUNICATION TECHNOLOGIES CO LTD
  • EP3026860B1 patent drawingFigure 1~2
  • EP3026860B1 patent drawingFigure 3
  • EP3026860B1 patent drawingFigure 4

AI summary

Disclosed in the present invention are a method and system for transmission management of full configuration synchronization between EML (Element Management Level) and NML (Network Management Level), The present invention relates to the field of EML-NML. The system comprises a DCN (Data Communication Network), a plurality of EMSes (Element Management System) and NMSes (Network Management System) which are connected with the DCN respectively, and a shared FTP (File Transfer Protocol) server; arranged in the shared FTP server are FTP interfaces which are fixedly separated, and FTP is employed as a mass data transfer protocol; the process of full configuration synchronization is divided by the NMSes into three parallel processes: a basic configuration synchronization request process, a network element cross synchronization request process and a service routing synchronization request process; a basic configuration synchronization request is sent to the EMSes, and the NMSes transfer the basic configuration synchronization request to the EMS side through interaction protocol IIOP/SOAP (Internet Inter-ORB Protocol/Simple Object Access Protocol). The present invention can avoid a large amount of network handshake interaction time, facilitate splitting XML (Extensible Markup Language) configuration files, realize a plurality of NMSes sharing configuration data, reduce full synchronization frequency between EML and NML, and improve the degree of parallelism of full configuration synchronization during big configuration data synchronization.