WO2004002172A1 - Procede et element de reseau pour la gestion de ressources d'un element de reseau - Google Patents

Procede et element de reseau pour la gestion de ressources d'un element de reseau Download PDF

Info

Publication number
WO2004002172A1
WO2004002172A1 PCT/DE2003/001819 DE0301819W WO2004002172A1 WO 2004002172 A1 WO2004002172 A1 WO 2004002172A1 DE 0301819 W DE0301819 W DE 0301819W WO 2004002172 A1 WO2004002172 A1 WO 2004002172A1
Authority
WO
WIPO (PCT)
Prior art keywords
database
central
network element
mdb
decentralized
Prior art date
Application number
PCT/DE2003/001819
Other languages
German (de)
English (en)
Inventor
Wolfgang Krille
Original Assignee
Siemens Aktiengesellschaft
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 Siemens Aktiengesellschaft filed Critical Siemens Aktiengesellschaft
Priority to EP03760550A priority Critical patent/EP1514434A1/fr
Publication of WO2004002172A1 publication Critical patent/WO2004002172A1/fr

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
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0062—Provisions for network management
    • 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/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
    • 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/04—Network management architectures or arrangements
    • H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality

Definitions

  • a management agent is implemented in the network elements, which processes the commands of the central network management system (e.g. reading and setting configuration data or administrative information) and which independently monitors the current operating status of the respective network element and, if necessary, messages about changes in status - for example by means of Alarms - transmitted to the central network management system.
  • the agent usually configured as a software application in the respective network element provides the central network management system with an abstract model of the physical and logical resources of the network element - also referred to as MIB or Management Information Base.
  • the central network management system can access the physical and logical resources of the respective network element or the administrative information representing these resources - also referred to as MO or "Managed Objects *" - via a special management protocol of the network element.
  • the network elements arranged in current communication networks generally represent distributed software systems with several modules. The functions of each module are monitored and controlled by a separate processor. The corresponding physical and logical resources (managed objects) of the network element are distributed among the modules of the network element - also referred to as sub-resources.
  • the management agent of the respective network element In order to enable central administration of the resources or partial resources provided by the network elements, the management agent of the respective network element must execute the commands transmitted by the central network management system and to execute the management agent-specific monitoring functions on the physical and logical components distributed in the system Access resources or partial resources via the interface system (problem 1).
  • Another problem with the central management of the resources or sub-resources provided by the network elements is that when executing configuration or Administrative actions created by the central network management system represent administrative information which represent the configuration or the state of the managed objects or physical and logical resources distributed in the respective network element. This administrative information must be stored semi-permanently in the central network element so that the network element can resume its functions after a restart or after a module change without external configuration measures.
  • the administration and semi-permanent storage of the configuration data or administration information is generally carried out on a central assembly of the respective network element (e.g. on a monitoring assembly), so that the administration information for further central system functions such as e.g. B. Backup, restore and audits are available (problem 2).
  • the management agent and a correspondingly assigned central database are implemented on a central assembly of the network element.
  • the above-mentioned problem 2 can be solved since the management agent and the central database are assigned to a control unit or a processor and are implemented on the same central assembly.
  • the above problem 1 is solved by introducing system interfaces via which the connection between the management agent (or other functionally similar, central software subsystems) and the software subsystems distributed in the network element is realized, the
  • Subsystems are responsible for the control or monitoring of the physical and logical resources of the network element (e.g. device driver).
  • the central implementation of the management agent has the disadvantage of the dependency between the central agent implementation (the management agent represents the managed objects or partial resources or resources of the network element) and changes in the partial resources by, for example, changing the configuration of the network element. Extensions or changes to the configuration of the network element (eg by inserting a new module type) are only possible if the centrally implemented management agent, the central database and the respective system interfaces are adapted accordingly. The introduction of a new module or a new module type into the network element is therefore disadvantageously generally associated with an update or an upgrade of the software implemented in the central module, which increases the technical and economic outlay for the implementation and for configuring the software.
  • Decentralized implementation of the management agent in the network element :
  • the management agent is implemented distributed over the modules of the network element.
  • the associated database is implemented on a central assembly of the network element.
  • the decentralized agent implementation implements the sub-agent components where the associated sub-resources or managed objects of the network element are also located.
  • new sub-resources can be included in the network element, which have no effects on the centrally implemented management agents - also known as master agents.
  • the master agents only have to forward the management commands to the sub-agents, which means that the above-mentioned disadvantage of central implementation, i.e. the disadvantageous dependency between central agent implementation and changes in partial resources or managed objects is avoided.
  • the forwarding function of the master agent (problem 1) that is now required is implemented here on the basis of identifiers or on the basis of identification information in the application layer (application layer) of the management protocol.
  • management protocols are "SISA-QD2 * and" SNMP ', with “SISA-QD2 * the FG and FE number and” SNMP "the respective object identifier as identification information for the application layer Will be provided.
  • the forwarding function of the master agent can be expanded dynamically with the help of the management protocols and the respective identification information of the application layer.
  • the application layer protocols are transported to the decentralized subagent and processed there, which usually results in a close link to the management protocol.
  • the change of the management protocol or the support of additional management protocols can only be realized with increased effort.
  • a database consisting of a collection of subagent-specific databases (files) can only support central system functions such as backup, restore and audis with difficulty.
  • the invention is therefore based on the object of enabling simple, centrally controlled management of resources or partial resources arranged in network elements, in particular the problems mentioned above being avoided.
  • the object is achieved on the basis of a method and a network element according to the features of the preamble of claims 1 and 19 by their characterizing features.
  • the resources comprise at least one partial resource provided in the network element.
  • the essential aspect of the method according to the invention is that at least one central database that manages the resources of the network element and at least one decentralized database that manages the at least one partial resource is provided in the network element.
  • the central database is logically designed in the form of a tree structure such that the at least one decentralized database is simultaneously a component of the tree structure. Structure of the higher-level central database forms, the distribution of the partial resources in the network element being represented by the tree structure.
  • the decentralized database of the at least one partial resource is accessed via the tree structure of the higher-level central database.
  • the main advantage of the method according to the invention is that two functions are implemented by using the central database according to the invention.
  • management commands are forwarded in the network element to, for example, subagents representing the partial resources, and additional administrative information is stored centrally in a central database - also referred to as the master database.
  • the central database according to the invention advantageously enables the use of a uniform interface (database synchronization) for the communication of central and decentralized administration agents or software objects.
  • the management of data or information using databases which are in the form of a
  • Tree structure is an easy to solve and supported by standard components programming task, so that the inventive method can be implemented with minimal technical and economic effort. This further reduces the effort in general for the maintenance and further development of applications coordinated with the central database according to the invention, as well as the effort for introducing new modules or module types, for changing the management protocol or for implementing further management protocols ,
  • the at least one decentralized database simultaneously forms part of the tree structure of the superordinate central database (MDB, SDB ⁇ 1 ... 3) in the form of a
  • This advantageous further development makes a particularly simple definition a decentralized database as a subset of the central database.
  • the method according to the invention in particular the synchronization of central and decentralized databases, can be implemented in a particularly simple and thus inexpensive manner.
  • FIG. 3 shows an illustration of the data structure (tree structure) of the database arranged centrally in the network element.
  • FIG. 4 shows an abstract model of the physical and logical resources provided by the network element.
  • FIG. 1 shows in a block diagram an application scenario implementing the method according to the invention, consisting of an in a communication network KN - e.g. a subscriber line network or “access network *” arranged network element NE, through which subscriber lines TA or subscriber TLN are connected to a switching device VE via the standardized switching protocol V5.2.
  • a number of different types of assemblies BG1 ... 3 are arranged in the network element NE, the first assembly BG1 for connecting analog subscribers - "Pots Line Card * - the second assembly for connecting digital subscribers -" ISDN Line Card * - and the third Assembly as LAN
  • Each of the three modules BG1 ... 3 thus realizes a part of the Network element NE in total provided resources POTS, ISDN, El, whereby for the management of the respective partial resources POTS, ISDN, El of each assembly BG1 ... 3 a decentralized database SDB1 ... 3 - also referred to as "slave database *" assigned.
  • a central module ZBG is also arranged in the network element NE, which is assigned a central database MDB which manages the entire resources of the network element NE and is designed in the form of a tree structure.
  • a central agent A which controls the management of the resources of the network element NE, is assigned to the central database MDB - also referred to as the “master database *”.
  • the decentralized data bases SDB1 ... 3 are stored on the respective assembly BG1 ... 3.
  • the slave databases SDBl ... 3 or the information stored therein are also stored (for example as a copy) in the central assembly ZBG, the slave databases or the copies of these slave databases - in FIG. 1 as SDB , 1 ... 3 marked - form part of the tree structure of the central master database MDB, ie each form a subtree of the master database MDB.
  • the management model for the administration of V5.2 network elements NE is defined in the ETSI standards ITS 300-377-1 and ITS 300-376-1, whereby an implementation variant of the management model in the form of a block diagram using the 2 is shown in the nomenclature used in the standards mentioned.
  • the model shown in FIG. 2 forms the basis for the internal data model of the application scenario shown in FIG. 1 and thus determines the data structure of the central master database MDB arranged in the network element NE.
  • the modifications result from the described structure of the network element - equipment hierarchy - which is used as the basic structure for the internal data model.
  • the modified data model is shown in FIG. 3.
  • the V5 protocol processing is implemented on the central assembly ZBG, on which the master database MDB is also implemented.
  • 3 shows the three module types arranged in the network element NE - El Line Unit, Pots Line Card and ISDN Line Card -, the modules - also shown in FIG. 3 as PluglnUnit - in slotl ... 3 plug devices in one Network element NE provided assembly bracket SHELF are arranged.
  • the agent A arranged in the central assembly ZBG of the network element NE provides the central administration device NMS with the abstract model of the physical and logical resources of the network element NE shown in FIG.
  • This abstract model is also called MIB or Management Information Base.
  • the central administration device NMS can access the physical and logical resources or managed objects of the network element using a management protocol.
  • the "SNMP * - Simple Network Management Protocol - assumed - illustrated by a dashed double arrow - is assumed as an external management protocol - but other management protocols can also be used.
  • FIG. 4 shows the basic structure of a V5 MIB module in a block diagram.
  • the managed objects of the management model of the above-mentioned ETSI standards can also be found in this block diagram. However, their arrangement corresponds to the registration hierarchy for SNMP.
  • the managed objects for the equipment are also managed by a standard MIB module (also referred to as an entity MIB).
  • the basic component of the method according to the invention is the central database MDB, which is arranged in the central assembly ZBG and designed in the form of a tree structure and has the following properties:
  • the data records or management information (managed objects) stored in the central database MDB are managed in one or more tree structures. Each data record is uniquely identified by a key.
  • 25 represents a managed physical or logical resource (managed objects) or the summary of similar resources.
  • the central database MDB is advantageously designed as a type-neutral database.
  • Type neutrality is achieved in that only references to the respective data records or administrative information that are only stored in external memory blocks are managed within the central database MDB. Only the software users
  • Goods objects such as agents know the structure of the data records; if necessary, the. can also be created using a simple formal description notation for data records Access to individual elements of a data record are supported by database functions.
  • the central database or master database MDB is assigned at least one update function, which is designed in such a way that when one of the managed objects POTS, ISDN, El arranged in the central tree structure is changed or when the the management object MO representing the managed object, the respective corresponding slave database SDB1 ... 3 or the corresponding management information MO stored in the slave database SDBl ... 3 are updated with regard to the changes.
  • at least one update function can be assigned to the slave databases SDB1 ... 3, which is designed in such a way that when one of the managed objects POTS, ISDN stored in the slave databases SDB1 ... 3 is changed , El, or in the event of a change in the management information representing the managed object, the master database MDB or the corresponding administration information stored in the master database MDB are updated with regard to the changes.
  • the update functions assigned to the master database MDB and / or the slave databases SDBl ... 3 provide, for example, functions for registration and for change notification, that is to say local software objects, ie locally on the respective module ZBG, BG1 ... 3 arranged functions and / or processes such as sub-agents can register for certain data records or administrative information of the respective database MDB, SDBl ... 3 and receive a message indicating the change every time the registered data records are changed the central database MDB or from the respective slave database SDB1 ... 3. Depending on the message transmitted, further functions are carried out by the respective software objects.
  • the central database MDB continues to provide functions for the synchronization of slave databases SDB1 ...
  • a slave database SDB1 ... 3 can be registered for a specific subtree of the master database MDB. If there are changes within the subtree of the master database MDB, the respective slave database SDB1 ... 3 is updated via the synchronization function - also referred to as “slave synchronization *. Conversely, a change in the slave database SDB1 ... 3 within the registered subtree leads to an update of the data record in the master database MDB - also called master synchronization.
  • the slave databases SDB1 ... 3 can also be arranged hierarchically on several levels, i.e. for one
  • Subtree of a slave database can register another slave database.
  • a master-slave relationship is again established between these two databases.
  • the central database MDB supports two data record references per data record key: a "temporary * and a" committed * reference to support type "TRY * and" Rollback * functions.
  • the database provides special "Remote Access * functions.
  • the following method for decentralized agent implementation in the network element NE is defined with a database MDB configured as a basic component in accordance with the above statements:
  • the physical and logical resources of the network element NE are managed as managed objects corresponding to their container relationships in the tree structure of the master database MDB on the central module ZBG of the network element.
  • managed objects corresponding to their container relationships in the tree structure of the master database MDB on the central module ZBG of the network element.
  • the following arrangement of managed objects is shown as an example, using the nomenclature of the ETSI standards mentioned:
  • NE Network element
  • SHELF EquipmentHolder
  • Slot EquipmentHolder
  • the slave databases SDB1 ... 3 of the respective modules BG1 ... 3 register for a subtree of the master database MDB with the associated "PluginUnit * data record as a top element.
  • the slave databases of external equipment register a subtree with the associated "equipment * data record as a top element.
  • the Slave databases SDB1 ... 3 are loaded with the current data records or management information from the master database MDB. If the subtree does not yet exist in the MDB master database, i.e. the module has not yet been configured, the module (or the external equipment) generates the required data records with preset values or default data (also as an auto) -Provisioning). Since the MDB master database is type-neutral, new data record types and new subtree structures can also be created, whereby the expansion is possible at runtime.
  • the subagents arranged locally in the modules BG1 ... 3 register as local software objects for the change notification function and configure the local resources according to the data in the MDB database.
  • Commands transmitted from the central administration device NMS to the network element NE via SNMP protocol are routed to the associated data record of the master database MDB using a “key translation function * based on the object identifier values of the command telegram (reading or writing records).
  • a write or set command With a write or set command, the corresponding data record is changed in the master database MDB. This change is sent to the responsible subagent via the synchronization and change notification function.
  • Reports of changes in the state of the subagent reach the master database MDB in the opposite way and are converted to corresponding messages or telegrams by an "inverse key translation function *" - also referred to as trap or notification telegrams - and sent to the central one Administrative facility sent NMS.
  • the data or data records of the network element NE are structured in the master database MDB and can be from central system functions such as B. semi-permanent storage, backup, restore and audits can be used.
  • the central database MDB which is designed in the form of a tree structure.
  • the type neutrality the dynamic expandability of the central master database MDB and the use of an independent internal data model, the known disadvantages of the known solutions mentioned at the outset do not occur and the decoupling of functions of the central assembly ZBG and the managed objects of the decentralized becomes Assemblies BG1 ... 3 and a better decoupling of management protocol and application software (such as agent implementations achieved.
  • Another advantage is the use of a uniform interface - here the database synchronization - for the communication of central and decentralized software objects, such as for the communication between a central agent A and the decentralized ones implemented in the respective modules BG1 ... 3 agents.
  • the application scenario shown in this exemplary embodiment is not limited to the described communication of central (master) agents and decentralized (sub) agents, but can be expanded as desired and thus the otherwise common message handler subsystems of the application Replace software in whole or in part.
  • the use of the tree structure in the MDB master database generally reduces the effort required to maintain and further develop the application software, such as the maintenance of agents or subagents used in the network element. It is advantageous for communication between the master database MDB with the respective slave databases SDB1 ... 3 with each other and for communication with the respective software goods objects of the application software use the transport protocol IP (Internet Protocol) and / or UTP. This means that an “application system * can be implemented on a single personal computer or distributed over any number of personal computers.
  • IP Internet Protocol

Abstract

Selon l'invention, dans un élément de réseau (NE) se trouvent au moins une base de données centrale (MDB) gérant les ressources de l'élément de réseau et au moins une base de données décentralisée (SDB1 3) qui gère respectivement une ressource partielle (ISND, POTS, E1). La base de données centrale (MDB, SDB'1 3) est constituée logiquement sous la forme d'une structure arborescente de sorte que la ou les base(s) de données décentralisée(s) (SDB1 3) forment simultanément une partie intégrante de la structure arborescente de la base de données centrale (MDB, SDB'1 3) hiérarchiquement supérieure, la répartition des ressources partielles étant reproduite dans l'élément de réseau par la structure arborescente. Dans le cadre de la gestion des ressources, l'accès à la base de données décentralisée (SDB1 3) de la ou des ressource(s) partielle(s) se fait par l'intermédiaire de la structure arborescente de la base de données centrale (MDB, SDB'1 3). De façon avantageuse, les commandes de gestion, dans l'élément de réseau, sont transmises à des sous-agents représentant par exemple les ressources partielles, et des informations de gestion sont mémorisées de façon centralisée dans la base de données centrale.
PCT/DE2003/001819 2002-06-20 2003-06-02 Procede et element de reseau pour la gestion de ressources d'un element de reseau WO2004002172A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP03760550A EP1514434A1 (fr) 2002-06-20 2003-06-02 Procede et element de reseau pour la gestion de ressources d'un element de reseau

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE10227556.4 2002-06-20
DE10227556 2002-06-20

Publications (1)

Publication Number Publication Date
WO2004002172A1 true WO2004002172A1 (fr) 2003-12-31

Family

ID=29795834

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/DE2003/001819 WO2004002172A1 (fr) 2002-06-20 2003-06-02 Procede et element de reseau pour la gestion de ressources d'un element de reseau

Country Status (2)

Country Link
EP (1) EP1514434A1 (fr)
WO (1) WO2004002172A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7729286B2 (en) 2005-10-07 2010-06-01 Amdocs Systems Limited Method, system and apparatus for telecommunications service management
US7797425B2 (en) 2005-12-22 2010-09-14 Amdocs Systems Limited Method, system and apparatus for communications circuit design
US8082335B2 (en) 2005-11-18 2011-12-20 Amdocs Systems Limited Method and system for telecommunications network planning and management
US8380833B2 (en) 2006-02-20 2013-02-19 Amdocs Systems Limited Method of configuring devices in a telecommunications network

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1158720A2 (fr) * 2000-05-25 2001-11-28 Alcatel USA Sourcing, L.P. Systéme et méthode de gestion de noeud de réseau en utilisant des proxies par agents extensibles

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1158720A2 (fr) * 2000-05-25 2001-11-28 Alcatel USA Sourcing, L.P. Systéme et méthode de gestion de noeud de réseau en utilisant des proxies par agents extensibles

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
DANIELE M ET AL: "Agent Extensibility (AgentX) Protocol Version 1", IETF RFC 2741, January 2000 (2000-01-01), pages 1 - 91, XP002247971 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7729286B2 (en) 2005-10-07 2010-06-01 Amdocs Systems Limited Method, system and apparatus for telecommunications service management
US8082335B2 (en) 2005-11-18 2011-12-20 Amdocs Systems Limited Method and system for telecommunications network planning and management
US7797425B2 (en) 2005-12-22 2010-09-14 Amdocs Systems Limited Method, system and apparatus for communications circuit design
US8380833B2 (en) 2006-02-20 2013-02-19 Amdocs Systems Limited Method of configuring devices in a telecommunications network

Also Published As

Publication number Publication date
EP1514434A1 (fr) 2005-03-16

Similar Documents

Publication Publication Date Title
EP0525432B1 (fr) Méthode de changement des données de configuration de système dans un système de commutation de télécommunications
DE60215002T2 (de) Verfahren und system für effiziente verteilung von netzwerk-ereignisdaten
EP0825524B1 (fr) Procédé pour nommer des objets
DE69832946T2 (de) Verteiltes System und Verfahren zur Steuerung des Zugriffs auf Netzmittel und Ereignismeldungen
EP3402152B1 (fr) Gestion de certificat automatisée, en fonction de l'installation
DE4125389C1 (fr)
DE60306932T2 (de) Schnelle Datenbankreplikation
EP1040623A2 (fr) Procede de coordination de composants de reseau
DE60220375T2 (de) Spezifischer Datenregistrierungsserver in einem Bedien- und Verwaltungszentrum für ein Telekommunikationssystem
EP0807883A2 (fr) Système de communication avec moyen pour échanger des processus de logiciel
EP2198352A1 (fr) Procédé de configuration d'un ensemble destiné à protéger, à commander ou à surveiller une installation d'alimentation en énergie électrique ou de commutation électrique
EP1430369A1 (fr) Acces dynamique a des ressources d'automatisation
DE112012003778T5 (de) Computernetzwerk-Management-Tools
DE10251911B4 (de) Verfahren für das Konfigurationsmanagement und Netzwerk
EP1227616B1 (fr) Méthode, programme et arrangement pour la synchronisation d'un gestionnaire de réseau avec un agent de réseau
DE102004030781A1 (de) SCADA-System und Verfahren zum Betreiben eines solchen Systems
EP1514434A1 (fr) Procede et element de reseau pour la gestion de ressources d'un element de reseau
DE102005014775B4 (de) Verfahren, Kommunikationsanordnung und Kommunikationseinrichtung zur Steuerung des Zugriffs auf zumindest eine Kommunikationseinrichtung
EP1655974A1 (fr) Procédé et appareils d'alignement d'information entre un manager et un agent dans un réseau de gestion
EP1536328B1 (fr) Système de traitement de données avec la gestion automatisable et procédé pour la gestion automatisée d'un système de traitement de données
CH686540A5 (de) Verfahren zum Steuern und Verwalten von Netzwerkelementen.
WO1999022491A1 (fr) Dispositif de raccordement des elements reseau d'une installation de telecommunications a un reseau de gestion des telecommunications
DE10318292B4 (de) Verfahren zur Parametrierung und Projektierung von Kommunikationsnetzwerken und Kommunikationsnetzwerk zur Implementierung eines solchen Verfahrens in der Automatisierungstechnik
DE60303106T2 (de) Kommandozeilenschnittstellen Prozessor mit dynamischer Aktualisierung von Attributabhängigkeiten
DE10229879A1 (de) Datenverarbeitungssystem mit Diensten zur Bereitstellung von Funktionalitäten

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): CN US

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR

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

Ref document number: 2003760550

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2003760550

Country of ref document: EP

WWW Wipo information: withdrawn in national office

Ref document number: 2003760550

Country of ref document: EP