QChat原理及系統(tǒng)架構(gòu)課件

1、QChat原理及系統(tǒng)架構(gòu)QChat項目團隊2010/07/122 | CTC QCHAT TrainingAll Rights Reserved Alcatel-Lucent Shanghai Bell 2010Solution Architecture for ShanghaiDFEHADMCCRDRULSRMUSDSDNSNTPeSMLBGLMSOMCQBSNPDSNRNCOMCRMSSHLRShanghai NetworkCo-located QChat Region and CoreShanghaiCPSPDRSMSCCRMAAADNSNMSCTC Province SuppliedC

2、TC Shanghai SuppliedALU ProductQAS Supplied through ALU3rd Party Supplied by ALUPayloadClients: QChat GLMSSubscriber Orderscome in hereAAA-QInternetWeb Portal UserSMGWWAPHTTP/XCAPOMCQSMGPPortalHTTPXCAPBillerSubscriberInvoicesSubscriber Ordersalso entered hereManagementXlate3 | CTC QCHAT TrainingAll

3、Rights Reserved Alcatel-Lucent Shanghai Bell 2010Provisioning Flow USDSeSMGLMSCPSCRMAAA-QCRMCRMOMC-RPortalWeb Portal UserDispatch ConsoleOrderMgrHLRAAA-ROrderMgrHLRAAA-ROtherProvincesOtherProvincesOtherProvinces SOAP/XML XCAP (Groups and DM) RNC LGC Cluster QueriesRNC SMGP SMPP (Update Notify)4 | CT

4、C QCHAT TrainingAll Rights Reserved Alcatel-Lucent Shanghai Bell 2010Billing Flow - TargetRULSNationalBillingCollectorRULSMultiple RULS inMultiple RegionsDedicatedDirectoryDedicatedDirectoryNationalRating &InvoicingGovernment and otherNational CorporationsProvincialRating &InvoicingUDRProcessingProv

5、incialRating &InvoicingOtherProvincesSubscriberInvoiceSubscriberInvoice (S)FTP Push5 | CTC QCHAT TrainingAll Rights Reserved Alcatel-Lucent Shanghai Bell 2010Binary to TextUDR TranslatorBilling Flow Shanghai TrialRULSShanghaiBillingCollectorRULSTwo RULS inShanghai RegionsInputDirectoryOutputDirector

6、yUDRProcessingSubscriberInvoice SFTP Push FTP Pull6 | CTC QCHAT TrainingAll Rights Reserved Alcatel-Lucent Shanghai Bell 2010Fault FlowDFEHADMCCRDRULSRMUSDSeSMGLMSOMCQOMCQNMS SNMPv2 SNMPv3MM /BNTMM /BNT7 | CTC QCHAT TrainingAll Rights Reserved Alcatel-Lucent Shanghai Bell 2010NTP FlowQASCoreCPSPorta

7、lQASRegionRMUSDSeSMGLMSOMCQCoreOMCQRegionNTPsourceNTPsourceExternal to HPPTTCiscoswitchCiscoswitch NTPv4Cisco switches serve as time reference for all HPPTT Network Elements8 | CTC QCHAT TrainingAll Rights Reserved Alcatel-Lucent Shanghai Bell 2010IP ConnectivityNote: for Shanghai TrialTraffic and O

8、AM routersare one and the same9 | CTC QCHAT TrainingAll Rights Reserved Alcatel-Lucent Shanghai Bell 2010GLMS CFBNT Switchin BCT chassisPhysical QChat LB ConnectivityF5 3600 LBF5 3600 LBTrafficL2/L3Switch/RouterTrafficL2/L3Switch/RouterOAML2/L3Switch/RouterOAML2/L3Switch/RouterAlive?100 Mb/s CopperR

9、egistrationManager3 chassis in Region (2 w. DCH, 2 w. Portal, 2. w. CPS)To/From OSSIncoming TrafficMirrorManagementSNMP Health ChecksMgmtSNMP HCIngressEgressIngressEgressRLSRLSRLSDCHDCHPortalCPS1 Gb/s CopperNote: for Shanghai TrialTraffic and OAM routersare one and the same10 | CTC QCHAT TrainingAll

10、 Rights Reserved Alcatel-Lucent Shanghai Bell 2010Logical QChat LB ConnectivityVS_RMVS_DCHVS_PortalRLSRLSDCHDCHPortalPortalOMC-RAN F5 VLAN-CN2 -Internet -ENIRM VLANPTT VLANPortal VLANRepliesRepliesVS_GLMSCFCFGLMS VLANRepliesVS_CPSCPSCPSCPS VLANCRMPortal User11 | CTC QCHAT TrainingAll Rights Reserved

11、 Alcatel-Lucent Shanghai Bell 2010RM Load BalancingF5 3600 LBTrafficL2/L3Switch/RouterRegistrationManagerBNT Switchin BCT chassisIncoming/Outgoing TrafficRM traffic uses SIP protocol. Persistence is required. Return traffic must go through the LB as it will be configured to inspect such traffic. F5

12、health check for RLS uses SIP Options.12 | CTC QCHAT TrainingAll Rights Reserved Alcatel-Lucent Shanghai Bell 2010RLSKernel IP StackPlatform Overload LogicRLS Application LogicF5Up to 340,000 Clients per RLS PairSIP Options MonitorRegistration Virtual ServerInspect Reply12Client / Load Balancer / Re

13、gistration Manager Components and Interfaces See slide notes forexplanation13 | CTC QCHAT TrainingAll Rights Reserved Alcatel-Lucent Shanghai Bell 2010DCH Load BalancingF5 3600 LBTraffic/OAML2/L3Switch/RoutersRegistrationManagerBNT Switchin BCT chassis3 chassis in Region (2 with DCH)Incoming/Outgoin

14、g TrafficDCH traffic uses QSP (proprietary UDP-based) protocol. Persistence is not required. Return traffic must NOT go through the LB as it cannot be distinguished from other DCH to Client traffic. F5 health check for DCH uses SNMP over OAM.14 | CTC QCHAT TrainingAll Rights Reserved Alcatel-Lucent

15、Shanghai Bell 2010Portal Load BalancingF5 3600 LBTrafficL2/L3Switch/RouterBNT Switchin BCT chassis3 chassis in Region (2 with Portal)Incoming/Outgoing TrafficPortal traffic uses HTTP protocol. Persistence is recommended, interval longer than login inactivity timer (30 min). Return traffic must go th

16、rough the LB as F5 has external (real) Internet IP address, but Portal Pool has private IPs. F5 health check for Portal uses HTTP.15 | CTC QCHAT TrainingAll Rights Reserved Alcatel-Lucent Shanghai Bell 2010CPS Load BalancingF5 3600 LBTrafficL2/L3Switch/RouterBNT Switchin BCT chassis3 chassis in Regi

17、on (2 with Portal)Incoming/Outgoing TrafficCPS traffic uses HTTP protocol. Persistence is not used. Return traffic will go through the LB. F5 health check for CPS uses HTTP.16 | CTC QCHAT TrainingAll Rights Reserved Alcatel-Lucent Shanghai Bell 2010GLMS CF Load BalancingF5 3600 LBTrafficL2/L3Switch/RouterCFIncoming/Outgoing TrafficGLMS traffic uses HTTP/XCAP protocol. Persistence is not required. Return traffic should go through the LB. The F5 needs to use SNAT to facilitate t