Dichroic Antenna Reflector for Space Applications CCITT ...

More documents

Recommendations

Info

44Fig. 13Interworking between Manager, Agent andManaged ObjectsFig. 14Shared Management Knowledge (SMK)SMK is related to a pair of communicatingfunction blocks. Each function block has to usethe same SMK to ensure communication. If theManager and Agent processes are located indifferent physical TMN entities, they communicatevia Q-interfaces. If they are located within thesame TMN entity, they are interconnected bymanagement functions via internal referencepointsElements appear as resources in networks.Several detail functions in a lowermanagement layer may, in a higher layer,be treated as combined functions in a blackbox. Descriptions of the functions of thedifferent resources as Managed Objetsand their interconnections are stored inseparate Management Information Bases(MIB). Correspondingly, an MIB containsdetailed specifications for all Managed Objectsin the TMN. It is also to contain specificationsof the functions and configurationof the TMN entities that control the NetworkElements. An MIB therefore provides thebasis for the information model.Organisational ModelThe organisational model describes-the ability of the managing process totake on a controlling role (Manager) and/or to be controlled (Agent)-the interworking between the Managerand Agent parts of the process-what is needed to make interworkingpossible.For a specific management action the TMNprocess will take on either of the two possibleroles of Manager and Agent. TheManager controls objects in its part of theprocess. An Agent follows the TMN directivesgiven by a Manager. Part of the role isto return the data image of Managed Objectsto the Manager. The principal relationshipsbetween Manager, Agent and Objectsare shown in Fig. 13.Multipoint relationships can exist betweenManager and Agent. One Manager may beinvolved in information exchange with severalAgents, and one Agent may exchangeinformation with several Managers.For systems to be capable of interworking,they must use the same protocol and TMNFunctions, and have common ManagedObjects, Object Instances, and Containingrelationships (name binding).Systems that have these concepts in commonare said to have the same SharedManagement Knowledge (SMK). Fig. 14shows that SMK is related to one pair ofcommunicating functions. SMK12 is differentfrom SMK23. If the Manager and Agentprocesses take place in physically separatedTMN entities, communication betweenthem will be via Q-interfaces. If Managerand Agent are in the same TMN entity, theyare connected by management functionsvia internal reference points (r).Start of information exchange requiresprocesses which ensure that the sameSMK is used by the interworking interfaces.These processes are called static or dynamiccontext negotiations. A static processnegotiates SMK at the beginning of theinformation exchange. In a dynamic process,SMK is affected by several conditionsand is modified during the exchange of information.The Managed Objects can be assigned differentManagement Domains, each ofwhich corresponds to a specific functional,geographical and/or organisational area.Exemples of functional areas are faultmanagement, billing management, and security.Within a Domain, the managementprocess can be adapted to specific requirementsof the network operator - related tofunctions, for example. The roles of Managerand Agent can be temporarily assignedand possibly also modified.Management Domains can be overlapping,contained in each other, or interacting.Managed Objects in overlapping domainsbelong to various domains simultaneously.The main reason for introducing the Domainconcept is to make it possible for net-
Fig. 15Exchange of information between NE and OS. TheMessage Communication Function (MCF) and theData Communication Function (DCF) are used.DCF is implemented in the data communicationnetwork, DCN, and located in the lower layers ofthe OSI reference model.The TMN entities OS, MD and NE contain MessageCommunication Functions, MCFFig. 16Survey of standardised protocol suiteswork operators to divide their objects accordingto their own requirements, policy,etc.Communication ModelThe communication model describes thefunctions, protocols and messages involvedin the exchange of information betweenTMN entities.Fig. 15 shows, as an example, the exchangeof information between a Managerin OS and an Agent in NE, by means of theMessage Communication Function, MCF,and the Data Communication Function,DCF. DCF is implemented in the DataCommunication Network, DCN. LAN,WAN, SS#7, X25 or embedded communicationfunctions can be used for DCN. TheDCF functions are to be found in the lowerlayers of the OSI reference model. OS, MDand NE contain message communicationfunctions (MCF), Fig. 3. The MCF conceptcan even be used outside the TMN, Fig. 4.A set of requirements has to be establishedfor the most likely communication needs,e.g. simple transactions, file handling, filetransfer, file access, or combinations ofthese procedures. Other characteristicsmust also be specified: transfer capacity,reliability and transit delay.Q-interfaces are used for exchange of informationbetween Network Elements andTMN entities, and between TMN entitiesthemselves. F-interfaces are used betweenworkstations and Network Elementsor TMN entities, and X-interfaces are usedbetween different TMNs. So far, CCITT hasonly specified Q-interfaces for managementof transmission systems.The Q-interface is defined in Rec. G.773 asfollows:-full 7-layer stack protocol suites B1, B2and B3, used in applications for e.g. synchronousnetworks- short-stack protocol suites A1 and A2,used primarily in applications for e.g. plesiochronousnetworks.Fig. 16 gives a survey of the proposed protocolsuites. An extensive list of referencesdefining protocols is included in Rec.G.773.The protocols used in the upper part of theapplication layer in the OSI ReferenceModel are CMIP (Common ManagementInformation Protocol) and FTAM (FileTransfer, Access and Management). 8CMIP is a transaction-oriented protocol
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 and 24: 41The Service Management Layerhandl
Page 25: 43Fig. 12Example of entity-relation
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?