Operator Logo

ZGO-05-04-003 A Over IP

Feature Guide
 ZGO-05-04-003 A Over IP

ZGO-05-04-003 A Over IP

Version Date Author Approved By Remarks

V1.00 2010-10-30 Not open to the Third Party

© 2010 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be
disclosed or used without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is
subjected to change without notice.

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. I

 ZGO-05-04-003 A Over IP

TABLE OF CONTENTS

1 Feature Property ............................................................................................. 1

2 Overview ......................................................................................................... 2
2.1 Feature Introduction.......................................................................................... 2
2.2 Correlation with Other Features ........................................................................ 2

3 Technical Description .................................................................................... 2

3.1 A over IP Architecture ....................................................................................... 3
3.2 A over IP Protocol Stack ................................................................................... 3
3.3 A over IP Application Scenarios ........................................................................ 6

4 Parameters and Configuration....................................................................... 7

4.1 Parameter List .................................................................................................. 7
4.2 Parameter Configuration ................................................................................... 8
4.2.1 IP Interface Configuration ................................................................................. 8
4.2.2 Configuration Related to Office and SIGTRAN ............................................... 16
4.2.3 Configuration Related to Service and RTP Multiplexing .................................. 31

5 Engineering Guide ........................................................................................ 36

5.1 Application Scenario ....................................................................................... 36
5.2 Configuration Description................................................................................ 37
5.3 Impact on Network .......................................................................................... 37

6 Related Counters and Alarms ...................................................................... 37

6.1 Related Counters ............................................................................................ 37
6.2 Related Alarms ............................................................................................... 42

7 Abbreviation.................................................................................................. 43

8 Reference Document .................................................................................... 43

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. II

 ZGO-05-04-003 A Over IP

FIGURES

Figure 3-1 A over IP Architecture ......................................................................................... 3

Figure 3-2 IPA Control Plane Protocol Stack ........................................................................ 3
Figure 3-3 IPA User Plane Protocol Stack ............................................................................ 5
Figure 4-1 Configuring IP Address of IPI Interface Board at IPA Interface ............................ 8
Figure 4-2 Configuring IP Address of SMP Module at IPA Interface ................................... 11
Figure 4-3 Configuring IP Address of Local Service ........................................................... 13
Figure 4-4 Static Route ...................................................................................................... 14
Figure 4-5 Configuring Local Office .................................................................................... 16
Figure 4-6 Configuring Adjacent Office............................................................................... 18
Figure 4-7 Configuring ASP ............................................................................................... 21
Figure 4-8 Configuring ASP IP ........................................................................................... 23
Figure 4-9 Configuring AS .................................................................................................. 24
Figure 4-10 Configuring ASP ID ......................................................................................... 26
Figure 4-11 SIO ................................................................................................................. 27
Figure 4-12 Configuring MSC Office................................................................................... 29
Figure 4-13 Configuring PLMN ........................................................................................... 30
Figure 4-14 Configuring AIPB DSP IP ................................................................................ 32
Figure 4-15 Configuring A CS ............................................................................................ 34
Figure 4-16 Configuring RTP Multiplexing .......................................................................... 35

TABLES

Table 3-1 A over IP Application Scenarios ........................................................................... 6

Table 4-1 Parameters Related to IP Interface ...................................................................... 7
Table 4-2 Parameters Related to Office and SIGTRAN ........................................................ 7
Table 4-3 Parameters Related to Service Configuration and RTP Multiplexing Configuration
............................................................................................................................................... 8
Table 6-1 Assignment counters .......................................................................................... 37
Table 6-2 Call drop counters .............................................................................................. 38
Table 6-3 Handover cause counters .................................................................................. 38
Table 6-4 TCH/F counters .................................................................................................. 38
Table 6-5 TCH/H counters ................................................................................................. 40

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. III
 ZGO-05-04-003 A Over IP

Table 6-6 BSSMAP message counters .............................................................................. 41

Table 6-7 Terrestrial resource availability measurement counters ...................................... 42
Table 6-8 Alarm list ............................................................................................................ 42

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. IV

 ZGO-05-04-003 A Over IP

1 Feature Property
iBSC Version: ZXG10 iBSC(V6.20.60)

BTS Version: Independent of BTS hardware platform

Property: Optional

Related Network Element:

NE Name Related Special Requirement

MS -

BTS -

BSC √

MSC √

MGW √

SGSN -

GGSN -

HLR -

Dependent Function: None

Exclusive Function: None

Note: A over IP must comply with the 3GPP standard.

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 1

 ZGO-05-04-003 A Over IP

2 Overview

2.1 Feature Introduction

This function makes the IP protocol bear the control plane and user plane of
A-interface, which complies with the 3GPP standard.

2.2 Correlation with Other Features

This feature has a correlation with the following features:

1. ZGF05-01-032 A over IP_V811_CN

The A over IP function of this feature complies with the 3GPP standard. The A over IP
function of ZGF05-01-032 A over IP_V811_CN complies with the China Mobile standard.

2. Bidirectional Forwarding Detection。

3. Link Aggregation Control Protocol。

4. Vlan and DSCP。

5. Path Protection。

This feature does not involve IP networking. For details of IP networking, refer to Feature
2, Feature 3, Feature 4, Feature 5.

3 Technical Description
With the evolution of network technology, it becomes much easier to get IP-based
transmission resource. Compared with the traditional circuit network, the IP network
enjoys a higher usage and more flexible networking. All transmission networks are
developing towards the trend of IP bone transmission network. The support of IP bearer
at A-interface helps the network develop towards the all-IP architecture, and makes it
easier to combine the GSM network and the future transmission network.

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 2

 ZGO-05-04-003 A Over IP

3.1 A over IP Architecture

The A over IP function, which complies with the 3GPP standard, supports two structures
of TC: TC in MGW and TC in BSS. At present, this feature supports the structure of TC in
MGW, as shown in Figure 3-1.

Figure 3-1 A over IP Architecture

MSC-S MSC-S
A/IP Nc A/IP

BSS
Mc/IP Mc/IP BSS

MGW MGW
A/IP Nb A/IP

e.g. AMR coded e.g. AMR coded

IP based IP based
protocol protocol
stack stack

= Signalling
= Transcoder or Transcoder-pair, typically not used in MS-to MS calls
= User p lane

3.2 A over IP Protocol Stack

The A over IP function, which complies with the 3GPP standard, adopts the protocol
stacks as shown in Figure 2 and Figure 3. Figure 2 shows the control plane protocol
stack, that is, Sigtran protocol stack. Figure 3 shows the user plane protocol stack.

Figure 3-2 IPA Control Plane Protocol Stack

BSC MSS
BSSAP BSSAP
SCCP SCCP
M3UA M3UA
SCTP SCTP
IP IP
MAC / PPP MAC / PPP

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 3

 ZGO-05-04-003 A Over IP

The following describes the protocol of each layer:

BSSAP: BSS Application Part. It is the protocol between BSC and MSC of the GSM
system, used for radio resource management and ground resource management for CS
services.

SCCP: Signaling Connect Control Part. It is part of SS7 signaling protocols, used for
BSSAP signaling information transmission at A-interface. The connection can be
established or not established.

M3UA: MTP Level 3 User Adaptation Layer protocol. It supports that IP protocol bears all
user messages of SS7 signaling MTP3 (ISUP, SCCP, TUP, ALCAP, H.248, and BICC).
M3UA provides the same function as MTP3, which makes MTP3 users not feel that the
service is provided by the remote M3UA.

SCTP: Stream Control Transmission Protocol. It is a connection-oriented transmission

layer protocol, providing reliable user-message-oriented transmission service among
peer SCTP users. SCTP follows the RFC2960 specification. It performs signaling bearing
in the IP network, makes signaling messages be exchanged in the IP-based public
packet switching network, and performs point-to-point flow control and error control.

IP: Internet Protocol. The IP layer receives data packet sent from the lower layer, divides
the packet, combines the packet, adds the source IP address and the destination IP
address of the data packet, and sends the data packet to the next network node. It does
not guarantee that the sequence of packet sending and receiving is reliable.

MAC: Media Access Control protocol. This protocol is used to control and connect
physical layer medium. In data sending, MAC first decides whether the data can be sent.
If the data can be sent, it adds some control information in the data and sends the data
and control information in specified format to the physical layer. In data receiving, MAC
first decides whether the input information contains any transmission error. If the data is
correct, it deletes the control information and sends it to the upper layer.

PPP: Point-to-Point Protocol. It is the link layer protocol, used for sending data packet
among peer units. The PPP link supports the duplex operation, and data packets are
transmitted according to the sequence. The point-to-point connection is established

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 4

 ZGO-05-04-003 A Over IP

through dialing or private line, via which the data is transmitted. It helps implement simple
connection among host machines, bridges, and routers.

Figure 3-3 IPA User Plane Protocol Stack

BSC MGW

Payload Payload
RTP RTP
UDP UDP
IP IP
MAC/PPP MAC/PPP

The following describes the protocol of each layer:

Payload: The voice payload of users. When BSS does not perform the voice coding
conversion, the payload is TRAU frames of various voice coding that satisfy GSM
wireless interface standards.

RTP: Real-time Transport Protocol. It is a transmission protocol specified for the media
data stream. In point-to-point or point-to-multipoint transmission, it provides the time
information and implements the stream synchronization. Based on Real-time Transport
Control Protocol (RTCP), RTP provides a scheme of sequential and reliable data
transmission, flow control, and congestion control.

IP: Internet Protocol. The IP layer receives data packet sent from the lower layer, divides
the packet, combines the packet, adds the source IP address and the destination IP
address of the data packet, and sends the data packet to the next network node. It does
not guarantee that the sequence of packet sending and receiving is reliable.

MAC: Media Access Control protocol. This protocol is used to control and connect
physical layer medium. In data sending, MAC first decides whether the data can be sent.
If the data can be sent, it adds some control information in the data and sends the data
and control information in specified format to the physical layer. In data receiving, MAC
first decides whether the input information contains any transmission error. If the data is
correct, it deletes the control information and sends it to the upper layer.

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 5

 ZGO-05-04-003 A Over IP

PPP: Point-to-Point Protocol. It is the link layer protocol, used for sending data packet
among peer units. The PPP link supports the duplex operation, and data packets are
transmitted according to the sequence. The point-to-point connection is established
through dialing or private line, via which the data is transmitted. It helps implement simple
connection among host machines, bridges, and routers.

3.3 A over IP Application Scenarios

At present, ZXG10 BSS supports the following application scenarios:

Table 3-1 A over IP Application Scenarios

Solution TC CN
AoTDM AoIP BSS Version
Example Location Version

Existing All Codecs

Yes, Traditional Traditional
network types are in No
only G.711 version version
scenario BSS

Select Yes,
AoIP Yes, Updated Updated
according to only 3GPP
scenario 1 only G.711 version version
Codec type CodeC

All Codecs Yes,

AoIP No TC New
types are in No only 3GPP
scenario 2 version version
CN CodeC

The following describes scenarios in Table 3-1.

Existing network scenario: It represents the traditional A-interface of TDM mode. The
TransCode (TC) is located at BSS side, the A-interface physical layer uses E1 interface,
the control plane adopts BSSAP over SCCP/MTP, and the user plane adopts the 64K
voice data in PCM format which has been processed by Codec type conversion.

AoIP scenario 1: It represents the hybrid A-interface mode which combines the traditional
A-interface of TDM mode and the A-interface of IP mode. The TransCode (TC) is located
partly at BSS side and partly at CN side. Which A-interface mode will be adopted is
decided by protocols of MSC and BSC. If A-interface of TDM mode is adopted, the TC

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 6

 ZGO-05-04-003 A Over IP

resource at BSS side is used, and A-interface user-plane data is the 64K voice data in
PCM format which has been processed by Codec type conversion. If A-interface of IP
mode is adopted, the TC resource at CN side is used, and A-interface user-plane data is
the voice frame of TRAU format carried in RTP stream.

It is complex to implement an office between BSC and CN, which supports both
A-interface of TDM mode and A-interface of IP mode. However, it helps implement
smooth upgrade of the existing network from A-interface of TDM mode to A-interface of
IP mode. After the upgrade is completed, disable the A-interface of TDM mode at both
BSS and CN, then AoIP scenario 1 becomes AoIP scenario 2.

AoIP scenario 2: It represents the all-IP interface and does not support A-interface of
TDM mode. It is the target of A-interface IP evolution. In this case, BSS does not have TC
resource, and the TC resource at CN is used. The A-interface user-plane data is the
voice frame of TRAU format carried in RTP stream.

4 Parameters and Configuration

4.1 Parameter List

Table 4-1 Parameters Related to IP Interface

No. Name Configuration Illustration

1 IPI Figure 4-1

2 SMP Figure 4-2

3 RPU Figure 4-3

4 Static route Figure 4-4

Table 4-2 Parameters Related to Office and SIGTRAN

No. Name Configuration Illustration

1 Local Office Figure 4-5

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 7

 ZGO-05-04-003 A Over IP

2 Adjacent Office Figure 4-6

3 ASP Basic config Figure 4-7

4 ASP IP Figure 4-8

5 AS Basic config Figure 4-9

6 ASP ID Figure 4-10

7 SIO Figure 4-11

8 MSC Office Figure 4-12

9 PLMN Figure 4-13

Table 4-3 Parameters Related to Service Configuration and RTP Multiplexing

Configuration

No. Name Configuration Illustration

1 Set IP Port Figure 4-14

2 A CS Figure 4-15

3 RTP multiplexing Figure 4-16

4.2 Parameter Configuration

4.2.1 IP Interface Configuration

1. In Configuration Management, double-click [OMC → GERAN Subnetwork → BSC

Managed Element → Config Set → BSC Function →IP Related Config. Click the
Add button, as shown in below.

Figure 4-1 Configuring IP Address of IPI Interface Board at IPA Interface

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 8

 ZGO-05-04-003 A Over IP

Full name IPA interface IP interface board

Abbreviation IPI

3GPP name -

3GPP reference -

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 9

 ZGO-05-04-003 A Over IP

To guarantee reliable communication between BSC and MSC, the

physical interface board's IP address must be configured. The
relevant parameters include:
User label: Defined according to actual requirement.
Board function type: Select IPI.
Subsystem:module:unit:sunit: If BSC is configured with IPI board,
the system prompts user to select appropriate configuration. Set
according to actual requirement.
Description Port Number: Select according to actual requirement. It must be
consistent with the physical connection.
MAC Address: Configured according to actual requirement.
The Number of IP: 4 at most. Configured according to actual
requirement.
IP Address: Configured according to actual requirement.
Subnet mask: Configured according to actual networking
requirement.
Other parameters use the default value.

Managed object BSC

Board function type: IPAB, IPBB, IPGB, IPI, EUIP, RPU, SMP
Subsystem:module:unit:sunit: Generated according to BSC board
Value range configuration.
Port Number: 1 ~ 4
The Number of IP: 1 ~ 4

Unit None

Board function type: IPAB

Subsystem:module:unit:sunit: Generated according to BSC board
Default value configuration.
Port Number: 1
The Number of IP: 1

Relevant
A over IP
features

Relevant
-
parameters

Related
-
interfaces

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 10

 ZGO-05-04-003 A Over IP

Figure 4-2 Configuring IP Address of SMP Module at IPA Interface

Full name Service processing module

Abbreviation SMP

3GPP name -

3GPP reference -

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 11

 ZGO-05-04-003 A Over IP

To guarantee reliable communication between BSC and MSC,

the SMP module's IP address must be configured. The relevant
parameters include:
User label: Defined according to actual requirement.
Board function type: Select SMP.
Subsystem:module:unit:sunit: Select according to CMP module
Description configuration.
Port Number: Select according to actual requirement.
The Number of IP: 4 at most. Configured according to actual
requirement.
IP Address: Configured according to actual requirement.
Subnet mask: 32 bits.
Other parameters use the default value.

Managed object BSC

Board function type: IPAB, IPBB, IPGB, IPI, EUIP, RPU, SMP
Value range Port Number: 1 ~ 4
The Number of IP: 1 ~ 4

Unit None

Board function type: IPAB

Default value Port Number: 1
The Number of IP: 1

Relevant features A over IP

Relevant
-
parameters

Related interfaces -

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 12

 ZGO-05-04-003 A Over IP

Figure 4-3 Configuring IP Address of Local Service

Full name Route Protocol Unit

Abbreviation RPU

3GPP name -

3GPP reference -

To guarantee reliable communication between BSC and MGW,

the virtual IP address of RPU must be configured. The relevant
parameters include:
User label: Defined according to actual requirement.
Board function type: Select RPU.
Description Port Number: Select according to actual requirement.
The Number of IP: 4 at most. Configured according to actual
requirement.
IP Address: Configured according to actual requirement.
Subnet mask: 32 bits.
Other parameters use the default value.

Managed object BSC

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 13

 ZGO-05-04-003 A Over IP

Board function type: IPAB, IPBB, IPGB, IPI, EUIP, RPU, SMP
Value range Port Number: 1 ~ 4
The Number of IP: 1 ~ 4

Unit None

Board function type: IPAB

Default value Port Number: 1
The Number of IP: 1

Relevant features A over IP

Relevant
-
parameters

Related interfaces -

2. In Configuration Management, double-click [OMC → GERAN Subnetwork → BSC

Managed Element → Config Set → BSC Function →IP Related Config. Click the
Add button in the Static Route tab, as shown in below.

Figure 4-4 Static Route

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 14

 ZGO-05-04-003 A Over IP

Full name Static route

Abbreviation -

3GPP name -

3GPP
-
reference

If the physical connection is normal and IP configuration is completed,

but the IP address of the interface between BSC and CN and the IP
address of service cannot access each other, then it is necessary to
add relevant routes. The relevant parameters include:
User label: Defined according to actual requirement.
Static route ID: Configured according to actual requirement.
Static route prefix: It represents the static route prefix, which is the IP
address of the opposite-end service.
Static route subnet mask: Configured according to actual networking
requirement.
Next hop type: Select IP.
Description Next hop IP address: IP address of the opposite-end IP interface
board.
Other parameters use the default value.
For example:
IP address of MGW interface board is 210.0.31.10; IP address of
service is 11.31.31.31.
IP address of BSC interface board is 210.0.55.10; IP address of
service is 210.0.55.1.
Obviously, the IP address of MGW service and the IP address of BSC
service cannot access each other, and it is necessary to add route.
The route added for BSC is:
11.31.31.31 (prefix), 255.255.255.255 (mask), 210.0.33.10 (next hop)

Managed
BSC
object

Static route ID: 1 ~ 2048

Value range
Next hop type: IP, interface.

Unit None

Default Static route ID: 1

value Next hop type: IP

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 15

 ZGO-05-04-003 A Over IP

Relevant
A over IP
features

Relevant
-
parameters

Related
-
interfaces

4.2.2 Configuration Related to Office and SIGTRAN

1. In Configuration Management, double-click [OMC → GERAN Subnetwork →

BSC Managed Element → Config Set → BSC Function  A/Ater Interface Related
Configuration  Create  Local Office ], as shown in below.

Figure 4-5 Configuring Local Office

Full name Local Signaling Point

Abbreviation -

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 16

 ZGO-05-04-003 A Over IP

3GPP name -

3GPP reference -

To implement communication between BSC and MSC, it is

necessary to configure parameters related to the local office of
BSC, including:
User label: Defined according to actual requirement.
No 7 type: IP mode used at A-interface. Select "IP" or "Narrow
band and IP".
Net type: Configure according to actual requirement, and
"CTCN" is often used.
Net appearance info: Consistent with CN, and the default value
Description
is "Disable".
OPC (14 bits or 24 bits): Consistent with both ends of CN.
Usually, BSC adopts the 14-bit signaling point coding instead of
the 24-bit signaling point coding.
Other parameters use the default value.
For example:
If the BSC office configured at CN uses 14-bit signaling point
and the coding is 1.55.1, then the local office at BSC is
configured with 14-bit signaling point and the coding is 1.55.1.

Managed object BSC

No 7 type: Narrow band, IP, Narrow band and IP

Net type: CTCN, CMCN, CUCN, RLTN, CNC, NFTN, Network7,
Value range
Network 8
Net appearance info: Disable, Enable

Unit None

No 7 type: Narrow band

Default value Net type: CTCN
Net appearance info: Disable

Relevant features A over IP

Relevant
-
parameters

Related interfaces -

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 17

 ZGO-05-04-003 A Over IP

2. In Configuration Management, double-click [Local Office Signaling Point ID] in

[OMC → GERAN Subnetwork → BSC Managed Element → Config Set → BSC
Function  A/Ater Interface Related Configuration]. Click the Add button in the
Adjacent Office tab, as shown in below.

Figure 4-6 Configuring Adjacent Office

Full name Adjacent office data

Abbreviation -

3GPP name -

3GPP
-
reference

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 18

 ZGO-05-04-003 A Over IP

To implement communication between BSC and MSC, it is necessary

to configure parameters related to the adjacent office of MSC,
including:
User label: Defined according to actual requirement.
Office ID: Customized, and the value range is 1 ~ 64.
Office type: Connecting MSC. Select "MSC server". For A over IP, if
the office type is MSC Server, then it is required to configure office; if
the office type is MGW, then there is no need to configure office.
SPT type: Configured according to actual requirement.
SSF: Configured according to actual requirement.
SPC Type: Consistent with the configuration at MSC side. Usually,
Description MSC Server adopts the 14-bit signaling point coding to communicate
with BSC.
DPC: Consistent with the configuration at MSC side.
AM: Select "AM SURE" for A over IP.
Other parameters use the default value.
For example:
If the local office configured at MSC uses 14-bit signaling point and the
coding is 1.32.1, then the adjacent office at BSC is configured with
14-bit signaling point and the coding is 1.32.1.
Note: If A-interface is configured with FLEX A mode, then add an office
with the type of MSC SERVER according to the parameter
configuration.

Managed
BSC
object

Office ID: 1 ~ 64
Office type: MGW, MSC Server, SMLC, RNC.
SPT type: STEP, SEP, STP.
Value range SSF: Global signal code, Global backup signal code, signal code,
backup signal code.
SPC Type: SPC 14, SPC 24.
AM: AM SURE, AM quasi, AM NONE.

Unit None

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 19

 ZGO-05-04-003 A Over IP

Office ID: 1
Office type: MGW
Default SPT type: STEP
value SSF: Global signal code
SPC Type: SPC 14
AM: AM SURE

Relevant
A over IP
features

Relevant
-
parameters

Related
-
interfaces

3. In Configuration Management, double-click [Local Office Signaling Point ID] in

[OMC → GERAN Subnetwork → BSC Managed Element → Config Set → BSC
Function  A/Ater Interface Related Configuration]. Click the Add button in the ASP
tab, as shown in below.

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 20

 ZGO-05-04-003 A Over IP

Figure 4-7 Configuring ASP

Full name Application Server Process

Abbreviation ASP

3GPP name -

3GPP reference -

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 21

 ZGO-05-04-003 A Over IP

To implement communication between BSC and MSC, it is

necessary to configure parameters related to the adjacent
ASP, including:
User label: Defined according to actual requirement.
ASP ID: Configured according to actual requirement.
SCTP ID: Configured according to actual requirement.
Module: SMP module number
Protocol type: Select M3UA.
Office ID: Corresponding to the adjacent office configured
Description
previously.
Property: Opposite to that configured at MSC.
For example: If Property is configured as Server at MSC,
then Property is configured as Client at BSC; vice versa.
Local port: Consistent with the configuration at MSC side.
Remote port: Consistent with the configuration at MSC side.
Other parameters use the default value.
Note: If it is required to configure multiple ASPs, add the
ASP one by one.

Managed object BSC

ASP ID: 1 ~ 256

SCTP ID: 1 ~ 256
Protocol type: M3UA, SUA.
Value range
Property: Server, Client.
Local port: 1 ~ 65535
Remote port: 1 ~ 65535

Unit None

ASP ID: 1
SCTP ID: 1
Protocol type: M3UA
Default value
Property: Server
Local port: 1
Remote port: 1

Relevant features A over IP

Relevant parameters -

Related interfaces -

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 22

 ZGO-05-04-003 A Over IP

Figure 4-8 Configuring ASP IP

Full name ASP IP Configuration

Abbreviation ASP-IP Config

3GPP name -

3GPP reference -

To implement communication between BSC and MSC, it is

necessary to configure parameters related to ASP,
including:
Description
Local IP Address: IP address of configured SMP module.
Remote IP Address: IP address of opposite-end MSC
service.

Managed object A/Ater interface

Value range -

Unit None

Default value -

Relevant features A over IP

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 23

 ZGO-05-04-003 A Over IP

Relevant parameters -

Related interfaces -

4. In Configuration Management, double-click [Local Office Signaling Point ID] in

[OMC → GERAN Subnetwork → BSC Managed Element → Config Set → BSC
Function  A/Ater Interface Related Configuration]. Click the Add button in the AS
tab, as shown in below.

Figure 4-9 Configuring AS

Full name Application Server

Abbreviation AS

3GPP name -

3GPP reference -

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 24

 ZGO-05-04-003 A Over IP

To implement communication between BSC and MSC, it is

necessary to configure parameters related to AS, including:
User label: Defined according to actual requirement.
Application server ID: Configured according to actual
requirement.
Context ID and Exist Contest: Consistent with those configured
at MSC.
Protocol type: M3UA
Tag: Opposite to that configured at MSC.
Description Note: If Property is configured as Server at MSC, then
Property is configured as Client at BSC; vice versa.
Service Mode: Consistent with that configured at MSC.
Mode N: Consistent with that configured at MSC. It indicates
the minimum number of ASPs required for AS service under
the load-sharing mode. This parameter is configured according
to the planning data.
Mode K: Consistent with that configured at MSC. It indicates
the number of standby ASPs under the load-sharing mode.
This parameter is configured according to the planning data.

Managed object BSC

Application server ID: 1 ~ 64

Context ID: 0 ~ 4294967295
Exist Contest: True, False.
Protocol type: M3UA, SUA.
Value range
Tag: SGP, ASP, IPSP_SERVER, IP_CLIENT.
Service Mode: override, participate.
Mode N: 1 ~ 16
Mode K: 0 ~ 15

Unit None

Application server ID: 1

Context ID: 4294967295
Exist Contest: False
Protocol type: M3UA
Default value
Tag: IP_CLIENT
Service Mode: override
Mode N: 1
Mode K: 0

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 25

 ZGO-05-04-003 A Over IP

Relevant features A over IP

Relevant
-
parameters

Related interfaces -

Figure 4-10 Configuring ASP ID

Full name Application Server Process ID

Abbreviation ASP ID

3GPP name -

3GPP
-
reference

To implement communication between BSC and MSC, it is necessary

to configure parameters related to AS, including:
Description
If it is required to configure multiple ASPs, select ID of the ASP to be
configured.

Managed
BSC
object

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 26

 ZGO-05-04-003 A Over IP

Value range -

Unit None

Default
-
value

Relevant
A over IP
features

Relevant
-
parameters

Related
-
interfaces

5. In Configuration Management, double-click [Local Office Signaling Point ID] in

[OMC → GERAN Subnetwork → BSC Managed Element → Config Set → BSC
Function  A/Ater Interface Related Configuration]. Click the Add button in the SIO
tab, as shown in below.

Figure 4-11 SIO

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 27

 ZGO-05-04-003 A Over IP

Full name SIO

Abbreviation -

3GPP name -

3GPP
-
reference

To implement communication between BSC and MSC, it is necessary

to configure parameters related to SIO, including:
User label: Defined according to actual requirement.
Office ID: Configured MSC office.
OPC: Signaling point, including signaling point of the local office and
the adjacent office.
Description
SIO: SCCP
Application server ID: Consistent with that of AS configured previously.
Tag: For IPA, select "PCM is invalid value".
Other parameters use the default value.
Note: For SIO configuration, the local signaling point and the remote
signaling point should be configured.

Managed
BSC
object

SIO: Invalid, SCCP, TUP, ISUP.

Value range
Tag: PCM is invalid value, PCM is valid value.

Unit None

Default SIO: Invalid

value Tag: PCM is invalid value

Relevant
A over IP
features

Relevant
-
parameters

Related
-
interfaces

6. In Configuration Management, double-click [OMC → GERAN Subnetwork → BSC

Managed Element → Config Set → BSC Function  Set PLMN/MSC Office/SGSN
Office/RNC Office], as shown in below.

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 28

 ZGO-05-04-003 A Over IP

Figure 4-12 Configuring MSC Office

Full name MSC Office

Abbreviation -

3GPP name -

3GPP reference -

To implement communication between BSC and MSC, it is

necessary to configure parameters related to MSC office,
including:
User label: Defined according to actual requirement.
Description MSC ID: Configured MSC office.
NRI: MSC ID, consistent with that configured at MSC.
Load allocate ratio of MSC: This parameter is used to
configure the load ratio of MSC in FLEX A configuration.
Other parameters use the default value.

Managed object BSC

MSC ID: 1 ~ 16
Value range
NRI: 0 ~ 1023

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 29

 ZGO-05-04-003 A Over IP

Unit None

MSC ID: 1
Default value
NRI: 0

Relevant features A over IP

Relevant parameters -

Related interfaces -

Figure 4-13 Configuring PLMN

Full name PLMN

Abbreviation -

3GPP name -

3GPP
-
reference

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 30

 ZGO-05-04-003 A Over IP

To implement communication between BSC and MSC, it is necessary

to add MSC into the configured PLMN. The relevant parameters
include:
User label: Defined according to actual requirement.
MCC: Mobile country code, consistent with that configured at CN.
MNC: Network code, consistent with that configured at CN.
Description
MSC ID: Configured MSC ID.
MSC CN ID: Consistent with that configured at CN.
Length of MSC NRI: Consistent with that configured at CN.
MSC-NULL-NRI ID: Consistent with that configured at CN.
MSC Version ID: Consistent with that configured at CN.
Other parameters use the default value.

Managed
BSC
object

MCC: 0 ~ 999
MNC: 0 ~ 99
Value range MSC CN ID: 0 ~ 65535
Length of MSC NRI: 1 ~ 10, 255
MSC-NULL-NRI ID: 0 ~ 1023

Unit None

MCC: 460
MNC: 2
Default
MSC CN ID: 65535
value
Length of MSC NRI: 255
MSC-NULL-NRI ID: 0

Relevant
A over IP
features

Relevant
-
parameters

Related
-
interfaces

4.2.3 Configuration Related to Service and RTP Multiplexing

1. In Configuration Management, double-click [OMC → GERAN Subnetwork → BSC

Managed Element → Config Set → BSC Function BSC Device config→ BSC

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 31

 ZGO-05-04-003 A Over IP

Rack]. Create the AIPB board in resource shelf 1 or resource shelf 3, right-click the
AIPB board, and select Set IP Port, as shown in below.

Figure 4-14 Configuring AIPB DSP IP

Full name AIPB DSP IP Configuration

Abbreviation -

3GPP name -

3GPP
-
reference

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 32

 ZGO-05-04-003 A Over IP

CS service must be processed by AIPB, the AIPB DSP parameters

include:
User label: Defined according to actual requirement.
VPN: 0. Do not modify the VPN value. At present, the system only
supports that VPN is 0.
Description IP Address: DSP IP address. It is the virtual IP address of MGW RPU
configured at background.
After the parameters are configured, import AIPB available DSP into
the dialog of creating DSP, and the IP port number will be generated
automatically.
Other parameters use the default value.

Managed
BSC
object

Value range -

Unit None

Default
-
value

Relevant
A over IP
features

Relevant
-
parameters

Related
-
interfaces

2. In Configuration Management, double-click [OMC → GERAN Subnetwork → BSC

Managed Element → Config Set → BSC Function]. Configure A CS in the IP
Property tab, as shown in below.

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 33

 ZGO-05-04-003 A Over IP

Figure 4-15 Configuring A CS

Full name A CS

Abbreviation -

3GPP name -

3GPP reference -
TOS used by CS service under IP A.
This parameter field belongs to service IP telegraph service type (IPTOS).
Description
TOS is short of Type Of Service, which is used to indicate service type or
quality required by datagram.

Managed object BSC

Value range 0 ~ 64

Unit None

Default value 0

Relevant
A over IP
features

Relevant
-
parameters

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 34

 ZGO-05-04-003 A Over IP

Related
-
interfaces

3. In Configuration Management, double-click [OMC → GERAN Subnetwork → BSC

Managed Element → Config Set → BSC Function. Modify the RTP multiplexing
parameters, as shown in below.

Figure 4-16 Configuring RTP Multiplexing

Full name RTP multiplexing

Abbreviation -

3GPP name -

3GPP reference -

Two parameters: RTP multiplexing enable, RTP

Description multiplexing Local UDP port. Both the two parameters
should be configured when the RTP function is used.

Managed object BSC

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 35

 ZGO-05-04-003 A Over IP

RTP multiplexing enable: disable, enable

Value range
RTP multiplexing Local UDP port: 1024 ~ 4998

Unit None

RTP multiplexing enable: disable

Default value
RTP multiplexing Local UDP port: 1024

Relevant features A over IP

Relevant parameters -

Related interfaces -

5 Engineering Guide

5.1 Application Scenario

This feature is applied in scenarios with the purpose of saving transmission or flexible
networking. Also, it is recommended to use this feature in the case of Flex A.

The A over IP function follows the 3GPP standard. To interconnect MSC, MSC must also
satisfy the 3GPP standard; otherwise, the interconnection will fail.

At present, BSC supports the dual-stack function. In other words, for the same MSC
office, both FULL IP and PCM over TDM are supported, but the G.711 function (i.e. PCM
over IP) is not supported. To interconnect MSC, it must be considered that whether MSC
supports the dual-stack function and G.711 function.

At present, both gigabit BSC and megabit BSC support the A over IP function. In
commissioning a megabit BSC, the planning of both IPI and AIPB should be considered,
otherwise, the voice quality might become abnormal due to traffic problem.

At present, the A over IP function supports RTP header multiplexing, but does not
support the multiplexing of header-compressed RTP.

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 36

 ZGO-05-04-003 A Over IP

5.2 Configuration Description

1. his feature involves BSC hardware configuration adjustment, including:

A-interface IP interface board: IPI board (the physical board is BIPI or GIPI),
interconnecting with that at CN side.

Service processing board: AIPB board (the physical board is GUP or GUP2), processing
user-plane data of A over IP.

2. t involve BTS hardware configuration adjustment.

5.3 Impact on Network

1. Compared with the traditional A over TDM mode, the TrFO scheme between the
calling party and the called party is added into the A over IP mode, which effectively
improves the voice quality.

2. The RTP multiplexing function is added into the A over IP mode, which saves the IP
transmission bandwidth at A-interface.

3. Compared with the TDM bearer, the IP bearer reduces the network construction
cost and improves the networking flexibility.

6 Related Counters and Alarms

6.1 Related Counters

Table 6-1 Assignment counters

Counter ID What It Counts

C100460050 The count of Assignment using FULL IP A-Interface

C100460051 The count of Assignment using PCM over IP A-Interface

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 37

 ZGO-05-04-003 A Over IP

The count of Assignment Failure caused by "Requested Codec Type or

C100460053
Codec Configuration not supported"

The count of Assignment Failure caused by "Requested Codec Type or

C100460054
Codec Configuration unavailable"

The count of Assignment Failure caused by "Requested A-Interface

C100460055
Type not supported"

The count of Assignment Failure caused by "Requested A-Interface

C100460056
Type unavailable"

The count of Assignment Failure caused by "Call Identifier already

C100460057
allocated"

The count of Assignment Failure caused by "Requested Redundancy

C100460058
Level not supported"

Table 6-2 Call drop counters

Counter ID What It Counts

C100470089 The Count of Drop Call caused by "IP Resource Reset"

Table 6-3 Handover cause counters

Counter ID What It Counts

C100490037 Number of TCH/F handover attempts due to MSC request

C100490060 Number of TCH/H handover attempts due to MSC request

Table 6-4 TCH/F counters

Counter ID What It Counts

Number of TCH/F allocation failure due to request AIPB resource failure
C100430106
for assignment (speech version1)

Number of TCH/F allocation failure due to request UDP port failure for
C100430107
assignment (speech version1)

Number of TCH/F allocation failure due to AIPB connection failure for

C100430108
assignment (speech version1)

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 38

 ZGO-05-04-003 A Over IP

Number of TCH/F allocation failure due to request AIPB resource failure

C100430109
for handover (speech version1)

Number of TCH/F allocation failure due to request UDP port failure for
C100430110
handover (speech version1)

Number of TCH/F allocation failure due to AIPB connection failure for

C100430111
handover (speech version1)

Number of TCH/F allocation failure due to request AIPB resource failure

C100430112
for assignment (speech version2)

Number of TCH/F allocation failure due to request UDP port failure for
C100430113
assignment (speech version2)

Number of TCH/F allocation failure due to AIPB connection failure for

C100430114
assignment (speech version2)

Number of TCH/F allocation failure due to request AIPB resource failure

C100430115
for handover (speech version2)

Number of TCH/F allocation failure due to request UDP port failure for
C100430116
handover (speech version2)

Number of TCH/F allocation failure due to AIPB connection failure for

C100430117
handover (speech version2)

Number of TCH/F allocation failure due to request AIPB resource failure

C100430118
for assignment (speech version3)

Number of TCH/F allocation failure due to request UDP port failure for
C100430119
assignment (speech version3)

Number of TCH/F allocation failure due to AIPB connection failure for

C100430120
assignment (speech version3)

Number of TCH/F allocation failure due to request AIPB resource failure

C100430121
for handover (speech version3)

Number of TCH/F allocation failure due to request UDP port failure for
C100430122
handover (speech version3)

Number of TCH/F allocation failure due to AIPB connection failure for

C100430123
handover (speech version3)

Number of TCH/F allocation failure due to request AIPB resource failure

C100430124
for assignment (data)

Number of TCH/F allocation failure due to request UDP port failure for
C100430125
assignment (data)

Number of TCH/F allocation failure due to AIPB connection failure for

C100430126
assignment (data)

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 39

 ZGO-05-04-003 A Over IP

Number of TCH/F allocation failure due to request AIPB resource failure

C100430127
for handover (data)

Number of TCH/F allocation failure due to request UDP port failure for
C100430128
handover (data)

Number of TCH/F allocation failure due to AIPB connection failure for

C100430129
handover (data)

Table 6-5 TCH/H counters

Counter ID What It Counts

Number of TCH/H allocation failure due to request AIPB resource failure
C100440106
for assignment (speech version1)

Number of TCH/H allocation failure due to request UDP port failure for
C100440107
assignment (speech version1)

Number of TCH/H allocation failure due to AIPB connection failure for

C100440108
assignment (speech version1)

Number of TCH/H allocation failure due to request AIPB resource failure

C100440109
for handover (speech version1)

Number of TCH/H allocation failure due to request UDP port failure for
C100440110
handover (speech version1)

Number of TCH/H allocation failure due to AIPB connection failure for

C100440111
handover (speech version1)

Number of TCH/H allocation failure due to request AIPB resource failure

C100440112
for assignment (speech version2)

Number of TCH/H allocation failure due to request UDP port failure for
C100440113
assignment (speech version2)

Number of TCH/H allocation failure due to AIPB connection failure for

C100440114
assignment (speech version2)

Number of TCH/H allocation failure due to request AIPB resource failure

C100440115
for handover (speech version2)

Number of TCH/H allocation failure due to request UDP port failure for
C100440116
handover (speech version2)

Number of TCH/H allocation failure due to AIPB connection failure for

C100440117
handover (speech version2)

Number of TCH/H allocation failure due to request AIPB resource failure

C100440118
for assignment (speech version3)

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 40

 ZGO-05-04-003 A Over IP

Number of TCH/H allocation failure due to request UDP port failure for
C100440119
assignment (speech version3)

Number of TCH/H allocation failure due to AIPB connection failure for

C100440120
assignment (speech version3)

Number of TCH/H allocation failure due to request AIPB resource failure

C100440121
for handover (speech version3)

Number of TCH/H allocation failure due to request UDP port failure for
C100440122
handover (speech version3)

Number of TCH/H allocation failure due to AIPB connection failure for

C100440123
handover (speech version3)

Number of TCH/H allocation failure due to request AIPB resource failure

C100440124
for assignment (data)

Number of TCH/H allocation failure due to request UDP port failure for
C100440125
assignment (data)

Number of TCH/H allocation failure due to AIPB connection failure for

C100440126
assignment (data)

Number of TCH/H allocation failure due to request AIPB resource failure

C100440127
for handover (data)

Number of TCH/H allocation failure due to request UDP port failure for
C100440128
handover (data)

Number of TCH/H allocation failure due to AIPB connection failure for

C100440129
handover (data)

Table 6-6 BSSMAP message counters

Counter ID What It Counts

C100610078 The count of Sending INTERNAL HANDOVER REQUIRED

C100610079 The count of Receiving INTERNAL HANDOVER COMMAND

C100610080 The count of Receiving INTERNAL HANDOVER REJECT

C100610081 The count of Receiving INTERNAL HANDOVER ENQUIRY

C100610082 The count of Sending UL RESET IP RESOURCE

C100610083 The count of Sending UL RESET IP RESOURCE ACKOWNLEDGE

C100610084 The count of Receiving DL RESET IP RESOURCE

C100610085 The count of Receiving DL RESET IP RESOURCE ACKOWNLEDGE

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 41

 ZGO-05-04-003 A Over IP

Table 6-7 Terrestrial resource availability measurement counters

Counter ID What It Counts

C100640006 Mean number of available UDP port

C100640007 Mean number of unavailable UDP port

C100640008 Number of allocation AIPB board success

C100640009 Number of allocation AIPB board failure

C100640010 Maximum number of seizure UDP port

C100640011 Number of successful one time request UDP port to AIPB

C100640012 Number of successful two time request UDP port to AIPB

C100640013 Number of successful three time request UDP port to AIPB

C100640014 Number of failure request UDP port to AIPB

C100640015 Seizure duration of UDP port

C100640016 The times of User Plane transport without RTP multiplexing

C100640017 The times of RTP multiplexing applied without RTP header compression

C100640018 The times of RTP multiplexing applied with RTP header compression

C100640019 Mean number of busy trunk circuits

C100640020 Mean number of seizure UDP port

6.2 Related Alarms

Table 6-8 Alarm list

NAF Alarm MINOS Alarm

NE Alarm Code Alarm Name
Code Code

GUP board
18915585 315 198087505
connection failure

Board's network port

18915586 307 198087513
load alarm

SCTP connection
8417537 566 198066026
interruption

Opposite-end port
5395 323 198005395
abnormal

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 42

 ZGO-05-04-003 A Over IP

DSP resource
5399 356 198005399
unavailable

DSP automatically
5655 315 198005655 detecting abnormality
and reporting

DSP resetting
5700 198005700
abnormally

M3UA office
8400384 566 198066014
unavailable

SCTP congestion
8402688 308 198066018
alarm

8402690 566 198066019 SCTP disconnection

Control-plane
communication
8393985 60 198066003 between the board
and the home module
is abnormal

7 Abbreviation
None

8 Reference Document
1. ZXG10 iBSC(V6.20.60) Base Station Controller Performance Counter Reference

2. ZXG10 iBSC(V6.20.60) Base Station Controller IPA Control Plane Design Solution

3. ZXG10 iBSC(V6.20.60) Base Station Controller IPA User Plane Design Solution

4. ZXG10 BSS(R9.1+) Version Package Test Procedure

ZTE Confidential Proprietary © 2010 ZTE CORPORATION. All rights reserved. 43