Dichroic Antenna Reflector for Space Applications CCITT ...

More documents

Recommendations

Info

42Fig. 11Example explaining the concept Object-orientatedmodelling. A Managed Object is the data image ofa resource. Each Managed Object belongs to anobject class; an object class may be a subclass ofanother object class. The subclass inherits all theproperties from the superior class; the class treeshows the inheritance hierarchy. An object classis characterised by attributes, categories andvalues. An attribute may be the object-relateddistinguishing namePhysical and/or logical items that can bemanaged and supervised are called manageableresources. Typical examples arecircuits, equipment, event logs, event reports,and end points of trails. In each ManagementLayer there are management interfacesfor communication between managingand managed systems. Viewed fromthe managing system, through the managementinterface, the resources in thecontrolled system appear as Managed Objects.The Managed Objects are thereforedata images of the physical and logical resources.There is not necessarily one-to-one mappingbetween Managed Objects and resources,i.e. a resource may be related tonone, one or several Managed Objects,and a Managed Object may be related tonone, one or several resources.The information model handles ManagedObjects and their relationships by employingobject-orientation and entity-relationtechniques. Object- orientation is a methodfor methodical description of the ManagedObjects. Entity-relations indicate the relationshipsbetween the two objects in a pair.Object-orientationEach Managed Object belongs to an objectclass, which may be a subclass of anotherclass. The subclass inherits all the propertiesof the class from which it has beenderived. The subclass refines the class definitionby new properties being added tothose included in the superior class. A particularobject of an object class is called anObject Instance.The different classes can be arranged toform a Class Tree, which shows the inheritancehierarchy. The Class Tree is basedon relationships of the "ISA" type. Fig. 11illustrates the rules of object-orientation.The Class Tree shows, for example, that acoaxial transmission system ISA transmissionequipment; in other words, that acoaxial transmission system is "derived"from transmission equipment. Class Treespermit the reuse of specifications, whichsimplifies data handling and reduces theneed for data storage.A Managed Object has the following characteristics:- the attributes visible at its boundary. Attributescan be assigned one or more values- the management operations that may beapplied to the Managed Object. Someoperations manipulate the values of aManaged Object; for example, GET,SET, ADD, REMOVE a value. Other operationsaffect the Managed Object itself:CREATE or DELETE the Managed Object- the notifications emitted by the ManagedObject-the behaviour exhibited by a ManagedObject in response to management operations.
43Fig. 12Example of entity-relations and relationship rulesLTREGAPTrailLine terminalRegeneratorClient-to-Server Access PointEnd-to-end connection in a transport networklayerEntity RelationsA model is created which defines the relationshipsbetween Managed Objects, anda set of rules is used to define the EntityRelations that may exist. A relationshipbinds attributes of two objects to each other;the objects may belong to the same ordifferent Management Layers. The numberof Object Instances involved in a relationshipis identified. Relationships may evenexist between instances of the same object;they are then called recursive relationships.Relationships can be described by applyingthe following orthogonal relationshiprules:-containingan object contains another object (physicalor logical decomposition)-terminatinga logical connection between logical objects-linkinga physical connection between physicalobjects- managinga managing relationship between objects-listinga point-to-multipoint relationship betweenobjects.Fig. 12 shows the basic rules for Entity Relations.In order to be consistent, the term"entity" has been replaced by "object". TheFigure shows examples of relationshiprules and an example of a ManagementInformation Tree based on the relationshiprule "containing".The Figure shows, for example:- A first object containing n Object Instancesis related by certain rules to a secondobject containing m Object Instances- A line terminal is linked to a regenerator.A Client-to-Server Access Point terminatesa Trail- An Operations System controls a MediationDevice, which controls a NetworkElement- A bay contains shelves.The containment relationship can be usedto obtain the Management InformationTree shown in Fig. 12:DIG-MUX (which IS A transmission equipmentaccording to Fig. 11) contains replaceableunits, or a replaceable unit ispart-ofDIG MUX.Each Managed Object is identified by aname. The name can be derived by combiningthe name of the superior object in theManagement Information Tree with a namingattribute (name binding). The ManagementInformation Tree can be used forname binding.There are manageable resources in thedifferent Management Layers, both in telecomnetworks and TMN networks. Thefunction of the telecom network is based onthe resources of the telecommunicationequipment. The equipment appears as resourcesin Network Elements, and Network
Page 3 and 4: ERICSSON REVIEWNumber 2 1991 Volume
Page 5 and 6: ANDERS DERNERYDHANS WILHELMSSONEric
Page 7 and 8: 25Fig. 4Different sandwich structur
Page 9 and 10: Fig. 6The lowest self-resonance of
Page 11 and 12: 29Fig. 12The frequency-selective su
Page 13 and 14: Fig. 14Calculated radiation pattern
Page 15 and 16: 33Fig. C for Box 2Examples of symme
Page 17 and 18: 35WALTER WIDLEricsson Telecom ABPri
Page 19 and 20: This functionality is represented b
Page 21 and 22: Fig. 5Example of connection of main
Page 23: 41The Service Management Layerhandl
Page 27 and 28: Fig. 15Exchange of information betw
Page 29 and 30: Fig. 18Transmission of an alarm fro
Page 31 and 32: Box 8EXAMPLE OF OBJECT CLASSES FOR
Page 33 and 34: Fig. 24An example of the use of Eri
Page 35 and 36: JOHAN FRANDFORSNIKLAS HAFDELLEricss
Page 37 and 38: Technical Data for Rectifiers55Inpu
Page 39 and 40: ZAN 202, a System for Operation and
Page 41 and 42: Fig. 3Several ZAN 202 may be used i
Page 43 and 44: 61ACTIVE ALARMS1991-APR-23TRANSMISS
Page 45: 63ZAN 202-ver2 Internal Alarm Print

Dichroic Antenna Reflector for Space Applications CCITT ...

Create successful ePaper yourself

Delete template?

Save as template?