EP1776801A1 - Procédé de communication dans un réseau de gestion en vue de l'information sur des modifications d'attribut - Google Patents

Procédé de communication dans un réseau de gestion en vue de l'information sur des modifications d'attribut

Info

Publication number
EP1776801A1
EP1776801A1 EP05771834A EP05771834A EP1776801A1 EP 1776801 A1 EP1776801 A1 EP 1776801A1 EP 05771834 A EP05771834 A EP 05771834A EP 05771834 A EP05771834 A EP 05771834A EP 1776801 A1 EP1776801 A1 EP 1776801A1
Authority
EP
European Patent Office
Prior art keywords
network
manager
size
information
change
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.)
Withdrawn
Application number
EP05771834A
Other languages
German (de)
English (en)
Inventor
Olaf Pollakowski
Clemens Suerbaum
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Solutions and Networks GmbH and Co KG
Original Assignee
Siemens AG
Nokia Siemens Networks GmbH and Co KG
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 AG, Nokia Siemens Networks GmbH and Co KG filed Critical Siemens AG
Publication of EP1776801A1 publication Critical patent/EP1776801A1/fr
Withdrawn legal-status Critical Current

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

Definitions

  • the invention relates to a method for communication in a management network of a telecommunication network, in which a manager and an agent communicate with one another using a network resource of the telecommunication network as object model modeling object model. Furthermore, the invention relates to a manager and an agent for carrying out the method.
  • TMN Telecommunications Management Network
  • management layers for the management of a communication system - such as a mobile radio communication system - with each layer except the top and bottom Layer a double function, namely a manager and an agent function be ⁇ sits.
  • each level except the lowest carries out a manager function for the underlying level.
  • each layer except the top has an agent function for the next higher layer.
  • Managers start network monitoring and control operations by sending so-called “requests” which are executed by agents, and receive corresponding acknowledgments, so-called “responses”, from the agents.
  • Devices or elements of the telecommunication network also referred to as resources of the telecommunication network, which perform the role of an agent in a TMN hierarchy, detect relevant events, so-called “events”, such as alarms, generate corresponding messages, so-called “Notifications” and transmit them in the form of event messages, so-called called “event reports” to managers to enable efficient network management.
  • the network management may include but not limited to fault management and / or configuration management and / or security management and / or accounting management and / or performance management. Performance Management).
  • the network management is intended to provide suitable mechanisms for distributing and managing information, so that a comprehensive picture of the network status is available, if required, and the individual resources of the telecommunications network can be efficiently monitored and configured.
  • the manager-agent communication takes place via so-called management interfaces or manager-agent interfaces, which in an object-oriented environment are communicated on the basis of a communication protocol, such as e.g. Common Management Information Protocol (CMIP) according to ITU-T X.711 or CORBA (Common Object Control Broker Architecture), and are gekennzeich ⁇ net by an object model.
  • CMIP Common Management Information Protocol
  • Object models also referred to as information models, are used to model resources of the telecommunications network, these resources being classified into object classes during the modeling.
  • Object classes are u.a. defined by certain operations, attributes, messages which can be sent and the object class-specific behavior, which is e.g. describes which state an object should assume in certain situations and for what purpose certain attributes are to be used.
  • Such interfaces exist, for example, between the network element management level and the network element level.
  • An example of network facilities of this manager-agent interface is the Operation and Maintenance Center (OMC) the side of the network element management level, and on the side of the network element level facilities such as base stations of the base station system (BSS: Base Station System) of a GSM mobile network, or base stations of other communication networks, such as NodeB ⁇ s UMTS mobile network (UMTS: Universal Mobile Telecommunication System), or radio access points of a WLAN system (WLAN: Wi-Fi Local Area Network), for example, according to one of the IEEE 802.11 standards.
  • OMC Operation and Maintenance Center
  • Management interfaces or manager-agent interfaces also exist, on the one hand, between the network management level and, on the other hand, the network element management level.
  • An example of network devices for this manager-agent interface are the network management centers (NMC: Network Management Center) on the side of the network management level and the operation and maintenance centers (OMC: Operation and Maintenance Center) on the side of the network management level Network element management level eg in said GSM or another mobile or telecommunications network...,.
  • the invention has for its object to provide an efficient method for operating a management network of the type mentioned. Furthermore, a suitable manager and a similar agent are to be presented for carrying out the method.
  • a communication between a manager and an agent takes place using an object model which contains network resources of the telecommunication network.
  • cation network modeled as object classes.
  • the object classes are defined, at least inter alia, by specific operations, attributes and dispatchable messages.
  • At least one object class is used with an attribute describing several sizes.
  • the agent sends a message to the manager for information about a change in a value of at least one of the quantities. This message includes information about which size or sizes are affected by the change and the changed value (s) of the change (s) affected by the change.
  • An object model is used for communication between a manager and an agent, wherein an object model is characterized by the object classes which it uses, and by the relationships of the object classes to each other, e.g.
  • the object model used according to the invention is designed in such a way that at least one object class has an attribute which describes ".sup.size.sup.that means that the attribute in .alpha
  • it may contain a plurality of values, corresponding to the number of variables.
  • the plurality of variables may be manufacturer-specific variables, which may differ from agent to agent with which the manager communicates
  • the at least one object class can have one or more such attributes, which describe a plurality of variables, Furthermore, it is possible for one, a plurality or all object classes of the object model to have such attributes which describe a plurality of variables.
  • the agent sends a message to the manager informing him of the change.
  • the agent may have been informed of the change, for example, by a subordinate agent.
  • the to the manager sent message can be deduced which size or sizes are affected by the change. This can be achieved, for example, by including identification information of the variables or variables affected by the change at a specific position or in a specific context in the message.
  • the method according to the invention can be applied to the communication between a manager and a plurality of agents, between an agent and a plurality of managers, and also between a plurality of managers and agents.
  • the message comprises information which allows the manager to interpret the at least one changed size.
  • the information thus represents metadata which serve to describe the representation of the variables described.
  • This information may be e.g. to handle a pointer to information necessary for interpretation by the manager, such as a pointer to a book or web page.
  • This information may be quantities described by one or more attributes of the at least one object class.
  • the information may be e.g. by a language used for the at least one changed size and / or by the construction of the at least one changed size, such as e.g. to act an XML schema.
  • the message comprises the one or more values of the unchanged size or sizes.
  • the message contains the current values for all sizes described by the attribute. Additionally or alternatively, it is possible that the message comprises the old values or values of the at least one changed size, ie the values of these quantities before the change.
  • the manager according to the invention has means for communicating with an agent using an object model which models network resources of the telecommunication network as object classes, wherein according to the object model the object classes are defined by specific operations, attributes and messages and at least an object class has an attribute which describes several variables.
  • the agent comprises means for receiving and processing a message from the agent for information about a change in a value of at least one size, wherein the message comprises: information about which size or variables are affected by the change, and the one or more changed values of the size or quantities affected by the change.
  • the inventive agent for a management network of a telecommunications network has means for communicating with a manager using an object model which models network resources of the telecommunication network as object classes, wherein according to the object model the object classes are defined by specific operations, attributes and messages to be transmitted and at least one object class has an attribute describing multiple sizes. It further comprises means for creating and sending a message to the manager for information about a change in a value of at least one size, the message comprising: information about which size or sizes are affected by the change, and the or the changed values of the size or quantities affected by the change.
  • Figure 1 a section of a management network of a mobile communication system.
  • the management network of a mobile communication system shown in FIG. 1 consists of the three levels NM-LEVEL (NM: Network Manager), NEM-LEVEL (NEM: Network Element Manager) and NE-LEVEL (NE: Network Element).
  • NM-LEVEL Network Manager
  • NEM-LEVEL Network Element Manager
  • NE-LEVEL Network Element
  • Part of the highest level NM-LEVEL is the network management center NMC, which is connected to the two operating and maintenance centers OMCl and OMC2 of the middle level NEM-LEVEL.
  • the two operation and maintenance centers OMC1 and OMC2 act as agents to the network management center NMC.
  • the operation and maintenance center OMC1 is connected to the three network elements NE, NE12 and NE13 of the lowest level NE-LEVEL, while the operating and maintenance centers OMC2 Maintenance center OMC2 is connected to the two network elements NE21 and NE22.
  • the network elements NEW, NE12, NE13, NE21 and NE22 may be e.g. to base stations or facilities, to control base stations.
  • the invention will be described below on the basis of the communication between the network management center NMC and the operation and maintenance centers OMC1 and OMC2.
  • the network resources of the mobile communication system such as: The network elements NEW, NE12, NE13, NE21 and NE22, are divided into object classes as part of network management.
  • 3GPP has defined an object model for communication via the interface between the network management center NMC and the operation and maintenance centers OMC1 and OMC2, which comprises, for example, the object class ManagedElement and ManagedFunction, which are base object classes with general attributes is.
  • Further object classes are eg gsmCell, utranCell, btsSiteManager, bssFunction, mscServerFunction, rncFunction, hlrFunction, vlrFunction, sgsnFunction and ggsnFunction.
  • Each object class is defined by certain operations, i. via commands which can be sent to network resources of this object class by a manager, as well as via certain attributes, i. Properties which can be queried by a manager and possibly edited, via specific messages which can be sent by network resources of the respective object class in the context of network management, as well as via the description of the meaning and behavior of the object class and their constituents.
  • the object model used or the defined object classes are generally generic in order to be used by operating and maintenance centers of different manufacturers. This is due to the fact that some of the managerial tasks which the operation and maintenance centers perform in relation to their subordinate network elements, such as e.g. the configuration management, depending on the specific hardware and software configuration of the network elements and thus are manufacturer-dependent.
  • an overly generic object model for the NMC-OMC interface is often insufficient for efficient network management. Therefore, it is possible to arrange a new or extended object model between the network management center NMC and a service and maintenance center OMC1 or OMC2. This can be realized by adding new attributes for operator-specific quantities to object classes defined in the standard. While usually the standardized, non- manufacturer-specific attributes each describe a size, an added attribute can have a plurality of be ⁇ written sizes.
  • VsDataContainer vs: vendor specific
  • VsDataContainer vs: vendor specific
  • the object class VsDataContainer has a first attribute VsData which describes one or more vendor-specific variables; a second attribute VsDataType for indicating the structure of the variable (s) described by the attribute VsData; a third VsDataFormatVersion attribute to specify the language used for the described size (s) of the VsData attribute.
  • the attributes VsDataFormatVersion and VsDataType contain metadata which describe the representation of the data of the attribute VsData or which enable the network management center NMC to interpret the variables described by the attribute VsData.
  • an operation and maintenance center OMC1 or OMC2 can send a notification of the change to the network management center NMC.
  • a notification contains identification information of the changed attribute, the new value of the changed attribute and possibly also the old value of the changed attribute.
  • Such a notification is referred to in document ITU-T X.721 as "attribute value change notification”.
  • the message can contain the current values for all the variables described, ie for both the changed and the unchanged variables.
  • the network management center NMC must then, after receiving such a For all the variables described by the attribute, the received actual values compare with all the old values in order to determine with respect to which of the variables described a change has occurred.
  • the notification of the change contains information which enables the network management center NMC, without comparing all new values with all old values, to directly recognize which variables are affected by the change.
  • This can e.g. be realized by the name or other unique identifier of the respective size described in combination with the changed value and optionally the old value is included; or also the name or another unique identifier of the respective size described in combination with the current values for all variables described by the attribute and optionally the old values for all variables described by the attribute.
  • the notification additionally contains the metadata at least in relation to the changed size or the changed sizes. If this information is not sent to the network management center NMC with the notification of the change, the network work center NMC must search for meta data previously transmitted to it in order to be able to interpret the changed values.
  • an attribute, called data, of an object class contains the manufacturer-specific variables timerl, timer2, timer3, functionStatus, and maxNumberOfUsers as described variables.
  • the quantities timerl, timer2 and timer3 are times, while the size functionStatus is an indication as to whether the respective network resource is functioning properly, and the quantity maxNumberOfUsers is an amount.
  • a second attribute, called DataType is the same Object class describes the structure of the described variables of the attribute Data.
  • a third attribute, called DataFormatVersion, of the same object class describes the language used for the written variables of the attribute Data.
  • the three attributes may be related to a particular network resource e.g. have the following values:
  • the described size timerl of the attribute Data is an integer with a value range of 1 to 60, in the described quantity timer2 of the attribute Data an integer with a value range of 1 to 24, in the case described Size timer3 of the attribute Data by an integer with a value range of 1 to 31, in the described size functionStatus of the attribute Data by the data type Enumerated, whereby for the ordinary betxieb the value 1, for an error the value 1 and for locked or locked the Value 2 is set, and with the described size maxNumberOfUsers of the attribute Data by an integer with a value range of 100 to 1000.
  • the operation and maintenance center OMC1 or OMC2 receives a corresponding error message from the considered network resource, so that the value of the variable functionStatus must be changed from 0 to 1.
  • a notification of the change in the value of the attribute Data is sent to the network management center NMC.
  • the notification contains the following components: Header, PartOfDataType, PartOfDataFormatversion, PartOfDataNewValue, PartOfDataOldValue, DataType, DataFormatVersion, DataNew, DataOld:
  • a header containing information such as e.g. "ManagedObjectClass”, i.e. the object class whose attribute is affected by the change, "managedObjectCitystance”, i. Identification information of the affected network resource, "eventTime”, i.e. the time of change of the attribute.
  • PartOfDataType "functionStatus ENUMERATED (okay 0, malfunction 1, locked 2)
  • PartOfDataFormatVersion ASN.l version 1997 ".
  • DataType "SEQUENCE (timerl INTEGER (1 ... 60), timer2 INTEGER (2 ... 24), timer3 INTEGER (1 ... 31), functionStatus ENUMERATED (okay 0, malfunction 1, Iocked2), maxNumberOffers INTEGER (100-1000)) ".
  • DataFormatVersion "ASN.l version 1997”.
  • the attributes Data, DataFormatVersion and DataType can be attributes of the object class VsDataContainer, for example. in this connection It is only to be noted that the 3GPP standardized attribute VsDataType does not contain metadata per se but a pointer to this metadata.

Abstract

Procédé de communication dans un réseau de gestion d'un réseau de télécommunication, selon lequel une communication entre un gestionnaire (NMC) et un agent (OMC1, OMC2) se produit à l'aide d'un modèle d'objets qui modélise les ressources de réseau du réseau de télécommunication en tant que classes d'objets. Selon le modèle d'objets, les classes d'objets peuvent être définies par des opérations déterminées, des attributs déterminés et des messages déterminés pouvant être envoyés. Au moins une classe d'objets est utilisée avec un attribut qui décrit plusieurs grandeurs. L'agent (OMC1, OMC2) envoie un message d'information sur une modification d'une valeur d'au moins une des grandeurs au gestionnaire (NMC). Ce message contient des informations sur la grandeur ou les grandeurs qui sont concernées par la modification, et sur la valeur ou les valeurs modifiées de la grandeur ou des grandeurs concernées par la modification. La présente invention concerne en outre un gestionnaire et un agent permettant la mise en oeuvre dudit procédé.
EP05771834A 2004-08-12 2005-07-14 Procédé de communication dans un réseau de gestion en vue de l'information sur des modifications d'attribut Withdrawn EP1776801A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102004039214A DE102004039214B4 (de) 2004-08-12 2004-08-12 Kommunikationsverfahren in einem Managementnetz zur Information über Attributsveränderungen
PCT/EP2005/053382 WO2006018357A1 (fr) 2004-08-12 2005-07-14 Procédé de communication dans un réseau de gestion en vue de l'information sur des modifications d'attribut

Publications (1)

Publication Number Publication Date
EP1776801A1 true EP1776801A1 (fr) 2007-04-25

Family

ID=35431140

Family Applications (1)

Application Number Title Priority Date Filing Date
EP05771834A Withdrawn EP1776801A1 (fr) 2004-08-12 2005-07-14 Procédé de communication dans un réseau de gestion en vue de l'information sur des modifications d'attribut

Country Status (4)

Country Link
EP (1) EP1776801A1 (fr)
CN (1) CN100521618C (fr)
DE (1) DE102004039214B4 (fr)
WO (1) WO2006018357A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102006038143A1 (de) * 2006-08-16 2008-02-21 Nokia Siemens Networks Gmbh & Co.Kg Referenzierung von Subattributen für das Netzwerkmanagement

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5414812A (en) * 1992-03-27 1995-05-09 International Business Machines Corporation System for using object-oriented hierarchical representation to implement a configuration database for a layered computer network communications subsystem
US6167448A (en) * 1998-06-11 2000-12-26 Compaq Computer Corporation Management event notification system using event notification messages written using a markup language
EP1152625A1 (fr) * 2000-05-04 2001-11-07 Siemens Aktiengesellschaft Mise à jour de données hardware spécifiques au fabricant à l'interface normalisée OMC-NMC d'un réseau radio mobile
AU2002321152A1 (en) * 2002-07-01 2004-01-19 Siemens Aktiengesellschaft Network management method for the configuration and the interface description of network elements by means of xml

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2006018357A1 *

Also Published As

Publication number Publication date
CN100521618C (zh) 2009-07-29
DE102004039214A1 (de) 2006-02-23
CN101002428A (zh) 2007-07-18
DE102004039214B4 (de) 2006-07-27
WO2006018357A1 (fr) 2006-02-23

Similar Documents

Publication Publication Date Title
WO2007144300A1 (fr) Modification flexible du domaine de responsabilité d'un opérateur pour la gestion de réseau
EP1810523A1 (fr) Procede et dispositifs d'alignement d'informations entre un gestionnaire et un agent dans un reseau de gestion
EP1228599B1 (fr) Procédé et système pour la gestion d'un réseau hiérarchique
EP1668822B1 (fr) Procede de synchronisation d'alarmes dans un systeme de gestion de reseau de communication
EP1520433A1 (fr) Identification d'insuffisances de rendement en matiere de services dans un reseau de communication
EP1776801A1 (fr) Procédé de communication dans un réseau de gestion en vue de l'information sur des modifications d'attribut
DE102006003391B4 (de) Verwendung einer Identifikationsinformation bei Netzwerkmanagement
DE19947083A1 (de) Konfigurieren eines Telekommunikationsnetzes mit mehreren Netzregionen
EP2002601B1 (fr) Detection de relations unidirectionnelles de transfert intercellulaire (handover)
DE102004039215B4 (de) Netzwerkmanagement mit erweitertem Objektmodell
EP2111070B1 (fr) Procédé de détecteur d'erreur des terminaux reconfigurables et d'assistance de décision de reconfiguration, élément réseau correspondant et agent correspondant
EP1617592A1 (fr) Méthode pour choisir un modèle objet pour la communication entre le gestionnaire et l'agent
EP1749369B1 (fr) Procede et dispositifs permettant de faire fonctionner un reseau de gestion en cas de defaillance d'un gestionnaire
EP1612993B1 (fr) Méthode et dispositif pour changer le mode d'opération d'un agent d'un réseau de gestion
WO2008019998A2 (fr) Référençage de sous-attributs pour la gestion de réseau
EP1841131A1 (fr) Gestion de la configuration avec opérations supplémentaires
EP1703667A1 (fr) Gestion de réseau en utilisant une méthode de type maître-réplique
WO2004107790A1 (fr) Procede pour traiter des modifications parametriques dans un reseau de gestion d'un systeme de communication cellulaire et systeme de communication
EP1763937B1 (fr) Procede pour transmettre des donnees de façon securisee dans un systeme de gestion
EP1407622B1 (fr) Configuration dynamique specifique-client d'interface omc-nmc
EP1525757A1 (fr) Mise a disposition d'elements reseau dans un systeme de communication
DE102006036566A1 (de) Vorabinformation von Managern über die Itf-N Schnittstelle
EP1703666A1 (fr) Gestion de réseau avec des transactions distribuées adaptatives
WO2008034804A1 (fr) Examen de l'intégrité de données dans des systèmes de gestion
DE19947893A1 (de) Erweiterter Management-Notification-Dienst zur Reduzierung der Kommunikation zwischen Agent und Manager

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20061130

AK Designated contracting states

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 IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SIEMENS NETWORKS GMBH & CO. KG

RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SIEMENS NETWORKS S.P.A.

DAX Request for extension of the european patent (deleted)
RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SIEMENS NETWORKS GMBH & CO. KG

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20120201