CN101778106A - Method and middleware for realizing conversion between CORBA and SNMP - Google Patents
Method and middleware for realizing conversion between CORBA and SNMP Download PDFInfo
- Publication number
- CN101778106A CN101778106A CN201010001227A CN201010001227A CN101778106A CN 101778106 A CN101778106 A CN 101778106A CN 201010001227 A CN201010001227 A CN 201010001227A CN 201010001227 A CN201010001227 A CN 201010001227A CN 101778106 A CN101778106 A CN 101778106A
- Authority
- CN
- China
- Prior art keywords
- snmp
- corba
- territory
- message
- conversion
- 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
Abstract
The invention discloses a method and a middleware for realizing the conversion between CORBA and SNMP, wherein the method mainly comprises the following steps: calling agent objects to be managed of each webmaster in a built CORBA domain; building grammar mapping between SNMP and CORBA by the agent objects to be managed; and building mapping between SNMP information and CORBA information in each network element in an SNMP domain by the agent objects to be managed. In addition, the invention further discloses a middleware for realizing the conversion between CORBA and SNMP. By adopting the invention, the network management of the EMS system management function and the interface standard of each network element with difference can be realized by a universal CORBA protocol, and thereby EMS of each manufacturer can be brought into a same management platform, and the integrated and unified maintenance and management of a computer network can be realized.
Description
Technical field
The present invention relates to field of wireless communication, relate in particular to the method and the middleware of a kind of CORBA of realization and SNMP conversion.
Background technology
At present, numerous producers are network element at the network equipment that production is used for building network all, the different network elements that different manufacturers is produced is respectively by self Element management system (EMS, Element Management System) controls and manage, realize NE management layer, then finish by the network management system on the EMS at the NML of local all network elements at each network element.Wherein, EMS provides " network view " of connection management, network management system to serve as gerentocratic role for network management system and sends or obtain the information of forwarding from EMS to each network element from each network element.
Simple Network Management Protocol (SNMP, Simple Network Management Protocol) is the NMP that is most widely used in the present computer network.Because manufacturer's difference, at each EMS of each network element on the Internet and each interface between each network element, when exploitation SNMP used, often the kit that need realize at the various different languages that each heterogeneous networks platform is adopted was done the work of treatment of repetition.
Common Object Request Broker Architecture (CORBA, Common Object Request BrokerArchitecture) be (OMG of OMG, Object Management Group) for solving distributed processing environment (DCE, Distributed Computing Environment) in, the interconnection of hardware and software system and a solution of proposing, it has very big advantage in the interoperability that solves between the distributed heterogeneous environment system, versatility with " software bus " has satisfied the needs of distributed heterogeneous network management.
Therefore, need will change between CORBA and the SNMP, could realize concentrated, unified network management computer network.
Summary of the invention
In view of this, main purpose of the present invention is to provide the method and the middleware of a kind of CORBA of realization and SNMP conversion, the EMS of different vendor can be included in same management platform, realizes the maintenance and management that computer network is concentrated, unified.
For achieving the above object, technical scheme of the present invention is achieved in that
The invention provides the method for a kind of CORBA of realization and SNMP conversion, described method comprises: the managed object of acting on behalf of of calling each webmaster in the CORBA territory of having created; Set up grammer mapping between SNMP and the CORBA by the described managed object of acting on behalf of; Set up the snmp message of each network element in the SNMP territory and the mapping between the CORBA message by the described managed object of acting on behalf of.
In such scheme, the described managed object of acting on behalf of of calling each webmaster in the CORBA territory of having created specifically comprises: create in acting on behalf of the managed object territory and act on behalf of managed object; Call the managed object of being created of acting on behalf of.
In such scheme, described grammer mapping of setting up between SNMP and the CORBA is specially: with the IDL among the CORBA according to setting up mapping relations between the management information bank among common object service regulation and the SNMP.
In such scheme, describedly set up the snmp message of each network element in the SNMP territory and the mapping between the CORBA message, specifically comprise: with the title among the SNMP, message transmit, incident transmits name service, operation calls and the Event Service that is mapped as the CORBA agreement.
The present invention also provides a kind of network management, and described method comprises: realize the conversion between CORBA and the SNMP; According to the conversion that is realized, the request that webmaster in the CORBA territory that receives is sent is converted to calling the SNMP interface; According to snmp protocol, calling of SNMP interface sent to the network element in the SNMP territory and receive the message that the SNMP territory is returned described; According to the conversion that is realized, the message conversion that described SNMP territory is returned becomes CORBA incident and the incident port in the CORBA territory to report.
The present invention also provides a kind of CORBA of realization and SNMP the middleware of conversion, and described middleware comprises call unit, grammer map unit and message maps unit, and wherein: call unit is used for calling the managed object of acting on behalf of of each webmaster of CORBA territory of having created; The grammer map unit, the managed object of acting on behalf of that is used for being called by described call unit is set up grammer mapping between SNMP and the CORBA; The message maps unit, the managed object of acting on behalf of that is used for being called by described call unit is set up the snmp message of each network element of SNMP territory and the mapping between the CORBA message.
In such scheme, described middleware also comprises: creating unit is used for creating and acting on behalf of managed object acting on behalf of the managed object territory.
In such scheme, described grammer map unit specifically is used for: with the IDL of CORBA according to setting up mapping relations between the management information bank among common object service regulation and the SNMP.
In such scheme, described message maps unit specifically is used for: with name service, operation calls and the Event Service that title, the message of SNMP transmit, the incident transmission is mapped as the CORBA agreement.
The present invention also provides a kind of network management system, and described system comprises: middleware, CORBA processing unit, SNMP processing unit, and wherein: middleware is used to realize the conversion between CORBA and the SNMP; The CORBA processing unit is used for the conversion according to described middleware realization, and the request that webmaster in the CORBA territory that receives is sent is converted to calling the SNMP interface; And, being used for the protocol conversion that realizes according to described middleware, the message conversion that the SNMP territory that described SNMP processing unit is received is returned becomes CORBA incident and the incident port in the CORBA territory to report; The SNMP processing unit is used for described calling of SNMP interface being sent to the network element in SNMP territory and receiving the message that the SNMP territory is returned.
By the method and the middleware of CORBA provided by the present invention and SNMP conversion, the SNMP that is used to manage each network element can be converted to inter-network element, cross-platform CORBA, manage each Network Management Equipment by CORBA again.Like this, can be with the EMS management function and the interface standard of each network element that there are differences, realize its network management by general CORBA agreement, thereby the EMS of each manufacturer can be included in same management picture mosaic, realize the maintenance and management that computer network is concentrated, unified.
In addition, with CORBA and SNMP conversion, adopt CORBA that each network element in the network management system is managed, help reducing the repeat work of each network element when its SNMP of exploitation uses by the present invention.In addition, because the versatility of CORBA agreement, each network management platform can use, and call method is roughly the same, helps reducing the workload of protocol development in the network management.
Description of drawings
Fig. 1 realizes the schematic flow sheet of CORBA and SNMP conversion method for the present invention;
Fig. 2 is for creating the realization flow schematic diagram of acting on behalf of managed object;
Fig. 3 calls the realization flow schematic diagram of being created of acting on behalf of managed object;
Fig. 4 is the realization flow schematic diagram of a kind of network management of the present invention;
Fig. 5 is the composition structural representation of the middleware of realization CORBA of the present invention and SNMP conversion;
Fig. 6 is the composition structural representation of a kind of network management system of the present invention.
Embodiment
Below in conjunction with accompanying drawing technical scheme of the present invention is elaborated.
A kind of method that realizes CORBA and SNMP conversion of the present invention with reference to shown in Figure 1, mainly may further comprise the steps:
Step 101: the managed object of acting on behalf of of calling each webmaster in the CORBA territory of having created;
Step 102: set up grammer mapping between SNMP and the CORBA by the described managed object of acting on behalf of;
Step 103: set up the snmp message of each network element in the SNMP territory and the mapping between the CORBA message by the described managed object of acting on behalf of.
Particularly, call the managed object of acting on behalf of of each webmaster in the CORBA territory of having created in the step 101, specifically can comprise:
In acting on behalf of the managed object territory, create and act on behalf of managed object; Call the managed object of being created of acting on behalf of.
Here, in acting on behalf of the managed object territory, create and act on behalf of managed object,, specifically can realize by following flow process with reference to shown in Figure 2:
Step 201: at webmaster with after acting on behalf of the managed object territory and setting up session, generate the object reference of the agent object (ProxyAgent) in the CORBA agreement, obtain to acting on behalf of the access rights in managed object territory;
Step 202: according to the object reference of generation ProxyAgent, call the get_domaines_factory_finder method of ProxyAgent, obtain acting on behalf of the object reference of the initial FactoryFinder in managed object territory;
Step 203: according to the object reference of resultant FactoryFinder, call the CosLifeCycle::FactoryFinder of ProxyAgent, key value by the sign proxy object factory set (mo_factories) that webmaster sent is searched the mo_factories of coupling, if do not find, then change step 204 over to; Otherwise, directly change step 205 over to;
Step 204: by FactoryFinder create one with the corresponding mo_factories of described key value;
Step 205: the CosLifeCycle::GenericFactory::_narrow that calls ProxyAgent, according to the CORBA protocol interface that webmaster sent, in the mo_factories that is found or created, find the needed my_factory of managed object factory that acts on behalf of.
Step 206: call the create_obj method of ProxyAgent, in my_factory, create the object reference of acting on behalf of managed object;
Step 207: return the object reference of acting on behalf of managed object and give webmaster in the CORBA territory, make webmaster to call this and to act on behalf of managed object according to this object reference of acting on behalf of managed object.
Here, call the managed object of being created of acting on behalf of,, specifically can realize by following flow process with reference to shown in Figure 3:
Step 301: by the ProxyAgentFinder in the CORBA agreement, find the object reference of ProxyAgent, to obtain to acting on behalf of the access rights in managed object territory;
Step 302: according to the object reference of resulting ProxyAgent, call the get_domain_naming_context of ProxyAgent, obtain the NamingContext object reference of ProxyAgent;
Step 303: according to resulting NamingContext object reference, call the resolve method of NamingContext, search the object reference of acting on behalf of managed object, if find, forward step 305 to, otherwise forward step 304 to;
Step 304: if do not find the described object reference of acting on behalf of managed object, then generate new ProxyAgent, and call get_domaines_factory_finder, CosLifeCycle::FactoryFinder, CosLifeCycle::GenericFactory::_narrow, create_obj, create and act on behalf of managed object;
Step 305: return the object reference of acting on behalf of managed object and give webmaster in the CORBA territory, make webmaster in the CORBA territory by the described object reference of acting on behalf of managed object, call the described method of acting on behalf of managed object, for example call by acting on behalf of managed object and finish the method etc. of each network element data configuration.
Particularly, set up the grammer mapping between SNMP and the CORBA agreement in the step 102, be specially:
With the IDL (IDL among the CORBA, Interface Definition Language) according to common object service regulation (COSS, Common Object Services Specifications) and between the management information bank (MIB, Management Information Base) among the SNMP set up mapping relations.
In actual applications, setting up the grammer mapping relations between CORBA and the SNMP, mainly is that the form of the mib information among the SNMP with IDL among the CORBA realized that algorithm is as follows:
Be included in interface, type and constant among the MIB what SNMP produced, all in CORBA, do corresponding description with the IDL form.
Particularly, the type of the import among the MIB (inlet) is defined as the typeof among the IDL in the CORBA agreement;
If among at least one group among the MIB form variable is arranged, then in the CORBA agreement, state the SmiEntryFactory interface with the IDL language;
If have at least a NOTIFICATION-TYPE grand among the MIB, in the IDL of CORBA, state two interfaces so, one is Notifications, another is PullNotifications, is respectively applied in Push and the Pull event communication;
If have at least an OBJECT-TYPE who comprises DEF-VAL clause grand among the MIB, pseudo-IDL interface of statement in IDL, DefaultValues by name;
If have at least a TEXTUAL-CONVENTION who comprises DISPLAY-HINT clause grand among the MIB, pseudo-IDL interface of statement in IDL, TextualConventions by name;
The grand SYNTAX clause's of TEXTUAL-CONVENTION numerical value statement among the mapping MIB in IDL.
The value of MODULE-IDENTITY macro-call is the character string constant of IDL among the mapping SNMP in IDL.
The value of OBJECT-IDENTITY macro-call is the IDL character string constant among the mapping SNMP in IDL.
Corresponding to each group among the MIB, in IDL, generate a corresponding with it interface;
Among the mapping MIB on the grand constant character string that type is ASN1_ObjectIdentifier in the IDL of NOTIFICATION-TYPE or TRAP-TYPE;
In IDL, produce a file by compiler, by name＜ModuleName .oid, each row is pressed following four arrangement of elements: IDL interface level name, OID (object identifier, Object Identifier), the SMI type of variable, MAX-ACCESS is with the SNMP message structure of corresponding network element;
With CosLifeCycle::LifeCycleObject interface among the IDL and CosPropertyService::PropertySet interface father's interface, make SNMPMgmt::SmiEntry interface among the MIB comprise the denominator of CosLifeCycle::LifeCycleObject interface and CosPropertyService::PropertySet interface among the IDL as SNMPMgmt::SmiEntry interface among the MIB;
With the OB of MIB entry with the grand operation that is mapped as an Iterator among the IDL of CT-TYPE;
INDEX with the OBJECT-TYPE of MIB entry in grand is mapped as the IDL constant.
The relation of grammer mapping can increase and decrease according to the needs of practical application between above-mentioned realization CORBA and the SNMP, and those skilled in the art can be according to the instantiation of above-mentioned algorithm, obtains implementation that algorithm is increased and decreased, does not repeat them here.
Particularly, in the step 103 snmp message of each network element in the SNMP territory is mapped as the message of CORBA, specifically comprises: the title among the SNMP, message transmission, incident are transmitted name service, operation calls and the Event Service that is mapped as in the CORBA agreement.
Wherein, message transmits the message transmission that specifically is meant by acting on behalf of managed object network element in the SNMP territory, and incident transmits by network element in the SNMP territory and transmits to the incident of acting on behalf of managed object.
In actual applications, idiographic flow is as follows:
At first, to CORBA, be exactly with each name map among the SNMP by the level naming method of naming the NamingContext nuclear interface standardizing SNMP of service based on CORBA;
Here, in the CORBA agreement, comprised the IDL interface that MIB entry/group of SNMP is shone upon, therefore, can obtain the object reference of mib object among the SNMP by the name service of CORBA according to the title among the SNMP.In addition, the title among the SNMP can be registered in the name service of CORBA, makes and can come according to SNMP name acquiring object value according to the dictionary preface of similar Get-Next.
Here, particularly, by Hostname, variable name and index name etc. based on each network element among the NamingContext nuclear interface standardizing SNMP of CORBA name server.
Secondly, with each variable name of each network element among the SNMP according to the different mappings of network element on different levels naming tree based on CORBA name service, make variable Instance Name in the SNMP territory be mapped as the attribute variable in the CORBA territory.
Here, the basic structure of the level naming tree that name is served based on CORBA is identical with the tree of mib information among the SNMP, the root node of MIB clauses and subclauses among the SNMP is mapped as the root node of this level naming tree, host name among the MIB, SNMP information module name, group or table clause are mapped as IDL interface name, IDL line index, as the leaf node of the middle-level naming tree of CORBA.
Once more, with the get among the SNMP (obtaining) message, set (setting) message maps in CORBA;
Wherein, promptly by acting on behalf of the behavioural information that managed object is provided with network element attribute in the SNMP territory, the network element of get Message Agent managed object in the SNMP territory obtains the behavioural information of configuration attribute, performance information, alarm information etc. to set message.
Here, the message that set message and get message are contained in above transmits, and carries out the incident that the result of this set message and get message then is contained in above and transmits.
Particularly, according to CosLifeCycle::LifeCycleObject interface and CosPropertyService::PropertySet interface among the above-mentioned defined IDL as father's interface of SNMPMgmt::SmiEntry interface among the MIB, set up in the CORBA territory call relation between get_a_variable (the obtaining variable) method in the interface and SNMP, the corresponding interface in the CORBA territory calls the get function in the SNMP api function, obtain acting on behalf of the mib variable value of managed object, thereby realize that get message is to the mapping in CORBA territory among the SNMP.
Set message maps among the SNMP is become SnmpGateway::define_variable in the CORBA agreement, corresponding to the set_a_variable among the SNMPMgmt::ProxyAgent among the SNMP (variable is set) method.In the set_a_variable of SNMP method realizes, call set function in the SNMPAPI function by the SnmpGateway::define_variable among the CORBA, realize that set message is to the mapping in CORBA territory among the SNMP.
Based on the method for above-mentioned CORBA and SNMP conversion, the present invention also provides a kind of network management, with reference to shown in Figure 4, mainly may further comprise the steps:
Step 401: realize the conversion between CORBA and the SNMP;
Here, the idiographic flow of changing between realization CORBA and the SNMP describes in detail as shown in Figure 1 hereinbefore, does not repeat them here.
Step 402: according to the conversion that is realized, the request that webmaster in the CORBA territory that receives is sent is converted to calling the SNMP interface;
Particularly, according to the conversion that is realized, the request call correspondence of sending according to webmaster in the CORBA territory act on behalf of managed object, act on behalf of managed object by this mapping of CORBA grammer of described request correspondence is obtained corresponding SNMP grammer, obtain message call by acting on behalf of the CORBA message maps of managed object more at last the SNMP interface with the described request correspondence.
Step 403:, calling of SNMP interface sent to the network element in the SNMP territory and receive the message that the SNMP territory is returned with described according to snmp protocol;
Step 404: according to the conversion that is realized, the message conversion that described SNMP territory is returned becomes CORBA incident and the incident port in the CORBA territory to report.
Particularly, according to the conversion that is realized, the message maps that described SNMP territory is returned obtains corresponding CORBA message, and the SNMP grammer mapping by SNMP territory institute return messages correspondence obtains corresponding CORBA grammer, calls the corresponding managed object of acting on behalf of at last and obtain corresponding CORBA incident again.
The middleware of realization CORBA of the present invention and SNMP conversion with reference to shown in Figure 5, mainly comprises call unit 51, grammer map unit 52, message maps unit 53, wherein:
Call unit 51 is used for calling the managed object of acting on behalf of of each webmaster of CORBA territory of having created;
Wherein, described middleware can also comprise: be used for creating the creating unit 54 act on behalf of managed object acting on behalf of the managed object territory.
Particularly, described grammer map unit 52 is used for, with the IDL among the CORBA according to setting up mapping relations between the management information bank among COSS and the SNMP; Described message maps unit 53 is used for, with name service, operation calls and the Event Service that the title among the SNMP, message transmit, the incident transmission is mapped as the CORBA agreement.
Based on above-mentioned middleware, the present invention also provides a kind of network management system, with reference to shown in Figure 6, mainly comprises above-mentioned middleware 61, CORBA processing unit 62, SNMP processing unit 63, wherein:
The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention, all any modifications of being done within the spirit and principles in the present invention, is equal to and replaces and improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. method that realizes CORBA and SNMP conversion is characterized in that described method comprises:
Call the managed object of acting on behalf of of each webmaster in the CORBA territory of having created;
Set up grammer mapping between SNMP and the CORBA by the described managed object of acting on behalf of;
Set up the snmp message of each network element in the SNMP territory and the mapping between the CORBA message by the described managed object of acting on behalf of.
2. realization according to claim 1 CORBA and the method that SNMP changes is characterized in that, the described managed object of acting on behalf of of calling each webmaster in the CORBA territory of having created specifically comprises:
In acting on behalf of the managed object territory, create and act on behalf of managed object;
Call the managed object of being created of acting on behalf of.
3. the method for realization CORBA according to claim 1 and SNMP conversion is characterized in that, described grammer mapping of setting up between SNMP and the CORBA is specially:
With the IDL among the CORBA according to setting up mapping relations between the management information bank among common object service regulation and the SNMP.
4. according to the arbitrary described method that realizes CORBA and SNMP conversion of claim 1 to 3, it is characterized in that, describedly set up the snmp message of each network element in the SNMP territory and the mapping between the CORBA message, specifically comprise: with the title among the SNMP, message transmit, incident transmits name service, operation calls and the Event Service that is mapped as the CORBA agreement.
5. a network management is characterized in that, described method comprises:
Realize the conversion between CORBA and the SNMP;
According to the conversion that is realized, the request that webmaster in the CORBA territory that receives is sent is converted to calling the SNMP interface;
According to snmp protocol, calling of SNMP interface sent to the network element in the SNMP territory and receive the message that the SNMP territory is returned described;
According to the conversion that is realized, the message conversion that described SNMP territory is returned becomes CORBA incident and the incident port in the CORBA territory to report.
6. a middleware of realizing CORBA and SNMP conversion is characterized in that described middleware comprises call unit, grammer map unit and message maps unit, wherein:
Call unit is used for calling the managed object of acting on behalf of of each webmaster of CORBA territory of having created;
The grammer map unit, the managed object of acting on behalf of that is used for being called by described call unit is set up grammer mapping between SNMP and the CORBA;
The message maps unit, the managed object of acting on behalf of that is used for being called by described call unit is set up the snmp message of each network element of SNMP territory and the mapping between the CORBA message.
7. according to the middleware of claim 6 described realization CORBA and SNMP conversion, it is characterized in that described middleware also comprises:
Creating unit is used for creating and acting on behalf of managed object acting on behalf of the managed object territory.
8. according to claim 6 or the 7 described middlewares of realizing CORBA and SNMP conversion, it is characterized in that described grammer map unit specifically is used for: with the IDL of CORBA according to setting up mapping relations between the management information bank among common object service regulation and the SNMP.
9. according to claim 6 or the 7 described middlewares of realizing CORBA and SNMP conversion, it is characterized in that, described message maps unit specifically is used for: with name service, operation calls and the Event Service that title, the message of SNMP transmit, the incident transmission is mapped as the CORBA agreement.
10. a network management system is characterized in that, described system comprises: middleware, CORBA processing unit, SNMP processing unit, wherein:
Middleware is used to realize the conversion between CORBA and the SNMP;
The CORBA processing unit is used for the conversion according to described middleware realization, and the request that webmaster in the CORBA territory that receives is sent is converted to calling the SNMP interface; And, being used for the protocol conversion that realizes according to described middleware, the message conversion that the SNMP territory that described SNMP processing unit is received is returned becomes CORBA incident and the incident port in the CORBA territory to report;
The SNMP processing unit is used for described calling of SNMP interface being sent to the network element in SNMP territory and receiving the message that the SNMP territory is returned.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010001227A CN101778106A (en) | 2010-01-13 | 2010-01-13 | Method and middleware for realizing conversion between CORBA and SNMP |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010001227A CN101778106A (en) | 2010-01-13 | 2010-01-13 | Method and middleware for realizing conversion between CORBA and SNMP |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101778106A true CN101778106A (en) | 2010-07-14 |
Family
ID=42514434
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010001227A Pending CN101778106A (en) | 2010-01-13 | 2010-01-13 | Method and middleware for realizing conversion between CORBA and SNMP |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101778106A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105162616A (en) * | 2015-07-29 | 2015-12-16 | 中国电子科技集团公司第五十四研究所 | Integrated network management method compatible with SNMP and CORBA protocol |
-
2010
- 2010-01-13 CN CN201010001227A patent/CN101778106A/en active Pending
Non-Patent Citations (2)
| Title |
|---|
| 姬风波: "一种基于CORBA/SNMP技术的网络管理模型及其设计与实现", 《中国优秀博硕士学位论文全文数据库（硕士）信息科技辑》 * |
| 李东亮等: "CORBA技术在综合网络管理中的应用", 《中国数据通信》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105162616A (en) * | 2015-07-29 | 2015-12-16 | 中国电子科技集团公司第五十四研究所 | Integrated network management method compatible with SNMP and CORBA protocol |
| CN105162616B (en) * | 2015-07-29 | 2018-02-13 | 中国电子科技集团公司第五十四研究所 | A kind of Integrated Network Management method of compatible snmp protocol and CORBA agreements |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102053860B (en) | CORBA-based OSGi distributed extensible system and method | |
| US6282579B1 (en) | Method for supporting address interaction between a first entity and a second entity, converter for address interaction, and computer system | |
| US7028307B2 (en) | Data management framework for policy management | |
| US7376670B2 (en) | System and method for provisioning presence application services | |
| EP1241828A1 (en) | Gateway system and method providing a common generic interface to network management applications | |
| CN100499498C (en) | A device, system and method for realizing MIB adaptation | |
| US20050278693A1 (en) | Distribution adaptor for network management application development | |
| US7904111B2 (en) | Mobile exchange infrastructure | |
| CN1968134B (en) | Middleware-based multimedia consolidation service realizing method and system | |
| KR102000990B1 (en) | Micro grid energy management system using dds middleware | |
| CN113381870B (en) | Message processing method and device | |
| Leppinen et al. | Java-and CORBA-based network management | |
| Lee | Enabling network management using Java technologies | |
| CN101296232B (en) | Adapting device and method with multi-network management and multi-north interface | |
| Deri | Network Management for the 90s | |
| Deri | Surfin'network resources across the Web | |
| CN101778106A (en) | Method and middleware for realizing conversion between CORBA and SNMP | |
| Bennaceur et al. | Towards an architecture for runtime interoperability | |
| JP2012528367A (en) | Method and associated system for adapting data in a data transmission system | |
| KR20000039702A (en) | Gateway system for interworking management agent of telecommunication management network and integrated service network management system and method for interworking the same | |
| KR100358156B1 (en) | Converting Method of Managing Operation from service management system to Switching Command in a Integrated Network | |
| KR20000028413A (en) | Interlocking system of tmn and corba | |
| Wu et al. | Integrating SNMP agents and CLI with NETCONF-based network management systems | |
| CN115118569B (en) | Request processing method, request processing device, network management equipment and readable storage medium | |
| Hsu et al. | Widget-based framework for web service discovery on multiple home social network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20100714 |