Next Generation Exchange
Next Generation Exchange
NOTE ON TERMINOLOGY
The terms exchange, IPX, federation and hub are often used interchangeably to describe a hub-and-spoke-based approach to facilitate scalable and efficient interconnection between multiple communications entities (e.g., operators, enterprises). This approach involves a central entity (e.g., hub, exchange, federation provider), thereby reducing the technical and commercial overhead and costs of multiple direct bilateral/ peering arrangements. We have predominately used the word exchange in this report. The services offered by the exchange can vary enormously, as outlined in this document.
Limited reach: Advanced services are limited in their ability to drive network effects because they cannot rely on the traditional PSTN for interconnection among service providers. Without an interconnection among different networks, revenue and margin opportunities will be limited to their home subscriber footprint. Revenue potential: These services will become an increasingly large portion of telecom operator revenue as legacy services such as POTS and SMS give way to services such as voice over broadband (VoBB) and Rich Communication Suite (RCS). Network operators that have made money selling TDM-based
voice services are at the beginning stages of a multi-year transition to the all-IP networks of the future. As networks evolve to IP, so do the services. These new services cannot rely on the PSTN for interconnection, creating a strategic need for multi-layered IP federation services.
March 2011
The benefits of IP services come with new security risks such as toll fraud, identity theft, spam over IP telephony (SPIT) and denial-ofservice (DoS) attacks. Traditional network security measures like firewalls and intrusion prevention systems (IPSs) mitigate some of those risks, but they are not designed to handle complex signaling/media sessions using protocols such as SIP. IP-to-IP interconnect requires some interworking in cases where different SIP signaling variants or the legacy H.323 protocol are used by IP network elements. Soon, consumers and enterprises alike will require critical services delivered over IP. The inevitable adoption of IP services is good for service providers, who will reap economic value from the services popularity. The realities of an iterative transition of this magnitude are complex. Hub-based IP interconnect can help reduce many of the complexities by providing a ready-made environment to maximize service reach and interconnection costs. By combining interoperability services with ENUM, interconnection delivers the features, quality and cost benefits of IP and eliminates use of the PSTN as the medium through which calls are delivered between operators. Service providers face a number of critical investment decisions about how best to manage the transition to IP in order to maximize profitability of existing services, minimize operational complexity and open the doors to new services and business models not yet commercialized. One of these critical decisions is choosing the method(s) for interconnection of IP services.
A hub-based provider of ENUM registries and multi-protocol, multi-vendor VoIP/NGN interconnection infrastructure can enable communications service providers to join multilateral interconnection relationships with IP service providers, either at the regional level or around the globe.
Trusted Environment
PathFinder
IPX2 IPX3
Voice VS
Internet
Voice VS
Mobile Subscribers
Mobile Subscribers
To clarify, IPX is not responsible for offering end-user services; it provides the interconnect between service providers that offer end-user services. IPX supports various functions so a customer of Service Provider A can set up and complete a session with a customer of Service Provider B. IP services transported over IPX must be standardized and documented in a service specification to ensure interoperability. IPX generally consist of two layers: The transport layer provides connectivity between two service providers. This layer provides a guaranteed QoS bit-pipe function. The service layer provides establishment of connections and management of billing and settlements for a service. Around these core assets, multilateral peering providers compete based on the flexibility of their offerings, in particular as it relates to security, settlement models, network management and reporting/ analytics. The efficient use of ENUM lies at the heart of any multilateral peering value proposition.
term ENUM often leads to confusion, given all the different types of ENUM in the marketplace and how they relate to intra-carrier peering architectures (see Exhibit 2). Proponents of ENUM have espoused the benefits of operational cost savings and service quality made possible by avoiding traditional PSTN routing infrastructure (i.e., SS7) to complete VoIP calls destined for a non-local VoIP endpoint. For some, this has been a benefit in search of a problem to address, as the islands of VoIP have been small enough that the percentage of originating VoIP calls that are actually destined for an IP endpoint are sufficiently small estimates range from 15 percent to less than 5 percent of overall call volume, depending on the operator. From a wholesale interconnect perspective, though, the benefits gained from direct or hub-based IP interconnect (e.g., cost, quality) are applicable for voice even if the endpoint is not IP, provided the interconnect is IP-enabled. Despite some clear advantages, some operators have deemed the existing SS7 routing infrastructure good enough and find the cost of TDM routing dips insufficiently prohibitive to motivate a move to a new model. However, this is not a static situation, as user demand and competition will force the hand of operators who have yet to commit to a hub-based peering approach. As the islands of IP grow and the number of endpoints that can consume IP services grows exponentially, several Tier 1 operators have publicly committed to a complete decommission of their PSTN infrastructure during the next several years. Furthermore, there is decreasing support for existing TDM gateway equipment as these products transition to end-of-life status.
Public ENUM
The original version of ENUM as a global, public directory, with subscriber opt-in capabilities and delegation and the country-code level in the e164.arpa domain. This is also referred to as User ENUM. A carrier may use ENUM within its own networks, in the same way DNS is used internally to networks. Groups of carriers or communications service providers agree to share subscriber information via ENUM in private peering relationships. This is the preferred ENUM model, as carriers themselves control subscriber information, not the individuals. Carrier ENUM is also referred to as Infrastructure ENUM and is being adopted today to support VoIP peering.
Private ENUM
Carrier ENUM
March 2011
30%
27% 25%
60,000
25%
20%
23% 39,946
47,934 44,220
50,000
20%
17% 35,118
40,000
15%
14% 24,497
29,804
30,000
10%
20,000
5%
10,000
adoption of advanced UC services planned over the next 24 months, including video and mobile VoIP, both of which benefit from hubbased interconnection.
Source: Yankee Groups Anywhere Enterprise: 2010 US Unified Communications (UC) FastView Survey, December 2010
Which of the following UC components have you deployed or do you plan to deploy?
Corporate IM Room-based video conferencing Web conferencing Desktop video conferencing Unified messaging In-house audio conferencing Desktop applications Mobile phone integration Telecommuter solutions Location-based services VoIP apps on IP phone Soft phones Telepresence Speech recognition apps
74% 74% 69% 59% 59% 59% 58% 56% 50% 48% 46% 42% 40% 33% 23% 21% 17% 20% 21% 22% 28% 19% 22% 19% 25% 21% 18% 21% 18% 23% 13% 7% 13% 19% 12% 18% 15% 12% 15% 13% Already deployed Pilot-testing Plan to deploy in next 24 months 12% 8%
n=443
0%
20%
40%
60%
80%
100%
March 2011
The key challenge to mass adoption of video calling is the lack of interoperability between different vendor or service provider implementations of the service. Telepresence and videoconferencing service providers such as Cisco, BT and AT&T have launched video exchanges to overcome these obstacles. Video exchanges are physical places where users on one enterprise and/or carrier telepresence and videoconferencing network service can connect securely and reliably with users on one or more other telepresence and videoconferencing networks. However, this interworking is limited to the telepresence environment and specific systems, and it requires a physical network connection to the exchange. Hub-based interconnect can provide the policy/routing support and signaling/media interworking between individual video calling service providers or video exchanges to overcome the remaining technical obstacles standing in the way of any-to-any video calling.
To recapture some of the lost value, service providers have the opportunity to either work with or peer with Skype to offer on-net completions among communities of subscribers, a situation that benefits both user communities. Hub-based interconnect affords the opportunity for OTT service providers to peer with one another or with network-based providers of IP services. By increasing the network effects of their services, they are able to increase their perceived value, resulting in faster growth for both OTT and traditional network service providers.
OTT IP Services
According to its latest financial results, Skype has rocketed past 550 million users and nearly U.S.$200 million in annual revenue (see Exhibit 5). Skype is rapidly becoming a popular mobile service due to the combination of smartphones and strategic alliances with traditional service providers such as Verizon Wireless and 3 U.K. The increasing popularity of services that ride over the top of service provider networks has created a disintermediation effect that separates network owner from application value creation. Exhibit 5: Skype Users Top 500 Million
Source: Yankee Group, 2011
560
2007
2008
2009
2010
Bilateral Interconnection
Without a central call-routing registry, bilateral peering requires a daily exchange of data between each pair of peered carriers so that each can maintain its own routing registry information. This process also introduces security and trust concerns, which limits scalability. Bilateral peering is viable for a number of significant direct peering relationships, but it will not facilitate more universal interconnection between the many hundreds (and soon to be thousands) of IP-enabled service providers globally.
March 2011
Protocol and XMPP) and normalizing media issues, such as transcoding, codec management, bandwidth issues, frame size, refresh rates, etc. For services like presence, both SIMPLE (a SIP derivative) and XMPP are often used. Even for HD voice, transcoding between different HD codecs, as well as G711.1, G.722, G722.2 (Adaptive MultiRate Wideband (AMR-WB)) and SILK, etc., all require increased functionality and services to enable a call/session to flow end to end. Questions to ask: To what extent are you able to guarantee interoperability among different video protocols, including proprietary? Which codecs are supported? How long will you support a given protocol or codec?
Signaling Interoperability
Every successful IP session requires interoperability among signaling protocols between service providers to initiate service sessions with feature transparency. Protocols in use within the industry include SIP, SIP-I, BICC, H.323 and, for new providers, Extensible Messaging and Presence Protocol (XMPP). Also, because providers use different software platforms to implement their service, there are significant variations even within a given protocol that require intermediation to ensure interoperability. Hub-based interconnection service providers should handle the translation and normalization of signaling among member service providers. Questions to ask: To what extent can you guarantee interoperability among different SIP protocol variants? What is your full range of multi-protocol support? What processes do you have to ensure that vendor-specific protocol implementations have support? How long will you support a given protocol?
Questions to ask: How is monthly reporting handled? What data are you collecting? How do you support complex settlement challenges? What reporting tools do you make available to member service providers? How do you charge for settlement and reporting services?
10
March 2011
Master Registry
Provisioning
Service Provider
Web Browser
Service Provider
Local Routing Engine
pl Re
ica
ti
ta /Da on
sh Pu
Replication Server
API
(Provisioning)
Number Query
Session Border Element Session Border Element
Media Flow
(Reporting)
API
11
The XConnect service provides the benefits associated with managed services. Service providers do not deploy any new equipment; they only pay for the services they actually use. Headquartered in London with offices and points of presence in the U.S., Europe and Asia, XConnect provides services to over 100 communications service providers in more than 20 countries. A useful exercise is to contrast XConnect hub-based interconnection services with an interconnection offering from a company like Sprint. Sprint offers an interconnection solution called the Partner Interexchange Network (PIN), which also aims to bring together VoIP networks but is only focused on the exchange of voice services and does not include ENUM directory services. Exhibit 8 provides a comprehensive market overview comparing different operators and vendors of ENUM directory services, interconnection hub services and additional value-added interconnection services.
GSMA PathFinder-Compliant
INTERCONNECTION HUB
Voice Interconnection
ADDED SERVICES
Flexible Settlement and Financial Clearing Services
XConnect Telcordia Syniverse Neustar IntelePeer Arbinet TNS BT - IP Exchange Neutral Tandem Sprint - PIN NetNumber
O O O O O O O O O O V/O
4 4 4 4 4 4 4 4 0 4 4
4 4 6 4 0 4 4 0 0 0 4
4 0 6 0 0 4 0 0 0 0 4
4 0 6 0 4 4 6 4 4 4 0
4 0 0 0 6 0 0 6 0 0 0
4 0 0 4 0 0 0 0 0 0 4
4 0 0 0 6 6 6 0 6 0 0
4 0 0 0 0 4 0 6 0 0 0
4 0 0 0 0 4 0 4 4 4 0
12
Enterprise Federations
Private Exchange/IPX
(O)perator/(V)endor
Inter-Registry Interoperability
Markets
Registry
4 0 0 0 6 0 0 0 0 0 0
March 2011
Telios mission is to be a major force in defining and providing fixed, video and mobile Internet communications to the consumer and small businesses.
As XConnect developed its hub-based federation model, it aligned with Telios views on how the telecom world should evolve while offering a distinct cost savings due to its multilateral basis. In particular, Telio takes advantage of the following XConnect hubbased interconnection services: National peering for domestic interconnect International peering via the XConnect Global Alliance Settlement-free peering via the Free Alliance High-definition voice interconnection via the HD Alliance The original interconnect between Telio and XConnect was completed in 2007 and went live approximately 20 days from the start of interoperability testing. Telio recently expanded its scope with XConnect to include its European subsidiaries, which took about 10 days to add.
Business Challenge
The business challenges that drove Telio to consider a hub-based IP interconnect involved operational cost control, management efficiency and differentiated service strategy. As it does in several countries, IP-to-IP communications in Norway falls outside the regulatory framework covering traditional telecommunications services (e-com services). The dependency on incumbent operators for regulated interconnect can be a major challenge in maintaining service profits for VoIP operators. Managing the costs associated with both national and international interconnect required a solution that was both costeffective and flexible enough to remove the administrative burden of maintaining several bilateral peering arrangements. On the service side, Telio required a solution that allowed for the cost-effective delivery of innovative IP services, such as HD voice calling, presence and video services, as well as pure IP delivery among the greatest amount of networks and subscribers.
Why XConnect?
Ultimately, XConnect was chosen due to the diverse range of federation options it could provide to Telio to reduce costs and increase service reach, quality and profitability. A major consideration was the fact that XConnect had multiple, live operating federation services in commercial use and allowed for both national and international peering in a neutral manner. Telio gives XConnect high marks for its overall scalability, since it offers the ability to easily peer with new service providers as they join. Technically, support for advanced interworking across multiple protocols (SIP, H.323 and XMPP) allowed for the greatest possible service reach and security features to protect Telios assets within the federated environment. Additional consideration was given based on the level of peering control and policy XConnect could provide; Telio could choose a high degree of interconnect configurability and control. Telio also gave consideration to business model flexibility, which removed many shortcomings of the traditional interconnection model.
Solution
To meets its business challenges, Telio decided to initially outsource IP interconnect to XConnect in a pay-as-you-grow model, thereby reducing the dependency for interconnections based on more capital-intensive TDM/IP gateway models of the past. The hub-based interconnect service allowed Telio to interconnect once and gain access to many networks it wouldnt have been able to access using the bilateral peering models of the past. The cost and complexity to re-create that reach through a bilateral model would be onerous at setup and beyond, on both a technical level (ENUM registry, interworking, security) and a commercial/ contractual level.
13
Benefits
Telio experienced the following benefits through its partnership with XConnect: Reduced opex and capex due to a single connection to the interconnection hub Increased ARPU and APPU through longer calls, lower customer management cost, better customer experience, and faster and better bundling of services at higher fees Reduced churn through more compelling and sticky customer experience and faster and better bundling of services, both within and outside of Telios network Availability of accurate call routing and addressing information through a global ENUM registry Assurance that calls are routed as IP all the way between networks to preserve call quality and exploit the revenue potential of new multimedia services Easier creation and management of multiple interconnect agreements, which involve complex work items such as interoperability testing, peering policy management and policy enforcement; XConnects interconnection hub allows Telio to interconnect with more than 150 services providers using just one agreement Negotiation of commercial agreements and settlement rates between interconnected networks Ensured network security across multiple interconnection partners Access to additional federated communities of interest such as members of GSMAs PathFinder service, other IPXs or other federated UC communities
Future Plans
In the future, Telio expects XConnect to remain a vital part of its operationsin particular, in support of new services-based federations in RCS, IM, video, presence and mobile VoIP. Telio expects its partnership with XConnect guarantees that future deployments and services will work seamlessly, and it anticipates that XConnect will be a key partner in the delivery of video services. Video interconnection is a new service segment with many more variables attached to it (handsets, screens, codecs), and that will demand a comprehensive review of the traditional interconnection model. Solutions in this area are still matriculating and represent an opportunity for both Telio and XConnect.
VII. Conclusions
The rich nature of IP services has caused an explosion of market demand. Traditional network service providers, Internet-based service providers and enterprise vendors alike are carefully evaluating strategies to aggressively compete for new customers and defend against subscriber churn. Against the backdrop of the current economic environment, service provider investment will either save costs or increase revenue. Multilateral hub-based peering/interconnect for IP services provides an opportunity to accomplish both. Choosing a multilateral interconnection partner is becoming a strategic imperative for service providers that wish to increase the network effects of their IP services while controlling costs. It is important to understand the differences among interconnection service providers regarding ENUM registries, peering connections and their services in support of peering policy, security and management. Arming oneself with the right set of questions will lead to a successful choice.
14
Research Data Interaction Yankee Groups products and services provide clients the insight, analysis and tools to navigate the global connectivity revolution. Consulting Events
Leverage qualitative research to make informed business decisions today and plan for the future. Gain quantitative insight into current markets and new opportunities via monitors, surveys and forecasts. Connect with analysts to gain deeper insight into research and trends. Get in-depth analysis and actionable recommendations tailored to your needs. Access world-class events live and online with industry leaders and Yankee Group experts.
ead H
Copyright 2011. Yankee Group Research, Inc. Yankee Group published this content for the sole use of Yankee Group subscribers. It may not be duplicated, reproduced or retransmitted in whole or in part without the express permission of Yankee Group, One Liberty Square, 7th Floor, Boston, MA 02109. All rights reserved. All opinions and estimates herein constitute our judgment as of this date and are subject to change without notice.
t uar
ers
Corporate
One Liberty Square 7th Floor BOSTON, MASSACHUSETTS 617-598-7200 phone 617-598-7400 fax
European
30 Artillery Lane LONDON E17LS UNITED KINGDOM 44-20-7426-1050 phone 44-20-7426-1051 fax