Dichroic Antenna Reflector for Space Applications CCITT ...

More documents

Recommendations

Info

36Box 2SURVEY OF TMN FUNCTION BLOCKSBox 4FUNCTIONAL SUBCOMPONENTS within theTMNFig. 2Function Blocks in the TMNOSFMFNEFOAFWSFOperations System Function blockMediation Function blockNetwork Element Function blockQ-Adapter Function blockWork Station Function blockOSFMFNEFQAFWSFOperations System Function blockhandles application processes visibleto the users, such as business,service and network managementMediation Function blockconverts information, e.g. translationbetween Managed Objectshandles data, e.g. data concentration,reduction, editingmakes decisions, e.g. regardingthreshold values, routingstores data, e.g. data identifyingequipment and networksNetwork Element Function blockhandles telecommunication processes,e.g. for switching and transmission- is involved in telecommunicationsupport processes, e.g. fault localisationand protection switchingQ-Adapter Function- converts non-standardised MCFs(Message Communication Function),transmitted via non-standardisedM-interfaces, into standardisedMCFs, transmitted viastandardised interfacesWork Station Function blockmanages user terminals, e.g. displayof information, transfer of users\ r\ m m 1 r\ f-i oMAFMIBICFPFMCFqHLPIHMAManagement Application Functions- needed for management functions,such as Manager (M) and Agent (A).MAF appears in NE as NEF-MAF, inMD as MF-MAF, and in OS as OSF-MAF. NEF-MAF performs functionsnecessary for serial connection of severalNEs. MF-MAF handles and storesdata and makes decisions. OSF-MAFperforms functions necessary for serialconnection of several OSsManagement Information Base- stores management information relatedto Information modelsInformation Conversion Function- gives the relationships between differentinformation models, e.g. betweenobject-oriented and non-object-orientedmodels as well as between modelswith different types of object-orientationPresentation Function- converts information into a formatwhich is intelligible to the userMessage Communication Function- is used by function blocks for informationhandling. MCF is structured accordingto the OSI reference model,with seven layers. Information is transferredby means of the Data CommunicationFunction, DCF, which uses layers1-3High Level Protocol Interworking- is needed when the highest levels ofMCF (layers 4-7) are to be convertedHuman-Machine Adaptation- is required for conversion from the TMNinternal Q-intertace information modelinto the F-interface information modelBox 3REFERENCE POINTS BETWEENBLOCKSFUNCTIONTEFqxgfmTMN external function blocksreference point between TMN entitiesreference point between separate TMNsreference point between WSF and operatorreference point between WSF and TMNinternal function blocksreference point between QAF and TMNexternal function blocksBox 5FUNCTIONAL COMPONENTS outside the TMNMEFSEFMCFmMaintenance Entity Function- contains the functions of the transmissionnetwork, e.g. for transmission andswitchingSupport Entity Function- contains support functions for thetransmission network, e.g. power supplyMessage Communication Function- is used by function blocks for informationhandling. MCF is structured accordingto the OSI reference model
This functionality is represented by FunctionBlocks consisting of Functional Subcomponents.Function Blocks are containedin building blocks through which aTMN of optional complexity can be implemented.A TMN comprises the following functionblocks. Fig. 2:OSF Operations Systems Function blockMF Mediation Function blockNEF Network Element Function blockQAF Q-Adapter Function blockWSF Work Station Function block.NEF, QAF and WSF are partly outside theTMN. Box 2gives an overview of the purposeof the different function blocks. Thefunction blocks represent general basicfunctions which are used in different managementactivities.Function Blocks/Functional Subcomponentsare separated from each other byReference Points. The different referencepoints, designated q, f, g and x, are listed inBox 3. For example, between WSF andOSF there are reference points f, and betweendifferent OSFs there may be referencepoints x andq depending on whetheror not the OSFs belong to the same TMN.Function Blocks within a TMN can be describedin more detail by the FunctionalSubcomponents shown in Boxes 4 and 5.The physical implementation of a referencepoint is called interface. An interface cantransfer information to several TMN entities,as exemplified in Fig. 22.Function Blocks and physical implementationscan be defined by means of FunctionalSubcomponents. Box 6 exemplifies theimplementation of TMN entities throughfunction blocks and functional subcomponents.Fig. 3 exemplifies the connection of networkelements to the TMN. The relationshipsbetween function blocks and theirphysical implementations are shown, aswell as the relationships between functionalreference pointsq and the physical Q-interfaces. TMN entities require for theircommunication the functional subcomponentMCF (Message CommunicationFunction). MCF uses the Data CommunicationFunction, DCF, for transfer of information.Fig. 4 shows how Maintenance Entities,ME, and Support Entities, SE, with non-Box 6aEXAMPLES OF FUNCTION BLOCKS AND FUNCTIONAL COMPONENTSBox 6bEXAMPLES OF IMPLEMENTATIONS WITHFUNCTION BLOCKSMOMandatory (Main Function Block)OptionalFor the WSF to be present, either the MF orOSF must also be present.Within this table, where more than one name ispossible, the choice of the building block nameis determined by the predominant usage of theblock.IMPLEMENTATIONSOS Operations SystemWS Work StationMD Mediation DeviceNE Network ElementQA Q-Adapter
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: 35WALTER WIDLEricsson Telecom ABPri
Page 21 and 22: Fig. 5Example of connection of main
Page 23 and 24: 41The Service Management Layerhandl
Page 25 and 26: 43Fig. 12Example of entity-relation
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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?