('ATM是特殊的面向连接的协议,不提供任何确认机制。虽然ATM提供了从AAL0到AAL5多种类型的适配层协议,但没有一种AAL支持简单的点到点的可靠传输,于是在AAL层定义了SSCOP实现此功能,SSCOP只用于控制信令,不用做数据传输。为了有效可靠地承载信令,在传输网络层使用分层结构,从下到上分别是SAAL(AAL5交换)、MTP3B和SCCP。再往上就是应用层的如NBAP(NodeB应用部分)、RANAP(无线接入网络应用部分)等。SAAL作为底层承载,采用AAL5交换,向MTP3B提供可靠的面向连接的数据传输,在OSI的7层体系中,可对应理解为数据链路层;MTP3B用于ATM网络中传送信令(MTP3用在TDM信令承载网中),MTP3B完成信令消息的传递和分发,包括消息识别、消息分配、消息路由控制三个功能,可理解为OSI的网络层;SCCP(信令连接控制部分)是MTP3B的增强,建立面向连接或无连接的网络服务。具体说来,MTP3B以信令链路、OSP、DSP等寻找路由,SCCP则结合了SSN子系统号,SSN区分使用SCCP的软件实体,如RANAP、RNSAP、SCCP管理等。在传输网络控制面内,与传输网络用户面协议一一对应。传输网络用户面的各连接都是由控制面信令控制的。无线网络用户面底层承载为AAL2,适合传送实时性强的话音数据。所以该协议栈为电路域的接口协议。如果是分组域,则承载就是AAL5。以上可以看出,根据话音数据、分组数据的特点,UTRAN采用不同的ATM适配层协议,对于控制信令采用了AAL5,其他用到的AAL还包括AAL0和AAL1(如RNC实现电路仿真业务CES)。此外,UTRAN中还使用了IMA(ATM反向复用技术)、IPOA(IP与ATM结合的技术)等ATM技术,在此不做详细介绍。6.3.2.3MTP-3bTerminationTheconfigurationoftheMTP-3bsignalingpointfunctioninRNCisrepresentedbytheMtp3bSpItu,Mtp3bSpAnsiorMtp3bSpTtcMOtypes,correspondingtodifferentmarket-dependentversionsoftheMTP-3bprotocols.TheexampleinFigure26andTable52arefortheITU-Tversion.EachremotenodeandtypeofsignalingserviceisrepresentedbyanaccesspointforMTP-3bsignaling,Mtp3bAp.TheroutingpossibilitiesforMTP-3bmessagestoeachremotenodeisrepresentedbyconfigurationofsignalingroutesetsMtp3bSrs,signalingroutes,Mtb3bSr,andsignalinglinksets,Mtb3bSls.Figure26RNCMTP-3bSignalingforIuTable52RNCMTP-3bSignalingforIuPos.MO:=Parent:=,...=Comment1MO:Mtp3bSpItu=1Parent:TransportNetwork=1networkInd=NATIONAL_NETWORKsignalingPointCode=ThepointcodeallocatedtoRNCrpuId=ReferencetoPos.1inTable38.2MO:Mtp3bSrs=csParent:Mtp3bSpItu=1(Pos.1)desPointCode=ThepointcodeallocatedtoMSCautoReroute=false3MO:Mtp3bSrs=psParent:Mtp3bSpItu=1(Pos.1)desPointCode=ThepointcodeallocatedtoSGSNautoReroute=false4MO:Mtp3bSls=csParent:Mtp3bSpItu=1(Pos.1)mtp3bSrsId=ReferencetoMOinPos.2.5MO:Mtp3bSls=psParent:Mtp3bSpItu=1(Pos.1)mtp3bSrsId=ReferencetoMOinPos.3.6MO:Mtp3bSr=csParent:Mtp3bSrs=cs(Pos.2)linkSeM3uId=ReferencetoMOinPos.4.priority=17MO:Mtp3bSr=psParent:Mtp3bSrs=ps(Pos.3)linkSeM3uId=ReferencetoMOinPos.5.priority=18MO:Mtp3bAp=csParent:Mtp3bSpItu=1(Pos.1)routeSetId=ReferencetoMOinPos.2serviceInd=3IndicatesSCCPusage9MO:Mtp3bAp=psParent:Mtp3bSpItu=1(Pos.1)routeSetId=ReferencetoMOinPos.3serviceInd=3IndicatesSCCPusage10MO:Mtp3bAp=cqParent:Mtp3bSpItu=1(Pos.1)routeSetId=ReferencetoMOinPos.2(AssumesthatthesameSS7destinationpointcodeisvalidforQ.2630andRANAPtoMSC.)serviceInd=12IndicatesQ.2630usage6.3.2.4SignalingLinkstoMSCandSGSNFigure27RNCSignalingLinksforRANAPtoMSCandSGSNTable53RNCSignalingLinksforRANAPtoMSCandSGSNPos.MO:=Parent:=,...=CommentSignalinglinktoMSC1MO:AtmTrafficDescriptor=U3PMParent:TransportNetwork=1ingressAtmPcr=egressAtmPcr=ingressAtmMcr=egressAtmMcr=ingressAtmQos=CLASS_THREEegressAtmQos=CLASS_THREEATMtrafficdescriptorforSAAL-NNIsignalinglinksforIu.SeeSection4.4.1.2regardingpcrandmcrvaluesSeeSectionserviceCategory=UBR+packetDiscard=true3.2.6.1regardingMOnamingconvention.2MO:VclTp=vc34Parent:...,VpcTp(Pos.3inFigure24)externalVci=34SignalinglinktoMSC.SeeSection2.6.2.4.atmTrafficDescriptorId=ReferencetoMOinPos.1.3MO:Aal5TpVccTp=csaParent:TransportNetwork=1processorId=ReferencetoPlugInUnitforactiveSccpMP,forexample,MS-8inRNC3810andMS-7inRNC3820.SeeSection2.3.2.1andSection2.6.2.4.vclTpId=ReferencetoMOinPos.2fromUserMaxSduSize=280toUserMaxSduSize=280SeeSection4.4.1.4MO:NniSaalProfile=win250Parent:TransportNetwork=1Seeprofile"win250"inSection4.4.1.4.Recommendedprofileforhigh-speedSAAL-NNIsignalinglinkSeeSection4.4.1.5MO:NniSaalTp=csaParent:TransportNetwork=1nniSaalProfileId=ReferencetoMOinPos.4.aal5TpVccTpId=ReferencetoMOinPos.3.MaxSduSize=276SeeSection4.4.1.6MO:Mtp3bSlItu=csaParent:Mtp3bSls=cs(Pos.4inTable52)tpId=ReferencetoMOinPos.5sigLinkCode=0Settodifferentvalues(0-15)fordifferentlinksinthesamesignalinglinksetSignalinglinktoSGSN7MO:VclTp=vc35Parent:...,VpcTp(Pos.3inFigure24)externalVci=35SignalinglinktoSGSN.SeeSection2.6.2.4atmTrafficDescriptorId=ReferencetoMOinPos.18MO:Aal5TpVccTp=psaParent:TransportNetwork=1processorId=ReferencetoPlugInUnitforactiveSccpMP,forexample,MS-8inRNC3810andMS-7inRNC3820.SeeSection2.3.2.1andSection2.6.2.4.vclTpId=ReferencetoMOinPos.6fromUserMaxSduSize=280toUserMaxSduSize=280SeeSection4.4.1.9MO:NniSaalTp=psaParent:TransportNetwork=1nniSaalProfileId=ReferencetoMOinPos.4.aal5TpVccTpId=ReferencetoMOinPos.7.MaxSduSize=276SeeSection4.4.1.10MO:Mtp3bSlItu=psaParent:Mtp3bSls=ps(Pos.5inTable52)tpId=ReferencetoMOinPos.9.sigLinkCode=0Settodifferentvalues(0-15)fordifferentlinksinthesamesignalinglinkset.6.3.2.5SCCPandRANAPFigure28RNCSCCPSignalingforIuTable54RNCSCCPSignalingforIuPos.MO:=Parent:=,...=Comment1MO:SccpSp=1mtp3bSpId=CommonParent:TransportNetwork=1attributesforSCCP.ReferencetoMOinPos.1inTable52.2MO:SccpScrc=1Parent:SccpSp=1(Pos.1)TheSCCProutingcontrolMOholdsperformancemanagementcountersforSCCP.3MO:SccpApLocal=ranapParent:SccpScrc=1(Pos.2)LocalAPforRANAP)ssN=142SubsystemnumberforRANAP=142(3GPPTS23.003).maxConn==NumberofsimultaneousSCCPconnectionsforRANAP.Thevalueofthisattributeshouldbedeterminedbasedontheexpectedtraffic.useS1=trueOPCisaddedtoCallingPartAddressifabsent.4MO:SccpApRemote=csParent:SccpScrc=1(Pos.2)(RemoteAPforMSC)ssN=142SubsystemnumberforRANAP=142(3GPPTS23.003).mtp3bApId=ReferencetoMOinPos8inTable52.5MO:SccpApRemote=psParent:SccpScrc=1(Pos.2)ssN=142SubsystemnumberforRANAP=142(RemoteAPforSGSN)(3GPPTS23.003).mtp3bApId=ReferencetoMOinPos9inTable52.6MO:Ranap=csParent:IuLink=cscnDomainInd=0IndicatesCSdomain.localSccpApRef=ReferencetoMOinPos.3.remoteSccpApRef=ReferencetoMOinPos.4.sccpGlobalTitleRef=null7MO:Ranap=psParent:IuLink=pscnDomainInd=1IndicatesPSdomain.localSccpApRef=ReferencetoMOinPos.3.remoteSccpApRef=ReferencetoMOinPos.5.sccpGlobalTitleRef=null6.3.2.6AAL2ControlandUserPlaneforIuThissectioncoversconfigurationofboththeAAL2controlplanewiththeQ.2630signalingprotocoltermination,Aal2Ap,andtheAAL2paths,Aal2PathVccTp,onwhichAAL2userplanebearerscanbeconnected.AnAAL2Pathcancarryupto248switchedAAL2connections.SeveralAAL2paths,relatedtothesameresourcehandler,Aal2PathDistributionUnit,mayneedtobeconfiguredonthetwoVirtualPathsbetweenRNCandMSCdependingonsite-specifictrafficdimensioning.Figure29RNCAAL2forIuTable55RNCAAL2forIuPos.MO:=Parent:=,...=Comment1MO:Aal2Sp=1Parent:TransportNetwork=1a2ea=AAL2addressallocatedtoRNC.SeeSection2.7.1.2MO:Aal2QoSCodePointProfile=1Parent:TransportNetwork=1SeeSection3.2.7.1.3MO:Aal2Ap=cParent:Aal2Sp=1(Pos.1)(Q.2630signalingtoMSC)sigLinkId=ReferencetoMOinPos.10inTable52.secondarySigLinkId=nullNoMOreference(=default)allocationMode=manualForIuitshouldbesettomanual.rpuId=ReferencetoMOinPos2inTable38.Aal2QosCodePointProfileId=ReferencetoMOinPos.2.4MO:Aal2RoutingCase=ndRoutingcasefornumberdirectiond>Parent:TransportNetwork=1routeList=ReferencetoMOinPos.3.(MultipleAal2Apreferencescanbespecifiedforalternativerouting)5MO:AtmTrafficDescriptor=c2pParent:TransportNetwork=1ingressAtmPcr=egressAtmPcr=ingressAtmQos=CLASS_TWOegressAtmQos=CLASS_TWOserviceCategory=CBRATMtrafficdescriptorforAAL2pathforIu.SeeSection4.5.1regardingpcrvalues.6MO:VclTp=vcParent:...,VpcTp(Pos.3inTable51.)externalVci=AAL2pathtowardsMSC.SeeSection2.6.2.4.atmTrafficDescriptorId=ReferencetoMOinPos.5.7MO:Aal2QosProfile=ad10bd20Parent:TransportNetwork=1SeeforrecommendationsaboutsettingsofAAL2QoSProfiles.8MO:Aal2PathVccTp=caParent:TransportNetwork=1(n=sequencenumberforidentificationofmultipleAal2PathVccTpMOstowardsthecorenetwork.)vclTpId=ReferencetoMOinPos.6.aal2PathId=SeeSection2.7.1.4.Coordinationofpathidentifiervalue(pid)withconfigurationofremotenodeneeded.Range:Integer>0aal2PathOwner=trueRNCisconfiguredas"owner"ofallAAL2pathstowardscorenetworkaal2QoSProfileId=ReferencetoMOinPos.7.aal2QoSAvailableProfiles=CLASS_A_B9MO:Aal2PathDistributionUnit=Parent=...,Aal2Ap=cPos.3IfallocatedtoCoreFunctionMP,=1.IfallocatedtomoduleMPs,=thenumberoftheRNCmodulerpuId=InRNC3810referencetoMOinPos4(CoreFunctionMP)orPos5(moduleMP)inTable38.InRNC3820referencetoMOinPos5(ModuleMP)inTable38.IncaseofmoduleMPs,multipleinstancesofAal2PathDistributionUnitareused.RefertoSection4.5.1forfurtherinformation.aal2PathVccTpList=ReferencetoMOinPos.8andadditionalAal2PathstobecontrolledbythesameAal2PathDistributionUnit.6.3.2.7IuUserPlanetoSGSN(GTP-U)TheUDP/IPhostandGTP-UpathterminationsoneachPacketDataRouterdeviceinRNCareimplementedtogetherwiththeRadioNetworkLayerfunctionsforIu-puserplaneterminationsinRNC.TheyarerepresentedbyPdrDeviceandPacketDataRouterMOs,andthusmanagedaspartsoftheradionetworklayermanagement,RncFunction.EachPdrDeviceMOrepresentsaprocessorunitwhichcanconnectuptoeightAAL5/ATMVCCs.EachsuchVCCterminationcorrespondstoanIPhostfunctionandisrepresentedbyaPacketDataRouterMO.ItisrecommendedtoconfiguretwoAAL5/ATMVCCsperPdrDeviceasdepictedinthefollowingfigure.Figure30RNCGTP-UPathstoSGSNInthecaseofIuFlexitmightbenecessarytoconfigureuptothemaximumofeightAAL5/ATMVCCsperPdrDeviceasitmustbepossibletoconfigureIPlinksfromonePdrDevicetomultipleSGSNnodes.Table56RNCGTP-UPathstoSGSNPos.MO:=Parent:=,...=Comment1MO:AtmTrafficDescriptor=u3pmParent:TransportNetwork=1ingressAtmPcr=egressAtmPcr=ingressAtmMcr=egressAtmMcr=ingressAtmQos=CLASS_THREEATMtrafficdescriptorforAAL2pathforIu.SeeSection4.5.2regardingpcrvalues.egressAtmQos=CLASS_THREEserviceCategory=UBR+packetDiscard=false2MO:VclTp=vcParent:...,VpcTp(Pos.3inTable51.)externalVci=ATMVCCforGTP-U.SeeSection2.6.2.4.atmTrafficDescriptorId=ReferencetoMOinPos.1.3MO:Aal5TpVccTp=pgParent:TransportNetwork=1(n=sequencenumberforidentificationofmultipleAal5TpVccTpMOsforGTP-Upathstowardsthecorenetwork.)processorId=ReferencetotheSpmMOforthePDRprocessorwhichshallterminatetheGTP-Upath.SeeSection2.3.3.3andSection2.6.2.4.vclTpId=ReferencetoMOinPos.2.fromUserMaxSduSize=1600toUserMaxSduSize=1600SeeSection4.5.2.6.3.2.8IuFlexThissectionassumesthattheconfigurationspecifiedinprevioussectionsofSection6.3.2hasbeencompleted.AlsonotethateachadditionalCNnoderequiresauniqueSccpApRemoteMO,Mtp3bApMOandMtp3bSrsMOtobedefined.ThisalsorequiresthatthenamingconventionfortheseMOsbemodifiedtoaccommodatethemultipleinstances.Thesuggestionis:\uf0a7ForCSdomainusecswheren=sequencenumberforidentificationofMOstowardstheCScorenetwork.\uf0a7ForPSdomainusepswheren=sequencenumberforidentificationofMOstowardsthePScorenetwork.IuFlexrequiresnewIuLinkandRanapMOstobecreatedforeachCNnode.Table57IuFlexPos.MO:=Parent:=,...=Comment1MO:RncFunction=1networkResourceIdentifierLengthCs=networkResourceIdentifierLengthPs=TheattributevalueneedstobegreaterthanzeroforIuFlextobeactive.2MO:CnOperator=Parent:RncFunction=1Usedescriptivename.3MO:IuLink=csParent:CnOperatoratmUserPlaneTermSubrackRef=ReferencetotheSubrackManagedObjectthatrepresentsthesubrackwheretheATMuserplaneterminationoftheIuLinkislocated.Note:Iu-CSUserPlaneshouldpointtoMS.userPlaneTransportOption=atmUserplanetransportoptionforthisIuLink.4MO:Ranap=cs(n=sequencenumberforidentificationofmultipleRanapMOscnDomainInd=0IndicatesCSdomain.cnId=Donotre-usevaluesforCNnodesinsametowardsthecorenetwork.)Parent:IuLink=csdomain.networkResourceIdentifier=Donotre-usevaluesforCNnodesinsamedomain.relativeCapacity=5MO:IuLink=psParent:CnOperatoratmUserPlaneTermSubrackRef=ReferencetotheSubrackManagedObjectthatrepresentsthesubrackwheretheATMuserplaneterminationoftheIuLinkislocateduserPlaneTransportOption=atmUserplanetransportoptionforthisIuLink.packetDataRouterRef=ReferencetoPacketDataRouterMOorIpEthPacketDataRouterMO.6MO:Ranap=ps(n=sequencenumberforidentificationofmultipleRanapMOstowardsthecorenetwork.)Parent:IuLink=pscnDomainInd=1IndicatesPSdomain.cnId=Donotre-usevaluesforCNnodesinsamedomain.networkResourceIdentifier=Donotre-usevaluesforCNnodesinsamedomain.relativeCapacity=RelativecapacityofthisRanapinstance(CNnode)comparedtoothernodesinthedomain.6.3.3ConfigurationofIurInterfaces6.3.3.1IurLinkObjectforEachConnectedRNCOneMOinstanceofclassIurLinkiscreatedinRNCforeachotherRNCtowhichanIurrelationistobecreated.ThisMOanditsattributesbelongtotheradionetworklayer.Figure31RNCIurLinktoOtherRNCTable58RNCIurLinktoOtherRNCPos.MO:=Parent:=,...=Comment1MO:IurLink=Parent:RncFunction=1atmUserPlaneTermSubrackRef=ReferencetotheSubrackManagedObjectthatrepresentsthesubrackwheretheATMuserplaneterminationoftheIurLinkislocated.TheIurUserPlaneshouldbeterminatedintheMS.6.3.3.2VPCTerminationforIurItisinthisexampleitisassumedthataseparatepair(forredundancy)ofVPCsaresetupforeachIurlink,usingthesamepairofphysicallinkstowardstheRNSGWnodeastheIuconnections.TheseVPCsareassumedtobecrossconnectedtotheotherRNCthroughtheRNSGWnode.Thisisanexampleofthe"dedicatedtopology"describedinSection2.2.2.Figure32RNCVirtualPathforIurTable59RNCVirtualPathforIurPos.MO:=Parent:=,...=Comment1MO:AtmTrafficDescriptor=C1PParent:TransportNetwork=1ingressAtmPcr=egressAtmPcr=ingressAtmQos=CLASS_ONEegressAtmQos=CLASS_ONEserviceCategory=CBRATMtrafficdescriptorforVirtualPathforO&MSeeSection4.6.2.2regardingpeakcellrate(pcr)value.2MO:VplTp=vpParent:...,AtmPort=MS-6-1externalVpi=SeeSection2.6.1.2regardingassignmentofVPIvaluesforIuratmTrafficDescriptor=ReferencetoMOinPos.13MO:VpcTp=1Parent:...,VplTp=vp1(Pos.2)VPconnectiontermination6.3.3.3MTP-3bSignalingRoutestoOtherRNCEachdirectlyconnectedremoteRNCnodeandtypeofsignalingserviceisrepresentedbyanaccesspointforMTP-3bsignaling,Mtp3bAp.TheroutingpossibilitiesforMTP-3bmessagestoeachremotenodeisrepresentedbyconfigurationofsignalingroutesetsMtp3bSrs,signalingroutes,Mtb3bSr,andsignalinglinksets,Mtb3bSls.Figure33RNCMTP-3bSignalingforIurTable60RNCMTP-3bSignalingforIurpos.MO:=Parent:=,...=Comment1MO:Mtp3bSrs=rsParent:Mtp3bSpItu=1(Pos.1inTable52)desPointCode=ThepointcodeallocatedtotheotherRNC.autoReroute=false2MO:Mtp3bSls=rsParent:Mtp3bSpItu=1(Pos.1inTable52)mtp3bSrsId=ReferencetoMOinPos.1.3MO:Mtp3bSr=1LinkSetM3uId=ReferencetoMOinParent:Mtp3bSrs=rs(Pos.1)Pos.2.priority=14MO:Mtp3bAp=rsParent:Mtp3bSpItu=1(Pos.1inTable52)routeSetId=ReferencetoMOinPos.1.serviceInd=3IndicatesSCCPusage.5MO:Mtp3bAp=rqParent:Mtp3bSpItu=1(Pos.1inTable52)routeSetId=ReferencetoMOinPos.1(AssumesthatthesameSS7destinationpointcodeisvalidforQ.2630andRNSAPtotheotherRNC.)serviceInd=12IndicatesQ.2630usage.6.3.3.4SignalingLinkstoOtherRNCFigure34RNCSignalingLinkstoOtherRNCTable61RNCSignalingLinkstoOtherRNCPos.MO:=Parent:=,...=Comment1MO:AtmTrafficDescriptor=U3PMingressAtmPcr=ATMtrafficdescriptorforParent:TransportNetwork=1egressAtmPcr=ingressAtmMcr=egressAtmMcr=ingressAtmQos=CLASS_THREEegressAtmQos=CLASS_THREEserviceCategory=UBR+packetDiscard=trueSAAL-NNIsignalinglinksforIur.SeeSection4.4.1.3regardingpcrandmcrvalues2MO:VclTp=vc36Parent:...,VpcTp(Pos.3inTable59.)externalVci=36SignalinglinktootherRNC.SeeSection2.6.2.5.atmTrafficDescriptorId=ReferencetoMOinPos.13MO:Aal5TpVccTp=rsaParent:TransportNetwork=1processorId=ReferencetoPlugInUnitforactiveSccpMP,forexample,MS-8inRNC3810andMS-7inRNC3820SeeSection2.3.2.1andSection2.6.2.5.vclTpId=ReferencetoMOinPos.2.fromUserMaxSduSize=280toUserMaxSduSize=280SeeSection4.4.1.4MO:NniSaalProfile=win100Parent:TransportNetwork=1Seeprofile"win100"inSection4.4.1.4RecommendedprofileforSAAL-NNIsignalinglinksbetweenRNCs.SeeSection4.4.15MO:NniSaalTp=rsaParent:TransportNetwork=1nniSaalProfileId=RecommendedprofileforSAAL-NNIsignalinglinksbetweenRNCs.SeeSection4.4.1.aal5TpVccTpId=ReferencetoMOinPos.4.MaxSduSize=276SeeSection4.4.16MO:Mtp3bSlItu=rsaParent:Mtp3bSls=cs(Pos.4inTable60.tpId=ReferencetoMOinPos.5.sigLinkCode=0-15Settodifferentvaluesfordifferentlinksinthesamesignalinglinkset.6.3.3.5SCCPandRNSAPFigure35RNCSCCPSignalingforIurTable62RNCSignalingLinkstoOtherRNCPos.MO:=Parent:=,...=Comment1MO:SccpApLocal=rsParent:SccpScrc=1(Pos.3inTable54)(LocalAPforRNSAP)ssN=143SubsystemnumberforRNSAP=143(3GPPTS23.003)maxConn==NumberofsimultaneousSCCPconnectionsforRNSAP,forexample,10000(fromtrafficdimensioning).useS1=trueOPCisaddedtoCallingPartAddressifabsent2MO:SccpApRemote=rParent:SccpScrc=1(Pos.3inTable54)(RemoteAPforRNC)ssN=143SubsystemnumberforRNSAP=143(3GPPTS23.003)mtp3bApId=ReferencetoMOinPos4inTable603MO:Rnsap=1Parent:RncFunction=1localSccpApRef=ReferencetoMOinPos.1.remoteSccpApRef=ReferencetoMOinPos.2.sccpGlobalTitleRef=nullsccpDisabledT=100userOutOfServiceT=1006.3.3.6AAL2ControlandUserPlaneforIurThissectioncoversconfigurationofboththeAAL2controlplanewiththeQ.2630signalingprotocoltermination,Aal2Ap,andtheAAL2paths,Aal2PathVccTp,onwhichAAL2userplanebearerscanbeconnected.AnAAL2Pathcancarryupto248switchedAAL2connections.SeveralAAL2paths,relatedtothesameresourcehandler,Aal2PathDistributionUnit,mayneedtobeconfiguredonthetwoVirtualPathsbetweenapairofRNCsdependingonsite-specifictrafficdimensioning.Figure36RNCAAL2forIurTable63RNCAAL2forIurPos.MO:=Parent:=,...=Comment1MO:Aal2QoSCodePointProfile=1Parent:TransportNetwork=1SeeSection3.2.7.1.2MO:Aal2Ap=rqParent:Aal2Sp=1(Pos.1inTable55)sigLinkId=ReferencetoMOinPos.5inTable60.secondarySigLinkId=nullNoMOreference(=default)allocationMode=manualForIuritshouldbesettomanual.rpuId=ReferencetoMOinPos.2inTable38.aal2QoSCodePointProfile=ReferencetoMOinPos.1.3MO:Aal2RoutingCase=ndParent:TransportNetwork=1numberDirection=RoutingcasefornumberdirectionrouteList=ReferencetoMOinPos.1(MultipleAal2Apreferencescanbespecifiedforalternativerouting)4MO:AtmTrafficDescriptor=c2pParent:TransportNetwork=1ingressAtmPcr=egressAtmPcr=ingressAtmQos=CLASS_TWOegressAtmQos=CLASS_TWOserviceCategory=CBRATMtrafficdescriptorforAAL2pathforIur.SeeSection4.5.3regardingpcrvalues.5MO:VclTp=vcParent:...,VpcTp(Pos.3inTable59)externalVci=Aal2pathtowardsotherRNC.SeeSection2.6.2.5.atmTrafficDescriptorId=ReferencetoMOinPos.4.6MO:Aal2QoSProfile=1Parent:TransportNetwork=1SeeSection3.2.7.2.7MO:Aal2PathVccTp=rParent:TransportNetwork=1(n=sequencenumberforidentificationofmultipleAal2PathVccTpMOstowardstheotherRNC)vclTpId=ReferencetoMOinPos.5.aal2PathId=SeeSection2.7.1.4.Coordinationofpathidentifiervalue(pid)withconfigurationofremotenodeneeded.Range:Integer>0aal2PathOwner=(trueorfalse)Sitedependentvalue.CoordinationofAAL2pathownershipbetweentheRNCneeded.aal2QoSProfileId=ReferencetoMOinPos.6.aal2QoSAvailableProfiles=CLASS_A_B_C8MO:Aal2PathDistributionUnit=1Parent=...,Aal2Ap=rq,Pos.3rpuId=ReferencetoMOinPos4inTable38.aal2PathVccTpList=(sequenceofMOref)ReferencetoMOinPos.7andadditionalAal2PathstobecontrolledbythesameAal2Ap.6.4RBSConfiguration6.4.1RNCConfigurationforMubTransfer6.4.1.1ATMVCCcross-connectforO&MAccesstoRBSThispartcoverstheRNCconfigurationofphysicalandATMportinterfacesusedtoconnectanRBStoRNCandthecross-connectinRNCoftheVCCforMubtowardstheRANO&MRouter.Inthisexample,theRBSisconnectedtotheRNCthroughadedicatedVPCthroughanintermediateATMcross-connectnetworkusinganSTM-1/VC-4physicalinterfacetoRNC.ThephysicalinterfacetoRNCmayincludemultipleVirtualPathsforconnectionstomultipleRBSs.ThephysicallinkterminationandATMportobjectsdothennotneedtobecreatedforeachRBS.TheMOsthatneedtobecreatedareshowninFigure37.TheshadedboxesillustrateadditionalMOsthatareneededforconnectionoftheRBSthroughdualVPCsandphysicallinkterminationsforlinkredundancy.MOrelationsandmandatoryattributesforaminimumconfigurationwithoutanyredundancyisdescribedinTable64.Previouslycreated,referencedMOsaremarkedwithdashedlinesinthefigure.MOsthatmaybecommonforseveralRBSconnectionsareindicatedwithinparenthesis.MOsthatarerequiredforprocessororlinkredundancyaremarkedwiththinlines.ThoseMOswhicharerequiredonlyforIublinkredundancyareshaded.Figure37RNCConfigurationforO&MAccesstoRBSThroughVCCCross-ConnectTable64RNCConfigurationforO&MAccesstoRBSThroughVCCCross-ConnectPos.MO:=Parent:=,...=Comment1MO:AtmTrafficDescriptor=C1PParent:TransportNetwork=1ingressAtmPcr=egressAtmPcr=ingressAtmQos=CLASS_ONEegressAtmQos=CLASS_ONEserviceCategory=CBRATMtrafficdescriptorforVirtualPathforRBS.SeeSection3.2.6.1regardingMOnamingconvention.SeeSection4.6.3regardingpeakcellrate(pcr)value.2MO:VplTp=vpParent:...,AtmPort=ES1-2-1externalVpi=SeeSection2.6.1.4atmTrafficDescriptor=ReferencetoMOinPos.1.3MO:VpcTp=1Parent:...,VplTp=vp(Pos.2)VPconnectiontermination4MO:VclTp=vc32Parent:...,VpcTp=1(Pos.5)externalVci=32MubVClinkRNC->RBSSeeSection2.6.2.2regardingVCIallocationatmTrafficDescriptorId=ReferencetoAtmTrafficDescriptor=U4inTable43.5MO:VclTp=vcParent:...,VpcTp=1(Pos.7inTable43.externalVci=MubVClinkRNC->RANO&MRouter.SeeSection2.6.2.2regardingVCIallocation.atmTrafficDescriptorId=ReferencetoAtmTrafficDescriptor=U4inTable43.6MO:AtmCrossConnection=biaParent:TransportNetwork=1vcTpAId=ReferencetoMOinPos.4.vcTpBId=ReferencetoMOinPos.5.6.4.2RNCConfigurationforIubtoRBS6.4.2.1IubLinkObjectforEachControlledRBSOneMOinstanceofclassIubLinkiscreatedinRNCforeachRBStobecontrolledbytheRNC.TheIubLinkobjectiscreatedwithareferencetotheRncModuleMOrepresentingthesubgroupofRNCprocessorresourcestowhichtheRBScontrolresponsibilityisallocated.ThisreferencethusdefinesonwhichRNCModuleMPsthesignalinglinkterminationstotheRBSshallbeconfigured.Figure38RNCIubRelationtoRNCModuleTable65RNCIubRelationtoRNCModulePos.MO:=Parent:=