Frame Relay - for Faster and More Efficient Data Communications ...

Fig. 32, leftCross-connect Fragment, Inheritance hierarchyFig. 33, rightCross-connect Fragment, Naming hierarchyed groups require six instances of GTPsand three instances of XCs. When GTPsare cross-connected, the nth CTP of oneGTP is cross-connected to the nth CTP ofthe other GTP. The assigned (not activated)group 3 in Fig. 30 will be indicated bythose CTPs (which constitute the GTPs)and which have NULL Connectivity pointers.Fig. 31 shows a broadcast (point-to-multipoint)cross-connection case. In additionto the point-to-point case, the InformationModel consists of the Multipoint cross-connectionManaged Object class (MPXC)which represents the assignment relationshipbetween the common CTP and thebroadcast CTPs. One instance of this Objectclass and three instances of the XCObject class will be required to model thecase.The Managed Objects for the cross-connectionFragment are defined in Box 1. Theinheritance hierarchy and naming tree areshown in Figs. 32 and 33 respectively.Box 1Object definitions for crossconnectFragmentThe Fabric Object class represents the set of logicalmatrices that are co-ordinated to provide connectivityof a range of characteristic informationtypes. It manages the establishment and releaseof cross connections. It also manages the assignmentof Termination Points to TP pools and GTPsThe Group Termination Point Managed Objectclass (GTP) represents a group of TerminationPoints that can be treated as a single unit for crossconnection and other administration purposes'TP pool" represents a set of Termination Pointsor GTPs that are equally handled in a number ofmanagement applications, e.g. routing. All theTPs in a TP pool have the same signal typeThe "Multipoint cross-connection" Managed Objectclass (MPXC) represents an assignment relationshipbetween a TP or GTP and the correspondingTPs or GTPs.Reference1 CCITT RecommendationsM.60M3010(M30)M.3020(M.meth)M.3100(M.gnm)M.3180(M.cat)M.3200(M.app)M.3300(M.f)M.3400(M.func)Maintenance Terminologyand DefinitionsTDSG.IV June 1992Principles for a TelecommunicationsManagementNetwork (TMN)COM IV-R28E, part 2, 991TMN interface specificationmethodologyCOM IV-R28E, part 2, 1991Generic Network InformationModelCOM IV-R28E, part 2, 1991Catalogue of TMN ManagedObjectsCOM IV-R28E, part 2, 1991TMN management services,introductionCOM IV-R28E, part 2, 1991F-lnterface managementcapabilitiesCOM IV-R28E, part 2, 1991TMN management functionsCOM IV-R28E, part 2, 1991G.773 Protocol profiles for the Qx-Interfaces for management oftransmission systemsG.774 SDH Network InformationModel for TMNQ.811 Lower Layer Protocol ProfilefortheQ3-lnterfaceQ.812 Upper Layer Protocol Profilefor the Q3-lnterfaceWidl, W.: Telecommunications NetworkArchitecture. Ericsson Review 67(1990):4, pp. 148-162.Widl, W.: CCITT standardisation of TMN.Ericsson Review 60(1991 ):2, pp. 34-51.Rec. Architecture of transport net-G.803 works based on SDHCCITT RecommendationsG.702G.707G.781G.782G.783Digital hierarchy bit ratesSynchronous Digital Hierarchybit ratesStructure of Recommendationson MultiplexingEquipment for SDHTypes and general characteristicsof SDH MultiplexequipmentCharacteristics of SDH multiplexingequipment functionalblocksERICSSON REVIEW No. 1-2, 1992