[go: up one dir, main page]

WO2000018069A1 - Process and device for managing at least one network element in a telecommunication network - Google Patents

Process and device for managing at least one network element in a telecommunication network Download PDF

Info

Publication number
WO2000018069A1
WO2000018069A1 PCT/EP1999/006955 EP9906955W WO0018069A1 WO 2000018069 A1 WO2000018069 A1 WO 2000018069A1 EP 9906955 W EP9906955 W EP 9906955W WO 0018069 A1 WO0018069 A1 WO 0018069A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
managing
protocol
data
user
Prior art date
Application number
PCT/EP1999/006955
Other languages
French (fr)
Inventor
Chris Shepherd
Original Assignee
Nokia Networks Oy
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 Nokia Networks Oy filed Critical Nokia Networks Oy
Priority to AU60858/99A priority Critical patent/AU6085899A/en
Publication of WO2000018069A1 publication Critical patent/WO2000018069A1/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/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/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
    • 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/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
    • 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/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • 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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • the invention relates to a process and a system for managing at least one network element in a telecommunication network in which a node manager exchanges data with a selected network element via a data connection, for example a LAN connection, using a standard data transmission protocol, for example the Ethernet Q 3 protocol, for conveying the management data.
  • a data connection for example a LAN connection
  • a standard data transmission protocol for example the Ethernet Q 3 protocol
  • the node management unit is used as a separate unit which communicates respectively with one of the various network elements.
  • Network element and the active node management unit usually takes place according to the LAN standard using the Ethernet protocol, mainly the Q 3 protocol.
  • the connection between the node management unit and the respective network element is realised by means of conventional connection techniques (routing) on the Q 3 protocol. From the point of view of marketing, in a telecommunications system the network element and the node management unit are sold as separate devices. This is not effective and is complicated from the point of view of maintenance.
  • node management unit is integrated into the selected network element and a user PC in a remote location is provided for addressing the network element via its at least one specific Internet protocol address (home page) , of the http Internet protocol, and for downloading the node management software to the user PC via the data connection.
  • a separate design unit for the node management software can be avoided.
  • the node management software is embedded in the special network element which has to be managed or in which the node management software has to be updated to the latest state.
  • a standard user PC addresses the respective network element via its address on the Internet protocol (home page) in order to commence the data exchange session.
  • the subsequent data exchange leads to the node manager application being downloaded from the network element to the user PC.
  • the data connection can be established as a standard data connection, for example an Ethernet protocol data connection. Because each network element comprises at least one separate home page, the standard user PC can be used to establish the connection to each of the network elements.
  • the node management software is in the form of a JAVA applet. This results in a platform-independent operation because JAVA applets are able to run on a multitude of different PCs.
  • IP addresses home pages
  • This embodiment is mainly intended for network elements which are organised according to an information model with a plural number of managed object classes.
  • ISDN ports or POTS ports are examples of such managed object classes.
  • Each of the managed object classes comprises a number of stages with various ascribed values corresponding to different physical areas.
  • "alarm notification” is a specific managed object class. Stages of this managed object class are always generated in the network element whenever an alarm or an error condition occurs. Using the conventional Q 3 protocol, the object is then sent to the node manager where it is deciphered and where some subsequent action is carried out. For example, usually the alarm information is displayed and written to a database. If the managed object class "alarm notification" is then again processed as a JAVA applet, the instruction as to how the alarm is to be handled on the side of the node manager, is located entirely within the alarm itself. In this way the alarm can display itself and write itself into the database.
  • Fig. 1 shows the design of a telecommunications network according to the present invention
  • Fig. 2 shows the design of a telecommunications network according to the state of the art
  • Fig. 3 is an explanatory diagram explaining the stepped function of the design according to Fig. 1;
  • Fig. 4 is a further explanatory diagram explaining the design according to Fig. 1.
  • Fig. 1 shows a plural number of network elements (NE) each of which comprises its own address on the Internet protocol (home page) .
  • Each network element has its own embedded node management software - referred to as "node manager" .
  • a standard user PC is provided which is configured in such a way that it can be connected with the respective PC of the network elements (NE) . Data traffic between the network elements (NE) and the user PC takes place according to the usual Q 3 protocol.
  • step 1 the user PC contacts the respective network element via its address on the Internet protocol (home page) (step 1) .
  • step 2) the node management software is downloaded from the network element (NE) to the user PC.
  • the http connection is interrupted and the Q 3 protocol connection is established between the network element and the user PC (step 3) .
  • step 3) the subsequent data exchange is used to download the node manager application from the network element to the user PC via the Q 3 data transmission protocol.
  • updating of the node manager takes place according to the conventional technique (step 4) .
  • step 5 the Q 3 data exchange session is terminated and the connection is closed.
  • Fig. 4 shows some characteristic features for further explanation of the embodiment according to Fig. 1.
  • the network element (NE) comprises the node manager as embedded software which is executable on the user PC and downloadable to said user PC (as described) , via the http Internet protocol according to the www home page.
  • the node manager application is running as a JAVA applet (Fig. 4b) which can be downloaded either onto a spatially remote PC or onto a work station.
  • each network element E comprises a structure in the form of a Q 3 management information tree with a plural number of different objects to be managed.
  • Each of the managed objects has its own home page (IP address) and can therefore run as a separate JAVA applet.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • Computer And Data Communications (AREA)
  • Small-Scale Networks (AREA)

Abstract

The invention relates to a process for managing a network element in a telecommunication network in which a node manager exchanges data with a selected network element via a data connection, e.g. a LAN connection, using a conventional data transmission protocol, for example the Q3 protocol, for conveying the management data. To simplify operation and reduce the costs of one or several network elements, it is provided for a respective network element to which at least one specific IP address (home page) is allocated, to be addressed by a user PC via the http Internet protocol, and for the node management software to be downloaded from the network element to the user PC via the data connection.

Description

Process and device for managing at least one network element in a telecommunication network
The invention relates to a process and a system for managing at least one network element in a telecommunication network in which a node manager exchanges data with a selected network element via a data connection, for example a LAN connection, using a standard data transmission protocol, for example the Ethernet Q3 protocol, for conveying the management data.
In line with the present conventional technology used in- house by the applicant (Fig. 2), the node management unit is used as a separate unit which communicates respectively with one of the various network elements.
Communication between the network element and the active node management unit usually takes place according to the LAN standard using the Ethernet protocol, mainly the Q3 protocol. The connection between the node management unit and the respective network element is realised by means of conventional connection techniques (routing) on the Q3 protocol. From the point of view of marketing, in a telecommunications system the network element and the node management unit are sold as separate devices. This is not effective and is complicated from the point of view of maintenance.
It is the object of the present invention to simplify the operation and to reduce the costs of one or several network elements. This object is met by a process where a respective network element to which at least one specific IP address (home page) has been allocated, is addressed via a user PC via the http Internet protocol, with the node management software being downloaded via the data connection, from the network element to the user PC.
This object is also met by a system where the node management unit is integrated into the selected network element and a user PC in a remote location is provided for addressing the network element via its at least one specific Internet protocol address (home page) , of the http Internet protocol, and for downloading the node management software to the user PC via the data connection.
According to the solution according to the invention, a separate design unit for the node management software can be avoided. Instead, the node management software is embedded in the special network element which has to be managed or in which the node management software has to be updated to the latest state. To this effect, a standard user PC addresses the respective network element via its address on the Internet protocol (home page) in order to commence the data exchange session. The subsequent data exchange leads to the node manager application being downloaded from the network element to the user PC. The data connection can be established as a standard data connection, for example an Ethernet protocol data connection. Because each network element comprises at least one separate home page, the standard user PC can be used to establish the connection to each of the network elements.
In a preferred embodiment of the invention, the node management software is in the form of a JAVA applet. This results in a platform-independent operation because JAVA applets are able to run on a multitude of different PCs.
In another preferred embodiment of the invention, different IP addresses (home pages) are provided for a network element; with each of these addresses corresponding to a different managed object. This embodiment is mainly intended for network elements which are organised according to an information model with a plural number of managed object classes. ISDN ports or POTS ports are examples of such managed object classes. Each of the managed object classes comprises a number of stages with various ascribed values corresponding to different physical areas.
In a further preferred embodiment of the invention, "alarm notification" is a specific managed object class. Stages of this managed object class are always generated in the network element whenever an alarm or an error condition occurs. Using the conventional Q3 protocol, the object is then sent to the node manager where it is deciphered and where some subsequent action is carried out. For example, usually the alarm information is displayed and written to a database. If the managed object class "alarm notification" is then again processed as a JAVA applet, the instruction as to how the alarm is to be handled on the side of the node manager, is located entirely within the alarm itself. In this way the alarm can display itself and write itself into the database.
Below, the invention is described by means of an explanatory embodiment, with the following drawings:
Fig. 1 shows the design of a telecommunications network according to the present invention; Fig. 2 shows the design of a telecommunications network according to the state of the art;
Fig. 3 is an explanatory diagram explaining the stepped function of the design according to Fig. 1;
Fig. 4 is a further explanatory diagram explaining the design according to Fig. 1.
Fig. 1 shows a plural number of network elements (NE) each of which comprises its own address on the Internet protocol (home page) . Each network element has its own embedded node management software - referred to as "node manager" . A standard user PC is provided which is configured in such a way that it can be connected with the respective PC of the network elements (NE) . Data traffic between the network elements (NE) and the user PC takes place according to the usual Q3 protocol.
The function is explained by means of Fig. 3:
If it becomes necessary for the node management software to be updated to the latest state, the user PC contacts the respective network element via its address on the Internet protocol (home page) (step 1) . In the next step (step 2) the node management software is downloaded from the network element (NE) to the user PC. After this, the http connection is interrupted and the Q3 protocol connection is established between the network element and the user PC (step 3) . After commencing the session, the subsequent data exchange is used to download the node manager application from the network element to the user PC via the Q3 data transmission protocol. After this step, updating of the node manager takes place according to the conventional technique (step 4) . As a last step (step 5) the Q3 data exchange session is terminated and the connection is closed.
Fig. 4 shows some characteristic features for further explanation of the embodiment according to Fig. 1. The network element (NE) comprises the node manager as embedded software which is executable on the user PC and downloadable to said user PC (as described) , via the http Internet protocol according to the www home page.
In the exemplary embodiment the node manager application is running as a JAVA applet (Fig. 4b) which can be downloaded either onto a spatially remote PC or onto a work station. As is also shown in Fig. 4, each network element E comprises a structure in the form of a Q3 management information tree with a plural number of different objects to be managed. Each of the managed objects has its own home page (IP address) and can therefore run as a separate JAVA applet.

Claims

A process for managing at least one network element (NE) in a telecommunication network in which a node manager exchanges data with a certain network element via a data connection, for example a LAN connection, using a standard data transmission protocol, for example the Q3 protocol, for conveying the management data, c h a r a c t e r i s e d i n t h a t a network element to which at least one specific Internet protocol address (home page) has been allocated, is respectively addressed via a user PC via the http Internet protocol, and that the software for managing the node is downloaded from the network element to the user PC via the data connection.
A process for managing at least one network element (NE) in a telecommunication network according to claim 1, c h a r a c t e r i s e d i n t h a t the node management software is in the form of a JAVA applet.
A process for managing at least one network element (NE) in a telecommunication network according to claim 1, c h a r a c t e r i s e d i n t h a t the data connection for downloading the node management software uses the http/IP protocol.
A process for managing at least one network element (NE) in a telecommunication network according to one of claims 1 to 3, c h a r a c t e r i s e d i n t h a t various different IP addresses are provided for each individual network element; with each of these addresses corresponding to different managed objects .
A process for managing at least one network element (NE) in a telecommunication network according to claim 4, c h a r a c t e r i s e d i n t h a t for each managed object class a different JAVA applet is provided.
A process for managing at least one network element (NE) in a telecommunication network according to claim 5, c h a r a c t e r i s e d i n t h a t the managed object class provides for "alarm notification" .
A system for managing at least one network element (NE) in a telecommunication network comprising a node management unit which interacts with a selected network element via a data connection, e.g. a LAN connection, using a standard data transmission protocol, e.g. the Q3 protocol for conveying management data, c h a r a c t e r i s e d i n t h a t the node management unit is integrated in the selected network element and that a user PC in a remote location is provided for addressing the network element via its specific Internet protocol (IP) address (home page) , of which there is at least one, of the http Internet protocol, and for downloading the node management software to the user PC via the data connection. A system according to claim 7, c h a r a c t e r i s e d i n t h a t for each network element a plural number of different IP addresses is provided, with each of these addresses belonging to an individual managed object.
PCT/EP1999/006955 1998-09-22 1999-09-21 Process and device for managing at least one network element in a telecommunication network WO2000018069A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU60858/99A AU6085899A (en) 1998-09-22 1999-09-21 Process and device for managing at least one network element in a telecommunication network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE19843324.7 1998-09-22
DE19843324A DE19843324C2 (en) 1998-09-22 1998-09-22 Method and device for managing at least one network element in a telecommunications network

Publications (1)

Publication Number Publication Date
WO2000018069A1 true WO2000018069A1 (en) 2000-03-30

Family

ID=7881760

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP1999/006955 WO2000018069A1 (en) 1998-09-22 1999-09-21 Process and device for managing at least one network element in a telecommunication network

Country Status (3)

Country Link
AU (1) AU6085899A (en)
DE (1) DE19843324C2 (en)
WO (1) WO2000018069A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1265417A3 (en) * 2001-06-05 2005-01-12 Hewlett-Packard Company Device management system and method
CN1317849C (en) * 2002-03-30 2007-05-23 中兴通讯股份有限公司 Network management system and method
EP2522334A1 (en) 2011-05-10 2012-11-14 Cutech S.R.L. Cosmetic compositions comprising diterpenoic acids, e.g. gibberellic acids

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1168160A1 (en) 2000-06-19 2002-01-02 Hewlett-Packard Company, A Delaware Corporation Process for automatically displaying graphical objects such as buttons in a web page
DE60039975D1 (en) 2000-06-19 2008-10-02 Hewlett Packard Co Method for managing units of an intranet network via the WEB

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0812091A2 (en) * 1996-06-04 1997-12-10 Sony Corporation Method and system for controlling the communication of electronic equipment

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5005122A (en) * 1987-09-08 1991-04-02 Digital Equipment Corporation Arrangement with cooperating management server node and network service node
WO1996024231A1 (en) * 1995-01-30 1996-08-08 Telefonaktiebolaget Lm Ericsson (Publ) Flexible downloading of software

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0812091A2 (en) * 1996-06-04 1997-12-10 Sony Corporation Method and system for controlling the communication of electronic equipment

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"DEVICE DRIVERS VIA THE ACCESS BUS", IBM TECHNICAL DISCLOSURE BULLETIN,US,IBM CORP. NEW YORK, vol. 39, no. 1, pages 135, XP000556349, ISSN: 0018-8689 *
BJERRING L H ET AL: "EXPERIENCES IN DEVELOPING MULTI-TECHNOLOGY TMN SYSTEMS", IEEE NETWORK OPERATIONS AND MANAGEMENT SYMPOSIUM,US,NEW YORK, NY: IEEE, vol. CONF. 10, pages 445-454, XP000799515, ISBN: 0-7803-4352-2 *
CARLSUND P ET AL: "AN ELEMENT MANAGER BASED ON WEB TECHNOLOGY", ERICSSON REVIEW,SE,ERICSSON. STOCKHOLM, no. 1, pages 46-51, XP000734509, ISSN: 0014-0171 *
DASSOW H: "REALIZATION OF A TMN JAVA MANAGEMENT API", IEEE NETWORK OPERATIONS AND MANAGEMENT SYMPOSIUM,US,NEW YORK, NY: IEEE, vol. CONF. 10, pages 412-421, XP000799512, ISBN: 0-7803-4352-2 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1265417A3 (en) * 2001-06-05 2005-01-12 Hewlett-Packard Company Device management system and method
CN1317849C (en) * 2002-03-30 2007-05-23 中兴通讯股份有限公司 Network management system and method
EP2522334A1 (en) 2011-05-10 2012-11-14 Cutech S.R.L. Cosmetic compositions comprising diterpenoic acids, e.g. gibberellic acids
WO2012152615A1 (en) 2011-05-10 2012-11-15 Cutech Srl. Cosmetic compositions comprising diterpenoic acids, e.g. gibberellic acids

Also Published As

Publication number Publication date
DE19843324A1 (en) 2000-03-23
DE19843324C2 (en) 2000-10-05
AU6085899A (en) 2000-04-10

Similar Documents

Publication Publication Date Title
US5546379A (en) Bandwidth-on-demand remote office network apparatus and method
US6684241B1 (en) Apparatus and method of configuring a network device
US8289873B2 (en) Method and apparatus providing automatic connection announcement from a modular network device to a network management point
US6463528B1 (en) Method and apparatus for simplifying the configuration of several models of customer premise equipment
CN100505749C (en) Router and SIP server
US6182045B1 (en) Universal access to audio maintenance for IVR systems using internet technology
EP3382988B1 (en) Method for self-provisioning of cable modems and multimedia terminal adapters
EP1346541B1 (en) Method and system for communications with remote embedded applications
US20050105508A1 (en) System for management of Internet telephony equipment deployed behind firewalls
US6618476B1 (en) Line information security interface for TAPI service provider
WO2000018069A1 (en) Process and device for managing at least one network element in a telecommunication network
CN111414262B (en) Service calling method and device
CN1192642C (en) Method for updating subscriber-related data in telecommunication network
EP1479192B1 (en) Method and apparatus for managing configuration of a network
JP3781764B1 (en) Remote control system and method for communication terminal
US20060168105A1 (en) Method for updating the local management system in at least one network element of a telecommunication network
KR100487238B1 (en) How to Manage Internet Gateway Integration on the Internet
CN100336347C (en) Configuration for monitoring the state of components in a packet-switched communications network
AU4865399A (en) Hypertext transport protocol interface in an intelligent network node
US6760427B2 (en) Computer telephony (CT) network serving multiple telephone switches
US8065400B1 (en) Method for controlling devices that are arranged in a communications network
KR100263386B1 (en) Method of parsing transaction language 1 in a regional monitor and control system
KR101083865B1 (en) System and method for network management using a mib table
JP3177674B2 (en) Module fault concealment method
WO2000056081A1 (en) Providing supplementary services in an expandable telecommunications system

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

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)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase