WO1999029067A1 - Http interface to element manager infrastructure - Google Patents

Http interface to element manager infrastructure Download PDF

Info

Publication number
WO1999029067A1
WO1999029067A1 PCT/CA1998/001113 CA9801113W WO9929067A1 WO 1999029067 A1 WO1999029067 A1 WO 1999029067A1 CA 9801113 W CA9801113 W CA 9801113W WO 9929067 A1 WO9929067 A1 WO 9929067A1
Authority
WO
WIPO (PCT)
Prior art keywords
http
element manager
browser
proxy
interface
Prior art date
Application number
PCT/CA1998/001113
Other languages
French (fr)
Inventor
Vincent Kadar
Frank Duimovich
Robert Turner
Original Assignee
Crosskeys Systems Corporation
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Crosskeys Systems Corporation filed Critical Crosskeys Systems Corporation
Priority to EP98958750A priority Critical patent/EP1038373A1/en
Publication of WO1999029067A1 publication Critical patent/WO1999029067A1/en

Links

Classifications

    • 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/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/0253—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using browsers or web-pages for accessing management information

Definitions

  • This invention relates to network management, and in particular an interface to an element management infrastructure in the Telecommunications Management Network (TMN) model.
  • TTN Telecommunications Management Network
  • Telecommunications Management Network (TMN) model, developed by the International Telecommunications Union (ITU), defines three areas: Element Management, Network Management and Service Management.
  • the Element Manager Layer controls the information exchange between network elements or groups of network elements. Functions within this layer communicate with the Network Management Layer by relaying element status and performance to a network management system (NMS). Element management allows TeMIP users to remotely configure equipment from virtually any equipment vendor at the Element Management Layer of the TMN Model.
  • NMS network management system
  • GDMO Guidelines for Definition of Managed Objects
  • GDMO is a standard for defining objects in a network in a consistent way. With a consistent "language" for describing such objects as workstations, LAN servers, and switches, programs can be written to control or sense the status of network elements throughout a network. GDMO prescribes how a network product manufacturer must describe the product formally so that others can write programs that recognize and deal with the product. GDMO is used to describe the class or classes of the object, how the object behaves, its attributes, and classes that it may inherit. Issues arise when the definition of the managed object class changes i.e. settable values change, GDMO definitions change etc. A change is then required in the definition of the managed objects as well as the test driver/viewer information. This creates inconsistencies in the sense that different definitions of the managed objects are essentially introduced, in other words, debugging now requires testing the test driver as well.
  • the element information is typically presented in the form of a GUI (Graphical User Interface).
  • GUI Graphic User Interface
  • An object of the invention is to alleviate this problem.
  • an element Manager Infrastructure in the TMN model having an interface to a browser.
  • the interface is preferably an HTTP interface.
  • HTTP stands for hyper text transfer protocol, and is a protocol that enables web browsers to interpret documents marked up with graphics and formatting. Different browsers may present the same document in different ways.
  • the HTTP interface provides immediate support for managed objects modeled in an element manager. When a managed object is introduced immediate support for testing and viewing the status of the object is supported. Managed object attributes can be set/reset, and reconciled, as well, simulate events for managed objects can be executed.
  • dynamic html pages are generated on the fly as the object model changes. This concept is applicable anywhere objects model the underlying problem domain through the use of data driven modeled attributes.
  • Figure 1 depicts the high level objects, with their relationships to each other, involved in the design and implementation of the HTTP interface
  • Figure 2 depicts the HTTP Interface Message Flow.
  • the element process manager 10 comprises a connection manager 11, a node manager 12, an NEM (Network Element Model. This is a term used to refer to the object model used to model the equipment being managed.) objects database 13, an HTTP parser 14, and an HTTP proxy 15.
  • the proxy 15 communicates under the control of the connection manager with an Internet Browser 16 using the http protocol.
  • the HTTP Proxy component 15 mingles with the several components of the architecture.
  • the HTTP Proxy 15 defines the interface for HTTP communication.
  • the NEM objects 13, shown as a singular module, represent a collection of persistent data objects.
  • the relationship to the NEM objects are direct access, through a get, and indirect (messaging) for all other messages.
  • the relationship line between the Node Manager 12 and the HTTP Proxy 15 is not solid since this relationship is garnered via messaging only.
  • FIG. 1 illustrates the HTTP components' existence within the process boundary of the element manager.
  • the HTTP interface could exist within its own process boundary translating the requests to specialized element management messages.
  • the Internet Browser 6 can be any recognized Web Browser, i.e. Netscape Navigator, Hot Java, Microsoft Explorer, etc.
  • FIG. 2 traces a message communicated from a web browser to the ATMC base process.
  • ATMC stands for ATM Commander by Crosskeys Systems Corporation, which provides element management services for the Siemens EWSX V3 node.
  • the element management process creates an HTTP proxy, if it is the first time establishing a HTTP connection 2. It then establishes the HTTP Proxy as the communication link for receiving all HTTP requests 3, 4 from the browser 16.
  • the HTTP proxy When a request is received by the HTTP proxy it processes the message 5 determining where the message should be directed (NodeManager or NEM Objects). The Proxy then interprets the text in the URL and acts on the request by either getting, or setting, data into the NEM objects 6, or even creating the appropriate NEM objects. At this point the HTTP Proxy needs to formulate the response. It now sends the compiled information to the HTTP parser 14 to format and data-fill the appropriate HTML response page 7. The HTTP proxy then streams the HTML response page to the browser 16 over link 8.
  • the HTTP Proxy's main responsibility is to service HTTP requests.
  • Supported HTTP requests include GET, HEAD, and POST.
  • Requests embedded in a HTTP message are directed to one of two places, the NEM objects, or the NodeManger. The following table below details the module receiving the message, the HTTP message, encoded message, and desired action for each message sent to the HTTP Proxy.
  • HTTP helper (not shown in the diagram) objects model the HTTP specification, and aid in the dissection of the received messages, as well as helping to formulate the responses.
  • Helper objects include: HTTP_Substitution, HTTP_URI, HTTP_Header, HTTP_Request, and HTTP_ResponseHeader. All these objects are reusable.
  • HTTP_Substitution object exists as entries in a dictionary, each with their identifier and data portion. The substitution object helps with parsing the request and formulating the response.
  • the HTTP_URJ object represents the Uniform Resource Identifier, also commonly referred to Uniform Resource Locator (URL). This object returns information with respect to a URI string parsing its contents and retrieving information such as absolute path, net path, host, port, etc.
  • the HTTP_Header object models a name- value pair for a HTTP message header.
  • the name and value information is encapsulated in the object which is then packaged in a list to be used by the request/response mechanism of the HTTP server.
  • the HTTP_Request object represents the data gathered from a simple/full request from a HTTP server. This class encompasses a HTTP GET, HEAD, and POST.
  • the HTTP_ResponseHeader object represents a FULL response to the HTTP client. Encapsulated within the class are the status codes identifying the response status.
  • the HTTP Parser's main responsibility is to execute a search for keywords located in a static HTML page and replace the keywords with data which has been compiled and interpreted by the HTTP Proxy.
  • the connection manager manages all communication to the ATM Commander base process.
  • the node manager is responsible for the management of multiple network elements in the ATMC. For a detailed explanation please see.
  • the NEM object represents the objects located in the database.
  • the http interface described provides immediate support for managed objects modeled in an element manager and thus gives the user access to a rich graphical user interface without requiring extensive modifications to the GUI code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

An element Manager Infrastructure in the TMN model has an interface, preferablyan an http interface, to a web browser. The interface in association with an http parser creates html pages on the fly.

Description

HTTP interface to Element Manager Infrastructure.
This invention relates to network management, and in particular an interface to an element management infrastructure in the Telecommunications Management Network (TMN) model.
The Telecommunications Management Network (TMN) model, developed by the International Telecommunications Union (ITU), defines three areas: Element Management, Network Management and Service Management.
In the TMN model, the Element Manager Layer controls the information exchange between network elements or groups of network elements. Functions within this layer communicate with the Network Management Layer by relaying element status and performance to a network management system (NMS). Element management allows TeMIP users to remotely configure equipment from virtually any equipment vendor at the Element Management Layer of the TMN Model.
To add the support infrastructure for viewing and testing the managed objects of an element managers, it is first necessary to add the support infrastructure (managed objects classes) to the architecture and then to create, or update, the test driver and viewer modules.
GDMO (Guidelines for Definition of Managed Objects) is a standard for defining objects in a network in a consistent way. With a consistent "language" for describing such objects as workstations, LAN servers, and switches, programs can be written to control or sense the status of network elements throughout a network. GDMO prescribes how a network product manufacturer must describe the product formally so that others can write programs that recognize and deal with the product. GDMO is used to describe the class or classes of the object, how the object behaves, its attributes, and classes that it may inherit. Issues arise when the definition of the managed object class changes i.e. settable values change, GDMO definitions change etc. A change is then required in the definition of the managed objects as well as the test driver/viewer information. This creates inconsistencies in the sense that different definitions of the managed objects are essentially introduced, in other words, debugging now requires testing the test driver as well.
The element information is typically presented in the form of a GUI (Graphical User Interface). In the prior art this necessitated the writing of a large amount of code. In the event of a change in the object model, for instance, the addition of new objects, it was necessary to write additional code, which is very time consuming.
An object of the invention is to alleviate this problem.
According to the present invention there is provided an element Manager Infrastructure in the TMN model having an interface to a browser.
The interface is preferably an HTTP interface. HTTP stands for hyper text transfer protocol, and is a protocol that enables web browsers to interpret documents marked up with graphics and formatting. Different browsers may present the same document in different ways. The HTTP interface provides immediate support for managed objects modeled in an element manager. When a managed object is introduced immediate support for testing and viewing the status of the object is supported. Managed object attributes can be set/reset, and reconciled, as well, simulate events for managed objects can be executed.
In accordance with the invention, dynamic html pages are generated on the fly as the object model changes. This concept is applicable anywhere objects model the underlying problem domain through the use of data driven modeled attributes.
The invention will now be described in more detail, by way of example, only with reference to the accompanying drawings, in which:-
Figure 1 depicts the high level objects, with their relationships to each other, involved in the design and implementation of the HTTP interface; and
Figure 2 depicts the HTTP Interface Message Flow.
In Figure 1, for simplicity only the necessary components of the network element manager are shown. The element process manager 10 comprises a connection manager 11, a node manager 12, an NEM (Network Element Model. This is a term used to refer to the object model used to model the equipment being managed.) objects database 13, an HTTP parser 14, and an HTTP proxy 15. The proxy 15 communicates under the control of the connection manager with an Internet Browser 16 using the http protocol.
The HTTP Proxy component 15 mingles with the several components of the architecture. The HTTP Proxy 15 defines the interface for HTTP communication. The NEM objects 13, shown as a singular module, represent a collection of persistent data objects. The relationship to the NEM objects are direct access, through a get, and indirect (messaging) for all other messages. The relationship line between the Node Manager 12 and the HTTP Proxy 15 is not solid since this relationship is garnered via messaging only.
Figure 1 illustrates the HTTP components' existence within the process boundary of the element manager. The HTTP interface could exist within its own process boundary translating the requests to specialized element management messages.
The Internet Browser 6 can be any recognized Web Browser, i.e. Netscape Navigator, Hot Java, Microsoft Explorer, etc.
Communication between components is shown in more detail in Figure 2, which traces a message communicated from a web browser to the ATMC base process. ATMC stands for ATM Commander by Crosskeys Systems Corporation, which provides element management services for the Siemens EWSX V3 node. When communication is initiated with the base process 1, by specifying the address and port to communicate with, i.e. http://yourMachine.company.com:80, the element management process creates an HTTP proxy, if it is the first time establishing a HTTP connection 2. It then establishes the HTTP Proxy as the communication link for receiving all HTTP requests 3, 4 from the browser 16.
When a request is received by the HTTP proxy it processes the message 5 determining where the message should be directed (NodeManager or NEM Objects). The Proxy then interprets the text in the URL and acts on the request by either getting, or setting, data into the NEM objects 6, or even creating the appropriate NEM objects. At this point the HTTP Proxy needs to formulate the response. It now sends the compiled information to the HTTP parser 14 to format and data-fill the appropriate HTML response page 7. The HTTP proxy then streams the HTML response page to the browser 16 over link 8.
The HTTP Proxy's main responsibility is to service HTTP requests. Supported HTTP requests include GET, HEAD, and POST. Requests embedded in a HTTP message are directed to one of two places, the NEM objects, or the NodeManger. The following table below details the module receiving the message, the HTTP message, encoded message, and desired action for each message sent to the HTTP Proxy.
Figure imgf000006_0001
HTTP helper (not shown in the diagram) objects model the HTTP specification, and aid in the dissection of the received messages, as well as helping to formulate the responses. Helper objects include: HTTP_Substitution, HTTP_URI, HTTP_Header, HTTP_Request, and HTTP_ResponseHeader. All these objects are reusable.
An HTTP_Substitution object exists as entries in a dictionary, each with their identifier and data portion. The substitution object helps with parsing the request and formulating the response. The HTTP_URJ object represents the Uniform Resource Identifier, also commonly referred to Uniform Resource Locator (URL). This object returns information with respect to a URI string parsing its contents and retrieving information such as absolute path, net path, host, port, etc.
The HTTP_Header object models a name- value pair for a HTTP message header. The name and value information is encapsulated in the object which is then packaged in a list to be used by the request/response mechanism of the HTTP server.
The HTTP_Request object represents the data gathered from a simple/full request from a HTTP server. This class encompasses a HTTP GET, HEAD, and POST.
The HTTP_ResponseHeader object represents a FULL response to the HTTP client. Encapsulated within the class are the status codes identifying the response status.
The HTTP Parser's main responsibility is to execute a search for keywords located in a static HTML page and replace the keywords with data which has been compiled and interpreted by the HTTP Proxy.
The connection manager manages all communication to the ATM Commander base process.
The node manager is responsible for the management of multiple network elements in the ATMC. For a detailed explanation please see.
The NEM object represents the objects located in the database.
The http interface described provides immediate support for managed objects modeled in an element manager and thus gives the user access to a rich graphical user interface without requiring extensive modifications to the GUI code.

Claims

Claims
1. An element manager infrastructure in the TMN model comprising an element management process having an interface to a browser.
2. An element manager infrastructure as claimed in claim 1, wherein said interface is a proxy.
3. An element manager infrastructure as claimed in claim 2, wherein said interface is an http proxy.
4. An element manager infrastructure as claimed in claim 3, wherein said http proxy exchanges messages with objects of said element management process.
5. An element manager infrastructure as claimed in any one of claims 1 to 4, wherein said browser is an Internet browser.
6. An element manager as claimed in any one of claims 1 to 5, further including an http parser for creating dynamic mark-up pages by replacing keywords in static pages with data that has been created and compiled by the proxy.
7. An element manager as claimed in claim 6, wherein said mark-up pages are html pages.
8. A method of interacting with a network element manager, comprising the steps of providing a browser to present a graphical user interface to the user, and establishing communication between said element manager and said browser via a proxy which forwards messages from the element manager in a common protocol understandable to said browser.
9. A method as claimed in claim 8, wherein said common protocol is http and said proxy is an http proxy.
10. A method as claimed in claim 9, wherein said proxy receives http requests from said browser, determines where in the element manager to direct said requests, and formulates a response to the browser.
11. A method as claimed in claim 10, wherein the proxy receives information from the element manager and sends it to an http parser, which formulates a response for the browser.
12. A method as claimed in claim 11, wherein said parser replaces keywords in a static mark-up language page with data which has been compiled and interpreted by the proxy.
13. A method as claimed in claim 11, wherein said mark-up language page is an html page.
14. A method as claimed in claim 12, wherein said http parser automatically formats and fills html response pages on the fly.
15. A method as claimed in any one of claims 8 to 14, wherein said browser is a web browser.
16. The use of a web browser as a graphical user interface for a network element manager, wherein said browser permits interactive communication with said network element manager.
PCT/CA1998/001113 1997-12-01 1998-12-01 Http interface to element manager infrastructure WO1999029067A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP98958750A EP1038373A1 (en) 1997-12-01 1998-12-01 Http interface to element manager infrastructure

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CA 2223123 CA2223123A1 (en) 1997-12-01 1997-12-01 Http interface to element manager infrastructure
CA2,223,123 1997-12-01

Publications (1)

Publication Number Publication Date
WO1999029067A1 true WO1999029067A1 (en) 1999-06-10

Family

ID=4161830

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CA1998/001113 WO1999029067A1 (en) 1997-12-01 1998-12-01 Http interface to element manager infrastructure

Country Status (3)

Country Link
EP (1) EP1038373A1 (en)
CA (1) CA2223123A1 (en)
WO (1) WO1999029067A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE19954289B4 (en) * 1999-11-11 2010-09-16 Tenovis Gmbh & Co. Kg Private telecommunications system and method for its configuration

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998004067A1 (en) * 1996-07-19 1998-01-29 Cisco Systems, Inc. Method and apparatus for providing multiple management interfaces to a network device

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998004067A1 (en) * 1996-07-19 1998-01-29 Cisco Systems, Inc. Method and apparatus for providing multiple management interfaces to a network device

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
DERI L: "Surfin' Network Resources across the Web", PROCEEDINGS OF IEEE INTERNATIONAL WORKSHOP ON SYSTEM MANAGEMENT, 19 June 1996 (1996-06-19) - 21 June 1996 (1996-06-21), pages 158 - 167, XP002100450 *
LARSEN A K: "THE NEXT WEB WAVE: NETWORK MANAGEMENT", DATA COMMUNICATIONS, vol. 25, no. 1, 1 January 1996 (1996-01-01), pages 31/32, 34, XP000545237 *
PRESTON D J: "INTERNET PROTOCOLS MIGRATE TO SILICON FOR NETWORKING DEVICES", ELECTRONIC DESIGN, vol. 45, no. 8, 14 April 1997 (1997-04-14), pages 87 - 90, 92 - 94, XP000730016 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE19954289B4 (en) * 1999-11-11 2010-09-16 Tenovis Gmbh & Co. Kg Private telecommunications system and method for its configuration

Also Published As

Publication number Publication date
EP1038373A1 (en) 2000-09-27
CA2223123A1 (en) 1999-06-01

Similar Documents

Publication Publication Date Title
US6253254B1 (en) Hyper media object management
US7325053B2 (en) Object oriented communication among platform-independent systems over networks using SOAP
US5973696A (en) Embedded web server
US6219708B1 (en) System for network resource management
US5905862A (en) Automatic web site registration with multiple search engines
US6456308B1 (en) Embedded web server
DE60121987T2 (en) Accessing data stored at an intermediate station from a service
US6918088B2 (en) Service portal with application framework for facilitating application and feature development
US6308206B1 (en) Internet enabled computer system management
US7395322B2 (en) Method and apparatus for provisioning network devices using instructions in Extensible Markup Language
US6209029B1 (en) Method and apparatus for accessing data sources in a three tier environment
US6701352B1 (en) Method and apparatus for importing information from a network resource
US20020152289A1 (en) System and method for accessing devices in a factory automation network
US20020174209A1 (en) Device configuration in a distributed environment
US20040024843A1 (en) Method for provisioning distributed web applications
US20030200301A1 (en) Web-based network management system
US6321251B1 (en) Gateway for dynamically providing web site status information
KR20010089173A (en) Method and apparatus for providing access to a legacy application on a distributed data processing system
CN100362788C (en) Network server and data interacting method for network server and browser
Whetzel Integrating the world wide web and database technology
EP1038373A1 (en) Http interface to element manager infrastructure
US8301587B2 (en) Internet enabled computer system management
US7181508B1 (en) System and method for communicating, monitoring and configuring a device operatively connected to a network
US7007094B1 (en) Object oriented communications system over the internet
Cisco Release Notes for CiscoWorks2000 Device Fault Manager 1.0 on Solaris

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): CA JP US

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
WWE Wipo information: entry into national phase

Ref document number: 1998958750

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 09555474

Country of ref document: US

WWP Wipo information: published in national office

Ref document number: 1998958750

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: CA

WWW Wipo information: withdrawn in national office

Ref document number: 1998958750

Country of ref document: EP