MGW for MSS integration overview

Page 1 of 12

Library:

Nokia Multimedia Gateway, Rel.

U4.0, Product Documentation, v.3

Identifier: dn02159419-911-en

MGW for MSS integration overview

You can start the integration of Multimedia Gateway (MGW) after it has been successfully installed and commissioned. During
the commissioning phase MGW is configured and tested as a standalone entity. During the integration phase the
interconnections between different network elements are configured and their parameters are customised. After successful
integration, MGW is ready for commercial use.
MGW's integration can be divided into two:
z basic integration
z integration extensions

The basic integration includes procedures that are commonly used when integrating MGW into the surrounding network. For
more information on the basic integration procedures, see MGW for MSS integration overview table.
In addition MGW provides integration extensions that can be used to configure alternative or additional interconnections between
different network elements. For more information on the integration extensions, see MGW for MSS integration extensions
overview.

Example networks
MGW's integration instructions are based on the following Nokia network solution examples:
z Nokia Circuit-Switched (CS) Core network solution

http://127.0.0.1:43231/NED/NED?service=printview&library=mgw_rel_u4_0_v3_2008_0... 4/23/2009

MGW for MSS integration overview

Page 2 of 12

Figure: Multimedia Gateway in the CS Core network environment based on the network architecture first
introduced in 3GPP Rel.4
z Nokia IP Multimedia Subsystem (IMS) network solution

http://127.0.0.1:43231/NED/NED?service=printview&library=mgw_rel_u4_0_v3_2008_0... 4/23/2009

MGW for MSS integration overview

Page 3 of 12

Figure: Multimedia Gateway in the IMS environment

z Nokia Unlicensed Mobile Access (UMA) solution for MSC Server

http://127.0.0.1:43231/NED/NED?service=printview&library=mgw_rel_u4_0_v3_2008_0... 4/23/2009

MGW for MSS integration overview

Page 4 of 12

Figure: Multimedia Gateway in the UMA solution for MSC Server

MGW's integration involves the following network elements and interfaces:
MGW
for MSS

Multimedia Gateway for MSC Server, whose main task is to convey the user plane data from the radio access
network to the backbone network and vice versa.
The following interfaces are used for connecting two MGWs:
z ATM backbone (Nb)
z IP backbone (Nb)
z TDM backbone (Nb)
z Nb' interface (Nokia proprietary)

MGW
for IMS

In the IMS network environment MGW provides the link between the circuit-switched networks or IP-/ATM-based
packet-switched (PS) networks and the IP Multimedia Core network. It acts as a gateway for both user plane and
signalling (signalling transport) traffic. MGW intercorporates functionality for protocol and media translation, and it
also provides tones, voice announcements, and voice conference services for Session Initiation Protocol (SIP)
users.
The Mb interface is used to connect MGW and the IP Multimedia Core network.

MGW
for
UMA

In the UMA network environment MGW provides the user plane connection towards the Unlicensed Mobile
Access Network (UMAN). UMA provides access to GSM and GPRS mobile services over unlicensed spectrum
technologies, including 802.11 (Wireless LAN) and Bluetooth. UMA technology also enables roaming and
handovers between GSM/EDGE/GPRS radio network and public/private unlicensed wireless networks for
subscribers with dual-mode mobile stations (MS).

http://127.0.0.1:43231/NED/NED?service=printview&library=mgw_rel_u4_0_v3_2008_0... 4/23/2009

MGW for MSS integration overview

Page 5 of 12

The Up-CS interface is used to connect MGW and the Unlicensed Mobile Access Network.
MSS

MSC Server, whose main task is to process the control plane of a call. The MSS can be a standalone MSS,
which does not have user plane connections, or it can be an integrated MSS which is a conventional MSC
upgraded with the actual MSC Server functionalities.
Table: Key functionalities in MSS and Integrated MSS
Functionality

MSS

Integrated MSS

VLR

Yes

Yes

SSP

Yes

Yes

Mobility Management

BSSAP, RANAP, MAP BSSAP, RANAP, MAP

CS Data Call IWF

In CDS

Yes

PBX connections

Yes*

Yes

Announcements, conference, tones In MGW

Yes

MGCF

Yes

Yes

SS7 over TDM

In IPCH

Yes

CAS

No

Yes

SIGTRAN

Yes

Yes

SIP

Yes

Yes

BICC-CS2

Yes

Yes

H.248

Yes

Yes

* PBX connections can be supported either by utilising the semipermanent TDM-TDM connection functionality or
by utilising the ISDN Q.921 User Adaptation Layer (IUA) on top of IP. In the case of semipermanent TDM-TDM
connections, the PBX connections are supported by deploying the Primary Rate Access Units (PAU) into the
optional IPCH cabinet. In the case of IUA, the IPCH cabinet is not needed as the transmission between the MSC
Server and MGW is handled on top of existing IP connections using the Stream Control Transport Protocol
(SCTP).
The following interfaces are used to connect MSS/Integrated MSS and MGW:
z interconnecting TDM interface
z H.248 control interface (Mc/Mn)

The integration procedures for different interfaces are mostly the same irrespective of whether MGW is integrated
to a standalone MSS or to an integrated MSS.
The key differencies are related to the TDM-based A interface and PSTN/PLMN interface. If MGW is controlled
by a standalone MSS, the TDM circuits of the A interface and PSTN/PLMN interface are always connected to
MGW. If MGW is controlled by an integrated MSS, the TDM circuits of the A interface and PSTN/PLMN interface
can also be connected to MSS.
Also, if MGW is controlled by a standalone MSS, the interconnecting TDM circuits and the IWF control interface
for CS data calls are connected to a standalone element called Circuit-switched Data Server (CDS). If MGW is
controlled by an integrated MSS, the interconnecting TDM circuits and the IWF control interface for CS data calls
can be connected to both the interworking function (IWF) in the integrated MSS and to the standalone CDS.
MSSu

The MSSu is a product variant that has all the core functionalities that are in the MSS.
The difference between the MSS and the MSSu is that the MSSu is always an upgrade from an existing MSCi.
Operators who want to deploy the MSC Server system to their existing GSM network and want to utilise the
existing hardware, can upgrade the MSCi to a standalone MSSu.
The difference between the MSSu and an Integrated MSS is that the MSSu is a standalone server product
dedicated only to control plane handling, whereas an Integrated MSS can also have TDM-based control and user
plane traffic.

http://127.0.0.1:43231/NED/NED?service=printview&library=mgw_rel_u4_0_v3_2008_0... 4/23/2009

MGW for MSS integration overview

Page 6 of 12

Table: Key functionalities in MSSu

Functionality

MSSu

VLR

Yes

SSP

Yes

Mobility Management

BSSAP, RANAP, MAP

CS Data Call IWF

In CDS

PBX connections

No

Announcements, conference, tones In MGW

GCS

MGCF

Yes

SS7 over TDM

No

CAS

No

SIGTRAN

Yes

SIP

Yes

BICC-CS2

Yes

H.248

Yes

Gateway Control Server. It is similar to MSS, but does not contain VLR and radio network access functionalities.
It is used in association with the calls which are destined to PSTN/ISDN.
Table: Key functionalities in GCS and Integrated GCS
Functionality

GCS

Integrated GCS

VLR

No

No

SSP

Yes

Yes

Mobility Management

MAP

MAP

CS Data Call IWF

In CDS No

PBX connections

Yes*

Yes

Announcements, conference, tones In MGW Yes

MGCF

Yes

Yes

SS7 over TDM

In IPCH Yes

CAS

No

Yes

SIGTRAN

Yes

Yes

SIP

Yes

Yes

BICC-CS2

Yes

Yes

H.248

Yes

Yes

* PBX connections can be supported either by utilising the semipermanent TDM-TDM connection functionality or
by utilising the ISDN Q.921 User Adaptation Layer (IUA) on top of IP. In the case of semipermanent TDM-TDM
connections, the PBX connections are supported by deploying the Primary Rate Access Units (PAU) into the
optional IPCH cabinet. In the case of IUA, the IPCH cabinet is not needed as the transmission between the MSC
Server and MGW is handled on top of existing IP connections using the Stream Control Transport Protocol
(SCTP).
The H.248 control interface (Mc/Mn) is used to connect GCS and MGW.
If MGW is controlled by a standalone GCS, the TDM circuits of the PSTN/ISDN interface are always connected to
MGW. If MGW is controlled by an integrated GCS, the TDM circuits of the PSTN/ISDN interface can also be
connected to GCS.
CDS

Circuit-switched Data Server, whose main task is to provide an interworking function (IWF) for circuit switched
data calls between the mobile network and PSTN. IWF can also be integrated into MSC Server.

http://127.0.0.1:43231/NED/NED?service=printview&library=mgw_rel_u4_0_v3_2008_0... 4/23/2009

MGW for MSS integration overview

Page 7 of 12

The following interfaces are used to connect CDS and MGW:

z interconnecting TDM interface
z IWF control interface (Nokia proprietary interface)

BSC

Base Station Controller, whose main task is to convey SS7/TDM-based user plane and control plane traffic
between the 2G BSS and core network. BSC is connected either to MGW or to MSC Server depending on the
operator's network architecture. If BSC is connected to MGW, the user plane traffic (speech and data) is always
routed via MGW to the ATM/IP/TDM backbone, while the control plane traffic (BSSAP signalling) is routed either
directly to MSC Server or transparently via MGW to MSC Server.
The A-interface is used to connect BSC and MGW.

RNC

Radio Network Controller, whose main task is to convey circuit switched traffic between 3G RAN and core
network.
The Iu-CS interface is used to connect RNC and MGW.
Note
In addition to the circuit switched traffic from the Iu-CS interface, it is also possible to route the
Iur traffic via MGW. ATM AAL type 2 nodal switching functionality makes it possible to route the
Iur traffic between two adjacent RNCs via MGW without any control from MSC Server.

Fixed
Softswitch

MGW provides an interface (Fss) towards external 3rd party Fixed Soft-switch products. Currently the solutions
for the Fixed Soft-switch products are mainly targeted to fixed line operators for bridging the gap between fixed
and mobile networks. In the future the Fixed Soft-switch solutions can also provide a way of implementing IP
convergence from a number of different kinds of access technologies to the unified IP-based core network.
The Fss is not a standard reference point but nevertheless its packet-switched user plane implementation is
equivalent to the Mb interface solution in MGW. In the Fss interface the use of the RTP protocol is based on the
IETF standards.

SGSN

GPRS support node, whose main task is to maintain the 3G packet switching connection towards 3G RAN.
Note
MGW does not have a direct interface towards SGSN, but the Iu-PS interface (between SGSN
and RNC) can be routed through MGW. When routing the Iu-PS interface, the packet-switched
traffic is cross-connected on the ATM layer inside MGW and routed towards SGSN.

NetAct

Nokia NetAct is a part of the total Nokia 3G solution. It provides a remote operation and maintenace connection
towards MGW. In addition to MGW, the NetAct system can be used to manage both 2G and 3G Radio Access
Networks (RAN) and the common core networks for 2G and 3G.

Integration steps
The following list includes the basic MGW integration steps and the recommended order in which they should be executed. The
steps can also be done in a different order, depending on the architecture and requirements of the existing network. For more
information on the different procedures, see MGW for MSS integration overview table.
1.

Plan the surrounding network.

2.

Configure the site connectivity.

3.

Configure the O&M connections between MGW and NetAct.

For information on preparing and configuring O&M connections between MGW and NetAct, refer to Integrating 2G/3G
Circuit Switched Core NEs to NetAct in NetAct (OSS) product documentation.

http://127.0.0.1:43231/NED/NED?service=printview&library=mgw_rel_u4_0_v3_2008_0... 4/23/2009

MGW for MSS integration overview

4.

Integrate NEMU.

5.

Install and activate software licences in MGW.

6.

Configure IP for user plane (Mb, Nb, Nb', Fss, Up-CS).

7.

Create MGW's local configuration parameters.

8.

Configure transit-signalling connections.

9.

Create Nb interface with ATM and/or TDM backbone.

Page 8 of 12

10.

Create interconnecting TDM connections.

11.

Create ATM-based Iu-CS interface.

12.

Create A-interface (optional).

13.

Create Ater interface (optional).

14.

Create PSTN/PLMN interface (optional).

15.

Configure Virtual Media Gateways, H.248 and IWF control connections.

16.

Construct announcement files.

17.

Configure synchronisation inputs.

18.

Print alarms.

MGW for MSS integration overview table

Table: MGW for MSS integration overview table
Integration descriptions
z Required integration planning information for MGW

Integration instructions
Configuring site connectivity for MGW

for MSS
z Overview of configuring site connectivity for MGW
z Overview of configuring O&M connections in MGW
z Configuring IP stack in functional units of MGW
z Overview of configuring IP for user plane (Mb, Nb,

Nb', Fss, Up-CS)

z Overview of configuring transit-signalling connections

(MGW - MSC Server)

z Overview of creating Nb interface with ATM

backbone (MGW for MSS - MGW for MSS)

z Overview of creating Nb interface with TDM

z Connecting O&M traffic in MGW via Ethernet

z Connecting signalling and control traffic in MGW via

Ethernet
z Configuring IP static routes in MGW
z Example: Configuring site connectivity for MGW

backbone (MGW for MSS - MGW for MSS)

Configuring O&M connections between MGW and NetAct
z Overview of creating interconnecting TDM

connections (MGW - MSC Server/CDS)

z Creating MMI user profiles and user IDs for remote

connections to NetAct
z Overview of creating ATM-based Iu-CS interface

(MGW for MSS - RNC)

z Checking the IP address information in NEMU

http://127.0.0.1:43231/NED/NED?service=printview&library=mgw_rel_u4_0_v3_2008_0... 4/23/2009

MGW for MSS integration overview

z Overview of creating A-interface (MGW for MSS -

Page 9 of 12

z Configuring NEMU for MGW connection

BSC)
z Defining external time source for network element
z Overview of creating Ater interface (MGW for MSS -

BSC)
z Overview of creating PSTN/PLMN interface (MGW

for MSS - PSTN/PLMN)

Integrating NEMU
z Configuring Nokia NetAct interface with NEMU

z Overview of configuring IP for H.248 and IWF control

connections (MGW - MSC Server/CDS)

Configuring software licences in MGW
z Installing and activating software licences in MGW
z Example: Installing and activating software licences in

MGW
Configuring IP for user plane (Mb, Nb, Nb', Fss, Up-CS)
z Configuring internal connections between IPFGE and

TCU
z Connecting MGW to external network via IPFGE
z Configuring MGW for User Plane via IP backbone with

NP2GE
z Configuring multiple isolated IP networks (optional)
z Configuring RTP/RTCP IP port number space in MGW
z Configuring RTCP user plane monitoring in IP-based

interfaces
z Configuring passthrough channel in MGW (optional)
z Configuring IP Quality of Service for user plane in

MGW
z Example: Configuring IP for user plane via IPFGE (Mb,

Nb, Nb', Fss, Up-CS)

z Example: Configuring IP for user plane via NP2GE (Mb,

Nb, Nb', Fss, Up-CS)

Creating MGW for MSS configuration parameters
z Creating local signalling configuration for MGW
z Creating MGW for MSS -specific default parameters
z Defining user plane parameter sets in MGW for MSS
z Configuring DSP service pools in MGW
z Configuring integrated IP Security for O&M and control

connections (optional)
z Example: Creating MGW for MSS configuration

http://127.0.0.1:43231/NED/NED?service=printview&library=mgw_rel_u4_0_v3_2008_0... 4/23/2009

MGW for MSS integration overview

Page 10 of 12

parameters
Configuring transit-signalling connections (MGW - MSC Server)
z Creating M3UA configuration
z Creating IUA configuration

Creating Nb interface with ATM backbone (MGW for MSS MGW for MSS)
z Configuring SDH for ATM transport
z Creating SDH protection group
z Creating phyTTP
z Creating ATM resources in MGW
z Creating remote MTP configuration
z Activating MTP configuration
z Setting MTP level signalling traffic load sharing
z Creating routing objects and digit analysis for Nb

interface in MGW
z Creating routing objects and digit analysis with

subdestinations and routing policy for Nb interface

z Example: Creating Nb interface with ATM backbone

(MGW for MSS - MGW for MSS)

Creating Nb interface with TDM backbone (MGW for MSS MGW for MSS)
z Configuring PDH for TDM transport
z Configuring SDH for PDH transport
z Creating SDH protection group
z Creating routing objects for TDM resources controlled

by MSC Server
z Example: Creating Nb interface with TDM backbone

(MGW for MSS - MGW for MSS)

Creating interconnecting TDM connections (MGW - MSC
Server/CDS)
z Configuring PDH for TDM transport
z Creating routing objects for IWF/CDS-dedicated TDM

connections
z Creating routing objects for TDM resources controlled

by MSC Server
z Example: Creating interconnecting TDM connections

http://127.0.0.1:43231/NED/NED?service=printview&library=mgw_rel_u4_0_v3_2008_0... 4/23/2009

MGW for MSS integration overview

Page 11 of 12

(MGW - MSC Server/CDS)

Creating ATM-based Iu-CS interface (MGW for MSS - RNC)
z Configuring SDH for ATM transport
z Creating SDH protection group
z Creating phyTTP
z Creating ATM resources in MGW
z Creating remote MTP configuration
z Activating MTP configuration
z Creating routing objects for ATM-based lu interface in

MGW
z Example: Creating ATM-based Iu-CS interface (MGW

for MSS - RNC)

Creating A-interface (MGW for MSS - BSC)
z Configuring PDH for TDM transport
z Configuring SDH for PDH transport
z Creating SDH protection group
z Creating remote MTP configuration
z Activating MTP configuration
z Creating routing objects for TDM resources controlled

by MSC Server
z Example: Creating A-interface (MGW for MSS - BSC)

Creating Ater interface (MGW for MSS - BSC)

z Configuring PDH for TDM transport
z Configuring the transcoder for the Ater interface

between BSC and MGW

z Configuring SDH for PDH transport
z Creating SDH protection group
z Creating remote MTP configuration
z Activating MTP configuration
z Creating routing objects for TDM resources controlled

by MSC Server
z Example: Creating Ater interface (MGW for MSS -

BSC)

http://127.0.0.1:43231/NED/NED?service=printview&library=mgw_rel_u4_0_v3_2008_0... 4/23/2009

MGW for MSS integration overview

Page 12 of 12

Creating PSTN/PLMN interface (MGW for MSS - PSTN/PLMN)

z Configuring PDH for TDM transport
z Configuring SDH for PDH transport
z Creating SDH protection group
z Creating remote MTP configuration
z Activating MTP configuration
z Setting MTP level signalling traffic load sharing
z Creating routing objects for TDM resources controlled

by MSC Server
z Example: Creating PSTN/PLMN interface (MGW for

MSS - PSTN/PLMN)
Configuring IP for H.248 and IWF control connections (MGW MSC Server/CDS)
z Configuring Virtual Media Gateways and H.248 control

protocol (MGW - MSC Server)

z Configuring IWF/CDS control protocol (MGW for MSS -

IWF/CDS)
z Example: Configuring IP for H.248 and IWF control

connections (MGW - MSC Server/CDS)

Constructing announcement files in MGW
Configuring synchronisation inputs
Printing alarms in MGW for MSS
z Printing alarms using LPD protocol
z Printing alarms via Telnet terminal or Web browser

Printed from NED5

Copyright Nokia Siemens Networks. All rights reserved.

http://127.0.0.1:43231/NED/NED?service=printview&library=mgw_rel_u4_0_v3_2008_0... 4/23/2009