2.QChat原理及系统架构.ppt

QChat原理及系统架构,QChat项目团队2010/07/12,SolutionArchitectureforShanghai,DFE,HAD,MCC,RD,RULS,RM,USDS,DNS,NTP,eSM,LB,GLMS,OMCQ,BSN,PDSN,RNC,OMCR,MSS,HLR,ShanghaiNetwork,Co-locatedQChatRegionandCoreShanghai,CPS,PDR,SMSC,CRM,AAA,DNS,NMS,Payload,Clients:QChatGLMS,SubscriberOrderscomeinhere,AAA-Q,Internet,WebPortalUser,SMGW,WAP,HTTP/XCAP,OMCQ,SMGP,Portal,HTTP,XCAP,Biller,SubscriberInvoices,SubscriberOrdersalsoenteredhere,Management,Xlate,ProvisioningFlow,USDS,eSM,GLMS,CPS,CRM,AAA-Q,CRM,CRM,OMC-R,Portal,WebPortalUser,DispatchConsole,SOAP/XML,XCAP(GroupsandDM),RNCLGCClusterQueries,RNC,SMGPSMPP(UpdateNotify),BillingFlow-Target,RULS,NationalBillingCollector,RULS,MultipleRULSinMultipleRegions,DedicatedDirectory,DedicatedDirectory,NationalRating&Invoicing,GovernmentandotherNationalCorporations,ProvincialRating&Invoicing,UDRProcessing,ProvincialRating&Invoicing,OtherProvinces,(S)FTPPush,BinarytoTextUDRTranslator,BillingFlowShanghaiTrial,RULS,ShanghaiBillingCollector,RULS,TwoRULSinShanghaiRegions,InputDirectory,OutputDirectory,UDRProcessing,SFTPPushFTPPull,FaultFlow,DFE,HAD,MCC,RD,RULS,RM,USDS,eSM,GLMS,OMCQ,OMCQ,NMS,SNMPv2,SNMPv3,MM/BNT,MM/BNT,NTPFlow,QASCore,CPS,Portal,QASRegion,RM,USDS,eSM,GLMS,OMCQCore,OMCQRegion,NTPsource,NTPsource,ExternaltoHPPTT,Ciscoswitch,Ciscoswitch,NTPv4,CiscoswitchesserveastimereferenceforallHPPTTNetworkElements,IPConnectivity,Note:forShanghaiTrialTrafficandOAMroutersareoneandthesame,BNTSwitchinBCTchassis,PhysicalQChatLBConnectivity,F53600LB,F53600LB,TrafficL2/L3Switch/Router,TrafficL2/L3Switch/Router,OAML2/L3Switch/Router,OAML2/L3Switch/Router,Alive?,100Mb/sCopper,RegistrationManager,3chassisinRegion(2w.DCH,2w.Portal,2.w.CPS),To/FromOSS,IncomingTraffic,Mirror,Management,SNMPHealthChecks,Mgmt,SNMPHC,Ingress,Egress,Ingress,Egress,Portal,1Gb/sCopper,Note:forShanghaiTrialTrafficandOAMroutersareoneandthesame,LogicalQChatLBConnectivity,VS_RM,VS_DCH,VS_Portal,RLS,RLS,DCH,DCH,Portal,Portal,OMC-RAN,F5VLAN-CN2-Internet-ENI,RMVLAN,PTTVLAN,PortalVLAN,Replies,Replies,VS_GLMS,CF,CF,GLMSVLAN,Replies,VS_CPS,CPS,CPS,CPSVLAN,CRM,PortalUser,RMLoadBalancing,F53600LB,TrafficL2/L3Switch/Router,Incoming/OutgoingTraffic,RMtrafficusesSIPprotocol.Persistenceisrequired.ReturntrafficmustgothroughtheLBasitwillbeconfiguredtoinspectsuchtraffic.F5healthcheckforRLSusesSIPOptions.,RLS,KernelIPStack,PlatformOverloadLogic,RLSApplicationLogic,F5,Upto340,000ClientsperRLSPair,SIPOptionsMonitor,RegistrationVirtualServer,InspectReply,1,2,Client/LoadBalancer/RegistrationManagerComponentsandInterfaces,Seeslidenotesforexplanation,DCHLoadBalancing,F53600LB,Traffic/OAML2/L3Switch/Routers,Incoming/OutgoingTraffic,DCHtrafficusesQSP(proprietaryUDP-based)protocol.Persistenceisnotrequired.ReturntrafficmustNOTgothroughtheLBasitcannotbedistinguishedfromotherDCHtoClienttraffic.F5healthcheckforDCHusesSNMPoverOAM.,PortalLoadBalancing,F53600LB,TrafficL2/L3Switch/Router,Incoming/OutgoingTraffic,PortaltrafficusesHTTPprotocol.Persistenceisrecommended,intervallongerthanlogininactivitytimer(30min).ReturntrafficmustgothroughtheLBasF5hasexternal(real)InternetIPaddress,butPortalPoolhasprivateIPs.F5healthcheckforPortalusesHTTP.,CPSLoadBalancing,F53600LB,TrafficL2/L3Switch/Router,Incoming/OutgoingTraffic,CPStrafficusesHTTPprotocol.Persistenceisnotused.ReturntrafficwillgothroughtheLB.F5healthcheckforCPSusesHTTP.,GLMSCFLoadBalancing,F53600LB,TrafficL2/L3Switch/Router,Incoming/OutgoingTraffic,GLMStrafficusesHTTP/XCAPprotocol.Persistenceisnotrequired