6
Evolution of the voice interconnect The migration to all-IP networks calls for an evolution of the interconnect between operator networks. This might lead to a new interconnect architecture featuring an intermediate carrier network based on either a pure IP transit architecture or a service hub architecture. has resulted in a reduction of the inter- national interconnect price of around 7 percent per year. Existing interconnect architecture Today’s interconnect architecture is predominantly TDM-based and is a mix- ture of direct interconnects between operator networks, typically used with- in a country, and indirect interconnects that use an intermediate global carrier network to reach the rest of the world. With the migration towards an IP-based interconnect, operators and carriers are looking at new architectures rather than simply replacing TDM pipes with IP pipes (Figure 1). The transformation from existing ISDN User Part (ISUP)/TDM intercon- nects to an IP-based interconnect has the following advantages: Evolution of the voice interconnect: Using bandwidth-optimized codecs will reduce bandwidth needs, and using IP instead of TDM will ensure better utilization of the point of interconnect. Both will significantly reduce capital During the past decade, network operators have transformed their existing wireline and wireless core networks from Time Division Multiplex (TDM) or Asynchronous Transfer Mode (ATM) transport technology to IP transport. The evolution of the voice interconnect between operator networks to IP is another natural step towards an all-IP archi- tecture. This transition will result in more efficient bandwidth usage, better speech quality, reduced costs, and a clear migra- tion path to a full multimedia service interconnection. Background Traffic forecast During the past five years there has been a continuous increase of 10-15 percent per year in international inter- connect traffic, and mobile operators are playing a more important role in interconnect for two main reasons. Firstly, worldwide the number of subscribers in mobile networks is still increasing, mainly driven by the demand in developing and emerging markets with low fixed-line penetra- tion. Secondly, there is an increased trend towards fixed-mobile substitu- tion in developed countries. In 2002, the number of mobile subscribers worldwide surpassed the number of fixed subscribers worldwide. The increases in subscribers and min- utes of use have resulted in the mobile terminating traffic surpassing the fixed terminating traffic in 2009. Although traffic growth continues, PC-based voice clients such as Skype have started to use the internet to bypass traditional international tran- sit networks. These new entrants have managed to capture approximately 8 percent of international voice traffic volume. 1 The increased competition JOHN BALDWIN, JÖRG EWERT AND SONER YAMEN BOX A Terms and abbreviations AMR Adaptive Multi-Rate AMR-NB Adaptive Multi-Rate Narrowband AMR-WB Adaptive Multi-Rate Wideband ATM Asynchronous Transfer Mode BICC Bearer Independent Call Control CELP code-excited linear prediction CPC Continuous Packet Connectivity CS-IBCF Circuit Switched Interconnection Border Control Function EFR Enhanced Full Rate GRX GPRS Roaming Exchange Node IBCF Interconnection Border Control Function IMS IP Multimedia Subsystem IPX Internet Packet Exchange ISUP ISDN User Part MGw Media Gateway M-MGw Mobile Media Gateway MMTel Multimedia Telephony MMS Multimedia Messaging Service MNO mobile network operator MSRP Message Session Relay Protocol MSC-S Mobile Switching Center Server MSS mobile softswitch MTP3 Message Transfer Part 3 NNI Network to Network Interface PCM pulse-code modulation PLMN Public Land Mobile Network RANAP Radio Access Network Application Part RCS Rich Communication Suite RTP Real-time Transport Protocol RTCP Real-time Transport Control Protocol SCCP Signaling Connection Control Part SCTP Stream Control Transmission Protocol SIP Session Initiation Protocol SIP-I SIP with encapsulated ISUP TDM Time Division Multiplex / Multiplexing TrFO Transcoder Free Operation TrGw Trunking Gateway TCP Transmission Control Protocol UDP User Datagram Protocol VoIP Voice over Internet Protocol 10 Ericsson rEviEw 2 2010 Vinjett Keep evolving towards all IP

Evolution Voice Interconnect

Embed Size (px)

DESCRIPTION

Article on the migration to all-IP networks calls for an evolution of the interconnect between operatornetworks. This might lead to a new interconnect architecture featuring an intermediatecarrier network based on either a pure IP transit architecture or a service hub architecture.

Citation preview

  • Evolution of the voice interconnect The migration to all-IP networks calls for an evolution of the interconnect between operator networks. This might lead to a new interconnect architecture featuring an intermediate carrier network based on either a pure IP transit architecture or a service hub architecture.

    has resulted in a reduction of the inter-national interconnect price of around 7 percent per year.

    Existing interconnect architectureTodays interconnect architecture is predominantly TDM-based and is a mix-ture of direct interconnects between operator networks, typically used with-in a country, and indirect interconnects that use an intermediate global carrier network to reach the rest of the world. With the migration towards an IP-based interconnect, operators and carriers are looking at new architectures rather than simply replacing TDM pipes with IP pipes (Figure 1).

    The transformation from existing ISDN User Part (ISUP)/TDM intercon-nects to an IP-based interconnect has the following advantages:

    Evolution of the voice interconnect: Using bandwidth-optimized codecs will reduce bandwidth needs, and using IP instead of TDM will ensure better utilization of the point of interconnect. Both will significantly reduce capital

    During the past decade, network operators have transformed their existing wireline and wireless core networks from Time Division Multiplex (TDM) or Asynchronous Transfer Mode (ATM) transport technology to IP transport.

    The evolution of the voice interconnect between operator networks to IP is another natural step towards an all-IP archi-tecture. This transition will result in more efficient bandwidth usage, better speech quality, reduced costs, and a clear migra-tion path to a full multimedia service interconnection.

    Background Traffic forecastDuring the past five years there has been a continuous increase of 10-15 percent per year in international inter-connect traffic, and mobile operators

    are playing a more important role in interconnect for two main reasons.

    Firstly, worldwide the number of subscribers in mobile networks is still increasing, mainly driven by the demand in developing and emerging markets with low fixed-line penetra-tion. Secondly, there is an increased trend towards fixed-mobile substitu-tion in developed countries.

    In 2002, the number of mobile subscribers worldwide surpassed the number of fixed subscribers worldwide. The increases in subscribers and min-utes of use have resulted in the mobile terminating traffic surpassing the fixed terminating traffic in 2009.

    Although traffic growth continues, PC-based voice clients such as Skype have started to use the internet to bypass traditional international tran-sit networks. These new entrants have managed to capture approximately 8 percent of international voice traffic volume.1 The increased competition

    Joh n Ba l dw i n, Jrg Ew E rt a n d Son E r Ya m E n

    BOX A Terms and abbreviations

    AMR Adaptive Multi-RateAMR-NB Adaptive Multi-Rate NarrowbandAMR-WB Adaptive Multi-Rate WidebandATM Asynchronous Transfer ModeBICC Bearer Independent Call ControlCELP code-excited linear predictionCPC Continuous Packet ConnectivityCS-IBCF Circuit Switched Interconnection Border Control FunctionEFR Enhanced Full Rate GRX GPRS Roaming Exchange NodeIBCF Interconnection Border Control FunctionIMS IP Multimedia Subsystem IPX Internet Packet Exchange

    ISUP ISDN User Part MGw Media GatewayM-MGw Mobile Media GatewayMMTel Multimedia TelephonyMMS Multimedia Messaging ServiceMNO mobile network operatorMSRP Message Session Relay ProtocolMSC-S Mobile Switching Center ServerMSS mobile softswitch MTP3 Message Transfer Part 3NNI Network to Network InterfacePCM pulse-code modulationPLMN Public Land Mobile NetworkRANAP Radio Access Network Application Part

    RCS Rich Communication SuiteRTP Real-time Transport ProtocolRTCP Real-time Transport Control ProtocolSCCP Signaling Connection Control PartSCTP Stream Control Transmission ProtocolSIP Session Initiation ProtocolSIP-I SIP with encapsulated ISUPTDM Time Division Multiplex / MultiplexingTrFO Transcoder Free OperationTrGw Trunking GatewayTCP Transmission Control ProtocolUDP User Datagram ProtocolVoIP Voice over Internet Protocol

    10

    E r i c s s o n r E v i E w 2 2010

    Vinjett

    E r i c s s o n r E v i E w 2 2010

    Keep evolving towards all IP

  • expenditure (capex) and operational expenditure (opex). Interconnect architecture: IP technology offers higher flexibility in choosing interconnect partners and architecture. Multimedia interconnect: Operators have started launching new multimedia based services such as presence and messaging. One of the key success factors will be interoperability between operators. This will require evolving the interconnect from a pure voice intercon-nect to a combined voice and multime-dia interconnect.

    The following sections examine the three areas in more detail.

    Evolution of the voice interconnectToday, voice interconnect is handled using legacy TDM connections with ISUP signaling and the G.711 codec. Over the years ISUP signaling has matured and now supports national and inter-national variants, as well as redundan-cy mechanisms required for telecom grade service.

    However, when it comes to the intro-duction of new services and inter-working with IP-based networks, ISUP has severe limitations and adds to the complexity of the solution.

    Figure 2 shows a Session Initiation Protocol with encapsulated ISDN User Part (SIP-I) interconnect between two MSS domains. When SIP-I is used, in addition to the protocol mapping done for SIP, the complete ISDN User Part (ISUP) message is transferred within the body of the SIP message. This allows the receiving SIP User Agent to pro-cess the encapsulated ISUP messages, so that no service-related information is lost for legacy functionality.2 Similar to ISUP, market variants are support-ed using SIP-I screening, which allows modification of messages, parameters and parameter fields from the encapsu-lated ISUP content.

    Figure 3 shows an SIP inter connect between an IMS and MSS domain. When the Gateway carries out protocol interworking between SIP and ISUP or Bearer Independent Call Control (BICC) or Radio Access Network Application Part (RANAP), it performs a mapping between the message parameters of the SIP and ISUP protocol.3 This map-ping can result in information loss

    Mobilesoftswitch

    MSC-S

    M-MGw

    MSC-S

    M-MGw

    IP TDM IP

    Softswitchor IMS

    Mobilesoftswitch

    IP IP IP

    Softswitchor IMS

    Control

    Control

    IP Gw

    TDM Gw

    FigurE 1 Evolution of the interconnect from TDM to iP is the natural next step after the transition to iP within operator domains.

    SIP-I Network to Network Interface

    BICC

    H.248 H.248 H.248 H.248

    BICCMSC

    serverMSC

    serverMSC

    serverMSC

    server

    MGw MGw MGw MGw

    CSIBCF

    CSIBCF

    CSTrGw

    CSTrG

    SIP-IUDP/TCP/SCTP

    IPEthernet

    RTP/RTCPUDP

    IPEthernet

    Nc

    Mc McMc/Mn Mc/MnCS-Ix CS-Ix

    Nb

    Nc

    Nb

    Control planeUser plane

    FigurE 2 reference architecture of an SiP-i and SiP Network to Network interface (NNi).

    E r i c s s o n r E v i E w 2 2010

    Vinjett

    11

    E r i c s s o n r E v i E w 2 2010

  • related to the requested service and does not support all legacy services.

    For voice interconnect between net-works there is more to consider than just the choice of signaling protocol. The following aspects should also be considered for interconnects based on SIP-I and SIP:

    Signaling policing: policing is needed to protect the domain against unwanted messages. For ISUP interconnects, policing is performed on the MTP3 or SCCP protocol level. For an SIP or SIP-I it is done by the Interconnection Border Control Function (IBCF) on the SIP/SIP-I signaling level and by the Trunking Gateway (TrGw) on the media protocol level. Bandwidth management: in the case of an ISUP interconnect, there is always a predefined bandwidth usage of 64Kbps or 56Kbps for G.711 per channel. Due to the fixed timeslots on the payload path it is not possible to use more than the assigned bandwidth. For an IP-based interconnect the bandwidth needed depends on the codec used. Also the user plane connections share a common IP pipe. This means that proper band-width allocations and admission control mechanisms are needed to avoid exceed-ing the allocated bandwidth or causing deterioration of the voice services. Voice transcoding: as more codecs are now available, it is important to intro-duce negotiation mechanisms to select the best codec for each situation. This will reduce the number of transcoding stages, resulting in a Transcoder Free Operation (TrFO) whenever possible. Fax, Video and CS Data Calls: fax and data calls represent only a small fraction of the total number of calls but must still work properly. In order to support com-pressed speech without disturbing fax and modem operation, voiceband data traffic detection and fallback to G.711 is desired. Also the T.38 fax gateway is desired to support proper fax inter-working over poor quality IP transport connections. Charging and Accounting: SIP/SIP-I based interconnect will reuse the exist-ing charging mechanism based on call data records.

    Emergency and Priority calls: intercon-nects need to support emergency and priority calls. Emergency and priority calls are indicated with a certain ISUP

    H.248

    Control planeUser plane

    H.248

    BICCMSC

    serverMSC

    server

    MGw MGw

    CSIBCF

    CSTrGw

    SIPUDP/TCP/SCTP

    IPEthernet

    RTP/RTCPUDP

    IPEthernet

    IMS orVoIP networks McMc/Mn

    CS-Ix

    Nc

    Nb

    SIP Network to Network Interface

    FigurE 3 reference architecture of an SiP-i and SiP Network to Network interface (NNi).

    FNO

    FNOMNO

    FNO

    MNO

    MNO

    MNO

    Global carrierIP networks

    Direct IP interconnectionIndirect IP interconnection via IP transport serviceIndirect IP interconnection via Hub serviceFixed network operatorMobile network operator

    SIPHub

    SIPHub

    FigurE 4 iP technology will be used as indirect, direct and indirect service aware interconnection.

    12

    E r i c s s o n r E v i E w 2 2010

    Vinjett

    E r i c s s o n r E v i E w 2 2010

    Keep evolving towards all IP

  • parameter (Continous Packet Connectivity or CPC) and a certain SIP parameter.Operators may implement IP-based

    voice interconnect using different codec types (Table 1) and enjoy the benefits of each. These can also be seen as evo-lution steps.

    Usage of IP transmission (still G.711)If transmission efficiency is not so important, an operator may introduce IP-based interconnect without sup-port for any additional codec above the default G.711 codec.

    Usage of bandwidth efficient codecs: for example, G.729 with transcoding

    As a next step, codecs with better band-width characteristics can be introduced on the interconnect to reduce opex. For example, G.729 is the most commonly used fixed network codec and can be used for compression.

    Removal of the need for transcoding (end-to-end codec negotiation)

    If the same codec is supported within the two connected networks then it is desirable to support this codec also on the interconnect. This can eliminate the need for transcoding, or at least mini-mize the number of transcoding stages, ensuring resource efficiency in MGws, which reduces capex and improves speech quality. As an example, AMR coded speech, which is commonly used by mobile networks, can be used on interconnect to achieve TrFO end-to-end when connecting two mobile networks. TrFO reduces the need for transcoders and therefore reduces capex.

    Improved voice quality with High Definition (HD) voice (for example, AMR-WB, G.722)

    Once interconnect is on IP transport and TrFO is achieved, new codecs with superior speech quality, HD-voice, can be introduced also for inter-Public Land Mobile Network (PLMN) calls. AMR-WB, which is optimized for mobile access, and G.722, which is widely used for fixed access, can be used for superior speech quality. These codecs can be transcod-ed to each other without losing wide-band characteristics. HD voice on inter-connect enables superior speech qual-ity for calls between mobile and fixed access and can help to increase revenue and reduce churn.

    Table 2 summarizes which codecs

    are used in which domain. It is clear that G.711 is the only codec that is common for all domains. A common codec via end-to-end codec negotiation is possible with AMR-NB, AMR-WB for a MSS-MSS and MSS-IMS interconnect. This is not possible for an MSS-wireline softswitch interconnect; G.729 is the optimal choice in this case, but requires transcoding in MSS due to the unavail-ability of the G.729 codec in mobile phones.

    interconnect architecture With the migration to all-IP networks and IP-based interconnect, operators and carriers are looking at new inter-connect architectures, rather than sim-ply replacing TDM pipes with IP pipes. In the new architectures, the concept of an intermediate carrier network exists in two forms:

    Pure IP transit architecture: in this case, the carrier network essentially provides an IP interconnection pipe between operators, which will have a bilateral agreement for settlement. The carrier

    network is agnostic to the type of application or media flowing through the network and will typically charge the operators based upon the amount of data transferred. Service Hub architecture: in this case, the carrier network is service aware and can differentiate the type of application or media that is flowing through the network for QoS and charging purposes. The carrier network can provide a complete multilateral hubbing service where operators set up single contracts with carriers for their complete inter-connection needs.The future IP interconnect architec-

    ture is likely to involve a combination of: Direct IP interconnect between two mobile operators (National traffic) Indirect interconnect via a third-party carrier IP backbone (International traffic first using pure IP transit) Indirect interconnect via a third-party carrier network that also is service aware (Service Hub)

    In its pure IP transit form, as illus trated in Figure 4, the carrier network

    Table 2: Summary of the codecs supported per domain. MOBILE SOFTSWITCH

    WIRELINE SOFTSWITCH IMSInside MSS Towards other networks

    G.711 G.711 G.711 G.711

    G.729 G.729 G.729

    AMR-NB AMR-NB AMR-NB

    AMR-WB AMR-WB AMR-WB

    GSM EFR GSM EFR

    Table 1: Most popular codecs and their characteristics.CODEC EXPLANATION PACKETIZATION

    TIME /DEFAULT VALUES IN MS)

    EFFECTIVE DATA RATE (KBPS)

    G.711 G.711 is the default codec for fixed and mobile applications and uses pulse-code modulation (PCM). It provides the best speech quality for narrowband codecs with a user data rate of 64K.

    0.125 64 (over TDM)

    G.729 G.729 is one of the most popular narrowband codecs for IP-based fixed networks based on code-excited linear prediction (CELP). It provides similar speech quality characteristics to AMR 7.4 with a user data rate of 8K.

    20 23 (over IP)

    G.722.0 G.722.0 is the fixed rate 7kHz wideband audio codec with a user data rate of 64K. Due to extended audio spectrum, it provides excellent audio quality with volume and clarity.

    20 54 (over IP)

    AMR-NB Adaptive multi-rate (AMR) is the most popular narrowband codec for wireless networks. It adapts to radio conditions and capacity requirements with user data rates between 12.2K down to 4.75K.

    20 23 (over IP)

    AMR-WB Adaptive multi-rate wideband (AMR-WB) is the 7kHz wideband audio codec with similar speech quality to G.722.0. It adapts to radio conditions and capacityrequirements with user data rates between 12.65K down to 6.60K.

    20 23 (over IP)

    E r i c s s o n r E v i E w 2 2010

    Vinjett

    13

    E r i c s s o n r E v i E w 2 2010

  • provides a mobile/fixed network operator (MNO, FNO) with IP connec-tivity to all other operators around the world, eliminating the need to establish individual IP connections. The IP connection provided by the carri-er has QoS characteristics defined, so can be used for real-time services such as voice.

    In its service hub form, the carrier network can provide additional servic-es such as service-based inter-operator settlement, service based routing and service interworking. This allows fixed/mobile operators to delegate a large part of interconnect administration to their chosen carrier.

    The different architectures give net-work operators flexibility in choosing the appropriate interconnect archi-tecture for particular destinations according to traffic and commercial requirements. The usage of IP tech-nology gives higher flexibility, such as having fewer and larger points of inter-connection. From an economy of scale perspective, this can provide benefits in terms of reduced administration and interconnect fees.

    These architectures provide well-defined technical and business roles for mobile/fixed operators and also for the global carriers. This is necessary for a sustainable interconnect solution. It is unlikely that models based upon interconnections over the public inter-

    net can provide such a sustainable inter-connect solution.

    There is a need for industry-wide coor-dination as operator network IP-based interconnects are emerging. The GSM Association is active in coordinating the industrys thinking on IP-based inter-connection. The GSMA suggests that the existing carrier GRX IP networks are evolved to support voice and multime-dia services. The IPX project builds upon the GRX to add QoS and so supports real-time CS and IMS services such as voice, video and presence. It is expected that within IPX there will be a service hub role for CS and IMS services. The service hub role is beneficial because an opera-tor only has to establish one agreement with the IPX hub provider who then has agreements with all other operators. To provide a service hub function for these real-time services SIP Servers will be introduced into the IPX core

    Multimedia interconnect Once IP-based interconnect for voice is established, there is a natural evolu-tion from voice to multimedia across interconnects, shown in Figure 5. The Rich Communication Suite (RCS) initia-tive from GSMA provides enrichment to voice services. RCS also provides end-user services such as presence, instant messaging and video sharing.

    The value of the RCS services will increase with the number of users and

    also with the number of interconnect-ed networks (Metcalfes law). Operators benefited from this correlation in the past, when they started their SMS and MSS services, and at the same time secured interoperability. This requires RCS services to be supported across oper-ator interconnects. These interconnects could be direct between two operators, or indirect using an intermediate carri-er IP network, such as IPX.

    RCS is a set of multimedia servic-es based upon 3GPP IMS using SIP signaling and RTP and MSRP media. The interconnect needs to support these signaling and media protocols. RCS is likely to be the first service that makes IP interconnect mandatory, simply because TDM networks cannot trans-port the media types defined in RCS.

    The different types of media in RCS have different bandwidth and delay requirements video requires high bandwidth for media, presence has a high signaling rate. It is not suffi-cient to base inter-operator settle-ment upon packet count at IP level. These services require new settlement arrangements between operators and new KPIs to be defined for inter-connects. There could be different settlement policies for different RCS services. The session border gate-way has an important role to play in policing KPIs.

    In effect, operator interconnects and intermediate carrier networks need to be service aware, both in terms of technical realization and commercial settlement mechanisms. This will allow RCS services to be deployed at nation-al and international level, and will be the basis for the evolution of these networks and interconnects towards the full MMTel service.

    With the introduction of new multi-media services there are benefits to be gained from using the service-aware hub carrier network. The service hub can provide interworking between services both at the media layer (trans-coding) and also at the service layer for example, interworking between legacy SMS/MMS and IMS messaging.

    Conclusion The evolution of the voice interconnect creates opportunities for the operators to:

    reduce capex/opex by using IP technolo-

    MSS

    IMS Multimedia IPinterconnect

    MSS

    IMS

    Control planeCS SIP-I voice/videoIMS SIP instant messaging IMS SIP presenceIMS SIP voice/video

    User planeMSRPRTP

    FigurE 5 Combined voice and multimedia interconnect.

    14

    E r i c s s o n r E v i E w 2 2010

    Vinjett

    E r i c s s o n r E v i E w 2 2010

    Keep evolving towards all IP

  • gy with more efficient codecs optimize voice quality by reducing the transcoding steps and introducing new HD audio codecs reduce transmission costs by selecting a new interconnect architecture increase revenue by providing multi-media interworking between operator networks.

    Ericsson believes that the evolution of the voice interconnect is an impor-tant part of the overall evolution of tele-phony. Ericsson is working with the major operators, carriers and standards bodies to ensure that this evolution is successful and that end users and the industry can benefit from the opportu-nities described above.

    Soner Yamen

    joined Ericsson in 1995 as a support engineer. In 1999, after having served as a solution and project

    manager in the market unit, he transferred to system management at Ericsson Eurolab. In 2000, he joined product management, where he is currently responsible for the functional areas Transport and Network Quality & Efficient Infrastructure in product line switching at Business Unit Networks. He holds a Master of Science in Electrical Engineering from the University of Wisconsin-Madison, US.

    http://www.telegeography.com/product-info/tg/index.php1. ITU Q1912.5, 3GPP TS 29.1642. 3GPP TS 29.1633.

    references

    John Baldwin

    joined Ericsson in 2006 following the Marconi acquisition. He first worked for the Systems

    and Technology group within the Core & IMS unit of Business Unit Networks on strategies for connecting the mobile softswitch (MSS) to IMS networks. He was then involved in IP-based interconnects for MSS and IMS networks. At present, he is involved in the study of IP-based interconnects and new applications that use IMS networks and the internet. He holds a Bachelor of Science in Mathematics from the University of Warwick, UK.

    Jrg Ewert

    joined Ericsson in 1999 as a system manager for MSS operation and maintenance. He later

    became the leader of the O&M system design team. In 2005 he joined the MSS product management team, where he was responsible for network management and security. At present, he is responsible for MSS and IMS co-existence and SIP interconnects in product line switching at Business Unit Networks. Jrg has studied business administration at the University of Hagen, Germany, and he holds a Master of Science and a PhD. in Physics from the University of Gttingen, Germany.

    E r i c s s o n r E v i E w 2 2010

    Vinjett

    15

    E r i c s s o n r E v i E w 2 2010