48Fig. 20Entity-relations <strong>for</strong> Equipment FragmentObject classes in the Network box and in theTermination Point box may appear in otherfragments tooFig. 21Entity-relations <strong>for</strong> Alarm Surveillance FunctionalArea Fragment
Box 8EXAMPLE OF OBJECT CLASSES FOR THE"EQUIPMENT" FRAGMENTEQUIPMENTThe "Equipment" object class is a class of ManagedObjects that is contained within the "ManagedElement" class and represents physical unitswhich per<strong>for</strong>m telecommunications and/or TMNfunctions. "Equipment" may be nested within other"Equipment" object classes, thereby creating acontaining relationship. An Object Instance belongingto this class is a single-location one.MANAGED ELEMENTThe "Managed Element" object class is a class ofManaged Objects that contains other ManagedObjects, which represent telecommunication and/or TMN implementations and functions. An ObjectInstance belonging to this class is a single-locationone.SOFTWAREThe "Software" object class is a class of ManagedObjects that represents an arbitrary set of storedinstructions, which can be used as programs anddata tables. "Software" may be nested within other"Software" object classes, thereby creating a containingrelationship. "Software" can be contained in"Equipment", <strong>for</strong> example.Fig. 22Use of the Organisational modelExample of Manager-Agent processesMCF Message Communication FunctionMAF Management Application FunctionMO Managed ObjectBox 9EXAMPLES OF OBJECT CLASSES FOR THE"ALARM SURVEILLANCE FUNCTIONAL AREA"FRAGMENTALARM RECORDThe "Alarm Record" object class is used to definethe in<strong>for</strong>mation stored in the log of received alarmreports. The semantics of the object class - itsattributes and behaviour - is derived from the alarmreports (Alarm notification) described in RecommendationX.733 (ISO/IEC101 64-5).EVENT FORWARDING DISCRIMINATORThe "Event Forwarding Discriminator" object class- a subclass of "Discriminator" - is used to definethe conditions that must be satisfied by potentialevent reports be<strong>for</strong>e a report is <strong>for</strong>warded to aparticular destination. The semantics o( this objectclass - its attributes, management operations andbehaviour - is described in RecommendationX.734 (ISO/IEC 101 64-5).Application of the TMN methodology issimplified by diagrams specifying the relevantEntity Relations. This leads to-a Class Tree, defining the InheritanceHierarchy-a Management In<strong>for</strong>mation Tree, to beused <strong>for</strong> name binding-a syntax (Abstracts Syntax Notation,ASN-1) used to provide a uni<strong>for</strong>m way ofspecifying object classes, attributes, notifications,and operations.In future, a catalogue containing ManagementIn<strong>for</strong>mation, such as Managed Objects,Relationships, TMN ManagementServices, Components and Functions, willfacilitate the introduction of TMN.The "Discriminator" object class is used to definethe conditions governing the management services.The semantics of this object class - its attributesand behaviour - is described in RecommendationX.734 (ISO/IEC 101 64-5).LOGThe "Log" object class is used to define the conditionsgoverning the logging of in<strong>for</strong>mation in themanagement APDUs. The semantics of this objectclass - its attributes and behaviour- is described inRecommendation X.735 (ISO/IEC 101 64-6).The "Log Record" object class is used to define therecords contained in a class "Log" Managed Object.The semantics of this object class - its attributesand behaviour- is described in RecommendationX.735 (ISO/IEC 101 64-6).The "Event Log Record" object class is used todefine the in<strong>for</strong>mation stored in the log as a result ofreceived events. This is a superordinate class (Superclass)from which reports (Records) on specifictypes of event are derived.Generic application exampleThe example in Fig. 19 illustrates a genericcase of network management by TMN.The Network Element Layer contains themanaged resources of the telecommunicationnetwork, i.e. the equipment that per<strong>for</strong>mstelecommunication and supportfunctions.The Network Element Management Layercontains the Mediation Devices (andsometimes Operations Systems) with theirresources, e.g. databases with in<strong>for</strong>mationabout the function of managed NetworkElements.The Network Management Layer containsOperations Systems with their resources,e.g. databases with in<strong>for</strong>mation about thefunction of the network. Telecom networkscan be divided into transport layer networks,one <strong>for</strong> each characteristic signal(bit rate, framing). Each transport layercontains subnetworks covering specific geographicalregions. The Network ManagementLayer can there<strong>for</strong>e contain a numberof Operations Systems, each handling itsown transport layer with various regions orits own region covering various transportlayers.The Managed Objects in each ManagementLayer can be combined in Entity-Relationdiagrams in order to establish theIn<strong>for</strong>mation model. Different aspects maybe considered, depending on the purposein view. Details of the telecommunicationand supervisory functions must be knownin the case of fault and per<strong>for</strong>mance management.For routing, it might be necessaryto consider only the end points oftrails.Fig. 20 shows Entity Relations - <strong>for</strong> transmissionequipment - and Fig. 21 those <strong>for</strong>
Change language