interconnects - sbc tutorial
TRANSCRIPT
© 2006, NexTone Communications. All rights reserved.
Interconnects – SBC TutorialLarry SchesselOffice of the CTOMSF Meeting, BerlinApril, 2006
© 2006, NexTone Communications. All rights reserved.
IP Interconnect vs VoIP Interconnect
VoIP
VoIP
VoIPVoIP
VoIP• Service dependent• Call setup protocols – extensions for service• Levels of transparency based on business contract• Federated/syndicated interconnection
IP
IP
IPIP
IP
• Service independent• Standard routing protocols• Transparency is key• Two predominant types – public and private peering
© 2006, NexTone Communications. All rights reserved.
Characteristics of VoIP
Signaling and media may traverse different networks
Intermediate systems for signaling and media are different
Signaling and media networks may be independently secured
Signaling and media have different quality characteristics Media is latency, jitter and packet loss sensitive Signaling quality measured by security
© 2006, NexTone Communications. All rights reserved.
Basic VoIP Interconnects
CarrierPeering
PSTNOrig/Term
Media GW
Enterprise IP TrunkingIP PBX’s
IP PhonesConsumer
Voice
2.5G or3G/IMS Applications
VoIPNetwork
PSTN
Mobile
Broadband
VoIPNetwork
© 2006, NexTone Communications. All rights reserved.
Typical SBC Requirements
SBC is point of … Administrative demarcation Security (DoS, DDoS) Prevention of service abuse Normalization Accounting Traffic segmentation SLA enforcement Quality of service Network isolation and insulation
© 2006, NexTone Communications. All rights reserved.
Basic Interconnect Example
SBG-NE SBG-NE
Media
ApplicationsLocation Management
CSC Core
© 2006, NexTone Communications. All rights reserved.
Roaming Interconnect Example
D-SBG-NE SBG-NC SBG-NE
Media
ApplicationsLocation Management
Roaming
P-CSC I-CSC Static CA
© 2006, NexTone Communications. All rights reserved.
Wholesale/ASP Interconnect Example
SBG-NEASPSBC
SBG-NE
Media
ApplicationsLocation Management
Static CAStatic CA
© 2006, NexTone Communications. All rights reserved.
Which SBC performs …
Security (DoS, DDoS)? Prevention of service abuse? Accounting? Traffic segmentation? SLA enforcement? Quality of service?
© 2006, NexTone Communications. All rights reserved.
IP Layer Poses Additional Considerations
SBG-NEASPSBC
SBG-NE
Media
ApplicationsLocation Management
Static CAStatic CA
Delay, packet loss, latency
© 2006, NexTone Communications. All rights reserved.
Proliferation of Interconnects
WLAN VoIP
Content
Enterprise
Fixed
ASP
Mobile Number of
interconnects does not scale
Business relationship proliferation
However, more demand for increased service reach
New Hub architecture for interconnects Promoted by
mobile operators
© 2006, NexTone Communications. All rights reserved.
Interconnect Requirements Beyond SBCs
Flexibility Separation of media and signaling routing “Any-to-any” interworking – SIP, H.323, multiple vendor interoperability “On-demand” media processing and transcoding
Enforceability Call admission control: limits for total concurrent, ingress and egress calls Session admission control: limits for total, ingress, and egress bandwidth Call/session accounting Real-time statistics, processing, reporting and reaction
Control Segmentation/classification of sessions Session routing
Manageability, scalability, reliability, etc.
© 2006, NexTone Communications. All rights reserved.
Conclusion: Interconnect Requires a Multi-Tier Architecture
Layers Functions Product
Layer 7 Session
Management
Layer 5Signalling
Sub-System
Layer 3-4Media SwitchSub-System
Reporting
Provisioning
Policy Control
Peering
Policy Enforcement
Session Control
Media Routing Engine
Media Processing
SessionManager
D-SBG
S-SBGSecurity
Interworking
Analytics Engine
TypicalSBC
Functionality
AdditionalInterconnect
SolutionFunctionality
Adaptive Routing Engine
Security
© 2006, NexTone Communications. All rights reserved.
Conclusion
Most current SBC requirements defined bottom-up and typical SBCs work well in basic single-service networks
However, session management requirements are changing as networks become more complex
Experience shows it is best for Service Providers to begin work from the service layer and work down (what interconnect service do they need to deliver?) Define interconnect requirements, then architecture, then
components
Interconnect service requires components to work as a system rather than point products – SBCs are just the tires on the car rather than the car itself
© 2006, NexTone Communications. All rights reserved.
www.nextone.com
The Freedom of seamless connectivity over diverse IP networks
Thank [email protected]; +1-240-912-3327