MGW overview for NOC

The M-MGw located in the Connectivity layer manipulates the network

resources as instructed by the MSC or GMSC/Transit servers.
The M-MGw itself is a self-contained network element that provides all the
necessary functionality for handling and setting up the Connectivity layer at
the borders between different networks.
The MGW- connects the Mobile Core Network with external networks such
as UMTS/WCDMA and GSM Radio Access Networks, PSTN networks or
other mobile networks.
The M-MGw contains a full set of speech and data resources for performing
modifications and additions on the Connectivity Layer. It also contains
transport resources for performing protocol and Connectivity Layer
conversions between different networks, and provides Signaling Gateway
functionality for performing bearer conversions of control protocols.
Depending on network topology and the traffic cases that the M-MGw is
handling, the node can assume different roles in the Mobile Core Network.

MGW features are:

• ANSI Interfaces
• GSM A-interface
• GSM High-Speed Datacom Service
• IP Transport -
• SS7 Signaling over IP
• Voice Quality Enhancements
• SCCP Relay
• SCCP Accounting
• SCCP Policing
• Global Text Telephony
• Element Manager
• ETSI Interfaces
• Datacom Base
• ATM Transport - RNC ,MSC and other MGW
• TDM Transport - MSC
• ATM Switch - RNC and other MGW
• SS7 Signaling Gateway and Signaling Transfer Point - for other Network
Element
• SS7 Signaling over TDM - For MSC
• SS7 Signaling over ATM
• Gateway Control Protocol - Connection between MSC to MGW
• Media Stream Function
 Operation & Maintenance
M-MGw Operation and Maintenance is provided via the integrated Element
Management. The element manager (EM) is handled via a thin client
application that can be run from a standard web browser on any computer
locally or remotely using a graphical user interface (GUI). The client
communicates with the M-MGw using HTTP, IIOP and FTP/S-FTP.

Fault Management
The M-MGw transfers alarms according to ITU-T recommendation X.733 to
a fault management application in the network management center where it
is displayed with the related information about the fault. Alarms are also
visible in the MGw EM.
Fault Management provides support for detecting, recovering and reporting
Hardware and software faults. The standard IP- based Inter ORB protocol
(IIOP), based on CORBA, is used for fault management communication.

Software Management
The M-MGw supports software handling both locally and remotely
including software installations, software upgrades and backups. New
software (upgrade packages and/or configuration data) can be downloaded to
the M-MGw with minimal service disturbance.

Equipment Management
The M-MGw element manager handles the management of the hardware
equipment. It is possible to read the hardware structure and operational
status of the M-MGw.
Performance Management
This application can be divided into two areas, transfer of performance data
(from the node) and configuration and control of performance monitoring.
Activation and deactivation of performance management is done by a client
application, other than MGw EM. The technology used for transferring the
performance data is FTP/S-FTP.

Configuration Management
All software required for configuration of the node is contained in the M-
MGw. A Graphical User Interface (GUI) or Configuration Manager Scripts
are used for setting and modification of parameters associated with the M-
MGw configuration.
Functions Related to Media Stream Handling
The M-MGw contains a set of functions needed to support the circuit-
switched speech services in WCDMA and GSM. With the help of these
functions, the MGw can adapt the circuit-switched speech for transfer over
different networks. Speech coding from PCM coded voice to Adaptive
Multi-Rate (AMR) coded voice in WCDMA can be mentioned as an
example.
On ATM and IP bearers, the payload is delivered to/from M-MGw in
packages that contain several speech samples accompanied by addressing
information used by the bearer in question. These packages are called
frames. In order to be able to carry out its task, the M-MGw will have to
extract the payload from the frames on incoming bearer, carry out the media
stream processing (e.g. speech coding or echo cancellation), and then pack
the resulting payload on frames needed on the outgoing bearer.
The Media Stream Handling functionality is implemented as pooled devices
that can be configured to support any of the individual functions listed
below. With the help of this unique M-MGw capability, the operator can
maximize the use of scarce network resources, such as echo cancellers.
The fundamental Media Stream Handling functions are:
• Speech Coder including AMR2 (the default speech coding/decoding
Algorithm for WCDMA. All modes of the AMR2 speech codec are
supported)
• Echo Canceller
• Multi-Party Call
• Tone Sender
• DTMF Sender/Receiver
• Interactive Messaging
• The Code Answer and Tone Sender (CAT), used for maintenance purposes
• Continuity Check (CC), used to test the integrity of the speech path
Four Voice Quality Enhancement functions are also available:
• Mobile Crosstalk Control (MCC) that cancels acoustic echo generated at
MS side
• Noise Reduction feature, effectively reduces background noise when
calling from noisy environments.
Signaling Gateway Function
The Signaling Gateway functionality enables seamless communication
between TDM, ATM and IP based signaling networks. The Signaling
Gateway functionality makes it possible to perform signaling bearer
conversion (MTP3B/SAAL-NNI, MTP3/MTP2 and M3UA/SCTP) in the M-
MGw at the network edges, thus allowing unified signaling bearers to be
used within the core network.
The Signaling Gateway can, for instance, relay control signaling to the MSC
Server and between MSC Servers by performing conversion of lower layer
control protocols.
MTP Level Signaling Transfer Point (STP) and SCCP Relay Point (SRP)
functionality is included in the SS7 Signaling Gateway.
Radio Access Network Interfaces the WCDMA Radio Access Network is
connected to the M-MGw over IU interface that defines the payload framing
used in the communication towards the WCDMA Radio Network
Controllers.
M-MGw supports also the physical connection between two Radio Network
Controllers (Iur interface).
Introducing the GSM A-interface gives the possibility to interface 2G BSS
directly via the M-MGw. The physical HW related to the A-interface TDM
devices is located in the M-MGw, but the MSC Server controls the call using
the GCP protocol.
All required signalling is relayed through the Signalling Gateway
functionality in the M-MGw to the MSC Server.
 CPP – Hardware

The CPP (Cello) architecture provides a robust platform with multi

processor architecture and full availability, and is optimized for products
developed for the 3G mobile networks. It is a base for development of real-
time IP routing and ATM switching functions, enabling the merging of
mobility, data communications and telecom.

Cello Subtract
CPP boards

SCB
Switch Core Board (SCB) that contains an ATM switch core, circuits for
Distribution of system clock, and interfaces for connection of four Inter
Subtract Links (ISL).

TU Board
Network synchronization a Timing Unit (TU) must be used per Cello
Node. The TUs have dedicated positions in the CPP subrack (slot 4 and 5).

MSB
Media Stream Board (MSB), which holds the media stream, functions
Such as speech coders and echo cancellers. The MSB also contains IP
Termination functionality.
GPB
General Purpose Board (GPB) that contains a flash disk, and can be
Configured to function as a Main processor for the MGw.
SXB
Switch Extension Board (SXB) that can be used for expansion of the
Media Gateway. The board includes four Inter Subrack Links (ISL) with
The same characteristics as the ISL links on Switch Core Board.

TE
Exchange Terminal boards (ET) that provide interfaces for traffic over
Various types of transmission lines. The Exchange Terminal boards are
Designed with a modular hardware structure. ET-M4, ET-MC41 and ETMC1
are the versions of Exchange Terminal which are supported in MGW

CPP Switch hardware overview

 ATM Transport Service
The ATM Transport service handles setups and releases of point-to-point ondemand
ATM Adaptation Layer (AAL) connections.

AAL0
The AAL0 Layer contains connection end-point (CEP) functionality for permanent
and dynamic AAL0 connections.
• Dynamic AAL0 connections are established by an application program
between two CEPs residing in the same Cello node. Node external
dynamic connections are not supported.
• Permanent AAL0 connections are established by an operator via
management operations between CEPs residing in different Cello
nodes. Node internal permanent connections are not supported.
AAL0 connection end-points are provided on Main Processors (MP), Board
Processors (BP) and Special purpose Processors (SP).

AAL2
AAL2 is used for node internal and network wide connections, for payload.
AAL2 is divided into a common part sublayer (CPS) and a service specific
Convergence sub-layer (SSCS).

AAL5
AAL5 is used for transfer of variable size data packets to a remote peer, for
signalling. AAL5 is divided into a common part (CP) which is the same for
All AALs of type 5 and a service specific part which is unique for each AAL5
Service.