UMG 8900

Operation and Maintenance

CONTENTS
1. R4 Networking
2. Basic Hardware Architecture
3. Operation and Maintenance

R4 NETWORKING

In mobile network, UMG8900 provides voice service and data transmission to realize service
flow transmission from radio access network Circuit Switched (CS) domain of wireless network
to such networks as: public packet switch network (such as PSTN, ISDN) and other mobile
networks (such as GSM, CDMA)

HARDWARE BASICS:
SHELF AND FRAME

HARDWARE BASICS:

FRAME CLASSIFICATION

The main control frame: Manages and controls the whole UMG8900
equipment and provides clock signals for other frames.

The central switching frame: Implements frame subtending function.

The service frame : Implements service processing and interfacing

functions.

The extended control frame: It is configured when the networking with

large capacity is required. It is responsible for protocol processing and
connection management, and implements controlling and managing the
service frames

FRAME CONFIGURATION

DEFAULT SLOT CONFIGURATION

DEFAULT SLOT CONFIGURATION

Service board

Service board

Service board

Service board
Service board

Service board

Service board
Service board
Service board

Service board

Service board

Service board

distribution
s slot

Back board

T
N
U
N
E
T
N
E
T
T
N
U

0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

HARDWARE MAINTENANCE
Board Function
Part 1
2.1 Operation and Maintenance Subsystem
2.2 Gateway Control Subsystem.
Part 2
2.3 Packet Service Processing Subsystem
2.4 TDM Service Processing Subsystem
2.5 Service Resource Subsystem
2.6 Signaling Forwarding Subsystem
2.7 Clock Subsystem

HARDWARE MAINTENANCE
OPERATION AND MAINTENANCE SUBSYSTEM

As the management and control center of the

whole equipment, the master and slave
MOMUs are inserted in front slots 7 and 8 in
the main control frame.
Providing packet switching function at the
control plane to communicate with all the
boards with FE control interfaces and to
exchange information with other frames and
manage interfaces in the multi-frame
cascading case.
Embedding a BAM, which provides MML and
Telnet interfaces to configure and maintain
boards, and saves log files and alarm

MOMU

RUN
A LM
A CT

R ESET

C O FM E 00

OMU BOARD (MOMU)

OFFLINE

H UAWEI

HARDWARE MAINTENANCE
OPERATION AND MAINTENANCE SUBSYSTEM (CONT.)

Other frame

MPU
(Master)
board
OMU
(Master)

board

MPU
(Slave)

board
board
board
board

board
OMU
(Slave)

board

Main control frame

MPU
(Slave)
MPU
(Master)
Board

board
board
board
board
Other frame

Monitoring and managing the states

of all boards in the equipment. When
multiple frames are cascaded, the
MOMU monitors and manages MMPUs
in other frames through cascaded
control planes.
Implementing state monitoring and
power-on/off management on the
equipment through special MBus
modules; avoiding attack from instant
currents by controlling board power-

HARDWARE MAINTENANCE
OPERATION AND MAINTENANCE SUBSYSTEM (CONT.)

Implementing control information interaction

between the boards and inter-frame control
information interaction as well as interface
management in the case of multiple frames
subtended.
Monitoring and managing the status of all
boards in the frame.
Implementing status querying, monitoring
and power-on or power-off management to
the equipment through special maintenance
module, and controlling board power-on
sequence to avoid impact from instant
current.

RUN
A LM
A CT

R ESET

C O FM E0 0

MPU BOARD (MMPU)

MMPU

OFFLINE

HUAWEI

HARDWARE MAINTENANCE
GATEWAY CONTROL SUBSYSTEM
MGC(MSOFTX3000)
H.248(FE)

PPU
FE-Switch

CMU

OMU/MPU

Gateway Control
Subsystem

HARDWARE MAINTENANCE
GATEWAY CONTROL SUBSYSTEM (CONT.)

PPU BOARD(MPPB)

MPPB

RUN
A LM

R ESET

RANAP
SCCP

COM0

H.248

FE0

Sending manipulation results to

the MGC in the form of H.248
messages.
Implementing H.248
transcoding, and resolving
transport-layer and networklayer protocols

OFFLINE

SCTP/UDP
IP
Stack for Mc interface

M3UA
SCTP
IP
Stack for SG function

HUAWEI

OPERATION AND MAINTENANCE

CONFIGURATION

UMG8900 Mc Interface Configuration

UMG8900 MC INTERFACE CONFIGURATION

Mc interface is a new interface determined in 3GPP R4, which is a
standard interface between MSC Server (or GMSC Server) and MGW.
The Mc interface provides the capabilities of the static and dynamic
resources for the MSC Server (GMSC Server) controlling the various
transmission modes (IP/ATM/TDM) in the MGW in the call processing
procedure, such as terminal property, terminal connection switching
relationship, MGW borne media streams.
The Mc interface also provides the call independent MGW status
maintenance and management capability.

UMG8900 MC INTERFACE CONFIGURATION

The Mc interface is used to
transmit data between the
following NEs:
MSC server and MGW
GMSC server and GMGW
The Mc interface complies with
the H.248 protocol. Figure 2
shows its protocol stack when
the Mc interface is used in the IP
network.

SCTP Stream Control Transmission

Protocol
In computer networking, the Stream Control
Transmission Protocol (SCTP) is a transport-layer
protocol, serving in a similar role to the popular protocols
TCP and UDP. It is standardized by IETF in RFC 4960. It is
a transport protocol for call signaling, created to
overcome several lacks and problems of TCP when used
for signaling between telephony nodes.
Typically, SCTP uses IP as its underlying protocol. The
assigned protocol number for SCTP on IP is 132.

Features of SCTP
Multihoming support in which one or both endpoints of a
connection can consist of more than one IP address,
enabling transparent fail-over between redundant
network paths.
Delivery of chunks within independent streams eliminate
unnecessary head-of-line blocking, as opposed to TCP
byte-stream delivery.
Acked error-free non duplicated user data transfer
Data fragmentation conforming to discovered path MTU
(max transmission unit)

Features of SCTP (Cont.)

Sequenced delivery of user messages within each
stream (but
have multiple streams)
Option for out-of-order delivery of a user message
Bundling of multiple user messages into a single SCTP
packet
Fault-tolerance (at network level) by supporting multihoming at
either/both ends of an association.
Heart-beat/keep alive messages
Message boundaries preserved
SACK

Need for SCTP

Head of line blocking in TCP; not good in many situations
Applications must add their own record making;
TCP vulnerable to Denial of Service attacks
Main motivator:
Carrying SS7 signalling on IP Networks

Media Gateway Control Protocol

(MEGACO/H.248)
MEGACO/H.248 is used to control Media Gateways in a
Multimedia systems. MEGACO can be Text or Binary
(ASN.1) encoded. Sometimes it's also referred as GCP
(Gateway Control Protocol).
A MediaGateway (MGW) as its name says is a system
used as a Gateway for Media. Current uses are in
telephony (Internet, Mobile and Wireline) and Video and
Narrowcasting. A MediaGateway is usually placed at the
edge of two or more different Transport Mediums (like:
ATM (AAL1,AAL2,AAL5), IP, TDM, even two wire PSTN)
and its main duty is to convert media (voice/video)
between these domains. MediaGateways are often
capable of playing and listening to DTMFs, playing tones

MC INTERFACE TROUBLESHOOTING SCENARIOS

Major scenarios of interaction between the MSC server and the MGW are as
follows:
The MSC server notifies the MGW to allocate the bearer resource.
The MSC server notifies the MGW to modify the attributes of the bearer
resource.
The MSC server notifies the MGW to release the bearer resource.
The MGW notifies the MSC server of the status change of the MGW.
5. The MGW notifies the MSC server of the occurrence of the bearerspecific events.

MC INTERFACE TROUBLESHOOTING SCENARIOS

The H.248 protocol can be
carried over either IP or
ATM.
The IP networking mode is
generally used. Figure 1
depicts the protocol stack
of the H.248 protocol
carried over IP. Figure 2
depicts the protocol stack
of the H.248 protocol
carried over ATM.

Figure 1

Figure 2

MC INTERFACE TROUBLESHOOTING SCENARIOS

The H.248 messages are encoded in
a binary format or in a text format.
When the binary format is used, the
H.248 messages comply with the
ASN.1 specification. When the text
format is used, the H.248 messages
comply with the ABNF specification.
For a specific context between the
MGW and the MSC server, one or
more commands constitute an action;
one or more actions constitute a
transaction; one or more transactions
constitute an H.248 message. Figure
shows the hierarchical structure of
the H.248 message.

H.248 TRANSACTIONS
For an H.248 message, actions
in a transaction must be
executed in sequence. If
execution of a command
(except commands that are
marked as "optional") in an
action fails, execution of the
subsequent commands in this
action is stopped. Execution
failure of an optional command
does not affect execution of its
subsequent commands.

H.248 MESSAGE LIST TROUBLESHOOTING

The structure of the H.248

message indicates that
the H.248 messages can
be distinguished by
commands.. Table
describes the five pairs of
common messages.

Message
ServiceChange

Direction
MSC -> MGW
MGW -> MSC

ServiceChange
Reply
ADD REQ

MSC -> MGW

MGW -> MSC
MSC -> MGW

ADD REPLY

MGW -> MSC

NTFY REQ

MGW -> MSC

NTFY REPLY

MSC -> MGW

MOD REQ

MSC -> MGW

MOD REPLY

MGW -> MSC

SUB REQ

MSC -> MGW

SUB REPLY

MGW -> MSC

Function
The MSC server requests the MGW to change the
service status of a termination or a group of
terminations.
The MGW notifies the MSC server that the service
status of a termination or a group of terminations is
changed.
The MSC server or the MGW responds to the
ServiceChange message sent by the peer side.
The MSC server requests the MGW to add a specified
termination to the specified context.
The MGW returns the result of adding the termination
to the MSC server.
The MGW requests the MSC server of the occurrence
of the termination event.
The MSC server acknowledges the reception of the
NTFY REQ message sent by the MGW.
The MSC server requests the MGW to modify the
attributes of a specified termination.
The MGW returns the result of modifying the
attributes of a termination to the MSC server.
The MSC server requests the MGW to remove a
specified termination from a specified context.
The MGW returns the result of moving a termination
to the MSC server.

H.248 MESSAGE LIST TROUBLESHOOTING

IE

Description

version

Indicates the version of the H.248 protocol used by the

message sender.

version: indicates the version of the H.248 protocol.

In this example, the version of the H.248 protocol used by
the message sender is 1.

enMID

Indicates the message sender in the network.

MID: indicates the identifier of the message sender in the

network.
In this example, the message is sent from