White Paper

Nokia MSC Server System

The rst true mobile soft switch and backbone independent Multimedia Gateway for GSM/EDGE and WCDMA networks

White Paper

Contents
Introduction Facing the future with Nokia MSC Server System Safe interworking with existing networks New interfaces and protocols Cutting costs with the MSC Server System Fewer sites Transmission savings Savings by mobile optimized VoIP Field proven quality and resiliency Long-term investment protection Optimal solution for all operators Abbreviations 2 3 3 4 4 4 5 5 5 6 6 7

Introduction
The mobile industry is facing new challenges in todays turbulent business environment. Although networks are growing, the revenue per minute from mobile phone calls is decreasing, while the implementation of EDGE and WCDMA networks demands an economic balancing act from industry players. In this challenging environment, operators need a solution that can answer four vital questions: How can I maximise voice revenue? How can I reduce operational costs? How can I protect existing network investments? How can I deploy WCDMA while increasing protability in GSM? To solve these challenges, Nokia has introduced the MSC Server solution, a common circuit switched core for both GSM/EDGE and WCDMA. When subscribers migrate from GSM to WCDMA, the same core network elements can be used throughout the migration. No changes in the elements or the network topology are needed, keeping the cost and risk to a minimum.

White Paper

Facing the future with Nokia MSC Server System

The MSC Server System is independent of the transmission backbone and is specied in the 3G Partnership Programs Release 4 specications (3GPP Rel4). It separates call control and signaling (control plane) and trafc (user plane) into separate network elements. The MSC Server (MSS) handles call control and signaling, while the Multimedia Gateway (MGW) takes care of switching and carries the actual trafc. This division allows a totally new style of structure for the core network. Call control can be amalgamated into very large centers, while the actual voice trafc ow can be optimized by locating the MGWs close to trafc hot spots and the interconnection points closer to other networks. The Nokia MSC Server System provides a state of the art system compliant with 3GPP Rel4 standards, which offer the rst real possibility of implementing Voice over IP (VoIP) in the mobile environment in a standardized way. This allows operators to achieve the benets of VoIP safely without the limitations of proprietary solutions. It also ensures a safe interworking of the mobile VoIP core network with the existing network infrastructure. In the Nokia implementation, the MSC Server has similar call control and signaling functions as the MSC, allowing an existing Nokia MSCi to be upgraded to an MSC Server. The element can operate as both a MSC and a MSC Server simultaneously, safeguarding the existing MSC investment. Nokia MSC Server System supports both GSM/EDGE and and WCDMA radio networks. Looking further ahead, 3GPP will standardize IP multimedia voice calls. The Nokia MSC Server System will interconnect voice calls with SIP between the IP Multimedia Subsystem (IMS) domain and existing circuit switched domains. The investment in the Nokia MSC Server System will bring substantial returns well into the IP Multimedia era.
IN & other application servers
CAP/INAP SIP

IP Multimedia Subsystem

HLR

MAP

MSC Server

Nc BICC

Mc

SIGTRAN H.248

Mc

GSM BSS 3G RAN PSTN MGW

Nb

IP, TDM or ATM

Nb

GSM BSS 3G RAN PSTN MGW

Figure 1. 3GPP Rel4 MSC Server architecture and main interfaces.

Network Management

Billing

Network Management

Billing

IN (CAP/INAP)

HLR (MAP)

IN (CAP/INAP)

HLR (MAP)

MSC Server
SIGTRAN H.248/Megaco

MSC (ISUP) RAN (RANAP) BSS (BSSAP) RAN (RANAP) BSS (BSSAP)

MSC (ISUP)

PSTN (ISUP)

PSTN (ISUP)

MSC

MGW

Figure 2. The MSC Server System integrates safely into the existing network. From the existing networks point of view, the MSC Server System uses the same eld-proven interfaces and protocols as the MSC System, ensuring safe interworking with both single vendor and multi-vendor networks.

Safe interworking with existing networks

The MSC Server System supports all existing interfaces with legacy network elements. For example, Intelligent Networks (with INAP or CAP) and GSM/PSTN networks (with ISUP) can be connected to the MSC Server System in a similar way to their connections with MSC systems. Also, interfaces with

GSM BSS (A interface) and WCDMA RAN (Iu-CS interface) networks are identical with todays eld proven interfaces and protocols. This ensures that MSC Server System is compatible with todays networks, including those with elements from several vendors. The similarity between the current MSC System and the MSC Server System is illustrated in Figure 2.

White Paper

Voice Mail Systems and Short Message Service Centers (SMSC) connect to the MSC Server System with the same interfaces currently used. In the case of the integrated MSC Server, the connection can remain in the MSC Server without changes. For a new standalone MSC Server, the VMS and SMSC can be connected via the MGW with ISUP. If the SMSC supports SIGTRAN, a direct connection from the MSC Server by SIGTRAN is also possible. Figure 3 illustrates the options for connecting an SMSC.

MSS
SIGTRAN

SIGTRAN capable SMSC Connection directly to MSS by SIGTRAN

H.248 & SIGTRAN

H.248 & SIGTRAN

Non SIGTRAN capable SMSC Connection by C7 over TDM SIGTRAN from MGW to MSC Server
TDM E1 / MAP

MGW

MGW SMS path (SIGTRAN connected SMSC) SMS path (TDM connected SMSC)

New interfaces and protocols

3GPP Rel4 technical specications dene the functional entities and the interfaces needed to support the mobile service. The main new interfaces are: Mc interface (MSC Server MGW) Nc interface (MSC Server MSC Server) Nb interface (MGW MGW) The main protocols introduced by 3GPP Rel4 are H.248/Megaco, SIGTRAN and Bearer Independent Call Control (BICC). H.248/Megaco is a control protocol used by the MSC Server to control the MGW over the Mc interface. SIGTRAN is used to transport C7 signaling over the IP network. It is also used between the MGW and MSC Server to transport PSTN and GSM / UMTS Radio Network signaling to the MSC Server over the Mc interface. Thus the MGW acts as an integrated Signaling Gateway. In the CS domain, SIGTRAN can also be used between the MSC Server and HLR and IN/SCP. BICC is used for call control between two MSC Servers in the Nc interface, allowing a backbone independent Control Plane and User Plane. The Nokia MSC Server System supports Session Initiation Protocol (SIP), connecting the MSS to IP Multimedia Core elements and other SIP capable network elements.

SMSC connection options E1 connection to Integrated MSC Server E1 connection to MGW SIGTRAN connection to Integrated or Standalone MSC Server

Figure 3. An SMSC connection to an MSC Server can use the same interfaces and protocols as SMSC connection to a traditional MSC.

MSS (control) Only signalling between MSS and MGW Number and location of MSS sites is independent of traffic => Number of sites can be reduced MGW seldom requires a site visit MGW elements can be located to existing BSC/RNC sites => No dedicated sites required
A Iu-CS Backbone PSTN

Signalling only

MSS and MGW are compact in size Footprint 1/3 of typical MSC footprint => Floorspace cost minimized

MGW (switching)

Figure 4. Site cost is reduced due to the optimal location of elements and the reduced oor space needed.

Cutting costs with the MSC Server System

The Nokia MSC Server System provides key benets that increase revenue as well as decrease costs. number of sites needed. Also, access costs can be kept low by local switching at distributed MGWs, which can be located in existing BSC and/or RNC sites. Thus the total number of sites can be minimized. Site cost savings are illustrated in Figure 4. Site numbers and total oor space requirement are also reduced through the improved capacity per footprint ratios of the Nokia MSC Server BHCA/ footprint and MGW-Erlang/footprint.

Fewer sites
The separation of the user plane and control plane allows the respective elements to be located independently of each other. MSC Servers can be concentrated on a few sites at the most convenient location, reducing the

White Paper

Transmission savings
The MSC Server System saves transmission costs by local switching for calls managed by a single, local MGW. Increasing the capacity of the call control element leads to increasing distances between call control and trafc hot spots. With MSC systems, this may lead to expensive inter-city transmission connections, even for local mobile-tomobile or mobile-to-PSTN calls, due to the fact that all trafc needs to be transported to the MSC to be switched. With MSC Server Systems, the distributed MGWs can perform local switching, removing the need to carry local trafc over long distances. This is illustrated in Figure 5. The Nokia MSC Server System also saves transmission bandwith capacity compared what is needed by traditional switching systems. This is possible by an integrated voice compression feature that is compatible with all transmission technologies (TDM, IP and ATM). Furthermore, transmission capacity savings can be combined with optimal voice quality by Transcoder Free Operation (TrFO) or Tandem Free Operation (TFO) with Nokia specic enhancements. Transmission backbone capacity can be shared based on trafc needs.
BSS/RAN MSC MSC System High MSC capacity increases access transmission cost Difficult to reduce the number of MSCs PSTN MSC Server MSC Server System Local traffic is switched locally in MGWs MSC Server capacity can be maximized without access cost increase City B

H.248 BSS/RAN MGW City A

Figure 5. Separation of call control and switching enables high capacity control elements and localized switching. This eliminates long transmission legs in local calls.

TMSC TMSC MSC MSC MSC MSC Servers MSC TDM for voice MSC MSC MSC

Multimedia Gateways

IP for all voice, data and signalling

MSC MSC

MSC

Figure 6. MSC network and MSC Server network. The MSC Server System uses the multi-service IP network to transport trafc and signaling.

Savings by mobile optimized VoIP

In a Nokia MSC Server network, the TDM point-to-point connections of MSC networks can be replaced by Ethernet interfaces to the IP backbone. Trafc changes can be accommodated in the interfaces without modications and the laborious conguration familiar from TDM connections is also unnecessary. The routing of trafc and signaling is provided by the backbone. This ease of operation of the IP based network will dramatically reduce the required O&M work. The IP based network will also remove the need for a transit layer. IP transport in the backbone allows trafc interfaces to be shared, rather than requiring dedicated TDM interfaces for each trafc direction. Together with the exible

operation of IP compared to TDM, this enables even large networks without a transit MSC layer, without compromising network operability. The differences between MSC and MSC Server networks are illustrated in Figure 6. Non-real-time (non-voice) packet data will grow signicantly during the coming years, along with GPRS and WCDMA. The MSC Server System is important in this development as it provides the voice call (and WCDMA real time video call) services in these networks. MSC Server, which supports all current transport technologies, including TDM and ATM, allows the operator to consolidate voice and data transport networks into a single IP based transport network.

Field proven quality and resiliency

Mobile telecommunications networks have grown from niche applications to the preferred carrier of all voice and data. To facilitate the cost-effective operation of large networks, the network elements must offer eld proven technology, high capacity, low energy consumption and small oor space. In the Nokia solution, the MSC Server and the Multimedia Gateway are based on the eld proven resilient DX 200 and IPA2800 platforms. The Nokia MSC Server System provides the highest proven capacity in the market. The processing capacity is the real operational capacity measured with a heavy usage prole that includes IN services. In addition to
5

White Paper

the resilient platforms, the Nokia MSC Server System employes system-wide multi-layer resilience mechanisms for both voice and signaling. This ensures that there is no single point of failure in the entire Nokia MSC Server System.

Optimal solution for all operators

The Nokia MSC Server System is the optimal solution for all kinds of operators, regardless of their current situation and network structure. For greeneld operators, the Nokia MSC Server System is an ideal solution as it provides best-in breed products and high capacities. As the Nokia MSC Server System has been developed on eld proven Nokia platforms, the operator gets the latest technology together with high quality and availability. Also, since the Nokia MSC Server System has all the interfaces for interconnecting with GSM, WCDMA and PSTN networks, Nokia can provide a exible solution to meet differing needs. For the existing Nokia GSM/EDGE customer, the Nokia MSC Server System provides an easy migration to the 3GPP Release 4 architecture, as the existing MSCis can be fully re-used. The Nokia MSC Server System also uses the current TDM based architecture where applicable. Furthermore, the network can be split, allowing certain regions to be built with the MSC Server System while other regions continue with traditional switching architecture. For Nokia WCDMA customers, the migration to MSC Server architecture is even easier as the current network elements, 3G MSC and MGW, can be fully reused in the MSC Server architecture. Nokia 3GPP Release 99 network elements can be upgraded to MSC Server System network elements with a simple software upgrade and in some cases with minor hardware changes. For operators currently using circuit switched core infrastructure from another telecommunications vendor, the Nokia MSC Server System is a feasible solution for expansion. Nokia has a long experience of multi-vendor integration and interoperability testing, guaranteeing a seamless expansion with the Nokia MSC Server System based on open interfaces. In todays challenging market situation, mobile network operators must cut investment while ensuring they are not left behind by as networks evolve. The MSC Server System meets both these needs by providing a cost-effective optimized circuit switched core solution that will evolve to accommodate IP Multimedia. An investment in the Nokia MSC Server System allows easy and safe migration from GSM to WCDMA radio access and to the pure IP Multimedia core through simultaneous support of existing and new core interfaces and standards. The Nokia MSC Server System guarantees service continuity, ensures investments are fully protected and maintains value for operators developing a mobile network to keep ahead in the competition. Looking further ahead, the advent of 3GPP Release 6 or Release 7 wilI standardize IP multimedia voice calls. The Nokia MSC Server will interconnect voice calls with SIP between the IP Multimedia domain and existing circuit switched domains, such as todays large circuit switched GSM/WCDMA networks and PSTN. Voice migration from circuit switched to IP Multimedia will happen gradually, yet the investment in the Nokia MSC Server System will bring substantial returns well into the IP Multimedia era.

Long-term investment protection

The current Nokia MSCi elements can be upgraded to MSC Servers in a simple way by activating the MSC Server software, fully safeguarding the existing MSCi investment. The MSC Server System supports GSM/EDGE and WCDMA subscribers simultaneously and can dynamically allocate any share of its capacity between them. This means that full use can be made of the MSC Server investment even with a purely GSM network. Numbers of WCDMA subscribers are expected to grow rapidly when they do, MSS capacity can be used for WCDMA by adding interfaces to RNCs. In terms of WCDMA migration as well as migration to VoIP, the MSC Server System is a safe investment. 3GPP Rel 6 or Rel 7 will fully standardize IP multimedia voice calls in future. MSC Server will be the system needed for interconnecting voice calls between the IMS domain and existing circuit switched (CS) domains, such as todays large circuit switched GSM/WCDMA networks and PSTN. Voice migration from CS to IMS will happen gradually and investments in MSC Server Systems will be relevant well into the IP Multimedia era.

White Paper

Abbreviations
3GPP Third Generation Partnership Project. A group of organizational partners that have agreed to co-operate in the formulation of technical specications for third generation mobile systems based on further evolved GSM core networks and radio access technologies. ATM Asynchronous Transfer Mode. An international CCITT standard for high-speed packet-switched networks that operates at digital transmission speeds above 1.544 Mbps. BHCA Busy Hour Call Attempt. How many call setups are made in an hour. Example value 3600 bhca means that new call attempt is made after every second. BICC Bearer Independent Call Control. An Inter-MSC Server signaling protocol specied by ITU-T and 3GPP. The use is dened in 3GPP Release 4 specications. CAP CAMEL Application Protocol. A signalling protocol between Service Switching Point and Service Control Point. It enables Intelligent Network services for roaming subscribers. H.248/Megaco MSC Server uses this protocol to control Multimedia Gateway over the Mc interface. It is dened in 3GPP Release 4 specications. IMS IP Multimedia Subsystem. Enables operators to deploy person-to-person multimedia services in 2G and 3G networks.

INAP Intelligent Network Application Protocol. A signalling protocol between Service Switching Point and Service Control Point. It enables Intelligent Network services. IP Internet protocol. A communication protocol specied by the Internet Engineering Task Force (IETF). ISUP ISDN User Part. This portion of the signaling system manages the telephone call, including calling party number information, call status checking, trunk management, system messaging. MAP Mobile Application Part. An open interface specied by ETSI. The MAP functions mainly concern the information exchange between switches and registers in GSM networks related to the possibility for a mobile station to roam. MGW Multimedia Gateway. Network element that together with MSC Server forms the MSC Server System. It takes care of switching and carries the actual trafc. Multimedia Gateway is dened in 3GPP Release 4 specications. MSS MSC Server. Network element that together with Multimedia Gateway forms the MSC Server System. It handles call control and signaling. MSC Server is dened in 3GPP Release 4 specications. PSTN Public Switched Telephone Network. Regular phone lines. SIGTRAN SIGTRAN is a set of protocols dened to transport SS7 messages over IP networks.

SIP Session Initiation Protocol. A signaling protocol for Internet conferencing, telephony, presence, events notication and instant messaging. SMSC Short Message Service Centre. Network element through which short messages are transmitted and in which they can be stored for later transmission if the receiver is not reached. TDM Time Division Multiplexing. A type of multiplexing that combines data streams by assigning each stream a different time slot in a set. TFO Tandem Free Operation. Conguration of a voice or multimedia call for which transcoders are physically present in the communication path but transcoding functions are disabled or partially disabled in order to avoid multiple transcoding. The objective of avoiding multiple transcoding is to improve the speech quality in calls. TrFO Transcoder Free Operation. Conguration of a speech or multimedia call for which no transcoder device is physically present in the communication path and hence no control or conversion or other functions can be associated with it. The purpose of TrFO is to remove unnecessary speech encoding completely from the speech path. UMTS Universal Mobile Telecommunication System. Third generation mobile system. VoIP Voice over IP. Technology to carry voice communication over a data network based on the Internet protocol.

The contents of this document are copyright 2004 Nokia. All rights reserved. A license is hereby granted to download and print a copy of this document for personal use only. No other license to any other intellectual property rights is granted herein. Unless expressly permitted herein, reproduction, transfer, distribution or storage of part or all of the contents in any form without the prior written permission of Nokia is prohibited. The content of this document is provided as is, without warranties of any kind with regards its accuracy or reliability, and specically excluding all implied warranties, for example of merchantability, tness for purpose, title and non-infringement. In no event shall Nokia be liable for any special, indirect or consequential damages, or any damages whatsoever resulting form loss of use, data or prots, arising out of or in connection with the use of the document. Nokia reserves the right to revise the document or withdraw it at any time without prior notice. Nokia and Nokia Connecting People are registered trademarks of Nokia Corporation. Nokia product names are either trademarks or registered trademarks of Nokia. Other product and company names mentioned herein may be trademarks or trade names of their respective owners.

Nokia code: 11129 1204 Indivisual/Libris Copyright 2004 Nokia. All rights reserved. Nokia and Nokia Connecting People are registered trademarks of Nokia Corporation. Other product and company names mentioned herein may be trademarks or trade names of their respective owners. Products are subject to change without notice.

NOKIA CORPORATION Networks P.O. Box 300 FIN-00045 NOKIA GROUP, Finland Phone: +358 (0) 7180 08000 www.nokia.com