EP1145538B1 - Method and communication system for processing state information in a management network having different management levels - Google Patents

Method and communication system for processing state information in a management network having different management levels Download PDF

Info

Publication number
EP1145538B1
EP1145538B1 EP99929089A EP99929089A EP1145538B1 EP 1145538 B1 EP1145538 B1 EP 1145538B1 EP 99929089 A EP99929089 A EP 99929089A EP 99929089 A EP99929089 A EP 99929089A EP 1145538 B1 EP1145538 B1 EP 1145538B1
Authority
EP
European Patent Office
Prior art keywords
agent
information
manager
state
state information
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.)
Expired - Lifetime
Application number
EP99929089A
Other languages
German (de)
French (fr)
Other versions
EP1145538A2 (en
Inventor
Lucian Hirsch
Alfred Schmidbauer
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.)
Siemens AG
Original Assignee
Siemens AG
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 filed Critical Siemens AG
Publication of EP1145538A2 publication Critical patent/EP1145538A2/en
Application granted granted Critical
Publication of EP1145538B1 publication Critical patent/EP1145538B1/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/22—Arrangements for supervision, monitoring or testing
    • H04M3/2254—Arrangements for supervision, monitoring or testing in networks
    • H04M3/2263—Network management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
    • H04M2201/54—Object oriented software

Definitions

  • the invention relates to a method and a corresponding communication system for handling status information by a management network having several management levels, wherein the status information for an information comparison is transmitted between an agent of a management level and at least one manager of a next higher management level.
  • Telecommunications Management Network (TMN) principles
  • Telecommunications Management Network defines several levels of management for the management of a communication system, such as a mobile communication system, where each level has a dual function.
  • each level except the bottom one has a manager function for the level below.
  • each level except the top one has an agent function for the next higher level.
  • State management is one of several TMN functional areas that characterizes the state of a managed object.
  • a managed object is a logical abstraction of a resource in the communication system.
  • a distinction is made between hardware-related managed objects that describe a vendor-specific implementation of a function, and function-related managed objects, each of which is the abstraction of a vendor-independent functionality.
  • an object-oriented environment such as between a manager and an agent in a mobile communication system - each agent functionality is provided by a particular object - as an instance of an object class - that both known to the agent as well as the manager.
  • the management state of an object can be described by state information according to the ITU-T X.731 standard. In this case, any change in the status of a managed object is transmitted by the agent in corresponding messages to the manager.
  • the agent must cache the status changes that occurred during this interval in order to ensure that the manager has an overview of the communication options as soon as possible the current state of the object is made available.
  • a state realignment between the agent and manager - for example, a new connection after a connection abort or after an initialization of the agent or the manager - is executed.
  • the manager plays the active role by triggering the information match and requesting and receiving the state information for each existing object from the agent. The request and transfer always occurs for all agent objects, i. regardless of the content of the respective state information at the time of the query by the manager. With a larger number of managed objects, the signaling load is significant and leads to an undesirably long duration of the alignment procedure.
  • the object of the invention is to specify a method and communication system for the treatment of status information by a management network having multiple management levels for improved information matching.
  • the invention assumes that status information is transmitted for an information comparison between an agent of a management level and at least one manager of a next higher management level.
  • the manager sends a request message to perform the information matching to the agent.
  • the agent checks the state information for deviations from a normal state and sends changes to the state information in one or more consecutive messages to the manager.
  • the information matching is done only when changed state information is available, so that the deviations from the normal state to the manager are notified by the agent on request. Consequently, all status information is not automatically transmitted, regardless of whether it has changed or not.
  • the manager is only interested in the information necessary for the changes of the state information, so that only these deviations are provided him according to the subject of the invention. Consequently, it saves the transmission of state information for which no deviation from the normal state has been determined by the agent.
  • state attributes and / or status attributes are used as state information.
  • the normal state is preferably defined on the basis of predefinable values for the state attributes and / or status attributes.
  • state attributes for indicating the operational readiness, the manageability and the use of a resource managed by the agent are used in the communication system as state information.
  • status attributes indicative of an agent-serviced resource in the communication system are advantageously used as state information.
  • the manager in the request message sends a correlation information for an assignment of the respective request to the messages received by the agent with the changed state information.
  • multiple requests for information matching can occur simultaneously or serially.
  • the parallel solution has the advantages of even better utilization of the transmission resources at the interface of the agent-manager relationship as well as faster provision of the changed state information for the next higher management level.
  • assigning the incoming responses of the agent with the changed status information even if the order does not comply with the correct request.
  • Successively initiated requests can in fact overtake each other, for example when a packet data network is passed between the agent and the manager.
  • the agent can process multiple requests in parallel, and immediately thereafter regardless of order the started requests return the status information to the manager (s) for reconciliation.
  • a further advantageous embodiment of the invention provides that the agent in a message for starting the information matching a correlation information for an association of the subsequently sent messages with the changed state information is sent to the respective started information matching.
  • the unambiguous correlation information assigned by the agent ensures that the changed state information of different, simultaneous or serial information reconciliations, irrespective of when they are sent by the agent, reaches the manager, who in each case processes the received status information.
  • the informational control is controlled by the manager as a function of at least one parameter sent to the agent.
  • the advantage of the information comparison that can be parametrized in comparison with the basic functionality is that only certain status information is transmitted on the basis of the transmitted parameter. This results in the manager a selection function for a subset of all state information.
  • the possibility of controlling the adjustment with simple means and using standardized messages increases the flexibility of the manager and additionally reduces the message and information flow.
  • the parameterizable alignment functionality for the treatment of the status information for example, a selection of resources and / or an active control of the order of the requested information can be achieved.
  • a parameter is sent by the manager, by means of which the information matching is automatically initiated by the agent. This allows the manager to reconcile the information so that it is triggered by the agent at specific times.
  • the embodiment describes the invention based on a TMN concept for the management of a mobile communication system, which comprises, for example, network equipment of a mobile network according to the GSM standard.
  • the invention is neither limited to the GSM standard nor to mobile radio networks, but can be applied to telecommunications networks of all types and operating modes using a TMN management network.
  • a mobile communication system is a hierarchically structured system of various network devices in which the lowest hierarchical level is formed by the mobile stations. These mobile stations communicate via a radio interface with the next hierarchical level forming radio stations, which are referred to as base stations.
  • the mobile stations for example, in a radio area of a radio cell serving base stations are preferably combined to cover a larger radio area and connected to higher-level network facilities, the base station controllers.
  • the base stations and base station controllers belong to a base station subsystem of the mobile communication system.
  • the base station controllers communicate with defined interfaces one or more switching devices, the mobile switching centers, via which, inter alia, the transition to other communication networks.
  • the mobile switching centers together with a plurality of databases form the switching system of the mobile communication system.
  • Operation and Maintenance Centers which ia. is used to configure and monitor the network equipment.
  • Surveillance measures and configuration measures are usually remotely controlled from the operations and maintenance center, which are usually located in the field of mobile exchanges.
  • An operating and maintenance center communicates with a base station system or switching system via a defined interface.
  • Another task of the operation and maintenance system is the management of state information ("state management"), which is one of several management functional areas and identifies the state of a managed object.
  • state management is a logical abstraction of a physical resource - i. a network device - in the mobile communication system.
  • hardware-related managed objects that describe a vendor-specific implementation of a function
  • function-related managed objects each of which is the abstraction of a vendor-independent functionality.
  • the TMN principles define multiple levels ("levels"), of which three levels are referred to in the present example with reference to FIG 1 and FIG. 2 will be explained below.
  • the 1 and FIG. 2 each show three levels A, B and C of the management network, of which the management level C, the Network Element Level with multiple base station systems BSS11, BSS12 ... BSS1N and BSS21, BSS22 ... BSS2M.
  • the management level B identifies the network element management level, and in the operations and maintenance centers OMC1 and OMC2, the vendor-specific management functionality for individual subsystems, such as the operation and maintenance center OMC1 for the base station systems BSS11, BSS12 in the present example. .BSS1N and the operation and maintenance center OMC2 for the base station systems BSS21, BSS22 ... BSS2M.
  • Management level A identifies the network management level, in which network management centers NMC1 and NMC2 each realize an integrated, manufacturer-independent management functionality.
  • network management centers NMC1 and NMC2 may have access to the same network device of the next lower management level B, in the present example the network management centers NMC1 and NMC2 of the next higher management level C to the operation and maintenance center OMC1 of the next lower management level B.
  • defined interfaces for information transmission are provided between the network devices of different management levels.
  • the difference in the representations according to the 1 and FIG. 2 is that an agent-manager relationship for handling state information for one or more state alignments in FIG. 1 between the operation and maintenance center OMC1 (agent) and a network management center NMC1 (manager) or several - physically separate - network management centers NMC1, NMC2 (manager) and in FIG.
  • the operation and maintenance center OMC1 the - stored state information stored on the basis of, for example, within the supervised base station systems BSS11 ... BSS1N - stored state information and sent in parallel to both managers on request. This is preferably done after a connection abort or after an initialization of the agent or manager.
  • FIG. 1 shows the structure for information reconciliation requests issued multiple times according to the invention, which in the present example is parallel between the management level B, in which the agent is in the form of the operation and maintenance center OMC1, and the next higher management level A, in which the managers of at least two network management centers NMC1, NMC2 are expired.
  • the base station system BSS11 provides the status information stored on the basis of, for example, events and statuses occurring within the managed base stations and base station controllers and parallel to at least two managers of the operation and maintenance center OMC1 in the form of the different applications OF1 and OF2, both of which are executed by one and the same physical device OMC1 sent. This is also preferably done after a connection abort or after an agent or manager initialization. A serial transmission of requests to the agent, eg the base station system BSS11, initiated several times by a single manager, eg the operation and maintenance center OMC1, is also possible.
  • an agent-manager relationship may also exist between the operations and maintenance center OMC1 (an agent) and the network management center NMC1 (a manager) for serial exchange of requests and status information, or parallel exchange of requests and status information for at least two different applications NF1 and NF2 (two managers) in the network management center NMC1.
  • FIG. 2 shows the structure for information balancing in parallel between the management level B according to the invention, in which the managers are located as applications OF1 and OF2, and the next lower management level C in which the agent is located.
  • the information comparison in the present example first begins between the base station system, e.g. BSS11, and the applications OF1, OF2 in the operation and maintenance center OMC1, and then continues in parallel between the operation and maintenance center OMC1 and the superordinate network management centers NMC1, NMC2. At the end of these procedures, the state situation in both the OMC and the NMC is again updated and coordinated.
  • the realignment method may be based on updating the status information between agent and managers in two immediately adjacent management levels, e.g. Level B and Level A, be restricted.
  • FIG. 3 shows a schematic representation of the structure of Agent AG and manager MA1, MA2 with the required for the implementation simultaneously - in two or more managers - or serially - with only one manager - expiring state realignment procedures facilities.
  • Each manager MA1, MA2 and agent AG has a control device M-CTR or A-CTR, which generate and evaluate the messages for the information comparison can.
  • they have - not shown - transmitting / receiving devices for sending and receiving the messages and storage devices for storing the status information and other useful and signaling information.
  • the manager M-CTR of the manager generates a request message with which the agent is called to transmit the status information, and preferably inserts in this request message a correlation information used to associate the request with subsequently sent messages. This, assigned by the controller M-CTR correlation information is unique.
  • the transfer of the request message to the agent takes place via the send / receive devices.
  • the M-CTR manager of the information reconciliation controller incorporates one or more par parameters into the respective request message to specifically request certain state information from selected network devices.
  • the respective request message is sent with the parameters par to the agent AG.
  • the information comparison can be automated on the basis of a parameter par, so that the control device A-CTR of the agent triggers the adjustment process of itself repeatedly in periods defined by a time interval.
  • the control device A-CTR of the agent AG receives the request message with the par parameters, evaluates them, and checks the state information regarding occurring deviations from a normal state. If so, the controller A-CTR generates one or more messages in which only the changes of the state information for at least one existing object are successively sent to the Manager MA1, MA2 and the controller M-CTR are sent back.
  • the managed object state information preferably includes a plurality of state attributes, exemplified by OST (Operational State), AST (Administrative State), and UST (Usage State) attributes for indicating the operational readiness, manageability, and use of an agent-managed and associated with the object Resource are specified in the communication system.
  • the state information preferably also includes a plurality of status attributes, of which the attributes UNS (Unknown Status), ALS (Alarm Status) and AVS (Available Status) are defined. In doing so, they indicate for the respective object or for the respective resource in the communication system whether it is in an unknown state (USS), in an alarm state (ALS) or in a state of availability (AVS).
  • UNS Unknown Status
  • ALS Alarm Status
  • AVS Available Status
  • the state attribute OST can assume the values “ready” (enabled) or “not ready” (disabled), whereby from the manager's point of view this status information is readable but not changeable.
  • the state attribute AST may take the values "released by the manager (unlocked)” or “disabled by the manager (locked)” or “shutting down", the latter state value meaning that in the event of a currently terminated operation, no new Services are accepted more by the resource. From a manager's point of view, this status information is readable and changeable.
  • the state attribute UST can assume the values "used, free capacity (active)” or “used, no free capacity (busy)” or “unused (idle)", whereby from the manager's point of view this status information is readable but not changeable.
  • the normal state which is used for checking the presence of deviations and thus of changed state information, can be set by a value (default), which consists of a combination of the above single values, for example “ready”, “released by the manager” and “not used ", results. This means that only the changed state information of managed objects from the agent to the manager be transferred, the state of which differs from the normal state defined above. All other status information, ie objects in the normal state, are ignored and will not be sent.
  • the status attributes UNS, ALS and AVS define in more detail the state of the resource associated with the object in terms of operational readiness, current usage and manageability.
  • the status attribute UNS is set to true if the state attribute OST or the state attribute AST is not supported.
  • the value of the respective state attribute OST, AST is irrelevant.
  • the status attribute ALS represents an overall indicator for the alarm state of a resource and is only readable by the manager and can not be influenced.
  • the attribute takes the binary value "one" in the alarm state and the binary value "zero" in the normal state.
  • the status attribute AVS can not take one or more values from a defined set of single values and is also read-only by the manager.
  • the normal state is characterized by an empty value set (empty set).
  • the status information entered in the memory device of the agent AG is checked by the control device A-CTR and only the changed state information cst (changed status) is transmitted to the control device M-CTR of the manager.
  • the clear correlation information entered by the control device M-CTR of the manager MA1, MA2 in the request message is used to correlate the requests, while with a further correlation information the assignment of the messages subsequently sent by the agent (state change notifications) to the "State -Realignment "is effected.
  • the correlation information assigned by the agent AG or its control device A-CTR is also clear and is moved to the next higher management level preferably in the respective message together with the changed state information cst sent.
  • each of the managers MA1, MA2 assignable and controllable by them filter functions EFD1, EFD2 Event Forwarding Discriminators
  • filter functions EFD1, EFD2 Event Forwarding Discriminators
  • the manager M-CTR of the manager is able to set up such filter functions in the agent AG, delete and set the filter criteria to control the message flow according to his individual requirements. Therefore, there may be a case where the filter function setting differs from manager to manager, so that content-wise different state information is handled by the concurrent realignment procedures.
  • FIG. 4 shows the message flow between an agent AG - in the example shown according to the FIG. 1 the operation and maintenance center OMC1 or in the example shown the FIG. 2 the base station system BSS11 - and the manager MA1, MA2 - in the example according to the FIG. 1 the different network management centers NMC1, NMC2 or in the example of FIG. 2 the different applications OF1, OF2.
  • the message flow is preferably carried out with standardized M-EVENT-REPORT services and an initially initiated M-CREATE service. These are generic CMISE-standardized (Common Management Information Service Element) procedures defined in accordance with ITU-T X.710.
  • the ITU-T X.731 defines the management of a standardized transmission of Condition information performed according to the M-EVENT-REPORT services.
  • the correlation information is entered in the messages or in certain message fields.
  • the managers MA1, MA2 provide the parameters for controlling the information matching with specific parameter values and enter them one or more times into the respective request message.
  • the example in FIG. 4 shows the message flow on the basis of individual messages, which can be transmitted in parallel between the agent AG and the managers MA1, MA2 or serially between the agent AG and the individual manager MA1.
  • each manager MA1, MA2 sends according to the M-CREATE service a request message staAS (start Alignment Scheduler) for transmitting the status information for the information matching to the Agent AG.
  • the correlation information staAH state alignment handle
  • the correlation information staAH is preferably also sent in, for example, in the defined message field "actionInformation", which identifies a direct assignment of the request to the subsequently received agent messages.
  • the agent checks whether changes of the state information are present based on deviations from the normal state and prepares the changed state information for each managed object that is not in the normal state. This is preferably done with the state and status attributes according to the intent FIG. 3 , The agent AG continues the information comparison by generating a start message stSA (Start State Alignment) and inserting the correlation information aliNI (alignment Notification Id) defined by it in this message.
  • the correlation information staAH assigned and transmitted by the manager is also contained in a specific message field of the start message stSA.
  • the correlation information aliNI is entered, for example, in the standardized message field "notification identifier" of the message stSA.
  • Both information staAH, aliNI are sent together in the message stSA from the agent AG to the managers MA1, MA2.
  • This allows "alignment-related" M-EVENT-REPORT messages of different M-CREATE requests to be distinguished from each other, but also from regular ones M-EVENT-REPORT Messages that have nothing to do with the reconciliation of information. This is because an alignment procedure does not necessarily stop other M-EVENT-REPORT messages that occur spontaneously during the alignment procedure and are sent to the manager (s).
  • the agent AG After the automatic start of the information comparison, which is controlled by at least one parameter by the manager MA1, MA2, the agent AG sends in consecutive state change messages staCN using the M-EVENT-REPORT service only the processed changed state information cst to the requesting manager MA1, MA2 back.
  • the status changes cst determined for an object and the resource associated therewith are transmitted in a message staCN, so that a plurality of messages, possibly different objects, also require a plurality of messages staCN.
  • each message staCN the correlation information aliNI - for example, in the defined message field "correlated notifications" - on.
  • the agent AG After the last M-EVENT-REPORT message of each information match, the agent AG generates an end message endA, which contains the correlation information aliNI.

Abstract

According to the invention, state information is transmitted between an agent (AG) of a management level (B, C) and at least one manager (MA1, MA2) of a next higher management level (A, B). A request message (staAS) is sent by the manager (MA1, MA2) to the agent (AG) for executing information matching. State information regarding deviations from a normal state are checked by the agent (AG) and changes in state information are sent to the manager (MA1, MA2) in one or several successive messages (staCN). Information matching is conducted only when changes in state information exist so that deviations from normal state are informed to the manager. Consequently, all state information regardless of whether said information has changed or not is not automatically transmitted to the manager. This results in reduced information flow between the agent and the manager and represents a considerable gain for the manager especially in the case of a plurality of managed objects.

Description

Die Erfindung betrifft ein Verfahren sowie ein entsprechendes Kommunikationssystem zur Behandlung von Zustandsinformationen durch ein mehrere Managementebenen aufweisendes Managementnetz, wobei die Zustandsinformationen für einen Informationsabgleich zwischen einem Agent einer Managementebene und zumindest einem Manager einer nächsthöheren Managementebene übertragen werden.The invention relates to a method and a corresponding communication system for handling status information by a management network having several management levels, wherein the status information for an information comparison is transmitted between an agent of a management level and at least one manager of a next higher management level.

Die Prinzipien eines Managementnetzes, die auch als TMN-Prinzipien (Telecommunications Management Network) bezeichnet werden, definieren mehrere Managementebenen für das Management eines Kommunikationssystems - beispielsweise eines Mobil-Kommunikationssystems - , wobei jede Ebene eine doppelte Funktion hat. Im managenden System hat jede Ebene außer der untersten eine Manager-Funktion für die darunterliegende Ebene. Im gemanagten System hat jede Ebene außer der obersten eine Agenten-Funktion für die nächsthöhere Ebene.The principles of a management network, also referred to as Telecommunications Management Network (TMN) principles, define several levels of management for the management of a communication system, such as a mobile communication system, where each level has a dual function. In the managing system, each level except the bottom one has a manager function for the level below. In the managed system, each level except the top one has an agent function for the next higher level.

Das Management von Zustandsinformationen ("State Management") stellt einen von mehreren TMN-Funktionsbereichen dar, der den Zustand eines gemanagten Objekts kennzeichnet. Ein gemanagtes Objekt ist eine logische Abstraktion einer Ressource im Kommunikationssystem. Hierbei wird unterschieden zwischen hardwarebezogenen gemanagten Objekten, die eine herstellerspezifische Realisierung einer Funktion beschreiben, und funktionsbezogenen gemanagten Objekten, bei denen es sich jeweils um die Abstraktion einer herstellerunabhängigen Funktionalität handelt. In einer objekt-orientierten Umgebung - wie zwischen Manager und Agent in einem Mobil-Kommunikationssystem - wird jede Agent-Funktionalität von einem bestimmten Objekt - als Instanz einer Objektklasse - bereitgestellt, das sowohl dem Agent als auch dem Manager bekannt ist. Der Managementzustand eines Objekts kann anhand von Zustandsinformationen gemäß dem Standard ITU-T X.731 beschrieben werden. Dabei wird jede Änderung des Zustands eines gemanagten Objekts vom Agent in entsprechenden Nachrichten zum Manager übertragen.State management is one of several TMN functional areas that characterizes the state of a managed object. A managed object is a logical abstraction of a resource in the communication system. Here, a distinction is made between hardware-related managed objects that describe a vendor-specific implementation of a function, and function-related managed objects, each of which is the abstraction of a vendor-independent functionality. In an object-oriented environment - such as between a manager and an agent in a mobile communication system - each agent functionality is provided by a particular object - as an instance of an object class - that both known to the agent as well as the manager. The management state of an object can be described by state information according to the ITU-T X.731 standard. In this case, any change in the status of a managed object is transmitted by the agent in corresponding messages to the manager.

Wenn die Verbindung zwischen den beiden Managementebenen, also zwischen Agent und Manager, für eine bestimmte Zeit nicht mehr gewährleistet ist, muß der Agent die während dieses Intervalls aufgetretenen Zustandsänderungen zwischenspeichern, um sicherzustellen, daß nach dem Wiederherstellen der Kommunikationsmöglichkeit dem Manager möglichst schnell eine Übersicht über den aktuellen Zustand des Objekts zur Verfügung gestellt wird. Zu diesem Zweck wird ein Informationsabgleich (state realignment) zwischen Agent und Manager - beispielsweise bei einem neuen Verbindungsaufbau nach einem Verbindungsabbruch oder nach einer Initialisierung des Agenten oder des Managers - ausgeführt. Grundsätzlich spielt der Manager die aktive Rolle, indem er den Informationsabgleich triggert und vom Agent die Zustandsinformationen für jedes vorhandene Objekt anfordert und empfängt. Die Anforderung und Übertragung erfolgt immer für alle Agent-Objekte, d.h. unabhängig vom Inhalt der jeweiligen Zustandsinformationen zum Zeitpunkt der Abfrage durch den Manager. Bei einer größeren Anzahl gemanagter Objekte ist die Signalisierungslast erheblich und führt zu einer unerwünscht langen Dauer der Alignment-Prozedur.If the connection between the two management levels, ie between agent and manager, is no longer guaranteed for a specific time, the agent must cache the status changes that occurred during this interval in order to ensure that the manager has an overview of the communication options as soon as possible the current state of the object is made available. For this purpose, a state realignment between the agent and manager - for example, a new connection after a connection abort or after an initialization of the agent or the manager - is executed. Basically, the manager plays the active role by triggering the information match and requesting and receiving the state information for each existing object from the agent. The request and transfer always occurs for all agent objects, i. regardless of the content of the respective state information at the time of the query by the manager. With a larger number of managed objects, the signaling load is significant and leads to an undesirably long duration of the alignment procedure.

In dem Dokument EP A 0,810,756 ist ein Verfahren offenbart, wie die Mitteilung von Zustandsänderungen einer Netzresource unterdrückt werden kann, wenn die Zuständsänderungen den Eindruck hervorrufen könnten, als wenn die Netzresource defekt wäre, obwohl sie lediglich nicht mehr so gut oder sicher wie normalerweise funktioniert. Dazu werden vom Manager bei der Zustandabfrage Schwellwerte übermittelt und die Zustände der abgefragten Netzresource nur dann mitgeteilt, wenn sie über den Schwellwerten liegen.In the document EP A 0,810,756 there is disclosed a method of suppressing the notification of state changes of a network resource when the state changes might give the impression that the network resource is defective, although it merely does not function as well or as normally as it normally does. For this purpose, the manager transmits threshold values during the status query and notifies the states of the queried network resource only if they are above the threshold values.

Das Dokument " SNMP, SNMPv2 and CMIP - the technologies for multisendor network management," Computer Communications 20 (1997), Seiten 73-88 , offenbart ein Verfahren zur Behandlung von Zustands informationen in einem KommunikationsSystem, bei dem Zustands informationen von einem Agenten in einer Management Information Base gesammelt werden, und von einem Manager abgefragt werden können.The document " SNMP, SNMPv2 and CMIP - the technologies for multisendor network management, "Computer Communications 20 (1997), pages 73-88 discloses a method for handling status information in a communication system in which status information is collected from an agent in a management information base and can be queried by a manager.

Aufgabe der Erfindung ist es, ein Verfahren und Kommunikationssystem zur Behandlung von Zustandsinformationen durch ein mehrere Managementebenen aufweisendes Managementnetz für einen verbesserten Informationsabgleich anzugeben.The object of the invention is to specify a method and communication system for the treatment of status information by a management network having multiple management levels for improved information matching.

Diese Aufgabe wird durch die Erfindung, dabei insbesondere durch die mit den Ansprüchen definierte Erfindung gelöst. Weiterbildungen der Erfindung sind den Unteransprüchen zu entnehmen.This object is achieved by the invention, in particular by the invention defined by the claims. Further developments of the invention are to refer to the dependent claims.

Die Erfindung geht davon aus, daß Zustandsinformationen für einen Informationsabgleich zwischen einem Agent einer Managementebene und zumindest einem Manager einer nächsthöheren Managementebene übertragen werden. Gemäß dem Gegenstand der Erfindung wird von dem Manager eine Anforderungsnachricht zur Durchführung des Informationsabgleichs an den Agent gesendet. Von dem Agent werden die Zustandsinformationen hinsichtlich Abweichungen von einem Normalzustand überprüft und Änderungen der Zustandsinformationen in einer oder mehreren aufeinanderfolgenden Nachrichten an den Manager gesendet.The invention assumes that status information is transmitted for an information comparison between an agent of a management level and at least one manager of a next higher management level. In accordance with the subject invention, the manager sends a request message to perform the information matching to the agent. The agent checks the state information for deviations from a normal state and sends changes to the state information in one or more consecutive messages to the manager.

Durch den Erfindungsgegenstand erfolgt der Informationsabgleich nur, wenn geänderte Zustandsinformationen vorliegen, sodaß die Abweichungen vom Normalzustand dem Manager auf Anforderung vom Agent mitgeteilt werden. Es werden folglich nicht automatisch alle Zustandsinformationen übermittelt, unabhängig davon, ob sie sich geändert haben oder nicht. Daraus ergibt sich ein reduzierter Informationsfluß zwischen Agent und Manager, was bei einer Vielzahl von gemanagten Objekten seitens des Managers einen erheblichen Gewinn darstellt. Der Manager interessiert sich aber nur für die zum Informationsabgleich notwendigen Änderungen der Zustandsinformationen, sodaß nur diese Abweichungen ihm gemäß dem Gegenstand der Erfindung zur Verfügung gestellt werden. Folglich spart man sich die Übertragung der Zustandsinformationen, für die keine Abweichung vom Normalzustand seitens des Agent festgestellt wurde.By the subject invention, the information matching is done only when changed state information is available, so that the deviations from the normal state to the manager are notified by the agent on request. Consequently, all status information is not automatically transmitted, regardless of whether it has changed or not. This results in a reduced flow of information between the agent and the manager, which represents a significant gain in a variety of managed objects by the manager. However, the manager is only interested in the information necessary for the changes of the state information, so that only these deviations are provided him according to the subject of the invention. Consequently, it saves the transmission of state information for which no deviation from the normal state has been determined by the agent.

Gemäß einer Weiterbildung der Erfindung werden Zustandsattribute und/oder Statusattribute als Zustandsinformationen verwendet. Dabei wird vorzugsweise der Normalzustand anhand vorgebbarer Werte für die Zustandsattribute und/oder Statusattribute definiert. Durch die obigen Attribute können detaillierte Informationen über den geänderten Zustand jedes vorhandenen Objekts vom Manager abgerufen und vom Agent bereitgestellt werden.According to one embodiment of the invention, state attributes and / or status attributes are used as state information. In this case, the normal state is preferably defined on the basis of predefinable values for the state attributes and / or status attributes. Through the above attributes can provide detailed information about the changed state of any existing Object retrieved from the manager and provided by the agent.

Vorzugsweise werden Zustandsattribute zur Kennzeichnung der Betriebsbereitschaft, der Verwaltbarkeit und der Benutzung einer vom Agent betreuten Ressource im Kommunikationssystem als Zustandsinformationen verwendet. Des weiteren werden in vorteilhafterweise Statusattribute, die für eine vom Agent betreute Ressource im Kommunikationssystem angeben, ob sie sich in einem unbekannten Zustand, in einem Alarmzustand oder in einem Zustand der Verfügbarkeit befindet, als Zustandsinformationen verwendet. Durch die Übertragung lediglich der geänderten Attribute erhält der Manager nur die detaillierten, minimal erforderlichen Informationen, um den Informationsabgleich zwischen Manager und Agent herzustellen.Preferably, state attributes for indicating the operational readiness, the manageability and the use of a resource managed by the agent are used in the communication system as state information. Furthermore, status attributes indicative of an agent-serviced resource in the communication system, whether in an unknown state, in an alert state, or in a state of availability, are advantageously used as state information. By transferring only the changed attributes, the manager receives only the most detailed, minimal information needed to reconcile information between the manager and the agent.

Es hat sich als günstig erwiesen, wenn von dem Manager in der Anforderungsnachricht eine Korrelationsinformation für eine Zuordnung der jeweiligen Anforderung zu den vom Agent empfangenen Nachrichten mit den geänderten Zustandsinformationen mitgesendet wird. Damit können mehrere Anforderungen zum Informationsabgleich simultan oder seriell ablaufen. Die parallele Lösung hat die Vorteile einer noch besseren Ausnutzung der Übertragungsressourcen auf der Schnittstelle der Agent-Manager-Beziehung sowie einer schnelleren Bereitstellung der geänderten Zustandsinformationen für die nächsthöhere Managementebene. Durch die Zuordnung anhand der eindeutigen, vom Manager vergebenen Korrelationsinformation besteht darüber hinaus die Möglichkeit, die eintreffenden Antworten des Agent mit den geänderten Zustandsinformationen auch bei einer Nichteinhaltung der Reihenfolge der richtigen Anforderung zuzuweisen. Nacheinander initiierte Anforderungen können sich nämlich gegenseitig überholen, so beispielsweise dann, wenn zwischen Agent und Manager ein Paketdatennetz durchlaufen wird. Der Agent kann mehrere Anforderungen parallel bearbeiten und unmittelbar danach ohne Rücksicht auf die Reihenfolge der gestarteten Anforderungen die Zustandsinformationen zum Informationsabgleich an den oder die Manager rücksenden.It has proved to be advantageous if the manager in the request message sends a correlation information for an assignment of the respective request to the messages received by the agent with the changed state information. Thus, multiple requests for information matching can occur simultaneously or serially. The parallel solution has the advantages of even better utilization of the transmission resources at the interface of the agent-manager relationship as well as faster provision of the changed state information for the next higher management level. By the assignment on the basis of the clear correlation information assigned by the manager, there is also the possibility of assigning the incoming responses of the agent with the changed status information even if the order does not comply with the correct request. Successively initiated requests can in fact overtake each other, for example when a packet data network is passed between the agent and the manager. The agent can process multiple requests in parallel, and immediately thereafter regardless of order the started requests return the status information to the manager (s) for reconciliation.

Eine weitere vorteilhafte Weiterbildung der Erfindung sieht vor, daß von dem Agent in einer Nachricht zum Starten des Informationsabgleichs eine Korrelationsinformation für eine Zuordnung der nachfolgend gesendeten Nachrichten mit den geänderten Zustandsinformationen zu dem jeweils gestarteten Informationsabgleich mitgesendet wird. Durch die eindeutige, vom Agent vergebene Korrelationsinformation ist gewährleistet, daß die geänderten Zustandsinformationen verschiedener, simultan oder seriell ablaufender Informationsabgleiche unabhängig vom Zeitpunkt ihres Aussendens durch den Agent den Manager erreichen, der jeweils die empfangenen Zustandsinformationen weiterverarbeitet.A further advantageous embodiment of the invention provides that the agent in a message for starting the information matching a correlation information for an association of the subsequently sent messages with the changed state information is sent to the respective started information matching. The unambiguous correlation information assigned by the agent ensures that the changed state information of different, simultaneous or serial information reconciliations, irrespective of when they are sent by the agent, reaches the manager, who in each case processes the received status information.

Gemäß einer besonders vorteilhaften Weiterbildung der Erfindung wird von dem Manager der Informationsabgleich abhängig von zumindest einem zum Agent gesendeten Parameter gesteuert. Der Vorteil des gegenüber der Basisfunktionalität parametrisierbaren Informationsabgleichs liegt darin, daß nur bestimmte Zustandsinformationen auf Grund des übermittelten Parameters übermittelt werden. Damit ergibt sich für den Manager eine Auswahlfunktion für eine Teilmenge aus allen Zustandsinformationen. Insbesondere die Möglichkeit der steuernden Beeinflussung des Abgleichs mit einfachen Mitteln und unter Anwendung standardisierter Nachrichten erhöht die Flexibilität des Managers und reduziert den Nachrichten- und Informationsfluß zusätzlich. Durch die parametrisierbare Alignment-Funktionalität für die Behandlung der Zustandsinformationen kann beispielsweise eine Auswahl der Ressourcen und/oder eine aktive Steuerung der Reihenfolge der angeforderten Informationen erzielt werden. Besonders die Kombination der Basisfunktionalität - Übertragung lediglich der Änderungen des Zustands auf Grund von Abweichungen gegenüber dem Normalzustand - mit der parametrisierbaren Alignment-Funktionalität führt zu einem besonders effektiven Verfahren und Kommunikationssystem, das eine optimale Nutzung der Übertragungsressourcen auf der Schnittstelle der Agent-Manager-Beziehung sowie ein schnellstmögliches Bereitstellen nur der vom Manager gewünschten Zustandsinformationen für die nächsthöhere Managementebene durch den Agent bewirkt.According to a particularly advantageous development of the invention, the informational control is controlled by the manager as a function of at least one parameter sent to the agent. The advantage of the information comparison that can be parametrized in comparison with the basic functionality is that only certain status information is transmitted on the basis of the transmitted parameter. This results in the manager a selection function for a subset of all state information. In particular, the possibility of controlling the adjustment with simple means and using standardized messages increases the flexibility of the manager and additionally reduces the message and information flow. The parameterizable alignment functionality for the treatment of the status information, for example, a selection of resources and / or an active control of the order of the requested information can be achieved. Especially the combination of the basic functionality - transmission of only the changes of the state due to deviations from the normal state - with the parametrisable alignment functionality leads to a particularly effective method and communication system, that causes the agent to make best use of the transmission resources at the interface of the agent-manager relationship, and to provide only as quickly as possible the agent's desired state information for the next higher management level.

Gemäß einer Weiterbildung der Erfindung wird von dem Manager ein Parameter gesendet, durch den der Informationsabgleich von dem Agent automatisch initiiert wird. Damit kann der Informationsabgleich vom Manager so gesteuert werden, daß er zu bestimmten Zeitpunkten vom Agent von selbst ausgelöst wird.According to a development of the invention, a parameter is sent by the manager, by means of which the information matching is automatically initiated by the agent. This allows the manager to reconcile the information so that it is triggered by the agent at specific times.

Gemäß weiterer vorteilhafter Weiterbildungen der Erfindung kann die Parametrisierung mit einem oder mehreren der folgenden, von dem Manager jeweils eingestellten Parameterwerten erfolgen. So wird ein Parameter von dem Manager mit Parameterwerten versehen, die einen Start-Zeitpunkt für den automatischen Informationsabgleich und/oder einen Ende-Zeitpunkt für den automatischen Informationsabgleich angeben. Andere Parameterwerte definieren

  • ein Zeitintervall für eine Wiederholung des automatischen Informationsabgleichs,
  • ausgewählte Ressourcen, für die geänderte Zustandsinformationen vom Agent zu übermitteln sind.
  • den Abbruch eines laufenden Informationsabgleichs
According to further advantageous developments of the invention, the parameterization can be carried out with one or more of the following parameter values set by the manager. Thus, a parameter is provided by the manager with parameter values indicating a start time for the automatic information reconciliation and / or an end time for the automatic information reconciliation. Define other parameter values
  • a time interval for a repetition of the automatic reconciliation of information,
  • Selected resources for which changed status information is to be transmitted by the agent.
  • the termination of a current information comparison

Nachstehend wird die Erfindung anhand von Ausführungsbeispielen unter Bezugnahme auf die Figuren näher erläutert. Es zeigen

FIG 1
das Blockschaltbild eines Managementnetzes für ein Mobil-Kommunikationssystem mit Agent-Manager- Beziehung zwischen einem Betriebs- und Wartungs- zentrum und einem oder mehreren Netzmanagementzen- tren,
FIG 2
das Blockschaltbild des Managementnetzes gemäß Figur 1 mit Agent-Manager-Beziehung zwischen ei- nem Basisstationssystem und einem Betriebs- und Wartungszentrum zur Durchführung von zumindest zwei Anwendungen für das Basisstationssystem,
FIG 3
das Blockschaltbild von Agent und Manager zur Be- handlung der Zustandsinformationen für parametri- sierbare Informationsabgleiche gemäß der Erfin- dung, und
FIG 4
den Nachrichtenfluß zwischen dem Manager und dem Agent zur Steuerung des Informationsabgleichs.
The invention will be explained in more detail by means of embodiments with reference to the figures. Show it
FIG. 1
1 is a block diagram of a management network for a mobile communication system with agent-manager relationship between an operation and maintenance center and one or more network management centers;
FIG. 2
the block diagram of the management network according to FIG. 1 with agent-manager relationship between a base station system and an operations and maintenance center for performing at least two applications for the base station system,
FIG. 3
the block diagram of the agent and manager for the treatment of the state information for parameterizable information adjustments according to the invention, and
FIG. 4
the message flow between the manager and the information balancing agent.

Das Ausführungsbeispiel beschreibt die Erfindung anhand eines TMN-Konzepts für das Management eines Mobil-Kommunikationssystems, das beispielsweise Netzeinrichtungen eines Mobilfunknetzes nach dem GSM-Standard aufweist. Die Erfindung ist weder auf auf den GSM-Standard noch auf Mobilfunknetze beschränkt, sondern läßt sich auf Telekommunikationsnetze jeder Art und Betriebsweise, die ein TMN-Managementnetz nutzen, anwenden.The embodiment describes the invention based on a TMN concept for the management of a mobile communication system, which comprises, for example, network equipment of a mobile network according to the GSM standard. The invention is neither limited to the GSM standard nor to mobile radio networks, but can be applied to telecommunications networks of all types and operating modes using a TMN management network.

Ein Mobil-Kommunikationssystem ist ein hierarchisch gegliedertes System verschiedener Netzeinrichtungen, bei dem die unterste Hierarchiestufe von den Mobilstationen gebildet wird. Diese Mobilstationen kommunizieren über eine Funkschnittstelle mit die nächste Hierarchieebene bildenden Funkstationen, die als Basisstationen bezeichnet werden. Die beispielsweise Mobilstationen in einem Funkbereich einer Funkzelle versorgenden Basisstationen sind vorzugsweise zur Abdeckung eines größeren Funkgebiets zusammengefaßt und mit übergeordneten Netzeinrichtungen, den Basisstationssteuerungen verbunden. Die Basisstationen und Basisstationssteuerungen gehören zu einem Basisstationssystem (Base Station Subsystem) des Mobil-Kommunikationssystems. Die Basisstationssteuerungen kommunizieren über definierte Schnittstellen mit einer oder mehreren Vermittlungseinrichtungen, den Mobilvermittlungsstellen, über die u.a. auch der Übergang zu anderen Kommunikationsnetzen erfolgt. Die Mobilvermittlungsstellen bilden gemeinsam mit einer Mehrzahl von Datenbasen das Vermittlungssystem (Switching Subsystem) des Mobil-Kommunikationssystems.A mobile communication system is a hierarchically structured system of various network devices in which the lowest hierarchical level is formed by the mobile stations. These mobile stations communicate via a radio interface with the next hierarchical level forming radio stations, which are referred to as base stations. The mobile stations, for example, in a radio area of a radio cell serving base stations are preferably combined to cover a larger radio area and connected to higher-level network facilities, the base station controllers. The base stations and base station controllers belong to a base station subsystem of the mobile communication system. The base station controllers communicate with defined interfaces one or more switching devices, the mobile switching centers, via which, inter alia, the transition to other communication networks. The mobile switching centers together with a plurality of databases form the switching system of the mobile communication system.

Neben den obigen Netzeinrichtungen existieren ein oder mehrere Betriebs- und Wartungszentren (Operation and Maintenance Centers), die u.a. zum Konfigurieren und Überwachen der Netzeinrichtungen dient. Überwachungsmaßnahmen und Konfigurierungsmaßnahmen werden hierzu meist vom Betriebs- und Wartungszentrum aus ferngesteuert, die üblicherweise im Bereich der Mobilvermittlungsstellen angeordnet sind. Ein Betriebs-und Wartungszentrum kommuniziert dabei jeweils mit einem Basisstationssystem oder Vermittlungssysstem über eine definierte Schnittstelle. Eine weitere Aufgabe des Betriebs- und Wartungssystems ist das Management von Zustandsinformationen ("State Management"), das einen von mehreren Managementfunktionsbereichen darstellt und den Zustand eines gemanagten Objekts kennzeichnet. Ein gemanagtes Objekt ist eine logische Abstraktion einer physikalischen Ressource - d.h. einer Netzeinrichtung - im Mobil-Kommunikationssystem. Hierbei wird unterschieden zwischen hardwarebezogenen gemanagten Objekten, die eine herstellerspezifische Realisierung einer Funktion beschreiben, und funktionsbezogenen gemanagten Objekten, bei denen es sich jeweils um die Abstraktion einer herstellerunabhängigen Funktionalität handelt.In addition to the above network facilities, there are one or more Operation and Maintenance Centers, which ia. is used to configure and monitor the network equipment. Surveillance measures and configuration measures are usually remotely controlled from the operations and maintenance center, which are usually located in the field of mobile exchanges. An operating and maintenance center communicates with a base station system or switching system via a defined interface. Another task of the operation and maintenance system is the management of state information ("state management"), which is one of several management functional areas and identifies the state of a managed object. A managed object is a logical abstraction of a physical resource - i. a network device - in the mobile communication system. Here, a distinction is made between hardware-related managed objects that describe a vendor-specific implementation of a function, and function-related managed objects, each of which is the abstraction of a vendor-independent functionality.

Für das Management des Mobil-Kommunikationssystems definieren die TMN-Prinzipien mehrere Ebenen ("Levels"), von denen im vorliegenden Beispiel drei Ebenen unter Bezugnahme auf die FIG 1 und FIG 2 nachfolgend erläutert werden.For the management of the mobile communication system, the TMN principles define multiple levels ("levels"), of which three levels are referred to in the present example with reference to FIG 1 and FIG. 2 will be explained below.

Die FIG 1 und FIG 2 zeigen jeweils drei Ebenen A, B und C des Managementnetzes, von denen die Managementebene C die Netzeinrichtungsebene ("Network Element Level") mit mehreren Basisstationssystemen BSS11, BSS12...BSS1N sowie BSS21, BSS22 ...BSS2M enthält. Die Managementebene B kennzeichnet die Netzeinrichtungsmanagementebene ("Network Element Management Level"), in der Betriebs- und Wartungszentren OMC1 und OMC2 jeweils die herstellerspezifische Managementfunktionalität für einzelne Subsysteme, wie im vorliegenden Beispiel das Betriebs- und Wartungszentrum OMC1 für die Basisstationssysteme BSS11, BSS12 ...BSS1N und das Betriebs- und Wartungszentrum OMC2 für die Basisstationssysteme BSS21, BSS22...BSS2M, bereitstellen. Die Managementebene A kennzeichnet die Netzmanagementebene ("Network Management Level"), in der Netzmanagementzentren NMC1 und NMC2 jeweils eine integrierte, vom Hersteller unabhängige Management-Funktionalität realisieren. Dabei können mehrere Netzmanagementzentren einen Zugriff zu derselben Netzeinrichtung der nächstniedrigeren Managementebene B haben, im vorliegenden Beispiel die Netzmanagementzentren NMC1 und NMC2 der nächsthöheren Managementebene C zum Betriebs- und Wartungszentrum OMC1 der nächstniedrigeren Managementebene B. Zwischen den Netzeinrichtungen unterschiedlicher Managementebenen sind definierte Schnittstellen zur Informationsübertragung vorgesehen.The 1 and FIG. 2 each show three levels A, B and C of the management network, of which the management level C, the Network Element Level with multiple base station systems BSS11, BSS12 ... BSS1N and BSS21, BSS22 ... BSS2M. The management level B identifies the network element management level, and in the operations and maintenance centers OMC1 and OMC2, the vendor-specific management functionality for individual subsystems, such as the operation and maintenance center OMC1 for the base station systems BSS11, BSS12 in the present example. .BSS1N and the operation and maintenance center OMC2 for the base station systems BSS21, BSS22 ... BSS2M. Management level A identifies the network management level, in which network management centers NMC1 and NMC2 each realize an integrated, manufacturer-independent management functionality. In this case, several network management centers may have access to the same network device of the next lower management level B, in the present example the network management centers NMC1 and NMC2 of the next higher management level C to the operation and maintenance center OMC1 of the next lower management level B. Defined interfaces for information transmission are provided between the network devices of different management levels.

Der Unterschied in den Darstellungen gemäß den FIG 1 und FIG 2 liegt darin, daß eine Agent-Manager-Beziehung zur Behandlung von Zustandsinformationen für einen oder mehrere Informationsabgleiche (state alignment) in FIG 1 zwischen dem Betriebs- und Wartungszentrum OMC1 (Agent) und einem Netzmanagementzentrum NMC1 (Manager) oder mehreren - physikalisch getrennten - Netzmanagementzentren NMC1, NMC2 (Manager) sowie in FIG 2 zwischen dem Basisstationssystem BSS11 (Agent) und zwei verschiedenen Anwendungen OF1 und OF2 (Manager) in dem Betriebs- und Wartungszentrum OMC1 oder zwischen dem Betriebs- und Wartungszentrum OMC1 (Agent) und zwei verschiedenen Anwendungen NF1 und NF2 (Manager) in dem Netzmanagementzentrum NMC1 besteht. Um in den Netzmanagementzentren NMC1, NMC2 jederzeit einen Überblick über den Zustand gemanagter Objekte sicherzustellen, werden vom Betriebs- und Wartungszentrum OMC1 die - auf Grund von beispielsweise innerhalb der betreuten Basisstationssysteme BSS11...BSS1N auftretenden Ereignissen und Zuständen - gespeicherten Zustandsinformationen bereitgestellt und parallel zu beiden Managern auf Anforderung gesendet. Dies erfolgt vorzugsweise nach einem Verbindungsabbruch oder nach einer Initialisierung des Agent oder des Managers. Ebenso können mehrere Anforderungen auch hintereinander von einem einzelnen Manager, z.B. dem Netzmanagementzentrum NMC1 an den Agent, z.B. dem Betriebs-und Wartungszentrum OMC1, gerichtet werden. FIG 1 zeigt die Struktur für gemäß der Erfindung mehrfach ausgesendete Anforderungen zum Informationsabgleich, die im vorliegenden Beispiel parallel zwischen der Managementebene B, in der sich der Agent in Form des Betriebs- und Wartungszentrums OMC1 befindet, und der nächsthöheren Managementebene A, in der die Manager von zumindest zwei Netzmanagementzentren NMC1, NMC2 gebildet werden, ablaufen.The difference in the representations according to the 1 and FIG. 2 is that an agent-manager relationship for handling state information for one or more state alignments in FIG. 1 between the operation and maintenance center OMC1 (agent) and a network management center NMC1 (manager) or several - physically separate - network management centers NMC1, NMC2 (manager) and in FIG. 2 between the base station system BSS11 (Agent) and two different applications OF1 and OF2 (Manager) in the operation and maintenance center OMC1 or between the operation and maintenance center OMC1 (Agent) and two different applications NF1 and NF2 (Manager) in the network management center NMC1 , In order to ensure an overview of the condition of managed objects in the network management centers NMC1, NMC2 at any time, they are provided by the operation and maintenance center OMC1 the - stored state information stored on the basis of, for example, within the supervised base station systems BSS11 ... BSS1N - stored state information and sent in parallel to both managers on request. This is preferably done after a connection abort or after an initialization of the agent or manager. Likewise, several requests can also be made in succession by a single manager, eg the network management center NMC1, to the agent, eg the operation and maintenance center OMC1. FIG. 1 FIG. 2 shows the structure for information reconciliation requests issued multiple times according to the invention, which in the present example is parallel between the management level B, in which the agent is in the form of the operation and maintenance center OMC1, and the next higher management level A, in which the managers of at least two network management centers NMC1, NMC2 are expired.

Um auch in der Managementebene B, z.B. in dem Betriebs- und Wartungszentrum OMC1 jederzeit einen Überblick über die Zustandssituation sicherzustellen, werden vom Basisstationssystem BSS11 die - auf Grund von beispielsweise innerhalb der betreuten Basisstationen und Basisstationssteuerungen auftretenden Ereignissen und Zuständen - gespeicherten Zustandsinformationen bereitgestellt und parallel zu mindestens zwei Managern des Betriebs- und Wartungszentrums OMC1 in Form der unterschiedlichen Anwendungen OF1 und OF2, die beide von ein-und derselben physikalischen Einrichtung OMC1 ausgeführt werden, gesendet. Dies erfolgt ebenfalls vorzugsweise nach einem Verbindungsabbruch oder nach einer Initialisierung des Agenten oder des Managers. Eine serielle Übertragung von mehrfach durch einen einzelnen Manager, z.B. dem Betriebs- und Wartungszentrum OMC1, initiierten Anforderungen an den Agent, z.B. dem Basisstationssystem BSS11, ist ebenfalls möglich. Alternativ oder zusätzlich kann eine-Agent-Manager Beziehung auch zwischen dem Betriebs- und Wartungszentrum OMC1 (ein Agent) und dem Netzmanagementzentrum NMC1 (ein Manager) zum seriellen Austausch von Anforderungen und Zustandsinformationen oder zum parallelen Austausch von Anforderungen und Zustandsinformationen für mindestens zwei unterschiedliche Anwendungen NF1 und NF2 (zwei Manager) im Netzmanagementzentrum NMC1 existieren. FIG 2 zeigt die Struktur für gemäß der Erfindung parallel ablaufende Informationsabgleiche zwischen der Managementebene B, in der sich die Manager als Anwendungen OF1 und OF2 befinden, und der nächstniedrigeren Managementebene C, in der sich der Agent befindet.In order to ensure an overview of the status situation at any time even in the management level B, for example in the operation and maintenance center OMC1, the base station system BSS11 provides the status information stored on the basis of, for example, events and statuses occurring within the managed base stations and base station controllers and parallel to at least two managers of the operation and maintenance center OMC1 in the form of the different applications OF1 and OF2, both of which are executed by one and the same physical device OMC1 sent. This is also preferably done after a connection abort or after an agent or manager initialization. A serial transmission of requests to the agent, eg the base station system BSS11, initiated several times by a single manager, eg the operation and maintenance center OMC1, is also possible. Alternatively or additionally, an agent-manager relationship may also exist between the operations and maintenance center OMC1 (an agent) and the network management center NMC1 (a manager) for serial exchange of requests and status information, or parallel exchange of requests and status information for at least two different applications NF1 and NF2 (two managers) in the network management center NMC1. FIG. 2 FIG. 2 shows the structure for information balancing in parallel between the management level B according to the invention, in which the managers are located as applications OF1 and OF2, and the next lower management level C in which the agent is located.

Sobald eine in der Managementebene C ausgefallene interne Schnittstelle wieder betriebsbereit ist, wird auf Anforderung des Managers/der Manager der Informationsabgleich, auch als Realignment-Prozedur oder Realignment-Verfahren bezeichnet, gestartet, wobei gemäß der Erfindung nur die auf Grund von Abweichungen gegenüber einem Normalzustand geänderten Zustandsinformationen agentseitig übermittelt werden. Dabei beginnt der Informationsabgleich im vorliegenden Beispiel zuerst zwischen dem Basisstationssystem, z.B. BSS11, und den Anwendungen OF1, OF2 im Betriebs- und Wartungszentrum OMC1 parallel und setzt sich anschließend zwischen dem Betriebs-und Wartungszentrum OMC1 und den übergeordneten Netzmanagementzentren NMC1, NMC2 parallel fort. Am Ende dieser Prozeduren ist die Zustandssituation sowohl im OMC als auch in den NMC wieder aktualisiert und aufeinander abgestimmt. Das Realignment-Verfahren kann selbstverständlich auf die Aktualisierung der Zustandsinformationen zwischen Agent und Managern in zwei unmittelbar angrenzenden Managementebenen, z.B. Ebene B und Ebene A, beschränkt sein.As soon as an internal interface which has failed in the management level C is again ready for operation, information is requested at the request of the manager / manager, also referred to as a realignment procedure or realignment procedure, whereby according to the invention only those due to deviations from a normal state changed state information to be transmitted agent side. In this case, the information comparison in the present example first begins between the base station system, e.g. BSS11, and the applications OF1, OF2 in the operation and maintenance center OMC1, and then continues in parallel between the operation and maintenance center OMC1 and the superordinate network management centers NMC1, NMC2. At the end of these procedures, the state situation in both the OMC and the NMC is again updated and coordinated. Of course, the realignment method may be based on updating the status information between agent and managers in two immediately adjacent management levels, e.g. Level B and Level A, be restricted.

FIG 3 zeigt in schematischer Darstellung den Aufbau von Agent AG und Manager MA1, MA2 mit den zur Durchführung simultan - bei zwei oder mehreren Managern - oder seriell - bei nur einem Manager - ablaufender State-Realignment-Prozeduren erforderlichen Einrichtungen. Jeder Manager MA1, MA2 und Agent AG verfügt über eine Steuereinrichtung M-CTR bzw. A-CTR, die die Nachrichten für den Informationsabgleich generieren und auswerten können. Ebenso weisen sie - nicht näher dargestellte - Sende/Empfangseinrichtungen für das Versenden und Empfangen der Nachrichten sowie Speichereinrichtungen für das Speichern der Zustandsinformationen und anderer Nutz- und Signalisierungsinformationen auf. FIG. 3 shows a schematic representation of the structure of Agent AG and manager MA1, MA2 with the required for the implementation simultaneously - in two or more managers - or serially - with only one manager - expiring state realignment procedures facilities. Each manager MA1, MA2 and agent AG has a control device M-CTR or A-CTR, which generate and evaluate the messages for the information comparison can. Likewise, they have - not shown - transmitting / receiving devices for sending and receiving the messages and storage devices for storing the status information and other useful and signaling information.

Dabei generiert die Steuereinrichtung M-CTR des Manager eine Anforderungsnachricht, mit der der Agent zur Übermittlung der Zustandsinformationen aufgerufen wird, und fügt in diese Anforderungsnachricht vorzugsweise eine zur Zuordnung der Anforderung zu nachfolgend gesendeten Nachrichten benutzte Korrelationsinformation ein. Diese, von der Steuereinrichtung M-CTR vergebene Korrelationsinformation ist eindeutig. Über die Sende/Empfangseinrichtungen erfolgt die Übertragung der Anforderungsnachricht zum Agent. Darüber hinaus bindet die Einrichtung M-CTR des Managers zur Steuerung des Informationsabgleichs einen oder mehrere Parameter par in die jeweilige Anforderungsnachricht ein, um bestimmte Zustandsinformationen von ausgewählten Netzeinrichtungen gezielt anzufordern. Die jeweilige Anforderungsnachricht wird mit den Parametern par zum Agent AG gesendet. Insbesondere läßt sich anhand eines Parameters par der oder die Informationsabgleiche automatisieren, sodaß in durch ein Zeitintervall definierten Zeiträumen die Steuereinrichtung A-CTR des Agent den Abgleichvorgang von selbst wiederholt auslöst. Durch die parametrisierbare Alignment-Funktionalität hinsichtlich der Behandlung von Zustandsinformationen kann beispielsweise eine Auswahl der Ressourcen und/oder eine aktive Steuerung der Reihenfolge der angeforderten Informationen erzielt werden.The manager M-CTR of the manager generates a request message with which the agent is called to transmit the status information, and preferably inserts in this request message a correlation information used to associate the request with subsequently sent messages. This, assigned by the controller M-CTR correlation information is unique. The transfer of the request message to the agent takes place via the send / receive devices. In addition, the M-CTR manager of the information reconciliation controller incorporates one or more par parameters into the respective request message to specifically request certain state information from selected network devices. The respective request message is sent with the parameters par to the agent AG. In particular, the information comparison can be automated on the basis of a parameter par, so that the control device A-CTR of the agent triggers the adjustment process of itself repeatedly in periods defined by a time interval. By means of the parameterizable alignment functionality with regard to the treatment of status information, for example a selection of the resources and / or an active control of the order of the requested information can be achieved.

Die Steuereinrichtung A-CTR des Agent AG empfängt die Anforderungsnachricht mit den Parametern par, wertet sie aus, und überprüft die Zustandsinformationen hinsichtlich auftretender Abweichungen von einem Normalzustand. Ist dies der Fall, erzeugt die Steuereinrichtung A-CTR eine oder mehrere Nachrichten, in der nur die Änderungen der Zustandsinformationen für zumindest ein vorhandenes Objekt aufeinanderfolgend an den Manager MA1, MA2 bzw. die Steuereinrichtung M-CTR rückgesendet werden. Die Zustandsinformationen gemanagter Objekte umfassen vorzugsweise mehrere Zustandsattribute, von denen beispielhaft die Attribute OST (Operational State), AST (Administrative State) und UST (Usage State) zur Kennzeichnung der Betriebsbereitschaft, der Verwaltbarkeit und der Benutzung einer vom Agent betreuten und mit dem Objekt assoziierten Ressource im Kommunikationssystem angegeben sind. Die Zustandsinformationen umfassen vorzugsweise auch mehrere Statusattribute, von denen die Attribute UNS (Unknown Status), ALS (Alarm Status) und AVS (Available Status) definiert sind. Dabei geben sie für das jeweilige Objekt bzw. für die jeweilige Ressource im Kommunikationssystem an, ob sie sich in einem unbekannten Zustand (UNS), in einem Alarmzustand (ALS) oder in einem Zustand der Verfügbarkeit (AVS) befindet.The control device A-CTR of the agent AG receives the request message with the par parameters, evaluates them, and checks the state information regarding occurring deviations from a normal state. If so, the controller A-CTR generates one or more messages in which only the changes of the state information for at least one existing object are successively sent to the Manager MA1, MA2 and the controller M-CTR are sent back. The managed object state information preferably includes a plurality of state attributes, exemplified by OST (Operational State), AST (Administrative State), and UST (Usage State) attributes for indicating the operational readiness, manageability, and use of an agent-managed and associated with the object Resource are specified in the communication system. The state information preferably also includes a plurality of status attributes, of which the attributes UNS (Unknown Status), ALS (Alarm Status) and AVS (Available Status) are defined. In doing so, they indicate for the respective object or for the respective resource in the communication system whether it is in an unknown state (USS), in an alarm state (ALS) or in a state of availability (AVS).

Das Zustandsattribut OST kann die Werte "betriebsbereit (enabled) "oder" nicht betriebsbereit (disabled)" annehmen, wobei aus Managersicht diese Zustandsinformation lesbar, aber nicht veränderbar ist. Das Zustandsattribut AST kann die Werte "freigegeben durch den Manager (unlocked) "oder" gesperrt durch den Manager (locked)" oder "gesperrt (shutting down)" annehmen, wobei letztgenannter Zustandswert bedeutet, daß für den Fall eines aktuell beendeten Betriebs keine neuen Dienste mehr von der Ressource angenommen werden. Aus Managersicht ist diese Zustandsinformation lesbar und veränderbar. Das Zustandsattribut UST kann die Werte "benutzt, freie Kapazität (active)" oder "benutzt, keine freie Kapazität (busy)" oder "nicht benutzt (idle)" annehmen, wobei aus Managersicht diese Zustandsinformation nur lesbar, aber nicht veränderbar ist. Der Normalzustand, der zur Prüfung des Vorliegens von Abweichungen und damit von geänderten Zustandsinformationen angewendet wird, ist einstellbar durch einen Wert (default), der sich aus einer Kombination obiger Einzelwerte, beispielsweise "betriebsbereit", "freigegeben durch den Manager" und "nicht benutzt", ergibt. Dies bedeutet, daß nur die geänderten Zustandsinformationen gemanagter Objekte vom Agent zum Manager übertragen werden, deren Zustand sich von dem oben definierten Normalzustand unterscheidet. Alle übrigen Zustandsinformationen, d.h. von Objekten im Normalzustand, bleiben unberücksichtigt und werden nicht übersandt.The state attribute OST can assume the values "ready" (enabled) or "not ready" (disabled), whereby from the manager's point of view this status information is readable but not changeable. The state attribute AST may take the values "released by the manager (unlocked)" or "disabled by the manager (locked)" or "shutting down", the latter state value meaning that in the event of a currently terminated operation, no new Services are accepted more by the resource. From a manager's point of view, this status information is readable and changeable. The state attribute UST can assume the values "used, free capacity (active)" or "used, no free capacity (busy)" or "unused (idle)", whereby from the manager's point of view this status information is readable but not changeable. The normal state, which is used for checking the presence of deviations and thus of changed state information, can be set by a value (default), which consists of a combination of the above single values, for example "ready", "released by the manager" and "not used ", results. This means that only the changed state information of managed objects from the agent to the manager be transferred, the state of which differs from the normal state defined above. All other status information, ie objects in the normal state, are ignored and will not be sent.

Neben diesen Zustandsattributen definieren die Statusattribute UNS, ALS und AVS in detaillierterer Form den Zustand der mit dem Objekt assoziierten Ressource hinsichtlich Betriebsbereitschaft, momentane Benutzung und Verwaltbarkeit. So ist das Statusattribut UNS auf den Wert "true" gesetzt, wenn das Zustandsattribut OST oder das Zustandsattribut AST nicht unterstützt wird. Der Wert des jeweiligen Zustandsattributs OST, AST ist dabei unerheblich. Das Statusattribut ALS stellt einen Gesamtindikator für den Alarmzustand einer Ressource dar und ist vom Manager nur lesbar, nicht beeinflußbar. Das Attribut nimmt den binären Wert "eins" bei Alarmzustand und den binären Wert "null" im Normalzustand ein. Das Statusattribut AVS kann keinen oder mehrere Werte aus einem definierten Satz von Einzelwerten annehmen und ist für den Manager ebenfalls nur lesbar. Der Normalzustand ist durch eine leere Wertemenge (empty set) gekennzeichnet.In addition to these state attributes, the status attributes UNS, ALS and AVS define in more detail the state of the resource associated with the object in terms of operational readiness, current usage and manageability. For example, the status attribute UNS is set to true if the state attribute OST or the state attribute AST is not supported. The value of the respective state attribute OST, AST is irrelevant. The status attribute ALS represents an overall indicator for the alarm state of a resource and is only readable by the manager and can not be influenced. The attribute takes the binary value "one" in the alarm state and the binary value "zero" in the normal state. The status attribute AVS can not take one or more values from a defined set of single values and is also read-only by the manager. The normal state is characterized by an empty value set (empty set).

Die in der Speichereinrichtung des Agent AG eingetragenen Zustandsinformationen werden von der Steuereinrichtung A-CTR überprüft und nur die geänderten Zustandsinformationen cst (changed status) zur Steuereinrichtung M-CTR des Managers ausgesendet.The status information entered in the memory device of the agent AG is checked by the control device A-CTR and only the changed state information cst (changed status) is transmitted to the control device M-CTR of the manager.

Dabei wird die von der Steuereinrichtung M-CTR des Managers MA1, MA2 in die Anforderungsnachricht eingetragene eindeutige Korrelationsinformation zur Korrelation der Anforderungen benutzt, während mit einer weiteren Korrelationsinformation die Zuordnung der nachfolgend vom Agent gesendeten Nachrichten (state change notifications) zu dem jeweils gestarteten "State-Realignment" bewirkt wird. Auch die vom Agent AG bzw. dessen Steuereinrichtung A-CTR vergebene Korrelationsinformation ist eindeutig und wird in die nächsthöhere Managementebene vorzugsweise in der jeweiligen Nachricht zusammen mit den geänderten Zustandsinformationen cst gesendet. Durch die Verwendung der Korrelationsinformationen ist eine eindeutige Zuordnung simultan oder seriell durchgeführter Informationsabgleiche zu mehreren Managern oder einem einzelnen Manager möglich.In this case, the clear correlation information entered by the control device M-CTR of the manager MA1, MA2 in the request message is used to correlate the requests, while with a further correlation information the assignment of the messages subsequently sent by the agent (state change notifications) to the "State -Realignment "is effected. The correlation information assigned by the agent AG or its control device A-CTR is also clear and is moved to the next higher management level preferably in the respective message together with the changed state information cst sent. By using the correlation information, it is possible to unambiguously assign simultaneous or serial information comparisons to multiple managers or a single manager.

Wahlweise können im Agent AG mehrere, jeweils den Managern MA1, MA2 zuordenbare und von ihnen steuerbare Filterfunktionen EFD1, EFD2 (Event Forwarding Discriminators) mit Filterkriterien für die vom Agent AG erzeugten Nachrichten mitbenutzt werden, sodaß die Nachrichten mit den geänderten Zustandsinformationen cst nur bei Erfüllen der Filterkriterien zu den Managern MA1, MA2 geroutet werden. Die Steuereinrichtung M-CTR des Managers ist in der Lage, derartige Filterfunktionen im Agent AG einzurichten, zu löschen und die Filterkriterien festzulegen, um je nach seinen individuellen Anforderungen den Nachrichtenfluß steuern zu können. Daher kann der Fall auftreten, daß die Filterfunktions-Einstellung von Manager zu Manager unterschiedlich ist, sodaß durch die simultan ablaufenden Realignment-Prozeduren inhaltlich verschiedene Zustandsinformationen behandelt werden.Alternatively, multiple, each of the managers MA1, MA2 assignable and controllable by them filter functions EFD1, EFD2 (Event Forwarding Discriminators) can be shared with filter criteria for the messages generated by the agent AG, so that the messages with the changed state information cst only when fulfilling the filter criteria are routed to the managers MA1, MA2. The manager M-CTR of the manager is able to set up such filter functions in the agent AG, delete and set the filter criteria to control the message flow according to his individual requirements. Therefore, there may be a case where the filter function setting differs from manager to manager, so that content-wise different state information is handled by the concurrent realignment procedures.

FIG 4 zeigt den Nachrichtenfluß zwischen einem Agent AG - im dargestellten Beispiel gemäß der FIG 1 dem Betriebs- und Wartungszentrum OMC1 oder im dargestellten Beispiel der FIG 2 dem Basisstationssystem BSS11 - und dem Manager MA1, MA2 - im Beispiel gemäß der FIG 1 den unterschiedlichen Netzmanagementzentren NMC1, NMC2 oder im Beispiel der FIG 2 den verschiedenen Applikationen OF1, OF2. FIG. 4 shows the message flow between an agent AG - in the example shown according to the FIG. 1 the operation and maintenance center OMC1 or in the example shown the FIG. 2 the base station system BSS11 - and the manager MA1, MA2 - in the example according to the FIG. 1 the different network management centers NMC1, NMC2 or in the example of FIG. 2 the different applications OF1, OF2.

Der Nachrichtenfluß erfolgt vorzugsweise mit standardisierten M-EVENT-REPORT Services sowie einem zu Anfang initiierten M-CREATE Service. Dieses sind generische CMISE-standardisierte (Common Management Information Service Element) Prozeduren, die gemäß ITU-T X.710 definiert sind. Die ITU-T X.731 definiert das Management einer standardisierten Übertragung von Zustandsinformationen, die gemäß den M-EVENT-REPORT Services durchgeführt wird. Die Korrelationsinformationen werden in die Nachrichten bzw. in bestimmte Nachrichtenfelder eingetragen. Des weiteren versehen die Manager MA1, MA2 die Parameter zur Steuerung des Informationsabgleichs mit bestimmten Parameterwerten und tragen sie einzeln oder mehrfach in die jeweilige Anforderungsnachricht ein. Das Beispiel in FIG 4 zeigt den Nachrichtenfluß anhand einzelner Nachrichten, wobei diese parallel zwischen dem Agent AG und den Managern MA1, MA2 oder seriell zwischen dem Agent AG und dem einzelnen Manager MA1 übertragen werden können.The message flow is preferably carried out with standardized M-EVENT-REPORT services and an initially initiated M-CREATE service. These are generic CMISE-standardized (Common Management Information Service Element) procedures defined in accordance with ITU-T X.710. The ITU-T X.731 defines the management of a standardized transmission of Condition information performed according to the M-EVENT-REPORT services. The correlation information is entered in the messages or in certain message fields. Furthermore, the managers MA1, MA2 provide the parameters for controlling the information matching with specific parameter values and enter them one or more times into the respective request message. The example in FIG. 4 shows the message flow on the basis of individual messages, which can be transmitted in parallel between the agent AG and the managers MA1, MA2 or serially between the agent AG and the individual manager MA1.

Sobald nach einer Unterbrechung der Verbindung die Kommunikation zwischen dem Manager MA1, MA2 und dem Agent AG wiederhergestellt ist, sendet jeder Manager MA1, MA2 gemäß dem M-CREATE Service eine Anforderungsnachricht staAS (start Alignment Scheduler) zum Übermitteln der Zustandsinformationen für den Informationsabgleich an den Agent AG. Vorzugsweise wird die vom Manager MA1, MA2 definierte Korrelationsinformation staAH (state Alignment Handle) - beispielsweise im definierten Nachrichtenfeld "actionInformation" - mitgesendet, die eine direkte Zuordnung der Anforderung zu den nachfolgend empfangenen Agent-Nachrichten kennzeichnet. Damit ist bei mehreren Managern die aktuelle Anforderung auch dem jeweiligen Manager zuordenbar, sodaß die parallelen Realignments der Manager voneinander unabhängig initiiert, durchgeführt und beendet werden können.As soon as the communication between the manager MA1, MA2 and the agent AG is restored after an interruption of the connection, each manager MA1, MA2 sends according to the M-CREATE service a request message staAS (start Alignment Scheduler) for transmitting the status information for the information matching to the Agent AG. The correlation information staAH (state alignment handle) defined by the manager MA1, MA2 is preferably also sent in, for example, in the defined message field "actionInformation", which identifies a direct assignment of the request to the subsequently received agent messages. Thus, with several managers, the current requirement can also be assigned to the respective manager, so that the parallel realignments of the managers can be initiated, executed and terminated independently of one another.

Die Anforderungsnachricht staAS enthält auch vom Manager eingetragene Parameterwerte für den nachfolgenden Funktionsablauf. Die Parametrisierung kann vorzugsweise mit einem oder mehreren eingestellten Parameterwerten durchgeführt werden, von denen die Werte begT (begin Time), endT (end Time), int (interval), admST (administrative State) und relEN (related Entities) beispielhaft angegeben sind. Durch die spezifischen Parameterwert werden beschrieben:

  • ein Start-Zeitpunkt (begT), beispielsweise Datum und Uhrzeit, für einen automatischen Informationsabgleich und/oder ein Ende-Zeitpunkt (endT), beispielsweise Datum und Uhrzeit, für den automatischen Informationsabgleich,
  • ein Zeitintervall (int), beispielsweise in Minuten, Stunden, Tagen usw., für eine Wiederholung des automatischen Informationsabgleichs,
  • ausgewählte Ressourcen (relEN), für die die geänderten Zustandsinformationen vom Agent zu übermitteln sind,
  • den Abbruch (admST) eines laufenden Informationsabgleichs, wobei nach - auch ein Wiederfortsetzen der Alignment-Prozudur
  • mit dem Wert admST=unlock - möglich ist. Die Parameterwerte begT...admST sind in einem gemäß dem Standard vorgegebenen Nachrichtenfeld des M-CREATE Service enthalten, um bereits vorhandene und definierte Felder mitbenutzen zu können.
The request message staAS also contains parameter values entered by the manager for the following functional sequence. The parameterization may preferably be carried out with one or more adjusted parameter values, of which the values begin (begin time), endT (end time), int (interval), admST (administrative state) and relEN (related entities) are given by way of example. The specific parameter values describe:
  • a start time (begT), such as date and time, for automatic information reconciliation and / or an end time (endT), for example date and time, for the automatic reconciliation of information,
  • a time interval (int), for example in minutes, hours, days, etc., for a repetition of the automatic reconciliation of information,
  • selected resources (relEN) for which the changed state information is to be transmitted by the agent,
  • the cancellation (admST) of a current information comparison, whereby after - also a resumption of the Alignment Prozudur
  • with the value admST = unlock - is possible. The parameter values begT ... admST are contained in a default message field of the M-CREATE service in order to be able to share already existing and defined fields.

Im Anschluß an die Auswertung der Parameter in der empfangenen Anforderungsnachricht staAS überprüft der Agent, ob Änderungen der Zustandsinformationen anhand von Abweichungen gegenüber dem Normalzustand vorliegen und bereitet für jedes gemanagte Objekt, das sich nicht im Normalzustand befindet, die geänderten Zustandsinformationen auf. Dies erfolgt vorzugsweise mit den Zustands- und Statusattributen gemäß der Beschrebung zu FIG 3. Der Agent AG führt den Informationsabgleich fort, indem er eine Startnachricht stSA (start State Alignment) erzeugt und die von ihr definierte Korrelationsinformation aliNI (alignment Notification Id) in diese Nachricht einfügt. Auch die von dem Manager vergebene und übersandte Korrelationsinformation staAH ist in einem bestimmten Nachrichtenfeld der Startnachricht stSA enthalten. Die Korrelationsinformation aliNI ist beispielsweise in dem standardisierten Nachrichtenfeld "notification Identifier" der Nachricht stSA eingetragen. Beide Informationen staAH, aliNI werden gemeinsam in der Nachricht stSA vom Agent AG zu den Managern MA1, MA2 ausgesendet. Dadurch können "alignmentbezogene" M-EVENT-REPORT Nachrichten verschiedener M-CREATE Anforderungen voneinander unterschieden werden, aber auch von regulären M-EVENT-REPORT Nachrichten, die mit dem Informationsabgleich nichts zu tun haben. Eine Alignment-Prozedur stoppt nämlich nicht zwingend andere M-EVENT-REPORT Nachrichten, die während der Alignment-Prozedur spontan auftreten und an den oder die Manager gesendet werden.Subsequent to the evaluation of the parameters in the received request message staAS, the agent checks whether changes of the state information are present based on deviations from the normal state and prepares the changed state information for each managed object that is not in the normal state. This is preferably done with the state and status attributes according to the intent FIG. 3 , The agent AG continues the information comparison by generating a start message stSA (Start State Alignment) and inserting the correlation information aliNI (alignment Notification Id) defined by it in this message. The correlation information staAH assigned and transmitted by the manager is also contained in a specific message field of the start message stSA. The correlation information aliNI is entered, for example, in the standardized message field "notification identifier" of the message stSA. Both information staAH, aliNI are sent together in the message stSA from the agent AG to the managers MA1, MA2. This allows "alignment-related" M-EVENT-REPORT messages of different M-CREATE requests to be distinguished from each other, but also from regular ones M-EVENT-REPORT Messages that have nothing to do with the reconciliation of information. This is because an alignment procedure does not necessarily stop other M-EVENT-REPORT messages that occur spontaneously during the alignment procedure and are sent to the manager (s).

Nach dem - vorzugsweise vom Manager MA1, MA2 durch zumindest einen Parameter gesteuerten automatischen Start des Informationsabgleichs - sendet der Agent AG in aufeinanderfolgenden Nachrichten staCN (state change notification) unter Verwendung des M-EVENT-REPORT Service nur die aufbereiteten geänderten Zustandsinformationen cst zum anfordernden Manager MA1, MA2 zurück. Vorzugsweise wird in einer Nachricht staCN nur die für ein Objekte und die damit assoziierte Ressource ermittelten Zustandsänderungen cst übertragen, sodaß bei mehreren, gegebenenfalls unterschiedlichen Objekten auch mehrere Nachrichten staCN benötigt werden. Dabei weist jede Nachricht staCN die Korrelationsinformation aliNI - beispielsweise in dem definierten Nachrichtenfeld "correlated Notifications" - auf. Nach der letzten M-EVENT-REPORT Nachricht jedes Informationsabgleichs generiert der Agent AG eine Endenachricht endA (end Alignment), die die Korrelationsinformation aliNI enthält. Für den Fall, daß zum Zeitpunkt des M-CREATE Service alle gemanagten Objekte sich im Normalzustand befinden oder wenn die Nachrichten mit den Zustandsänderungen von den aktuellen Filtereinstellungen aussortiert werden, folgt die Endenachricht endA unmittelbar auf die Startnachricht stSA. Der obige Nachrichtenfluß wiederholt sich für jedes "State-Alignment", bis das Ende des automatischen Informationsabgleichs - erkennbar am Parameterwert endT - erreicht ist. Auch wenn das zu FIG 4 beschriebene Beispiel sich auf parallel Realignments zu mehreren Managern bezieht, kann der Nachrichtenfluß selbstverständlich auf mehrere, von einem einzigen Manager nacheinander ausgelöste Anforderungen für die Behandlung von Zustandsinformationen gemäß dem "State-Alignment" angewendet werden. Dies bringt den Vorteil mit sich, daß durch die eindeutige Zuordnung anhand der Korrelationsinformationen für den einzelnen Manager die Möglichkeit besteht, die eintreffenden Antworten des Agent auch bei Nichteinhalten der Reihenfolge eindeutig den Anforderungen zuordnen zu können - beispielsweise unterschiedlichen Anwendungen im Manager. Nacheinander gesendete Anforderungen können sich gegebenenfalls gegenseitig überholen, beispielsweise dann, wenn zwischen Agent und Manager ein Paketnetz durchlaufen wird.After the automatic start of the information comparison, which is controlled by at least one parameter by the manager MA1, MA2, the agent AG sends in consecutive state change messages staCN using the M-EVENT-REPORT service only the processed changed state information cst to the requesting manager MA1, MA2 back. Preferably, only the status changes cst determined for an object and the resource associated therewith are transmitted in a message staCN, so that a plurality of messages, possibly different objects, also require a plurality of messages staCN. In this case, each message staCN the correlation information aliNI - for example, in the defined message field "correlated notifications" - on. After the last M-EVENT-REPORT message of each information match, the agent AG generates an end message endA, which contains the correlation information aliNI. In the event that all managed objects are in the normal state at the time of the M-CREATE service or if the messages with the status changes are sorted out from the current filter settings, the end message endA immediately follows the start message stSA. The above message flow is repeated for each "state alignment" until the end of the automatic information adjustment - recognizable by the parameter value endT - is reached. Even if that too FIG. 4 Of course, while the example described relates to parallel realignments to multiple managers, the flow of messages may of course be applied to multiple requests initiated by a single manager for the treatment of state information according to the "state alignment". This has the advantage that the unique assignment based on the correlation information it is possible for the individual manager to clearly assign the incoming responses of the agent to the requirements, even if the order is not followed - for example, different applications in the manager. Subsequent requests may overtake each other, for example, when a packet network is traversed between agent and manager.

Claims (22)

  1. A method for processing state information in a communication system through a management network having a number of management levels (A, B, C), with the state information being transmitted for a synchronisation of information between an agent (AG) of a management level (B, C) and at least one manager (MA1, MA2) of a higher management level (A, B), in which
    - a request message (staAS) for synchronising the information is sent by at least one of the managers to the agent, and
    - in response, only that state information is sent by the agent in one or more consecutive messages (staCN) to at least one of the managers for which a deviation from a normal state of the state information was established by the agent.
  2. Method according to claim 1
    In which state attributes (OST, AST, UST) and/or status attributes (UNS, ALS, AVS) are used as state information.
  3. Method according to claim 2,
    In which the normal state is defined on the basis of predeterminable values for the state attributes and/or status attributes.
  4. Method according to one of claims 2 or 3,
    in which the state attributes that serve to identify the operational readiness, ability to be managed and the use of a resource looked after by an agent in the communication system.
  5. Method according to one of claims 2 to 4,
    in which the status attributes for a resource looked after by an agent in the communication system specify whether it is in an unknown state, in an alarm state or in a state of availability.
  6. Method according to one of the previous claims,
    In which correlation information (staAH) for an assignment of the respective request to the messages received by the agent is sent along with the modified state information by the manager in the request message.
  7. Method according to one of the previous claims,
    In which, in a message (stSA) for starting information synchronisation, correlation information (aliNI) for an assignment of the subsequently sent messages (staCN) is sent along with the changed state information for the information synchronisation started in each case.
  8. Method according to claim 7,
    in which the correlation information (aliNI) created by the agent is sent in the message or messages (staCN) along with the changed state information.
  9. Method according to one of the previous claims,
    In which the information synchronisation is controlled by the manager depending on at least one parameter (par) sent to the agent.
  10. Method according to claim 9,
    In which the information is automatically initiated by the agent through a parameter.
  11. Method according to claim 10,
    in which a parameter is provided by the manager with a parameter value (begT) which specifies a begin time for the automatic information synchronisation.
  12. Method according to one of claims 9 to 11,
    in which a parameter is provided by the manager with a parameter value (endT) which specifies an end time for the automatic information synchronisation.
  13. Method according to one of claims 9 to 12,
    in which a parameter is provided by the manager with a parameter value (int) which specifies a time interval for a repetition of the automatic information synchronisation.
  14. Method according to one of claims 9 to 13,
    in which a parameter is provided by the manager with a parameter value (relEN) which identifies the resources for which changed state information is to be transferred by the agent.
  15. Method according to one of claims 9 to 14,
    in which a parameter (par) is provided by the manager (MA1, MA2) with a parameter value (admS) through which an ongoing information synchronisation can be interrupted.
  16. Method according to one of claims 9 to 15,
    In which the parameter or parameters (par) is or are sent by the manager in the request message (staAS) to the agent (AG).
  17. Method according to one of the previous claims,
    In which the possibility of communication is not guaranteed because of a connection break and/or an initialisation of the agent and/or of the manager.
  18. Communication system for carrying out one of the previous methods.
  19. Method according to one of the previous claims in which the normal state is able to be set.
  20. Method according to one of the previous claims in which the normal state is produced from a combination of individual values of the state information.
  21. Agent (AG) of a management level (B, C) for handling state information in a communication system with a management network comprising a number of management levels (A, B, C), with the state information being transmitted for an information synchronisation between the agent and at least one manager (MA1, MA2) of a higher management level (A, B), comprising means
    - for receiving a request message (staAS) for carrying out the information synchronisation sent by at least one of the managers to the agent, and
    - for subsequently sending only that state information in one or more consecutive messages (staCN) to at least one of the managers in which a deviation was established by the agent from a normal state of the state information.
  22. Manager (MA1, MA2) of a higher management level (A, B) for handling state information in a communication system with a management network featuring a number of management levels (A, B, C), with the state information being transmitted for information synchronisation between an agent of a management level (B, C) and at least the manager (MA1, MA2), comprising means
    - for sending a request message (staAS) for carrying out the information synchronisation to the agent according to which only that state information is to be sent by the agent to at least the manager in which a deviation from a normal state of the state information is established by the agent,
    - for receiving one or more consecutive messages with which the agent, on receipt of a request message (staAS), sent by the manager to the agent for executing the information synchronisation, only sends that state information to at least one of the managers for which the agent has established a deviation from a normal state of the state information, and
    - to thus synchronise state information which is known to both the manager and also the agent, so that the state information known to the manager corresponds to the actual state information of the agent.
EP99929089A 1998-05-11 1999-05-03 Method and communication system for processing state information in a management network having different management levels Expired - Lifetime EP1145538B1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
DE19821032 1998-05-11
DE19821032 1998-05-11
PCT/DE1999/001309 WO1999059326A2 (en) 1998-05-11 1999-05-03 Method and communication system for processing state information in a management network having different management levels

Publications (2)

Publication Number Publication Date
EP1145538A2 EP1145538A2 (en) 2001-10-17
EP1145538B1 true EP1145538B1 (en) 2010-09-01

Family

ID=7867383

Family Applications (1)

Application Number Title Priority Date Filing Date
EP99929089A Expired - Lifetime EP1145538B1 (en) 1998-05-11 1999-05-03 Method and communication system for processing state information in a management network having different management levels

Country Status (7)

Country Link
EP (1) EP1145538B1 (en)
JP (1) JP2002519874A (en)
CN (1) CN1282328C (en)
CA (1) CA2331899C (en)
DE (1) DE59915199D1 (en)
ES (1) ES2351892T3 (en)
WO (1) WO1999059326A2 (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6697970B1 (en) * 2000-07-14 2004-02-24 Nortel Networks Limited Generic fault management method and system
EP1227616B1 (en) * 2001-01-26 2006-11-08 Siemens Aktiengesellschaft Method, program and arrangement for synchronization of a network manager with a network agent
DE10345881A1 (en) * 2003-09-30 2005-04-14 Siemens Ag Method for synchronizing alarms in a management system of a communication network
EP1655974A1 (en) 2004-11-08 2006-05-10 Siemens Aktiengesellschaft Method and apparatuses for information alignment between a manager and an agent in a management network
US7966524B2 (en) 2007-10-19 2011-06-21 Citrix Systems, Inc. Systems and methods for gathering and selectively synchronizing state information of at least one machine

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5317568A (en) * 1991-04-11 1994-05-31 Galileo International Partnership Method and apparatus for managing and facilitating communications in a distributed hetergeneous network

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
IT1271326B (en) * 1994-12-23 1997-05-27 Sits Soc It Telecom Siemens PROCEDURE FOR AUTOMATIC REALIGNMENT IN THE EVENT REPORT IN A MANAGEMENT SYSTEM AND RELATED SYSTEM
SE504072C2 (en) * 1995-02-08 1996-11-04 Ericsson Telefon Ab L M Device management and method of communication and a telecommunication system with a management device
US5930476A (en) * 1996-05-29 1999-07-27 Sun Microsystems, Inc. Apparatus and method for generating automatic customized event requests

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5317568A (en) * 1991-04-11 1994-05-31 Galileo International Partnership Method and apparatus for managing and facilitating communications in a distributed hetergeneous network

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ABSTRACT ARTICLE: "Information technology - Open Systems Interconnection - Systems Management: Event report management function; X.734 (09/92)", ITU-T STANDARD IN FORCE (I), no. X.734, 10 September 1992 (1992-09-10), INTERNATIONAL TELECOMMUNICATION UNION, GENEVA, CH, XP017404181 *
RAY HUNT: "SNMP,SNMPv2 and CMIP - the technologies for multivendor network management", COMPUTER COMMUNICATIONS, vol. 20, 1997, pages 73 - 88 *

Also Published As

Publication number Publication date
CN1561643A (en) 2005-01-05
ES2351892T3 (en) 2011-02-11
JP2002519874A (en) 2002-07-02
CN1282328C (en) 2006-10-25
DE59915199D1 (en) 2010-10-14
CA2331899C (en) 2009-04-28
CA2331899A1 (en) 1999-11-18
WO1999059326A3 (en) 2001-10-04
EP1145538A2 (en) 2001-10-17
WO1999059326A2 (en) 1999-11-18

Similar Documents

Publication Publication Date Title
EP1034639B1 (en) Method and communication system for processing alarms in a management network with several management levels
EP1050170B1 (en) Method and communication system for processing alarms using a management network involving several layers of management
EP0973342B1 (en) Method and communication system for processing alarms in a network with several management layers
EP1058983B1 (en) Method and communication system for processing alarms using a management network involving several layers of management
EP1810523B1 (en) Method and products for aligning data between a manager and an agent in a management network
DE60220375T2 (en) Specific data registration server in a telecommunication system operating and management center
EP1668822B1 (en) Method for synchronizing alarms in a management system of a communications network
EP1206883B1 (en) Generic alignment method in a multi-manager environment
EP1145538B1 (en) Method and communication system for processing state information in a management network having different management levels
EP1730886B1 (en) Method and devices for distributing management information in a management network of a communications system
DE19740718C2 (en) Realignment procedure between an operations and maintenance center and a higher-level network management center
EP1582030B1 (en) Method for handling alerts by means of a management network comprising several levels in a communication system
EP1749369B1 (en) Method and devices for operating a management network in the event a manager fails
EP1612993B1 (en) Method and arrangement for changing the operation mode of an agent of a management network
EP1703667A1 (en) Network management using a master-replica method
EP2002601A1 (en) Location of unidirectional handover relationships
EP1091596A2 (en) Extented management notification service to reduce communication between an agent and a manager
EP1089576A1 (en) Network management
EP1148742A1 (en) Method and system for processing of event reports in a telecommunication network

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: 20000907

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): DE ES FR GB SE

XX Miscellaneous (additional remarks)

Free format text: DERZEIT SIND DIE WIPO-PUBLIKATIONSDATEN A3 NICHT VERFUEGBAR.

PUAK Availability of information related to the publication of the international search report

Free format text: ORIGINAL CODE: 0009015

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): DE ES FR GB SE

RIC1 Information provided on ipc code assigned before grant

Free format text: 7H 04Q 3/00 A, 7H 04L 12/24 B

17Q First examination report despatched

Effective date: 20070810

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE ES FR GB SE

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Free format text: NOT ENGLISH

XX Miscellaneous (additional remarks)

Free format text: DERZEIT SIND DIE WIPO-PUBLIKATIONSDATEN A3 NICHT VERFUEGBAR.

REF Corresponds to:

Ref document number: 59915199

Country of ref document: DE

Date of ref document: 20101014

Kind code of ref document: P

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Effective date: 20110201

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100901

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20110606

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 59915199

Country of ref document: DE

Effective date: 20110606

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 18

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: ES

Payment date: 20160627

Year of fee payment: 18

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 19

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20170508

Year of fee payment: 19

Ref country code: FR

Payment date: 20170526

Year of fee payment: 19

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20170721

Year of fee payment: 19

REG Reference to a national code

Ref country code: ES

Ref legal event code: FD2A

Effective date: 20180626

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170504

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 59915199

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20180503

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181201

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180503

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180531