1-AoIP Networking and Principle ISSUE1.00

AoIP Networking and
Principle
www.huawei.com
Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

References
MSOFTX3000 product manual
UMG8900 product manual
Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved. Page1
Objectives
Upon completion of this course, you will be able to:
Outline the Modifications from AoTDM to AoIP
Describe the function of each network element on AoIP
Describe AoIP codec selecting policy
Describe the signaling flow difference between AoIP and AoTDM
Describe the principle of QoS and IP domain on AoIP
Contents
1. AoIP Overview
2. AoIP Principle
Contents
1. AoIP Overview
2. AoIP Principle
Contents
1. AoIP Overview
1.1 Background
1.2 Networking
1.3 Modification from AoTDM to AoIP
Background
A interface over IP (AoIP) plays a significant role in simplifying
and evolving the network. It enables the network to evolve into
an all-IP network on the basis of the IP-based core network
(CN).
AoIP brings the following benefits to carriers:

Reducing the TC and transmission resources
Maximizing the resource utilization rate
Enabling flexible and reliable networking
Improving the Quality of Service (QoS)
Contents
1. AoIP Overview
1.1 Background
1.2 Networking
AoTDM
The TDM signaling is transferred on both the signaling plane and the user
plane of the A interface.
The MGW functions as the Signaling Gateway (SG) for the A-interface
signaling, converts the TDM signaling into the IP signaling, and sends the IP
signaling to the MSC server for further processing.
AoIP
IP is used to transfer the speech codecs. The protocol stack RTP/UDP/IP is

adopted on the bearer plane over the A interface. If the compressed speech
codec is used over the A interface, the transcoder, which is originally located on
the BSC, is moved to the CN. In this case, the BSC does not provide the
transcoder function. If the G.711 codec is used over the A interface, the original
transcoder resource on the BSC can be used.
The AoIP Benefits:
End-to-end Transcoder Free Operation (TrFO) is implemented for 2G calls. --
Same to 3G.
Transmission resources are saved.

The IP network adopts the statistical multiplexing technology. The bandwidth is
allocated according to the requirements but not subject to limitations such as the
granularity limitation of the TDM network.
When a compressed codec is transmitted, AoIP can effectively reduce the

bandwidth usage and the CAPEX.
The maintenance cost is reduced.

When IP transformation of the CN, A interface and BSS is complete, all types of
networks to be maintained can be unified to a single type. This lowers the
requirements on the technical capability of maintenance and reduces the OPEX.
The AoIP benefits: - continue
With the AoIP, BSCs can provide the A-Flex function, which enables flexible
networking of the MSC Pool.
MGWs can be selected flexibly, which further reduces the CAPEX.
After AoIP, the MSC server can use the advantage of the fully-meshed IP network to select the
optimum MGW for access. This increases the capacity of MGWs from the network perspective.
For example, if a call should be routed through a remote MGW, the remote MGW can be directly
selected as a termination over the A interface. This process does not involve the local MGW.
Contents
1. AoIP Overview
1.1 Background
1.2 Networking
Interface Modification
AoIP is developed by modifying the AoTDM in the following
aspects:
The IP bearer is supported on the bearer plane. The signaling plane
transfers the IP address of the bearer plane.
Codecs are modified and negotiated between the terminals, BSCs,

and MSCs on the signaling plane.
Transferring the IP address of the
bearer plane
BSS MSC MGW
Complete Layer3
Add.Req
MGW allocates local IP

resource: ip1, port1
Assignmment Requst
(ip1, port1) Add.Reply(ip1, port1)
BSC allocates local IP

resource: ip2, port2
Assignmment Compelete
(ip2, port2)
Mod.Req(ip2, port2)
Mod.Reply
Bearer is available for traffic: (ip1,port1)<->(ip2,port2)
The IP bearer is supported on the bearer plane. The signaling

plane transfers the IP address of the bearer plane.
Negotiating and modifying the codecs
Codecs are modified

and negotiated
between the terminals,
BSCs, and MSCs on
the signaling plane
Functions of NEs Related to AoIP
NE Function
MSC Server 1) Transfers the IP address and port number between the MGW and the BSC.
2) Transfers the SDP information (including the payload type, rate, clock rate,
and PTime) between the MGW and the BSC.
Identifies the bearers (IP or TDM) between the MGW and the BSC.
3) Supports the 2G codecs, including EFR, HR, FR, HR AMR, and FR AMR.
MGW 1) Allocates the IP addresses and ports at the core network side.
2) Prepares for establishment of the bearer capability as instructed by the
SDP information, including the payload type, rate, clock rate, and
packetization time (PTime).
BSC 1) Allocates the IP addresses and ports at the access network side.
2) Prepares for establishment of the bearer capability as instructed by the
SDP information, including the payload type, rate, clock rate, and packet
time (PTime).
Comparison Between AoIP and AoTDM
Difference AoTDM AoIP
Signaling plane: applying for the The MSC server sends a The MSC server sends a request to the
termination at the access side request to the MGW to MGW to apply for the IP termination
through the Mc interface apply for the TDM with the specified codec, IP address
termination. and port number.
Signaling plane: sending the The MSC server allocates The MSC server sends the codec, IP
Assignment Request message and sends the CIC to the address, and port number of the
through the interface at the BSC. termination allocated by the MGW to
access side the RNC.
Signaling plane: receiving the The BSC directly selects a The RNC allocates and sends IP + port
Assignment Complete message circuit based on the CIC. to the MSC server through the UP
through the interface at the Therefore, the BSC sends the initialization message (establishment of
access side Assignment Complete to the the user plane between the MGW and
MSC server, informing that the RNC is completed). The Assignment
assignment is complete. Complete message only informs that
assignment is complete.
User plane: transcoder on the BSC. on the MGW.
Question
From AoTDM to AoIP, what are the A Interface Modifications?
Which messages are modified?
Contents
1. AoIP Overview
2. AoIP Principle
Contents
2. AoIP Principle
2.1 Codec selection policy
2.2 AoIP Call Flow
2.3 QoS Control
2.4 IP Domain Control
Intra-MSC Calls Codec Selection
Intra-MSC calls refer to the calls that are controlled by a single MSC server. Under the
control of the MSC server, the TrFO is implemented whenever possible.
For calls between the 2G AoIP and the 2G AoIP, the same GSM codec is used through
negotiation whenever possible.
For calls between the 2G AoIP and the 2G TDM, the same GSM codec is used through
negotiation whenever possible.
For inter-MGW calls between the 2G TDM and the 2G TDM, the G.711 codec is used to reduce
the conversion or the GSM codec is used to save the bandwidth whenever possible.
For calls between 3G networks, the same AMR codec and rate are used through negotiation
whenever possible.
For calls between 2G and 3G networks, the TC must be inserted to convert between the GSM
codec and the AMR codec.
Inter-MSC ISUP Calls Codec Selection
The TrFO cannot be implemented for inter-MSC ISUP calls.
These calls are processed in the same way as the intra-MSC
calls between the 2G TDM and the 2G TDM.
Inter-MSC TrFO Calls Codec Selection
Scenario MO Call MT Call Use GSM Codec Selection Policy
Flow Flow Codec for
Inter-MSC
Calls
1 2G AoIP 3G N The terminating MSC uses the AMR codec.
The AMR codec is used between MSCs.
The originating MSC uses the GSM codec and converts GSM/AMR.
Y The terminating MSC uses the GSM codec.
The GSM codec is used between MSCs.
2 2G AoIP 2G AoTDM N The terminating MSC uses the AMR codec and converts GSM/AMR.
Y The terminating MSC uses the GSM codec and converts GSM/AMR.
The originating MSC uses the GSM codec.
3 2G AoIP 2G N The terminating MSC uses the GSM codec and converts GSM/AMR.
AoIP The AMR codec is used between MSCs.
The originating MSC uses the GSM codec.
Inter-MSC TrFO Calls Codec Selection -
Continue
Scen MO Call MT Use GSM Codec Codec Selection Policy
ario Flow Call for Inter-MSC
Flow Calls
4 3G 2G AoIP N The terminating MSC uses the GSM codec and converts
GSM/AMR.
The originating MSC uses the AMR codec.
The originating MSC uses the AMR codec and converts
GSM/AMR.
5 2G AoTDM 2G AoIP N The terminating MSC uses the GSM codec and completes
GSM/AMR conversion.
The originating MSC uses the AMR codec and converts
GSM/AMR.
The originating MSC uses the GSM codec and converts
GSM/AMR.
6 3G 3G N The terminating MSC uses the AMR codec.
The originating MSC uses the AMR codec.
Inter-MSC TrFO Calls Codec Selection-
Continue
On the basis of the existing IP-based Nb interface, after the GSM codecs are
used between MSCs, introduction of the AoIP to the 2G MSCs can reduce the
number of times that the codec is converted.
For example, the number of codec conversion attempts is smaller in scenarios 2, 3,
and 5. (Using too many GSM codecs is not a good idea, because this will
complicate the negotiation process. It is recommended that only the GSM FR codec
be used.)
If the new 2G AoIP MSC interworks with a 3G MSC, the 3G MSC

requires more codec conversion resources, as described in scenario 4.
If the GSM codecs are not used between MSCs, the existing 3G MSCs
are not affected.
In MSC Server, the BSC codec configuration
The codec is configured by ADD BSC. And it should be consistent with the codec
supported by BSC. Otherwise, calls maybe fail because of codec negotiating failure or
negotiating error.
In MSC Server, the MGW codec configuration
The codec is configured by ADD MGW. And it should be consistent with the
codec supported by MGW. Otherwise, calls maybe fail because of codec
processing failure.
In MGW, the codec configuration
The codec is configured by SET CODECCAP.
Question
About the inter-MSC TrFO Calls Codec Selection: If MO is 3G
and MT is 2G AoIP,
when the codec used for inter-MSC calls is GSM codec, what is the
codec selection policy for MO MSC and MT MSC?
When the codec used for inter-MSC calls is not GSM codec, what
is the codec selection policy for MO MSC and MT MSC?
Contents
2. AoIP Principle
2.2 AoIP Call Flow

2.3 QoS Control
MO Call Flow
CM SERVICE REQUEST
The BSS sends a CM SERVICE REQUEST message
to the MSC. This message contains the speech
codec supported by the BSS.
Structure of Speech Codec List
Structure of Speech Codec Element
Setup
The BSC sends a Setup message to
the MSC. This message contains
the speech codec supported by the
MS. The IE gsm-bearer-capability in
the Setup message contains the
speech versions supported by the
MS. The MSC server converts the
speech version into the codec
based on the related protocol.
Add Req
The MSC server sends an Add Req message to the MGW to create an IP termination. Contains :
Codec list used for the call
Parameters of each codec, such as PayloadType, PTime, and ClockRate
Rate indicators such as ACS/SCS if the multi-rate codec (such as 2G AMR) is used
AMR codec description

ip-interface-type
Add reply
The MGW sends the allocated IP address,
PayloadType, PTime, and ClockRate to the
MSC server through the Add Reply message.
The MSC server then forwards the
information to the BSC.
Assignment Request
The MSC server sends an Assignment Request message to the BSC. Contains：
IP address, Call Identifier and Codec
Transport Layer Address
Speech Codec List

(MSC Preferred)
Call Identifier
Assignment Complete
On receiving the Assignment Request message, the BSC selects a codec and allocates the IP address
and port number used on the user plane. The BSC then sends an Assignment Complete message
that contains the codec selected by the BSS and the codec list supported by the BSS.
Mod Req
The MSC server sends a Mod Req
message to the MGW. This message
contains the IP address and port
number of the BSC. If the MSC server
requires modification of the codec type
on the MGW, this message also
contains the corresponding codec,
Payloadtype, PTime, ClockRate, and
ACS.
Inter-BSC Handover
During handover, the modification of messages between the MSC Server and
MGW is similar to the messages of basic calls. The modification of Handover
Request、Handover Request ack are similar to Assignment Request and
Assignment Complete.
Source BSC MSC Server MGW Target BSC
Handover Required
Add Req
Add Reply
Handover Request
Handover Request Ack
Mod Req
Mod Reply
Handover Command
Handover Complete
Sub Req
Sub Reply
Handover Required
The source BSC sends a
Handover Required message to
the MSC server. Contains :
the list of target cells to which
the MS can be handed over
handover reason
speech codec supported by

the MS.
Handover Request
On receiving the Add Reply message,
the MSC server sends a Handover
Request message to the selected
target BSC.
The Handover Request message

contains AoIP Transport Layer Address
(MGW), Speech Codec List (MSC
Preferred), and Call Identifier allocated
by the MSC for the current handover.
Handover Request Ack
On receiving the Handover Request message, the target
BSC selects a speech codec, assigns the IP address and
port number used on the user plane, and then sends
AoIP Transport Layer Address and Speech Codec (BSS
chosen) through the Handover Request Ack message to
the MSC server.
The MSC server sends a Mod Req message to the

MGW.
This message contains the IP address and port number of
the BSC.
If the MSC server requires modification of the codec type

on the MGW, this message also contains the
corresponding codec.
Intra-BSC Handover
Intra-BSC handover is a new process after AoIP. The Voice quality of the
whole network will be improved after frequently handover.
Internal Handover Required
When the BSC needs to change the
codec and the codec used before and
after the handover are not compatible
with each other, the BSC sends an
Internal Handover Required message to
the MSC server.
This message contains the IP address and
port number of the target termination
and the codec information to be changed.
Add Req
The MSC server sends an Add Req
message to the MGW. In this
message, localDescriptor contains
the new codec information, and
remoteDescriptor contains the IP
address of the latest IP termination
established by the BSC.
The MGW prepares the resource for

establishing the A interface and
records the information about the
IP termination at the access side.
Add Reply
The MGW establishes a termination based
on the new codec information and sends
the IP address assigned by the MGW and
the codec information through the Add
Reply message to the MSC server.
Internal Handover Command
On receiving the Add Reply message from
the MGW, the MSC server sends an
Internal Handover Command message to
the BSS, informing the BSS of the IP
address and codec information of the new
termination.
The Internal Handover Command message

contains Speech-codec-msc-chosen
(indicating the codec selected by the MSC
server) and aoip-transportlayer-address-
mgw (indicating the IP address of the new
termination of the MGW).
Contents
1. 2. AoIP Principle
2.2 AoIP Call Flow
2.3 QoS Control

Implementation Principle
After the AoIP is introduced, as the IP bearer network does not have
any circuit, the MSC server cannot know how many calls the bearer
network can handle. Therefore, virtual channels are added to ensure
the QoS.
The concept of the number of virtual channels is similar to that of the
number of circuits.
Only a limited number of virtual channels are available in a BSC office
direction.
When all virtual channels are occupied, the MSC server directly rejects the
calls.
Assume that the total bearer bandwidth in a BSC office direction is M,
and the average bandwidth occupied by a call is N. The number of
virtual channels is M/N.
The number of virtual channels
The number of virtual channels can be configured by MSC Server or
MGW, according to the switch parameter “MGW report IP bear
resources” in ADD BSC.
Configured by MSC Server
Run ADD RANMGW to configure the number of virtual channels on the MSC server. If
this method is used, the number of virtual channels is maintained on the MSC server.
The number of virtual channels is related to the BSC office direction.

Each time the MSC server accepts a call in a BSC office direction, the number of virtual channels
decreases by 1.
Each time the MSC server releases a call in a BSC office direction, the number of virtual
channels increases by 1.
Configured by MGW
Run ADD OFCBAND to configure the bandwidth in a BSC office
direction on the MGW. The number of virtual channels is maintained
on the MGW.
The MSC server determines whether any virtual channels are available
based on the number of virtual channels reported by the MGW.
The MSC server does not perform the addition or subtraction operation
on the number of virtual channels.
Add Req/Add Reply
When the MSC server sends an Add Req message for establishing a termination, the
message contains the DCP NI. Based on the DPC NI, the MGW learns the number of
virtual channels in the specified office direction and sends the number of virtual
channels through the Add Reply message to the MSC server.
Add Req Add Reply
Notify Req
The MGW also reports the numbers of
virtual channels in all BSC office directions
every 30 seconds through the Notify Req
message.
Based on the information, the MSC server

periodically updates the numbers of virtual
channels in all BSC office directions.
Question
How to configure the number of virtual channels by MSC
Server or MGW ?
Contents
2. AoIP Principle
2.2 AoIP Call Flow
2.3 QoS Control
Implementation Principle
After the AoIP is introduced, if the BSC and the core network do not use the same bearer network,
each BSC can be directly connected to the MGW to divide the IP bearer network where the A
interface is located from the IP bearer network of the core network.
the IP domain information must be transferred during the bearer-specific operations. When the BSC
office directions are configured on the MSC server, the MSC server must support the IP domain.
An IP domain is an independent IP address space. The same IP address can be allocated in different
IP domains. The IP network of the core network forms another IP domain.
The MGW is responsible for application layer forwarding between IP domains.
The IP Domain Selection
On establishing the AoIP termination, the MSC server sends a message to the
MGW, indicating the IP domain that should be used by the MGW. The MGW
then selects the bearer resource in the specified IP domain. Other part of the
flow is similar to the basic AoIP call flow.
In the scenario that the signaling must be forwarded by the MGW, the IP
address used for the signaling plane interworking between the MGW and the
BSC and the IP interface forwarded by the MGW to the MSC server must be
planned in the same IP domain at the MGW side.
The MSC server provides only four IP interfaces. Therefore, it is recommended that
the MSC server is connected to BSCs by using the same IP address.
Summary
The course mainly introduces：
the Modifications of networking from AoTDM to AoIP
the function of each network element on AoIP
AoIP codec selecting policy
the signaling flows difference between AoIP and AoTDM
the principle of QoS and IP domain on AoIP
Thank you
www.huawei.com

1-AoIP Networking and Principle ISSUE1.00

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1-AoIP Networking and Principle ISSUE1.00

Uploaded by

Copyright:

Available Formats

AoIP Networking and

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

UMG8900 product manual

Describe the function of each network element on AoIP

Describe AoIP codec selecting policy

Describe the signaling flow difference between AoIP and AoTDM

Describe the principle of QoS and IP domain on AoIP

1.3 Modification from AoTDM to AoIP

AoIP brings the following benefits to carriers:

Maximizing the resource utilization rate

Enabling flexible and reliable networking

Improving the Quality of Service (QoS)

1.3 Modification from AoTDM to AoIP

IP is used to transfer the speech codecs. The protocol stack RTP/UDP/IP is

Transmission resources are saved.

When a compressed codec is transmitted, AoIP can effectively reduce the

The maintenance cost is reduced.

MGWs can be selected flexibly, which further reduces the CAPEX.

1.3 Modification from AoTDM to AoIP

Codecs are modified and negotiated between the terminals, BSCs,

MGW allocates local IP

BSC allocates local IP

Bearer is available for traffic: (ip1,port1)<->(ip2,port2)

The IP bearer is supported on the bearer plane. The signaling

Codecs are modified

2.1 Codec selection policy

2.2 AoIP Call Flow

2.3 QoS Control

2.4 IP Domain Control

If the new 2G AoIP MSC interworks with a 3G MSC, the 3G MSC

The codec is configured by SET CODECCAP.

2.1 Codec selection policy

2.2 AoIP Call Flow

2.4 IP Domain Control

Structure of Speech Codec List

Structure of Speech Codec Element

Parameters of each codec, such as PayloadType, PTime, and ClockRate

AMR codec description

Transport Layer Address

Speech Codec List

Handover Request Ack

speech codec supported by

The Handover Request message

The MSC server sends a Mod Req message to the

If the MSC server requires modification of the codec type

The MGW prepares the resource for

The Internal Handover Command message

2.1 Codec selection policy

2.2 AoIP Call Flow

2.3 QoS Control

The number of virtual channels is related to the BSC office direction.

Based on the information, the MSC server

2.1 Codec selection policy

2.2 AoIP Call Flow

2.3 QoS Control

2.4 IP Domain Control

The MGW is responsible for application layer forwarding between IP domains.

the function of each network element on AoIP

AoIP codec selecting policy

the signaling flows difference between AoIP and AoTDM

the principle of QoS and IP domain on AoIP

You might also like