WO2008019998A2 - Référençage de sous-attributs pour la gestion de réseau - Google Patents

Référençage de sous-attributs pour la gestion de réseau Download PDF

Info

Publication number
WO2008019998A2
WO2008019998A2 PCT/EP2007/058325 EP2007058325W WO2008019998A2 WO 2008019998 A2 WO2008019998 A2 WO 2008019998A2 EP 2007058325 W EP2007058325 W EP 2007058325W WO 2008019998 A2 WO2008019998 A2 WO 2008019998A2
Authority
WO
WIPO (PCT)
Prior art keywords
manager
agent
sizes
message
attribute
Prior art date
Application number
PCT/EP2007/058325
Other languages
German (de)
English (en)
Other versions
WO2008019998A3 (fr
Inventor
Olaf Pollakowski
Original Assignee
Nokia Siemens Networks Gmbh & 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 Nokia Siemens Networks Gmbh & Co. Kg filed Critical Nokia Siemens Networks Gmbh & Co. Kg
Publication of WO2008019998A2 publication Critical patent/WO2008019998A2/fr
Publication of WO2008019998A3 publication Critical patent/WO2008019998A3/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/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

Definitions

  • the invention relates to a management system comprising at least one manager and one agent for operating an object model for communication between the manager and the agent.
  • Managers start network monitoring and control operations by sending so-called “requests” that are executed by agents, and receive corresponding responses from the agents.
  • Elements of the managed network also referred to as resources, which perform the role of an agent in the hierarchy, recognize relevant events, so-called “events”, such as alarms, generate corresponding notifications, and transmit them in the form of event messages, so-called “event reports” to managers to enable efficient network management.
  • the manager-agent communication takes place via so-called
  • Object model are marked. Object models are used to model resources of the telecommunications network, these resources being divided into object classes during modeling.
  • Such interfaces exist between, on the one hand, the Network Element Management Level and, on the other hand, the Network Element Level.
  • An example of network facilities of this manager-agent interface is the Operation and Maintenance Center (OMC) on the side of the OMC
  • Network element management level as well as 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 x s of a UMTS mobile network (UMTS: Universal Mobile Telecommunication System) , or radio access points of a WLAN system (WLAN: Wireless Local Area Network), for example, according to one of the IEEE 802.11 standards.
  • BSS Base Station System
  • 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 to this manager-agent interface are the Network Management Center (NMC: Network Management Center) and the Network Management Element (OMC) operation and maintenance center in said GSM or another mobile or telecommunications network.
  • NMC Network Management Center
  • OMC Network Management Element
  • the invention has for its object to provide an efficient method for operating a management system and devices for performing the method.
  • an object model is used for communication between the manager and the agent, with which object classes attributes are assigned. At least one attribute is used to describe a plurality of sizes.
  • referencing information for each size of the subset is included for reference to the respective size.
  • At least one attribute is used to describe a plurality of sizes.
  • the sizes of the attribute can in this case be designed such that they could be used as their own attributes.
  • Such an attribute may, for example, describe the two quantities "number of hardware units used" and "current performance".
  • An example of an attribute, which typically describes multiple sizes, is the vendor specific data (VSData) attribute of a UMTS mobile communication system.
  • Sizes but not every one of these sizes. This case is relevant in practice because often an operation or notification should not be made in relation to all quantities described by the attribute. This is especially true for attributes that describe a variety of sizes.
  • the message contains referencing information for each of the subset sizes; For example, if the message concerns two sizes of the attribute, it will contain two referencing information.
  • a referencing information for each of the subset sizes; For example, if the message concerns two sizes of the attribute, it will contain two referencing information.
  • the referencing information is necessary when referring to a particular size, because due to the majority of the sizes described by the attribute, the mention of the attribute is not sufficient for this.
  • the receiver can thus clearly deduce the referencing information to which size the referencing information belongs. Is thus in the Message a specific indication in connection with a specific referencing information, so the receiver can clearly identify the size of the attribute refers to the specific information.
  • the message is an operation sent by the manager to the agent for reading out the sizes of the subset.
  • a read operation requests read-out and feedback of the respective requested information from the agent.
  • the agent upon receiving the message, the agent sends a response message to the manager, the response message including at least one value for each size of the subset.
  • the response message including at least one value for each size of the subset.
  • the message is an operation for setting values sent by the manager to the agent, wherein the message contains at least one value to be set for each size of the subset.
  • the request to set values is in this case directed to a change of values for the sizes of the subset, or to the generation of such values for the sizes of the subset.
  • the message may be a message sent by the agent to the manager, the message being a change of at least one value of each size
  • Subset applies. Such a message may cause the values of the attributes of the attribute present to the manager and the agent to be the same.
  • At least one or each of the plurality of variables is a variable that can be assigned a respective variable value.
  • a value of a size may be a number, a Word or any combination of characters. There may exist a certain number of discrete values which one size may occupy.
  • An example of a variable that can be assigned with a single variable value is the size "transmission power" of a radio station, which can be assigned a numerical value
  • at least one or each of the plurality of variables is name-value pairs Name fixed while the value is changeable.
  • At least one or each of the plurality of sizes is a variable describing a plurality of sizes.
  • the data structure of the attribute is multi-layered, because the attribute describes multiple sizes, and one or more of these sizes again describe multiple sizes.
  • Different sizes of the first layer may in this case describe different numbers of further sizes of the second layer. It is possible for one or more sizes of the attribute to represent variables that can be assigned a single variable value while one or more other sizes of the attribute describe a plurality of sizes.
  • the referencing information is created using a language used by the manager and / or the agent for filtering. During filtering, it is checked on the basis of specific filter criteria whether the entity entered into the filter, for example a message, passes the filter.
  • the language of the referencing information can be used here to access components of the entity to be filtered, which are to be subjected to a review on the basis of the filter criteria.
  • the language with which the referencing information is created is the Extended Trader Constraint Language specified by the OMG (Object Management Group).
  • OMG Object Management Group
  • the inventive agent comprises means for communicating with a manager using an object model in which object classes attributes are assigned using at least one attribute to describe a plurality of sizes, and means for sending and / or receiving a message containing a subset of the And in which for each of the sizes of the subset a referencing information for reference to the respective size is included.
  • Figure 1 a section of a management system.
  • the network resources of the mobile radio communication system e.g. the network elements NE1, NE2, NE3 are divided into object classes as part of the network management.
  • 3GPP has defined an object model or information model for the communication over the Itf-N interface, which e.g. includes the object classes ManagedElement and ManagedFunction, which are base object classes.
  • Further object classes are e.g. gsmCell, utranCell, btsSiteManager, bssFunction, mscServerFunction, rncFunction, hlrFunction, vlrFunction, sgsnFunction and ggsnFunction. Since object classes can contain other object classes, the
  • An object class is defined over certain operations, i. via commands to network resources of this
  • Object class can be sent by a higher-level manager, as well as certain attributes, ie properties that are assigned to this object class and by one Managers can be queried and edited, and certain messages that can be sent by network resources of the respective object class in the context of network management, as well as the description of the meaning and the behavior of the object class and its components.
  • the object model used or the defined object classes are predominantly generic in order to be used by management facilities of different manufacturers. Modeling of manufacturer-specific properties and functionalities can be done using the attribute vDData (vendor specific Data).
  • vDData vendor specific Data
  • a description of this attribute can be found e.g. in the standard specification 3GPP TS 32.622 (3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Network Resource Model (NRM) (Release 6))
  • CM Configuration Management
  • IRP Generic network resources Integration Reference Point
  • NRM Network Resource Model
  • the advantage of the vsData attribute is that some of the managerial tasks, such as the configuration management, depending on the specific hardware and software design and thus manufacturer-dependent.
  • the vsData attribute is typically one of several attributes that has an object class.
  • the content of the vsData attribute i. the size or sizes described by the vsData attribute is not required by the standard. This can therefore depend on the operator of the management system depending on his
  • vsData attribute has also not been standardized so far.
  • attribute vsData is used in such a way that it has several Data elements and thus contains a complex data structure.
  • This data structure consists of a plurality of individual components, which are referred to below as sub-attributes.
  • a sub-attribute can represent a single variable, which can be assigned specific values, or else a variable that forms its own data structure.
  • the manager MANAGER can send to the agent AGENT an operation OP which causes the setting or reading of sub-attributes of the attribute vsData.
  • Operation OP specifies values for sub-attributes so that the agent AGENT can make the relevant changes after receiving the operation.
  • a read operation OP causes the agent AGENT to send a response to the manager MANAGER with the values of the requested sub-attributes.
  • the agent AGENT can send a value change notification NOTIF (value change notification) to the manager MANAGER, with which he informs the manager MANAGER of the change made.
  • Read operations and set operations are presented e.g. in 3GPP TS 32.602 and 3GPP TS 32.603.
  • Value change notifications are presented e.g. in 3GPP TS 32.662 and 3GPP TS 32.663.
  • the agent AGENT usually specifies the values of all subattributes in its value change notification NOTIF.
  • the manager MANAGER evaluates the received value change notification NOTIF by comparing the received value with the value stored by it for each sub-attribute in order to determine which sub-attribute is affected by the change.
  • both the transmission capacity on the interface between manager MANAGER and agent AGENT and the processing capacity of the MANAGER manager are heavily used. This adverse effect increases with the number of sub-attributes of an attribute, i. with the
  • Messages OP and NOTIF used a referencing of sub-attributes explained in more detail below. Because of the referencing contained in a message, the recipient knows which subattribute is affected by the message. With a set operation OP, the manager MANAGER uses this referencing, so that the agent AGENT recognizes from the referencing that the value of which subattribute is to be set. Likewise, the manager MANAGER uses referencing for a read operation OP, so that the agent AGENT recognizes which sub-attribute is to be read out and thus reports the current value of this sub-attribute to the manager MANAGER. For a value change notification NOTIF, the agent AGENT uses the referencing so that Manager MANAGER uses referencing to identify which sub-attribute is affected by the change in value.
  • the Extended Trader Constraint Language is commonly used in CORBA-based management systems as part of filtering, e.g. if, after receiving a message using certain filter criteria, it is necessary to check whether the message passes a filter and is therefore to be forwarded.
  • the attribute vsData contains a list or sequence of subattributes, each subattribute consisting of a name value pair.
  • the name is of type String, the value is a variable of type any.
  • IDL Interface Definition Language
  • a declarative formal language with a language syntax for describing interfaces is used.
  • the IDL structure definition of the name-value pair is (hereafter: NameValuePairType)
  • NameValuePairListType The IDL type definition of the name-value pairs sequence (hereafter: NameValuePairListType) is
  • VsDataType The IDL type definition of the vsData attribute
  • the length of the sequence is 2, i. the attribute vsData contains two sub-attributes. These have the names “abcMin” and “abcMax” and are each of type short. The IDL name and type definitions of these two sub-attributes is
  • vsData (abcMin) that of the sub-attribute abcMax is based on the Extended Trader Constraint Language
  • the name of the top-level attribute that is, the name of the attribute
  • the name of the attribute is first written.
  • of the attribute vsData, in the parenthesis is the name of the subattribute.
  • Attributes vsData in two layers, where the upper layer contains the top-level attribute vsData, and on the second layer below the sequence of name-value pairs.
  • the data structure of the vsData attribute is tri-level, with the top one being
  • vsData stands, on the second underlying layer a sequence of data envelopes, and on the lowest third layer the contents of the data envelopes.
  • the data envelopes each contain the specification of what kind of data (in the following: VsDataEnvelopeKindType) of type string, as well as the actual data (in the following: VsDataEnvelopeDataType). Again, these actual data are lists of name-value pairs of the type discussed in relation to the first example.
  • typedef string NameType NameType
  • typedef any ValueType typedef NameValuePairType ⁇ nameType name; ValueType value; ⁇ ;
  • typedef sequence ⁇ NameValuePairType> NameValuePairListType; typedef NameValuePairListType vsDataEnvelopeType;
  • VsDataEnvelopeKindType vsDataEnvelopeKind
  • VsDataEnvelopeDataType vsKindEnvelopeKind
  • ⁇ ⁇
  • the length of the sequence of data envelopes is 3, i. the attribute vsData consists of three data envelopes, and further let the length of the sequence of the name-value be pairs within the first data envelope 2, i. Within the first data envelope there are two sub-attributes with the names "abcMin” and "abcMax", each of the type Short. The IDL name and type definitions of these two sub-attributes are the same as in the first example
  • vsDataEnvelopeData (abcMin) that is the sub-attribute abcMax of the first data envelope based on the Extended Trader Constraint Language

Landscapes

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

Abstract

L'invention concerne un procédé d'utilisation d'un système de gestion comportant au moins un gestionnaire (MANAGER) et un agent (AGENT). Le procédé consiste à employer un modèle d'objet pour la communication entre le gestionnaire (MANAGER) et l'agent (AGENT), des attributs étant affectés à des classes d'objet. Au moins un attribut est employé pour décrire une pluralité de grandeurs. Un message (OP, NOTIF) envoyé par le gestionnaire (MANAGER) ou l'agent (AGENT), concernant une quantité partielle des grandeurs, contient une information de référençage pour chaque grandeur de la quantité partielle, pour la référence à la grandeur respective. L'invention concerne également un gestionnaire (MANAGER) et un agent (AGENT) destinés à la mise en oeuvre du procédé.
PCT/EP2007/058325 2006-08-16 2007-08-10 Référençage de sous-attributs pour la gestion de réseau WO2008019998A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE200610038143 DE102006038143A1 (de) 2006-08-16 2006-08-16 Referenzierung von Subattributen für das Netzwerkmanagement
DE102006038143.2 2006-08-16

Publications (2)

Publication Number Publication Date
WO2008019998A2 true WO2008019998A2 (fr) 2008-02-21
WO2008019998A3 WO2008019998A3 (fr) 2008-07-24

Family

ID=38926356

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2007/058325 WO2008019998A2 (fr) 2006-08-16 2007-08-10 Référençage de sous-attributs pour la gestion de réseau

Country Status (2)

Country Link
DE (1) DE102006038143A1 (fr)
WO (1) WO2008019998A2 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6199068B1 (en) * 1997-09-11 2001-03-06 Abb Power T&D Company Inc. Mapping interface for a distributed server to translate between dissimilar file formats
US20060070082A1 (en) * 2004-06-15 2006-03-30 Manjula Sridhar Managed object framework for network management application development
EP1655974A1 (fr) * 2004-11-08 2006-05-10 Siemens Aktiengesellschaft Procédé et appareils d'alignement d'information entre un manager et un agent dans un réseau de gestion

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102004039214B4 (de) * 2004-08-12 2006-07-27 Siemens Ag Kommunikationsverfahren in einem Managementnetz zur Information über Attributsveränderungen

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6199068B1 (en) * 1997-09-11 2001-03-06 Abb Power T&D Company Inc. Mapping interface for a distributed server to translate between dissimilar file formats
US20060070082A1 (en) * 2004-06-15 2006-03-30 Manjula Sridhar Managed object framework for network management application development
EP1655974A1 (fr) * 2004-11-08 2006-05-10 Siemens Aktiengesellschaft Procédé et appareils d'alignement d'information entre un manager et un agent dans un réseau de gestion

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LUCIAN HIRSCH DIE TELECOMMUNICATIONS MANAGEMENT NETWORK: "Vorläufiges Setzen von einzelnen Netzelementen eines Telekommunikationsnetzes in den Zustand au er Dienst an der NMC-OMC-Schnittstelle" IP.COM JOURNAL, IP.COM INC., WEST HENRIETTA, NY, US, 23. Juli 2003 (2003-07-23), XP013011714 ISSN: 1533-0001 *

Also Published As

Publication number Publication date
DE102006038143A1 (de) 2008-02-21
WO2008019998A3 (fr) 2008-07-24

Similar Documents

Publication Publication Date Title
DE69416399T2 (de) Allgemeines modell von verwalteten objekten für den lan-bereich
WO2007144300A1 (fr) Modification flexible du domaine de responsabilité d'un opérateur pour la gestion de réseau
EP1810523B1 (fr) Procede et produits d'alignement d'informations entre un gestionnaire et un agent dans un reseau de gestion
EP1668822B1 (fr) Procede de synchronisation d'alarmes dans un systeme de gestion de reseau de communication
EP1742415A1 (fr) Correction automatique de listes d'alarme dans des systémes de gestion
EP1730886B1 (fr) Procedes et dispositifs de distribution d'informations de gestion dans un reseau de gestion d'un systeme de communication
DE102006003391B4 (de) Verwendung einer Identifikationsinformation bei Netzwerkmanagement
EP2002601B1 (fr) Detection de relations unidirectionnelles de transfert intercellulaire (handover)
WO2008019998A2 (fr) Référençage de sous-attributs pour la gestion de réseau
DE102004039214B4 (de) Kommunikationsverfahren in einem Managementnetz zur Information über Attributsveränderungen
DE102004039215B4 (de) Netzwerkmanagement mit erweitertem Objektmodell
EP1629682B1 (fr) Procede pour traiter des modifications parametriques dans un reseau de gestion d'un systeme de communication cellulaire et systeme de communication
DE10337464A1 (de) Verfahren zur Behandlung von Alarmen in einem Managementsystem eines Kommunikationsnetzes
EP1612993B1 (fr) Méthode et dispositif pour changer le mode d'opération d'un agent d'un réseau de gestion
EP1617592A1 (fr) Méthode pour choisir un modèle objet pour la communication entre le gestionnaire et l'agent
EP1734689A1 (fr) Opération de véto pour un système de gestion avec une configuration multi manager
EP1749369B1 (fr) Procede et dispositifs permettant de faire fonctionner un reseau de gestion en cas de defaillance d'un gestionnaire
EP1763937B1 (fr) Procede pour transmettre des donnees de façon securisee dans un systeme de gestion
EP1802031A1 (fr) Gestion de réseau avec configuration redondante
DE102006036566B4 (de) Vorabinformation von Managern über die Itf-N Schnittstelle
EP1901478A1 (fr) Traitement de données de performance en fonction de la charge dans un système de gestion de réseau
EP1841131A1 (fr) Gestion de la configuration avec opérations supplémentaires
EP1701471A1 (fr) Système de gestion pour un système de communication
DE102006043671B4 (de) Überprüfung der Datenintegrität in Managementsystemen
EP1703666A1 (fr) Gestion de réseau avec des transactions distribuées adaptatives

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07819932

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

122 Ep: pct application non-entry in european phase

Ref document number: 07819932

Country of ref document: EP

Kind code of ref document: A2