US20060168229A1 - System and method for network management using extensible markup language - Google Patents
System and method for network management using extensible markup language Download PDFInfo
- Publication number
- US20060168229A1 US20060168229A1 US11/023,629 US2362904A US2006168229A1 US 20060168229 A1 US20060168229 A1 US 20060168229A1 US 2362904 A US2362904 A US 2362904A US 2006168229 A1 US2006168229 A1 US 2006168229A1
- Authority
- US
- United States
- Prior art keywords
- xml
- snmp
- network management
- result
- formatted
- 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.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title claims abstract description 63
- 230000009466 transformation Effects 0.000 claims abstract description 23
- 238000012545 processing Methods 0.000 claims description 9
- 230000001131 transforming effect Effects 0.000 claims description 6
- 238000000844 transformation Methods 0.000 abstract description 6
- 230000008569 process Effects 0.000 description 38
- 238000010586 diagram Methods 0.000 description 16
- 238000004891 communication Methods 0.000 description 10
- 230000004044 response Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0226—Mapping or translating multiple network management protocols
Definitions
- the invention relates generally to the field of communications. More specifically, but not by way of limitation, the invention relates to a system and method for management of a Voice Over Internet Protocol (VoIP) or other Internet Protocol (IP) network using eXtensible Markup Language (XML).
- VoIP Voice Over Internet Protocol
- IP Internet Protocol
- XML eXtensible Markup Language
- VoIP Voice over Internet Protocol
- IP Internet Protocol
- FIG. 1 is a block diagram of a functional architecture of a communications network, according to the prior art.
- a network management system 105 is coupled to managed devices 110 , 115 , 120 , and 125 via links 130 , 135 , 140 , and 145 , respectively.
- the managed devices may be routers, switches, call servers, gateways, gatekeepers, handsets, Multipoint Control Units (MCU's), Session Initiation Protocol (SIP) proxy servers, or other devices.
- links 130 , 135 , 140 , and 145 utilize Simple Network Management Protocol (SNMP).
- SNMP Simple Network Management Protocol
- SNMP has many disadvantages, however.
- MIB Management Information Base
- SNMP is limited to five management commands: “get” to request values from the Management Information Base (MIB) of a managed device; “get next” to request the successive values from the MIB; “get response” to retrieve the answer returned; “set” to update MIB values; and “trap” to send an event notification.
- MIB Management Information Base
- SNMP information is presented in long unstructured data strings.
- the limited command set and unwieldy data formats associated with SNMP result in increased cost and cycle time for the development and maintenance of IP network management systems.
- the processing overhead for SNMP-based network management systems may be substantial, making them unsuitable for VoIP and other network communications that must operate in near real-time with low packet losses.
- a more robust management protocol is needed for time-sensitive IP network applications.
- the invention relates to a system and method for management of an IP network using eXtensible Markup Language (XML) or a similar protocol in addition to SNMP or other managed-device protocol.
- XML eXtensible Markup Language
- an XML Network Management Protocol (XNMP) gateway is coupled between the network management system and one or managed devices.
- the XNMP gateway performs transformations so that the link between the network management system and XNMP gateway uses XML or a similar protocol, and the links between the XNMP gateway and managed devices use SNMP or other local protocol.
- XML is more flexible and robust than SNMP, resulting in improved processing efficiencies at the network management system.
- Embodiments of the invention provide a method for managing a network, including: receiving an eXtensible Mark-up Language (XML)-formatted request for data, the data associated with a managed Voice over IP (VoIP) device; transforming the XML-formatted request to a Simple Network Management Protocol (SNMP)-formatted command; and receiving an SNMP-formatted result based on the SNMP-formatted command.
- XML eXtensible Mark-up Language
- VoIP Voice over IP
- SNMP Simple Network Management Protocol
- Embodiments of the invention provide a method for processing data, including: receiving an eXtensible Mark-up Language (XML)-formatted request for data, the data associated with a managed Voice over IP (VoIP) device; specifying a device IP address in a first argument and a Xpath query in a second argument, the device IP address and the Xpath query based on the XML-formatted request; and identifying a Management Information Base (MIB) variable based on the Xpath query.
- XML eXtensible Mark-up Language
- VoIP Voice over IP
- MIB Management Information Base
- Embodiments of the invention provide a method for processing data, including: receiving Simple Network Management Protocol (SNMP) data; marking up the SNMP data based on an extensible Markup Language (XML) schema; and converting the SNMP data to XML-formatted data.
- SNMP Simple Network Management Protocol
- XML extensible Markup Language
- Embodiments of the invention also provide computer-readable medium for performing the foregoing methods.
- Embodiments of the invention provide a system configured to manage a network, including: a network management system; an extensible Network Management Protocol (XNMP) gateway coupled to the network management system; and at least one managed Voice over IP (VoIP) device coupled to the XNMP gateway, the XNMP gateway configured to receive an extensible Markup language (XML) request from the network management system, the XNMP gateway further configured to transform the XML request into an Simple Network Management Protocol (SNMP) command, the XNMP gateway further configured to send the SNMP to the at least one managed VoIP device.
- XNMP extensible Network Management Protocol
- VoIP Voice over IP
- FIG. 1 is a block diagram of a functional architecture of a communications network, according to the prior art
- FIG. 2 is a block diagram of a functional architecture of a communications network having a XNMP gateway, according to an embodiment of the invention
- FIG. 3 is a message sequence diagram of communications between a network management system, an XNMP gateway, and a managed device, according to an embodiment of the invention
- FIG. 4 is a flow diagram of XML processing, according to an embodiment of the invention.
- FIG. 5 is a flow diagram of a XML transformation process, according to an embodiment of the invention.
- FIG. 6 is an illustration of XML schema code, according to an embodiment of the invention.
- FIG. 7 is a flow diagram of a SNMP transformation process, according to an embodiment of the invention.
- FIG. 8 is a flow diagram of a portion of a XML transformation process, according to an embodiment of the invention.
- FIG. 9 is an illustration of eXtensible Style sheet Language (XSL) code, according to an embodiment of the invention.
- FIG. 10 is an illustration of process output data formats, according to an embodiment of the invention.
- FIG. 11 is a block diagram of a functional architecture of an XNMP gateway, according to an embodiment of the invention.
- This section provides an overview of an exemplary system and method for managing IP networks. More detailed disclosure is provided for transformation from XML to SNMP, and for transformation from SNMP to XML. A functional architecture for an exemplary XNMP gateway is also provided. Sub-headings are used below for organizational convenience. The disclosure of any particular feature is not necessarily limited to any particular section, however.
- FIG. 2 is a block diagram of a functional architecture of a communications network having a XNMP gateway, according to an embodiment of the invention.
- a network management system 205 is coupled to a XNMP gateway 210 via link 285 .
- the XNMP gateway 210 is coupled to managed devices 215 , 220 , 225 , 230 , 235 and 240 via links 250 , 255 , 260 , 265 , 270 and 275 , respectively.
- Managed device 245 is directly coupled to the network management system 205 via link 280 .
- the network management system 205 may be or include, for example, a personal computer, network server, or other networked device or system configured to perform administrative functions such as issuing commands, processing received information, and/or displaying information.
- the XNMP gateway 210 is configured to perform protocol transformations between the network management system 205 and the managed devices 215 , 220 , 225 , 230 , 235 , and 240 .
- the managed devices 215 , 220 , 225 , 230 , 235 , 240 , and 245 may be or include, for instance, routers, switches, call servers, gateways, gatekeepers, handsets, Multipoint Control Units (MCU's), Session Initiation Protocol (SIP) proxy servers, or other network devices.
- MCU's Multipoint Control Units
- SIP Session Initiation Protocol
- managed devices 215 , 220 , 225 , and 230 each include a Management Information Base (MIB) and a SNMP agent.
- MIB stores objects that relate to the status of the managed device.
- the SNMP agent updates the stored objects, is responsive to status requests from the network management system 205 , and may also issue alerts to the network management system 205 .
- links 250 , 255 , 260 , and 265 utilize SNMP
- link 270 utilizes a proprietary protocol
- link 275 utilizes Hyper-Text Transfer Protocol (HTTP) Common Gateway Interface (CGI)
- link 280 utilizes XNMP
- link 285 utilizes either XML over HTTP.
- the XNMP gateway 210 provides transformations between SNMP and XML, and between proprietary protocols and XML.
- the XNMP gateway 210 removes presentation information from the HTTP CGI formatted data received from the call server 240 to transform the HTTP CGI data to XML format. Because managed device 245 communicates via XNMP, managed device 245 is linked directly to the network management system 205 via link 280 without being routed through the XNMP gateway 210 .
- the functional architecture presented in FIG. 2 can be varied according to design choice. For instance, the type and quantity of managed devices will vary according to application needs.
- other implementations may use more than one network management system and/or more than one XMNP gateway to monitor a single network.
- the functions of the network management system and the XNMP gateway can be combined into a single functional component.
- Exemplary transformations between SNMP and XML are described below with reference to FIG. 3 .
- a benefit of using XML protocol for communications with the network management system 205 is discussed below with reference to FIG. 4 .
- FIG. 3 is a message sequence diagram of communications between a network management system 305 , an XNMP gateway 310 , and a managed device 315 , according to an embodiment of the invention.
- the network management system 305 sends an XML request to the XNMP gateway 310 .
- the XNMP gateway 310 transforms the XML request to a SNMP command and sends the SNMP command to the managed device 315 .
- the managed device 315 sends a SNMP response to the XNMP gateway 310 .
- the XNMP gateway 310 transforms the SNMP response into an XML result.
- the XNMP gateway 310 sends the XML result to the network management system 305 .
- the messaging sequence illustrated in FIG. 3 may be varied according to application requirements.
- a single XNMP gateway will communicate with multiple managed devices.
- a message may be initiated by the managed device 315 ; for example, a SNMP agent in managed device 315 could send an SNMP message to the XNMP gateway 310 as a result of an alert condition determined by the SNMP agent.
- SNMP messages are shown between the XNMP gateway 310 and the managed device 315 , other messaging protocols, such as a proprietary vendor protocol, may also be used between these two functional blocks.
- XML messaging or a similar protocol is used between the XNMP gateway 310 and the management system 305 , for reasons discussed below with reference to FIG. 4 .
- FIG. 4 is a flow diagram of XML processing, according to an embodiment of the invention.
- various processes can begin by receiving an XML message in step 405 .
- steps 410 , 415 , 420 , and 425 may be performed in combination or in the alternative.
- a portion of the XML data may be addressed or filtered using Xpath in step 410 .
- the XML data can be displayed or transformed into a new XML document via an XML Style sheet Transformation (XSLT) in step 415 .
- the XML data may be processed using Xquery (a more generalized version of Xpath) in step 420 .
- the XML data can be displayed using Cascading Style Sheets (CSS) in step 425 .
- CSS Cascading Style Sheets
- XML XML
- Using XML at the network management system may therefore result in decreased development time and maintenance expense.
- run-time overhead can also be reduced compared to a pure SNMP-based system, a network management system using XML may better support application environments such as VoIP that require near real-time performance.
- Xpath process 410 and/or Xquery process 420 are executed in the XNMP gateway 210 to transform an XML request into an SNMP command
- XSLT process 415 is used in the XNMP gateway 210 to transform an SNMP result into an XML result
- CSS process 425 may optionally be used to display at least a portion of the XML result at the network management system 205 .
- FIG. 5 is a flow diagram of a XML transformation process, according to an embodiment of the invention.
- the process begins in step 505 by receiving an XML request, for example from a network management system.
- the process specifies a device IP address in a first argument and an Xpath (or Xquery) query in a second argument. Both the target IP address and the Xpath (or Xquery) query are based on the XML request.
- the process finds corresponding MIB variables in step 515 .
- the process issues an SNMP command to the managed device.
- interface code such as “helper.getsnmp( )” may be used to specify the address and Xpath query.
- the form of an output from step 510 may be “helper.getsnmp(10.10.1.221,//dot1dTpFdbPort)” where “10.10.1.221” is the target IP address and “dotldTpFdbPort” is the Xpath query.
- Requests received in step 505 may require that MIB variables associated with phone number, voice quality, phone status, or other information is specified in step 510 in the alternative to, or in combination with, MAC address information.
- FIG. 6 is an illustration of XML schema code that may be used in executing step 515 , according to an embodiment of the invention.
- an element name of “dotldTpFdbPort” (the Xpath query) is associated with MIB variable “1.3.6.1.2.1.17.4.3.1.2.”
- the form of the SNMP command issued in step 520 may be “snmpwalk—c public 10.10.1.221 1.3.6.1.2.1.17.4.3.1.2.”
- FIG. 7 is a flow diagram of a SNMP transformation process, according to an embodiment of the invention.
- the process begins in step 705 by receiving the SNMP result from a managed device. Alternatively, the process could begin by receiving an alert from a SNMP agent in a managed device.
- the process marks up the SNMP result using an XML schema to create a first XML result.
- the process converts the first XML result to a second XML result using an XSLT.
- the format of the second XML result is predetermined according to application requirements.
- the process outputs the second XML result, for example to a network management system, in step 720 .
- Embodiments of the processes in FIG. 7 are described with reference to FIGS. 8-10 below.
- FIG. 8 is a flow diagram of a portion of a XML transformation process, according to an embodiment of the invention.
- the process in FIG. 8 is an exemplary embodiment of step 715 in FIG. 7 .
- the process begins by selecting an appropriate template in step 805 .
- the process lists a first or next port in step 810 .
- the process lists the first or next Media Access Control (MAC) address in step 815 .
- MAC Media Access Control
- conditional step 820 the process determines whether all MAC addresses have been listed. Where the result of conditional step 820 is in the negative, the process returns to step 815 to list an additional MAC address. Where the result of conditional step 820 is in the affirmative, the process advances to conditional step 825 to determine whether all ports have been listed. Where the result of conditional step 825 is in the negative, the process returns to step 810 to list the next port. Where the result of conditional step 825 is in the affirmative, the process terminates in step 830 .
- MAC Media Access
- FIG. 8 is an embodiment of a process that lists one or more MAC addresses associated with each of one or more ports based on marked-up XML data.
- FIG. 9 is an illustration of eXtensible Style sheet Language Transformation (XSLT) code, according to an embodiment of the invention.
- the XSLT code illustrated in FIG. 9 may be used in executing the conversion process illustrated as step 715 in FIG. 7 .
- the XSLT code illustrated in FIG. 9 executes a process that is substantially similar to the process illustrated in FIG. 8 .
- the code illustrated in FIG. 9 lists several XSLT elements, including: “xsl:template,” which defines a reusable template for generating the desired output for nodes of a predetermined type; “xsl:choose,” which provides repeated conditional testing in conjunction with the “xsl:otherwise” and “xsl:when” elements; “xsl:attribute,” which creates an attribute node and associates an output with the node; and “xsl:value-of,” which inserts the value of the selected node as text.
- a template named “VarBind” is used to list port number attributes and MAC address attributes into a predetermined format.
- Alternative templates could be selected in step 805 for data received from different types of managed devices.
- FIG. 10 is an illustration of process output data formats, according to an embodiment of the invention.
- the data formats in FIG. 10 relate to process steps illustrated in FIG. 7 .
- the data in box 1005 is the SNMP result output from receiving step 705
- the data in box 1010 is the first XML result output from step 710
- the data in box 1015 is the second XML result output from step 715 .
- FIG. 11 is a block diagram of a functional architecture of an XNMP gateway, according to an embodiment of the invention.
- the architecture illustrated in FIG. 11 is one embodiment of the XNMP gateway 210 shown in FIG. 2 .
- an XNMP gateway 210 includes a database 1105 coupled to a processor 1110 .
- a network management system interface 1115 and a managed device interface 1120 are further coupled to the processor 1110 .
- the database 1105 may be, for example, an eXist database that resides on any processor-readable storage medium.
- the database 1105 preferably includes multiple XML schemas 1125 and at least one XML style sheet 1130 .
- the network management system interface 1115 may be connected to link 285
- the managed device interface 1120 may be connected to links 250 , 255 , 260 , 265 , 270 , and 275 .
- Components of the gateway illustrated in FIG. 11 are preferably configured to execute the processes described above with reference to FIGS. 3-10 .
- the processor 1110 may receive a XML request at the network management system interface 1115 and retrieve at least one of the XML schemas 1125 to output a SNMP command via the managed device interface 1120 .
- the processor 1110 may receive an SNMP result (or alert) at the managed device interface 1120 , retrieve at least one XML schema 1125 and the XML style sheet 1130 to output an XML-formatted message at the network management system interface 1115 .
- the invention described above thus overcomes the disadvantages of known systems and methods by inserting a XNMP gateway between the network management system and one or managed devices so that the VoIP network management system operates with XML instead of the more conventional SNMP.
- this invention has been described in various explanatory embodiments, other embodiments and variations can be effected by a person of ordinary skill in the art without departing from the scope of the invention.
- XML At the network management system
- other common languages such as XHTML
- the invention is not necessarily limited to VoIP applications.
Abstract
Description
- The invention relates generally to the field of communications. More specifically, but not by way of limitation, the invention relates to a system and method for management of a Voice Over Internet Protocol (VoIP) or other Internet Protocol (IP) network using eXtensible Markup Language (XML).
- Voice over Internet Protocol (VoIP) is an alternative to circuit-committed protocols such as Time Division Multiplexing (TDM) that are used on conventional Public Switched Telephone Networks (PSTN's). With VoIP, voice communications share the same network with data, effectively consolidating bandwidth by sending packets to any available path at any given time. Monitoring and managing a VoIP network requires a network protocol to communicate with, and gather information from, numerous Internet Protocol (IP) network devices.
-
FIG. 1 is a block diagram of a functional architecture of a communications network, according to the prior art. As shown inFIG. 1 , anetwork management system 105 is coupled to manageddevices links links - SNMP has many disadvantages, however. For example, SNMP is limited to five management commands: “get” to request values from the Management Information Base (MIB) of a managed device; “get next” to request the successive values from the MIB; “get response” to retrieve the answer returned; “set” to update MIB values; and “trap” to send an event notification. Moreover, SNMP information is presented in long unstructured data strings. The limited command set and unwieldy data formats associated with SNMP result in increased cost and cycle time for the development and maintenance of IP network management systems. Moreover, the processing overhead for SNMP-based network management systems may be substantial, making them unsuitable for VoIP and other network communications that must operate in near real-time with low packet losses. A more robust management protocol is needed for time-sensitive IP network applications.
- The invention relates to a system and method for management of an IP network using eXtensible Markup Language (XML) or a similar protocol in addition to SNMP or other managed-device protocol. In embodiments of the invention, an XML Network Management Protocol (XNMP) gateway is coupled between the network management system and one or managed devices. The XNMP gateway performs transformations so that the link between the network management system and XNMP gateway uses XML or a similar protocol, and the links between the XNMP gateway and managed devices use SNMP or other local protocol. Advantageously, XML is more flexible and robust than SNMP, resulting in improved processing efficiencies at the network management system.
- Embodiments of the invention provide a method for managing a network, including: receiving an eXtensible Mark-up Language (XML)-formatted request for data, the data associated with a managed Voice over IP (VoIP) device; transforming the XML-formatted request to a Simple Network Management Protocol (SNMP)-formatted command; and receiving an SNMP-formatted result based on the SNMP-formatted command.
- Embodiments of the invention provide a method for processing data, including: receiving an eXtensible Mark-up Language (XML)-formatted request for data, the data associated with a managed Voice over IP (VoIP) device; specifying a device IP address in a first argument and a Xpath query in a second argument, the device IP address and the Xpath query based on the XML-formatted request; and identifying a Management Information Base (MIB) variable based on the Xpath query.
- Embodiments of the invention provide a method for processing data, including: receiving Simple Network Management Protocol (SNMP) data; marking up the SNMP data based on an extensible Markup Language (XML) schema; and converting the SNMP data to XML-formatted data.
- Embodiments of the invention also provide computer-readable medium for performing the foregoing methods.
- Embodiments of the invention provide a system configured to manage a network, including: a network management system; an extensible Network Management Protocol (XNMP) gateway coupled to the network management system; and at least one managed Voice over IP (VoIP) device coupled to the XNMP gateway, the XNMP gateway configured to receive an extensible Markup language (XML) request from the network management system, the XNMP gateway further configured to transform the XML request into an Simple Network Management Protocol (SNMP) command, the XNMP gateway further configured to send the SNMP to the at least one managed VoIP device.
- The features and advantages of the invention will become apparent from the following drawings and detailed description.
- Embodiments of the invention are described with reference to the following drawings, wherein:
-
FIG. 1 is a block diagram of a functional architecture of a communications network, according to the prior art; -
FIG. 2 is a block diagram of a functional architecture of a communications network having a XNMP gateway, according to an embodiment of the invention; -
FIG. 3 is a message sequence diagram of communications between a network management system, an XNMP gateway, and a managed device, according to an embodiment of the invention; -
FIG. 4 is a flow diagram of XML processing, according to an embodiment of the invention; -
FIG. 5 is a flow diagram of a XML transformation process, according to an embodiment of the invention; -
FIG. 6 is an illustration of XML schema code, according to an embodiment of the invention; -
FIG. 7 is a flow diagram of a SNMP transformation process, according to an embodiment of the invention; -
FIG. 8 is a flow diagram of a portion of a XML transformation process, according to an embodiment of the invention; -
FIG. 9 is an illustration of eXtensible Style sheet Language (XSL) code, according to an embodiment of the invention; -
FIG. 10 is an illustration of process output data formats, according to an embodiment of the invention; -
FIG. 11 is a block diagram of a functional architecture of an XNMP gateway, according to an embodiment of the invention. - This section provides an overview of an exemplary system and method for managing IP networks. More detailed disclosure is provided for transformation from XML to SNMP, and for transformation from SNMP to XML. A functional architecture for an exemplary XNMP gateway is also provided. Sub-headings are used below for organizational convenience. The disclosure of any particular feature is not necessarily limited to any particular section, however.
- Overview
-
FIG. 2 is a block diagram of a functional architecture of a communications network having a XNMP gateway, according to an embodiment of the invention. As shown therein, anetwork management system 205 is coupled to aXNMP gateway 210 vialink 285. In turn, the XNMPgateway 210 is coupled to manageddevices links device 245 is directly coupled to thenetwork management system 205 vialink 280. - In the illustrated embodiment, the
network management system 205 may be or include, for example, a personal computer, network server, or other networked device or system configured to perform administrative functions such as issuing commands, processing received information, and/or displaying information. The XNMPgateway 210 is configured to perform protocol transformations between thenetwork management system 205 and the manageddevices devices - In the illustrated embodiment, managed
devices network management system 205, and may also issue alerts to thenetwork management system 205. - In the illustrated embodiment,
links link 270 utilizes a proprietary protocol,link 275 utilizes Hyper-Text Transfer Protocol (HTTP) Common Gateway Interface (CGI),link 280 utilizes XNMP, andlink 285 utilizes either XML over HTTP. The XNMPgateway 210 provides transformations between SNMP and XML, and between proprietary protocols and XML. - In the illustrated embodiment, the XNMP
gateway 210 removes presentation information from the HTTP CGI formatted data received from thecall server 240 to transform the HTTP CGI data to XML format. Because manageddevice 245 communicates via XNMP, manageddevice 245 is linked directly to thenetwork management system 205 vialink 280 without being routed through the XNMPgateway 210. - The functional architecture presented in
FIG. 2 can be varied according to design choice. For instance, the type and quantity of managed devices will vary according to application needs. In addition, other implementations may use more than one network management system and/or more than one XMNP gateway to monitor a single network. In other embodiments, the functions of the network management system and the XNMP gateway can be combined into a single functional component. - Exemplary transformations between SNMP and XML are described below with reference to
FIG. 3 . A benefit of using XML protocol for communications with thenetwork management system 205 is discussed below with reference toFIG. 4 . -
FIG. 3 is a message sequence diagram of communications between anetwork management system 305, anXNMP gateway 310, and a manageddevice 315, according to an embodiment of the invention. As illustrated inFIG. 3 , thenetwork management system 305 sends an XML request to theXNMP gateway 310. In response, theXNMP gateway 310 transforms the XML request to a SNMP command and sends the SNMP command to the manageddevice 315. The manageddevice 315 sends a SNMP response to theXNMP gateway 310. TheXNMP gateway 310 transforms the SNMP response into an XML result. Finally, theXNMP gateway 310 sends the XML result to thenetwork management system 305. - The messaging sequence illustrated in
FIG. 3 may be varied according to application requirements. For example, in some embodiments, a single XNMP gateway will communicate with multiple managed devices. Further, a message may be initiated by the manageddevice 315; for example, a SNMP agent in manageddevice 315 could send an SNMP message to theXNMP gateway 310 as a result of an alert condition determined by the SNMP agent. Moreover, although SNMP messages are shown between theXNMP gateway 310 and the manageddevice 315, other messaging protocols, such as a proprietary vendor protocol, may also be used between these two functional blocks. Preferably, XML messaging or a similar protocol is used between theXNMP gateway 310 and themanagement system 305, for reasons discussed below with reference toFIG. 4 . -
FIG. 4 is a flow diagram of XML processing, according to an embodiment of the invention. As shown inFIG. 4 , various processes can begin by receiving an XML message instep 405.Subsequent steps step 410. The XML data can be displayed or transformed into a new XML document via an XML Style sheet Transformation (XSLT) instep 415. The XML data may be processed using Xquery (a more generalized version of Xpath) instep 420. Finally, the XML data can be displayed using Cascading Style Sheets (CSS) instep 425. - Accordingly, a variety of powerful and flexible tools exist to process received XML data. Using XML at the network management system may therefore result in decreased development time and maintenance expense. Moreover, because run-time overhead can also be reduced compared to a pure SNMP-based system, a network management system using XML may better support application environments such as VoIP that require near real-time performance.
- In embodiments of the invention,
Xpath process 410 and/orXquery process 420 are executed in theXNMP gateway 210 to transform an XML request into an SNMP command, andXSLT process 415 is used in theXNMP gateway 210 to transform an SNMP result into an XML result.CSS process 425 may optionally be used to display at least a portion of the XML result at thenetwork management system 205. - XML-to-SNMP Transformation
-
FIG. 5 is a flow diagram of a XML transformation process, according to an embodiment of the invention. As shown inFIG. 5 , the process begins instep 505 by receiving an XML request, for example from a network management system. Next, instep 510, the process specifies a device IP address in a first argument and an Xpath (or Xquery) query in a second argument. Both the target IP address and the Xpath (or Xquery) query are based on the XML request. Next, the process finds corresponding MIB variables instep 515. Finally, instep 520, the process issues an SNMP command to the managed device. - In executing
step 510, interface code such as “helper.getsnmp( )” may be used to specify the address and Xpath query. For example, the form of an output fromstep 510 may be “helper.getsnmp(10.10.1.221,//dot1dTpFdbPort)” where “10.10.1.221” is the target IP address and “dotldTpFdbPort” is the Xpath query. Requests received instep 505 may require that MIB variables associated with phone number, voice quality, phone status, or other information is specified instep 510 in the alternative to, or in combination with, MAC address information. -
FIG. 6 is an illustration of XML schema code that may be used in executingstep 515, according to an embodiment of the invention. Using the portion of schema shown inFIG. 6 , an element name of “dotldTpFdbPort” (the Xpath query) is associated with MIB variable “1.3.6.1.2.1.17.4.3.1.2.” Accordingly, the form of the SNMP command issued instep 520 may be “snmpwalk—c public 10.10.1.221 1.3.6.1.2.1.17.4.3.1.2.” - SNMP-to-XML Transformation
-
FIG. 7 is a flow diagram of a SNMP transformation process, according to an embodiment of the invention. As shown inFIG. 7 , the process begins instep 705 by receiving the SNMP result from a managed device. Alternatively, the process could begin by receiving an alert from a SNMP agent in a managed device. Next, instep 710, the process marks up the SNMP result using an XML schema to create a first XML result. Then, instep 715, the process converts the first XML result to a second XML result using an XSLT. The format of the second XML result is predetermined according to application requirements. Finally, the process outputs the second XML result, for example to a network management system, instep 720. Embodiments of the processes inFIG. 7 are described with reference toFIGS. 8-10 below. -
FIG. 8 is a flow diagram of a portion of a XML transformation process, according to an embodiment of the invention. The process inFIG. 8 is an exemplary embodiment ofstep 715 inFIG. 7 . The process begins by selecting an appropriate template instep 805. Next, the process lists a first or next port instep 810. Then, for the current port, the process lists the first or next Media Access Control (MAC) address instep 815. Inconditional step 820, the process determines whether all MAC addresses have been listed. Where the result ofconditional step 820 is in the negative, the process returns to step 815 to list an additional MAC address. Where the result ofconditional step 820 is in the affirmative, the process advances toconditional step 825 to determine whether all ports have been listed. Where the result ofconditional step 825 is in the negative, the process returns to step 810 to list the next port. Where the result ofconditional step 825 is in the affirmative, the process terminates instep 830. - Accordingly,
FIG. 8 is an embodiment of a process that lists one or more MAC addresses associated with each of one or more ports based on marked-up XML data. -
FIG. 9 is an illustration of eXtensible Style sheet Language Transformation (XSLT) code, according to an embodiment of the invention. The XSLT code illustrated inFIG. 9 may be used in executing the conversion process illustrated asstep 715 inFIG. 7 . The XSLT code illustrated inFIG. 9 executes a process that is substantially similar to the process illustrated inFIG. 8 . - The code illustrated in
FIG. 9 lists several XSLT elements, including: “xsl:template,” which defines a reusable template for generating the desired output for nodes of a predetermined type; “xsl:choose,” which provides repeated conditional testing in conjunction with the “xsl:otherwise” and “xsl:when” elements; “xsl:attribute,” which creates an attribute node and associates an output with the node; and “xsl:value-of,” which inserts the value of the selected node as text. In the illustrated embodiment, a template named “VarBind” is used to list port number attributes and MAC address attributes into a predetermined format. Alternative templates could be selected instep 805 for data received from different types of managed devices. -
FIG. 10 is an illustration of process output data formats, according to an embodiment of the invention. The data formats inFIG. 10 relate to process steps illustrated inFIG. 7 . In particular, the data inbox 1005 is the SNMP result output from receivingstep 705, the data inbox 1010 is the first XML result output fromstep 710 and the data inbox 1015 is the second XML result output fromstep 715. - Functional Architecture of an XNMP Gateway
-
FIG. 11 is a block diagram of a functional architecture of an XNMP gateway, according to an embodiment of the invention. The architecture illustrated inFIG. 11 is one embodiment of theXNMP gateway 210 shown inFIG. 2 . - As shown in
FIG. 11 , anXNMP gateway 210 includes adatabase 1105 coupled to aprocessor 1110. A networkmanagement system interface 1115 and a manageddevice interface 1120 are further coupled to theprocessor 1110. Thedatabase 1105 may be, for example, an eXist database that resides on any processor-readable storage medium. Thedatabase 1105 preferably includesmultiple XML schemas 1125 and at least oneXML style sheet 1130. With reference also toFIG. 2 , the networkmanagement system interface 1115 may be connected to link 285, and the manageddevice interface 1120 may be connected tolinks - Components of the gateway illustrated in
FIG. 11 are preferably configured to execute the processes described above with reference toFIGS. 3-10 . For example, in performing a XML-to-SNMP transformation, theprocessor 1110 may receive a XML request at the networkmanagement system interface 1115 and retrieve at least one of theXML schemas 1125 to output a SNMP command via the manageddevice interface 1120. Likewise, in performing a SNMP-to-XML transformation, theprocessor 1110 may receive an SNMP result (or alert) at the manageddevice interface 1120, retrieve at least oneXML schema 1125 and theXML style sheet 1130 to output an XML-formatted message at the networkmanagement system interface 1115. - The invention described above thus overcomes the disadvantages of known systems and methods by inserting a XNMP gateway between the network management system and one or managed devices so that the VoIP network management system operates with XML instead of the more conventional SNMP. While this invention has been described in various explanatory embodiments, other embodiments and variations can be effected by a person of ordinary skill in the art without departing from the scope of the invention. For example, although disclosed embodiments utilize XML at the network management system, other common languages, such as XHTML, could be used so long as the appropriate transformations are performed at the gateway that is connected between the network management system and the managed device(s). Moreover, the invention is not necessarily limited to VoIP applications.
Claims (19)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/023,629 US20060168229A1 (en) | 2004-12-29 | 2004-12-29 | System and method for network management using extensible markup language |
US13/863,274 US9491245B2 (en) | 2004-12-29 | 2013-04-15 | System and method for network management using extensible markup language |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/023,629 US20060168229A1 (en) | 2004-12-29 | 2004-12-29 | System and method for network management using extensible markup language |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/863,274 Continuation US9491245B2 (en) | 2004-12-29 | 2013-04-15 | System and method for network management using extensible markup language |
Publications (1)
Publication Number | Publication Date |
---|---|
US20060168229A1 true US20060168229A1 (en) | 2006-07-27 |
Family
ID=36698347
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/023,629 Abandoned US20060168229A1 (en) | 2004-12-29 | 2004-12-29 | System and method for network management using extensible markup language |
US13/863,274 Active 2026-01-28 US9491245B2 (en) | 2004-12-29 | 2013-04-15 | System and method for network management using extensible markup language |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/863,274 Active 2026-01-28 US9491245B2 (en) | 2004-12-29 | 2013-04-15 | System and method for network management using extensible markup language |
Country Status (1)
Country | Link |
---|---|
US (2) | US20060168229A1 (en) |
Cited By (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040199635A1 (en) * | 2002-10-16 | 2004-10-07 | Tuan Ta | System and method for dynamic bandwidth provisioning |
US20040267918A1 (en) * | 2003-06-30 | 2004-12-30 | Guarraci Brian J | Managing headless computer systems |
US20050044350A1 (en) * | 2003-08-20 | 2005-02-24 | Eric White | System and method for providing a secure connection between networked computers |
US20050204031A1 (en) * | 2004-03-10 | 2005-09-15 | Keith Johnston | System and method for comprehensive code generation for system management |
US20050204169A1 (en) * | 2004-03-10 | 2005-09-15 | Tonnesen Steven D. | System and method for detection of aberrant network behavior by clients of a network access gateway |
US20050204022A1 (en) * | 2004-03-10 | 2005-09-15 | Keith Johnston | System and method for network management XML architectural abstraction |
US20060204943A1 (en) * | 2005-03-10 | 2006-09-14 | Qbinternational | VOIP e-learning system |
US7665130B2 (en) | 2004-03-10 | 2010-02-16 | Eric White | System and method for double-capture/double-redirect to a different location |
US20110239109A1 (en) * | 2010-03-24 | 2011-09-29 | Mark Nixon | Methods and apparatus to display process data |
US20110238780A1 (en) * | 2010-03-24 | 2011-09-29 | Lee Allen Neitzel | Methods and apparatus to access process data stored on a server |
US8117639B2 (en) | 2002-10-10 | 2012-02-14 | Rocksteady Technologies, Llc | System and method for providing access control |
US20120173658A1 (en) * | 2010-12-30 | 2012-07-05 | Sebastian Tussing | Schema Validation Proxy |
US20130039258A1 (en) * | 2011-08-11 | 2013-02-14 | Yoshihiro Suzuki | Communication System and Communication Method |
US8397282B2 (en) | 2004-03-10 | 2013-03-12 | Rpx Corporation | Dynamically adaptive network firewalls and method, system and computer program product implementing same |
US8543710B2 (en) | 2004-03-10 | 2013-09-24 | Rpx Corporation | Method and system for controlling network access |
EP2747341A1 (en) * | 2012-12-21 | 2014-06-25 | Sap Ag | Connecting computer management systems via cellular digital telecommunication networks |
US20140365621A1 (en) * | 2013-06-06 | 2014-12-11 | Alcatel-Lucent Canada, Inc. | Netconf snmp gateway |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108418778A (en) * | 2017-02-09 | 2018-08-17 | 北京视联动力国际信息技术有限公司 | A kind of internet and method, apparatus and interactive system regarding connected network communication |
CN108509187B (en) * | 2018-03-29 | 2021-05-18 | 烽火通信科技股份有限公司 | Method and system for automatically generating MIB function code of software platform |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020032790A1 (en) * | 2000-05-31 | 2002-03-14 | Michael Linderman | Object oriented communications system over the internet |
US20020176404A1 (en) * | 2001-04-13 | 2002-11-28 | Girard Gregory D. | Distributed edge switching system for voice-over-packet multiservice network |
US20030059038A1 (en) * | 2001-09-24 | 2003-03-27 | Teleware, Inc. | Teledata space and docking station with modular and integrated display |
US20040221026A1 (en) * | 2003-04-30 | 2004-11-04 | Dorland Chia-Chu S. | Method and system for managing a network |
US20050204022A1 (en) * | 2004-03-10 | 2005-09-15 | Keith Johnston | System and method for network management XML architectural abstraction |
US20060036723A1 (en) * | 2004-07-30 | 2006-02-16 | Michael Yip | Method and apparatus for converting network management protocol to markup language |
Family Cites Families (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5802146A (en) * | 1995-11-22 | 1998-09-01 | Bell Atlantic Network Services, Inc. | Maintenance operations console for an advanced intelligent network |
US20020078134A1 (en) * | 2000-12-18 | 2002-06-20 | Stone Alan E. | Push-based web site content indexing |
US20040117439A1 (en) * | 2001-02-12 | 2004-06-17 | Levett David Lawrence | Client software enabling a client to run a network based application |
US6816897B2 (en) * | 2001-04-30 | 2004-11-09 | Opsware, Inc. | Console mapping tool for automated deployment and management of network devices |
US20050086584A1 (en) * | 2001-07-09 | 2005-04-21 | Microsoft Corporation | XSL transform |
US6901410B2 (en) * | 2001-09-10 | 2005-05-31 | Marron Pedro Jose | LDAP-based distributed cache technology for XML |
US20030069960A1 (en) * | 2001-10-04 | 2003-04-10 | Symons Julie A. | Method for describing and comparing data center physical and logical topologies and device configurations |
JP3912582B2 (en) * | 2001-11-20 | 2007-05-09 | ブラザー工業株式会社 | Network system, network device, web page creation method, web page creation program, and data transmission program |
US20030105881A1 (en) * | 2001-12-03 | 2003-06-05 | Symons Julie Anna | Method for detecting and preventing intrusion in a virtually-wired switching fabric |
US7370032B2 (en) * | 2002-04-30 | 2008-05-06 | Sap Ag | Data gathering |
US7234109B2 (en) * | 2002-11-19 | 2007-06-19 | Microsoft Corp. | Equality of extensible markup language structures |
US7831905B1 (en) * | 2002-11-22 | 2010-11-09 | Sprint Spectrum L.P. | Method and system for creating and providing web-based documents to information devices |
US7673048B1 (en) * | 2003-02-24 | 2010-03-02 | Cisco Technology, Inc. | Methods and apparatus for establishing a computerized device tunnel connection |
US7657832B1 (en) * | 2003-09-18 | 2010-02-02 | Adobe Systems Incorporated | Correcting validation errors in structured documents |
US20050091346A1 (en) * | 2003-10-23 | 2005-04-28 | Brijesh Krishnaswami | Settings management infrastructure |
US7315852B2 (en) * | 2003-10-31 | 2008-01-01 | International Business Machines Corporation | XPath containment for index and materialized view matching |
US20050114851A1 (en) * | 2003-11-26 | 2005-05-26 | Brett Watson-Luke | System and method for configuring a graphical user interface based on data type |
US7454696B2 (en) * | 2004-04-09 | 2008-11-18 | International Business Machines Corporation | Method and apparatus for stream based markup language post-processing |
US20050160175A1 (en) * | 2004-01-21 | 2005-07-21 | D-Link Corporation | Communication system employing HTTP as transfer protocol and employing XML documents to automatically configure VoIP device |
US20060123393A1 (en) * | 2004-12-02 | 2006-06-08 | Brian Atkins | User interface for network application |
-
2004
- 2004-12-29 US US11/023,629 patent/US20060168229A1/en not_active Abandoned
-
2013
- 2013-04-15 US US13/863,274 patent/US9491245B2/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020032790A1 (en) * | 2000-05-31 | 2002-03-14 | Michael Linderman | Object oriented communications system over the internet |
US20020176404A1 (en) * | 2001-04-13 | 2002-11-28 | Girard Gregory D. | Distributed edge switching system for voice-over-packet multiservice network |
US20030059038A1 (en) * | 2001-09-24 | 2003-03-27 | Teleware, Inc. | Teledata space and docking station with modular and integrated display |
US20040221026A1 (en) * | 2003-04-30 | 2004-11-04 | Dorland Chia-Chu S. | Method and system for managing a network |
US20050204022A1 (en) * | 2004-03-10 | 2005-09-15 | Keith Johnston | System and method for network management XML architectural abstraction |
US20060036723A1 (en) * | 2004-07-30 | 2006-02-16 | Michael Yip | Method and apparatus for converting network management protocol to markup language |
Cited By (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8117639B2 (en) | 2002-10-10 | 2012-02-14 | Rocksteady Technologies, Llc | System and method for providing access control |
US8484695B2 (en) | 2002-10-10 | 2013-07-09 | Rpx Corporation | System and method for providing access control |
US20040199635A1 (en) * | 2002-10-16 | 2004-10-07 | Tuan Ta | System and method for dynamic bandwidth provisioning |
US20040267918A1 (en) * | 2003-06-30 | 2004-12-30 | Guarraci Brian J | Managing headless computer systems |
US7424525B2 (en) * | 2003-06-30 | 2008-09-09 | Microsoft Corporation | Managing headless computer systems |
US20050044350A1 (en) * | 2003-08-20 | 2005-02-24 | Eric White | System and method for providing a secure connection between networked computers |
US8429725B2 (en) | 2003-08-20 | 2013-04-23 | Rpx Corporation | System and method for providing a secure connection between networked computers |
US8381273B2 (en) | 2003-08-20 | 2013-02-19 | Rpx Corporation | System and method for providing a secure connection between networked computers |
US8543710B2 (en) | 2004-03-10 | 2013-09-24 | Rpx Corporation | Method and system for controlling network access |
US20050204022A1 (en) * | 2004-03-10 | 2005-09-15 | Keith Johnston | System and method for network management XML architectural abstraction |
US8019866B2 (en) | 2004-03-10 | 2011-09-13 | Rocksteady Technologies, Llc | System and method for detection of aberrant network behavior by clients of a network access gateway |
US20050204031A1 (en) * | 2004-03-10 | 2005-09-15 | Keith Johnston | System and method for comprehensive code generation for system management |
US8543693B2 (en) | 2004-03-10 | 2013-09-24 | Rpx Corporation | System and method for detection of aberrant network behavior by clients of a network access gateway |
US20090300177A1 (en) * | 2004-03-10 | 2009-12-03 | Eric White | System and Method For Detection of Aberrant Network Behavior By Clients of a Network Access Gateway |
US7665130B2 (en) | 2004-03-10 | 2010-02-16 | Eric White | System and method for double-capture/double-redirect to a different location |
US20050204169A1 (en) * | 2004-03-10 | 2005-09-15 | Tonnesen Steven D. | System and method for detection of aberrant network behavior by clients of a network access gateway |
US8397282B2 (en) | 2004-03-10 | 2013-03-12 | Rpx Corporation | Dynamically adaptive network firewalls and method, system and computer program product implementing same |
US20060204943A1 (en) * | 2005-03-10 | 2006-09-14 | Qbinternational | VOIP e-learning system |
US20110238780A1 (en) * | 2010-03-24 | 2011-09-29 | Lee Allen Neitzel | Methods and apparatus to access process data stored on a server |
US10574791B2 (en) | 2010-03-24 | 2020-02-25 | Fisher-Rosemount Systems, Inc. | Methods and apparatus to access process data stored on a server |
US9122764B2 (en) | 2010-03-24 | 2015-09-01 | Fisher-Rosemount Systems, Inc. | Methods and apparatus to access process data stored on a server |
US20110239109A1 (en) * | 2010-03-24 | 2011-09-29 | Mark Nixon | Methods and apparatus to display process data |
US20120173658A1 (en) * | 2010-12-30 | 2012-07-05 | Sebastian Tussing | Schema Validation Proxy |
US9374437B2 (en) * | 2010-12-30 | 2016-06-21 | Sap Se | Schema validation proxy |
US8842686B2 (en) * | 2011-08-11 | 2014-09-23 | Funai Electric Co., Ltd. | Communication system configured with an SIP functioned relay server and communication method using the same |
US20130039258A1 (en) * | 2011-08-11 | 2013-02-14 | Yoshihiro Suzuki | Communication System and Communication Method |
EP2747341A1 (en) * | 2012-12-21 | 2014-06-25 | Sap Ag | Connecting computer management systems via cellular digital telecommunication networks |
US20140365621A1 (en) * | 2013-06-06 | 2014-12-11 | Alcatel-Lucent Canada, Inc. | Netconf snmp gateway |
US9258132B2 (en) * | 2013-06-06 | 2016-02-09 | Alcatel Lucent | NETCONF SNMP gateway |
Also Published As
Publication number | Publication date |
---|---|
US20130297762A1 (en) | 2013-11-07 |
US9491245B2 (en) | 2016-11-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9491245B2 (en) | System and method for network management using extensible markup language | |
US9418053B2 (en) | Method and system for deploying content to wireless devices | |
US7395322B2 (en) | Method and apparatus for provisioning network devices using instructions in Extensible Markup Language | |
US20050204022A1 (en) | System and method for network management XML architectural abstraction | |
US8661095B2 (en) | Identifying scripting form of text commands for a network device | |
CN100499498C (en) | A device, system and method for realizing MIB adaptation | |
Choi et al. | XML‐Based Network Management for IP Networks | |
KR100737991B1 (en) | Priorization of management objects | |
WO2006014766A2 (en) | Method and apparatus for converting network management protocol to markup language | |
US20110295989A1 (en) | Network system, network management device and gateway device | |
US20070100866A1 (en) | Method for registering a template message, generating an update message, regenerating and providing an application request, computer arrangement, computer program and computer program product | |
Oh et al. | Interaction translation methods for XML/SNMP gateway | |
US8135860B1 (en) | Content interpolating web proxy server | |
JP2009265718A (en) | Network device transmitting only difference data of network management information, server, program and method | |
US20230308348A1 (en) | Server to support client data models from heterogeneous data sources | |
JP2009211504A (en) | Information providing server, program, information providing method, and information providing system | |
EP1297451B1 (en) | Service provision in a communications network | |
US20040210631A1 (en) | Method and apparatus for accessing legacy data in a standardized environment | |
JP2002366399A (en) | Method, system, and program for ldap/xml conversion, recording medium, and ldap server | |
Lewis et al. | The role of XML in TMN evolution | |
Shin et al. | XNMP-an XML based network management protocol over VoIP | |
KR100503826B1 (en) | Xml/snmp gateway for integrated network management | |
WO2009016369A1 (en) | Communications network | |
CN114844756A (en) | Method for managing network equipment based on NETCONF proxy server | |
KR100495834B1 (en) | The converting system for abstracting snmp operation into xml operation and the method therefor, and computer program product using the same |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: QOVIA, INC., MARYLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SHIM, CHOON B.;SHIN, DONGWOOK;REEL/FRAME:015954/0062 Effective date: 20050308 |
|
AS | Assignment |
Owner name: CISCO SYSTEMS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:QOVIA, INC.;REEL/FRAME:020208/0156 Effective date: 20070202 Owner name: CISCO SYSTEMS, INC.,CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:QOVIA, INC.;REEL/FRAME:020208/0156 Effective date: 20070202 |
|
AS | Assignment |
Owner name: CISCO TECHNOLOGY, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CISCO SYSTEMS, INC.;REEL/FRAME:020860/0257 Effective date: 20071210 Owner name: CISCO TECHNOLOGY, INC.,CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CISCO SYSTEMS, INC.;REEL/FRAME:020860/0257 Effective date: 20071210 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |