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

54Table 5Cross-connect functions, Resources and ManagedObjects related to the example in Fig. 25No30LPC31HPCFunction (sending, receiving)Assignment of VC12s within VC4ResourceCross-connectioncapabilityAssignment of VC4s within STM-1 Cross-connection(STN-N in general case)capability* The name of this Managed Object is not included in Rec. G.774Managed Object *VC12TTP-TU12CTPVCTU12XCVC4TTP-AU4CTPVCAU4XCFig. 29Point-to-Point cross connectionsIn the Information Model (Figs. 29-31)Cross Connection Pointers pointing from CTP toCX are not shownManaged ObjectTo/from TP pointer between a CTP and an XCConnectivity pointer between CTPsTo/From TP pointer between a GTP and an XCCross Connection object pointertivity pointers (see Table 2) or flexibilitypoints represented by Managed Objectsbelonging to the cross-connection Fragment(see below).Cross connectionThe cross-connection capability referredto in Table 5 deals with the possibility (withinthe equipment) of freely assigning VCsto available VC-n capacity in a higher orderPath (LPC) or in a multiplex section(HPC). The association can either be anassignment (preparation) or an actualcross connection.In the Functional Model (the left side of figures29,30 and 31) cross connection is thepossible association between a TCP anda CP or between CPs. It is by controllingthis association that networks can be configuredto meet changing demands. Certainrequirements have to be met to makethe control function easier. Examples offunctional requirements are:- It should be possible only to assign (prepare)a cross connection without activatingit (Figs. 29 and 30)- It should be possible to perform point-topointand point-to-multipoint (broadcast)cross connections (Figs. 29 and 31)- It should be possible to cross-connectseveral Termination/Connection Pointsas a single unit without the need to makeindividual cross connections (Fig. 30)- It should be possible to group Termination/ConnectionPoints for managementpurposes like routing, etc.Figs. 29,30 and 31 illustrate how the functionalrequirements listed above are usedto derive both the Functional and InformationModels.Fig. 29 shows a point-to-point cross-connectioncase. The Information Model (theright side of Fig. 29) consists of:-A cross-connection Managed Objectclass (XC) which models the associationbetween the Termination Points involvedNamingIn the Functional Model (Figs. 29-31)ERICSSON REVIEW No. 1-2, 1992