CN108958758A - A kind of management information bank MIB data managing method and device - Google Patents
A kind of management information bank MIB data managing method and device Download PDFInfo
- Publication number
- CN108958758A CN108958758A CN201710369247.4A CN201710369247A CN108958758A CN 108958758 A CN108958758 A CN 108958758A CN 201710369247 A CN201710369247 A CN 201710369247A CN 108958758 A CN108958758 A CN 108958758A
- Authority
- CN
- China
- Prior art keywords
- data
- data model
- node
- nodal properties
- object node
- 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.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a kind of management information bank MIB data managing method and devices, to solve the problems, such as that MIB data correctness existing in the prior art and compatibility are lower.It include: the corresponding configuration file of version to be updated for obtaining target device；Create corresponding first data model of configuration file；Determine the first object node having differences in nodal properties data between the first data model the second data model corresponding with the original version of the target device in MIB database；When the constraint relationship in determining the first data model in the corresponding value of nodal properties data of first object node is unsatisfactory for the constraint relationship being pre-configured, the nodal properties data of first object node in the first data model are modified, or delete the nodal properties data of first object node in the first data model；Modified first data model is imported into the corresponding configuration file of version to be updated.
Description
Technical field
The present invention relates to information technology (English: Information Technology, abbreviation: IT) fields, in particular to
A kind of management information bank (English: Management Information Base, referred to as: MIB) data managing method and device.
Background technique
Communication equipment in existing network, generally using Simple Network Management Protocol (English: Simple Network
Management Protocol, referred to as: SNMP) be managed.The network management model of SNMP includes following crucial member
Element: manager (Manager), succedaneum (Agent), MIB, SNMP.Manager is exactly the network of an operation on a workstation
Management software, it issues operational order to Agent by snmp protocol, implements the monitoring and control to resources various in network；
Agent typically resides in the program in communication equipment, it responds the operation requests of Manager, executes management function.MIB is
Manager and Agent realizes the data medium of management function, is specific a hierarchy, structuring, and by all managed objects
The set of composition.Manager is ordered and is operated to MIB by reading (GET) order and setting (SET), to realize to logical
Believe the control of equipment.
For function is complicated, be mutually related all kinds of communication equipments, huge MIB data have certain complexity in management
Property, especially when communications device functions are changed and extended on a large scale, how can guarantee the correctness and compatibility of MIB data
Property, it is a problem in need of consideration.MIB data in one communication equipment include the section of several nodes of the communication equipment
Dot characteristics data, wherein node is used to describe the function of the communication equipment, such as transmission power, dominant frequency, load.The section of node
Dot characteristics data include parameter value, Parameter Value Type, the object identifier (English: Object identifier, letter of the node
Claim: OID) etc..Existing MIB management method mainly has based on the management method for comparing tool.
Specifically, comparing tool when being updated the MIB data of communication equipment a certain in MIB by comparing tool
The original MIB data of the communication equipment stored in the MIB data and MIB to be updated of the communication equipment are compared,
When the case where nodal properties data for occurring same node point between MIB data and original MIB data to be updated have differences, by
User by the node that the original MIB data interior joint performance data of the communication equipment has differences be revised as the communication equipment to
Corresponding nodal properties data in the MIB data of update.Therefore, by based on compare the management method of tool to MIB data into
When row management, it is right in MIB data to be updated to be only revised as the node that original MIB data interior joint performance data has differences
The nodal properties data answered cause the correctness of MIB data and compatibility lower.
Summary of the invention
The embodiment of the present invention provides a kind of management information bank MIB data managing method and device, to solve the prior art
When middle presence is managed MIB data, the correctness and the lower problem of compatibility of MIB data.
In a first aspect, the embodiment of the invention provides a kind of management information bank MIB data managing methods, comprising:
The corresponding configuration file of version to be updated of management equipment acquisition target device；The configuration file includes to be updated
Several nodes nodal properties data；
The management equipment creates corresponding first data model of the configuration file；First data model includes institute
State the node of each node in the nodal properties data and several described nodes of several nodes in configuration file
The constraint relationship between performance data and the nodal properties data of other nodes in several described nodes in value；
The management equipment determines the original version of the target device in first data model and MIB database
The first object node being had differences in nodal properties data between corresponding second data model；
In the corresponding value of nodal properties data for determining first object node described in first data model
On the constraint relationship when being unsatisfactory for the constraint relationship being pre-configured, the management equipment modifies described in first data model the
The nodal properties data of one destination node, or delete the nodal properties of first object node described in first data model
Data；
Modified first data model is imported into the corresponding configuration of the version to be updated by the management equipment
In file.
Management equipment obtains the corresponding configuration file of version to be updated of target device in the embodiment of the present invention, and creates institute
State corresponding first data model of configuration file.Then the target in first data model and MIB database is determined
The first object node being had differences in nodal properties data between corresponding second data model of the original version of equipment.?
Determine that the constraint in the corresponding value of the nodal properties data of first object node described in first data model is closed
When system is unsatisfactory for the constraint relationship being pre-configured, the management equipment modifies first object node described in first data model
Nodal properties data, or delete the nodal properties data of first object node described in first data model, finally
Modified first data model is imported into the corresponding configuration file of the version to be updated., compared with prior art
In when being managed by comparing tool to MIB data, only for the node that nodal properties data have differences, according to node spy
The method that the difference condition of property data modifies to the nodal properties data of the node, in the embodiment of the present invention, management equipment
It is special to consider the node of each node and other nodes in several described nodes in several nodes of the target device
Property data between the constraint relationship in value, then the nodal properties data of several nodes of the target device are carried out
Processing, to improve the correctness and compatibility of the MIB data of the target device.
With reference to first aspect, in the first possible embodiment of first aspect, institute is determined in the management equipment
It states and is being saved between the first data model the second data model corresponding with the original version of the target device in MIB database
After the first object node having differences in dot characteristics data, the management equipment is modified described in first data model
The nodal properties data of first object node, or delete the node spy of first object node described in first data model
Before property data, further includes:
It is prewired that the management equipment determines whether the format that the nodal properties data of the first object node use meets
The format for the nodal properties data set, when definitive result is to be unsatisfactory for, the node data for correcting the first object node is special
The format of property.
With reference to first aspect or the first possible embodiment of first aspect, second in first aspect are possible
In embodiment, the original of the target device in first data model and MIB database is determined in the management equipment
After the first object node being had differences in nodal properties data between corresponding second data model of beginning version, the pipe
The nodal properties data of first object node described in the first data model described in apparatus modifications are managed, or delete first number
Before the nodal properties data of first object node described in model, further includes:
Whether the management equipment determines the nodal properties data interior joint value of the first object node preset
In value range, when being determined as no, the node value in the nodal properties data of the first object node is modified, so that institute
The nodal properties data interior joint value of first object node is stated in the preset value range.
With reference to first aspect, in the third possible embodiment of first aspect, nodal properties data include object
Identifier OID, after corresponding first data model of management equipment creation configuration file, the management equipment modifies institute
The nodal properties data of first object node described in the first data model are stated, or are deleted described in first data model
Before the nodal properties data of first object node, further includes:
When the management equipment determines two nodes identical including OID in first data model, modification described two
The OID of one of node in a node, so that the OID of modified described two nodes is different.
With reference to first aspect, in the 4th kind of possible embodiment of first aspect, nodal properties data include object
Identifier OID determines the original of first data model and the target device in MIB database in the management equipment
After the first object node being had differences in nodal properties data between corresponding second data model of version, the management
Before modified first data model is imported into the corresponding configuration file of the version to be updated by equipment, the side
Method further include:
The management equipment determines the OID of first object node described in first data model, and in the MIB number
OID according to the other nodes in addition to the first object node stored in library is identical；
The management equipment modifies the OID of first object node described in first data model, so that modified
The OID of the first object node and the other sections in addition to the first object node stored in the MIB database
The OID of point is all different.
Second aspect, the embodiment of the invention provides a kind of management information bank MIB data administrator, described device applications
In management equipment, comprising:
Module is obtained, for obtaining the corresponding configuration file of version to be updated of target device；The configuration file includes
The nodal properties data of several nodes to be updated；
Creation module, corresponding first data model of the configuration file obtained for creating the acquisition module；Institute
State nodal properties data that the first data model includes several nodes in the configuration file and it is described several
In node between the nodal properties data of each node and the nodal properties data of other nodes in several described nodes
The constraint relationship in value；
Determining module, the institute in first data model and MIB database for determining the creation module creation
State the first object having differences in nodal properties data between corresponding second data model of original version of target device
Node；
Modified module, for the institute in first data model that the determining module determines the creation module creation
It states the constraint relationship in the corresponding value of nodal properties data of first object node and is unsatisfactory for the constraint relationship being pre-configured
When, the nodal properties data of first object node described in first data model are modified, or delete first data
The nodal properties data of first object node described in model；
Update module, for modified first data model of the modified module to be imported into the version to be updated
In this corresponding configuration file.
In conjunction with second aspect, in the first possible embodiment of second aspect, the determining module is also used to
Determine first data model of the creation module creation and the original version pair of the target device in MIB database
After the first object node being had differences in nodal properties data between the second data model answered, in the modified module
The nodal properties data of first object node described in first data model are modified, or delete first data model
Described in first object node nodal properties data before, determine the first object node nodal properties data use
Whether format meets the format of the nodal properties data of pre-configuration；
The modified module is also used to correct the first object when the determining module definitive result is to be unsatisfactory for
The format of the node data characteristic of node.
In conjunction with the possible embodiment of the first of second aspect or second aspect, second in second aspect is possible
In embodiment, the determining module is also used in first data model and MIB number for determining the creation module creation
It is had differences in nodal properties data according between corresponding second data model of the original version of the target device in library
First object node after, the node that the modified module modifies first object node described in first data model is special
Property data, or before deleting the nodal properties data of first object node described in first data model, determine described in
Whether the nodal properties data interior joint value of first object node is in preset value range；
The modified module is also used to modify the section of the first object node when the determining module is determined as no
Node value in dot characteristics data, so that the nodal properties data interior joint value of the first object node is described default
Value range in.
In conjunction with second aspect, in the third possible embodiment of second aspect, nodal properties data include object
Identifier OID, the determining module are also used to create corresponding first data model of the configuration file in the creation module
Later, the modified module modifies the nodal properties data of first object node described in first data model, or deletes
Before the nodal properties data of first object node described in first data model, the creation module creation is determined
It include identical two nodes of OID in first data model；
The modified module is also used to determine the first data mould of the creation module creation in the determining module
In type when two nodes identical including OID, the OID of one of node in described two nodes is modified, so that modified
The OID of described two nodes is different.
In conjunction with second aspect, in the 4th kind of possible embodiment of second aspect, nodal properties data include object
Identifier OID, the determining module are also used in first data model and MIB number for determining the creation module creation
It is had differences in nodal properties data according between corresponding second data model of the original version of the target device in library
First object node after, modified first data model of the modified module is imported into institute by the update module
Before stating in the corresponding configuration file of version to be updated, described in first data model that determines creation module creation
The OID of first object node, with other nodes in addition to the first object node for being stored in the MIB database
OID is identical；
The modified module is also used to determine the first data mould of the creation module creation in the determining module
The OID of first object node described in type, with its in addition to the first object node stored in the MIB database
When the OID of its node is identical, the OID of first object node described in first data model is modified, so that modified institute
State the OID of first object node and the other nodes in addition to the first object node stored in the MIB database
OID be all different.
Management equipment obtains the corresponding configuration file of version to be updated of target device in the embodiment of the present invention, and creates institute
State corresponding first data model of configuration file.Then the target in first data model and MIB database is determined
The first object node being had differences in nodal properties data between corresponding second data model of the original version of equipment.?
Determine that the constraint in the corresponding value of the nodal properties data of first object node described in first data model is closed
When system is unsatisfactory for the constraint relationship being pre-configured, the management equipment modifies first object node described in first data model
Nodal properties data, or delete the nodal properties data of first object node described in first data model, finally
Modified first data model is imported into the corresponding configuration file of the version to be updated., compared with prior art
In when being managed by comparing tool to MIB data, only for the node that nodal properties data have differences, according to node spy
The method that the difference condition of property data modifies to the nodal properties data of the node, in the embodiment of the present invention, management equipment
It is special to consider the node of each node and other nodes in several described nodes in several nodes of the target device
Property data between the constraint relationship in value, then the nodal properties data of several nodes of the target device are carried out
Processing, to improve the correctness and compatibility of the MIB data of the target device.
Detailed description of the invention
Fig. 1 is a kind of flow chart of MIB data managing method provided in an embodiment of the present invention；
Fig. 2 is a kind of flow chart of MIB data managing method provided in an embodiment of the present invention；
Fig. 3 is a kind of flow chart of model modification method provided in an embodiment of the present invention；
Fig. 4 is a kind of flow chart of MIB data managing method provided in an embodiment of the present invention；
Fig. 5 is a kind of structural schematic diagram of MIB data administrator provided in an embodiment of the present invention.
Specific embodiment
To make the objectives, technical solutions, and advantages of the present invention clearer, below in conjunction with attached drawing to the present invention make into
It is described in detail to one step, it is clear that described embodiments are only a part of the embodiments of the present invention, rather than whole implementation
Example.Based on the embodiments of the present invention, obtained by those of ordinary skill in the art without making creative efforts
All other embodiment, shall fall within the protection scope of the present invention.
The embodiment of the present invention provide a kind of management information bank (English: Management Information Base, referred to as:
MIB) data managing method and device, to solve it is existing in the prior art MIB data are managed when, MIB data
Correctness and compatible lower problem.Wherein, method and apparatus are based on the same inventive concept, due to method and device
The principle solved the problems, such as is similar, therefore the implementation of apparatus and method can be with cross-reference, and overlaps will not be repeated.
The embodiment of the present invention can be applied to MIB management system, as shown in Figure 1, the MIB management system includes that management is set
Standby and MIB database.
Wherein, MIB database is used to save the data model of several equipment.Data model includes the corresponding configuration of equipment
The nodal properties data of each node and institute in the nodal properties data of several nodes and several described nodes in file
State the constraint relationship between the nodal properties data of other nodes in several nodes in value.
It wherein, include at least one tables of data in the configuration file of each equipment for saving several sections of the equipment
The nodal properties data of point.
For example, including that antenna array planning table and antenna install planning table in configuration file, wherein in antenna array planning table
Antenna radical node and antenna installation planning table in antenna channels numbered node there are the constraint relationship, the constraint relationship is value
Range is identical, and there are the constraint relationship, the constraint relationship is radio frequency unit for board type of hardware node and radio frequency unit access board type
The value for accessing board type must be included within board type of hardware value range.
The management equipment is used for the corresponding data model of configuration file and MIB number according to target device version to be updated
It is deposited in nodal properties data according between the corresponding data model of configuration file of the original version of the target device in library
Difference update MIB database in target device data model.
In order to enable the embodiment of the present invention is more easily understood, in the following, first to involved in the embodiment of the present invention
Some descriptions are illustrated, these explanations are not construed as the restriction to protection scope of the presently claimed invention.
Node is used to describe the function of the communication equipment, such as transmission power, dominant frequency, load.The nodal properties number of node
According to the parameter value, Parameter Value Type, object identifier (English: Object identifier, abbreviation: OID) for including the node
Deng.
OID is the label added to distinguish the object in entirety, in order to which destination node can be found in MIB, I
Need for each node distribute a unique identification number.One OID must be kept uniquely in a MIB, i.e., and one
The OID of same node point is identical in MIB, and the OID of different nodes is different, as the OID of the node A in MIB in all devices must phase
Together, and node A and the OID of other nodes are all different.
The preferred embodiment of the present invention is described in detail with reference to the accompanying drawing.
As shown in fig.2, being a kind of flow chart of MIB data managing method provided in an embodiment of the present invention, the method
It updates, can specifically include as follows including data acquisition, model creation, difference determination, Modifying model and data:
Data acquisition: S201, management equipment obtain the corresponding configuration file of version to be updated of target device.
The configuration file includes the nodal properties data of several nodes to be updated.
Model creation: S202, the management equipment create corresponding first data model of the configuration file.
First data model include several nodes in the configuration file nodal properties data and
The nodal properties of the nodal properties data of each node and other nodes in several described nodes in several described nodes
The constraint relationship between data in value.
Wherein, the management equipment creates the corresponding first data mould of the configuration file according to the characteristic of target device
Type.In the first data model, the data model of a node further includes in addition to including nodal properties data, set membership
There are the mark of the node of the constraint relationship and corresponding the constraint relationships in value with the nodal properties data of the node.
Optionally, user summarizes the constraint relationship between the nodal properties data of each node in value and is configured to institute
It states in management equipment, so that the constraint relationship creation for each node that the management equipment can be summarized according to user is described to more
The data model of each node in several new nodes, the management equipment can also create the configuration by other means
The data model of each node, the embodiment of the present invention are not specifically limited herein in file.
Difference determines: S203, and the management equipment determines the target in first data model and MIB database
The first object node being had differences in nodal properties data between corresponding second data model of the original version of equipment.
Wherein, the first object node is any node in first data model.Existing difference can be
Nodal properties data difference such as value difference etc., or set membership difference has such as increased newly new under node or existing node
Increased child node etc., or association the difference i.e. data model of certain node in include there are the constraint relationships with the node
Node exists different, or other differences, the embodiment of the present invention are not specifically limited herein.
Modifying model: S204, in the nodal properties data for determining first object node described in first data model
When the constraint relationship in the corresponding value is unsatisfactory for the constraint relationship being pre-configured, management equipment modification first number
According to the nodal properties data of first object node described in model, or delete first object described in first data model
The nodal properties data of node.
Data update: modified first data model imported into described to be updated by S205, the management equipment
In the corresponding configuration file of version.
Optionally, when data update, the management equipment can also save modified first data model
In MIB database.
Management equipment obtains the corresponding configuration file of version to be updated of target device in the embodiment of the present invention, and creates institute
State corresponding first data model of configuration file.Then the target in first data model and MIB database is determined
The first object node being had differences in nodal properties data between corresponding second data model of the original version of equipment.?
Determine that the constraint in the corresponding value of the nodal properties data of first object node described in first data model is closed
When system is unsatisfactory for the constraint relationship being pre-configured, the management equipment modifies first object node described in first data model
Nodal properties data, or delete the nodal properties data of first object node described in first data model, finally
Modified first data model is imported into the corresponding configuration file of the version to be updated., compared with prior art
In when being managed by comparing tool to MIB data, only for the node that nodal properties data have differences, according to node spy
The method that the difference condition of property data modifies to the nodal properties data of the node, in the embodiment of the present invention, management equipment
It is special to consider the node of each node and other nodes in several described nodes in several nodes of the target device
Property data between the constraint relationship in value, then the nodal properties data of several nodes of the target device are carried out
Processing, to improve the correctness and compatibility of the MIB data of the target device.
Optionally, difference determines to include variance analysis and service filter, in which:
Variance analysis: the management equipment determines the target device in first data model and MIB database
Corresponding second data model of original version between at least one node for being had differences in nodal properties data.
The management equipment can carry out variance analysis according to demand, if the demand is the conventional upgrading of equipment, institute
It states management equipment and only needs to carry out variance analysis between identical equipment different editions, i.e., it is the version to be updated of target device is corresponding
Configuration file in several nodes nodal properties data configuration file corresponding with the original version of target device in MIB in
The nodal properties data of several nodes are compared, and obtain the node that nodal properties data have differences.
If the demand is related to multi-product, if the characteristic of plurality of devices pulls together, then phase in multiple target devices in MIB
Nodal properties data with node are compared, and obtain the node that nodal properties data have differences.
Service filter: the management equipment according to the preconfigured nodal information for needing to correct nodal properties data, from
The first object node for needing to correct nodal properties data is determined at least one described node.
Specifically, the management equipment executes service filter, the filtering of the pre-configuration based on the filtering rule of pre-configuration
Rule is the preconfigured nodal information for needing to correct nodal properties data, in described several nodes to be updated,
At least one section being had differences with the nodal properties data of the node of the target device stored in management information bank MIB
Point retains the node for needing to correct nodal properties data, filters out the node for not needing amendment nodal properties data.It is described prewired
The filtering rule set be not it is unalterable, user, which can according to need, reconfigures filtering rule.
Wherein, when filtering out the node for not needing amendment nodal properties data, the section of the node Yu other nodes is deleted
Dot characteristics data are in the constraint relationship present on value, but there are other nodes of the constraint relationship with the node for reservation.
The process now determined to difference is illustrated: management equipment is by by the first data model and MIB database
In corresponding second data model of original version of target device be compared, the first data model of discovery increases 3 sections
The temperature of point, respectively CPU work, the power consumption of CPU, the manufacturer of CPU.And the function of temperature, CPU that user only needs CPU to work
Consume two nodes, therefore user is pre-configured with that need to correct the nodal information of nodal properties data be CPU work in management equipment
Temperature, the power consumption of CPU of work, so that management equipment is believed according to according to the preconfigured node for needing to correct nodal properties data
Breath determines that the first object node for needing to correct nodal properties data is the temperature of CPU work, the power consumption of CPU.
Optionally, Modifying model includes business verification, business is corrected and business matching, in which:
After difference determines, business verification is executed.Whether node of the specific verification of business verification after difference determines
It meets the requirements, if verification is not met, business correction and business matching is carried out, as shown in figure 3, the process of Modifying model is specific
Are as follows:
Business verification: S301, section of the management equipment to the first object node in first data model
Dot characteristics data carry out business verification, and judge whether the result of the business verification mistake occurs；If so, executing step S302
Carry out business correction；If it is not, executing step S303 carries out business matching.
The business verification can be at least one of following four verification:
Verification one: determine whether the format of the nodal properties data use of the first object node meets the section of pre-configuration
The special data format of point.
Wherein, the node spy data format can be binary system, octal system, hexadecimal etc., the node spy number
According to format or three bytes, five bytes etc., the embodiment of the present invention is not specifically limited herein.
The node spy data format of the pre-configuration can be safeguarded according to the product operation of the target device (English:
Operation&Maintenance, referred to as: OM) frame requirements are pre-configured with.
Verification two: determine the nodal properties data interior joint value of the first object node whether in preset value model
In enclosing.
Wherein, the preset value range can be pre-configured with according to the OM frame requirements of the target device.
Verification three: determine the constraint relationship in the corresponding value of the nodal properties data of the first object node not
Meet the constraint relationship being pre-configured.
For example, first object node is that radio frequency unit accesses board type, board type of hardware node in the first data model
With radio frequency unit access board type there are the constraint relationship, the constraint relationship is that the value of radio frequency unit access board type must be included in
Within board type of hardware value range, whether management equipment determines the value of radio frequency unit access board type in plate in verification three
Within card type of hardware value range.
Optionally, the constraint relationship of the pre-configuration can be matched in advance according to the OM frame requirements of the target device
It sets.
It examines four: determining whether the OID of the first object node is correct.
Specifically, the management equipment determine first object node described in first data model OID whether with
The OID of first object node described in corresponding second data model of the original version of the target device in MIB database
It is identical, and the OID of first object node described in first data model whether with the target device in MIB database
Corresponding second data model of original version in the OID of other nodes in addition to the first object node be all different.
Optionally, the management equipment can also carry out other types of business verification for first data model,
Repeated detection is such as designed, that is, determines that, with the presence or absence of identical node etc. in first data model, business verifies interior
Appearance can be configured according to the function of target device, and the embodiment of the present invention is not specifically limited herein.
Verification rule in business checking procedure based on pre-configuration is to the first object in first data model
The nodal properties data of node are verified, the verification rule of the pre-configuration be not it is unalterable, user can basis
It needs to reconfigure verification rule.
Business correction is carried out when the result of business verification indicates mistake.
Business is corrected: S302, and the management equipment carries out business to the nodal properties data of the first object node and entangles
Just.
Specifically, determining the first object node when result of the verification one in business verification indicates mistake
When the format that nodal properties data use is unsatisfactory for the node spy's data format being pre-configured, the management equipment amendment described first
The format of the node data characteristic of destination node.
When the result of verification two in business verification indicates mistake, that is, determine the nodal properties of the first object node
When data interior joint value is not in preset value range, the management equipment corrects the number of nodes of the first object node
According to characteristic interior joint value, so that the node data characteristic interior joint value of the first object node is in the preset value
In range.
When the result of verification three in business verification indicates mistake, that is, determining described in first data model the
When the constraint relationship in the corresponding value of the nodal properties data of one destination node is unsatisfactory for the constraint relationship being pre-configured, institute
It states the nodal properties data that management equipment modifies first object node described in first data model, or deletes described the
The nodal properties data of first object node described in one data model.
For example, first object node is that radio frequency unit accesses board type, board type of hardware node in the first data model
With radio frequency unit access board type there are the constraint relationship, the constraint relationship is that the value of radio frequency unit access board type must be included in
Within board type of hardware value range, the value of radio frequency unit access board type is 4 in the first data model, and MIB data
The value of radio frequency unit access board type is 2 in corresponding second data model of the original version of target device in library, can be with
Determine the value of radio frequency unit access board type and radio frequency unit access board type in the second data model in the first data model
Value have differences, and in the first data model the value of board type of hardware be 123, therefore by the first data mould
The value of radio frequency unit access board type is revised as 1 or 2 or 3 in type, or deletes radio frequency unit in first data model
Access the nodal properties data of board type.
Optionally, the value of board type of hardware in first data model can also be revised as by the management equipment
1\2\3\4。
When the result of verification four in business verification indicates mistake, that is, determining described in first data model the
Described in the OID of one destination node the second data model corresponding with the original version of the target device in MIB database
When the OID difference of first object node, the management equipment modifies the OID of first object node described in the first data model,
So that the OID of first object node described in the first data model is identical as the OID of first object node in the second data model；
Alternatively, in determining the first data model in the OID of first object node and the second data model in addition to first object node
Other nodes OID it is identical, modify the first data model described in first object node OID so that the first data model
Described in first object node OID and the second data model in other nodes in addition to first object node OID not
It is identical.
For example, the OID for the temperature nodes that CPU works in the first data model is xxxx.3, the Oid of CPU power consumption node is set
When being set to xxxx.3, the OID of the CPU temperature nodes to work is set xxxx.3 by management equipment, by the OID of CPU power consumption node
It is set as xxxx.4.
Optionally, in the business verification for being designed repeatability detection, and inspection result is designated as mistake i.e. described first
There are when identical node in data model, the management equipment closes the nodal properties data of the identical node
And and delete duplicate node.
For example, save node e in the tables of data A of the target device, and the tables of data A node e that saves takes
Value range is 0-3, and node e is equally saved in the tables of data B of the target device, and the section that tables of data B is saved
The value range of point e is 0-5, and the management equipment is merged the value range of node e based on the correction rule of pre-configuration,
And the nodal properties data of node e and node e are deleted in tables of data A, or in tables of data B by node e with
And the nodal properties data of node e are deleted.
It is described if mistake occurs in the check results instruction of business verification when the business is verified as other verifications
Management equipment corrects the nodal properties data of the first object node based on the content that the business verifies accordingly,
So that the nodal properties data meet demand of the modified first object node.
Correction rule in business correction procedure based on pre-configuration is to the first object in first data model
The nodal properties data of node are corrected, the correction rule of the pre-configuration be not it is unalterable, user can basis
It needs to reconfigure correction rule.
Correction rule in business correction procedure based on pre-configuration to the nodal properties data of the first object node into
Row modification, correcting in regular configuration file for the pre-configuration includes: ginseng mark information, the functional characteristic of target device, higher level
Network management restricted information etc..Wherein, ginseng mark information is to be supplied to the reference configuration information of user.The correction rule of the pre-configuration is simultaneously
Be not it is unalterable, user can according to need to correct rule reconfigures.
It corrects in the configuration file of rule comprising ginseng mark information, the functional characteristic of target device, Upper NM Station restricted information
Etc. information so that management equipment based on pre-configuration correct rules modification described in first object node nodal properties data
When, it is ensured that the nodal properties data of the first object node ensure that described in ginseng mark and Upper NM Station allowed band
The uniqueness of the OID of first object node.
After executing the step S302 business correction procedure or the result instruction of step S301 business verification does not occur
When mistake, step S303 business matching process is executed.
Business matching: S303, the management equipment determine first object node described in first data model
OID, when identical as the OID of other nodes in addition to the first object node stored in the MIB database, modification
The OID of first object node described in first data model so that the OID of the modified first object node with
The OID of the other nodes in addition to the first object node stored in the MIB database is all different.
For example, first object node is the temperature of CPU work, the OID of the temperature of CPU work is in the first data model
Xxxx.3, the OID of the stone number of the CPU of third data model is equally xxxx.3 in MIB database, at this moment, when user looks into
When asking xxxx.3 node, what the first data model was fed back is the temperature of CPU work, and third data model feedback is the hard of CPU
Nucleus number mesh, causes ambiguity.In embodiments of the present invention, the management equipment temperature that CPU works in the first data model and MIB number
When identical according to the OID of the stone number of the CPU of third data model in library, the OID of the temperature nodes of CPU work is revised as
xxxx.4。
Optionally, the target device of data to be updated is multiple, and the process of the management equipment management MIB data specifically may be used
In method shown in Figure 4, can specifically include as follows:
S401, management equipment obtain the corresponding configuration of version to be updated of each target device in multiple target devices respectively
File.
The corresponding data model of configuration file of each target device is respectively created in S402, the management equipment.
S403, the management equipment determine between the data model of any two equipment in multiple target devices in node
At least one node being had differences in performance data.
S404, the management equipment is according to the preconfigured nodal information for needing to correct nodal properties data, from described
The second destination node for needing to correct nodal properties data is determined at least one node.
Specifically how to determine the second destination node for needing to correct nodal properties data, it can be refering to implementation shown in Fig. 2
Service filter process in example, the embodiment of the present invention are not done repetition herein and are repeated.
S405, the management equipment carries out business verification to the nodal properties data of second destination node, and judges
Whether the result of the business verification indicates existing mistake；If so, executing step S406；If it is not, executing step S407.
Specifically how to determine and business verification is carried out to the nodal properties data of second destination node, it can be refering to Fig. 2
Shown in business checking procedure in embodiment, the embodiment of the present invention do not do repetition herein and repeats.
S406, the management equipment correct the nodal properties data of second destination node.
Specifically how the nodal properties data of second destination node are corrected, it can be shown in Fig. 2 refering to step
Business correction procedure in embodiment, the embodiment of the present invention are not done repetition herein and are repeated.
S407, the management equipment modify the section of the second destination node in the corresponding data model of any two equipment
Dot characteristics data so that in the corresponding data model of the multiple target device the second destination node nodal properties data phase
Together.
Data model after each apparatus modifications is imported into corresponding configuration file by S408, the management equipment.
Based on the same inventive concept of embodiment of the method corresponding with Fig. 2, the embodiment of the present invention provides a kind of management information
Library MIB data administrator 50, the structure of the device is as shown in figure 5, include obtaining module 51, creation module 52, determining module
53, modified module 54 and update module 55, in which:
Module 51 is obtained, for obtaining the corresponding configuration file of version to be updated of target device.
The configuration file includes the nodal properties data of several nodes to be updated.
Creation module 52, the corresponding first data mould of the configuration file obtained for creating the acquisition module 51
Type.
First data model include several nodes in the configuration file nodal properties data and
The nodal properties of the nodal properties data of each node and other nodes in several described nodes in several described nodes
The constraint relationship between data in value.
Determining module 53, for determining in first data model and MIB database that the creation module 52 creates
The target device corresponding second data model of original version between had differences in nodal properties data first
Destination node.
Modified module 54, for determining the first data mould that the creation module 52 creates in the determining module 51
The constraint relationship in the corresponding value of the nodal properties data of first object node described in type is unsatisfactory for the pact being pre-configured
When beam relationship, the nodal properties data of first object node described in first data model are modified, or delete described the
The nodal properties data of first object node described in one data model.
Update module 55, it is described to more for modified first data model of the modified module 54 to be imported into
In the corresponding configuration file of new version.
In a kind of possible embodiment, the determining module 53 is also used to determining the creation of creation module 52
First data model the second data model corresponding with the original version of the target device in MIB database between
After the first object node having differences in nodal properties data, the first data mould is modified in the modified module 54
The nodal properties data of first object node described in type, or delete first object node described in first data model
Nodal properties data before, determine the first object node nodal properties data use format whether meet pre-configuration
Nodal properties data format.
The modified module 54 is also used to the amendment described first when 53 definitive result of determining module is to be unsatisfactory for
The format of the node data characteristic of destination node.
In alternatively possible embodiment, the determining module 53 is also used to determining the wound of creation module 52
First data model built the second data model corresponding with the original version of the target device in MIB database it
Between after the first object node that is had differences in nodal properties data, the modified module 54 modifies the first data mould
The nodal properties data of first object node described in type, or delete first object node described in first data model
Nodal properties data before, determine whether the nodal properties data interior joint value of the first object node takes preset
It is worth in range.
The modified module 54 is also used to modify the first object node when the determining module 53 is determined as no
Nodal properties data in node value so that the nodal properties data interior joint value of the first object node is described
In preset value range.
Optionally, nodal properties data include object identifier OID, and the determining module 53 is also used in the creation
After module 52 creates corresponding first data model of the configuration file, the modified module 54 modifies the first data mould
The nodal properties data of first object node described in type, or delete first object node described in first data model
Nodal properties data before, determine in first data model of creation module creation to include OID two identical
Node；
The modified module 54 is also used to determine first number of the creation module creation in the determining module 53
When according to two nodes identical including OID in model, the OID of one of node in described two nodes is modified, so that modification
The OID of described two nodes afterwards is different.
Optionally, nodal properties data include object identifier OID, the determining module 53, are also used to described in the determination
First data model that creation module 52 creates corresponding with the original version of the target device in MIB database the
After the first object node having differences in nodal properties data between two data models, the update module 55 will be described
Before modified first data model of modified module 54 is imported into the corresponding configuration file of the version to be updated, really
The OID of first object node described in first data model that the fixed creation module 52 creates, and in the MIB data
The OID of the other nodes in addition to the first object node stored in library is identical；
The modified module 54 is also used to determine described first that the creation module 52 creates in the determining module 32
The OID of first object node described in data model, with stored in the MIB database except the first object node with
When the OID of outer other nodes is identical, the OID of first object node described in first data model is modified, so that modification
The OID of the first object node afterwards and its in addition to the first object node stored in the MIB database
The OID of its node is all different.
Management equipment obtains the corresponding configuration file of version to be updated of target device in the embodiment of the present invention, and creates institute
State corresponding first data model of configuration file.Then the target in first data model and MIB database is determined
The first object node being had differences in nodal properties data between corresponding second data model of the original version of equipment.?
Determine that the constraint in the corresponding value of the nodal properties data of first object node described in first data model is closed
When system is unsatisfactory for the constraint relationship being pre-configured, the management equipment modifies first object node described in first data model
Nodal properties data, or delete the nodal properties data of first object node described in first data model, finally
Modified first data model is imported into the corresponding configuration file of the version to be updated., compared with prior art
In when being managed by comparing tool to MIB data, only for the node that nodal properties data have differences, according to node spy
The method that the difference condition of property data modifies to the nodal properties data of the node, in the embodiment of the present invention, management equipment
It is special to consider the node of each node and other nodes in several described nodes in several nodes of the target device
Property data between the constraint relationship in value, then the nodal properties data of several nodes of the target device are carried out
Processing, to improve the correctness and compatibility of the MIB data of the target device.
It should be understood by those skilled in the art that, the embodiment of the present invention can provide as method, system or computer program
Product.Therefore, complete hardware embodiment, complete software embodiment or reality combining software and hardware aspects can be used in the present invention
Apply the form of example.Moreover, it wherein includes the computer of computer usable program code that the present invention, which can be used in one or more,
The computer program implemented in usable storage medium (including but not limited to magnetic disk storage, CD-ROM, optical memory etc.) produces
The form of product.
The present invention be referring to according to the method for the embodiment of the present invention, the process of equipment (system) and computer program product
Figure and/or block diagram describe.It should be understood that every one stream in flowchart and/or the block diagram can be realized by computer program instructions
The combination of process and/or box in journey and/or box and flowchart and/or the block diagram.It can provide these computer programs
Instruct the processor of general purpose computer, special purpose computer, Embedded Processor or other programmable data processing devices to produce
A raw machine, so that being generated by the instruction that computer or the processor of other programmable data processing devices execute for real
The device for the function of being specified in present one or more flows of the flowchart and/or one or more blocks of the block diagram.
These computer program instructions, which may also be stored in, is able to guide computer or other programmable data processing devices with spy
Determine in the computer-readable memory that mode works, so that it includes referring to that instruction stored in the computer readable memory, which generates,
Enable the manufacture of device, the command device realize in one box of one or more flows of the flowchart and/or block diagram or
The function of being specified in multiple boxes.
These computer program instructions also can be loaded onto a computer or other programmable data processing device, so that counting
Series of operation steps are executed on calculation machine or other programmable devices to generate computer implemented processing, thus in computer or
The instruction executed on other programmable devices is provided for realizing in one or more flows of the flowchart and/or block diagram one
The step of function of being specified in a box or multiple boxes.
Although preferred embodiments of the present invention have been described, it is created once a person skilled in the art knows basic
Property concept, then additional changes and modifications may be made to these embodiments.So it includes excellent that the following claims are intended to be interpreted as
It selects embodiment and falls into all change and modification of the scope of the invention.
Obviously, various changes and modifications can be made to the invention without departing from essence of the invention by those skilled in the art
Mind and range.In this way, if these modifications and changes of the present invention belongs to the range of the claims in the present invention and its equivalent technologies
Within, then the present invention is also intended to include these modifications and variations.
Claims (10)
1. a kind of management information bank MIB data managing method characterized by comprising
The corresponding configuration file of version to be updated of management equipment acquisition target device；If the configuration file includes to be updated
The nodal properties data of dry node；
The management equipment creates corresponding first data model of the configuration file；First data model includes described matches
Set the nodal properties of each node in the nodal properties data and several described nodes of several nodes in file
The constraint relationship between data and the nodal properties data of other nodes in several described nodes in value；
The management equipment determines that first data model is corresponding with the original version of the target device in MIB database
The second data model between the first object node that is had differences in nodal properties data；
In the corresponding value of nodal properties data for determining first object node described in first data model
When the constraint relationship is unsatisfactory for the constraint relationship being pre-configured, the management equipment modifies the first mesh described in first data model
The nodal properties data of node are marked, or delete the nodal properties number of first object node described in first data model
According to；
Modified first data model is imported into the corresponding configuration file of the version to be updated by the management equipment
In.
2. the method as described in claim 1, which is characterized in that the management equipment determine first data model with
Exist in nodal properties data between corresponding second data model of the original version of the target device in MIB database
After the first object node of difference, the management equipment modifies the section of first object node described in first data model
Before dot characteristics data, or the nodal properties data of first object node described in deletion first data model, also wrap
It includes:
Whether the format that the management equipment determines that the nodal properties data of the first object node use meets pre-configuration
The format of nodal properties data corrects the node data characteristic of the first object node when definitive result is to be unsatisfactory for
Format.
3. method according to claim 1 or 2, which is characterized in that determine first data model in the management equipment
It is deposited in nodal properties data between the second data model corresponding with the original version of the target device in MIB database
After the first object node of difference, the management equipment modifies first object node described in first data model
Before nodal properties data, or the nodal properties data of first object node described in deletion first data model, also
Include:
Whether the management equipment determines the nodal properties data interior joint value of the first object node in preset value
In range, when being determined as no, the node value in the nodal properties data of the first object node is modified, so that described
The nodal properties data interior joint value of one destination node is in the preset value range.
4. the method as described in claim 1, which is characterized in that nodal properties data include object identifier OID, in the pipe
After managing corresponding first data model of equipment creation configuration file, the management equipment modifies institute in first data model
The nodal properties data of first object node are stated, or delete the node of first object node described in first data model
Before performance data, further includes:
When the management equipment determines two nodes identical including OID in first data model, described two sections are modified
The OID of one of node in point, so that the OID of modified described two nodes is different.
5. the method as described in claim 1, which is characterized in that nodal properties data include object identifier OID, in the pipe
Reason equipment determines first data model the second data corresponding with the original version of the target device in MIB database
After the first object node having differences in nodal properties data between model, the management equipment will be modified described
Before first data model is imported into the corresponding configuration file of the version to be updated, the method also includes:
The management equipment determines the OID of first object node described in first data model, and in the MIB database
The OID of other nodes in addition to the first object node of middle storage is identical；
The management equipment modifies the OID of first object node described in first data model, so that modified described
The OID of first object node and other nodes in addition to the first object node for being stored in the MIB database
OID is all different.
6. a kind of management information bank MIB data administrator, described device is applied to management equipment characterized by comprising
Module is obtained, for obtaining the corresponding configuration file of version to be updated of target device；The configuration file includes to more
The nodal properties data of several new nodes；
Creation module, corresponding first data model of the configuration file obtained for creating the acquisition module；Described
One data model include several nodes in the configuration file nodal properties data and several described nodes
In between the nodal properties data of each node and the nodal properties data of other nodes in several described nodes in value
On the constraint relationship；
Determining module, the mesh in first data model and MIB database for determining the creation module creation
The first object node being had differences in nodal properties data between corresponding second data model of the original version of marking device；
Modified module, for determining described in first data model of creation module creation the in the determining module
When the constraint relationship in the corresponding value of the nodal properties data of one destination node is unsatisfactory for the constraint relationship being pre-configured, repair
Change the nodal properties data of first object node described in first data model, or deletes in first data model
The nodal properties data of the first object node；
Update module, for modified first data model of the modified module to be imported into the version pair to be updated
In the configuration file answered.
7. device as claimed in claim 6, which is characterized in that the determining module is also used to determining the creation module
First data model the second data model corresponding with the original version of the target device in MIB database of creation
Between after the first object node that is had differences in nodal properties data, modify first data in the modified module
The nodal properties data of first object node described in model, or delete first object section described in first data model
Before the nodal properties data of point, it is prewired to determine whether the format of the nodal properties data use of the first object node meets
The format for the nodal properties data set；
The modified module is also used to correct the first object node when the determining module definitive result is to be unsatisfactory for
Node data characteristic format.
8. device as claimed in claims 6 or 7, which is characterized in that the determining module is also used to the determining module, also
For in the original of first data model for determining creation module creation and the target device in MIB database
After the first object node being had differences in nodal properties data between corresponding second data model of version, the modification
Module modifies the nodal properties data of first object node described in first data model, or deletes first data
Before the nodal properties data of first object node described in model, in the nodal properties data that determine the first object node
Whether node value is in preset value range；
The modified module, the node for being also used to modify the first object node when the determining module is determined as no are special
Node value in property data, so that the nodal properties data interior joint value of the first object node preset takes described
It is worth in range.
9. device as claimed in claim 6, which is characterized in that nodal properties data include object identifier OID, the determination
Module is also used to after the creation module creates corresponding first data model of the configuration file, the modified module
The nodal properties data of first object node described in first data model are modified, or delete first data model
Described in first object node nodal properties data before, in first data model that determines creation module creation
Including identical two nodes of OID；
The modified module is also used in first data model that the determining module determines the creation module creation
When two nodes identical including OID, the OID of one of node in described two nodes is modified, so that modified described
The OID of two nodes is different.
10. device as claimed in claim 6, which is characterized in that nodal properties data include object identifier OID, described true
Cover half block, the target being also used in first data model and MIB database for determining the creation module creation
The first object node being had differences in nodal properties data between corresponding second data model of the original version of equipment it
Afterwards, modified first data model of the modified module is imported into the version to be updated and corresponded to by the update module
Configuration file in front of, determine first object node described in first data model of creation module creation
OID is identical as the OID of other nodes in addition to the first object node stored in the MIB database；
The modified module is also used in first data model that the determining module determines the creation module creation
The OID of the first object node, with the other sections in addition to the first object node stored in the MIB database
When the OID of point is identical, the OID of first object node described in first data model is modified, so that modified described the
The OID of the OID of one destination node and the other nodes in addition to the first object node stored in the MIB database
It is all different.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710369247.4A CN108958758A (en) | 2017-05-23 | 2017-05-23 | A kind of management information bank MIB data managing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710369247.4A CN108958758A (en) | 2017-05-23 | 2017-05-23 | A kind of management information bank MIB data managing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108958758A true CN108958758A (en) | 2018-12-07 |
Family
ID=64493710
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710369247.4A Pending CN108958758A (en) | 2017-05-23 | 2017-05-23 | A kind of management information bank MIB data managing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108958758A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109918123A (en) * | 2019-03-11 | 2019-06-21 | 山石网科通信技术股份有限公司 | The configuration method and device of firewall markup language |
| CN112436964A (en) * | 2020-11-12 | 2021-03-02 | 中国联合网络通信集团有限公司 | Equipment adaptation method and network management device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030217193A1 (en) * | 2002-05-17 | 2003-11-20 | Sun Microsystems, Inc. | Method, system and article of manufacture for a firmware image |
| CN101046822A (en) * | 2006-03-31 | 2007-10-03 | Sap股份公司 | Centralized management of data nodes |
| CN102054041A (en) * | 2010-12-30 | 2011-05-11 | 用友软件股份有限公司 | Method and system for upgrading metadata |
| CN102299814A (en) * | 2010-06-24 | 2011-12-28 | 中兴通讯股份有限公司 | Method and system for upgrading MIB (management information base) on SNMP (simple network management protocol) agent |
| CN103997412A (en) * | 2013-02-18 | 2014-08-20 | 中兴通讯股份有限公司 | Management information base file generation method and device, and data processing system |
-
2017
- 2017-05-23 CN CN201710369247.4A patent/CN108958758A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030217193A1 (en) * | 2002-05-17 | 2003-11-20 | Sun Microsystems, Inc. | Method, system and article of manufacture for a firmware image |
| CN101046822A (en) * | 2006-03-31 | 2007-10-03 | Sap股份公司 | Centralized management of data nodes |
| CN102299814A (en) * | 2010-06-24 | 2011-12-28 | 中兴通讯股份有限公司 | Method and system for upgrading MIB (management information base) on SNMP (simple network management protocol) agent |
| CN102054041A (en) * | 2010-12-30 | 2011-05-11 | 用友软件股份有限公司 | Method and system for upgrading metadata |
| CN103997412A (en) * | 2013-02-18 | 2014-08-20 | 中兴通讯股份有限公司 | Management information base file generation method and device, and data processing system |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109918123A (en) * | 2019-03-11 | 2019-06-21 | 山石网科通信技术股份有限公司 | The configuration method and device of firewall markup language |
| CN112436964A (en) * | 2020-11-12 | 2021-03-02 | 中国联合网络通信集团有限公司 | Equipment adaptation method and network management device |
| CN112436964B (en) * | 2020-11-12 | 2022-08-26 | 中国联合网络通信集团有限公司 | Equipment adaptation method and network management device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11902174B2 (en) | Network slice configuration | |
| US7493377B2 (en) | Method and apparatus to manage a configuration of clustered computers according to deployment date structures | |
| US20030074436A1 (en) | Management information base object model | |
| CN112217656B (en) | Method and device for synchronizing configuration information of network equipment in SD-WAN (secure digital-to-Wide area network) system | |
| CN109951315A (en) | A kind of method and system realizing YANG model and being mapped to internal model | |
| CN104363122B (en) | A kind of method for pre-configuration and system of network element | |
| CN110650037B (en) | Heterogeneous network device configuration method and device | |
| WO2020062959A1 (en) | Data configuration method and apparatus | |
| CN106134141A (en) | A kind of method and device updating network service describer NSD | |
| CN105164660A (en) | Cloud based service design inheritance | |
| US10680852B2 (en) | Configuration of a managed device | |
| CN105490826A (en) | Configuration management system and method based on automatic discovery | |
| US20150127798A1 (en) | Object version management | |
| CN108958758A (en) | A kind of management information bank MIB data managing method and device | |
| CN113157980A (en) | Data synchronization method, device, equipment and storage medium | |
| CN111711532B (en) | Unified management method for heterogeneous network equipment | |
| CN110018835A (en) | YANG model configuration data processing method and device, terminal device and storage medium | |
| EP3672158A1 (en) | Network slice management | |
| CN110011971B (en) | Manual configuration method of network security policy | |
| CN111897643A (en) | Thread pool configuration system, method, device and storage medium | |
| US10003492B2 (en) | Systems and methods for managing data related to network elements from multiple sources | |
| WO2021037178A1 (en) | Base station station-type replacement method, sdr network management system, base station station-type replacement apparatus and computer-readable storage medium | |
| CN110460456A (en) | A kind of management information bank MIB synchronizes the method and device of generation network topology | |
| CN101426220A (en) | Method, apparatus and system for base station cutover | |
| CN115603923A (en) | Access Control List (ACL) policy management method, device and related equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20181207 |
|
| RJ01 | Rejection of invention patent application after publication |