Successfully reported this slideshow.

Scaling Diameter for LTE


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Scaling Diameter for LTE

  1. 1. ScalingDiameter Acme Packet01/06/12 Acme Packet | 1
  2. 2. Scaling Diameter for LTE• Introduction• What is Diameter and Why it is important• What it means for operators and vendors• Market projections• Diameter signaling controller requirements• Role of Centralized Routing Databases
  3. 3. Introductions• Greg Collins, Exact Ventures• Kevin Mitchell, Acme Packet• Glenn Marschel, NetNumber
  4. 4. What is Diameter?• Next generation signaling protocol, replacing SS7• Exchange subscriber profile data between fundamental core network elements/systems: – IMS – EPC – Billing systems – Roaming exchanges
  5. 5. Why is Signaling & Diameter Important?• Since LTE has a relatively flat architecture, the core network is more exposed to signaling, than with 3G, which has an RNC.• Network outages and/or poor performance – Increases churn – Destroys brands
  6. 6. Diameter Signaling Controllers• New product category, encompassing DEA, DRA, protocol translation, other functions.• More efficient, scalable, and reliable Diameter networks• Many dimensions for growth: – Subscribers – Voice and Data usage/sessions – Dynamic billing and policy applications – Roaming
  7. 7. Diameter Signaling Controllers• Multi-billion dollar market opportunity – New product category – Major technology transition – Continued strong organic growth in signaling• High degree of vendor activity – Very early days; Accelerating RFI/RFP activity – Much more entry and consolidation to come
  8. 8. DiametersignalingcontrollerrequirementsOct 2012 Kevin Mitchell @mitchellkp
  9. 9. Diameter Underpins theMonetization of LTEAttachment/registration Mobility/trackingAuthentication & authorization Authentication & authorizationData and voice sessions Roaming QoS & charging AAA, charging & QoSOct. 2012 Acme Packet |
  10. 10. Diameter signaling pain points Visited Home service provider service provider Interoperability Overload & downtime Network opacity Network complexityOct. 2012 Acme Packet |
  11. 11. Outages are costly –to top line and to brandOct. 2012 Acme Packet |
  12. 12. IntroducingDiameter Signaling Controllers All Diameter interfaces & applications • Authentication Service provider • Location/mobility HSS, OCS, PCR IPX/ • QoS F nodes roaming • Charging hub • LTE data and VoLTE roaming Provides critical signaling controls MME, PDN Visited • Security service GW, GGSN, CS • Traffic & congestion control CF, AS provider • Interoperability & mediation • Routing & aggregation • Reporting & analysis• Fulfill key standards DSCs enable successful • RFC 3588 Diameter agent transition to LTE & IMS • 3GPP Diameter Routing Agent (DRA) • Lowers total cost of ownership • 3GPP Subscriber Location Function (SLF) • GSMA Diameter Edge Agent (DEA) • Accelerates time to market • Mitigates riskOct. 2012 Acme Packet |
  13. 13. Where DSCs are needed: Core and Edge • Voice roaming IPX • Data roaming MNOInterconnect • Services MNO federation Service provider HSS, OCS, PCR • Aggregation & F nodes routing • OCS proxy Core • HSS/AAA proxy • PCRF proxy MME, PDN GW, GGSN, CS CF, AS Oct. 2012 Acme Packet |
  14. 14. Key requirements Universal Diameter interface support Signaling security Overload and congestion controls Programmable L3-L5 interworking Dynamic and scalable Diameter routing Multi-vendor, end-to-end service management & operationsOct. 2012 Acme Packet |
  15. 15. Scaling DSCs with CentralizedRouting Databases Simplifies provisioning – eliminates silos PSTN Wholesale/ IPX MNO Highly scalable: 100s-1000s STP Diameter of millions of entries servers Routing DB Support for dynamic, complex routing Registries decisions LCR LNP OSS Diameter clients xCSCF Integration with legacy Fixed Mobile routing databases DB query Diameter Extensible – SIP, multi- vendor, future applications SIP SOAP/XMLOct. 2012 Acme Packet |
  16. 16. Role of CRDB in NGN Centralized Routing and Database Services
  17. 17. Common Data – Multiple Applications• SIP Services, DIAMETER services, TDM services – All need access to shared/common routing data• Common Routing Data – Subscriber data – Portability-data – Code-range data – MVNO data (Virgin Mobile) – OTT data (GoogleVoice) – Carrier-ENUM data (IMS endpoints) – Routing policy data (Route-list for destinations) • Internal routing • Trusted interconnect partner routing • Least cost interconnect routing
  18. 18. Common Data – Multiple Applications Portability Data Code-Range Data Subscriber Assignment Data Carrier-ENUM Interconnect Trunk-Group Profiles MVNO destinations OTT destinations (Google Voice)MULTIPLE Geographic destinations (LCR) MULTIPLE DATA Local Routing Policy DATASOURCES L SOURCES We ocal ery AP b, p qu P, IN File rovis ral , S ion fer , MA OA ing P/X Re AIN ML M, E NU CRDB (ENUM, SIP, INAP, MAP, CAP, WIN, DIAMETER) STP DRA S-CSCF Connection Management Services C4/C5 MSC SMS/MMS MGCF DEA pCSCF AS/TAS SBC Network Edge Services CONVERGED TDM & IMS NETWORK
  19. 19. Key Issues To Consider• In-Switch Routing Model is Costly – Provision common data into every switch – Learn routing database model for every switch – Staff routing experts for every switch – Fix routing inconsistencies across multiple platforms• CRDB Model is a Strategic Decision – We’ve been living with cost of in-switch routing model for past 100-years. Obviously we can continue. – Switching to a centralized model requires some strategy vision to avoid the costs of the old model. – Introduction of IMS-Core and DIAMETER services are opportunity to switch to a centralized model • Reduced network complexity (lower operating costs) • Faster service deployment (faster revenue generation) • Enhanced routing options (improved quality)
  20. 20. Additional Resources  Blog Post: The Next Generation Signaling Core for LTE and IMS  White Paper: Scaling Diameter in LTE and IMSOct. 2012 Acme Packet |