CN102571420B - Method and system for network element data management - Google Patents
Method and system for network element data management Download PDFInfo
- Publication number
- CN102571420B CN102571420B CN201110428834.9A CN201110428834A CN102571420B CN 102571420 B CN102571420 B CN 102571420B CN 201110428834 A CN201110428834 A CN 201110428834A CN 102571420 B CN102571420 B CN 102571420B
- Authority
- CN
- China
- Prior art keywords
- network element
- data
- element data
- database
- mib
- 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.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000013523 data management Methods 0.000 title claims abstract description 39
- 238000007726 management method Methods 0.000 claims abstract description 83
- 238000012423 maintenance Methods 0.000 claims description 16
- 230000001105 regulatory effect Effects 0.000 claims description 11
- 230000008859 change Effects 0.000 claims description 10
- 238000012217 deletion Methods 0.000 claims description 7
- 230000037430 deletion Effects 0.000 claims description 7
- 238000012544 monitoring process Methods 0.000 claims description 5
- 230000007246 mechanism Effects 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 12
- 230000008569 process Effects 0.000 description 8
- 239000003795 chemical substances by application Substances 0.000 description 5
- 235000010627 Phaseolus vulgaris Nutrition 0.000 description 4
- 244000046052 Phaseolus vulgaris Species 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 3
- 238000007792 addition Methods 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Abstract
An embodiment of the invention discloses a method for network element data management, which includes the following steps: a management information base (MIB) tree directory is established in advance according to management requirements, and the MIB tree directory comprises at least one MIB node; the MIB tree directory is converted to a corresponding extensive makeup language (XML) file, and the XML file comprises a defined object identifier (OID) of each MIB node; network element data corresponding to each MIB node are obtained respectively from each network element within the range of management and saved in a data base through a cache. The embodiment of the invention further discloses a system for network element data management. By means of the system, once an MIB node is changed, the changes of the MIB node can be updated to the XML file only by generating the XML file again so that unnecessary object expenses can be avoided. In addition, due to the fact that most network element data maintain unchanged, network element data can be directly queried on the network management side through a data base cache mechanism, querying speed is greatly quickened, and network management performance is improved.
Description
Technical field
The present invention relates to network data management field, particularly relate to a kind of network element data management method and system.
Background technology
According to IAB(Internet Architecture Board, Internet Architecture Board) suggestion, all network (IP/TCP) equipment must be manageable, manageable prerequisite realizes SNMP(Simple Network Management Protocol, Simple Network Management Protocol) agreement.In order to support SNMP, first we need according to regulatory requirement definition MIB(Management Information Base, management information bank), then the mib information of definition is loaded into NMS(Network Management System, network management system) in, wherein MIB defines a series of attributes of managed object, the data type etc. of the title of such as object, the access rights of object and object.Like this, NMS just can utilize snmp protocol to carry out management and supervision to the network equipment.Such as, NMS can act on behalf of to Agent() send SNMP request collection data, also can receive the Trap information (Trap refers to show the proactive notification of device fails or change by the trap message that managed devices (agency) reports) that Agent initiatively sends.Agent, for safeguarding the information data of managed devices and responding the request of NMS, reports management data to the NMS sent request, and in addition when equipment state occurs abnormal, reports abnormal information to arrive NMS.
Network management monitoring equipment mainly collects NE(Net Element by snmp protocol, network element) data of side, and make the specific function of NE side apparatus support by the value revising relevant NE side MIB node.In addition when NE state occurs abnormal, alarm can also be sent to NMS server by Agent by some variable of alarm Bind NE side.And NE side data is managed by MIB in Agent side, due to the tree hierachy structure of MIB, traditional network element data management method is that each directory node in being set by MIB is packaged into an object, under directory node, each leaf node is as an attribute of object, therefore once mib structure more complicated, will produce a lot of object, this is extremely difficult maintenance and change for the later stage.Further, all NE-side data being existed a database table for the NE management of 1,000,000 grades is poor efficiency, and therefore this kind of scheme is only suitable for middle-size and small-size NE management.
Management method traditional in addition, when carrying out data query at every turn, all must obtain data by snmp protocol from network element side network element, and this is very poor efficiency.
Summary of the invention
Embodiment of the present invention technical problem to be solved is, provides a kind of network element data management method and system.Can managed network element data efficiently, workload when reducing the later maintenance such as network element data additions and deletions, amendment and difficulty.
In order to solve the problems of the technologies described above, embodiments provide a kind of network element data management method, comprising: in advance according to regulatory requirement creative management information bank tree directory, described management information bank tree directory comprises at least one management information bank node;
Described management information bank tree directory is converted to corresponding extensible markup language document, in described extensible markup language document, comprises the defining objects mark of each management information bank node;
Obtain the network element data corresponding to each management information bank node respectively from the network element in range of management, and described network element data is cached in database.
Wherein, the content stored in described database comprises element name field, instance objects identification field and data value field;
Element name field is for storing element name, and described element name is used for unique identification network element;
Instance objects identification field is for storing instance objects mark, and described instance objects mark is used for a kind of management information bank node of unique identification, and described instance objects mark corresponds to described defining objects mark;
Data value field is identified the data of the special network element customized configuration item of common ID by described element name and described instance objects for storing.
Wherein, described method also comprises:
Monitor the network element more new events in described range of management;
Judge whether that network element changes, if be judged as YES, then determined the network element deletion having new network element to increase or have been friends in the past, if there is new network element to increase, then obtains network element data from new network element, and the network element data of acquisition is cached in database; If the network element of haveing been friends in the past is deleted, then the network element data of the old network element of buffer memory in database is deleted.
Wherein, described method also comprises:
Receive network element data inquiry request;
Described network element data is inquired about in the database according to described network element data inquiry request;
Judge that whether the database query result of described network element data is empty, if be judged as YES, then in described network element, inquire about described network element data, and the Query Result in network element is returned to user; If be judged as NO, then the Query Result in database is returned to user.
Wherein, described method also comprises:
Judge whether management information bank tree directory there occurs amendment, if be judged as YES, then return and perform the described step described management information bank tree directory being converted to corresponding extensible markup language document.
Correspondingly, the embodiment of the present invention additionally provides a kind of network element data management system, comprising:
Management information bank creation module, in advance according to regulatory requirement creative management information bank tree directory, described management information bank tree directory comprises at least one management information bank node;
Management information bank-extend markup language modular converter, for described management information bank tree directory being converted to corresponding extensible markup language document, comprises the defining objects mark of each management information bank node in described extensible markup language document;
Data acquisition module, for obtaining the network element data corresponding to each management information bank node respectively from the network element in range of management, and is cached in database by described network element data;
Database, for storing described network element data.
Wherein, the content stored in described database comprises element name field, instance objects identification field and data value field;
Element name field is for storing element name, and described element name is used for unique identification network element;
Instance objects identification field is for storing instance objects mark, and described instance objects mark is used for a kind of management information bank node of unique identification, and described instance objects mark corresponds to described defining objects mark;
Data value field is identified the data of the special network element customized configuration item of common ID by described element name and described instance objects for storing.
Wherein, described system also comprises:
Finding module, for monitoring the network element more new events in described range of management, having judged whether that network element changes;
First judge module, during for finding that there is network element change in described discovery module, judgement has new network element to increase or the network element of haveing been friends in the past is deleted, if there is new network element to increase, then notify that described data acquisition module obtains network element data from new network element, and the network element data of acquisition is cached in described database;
Database maintenance module, when the network element for determining to have been friends in the past at described first judge module is deleted, deletes the network element data of the old network element of buffer memory in described database.
Wherein, described system also comprises:
Human-machine interface module, for receiving network element data inquiry request;
Enquiry module, for inquiring about described network element data in the database according to described network element data inquiry request;
Result returns module, for judging whether the database query result of network element data is empty, if be judged as NO, then by described human-machine interface module, the Query Result in database is returned to user; If be judged as YES, then notify that described enquiry module inquires about required network element data in network elements, and the Query Result in network element is returned to user.
Wherein, described system also comprises:
Second judge module, for judging whether management information bank tree directory there occurs amendment, if be judged as YES, then notifies that management information bank-extend markup language modular converter regenerates extensible markup language document.
Implement the embodiment of the present invention, there is following beneficial effect: by the MIB(Management Information Base that will be pre-created, management information bank) tree directory is mapped to XML(Extensible Markup Language, extend markup language) file, and the database caches network element data in webmaster side, once MIB node changes, only need to regenerate XML file, can the change of MIB node be updated in XML file, avoid unnecessary object expense; In addition, because most of network element data remains unchanged, directly at webmaster side inquiry network element data, greatly can be accelerated inquiry velocity, and improve the performance of network management by database caches mechanism.
Accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.
Fig. 1 is the first embodiment flow chart of network element data management method provided by the invention;
Fig. 2 is the second embodiment flow chart of network element data management method provided by the invention;
Fig. 3 is the source file that the reference MIB of SystemConfigutationGroup configuration item in MIB tree directory defines;
Fig. 4 is the XML file after the conversion of SystemConfigutationGroup configuration item;
Fig. 5 is the method flow diagram inquired about network element data provided by the invention;
Fig. 6 is the method flow diagram carrying out network element data inquiry in network element side network element provided by the invention;
Fig. 7 is the method flow diagram in webmaster side maintenance network metadata provided by the invention;
Fig. 8 is the first example structure schematic diagram of network element data management system provided by the invention;
Fig. 9 is the second example structure schematic diagram of network element data management system provided by the invention;
Figure 10 is the 3rd example structure schematic diagram of network element data management system provided by the invention;
Figure 11 is the structural representation of the network element data management system based on user terminal/server framework provided by the invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, be clearly and completely described the technical scheme in the embodiment of the present invention, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
See Fig. 1, be the first embodiment flow chart of network element data management method provided by the invention, as shown in Figure 1, comprise:
In step S100, create MIB(Management Information Base according to regulatory requirement in advance, management information bank) tree directory, described MIB tree directory comprises at least one MIB node.It should be noted that, " MIB tree directory " used herein is not mib information of the prior art, and it is only similar to mib information in version, is namely all tree, but both are different in data management mode.MIB carrys out managed network element data by complicated Java Bean entity class under directory tree, need to safeguard a large amount of objects and database table, such as each root MIB node comprising leaf MIB node is by generation Java Bean entity class, each leaf MIB node under this root MIB node is an attribute of Bean object, when root MIB node is a lot, a lot of Java Bean entity class will be produced.In contrast to this, MIB tree directory is only a kind of directory tree, and it only needs maintenance Java Bean object, and each root MIB node comprising leaf MIB node is an attribute (i.e. configuration item) of Java Bean object.
In step S101, described MIB tree directory is converted to corresponding XML(Extensible Markup Language, extending mark language) file, comprise the definition OID(Object Identifier of each MIB node in described XML file, object identity).
In step S102, obtain the network element data corresponding to each MIB node respectively from the network element in range of management, and described network element data is cached in database.
A kind of network element data management method of the present invention is by being mapped to XML file by the MIB tree directory be pre-created, and the database caches network element data in webmaster side, once MIB node changes, only need to regenerate XML file, can the change of MIB node be updated in XML file, avoid unnecessary object expense; In addition, because most of network element data remains unchanged, directly at webmaster side inquiry network element data, greatly can be accelerated inquiry velocity, and improve the performance of network management by database caches mechanism.
See Fig. 2, it is the second embodiment flow chart of network element data management method provided by the invention.In the present embodiment, by the method flow of this network element data of description specifically management.As shown in Figure 2, the method flow process comprises:
In step S200, create MIB tree directory according to regulatory requirement in advance, described MIB tree directory comprises at least one MIB node.According to regulatory requirement, the hierarchical structure of MIB tree directory may be very complicated, and such as, MIB tree directory can comprise at least one root MIB node, each MIB node can comprise at least one leaf MIB node, can comprise again at least one secondary leaf MIB node etc. under each leaf MIB node.Wherein, the root MIB node comprising leaf MIB node can be called configuration item, and each leaf MIB node can be used for each attribute representing configuration item.Such as, when a root MIB node represents configuration information, leaf MIB node under this root MIB node can comprise: system type code, software version, proxy port and Log Desinations table etc., wherein can comprise again secondary leaf MIB node under Log Desinations table, such as CPU use amount, internal memory use amount, hard disk use amount, network traffics etc.Preferably, in this step S200, can also comprise and generate network element list according to the network element in range of management, the element name of each network element or the information of other this network element of energy unique identification in this network element list, can be comprised.
In step S201, described MIB tree directory is converted to corresponding XML file, in described XML file, comprises the definition OID of each MIB node.In the prior art, each root MIB node (such as SystemConfigutationGroup) comprising leaf MIB node is by generation Java Bean entity class, then by the attribute of each leaf MIB node under root MIB node as Bean object, once such root MIB node is a lot, will produce a lot of object and database table, this maintenance for the project later stage is very difficult.Such as, and once mib information produces change, update routine code again, increases, revises or deletes, and this will cause very large workload.
Particularly, see Fig. 3, the source file that the reference MIB for the SystemConfigutationGroup configuration item in MIB tree directory defines.Fig. 3 illustrate only leaf MIB node serverIdentifer, and other leaf MIB node is similar, no longer describes in detail.See Fig. 4, it is the XML file after the conversion of SystemConfigutationGroup configuration item.As shown in Figure 4, each leaf MIB node corresponds to a columnAttribute node in xml, and wherein identifier attribute corresponds to the definition OID of MIB node.Can be obtained the example OID of this MIB node by the definition OID of MIB node, thus can inquire about the network element data of this MIB node in database or network element, this will be described in detail later.
In step S202, obtain the network element data corresponding to each MIB node respectively from the network element in range of management, and described network element data is cached in database.Particularly, the content stored in described database can comprise element name field, example oid field and data value field.Element name field is for storing element name, and element name is used for unique identification network element.Example oid field, for storing example OID, is also configuration item information, and example OID is used for a kind of MIB node of unique identification, and described example OID corresponds to described definition OID.Data value field is for storing by the data of the special network element customized configuration item of described element name and described example OID common ID.
More specifically, according to the definition of MIB in prior art, variable can be divided into scalar sum table amount node, and each variable has one to define OID and example OID.For scalar, example OID=defines OID+ " .0 "; For table amount, example OID=defines OID+ ". "+major key information.Such as, represent the name of a people with a root MIB node, the definition OID of this root MIB node is 1.1, if do not have other leaf MIB node under this root MIB node, so this root MIB node is scalar node, and its example OID is 1.1.0; If when this root MIB node also comprises leaf MIB node Chinese name, English name, pet name etc., its example OID can be 1.1.1(Chinese name), 1.1.2(English name) or the 1.1.3(pet name).In network element side network element, the specific MIB node of unique identification one can be carried out by example OID.But in webmaster side, because different network elements may have identical MIB node, so element name is also adopted to carry out unique identification network element.That is, the next specific configuration item of unique identification network element is carried out with element name+example OID.In addition, in webmaster side, go back the value that usage data value field value carrys out store M IB node.Such as, a database table for buffer memory network element data can be as follows:
| Field name | Type | Whether major key |
| NeID | String | Be |
| oid | String | Be |
| value | String | No |
In step S203, the more new events of the network element within the scope of management of monitor, has judged whether that network element changes.If be judged as NO, be then left intact, if be judged as YES, then perform step S204.
In step S204, determine the network element deletion having new network element to increase or have been friends in the past.If there is new network element to increase, then perform step S205; If the network element of haveing been friends in the past is deleted, then perform step S206.
In step S205, obtain network element data from new network element, and the network element data of acquisition is cached in database, and return execution step S203.
In step S206, the network element data of the old network element of buffer memory in database is deleted, and return execution step S203.
By the more new events of the network element within the scope of management of monitor, the consistency of network element side network element and webmaster side data can be kept.In addition, if find, the data of network element side network element and webmaster side are inconsistent, can also manually refresh to realize consistency.
See Fig. 5, it is the method flow diagram that network element data is inquired about provided by the invention.As shown in Figure 5, the method flow process is from step S500, and step S500 can perform any time after the step S202 shown in the step S102 shown in Fig. 1 and Fig. 2.
In step S500, receive network element data inquiry request.Particularly, network element inquiry request can comprise the instruction of MIB sensor selection problem and network element selection instruction.Such as, MIB tree directory can be shown on display interface, and receive the click of user to certain specific MIB node in MIB tree directory, in addition, on display interface, can also show or eject network element select interface, and receive the click of user to certain specific element name, wherein network element is selected network element list can be listed in interface.
Preferably, network element list can real-time update.Such as, in the step S205 shown in Fig. 2, can also comprise and reload network element list, the network element list of reloading comprises the element name of new network element; In step S206, can also comprise and reload network element list, in the network element list of reloading, not comprise the element name of old network element.
In step S501, inquire about network element data in a database according to received network element data inquiry request.Particularly, the MIB node needing inquiry can be determined according to received MIB sensor selection problem instruction, and in XML file, obtain the definition OID of this MIB node, then example OID is obtained according to the definition OID of this MIB node, the element name of the network element needing inquiry can also be determined according to network element selection instruction simultaneously, next, just required network element data can be inquired about in a database according to element name+example OID.
In step S502, judge whether the database query result of network element data is empty, if be judged as NO, perform step S503; If be judged as YES, perform step S604.
In step S503, the Query Result in database is returned to user.
In step S504, the required network element data of inquiry in network elements, and the Query Result in network element is returned to user.
Preferably, as shown in Figure 6, step S504 specifically comprises:
In step S600, inquire about network element data in network elements by snmp protocol.
In step S601, judge whether the Query Result of network element data is empty, if judged result is no, then perform step S602; If the determination result is YES, then directly step S603 is performed.
In step S602, the network element data found is cached in database, and then performs step S603.
In step S603, the Query Result in network element is returned to user.
By buffer memory network element data in the database of webmaster side, the performance of managed network element data greatly can be improved.Suppose that inquiring about a secondary data (inquiring about a configuration item) in network element side network element needs 2s, needs 0.5s in data base querying one secondary data, supposes 10 configuration items (i.e. 10 MIB nodes) will inquiring about network element, adopt conventional method to need the time in network element side network element inquiry:
10*2s=20s
Adopt the present invention data base querying (usually having the success rate of at least 90%), so query time only needs:
10*0.9*0.2s+10*0.1*2s=3.8s
Even the new network element found, need to obtain network element data to database from new network element, but generally carry out in the ignorant situation of user due to this section of automatic acquisition process, therefore negligible.Comparatively speaking, the time that present invention saves more than at least 81% is adopted.
See Fig. 7, for provided by the invention at the method flow diagram of webmaster side maintenance network metadata.As shown in Figure 7, the method flow process is from step S700, and step S700 can perform any time after the step S202 shown in the step S102 shown in Fig. 1 and Fig. 2.The method comprises:
In step S700, judge whether MIB tree directory there occurs amendment, if not, then continue to perform step S700; If so, then return and perform step S101 or S201.
Particularly, if define new MIB node, XML file can be regenerated according to new MIB tree directory; If delete old MIB node, corresponding columnAttribute node can be deleted in XML file.Like this, no matter how MIB node changes, and all only needs maintenance Java Bean object and an XML file, substantially reduce the maintenance cost in project later stage in webmaster side.
See Fig. 8, be the first example structure schematic diagram of network element data management system provided by the invention, as shown in Figure 8, comprise:
MIB creation module 810, for creating MIB tree directory according to regulatory requirement in advance, described MIB tree directory comprises at least one MIB node.It should be noted that, " MIB tree directory " used herein is not mib information of the prior art, and it is only similar to mib information in version, is namely all tree, but both are different in data management mode.MIB carrys out managed network element data by complicated Java Bean entity class under directory tree, need to safeguard a large amount of objects and database table, such as each root MIB node comprising leaf MIB node is by generation Java Bean entity class, each leaf MIB node under this root MIB node is an attribute of Bean object, when root MIB node is a lot, a lot of Java Bean entity class will be produced.In contrast to this, MIB tree directory is only a kind of directory tree, and it only needs maintenance Java Bean object, and each root MIB node comprising leaf MIB node is an attribute (i.e. configuration item) of Java Bean object.
MIB-XML modular converter 820, for described MIB tree directory being converted to corresponding XML file, comprises the definition OID of each MIB node in described XML file.
Data acquisition module 830, for obtaining the network element data corresponding to each MIB node respectively from the network element in range of management, and is cached to described network element data in database.
Database 840, for storage network metadata.
A kind of network element data management system of the present invention is by being mapped to XML file by the MIB tree directory be pre-created, and the database caches network element data in webmaster side, once MIB node changes, only need to regenerate XML file, can the change of MIB node be updated in XML file, avoid unnecessary object expense; In addition, because most of network element data remains unchanged, directly at webmaster side inquiry network element data, greatly can be accelerated inquiry velocity, and improve the performance of network management by database caches mechanism.
See Fig. 9, it is the second example structure schematic diagram of network element data management system provided by the invention.In the present embodiment, by the structure of this network element data management system of description specifically.As shown in Figure 9, this system comprises:
MIB creation module 810, for creating MIB tree directory according to regulatory requirement in advance, described MIB tree directory comprises at least one MIB node.According to regulatory requirement, the hierarchical structure of MIB tree directory may be very complicated, and such as, MIB tree directory can comprise at least one root MIB node, each MIB node can comprise at least one leaf MIB node, can comprise again at least one secondary leaf MIB node etc. under each leaf MIB node.Wherein, the root MIB node comprising leaf MIB node can be called configuration item, and each leaf MIB node can represent each attribute of configuration item.Such as, when a root MIB node represents configuration information, leaf MIB node under this root MIB node can comprise: system type code, software version, proxy port and Log Desinations table etc., wherein can comprise again secondary leaf MIB node under Log Desinations table, such as CPU use amount, internal memory use amount, hard disk use amount, network traffics etc.
Preferably, in MIB creation module 810, network element List Generating Module can also being comprised, for generating network element list according to the network element in range of management, the element name of each network element or the information of other this network element of energy unique identification in this network element list, can be comprised.
MIB-XML modular converter 820, for described MIB tree directory being converted to corresponding XML file, comprises the definition OID of each MIB node in described XML file.In the prior art, each root MIB node (such as SystemConfigutationGroup) comprising leaf MIB node is by generation Java Bean entity class, then by the attribute of each leaf MIB node under root MIB node as Bean object, once such root MIB node is a lot, will produce a lot of object and database table, this maintenance for the project later stage is very difficult.Such as, and once mib information produces change, update routine code again, increases, revises or deletes, and this will cause very large workload.
Particularly, see Fig. 3, the source file that the reference MIB for the SystemConfigutationGroup configuration item in MIB tree directory defines.Fig. 3 illustrate only leaf MIB node serverIdentifer, and other leaf MIB node is similar, no longer describes in detail.See Fig. 4, it is the XML file after the conversion of SystemConfigutationGroup configuration item.As shown in Figure 4, each leaf MIB node corresponds to a columnAttribute node in xml, and wherein identifier attribute corresponds to the definition OID of MIB node.Can be obtained the example OID of this MIB node by the definition OID of MIB node, thus can inquire about the network element data of this MIB node in database or network element, this will be described in detail later.
Data acquisition module 830, for obtaining the network element data corresponding to each MIB node respectively from the network element in range of management, and is cached to described network element data in database.
Database 840, for storing the network element data that data acquisition module 830 obtains.Particularly, the content stored in described database 840 can comprise element name field, example oid field and data value field.Element name field is for storing element name, and element name is used for unique identification network element.Example oid field, for storing example OID, is also configuration item information, and example OID is used for a kind of MIB node of unique identification, and described example OID corresponds to described definition OID.Data value field is for storing by the data of the special network element customized configuration item of described element name and described example OID common ID.
More specifically, according to the definition of MIB in prior art, variable can be divided into scalar sum table amount node, and each variable has one to define OID and example OID.For scalar, example OID=defines OID+ " .0 "; For table amount, example OID=defines OID+ ". "+major key information.Such as, represent the name of a people with a root MIB node, the definition OID of this root MIB node is 1.1, if do not have other leaf MIB node under this root MIB node, so this root MIB node is scalar node, and its example OID is 1.1.0; If when this root MIB node also comprises leaf MIB node Chinese name, English name, pet name etc., its example OID can be 1.1.1(Chinese name), 1.1.2(English name) or the 1.1.3(pet name).In network element side network element, the specific MIB node of unique identification one can be carried out by example OID.But in webmaster side, because different network elements may have identical MIB node, so element name is also adopted to carry out unique identification network element.That is, in database 840, the next specific configuration item of unique identification network element can be carried out with element name+example OID.In addition, in webmaster side, in database 840, go back the value that usage data value field value carrys out store M IB node.
Find module 850, for the more new events of the network element within the scope of management of monitor, judged whether that network element changes.
First judge module 860, has new network element to increase or the network element deletion of haveing been friends in the past for determining.If there is new network element to increase, then notification data acquisition module 830 obtains network element data from new network element, and is cached in database 840 by the network element data of acquisition; If the network element of haveing been friends in the past is deleted, then notification database maintenance module 870.
Database maintenance module 870, when the network element for determining to have been friends in the past at the first judge module 860 is deleted, deletes the network element data of the old network element of buffer memory in database.
The network element data management system that the present embodiment provides, by monitoring network element more new events, can keep the consistency of network element side network element and webmaster side data.
See Figure 10, it is the 3rd example structure schematic diagram of network element data management system provided by the invention.As shown in Figure 10, except the module be described with reference to figure 8 and Fig. 9, this system can also comprise:
Human-machine interface module 880, for receiving network element data inquiry request.Particularly, network element inquiry request can comprise the instruction of MIB sensor selection problem and network element selection instruction.Such as, human-machine interface module 880 can show MIB tree directory on display interface, and receive the click of user to certain specific MIB node in MIB tree directory, in addition, human-machine interface module 880 can also show or eject network element and select interface on display interface, and receive the click of user to certain specific element name, wherein network element is selected network element list can be listed in interface.Human-machine interface module 880 can be the electronic device for man-machine interaction of any appropriate such as display screen, keyboard, touch-screen, handwriting screen.
Enquiry module 890, inquires about network element data for the network element data inquiry request received according to human-machine interface module 880 in database 840.Particularly, the MIB node needing inquiry is determined in the MIB sensor selection problem instruction that enquiry module 890 can receive according to human-machine interface module 880, and in XML file, obtain the definition OID of this MIB node, then example OID is obtained according to the definition OID of this MIB node, the element name of the network element needing inquiry can also be determined according to network element selection instruction simultaneously, next, enquiry module 890 just can inquire about required network element data according to element name+example OID in database 940.
Result returns module 900, for judging whether the database query result of network element data is empty, if be judged as NO, then by human-machine interface module 880, the Query Result in database 840 is returned to user; If be judged as YES, then notify that enquiry module 890 inquires about required network element data in network elements, and the Query Result in network element is returned to user.
Preferably, specifically for inquiring about network element data in network elements by snmp protocol when enquiry module 890 inquires about network element data in network elements.Result returns module 900 specifically for judging whether the Query Result of network element data is empty, if the determination result is YES, then the Query Result in network element is returned to user; If judged result is no, then the network element data found is cached in database 840 by notification data acquisition module 830, and the Query Result in network element is returned to user.
By buffer memory network element data in the database of webmaster side, the performance of managed network element data greatly can be improved.
Preferably, network element data management system can also comprise the second judge module, for judging whether MIB tree directory there occurs amendment, if not, then continues to judge; If so, then notify that MIB-XML modular converter 820 regenerates XML file.
Particularly, if the second judge module finds to define new MIB node, then can notify that MIB-XML modular converter 820 regenerates XML file according to new MIB tree directory; If the second judge module finds to delete old MIB node, then can notify that MIB-XML modular converter 820 deletes corresponding columnAttribute node in XML file.Like this, no matter how MIB node changes, and all only needs maintenance Java Bean object and an XML file, substantially reduce the maintenance cost in project later stage in webmaster side.
Preferably, network element data management system can also comprise network element list update module.Such as, when finding that module 850 finds to add new network element, the element name of new network element can add in network element list by network element list update module.When finding that module 850 finds to add new network element, the element name of old network element can be deleted by network element list update module from network element list.
The method that above reference diagram 1-7 describes or other embodiment of the method can use and perform with reference to the system described by figure 8-10 or other system embodiment.But, the various modules defined in system embodiment described above, and be not used in the border limiting physical circuit, when reality is implemented, these modules can also be divided into other module, unit or circuit.
See Figure 11, it is the structural representation of a kind of network element data management system based on user terminal/server framework provided by the invention.
As shown in figure 11, this system comprises client, server and database.Wherein, server can be one independently individual, also can be divided into FE(Front Server, front-end server) and BE(Back Server, back-end server) two parts.Server is divided into FE and BE, when multiple data inquiry request is concurrent, inquiry pressure can be alleviated, improve query performance, because a part of data inquiry request only can be mail to BE process by the queuing mechanism of FE, and by other data inquiry request buffer memory, delays to send.Topo module can be positioned at client and/or server, is equivalent to find module, is mainly used in the network element more new events within the scope of management of monitor.
Client can comprise the main interface of configuration, MIB-XML modular converter, Socket monitor module, RMI calling module.Configure main interface and be equivalent to human-machine interface module, provide the entrance that user carries out various network element data management, and network element data is showed user according to the hierarchical structure of MIB.MIB-XML modular converter is mainly used in converting special mib file to XML file.Socket monitors module and is mainly used in monitoring the network element list update message that sends over of FE, once topo finds that network element upgrades, will trigger this operation that Socket monitors module.In addition, the operation requests of client (such as data inquiry request) can be forwarded to FE by RMI calling module.
FE can comprise transmission provides interface & client session to pass on device and RMI FE applies, be respectively used to forward RMI, Socket of client and ask BE, and the RMI result that BE is returned or the Socket request forward of BE that receives are to client.
BE can comprise BE Socket conversation module, RMI BE applies, network element operational module and database operating modules, be mainly used in changing the additions and deletions of data network element data look into operation, the additions and deletions of NE-side data change the synchronized update operation etc. of looking into operation, webmaster side and NE-side data.In addition, once there is network element more new events at topo place, network element can be sent by BE Socket conversation module to client and upgrade list, and by network element operational module and database operating modules, the network element data of new network element is added in database, or deleted from database by the network element data of old network element, thus ensure the consistency of network element side network element and webmaster side data.When the data inquiry request of FE arrives, first BE will obtain data from database, if countless certificate in database, then fetches data from network element side network element, and stored in database.
One of ordinary skill in the art will appreciate that all or part of flow process realized in above-described embodiment method, that the hardware that can carry out instruction relevant by computer program has come, described program can be stored in a computer read/write memory medium, this program, when performing, can comprise the flow process of the embodiment as above-mentioned each side method.Wherein, described storage medium can be magnetic disc, CD, read-only store-memory body (Read-Only Memory, ROM) or random store-memory body (Random Access Memory, RAM) etc.
Above disclosedly be only a kind of preferred embodiment of the present invention, certainly the interest field of the present invention can not be limited with this, one of ordinary skill in the art will appreciate that all or part of flow process realizing above-described embodiment, and according to the equivalent variations that the claims in the present invention are done, still belong to the scope that invention is contained.
Claims (8)
1. a network element data management method, is characterized in that, comprising:
In advance according to regulatory requirement creative management information bank tree directory, described management information bank tree directory comprises at least one management information bank node;
Described management information bank tree directory is converted to corresponding extensible markup language document, in described extensible markup language document, comprises the defining objects mark of each management information bank node;
Obtain the network element data corresponding to each management information bank node respectively from the network element in range of management, and described network element data is cached in database;
The content stored in described database comprises element name field, instance objects identification field and data value field;
Element name field is for storing element name, and described element name is used for unique identification network element;
Instance objects identification field is for storing instance objects mark, and described instance objects mark is used for a kind of management information bank node of unique identification, and described instance objects mark corresponds to described defining objects mark;
Data value field is identified the data of the special network element customized configuration item of common ID by described element name and described instance objects for storing.
2. network element data management method according to claim 1, is characterized in that, described method also comprises:
Monitor the network element more new events in described range of management;
Judge whether that network element changes, if be judged as YES, then determined the network element deletion having new network element to increase or have been friends in the past, if there is new network element to increase, then obtains network element data from new network element, and the network element data of acquisition is cached in database; If the network element of haveing been friends in the past is deleted, then the network element data of the old network element of buffer memory in database is deleted.
3. network element data management method according to claim 1, is characterized in that, described method also comprises:
Receive network element data inquiry request;
Described network element data is inquired about in the database according to described network element data inquiry request;
Judge that whether the database query result of described network element data is empty, if be judged as YES, then in described network element, inquire about described network element data, and the Query Result in network element is returned to user; If be judged as NO, then the Query Result in database is returned to user.
4. network element data management method according to claim 1, is characterized in that, described method also comprises:
Judge whether management information bank tree directory there occurs amendment, if be judged as YES, then return and perform the described step described management information bank tree directory being converted to corresponding extensible markup language document.
5. a network element data management system, is characterized in that, comprising:
Management information bank creation module, in advance according to regulatory requirement creative management information bank tree directory, described management information bank tree directory comprises at least one management information bank node;
Management information bank-extend markup language modular converter, for described management information bank tree directory being converted to corresponding extensible markup language document, comprises the defining objects mark of each management information bank node in described extensible markup language document;
Data acquisition module, for obtaining the network element data corresponding to each management information bank node respectively from the network element in range of management, and is cached in database by described network element data;
Database, for storing described network element data;
The content stored in described database comprises element name field, instance objects identification field and data value field;
Element name field is for storing element name, and described element name is used for unique identification network element;
Instance objects identification field is for storing instance objects mark, and described instance objects mark is used for a kind of management information bank node of unique identification, and described instance objects mark corresponds to described defining objects mark;
Data value field is identified the data of the special network element customized configuration item of common ID by described element name and described instance objects for storing.
6. network element data management system according to claim 5, is characterized in that, described system also comprises:
Finding module, for monitoring the network element more new events in described range of management, having judged whether that network element changes;
First judge module, during for finding that there is network element change in described discovery module, judgement has new network element to increase or the network element of haveing been friends in the past is deleted, if there is new network element to increase, then notify that described data acquisition module obtains network element data from new network element, and the network element data of acquisition is cached in described database;
Database maintenance module, when the network element for determining to have been friends in the past at described first judge module is deleted, deletes the network element data of the old network element of buffer memory in described database.
7. network element data management system according to claim 5, is characterized in that, described system also comprises:
Human-machine interface module, for receiving network element data inquiry request;
Enquiry module, for inquiring about described network element data in the database according to described network element data inquiry request;
Result returns module, for judging whether the database query result of network element data is empty, if be judged as NO, then by described human-machine interface module, the Query Result in database is returned to user; If be judged as YES, then notify that described enquiry module inquires about required network element data in network elements, and the Query Result in network element is returned to user.
8. network element data management system according to claim 5, is characterized in that, described system also comprises:
Second judge module, for judging whether management information bank tree directory there occurs amendment, if be judged as YES, then notifies that management information bank-extend markup language modular converter regenerates extensible markup language document.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110428834.9A CN102571420B (en) | 2011-12-20 | 2011-12-20 | Method and system for network element data management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110428834.9A CN102571420B (en) | 2011-12-20 | 2011-12-20 | Method and system for network element data management |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102571420A CN102571420A (en) | 2012-07-11 |
| CN102571420B true CN102571420B (en) | 2014-12-31 |
Family
ID=46415946
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110428834.9A Expired - Fee Related CN102571420B (en) | 2011-12-20 | 2011-12-20 | Method and system for network element data management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102571420B (en) |
Families Citing this family (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104113438B (en) * | 2014-07-31 | 2018-04-06 | 上海斐讯数据通信技术有限公司 | A kind of management method and system of the multiple equipment based on MIB |
| CN104660447B (en) * | 2015-01-29 | 2018-10-26 | 杭州初灵信息技术股份有限公司 | A kind of management method of SNMP nodal informations and management system |
| CN107305562A (en) * | 2016-04-21 | 2017-10-31 | 展讯通信（上海）有限公司 | Generate the method, device and mobile terminal of KML file |
| CN107451918B (en) * | 2016-05-31 | 2020-11-03 | 创新先进技术有限公司 | Asset data management method and device |
| CN106330543A (en) * | 2016-08-25 | 2017-01-11 | 成都广达新网科技股份有限公司 | XML technology-based MIB data capture method and device |
| CN106844753B (en) * | 2017-02-16 | 2019-12-20 | 北京天元创新科技有限公司 | Method and device for constructing network element tree component |
| CN108880849B (en) * | 2017-10-12 | 2021-10-19 | 视联动力信息技术股份有限公司 | Statistical method, device and system for attribute information |
| CN107864060B (en) * | 2017-11-13 | 2020-09-01 | 广东电网有限责任公司电力科学研究院 | Method and device for synchronizing switch configuration tool and switch |
| CN108509187B (en) * | 2018-03-29 | 2021-05-18 | 烽火通信科技股份有限公司 | Method and system for automatically generating MIB function code of software platform |
| CN109510728B (en) * | 2018-12-24 | 2022-02-22 | 成都天奥电子股份有限公司 | Method for automatically converting MIB file of network management information base into XML file |
| CN110879774B (en) * | 2019-11-27 | 2024-03-29 | 北京天元创新科技有限公司 | Network element performance data alarming method and device |
| CN111177153A (en) * | 2019-12-27 | 2020-05-19 | 北京华环电子股份有限公司 | Net-SNMP based management method for Mib table |
| CN114244677B (en) * | 2021-11-29 | 2023-08-04 | 广东九博科技股份有限公司 | SNMP message analysis method, readable storage medium and computer equipment |
| CN115174344B (en) * | 2022-06-15 | 2023-05-23 | 武汉烽火技术服务有限公司 | OneID generation method and generator suitable for network management system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1996877A (en) * | 2006-09-30 | 2007-07-11 | 华为技术有限公司 | A device, system and method for realizing MIB adaptation |
| CN101197723A (en) * | 2008-01-03 | 2008-06-11 | 中兴通讯股份有限公司 | Network management intermediate part |
| CN101340316A (en) * | 2008-08-22 | 2009-01-07 | 中兴通讯股份有限公司 | Method and apparatus for uploading network metadata to network management database |
| CN101359999A (en) * | 2007-07-30 | 2009-02-04 | 中兴通讯股份有限公司 | Method and apparatus for network element data synchronization |
| CN102185703A (en) * | 2010-07-29 | 2011-09-14 | 艾默生网络能源有限公司 | A network device management method based on an SNMP protocol and a primary device |
-
2011
- 2011-12-20 CN CN201110428834.9A patent/CN102571420B/en not_active Expired - Fee Related
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1996877A (en) * | 2006-09-30 | 2007-07-11 | 华为技术有限公司 | A device, system and method for realizing MIB adaptation |
| CN101359999A (en) * | 2007-07-30 | 2009-02-04 | 中兴通讯股份有限公司 | Method and apparatus for network element data synchronization |
| CN101197723A (en) * | 2008-01-03 | 2008-06-11 | 中兴通讯股份有限公司 | Network management intermediate part |
| CN101340316A (en) * | 2008-08-22 | 2009-01-07 | 中兴通讯股份有限公司 | Method and apparatus for uploading network metadata to network management database |
| CN102185703A (en) * | 2010-07-29 | 2011-09-14 | 艾默生网络能源有限公司 | A network device management method based on an SNMP protocol and a primary device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102571420A (en) | 2012-07-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102571420B (en) | Method and system for network element data management | |
| CN101098248B (en) | Method and system for implementing universal network management based on configuration describing document | |
| US20150281339A1 (en) | Context-Aware Dynamic Policy Selection for Load Balancing Behavior | |
| US8032779B2 (en) | Adaptively collecting network event forensic data | |
| US20080263082A1 (en) | Recovery segment identification in a computing infrastructure | |
| CN100484039C (en) | Network management apparatus and network management method | |
| EP3364631A1 (en) | Dynamic orchestration of microservices | |
| JP2012155728A (en) | Method of supplying content to device | |
| JP2007523419A6 (en) | How to supply content to a device | |
| KR100606025B1 (en) | Network management apparatus and method based on simple network management protocol | |
| JP2006520575A (en) | Relational model for management information in network services | |
| CN103390018B (en) | A kind of Web service data modeling and searching method based on SDD | |
| CN104731943A (en) | Server and data processing method | |
| CN112698921A (en) | Logic code operation method and device, computer equipment and storage medium | |
| Ju et al. | An embedded Web server architecture for XML-based network management | |
| Wang et al. | SaaS-based enterprise application integration approach and case study | |
| CN100534084C (en) | Long-distance XML data updating method and system | |
| CN102684894B (en) | Method and device for realizing northboundbound interface | |
| US20230308348A1 (en) | Server to support client data models from heterogeneous data sources | |
| Ismail et al. | Semantic enhancement for network configuration management | |
| WO2022193855A1 (en) | Task state updating method and apparatus, device, and medium | |
| CN109634759A (en) | A kind of quota management method of distributed memory system, system and associated component | |
| Fang et al. | Exposing UDDI service descriptions and their metadata annotations as WS-resources | |
| CN108234447A (en) | A kind of safety regulation for heterogeneous networks security function manages system and method | |
| JP2000066979A (en) | Network management system corresponding to plural management protocols |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| ASS | Succession or assignment of patent right |
Owner name: SHENZHEN LONGSHI MEDIA CO., LTD. Free format text: FORMER OWNER: SHENZHEN COSHIP VIDEO COMMUNICATION CO., LTD. Effective date: 20130619 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20130619 Address after: 4, 518057 floor, rainbow science and technology building, north high tech Zone, Nanshan District, Guangdong, Shenzhen Applicant after: Shenzhen Longguan Media Co., Ltd. Address before: 518057 B2-1 District, rainbow tech building, North Fifth Industrial Zone, north high tech Zone, Nanshan District, Guangdong, Shenzhen Applicant before: Shenzhen Tongzhou Video Media Co., Ltd. |
|
| ASS | Succession or assignment of patent right |
Owner name: SHENZHEN TONGZHOU ELECTRONIC CO., LTD. Free format text: FORMER OWNER: SHENZHEN LONGSHI MEDIA CO., LTD. Effective date: 20140523 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20140523 Address after: 518057 Nanshan District hi tech park, Guangdong, North District Rainbow science and Technology Building Applicant after: Shenzhen Tongzhou Electronic Co., Ltd. Address before: 4, 518057 floor, rainbow science and technology building, north high tech Zone, Nanshan District, Guangdong, Shenzhen Applicant before: Shenzhen Longguan Media Co., Ltd. |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20141231 Termination date: 20161220 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |