WO1997024835A1 - Procede de gestion d'un reseau de telecommunications - Google Patents

Procede de gestion d'un reseau de telecommunications Download PDF

Info

Publication number
WO1997024835A1
WO1997024835A1 PCT/FI1996/000688 FI9600688W WO9724835A1 WO 1997024835 A1 WO1997024835 A1 WO 1997024835A1 FI 9600688 W FI9600688 W FI 9600688W WO 9724835 A1 WO9724835 A1 WO 9724835A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
value
stored
objects
managed
Prior art date
Application number
PCT/FI1996/000688
Other languages
English (en)
Inventor
Graham French
David Bending
Original Assignee
Nokia Telecommunications Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Telecommunications Oy filed Critical Nokia Telecommunications Oy
Priority to AU11965/97A priority Critical patent/AU1196597A/en
Publication of WO1997024835A1 publication Critical patent/WO1997024835A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0062—Provisions for network management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13503—Indexing scheme relating to selecting arrangements in general and for multiplex systems object-oriented systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13547—Indexing scheme relating to selecting arrangements in general and for multiplex systems subscriber, e.g. profile, database, database access

Definitions

  • the present invention relates to a management method according to the preamble of the attached claim 1 for managing a telecommunications network.
  • the telecommunications network to be managed may be e.g. a SDH (Synchronous Digital Hierarchy) network, a PDH (Plesiochronous Digital Hierarchy) network, or a combination of such networks.
  • the basic situation in network management is usually such that an operator managing a telecom ⁇ munication networks, e.g. a telephone company, has a plurality of customers (i.e. network users) in addi- tion to the physical network.
  • the operator sells the customers various services that utilize the network.
  • a public network will be used herein as an example ; in principle, however, the same description applies to a private operator managing e.g. an organization network
  • the operator utilizes a number of facilities or operative processes for the provision of customer services . These oper ⁇ ative processes can be divided into groups in accord- ance with the functions for which they are intended :
  • Service Provisioning taking care of the performance of customer services, including e.g. invoicing customers for services.
  • network management takes place on several different levels, depending on the extent to which the functions to be performed on a specific level are associated with the overall manage ⁇ ment of the operator enterprise.
  • the management of a telecommunications network is generally divided into four different levels, which are from bottom to top as follows:
  • This division is used e.g. in the ITU-T (the former CCITT) recommendation M.3010, which specifies a kind of framework for the management architecture of a telecommunications network.
  • the bottom layer below the above four layers is the equipment itself; these equipments are managed by installation and field engineering tools.
  • the network element management layer means the management of an individual network element (such as a multiplexer or a cross-connection device) as a separ- ate component without simultaneously paying attention to the condition of the network or other network elements.
  • the majority of so called "network mana ⁇ gement" systems commercially available today are actu ⁇ ally network element management systems within this layer.
  • the network management layer is concerned with the management of the entire telecommunications net ⁇ work, such as overall management of network con ⁇ nections.
  • One example is the creation of connections and the end-to-end supervision of their condition. This means that e.g. alarms detected on equipment are not just displayed against that equipment, but they are also propagated to show what services (paths and circuits) are affected by the fault, if any.
  • the present invention is positioned in this layer.
  • the service manage ⁇ ment layer is not concerned with technical network management. It takes care of e.g. customer data, supervision of services provided to customers, invoic- ing for services, and considering needs for services of different types.
  • the business management layer is used to monitor and plan the business activities and economy of the entire enterprise, resulting in decisions affecting the lower levels.
  • the above-mentioned recommendation M.3010 specifies the management architecture as shown in Figure 1.
  • the architecture basically consists of one or more operations systems OS connected to a data communication network DCN communicating with an actual telecommunications network which is to be managed and which includes the network elements NE managed. It is to be noted that the connections of the data communications network and those of the telecommunications network are logically distinct, although they can be implemented physically in one and the same cable. Logically, there are thus two networks: (a) a network providing services to customers, and (b) a network maintaining the service provisioning network.
  • the management of certain transmission equipments further requires a separate Mediation Device MD, which mainly acts as a protocol converter between a Q3 interface complying with the recommendations and transmission equipments that do not understand the protocol applied in the interface but use their own proprietary protocol.
  • New SDH equipment for instance, can be connected directly to the Q3 interface, whereas older PDH equipment requires a Mediation Device.
  • a management network for a combined SDH and PDH network may be e.g. such as shown in Figure 2.
  • Users sitting at the operation centre use network management work stations WS connected to a separate local area network SN, which may be e.g. an Ethernet network.
  • the management system is typically distributed in several computers of the local area network, one of the computers being a dedicated application server SRV having a database DB containing information necessary for managing the network.
  • the local area network further comprises e.g. necessary back-up devices (like DAT drives or mirrored disks) and event-logging printers (not shown) .
  • the management system is connected via the above-mentioned Q3 interface e.g. to the SDH network.
  • the interface may be e.g. an X.25 type packet switched interface or an Ethernet LAN interface.
  • the packet switched interface is useful if the operator in charge of the network management also otherwise uses a packet switched network.
  • Such control channels established in the overhead bytes are called Embedded Control Channels, and they are formed e.g. in the STM-1 frame by the section overhead bytes Dl to D12.
  • PDH equipments on the contrary, need manu acturer-specific solutions, wherefore they have to be connected to the management system through a separate mediation device 22.
  • the management system may also be hierarchical so that different geographical areas have their own smaller management systems that together form an integral management network. For instance, a management system covering one country may be divided geographically into smaller management systems operating in different parts of the country. Each smaller management system takes care of the management of the network portion in the concerned geographical area.
  • management systems MSI and MS2 geographically apart from each other form together a single common management system and management network.
  • Objects are data structures in a network management system, which describe the functions and state of a network component.
  • An object is thus an element having certain attributes ("I am like this") and certain operations ("I can do these things") .
  • objects with the same data structure (attributes) and the same behaviour (operations) are grouped into a class.
  • a specific implementation of an operation is called a method and each object is said to be an instance of its class.
  • a typical object is e.g. a cross- connection device with certain attributes (cross- connections that are active) and certain methods (e.g. make cross-connection and release cross-connection) .
  • objects can be physical ones or logical ones.
  • Physical objects are elements that form part of the physical network. Such objects are e.g. the above- mentioned network elements (a network element is any piece of telecommunication equipment that works as a single unit to provide telecommunication functions) or physical connections (such as optical fibres, twisted pair cables, coaxial cables, radio links or satellite links) .
  • Logical objects are logical entities that do not form a single piece of the physical network. Such objects are e.g. paths and circuits.
  • a path is a connection of a fixed bit rate and format between two physical interfaces within the network.
  • a circuit is a connection set up for a customer, between two physical interfaces on the boundary of the network.
  • a circuit usually comprises several consecutive paths.
  • a network object may have a number of different attributes. Some attributes (such as "fault state”) are used by several different types of object. In addition, for some types of network object (such as a route) , it is convenient to define an attribute which consists of a collection of other attributes. Typical attributes are e.g. "availability status", "fault state” and "operational state”. The attributes have different possible values, e.g. "fault state” can have values: - OK. There are no problems.
  • the "operational state”, in turn, can have e.g. two different values:
  • the object can operate, either completely or in part.
  • the object cannot operate at all.
  • objects are used to represent the fundamental items with which the management system works, e.g. network elements, paths and users.
  • the management system needs to obtain copies of these objects from the persistent storage.
  • the objects can be fetched by their internal unique identifier if this is known, or by performing a search of the objects using search criteria which define a group of conditions which an object must match to be selected.
  • events are passed around to various processes. An event may originate from e.g. from the network to be managed or it may occur as a result of the user actions, e.g. when the user gives a command from the workstation.
  • filtering/selecting is a way of specifying the information you are interested in.
  • the criteria which can be used for filtering evolve over time, as different objects are included in the system (as a result of e.g. changes in the network to be managed) . Therefore, the problem relating to filtering is how to get a method which allows new type of data and new type of objects to be added easily in the system, without effecting the ability to apply all filters to all objects and all events. The possibility to apply all filters to all objects should remain even if the objects do not have the attributes which are being filtered upon.
  • the idea of the present invention is to find at a selection/filtering point of the system the value of an attribute in an objec /event, apply a predetermined stored operation to that value and another value which is stored in the system, and evaluating the result.
  • the above steps are repeated as many times as the stored filtering information shows and the results are then combined, using the stored filtering information, to get a final result for the filter.
  • the final result determines whether the event is filtered (or the object selected) .
  • filtering can be applied to any object without any special knowledge of the type or attributes of the object to be filtered.
  • the method is also generic, extensible and typesafe, i.e. it can use the comparisons appropriate for the attribute being filtered and copes with objects not containing that attribute.
  • Figure 1 illustrates a telecommunications network management architecture
  • Figure 2 shows an example of a management network for a combined SDH and PDH network
  • FIG. 3 illustrates the functional architecture of the management system according to the present invention in its basic form
  • Figure 5 is a flow chart describing how a filter is applied to searching for objects from the database
  • Figure 6 is a flow chart which illustrates evaluating an AVA.
  • Figure 7 illustrates the method according to the invention when a filter is applied to an object which it matches, and
  • Figure 8 illustrates the method according to the invention when a filter is applied to an object which it does not match.
  • the management system shown in Figure 3 will first be referred to, the system having such a functional architecture that the greatest possible benefit will be derived from filtration.
  • a system with this kind of architecture is able to operate e.g. in the system shown in Figure 2.
  • the system comprises a single core part CP and one or more peripheral parts PP1...PPN, which are connected to the core part of the system.
  • each peripheral part is intended for one user (operator employee) of the system.
  • the system typically has a dedicated core com ⁇ puter, such as a server SRV (also shown in Figure 2) .
  • the core part of the system keeps up an updated model of the state and operation of the telecommunications network TN to be managed, of which a single network element is shown in the figure. As described earlier, the core part uses objects to keep up this model.
  • the core computer SRV is connected to one or several work- stations WS1...WSN each including one peripheral part.
  • An application (indicated with the references APPLNl ...APPLN4 in Figure 3) is a functional system block which allows the user to configure the network and view network events on the screen of the work ⁇ station.
  • the application is thus a system part offer- ing the system's services to the user.
  • An individual workstation is therefore also called an application server.
  • a Session Handler SH is a functional system part that handles a single user's session with the system and forwards messages between the core and the user's applications.
  • the Session Handler can be associated with the initial system log-on window through which a user logs on and establishes a session with the core.
  • the Session Handler starts up various applications according to commands given by the user.
  • the Session Handler performs the necessary closing-down and deregistering operations to terminate the session (the term registering will be explained later) .
  • a Core Access Process CAP verifies that the
  • Session Handler belongs to a known user on a known host. Having done so, it acts as the gateway to the system core. For each CAP in the core part there is a corresponding Session Handler in the peripheral part.
  • a Database Process DP controls access to the database DB to store persistent information (master objects of the management system) .
  • the main function ⁇ ality of this process is:
  • the Modelling Process MP is responsible for maintaining the currency of the core's model of the network to be managed and dealing with changes to it.
  • the main functions of the Modelling Process are:
  • the Interface Process IP is a functional system part that converts data from the external world (data from the network to be managed) into the internal world of the management system. As far as the system user is concerned, he or she just sees a network element NE, like a multiplexer or a cross-connect device, without having to know the manufacturer or the version of the device. Different types of Interface Processes are used for different classes of equipment.
  • the main functionality of each IP is: to monitor the network for events and to exchange notifications with the network,
  • Interface Processes could also be included in the core part, but Figure 3 shows them separate, as they form the interface of the management system with the external world.
  • a Fault Propagation Agent Process FPAP is a functional system part that works out the actual impact of a received event in the system.
  • the FPAP uses information about the object class in question. This information it receives from the Database Process DP.
  • the database DB must store information e.g. about individual net ⁇ work elements and interconnections and interrelations between the network elements, the operations the net- work elements are capable of performing, and the ser ⁇ vices provided by the network elements.
  • This informa ⁇ tion is stored in the form of an object model repre ⁇ senting the transmission network TN in terms of objects and their attributes and methods performed on these attributes.
  • an object is the representa ⁇ tion, in the object model, of one of the resources to be managed.
  • An application uses these objects that form the image of the network to be managed within the system. Therefore, they have to get objects from the core part of the system.
  • An application can also create a new core object to database DB, e.g. as a result of a user command.
  • the Applications also register to receive various events.
  • the registration is passed to the Session Handler and further to the core part of the system.
  • the registration is stored in the form of a filter Fl in association with the Database Process DP.
  • This filter finds out on the basis of the event type, to which Core Access Processes and to which applications a certain type of event is to be transmitted (i.e. what users are interested in a certain type of event) .
  • Events from the core of the system are duplicated in the Session Handler and sent to all applications which have registered to receive them. In this way, all of the user's applications can receive the event at the same time, so that information presented to the user by the different applications is consistent.
  • the core part of the system knows to which application a certain event has to be trans ⁇ mitted. This also allows unwanted events to be filter ⁇ ed out as soon as possible (in the core) and reduces the bandwidth used between applications and the core part of the system.
  • the core part is thus able to filter events up to the application level. It is also possible to use filters in steps so that the core part knows only up to the level of the Session Handler what event has to be transmitted to the peripheral part.
  • the Session Handler thereafter has a new filter, which indicates in which event a specific application inside the concerned Session Handler is interested.
  • the first alternative is to be preferred in that it does not make the peripheral part (Session Handler) too complicated.
  • part of the objects stored in the core part of the management system are also placed as copies in a cache CH at each Session Handler SH.
  • a cache is a certain kind of memory, in this connection caching means only that a copy of something is kept to get fast access to it.
  • the Session Handler has a copy of any object an application has fetched from the core part of the system.
  • the Session Handler thus also stores object-specific information indicating which one of its applications uses a specific object. This information can be stored e.g. in the form of a table TBLl shown in Figure 3.
  • the core part correspondingly knows which Session Handler has a copy of a specific master object. This information can be stored in the form of a table TBL2 in association with the Database Process.
  • the Session Handler has no copies of objects.
  • the application needs a copy for the first time, the copy is fetched from the core part.
  • the Session Handler is able to keep up a table (TBLl) indicating which application uses a specific object, and the Database Process is able to keep up a table indicating which Session Handler uses a copy of a specific master object.
  • TBLl table indicating which application uses a specific object
  • the Database Process is able to keep up a table indicating which Session Handler uses a copy of a specific master object.
  • an application fetches an object of which the Session Handler already has a copy
  • the application receives a copy of the object from the Session Handler without having to interact with the core part of the system.
  • the application ceases using an object, it transmits a message as an indication of this to the core part through the Session Handler, as a result of which the copy is removed from the memory of the Ses ⁇ sion Handler and the tables are updated accordingly.
  • the object is needed again, the copy is fetched from the core in the same way as at the system start ⁇ up.
  • the Session Handler immediately com ⁇ municates them to all other applications in the session that use said object.
  • the Session Handler receives information on the change from the application making the change, updates its own copy, and passes the events to all other applications using said object.) These changes are also transmitted through the Session Handler to the core, which reapplies the changes to the master objects to keep the state of the master copies consistent with the state of the copies in the peripheral part.
  • the present invention relates to the operation of filters (like filter Fl in the above described system) for selecting objects, or for filtering of events, in a management system, which was described briefly above by means of an example.
  • filters like filter Fl in the above described system
  • This above- described example of the system is advantageous in the sense that it allows the bandwidth used between the applications and the core part to be reduced efficiently by filtration.
  • selecting objects will be used as an example in the text below, it is to be understood that filtering of objects or events could equally well be used as an example.
  • selection criteria used to perform filtering are stored assertions about the values of attributes of the objects stored in the system. These assertions are data sets which are here called as Attribute Value Assertions, abbreviated to A V A s .
  • a stored filter is a collection of AVAs linked together by logical operators (i.e. AND, OR and NOT) .
  • Figure 5 shows how filters are used to search for objects from the database.
  • First a filter to be used is created (stage 511) or a previously stored filter is retrieved from the database (stage 512) .
  • the first object is then retrieved from the database
  • stage 513 filtering is performed (stage 514) .
  • stage 515 it is tested whether the end result is true (stage 515) . If so, the object is selected (stage 517), if not, the object is discarded (stage 516) . Then it is checked whether there are any objects to be filtered left (stage 518) . If so, stage 513 is returned to, if not, the filtering is stopped (stage 519) .
  • the filter is first fetched to the selection point of the system (if it is not stored there), i.e. to the point where selection is performed.
  • the filter is applied to an object (stage 514 in Figure 5) , the following method steps are performed.
  • the attribute identifier is first used to get the value of that attribute from the object being filtered.
  • the operation stored in the AVA is then applied to this value and to the value stored in the filter.
  • the operation evaluates to a truth value by performing the operation on the values. This value indicates whether the AVA is true for the value of attribute in the object and the stored value. If the object does not contain the identified attribute, then the AVA evaluates to false as the assertion cannot be true for this object.
  • each type of object describes the attributes within the object.
  • the attributes of an object are defined in the object model, i.e. they are part of the class that is used to model the object.
  • the description of each attribute contains the following information:
  • this identifier can be used to find the value of the attribute within the object.
  • this may be a simple type such as String or Integer, or a complex type such as Set of
  • V alueMethods objects are used to evaluate AVAs .
  • This reference can be implemented in any possible ways, e.g. by means of a pointer word, i.e. a binary number the value of which corresponds to the object it is pointing to.
  • the attributes are stored in the form of the attribute identifiers which contain the type, a unique identifying number forming said identifier and said reference to a ValueMethods object. Values of the attributes are stored elsewhere, as explained later.
  • a network element may contain e.g. a Name attribute.
  • This Name attribute would then contain the following information: - identifier: 1 (if this is the first attribute in the object) ,
  • ValueMethods object reference (e.g. a pointer) to the String ValueMethods object.
  • the value of a specific attribute of a specific object can be found by using the object and identifier to find out where in the object the attribute is stored. For example, to find out the name of a network element A: - the identifier is taken from the attribute (in this example 1) ,
  • the ValueMethods object is found from the attribute and used to convert the generic form to a String which then gives the name.
  • values of attributes are, according to the preferred embodiment of the invention, stored in generic form. This means that all values are stored, regardless of the data type, in only one way. In addition to the stored value the system then keeps up information indicating what type of data each memory location contains in order that data could be converted back to specific form.
  • the storing in generic form can be implemented e.g by using the C++ template mechanism in such a way that there is an abstract base class called e.g. Value and several subclasses, one for each type that is stored in generic form. This is illustrated in figure 4 for integer values, string values and for Boolean values. The following operations may be performed on generic Value objects: (i) copy, (ii) store to a file,
  • a checking is performed to see if the object has the attribute we are interested in. If the object does not have the attribute, an error is reported at this stage.
  • the attribute may be defined either in the object or in one of its ancestors.
  • a member pointer is combined, in a manner known as such, with the pointer to the object to find the value of the attribute. (This known member pointer, which is an offset into an object, is contained in the attribute identifier. When combined with a pointer to an object the member pointer points to an individual data member or method of an object. )
  • ValueMethods objects perform a number of operations for the attribute type. There is one ValueMethods object in the system for every supported type. For example there may be three String attributes in the system for a network element: name, manufacturer and physical location. These three attributes then all share a single String ValueMethods ob ect. ValueMethods objects perform the following services in the system: a range of supported operations : the operations supported will depend on the attribute type that this ValueMethods object is managing.
  • a String ValueMethods object would support isEqual, isNotEqual, startsWith, endsWith and contains; whereas an Integer ValueMethods object would support isEqual, isNotEqual, isGreaterThan, isLessThan, etc.
  • all values in the management system are preferably held in a generic form.
  • This generic form allows the system to store values without knowing their type.
  • the generic form also provides an efficient way of implementing the test in which the logical operators stored in the filter are used.
  • the ValueMethods object is able to convert from this generic type back to a specific type, for example from a generic representation of a String to a Specific String.
  • the name attribute introduced above contains a reference to a String ValueMethods object.
  • the String ValueMethods object will support the following operations: - range of operations: isEqual, isNotequal, startWith, endsWith, contains.
  • each AVA comprises an attribute, an operation and a value.
  • the operation should be one of the operations supported by the ValueMethods object referenced by the attribute. If an illegal operation is used, e.g. a startWith operation on an Integer, the AVA will evaluate to False.
  • the value stored in the AVA is held in generic format as mentioned above. This value will then be compared to the value of the specified attribute using the specified operator. (The comparison is made using said generic values.) To give an example, let us imagine that there is a need to find all network elements whose name begins with "SXC". The AVA for this purpose would be created with the following fields:
  • Figure 6 illustrates evaluating a single AVA. First the attribute is fetched from the AVA (stage 611) . Then, it is tested if the object has this attribute (612) . If no, the result of the AVA is false
  • stage 619 If yes, stage 613 is entered, where the
  • the ApplyTest Method is a generic operation (comparing generic values) but at the same time a specific operation for the particular types of values that are compared with each other.
  • a filter is applied to an object which it matches (object 1, figure 7) and to one which it does not (object 2, figure 8) . Further, object 2 does not contain one of the attributes which the filter attempts to filter on.
  • the filter stored at the selection point of the network is defined functionally as follows: (ExternalName, isEqual, "name”) AND (FaultState, isGreaterThan, 1) . This means that the filter asserts that the object has an attribute ExternalName which has a value of "name” and that the object also has an attribute FaultState which has a value greater than one.
  • Object 1 is filtered as follows (figure 7) :
  • Node A is evaluated which recursively evaluates its two child nodes. 2. Node B is evaluated.
  • Node A is evaluated which recursively evaluates its two child nodes.
  • the management system includes a variety of objects, representing both logical and physical entities. In the enclosed claims all these objects are are set forth as "the objects that relate to the network elements to be managed", i.e. objects that represent the managed environment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Dans un système de gestion d'un réseau de télécommunications, des ensembles séparés de données reliés par des opérateurs logiques sont envoyés à un point de sélection du système pour y être mémorisés, chaque ensemble de données comprenant un identificateur d'attribut, une valeur et une opération, la sélection étant effectuée au niveau du point de sélection, de sorte qu'un résultat intermédiaire est d'abord calculé pour chaque ensemble au niveau du point de sélection par l'utilisation dudit identificateur d'attribut, afin d'obtenir la valeur du même attribut à partir de l'objet en cours de sélection, et par l'application de ladite opération à cette valeur et à la valeur mémorisée au niveau du point de sélection, afin d'obtenir ledit résultat intermédiaire, les résultats intermédiaires obtenus étant combinés par les opérateurs logiques mémorisés, de manière à obtenir un résultat final, la sélection finale des objets étant effectuée sur la base du résultat final.
PCT/FI1996/000688 1995-12-28 1996-12-20 Procede de gestion d'un reseau de telecommunications WO1997024835A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU11965/97A AU1196597A (en) 1995-12-28 1996-12-20 Telecommunications network management method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB9526600.3 1995-12-28
GB9526600A GB2308777A (en) 1995-12-28 1995-12-28 Telecommunications network management

Publications (1)

Publication Number Publication Date
WO1997024835A1 true WO1997024835A1 (fr) 1997-07-10

Family

ID=10786125

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/FI1996/000688 WO1997024835A1 (fr) 1995-12-28 1996-12-20 Procede de gestion d'un reseau de telecommunications

Country Status (3)

Country Link
AU (1) AU1196597A (fr)
GB (1) GB2308777A (fr)
WO (1) WO1997024835A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999037101A1 (fr) * 1998-01-19 1999-07-22 Siemens Aktiengesellschaft Procede et systeme de communication pour le traitement d'alarmes par un reseau de gestion comportant plusieurs niveaux de gestion
CN1297096C (zh) * 2001-03-22 2007-01-24 西门子公司 在tmn网络中有选择地和集中传输报文的方法

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2308779B (en) * 1995-12-28 1998-06-10 Nokia Telecommunications Oy Telecommunications network management system
GB2308778B (en) 1995-12-28 1998-06-10 Nokia Telecommunications Oy Telecommunications network management system
DE19831825C2 (de) * 1998-07-15 2000-06-08 Siemens Ag Verfahren und Kommunikationssystem zur Behandlung von Alarmen durch ein mehrere Managementebenen aufweisendes Managementnetz
US6339705B1 (en) * 1998-10-26 2002-01-15 Telefonaktiebolaget Lm Ericsson Management of multiple types of radio base stations in a telecommunication system
DE19940048A1 (de) 1999-08-24 2001-08-23 Siemens Ag Generisches Alignment-Verfahren in einer Multi-Manager-Umgebung

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5063523A (en) * 1989-11-16 1991-11-05 Racal Data Communications Inc. Network management system with event rule handling
WO1995020297A1 (fr) * 1994-01-19 1995-07-27 British Telecommunications Public Limited Company Gestionnaire d'elements pour un reseau de communications

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
BR9305624A (pt) * 1992-08-28 1995-03-01 Ericsson Telefon Ab L M Rede de gerenciamento e processo para a implementação de um objeto gerenciado em um subsistema do sistema gerenciado em uma rede de gerenciamento

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5063523A (en) * 1989-11-16 1991-11-05 Racal Data Communications Inc. Network management system with event rule handling
WO1995020297A1 (fr) * 1994-01-19 1995-07-27 British Telecommunications Public Limited Company Gestionnaire d'elements pour un reseau de communications

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999037101A1 (fr) * 1998-01-19 1999-07-22 Siemens Aktiengesellschaft Procede et systeme de communication pour le traitement d'alarmes par un reseau de gestion comportant plusieurs niveaux de gestion
US6351213B1 (en) 1998-01-19 2002-02-26 Siemens Aktiengesellschaft Method and communication system for processing alarms using a management network involving several layers of management
CN1297096C (zh) * 2001-03-22 2007-01-24 西门子公司 在tmn网络中有选择地和集中传输报文的方法

Also Published As

Publication number Publication date
AU1196597A (en) 1997-07-28
GB2308777A (en) 1997-07-02
GB9526600D0 (en) 1996-02-28

Similar Documents

Publication Publication Date Title
US6070188A (en) Telecommunications network management system
US6349334B1 (en) Telecommunications network management method and system
US6901440B1 (en) System and method for universal service activation
US6223219B1 (en) Trail management across transport functionality of large and complex telecommunications networks
US5533116A (en) Network management system
US6556539B1 (en) Selector switch control using priority table
US5903731A (en) System and associated method for re-engineering a telecommunications network support system with object-oriented translators
US5764955A (en) Gateway for using legacy telecommunications network element equipment with a common management information protocol
US7185075B1 (en) Element management system with dynamic database updates based on parsed snooping
US6222827B1 (en) Telecommunications network management system
SE503021C2 (sv) Driftstödsnät för ett telekommunikationsnät innefattande nätelement, telekommunikationsnät innefattande nätelement, nätelement samt sätt att strukturera programvara i ett nätelement
EP1212686A1 (fr) Systeme de gestion d'elements de reseau
EP0661891B1 (fr) Dispositif pour gérer un contrôleur d'élément pour un commutateur de télécommunications
US6944657B1 (en) Automatic network synchronization of the network configuration with the management information database
WO1997024835A1 (fr) Procede de gestion d'un reseau de telecommunications
EP0899913A2 (fr) Réseau de communication ayant une architecture de système de gestion et procédé de conception pour supporter la réutilisation du réseau
EP0923270B1 (fr) Machine d'état pour un système de gestion de tracés
WO1997024836A1 (fr) Systeme de gestion de reseau de telecommunications
US20030074359A1 (en) Network management unit
Campbell et al. A layered approach to network management control
Mills An OSCA™ architecture characterization of network functionality and data
Bergholm et al. Service Design and Inventory System—an object-oriented reusable software asset
Blume et al. Control and operation of SDH network elements
Znaty et al. Object oriented generic models: a common way for designing network protocols, their management and the services they support
Zeisler et al. A framework for systems and network management ensembles

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

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

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): KE LS MW SD SZ UG AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG

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

Ref country code: JP

Ref document number: 97524040

Format of ref document f/p: F

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase