CN101170451A - A device management method and a device proxy system - Google Patents
A device management method and a device proxy system Download PDFInfo
- Publication number
- CN101170451A CN101170451A CNA2007101947704A CN200710194770A CN101170451A CN 101170451 A CN101170451 A CN 101170451A CN A2007101947704 A CNA2007101947704 A CN A2007101947704A CN 200710194770 A CN200710194770 A CN 200710194770A CN 101170451 A CN101170451 A CN 101170451A
- Authority
- CN
- China
- Prior art keywords
- equipment
- snmp
- message
- sxp
- request message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Computer And Data Communications (AREA)
Abstract
The invention discloses a facility management method. In the method, a unified agent converts a received simple network management protocol SNMP request to a simple extended protocol SXP request, and then, the SXP request information is sent to an equipment by calling the interface which is corresponding to the SXP request information, thus, realizing the shielding of the SNMP information for the equipment, so the development of the equipment is more simple; furthermore, the unified agent can act as the agent of various equipments and improve the compatibility of the unified agent. In addition, the invention also provides an equipment agent system which is corresponding to the method, and the usage of the system can realize the detail of shielding SNMP information of the managed equipment.
Description
Technical field
The present invention relates to computer realm, relate in particular to a kind of device management method and a kind of proxy for equipment system.
Background technology
Network management based on TCP/IP comprises two parts: and network management system (NetworkManagement System, NMS) and managed device.Operational management process on the network management system, agent process then are processes that resides on the managed device.Communication protocol between managing process and the agent process is called Simple Network Management Protocol (Simple Network Management Protocol, SNMP), SNMP is the industrial standard that is widely accepted and comes into operation, use in the network management of this agreement, the network manager can retrieve the information of any node by network management system, then according to the node of the information trouble-shooting that retrieves, and finish failure diagnosis, capacity planning and report and generate.
Existing SNMP has defined between managing process and the agent process 5 kinds of messages when mutual:
1, Get request operation: managing process extracts one or more parameter values from agent process.
2, Set request operation: managing process is provided with one or more parameter values of agent process.
3, GetNext request operation: managing process extracts the next parameter value of closelying follow the parameter current value from agent process.
4, Get/Set response operation: one or more parameter values that agent process returns to managing process, or the response message that returns to managing process of agent process about Set request operation.This operation is sent by agent process.It is the operation response of previous action 1 or 2.
5, Trap operation: the message that agent process initiatively sends, the notice managing process has some thing to take place.
In a kind of simple network management method that prior art one provides, a NMS need manage a plurality of equipment, each managed device comprises an agent process, and in this agent process, preserve management information bank (the Management Information Base of this equipment self, MIB), that is: each managed device is realized the parsing of SNMP message separately and is responded accordingly, therefore, and the complexity height of NMS management work.In addition, because the MIB function that realizes is all fixed in each agent process, when MIB that needs expansion agent process is supported, the renewal of MIB causes agent process also must upgrade.As seen, prior art one can't promptly can not realize dynamic expansion supporting not change extension MIB under original agency's the situation.And the agency on many distributed apparatus or the complex device be made up of many standalone modules has the demand of dynamic expansion MIB, if to the independent agent process (expanding the MIB of each managed device) of each managed device exploitation, then development repeats, and efficient is low.
In order to solve the defective of prior art one, prior art two provides a kind of new Managed Solution, has wherein used the AgentX agreement.The AgentX protocol definition standard architecture that can expand SNMP agency, snmp protocol handled and MIB visits these two functions and decomposes, on structure, network agent is divided into master agent and two parts of sub agent: 1) master agent: the snmp protocol message that responsible processing is received, carry out information interaction with NMS, but generally do not possess the authority of MIB of the equipment of direct its management of visit; 2) plurality of sub agency: each sub agent is responsible for visiting local MIB.Master-proxy-process and sub agent process communicate by agent process X agreement.
As shown in Figure 1, in the scheme that prior art two provides, some managed devices can not only serve as master agent but also serve as sub agent: these equipment can be accepted the request command of NMS, and a part is relevant with the data of these equipment this locality in these request commands, another part is relevant to the data of all the other equipment of these equipment with " connection ": for the request command relevant with the data of equipment this locality, these equipment are directly replied the snmp message that NMS sends as sub agent, for with " connection " to the relevant request command of the data of all the other equipment of these equipment, the device request data that these equipment are just managed to them with the identity of master agent, the NMS under again response message having been passed to.
Therefore for network management system, the AgentX agreement is transparent.The AgentX structure has realized acting on behalf of dynamic expansion function flexibly by sub agent to the registration of master agent.But because master agent just uses the AgentX agreement that snmp message is sent to the equipment of its management simply, so each sub agent also must be concerned about the details of snmp protocol, and the sub agent exploitation is difficult.In addition because in the scheme that provides of prior art two, snmp message must change into agent process X message and be issued to each sub agent, so between master agent and the sub agent mutual frequent, efficient is low.
In sum, prior art can't be when the range of management of expansion SNMP, and equipment need not be concerned about the realization details of SNMP, and network management system is low to the efficiency of management of each equipment.
Summary of the invention
The invention provides a kind of device management method and a kind of proxy for equipment system, in order to solve exist in the prior art when the range of management of expansion SNMP, equipment must be concerned about realization details and the network management system problem low to the efficiency of management of each equipment of SNMP.
A kind of device management method that the embodiment of the invention provides comprises:
Unified agent UA receives and resolves the Simple Network Management Protocol SNMP request message that network management system NMS sends;
Described UA determines described SNMP request message corresponding equipment;
Described UA converts described SNMP request message to Simple Extensible Protocol SXP request message;
Described UA sends to described equipment with described SXP request message;
Described UA obtains the SXP response message that described equipment returns;
The described SXP response message that described UA will receive converts SNMP response message to, and sends to described NMS.
The embodiment of the invention also provides a kind of proxy for equipment system, comprising:
Simple Network Management Protocol snmp message processing module is used to receive and resolve the Simple Network Management Protocol SNMP request message that network management system NMS sends, and determines described SNMP request message corresponding equipment; And be used for the SNMP response message that protocol conversion module generates is sent to network management system;
Protocol conversion module is used for converting the SNMP request message that described snmp message processing module provides to Simple Extensible Protocol SXP request message; The SXP response message that also is used for interface module is returned converts SNMP response message to;
Interface module is used for the SXP request message that described protocol conversion module generates is sent to described equipment, and the SXP response message that described equipment returns is sent to described protocol conversion module.
In the scheme that the embodiment of the invention provides, UA changes the snmp message that the network management system side provides by internal agreement, be converted to SXP message, with respect to existing AgentX agreement implementation, unified agent to device mask the snmp message details, make that the exploitation of equipment is more simple, and UA can act on behalf of polytype equipment, improve the compatibility of unified agent.
Description of drawings
The network agent structural representation that Fig. 1 provides for prior art two;
The method flow diagram of a certain facility registration that Fig. 2 provides for the embodiment of the invention to the NMS;
Fig. 3 for the embodiment of the invention 1 provide a kind of from registered device management method flow chart getparms;
A kind of management method flow chart that the parameter of registered device is set that Fig. 4 provides for the embodiment of the invention 2;
One of a kind of proxy for equipment system configuration schematic diagram that Fig. 5 provides for the embodiment of the invention;
Two of a kind of proxy for equipment system configuration schematic diagram that Fig. 6 provides for the embodiment of the invention.
Embodiment
The embodiment of the invention provides a kind of proxy for equipment method of supporting Simple Network Management Protocol SNMP, in this method, as unified agent (Uniform Agent, UA) during treatment S NMP request message, be translated into Simple Extensible Protocol (Simple eXtended Protocol, SXP) request message sends to equipment, makes equipment need not to be concerned about the details of SNMP request message.Wherein, unified agent is similar to the master agent in the prior art two, is used to accept the network management of network management system, and is used to manage at least one equipment.
Below in conjunction with accompanying drawing, specify the embodiment of the invention.
When initial, can get access to the mib information of coupled all devices among the UA, equipment can be registered on the network management system NMS by UA then, to participate in the network management process.Figure 2 shows that the method flow diagram of a certain facility registration to the NMS, specifically may further comprise the steps:
The SXP registration message of S21:UA receiving equipment.
Wherein, equipment sends registration message by registration interface to UA.
S22:UA searches and stores the mib information of this equipment.
Wherein, the UA mib information that this equipment and other equipment is public is loaded into storage in the public MIB table of equipment; In addition, UA sets a specific identifier and storage for the specific mib file of this equipment.During storage the specific mib file of this equipment is described with extend markup language (XML), and be the different specific identifier of specific mib file setting of distinct device, for example: the specific mib file of certain equipment can be loaded among the UA one is in the mib file of sign with " Context ", certain equipment that promptly is called " Name " for name, the sign of the specific mib file of this equipment correspondence of UA end storage can be " ContextName ".
S23:UA is converted to the SNMP registration message with this SXP registration message and sends to its affiliated NMS.
Below describe the method that the equipment that is registered on the NMS is managed in detail with specific embodiment.
Embodiment 1
It is a kind of from registered device management method flow chart getparms to Figure 3 shows that present embodiment 1 provides, and specifically may further comprise the steps:
S31:UA receives and resolves SNMP that NMS the sends request message that gets parms.
Wherein, SNMP gets parms and has comprised the specific identifier of NMS appointment in the request message (SNMP Get request message), and this specific identifier is corresponding to the specific mib file of certain equipment of storing among the UA.
S32:UA determines this SNMP request message corresponding equipment that gets parms.
In this step, UA matches specific identifier and obtains/be provided with the consistent mib file of specific identifier that comprises in the parameter request message with described SNMP in several specific mib files of having stored, and with the mib file corresponding equipment that matches as described equipment.
S33:UA converts the SNMP request message that gets parms to the SXP request message that gets parms.
In this step, pre-defined snmp message and SXP message mapping relation wherein, can be a SXP-Get message with SNMP Get request message conversion in UA, and this message is used for asking the equipment from determining to extract one or more parameter values.For example, SXP-Get message is: ContextName, SquenceID, [ObjIdentifys].
Wherein, carried the device parameter type identification of acquisition request in the SNMP Get request message in the SXP-Get message.
S34:UA is by calling the interface that gets parms, and the SXP request message that gets parms is sent to the equipment of determining.
Wherein, SXP-Get message is corresponding to the interface that gets parms, for example: if get parms interface " OnGet " by name, the parameter of OnGet interface is: ContextName, SquenceID, [ObjIdentify, ObjValue, ErrCode], UA is by calling one or more parameters that the OnGet interface obtains equipment.
S35: equipment is by calling the response interface that gets parms, and returns the SXP response message that gets parms to UA.
Be similar to SNMP response message, if the SXP request message that sends among the step S34 is a SXP-Get message, then equipment returns SXP-Get Response message by the response interface that gets parms to UA.
Wherein, the response interface that gets parms is corresponding to the interface that gets parms of equipment, and behind the interface that gets parms of UA invocation facility, equipment is by calling the response interface that gets parms, and the data snapshot of all data of equipment self is sent to UA.For example: the response interface that gets parms can be " ReplyGet ", and the parameter of ReplyGet is: ContextName, SquenceID, [ObjIdentifys, ObjValues, ErrCode].
The get parms data snapshot of the equipment that carries in the response message of S36:UA storage SXP.
S37:UA converts the SXP that the receives response message that gets parms to the SNMP response message that gets parms, and returns to network management system after the assembling.
In this step, the device parameter type identification corresponding parameters of acquisition request in the SNMP Getrequest message when extracting beginning in the data snapshot of the equipment that UA stores from S36, and according to predefined snmp message and SXP message mapping relation, the SXP-Get Response message returned (SXP get parms response message) is converted to SNMP Get response message, has carried one or more parameter values that UA extracts in this response message from data snapshot.For example, this message content is: ContextName, SquenceID, [ObjIdentifys, ObjValues, ErrCode].In addition, the message that the SNMP Getresponse message that generates is assembled into the SNMP prescribed form sends to NMS.
In the method shown in Figure 3, because equipment has sent to UA with the data snapshot of all data of self among the step S35, therefore, receive the SNMP GetNext request message of NMS transmission as UA after, need not is that SXP-GetNext message more need not by calling the corresponding interface to obtain the parameter of equipment once more with this message conversion, and obtain the data of the equipment that need obtain in the data snapshot that only needs in step S36, to preserve, then the data that get access to are generated SNMP GetNextResponse message and return to NMS and get final product.As seen, the method has significantly reduced the mutual of UA and equipment, and with respect to prior art, equipment control efficient is higher.
Embodiment 2
Figure 4 shows that a kind of management method flow chart that the parameter of registered device is set that the embodiment of the invention provides, specifically may further comprise the steps:
The SNMP that S41:UA received and resolved the NMS transmission is provided with parameter request message.
S42:UA determines that this SNMP is provided with parameter request message corresponding equipment.
S43:UA is provided with the parameter request message conversion with SNMP and becomes SXP that parameter request message is set.
Being similar to embodiment 1, in this step, according to predefined snmp message and SXP message mapping relation, is SXP-Set message with SNMP Set request message conversion among the UA, and this message is used to ask one or more parameter values of the equipment that is provided with.For example, SXP-Set message is: ContextName, SquenceID, [OperationType, ObjIdentifys, ObjValues].
Wherein, carried the device parameter value that request is provided with in the SNMP Set request message in the SXP-Set message.
S44:UA is provided with the parameter interface by calling, and SXP is provided with parameter request message sends to the equipment of determining.
Wherein, SXP-Set message is corresponding to the parameter interface is set, for example: if parameter interface " OnGet " by name is set, and the OnSet interface parameters is: ContextName, SquenceID, [OperationType, ObjIdentifys, ObjValues], then UA is provided with one or more parameters of this equipment by calling the OnSet interface.
S45: equipment is provided with the parameter response interface by calling, and returns SXP to UA parameter response message is set.
Be similar to embodiment 1, if the SXP request message that sends among the step S44 is a SXP-Set message, then equipment returns SXP-Set Response message by the parameter response interface is set to UA.
Wherein, be provided with the parameter response interface corresponding to equipment the parameter interface is set, when the UA invocation facility the parameter interface is set after, equipment is provided with designated parameters, and by calling the parameter response interface is set, and the execution result of this operation is sent to UA.For example: the parameter response interface is set can be that " " ReplySet ", the parameter of ReplySet is: ContextName, SquenceID, [OperationType, ObjIdentifys, ObjValues, ErrCode].
S46:UA is provided with the parameter response message conversion with the SXP that receives and becomes SNMP that parameter response message is set, and returns to network management system after the assembling.
In this step, UA is according to predefined snmp message and SXP message mapping relation, the SXP-Set Response message of returning (SXP is provided with parameter response message) is converted to SNMP Setresponse message, for example, this message content is: ContextName, SquenceID, [OperationType, ObjIdentifys, ObjValues, ErrCode].
Similarly, the said method that provides according to the embodiment of the invention, the transport process of the Trap message that is initiatively reported to UA by equipment is as follows:
1, equipment initiatively reports interface to send SXP-Trap message to UA by calling.
For example, equipment reports some information by calling " Alarm " interface to SDK, and this Alarm interface parameters is: ContextName, [Trap Contents].
2, UA becomes SNMP-Trap message with the SXP-Trap message conversion, and returns to NMS after the assembling.
In the said method that the embodiment of the invention provides, the snmp message that UA will send to equipment is converted to SXP message, and by interface interchange, to device mask the details of snmp message, thereby reduced the difficulty that equipment is accepted management; UA is improved to compatibility of apparatus simultaneously, can act on behalf of a large amount of different types of equipment, has reduced the overlapping development of a plurality of equipment in device management process; In addition, because UA has stored equipment in the process of treatment S NMP Get request message data snapshot, therefore, receive the SNMP GetNext request message of NMS transmission as UA after, can be directly from the data snapshot of the equipment of self storage, obtain the parameter that to obtain and return to NMS, reduce the mutual of UA and equipment side, significantly improved the efficient of equipment control.
Corresponding to the device management method that the embodiment of the invention provides, the embodiment of the invention also provides a kind of proxy for equipment system, and as shown in Figure 5, this system comprises: snmp message processing module 51, protocol conversion module 52 and interface module 53.Wherein, each functions of modules is as follows:
Snmp message processing module 51 is used to receive and resolve the Simple Network Management Protocol SNMP request message that NMS sends, and determines described SNMP request message corresponding equipment; In addition, this module also is used for the SNMP response message that protocol conversion module 52 generates is sent to NMS.
As shown in Figure 6, the said equipment agency plant also can comprise: stores processor module 61 and mib information load-on module 62; Wherein:
Mib information load-on module 62, the public mib information of the mib information that also is used for the equipment that will receive and other equipment is loaded into storage in the public MIB table of the equipment that sets in advance, and stores after the specific mib file of equipment set a specific identifier.
Snmp message processing module 51, send to NMS after the SNMP registration message assembling that also is used for to receive, in addition, also be used in several specific mib files of mib information load-on module 62 storage, matching the consistent mib file of specific identifier that comprises in specific identifier and the SNMP request message, and with the mib file corresponding equipment that matches as this SNMP request message corresponding equipment.
In addition, when the snmp message that sends to proxy for equipment system shown in Figure 6 as NMS was SNMP Getrequest message, interface module 53 sent to stores processor module 61 with the SXP-GetResponse message of the data snapshot of carrying this equipment that equipment returns.
When snmp message processing module 51 receives and parses the SNMP GetNextrequest request message of NMS transmission, determine SNMP GetNext request request message corresponding equipment, and notification protocol modular converter 52 obtains the parameter of SNMP GetNext request request message corresponding equipment.
Snmp message processing module 51 also is used for and will sends to NMS after the assembling of SNMP GetNextResponse message.
In the proxy for equipment system that the front provided, interface module 53 can be arranged on the equipment.
The said equipment agency plant that the embodiment of the invention provides also can make that the exploitation of equipment is more simple to device mask snmp message details, and polytype equipment can be acted on behalf of by described proxy for equipment system.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (11)
1. a device management method is characterized in that, comprising:
Unified agent UA receives and resolves the Simple Network Management Protocol SNMP request message that network management system NMS sends;
Described UA determines described SNMP request message corresponding equipment;
Described UA converts described SNMP request message to Simple Extensible Protocol SXP request message;
Described UA sends to described equipment with described SXP request message;
Described UA obtains the SXP response message that described equipment returns;
The described SXP response message that described UA will receive converts SNMP response message to, and sends to described NMS.
2. the method for claim 1 is characterized in that, described UA sends to described equipment with described SXP request message, specifically comprises: described UA sends to described equipment by calling the interface corresponding to described SXP request message with described SXP request message.
3. method as claimed in claim 1 or 2 is characterized in that, before described unified agent UA receives and resolves the Simple Network Management Protocol snmp message of network management system NMS transmission, also can comprise:
The SXP registration message of described UA receiving equipment;
Described UA searches and stores the management information bank mib information of described equipment;
Described UA is converted to the SNMP registration message with described SXP registration message and sends to NMS under it.
4. method as claimed in claim 3, it is characterized in that, the SNMP request message that receives and parse as described UA is that SNMP is when getting parms request message, described UA obtains the SXP response message that described equipment returns, specifically comprise: described UA is by the response interface that gets parms of described equipment calls, the SXP that obtains the data snapshot of the carrying described equipment response message that gets parms;
The described SXP response message that described UA will receive converts SNMP response message to, specifically comprises: the described SXP that described UA will the receive response message that gets parms converts the SNMP response message that gets parms to;
Described UA obtains SXP that described equipment returns and gets parms after the response message, the described SXP that described UA will the receive response message that gets parms converts SNMP to and gets parms before the response message, also comprises: described UA stores the get parms data snapshot of the equipment that carries in the response message of described SXP.
5. method as claimed in claim 4 is characterized in that, described SNMP is got parms after response message sends to described NMS at described UA, also can comprise:
The SNMP that described UA received and resolved described NMS transmission obtains next parameter request message;
Described UA determines that described SNMP obtains next parameter request message corresponding equipment;
Described UA obtains the parameter that described SNMP obtains acquisition request in the next parameter request message from the data snapshot of the described equipment of storage;
Described UA is generated as SNMP with the parameter of obtaining and obtains next parameter response message, and sends to described NMS.
6. method as claimed in claim 3, it is characterized in that, described UA searches and store the management information bank mib information of described unregistered equipment, specifically comprises: the public mib information of the described unregistered equipment that described UA will find and other equipment is loaded into storage in the public MIB table of the equipment that sets in advance; The specific mib file of the described unregistered equipment that described UA will find is set a specific identifier and storage.
7. method as claimed in claim 6 is characterized in that, comprises described specific identifier in the described SNMP request message;
Described UA determines SNMP request message corresponding equipment, specifically comprise: described UA matches the consistent mib file of specific identifier that comprises in specific identifier and the described SNMP request message in the specific mib file of having stored, and with the mib file corresponding equipment that matches as described equipment.
8. a proxy for equipment system is characterized in that, comprising:
Simple Network Management Protocol snmp message processing module is used to receive and resolve the Simple Network Management Protocol SNMP request message that network management system NMS sends, and determines described SNMP request message corresponding equipment; And be used for the SNMP response message that protocol conversion module generates is sent to network management system;
Protocol conversion module is used for converting the SNMP request message that described snmp message processing module provides to Simple Extensible Protocol SXP request message; The SXP response message that also is used for interface module is returned converts SNMP response message to;
Interface module is used for the SXP request message that described protocol conversion module generates is sent to described equipment, and the SXP response message that described equipment returns is sent to described protocol conversion module.
9. proxy for equipment as claimed in claim 8 system is characterized in that, also comprises: stores processor module and mib information load-on module; Wherein:
Described interface module also is used for providing registration interface to equipment, makes described equipment by calling described registration interface, sends the SXP registration message to the stores processor module;
Described stores processor module is used for storing in advance the mib information of all devices, and according to the SXP registration message of receiving, finds the mib information of described equipment and send to described mib information load-on module;
Described mib information load-on module, the public mib information of the mib information that is used for the described equipment that will receive and other equipment is loaded into storage in the public MIB table of the equipment that sets in advance, and stores after the specific mib file of described equipment set a specific identifier;
Described protocol conversion module also is used for the described SXP registration message that described interface module provides is converted to the SNMP registration message and sends to described snmp message processing module;
Described snmp message processing module also is used for described SNMP registration message is sent to network management system; And be used in the specific mib file that described mib information load-on module is stored, matching the consistent mib file of specific identifier that comprises in specific identifier and the described SNMP request message, and with the mib file corresponding equipment that matches as described SNMP request message corresponding equipment.
10. proxy for equipment as claimed in claim 9 system is characterized in that, the SXP that carries its data snapshot that described interface module is also the returned described equipment response message that gets parms sends to described stores processor module;
Described stores processor module also is used for storing the get parms data snapshot of the equipment that response message carries of described SXP;
The described SNMP request message that receives and parse when described snmp message processing module is SNMP when obtaining next parameter request message, and described snmp message processing module also is used to notify described protocol conversion module to obtain the parameter that described SNMP obtains next parameter request message corresponding equipment;
Described protocol conversion module, also be used for notice according to described snmp message processing module, obtain described SNMP in the data snapshot of the described equipment of from described stores processor module, storing and obtain the parameter that next parameter request message request is obtained, and generation SNMP obtains next parameter response message;
Described snmp message processing module is used for that also described SNMP is obtained next parameter response message and sends to network management system.
11., it is characterized in that described interface module is arranged on the described equipment as the arbitrary described proxy for equipment of claim 8 to 10 system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2007101947704A CN101170451A (en) | 2007-12-03 | 2007-12-03 | A device management method and a device proxy system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2007101947704A CN101170451A (en) | 2007-12-03 | 2007-12-03 | A device management method and a device proxy system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101170451A true CN101170451A (en) | 2008-04-30 |
Family
ID=39390930
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2007101947704A Pending CN101170451A (en) | 2007-12-03 | 2007-12-03 | A device management method and a device proxy system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101170451A (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011015094A1 (en) * | 2009-08-04 | 2011-02-10 | 中兴通讯股份有限公司 | Peer to peer network management system and method for realizing management thereof |
| CN102036245A (en) * | 2010-12-03 | 2011-04-27 | 大唐移动通信设备有限公司 | Network element management method and equipment |
| WO2012129848A1 (en) * | 2011-04-01 | 2012-10-04 | 中兴通讯股份有限公司 | Method and apparatus for simulating universal serial bus device |
| CN101729530B (en) * | 2009-10-30 | 2013-03-20 | 中兴通讯股份有限公司 | Data synchronization method and data synchronization system |
| CN103812690A (en) * | 2013-08-06 | 2014-05-21 | 国家电网公司 | Fault diagnosis information transferring and processing method for normalization management interface of device |
| CN103840953A (en) * | 2012-11-21 | 2014-06-04 | 中兴通讯股份有限公司 | Remote log real-time acquisition method and system |
| CN104022893A (en) * | 2014-04-22 | 2014-09-03 | 烽火通信科技股份有限公司 | Configuration managing method for SNMP redirection with multiple subagents |
| CN109905292A (en) * | 2019-03-12 | 2019-06-18 | 北京奇虎科技有限公司 | A kind of terminal device recognition methods, system and storage medium |
| CN109951354A (en) * | 2019-03-12 | 2019-06-28 | 北京奇虎科技有限公司 | A kind of terminal device recognition methods, system and storage medium |
| CN110808847A (en) * | 2019-09-23 | 2020-02-18 | 三维通信股份有限公司 | Method and device for managing DAS (data-based system), electronic device and storage medium |
| CN112383408A (en) * | 2020-09-29 | 2021-02-19 | 武汉虹信科技发展有限责任公司 | Management platform end for data format conversion and data format conversion method |
-
2007
- 2007-12-03 CN CNA2007101947704A patent/CN101170451A/en active Pending
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011015094A1 (en) * | 2009-08-04 | 2011-02-10 | 中兴通讯股份有限公司 | Peer to peer network management system and method for realizing management thereof |
| CN101729530B (en) * | 2009-10-30 | 2013-03-20 | 中兴通讯股份有限公司 | Data synchronization method and data synchronization system |
| CN102036245A (en) * | 2010-12-03 | 2011-04-27 | 大唐移动通信设备有限公司 | Network element management method and equipment |
| CN102737003B (en) * | 2011-04-01 | 2015-09-16 | 中兴通讯股份有限公司 | A kind of method and device of simulating USB device |
| CN102737003A (en) * | 2011-04-01 | 2012-10-17 | 中兴通讯股份有限公司 | Method and device for simulating USB (Universal Serial Bus) device |
| WO2012129848A1 (en) * | 2011-04-01 | 2012-10-04 | 中兴通讯股份有限公司 | Method and apparatus for simulating universal serial bus device |
| CN103840953A (en) * | 2012-11-21 | 2014-06-04 | 中兴通讯股份有限公司 | Remote log real-time acquisition method and system |
| US9942111B2 (en) | 2012-11-21 | 2018-04-10 | Zte Corporation | Method for remotely acquiring in real time log |
| CN103812690A (en) * | 2013-08-06 | 2014-05-21 | 国家电网公司 | Fault diagnosis information transferring and processing method for normalization management interface of device |
| CN103812690B (en) * | 2013-08-06 | 2017-02-22 | 国家电网公司 | Fault diagnosis information transferring and processing method for normalization management interface of device |
| CN104022893B (en) * | 2014-04-22 | 2017-08-01 | 烽火通信科技股份有限公司 | The configuring management method that a kind of many sub-agent SNMP are redirected |
| CN104022893A (en) * | 2014-04-22 | 2014-09-03 | 烽火通信科技股份有限公司 | Configuration managing method for SNMP redirection with multiple subagents |
| CN109905292A (en) * | 2019-03-12 | 2019-06-18 | 北京奇虎科技有限公司 | A kind of terminal device recognition methods, system and storage medium |
| CN109951354A (en) * | 2019-03-12 | 2019-06-28 | 北京奇虎科技有限公司 | A kind of terminal device recognition methods, system and storage medium |
| CN110808847A (en) * | 2019-09-23 | 2020-02-18 | 三维通信股份有限公司 | Method and device for managing DAS (data-based system), electronic device and storage medium |
| CN110808847B (en) * | 2019-09-23 | 2021-10-15 | 三维通信股份有限公司 | Method and device for managing DAS (data-based system), electronic device and storage medium |
| CN112383408A (en) * | 2020-09-29 | 2021-02-19 | 武汉虹信科技发展有限责任公司 | Management platform end for data format conversion and data format conversion method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101170451A (en) | A device management method and a device proxy system | |
| EP2914022B1 (en) | Device management method, middleware, and machine-to-machine communications platform, device, and system | |
| CN102185716B (en) | Universal management method and system for communication equipment | |
| CN101009591A (en) | Method and system for configuring network devices through an operations support system interface | |
| CN102014403A (en) | Method and system for transmitting network topology information | |
| CN100539597C (en) | Configuring management method and device | |
| CN101795206B (en) | Method and device for realizing SNMP agent on distributed equipment | |
| US9009306B2 (en) | Method, system, client and server for locating operation nodes in communication system | |
| CN100477839C (en) | Method and system for updating producer-specific hardware information on the producer-independent OMC-NMC interface in a mobile radio network | |
| US8387068B2 (en) | Method and device for managing object instance label | |
| CN101345657B (en) | Method and system for cluster management of multiple network elements based on simple network management protocol | |
| CN101247272B (en) | Network management method and apparatus | |
| CN102684894B (en) | Method and device for realizing northboundbound interface | |
| US20110145294A1 (en) | Device description framework information reporting and updating method, device and system | |
| CN103684822A (en) | Method and equipment for managing network equipment | |
| CN101848110A (en) | TR069 network management method and equipment | |
| CN113992504A (en) | Network transmission equipment management method based on industrial internet identification analysis | |
| CN106254122B (en) | Simple network management protocol agent implementation method based on EOC equipment | |
| CN102904739A (en) | Method for realizing event transmission and common information model (CIM) server | |
| CN113824587B (en) | Multi-communication protocol equipment management method and system | |
| EP2573978B1 (en) | Method, apparatus and system for device management | |
| CN100452721C (en) | Customer end management system and method | |
| McCarthy et al. | Exploiting the power of OSI Management for the control of SNMP-capable resources using generic application level gateways | |
| US20040215760A1 (en) | Device for the control of heterogeneous equipment in a telecommunication network | |
| KR20090046054A (en) | Apparatus and method for transferring protocol |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20080430 |