CN101572624A - Cross-platform cross-method SNMP extension MIB realization method - Google Patents
Cross-platform cross-method SNMP extension MIB realization method Download PDFInfo
- Publication number
- CN101572624A CN101572624A CNA2009100580114A CN200910058011A CN101572624A CN 101572624 A CN101572624 A CN 101572624A CN A2009100580114 A CNA2009100580114 A CN A2009100580114A CN 200910058011 A CN200910058011 A CN 200910058011A CN 101572624 A CN101572624 A CN 101572624A
- Authority
- CN
- China
- Prior art keywords
- mib
- interface
- framework
- function
- expansion
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 89
- 238000011161 development Methods 0.000 claims abstract description 18
- 230000008569 process Effects 0.000 claims abstract description 18
- 230000007246 mechanism Effects 0.000 claims description 13
- 238000012545 processing Methods 0.000 claims description 12
- 238000013461 design Methods 0.000 claims description 10
- 238000005538 encapsulation Methods 0.000 claims description 7
- 230000008676 import Effects 0.000 claims description 5
- 238000013459 approach Methods 0.000 claims description 4
- 230000002093 peripheral effect Effects 0.000 claims description 3
- 230000006870 function Effects 0.000 description 46
- 238000005516 engineering process Methods 0.000 description 14
- 238000004891 communication Methods 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 239000011800 void material Substances 0.000 description 2
- 108700010388 MIBs Proteins 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
Images
Landscapes
- Computer And Data Communications (AREA)
Abstract
The invention relates to a cross-platform cross-method SNMP extension MIB realization method, and belongs to the category of computer network management. An intermediate layer is established between an SNMP main agent and an SNMP sub-agent. The interface of the intermediate layer is provided with two levels of frameworks, wherein a first level framework is a framework special for expansion agent development, a second level framework is an expansion agent framework EAgentX++ containing the API programming interfaces of a plurality of different expansion agent development techniques, and the two levels of frameworks are packaged in an AgentFrame. A simple interface is provided for the outside use. A developer only needs providing the codes which have to be finished by the developer in a similar space filling mode, and cannot experience the difference between different platforms and methods in the development process. The method can realize quick expansion. When a new SNMP expansion technique appears, the interface can be used to add the new technique into the package, while the interface remains unchanged. Therefore, the method continuously adapts to demands and requirements in new modes.
Description
Technical field
The invention belongs to the SNMP extension MIB implementation method of computer network management technology category, particularly a kind of cross-platform cross-method.
Background technology
SNMP (Simple Network Manage Protocol is a simple network management) technology is the de facto standard of network management, also is the technology that must grasp in the webmastering software exploitation.The SNMP technology can be divided into two aspects from the transmitting-receiving of order: management station and agent side.Management station's exploitation is relatively more commonly used also fairly simple, and agent side is provided by the embedded system in operating system or the networking products generally speaking.
Usually having equipment or software even bigger application system does not in actual applications provide based on SNMP but monitoring hardware interface and agreement based on other modes is provided, and the system for using third party NMS software can not monitor this equipment.In order to solve this class problem, the UNIX operating system of the nearly all SNMP of providing service all provides the api interface of extension MIB, make things convenient for the developer to provide MIB (Management Information Base is a management information bank) information based on SNMP for these equipment and software, these mib informations that are expanded realization are called extension MIB, the software of realizing extension MIB is generally process or dynamic base, be called as the expansion agency, expansion agency one side and monitored hardware or software systems are passed through privately owned, nonstandard protocol communication, one side use the snmp protocol of standard that the mib information of expansion externally is provided.The extension MIB technology is with a long history, and method and agreement are numerous, and be widely different, and any one interface has suitable difficulty in the study.
In the SNMP exploitation, agency's exploitation generally is divided into two classes: 1. similar Agent++ generates specific mib information for special applications like this; 2. use each platform to carry the extension mechanism that the SNMP master agent provides, promptly use expansion to act on behalf of development technique, use the expansion agent skill group to realize that agency by agreement has following advantage:
1, general, realize that expansion agency's function interface and data-interface are that each supports the operating system of SNMP all can provide;
2, expansion agency's function interface and data-interface are that each provides the process of SNMP agency service all to realize;
3, the MIB subtree of expansion agency generation is the expansion to system standard MIB tree, meets the expansion standard of MIB tree itself;
4, the expansion agency is based on the expansion of the SNMP agency service of operating system grade, and the part of expansion is to offer management station as the part that this operating system SNMP realizes;
5, expansion agency and the original SNMP proxy class of system are like father and son's relation, and the expansion agency generally is also referred to as sub agent, and this has also reflected the correspondence between sub agent and the master agent;
6, the expansion agency supports Trap mechanism.
As one of the most complicated SNMP basic technology, use expansion proxy interface exploitation agency by agreement that the right technological difficulties of following demand side are arranged:
1, the expansion agent skill group is with a long history, of a great variety, from early stage SMUX, and the EAgent that DPI is popular till now;
2, different with the performance of a kind of expansion agent skill group, as the SMUX agreement on the AIX and show different under the LINUX;
3, the expansion agency's who provides under the different operating system platform mechanism is different, and difference is huge;
4, same operating system the multiple extended method of acting on behalf of may be provided, difference is huge;
5, the same but expansion DLL (dynamic link library) difference of the extension mechanism that exists of different operating system;
6, the very big difference in above 5 programmings that difference caused.
Summary of the invention
The SNMP extension MIB implementation method that the purpose of this invention is to provide a kind of cross-platform cross-method, solution is when providing based on the SNMP interface under the unix platform for the hardware and software system, learning difficulty is big under multiple unix platform, the time is long for the expansion agent skill group, the shortcoming of support team's exploitation is not implemented expansion fast.
The objective of the invention is to reach like this:
A kind of SNMP extension MIB implementation method of cross-platform cross-method is characterized in that: the intermediate layer of setting up an exploitation extension MIB between SNMP master agent and SNMP sub agent.This intermediate layer interface is provided with the two-stage framework, first order framework is the framework that is specifically designed to expansion agency exploitation, comprise cross-platform serial ports, network transmitting-receiving interface and byte stream fast processing storehouse, the required many peripheral functional modules of expansion Agent, these modules are encapsulated in to be acted on behalf of in the Development Framework AgentFrame; Second level framework is expansion agent framework EAgentX++, contain some different expansions and act on behalf of the API DLL (dynamic link library) of development technique, comprise an initialization process interface, operation and event handling interface, one can be the mechanism of OID configuration call back function to the nodal information of describing in the mib file, this framework is encapsulated in the AgentFrame with first order framework.In the EAgentX++ development and Design, skip every kind of expansion agency's RFC document, according to the details encapsulation of the common interface of EAgentX++ design, realize that this interface is constant but can constantly add the C++ DLL (dynamic link library) of new extension MIB method specific to different platform and different Extended Protocols.Finished traditional expansion agency's basic step in interface: (a) initialization of MIB, (b) connect with master agent, the registration of (c) MIB, (d) wait for that request, (e) receive request, (f) sends processing of request, (g) result; To (a) in the basic step (b) (c) do initialization process as the initialization section of framework; In the step (e) and (g) provided by expansion agency's api function fully, (d) trigger by select mechanism or by expansion agency's api function, step (e), (g), (d) are all packed to be advanced in operation and the event handling interface; The then complete user by this method of step (f) realizes voluntarily according to the call back function mechanism that disposes and finishes.
Described have an initialization process interface in the framework of the second level, it is the initialization process of in initialization interface, finishing each each method of platform, import two parameters into, first parameter p InitFunc is the function of MIB node OID information initializing, import into as a function pointer, finish the structure of MIB tree.Second parameter is configuration file, the title that comprises mib file, realize the root node OID of subtree, community's name, and individual platform and the method def filename that need use, in the function that pInitFunc points to, with information and the readjustment processing adding type of each node OID in the mib file is in the tabulation of SETree, in the InitEAgentx function, finish read configuration file and finish every kind of different platform and initialization process that method expansion agency is specific after, call the call back function that pInitFunc points to, obtain needing to handle all nodal informations of MIB, call the specific MIB registration function of different platform and extended method then, finish initialization.
Described in the framework of the second level operation and event handling interface and the call back function of OID configuration is called is that driving function by by name _ Run provides, after initialization is finished, _ Run driving function is finished: various expansion agencies send into the Fd with the master agent net connection wait submit state that forms asynchronous reception in select function or the similar approach, Fd is set when the request of receiving master agent, to obtain the type and the ODI information of this request afterwards, its type of obtaining this request is a kind of among Set or Get or the Get Next, the EsetFunc of the ODI of the correspondence of registering when at this moment being invoked at initialization or EgetFunc call back function, the specific function that calls different platform and method is at last finished the submission work to master agent.
Good effect of the present invention is: set up an intermediate layer between SNMP master agent and SNMP sub agent, realized the quick exploitation of SNMP extension MIB cross-platform cross-method.The interface that this method provides has carried out the encapsulation of expert's level, has adopted the two-stage frame structure, externally provides simple interface to satisfy general developer's quick exploitation needs.The developer use this method can: 1. exploitation realizes monitoring communications work with hardware device apace; 2. the processing of configuration MIB node under the situation that SNMP knowledge is only done to understand, the function that calling two these methods then provides can be finished the work that needs a large amount of study just can finish; 3. for the hardware device of not supporting SNMP provides standardized SNMP monitor-interface, the convenient third party of use monitoring software is implemented monitoring to hardware.This interface is owing to have a generality, and the extension MIB technology of the unix system in future is also provided support.When new SNMP expansion technique occurs, all be the general character interface that expansion agency must provide because interface provides, thus can use top technology to join in the encapsulation equally, and keep interface constant, constantly adapt to the needs and the requirement of new model.
Description of drawings
Fig. 1 is that AgentFrame acts on behalf of the Development Framework structure chart;
Fig. 2 is the EAgentX++ structure chart;
Fig. 3 initialization realizes schematic diagram;
Fig. 4 _ Run function is realized schematic diagram.
Embodiment
The present invention has adopted the two-stage framework, the one-level framework solves mainly that to write under the unix platform select multiplexed, act on behalf of programming problems such as asynchronous reception external data, the secondary framework mainly solves the problem of the MIBization of proxy information, and these two frameworks have finally been realized the SNMP scaling problem of cross-platform cross-method.
Above two-stage framework is to be the custom-designed framework that is used to expand agency's exploitation of convenient exploitation, and the class in the framework cooperates with each other, and the agency provides reusable framework for expansion.The developer uses this framework can pay close attention to concrete application itself better.Target be by in framework, add few code develop stable, expand agent software efficiently.
Exploitation based on framework makes the developer very little to the development amount of individual task, and less workload can guarantee that less mistake takes place, and implements exploitation fast so be fit to very much team; Because most of development is similar, so can confirm that several typical examples are as template in expansion agency's development, the developer as with reference to implementing coding, can realize the standardization of encoding with this, and this has further guaranteed development quality.
In the hardware of monitor-interface is provided, provide the in the majority of monitor message with serial ports form and latticed form as means of communication, cross-platform serial ports class and network transmitting-receiving interface is provided in this framework, the byte stream fast processing storehouse of a streamproc by name is also arranged specially at the byte stream characteristic of serial data simultaneously.
As shown in Figure 1; AgentFrame has encapsulated and has developed the required many peripheral functions of expansion Agent; spiritization (Daemon) as process; multiplexed (multiplex); log interface (Log); byte stream is handled (StreamProc); thread pool (Thread_pool); serial ports storehouse (serial); timer (Timer); network (NetWork) etc.; these functions generally are that the developer is implementing to develop alone and easy concealing errors through regular meeting in the monitoring communication with hardware device; by writing these services; guaranteed the reliable of most of code, can finish development as long as the user of framework writes necessary code.For example, if be an agency by agreement that the equipment development that uses serial ports to insert is monitored, just can in the very short time, finish the coding work of the transmission-receiving function of data by configuration, use serial ports storehouse and byte stream fast processing storehouse and incident splitter.
The secondary framework is provided with at expansion agency 6 exploitations difficult point.The structure of this interface as shown in Figure 2.
Structure among the figure has embodied interface and the design philosophy that realizes separating, wherein E1, E2, E3 ... .En act on behalf of the API DLL (dynamic link library) of development technique for different expansions, by OO one by one encapsulation to them, pass through the abstract of complexity then, use outward appearance and factory mode, unified DLL (dynamic link library) externally is provided.Design at generality on this Interface design, to the concrete difference of caller shield technology itself based on expansion SNMP technology.When have new SNMP expansion technique to occur future, all be the general character interface that expansion agency must provide because interface provides, thus can use top technology to join in the encapsulation of EAgentX++ equally, and keep interface constant.
The Important Thought of EAgentX++ is: skip every kind of expansion agency's RFC document, as describing the RFC1227 of SMUX, describe the RFC1228 of DPI, describe the RFC2741 of AgentX; By studying api interface and the programming example that these technology provide at each platform carefully, details encapsulation specific to different platform and different agreement is carried out in design according to the common interface of EAgentX++ then, finally realizes the constant and C++ DLL (dynamic link library) that can constantly add on realizing of interface; The precedent of also not doing does not so both at home and abroad at present equally have the such interface class that can hold numerous Extended Protocols yet.
The realization of expansion Proxy Method, the SNMP expansion agency who is based upon various unix platform realizes on the basis of example.To Smux agreement (SNMP Multiplexing Protocol is SNMP multichannel agreement rfc1227), SNMP-DPI (Simple Network Management Protocol DistributedProgram Interface is a SNMP distribution DLL (dynamic link library)), eSNMP (Extensible Simple NetworkManagement Protocol is a scalable network management agreement), after the SNMP extension MIB methods analyst of realizing on AgentX a plurality of unix systems such as (Agent eXtensibility are a scalable network management agreement RFC 2741), interface and the implementation method that can find different agency's expansions are all inequality, and the version of the snmp protocol of being followed is also different, and same agreement also might be different in the implementation method of different platform.But its basic step is more or less the same, and by studying the implementation method of these different platforms and distinct methods extension MIB, obtains the function that the expansion interface of cross-platform cross-method need be realized, these functions also can be followed in the SNMP in future extended method:
1. initialization;
2. provide one can be the mechanism of OID (Object ID object ID) configuration call back function to the node among the MIB;
3. provide one can move the mechanism of constantly carrying out the SNMP event handling continuously for all requests.
Referring to Fig. 3, Fig. 4.
Initialization is an important process, at first sets up initialization interface.Initialization interface in this method is finished initialization and is provided one can be the function of the mechanism of OID configuration call back function to the node among the MIB, and its initialization definitions is as follows:
Void InitEAgentx (EInitFunc pInitFunc, const char*pszIniFile); Mainly finish the initialization process of each each method of platform in initialization interface, the function of the MIB node OID information initializing that provided by the user is provided first parameter p InitFunc; The title of the mib file that needs in the initialization realizes the root node OID of subtree, and community's name etc. comprise that these information such as def filename that individual platform need be used all describe in configuration file, and the name of configuration file is imported into as second parameter.
Configuration file is write by the philosophical works in the following example:
[mib]
treeName＝eagentx
treeOid＝1.3.6.1.4.1.17099
community＝public
[subTree]
num＝2
Name_1＝extTree
Oid_1＝3
Name_2＝mainTree
Oid_2＝0
[smux]
path＝eagentx.defs
entry＝eagentx
access＝write
Wherein comprise the subtree OID that the expansion agency realizes in [mib], generated the name of the sub agent process of this tree, community's name.[subTree] is the configuration information of subtree, needs the path of the defs file of use in [smux] for the realization of SMUX agreement, read-write properties;
After finishing the basic initialization information of each each method of platform, carry out the registration of mib information, initialization to mib information need be finished by user oneself, first initialization function pInitFunc imports into as a function pointer, mainly finish the structure of MIB tree, the type definition of pInitFunc be EInitFunc its be defined as follows:
Typedef void (* EInitFunc) (SETree ﹠amp; ); Finish the preparation that OID is handled.
This interface kit uses following data structure:
struct?ETreeNode
{
string?oid；
ESetFunc?pSetFunc；
EGetFunc?pGetFunc；
AccessEnum?access；
TypeEnum?type；
}；
This is the structure of a MIB node, in this structure, oid is the oid character string, and pSetFunc and pGetFunc are respectively the call back function of Set and Get processing, this needs user oneself to write to finish, and wherein the organization definition of EsetFunc and pGetFunc is as follows:
typedef?ErrorEnum(*ESetFunc)(EVarBindUnit*unit，int?index)；
typedef?ErrorEnum(*EGetFunc)(EVarBindUnit*unit，int?index)；
The information of the MIB tree that will realize leaves in the tabulation, is defined as follows:
map<int，ETreeNode>SETree；
In the function that pInitFunc points to, the user finishes the information of each node OID in the mib file and readjustment is handled the work that adds SETree.
In the InitEAgentx function, finish read configuration file and finish every kind of different platform and initialization process that method expansion agency is specific after, call the call back function that pInitFunc points to, obtain needing to handle all nodal informations of MIB, call the specific MIB registration function of different platform and extended method then, finish initialization.
Initialization function inside is embodied as realization to the calling of the extended method of different platform distinct methods, and is distinguished in the method for inner service condition compiling, is equipped with the factory mode that uses in the Design Mode simultaneously unified external interface is provided.
_ Run is a function of being responsible for operation and event handling in this method.To most of extension MIB technology, after initialization is finished, various expansion agencies generally will send into the Fd (filec descriptor) with the master agent net connection state registration submit state that forms asynchronous reception in select function or the similar approach, Fd is set when the request of receiving master agent, to obtain the type (Set/Get/Get Next) and the ODI information of this request afterwards, the EsetFunc of the ODI correspondence of the correspondence of registering when at this moment being invoked at initialization or EgetFunc call back function, after call back function executes, call the data of ad hoc approach and platform again and submit function to, promptly finish the above step of (g), finish whole request function.
Operation and event handling function be inner to be realized the calling of the extended method of different platform distinct methods distinguished in the method for inner service condition compiling, is equipped with the factory mode that uses in the Design Mode simultaneously unified external interface is provided.
It should be noted that: during some platforms is realized before the select function call, different extension MIBs has unique processing when realizing, these are more difficult to get by the routine that analytical system provides, and must read source code, as the processing of snmp_select_info function under the Linux platform.During realizing, used on some platform the mode of script generating code, when the extended method of these platforms is studied, light sees that the code of these generations is not enough, need further research could obtain to realize whole API of this method, control the code of increasing income as a thermometer that needs under the Linux platform to study a SNMPtherm by name carefully.
The present invention is inner use the in certain type air traffic control system that the applicant participates in and recording equipment, for a plurality of hardware devices, all software in the system all provide the extension MIB interface based on SNMP, the extend information of whole system also is provided simultaneously, wherein in the system level information MIB node above 1000, relate to all platforms of mentioning in the specification, effect is fairly obvious, and is easy to operate.
Claims (3)
1, a kind of SNMP extension MIB implementation method of cross-platform cross-method, it is characterized in that: the intermediate layer of between SNMP master agent and SNMP sub agent, setting up an exploitation extension MIB, this intermediate layer interface is provided with the two-stage framework, first order framework is the framework that is specifically designed to expansion agency exploitation, comprise cross-platform serial ports, network transmitting-receiving interface and byte stream fast processing storehouse, the required many peripheral functional modules of expansion Agent, these modules are encapsulated in to be acted on behalf of in the Development Framework AgentFrame; Second level framework is expansion agent framework EAgentX++, contain some different expansions and act on behalf of the API DLL (dynamic link library) of development technique, comprise an initialization process interface, operation and event handling interface, one can be the mechanism of OID configuration call back function to the nodal information of describing in the mib file, this framework is encapsulated in the AgentFrame with first order framework; In the EAgentX++ development and Design, skip every kind of expansion agency's RFC document, according to the details encapsulation of the common interface of EAgentX++ design, realize that this interface is constant but can constantly add the C++ DLL (dynamic link library) of new extension MIB method specific to different platform and different Extended Protocols; Finished traditional expansion agency's basic step in interface: (a) initialization of MIB, (b) connect with master agent, the registration of (c) MIB, (d) wait for that request, (e) receive request, (f) sends processing of request, (g) result; To (a) in the basic step (b) (c) do initialization process as the initialization section of framework; In the step (e) and (g) provided by expansion agency's api function fully, (d) trigger by select mechanism or by expansion agency's api function, step (e), (g), (d) are all packed to be advanced in operation and the event handling interface; The then complete user by this method of step (f) realizes voluntarily according to the call back function mechanism that disposes and finishes.
2, SNMP extension MIB implementation method as claimed in claim 1, it is characterized in that: described have an initialization process interface in the framework of the second level, it is the initialization process of in initialization interface, finishing each each method of platform, import two parameters into, first parameter p InitFunc is the function of MIB node OID information initializing, import into as a function pointer, finish the structure of MIB tree; Second parameter is configuration file, the title that comprises mib file, realize the root node OID of subtree, community's name, and individual platform and the method def filename that need use, in the function that pInitFunc points to, with information and the readjustment processing adding type of each node OID in the mib file is in the tabulation of SETree, in the InitEAgentx function, finish read configuration file and finish every kind of different platform and initialization process that method expansion agency is specific after, call the call back function that pInitFunc points to, obtain needing to handle all nodal informations of MIB, call the specific MIB registration function of different platform and extended method then, finish initialization.
3, SNMP extension MIB implementation method as claimed in claim 1, it is characterized in that: described in the framework of the second level operation and event handling interface and the call back function of OID configuration is called is that driving function by by name _ Run provides, after initialization is finished, _ Run driving function is finished: various expansion agencies send into the Fd with the master agent net connection wait submit state that forms asynchronous reception in select function or the similar approach, Fd is set when the request of receiving master agent, to obtain the type and the ODI information of this request afterwards, its type of obtaining this request is a kind of among Set or Get or the Get Next, the EsetFunc of the ODI of the correspondence of registering when at this moment being invoked at initialization or EgetFunc call back function, the specific function that calls different platform and method is at last finished the submission work to master agent.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009100580114A CN101572624B (en) | 2009-01-04 | 2009-01-04 | Cross-platform cross-method SNMP extension MIB realization method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009100580114A CN101572624B (en) | 2009-01-04 | 2009-01-04 | Cross-platform cross-method SNMP extension MIB realization method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101572624A true CN101572624A (en) | 2009-11-04 |
| CN101572624B CN101572624B (en) | 2011-06-08 |
Family
ID=41231863
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009100580114A Expired - Fee Related CN101572624B (en) | 2009-01-04 | 2009-01-04 | Cross-platform cross-method SNMP extension MIB realization method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101572624B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103532948A (en) * | 2013-10-11 | 2014-01-22 | 苏州新海宜通信科技股份有限公司 | Binary system communication structure |
| CN103731251A (en) * | 2012-10-12 | 2014-04-16 | 上海斐讯数据通信技术有限公司 | Rack-mounted equipment card synchronization system and synchronization method thereof |
| CN104301386A (en) * | 2014-11-03 | 2015-01-21 | 合一网络技术(北京)有限公司 | Server application system development framework and running method thereof |
| CN105187244A (en) * | 2015-08-21 | 2015-12-23 | 成都广达新网科技股份有限公司 | Access management system of digital communication equipment supporting multiple management modes |
| CN112148349A (en) * | 2020-07-03 | 2020-12-29 | 上海金融期货信息技术有限公司 | System for cross-platform instruction and configuration unified interface |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100337431C (en) * | 2003-10-22 | 2007-09-12 | 华为技术有限公司 | Development method of management agent for supporting simple network management protocol |
-
2009
- 2009-01-04 CN CN2009100580114A patent/CN101572624B/en not_active Expired - Fee Related
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103731251A (en) * | 2012-10-12 | 2014-04-16 | 上海斐讯数据通信技术有限公司 | Rack-mounted equipment card synchronization system and synchronization method thereof |
| CN103532948A (en) * | 2013-10-11 | 2014-01-22 | 苏州新海宜通信科技股份有限公司 | Binary system communication structure |
| CN104301386A (en) * | 2014-11-03 | 2015-01-21 | 合一网络技术(北京)有限公司 | Server application system development framework and running method thereof |
| CN104301386B (en) * | 2014-11-03 | 2015-11-11 | 合一网络技术(北京)有限公司 | Service end application system development frame mounting and operation method thereof |
| CN105187244A (en) * | 2015-08-21 | 2015-12-23 | 成都广达新网科技股份有限公司 | Access management system of digital communication equipment supporting multiple management modes |
| CN105187244B (en) * | 2015-08-21 | 2018-10-30 | 成都广达新网科技股份有限公司 | A kind of digital communication equipment access information management and its working method for supporting a variety of management modes |
| CN112148349A (en) * | 2020-07-03 | 2020-12-29 | 上海金融期货信息技术有限公司 | System for cross-platform instruction and configuration unified interface |
| CN112148349B (en) * | 2020-07-03 | 2024-03-15 | 上海金融期货信息技术有限公司 | Cross-platform instruction and system for configuring unified interface |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101572624B (en) | 2011-06-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7752598B2 (en) | Generating executable objects implementing methods for an information model | |
| US5931911A (en) | Information processing device enabling the management of an information resource by an administration system | |
| US7831724B2 (en) | Services layer model for providing standards-based communications | |
| US8713177B2 (en) | Remote management of networked systems using secure modular platform | |
| US20060143179A1 (en) | Apparatus and method for managing security policy information using a device management tree | |
| EP1241828A1 (en) | Gateway system and method providing a common generic interface to network management applications | |
| US20020087734A1 (en) | System and method for managing dependencies in a component-based system | |
| US20080301143A1 (en) | Automatic Update System and Method for Using a Meta Mib | |
| CN101572624B (en) | Cross-platform cross-method SNMP extension MIB realization method | |
| CN102447585A (en) | Method and device for converting network configuration protocol response message into command line | |
| CN103457761B (en) | Cross-platform command line configuration interface implementation method | |
| US8244844B2 (en) | Tool for data generation for simple network management protocol (SNMP) | |
| US20240205068A1 (en) | Using generic key-value pairs to configure ran component attributes in a ran system | |
| Goshi et al. | Pp5gs—an efficient procedure-based and stateless architecture for next-generation core networks | |
| CA2248634C (en) | Common connector framework | |
| CN113360386B (en) | Method and device for testing driving of switching chip, electronic equipment and storage medium | |
| WO2016197688A1 (en) | Data collection method and device | |
| CN105847047B (en) | A method of realizing that special OID is acquired and parsed in MIB using plug-in unitization | |
| US8806512B2 (en) | Collocation in a Java virtual machine of JSLEE, SIP servlets, and Java EE | |
| US20070220157A1 (en) | Simple network management protocol (SNMP) agent system and method | |
| CN103763325B (en) | Method for building IP security product development environment | |
| CN100369443C (en) | Method of following SNMP/CIM protocol intermediate piece projection | |
| US20070208842A1 (en) | Methods and systems for pushing and pulling network data in user interface design | |
| CN103684904A (en) | Tri-networks integration network monitoring system based on IP | |
| CN109274715A (en) | The platform resource management system of vehicle-mounted multi-channel communication systems |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110608 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |