QChat原理及系统架构.ppt

1、QChat原理及系统架构,QChat项目团队 2010/07/12,Solution Architecture for Shanghai,DFE,HAD,MCC,RD,RULS,RM,USDS,DNS,NTP,eSM,LB,GLMS,OMCQ,BSN,PDSN,RNC,OMCR,MSS,HLR,Shanghai Network,Co-located QChat Region and Core Shanghai,CPS,PDR,SMSC,CRM,AAA,DNS,NMS,Payload,Clients: QChat GLMS,Subscriber Orders come in here,AAA-Q

2、,Internet,Web Portal User,SMGW,WAP,HTTP/ XCAP,OMCQ,SMGP,Portal,HTTP,XCAP,Biller,Subscriber Invoices,Subscriber Orders also entered here,Management,Xlate,Provisioning Flow,USDS,eSM,GLMS,CPS,CRM,AAA-Q,CRM,CRM,OMC-R,Portal,Web Portal User,Dispatch Console, SOAP/XML, XCAP (Groups and DM), RNC LGC Cluste

3、r Queries,RNC, SMGP SMPP (Update Notify),Billing Flow - Target,RULS,National Billing Collector,RULS,Multiple RULS in Multiple Regions,Dedicated Directory,Dedicated Directory,National Rating & Invoicing,Government and other National Corporations,Provincial Rating & Invoicing,UDR Processing,Provincial

4、 Rating & Invoicing,Other Provinces, (S)FTP Push,Binary to Text UDR Translator,Billing Flow Shanghai Trial,RULS,Shanghai Billing Collector,RULS,Two RULS in Shanghai Regions,Input Directory,Output Directory,UDR Processing, SFTP Push FTP Pull,Fault Flow,DFE,HAD,MCC,RD,RULS,RM,USDS,eSM,GLMS,OMCQ,OMCQ,N

5、MS, SNMPv2, SNMPv3,MM / BNT,MM / BNT,NTP Flow,QAS Core,CPS,Portal,QAS Region,RM,USDS,eSM,GLMS,OMCQ Core,OMCQ Region,NTP source,NTP source,External to HPPTT,Cisco switch,Cisco switch, NTPv4,Cisco switches serve as time reference for all HPPTT Network Elements,IP Connectivity,Note: for Shanghai Trial

6、Traffic and OAM routers are one and the same,BNT Switch in BCT chassis,Physical QChat LB Connectivity,F5 3600 LB,F5 3600 LB,Traffic L2/L3 Switch/Router,Traffic L2/L3 Switch/Router,OAM L2/L3 Switch/Router,OAM L2/L3 Switch/Router,Alive?,100 Mb/s Copper,Registration Manager,3 chassis in Region (2 w. DC

7、H, 2 w. Portal, 2. w. CPS),To/From OSS,Incoming Traffic,Mirror,Management,SNMP Health Checks,Mgmt,SNMP HC,Ingress,Egress,Ingress,Egress,P o r t a l,1 Gb/s Copper,Note: for Shanghai Trial Traffic and OAM routers are one and the same,Logical QChat LB Connectivity,VS_RM,VS_DCH,VS_Portal,RLS,RLS,DCH,DCH

8、,Portal,Portal,OMC-RAN,F5 VLAN-CN2 -Internet -ENI,RM VLAN,PTT VLAN,Portal VLAN,Replies,Replies,VS_GLMS,CF,CF,GLMS VLAN,Replies,VS_CPS,CPS,CPS,CPS VLAN,CRM,Portal User,RM Load Balancing,F5 3600 LB,Traffic L2/L3 Switch/Router,Incoming/Outgoing Traffic,RM traffic uses SIP protocol. Persistence is requi

9、red. Return traffic must go through the LB as it will be configured to inspect such traffic. F5 health check for RLS uses SIP Options.,RLS,Kernel IP Stack,Platform Overload Logic,RLS Application Logic,F5,Up to 340,000 Clients per RLS Pair,SIP Options Monitor,Registration Virtual Server,Inspect Reply

10、,1,2,Client / Load Balancer / Registration Manager Components and Interfaces,See slide notes for explanation,DCH Load Balancing,F5 3600 LB,Traffic/OAM L2/L3 Switch/Routers,Incoming/Outgoing Traffic,DCH traffic uses QSP (proprietary UDP-based) protocol. Persistence is not required. Return traffic mus

11、t 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.,Portal Load Balancing,F5 3600 LB,Traffic L2/L3 Switch/Router,Incoming/Outgoing Traffic,Portal traffic uses HTTP protocol. Persistence is recommended, interval longer th

12、an login inactivity timer (30 min). Return traffic must go through the LB as F5 has external (real) Internet IP address, but Portal Pool has private IPs. F5 health check for Portal uses HTTP.,CPS Load Balancing,F5 3600 LB,Traffic L2/L3 Switch/Router,Incoming/Outgoing Traffic,CPS traffic uses HTTP protocol. Persistence is not used. Return traffic will go through the LB. F5 health check for CPS uses HTTP.,GLMS CF Load Balancing,F5 3600 LB,Traffic L2/L3 Switch/Router,Incoming/Outgoing Traffic,GLMS traffic uses HTTP/XCAP protocol. Persistence is not required. Ret