Livre AoIP PDF

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 AoIP codec selecting policy
Describe the signaling flow difference between AoIP and
AoTDM
Page2
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
Page5
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)
Page6
Contents
1. AoIP Overview
1.1 Background
1.2 Networking
Page7
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.
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.
Page10
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.
Page11
Contents
1. AoIP Overview
1.1 Background
1.2 Networking
Page12
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.
Page13
Transferring the IP address of the
bearer plane
BSS MSC MGW
Complete Layer3
Add.Req
Add.Reply(ip1, port1)
Assignmment Requst
(ip1, port1)
MGW allocates local IP
resource: ip1, port1
The IP bearer is supported on the bearer plane. The signaling
plane transfers the IP address of the bearer plane.
Assignmment Compelete
(ip2, port2)
Mod.Req(ip2, port2)
Mod.Reply
Bearer is available for traffic: (ip1,port1)<->(ip2,port2)
BSC allocates local IP
resource: ip2, port2
Negotiating and modifying the codecs
Codecs are modified
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).
Page16
Comparison Between AoIP and AoTDM
Difference
AoTDM AoIP
Signaling plane: applying for the
termination at the access side
through the Mc interface
The MSC server sends a
request to the MGW to
apply for the TDM
termination.
The MSC server sends a request to
the MGW to apply for the IP
termination with the specified
codec, IP address and port number.
Signaling plane: sending the
Assignment Request message
through the interface at the
access side
The MSC server allocates
and sends the CIC to the
BSC.
The MSC server sends the codec, IP
address, and port number of the
termination allocated by the MGW
to the BSC.
access side to the BSC.
Signaling plane: receiving the
Assignment Complete message
through the interface at the
access side
The BSC directly selects a
circuit based on the CIC.
Therefore, the BSC sends
the Assignment Complete
to the MSC server,
informing that
assignment is complete.
The BSC allocates and sends IP +
port to the MSC server through the
UP initialization message
(establishment of the user plane
between the MGW and the BSC is
completed). The Assignment
Complete message only informs
that assignment is complete.
User plane: transcoder on the BSC. on the MGW.
Page17
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.3 QoS Control
Page19
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
For calls between the 2G AoIP and the 2G TDM, the same GSM codec is used through
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
For calls between 2G and 3G networks, the TC must be inserted to convert between
the GSM codec and the AMR codec.
Page20
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.
TrFO in 2G-to-2G inter-MSC calls
If the A interface is IP-based and the BSC
and the MGW use the same codec or
compatible codecs, TrFO is started upon
successful codec negotiation
If the A interface is time division
multiplexing (TDM)-based, TrFO is started
between MGWs upon successful codec
negotiation
AoIP
AoTDM
Inter-MSC TrFO Calls Codec Selection
Scenario MO Call
Flow
MT Call
Flow
Use GSM
Codec for
Inter-MSC Calls
Codec Selection Policy
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 originating MSC uses the GSM codec.
The GSM codec is used between MSCs.
The terminating MSC uses the AMR codec and converts GSM/AMR.
2 2G AoIP 2G AoTDM N The terminating MSC uses the GSM codec and converts GSM/AMR.
Y The terminating MSC uses the GSM
The originating MSC uses the GSM codec.
3 2G AoIP 2G
AoIP
N The terminating MSC uses the GSM codec and converts GSM/AMR.
Y The terminating MSC uses the GSM codec.
Inter-MSC TrFO Calls Codec Selection -
Continue
Scen
ario
MO Call
Flow
MT
Call
Flow
Use GSM Codec
for Inter-MSC
Calls
Codec Selection Policy
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.
GSM/AMR.
6 3G 3G N The terminating MSC uses the AMR codec.
The originating MSC uses the AMR codec.
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.
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 MSC Server, the MGW codec configuration
The codec is configured by SET CODECCAP.
In MGW, the codec configuration
Contents
2. AoIP Principle
2.2 AoIP Call Flow
2.3 QoS Control
2.3 QoS Control
Page28
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
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.
Page31
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
ip-interface-type
AMR codec description
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.
BSC.
Page33
Assignment Request
The MSC server sends an Assignment Request message to the BSC.
ContainsIP address, Call Identifier and Codec
Transport Layer Address
Call Identifier
Speech Codec List
(MSC Preferred)
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
the codec type on the MGW, this
message also contains the
corresponding codec, Payloadtype,
PTime, ClockRate, and ACS.
Page36
Contents
1. 2. AoIP Principle
2.2 AoIP Call Flow
2.3 QoS Control
2.3 QoS Control
Page37
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.
Page38
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.
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.
Page40
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
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.
Page41
Add Req/Add Reply
When the MSC server sends an Add Req message for establishing a
termination, the message contains the DPC 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.
Page43
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
AoIP codec selecting policy
the signaling flows difference between AoIP and AoTDM
the principle of QoS on AoIP
Page44
Thank you
www.huawei.com www.huawei.com
AoIP Data Configuration
www.huawei.com
References
MSOFTX3000 V100R008C03 Product Documentation
UMG8900 V200R008C03 Product Documentation
Objectives
Configure AoIP data on MSC Server and MGW
Contents
1. Data Configuration for Direct Connection Mode between
MSC Server and BSC
2. Data Configuration for MGW Connection Mode between
MSC Server and BSC (M3UA Forward)
Contents
1. Data Configuration for Direct Connection Mode
between MSC Server and BSC
1.1 Scenario
1.2 Data Configuration on MSC Server
1.3 Data Configuration on MGW
1.4 Maintenance Commands
Page50
Networking in Direct Connection Mode
MSC Server
161.66.1.32
BSC
161.66.1.166
0X2132
Signaling plane
User plane
IP
AS/AS/IPSP
MGW
161.66.1.247
0X2149
IP
IPSP
Contents
1.1 Scenario
Page52
Configure Procedure
Configure M3UA Data
Configure SCCP Data
Start
Configure Service Data
End
M3UA Configuration Commands
M3UA
SCCP
BSSAP
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 54
SCTP
MAC
PHY
IP
Add M3UA Local Entity
Set the SPC of the MSC server to 0x2132 , the network
indicator to National reserved network and local entity
type to
ADD M3LE: LENM="MSX2-B", NI=NATB, OPC="002132",
LET=AS;
Page55
Add M3UA Destination Entity
Set the SPC of the BSC to 0x2149 and destination entity
type to AS
ADD M3DE: DENM="BSC49", LENM="MSX2-B", NI=NATB,
DPC="2149", DET=AS;
ADD M3UA Linkset
Set traffic mode to loadshare and work mode to IPSP
ADD M3LKS: LSNM="BSC49", ADNM="BSC49", WM=IPSP;
Add M3UA Route
ADD M3RT: RTNM="BSC49", DENM="BSC49",
LSNM="BSC49";
Add M3UA Link
The BSG module number is 137, the IP address of the
MSC server is 161.66.1.32, and the IP address of the BSC
is 161.66.1.166, the Client/Server mode is Client side
ADD M3LNK: MN=137, LNKNM="BSC49", LOCIP1="161.66.1.32",
LOCPORT=2048, PEERIP1="161.66.1.166", PEERPORT=2048, CS=C,
LOCPORT=2048, PEERIP1="161.66.1.166", PEERPORT=2048, CS=C,
LSNM="BSC49", QUALITYCHECK=TRUE, QoS=TOS;
Page59
SCCP Configuration Commands
M3UA
SCCP
BSSAP
SCTP
MAC
PHY
IP
Add SCCP Destination Signaling
Point
Set Network indicator to National reserved network and
DPC to the 2149 of the BSC
ADD SCCPDSP: DPNM="BSC49", NI=NATB, DPC="2149",
OPC="2132";
Add BSSAP SCCP Sub-system
Number
ADD SCCPSSN: SSNNM="BSC49", NI=NATB, SSN=BSSAP,
SPC="2149", OPC="2132";
Service Configuration Commands
M3UA
SCCP
BSSAP
M3UA
SCTP
MAC
PHY
IP
ADD BSC Office
Set Peer office type to BSC, Peer office level to LOW,
Network indicator to National reserved network and DPC1
to the 2149 of the BSC.
ADD OFC: ON="BSC49", OOFFICT=BSC, DOL=LOW,
DOA=BSC, BOFCNO=49, OFCTYPE=COM,
DOA=BSC, BOFCNO=49, OFCTYPE=COM,
SIG=NONBICC/NONSIP, NI=NATB, DPC1="2149", SVQE=NO;
Page64
Add Radio Access Network Media
Gateway
ADD RANMGW: OFFICENAME="BSC49",
MGWNAME="MGW3";
Add BSC
Add an BSC that interworks with the MGW through IP
(for the 3GPP AoIP specification).
ADD BSC: DPC="2149", OPC="2132", BSCNM="BSC49",
MLAIF=YES, BSCBEARERTYPE=IPSTD;
Add a 2G location area
The local MSC number is 861310751202 and the call source
name is CM_MSX1
ADD LAIGCI: GCI="460490049", MSCVLRTYPE=MSCVLRNUM,
MSCN="861310751202", VLRN="861310751202", NONBCLAI=NO, LAICAT=LAI,
LAIT=HVLR, LOCNONAME="INVALID", BSCDPC1="2149", CSNAME="CM_MSX1",
TONENAME="INVALID", CELLGROUPNAME="INVALID", TZDSTNAME="INVALID",
LOCATIONIDNAME="INVALID", E911PHASE=INVALID;
Page67
Add a 2G cell
the local MSC number is 861310751202 and the call
source name is CM_MSX1.
ADD LAIGCI: GCI="4604900490001", MSCVLRTYPE=MSCVLRNUM,
MSCN="861310751202", VLRN="861310751202", NONBCLAI=NO, LAICAT=GCI,
LAIT=HVLR, LOCNONAME="INVALID", BSCDPC1="2149", CSNAME="CM_MSX1",
LOCATIONIDNAME="INVALID", E911PHASE=INVALID;
Page68
Contents
1.1 Scenario
Page69
Modify the bandwidth of the HRU
connected to the A interface
MOD IPIF: IFT=ETH, BT=HRB, BN=1, IFN=0, BEARBW=51200;
Set the IP address of the HRU
ADD IPADDR: BT=HRB, BN=1, IFT=ETH, IFN=0,
IPADDR="161.66.1.247", MASK="255.255.255.0",
FLAG=MASTER, INVLAN=NO, IFMPLS=NO;
Set the gateway IP address of the
HRU
ADD GWADDR: BT=HRB, BN=1, IPADDR="161.66.1.247",
GWIP="161.66.1.1", TIMEOUT=NoAging;
Contents
1.1 Scenario
Page73
Maintenance Commands on MSC
Server
Commands of querying the SPC, link status, and SSP
status of BSC:
DSP M3DE Display M3UA Destination Entity Status
DSP M3RT Display M3UA Route Status
DSP M3LNK Display M3UA Link Status
DSP SCCPDSP Display SCCP Destination Signaling Point
Status
DSP SCCPSSN Display SCCP Sub-system Status
Contents
1. Data Configuration for Direct Connection Mode between
MSC Server and BSC
MSC Server and BSC (M3UA Forward)
Contents
MSC Server and BSC(M3UA Forward)
2.1 Scenario
Page76
M3UA Forward Mode of MGW
Connection Mode(Pool)
MSC Server
171.40.200.40
0XA01
AS/SG/ASP
BSC
171.40.200.33
MGW
171.40.200.51
0XC01
0XD01
0XD02
SG/AS/SGP
SG/SP/IPSP
IPSP
Contents
2.1 Scenario
Page78
Configure Procedure
Configure M3UA Data
to MGW
Configure M3UA Data
to BSC
Start
Configure SCCP Data
to BSC
Configure Service Data
End
Data Configuration on MSC Server
Configure M3UA Data to MGW
ADD M3LE: LENM="MSX1_NATB", NI=NATB, OPC="a01", LET=AS;
ADD M3DE: DENM="UMG1", LENM="MSX1_NATB", NI=NATB, DPC="d01",
STPF=TRUE, DET=SG;
ADD M3LKS: LSNM="TO_UMG1", ADNM="UMG1", WM=ASP;
ADD M3RT: RTNM="TO_UMG1", DENM="UMG1", LSNM="TO_UMG1";
ADD M3RT: RTNM="TO_UMG1", DENM="UMG1", LSNM="TO_UMG1";
ADD M3LNK: LNKNM="TO_UMG1", LOCIP1="171.40.200.40", LOCPORT=2903,
PEERIP1="171.40.200.51", PEERPORT=2903, CS=C, LSNM="TO_UMG1", QoS=TOS;
Page80
Data Configuration on MSC Server
Configure M3UA Data to BSC
ADD M3DE: DENM="BSC1", LENM="MSX1_NATB", NI=NATB, DPC="c01", DET=SP;
ADD M3RT: RTNM="TO_BSC1", DENM="BSC1", LSNM="TO_UMG1";
Configure SCCP Data to BSC
ADD SCCPDSP: DPNM="BSC1", NI=NATB, DPC="c01", OPC="a01";
ADD SCCPSSN: SSNNM="MSX1_BSC1_BSSAP", NI=NATB, SSN=BSSAP, SPC="c01", OPC="a01";
Configure BSC Office
ADD OFC: ON="BSC1", OOFFICT=BSC, DOL=LOW, DOA=BSC, BOFCNO=1, OFCTYPE=COM,
SIG=NONBICC/NONSIP, NI=NATB, DPC1="c01", SVQE=NO;
ADD BSC: DPC="c01", OPC="a01", BSCNM="BSC1", CAPABILITY=MGWPROXYAFLEX-1, MLAIF=YES,
BSCBEARERTYPE=IPSTD;
Page81
Contents
2.1 Scenario
Page82
Configure Procedure
Configure Local Entity
Configure M3UA Data
to MSC Server
Start
to MSC Server
Configure Pool Data
Configure M3UA Data
to BSC
End
Add M3UA Local Entity
Add two M3UA local entities, one for interworking with
MSC server and the other for interworking with the BSC
ADD M3LE: LEX=1, LET=SG, NI=NATB, OPC=H'd01;
ADD M3LE: LEX=2, LET=SG, NI=NATB, OPC=H'd02;
Add M3UA Destination Entity to MSC
Server
Add M3UA destination entity 1 (which is H'a01, interworking with
H'd01)
ADD M3DE: DEX=1, DEN="MSC1_1", DET=AS, NI=NATB, DPC=H'a01, LEX=1, NETTYPE=MSCPOOL;
If the MGW connection mode is adopted, add the M3UA destination
entity 2 (H'a01) mapping M3UA local entity 2 (H'd02, interworking
with the BSC).
ADD M3DE: DEX=2, DEN="MSC1_2", DET=AS, NI=NATB, DPC=H'a01, LEX=2,
NETTYPE=MSCPOOL;
Page85
Add an M3UA link set to MSC Server
ADD M3LKS: LSX=1, LSN="MSC1", ADX=1,
TM=LOADSHARE;
Add an M3UA route to MSC Server
ADD M3RT: RN="MSC1", DEX=1, LSX=1;
Add an M3UA link to MSC Server
ADD M3LNK: LNK=0, BT=SPF, BN=0, LKN="MSC1",
LIP1="172.40.200.51", LP=2903, RIP1="172.40.200.40",
RP=2903, LSX=1, ASF=ACTIVE;
Add CN Node 1
ADD CNNODE: CNID=1, CNNAME="MSC1", MSCIDX=1,
M3DEIDX=1, INITCAP=1000;
Add The Relation Between NRI And
MSC
ADD NRIMSC: NRIV=1, CNID=1;
Configure M3UA Data to BSC
Configure destination entity, linkset, route and link to BSC
ADD M3DE: DEX=5, DEN="BSC1_1", DET=SP, NI=NATB, DPC=H'c01, LEX=2,
NETTYPE=POOLBSC;
ADD M3DE: DEX=6, DEN="BSC1_2", DET=SP, NI=NATB, DPC=H'c01, LEX=1,
NETTYPE=POOLBSC;
ADD M3LKS: LSX=3, LSN="POOL_ToBSC", ADX=5, TM=LOADSHARE,
WM=IPSP;
ADD M3RT: RN="POOL_BSC", DEX=5, LSX=3;
ADD M3LNK: LNK=3, BT=SPF, BN=0, LKN="POOL_BSC",
LIP1="171.40.200.51", LP=6000, RIP1="171.40.200.33", RP=6000, LSX=3,
ASF=ACTIVE;
Page91
Contents
2.1 Scenario
Page92
Maintenance Commands on MSC
Server
Commands of querying the SPC, link status of BSC
and MGW, and SSP status of BSC:
DSP SCCPDSP Display SCCP Destination Signaling Point
Status
DSP SCCPSSN Display SCCP Sub-system Status
Maintenance Commands on MGW
Commands of querying the SPC, link status of MSC
Server and BSC
Appendix: Reconstruct Procedure
Save Data Relate to AoTDM
Delete Data Relate to AoTDM,
and M3UA Data to MGW and
BSC on MSC Server
Start
Delete M3UA Data to MSC
Server and N7 Data to BSC
Configure M3UA Data to BSC,
Bear Data on MGW
End
Appendix: Reconstruct Notes
Reconstruct in low traffic;
Save the data relate to AoTDM, Run DSP CFG on MGW
In AoIP, TC resource will be provided by MGW, consider
to add VPU board which supports FR/EFR/HR/AMR;
to add VPU board which supports FR/EFR/HR/AMR;
License on MSC Server and MGW should support AoIP;
Consider to add IFM board on MSC Server, and HRU
board on MGW.
Page96
Summary
The following contents are introduced in this course:
Commands related to AoIP on MSC Server and;
Data configuration for direct connection mode between
MSC Server and BSC
Data configuration for MGW connection mode between
MSC Server and BSC (M3UA forward)
Page97
Thank you
AoIP Troubleshooting
www.huawei.com
References
MSOFTX3000 V100R008C03 Product Documentation
UMG8900 V200R008C03 Product Documentation
Objectives
Analyze and handle faults related to core network AoIP
Complete analysis and handling of common faults
Contents
1. Core Network AoIP Troubleshooting Methods
2. Common Fault Handling
Contents
Core Network IP Troubleshooting Methods
Fault delimitation
Fault information collection
Fault location
Troubleshooting
Fault Information Collection
Information Source
In case a fault occurs on an AoIP network, you need to
collect fault information based on the following aspects:
Bearer network devices
Core network devices
Maintenance engineers and the network management
center (NMC)
Subscribers affected by the fault
Page 105
Alarms Generated on the MSC Server and
MGW
ALM-2010 IP Auto Locate Fault Detect Failure
ALM-2012 IP Auto Locate Fault Info
ALM-2039 FE Port Faulty
ALM-2137 IP Address Conflict
ALM-2255 Error frame Rate of ETH Port

Exceeding Threshold
ALM-2273 ARP Detect Abnormal

ALM-3209 IP Interface Failure
ALM-3260 IP Address Conflict
ALM-3265 Switch to the Backup IP Route
ALM-3282 IP Bearer Network Abnormal
ALM-3287 IP Packets Loss During Flow Control
ALM-3289 IP Address Disabled
ALM-1809 M3UA Link Congestion
ALM-1811 M3UA Link Failure
ALM-1831 M3UA Link Overload
ALM-1762 M3UA SCTP Path Alarm

ALM-3990 M3UA Link Failure
ALM-3991 M3UA Destination Entity Route
Unavailable
ALM-3992 M3UA Route Unavailable
ALM-3993 M3UA Destination Entity Unreachable
ALM-3994 M3UA Link SCTP Congestion
ALM-3998 M3UA Link Set Failure
MSC Server
MGW
AoIP Traffic Measurement Involving
the MSC Server
Bearer Traffic
Bearer Modification Invoked by BSC
Internal Handover Traffic
Outgoing Calls in Mobile Office Direction
Incoming Calls in Mobile Office Direction
MSC Basic Services
GSM Assignment
Page107
AoIP Traffic Measurement Involving
the MGW
Resources Measurement of the Whole Equipment
Statistics of TC Occupation of the Whole Equipment
Statistics of EC Occupation of the Whole Equipment
Statistics of CC Occupation of the Whole Equipment
Call Processing Measurement
Allocation Information About Codec Resources
Page108
Fault Information Collection
Procedure
Collect alarms and subscriber complaints to determine the
fault occurring time, scope, and impact degree.
Check the running status of the bearer network and CEs.
Check the running status of the MSC Server/MGW.
Check for exceptions or operations performed on the local
site or peripheral NEs before and after the fault occurrence.
(Important)
Collect the data configuration related to AoIP
Perform dialing test and trace the signaling.
Page109
Fault DelimitationPrinciples
Troubleshooting must be performed based on principles. If you do
not follow the principles, troubleshooting duration may be
prolonged, which causes low efficiency and greater damages even
though fault information is collected.
You are advised to use delimitation methods that are fast and with
little impact on services, such as active and standby switchover, load-
sharing, and board replacement.
Troubleshooting must be performed on hardware and then software.
Troubleshooting must be performed from bottom layer to top layer of a
protocol stack.
Most network faults occur at the bottom layer.
Page 110
Fault DelimitationCommon Methods
Original information analysis
Alarm information analysis
Indicator status analysis
Dialing test analysis
Information tracing by using meters and instruments
Measurement data analysis
Log analysis
Page 111
A Interface Message Tracing on MSC
Server
Check the messages exchanged over the signaling
interface.
Subscribe Message Tracing on MSC
Server
Check the call proceeding messages of a specified call
over various interfaces of the MSC server
Fault Location
Analyze the reason according to the information
collected, including alarm, traffic measurement, data
configuration, message tracing.
Contents
Contents
2.1 SCTP Multi-Homing
2.2 Codec
Basic Concepts of SCTP Multi-Homing
Stream Control Transmission Protocol (SCTP) supports
multiple IP addresses in one SCTP association and
provides reliable transmission mechanism of end to end
(E2E) path for users of upper-layer protocols. In a bearer
network, when a plane is blocked or a customer edge (CE)
network, when a plane is blocked or a customer edge (CE)
fails, SCTP multi-homing can be used to fast switch the
signaling to a normal plane. In this way, the loss of
services can be reduced.
Page 117
Basic Concepts of SCTP Multi-Homing
Two endpoints: (IP1, IP2, 2000) and (IP3, IP4, 3000)
One association: (IP1, IP2, 2000, IP3, IP4, 3000)
2/4 paths: Path or
IP1
IP2 IP4
IP3
1
2
3
4
2000 3000
Path Status Maintenance
The maintenance mechanism of path status in SCTP
multi-homing mode is as follows:
Each path is configured with a retransmission counter. When
the value obtained by the counter exceeds the maximum
retransmission attempts of the path, the destination transport
retransmission attempts of the path, the destination transport
address is considered to be unreachable. The path status is set
to Inactive.
When user data is transmitted through the current path, the path
status is monitored by using data messages.
When no user data is transmitted through the current path, the
path status is detected by using heartbeat messages.
Page 119
Path Switchover
The path switchover principles of SCTP multi-homing are as follows:
1 Use the primary path to perform data transmission when the primary path is in
active status. In the case of packet retransmission, use the standby path. (Note
that the primary path is not switched.)
2 When the primary path is in inactive status, the transmission path
automatically switches to the standby path. If the standby path is in inactive
automatically switches to the standby path. If the standby path is in inactive
status, the current transmission path is not changed and links are broken over
the transmission path.
3 When the primary path is recovered, the transmission path is automatically
switched to the primary path.
Data/SACK
Heartbeat/Heartbeat ACK
Data/SACK
Heartbeat/Heartbeat ACK
Page 120
Switching of the SCTP MultiHoming Paths
Symptom:
Switching of the SCTP multi-homing paths fails.
Analysis:
Backup paths cannot be reached. You can run the PING command
to locate the fault. If the physical connection is faulty, you must
to locate the fault. If the physical connection is faulty, you must
ensure that the physical connection is normal by checking the
cables.
Modes are different for the SCTP protocol stack multi-homing
paths on the local and peer devices. At present, SCTP path modes
on the MGW and MSC Server are 2-path mode and 4-path mode.
The 2-path mode is used primarily. Path modes on the local and
peer devices must be the same.
Page 121
SCTP Traffic Exception
Symptom:
Abnormal changes are detected in the SCTP traffic after comparing the historical
data by using the NMS statistics system. These changes may lead to faults
occasionally and affect services.
Analysis:
Significant changes are caused due to the changes of call attempts, subscriber
quantity, and network topologies. The changes are normal traffic increase. You
quantity, and network topologies. The changes are normal traffic increase. You
need to check whether congestion exists. If congestion exists, add associations or
message dispatches.
Messages are retransmitted locally because of IP network quality degradation or
delayed processing of the peer signaling. If message retransmission is caused by
delayed signaling processing, the fault can be solved on the peer device. If
message retransmission is caused by IP network quality degradation, the fault can
be solved by troubleshooting on the CE.
Traffic exception can be caused by incorrect data configuration, such as uneven
load-sharing.
Page 122
Contents
2.1 SCTP Multi-Homing
2.2 Codec
TrFo
The Transcoder Free Operation (TrFO) feature enables setup of speech calls
without using Transcoders (TCs) for speech transmission. It helps to achieve
end-to-end high fidelity and low delay.
TrFO is implemented by means of out-of-band transcoder control (OoBTC). It is
applicable to calls between mobile networks, and calls between mobile
networks and other networks. OoBTC enables networks to negotiate the codec
networks and other networks. OoBTC enables networks to negotiate the codec
type and mode before call setup. After successful negotiation, a network can
set up a call between two mobile subscribers without the assistance of TCs.
This improves voice quality. As outband negotiation is used, expensive TC
resources and associated power consumption are not required.
Page124
TrFO in 2G-to-2G intra-MSC(AoIP)
If the BSCs (AoIP) at the calling and called sides use the
same codec or compatible codecs, TrFO is started upon
TrFO in 2G-to-2G inter-MSC calls
If the A interface is IP-based and the BSC
and the MGW use the same codec or
compatible codecs, TrFO is started upon
If the A interface is time division
multiplexing (TDM)-based, TrFO is started
between MGWs upon successful codec
negotiation
AoIP
AoTDM
Codec Negotiation Principles
If the TDM-based A interface is used on the 2G access side, the A interface adopts the
G.711 codec. In this case, the BSC is not configured with any codec type or rate and is not
involved in obtaining the codec intersection. If bit 6 of P92 is set to 0 (that is, negotiation
of 2G codecs is enabled), 2G compressed codecs are also involved in the subsequent codec
negotiation.
If the IP-based A interface is used on the 2G access side, the MSC server obtains the
intersection of the codecs supported by the BSC and those supported by the UE and MGW.
intersection of the codecs supported by the BSC and those supported by the UE and MGW.
Then, the MSC server obtains the intersection of the rates of the HR-AMR and FR-AMR
configured on the BSC and the rates of the AMR codecs configured on the MGW.
On the 3G access side, codec negotiation is performed by obtaining the intersection of the
codecs used by the user equipment (UE) and the MGW. The AMR codecs (UMTS AMR,
UMTS AMR2, and WB-AMR) in the intersection should be configured with the rate sets
obtained from the intersection of the rate sets supported by the MGW and the RNC.
In inter-MSC codec negotiation, there must be a codec intersection between the
associated MGWs. Otherwise, the inter-MSC bearer setup fails.
Page127
Codec Negotiation in an intra-MSC
call Between 2G Subscribers (AoIP)
Codec Inconsistent of MGWs Lead to
Low Success Rate of Handover In
Symptom
AoTDM reconstruct to AoIP, the success rate of handover in
declines to 23%. From the message tracing, the main
reason is Requested terrestrial resource unavailable
returned by MSC Server.
returned by MSC Server.
Networking
Page129
MSOFTX3000
UMG1 UMG2
TDM-BSC1
IP-BSC2
Reason Analysis
From the message tracing, the reason is returned when
MSC Server requests resource.
Reason Analysis
Check the codec the MGW configured, We find that all the MGWs except
one corresponding to the BSC based on IP have not been configured 2G
codec.
So, if the handover from the MGW corresponding to the BSC based on TDM to
the MGW corresponding to the BSC based on IP, the intersection of codec list of
BSC, MGW, and MS will fail, then handover fail.
Solution
Configure 2G codec to all the MGW on MSC Server, and
TC resource on each MGW.
Summary
The course describes the troubleshooting methods,
delimitation, and location of core network AoIP faults as
well as the common fault handling procedures.
Thank you

Livre AoIP PDF

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Livre AoIP PDF

Transféré par

Droits d'auteur :

Formats disponibles

AoIP Networking and

ALM-2010 IP Auto Locate Fault Detect Failure

ALM-2012 IP Auto Locate Fault Info

ALM-2039 FE Port Faulty

ALM-2137 IP Address Conflict

ALM-2255 Error frame Rate of ETH Port

ALM-2273 ARP Detect Abnormal

ALM-1809 M3UA Link Congestion

ALM-1811 M3UA Link Failure

ALM-1831 M3UA Link Overload

ALM-1762 M3UA SCTP Path Alarm

Vous aimerez peut-être aussi