QChat原理及系统架构

QChat原理及系统架构QChat项目团队2010/07/12SolutionArchitectureforShanghaiDFEHADMCCRDRULSRMUSDSDNSNTPeSMLBGLMSOMCQBSNPDSNRNCOMCRMSSHLRShanghaiNetworkCo-locatedQChatRegionandCoreShanghaiCPSPDRSMSCCRMAAADNSNMSCTCProvinceSuppliedCTCShanghaiSuppliedALUProductQASSuppliedthroughALU3rdPartySuppliedbyALUPayloadClients:QChatGLMSSubscriberOrderscomeinhereAAA-QInternetWebPortalUserSMGWWAPHTTP/XCAPOMCQSMGPPortalHTTPXCAPBillerSubscriberInvoicesSubscriberOrdersalsoenteredhereManagementXlate2ProvisioningFlowUSDSeSMGLMSCPSCRMAAA-QCRMCRMOMC-RPortalWebPortalUserDispatchConsoleOrderMgrHLRAAA-ROrderMgrHLRAAA-ROtherProvincesOtherProvincesOtherProvinces

SOAP/XML

XCAP(GroupsandDM)

RNCLGCClusterQueriesRNC

SMGPSMPP(UpdateNotify)3BillingFlow-TargetRULSNationalBillingCollectorRULSMultipleRULSinMultipleRegionsDedicatedDirectoryDedicatedDirectoryNationalRating&InvoicingGovernmentandotherNationalCorporationsProvincialRating&InvoicingUDRProcessingProvincialRating&InvoicingOtherProvincesSubscriberInvoiceSubscriberInvoice

(S)FTPPush4BinarytoTextUDRTranslatorBillingFlow–ShanghaiTrialRULSShanghaiBillingCollectorRULSTwoRULSinShanghaiRegionsInputDirectoryOutputDirectoryUDRProcessingSubscriberInvoice

SFTPPushFTPPull5FaultFlowDFEHADMCCRDRULSRMUSDSeSMGLMSOMCQOMCQNMS

SNMPv2

SNMPv3MM/BNTMM/BNT6NTPFlowQASCoreCPSPortalQASRegionRMUSDSeSMGLMSOMCQCoreOMCQRegionNTPsourceNTPsourceExternaltoHPPTTCiscoswitchCiscoswitch

NTPv4CiscoswitchesserveastimereferenceforallHPPTTNetworkElements7IPConnectivityNote:forShanghaiTrialTrafficandOAMroutersareoneandthesame8GLMSCFBNTSwitchinBCTchassisPhysicalQChatLBConnectivityF53600LBF53600LBTrafficL2/L3Switch/RouterTrafficL2/L3Switch/RouterOAML2/L3Switch/RouterOAML2/L3Switch/RouterAlive?100Mb/sCopperRegistrationManager3chassisinRegion(2w.DCH,2w.Portal,2.w.CPS)To/FromOSSIncomingTrafficMirrorManagementSNMPHealthChecksMgmtSNMPHCIngressEgressIngressEgressRLSRLS…RLSDCHDCHPortalCPS……1Gb/sCopperNote:forShanghaiTrialTrafficandOAMroutersareoneandthesame9LogicalQChatLBConnectivityVS_RMVS_DCHVS_PortalRLSRLS…DCHDCH…PortalPortal…OMC-RAN

F5VLAN-CN2-Internet-ENIRMVLANPTTVLANPortalVLANRepliesRepliesVS_GLMSCFCF…GLMSVLANRepliesVS_CPSCPSCPS…CPSVLANCRMPortalUser10RMLoadBalancingF53600LBTrafficL2/L3Switch/RouterRegistrationManagerBNTSwitchinBCTchassisIncoming/OutgoingTrafficRMtrafficusesSIPprotocol.Persistenceisrequired.ReturntrafficmustgothroughtheLBasitwillbeconfiguredtoinspectsuchtraffic.F5healthcheckforRLSusesSIPOptions.11RLSKernelIPStackPlatformOverloadLogicRLSApplicationLogicF5Upto340,000ClientsperRLSPairSIPOptionsMonitorRegistrationVirtualServerInspectReply12Client/LoadBalancer/RegistrationManagerComponentsandInterfacesSeeslidenotesforexplanation12DCHLoadBalancingF53600LBTraffic/OAML2/L3Switch/RoutersRegistrationManagerBNTSwitchinBCTchassis3chassisinRegion(2withDCH)Incoming/OutgoingTrafficDCHtrafficusesQSP(proprietaryUDP-based)protocol.Persistenceisnotrequired.ReturntrafficmustNOTgothroughtheLBasitcannotbedistinguishedfromotherDCHtoClienttraffic.F5healthcheckforDCHusesSNMPoverOAM.13PortalLoadBalancingF53600LBTrafficL2/L3Switch/RouterBNTSwitchinBCTchassis3chassisinRegion(2withPortal)Incoming/OutgoingTrafficPortaltrafficusesHTTPprotocol.Persistenceisrecommended,intervallongerthanlogininactivitytimer(30min).ReturntrafficmustgothroughtheLBasF5hasexternal(real)InternetIPaddress,butPortalPoolhasprivateIPs.F5healthcheckforPortalusesHTTP.14CPSLoadBalancingF53600LBTrafficL2/L3Switch/RouterBNTSwitchinBCTchassis3chassisinRegion(2withPortal)Incoming/OutgoingTrafficCPStrafficusesHTTPprotocol.Persistenceisnotused.ReturntrafficwillgothroughtheLB.F5healthcheckforCPSusesHTTP.15GLMSCFLoadBalancingF53600LBTrafficL2/L3Switch/RouterCFIncoming/OutgoingTrafficGLMStrafficusesHTTP/XCAPprotocol.Persistenceisnotrequired.ReturntrafficshouldgothroughtheLB.TheF5needstouseSNATto