CN102447542B - Difference self-recognizing method and system for configuration data of network equipment - Google Patents
Difference self-recognizing method and system for configuration data of network equipment Download PDFInfo
- Publication number
- CN102447542B CN102447542B CN201010504407.XA CN201010504407A CN102447542B CN 102447542 B CN102447542 B CN 102447542B CN 201010504407 A CN201010504407 A CN 201010504407A CN 102447542 B CN102447542 B CN 102447542B
- Authority
- CN
- China
- Prior art keywords
- timestamp
- management node
- configuration
- data
- configuration set
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a difference self-recognizing method for configuration data of network equipment. The method comprises the following steps: when configuration data is updated, a management node and a network element (NE) update respective timestamps; the management node queries the timestamp of the NE and compares the timestamp of the NE with the timestamp per se; and then, the difference between the configuration data of the management node and the configuration data of the NE is determined. The invention further discloses a difference self-recognizing system for the configuration data of the network equipment. With the adoption of the method and the system, disclosed by the invention, the data difference between the NE and the management node can be accurately recognized, and the latest modification time is displayed, so that problems can be accurately analyzed and located by engineers conveniently.
Description
Technical Field
The present invention relates to the field of network device data configuration, and in particular, to a method and system for self-identifying differences of network device configuration data.
Background
The communication network is composed of a plurality of communication nodes and management nodes, and the communication nodes refer to communication equipment in the communication network, such as: a base station Node B in a time division synchronous code division multiple access (TD-SCDMA) Network, a Radio Network Controller (RNC), a base station and a base station Controller in a global system for mobile communications (GSM) Network and the like; the communication nodes may be collectively referred to as Network Elements (NE), and the network elements communicate with each other through physical medium links such as optical fibers, cables, E1/T1 lines, and the like. The management node is indispensable management equipment in a communication network, and the management node remotely configures, maintains and monitors network elements in the network through a communication link; the Management nodes are classified according to the specification of a communication Management Network (TMN), and may be: an Element Management System (EMS) and a Network Management System (NMS), where Management nodes pass through interfaces defined in the TMN specification, such as: a Q3 interface, a Common Object Request Broker Architecture (CORBA) interface, etc.
Typically, configuration data of the NE is maintained by EMS, NMS, Local Maintenance Tool (LMT), or third party configuration management Tool, including terrestrial configuration, wireless configuration, etc. The EMS and the NMS belong to an offline configuration tool, that is, the configuration data is locally stored, and when an engineer modifies the configuration data of the offline configuration tool, the configuration data of the NE cannot be updated in real time, the offline configuration tool needs to be manually triggered to be synchronized with the NE, and then the updated configuration data is synchronized to the NE, so that the configuration data of the NE is updated. And the LMT or the third party configuration tool belongs to the online configuration tool, and when the engineering personnel modify the configuration data through the online configuration tool, the online configuration tool synchronizes the modified configuration data to the NE in real time, so that the configuration data of the NE is updated.
In an actual network operation process, an engineer may update configuration data of the NE through an offline configuration tool, that is, a management node or an online configuration tool, due to a certain operation requirement, and when the configuration data of the NE is updated through the online configuration tool or the management node updates configuration data of the NE itself, but forgets to synchronize with the NE, a situation that the configuration data of the NE is inconsistent with the configuration data of the management node may occur. At this time, other engineering personnel may not know the actual configuration data condition of the current NE, and may not operate the NE network element, or may mistakenly assume that the configuration data of the current NE is the same as the configuration data of the management node, which may cause a wrong operation on the NE network element, and affect the network operation.
In the current management node, a commonly used method for identifying configuration data differences is as follows: network element modification flags or message flow numbers are used to describe the difference between the management node and the NE configuration data. Taking the message serial number as an example, the management node and the NE both store the message serial number, and the message serial number of the management node is correspondingly changed when the configuration data in the management node is updated once, wherein the change is to add 1 on the basis of the original message serial number, synchronize the updated configuration data to the NE after the management node is synchronized with the NE, and simultaneously cover the message serial number of the NE with the message serial number of the management node; or the configuration data in the management node is updated, the message serial number in the management node is not changed, when the management node is synchronized with the NE, the message serial number of the management node is changed, and the changed message serial number covers the message serial number of the NE.
However, this configuration data difference identification method has a problem: if the engineer modifies the configuration data of the management node but forgets synchronization, at this time, the message serial number of the management node is the same as that of the NE, but the configuration data of the management node and the NE are different; or, the engineer updates the configuration data of the NE through the online configuration tool, and the message serial number of the NE is not changed, and the message serial number of the NE is the same as that of the management node, but the configuration data of the NE and the management node are different; alternatively, when an engineer imports or replaces a NE with data, the configuration data difference between the management node and the NE cannot be confirmed. It can be seen that the message serial number does not accurately reflect the difference between the configuration data of the management node and the NE and the data difference between multiple sets of data configuration sets in the management node. If the engineer synchronizes the management node with the NE without trade, the current network environment may be damaged, and the work process and the network operation and maintenance are affected. Meanwhile, if an engineer wants to know the configuration data modification time of the management node or the NE, the operation log is positioned according to the modification time, and when the content of the modified data is obtained, the data modification record cannot be searched in a large amount of operation logs, and the current modified scene cannot be positioned and restored.
Disclosure of Invention
In view of the above, the main objective of the present invention is to provide a method and a system for self-identifying a difference between network device configuration data, which can accurately identify a data difference between an NE and a management node and display a latest modification time, so as to facilitate accurate analysis and positioning of engineering personnel.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the invention provides a method for self-identifying the difference of network equipment configuration data, which comprises the following steps: when the configuration data is updated, the management node and the NE update the timestamps of the NE; and the management node inquires the NE time stamp and compares the NE time stamp with the time stamp of the management node to determine the difference between the management node and the NE configuration data.
In the above scheme, when the configuration data is updated, the updating of the timestamp of the management node itself includes: updating configuration data under the configuration set management object MO in the management node, and generating a timestamp and storing the timestamp in the updated configuration set MO by the management node; or, when NE data reconstruction is performed, the management node uploads the NE timestamp and stores the NE timestamp in the main configuration set MO and the network element MO, and if only one configuration set MO exists, the NE timestamp is stored in the configuration set MO and the network element MO; or, when synchronizing with NE data, the management node synchronizes the timestamp in the main configuration set MO to the network element object MO; or if the master-standby configuration set MO exists, when the master-standby configuration set MO is switched, the timestamp of the management node is the timestamp of the switched master-standby configuration set MO; or, when the backup data is imported, the management node imports the backup data timestamp and stores the timestamp in the primary configuration set MO, and if only one configuration set MO exists, the timestamp is stored in the configuration set MO.
In the above scheme, when the NE updates the configuration data, the updating of the timestamp of the NE itself includes: updating configuration data by the online configuration tool, and generating and storing a time stamp by the NE; or the management node updates the configuration data and synchronizes with the NE data, and the NE receives and stores the timestamp synchronized by the management node.
In the foregoing solution, before the management node queries the NE timestamp, the method further includes: the management node establishes a communication link with the NE; or the online configuration tool logs out of the NE, and the NE sends the message logged out by the online configuration tool to the management node.
In the foregoing solution, the comparing with the self timestamp includes: and the management node inquires the NE time stamp and stores the NE time stamp in the local network element MO, and compares the stored NE time stamp with the time stamp in the main configuration set MO.
The invention also provides a system for self-identifying the difference of the configuration data of the network equipment, which comprises the following steps: the management node comprises a management node data configuration module, a management node control module and an NE control module; the management node data configuration module informs the management node control module when a user updates configuration data; the management node control module is used for updating the timestamp of the management node control module according to the notification of the management node data configuration module; inquiring the NE timestamp, and comparing the NE timestamp with the management node timestamp; and the NE control module updates the time stamp of the NE control module when the user updates the configuration data.
In the above solution, the NE control module is further configured to notify the management node control module when the online configuration tool logs out; correspondingly, the management node control module is also used for establishing a communication link with the NE; or when the online configuration tool logs out, the NE timestamp is queried.
In the foregoing solution, the management node control module includes: the system comprises a management node timestamp management unit, a management node communication unit, a management node timestamp comparison unit and a difference maintenance unit; the management node timestamp management unit is used for updating the timestamp of the management node according to the notification of the management node data configuration module; the management node communication unit is used for establishing a communication link with the NE, carrying out information interaction and informing the management node timestamp comparison unit; the management node timestamp comparison unit is used for inquiring the NE timestamp and storing the NE timestamp in the local network element MO after the management node communication unit establishes a communication link with the NE or the online configuration tool logs out the NE; comparing the time stamps in the network element MO and the main configuration set MO, converting the time stamps in the network element MO and the main configuration set MO, and sending the comparison result to a difference maintenance unit; and the difference maintenance unit is used for displaying the comparison result.
In the foregoing solution, the NE control module includes: the system comprises an NE communication unit, an NE timestamp management unit and an NE data configuration unit; the NE communication unit is used for establishing a communication link with the management node and carrying out information interaction; the NE data configuration unit is used for receiving the configuration data sent by the online configuration tool and informing the NE timestamp management unit; receiving configuration data and a timestamp synchronized by a management node, and sending a message synchronized by the management node containing the timestamp to an NE timestamp management unit; receiving a logout message sent by an online configuration tool, and informing a management node timestamp management unit through a management node communication unit; the NE timestamp management unit is used for updating the timestamp of the NE timestamp when the online configuration tool sends the configuration data; and receiving the timestamp synchronized by the management node, and storing the timestamp to the local.
In the foregoing solution, the management node timestamp management unit is specifically configured to receive a configuration data update message sent by a management node configuration module, generate a timestamp, and store the timestamp in a configuration set MO for updating configuration data; receiving data reconstruction information containing NE time stamps, storing the NE time stamps in a main configuration set MO and a network element MO, and if the network element MO only has one configuration set MO, storing the NE time stamps in the configuration set MO and the network element MO; if the master-standby configuration set MO exists, switching the master-standby configuration set MO, receiving a message of switching the master-standby configuration set MO, wherein the timestamp of the management node is the timestamp of the switched master-standby configuration set MO; receiving data synchronization information containing a timestamp of a main configuration set MO, and synchronizing the timestamp in the main configuration set MO to a network element MO; and receiving data import information containing the backup data time stamp, storing the backup data time stamp in the main configuration set MO, and if the network element MO only has one configuration set, storing the backup data time stamp in the configuration set MO.
Therefore, by adopting the method and the system, the user modifies the configuration data of the management node, and when the user updates the configuration data of the NE through the online configuration tool or the management node, the management node and the NE update the time stamp in time, and then the NE time stamp and the management node time stamp are compared to obtain a comparison result, so that the difference between the NE and the management node data can be accurately identified, and thus, engineering personnel can conveniently determine the consistency state and the modification time of the current data to determine the next operation.
Furthermore, the operation log of the management node or the online configuration tool can be positioned according to the latest modification time in the comparison result, and the modified data content of the related operation can be searched, so that the problem analysis and positioning are facilitated.
Drawings
FIG. 1 is a flow chart illustrating a method for implementing network device configuration data difference self-identification according to the present invention;
fig. 2 is a schematic diagram of a system for implementing the network device configuration data difference self-recognition according to the present invention.
Detailed Description
The basic idea of the invention is: when the configuration data is updated, the management node and the NE update the timestamps of the NE; and the management node inquires the NE time stamp and compares the NE time stamp with the time stamp of the management node to determine the difference between the management node and the NE configuration data.
Specifically, when the user updates the configuration data, the management node or NE updates its own timestamp; correspondingly, when a communication link is established between the management node and the NE or the online configuration tool logs out the NE, the management node queries the NE timestamp, stores the NE timestamp in a network element Management Object (MO) of the management node, compares the timestamp in the network element MO with the timestamp in the main configuration set MO of the management node, and displays the comparison result to the user.
Here, the online configuration tool logging out of the NE means that the online configuration tool disconnects the link with the NE. The network element MO is positioned at the management node, corresponds to the NE one by one and is used for storing the network operation attribute of the NE, wherein the operation attribute comprises the IP address, the longitude and latitude information, the supplier, the user identification and the like of the NE; one main configuration set MO is hung under one network element MO, or one main configuration set MO and a plurality of standby configuration sets MO, and one configuration set MO is hung under one or a plurality of configuration object MOs. The management node distinguishes a main configuration set MO and a standby configuration set MO through main and standby marks; the network element MO, the configuration set MO and the configuration object MO are tree structures; the network element MO is a root node, the configuration set MO is a branch node, and the configuration object MO is a branch node or a leaf node. Reserving a certain field for storing NE time stamps in a network element MO, and reserving a certain field for storing management node time stamps in a configuration set MO; the configuration object MO in the configuration set MO is used for storing NE configuration data, the primary configuration set is used for synchronizing with NE, maintaining and displaying the current NE configuration data, and the standby configuration set can be switched to the primary configuration set when required by a user.
The invention is explained in detail below with reference to the figures and the specific embodiments.
As shown in fig. 1, the method for self-identifying the difference of the configuration data of the network device of the present invention specifically includes the following steps:
step 101, a user updates configuration data, and a management node or NE updates a timestamp of the management node or NE;
here, when the user updates the NE configuration data in the management node, the management node updates the time stamp. The updating of the NE configuration data in the management node by the user comprises: updating NE configuration data in a configuration set MO in a management node by a user; or the user carries out data reconstruction; or the user carries out MO switching of the configuration set; or the user performs data import.
Wherein, the NE configuration data in the management node is updated by the user, and the update time stamp of the management node comprises: the user modifies, deletes and adds NE configuration data in a configuration set MO under a network element MO of a management node, and the management node generates a timestamp; the generating the timestamp further comprises: the management node reads the current system time, converts the system time into microseconds, and then converts the microseconds into a new time sequence by utilizing the reference time, namely the timestamp; and storing the time stamp in the modified configuration set MO, and if the time stamp is in the modified configuration set MO, covering the original time stamp.
The user carries out data reconstruction, and the management node updating time stamp comprises: a user wants to check configuration data in NE, data reconstruction can be selected through a management node, the management node uploads the configuration data of the NE and an NE timestamp to the management node, a configuration set MO is newly added under a network element MO, the uploaded configuration data of the NE is stored in a configuration object MO under the newly added configuration set MO, the newly added configuration set MO is marked as a main configuration set MO, an original main configuration set MO is marked as a standby configuration set MO, and the NE timestamp is stored in the main configuration set MO and the network element MO; if only one configuration set MO exists under the network element MO, directly covering the original configuration set MO, and storing NE time stamps in the configuration set MO and the network element MO; if the network element MO has the time stamp, the time stamp of the original network element MO is covered;
the user carries out MO switching of the configuration set, and the management node updating time stamp comprises: if a main configuration set MO and a standby configuration set MO exist under a network element MO, and a management node allows switching of the main configuration set MO and the standby configuration set MO, a user selects configuration data under the standby configuration set MO as NE configuration data synchronized with NE in the future, the switching configuration set MO is selected by the management node, the standby configuration set MO selected by the user is marked as the main configuration set MO by the management node, the original main configuration set MO is marked as the standby configuration set MO, and a timestamp of the management node is a timestamp of the changed main configuration set MO.
The user conducts backup data import, and the management node updating time stamp comprises the following steps: a user selects to import local backup data through a management node, the management node imports the backup data, adds a configuration set MO under a network element MO, stores the backup data in a configuration object MO under the newly added configuration set MO, marks the newly added configuration set MO as a main configuration set MO, stores a backup data time stamp in the main configuration set MO, marks an original main configuration set MO as a standby configuration set MO, and stores the time stamp of the management node as the time stamp of the imported main configuration set, if only one configuration set MO exists under the network element MO, directly covers the original configuration set MO, stores the time stamp of the backup data in the configuration set MO, and the time stamp of the management node is the time stamp of the configuration set; the local backup data is the configuration data previously exported from the main configuration set MO, and is stored locally, where the local backup data includes a timestamp of the main configuration set MO, and when a user needs to backup the configuration data in the data, the local backup data can be selectively imported to the management node.
The NE updates the configuration data of the NE through an online configuration tool by a user, or updates the time stamp when the configuration data of the NE is updated through the management node. The online configuration tool updates configuration data of the NE, and the NE update timestamp includes: a user updates configuration data through an online configuration tool, the online configuration tool sends the configuration data to an NE, the NE receives the configuration data sent by the online configuration tool, covers the received configuration data with local configuration data, generates a timestamp and stores the timestamp locally, the configuration data can be updated parameters or parameter values or all parameters and parameter values, the timestamp generation method is the same as the timestamp generation method of a management node, and if the NE locally stores the timestamp, the original timestamp is covered; the management node updates configuration data of the NE, and the NE update timestamp comprises: the management node updates configuration data of the NE, namely the management node and the NE perform data synchronization, a user selects data synchronization, the management node synchronizes the configuration data and the timestamp in the main configuration set MO to the NE, the timestamp in the main configuration set MO is stored in the network element MO, the NE receives the configuration data sent by the management node to cover the original configuration data of the NE, receives the timestamp sent by the management node to cover the original timestamp of the NE.
Step 102, the management node inquires the NE timestamp and stores the NE timestamp in the network element MO;
here, when a user adds an operation attribute of an NE to a network element MO, a management node establishes a communication link with the NE according to a communication protocol and the operation attribute of the NE, and the management node queries an NE timestamp, where the communication protocol includes a Transmission Control Protocol (TCP)/internet Interconnection Protocol (IP), a User Datagram Protocol (UDP), a Simple Network Management Protocol (SNMP), a Common Management Information Protocol (CMIP), and the like; or, when the online configuration tool logs out of the NE, the online configuration tool sends a logout message to the NE, the NE receives the logout message and sends the logout message of the online configuration tool to the management node, and the management node queries the timestamp of the NE, where the querying includes: the management node sends a message for inquiring the NE time stamp to the NE, the NE returns the time stamp of the NE to the management node after receiving the message, and the management node saves the NE time stamp in a local network element MO.
And 103, the management node compares the time stamp in the network element MO with the time stamp in the main configuration set MO of the management node, and displays the comparison result.
Here, the management node compares the time stamp, i.e. the NE time stamp, in the network element MO with the time stamp, i.e. the time stamp of the management node itself in the main configuration set MO, and if the two are the same, it indicates that the configuration data of the management node and the NE are the same; if the two are different, the configuration data of the management node and the NE are different. The management node converts the NE time stamp and the time stamp of the management node into actual time, and displays a comparison result to a user, wherein the comparison result comprises the following steps: whether the NE timestamp is the same as the timestamp in the primary configuration set MO or not, and the latest modification time of the configuration data in the management node and the NE, namely the actual time after the timestamp conversion.
The process of converting the timestamp into the actual time by the management node is as follows: the management node converts the time stamp to microseconds using the reference time and then converts the microseconds to time.
When the timestamp in the network element MO is different from the timestamp in the main configuration set MO, the user may analyze the operation log according to the displayed result, thereby locating the problem, where the specific analysis process is:
the user displays the result, compares the latest modification time of the NE configuration data, namely the MO time of the network element, with the latest modification time of the management node, namely the MO time of the main configuration set, if the MO time of the network element is later, the latest update of the NE configuration data is updated by the online configuration tool, and the user can inquire the operation log of the online configuration tool according to the time and obtain the update record; if the time of the primary configuration set MO is later, it indicates that the latest update of the NE configuration data is updated synchronously by the management node, and the user can query the operation log of the management node according to the time to obtain the update record.
The invention also provides a system for self-identifying the difference of the configuration data of the network equipment, which comprises the following steps: a management node control module 201, an NE control module 202 and a management node data configuration module 203; wherein,
the management node data configuration module 203 is used for providing an interface for user operation, and notifying the management node control module 201 when a user updates configuration data;
the specific process comprises the following steps: when a user updates NE configuration data in a management node, a configuration data update message is sent to the management node control module 201; when a user selects data reconstruction, uploading configuration data of the NE and an NE timestamp, and sending data reconstruction information including the NE timestamp to the management node control module 201; when a user switches a configuration set MO, a standby configuration set MO selected by the user is marked as a primary, an original primary configuration set MO is marked as a standby, and a configuration set MO switching message is sent to the management node control module 201; when the user synchronizes with the NE data, the configuration data and the timestamp in the master configuration set MO are synchronized to the NE control module 202, and after the synchronization is successful, the data synchronization information including the timestamp of the master configuration set MO is sent to the management node control module 201; when a user imports data, importing backup data, and sending data import information containing a backup data timestamp to the management node control module 201;
a management node control module 201, configured to update the management node timestamp according to the notification of the management node data configuration module 203; establishing a communication link with the NE control module 202, or when the online configuration tool logs out the NE, querying the NE timestamp, comparing the NE timestamp with the timestamp in the master configuration set MO of the management node, that is, the difference of the management node timestamp, and displaying the comparison result to the user;
the NE control module 202 is configured to update the NE timestamp and store the NE timestamp when the online configuration tool updates the configuration data or the management node updates the configuration data; when the online configuration tool logs out the NE, the management node control module 201 is notified, and the notification includes: a message is sent to the management node control module 201 that the online configuration tool is logged out.
The management node control module 201 specifically includes: a management node timestamp management unit 2011, a management node timestamp comparison unit 2012, a difference maintenance unit 2013, and a management node communication unit 2014;
a management node timestamp management unit 2011, configured to update the timestamp of the management node according to the notification of the management node data configuration module 203;
the specific updating process is as follows: receiving a configuration data updating message, generating a time stamp and storing the time stamp in a configuration set MO updated by the configuration data; receiving data reconstruction information containing NE time stamps, and storing the NE time stamps in a main configuration set MO and a network element MO, or when the network element MO only has one configuration set MO, storing the NE time stamps in the configuration set MO and the network element MO; receiving a configuration set MO switching message, wherein the timestamp of a management node is the timestamp of the switched main configuration set MO; receiving data synchronization information containing a time stamp of a main configuration set MO, and synchronizing the time stamp of the main configuration set MO to a network element MO; receiving data import information containing a backup data time stamp, and storing the backup data time stamp in a main configuration set MO, or when a network element MO only has one configuration set MO, storing the backup data time stamp in the configuration set MO; the timestamp generation process is as follows: reading the current system time, converting the system time into microseconds, and converting the microseconds into a time sequence by utilizing the reference time, namely a timestamp;
the management node communication unit 2014 is used for establishing a communication link with the NE control module 202 through a communication protocol according to the operation attribute when the user adds the operation attribute of the NE to the network element MO, performing information interaction with the NE as the communication link between the management node and the NE, and notifying the management node timestamp comparison unit 2012 that a message about establishing the communication link is to be sent to the management node timestamp comparison unit 2012;
a management node timestamp comparing unit 2012, configured to receive a message for establishing a communication link, or receive a message posted by an online configuration tool and sent by the NE control module 202, query an NE timestamp, and store the NE timestamp in the network element MO; the query includes sending a message for querying the NE timestamp to the NE control module 202, and receiving the timestamp returned by the NE control module 202;
comparing the time stamp in the network element MO, that is, the NE time stamp with the time stamp in the master configuration set MO, that is, the management node time stamp, converting the NE time stamp and the management node time stamp into time, and sending the comparison result to the difference maintenance unit 2013; the comparison result comprises the similarities and differences between the NE timestamp and the management node timestamp and the latest modification time of the management node configuration data, namely the time after the conversion of the management node timestamp, and the latest modification time of the NE configuration data, namely the time after the conversion of the NE timestamp; the conversion comprises the following steps: converting the timestamp into microseconds by using the reference time, and then converting the microseconds into time;
and the difference maintenance unit 2013 is used for displaying the comparison result.
The NE control module 202 specifically includes: NE communication unit 2021, NE timestamp management unit 2022, NE data configuration unit 2023;
the NE communication unit 2021 is configured to establish a communication link with the management node according to a communication protocol, serve as the communication link between the NE and the management node, and perform information interaction with the management node;
the NE data configuration unit 2023 receives the configuration data sent by the online configuration tool, and sends a configuration data update message to the NE timestamp management unit 2022; receiving a logout message sent by the online configuration tool, and sending the logout message of the online configuration tool to the management node timestamp comparison unit 2012 through the NE communication unit 2021 and the management node communication unit 2014; receiving the configuration data and the timestamp sent by the management node data configuration module 203, and sending a management node synchronization message including the timestamp to the NE timestamp management unit 2022;
the NE timestamp management unit 2022 is configured to receive a configuration data update message sent by the NE data configuration unit 2023, and update the timestamp, where the update is: generating and storing a timestamp, and if the original timestamp is generated, covering the original timestamp; receiving and storing the time stamp sent by the NE data configuration unit 2023, and if the time stamp is originally present, covering the original time stamp; and receiving a message for inquiring the NE timestamp sent by the management node control module 201, and returning the NE timestamp.
The above description is only exemplary of the present invention and should not be taken as limiting the scope of the present invention, and any modifications, equivalents, improvements, etc. that are within the spirit and principle of the present invention should be included in the present invention.
Claims (7)
1. A method for self-identifying differences of configuration data of network equipment is characterized by comprising the following steps:
when the configuration data is updated, the management node and the NE update the timestamps of the NE;
the management node establishes a communication link with the NE, or the online configuration tool logs out the NE, after the NE sends the information logged out by the online configuration tool to the management node, the management node queries the NE timestamp and stores the NE timestamp in the local network element MO, and compares the stored NE timestamp with the self timestamp in the main configuration set MO to determine the difference of the management node and the NE configuration data.
2. The method of claim 1, wherein the updating of the timestamp of the management node when the configuration data is updated comprises:
updating configuration data under the configuration set management object MO in the management node, and generating a timestamp and storing the timestamp in the updated configuration set MO by the management node; or,
when NE data reconstruction is carried out, the NE timestamp is uploaded by the management node and is stored in the main configuration set MO and the network element MO, and if only one configuration set MO exists, the NE timestamp is stored in the configuration set MO and the network element MO; or,
when carrying out data synchronization with NE, the management node synchronizes the time stamp in the main configuration set MO to the network element object MO; or,
if the master-standby configuration set MO exists, when the master-standby configuration set MO is switched, the timestamp of the management node is the timestamp of the switched master-standby configuration set MO; or,
when the backup data is imported, the management node imports the backup data timestamp and stores the timestamp in the main configuration set MO, and if only one configuration set MO exists, the timestamp is stored in the configuration set MO.
3. The method of claim 1, wherein updating the timestamp of the NE itself at the time of the configuration data update comprises:
updating configuration data by the online configuration tool, and generating and storing a time stamp by the NE; or the management node updates the configuration data and synchronizes with the NE data, and the NE receives and stores the timestamp synchronized by the management node.
4. A system for differential self-identification of network device configuration data, the system comprising: the management node comprises a management node data configuration module, a management node control module and an NE control module;
the management node data configuration module informs the management node control module when a user updates configuration data;
the management node control module is used for updating the timestamp of the management node control module according to the notification of the management node data configuration module; inquiring the NE timestamp, and comparing the NE timestamp with the management node timestamp;
the NE control module updates the time stamp of the NE control module when the user updates the configuration data;
the NE control module is further used for informing the management node control module when the online configuration tool logs out;
correspondingly, the management node control module is also used for establishing a communication link with the NE; or when the online configuration tool logs out, the NE timestamp is inquired and stored in the local network element MO, and the network element MO and the timestamp in the main configuration set MO are compared.
5. The system of claim 4, wherein said management node control module comprises: the system comprises a management node timestamp management unit, a management node communication unit and a difference maintenance unit;
the management node timestamp management unit is used for updating the timestamp of the management node according to the notification of the management node data configuration module;
the management node communication unit is used for establishing a communication link with the NE, carrying out information interaction and informing the management node timestamp comparison unit;
the management node timestamp comparison unit is used for inquiring the NE timestamp and storing the NE timestamp in the local network element MO after the management node communication unit establishes a communication link with the NE or the online configuration tool logs out the NE; comparing the time stamps in the network element MO and the main configuration set MO, converting the time stamps in the network element MO and the main configuration set MO into time, and sending the comparison result to a difference maintenance unit;
and the difference maintenance unit is used for displaying the comparison result.
6. The system of claim 5, wherein the NE control module comprises: the system comprises an NE communication unit, an NE timestamp management unit and an NE data configuration unit;
the NE communication unit is used for establishing a communication link with the management node and carrying out information interaction;
the NE data configuration unit is used for receiving the configuration data sent by the online configuration tool and informing the NE timestamp management unit; receiving configuration data and a timestamp synchronized by a management node, and sending a message synchronized by the management node containing the timestamp to an NE timestamp management unit; receiving a logout message sent by an online configuration tool, and informing a management node timestamp management unit through a management node communication unit;
the NE timestamp management unit is used for updating the timestamp of the NE timestamp when the online configuration tool sends the configuration data; and receiving the timestamp synchronized by the management node, and storing the timestamp to the local.
7. The system according to claim 5, wherein the management node timestamp management unit is specifically configured to receive a configuration data update message sent by the management node configuration module, generate a timestamp, and store the timestamp in a configuration set MO for configuration data update; receiving data reconstruction information containing NE time stamps, storing the NE time stamps in a main configuration set MO and a network element MO, and if the network element MO only has one configuration set MO, storing the NE time stamps in the configuration set MO and the network element MO; if the master-standby configuration set MO exists, switching the master-standby configuration set MO, receiving a message of switching the master-standby configuration set MO, wherein the timestamp of the management node is the timestamp of the switched master-standby configuration set MO; receiving data synchronization information containing a timestamp of a main configuration set MO, and synchronizing the timestamp in the main configuration set MO to a network element MO; and receiving data import information containing the backup data time stamp, storing the backup data time stamp in the main configuration set MO, and if the network element MO only has one configuration set, storing the backup data time stamp in the configuration set MO.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010504407.XA CN102447542B (en) | 2010-10-09 | 2010-10-09 | Difference self-recognizing method and system for configuration data of network equipment |
| PCT/CN2011/076778 WO2012045250A1 (en) | 2010-10-09 | 2011-07-01 | Method and system for network equipment configuration data difference self-recognization |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010504407.XA CN102447542B (en) | 2010-10-09 | 2010-10-09 | Difference self-recognizing method and system for configuration data of network equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102447542A CN102447542A (en) | 2012-05-09 |
| CN102447542B true CN102447542B (en) | 2014-12-10 |
Family
ID=45927212
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010504407.XA Active CN102447542B (en) | 2010-10-09 | 2010-10-09 | Difference self-recognizing method and system for configuration data of network equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102447542B (en) |
| WO (1) | WO2012045250A1 (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103297529B (en) * | 2013-06-06 | 2016-01-20 | 浙江大学 | Based on the tree-type structure data synchronous method of timestamp |
| CN104243515A (en) * | 2013-06-13 | 2014-12-24 | 中兴通讯股份有限公司 | Method and device for processing configuration information |
| CN107528703B (en) * | 2016-06-20 | 2021-09-03 | 阿里巴巴集团控股有限公司 | Method and equipment for managing node equipment in distributed system |
| CN108494828B (en) * | 2018-02-26 | 2021-04-16 | 网易（杭州）网络有限公司 | Node data updating method, medium, device and computing equipment |
| CN110955615B (en) * | 2019-10-23 | 2021-11-09 | 武汉光庭信息技术股份有限公司 | TBox internal data protection method and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1677887A (en) * | 2005-02-01 | 2005-10-05 | 北京北方烽火科技有限公司 | N+1 duplicates data real-time synchronising method |
| CN101110706A (en) * | 2007-07-23 | 2008-01-23 | 中兴通讯股份有限公司 | Configuration data synchronization method |
| CN101212342A (en) * | 2006-12-27 | 2008-07-02 | 大唐移动通信设备有限公司 | Multi-version network element network management method |
| CN101686431A (en) * | 2008-09-22 | 2010-03-31 | 中兴通讯股份有限公司 | Synchronous processing method and device |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100370745C (en) * | 2004-09-27 | 2008-02-20 | 华为技术有限公司 | Method and network management system for realizing intelligent net element cross information synchronization |
| JP4150037B2 (en) * | 2005-09-30 | 2008-09-17 | 株式会社東芝 | Time stamp acquisition system, time stamp acquisition device, time stamp acquisition program, and time stamp acquisition method |
-
2010
- 2010-10-09 CN CN201010504407.XA patent/CN102447542B/en active Active
-
2011
- 2011-07-01 WO PCT/CN2011/076778 patent/WO2012045250A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1677887A (en) * | 2005-02-01 | 2005-10-05 | 北京北方烽火科技有限公司 | N+1 duplicates data real-time synchronising method |
| CN101212342A (en) * | 2006-12-27 | 2008-07-02 | 大唐移动通信设备有限公司 | Multi-version network element network management method |
| CN101110706A (en) * | 2007-07-23 | 2008-01-23 | 中兴通讯股份有限公司 | Configuration data synchronization method |
| CN101686431A (en) * | 2008-09-22 | 2010-03-31 | 中兴通讯股份有限公司 | Synchronous processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102447542A (en) | 2012-05-09 |
| WO2012045250A1 (en) | 2012-04-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101459534B (en) | Network topology collecting method for tree shaped network and network equipment | |
| CN103001806B (en) | For the distributed O&M monitoring system of IT system | |
| CN102447542B (en) | Difference self-recognizing method and system for configuration data of network equipment | |
| CN103248512A (en) | Method and system for generating topological structure of application layer in communication network | |
| CN101242302A (en) | Data synchronization method, device and system | |
| CN102833113B (en) | Substation Ethernet communication network monitoring method and system | |
| CN103905251A (en) | Network topology obtaining method and device | |
| CN115314392A (en) | Automatic network topology generation system and method based on network equipment resource discovery algorithm | |
| CN104243589A (en) | Operation service platform system and method based on Big Dipper RDSS/RNSS | |
| US20240113944A1 (en) | Determining an organizational level network topology | |
| CN110557292A (en) | Topological graph obtaining method, device and equipment based on distributed routing Internet of things | |
| US20080301143A1 (en) | Automatic Update System and Method for Using a Meta Mib | |
| CN102082652B (en) | Method, device and system for acquiring network clock topological structure | |
| CN103888289B (en) | Gateway control method, gateway, management and control device and system | |
| CN110740355A (en) | Equipment monitoring method and device, electronic equipment and storage medium | |
| CN103108347B (en) | The associated alarm method and device of cable network and wireless network | |
| CN102104490B (en) | Comprehensive network management system for railway communication network | |
| CN111010226A (en) | Optical fiber testing system based on cloud computing | |
| CN102811144B (en) | NMS topological discovery performance testing system and method | |
| Gopalakrishnan et al. | Applications of emerging communication trends in automation | |
| CN105681105A (en) | Network element configuration information synchronization method and device | |
| CN101316195B (en) | Method and system for implementing configuration consistency of monitoring system | |
| CN100515111C (en) | UTRAN monitoring instrument, monitoring system and monitoring method | |
| CN106603418B (en) | Network topology updating method and traffic analysis equipment | |
| CN111466134B (en) | Method and arrangement for allocating communication resources in a communication network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |