Safe Harbor Statement The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle s products remains at the sole discretion of Oracle. 1
SIP Interconnect The Why s and How s Don Troshynski Sr. Director, Solutions Architecture Oracle Communications
IP service interconnection is becoming critical 75% of international voice traffic in 2010 was carried using VoIP and is expected to be virtually 100% by 2015 Mobile voice interconnect remains TDM in many networks Disconnects The vast majority of international voice traffic will be mobileoriginated in 2016 Wholesale voice traffic will grow 6.1% CAGR Cost reduction and service expansion is required Wholesale voice revenue will decline at 2.4% CAGR
Global trends driving SIP interconnect Today: Fixed VoIP increasing use of SIP access Mobile TrFO for improved quality Wholesale VoIP transit/termination at lower cost Tomorrow: New services & business models VoLTE and IP-based roaming Enhanced RCS services for mobile OTT/cloud FCC Connect America Fund to reform intercarrier connection and compensation NTT deactivation of PSTN around 2025 Australia NBN program PSTN Sunset Italy 100% VoIP interconnects in 2013 Canada CRTC IP voice interconnection reform 4
2012 CRTC Network Interconnection Policy CRTC approved the use of SIP interconnection formally Addresses local, wireless, LD, and voice network interconnection Strongly endorses technology Eases tariff requirements Enables off-tariff and direct bill-and-keep models over IP Mandates requirement for operators to implement IP interconnection When carrier provides VoIP to affiliates companies When carrier provides VoIP-based services to subscriber base Triggered readiness efforts at Telus, Rogers, Shaw, Cogeco, Videotron, SaskTel and others 5
Why SIP as the protocol of choice for IP networks? If not SIP, then what? Jabber/XMPP has roots in client/server messaging/presence versus peer-to-peer trunks and interconnect Pure HTTP-based interfaces lack widespread standardization (even WebRTC does not standardize signaling) SIP allows for almost all multi-media session-based use cases Voice, video, short & multimedia messaging, chat, presence, file transfer SIP has been standardized across the most access technologies Fixed softswitch/ngn networks Wholesale peering partners SIP contact centers Mobile access and interconnect SIP has been selected as the protocol of choice for all IP mobile networks Core component of 3GPP IMS specification GSM Association endorsed OneVoice (SIP-based) for LTE, Rich Communications Suite (RCS) and SIP-I for IPX 6
What are the benefits of SIP Interconnection? Reduce total cost of ownership Eliminate TDM interconnects Minimize transcoding Single point of IP interconnect all real-time multimedia services Improved route management LCR, QoS, roaming steering, etc. Accelerate enhanced services time to market Dynamic protocol mediation and interworking Programmable and extendable Improve network availability to assure revenue Traffic congestion controls Encryption High availability and geo redundancy 7
SIP Interconnect Technical Implementation
Limitations of existing elements in controlling IP-based real-time communications Network Element Softswitches, signaling proxies, application servers Limitations Don t control media flows Don t protect against denial of service, overloads, etc. Routers Data Firewalls Don t participate in session signaling Don t recognize packets as belonging to a session Route/distribute packets, not sessions Don t actively monitor link or adjacent element utilization Don t dynamically adjust ACLs May be SIP-aware but are not SIP session state-aware 9
Benefits of an SBC for SIP Interconnection Benefit Comprehensive Security Protocol Harmonization IP Version Interworking QoS Reporting Flexible Accounting Efficient Transcoding Sophisticated Policy Control Sophisticated routing controls Inherent flexibility and extensibility Features/supporting statements/ DoS/DDoS, fraud prevention, signaling screening, White/Black list method/header SIP/SIP-I IWF, PRACK/non-PRACK, transport protocol interworking IPv4 IPv6 using true B2BUA R-factor/MoS reporting Customizable CDRs Transcoding on-board and in-line Concurrent sessions, session rate, bandwidth, minimum QoS, ASR Method/header/parameter based routing Genuine B2BUA, Header manipulation, Codec agnostic 10
Session Border Controller (SBC) vs. Firewalls with ALGs SBC Firewall with SIP ALG Back-to-back user agent Fully state-aware at layers 2-7 Inspects and modifies any application layer header info (SIP, SDP, etc.) Can terminate, initiate, re-initiate signaling & SDP Static & dynamic ACLs Modifies single session data Fully state-aware at layers 3 & 4 only Inspects and modifies only application layer addresses (SIP, SDP, etc.) Unable to terminate, initiate, re-initiate signaling & SDP Static ACLs only SIP trunking Data center IP PBX UC server SIP trunking Data center IP PBX UC server 11
Service Provider Session Border Controller (SBC) Architecture Access and interconnect borders NGN session delivery Complement other service elements Service Provider Service Provider Softswitches IMS call session control functions (S/I-CSCF) Mobile switching centers Application servers Enterprise Internet Fixed & Mobile Augment access and aggregation routers 12
SIP Routing with Proxies Centralized versus decentralized route management Centralized Routing Eases workload caused by static nature of PSTN routing PSTN Simplified soft switch and routing tables One common outbound route versus N-squared Create unified dial plan Overlapping address resolution Reduced costs Decentralized Routing Centralized provisioning more cost effective than distributed Better utilization of SIP trunks and pooling of PSTN gateways PSTN SLAs Call Admission Control Rerouting for network resiliency Accounting call detail records PSTN 13
Mobile Interconnect and IPX
Mobile Legacy: IP-based core, TDM interconnect Core networks have been migrated to mostly IP-based BICC was used initially but a further migration to SIP-I is likely BICC lacks multi-vendor interoperability for interconnects, so TDM is still being used Operator A Operator B HLR G G HLR TDM link IP link (BICC or SIP-I) 15
Mobile Trend: SBC/SIP-I Interconnect End-to-end IP and associated benefits now possible Reuse of IP transport layer No degradation of voice quality between operators due to MGW transcoding Easier to interconnect over distance using IP Operator A HLR G Flexibility and reuse of SIP-based interconnect Externally: Connectivity to Fixed operators as well as International ones Internally: Single POI can be used for mobile as well as VoLTE/IMS TDM link G IP link (BICC or SIP-I) Operator B HLR 16
IPX for mobile interconnection what is IPX? An i3 forum definition (IP Packet exchange) is a generic term that refers to a class of IP-based interconnection models and implementations that share the following features: Based on private IP Domain (i.e. no use of the Public Internet) which spans from Service Provider to Service Provider Multi-service capable (implementation of multi-service offers is a commercial matter) Designed and operated to support High Quality IP based services (break-outs and break-ins to/from non-ipx services are possible and disclosed) Allows a cascading business model Guarantees service assurance across the whole IPX Domain, being (among others): SLA capable (SLAs can be offered, actual implementation is a commercial matter) Secure (e.g. MPLS based but other technique can be used) Scalable (as opposed to dedicated bilateral private IP interconnects) IPX services are offered by an IPX Provider (e.g. international carrier) to a Service Provider IPX Providers can interconnect among themselves in order to guarantee a worldwide coverage
IPX Technical Capabilities Multi-service. Capable of HiDef voice, IP-based Video, and Enhanced Messaging (RCS). Service-layer hubbing. QoS. Must provide differentiated services for traffic types with monitoring and reporting at service layer. Routing. Provide global reachability. Leverage ENUM for MNP/messaging/RCS. Transcoding. Optional voice and video transcoding services. Security. Service layer security with Session Border Controller. Interworking. SIP, RCS, SMS/MMS.
GSMA IPX Business Drivers Reduce operational costs Overhead of n^2 mesh of bi-lateral agreements Use lower-cost IP reachability for data roaming and voice termination Graceful technical transition to IP Interconnect IPX IPX Improve customer experience Enable IP-based high-definition codecs to traverse directly between many operators Improve user experience using QoS and high-definition voice/video to exceed Facetime/Skype Ensure global reachability for video/messaging services MNO $ IPX $ IPX $ MNO SLA SLA SLA
IPX Solution Architecture Extensive provisioning and operations tool set OTT Network & service management Routing LCR PSTN 3G MNO FNO Scalable core routing LTE MNO LTE MNO Diameter SIP signaling RTP media Complete SIP and Diameter security and control
SIP-based interconnection using a combined approach Bilateral Peering MNO/FNO negotiates either traffic exchange or termination at negotiated rates. May offer the potential for settlement free termination in certain cases. Enables negotiation or direct peering elements/capacities. Originating MNO MNO/FNO IPX-based Multilateral MNO/FNO negotiates with IPX to obtain reachability to many operators to obtain either QoS for direct bilateral data exchange or termination. IPX may provide service transparency or interworking. MNO/FNO IPX MNO/FNO MNO/FNO
Summary Migrating to SIP-based Interconnects has long term CAPEX and OPEX savings for network operators Immediate benefits: Reuse of IP core infrastructure Decrease the use of expensive media gateway ports Improve voice quality by avoiding transcoding Longer term benefits: Reduction in number of media control protocols in the core network Support for mixed applications Support for mixed access technology interconnects (mobile/fixed, domestic/international, etc.) No need to forklift interconnection infrastructure as networks migrate to SIP cores 22
23
24