CN102185703B - Network device management method based on SNMP protocol and primary device - Google Patents
Network device management method based on SNMP protocol and primary device Download PDFInfo
- Publication number
- CN102185703B CN102185703B CN 201010240206 CN201010240206A CN102185703B CN 102185703 B CN102185703 B CN 102185703B CN 201010240206 CN201010240206 CN 201010240206 CN 201010240206 A CN201010240206 A CN 201010240206A CN 102185703 B CN102185703 B CN 102185703B
- Authority
- CN
- China
- Prior art keywords
- file
- subset
- mib
- template
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Computer And Data Communications (AREA)
Abstract
The invention relates to a network device management method based on an SNMP protocol and a primary device. The method is characterized in that the primary device reads and analyzes a device template file and a device instance file, integrates the information, such as a device name, a device ID, a template ID, a signal ID and a control ID, in the two files according to the template ID and then saves in an integrated information array, generates an MIB file and a mapping relational file according to the data in the information array and uploads the generated MIB file to a network management center; and during the management operation, the primary device receives an SNMP protocol message sent by the network management center, extracts an OID and an operational order in the message, seeks a corresponding sub-device through the mapping relational file and performing the corresponding operational order for completing the management operation. The primary device in the invention is the primary device for implementing the above-mentioned method. The method and device in the invention realize dynamic update of the MIB file in the network device management, improve management efficiency and have evident advantages.
Description
Technical field
The present invention relates to the SNMP field of network management, particularly relate to a kind of network device management method based on snmp protocol and main equipment thereof.
Background technology
Along with the development of networking, increasing equipment and solution need provide snmp protocol support to be linked in the network, so that the center can manage by unified snmp protocol.In the SNMP network management system, the data variable that is managed of managed devices all is conceptualized as object, the set of managed object is organized as management information bank (MIB) and is stored in the main equipment (AGENT), each managed object is endowed an object identifier (OID) in MIB, network management system (NMS) is located managed object by OID, and by object value among the MIB read and revise the management that realizes subset.Wherein main equipment also utilizes the TRAP message report to report critical event to NMS.
Because in the SNMP network management, all are managed resource and all need to be recorded among the MIB after abstract, development along with technology, equipment increases in the SNMP network management, the interpolation of equipment, change also more frequent, and equipment adds, changes and all need mib file is upgraded each time, and equipment is carried out Installation and Debugging.In the prior art, the mib file in the main equipment generally can't upgrade dynamically, and need to carry out complicated writing, debug etc., and the efficiency of management is low.
Summary of the invention
Technical problem to be solved by this invention is, a kind of network device management method based on snmp protocol is provided, and the method can realize dynamically updating of mib file.
Another technical problem to be solved by this invention is, a kind of main equipment of the network apparatus management system based on snmp protocol is provided, this main equipment is when access is new when being managed subset or receives instruction, can in time generate or the renewal mib file by the data file in the equipment, and then realization is to compatibility, the management of equipment.
For solving above-mentioned first technical problem, the invention provides a kind of network device management method based on snmp protocol, main equipment communicates and carries out network management center to the operational order of subset by snmp protocol and network management center, may further comprise the steps:
A, main equipment read and resolve equipment template and the device instance file in the main equipment memory, and deposit in the integrate information array after the subset information in described equipment template and the described device instance file mated, integrates;
B, main equipment are according to mib file and mapping relations file in the generation of the data in the described integrate information array or the renewal main equipment, and described mapped file is for the mapping relations of the OID that records described mib file leaf node and device id and signal ID, control ID;
C, main equipment are uploaded to described mib file the snmp protocol message of network management center and the transmission of receiving network managing center, extract OID and operational order in the message, and according to extracting OID and subset corresponding to described mapping relations ff that obtains, subset is carried out corresponding operational order.
Owing to adopted above steps, in new subset access management system or when receiving keeper's instruction, the method can be by the equipment template in the main equipment and the data in the example message file, mib file is dynamically updated or generates new mib file in real time, thereby realize fast the management to subset, simplified the equipment debugging process, improved network management efficiency, particularly in telemanagement, the method can realize rapidly the access of new equipment.
As a kind of form of implementation of the inventive method, in the steps A, the subset information in the described equipment template comprises: the signal ID of template ID and corresponding subset, control ID; Subset information in the described device instance file comprises: template ID and device id; Main equipment mates the subset information in described equipment template and the described device instance file, integrate by template ID.
Preferably, also comprise following information in the described integrate information array: subset title, signal number, control number, described signal number, control number represent respectively the signal number, the control number that comprise for subset.As further preferred version, also comprise signal name and control name information.
Preferably, also comprise management type information in the described mapping relations file, described management type information is used for judging that corresponding with it OID leaf node is signal or the control in the corresponding subset, this preferred version can be optimized the list structure of mapping relations file, is that the mapping relations file structure is simpler.
The same with existing SNMP network management, main equipment of the present invention is also informed the anomalous event of subset to network management center, and this anomalous event sends network management center to by the message report of set form.
For solving aforementioned second technical problem, the invention provides a kind of main equipment of the network apparatus management system based on snmp protocol, comprise management program module, MIB module, comprise mib file in the described MIB module, it is characterized in that: also comprise data file module, MIB generation module, described data file module comprises equipment template and device instance file, records the information of all signal ID and the control ID of corresponding subset in the described equipment template; Described device instance file is used for record and the actual subset information that is connected of main equipment;
Described MIB generation module is used for reading the information of described equipment template and device instance file, coupling, deposit in the integrate information array after integrating, and generate mib file and be sent to described MIB module or upgrade existing mib file in the described MIB module according to described integrate information array.
Preferably, described equipment template is assigned template ID, and described subset information comprises the template ID of the equipment template that this subset is applicable; Described MIB generation module mates the information of described equipment template and device instance file by template ID.
Preferably, described MIB module also comprises the mapping relations file, and described mapping relations file is for the mapping relations of the OID that records described mib file leaf node and device id and signal ID, control ID; Described MIB generation module generates described mapping relations file according to described integrate information array or described mapping relations file is upgraded.
Preferably, comprise management type information in the described mapping relations file, described management type information is used for representing that corresponding with it OID leaf node is signal or the control in the corresponding subset.
The beneficial effect of the network device management equipment based on snmp protocol of the present invention is, when receiving that keeper's instruction or equipment Inspection are when having the access of new subset, main equipment can dynamically update MIB and mapping relations file timely, has improved network management efficiency.
Description of drawings
Fig. 1 is the equipment connecting relation schematic diagram of the specific embodiment of the invention;
Fig. 2 is the network management FB(flow block) of the specific embodiment of the invention;
Fig. 3 is the data structure schematic diagram of the mapping relations file raw.cfg table of the specific embodiment of the invention.
Embodiment
Be more detailed elaboration the present invention, present invention is described below in conjunction with embodiment.
As shown in Figure 1, be the equipment connecting relation schematic diagram of this embodiment.
The network apparatus management system based on snmp protocol of this embodiment comprises network management center (NMS), main equipment, temperature sensor, a UPS (can comprise more subset in practical application); Described NMS is connected with described main equipment, and described temperature sensor, UPS are connected with described main equipment by 232 interfaces, RS485 interface respectively, communicate by snmp protocol between described NMS and described main equipment.Wherein, each subset (such as temperature sensor etc.) being designed with the separately equipment template of XML-based form, template comprises the elements such as signal, control and event, and each template has a template ID number, and signal, control also have oneself ID number.
Also comprise a MIB generation module and a data file module in the main equipment, comprise equipment template type file and a device instance file in the described data file module, (starting of filename is EquipmentTemplate to comprise the equipment template of all subsets that main equipment supports in the equipment template type file, file is the XML form), the information in the equipment template comprises: the signal number of template ID and corresponding subset, signal ID and signal name; Control number, control ID and control title.Also (starting of filename is MonitorUnits to described device instance file for the file of XML form, hereinafter to be referred as the MU file), the MU file is used for device id, the device name of the subset that record actual motion environment is connected with main equipment and is used to specify the template ID which equipment template this subset is suitable for.
Comprise in the described MIB generation module that a MIB generates application program, when the operating instruction of receiving the keeper or when detecting new subset access main equipment, the MIB generation module moves this MIB and generates application program, the running that this MIB generates application program hereinafter specifically describes as an example of temperature sensor and ups power example as shown in Figure 2:
The program operation, the first step: at first the storage directory of read data files module and wish generate the output directory of mib file and mapping relations file (file is called raw.cfg);
Second step: (namely start when filename and be EquipmentTemplate according to all devices template and MU file in the filename read data files module, file format is that the XML form is then thought the equipment template, file is started and is MonitorUnits, file format is that the XML form is then thought the MU file), wherein the filename of the equipment template of temperature sensor and ups power is respectively EquipmentTemplateIDU_S.xml and EquipmentTemplate LIEBERT peace holy three and advances singly to go out UPS (UH31) .xml; The file of MU file is called MonitorUnitsIDU_S2.xml.
The 3rd step: resolve the MonitorUnitsIDU_S2.xml file, obtain device id, device name and the equipment template ID data of storing in the file, and these data are deposited in the Template Information array.
The 4th step: resolve EquipmentTemplateIDU_S.xml and EquipmentTemplate LIEBERT peace holy three and advance singly to go out UPS (UH31) .xml file, extract the equipment template ID in above-mentioned two files, the ID of signal, control or event, and deposit in the facility information array.
The 5th step: according to the corporate data template ID in Template Information array and the facility information array, data in two arrays are mated one by one, and integrate two data in the array and deposit in the integrate information array, thereby the information in this array comprises: device id, device name, equipment template ID, signal ID and signal number, control ID and control number, control title, signal name.
The 6th step: according to described integrate information array, generate mib file and the mapping relations file raw.cfg of standard.
The below is described in detail said process as an example of subset temperature sensor and ups power example: (hereinafter as exectorial output for example, the explanatory note of the content in its bracket for adding)
(step: obtain MU filename and equipment template filename)
MU file MonitorUnitsIDU_S2.xml (this is the MU filename)
EquipFile[0] EquipmentTemplateIDU_S.xml (the equipment template filename of temperature sensor)
EquipFile[1] EquipmentTemplate LIEBERT peace holy three advances singly to go out UPS (UH31) .xml
(the equipment template filename of ups power)
(step: obtain the device instance information in the MU file)
PStruEquipInfo[0]: (the device instance information of temperature sensor)
EquipId 1000 (device id of temperature sensor)
EquipTemplateId 755000021 (the equipment template ID that device id is corresponding)
EquipName SerialTH0 (device name)
PStruEquipInfo[1]: (the device instance information of ups power)
EquipId 1001
EquipTemplateId 755000022
EquipName UPS(UH31)
(step: obtain the facility information in the equipment template)
[0] EquipmentTemplateIDU_S.xml (the equipment template filename that the equipment template of temperature sensor is corresponding, following information is obtained from this file)
IEquipTempId 755000021 (the equipment template ID value of temperature sensor)
ISigNum 9 (the signal number that this equipment template comprises)
iSigId 51160004 szSigName Temperature5
iSigId 51160005 szSigName Temperature6
iSigId 51160007 szSigName Temperature8
ICtrlNum 2 (the control number that this equipment template comprises)
ICtrlId 51360000 szCtrlName Relay1 (control ID value and control title)
iCtrlId 51360001 szCtrlName Relay2
[1] EquipmentTemplate LIEBERT peace holy three advances singly to go out UPS (UH31) .xml (second equipment template filename that the equipment template is corresponding, following information is obtained) from this file
iEquipTempId 755000022
ISigId 3110001 szSigName exchange input A phase voltage
ISigId 3110002 szSigName exchange input B phase voltage
ISigId 3110003 szSigName exchange input C phase voltage
ISigId 3110004 szSigName exchange output A phase voltage
ISigId 3110005 szSigName exchange output B phase voltage
ISigId 3110006 szSigName exchange output C phase voltage
ISigId 3110007 szSigName exchange output A phase current
ISigId 3110008 szSigName exchange output B phase current
ISigId 3110009 szSigName exchange output C phase current
ISigId 3110010 szSigName DC input voitage (just organizing)
ISigId 3110011 szSigName output frequencies
ISigId 3110012 szSigName indicate number of batteries
ISigId 3110013 szSigName indicate temperature quantity
The iCtrlId 3130001 szCtrlName storage battery total voltage upper limits
ICtrlId 3130002 szCtrlName storage battery total voltage lower limits
The new control 3136000 of iCtrlId 3136000 szCtrlName
(step: coupling, integration obtain the integrate information array)
[0] SerialTH0 (information that first subset is corresponding, this row is device name)
IEquipId 1000 (device id)
IEquipTempId 755000021 (equipment template ID can know that according to this value his the equipment template of correspondence is EquipmentTemplateIDU_S.xml)
ISigNum 9 (just know signal and the control information that this subset has according to equipment template corresponding to this subset, follow the same of EquipmentTemplateIDU_S.xml the inside)
iSigId 51160007 szSigName temperature8
iCtrlNum 2
iCtrlId 51360000 szCtrlName relay1
iCtrlId 51360001 szCtrlName relay2
[1] UPS (UH31) (second information that subset is corresponding, this row are the subset titles)
IEquipId 1001 (device id)
IEquipTempId 755000022 (equipment template ID can know that according to this value the equipment template of his correspondence is that EquipmentTemplate LIEBERT peace holy three advances singly to go out UPS (UH31) .xml)
ISigNum 13 (just know signal and the control information that this device instance has according to equipment template corresponding to this device instance, advance singly to go out in UPS (UH31) the .xml file with EquipmentTemplate LIEBERT peace holy three)
ISigId 3110001szSigName exchanges input A phase voltage
ISigId 3110002szSigName exchanges input B phase voltage
ISigId 3110003szSigName exchanges input C phase voltage
ISigId 3110004szSigName exchanges output A phase voltage
ISigId 3110005szSigName exchanges output B phase voltage
ISigId 3110006szSigName exchanges output C phase voltage
ISigId 3110007szSigName exchanges output A phase current
ISigId 3110008szSigName exchanges output B phase current
ISigId 3110009szSigName exchanges output C phase current
ISigId 3110010szSigName DC input voitage (just organizing)
ISigId 3110011szSigName output frequency
ISigId 3110012szSigName indicates number of batteries
ISigId 3110013szSigName indicates temperature quantity
The iCtrlId 3130001szCtrlName storage battery total voltage upper limit
ICtrlId 3130002szCtrlName storage battery total voltage lower limit
The new control 3136000 of iCtrlId 3136000szCtrlName
Characteristics according to the target mib file, only have leaf node and Section Point to change, and the information of these nodes all is included in the above-mentioned integrate information array, described MIB generation module is according to the format characteristic of the data in the above-mentioned integrate information array and target mib file, for each information or control (being the leaf node of MIB) distribute OID number, generate the mib file of standard or upgrade existing mib file; Generate simultaneously a mapping relations file raw.cfg or upgrade existing mapping relations file, described mapping relations list file is the form of cfg form, recorded in this document: the mapping relations of the OID of leaf node and management type information (ID_TYPE), device id and signal ID or control ID in the mib file, described ID_TYPE is used for difference and represents that corresponding with it OID leaf node is signal or the control of corresponding subset, and the data structure schematic diagram of mapping relations table as shown in Figure 3.
After mib file and mapping relations file generated or the renewal, mib file after main equipment will upgrade sends network management center to, network management center is resolved the mib file after this renewal and OID and the operational order of the object that will implement to manage by the snmp protocol message send to main equipment, after main equipment receives this snmp protocol message, extract OID and operational order in its message, by its corresponding subset of described mapping relations ff, and carry out corresponding operational order.
The main equipment of present embodiment also can initiatively send the anomalous event message (TRAP message) of subset to network management center, the processes such as the generation of this message, reception are same as the prior art.
Above content is the further description of the present invention being done in conjunction with concrete preferred implementation, can not assert that implementation of the present invention is confined to these explanations.For those skilled in the art, without departing from the inventive concept of the premise, can also make some simple deduction or replace, all should be considered as belonging to protection scope of the present invention.
Claims (10)
1. network device management method based on snmp protocol, main equipment communicates and carries out network management center to the operational order of subset by snmp protocol and network management center; When the operating instruction of receiving the keeper or when detecting new subset access main equipment, carry out following steps:
A, main equipment read and resolve equipment template and the device instance file in the main equipment memory, and deposit in the integrate information array after the subset information in described equipment template and the described device instance file mated, integrates;
B, main equipment are according to mib file and mapping relations file in the generation of the data in the described integrate information array or the renewal main equipment, and described mapping relations file is used for recording OID and the device id of subset and the mapping relations of signal ID, control ID of described mib file leaf node;
C, main equipment are uploaded to described mib file the snmp protocol message of network management center and the transmission of receiving network managing center, extract OID and operational order in the message, and according to extracting OID and subset corresponding to described mapping relations ff that obtains, subset is carried out corresponding operational order.
2. the network device management method based on snmp protocol according to claim 1, it is characterized in that: in the described steps A, the subset information in the described equipment template comprises: the signal ID of template ID and corresponding subset, control ID; Subset information in the described device instance file comprises: template ID and device id; Main equipment mates the subset information in described equipment template and the described device instance file, integrate by template ID.
3. the network device management method based on snmp protocol according to claim 1 is characterized in that: also comprise step D: when subset had anomalous event to occur, described main equipment initiatively sent the report of subset unexpected message to network management center.
4. the network device management method based on snmp protocol according to claim 2, it is characterized in that: also comprise following information in the described integrate information array: subset title, signal number, control number, described signal number, control number represent respectively signal number, the control number that corresponding subset comprises.
5. it is characterized in that: also comprise following information in the described integrate information array according to claim 2 or 4 described network device management methods based on snmp protocol: signal name, control title.
6. the network device management method based on snmp protocol according to claim 1, it is characterized in that: also comprise management type information in the described mapping relations file, described management type information is used for representing that corresponding with it OID leaf node is signal or the control that corresponds in the subset.
7. main equipment based on the network apparatus management system of snmp protocol, comprise management program module, MIB module, comprise mib file in the described MIB module, it is characterized in that: also comprise data file module, MIB generation module, described data file module comprises equipment template and device instance file, records the information of all signal ID and the control ID of corresponding subset in the described equipment template; Described device instance file is used for record and the actual subset information that is connected of main equipment;
Described MIB generation module is used for when the operating instruction of receiving the keeper or when detecting new subset and accessing main equipment, read the information of described equipment template and device instance file, coupling, deposit in the integrate information array after integrating, and generate mib file and be sent to described MIB module or upgrade existing mib file in the described MIB module according to described integrate information array;
Also comprise the mapping relations file in the described MIB module, described mapping relations file is used for recording OID and the device id of subset and the mapping relations of signal ID, control ID of described mib file leaf node; Described MIB generation module is also for generating described mapping relations file according to described integrate information array or described mapping relations file being upgraded.
8. main equipment according to claim 7, it is characterized in that: described equipment template is assigned template ID, and described subset information comprises the template ID of the equipment template that this subset is applicable; Described MIB generation module mates the information of described equipment template and device instance file by template ID.
9. main equipment according to claim 7, it is characterized in that: described MIB module also comprises the mapping relations file, and described mapping relations file is for the mapping relations of the OID that records described mib file leaf node and subset device id and signal ID, control ID; Described MIB generation module generates described mapping relations file according to described integrate information array or described mapping relations file is upgraded.
10. main equipment according to claim 9 is characterized in that: comprise management type information in the described mapping relations file, described management type information be used for expression with it corresponding OID leaf node be signal or the control that corresponds in the subset.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201010240206 CN102185703B (en) | 2010-07-29 | 2010-07-29 | Network device management method based on SNMP protocol and primary device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201010240206 CN102185703B (en) | 2010-07-29 | 2010-07-29 | Network device management method based on SNMP protocol and primary device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102185703A CN102185703A (en) | 2011-09-14 |
| CN102185703B true CN102185703B (en) | 2013-10-23 |
Family
ID=44571776
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 201010240206 Active CN102185703B (en) | 2010-07-29 | 2010-07-29 | Network device management method based on SNMP protocol and primary device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102185703B (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102520941B (en) * | 2011-12-01 | 2014-12-10 | 大唐移动通信设备有限公司 | Method and device for generating executable documents |
| CN102571420B (en) * | 2011-12-20 | 2014-12-31 | 深圳市同洲电子股份有限公司 | Method and system for network element data management |
| CN102624552A (en) * | 2012-03-02 | 2012-08-01 | 瑞斯康达科技发展股份有限公司 | Configuration management method and configuration management device of network equipment |
| CN103997412B (en) * | 2013-02-18 | 2018-01-02 | 中兴通讯股份有限公司 | Management information base file generation method and device, data handling system |
| CN103297439B (en) * | 2013-06-24 | 2016-09-28 | 福建星网锐捷网络有限公司 | The control method of AC group facility based on SNMP, Apparatus and system |
| CN106685675A (en) * | 2015-11-05 | 2017-05-17 | 中兴通讯股份有限公司 | Network management method, apparatus, network equipment and data synchronization system |
| CN107453949A (en) * | 2017-07-31 | 2017-12-08 | 郑州云海信息技术有限公司 | A kind of method and device of monitoring management |
| CN108509187B (en) * | 2018-03-29 | 2021-05-18 | 烽火通信科技股份有限公司 | Method and system for automatically generating MIB function code of software platform |
| CN110620674B (en) * | 2018-06-20 | 2022-05-31 | 中兴通讯股份有限公司 | Configuration method of monitoring system and computer equipment |
| CN109787820A (en) * | 2019-01-02 | 2019-05-21 | 郑州云海信息技术有限公司 | A kind of snmp protocol detection method, device, terminal and storage medium |
| CN113052442A (en) * | 2021-03-09 | 2021-06-29 | 合安科技技术有限公司 | Equipment information management method, equipment information acquisition method, related terminal and system |
| CN114244677B (en) * | 2021-11-29 | 2023-08-04 | 广东九博科技股份有限公司 | SNMP message analysis method, readable storage medium and computer equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1326280A (en) * | 2000-05-25 | 2001-12-12 | 美国阿尔卡塔尔资源有限合伙公司 | Network node control system and method by extendable representative use |
| KR20020078758A (en) * | 2001-04-10 | 2002-10-19 | 현대네트웍스 주식회사 | Network management device and method using mib name server |
| CN1819532A (en) * | 2006-03-15 | 2006-08-16 | 杭州华为三康技术有限公司 | Management information base processing method |
| CN1983962A (en) * | 2006-06-08 | 2007-06-20 | 华为技术有限公司 | Extended network managing system and method |
| CN101729286A (en) * | 2008-10-21 | 2010-06-09 | 大唐移动通信设备有限公司 | Method, device and system for modifying variables in management information base of agent terminal |
-
2010
- 2010-07-29 CN CN 201010240206 patent/CN102185703B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1326280A (en) * | 2000-05-25 | 2001-12-12 | 美国阿尔卡塔尔资源有限合伙公司 | Network node control system and method by extendable representative use |
| KR20020078758A (en) * | 2001-04-10 | 2002-10-19 | 현대네트웍스 주식회사 | Network management device and method using mib name server |
| CN1819532A (en) * | 2006-03-15 | 2006-08-16 | 杭州华为三康技术有限公司 | Management information base processing method |
| CN1983962A (en) * | 2006-06-08 | 2007-06-20 | 华为技术有限公司 | Extended network managing system and method |
| CN101729286A (en) * | 2008-10-21 | 2010-06-09 | 大唐移动通信设备有限公司 | Method, device and system for modifying variables in management information base of agent terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102185703A (en) | 2011-09-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102185703B (en) | Network device management method based on SNMP protocol and primary device | |
| US8792385B2 (en) | Method and device for auto-generating goose signal connection topology from substation level | |
| CN102089749B (en) | Method and apparatus for managing binding information about a bundle installed remotely in an osgi service platform | |
| CN103942063A (en) | Centralized configuration and remote deployment method for Java Web application | |
| CN101540700A (en) | Configuration linkage method, system, terminal and network equipment management server | |
| CN102638378B (en) | Mass storage system monitoring method integrating heterogeneous storage devices | |
| CN101369933A (en) | Automatic test method and system | |
| CN103235820A (en) | Data storage method and device in cluster system | |
| CN101309178B (en) | Parsing method and apparatus for automatic exchanging optical network systematic log information | |
| CN103390018A (en) | Web service data modeling and searching method based on SDD (service data description) | |
| CN104660447B (en) | A kind of management method of SNMP nodal informations and management system | |
| CN113658591A (en) | Voice interaction adaptation system for smart home | |
| CN101409723A (en) | Method for designing synthesis network management system based on ForCES protocol | |
| CN102136926B (en) | Method for actively collecting data and server for actively collecting data | |
| CN105337764A (en) | Equipment resource information acquisition method | |
| CN102034163A (en) | Method and system for managing asset information of telecommunication equipment | |
| CN102185381B (en) | Method for processing SCD (substation configuration description) iteration of SCD model during automatic switching | |
| CN107193563B (en) | Method for managing server stateless firmware version | |
| CN112333758B (en) | Stability monitoring management method, system and application of television gateway system | |
| CN103139806B (en) | Method and base station of the webmaster with base station configuration data decoupling | |
| KR101368500B1 (en) | Method for providing database history management and the database management system thereof | |
| CN101393554A (en) | Conversion method and device from IDL information to OWL information | |
| CN103236954B (en) | Mobile network's Web service evaluation system | |
| CN115878702A (en) | Method, device and equipment for realizing operation and maintenance data acquisition | |
| Shen et al. | Standardizing the Internet of Things in an evolutionary way |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 518057 Nanshan District science and Technology Industrial Park, Guangdong, Shenzhen Branch Road, No. Patentee after: Vitamin Technology Co., Ltd. Address before: 518057 Nanshan District science and Technology Industrial Park, Guangdong, Shenzhen Branch Road, No. Patentee before: Aimosheng Network Energy Source Co., Ltd. |