Huawei - Configuring Signaling Transport Data

HUAWEI MSOFTX3000
Configuration Guide Contents
Contents
6 Configuring Signaling Transport Data..................................................................................6-1

6.1 Configuring SCTP Data ................................................................................................................................6-2
6.1.1 Background Information ......................................................................................................................6-2
6.1.2 Setting SCTP Parameters .....................................................................................................................6-3
6.2 Configuring M2UA Signaling Data ..............................................................................................................6-6
6.2.1 Background Information ......................................................................................................................6-6
6.2.2 Configuration Overview ......................................................................................................................6-9
6.2.3 Adding Embedded SG........................................................................................................................ 6-11
6.2.4 Adding M2UA Linkset.......................................................................................................................6-12
6.2.5 Adding M2UA Link ...........................................................................................................................6-13
6.3 Configuring M3UA Data.............................................................................................................................6-15
6.3.1 Background Information ....................................................................................................................6-15
6.3.2 Overview of Configuration ................................................................................................................6-16
6.3.3 Adding M3UA Local Entity...............................................................................................................6-20
6.3.4 Adding M3UA Destination Entity......................................................................................................6-21
6.3.5 Adding M3UA Additional Destination Service (Optional) ................................................................6-24
6.3.6 Adding M3UA Linkset.......................................................................................................................6-25
6.3.7 Adding M3UA Link ...........................................................................................................................6-27
6.3.8 Adding M3UA Route .........................................................................................................................6-29
6.4 Configuring IUA Data.................................................................................................................................6-30
6.4.2 Configuration Overview ....................................................................................................................6-31
6.4.3 Adding Embedded SG........................................................................................................................6-33
6.4.4 Adding IUA Linkset...........................................................................................................................6-34
6.4.5 Adding IUA link.................................................................................................................................6-35
6.5 Configuring DSS1 Signaling Data ..............................................................................................................6-37
6.5.2 Configuration Overview ....................................................................................................................6-37
6.5.3 Adding PRA link ................................................................................................................................6-39
6.6 Configuring MTP Data................................................................................................................................6-41
6.6.1 Related Concepts ...............................................................................................................................6-41
6.6.2 Overview............................................................................................................................................6-43
Issue 09 (2007-05-20) Huawei Technologies Proprietary i

HUAWEI MSOFTX3000
Contents Configuration Guide
6.6.3 Adding MTP Destination Signaling Point..........................................................................................6-46

6.6.4 Adding MTP Linkset..........................................................................................................................6-48
6.6.5 Adding MTP Link ..............................................................................................................................6-49
6.6.6 Adding MTP Route ............................................................................................................................6-52
6.7 Configuring ATM Signaling Data ...............................................................................................................6-53
6.7.3 Setting ATM Link Type (Optional) ....................................................................................................6-59
6.7.4 Adding IMA Group ............................................................................................................................6-60
6.7.5 Adding IMA Link...............................................................................................................................6-61
6.7.6 Adding UNI Link ...............................................................................................................................6-62
6.7.7 Adding PVC Link ..............................................................................................................................6-63
6.7.8 Modifying SAAL Link Parameter (Optional) ....................................................................................6-65
6.8 Configuring MTP3B Data...........................................................................................................................6-69
6.8.2 Overview............................................................................................................................................6-69
6.8.3 Setting MTP3B OSP (Optional).........................................................................................................6-72
6.8.4 Adding MTP3B DSP..........................................................................................................................6-73
6.8.5 Adding MTP3B Linkset .....................................................................................................................6-74
6.8.6 Adding MTP3B Link .........................................................................................................................6-75
6.8.7 Adding MTP3B Route .......................................................................................................................6-76
6.9 Configuring SCCP Data ..............................................................................................................................6-77
6.9.3 Adding SCCP Destination Signaling Point ........................................................................................6-82
6.9.4 Adding Originating Address Format Translation (Optional)..............................................................6-83
6.9.5 Adding SCCP Subsystem Number.....................................................................................................6-85
6.9.6 Adding SCCP New GT (Optional).....................................................................................................6-87
6.9.7 Adding SCCP Global Title .................................................................................................................6-88
6.9.8 Adding SCCP Shielding Policy (Optional) ........................................................................................6-91
ii Huawei Technologies Proprietary Issue 09 (2007-05-20)

HUAWEI MSOFTX3000
Configuration Guide Figures
Figures
Figure 6-1 Bit structure of TOS..........................................................................................................................6-6

Figure 6-2 SIGTRAN protocol model................................................................................................................6-7
Figure 6-3 M2UA application model..................................................................................................................6-8
Figure 6-4 Relationship between data tables .................................................................................................... 6-11
Figure 6-5 Application mode of M3UA (non-peer network mode)..................................................................6-15
Figure 6-6 Application mode of M3UA (peer network mode) .........................................................................6-15
Figure 6-7 Parameter referencing relationship .................................................................................................6-19
Figure 6-8 IUA application model....................................................................................................................6-30

Figure 6-9 Relationship between data tables ....................................................................................................6-33
Figure 6-10 Relationship between data tables ..................................................................................................6-39
Figure 6-11 Parameter referencing relationship ...............................................................................................6-45

Figure 6-12 Structure of the SAAL protocol stack...........................................................................................6-54
Figure 6-13 Formats of the ATM cell ...............................................................................................................6-55
Figure 6-14 Introduction to links of the ATM signaling...................................................................................6-56

Figure 6-17 Format of the calling/called address field in an SCCP message ...................................................6-78
Issue 09 (2007-05-20) Huawei Technologies Proprietary iii

HUAWEI MSOFTX3000
Tables Configuration Guide
Tables
Table 6-1 Input parameters required in M2UA signaling data............................................................................6-9

Table 6-2 Output parameters defined in M2UA signaling data ..........................................................................6-9
Table 6-3 Preparations ........................................................................................................................................6-9
Table 6-4 Configuration steps...........................................................................................................................6-10
Table 6-5 Input parameter needed by M3UA data............................................................................................6-16
Table 6-6 Output parameter defined by M3UA data.........................................................................................6-17
Table 6-7 Checking items for preparations.......................................................................................................6-17
Table 6-8 Configuration steps...........................................................................................................................6-18

Table 6-9 Input parameters required in IUA signaling data..............................................................................6-31
Table 6-10 Output parameters defined in IUA signaling data...........................................................................6-31
Table 6-11 Preparations ....................................................................................................................................6-31

Table 6-12 Configuration steps.........................................................................................................................6-32
Table 6-13 Input parameters required in DSS1 signaling data .........................................................................6-37
Table 6-14 Output parameters defined in DSS1 signaling data ........................................................................6-38

Table 6-16 Configuration step ..........................................................................................................................6-38
Table 6-17 Input parameters referencing relationship ......................................................................................6-43
Table 6-18 Output parameter referencing relationship .....................................................................................6-44

Table 6-21 Input parameters needed by ATM signaling data............................................................................6-57
Table 6-22 Input parameters required by ATM signaling data..........................................................................6-57

iv Huawei Technologies Proprietary Issue 09 (2007-05-20)

HUAWEI MSOFTX3000
Configuration Guide Tables
Table 6-27 Input parameters referencing relationship ......................................................................................6-70
Table 6-28 Output parameter referencing relationship .....................................................................................6-70

Table 6-31 Meanings of the bits in the address indicator field.......................................................................6-78
Table 6-32 Input parameters required by SCCP data........................................................................................6-79
Table 6-33 Output parameters defined by SCCP data ......................................................................................6-80
Issue 09 (2007-05-20) Huawei Technologies Proprietary v

HUAWEI MSOFTX3000
Configuration Guide 6 Configuring Signaling Transport Data
6 Configuring Signaling Transport Data
About This Chapter
The following table lists the contents of this chapter.
Section Describes
6.1 Configuring SCTP Data This section describes how to configure the SCTP data of
the MSOFX3000.
6.2 Configuring M2UA This section describes how to configure the M2UA
Signaling Data signaling data of the MSOFX3000.
6.3 Configuring M3UA Data This section describes how to configure the M3UA data of
the MSOFX3000.
6.4 Configuring IUA Data This section describes how to configure the IUA data of
the MSOFX3000.
6.5 Configuring DSS1 This section describes how to configure the DSS1
Signaling Data signaling data of the MSOFX3000.
6.6 Configuring MTP Data This section describes how to configure the MTP data of
the MSOFX3000.
6.7 Configuring ATM This section describes how to configure the ATM data of
Signaling Data the MSOFX3000.
6.8 Configuring MTP3B Data This section describes how to configure the MTP3B data
of the MSOFX3000.
6.9 Configuring SCCP Data This section describes how to configure the SCCP data of
the MSOFX3000.
Issue 09 (2007-05-20) Huawei Technologies Proprietary 6-1

HUAWEI MSOFTX3000
6 Configuring Signaling Transport Data Configuration Guide
6.1 Configuring SCTP Data

6.1.1 Background Information
Basic Concept
The Stream Control Transmission Protocol (SCTP) is in the transport layer. It is based on IP and
mainly provides highly efficient and reliable transmission service for the message transfer part
2-user adaptation layer (M2UA), M3UA, integrated services digital network Q.921-user
adaptation layer (IUA), H.248 and bearer independent call control (BICC) signaling on the
connectionless IP network.
In the IP network, messages are usually exchanged through the User Datagram Protocol (UDP)
or Transmission Control Protocol (TCP). Both of the protocols, however, are not satisfied,
because UDP cannot make sure the reliability of the transmission and TCP cannot guarantee the
high efficiency and security of the transmission. SCTP integrates the advantages of the two
protocols, and becomes a reliable transmission protocol based on the connectionless and
unreliable IP packet network.
Station
An SCTP station is the logical receiver or sender of SCTP packets. On a multi-home host, an
SCTP station can be represented by the peer host as either of the following:
z A group of qualified destination addresses which SCTP packets can be sent.
z A group of qualified source addresses which SCTP packets can be received.
All transmission addresses used by an SCTP station must share the same port number. Different
IP addresses are however, allowed.
Association
An SCTP association is a mapping between two SCTP stations. It includes two SCTP stations
and the protocol state information containing verification label and serial number of
transmission. An SCTP association can be uniquely identified by a transmission address of an
SCTP station involved in the association. SCTP prescribes that between two SCTP stations,
only one association must be created at any time.
An SCTP association is defined by the transmission addresses of the two SCTP stations. When
SCTP works based on IP, the transmission address is defined by the combination of IP addresses
and SCTP port numbers. Therefore, an SCTP association can be uniquely identified by defining
local IP address, local SCTP port number, peer IP address, and peer SCTP port number. In the
MSOFTX3000, an SCTP association can be treated as an M2UA link, an M3UA link, an IUA
link, an H.248 link or a BICC link.
Stream
The stream is a specific term in SCTP. In an SCTP association, a stream means a series of
messages to be sent to the upper layer protocol in sequence. In the same stream, messages
should be submitted in order. Strictly, a stream is a one-way logical channel from one station to
another in an SCTP association.
6-2 Huawei Technologies Proprietary Issue 09 (2007-05-20)

HUAWEI MSOFTX3000
An SCTP association can consist of several separate one-way streams. They are identified with
stream ID and each of them can send data independently without being affected by other
streams. An SCTP association can contain several streams. The number of available streams is
decided after the two stations negotiate when creating an SCTP association.
Path
The path is a route along which SCTP packets are sent from one station to the specific
destination address of the peer station. If packets are sent to different destination addresses of
the peer station, you do not have to configure different paths accordingly.
6.1.2 Setting SCTP Parameters

Related Commands
Command Function
SET SCTPPARA To set an SCTP parameter

LST SCTPPARA To list SCTP parameters
Configuration Description
In the MSOFTX3000, SCTP carries different types of SCTP user layer signaling such as M2UA,
M3UA, IUA, H.248 and BICC. After you set parameters with SET SCTPPARA, the results
affects all SCTP associations in the MSOFTX3000. Before modifying SCTP parameters, read
descriptions of parameters in the command and relevant precautions carefully.
Note that the initial values are listed with LST SCTPPARA.
Parameter Description
Minimum RTO
It defines the minimum duration of the retransmission time-out (RTO) timer. Its value ranges
from 0 to 65534 (in millisecond). The initial value is 1000. The configuration principles are as
follows:
z The minimum of RTO is shorter than or equal to the maximum of RTO.
z The initial value of RTO is longer than or equal to the minimum of RTO and shorter than
or equal to the maximum of RTO.
Maximum RTO
It defines the maximum duration of the RTO timer. Its value ranges from 0 to 65534 (in
millisecond). The initial value is 3000. The configuration principles are as follows:
Initial RTO

HUAWEI MSOFTX3000
It defines the initial duration of the RTO timer. Its value ranges from 0 to 65534 (in millisecond).
The initial value is 1000. The configuration principles are as follows:
RTO alpha value
It defines the alpha parameter of the RTO timer. Its value ranges from 0 to 100 (in unit of
percentage). The initial value is 12. The configuration principles are as follows:
z The value of RTO alpha is shorter than or equal to that of RTO beta.
z RTO alpha is used to calculate and update the duration of the RTO timer. For details, see
relevant contents in RFC2960.
RTO beta value
It defines the beta parameter of the RTO timer. Its value ranges from 0 to 100 in unit of
percentage. The initial value is 25. The configuration principles are as follows:
z The value of RTO alpha is shorter than or equal to that of RTO beta.
z RTO beta is used to calculate and update the duration of the RTO timer. See relevant
contents in RFC2960 for details.
Heartbeat interval
If an SCTP association does not send data to a specific IP address within a certain period of time,
it sends heartbeat messages to the IP address to check whether the IP address is activated. The
parameter specifies the interval between two heartbeat messages sent from the MSOFTX3000
to the remote IP address. Its value ranges from 0 to 65534 (in millisecond). The initial value is
2000.
Maximum number of association retransmissions
It specifies the maximum number of retransmitting messages continuously on an SCTP
association. For example, if the parameter is set to 10, when a message is retransmitted
continuously over ten times on an SCTP association, the MSOFTX3000 considers the peer
SCTP station unreachable. Then the MSOFTX3000 closes the SCTP association automatically
and informs SCTP user layers, such as M2UA, M3UA, IUA, H.248 and BICC, that the SCTP
association is unavailable. The value ranges from 0 to 254. The initial value is 10. The
configuration principles are as follows:
z The maximum number of association retransmissions must be smaller than or equal to the
sum of maximum number of path retransmissions of all remote IP addresses on an SCTP
association.
z The maximum number of association retransmissions must be bigger than or equal to the
maximum number of path retransmissions.
Maximum number of path retransmissions
It specifies the maximum number of retransmitting messages continuously to a specific IP
address on an SCTP association. For example, if the parameter is set to 5, when a message is
retransmitted continuously to a specific IP address over five times on an SCTP association, the
MSOFTX3000 considers the peer SCTP station unreachable. Then the MSOFTX3000 closes
the SCTP association automatically and informs SCTP user layers, such as M2UA, M3UA,
IUA, H.248 and BICC, that the SCTP association is unavailable. The value ranges from 0 to
254. The initial value is 5.

HUAWEI MSOFTX3000
Note that if messages or heart beat signals sent from the MSOFTX3000 to a specified IP
address through the assumed unavailable SCTP association are acknowledged by the peer end,
the MSOFTX3000 assumes that the peer end is available and enables the SCTP association.
Then it notifies SCTP user layer that the association is available.
No congestion threshold
When an SCTP association is congested, this parameter defines the threshold at which the
signaling load of the SCTP association becomes decongested. Its value ranges from 0 to 100 in
unit of percentage. The initial value is 40. In actual configuration, No congestion threshold
must be lower than Low congestion threshold, which must be lower than High congestion
threshold.
Threshold is the percentage of the occupied signaling sending buffer. For example, if the
parameter is set to 40, an SCTP association is congested, and the ratio of subsequent occupied
send buffer to the whole send buffer is lower than 40%, the SCTP association is decongested.
Low congestion threshold
It defines the low congestion threshold. If the value of the parameter is below or equal to the
threshold, the signaling load of an SCTP association is considered to be in the low congested
state. Its value ranges from 0 to 100 in unit of percentage. The initial value is 60. In actual
configuration, No congestion threshold must be lower than Low congestion threshold, which
must be lower than High congestion threshold.
Threshold is the percentage of occupied signaling send buffer to the whole send buffer. For
example, if Low congestion threshold is set to 60, High congestion threshold is set to 80, and
the ratio of occupied send buffer to the whole send buffer is between 60% and 80%, the system
considers the SCTP association is in the low congested state.
High congestion threshold
It defines the high congestion threshold. If the value of the parameter is below or equal to the
threshold, the signaling load of an SCTP association is considered to be in the high congested
state. Its value ranges from 0 to 100 in unit of percentage. The initial value is 80. In actual
configuration, No congestion threshold must be lower than Low congestion threshold, which
must be lower than High congestion threshold.
Threshold is the percentage of occupied signaling send buffer to the whole send buffer. For
example, if the parameter is set to 80, when the ratio of occupied send buffer to the whole send
buffer is higher than 80%, the system considers the SCTP association is in a high congested
state.
Calculate checksum when sending message
It indicates whether the MSOFTX3000 calculates checksum when sending SCTP messages.
The initial value is Yes. When the parameter is set to No, Check checksum when receiving
message in the peer SCTP station must be set to No, too. Otherwise, the SCTP association
cannot be created.
Check checksum when receiving message
It indicates whether the MSOFTX3000 checks the checksum field for received SCTP messages.
The initial value is Yes.
Checksum algorithm
It specifies which checksum algorithm is supported by SCTP at the MSOFTX3000 side, the
ADLER32 algorithm or the CRC32 algorithm. The initial value is CRC32. Both ends of an

HUAWEI MSOFTX3000
SCTP association must adopt the same checksum algorithm. Otherwise, SCTP messages are
discarded by the receiving station because of incorrect checksum.
The set of the parameter affects all SCTP associations in the MSOFTX3000. Therefore, when
the MSOFTX3000 interworks with the media gateway (MGW) or the imbedded signaling
gateway (SG), if the default checksum algorithms supported by the two ends are different, it is
recommended to modify the checksum algorithm supported by the MGW or imbedded SG to
solve the problem.
Type of service
When the MSOFTX3000 uses the header of an IP data packet to encapsulate an SCTP message
capsule, the parameter indicates the value of type of service (TOS) in the header. The default
value is NONE.
TOS is an 8-bit field in the header of an IP data packet. It controls the routing policy when a
router forwards IP packets. The bit structure of TOS is as shown in Figure 6-1.
Figure 6-1 Bit structure of TOS
Priority sub-
TOS sub-field Unused
field
7 6 5 4 3 2 1 0
The priority sub-field occupies three bits and is not used at present. But all the three bits must be
set to 0. The TOS sub-field occupies four bits. The meanings of the four bits are as follows:
z Bit 1: minimum costs
z Bit 2: highest reliability
z Bit 3: maximum throughput
z Bit 4: minimum time delay
Among the four bits, at most one can be set to 1. If all of them are set to 0, the service is an
ordinary service. In practice, TOS controls a router in the IP bearer network to scatter different
services when the router forwards IP packets. To implement the scattering function of TOS,
relevant pieces of equipment such as the MSC server, router and MGW must also support
identifying TOS in IP packets.
6.2 Configuring M2UA Signaling Data

Basic Concepts
The Signaling Transport (SIGTRAN) protocol supports the transmission of the Switched
Circuit Network (SCN) signaling through the IP network. SIGTRAN is used by the inter-layer
standardized primitive interface defined in the hierarchical model of the SCN signaling
protocol. In this way, the existing SCN signaling can be used without any change. At the same
time, taking the standardized IP transport protocol as the transmission bottom layer, the
SIGTRAN protocol can meet the specific requirements of the SCN signaling transport. In terms
of functions, the protocol is divided into two types:

HUAWEI MSOFTX3000
z Signaling transport protocol: The protocol adopts the Stream Control Transmission
Protocol (SCTP) defined by the Internet Engineering Task Force (IETF). It is used by the
SCN signaling to keep the transport efficient and reliable in the IP network.
z Signaling adaptation protocol: It is designed for the signaling of the SCN including the
M3UA, M2UA, M2PA, IUA, V5UA, and SUA protocol. Figure 6-2 shows the SIGTRAN
protocol model.
Figure 6-2 SIGTRAN protocol model
M3UA M2UA M2PA IUA V5UA SUA
SCTP
IP
MAC
M3UA: MTP3-user adaptation layer M2UA: MTP2-user adaptation layer

M2PA: MTP2-user peer-to-peer adaptation layer IUA: ISDN Q.921-user adaptation layer
V5UA: V5-user adaptation layer SUA: SCCP-user adaptation layer
SCTP: Stream Control Transmission Protocol IP: Internet Protocol
MAC: Media Access Control
Signaling Gateway
The signaling gateway (SG), a signaling agent, connects the SCN and the IP network. It is used
to implement the translation and termination from the SCN signaling to the IP signaling. In the
actual networking, there are different types of SG.
z Independent SG: It is an independent device (such as the SG7000 of Huawei) for
implementing the conversion and adaptation between the SS7 and the M3UA protocols.
z Embedded SG: It is embedded in the media gateway (such as the UMG8900). In different
networking modes, the embedded SG can implement the conversion and adaptation
between the SS7 and the M2UA protocols, the SS7 and the M3UA protocols, and the
DSS1 and the IUA protocols.
Four Parameters for Identifying an SCTP Association

In SIGTRAN, an SCTP association is uniquely identified by the following four parameters:
z Local IP address
z Local port number
z Peer IP address
z Peer port number
In the MSOFTX3000, the SCTP association can be an M2UA link, M3UA link, IUA link,
H.248 link or BICC link. Add one of the links as follows:

HUAWEI MSOFTX3000
z Local IP address, Local SCTP port number, Peer IP address, and Peer SCTP port
number are parameters used for interconnecting the local and peer ends, and should be
negotiated between both ends.
z When Local IP address and Peer IP address have been set, the link between two
signaling devices is determined by Local SCTP port number and Peer SCTP port
number. If Peer SCTP port number of each link are the same, Local SCTP port
number should be different. Conversely, if Local SCTP port number of each link are the
same, Peer SCTP port number should be different.
z For a specific protocol, if the MSOFTX3000 is the client, it is suggested that you should
set Peer SCTP port number of each link to the same value, and Local SCTP port
number to different values. The numbers should be planned together.
z For a specific protocol, if the MSOFTX3000 is the server, it is suggested that you should
set Local SCTP port number of each link to the same value, and Peer SCTP port
number to different values. The numbers should be planned together.
Client/Server Working Mode for SCTP Associations

SCTP, with associations structured in a Client/Server working mode, is the transport layer of
SIGTRAN. To ensure the normal functioning of SIGTRAN, it is suggested that you should
learn the working mode of a variety of devices in SCTP associations. Typically, a device acting
as an SG is usually configured as a server in SCTP associations, and other devices
interconnected to the SG must be configured as a client in SCTP associations.
When the MOSFTX3000 is interconnected with M2UA embedded SG (such as the UMG8900
of Huawei), the MSOFTX3000 can only be the client (you cannot change it). In this case, the
UMG8900 is the server.
M2UA Application Model

The M2UA protocol defined by RFC3331 adopts the SCTP protocol as a transport protocol. It
sends MTP3 over the IP network. MTP3 is the user layer of MTP2 in SS7. The M2UA protocol
is used for transporting signaling between the SG and the media gateway controller (MGC). See
Figure 6-3.
Figure 6-3 M2UA application model
MTP link M2UA link

SP SG MGC
BSSAP
BSSAP
TCAP
TCAP
SCCP
SCCP
MTP3
MTP3
M2UA M2UA
MTP2 MTP2
SCTP SCTP
MTP1 MTP1 IP IP

HUAWEI MSOFTX3000
In Figure 6-3, the M2UA SG acts as a device for cross-connecting signaling. Only the transport
method of the level-2 link is changed.
6.2.2 Configuration Overview

Relationship Description
The M2UA signaling data is used for interconnecting the MSOFTX3000 and the embedded SG
(such as the UMG8900 of Huawei). The data related to the M2UA link defines Local IP
address, Peer IP address, Local SCTP port number, Peer SCTP port number, service
mode of the link and so on.
During configuration, the M2UA signaling data needs to use key parameters defined by
hardware data and MGW data. The key parameters are Module number of the WBSG, IP
address of the FE port and MGW index. The referencing relationship is shown in Table 6-1.
Table 6-1 Input parameters required in M2UA signaling data

Parameter Defined in Source data type Referenced in
Module number of the ADD BRD Hardware Data ADD M2LNK

WBSG
IP address of the FE port ADD FECFG Hardware Data ADD M2LNK
MGW index ADD MGW Media gateway data ADD ESG
The M2UA linkset index is a key parameter defined by the M2UA signaling data. The
parameter is used during the configuration of the MTP signaling data. The referencing
relationship between parameters of the M2UA and the MTP is shown in Table 6-2.
Table 6-2 Output parameters defined in M2UA signaling data

Parameter Defined in Referenced in Destination data type
M2UA linkset index ADD M2LKS ADD N7LNK MTP signaling data
Preparations Description
Before setting the M2UA signaling data, make sure that all preparations are done as specified in
Table 6-3.
Table 6-3 Preparations

SN Item Remark
1 IP address of the embedded SG A parameter for interconnecting the

MSOFTX3000 and the embedded SG.

HUAWEI MSOFTX3000
SN Item Remark
2 Local SCTP port number of each A parameter for interconnecting the

M2UA link (at the client side) MSOFTX3000 and the embedded SG. It
should be defined together with the M3UA
link and the local SCTP port number of the
IUA link.
3 Peer SCTP port number of each A parameter for interconnecting the
M2UA (at the server end) MSOFTX3000 and the embedded SG.
Configuration Steps
Table 6-4 lists the steps for configuring M2UA signaling data.
Table 6-4 Configuration steps

Step Description Command
1 Add an embedded SG. ADD ESG

2 Add an M2UA linkset. ADD M2LKS
3 Add an M2UA link. ADD M2LNK
Relationship Between Data Tables in Database

Figure 6-4 shows the relationship between data tables for referencing parameters when you set
the M2UA signaling data.

HUAWEI MSOFTX3000
Figure 6-4 Relationship between data tables
ADD ESG
Signaling gateway ID
Signaling gateway name
MGW ID
ADD M2LKS
M2UA linkset index
Linkset name
ADD M2LNK
WBSG module number
Link number
M2UA linkset index
6.2.3 Adding Embedded SG

Related Commands
Command Function
ADD ESG To add an embedded SG

RMV ESG To remove an embedded SG
MOD ESG To modify an embedded SG
LST ESG To list embedded SGs
It defines an embedded SG (such as the UMG8900 of Huawei) in the configuration database of
the MSOFTX3000. The SG adopts one or more than one of the following protocols: the M2UA,
M3UA and IUA. The value range is from 0 to 511.
It defines the name of an SG. The parameter is a string of characters to describe an embedded
SG.
MGW ID

HUAWEI MSOFTX3000
It defines an MGW where the SG is embedded. The parameter should be defined by ADD
MGW before being used here.
6.2.4 Adding M2UA Linkset

Related Commands
Command Function
ADD M2LKS To add an M2UA linkset

RMV M2LKS To remove an M2UA linkset
MOD M2LKS To modify an M2UA linkset
LST M2LKS To list M2UA linksets
M2UA linkset index
It defines an M2UA linkset in the configuration database of the MSOFTX3000. The value
range is from 0 to 65534.
M2UA Linkset name
It defines the name of an M2UA linkset. The parameter is a string of characters to describe an
M2UA linkset.
It defines which embedded SG the M2UA links belong to. The parameter should be defined by
ADD ESG before being used here.
Traffic mode
As one of the parameters for the MSOFTX3000 to interconnect with an embedded SG (such as
the UMG8900 of Huawei), it specifies the service mode used by an M2UA linkset. It is set to
Load share by default. There are two traffic modes:
z Override mode: N+1 backup mode. In this mode, only one link in a linkset is activated,
and the other links are standby. When the activated link is faulty, one standby link will be
activated immediately for traffic transmission.
z Load-sharing mode: In this mode, all links in a linkset are activated and they share load.
When the MSOFTX3000 interconnects with the embedded SG, the linkset for interworking
must remain the same traffic mode at both ends (load-sharing mode is recommended);
otherwise, M2UA links cannot work normally.
Interface ID type
the UMG8900 of Huawei), it specifies the interface ID type of MTP links carried on an M2UA
linkset (you can refer to ADD N7LNK). By default, it is Integer. You can set it to Text as
required, but it must be consistent with the embedded SG.

HUAWEI MSOFTX3000
6.2.5 Adding M2UA Link

Related Commands
Command Function
ADD M2LNK To add an M2UA link

RMV M2LNK To remove an M2UA link
LST M2LNK To list M2UA links
WBSG module number
It defines the module number of the WBSG to process the message of the M2UA link protocol.
The parameter should be defined by ADD BRD before being used here.
Link number
It defines the logical number of the M2UA link in the related WBSG module. The value range is
from 0 to 31. In the same WBSG module, all M2UA links must be numbered universally. That
is, one WBSG module supports up to 32 M2UA links.
M2UA linkset index
It defines the M2UA linkset to which M2UA links belong. It must be defined by ADD M2LKS
before being used here.
For the M2UA links in one M2UA linkset, all of them can be set only on one WBSG. To ensure
the reliability of M2UA links, the M2UA links from the MSOFTX3000 to the same embedded
SG should be allocated to different WBSGs. Thus, you must assign the M2UA links on
different WBSGs to different M2UA linksets.
Maximum incoming flow of SCTP association
It defines the maximum number of SCTP streams in each M2UA protocol message received by
the MSOFTX3000 when an SCTP association is established. Usually, this parameter is 1 plus
the number of the MTP links actually borne over M2UA links. It can also be the default value,
33. The actual number of streams received after an SCTP association is established is
negotiated between both ends.
Maximum outgoing flow of SCTP association
It defines the maximum number of SCTP streams in each M2UA protocol message sent by the
MSOFTX3000 when an SCTP association is established. Usually, this parameter is 1 plus the
number of the MTP links actually borne over M2UA link. It can also be the default value, 33.
The actual number of streams sent after an SCTP association is established is negotiated
between both ends.
Local port number
It is one of parameters for interconnecting the MSOFTX3000 and the embedded SG (such as
the UMG8900 of Huawei). It defines the SCTP port number used for M2UA messages at the
MSOFTX3000 side. The configuration principles for this port number are as follows:

HUAWEI MSOFTX3000
z The MSOFTX3000 is set to act as a client in the M2UA link. In this case, when there are
several M2UA links between the MSOFTX3000 and the embedded SG, the local port
numbers of each M2UA link cannot be the same.
z The M2UA, M3UA, IUA, H.248, and BICC protocols are all transported on the basis of
the SCTP, therefore, it is suggested that you should universally plan the ranges of local
SCTP port numbers for the links of different protocols before data configuration. Do not
assign the same port number to several links.
Local IP address1 and Local IP address2
Both Local IP address1 and Local IP address2 are the parameters for interconnecting the
MSOFX3000 and the embedded SG. These two parameters define the IP addresses of the FE
port used for dispatching M2UA messages at the MSOFTX3000. They must be defined by
ADD FECFG before being used here. Local IP address 1 is mandatory.
If the MSOFTX3000 is configured with more than one WIFM boards, you can specify Local IP
address 2. It aims at supporting the multi-homing function of the SCTP associations at the
MSOFTX3000 to improve the networking reliability of the system.
Peer port number
It is one of the parameters for interconnecting the MSOFTX3000 and the embedded SG. It
defines the SCTP port number used for M2UA messages at the embedded SG.
The MSOFTX3000 is set to act as a client in the M2UA link, so for the MSOFTX3000, the peer
end numbers for different M2UA links can be the same. For example, if the well-known port
number for M2UA is used at the embedded SG, the peer port numbers for different M2UA links
at the MSOFTX3000 can be the default value, 2904.
Peer IP address1, Peer IP address2
Both of them are parameters for interconnecting the MSOFTX3000 and the embedded SG.
They define the IP addresses of the embedded SG. Peer IP address 1 is mandatory.
If the embedded SG also supports the multi-homing function of the SCTP associations, you can
specify Peer IP address 2. It aims at supporting the multi-homing function of the SCTP
associations at the SG side to improve the networking reliability of the system.
Priority
It defines the routing priority for an M2UA link. The M2UA link with the highest priority is
chosen. A link is selected to convey signaling traffic only after there is no link with a higher
priority. The greater the value is, the lower the priority is. 0 indicates the highest priority..
Active/Standby flag
It defines the work state of an M2UA link in normal cases. The configuration of this parameter
is closely related to the traffic mode of the M2UA linkset.
z In the override traffic mode, only one M2UA link in the same linkset can be set to Active
and the other links must be set to Standby.
z In the load-sharing traffic mode, all the M2UA links in the same linkset must be set to
Active.

HUAWEI MSOFTX3000
6.3 Configuring M3UA Data

Basic Concepts
See section 6.2.1 "Background".
Application Mode of M3UA

M3UA is an MTP3 user adaptation protocol defined by RFC3332 and applies the SCTP as the
transmission protocol. M3UA can be applied to signals transmission between the signaling
gateway (SG) and the media gateway controller (MGC) as shown in Figure 6-5, or between
applications over IP as shown in Figure 6-6.
Figure 6-5 Application mode of M3UA (non-peer network mode)
MTP link M3UA link

SP SG MGC
RANAP RANAP
TCAP TCAP
SCCP SCCP
MTP3 MTP3 M3UA M3UA
MTP2 MTP2 SCTP SCTP
MTP1 MTP1 IP IP
Figure 6-6 Application mode of M3UA (peer network mode)
M3UA link
MGC MGC
MAP MAP
TCAP TCAP
SCCP SCCP
M3UA M3UA
SCTP SCTP
IP IP

HUAWEI MSOFTX3000
For two signaling devices applying SIGTRAN, if one is the application server (AS), the other is
the signaling gateway (SG), the networking mode is non-peer network mode. If the both
devices are ASs or SGs, the networking mode is peer network mode. In the SIGTRAN protocol
stack, M2UA and IUA supports only non-peer networking mode, but M3UA supports both peer
and non-peer networking mode.
M3UA Local Entity and Destination Entity

M3UA local entities and destination entities can be viewed as the mapping entities of SS7 local
signaling points and destination signaling points. The adjacent and non-adjacent destination
entities can be viewed as the extension entities of SS7 relative concepts. Therefore, the process
of configuring M3UA data is basically the same as that of configuring MTP data.
Link Selection Mask and Linkset Selection Mask

See section 6.6.1 "Related Concepts".
6.3.2 Overview of Configuration

Relationship Between Parameters
The M3UA data is one of the interworking data of the MSOFTX300. It defines related
information for the MSOFTX3000 to interconnect with embedded SG (for example, Huawei
UMG8900), independent SG (for example, Huawei SG7000), MSC server, HLR, and SCP. The
M3UA data includes signaling point codes of local entities, signaling point codes of destination
entities, local and peer IP addresses, local and peer SCTP port number, C/S working mode of
links, and traffic mode of links.
During the process of M3UA data configuration, parameters defined by hardware data and
office data must be used, including module number of the WBSG, IP address of FE port, and
local office signaling point code. For referencing relationship of the parameters, see Table 6-5.
Table 6-5 Input parameter needed by M3UA data

Name Defined by Source data type Referenced by
Module number of ADD BRD Hardware data ADD M3LNK

WBSG
IP address of FE ADD FECFG Hardware data ADD M3LNK
port
Signaling code of SET OFI / ADD Office data ADD M3LE
local office OFI
Parameters defined by M3UA data include signaling point code of local entities and of
destination entities. They are used during the process of configuring SCCP signaling data,
routing data, and trunk data. The referencing relationship of the parameters is shown in Table
6-6.

HUAWEI MSOFTX3000
Table 6-6 Output parameter defined by M3UA data
Name Defined by Referenced by Destination data
Signaling point ADD M3LE ADD SCCPDSP SCCP signaling data

code of local
entity ADD OFC Routing data
ADD AIETG Trunk data
ADD N7TG Trunk data
Signaling point ADD M3DE ADD SCCPDSP SCCP signaling data
code of local
entity ADD OFC Routing data
Signaling point ADD M3DE ADD N7TG Trunk data
code of local
entity
Preparations
Before configuring M3UA data, check the items listed in Table 6-7. .
Table 6-7 Checking items for preparations

SN Item Remarks
1 Signaling point code of local A parameter used for the interworking between
entity the MSOFTX3000 and M3UA signaling
equipments.
2 Signaling point code of A parameter used for interworking between the
destination entity MSOFTX3000 and M3UA signaling equipments.
3 IP address of destination entity A parameter used for interworking between the
MSOFTX3000 and M3UA signaling equipments.
4 Local SCTP port number of A parameter used for interworking between the
M3UA links (at client side) MSOFTX3000 and M3UA signaling equipments.
This port number should be planned and assigned
in a unified way with the local SCTP port
numbers for M2UA links, M3UA links, and IUA
links.
5 Peer SCTP port number of A parameter used for interworking between the
M3UA links (at server side) MSOFTX3000 and M3UA signaling equipments.
6 Routing context (optional) A parameter used for interworking between the
MSOFTX3000 and M3UA.

HUAWEI MSOFTX3000
Configuration Steps
Table 6-8 lists the general steps for configuring M3UA data.

1 Add an M3UA local entity. ADD M3LE

2 Add an M3UA destination entity. ADD M3DE
3 Add an M3UA additional destination service ADD M3DS
(optional).
4 Add an M3UA linkset. ADD M3LKS
5 Add an M3UA link. ADD M3LNK
6 Add an M3UA route. ADD M3RT
Parameter Referencing Relationship

Figure 6-7 illustrates the referencing relationship between key parameters used when you
configure M3UA data.

HUAWEI MSOFTX3000
Figure 6-7 Parameter referencing relationship
ADD M3LE
Local entity index
Local entity name
Network indicator
ADD M3DE
Destination entity
index
Local entity index
Destination entity
name
ADD M3DS
Additional service
index
Destination entity
index
Source signaling
point code
ADD M3LKS
Link set index
Link set name
Adjacent entity
index
ADD M3LNK
Module number of
WBSG
Link
number
Link set
index
ADD M3RT
Rout name
Destination entity
index
Link set index

HUAWEI MSOFTX3000
6.3.3 Adding M3UA Local Entity

Related Commands
Command Function
ADD M3LE To add an M3UA local entity

RMV M3LE To remove an M3UA local entity
MOD M3LE To modify an M3UA local entity
LST M3LE To list M3UA local entities
Local entity index
It defines an M3UA local entity in the configuration database of the MSOFTX3000. The value
range is from 0 to 253. The quantity of local entities to be configured depends on the number of
the local office signaling point codes of signaling borne over the M3UA.
For example, the MSOFTX3000 shows its presence in both international and national networks
with one signaling point code for the international network and four signaling point codes for
the national network.
z If the M3UA is used to bear signaling in both international and national networks, you
must define five local entities;
z If the MTP is used to bear signaling in the international network and the M3UA to bear
signaling in the national network, you must define four local entities.
Local entity name
It identifies a local entity. The value must be a character string.
Network indicator
It is a parameter set for the interworking between the MSOFTX3000 and the M3UA signaling
devices and defines the signaling network to which the signaling point code of the local entity
belongs. The signaling network may be the international network, the international reserved
network, the national network, or the national reserved network. The default value is National
network. It must be set same as the network indicator of the local office signaling point code
set by SET OFI/ADD OFI. Otherwise, the system faults occur.
Signaling point code of local entity
It is a parameter set for the interworking between the MSOFTX3000 and M3UA and defines the
corresponding local signaling point code of the local entity. It is defined by SET OFI or ADD
OFI before it can be used here.
Local entity type
It is a parameter set for the interworking between the MSOFTX3000 and M3UA, and defines
the application mode of the MSOFTX3000 in M3UA links. The configuration principles are as
follows:

HUAWEI MSOFTX3000
z In a non-peer network mode, set this parameter to Application Server if the

MSOFTX3000 interconnects with MSC, BSC, RNC, HLR or SCP in the SS7 network
through the SG.
z In a non-peer network mode, set this parameter to SG if the MSOFTX3000 functions as an
integrated SG.
z In a peer network mode, set this parameter to AS if the MSOFTX3000 interconnects with
MSC server, HLP, SCP or fixed softswitch through M3UA links (instead of through SG).
Routing context
It is a parameter set for the interworking between the MSOFTX3000 and M3UA. When Local
entity type is set to AS, this parameter is valid to define the routing key used by the
MSOFTX3000 to send registration requests to the SG. The configuration principles are as
follows:
z The routing context can be a decimal number or null (that is, not configured). It must be
determined by negotiation before the interworking.
z If it is set to "2147483647", that means the routing context is null. In other words, the
parameter is unavailable for use.
6.3.4 Adding M3UA Destination Entity

Related Commands
Command Function
ADD M3DE To add an M3UA destination entity

RMV M3DE To remove an M3UA destination entity
MOD M3DE To modify an M3UA destination entity
LST M3DE To list M3UA destination entities
Destination entity index
It defines a M3UA destination entity in the configuration database of the MSOFTX3000. The
value range is from 0 to 65534. The configuration principles are as follows:
z When there are associated M3UA signaling routes between the MSOFTX3000 and the
peer signaling device, you must define the signaling device as a destination entity. For
example, if the MSOFTX3000 interconnects with SG, MSC server, HLR, SCP and
softswitch through M3UA links directly, these devices have to be defined to be destination
entities.
z When the peer signaling device is a DSP (destination signaling point), that signaling
device must be defined to be a destination entity. For example, the MSOFTX3000
interconnects with five MSCs, and two PSTN switches through the transfer of SG and
signaling transfer point (STP). You must define seven destination entities (STP is
excluded).
Local entity index

HUAWEI MSOFTX3000
It defines the originating signaling point code in the corresponding M3UA when the
MSOFTX3000 sends M3UA messages to the destination entity at the peer end. It is defined by
ADD M3LE before it can be used here.
Destination entity name
It identifies a destination entity. The value must be a character string.
Network indicator
It is internal network indicator, which defines the signaling network of the MSOFTX3000 to
which the DPC of the destination entity belongs. The signaling network may be the
international network, international reserved network, national network, or national reserved
network. It is used together with the parameter External network indicator to realize the
conversion between the internal network indicator and the external network indicator. The
z If the DPC of the destination entity is located in the same signaling network as the OPC of
the MSOFTX3000 and they have the same coding structure (14 bits or 24 bits), you need
to only set the internal network indicator to the same value as that of the destination entity.
In this case, you need not set the external network indicator.
z If the DPC of the destination entity is located in the same signaling network as the OPC of
the MSOFTX3000, but they have different coding structures (one has 14 bits and the other
has 24 bits), you need to set the external network indicator to the same value as that of the
destination entity, and set the internal network indicator to that of the corresponding active
or standby network. For example, if DPC is located in the international network, you need
to set the external network indicator of the DPC at the MSOFTX3000 side to
International network, and the internal network indicator to International reserved
network. If DPC is located in the national network, you need to set the external network
indicator of the DPC at the MSOFTX3000 side to National network, and the internal
network indicator to National reserved network.
Signaling point code of destination entity
the signaling point code of the destination entity in the SS7 network. The signaling point code
configured here should not be the same as that configured with the command ADD N7DSP and
ADD MTP3BDSP.
In the "MSOFTX3000 → SG → peer device" network mode, if the peer device also supports
M3UA and the SG works as a non-exclusive signaling point, the peer device uses the same
signaling point code assigned to the SG. That is, the two destination entities share the same
signaling point code (assigned to the SG) at the MSOFTX3000 side.
STP flag
It defines whether the destination entity has the signaling transfer functions. Set this parameter
to YES only when the destination entity is an associated SG of the MSOFTX3000. Set this
parameter to NO in other cases.
Linkset selection mask
It defines how the MSOFTX3000 shares signaling traffic load among multiple M3UA linksets
to the destination entity. The configuration principles are as follows:
z When there is only one linkset between the MSOFTX3000 and the destination entity,
select the default value B1111 for the linkset selection mask.
z When there are two or more than two linksets between the MSOFTX3000 and the
destination entity, you must ensure that the decimal value of the linkset selection mask is

HUAWEI MSOFTX3000
bigger than or equals to the result of the total number of linksets minus 1. For example, if
the total number of linksets is 2, you cannot set the linkset selection mask to B0000.
z To prevent overlapping of bits, you cannot set the linkset selection mask and the link
selection mask of any linkset to the same value. It is recommended to set 1 in different
positions in the two masks. For example, if the linkset selection mask is 0110, you can set
the link selection mask to 1001.
Destination entity type
the application mode of the destination entity in an M3UA linkset. The configuration principles
are as follows:
z In a non-peer network mode, set this parameter to SP if the destination entity is MSC, BSC,
RNC, HRL or SCP that interconnects with the MSOFTX3000 through SG.
z In a non-peer network mode, set this parameter to SG if the destination entity is an
associated SG of the MSOFTX3000.
z In a non-peer-to-peer networking model, set this parameter to AS if the MSOFTX3000
functions as an integrated SG, that is, the destination entity is an AS.
z In a peer network mode, set this parameter to AS if the destination entity is a MSC server,
HRL, SCP or softswitch that directly interconnects with the MSOFTX3000 through
M3UA (not transferred through SG)
Adjacent flag
When the destination entity type is set to SG or AS, this parameter is valid to define whether or
not there is any associated M3UA signaling route between the MSOFTX3000 and the peer
destination entity. If the M3UA messages between the MSOFTX3000 and the destination entity
are unnecessarily transferred through an SG, set this parameter to YES. If necessarily
transferred through an SG, set this parameter to NO. For example:
z In a non-peer network mode, set this parameter to YES if the destination entity is an
associated SG of the MSOFTX3000.
z In a non-peer network mode, set this parameter to NO if the destination entity is MSC,
BSC or HRL that interconnects with the MSOFTX3000 through an SG.
z In a peer network mode, always set this parameter to YES irrespective of the type of
device the destination entity is.
Networking mode
When Destination entity type is set to AS, this parameter is valid to define whether the AS
interconnected with the MSOFTX3000 has an exclusive signaling point code or shares a
signaling point code with other ASs (The MSOFTX3000 functions as an SG). By default, it is
Exclusive SPC.
Routing context
The route context (also known as routing context) is a parameter set for the interworking
between the MSOFTX3000 and AS. That is, when the type of the destination entity is set to AS,
this parameter is valid to define the routing key used by the AS to send registration requests to
the MSOFTX3000. The configuration principles are as follows:
z The routing context may be a decimal number or may be null (that is, not configured). It
must be negotiated and determined before the interworking.
z If it is set to "2147483647", it means the routing context is null. In other words, the
parameter is unavailable for use.

HUAWEI MSOFTX3000
M3UA protocol version

As a parameter set for the interworking between the MSOFTX3000 and M3UA, it defines the
M3UA version supported by the destination entity. By default, the system supports M3UA
defined in RFC3332.
External network indicator
As a parameter set for the MSOFTX3000 to interwork with the destination entity, it defines the
signaling network to which the DPC of the destination entity belongs. It can be the international
network, international reserved network, national network, or national reserved network. It is
used together with the parameter Network indicator of the command to realize the conversion
between the internal network indicator and the external network indicator. Refer to Network
indicator for the configuration principles.
By default, if you do not set the type of the external network indicator, the SoftX3000 regards
that the external network indicator of the destination entity is of the same type of the internal
network indicator.
6.3.5 Adding M3UA Additional Destination Service (Optional)

Related Commands
Command Function
ADD M3DS To add an M3UA additional destination service

RMV M3DS To remove an M3UA additional destination service
MOD M3DS To modify an M3UA additional destination service
LST M3DS To list M3UA additional destination services
This configuration step is optional. Before you start to set the data, read the following notes.
If the MSOFTX3000 acting as an integrated SG works as a non-exclusive signaling point,
M3UA additional destination service has to be added for every AS sharing the same signaling
point code with the MSOFTX3000 by ADD M3DS.
Additional service index
It defines an M3UA additional destination service in the configuration database of the
MSOFTX3000.
It defines the destination entity to which the MSOFTX3000 transfers the received M3UA
messages from the originating signaling point. It is defined by ADD M3DE before it can be
used here.
OPC

HUAWEI MSOFTX3000
The originating point code delimitates the scope of M3UA messages for the MSOFTX3000 to
transfer. That is, the MSOFTX3000 only transfers the M3UA messages sent by the AS in which
the value of the OPC field matches the originating point code defined here; otherwise, the
MSOFTX3000 discards them. By default, it is All. That is, the OPC field in the M3UA
messages sent from the AS to the MSOFTX3000 is not compared.
Service indicator
The service indicator delimitates the scope of M3UA messages transferred by the
MSOFTX3000. That is, the MSOFTX3000 only transfers the M3UA messages sent by the AS
in which the value of the SI field matches the service indicator defined here; otherwise, the
MSOFTX3000 discards them. By default, it is All. That is, the SI field in the M3UA messages
sent from the AS to the MSOFTX3000 is not compared.
Start CIC, End CIC
When the service indicator is TUP or ISUP, the start circuit identification code and the end
circuit identification code are valid to delimitate the scope of the M3UA messages transferred
by the MSOFTX3000. That is, the MSOFTX3000 only transfers the M3UA messages sent by
the AS in which the value of the CIC field is within the range of the circuit identification code
defined here; otherwise, the MSOFTX3000 discards them. If no values are defined for these
parameters, the CIC field in the M3UA messages sent from the AS to the MSOFTX3000 is not
compared.
6.3.6 Adding M3UA Linkset

Related Commands
Command Function
ADD M3LKS To add an M3UA linkset

RMV M3LKS To remove an M3UA linkset
MOD M3LKS To modify an M3UA linkset
LST M3LKS To list M3UA linksets
Linkset index
It defines an M3UA linkset in the configuration database of the MSOFTX3000. The value
range is from 0 to 65534. One linkset stands for one signaling route, therefore only one M3UA
linkset can be configured between the local entity (the MSOFTX3000) and an adjacent
destination entity.
Linkset name
It identifies a linkset with a character string.
Adjacent entity index
It defines the destination entity that has an associated signaling route with the MSOFTX3000. It
is defined by ADD M3DE before it can be used here. The configuration principles are as
follows:

HUAWEI MSOFTX3000
z In a non-peer network mode, if the MSOFTX3000 functions as an AS in the M3UA linkset,

the SG interconnected with the MSOFTX3000 is considered as an adjacent destination
entity and other devices are considered as non-adjacent destination entities.
z In a non-peer network mode, if the MSOFTX3000 functions as an SG in the linkset, all the
signaling devices of M3UA such as MSC, BSC, RNC, HLR and SCP interconnected with
the MSOFTX3000 are considered as adjacent destination entities.
z In a peer network mode, all the peer devices are considered as adjacent destination entities.
Link selection mask
It defines how the MSOFTX3000 shares signaling traffic load among multiple M3UA links in
one linkset. The configuration principles are as follows:
z When there is only one link in an M3UA linkset, select the default value B1111 for the link
selection mask.
z When there are two or more than two links in an M3UA linkset, you must ensure that the
decimal value of the link selection mask is bigger than or equals the result of the total
number of links minus 1. For example, if the total number of links is 2, you cannot set the
link selection mask to B0000.
z To prevent overlapping of bits, you must not set the linkset selection mask and the link
selection mask of any linkset to the same value. It is recommended to set 1 in the two
masks in different positions. For example, if the linkset selection mask is 0110, you can set
the link selection mask to 1001.
Traffic mode
It is a parameter set for the interworking between the MSOFTX3000 and an M3UA, and
defines the traffic mode of the M3UA linkset. The default value is load-sharing. The parameter
options are:
z Override mode: N + 1 backup mode. In this mode, only one link in the linkset is active and
the other links are in the standby state. When the active link becomes faulty, one of the
standby links is activated immediately to convey the traffic.
z Load-sharing mode: In this mode, all the links in the linkset are active and the traffic to be
conveyed is shared among the links.
To interconnect the SoftX3000 with SG or SCP, both ends of the interconnecting linkset must
be set to the same traffic mode; otherwise, the M3UA links cannot work normally. We
recommend the load-sharing mode.
Work mode
the work mode of the M3UA linkset. The configuration principles are as follows:
z In a non-peer network mode, set this parameter to ASP (Application Server Process) if the
MSOFTX3000 functions as an AS.
z In a non-peer network ode, set this parameter to SGP (Signaling Gateway Process) if the
MSOFTX3000 functions as an SG.
z In a peer network mode, set this parameter to IPSP (IP Server Process) if the
MSOFTX3000 interconnects with MSC server, HRL, SCP or softswitch through M3UA
links (not transferred through SG).

HUAWEI MSOFTX3000
6.3.7 Adding M3UA Link

Related Commands
Command Function
ADD M3LNK To add an M3UA link

RMV M3LNK To remove an M3UA link
MOD M3LNK To modify an M3UA link
LST M3LNK To list M3UA links
WBSG module number
It defines the module number of the WBSG to process the M3UA messages. It must be defined
by ADD BRD before it can be used here.
Link number
It defines the logical number of the M3UA link in the corresponding WBSG module. The value
range is from 0 to 63. In the same WBSG module, all M3UA links must be numbered. That is,
one WBSG module supports a maximum of 64 M3UA links.
Link name
It identifies a link with a character string.
Local IP address1, Local IP address2
It is a parameter set for the interworking between the MSOFTX3000 and the M3UA. It defines
the IP address of the FE port used for dispatching M3UA messages in the MSOFTX3000. It is
defined by ADD FECFG before it can be used here. Local IP address 1 is a mandatory
parameter.
If the MSOFTX3000 accommodates more than one the WIFM, you can also define the local IP
address 2. This type of configuration supports the multi-homing function of the SCTP
associations at the MSOFTX3000 side to improve the networking reliability of the system.
Local port number
the SCTP port number used for M3UA messages at the MSOFTX3000 side. The configuration
principles are as follows:
z If the MSOFTX3000 acts as a server in the M3UA link (that is, SCTP coupling), it is
recommended to set the local SCTP port numbers of several M3UA links configured
between the MSOFTX3000 and M3UA to the same value.
z If the MSOFTX3000 acts as a client in the M3UA link (that is, SCTP coupling), the local
port numbers of several M3UA links configured between the MSOFTX3000 and an
M3UA cannot be the same.
The M2UA, M3UA, IUA, H.248 and BICC protocols are all transported based on the SCTP,
therefore, it is recommended to universally plan the ranges of local SCTP port numbers for the

HUAWEI MSOFTX3000
links of different protocols before data configuration. Do not assign the same port number to
several links.
Peer IP address1, Peer IP address2
the IP address of the SG. The peer IP address 1 is a mandatory parameter.
If the SG also supports the multi-homing function of the SCTP coupling associations, you can
specify the peer IP address 2. This type of configuration supports the multi-homing function of
the SCTP coupling associations at the SG side to improve the networking reliability of the
system.
Peer port number
the SCTP port number used for M3UA messages at the peer M3UA side. If the peer M3UA acts
as a server in the M3UA link, for the MSOFTX3000, the peer port numbers for its different
M3UA links can be the same. For example, if the peer M3UA uses the well-known M3UA port
number, the peer port numbers for the M3UA links at the MSOFTX3000 side can be the default
value, 2905.
Client/Server mode
It is a parameter set for the interworking between the SOFTX3000 and the M3UA. It defines the
application mode of the MSOFTX3000 in the M3UA links (that is, SCTP coupling
associations).
z In a non-peer network mode, for example, the MSOFTX3000 interconnects with an SG, if
functioning as an AS, the application mode of the MSOFTX3000 must be set to Client in
the M3UA link.
z In a non-peer network mode, for example, the MSOFTX3000 is applied as an integrated
SG, if functioning as an SG, the application mode of the MSOFTX3000 must be set to
Server in the M3UA link.
z In a peer network mode, for example, the MSOFTX3000 directly interconnects with the
peer M3UA instead of being transferred through an SG, the application mode of the
MSOFTX3000 in the M3UA link must be set to Client.
Linkset index
It defines the M3UA linkset to which the M3UA link belongs. It is defined by ADD M3LKS
before it can be used here.
Active/Standby flag
It defines the work state of the M3UA link in normal cases. The configuration of this parameter
is closely related to the traffic mode of the M3UA linkset.
z In the override traffic mode, only one M3UA link in the same linkset is set to active mode
and the other links are set to standby mode.
z In the load-sharing traffic mode, all the M3UA links in the same linkset are set to active
mode.
Priority
It defines the routing priority for the M3UA link to convey signaling traffic. A link with the
highest priority is preferred. A link is selected to convey signaling traffic only after there are
absolutely no available links with a higher priority than it. The greater the value is, the lower the
priority. Value 0 indicates the highest priority.

HUAWEI MSOFTX3000
Maximum incoming flow of SCTP coupling association

It defines the maximum number of SCTP streams contained in each M3UA message received
by the MSOFTX3000. By default, it is 17. The actual number of SCTP streams received by the
MSOFTX3000 after the SCTP association is established is the result negotiated by both parties.
Maximum outgoing flow of SCTP coupling association
It defines the maximum number of SCTP streams contained in each M3UA message sent by the
MSOFTX3000. By default, it is 17. The actual number of SCTP streams sent by the
MSOFTX3000 after the SCTP association is established is the result negotiated by both parties.
Congestion start threshold
The unit for this parameter is "%". Whenever the signaling traffic loaded on the M3UA link
reaches this threshold, the MSOFTX3000 starts the congestion control automatically. The value
range is from 1 to 99. By default, it is 80.
Threshold means the percentage occupied in the sending buffers of the signaling link. When the
MSOFTX3000 starts congestion control, the MSOFTX3000 reduces the number of MSU
(message signaling unit) to be sent. In practical configuration, the value of congestion start
threshold should exceed that of congestion end threshold.
Congestion end threshold
It is used to indicate the MSOFTX3000 to cancel the congestion control automatically when the
signaling traffic loaded on the M3UA link is reduced to this threshold. The value range is from
1 to 99, and the unit for this parameter is "%". By default, it is 40.
Self loop flag
It defines whether to enable the self loop function for the M3UA link. By default, it is set to NO.
That is, the self loop function is not enabled. It is only used for debugging purposes. Be careful
while setting it.
6.3.8 Adding M3UA Route

Related Commands
Command Function
ADD M3RT To add an M3UA route

RMV M3RT To remove an M3UA route
MOD M3RT To modify an M3UA route
LST M3RT To list M3UA routes
Route name
It defines the M3UA route with a character string.

HUAWEI MSOFTX3000
It defines the destination entity to which the M3UA route is directed. It must be defined by
ADD M3DE before it can be used here.
It should be noted that an M3UA route is added for all destination entities defined by ADD
M3DE except SG.
Linkset index
It defines the M3UA route toward the destination entity, that is, through which the M3UA
linkset the MSOFTX3000 conveys signaling traffic. It must be defined by ADD M3LKS
before it can be used here.
Priority
It defines the routing priority for the M3UA linkset (signaling route) to convey signaling traffic.
A linkset with the highest priority is preferred. A linkset is selected to convey signaling traffic
only after there are absolutely no available signaling routes with a higher priority than it. The
greater the value is, the lower the priority. Value 0 indicates the highest priority.
6.4 Configuring IUA Data

Basic Concept
Refer to 6.2.1 "Background" for details.
IUA Application Model

The IUA protocol defined by RFC3057 adopts the SCTP protocol as a transport protocol. It
transports the user layer of Q.921 (Q.931) in DSS1 over the IP packet-based network. The
protocol is used to transport signaling between the SG and the MGC. Figure 6-8 shows the IUA
application model.
Figure 6-8 IUA application model
PRA link IUA link

PBX SG MGC
Q.931
Q.931
IUA IUA
Q.921 SCTP SCTP

Q.921
IP IP

HUAWEI MSOFTX3000

IUA signaling data are used to define data related to IUA links for interconnecting the
MSOFTX3000 and the embedded SG (such as the UMG8900 of Huawei) including the
following data:
z Local IP address
z Peer IP address
z Local SCTP port number
z Peer SCTP port number
z C/S work mode of links
z Service mode of links
During the configuration of IUA signaling data, the following parameters are used: WBSG
module number, IP address of FE port and MGW index. These parameters are defined when
you configure hardware data and MGW data. Table 6-9 shows referencing relationship between
the IUA signaling parameters and other parameters.
Table 6-9 Input parameters required in IUA signaling data

WBSG module number ADD BRD Hardware data ADD IUALNK

IP address of FE port ADD FECFG Hardware data ADD IUALNK
MGW index ADD MGW MGW data ADD ESG
The key parameter defined by IUA signaling data is IUA linkset index that is used during the
configuration of DSS1 signaling data.
Table 6-10 Output parameters defined in IUA signaling data

Parameter Defined in Referenced in Destination data type
IUA linkset index ADD IUALKS ADD PRALNK DSS1 signaling data
Before setting the IUA signaling data, make sure that all preparations are done as specified in
Table 6-11.

SN Item Remark
1 IP address of embedded SG A parameter for interconnecting the

MSOFTX3000 and the embedded SG.

HUAWEI MSOFTX3000
SN Item Remark
2 Local SCTP port number of each A parameter for interconnecting the

IUA link ( at the client side) MSOFTX3000 and the embedded SG. It
should be defined together with the local
SCTP port number of the M3UA link and the
M2UA link.
3 Peer SCTP port number of each A parameter for interconnecting the
IUA link (at the server side) MSOFTX3000 and the embedded SG.
Configuration Steps
Table 6-12 lists the steps for configuring M2UA signaling data.

1 Add an SG. ADD ESG

2 Add an IUA linkset. ADD IUALKS
3 Add an IUA link. ADD IUALNK

the IUA signaling data.

HUAWEI MSOFTX3000
ADD ESG
MGW ID
ADD IUALKS
Linkset index
Linkset name
ADD IUALNK
WBSG module number
Link number
Linkset index
6.4.3 Adding Embedded SG

Related Commands
Command Function
ADD ESG To add an embedded SG

RMV ESG To remove an embedded SG
MOD ESG To modify an embedded SG
LST ESG To list embedded SGs
It defines an embedded SG (such as the UMG8900 of Huawei) in the configuration database of
the MSOFTX3000. The SG adopts one or more than one of the following protocols: the M2UA,
M3UA and IUA. The value range is from 0 to 511.
It defines the name of an SG. The parameter is a string of characters to describe an embedded
SG.
MGW ID

HUAWEI MSOFTX3000
It defines an MGW where the SG is embedded. The parameter should be defined by ADD
MGW before being used here.
6.4.4 Adding IUA Linkset

Related Commands
Command Function
ADD IUALKS To add an IUA linkset

RMV IUALKS To remove an IUA linkset
MOD IUALKS To modify an IUA linkset
LST IUALKS To list IUA linksets
Linkset index
It defines an IUA linkset in the configuration database of the MSOFTX3000. The value range is
from 0 to 65534.
Linkset name
It defines the name of a linkset. The parameter is a string of characters to describe an IUA
linkset.
Traffic mode
the UMG8900 of Huawei), it specifies the service mode used by an IUA linkset. It is set to
Load share by default. There are two traffic modes:
z Override mode: N+1 backup mode. In this mode, only one link in a linkset is activated,
and the other links are standby. When the activated link is faulty, one standby link is
activated immediately for traffic transmission.
z Load-sharing mode: In this mode, all links in a linkset are activated and they share load.
When the MSOFTX3000 interconnects with the embedded SG, the linkset for interworking
must remain the same traffic mode at both ends (load-sharing mode is recommended);
otherwise, IUA links cannot work normally.
Interface ID type
the UMG8900 of Huawei), it specifies the interface ID type of PRA links (signaling links in
channel D) carried on an IUA linkset. By default, it is Integer. You can set it to Text as required,
but it must be consistent with the embedded SG.
It defines an embedded SG to which the links of an IUA linkset belong. The parameter should
be defined by ADD ESG before being used here.

HUAWEI MSOFTX3000
6.4.5 Adding IUA link

Related Commands
Command Function
ADD IUALNK To add an IUA link

RMV IUALNK To remove an IUA link
LST IUALNK To list IUA links
Parameter description
WBSG module number
It defines the module number of the WBSG to process the message of the IUA link protocol.
The parameter should be defined by ADD BRD before being used here.
Link number
It defines the logical number of the IUA link in the related WBSG module. The value range is
from 0 to 31. In the same WBSG module, all IUA links must be numbered universally. That is,
one WBSG module supports up to 32 IUA links.
Linkset index
It defines the IUA linkset to which IUA links belong. It must be defined by ADD IUALKS
Maximum incoming flow of SCTP association
It defines the maximum number of SCTP streams in each IUA protocol message received by the
number of the PRA links actually borne over IUA links. It can also be the default value, 33. The
actual number of streams received after an SCTP association is established is negotiated
between both ends.
Maximum outgoing flow of SCTP association
It defines the maximum number of SCTP streams in each IUA protocol message sent by the
number of the PRA links actually borne over IUA links. It can also be the default value, 33. The
actual number of streams sent after an SCTP association is established is negotiated between
both ends.
Local port number
It is one of parameters for interconnecting the MSOFTX3000 and the embedded SG (such as
the UMG8900 of Huawei). It defines the SCTP port number used for IUA messages at the
MSOFTX3000 side. The configuration principles for this port number are as follows:
z The MSOFTX3000 can be set to act as a server in the IUA link. In this case, when there are
several IUA links between the MSOFTX3000 and the embedded SG, the local port
numbers of each IUA link should be the same.

HUAWEI MSOFTX3000
z The MSOFTX3000 can be set to act as a client in the IUA link. In this case, when there are
several IUA links between the MSOFTX3000 and the embedded SG, the local port
numbers of each IUA link should not be the same.
z The M2UA, M3UA, IUA, H.248, and BICC protocols are all transported on the basis of
the SCTP, therefore it is suggested that you should universally plan the ranges of local
SCTP port numbers for the links of different protocols before data configuration. Do not
assign the same port number to several links.
Local IP address1 and Local IP address2
Both Local IP address1 and Local IP address2 are the parameters for interconnecting the
MSOFX3000 and the embedded SG. These two parameters define the IP addresses of the FE
port used for dispatching IUA messages at the MSOFTX3000. They must be defined by ADD
FECFG before being used here. Local IP address 1 is mandatory.
If the MSOFTX3000 is configured with more than one WIFM boards, you can specify Local IP
address 2. It aims at supporting the multi-homing function of the SCTP associations at the
MSOFTX3000 to improve the networking reliability of the system.
Peer port number
It is one of the parameters for interconnecting the MSOFTX3000 and the embedded SG. It
defines the SCTP port number used for IUA messages at the embedded SG.
The embedded SG is set to act as a server in the IUA link, so for the MSOFTX3000, the peer
end numbers for different IUA links can be the same. For example, if the well-known port
number for IUA is used at the embedded SG, the peer port numbers for different IUA links at the
MSOFTX3000 can be the default value, 9900.
Peer IP address1 and Peer IP address2
Both of them are parameters for interconnecting the MSOFTX3000 and the embedded SG.
They define the IP addresses of the embedded SG. Peer IP address 1 is mandatory.
If the embedded SG also supports the multi-homing function of the SCTP associations, you can
specify Peer IP address 2. It aims at supporting the multi-homing function of the SCTP
associations at the SG side to improve the networking reliability of the system.
Client/Server mode
It is one of parameters for interconnecting the MSOFTX3000 and the embedded SG. It defines
the application mode of the MSOFTX3000 in the IUA link (SCTP association). The default
value is Client. If the MSOFTX3000 is set to Client, the SG must be set to Server. Conversely,
if the SG is set to Client, the MSOFTX3000 must be set to Server.
Active/Standby flag
It defines the work state of an IUA link in normal cases. The configuration of this parameter is
closely related to the traffic mode of the IUA linkset.
z In the override traffic mode, only one IUA link in the same linkset can be set to Active and
the other links must be set to Standby.
z In the load-sharing traffic mode, all the M2UA links in the same linkset must be set to
Active.

HUAWEI MSOFTX3000
6.5 Configuring DSS1 Signaling Data

Basic Concepts
The Digital Subscriber Signaling No. 1 (DSS1) is used for coordination and control between
integrated services digital network (ISDN) terminal devices and ISDN network devices. It
provides signaling functions required by basic bearer services and supplementary services for
both voice and non-voice usages on the ISDN network. The DSS1 signaling is applicable to the
"subscriber-network" interface specifications such as Basic Rate Interface (2B+D) and Primary
Rate Interface (30B+D).
The MSOFTX3000 supports the PRI interface instead of the BRI interface. In the system, the
PRA link is a type of signaling link. It can occupy only the time slot 16 of an E1, and it is used
to bear the DSS1 signaling on the primary rate interface.
Network Indicator for PRA Link

The DSS1 signaling is not a peer-to-peer subscriber signaling. Before a PRA link is set up, both
ends of the link detect the network indicator of each other. To set up a PRA link, the network
indicator at one end must indicate "network side" and that at the other end must indicate
"subscriber side". Thus, the network indicators for a PRA link must be negotiated and
determined with the opposite office before the PRA link is set on the MSOFTX3000 and
UMG8900 side. The purpose is to ensure that the network indicators at both ends are consistent.

DSS1 signaling data is used to interconnect the MSOFTX3000 to PBX or NAS devices. It is the
data related to the PRA link including interface ID, signaling type, and circuit number of
signaling links.
z During the configuration of DSS1 signaling data, the following parameters are used:
WCCU/WCSU module number, IUA linkset index and Caller number change index.
These parameters are defined when you configure hardware data, IUA signaling data, and
number analysis data. Table 6-13 shows referencing relationship between the DSS1
signaling parameters and other parameters.
Table 6-13 Input parameters required in DSS1 signaling data
WCCU/WCSU module ADD BRD Hardware data ADD PRALNK

number
IUA linkset index ADD IUALKS IUA signaling data ADD PRALNK
Caller number change ADD DNC Number analysis data ADD PRALNK
index

HUAWEI MSOFTX3000
z PRA signaling link number is a key parameter defined by the DSS1 signaling data. The
parameter is used during the configuration of the PRA trunk data. The referencing
relationship between parameters of the DSS1 and the PRA trunk data is shown in Table
6-14.
Table 6-14 Output parameters defined in DSS1 signaling data
Parameter Defined in Referenced in Destination data

type
PRA signaling link ADD PRALNK ADD PRATG PRA trunk data
number
Before setting the DSS1 signaling data, make sure that all preparations are done as specified in
Table 6-15.

SN Item Remark
1 Integer interface ID A parameter for interconnecting the

MSOFTX3000 and the embedded SG
2 Text interface ID (optional) A parameter for interconnecting the
MSOFTX3000 and the embedded SG
3 Network check flag A parameter for interconnecting the
MSOFTX3000 to PBX or NAS devices
4 Signal circuit number A parameter for interconnecting the
5 Outgoing CR length (optional) A parameter for interconnecting the
Configuration Steps
Table 6-16 lists the step for configuring DSS1 signaling data.
Table 6-16 Configuration step

1 Add a PRA link. ADD PRALNK

HUAWEI MSOFTX3000

the DSS1 signaling data.
ADD IUALKS
Linkset index
Linkset name
ADD PRALNK
Signaling link number
Signaling circuit number
IUA linset index
6.5.3 Adding PRA link

Related Commands
Command Function
ADD PRALNK To add a PRA link

MOD PRALNK To remove a PRA link
RMV PRALNK To modify a PRA link
LST PRALNK To list PRA links
Link number
It defines the logical number of the PRA link in the related WCCU or WCSU. The value range
is from 0 to 999. In the same WCCU or WCSU, all PRA links must be numbered universally.
Signal circuit number
It defines the E1 time slot of PRA trunk group. The time slot is occupied by the PRA link. The
configuration principles for this parameter are as follows:
z This is a unique logical number assigned inside the MSOFTX3000 to the A interface, and
the E1/T1 trunk circuit of SS7, CAS, PRA that are in a WCCU/WCSU. It is not the
physical number of E1/T1 circuits at the MGW side.
z When the E1 link is adopted, the circuit number cannot be any time slots but time slot 16
of a certain E1 line. For example, if the start circuit number of time slot 0 of an E1 is SC,
the circuit number of the PRA signaling circuit is SC+16.

HUAWEI MSOFTX3000
z When the T1 link is adopted, the circuit number can be any time slot except time slot 0.
z When a circuit in the MGW is used as a PRA signaling time slot, you should set the circuit
to unavailable through MOD PRATKC.
WCCU/WCSU module number
It defines the module number of the WCCU or WCSU to process the message of the PRA
signaling. The parameter must be defined by ADD BRD before being used here.
IUA linkset index
It defines the IUA linkset that bears the PRA link (that carries the D-channel signaling messages
of the PRA subscribers). It must be defined by ADD IUALKS before being used here.
Integer interface ID
This is one of parameters for interconnecting the MSOFTX3000 and the embedded SG (such as
the UMG8900 of Huawei). It is used to uniquely identify the PRA link from all the D-channel
signaling messages of the PRA subscribers that are borne over the IUA linkset. The
MSOFTX3000 supports both integer interface ID and text interface ID. In the actual cases, the
integer interface ID is preferred.
Text interface ID
This is one of parameters for interconnecting the MSOFTX3000 and the embedded SG. It is
used to uniquely identify this PRA link from all the D-channel signaling messages of the PRA
subscribers that are borne over the IUA linkset. The MSOFTX3000 supports both integer
interface ID and text interface ID. In the actual applications, the integer interface ID is
preferred.
Signaling type
This is one of parameters for interconnecting the MSOFTX3000 and the PRA device. It is used
to identify the application mode of the local end in the PRA link. By default, it is set to DSS1
network side.
In the actual applications, the MSOFTX3000 generally provides PRA link through embedded
SG (such as the UMG8900 of Huawei). You must set related signaling type of PRA signaling
links at the three devices: the MSOFTX3000, SG and peer PRA as follows:
z Regard the MSOFTX3000 and SG as a unit. Set the same type of PRA signaling links —
either DSS1 network side or DSS1 subscriber side for the MSOFTX3000 and the SG.
z The PRA signaling type of peer PRA device must be different from the local end (that is
MSOFTX3000+SG). If the local end is DSS1 network side, the opposite end must be
DSS1 subscriber side, and it is the same case conversely.
Outgoing CR length
This is one of parameters for interconnecting the MSOFTX3000 and the PRA device. It is used
to specify the length of the CR Value field in Q.931 call messages. The length is represented in
bytes. By default, it is set to 2 indicating the field has two bytes. It is used to adapt PRA devices
provided by different vendors. It should be set to 1 when applied in certain countries.
Caller number check mode
It indicates whether the MSOFTX3000 performs a validity check to the caller number of an
incoming call originated by the peer PRA device (for example, PBX) through a PRA link so as
to determine the calling number for call connection. It is valid only to incoming trunks. The
validity is defined as follows:

HUAWEI MSOFTX3000
z If the calling number sent by the peer office is not a PRA subscriber number defined in the
local office, that is, if the received number cannot be found in the PRA subscriber number
data table of the local office, the calling number is invalid.
z If the calling number sent by the peer office is a PRA subscriber number defined in the
local office, that is, the received number can be found in the PRA subscriber number data
table of the local office, the calling number is valid. For example, it is assumed that A is the
route selection code used by the PRA subscriber, and B1–B5 are the route selection codes
used by the default calling number of PRA trunk group. The PRA signaling link controls n
(1≤n≤5) PRA trunk group(s). If A is equal to one of the numbers between B1 and B5, the
calling number is valid. If A is not equal to any one between B1 and B5, the calling number
is invalid.
The validity check aims at determining the calling number that is used in the subsequent call
processing. The setting of Caller number check mode affects charging, because the calling
number used here is the number in a bill. Set this parameter as follows:
z If the parameter is set to Yes (default value), validity check is performed. When receiving
no calling number from the peer PRA, the MSOFTX3000 assumes the default calling
number on the PRA trunk as the present calling number. When receiving the calling
number from the peer PRA, the MSOFTX3000 checks whether the calling number is valid.
If so, the calling number is assumed as the present calling number; otherwise, the default
number is used.
z If the parameter is set to No, no validity check is performed. When the address nature of a
calling number sent by the PRA is a national number, the MSOFTX3000 assumes the
calling number as the present calling number (that is, the local office transmits all numbers
from the peer office transparently); otherwise, the MSOFTX3000 assumes the default
calling number on the PRA trunk group as the present calling number.
Caller number change index
It defines whether the MSOFTX3000 needs to change the calling number on the PRA link. If it
is set to 0, no change is performed. If it is set to other values, it must be defined by ADD DNC
6.6 Configuring MTP Data

6.6.1 Related Concepts
Signaling Point and Signaling Point Code
A signaling point is the origination (OPC) and destination (DPC) of signaling messages. It can
be an exchange with SS7 functions, such as a VMSC, a GMSC, a TMSC, a PSTN exchange, a
data exchange, or an ISDN exchange. It can also be a non-exchange device, such as a BSC,
RNC, HLR, SCP, SGSN and GMLC.
An SPC uniquely identifies a signaling point in the signaling network. As specified in the SS7,
there are four types of signaling networks, namely international network, international reserved
network, national network, and national reserved network. A signaling point can be in those
four networks simultaneously and coded in each network.
The CCITT recommends that the signaling point code adopts 24-bit and 14-bit encoding
schemes. The encoding principles are as follows:
z The international network adopts the 14-bit encoding scheme.

HUAWEI MSOFTX3000
z The encoding scheme for the national network is determined by the telecommunication
supervision department of each country. For example: the Ministry of Information
Industry of China regulates that the national network adopts 24-bit encoding scheme.
z The encoding schemes for the international reserved network and the national reserved
network are determined by network carriers.
Signaling Link Code

According to the SS7, there are up to 16 MTP signaling links between two adjacent signaling
points. The 16 MTP signaling links are called a signaling linkset. To uniquely identify a MTP
signaling link in the linkset, signaling link code (SLC) is used.
The value range of the 4-bit SLC is from 0 to 15 in decimal notation. In the interworking of two
signaling points, the SLC values of a signaling link must be the same after negotiation.
Otherwise, the MTP link cannot be established.
Link Selection Mask

Mask is used when you configure M3UA destination entity, M3UA linkset, MTP DSP, MTP
linkset, MTP3B DSP, and MTP3B linkset. If there are multiple signaling routes or links, mask
is used for load sharing among signaling links.
Link selection mask is used to select different signaling links in a linkset (signaling route). The
following shows an example of the application of this mask.
The signaling link selection (SLS) code is a 4-bit binary code. It is an independent field in ISUP
messages. In TUP messages, it is the four low order digits from the Circuit Identification Code
(CIC) in the signaling unit. The SLS value varies with calls. When the SLS value changes, the
link selected by signaling unit changes accordingly. Thus load sharing function is achieved.
The mask is also a 4-bit binary code. It determines, together with the SLS code, the signaling
link to be seized by signaling unit. In the mask, digit 1 indicates that the corresponding bit of the
SLS code is retained, while digit 0 indicates that the corresponding bit of the SLS code is
masked. In this way, you can get a valid link selection bit by masking or retaining a specified
SLS bit. For example:
SLS = 1 0 1 0
Mask = 0 0 1 1
Result = 0 0 1 0
The result of the SLS ANDed with the mask is a 4-bit binary code. Its value range is determined
by the mask. Theoretically, if the decimal value of the mask = the total number of links in a
linkset -1, the signaling unit can directly use this result for link selection. For example, if a
linkset has four links and the mask is 0011, the result of the SLS together with the mask ranges
from 0 to 3 no matter how the SLS changes. Thus this result can be directly or indirectly used
for link selection.
The above-mentioned algorithm can achieve load sharing among links in a linkset, but it has a
strict requirement on the number and position of digit 1 in the link selection mask. When the
link selection mask is used with linkset selection mask, overlapping of bits occurs. For details,
refer to "Overlapping of Bits."
To solve this problem, the MSOFTX3000 uses the following algorithm:
C=A%S+B

HUAWEI MSOFTX3000
z A: the result of the SLS ANDed with the mask.

z S: the total number of links in a linkset.
z B: the link number of the first link.
z C: the link number to be selected.
z A%S: the remainder of dividing A by S. If A<S, the remainder is A.
With this algorithm, the system can automatically select a valid link if the decimal value of the
link selection mask ≥ the total number of links in a linkset – 1. Thus the flexibility of data
configuration improves.
Linkset Selection Mask

Linkset selection mask is used for selecting different signaling linksets (signaling routes) in an
office direction. It is the same as link selection mask in terms of the concept and algorithm.
Overlapping of Bits
It means that the signaling unit always selects the same linkset number and link number.
Suppose there are two MTP linksets, numbered 0 and 1, in one office direction. Each has two
links, numbered 0 and 1. If both the linkset selection mask and the link selection mask are 0010,
the overlapping of bits occurs due to the same algorithm when the system originates a call. That
is, link 0 in linkset 0 and link 1 in linkset 1 are always seized, while link 0 in linkset 1 and link
1 in linkset 0 are idle.
To avoid this, set the linkset selection mask and the link selection mask to two different values.
It is suggested to set digit 1 in two masks in staggered position. For example, if the linkset
selection mask is 0110, set the link selection mask to 1001.
6.6.2 Overview
Relationship Between Configuration Steps
MTP data defines the MTP link-related information when the MSOFTX3000 interconnects
such equipment as the MSC, BSC, RNC, HLR, SCP, SGSN, GMLC and PSTN exchange. The
information includes:
z Destination signaling point code (DPC)
z Signal circuit number
z Signaling link code
z Signaling link code send
MTP data configuration should use WCSU/WSGU module number, M2UA linkset index and
local signaling point code which are respectively defined in equipment information, M2UA
data and office data. Table 6-17 shows the input parameters referencing relationship.
Table 6-17 Input parameters referencing relationship

Name Defined in Source data Referenced in
WCSU/WSGU ADD BRD Equipment ADD N7LNK

module number information
M2UA linkset index ADD M2LKS M2UA data ADD N7LNK

HUAWEI MSOFTX3000
Local signaling SET OFI / ADD OFI Office data ADD N7DSP
point code
MTP data configuration defines MTP3 DPC that is used in SCCP data, routing data and trunk
data. Table 6-18 shows the output parameter referencing relationship.
Table 6-18 Output parameter referencing relationship

Name Defined in Referenced in Destination data
MTP3 DPC ADD N7DSP ADD SCCPDSP SCCP data

ADD OFC Routing data
ADD N7TG Trunk data
Preparations
Before MTP data configuration, ensure that all preparations are done as specified in Table 6-19.

SN Item Remark
1 Destination signaling One of the interworking parameters between the

point code MSOFTX3000 and the SS7 equipment.
2 STP flag One of the interworking parameters between the
MSOFTX3000 and the SS7 equipment.
3 Signaling link code One of the interworking parameters between the
4 Signaling link code send One of the interworking parameters between the
5 Signal circuit number One of the interworking parameters between the
MSOFTX3000 and the SS7 equipment (when the
MSOFTX3000 provides MTP links).
6 Integer interface ID One of the interworking parameters between the
MSOFTX3000 and the SS7 equipment. (when the
MSOFTX3000 provides M2UA links).
Configuration Steps
Table 6-20 lists the steps for MTP data configuration.

HUAWEI MSOFTX3000
1 Add a MTP destination signaling point. ADD N7DSP

2 Add a MTP linkset. ADD N7LKS
3 Add a MTP link. ADD N7LNK
4 Add a MTP route. ADD N7RT

Figure 6-11 shows the parameter referencing relationship for MTP data configuration.
ADD N7DSP ADD M2LKS

DSP index M2UA linkset index
Network indicator Linkset name
DPC Signaling gateway
ID
ADD N7LKS
Linkset index
Adjacent DSP index
Linkset name
ADD N7LNK
WCSU/WBSG
module number
Linkset index
M2UA linkset index
ADD N7RT
Linkset index
DSP index
Route priority

HUAWEI MSOFTX3000
6.6.3 Adding MTP Destination Signaling Point

Related Commands
Command Function
ADD N7DSP To add a MTP destination signaling point

RMV N7DSP To remove a MTP destination signaling point
MOD N7DSP To modify a MTP destination signaling point
LST N7DSP To list a MTP destination signaling point
DSP index
It defines a MTP destination signaling point. The value range is from 0 to 65534. The number of
DSP depends on the number of DPC that bears SS7 service on MTP links and M2UA links on
the MSOFTX3000 side. For example:
z If the MSOFTX3000, through MTP links (without an STP), connects five BSCs, one
GMSC, two TMSCs and two SCPs, define ten DSPs.
z If the MSOFTX3000 connects five BSCs, one GMSC, two TMSCs and two SCPs without
a STP and one GMSC with two STPs, define 12 DSPs. (The two STPs are included.)
z If the MSOFTX3000, through M2UA links (without an STP), connects five BSCs, one
GMSC and two TMSCs, define eight DSPs. (The UMG8900 provides MTP links.)
Network indicator
It defines a type of the signaling network to which the DPC of a DSP belongs. The parameter
options include: international network, international reserved network, national network and
national reserved network. This parameter can be used with the parameter external network
indicator. The configuration principle is as follows:
z If the DPC of a DSP and the OPC of the MSOFTX3000 are in the same signaling network
and they adopts the same encoding scheme (14 bits or 24 bits), set the network indicator
based on the DSP. You do not have to configure the external network indicator
z If the DPC of a DSP and the OPC of the MSOFTX3000 are in the same signaling network
and they adopts different encoding scheme (one is 14 bits, and the other is 24 bits), set the
external network indicator based on the DSP and set the network indicator to the
corresponding network. For example: if a DPC is in the international network, set the
external network indicator to international network and the network indicator to
international reserved network. If a DPC is in the national network, set the external
network indicator to national network and the network indicator to national reserved
network.
DPC
It is one of the interworking parameters between the MSOFTX3000 and the SS7 equipment. It
defines a signaling point code for a DSP. The code configured here should be the same as that
configured by ADD M3DE and ADD MTP3BDSP.
OPC

HUAWEI MSOFTX3000
defines an origination point code carried in SS7 messages that are sent from the MSOFTX3000.
The parameter must be defined by SET OFI or ADD OFI before it can be used here. By default,
the OPC is what defined by SET OFI.
DSP name
It specifies the name of the DSP. The field type is character string.
STP flag
It defines whether a DSP has STP function. If the DSP is the STP equipment that connects the
MSOFTX3000 in associated mode, set the parameter to Yes. Otherwise, set it to No.
Adjacent flag
It defines whether there are direct MTP signaling routing between the MSOFTX3000 and a
DSP. The configuration principle is as follows:
z If the peer end equipment is the STP that connects the MSOFTX3000 in associated mode,
set the parameter to Yes.
z If the peer end equipment is the BSC, RNC, HLR, MSC, PSTN exchange or SCP that
connects with the MSOFTX3000 in associated mode, set the parameter to Yes.
z If the peer end equipment is the BSC, RNC, HLR, MSC, PSTN exchange or SCP that
connects with the MSOFTX3000 in quasi-associated mode, in other words, an STP is
required to forward signaling, set the parameter to No.
It is used to achieve load-sharing among multiple MTP linksets from the MSOFTX3000 to a
z If there is a linkset between the MSOFTX3000 and a DSP, set the parameter to the default
value B1111.
z If the number of the linkset is more than one, ensure that the decimal value of the linkset
selection mask ≥ the total number of linksets – 1. For example, if the total number of
linksets is two, you cannot set the parameter to B0000.
z To avoid overlapping of bits, set the linkset selection mask and the link selection mask to
two different values. It is suggested to set digit 1 in two masks in staggered position. For
example, if the linkset selection mask is 0110, set the link selection mask to 1001.
SI configuration
It specifies the signaling types of MTP3 user layer for MTP links of the DSP that connects the
MSOFTX3000. The default values are SCCP, TUP, ISUP and BICC.
The parameter is used to support the shielding function of MTP3 user layer. For example, if the
value is ISUP, the MSOFTX3000 can only send and receive MTP messages whose MTP3 user
layer is ISUP to a DSP. If not, the MSOFTX3000 refuses the MTP messages whose MTP3 user
layer is not ISUP. In addition, it returns a UPU message to the DSP.
External network indicator
defines a type of the signaling network to which the DPC of a DSP belongs. The parameter
options include: international network, international reserved network, national network and
national reserved network. This parameter can be used with the parameter network indicator.
For configuration principles, refer to network indicator.

HUAWEI MSOFTX3000
If you do not configure this parameter, then by default, it is the same as network indicator.
6.6.4 Adding MTP Linkset

Related Commands
Command Function
ADD N7LKS To add a MTP linkset

RMV N7LKS To remove a MTP linkset
MOD N7LKS To modify a MTP linkset
LST N7LKS To list a MTP linkset
Linkset index
It defines a MTP linkset. The value range is from 0 to 65534. A linkset is a signaling route,
therefore you can configure only one MTP linkset between the MSOFTX3000 and an adjacent
DSP.
Adjacent DSP index
It defines a DSP that has a direct signaling route to the MSOFTX3000. The parameter must be
defined by ADD N7DSP before it can be used here. The two circumstances are as follows:
z The DSP is the STP that connects the MSOFTX3000 in associated mode.
z The DSP is the BSC, RNC, HLR, MSC, PSTN exchange or SCP that connects the
MSOFTX3000 in associated mode. In other words, no STPs are required to forward
signaling.
Linkset name
It specifies the name of the DSP. The field type is character string.
Link selection mask
It is used to achieve load-sharing among multiple MTP links in a linkset. The configuration
principle is as follows:
z If there is a link in a linkset, set the parameter to the default value B1111.
z If the number of the links in a linkset is more than one, ensure that the decimal value of the
link selection mask ≥ the total number of links – 1. For example, if the total number of
links is two, you cannot set the parameter to B0000.

HUAWEI MSOFTX3000
6.6.5 Adding MTP Link

Related Commands
Command Function
ADD N7LNK To add a MTP link

RMV N7LNK To remove a MTP link
MOD N7LNK To modify a MTP link
LST N7LNK To list a MTP link
The MSOFTX3000 provides MTP links in different ways, therefore, configure the link type
based on real networking.
z When the MSOFTX3000 provides MTP links from E1 port on the WEPI (TDM bearer
mode), set the link type to TDM 64 kbit/s link or TDM 2 Mbit/s link.
z When the MSOFTX3000 provides MTP links from embedded signaling gateway, such as
the UMG8900, (M2UA bearer mode), set the link type to M2UA 64 kbit/s link or M2UA
2 Mbit/s link.
WCSU/WBSG module number
mode), it defines the module number of the WCSU that processes MTP2 protocol.
z When the MSOFTX3000 provides MTP links from embedded signaling gateway, such as
the UMG8900, (M2UA bearer mode), it defines the module number of the WBSG that
processes MTP2 protocol.
The parameter must be defined by ADD BRD before it can be used here.
Link number
It defines the number of links in the module. There are two cases:
mode), it defines the physical number of the link in the WCSU module. Two WCPCs are
pinched on the WCSU and each can process 16 MTP links (determined by SLC) or one
2-Mbit/s MTP link. The following is the configuration principle.
− For 64-kbit/s MTP links, the value range is from 0 to 31. For the lower WCPC, the
value range is from 0 to 15. For the upper WCPC, the range is from 16 to 31. Note that,
at present, it is recommended to configure a maximum of eight 64-kbit/s MTP links for
each WCPC subboard.
− For 2-Mbit/s MTP links, the value can be 0 or 16. The value 0 is for the lower WCPC
and 16 for the upper WCPC.
z When the MSOFTX3000 provides MTP links from an embedded signaling gateway, such
as the UMG8900, (M2UA bearer mode), it defines the logical number of the link in the

HUAWEI MSOFTX3000
WBSG module. The value range is from 0 to 191. In other words, a maximum of 192 MTP
links are numbered in the same WBSG module.
Link name
It specifies the name of the link. The field type is character string.
Link type
It specifies the type of the link. Set this parameter based on real networking. The parameter
options include:
z TDM 64 kbit/s link: provided by E1 port on the WEPI of the MSOFTX3000.
z TDM 2 Mbit/s link: provided by E1 port on the WEPI of the MSOFTX3000.
z M2UA 64 kbit/s link: provided by E1 port on the ME32 or MS2L of the embedded
signaling gateway (for example, the UMG8900).
z M2UA 2 Mbit/s link: provided by E1 port on the ME32 or MS2L of the embedded
signaling gateway (for example, the UMG8900).
Start timeslot number
It defines the seized E1 timeslot of the MTP link. This parameter is valid when the bearer mode
is TDM. The configuration principle is as follows:
z MTP links can only seize the E1 timeslots provided by the WEPI of the same subrack, not
from the other subracks.
z Since the WCSU module number has been configured and the WEPI is the back board of
the WCSU, the seized E1 timeslots are provided by the WEPI that is in the same slot as the
WCSU. A pair of WEPIs (active/standby) offer eight E1 ports (active). The sequential
numbering is from 0 to 255, starting from timeslot 0 of the first E1 port.
z MTP links cannot seize timeslot 0 (synchronization timeslot) of the eight E1 ports. In other
words, timeslots numbered 0, 32, 64, 96, 128, 160, 192 and 224 cannot be seized.
z For 64-kbit/s MTP links, if the link number is from 0 to15, the parameter value range is
from 1 to 127. If the number is from 16 to 31, the parameter value range is from 128 to
255.
z For 2-Mbit/s MTP links, if the link number is 0, the parameter value is 1, 33, 65 or 97. If
the link number is 16, the parameter value is 129, 161, 193 or 225.
Number of timeslots
It defines the number of 64-kbit/s timeslots seized by the 2-Mbit/s link. The parameter is valid
when the link type is set to TDM 2 Mbit/s link. Remain the parameter configuration consistent
with that of the peer end SS7 equipment. The default value is 31.
M2UA linkset index
It defines an M2UA linkset that bears SS7 service of the MTP link (logic link at the
MSOFTX3000 side). The parameter is valid when the bearer mode is M2UA. The parameter
must be defined by ADD M2LKS before it can be used here.
Integer interface ID
It uniquely identifies the MTP link among all the MTP links with M2UA bearer mode. It is one
of the interworking parameters between the MSOFTX3000 and an embedded signaling
gateway. The parameter is valid when the bearer mode is M2UA.
Note that if an embedded signaling gateway provides multiple MTP links, the integer interface
ID for them cannot be the same even if they are borne on the same M2UA link.

HUAWEI MSOFTX3000
Linkset index
It defines the linkset to which the MTP link belongs. The parameter must be defined by ADD
N7LKS before it can be used here.
Signaling link code
It defines the logical number of the MTP link in its linkset. The parameter is one of the
interworking parameters between the MSOFTX3000 and SS7 signaling equipment (in
associated mode). According to MTP protocol, SLC is a 4-bit binary code. The decimal value
range is from 0 to 15. In addition, SLC of signaling links within the same linkset cannot be the
same.
Signaling link code send
It is used for the self-loop test of two MTP links in the local office. The configuration principle
is as follows:
z If you do not perform the self-loop test, the signaling link code send and the SLC must be
the same. Otherwise, the signaling interworking fails.
z If you perform the self-loop test, the signaling link code send and the SLC cannot be the
same. In addition, the SLC of link 1= the SLC send of link 2, the SLC of link 2= the SLC
send of link 1.
Link priority
It specifies the link priority levels. The link with higher priority level is preferential. When it is
unavailable, the lower priority level link can bear signaling service. The highest priority level is
0, 1 ranks the next, and so on and so forth.
Satellite flag
It identifies whether the bearer of the link is satellite circuit. Configure it according to real
situations. Usually, it is set to NO.
Congestion start threshold
It specifies a threshold of signaling load from which the MSOFTX3000 starts congestion
control. The value range is from 1 to 99. The unit is %. The default value is 80.
Threshold refers to the occupied percentage of the signaling link sending buffer. When
congestion control starts, the transmission of MSUs is decreased by a certain proportion.
During real configuration, the congestion start threshold is greater than the congestion end
threshold.
Congestion end threshold
It specifies a threshold of signaling load from which the MSOFTX3000 ends congestion control
automatically. The value range is from 1 to 99. The unit is %. The default value is 70.
Test code
It specifies a test code padded in SLTM message for MTP link test. The parameter value is 2-bit
hexadecimal code (0-9, A-F). The default value is AA.
The test code is used for testing the availability of MTP link. In other words, when the SLTM
message is sent, the peer end responds with the SLTA message.
Test code length
It specifies the length of the test code padded in SLTM message for MTP link test. The
parameter range is from 1 to15. The unit is byte. The default value is 10.

HUAWEI MSOFTX3000
Handle module number

It specifies the module number of the WCCU/WCSU that process signaling messages. The
messages are on the user layer above MTP3 layer, including BSSAP, RANAP, ISUP, TUP, MAP,
and CAP. The configuration principle is as follows:
z If you enter no value (by default), the messages are distributed among the WCCU/WCSUs
in load-sharing mode.
z If you want to enter a specific value, the parameter must be defined by ADD BRD before
it can be used here.
z If you want to restore the default configuration using MOD N7LNK, enter 255.
Sending SLTM periodically
It defines whether the MSOFTX3000 sends the SLTM message periodically (60 seconds) over
MTP links to peer signaling equipment. By default, the SLTM message is not sent periodically.
If you configure the parameter with sending SLTM periodically, under normal condition, peer
signaling equipment returns the SLTA message after receiving the SLTM message. In this way,
the MSOFTX3000 can check the availability of MTP links regularly.
6.6.6 Adding MTP Route

Related Commands
Command Function
ADD N7RT To add a MTP route

RMV N7RT To remove a MTP route
MOD N7RT To modify a MTP route
LST N7RT To list a MTP route
Linkset index
It defines the MTP route to a DSP. In other words, it defines the linkset used to transport
signaling. The parameter must be defined by ADD N7LKS before it can be used here.
DSP index
It defines the DSP for the MTP route. The parameter must be defined by ADD N7DSP before it
can be used here. Note that MTP routes must be defined by ADD N7DSP for all DSPs except
STPs.
Route priority
It specifies the linkset (signaling route) priority levels. The linkset with higher priority level is
preferential. When it is unavailable, the lower priority level linkset can bear signaling service.
The highest priority level is 0, 1 ranks the next, and so on.
Route name
It specifies the name of the route. The field type is character string.

HUAWEI MSOFTX3000
6.7 Configuring ATM Signaling Data

Basic Concept
Asynchronous transfer mode (ATM) is a connection-oriented time division multiplexing (TDM)
technology based on packet switching. It is developed as required by the development of
B-ISDN. Featuring in high rate and low delay, ATM supports a variety of subscriber services,
including voice, data and video. ATM is widely used in WCDMA R99 and WCDMA R4. For
instance, it is used for the Iu-CS interface between the MSC and the RNC, the Iu-PS interface
between the SGSN and the RNC, the Iu-b interface between the RNC and the Node B and the
Iu-r interface between two RNCs.
The MSOFTX3000 supports the ATM signaling and bears the MTP3B user layer signaling
through ATM.
z When the H.248 protocol is used as the MTP3B user layer signaling, the MSOFTX3000
provides the Mc interface to connect itself and the MGW. The structure of the protocol
stack is H.248/MTP3B/SAAL/ATM.
z When the SCCP protocol is used as the MTP3B user layer signaling, the MSOFTX3000
provides the lu-CS interface to connect itself and the RNC. The structure of the protocol
stack is RANAP/SCCP/MTP3B/SAAL/ATM.
z When the BICC protocol is used as the MTP3B user layer signaling, the MSOFTX3000
provides the Nc interface to connect itself and the MSC server. The structure of the
protocol stack is BICC/MTP3B/SAAL/ATM.
SAAL Protocol
To enable the MTP3B user layer signaling messages, such as the H.248, SCCP and BICC
messages, to be transmitted in the ATM packet network, ITU-T prescribes that the signaling
ATM adaptation layer (SAAL) protocol is adopted to adapt the MTP3B user layer signaling. In
other words, the SAAL protocol is used to transform the MTP3B user layer signaling so that it
can be transmitted in the ATM packet network, and AAL connections are created for the
MTP3B user layer signaling.
The SAAL protocol, composed of convergence sub-layer (CS) and segmentation and
reassembly (SAR), adopts ATM adaptation layer type 5 (AAL5). The CS sub-layer consists of
service special convergence sub-layer (SSCS) and common part convergence sub-layer (CPCS).
The SSCS sub-layer consists of service special convergence function (SSCF) and service
specific connection oriented protocol (SSCOP). Figure 6-12 shows the structure of the SAAL
protocol stack.

HUAWEI MSOFTX3000
Figure 6-12 Structure of the SAAL protocol stack
MTP3B user
layer signaling
MTP3B
SSCF
SSCS
SSCOP CS
SAAL
CPCS and CPCS
SAR of AAL5 SAR
ATM layer
Physical layer
The functions of the sub-layers in the SAAL protocol are as follows:

z The SCCF sub-layer maps the services required by the MTP3B user layer signaling onto
the services provided by the SSCOP sub-layer to support various applications of the
MTP3B user layer signaling.
z The SSCOP sub-layer sets up and disconnects a connection. It ensures reliable
transmission of messages between peer entities in acknowledged or unacknowledged
mode.
z The CPCS works with the SAR sub-layer to provide AAL5 adaptation service. All data
packets sent from the SAR sub-layer to the ATM layer consist of 48-byte user payloads.
When receiving the 48-byte user payload sent from the SAR sub-layer, the ATM layer further
encapsulates the user payload, that is, adds a 5-byte ATM cell header before the user payload
(containing such routing information as VPI and VCI). In this way, all data packets sent from
the ATM layer to the physical layer are standard 53-byte ATM cells.
ATM Cell
To support more kinds of user services, ATM divides service information streams of users into
small units in fixed length, namely, ATM cells, and then multiplexes and exchanges the cells.
An ATM cell is always 53 byte in length, including a 5-byte cell header and 48-byte user
payload. When passing through the ATM network, an ATM cell is usually transmitted through
one of the two interfaces:
z The UNI interface between the end user and the network
z The NNI interface between two networks
For the two interfaces, the formats of the ATM cell are the same, as shown in Figure 6-13.

HUAWEI MSOFTX3000
Figure 6-13 Formats of the ATM cell
Transmission sequence
8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
1 GFC VPI 1 VPI

2 VPI VCI 2 VPI VCI
3 VCI 3 VCI
CL CL
4 VCI PT P 4 VCI PT P
5 HEC 5 HEC
6 6
User payload User payload

53 53
UNI cell format NNI cell format
The following describes the fields in the ATM cell header:

z GFC: It is used only for the UNI interface. It controls the traffic flow during an ATM
connection to avoid overload at the user equipment (UE) side.
z VPI and VCI: It defines a specific local connection on a specific link. It is used mainly for
routing.
z PT: It contains user information and service adaptation information. It specifies whether
the cell payload is user data or management data.
z CLP: It defines the sequence of loss of cells. The priority of the cell with CLP set to 0 is
higher than that of the cell with CLP set to 1, that is, the cell with CLP set to 1 is discarded
before the cell with CLP set to 0.
z HEC: It detects and controls the error in the ATM cell header. It provides cell delimitation.
Physical Transmission Mode of ATM Signaling

The ATM signaling can be transmitted on the ATM 155-Mbit/s, ATM 2-Mbit/s and IMA E1
interface. Therefore, the MSOFTX3000 has such features as flexible networking, easy
expansion and low cost. The following describes the three physical transmission modes:
z ATM 155-Mbit/s interface: Complying with ITU-T I.432 recommendations, the
MSOFTX3000 multiplexes an ATM cell stream into a data subrack in the format of
STM-1 or OC-3 on the physical layer, and then is connected to the ATM device through
the optical interface.
z ATM 2-Mbit/s interface: It is a kind of ATM UNI interface. Complying with ITU-T G.804
recommendations, the MSOFTX3000 maps an ATM cell stream onto a PCM data subrack
over an E1 link on the physical layer, and then is connected to the ATM device through the
E1 interface.
z IMA E1 interface: Inverse multiplexing ATM (IMA) reversely multiplexes an ATM cell
stream onto several E1 or T1 links for transmission, and then restores them to a single
ATM cell stream remotely. In this way, several low-rate physical connections are
multiplexed into a high-rate logical connection. The IMA E1 interface of the

HUAWEI MSOFTX3000
MSOFTX3000 can reversely multiplex an ATM cell stream onto one to eight E1 or T1
links. The highest transmission rate is 16 Mbit/s.
Although both the transmission on the ATM 2-Mbit/s interface and that on the IMA E1 interface
are based on the E1 link physically, they differ in multiplexing:
z The ATM 2-Mbit/s does not encapsulate an IMA control protocol message (ICP) and only
multiplexes an ATM cell stream onto an E1 link. The multiplexing is simple, but the
transmission bandwidth is limited.
z The IMA E1 interface takes turns to distribute all cells on several E1 links in sequence by
cyclic multiplexing, and then encapsulates an ICP message. The byte of the ICP message
indicates the mapping between two E1 links. Several E1 interfaces are bound through the
encapsulation. In this way, the transmission bandwidth is enhanced.
PVC
The ATM signaling is a connection-oriented protocol. That is, the ATM network transmits
information only after the virtual connection of the communication entities in the network is
created. The ATM virtual connection includes permanent virtual connection (PVC) and
switched virtual connection (SVC). PVC is the permanent hardware circuit connection between
the source address and the destination address. SVC is the temporary switched circuit
connection required by real-time exchange. The following describes their difference:
z PVC provides connection no matter whether there is data transmission or not.
z SVC is automatically disconnected when the data transmission is complete.
The ATM signaling of the MSOFTX3000 supports PVC and uniquely identifies a PVC
connection between two ATM devices through VPI and VCI in the ATM cell header.
Concept of Links
When you configure the signaling data related to ATM in the MSOFTX3000, such terms as the
ATM, IMA, UNI, PVC, SAAL and MTP3B links are used. Figure 6-14 shows the links.
Figure 6-14 Introduction to links of the ATM signaling

MTP3B user layer
signaling
MTP3B MTP3B link
SAAL SAAL link
ATM layer PVC link
Physical layer
For the ATM 155-Mbit/s optical interface: ATM link
For the ATM 2-Mbit/s interface: UNI link
Structure of ATM protocol stack For the IMA E1 interface: IMA link

HUAWEI MSOFTX3000

Configuration Relationship
ATM signaling data is a type of interworking data of the MSOFTX3000. It defines the data
related to the ATM PVC link when the MSOFTX3000 interworks with the MGW, RNC or MSC
server. The data includes VPI, VCI and IMA group identification.
When you configure ATM signaling data, parameters such as the module number of the WAFM,
WEAM and WBSG defined in hardware data are used in ATM signaling data. Table 6-21 shows
the referencing relationship.
Table 6-21 Input parameters needed by ATM signaling data

The module number of ADD BRD Hardware data ADD PVCLNK

the WAFM
The module number of ADD BRD Hardware data ADD IMAGRP
the WEAM ADD UNILNK
ADD PVCLNK
The module number of ADD BRD Hardware data ADD PVCLNK
the WBSG
ATM signaling data defines PVC link number. This key parameter is used during the
configuration of MTP3B signaling data. Table 6-22 shows the referencing relationship.
Table 6-22 Input parameters required by ATM signaling data

PVC link number ADD PVCLNK ADD MTP3BLNK MTP3B signaling

data
Preparations
Before configuring ATM signaling data, make sure that all preparations are done as specified in
Table 6-23.
SN Item Remark
1 Physical transmission It defines whether the ATM 155 Mbit/s interface or

mode of the ATM the IMA E1 interface is adopted to transmit the ATM
signaling signaling between the MSOFTX3000 and the ATM
device.
2 VPI It is a parameter for interworking with the ATM
device.

HUAWEI MSOFTX3000
SN Item Remark
3 VCI It is a parameter for interworking with the ATM

device.
4 IMA group ID (optional) It is a parameter for interworking with the ATM
device when the IMA E1 interface is adopted to
transmit the ATM signaling.
Configuration Steps
Table 6-24 lists the general steps for configuring ATM signaling data when the ATM
155-Mbit/s interface is adopted to transmit the ATM signaling.

1 Set an ATM link type (optional). SET ATMLNKTYPE

2 Add a PVC link. ADD PVCLNK
3 Modify an SAAL link parameter (optional). MOD SAALPARA
Table 6-25 lists the general steps for configuring ATM signaling data when the IMA E1
interface is adopted to transmit the ATM signaling.

1 Add an IMA group. ADD IMAGRP

2 Add an IMA link. ADD IMALNK
Table 6-26 lists the general steps for configuring ATM signaling data when the ATM 2-Mbit/s
interface is adopted to transmit the ATM signaling.

1 Add a UNI link. ADD UNILNK


HUAWEI MSOFTX3000
Parameter referencing relationship

Figure 6-15 shows the referencing relationship between key parameters used when ATM
signaling data is configured.
ADD IMAGRP
WEAM module number
IMA group number
IMA group ID
ADD IMALNK
WEAM module number
IMA group number
E1 port number
ADD UNILNK
WEAM module number
E1 port number
Scramble switch
ADD PVCLNK MOD SAALPARA

PVC link number PVC link number
IMA group number Maximum CC
E1 port number Maximum PD
6.7.3 Setting ATM Link Type (Optional)

Related Commands
Command Function
SET ATMLNKTYPE To set an ATM link type

LST ATMLNKTYPE To list ATM link types
This configuration is optional. Before starting the data configuration, read the following
descriptions.

HUAWEI MSOFTX3000
z This command is used when the ATM 155-Mbit/s optical interface is adopted to transmit
the ATM signaling between the MSOFTX3000 and the ATM device.
z When a WAFM is added with ADD BRD, the ATM port of the WAFM adopts STM-1
subrack structure (SDH standard) by default. To change the subrack structure of the ATM
port to OC-3 (SONET standard), set the ATM link type with SET ATMLNKTYPE.
Subrack number, Slot number
They define the location of the WAFM, the ATM type (the subrack structure of the ATM port)
of which is to be set, in the subrack.
ATM link type
It defines the subrack structure of the ATM link (ATM port) provided by the WAFM. The
following describes the parameters:
z STM_1: The ATM port adopts STM-1 subrack structure (SDH standard).
z OC_3: The ATM port adopts OC-3 subrack structure (SONET standard).
6.7.4 Adding IMA Group

Related Commands
Command Function
ADD IMAGRP To add an IMA group

RMV IMAGRP To remove an IMA group
MOD IMAGRP To modify an IMA group
LST IMAGRP To list IMA groups
This command is used when the IMA E1 interface is adopted to transmit the ATM signaling
between the MSOFTX3000 and the ATM device.
WEAM module number
It defines the module number of the WEAM reversely multiplexing an ATM cell stream at the
MSOFTX3000 side. This parameter is defined by ADD BRD before it can be used here.
You cannot configure an IMA link and an ATM UNI link for a WEAM simultaneously.
IMA group number
It defines an IMA group in the configuration database of the MSOFTX3000. The WEPI, the
back board of the WEAM, can provide up to eight E1 ports. If each IMA group is bound to one
E1 port, a WEAM can provide up to eight IMA groups. Therefore, the value of this parameter
ranges from 0 to 7.

HUAWEI MSOFTX3000
IMA group ID
It is a parameter for interworking with the ATM device. It identifies several E1 links as an IMA
E1 interface when the IMA E1 interface encapsulates an ICP message.
The IMA E1 interface takes turns to distribute all ATM cells on several E1 links in sequence by
cyclic multiplexing, and then encapsulates an ICP message. The byte of the ICP (IMA group ID)
indicates the mapping between two E1 links. Several E1 interfaces are bound through the
encapsulation.
IMA subrack length
It is a parameter for interworking with the ATM device. It defines the length of an IMA data
subrack after the MSOFTX3000 encapsulates an ICP message of an ATM cell stream. The
default value is 128bit.
IMA maximum time delay
For the IMA data subracks with the same IMA group ID received by the MSOFTX3000, this
parameter defines the maximum time delay allowed between the first subrack and the last one.
Its value ranges from 0 to 200. The unit is ms. The default value is 200.
IMA version
It is a parameter for interworking with the ATM device. It defines that the IMA protocol at the
MSOFTX3000 side complies with IMA 1.0 or IMA 1.1. The default value is Version 1.1.
IMA 1.0 and IMA 1.1 are two versions specified by ATM Forum for the IMA protocol. The
IMA groups of different versions cannot interwork.
Scramble switch
It is a parameter for interworking with the ATM device. It defines whether the MSOFTX3000
checks errors in data subracks when sending IMA data subracks over the E1 link. The default
value is Yes.
E1 time slot mode
uses slot 0 and slot 16 of each E1 link when sending IMA data subracks over the E1 link. The
default value is Do not use slot 0 and slot 16.
6.7.5 Adding IMA Link

Related Commands
Command Function
ADD IMALNK To add an IMA link

RMV IMALNK To remove an IMA link
LST IMALNK To list IMA links

HUAWEI MSOFTX3000
This command is used when the IMA E1 interface is adopted to transmit the ATM signaling
between the MSOFTX3000 and the ATM device.
WEAM module number
It defines the module number of the WEAM reversely multiplexing an ATM cell stream at the
MSOFTX3000 side. This parameter is defined by ADD BRD before it can be used here.
IMA group number
It defines to which IMA group the IMA link to be configured belongs. This parameter is defined
by ADD IMAGRP before it can be used here.
E1 port number
It defines to which E1 port on the WEPI the IMA link to be configured corresponds physically,
that is, which E1 port is bound to the IMA group specified by this command. If only one IMA
group is defined in the WEAM, up to eight E1 ports can be bound to the IMA group.
6.7.6 Adding UNI Link

Related Commands
Command Function
ADD UNILNK To add a UNI link

RMV UNILNK To remove a UNI link
MOD UNILNK To modify a UNI link
LST UNILNK To list UNI links
This command is used when the ATM 2-Mbit/s interface (an ATM UNI interface) is adopted to
transmit the ATM signaling between the MSOFTX3000 and the ATM device.
WEAM module number
It defines the module number of the WEAM performing PCM multiplexing on an ATM cell
stream (mapping the ATM cell stream onto an E1 subrack) at the MSOFTX3000 side. This
parameter is defined by ADD BRD before it can be used here.
E1 port number

HUAWEI MSOFTX3000
It defines to which E1 port on the WEPI the UNI link to be configured corresponds physically.
Scramble switch
checks errors in data subracks when sending PCM data subracks over an E1 link. The default
value is Yes.
E1 time slot mode
uses slot 0 and slot 16 of the E1 link when sending PCM data subracks over an E1 link. The
default value is Do not use slot 0 and slot 16.
6.7.7 Adding PVC Link

Related Commands
Command Function
ADD PVCLNK To add a PVC link

RMV PVCLNK To remove a PVC link
MOD PVCLNK To modify a PVC link
LST PVCLNK To list PVC links
Irrespective of which physical mode (including the ATM 155-Mbit/s interface, the ATM
2-Mbit/s interface and the IMA E1 interface) is adopted to transmit the ATM signaling, you
should configure the PVC link between the MSOFTX3000 and the ATM device. Otherwise, the
ATM interface does not work.
PVC link number
It defines a PVC link in the configuration database of the MSOFTX3000. Its value ranges from
0 to 999. To ensure reliable signaling transmission, you are advised to logically divide a whole
physical ATM link into several PVC links evenly based on the bandwidth (2.048 Mbit/s) of an
E1 link. For example, if an IMA link is bound to four E1 links, you are advised to configure four
PVC links. You are also advised to configure one PVC link for each ATM UNI link.
Virtual path identifier
It is a parameter for interworking with the ATM device. VPI and VCI in the ATM cell header
uniquely identify a PVC link. This parameter defines the value of VPI in the ATM cell header.
Its value ranges from 0 to 255.
Virtual path identifier
It is a parameter for interworking with the ATM device. VPI and VCI in the ATM cell header
uniquely identify a PVC link. This parameter defines the value of VCI in the ATM cell header.
Its value ranges from 0 to 1023.

HUAWEI MSOFTX3000
Flow type
It is a parameter for interworking with the ATM device. The field is reserved. Currently, you
should choose CBR.
Peak cell rate(kbit/s)
As a QoS parameter, it defines the maximum transmission rate when the MSOFTX3000 sends
ATM cells over the PVC link. The value ranges from 0 to 150000. The unit is kbit/s. The default
value is 1920.
To ensure the QoS when the ATM network resources are fully made use of, ATM Forum has
some principles in the UNI signaling. According to the principles, the user system provides its
requirements (a series of QoS parameters) for service quality during the establishment of the
virtual circuit. The network decides whether to receive the requirements. Once the requirements
are received, the network controls the traffic flow over all links. The packets overloaded with
traffic are intercepted to avoid network congestion and overload.
Sustainable cell rate(kbit/s)
As a QoS parameter, it defines the average transmission rate when the MSOFTX3000 sends
value is 1920. The configuration principles are as follows:
z During configuration, the relationship among the QoS parameters is minimum cell rate
(MCR) ≤ sustainable cell rate (SCR) ≤ peak cell rate (PCR).
z You are advised to logically divide a whole physical ATM link into several PVC links
evenly based on the bandwidth (2.048 Mbit/s) of an E1 link. At this time, the SCR of a
PVC link is set to 1920 kbit/s, which equals the bandwidth of an E1 link when neither slot
0 nor slot 16 is used.
z If the bandwidth of a physical ATM link equals that of several (such as N) El links and the
ATM link is logically defined as one PVC link, the SCR of the PVC link is N x 1920 kbit/s.
The MCR and PCR should be adjusted accordingly.
Minimum cell rate(kbit/s)
As a QoS parameter, it defines the minimum transmission rate when the MSOFTX3000 sends
value is 1920.
Maximum burst size
As a QoS parameter, it defines the maximum number of the ATM cells allowed when the
MSOFTX3000 sends ATM cells over the PVC link at PCR. The value ranges from 0 to 65535.
The default value is 0, indicating no limitation.
Signaling dispatch module number (WAFM/WEAM)
It defines the module number of the WAFM or WEAM performing ATM layer processing
functions, including:
z Creating and extracting the ATM cell header
z Converting VPI and VCI of the ATM cell
z Multiplexing and Demultiplexing the ATM cell
This parameter is defined by ADD BRD before it can be used here. The configuration
principles are as follows:
z For the ATM 155-Mbit/s interface, type in the module number of the WAFM.

HUAWEI MSOFTX3000
z For the ATM 2-Mbit/s interface, type in the module number of the WEAM.
Signaling handling module number (WBSG/WAFM/WEAM)
It defines the module number of the WBSG, WAFM or WEAM performing SAAL and MTP3B
layer processing functions.
SAAL layer processing functions include:
z Mapping the protocol data unit (PDU) message on the MTP3B layer onto the SAR
sub-layer
z Defining, disassembling and reinstalling the PDU message on the MTP3B layer
MTP3B layer processing functions refer to transferring and distributing the MTP3B messages,
including identification, distribution and routing control of the MTP3B messages. This
parameter is defined by ADD BRD before it can be used here.
Although the WAFM and WEAM can accomplish the SAAL and MTP3B processing functions,
you are advised to separate the signaling processing functions and the signaling distribution
functions of the WAFM or WEAM to ensure reliability of the system, that is, only configure the
signaling processing functions only on the WBSG.
Bearer type
It defines the physical bearer mode of the ATM signaling at the MSOFTX3000 side. The
following describes the parameter options:
z Fiber: The ATM 155-Mbit/s optical interface is adopted to bear the ATM signaling. At this
time, the specified WAFM provides the PVC link.
z Inverse multiplexing for ATM: The IMA E1 interface is adopted to bear the ATM
signaling. At this time, you should define IMA group number.
z User network interface: The ATM 2-Mbit/s (ATM UNI) interface is adopted to bear the
ATM signaling. At this time, you should define E1 port number.
IMA group number
It is valid only when Bearer type is set to Inverse multiplexing for ATM. It defines to which
IMA group the IMA E1 interface bearing the ATM signaling belongs. This parameter is defined
by ADD IMAGRP before it can be used here.
E1 port number
It is valid only when Bearer type is set to User network interface. It defines the E1 port
number on the WEPI, to which the ATM 2-Mbit/s (ATM UNI) interface bearing the ATM
signaling corresponds physically. This parameter is defined by ADD UNILNK before it can be
used here.
6.7.8 Modifying SAAL Link Parameter (Optional)

Related Commands
Command Function
MOD SAALPARA To modify an SAAL link parameter

LST SAALPARA To list SAAL link parameters

HUAWEI MSOFTX3000
This configuration is optional. Before starting the data configuration, read the following
descriptions.
When the MSOFTX3000 interworks with the ATM device through the PVC link, you do not
need to modify the related parameters of the PVC link on the SAAL layer. When the
MSOFTX3000 adopts the ATM 2-Mbit/s interface or the IMA E1 interface to transmit the ATM
signaling, if there are special service demands, or some special requirements for quality of link,
rate of link, response delay or window of receiving buffer, you need to modify the related
parameters of the PVC link on the SAAL layer.
Note that the initial value is the value preset during system initialization and can be queried by
LST SAALPARA.
PVC link number
It defines the number of the PVC link whose SAAL link parameters are to be modified. This
parameter is defined by ADD PVCLNK before it can be used here.
CC timer (ms)
It defines the maximum duration for the MSOFTX3000 to wait for the response from the ATM
device after the MSOFTX3000 sends PDU messages such as the BGN, END, RS and ER
message. The value ranges from 0 to 32767. The unit is ms. The initial value is 200. When the
physical channel transmitting the ATM signal includes satellite circuits, set the parameter to
700.
If the MSOFTX3000 does not receive any response from the ATM device within the duration,
the MSOFTX3000 sends the PDU message to the ATM device again. When the times of the
MSOFTX3000's sending the same PDU message exceeds the value defined in Maximum CC,
the MSOFTX3000 does not send the PDU message any more, and an alarm is generated on the
alarm subsystem.
Poll timer(ms)
It defines the duration for the MSOFTX3000 to wait for the STAT PDU message from the ATM
device after the MSOFTX3000 sends the POLL PDU message (requesting status query) to the
ATM device. The value ranges from 0 to 32767. The unit is ms. The initial value is 100. The
z This parameter is larger than the average duration from sending a message to receiving a
response to this message.
z The sum of this parameter and the average duration from sending a message to receiving a
response to this message is less than the value of No response timer(ms).
If the MSOFTX3000 does not receive the STAT PDU message from the ATM device within the
duration specified by the Poll timer, the related SAAL link becomes transient. At the same time,
the MSOFTX3000 starts the Keep alive timer.
Idle timer(ms)
If the MSOFTX3000 receives the STAT PDU message from the ATM device after sending the
POLL PDU message to the ATM device, this parameter defines the maximum duration allowed
before the MSOFTX3000 sends next SD PDU message. The value ranges from 0 to 32767. The
unit is ms. The initial value is 100.

HUAWEI MSOFTX3000
If the MSOFTX3000 does not send the SD PDU message within the duration specified by the
Idle timer, the related SAAL link enters transient mode. At the same time, the MSOFTX3000
starts the Keep alive timer.
No response timer(ms)
It defines the maximum duration for the MSOFTX3000 to wait for the STAT PDU message
from the ATM device after the MSOFTX3000 sends the POLL PDU message to the ATM
device. The value ranges from 0 to 32767. The unit is ms. The initial value is 1500. The
z The value of No response timer(ms) is larger than that of Idle timer(ms).
z The value of No response timer(ms) is larger than the sum of the average duration from
sending a message to receiving a response to this message and the value of Poll
timer(ms).
z The value of No response timer(ms) is larger than the sum of the average duration from
sending a message to receiving a response to this message and the value of Keep
alive(ms).
If the MSOFTX3000 does not receive the STAT PDU message from the ATM device within the
duration specified in No response timer(ms), the MSOFTX3000 considers the SAAL link is
broken (out of location). At this time, the MSOFTX3000 needs to relocate the SAAL link.
Keep alive timer(ms)
When the SAAL link enters transient mode because of time-out of the Poll timer or Idle timer,
this parameter defines the maximum duration for the SAAL link to keep in the transient mode.
The value ranges from 0 to 32767. The unit is ms. The initial value is 100.
An SAAL link in transient mode cannot send the POLL PDU message. Within the duration
specified by the Keep alive timer, if the MSOFTX3000 sends the SD PDU message through the
SAAL link, or the MSOFTX3000 receives the SD PDU message from the ATM device through
the SAAL link, or the Keep alive timer times out, the SAAL link is activated again.
T1 timer(ms)
When the SAAL link is broken, the MSOFTX3000 sends request to the ATM device for setting
up the link in the sequence of BGN→BGN→BGN→BGN→END periodically until the link is
successfully set up. The T1 timer defines the interval between two sending periods, for instance,
the interval between the END PDU message sent in last period and the BGN PDU message sent
in the existing period. The value ranges from 0 to 32767. The unit is second. The initial value is
5.
T2 timer(ms)
When the SAAL link is broken, the MSOFTX3000 sends request to the ATM device for setting
up the link in the sequence of BGN→BGN→BGN→BGN→END periodically until the link is
successfully set up. The T2 timer defines the maximum link setup period (relocation period)
allowed by the MSOFTX3000. The value ranges from 0 to 32767. The unit is second. The
initial value is 30.
If the MSOFTX3000 fails in setting up the link within the duration specified by the T2 timer,
the SAAL software module sends a message to the MTP3B software module inside the
software of the MSOFTX3000, indicating loss of link location. At this time, the timer of the
MTP3B decides when the request for setting up the SAAL link is sent again.
T3 timer(ms)

HUAWEI MSOFTX3000
It defines the period of sending request for proving the PDU message in a normal proving
process. The value ranges from 0 to 32767. The unit is ms. The initial value is 10.
Maximum CC
It defines the maximum times for the MSOFTX3000 to send the same PDU message
continuously if the MSOFTX3000 does not receive the response from the ATM device after the
MSOFTX3000 sends such PDU messages as the BGN, END, RS and ER message to the ATM
device. The value ranges from 0 to 32767. The initial value is 4.
Maximum PD
It defines the maximum number of the SD PDU message that the MSOFTX3000 can send
before sending the POLL PDU message to the ATM device. The value ranges from 0 to 32767.
The initial value is 500. The following describes the referencing relationship between the
parameter and the Poll timer:
z If the number of the SD PDU message sent from the MSOFTX3000 to the ATM device
within the duration specified by the Poll timer is less than or equals the value of
Maximum PD, the MSOFTX3000 sends the POLL PDU message to the ATM device
periodically based on the duration specified by the Poll timer.
z If the number of the SD PDU message sent from the MSOFTX3000 to the ATM device
within the duration specified by the Poll timer exceeds the value of Maximum PD, the
MSOFTX3000 sends the POLL PDU message to the ATM device at once and clears the
Poll timer.
The POLL PDU message (status request) and the SD PDU message (sequenced data) are two
message units on the SSCOP sub-layer of the SAAL layer. The POLL PDU message is used to
request the status of the peer SSCOP entity. The SD PDU message is used to send user service
data to the peer SSCOP entity in sequence.
Maximum STAT
The MSOFTX3000 receives an STAT PDU message from the ATM device after sending the
POLL PDU message to the ATM device. This parameter defines the maximum number of the
list elements that the STAT PDU message can contain. The value ranges from 0 to 32767. The
initial value is 67.
The STAT PDU message (solicited status response) is the response to the POLL PDU message,
informing the SSCOP entity of the receiving of the related packet (SD PDU), including which
SD PDU messages are received and which ones are not received. The STAT PDU message also
updates the location of the sending window to control the maximum number of the SD PDU
message to be sent currently.
N1
It defines the maximum number of the PDU messages allowed to be sent in a normal proving
process. The value ranges from 0 to 32767. The initial value is 1000.
Maximum NRP
It defines the maximum number of the PDU messages allowed to be sent in a normal proving
process. The value ranges from 0 to 32767. The initial value is 0.
Repeat SREC timer (min)
The Repeat SREC timer is the management timer of the SAAL layer. It is unnecessary to
modify the timer. The value ranges from 0 to 32767. The unit is minute. The initial value is 60.
No credit timer (ms)

HUAWEI MSOFTX3000
The No credit timer is the management timer of the SAAL layer. It is unnecessary to modify the
timer. The value ranges from 0 to 32767. The unit is ms. The initial value is 1500.
Window size
It is a parameter for interworking with the ATM device. It defines the maximum number of the
SD PDU message allowed to be sent during a process. The value ranges from 0 to 32767. The
initial value is 256. This function controls flow on SAAL links.
6.8 Configuring MTP3B Data

MTP3B
MTP3B refer to broadband MTP3. It is ATM-based and is a protocol extended from MTP3.
MTP3B, supported by SAAL, bears signaling messages of MTP3B user layer. In the
MSOFTX3000, MTP3B has the following applications:
z When the signaling protocol of MTP3B user layer is H.248, it offers Mc interface between
the MSOFTX3000 and the MGW. The protocol stack is H.248/MTP3B/SAAL/ATM.
z When the signaling protocol of MTP3B user layer is SCCP, it offers Iu-CS interface
between the MSOFTX3000 and RNC. The protocol stack is
RANAP/TCAP/SCCP/MTP3B/SAAL/ ATM.
z When the signaling protocol of MTP3B user layer is BICC, it offers Nc interface between
the MSOFTX3000 and other MSC servers. The protocol stack is
BICC/MTP3B/SAAL/ATM.
MTP3B and MTP3

The difference between MTP3B and MTP3 are listed as follows:
z On the link layer, MTP3 uses MTP2, while MTP3B uses SAAL (SSCOP and SSCF). On
the physical layer, MTP3 uses TDM, while MTP3B uses ATM PVC.
z MTP3B increases the length of subscriber data in a signaling unit to a maximum of 4091
bytes, while for MTP3, the maximum is 272 bytes.
z Besides user layer signaling of SCCP, MTP3B supports that of H.248 and BICC, which
MTP3 does not support.
Link Selection Mask and Linkset Selection Mask

For the information of the two masks, refer to 6.6.1 "Related Concepts."
6.8.2 Overview
Relationship Between Configuration Steps
MTP3B signaling data defines the MTP3B link-related information when the MSOFTX3000
interconnects equipment such as the MGW, RNC, MSC server, HLR and SGSN. The
information includes OPC, DPC, and SLC.

HUAWEI MSOFTX3000
MTP3B data uses the parameters OPC and PVC link number that are defined in office data and
ATM data respectively. Table 6-27 shows the input parameters referencing relationship.
Table 6-27 Input parameters referencing relationship

OPC SET OFI / ADD OFI Office data SET MTP3BOSP

PVC link number ADD PVCLNK ATM data ADD MTP3BLNK
MTP3B data defines the parameter MTP3B DPC that is used in SCCP data, route data and
MGW data. Table 6-28 shows the output parameter referencing relationship.
Table 6-28 Output parameter referencing relationship

MTP3B DPC ADD MTP3BDSP ADD SCCPDSP SCCP data

ADD OFC Route data
ADD MGW MGW data
Preparations
Before MTP3B data configuration, ensure that all preparations are done as specified in Table
6-29

SN Item Remark
1 Destination One of the interworking parameters between the

signaling point code MSOFTX3000 and the peer end SS7 signaling equipment
2 STP flag One of the interworking parameters between the
MSOFTX3000 and the peer end SS7 signaling equipment
3 Signaling link code One of the interworking parameters between the
MSOFTX3000 and the peer end SS7 signaling equipment
Configuration Steps
Table 6-30 lists the general steps for configuring MTP3B data.

HUAWEI MSOFTX3000
1 Set an MTP3B OSP (optional). SET MTP3BOSP

2 Add an MTP3B DSP. ADD MTP3BDSP
3 Add an MTP3B linkset. ADD MTP3BLKS
4 Add an MTP3B link. ADD MTP3BLNK
5 Add an MTP3B route. ADD MTP3BRT

Figure 6-16 shows the parameter referencing relationship for MTP3B data configuration.
ADD MTP3BDSP
DSP index
DSP name
DPC
ADD MTP3BLKS
Linkset index
Linkset name
DSP index
ADD MTP3BLNK
Link name
Linkset index
Signaling link code
ADD MTP3BRT
Route name
DSP index
Linkset index

HUAWEI MSOFTX3000
6.8.3 Setting MTP3B OSP (Optional)

Related Commands
Command Function
SET MTP3BOSP To set an MTP3B originating signaling point

LST MTP3BOSP To list an MTP3B originating signaling point
The step is optional. Before using the commands, read the notes carefully.
If you configure the local signaling point code by SET OFI or ADD OFI, by default, the code
(OSP index is 0 and network indicator is national network) is MTP3B OSP code. To change it,
use SET MTP3BOSP to set another MTP3B OSP.
Network indicator
It is one of the interworking parameters between the MSOFTX3000 and MTP3B signaling
equipment. It defines a type of the signaling network to which the MTP3B OSP belongs. The
parameter options include:
z International network
z International reserved network,
z National network
z National reserved network
The default value is national network.
The value of Network indicator set by SET MTP3BOSP must be consistent with that set by SET OFI or
ADD OFI. Otherwise, an error occurs.
OPC
It is one of the interworking parameters between the MSOFTX3000 and the MTP3B signaling
equipment. It defines an OPC carried in MTP3B messages and sent to peer office. The field
type is hexadecimal numeral. The maximum length is six.
STP function flag
It defines whether the local MSOFTX3000 has STP function. In other words, if the local office
can exchange SS7 messages in broadband SS7 network, set the parameter to Yes. The default
value is No.

HUAWEI MSOFTX3000
6.8.4 Adding MTP3B DSP

Related Commands
Command Function
ADD MTP3BDSP To add an MTP3B DSP

RMV MTP3BDSP To remove an MTP3B DSP
MOD MTP3BDSP To modify an MTP3B DSP
LST MTP3BDSP To list an MTP3B DSP
DSP index
It defines a DSP in the MSOFTX3000. The value range is from 0 to 65534.
DSP name
It specifies a DSP. The field type is character string.
Network indicator
equipment. It defines a type of the signaling network to which the DPC of the DSP belongs. The
parameter options include:
z International network
z International reserved network
z National network
z National reserved network
The default value is national network.
DPC
equipment. It defines a code for a DSP in SS7. The DPC set here cannot be the same as that set
by ADD N7DSP and ADD M3DE.
Adjacent flag
It defines whether there are direct MTP3B signaling routes between the MSOFTX3000 and a
z If the peer end equipment is the STP that connects the MSOFTX3000 in associated mode,
set the parameter to Yes.
z If the peer end equipment is the MGW, RNC, MSC server, HLR or SCP that connects with
the MSOFTX3000 in associated mode, set the parameter to Yes.
z If the peer end equipment is the MGW, RNC, MSC server, HLR or SCP that connects the
MSOFTX3000 in quasi-associated mode, in other words, an STP is needed to forward
signaling, set the parameter to No.

HUAWEI MSOFTX3000
STP flag
It defines whether a DSP has STP function. If the DSP is the STP equipment that connects the
MSOFTX3000 in associated mode, set the parameter to Yes. Otherwise, set it to No.
It is used to achieve load-sharing among multiple MTP3B linksets from the MSOFTX3000 to a
z If there is a linkset between the MSOFTX3000 and a DSP, set the parameter to the default
value B1111.
z If the number of the linkset is more than one, ensure that the decimal value of the linkset
selection mask ≥ the total number of linksets – 1 For example, if the total number of
linksets is two, you cannot set the parameter to B0000.
6.8.5 Adding MTP3B Linkset

Related Commands
Command Function
ADD MTP3BLKS To add MTP3B linkset

RMV MTP3BLKS To remove MTP3B linkset
MOD MTP3BLKS To modify MTP3B linkset
LST MTP3BLKS To list MTP3B linkset
Linkset index
It defines a linkset in the MSOFTX3000. The value range is from 0 to 65534. A linkset
represents a signaling route, therefore you can configure only one MTP3B linkset between the
MSOFTX3000 and an adjacent DSP.
Linkset name
It specifies the name of the linkset. The field type is character string.
Link selection mask
It is used to achieve load-sharing among multiple MTP links in a linkset. The configuration
principle is as follows:
z If there is a link in a linkset, set the parameter to the default value B1111.
z If the number of the links in a linkset is more than one, ensure that the decimal value of the
link selection mask ≥ the total number of links – 1. For example, if the total number of
links is two, you cannot set the parameter to B0000.

HUAWEI MSOFTX3000
two different values. It is suggested to set the two masks with entirely different choice of 0
and 1 in the same bit. For example, if the linkset selection mask is 0110, set the link
selection mask to 1001.
Emergency flag
It defines whether to adopt emergency locating program when the MTP3B link is initially
activated or recover from faults. If it is set to No (by default), normal locating program is used.
If it is set to Yes, emergency locating program is used. In emergency locating program, the
acceptance cycle of SAAL link setup is shorter than normal locating program.
6.8.6 Adding MTP3B Link

Related Commands
Command Function
ADD MTP3BLNK To add an MTP3B link

RMV MTP3BLNK To remove an MTP3B link
MOD MTP3BLNK To modify an MTP3B link
LST MTP3BLNK To list an MTP3B link
Link name
It specifies the name of the link. The field type is character string.
Linkset index
It defines the linkset to which the MTP3B link belongs. The parameter must be defined by ADD
MTP3BLKS before it can be used here.
Signaling link code
It defines the logical number of the MTP link in its linkset. The parameter is one of the
interworking parameters between the MSOFTX3000 and MTP3B signaling equipment (in
associated mode). According to MTP3B protocol, SLC is a 4-bit binary code. The decimal
value range is from 0 to 15. In addition, SLC of signaling links within the same linkset cannot
be the same.
PVC link number
It defines a number for ATM PVC link that bears MTP3B signaling messages. The parameter
must be defined by ADD PVCLNK before it can be used here.
Priority
It specifies the link priority levels. The link with higher priority level is preferential. When it is
unavailable, the lower priority level link can bear signaling service. The highest priority level is
0, 1 ranks the next and so on.
Test code length

HUAWEI MSOFTX3000
It specifies the length of the test code padded in SLTM message for MTP3B link test. The
parameter range is from 1 to 15. The unit is byte. The default value is 10.
Test code
It specifies a test code padded in SLTM message for MTP3B link test. The parameter value is
2-bit hexadecimal code (0-9, A-F). The default value is AA.
The test code is used for testing the availability of MTP3B link. In other words, when the SLTM
message is sent, the peer end responds with the SLTA message.
6.8.7 Adding MTP3B Route

Related Commands
Command Function
ADD MTP3BRT To add an MTP3B route

RMV MTP3BRT To remove an MTP3B route
MOD MTP3BRT To modify an MTP3B route
LST MTP3BRT To list an MTP3B route
Route name
It specifies the name of the route. The field type is character string.
DSP index
It defines the DSP for the MTP3B route. The parameter must be defined by ADD MTP3BDSP
before it can be used here. Note that MTP routes must be configured for all DSPs (except STPs)
defined by ADD MTP3BDSP.
Linkset index
It defines the MTP3B route to a DSP. In other words, it defines the linkset used to transport
signaling. The parameter must be defined by MTP3BLKS before it can be used here.
Priority
It specifies the linkset (signaling route) priority levels. The linkset with higher priority level is
preferential. When it is unavailable, the lower priority level linkset can bear signaling service.
The highest priority level is 0, 1 ranks the next and so on.

HUAWEI MSOFTX3000
6.9 Configuring SCCP Data

Basic Concepts
To meet the requirements for message transfer from the user part of the SS7 such as BSSAP,
RANAP, MAP, CAP, and INAP, the SS7 employs the Signaling Connection Control Part
(SCCP) . SCCP provides supplementary functions for the Message Transfer Part (MTP),
realizing packet switching of virtual circuits and datagram that helps the SS7 network:
z Set up connectionless and connection-oriented services between the MSC and other
devices in the telecom network such as the BSC, RNC, HLR, MSC, SGSN and GMLC
through the SS7 network
z Transfer circuit-related and non-circuit-related signaling information and other
information like that about maintenance and management
SCCP completes the functions of MTP in the network layer. Together with MTP3, it functions
as the network layer in the OSI model. It equals interworking in an open system and realizes
transparent transmission.
SCCP Sub-System Number

SCCP has the supplementary addressing function. It provides sub-system numbers (SSNs) that
can identify more SCCP subscribers within one signaling point (SP). An SSN is a binary code
with eight bits. The SSNs often used contain:
z ISUP: ISDN User Part
z BSSAP: Base Station Subsystem Application Part
z RANAP: Radio Access Network Application Part
z SCMG: SCCP Management Part
z OMAP: Operation and Maintenance Application Part
z MAP: Mobile Application Part
z HLR: Home Location Register
z VLR: Visited Location Register
z MSC: Mobile Switching Center
z EIR: Equipment Identity Register
z SMC: Short Message Center
z AUC: Authentication Center
z INAP: Intelligent Network Application Part
z CAP: CAMEL Application Part
z GMLC: Gateway Mobile Location Center
z SGSN: Serving GPRS Support Node
z GGSN: Gateway GPRS Support Node
Among the preceding SSNs, ISUP, BSSAP, and RANAP use the connection-oriented services
of SCCP while the others use the connectionless services.

HUAWEI MSOFTX3000
SCCP Global Title

SCCP also provides the address translation function. Its address is a combination of the global
title (GT) code, destination signaling point code (DPC) and SSN. Generally speaking, the GT is
the number to be dialed, such as an international telephone number and ISDN number. Since it
does not represent the route information in its signaling network, the route information can be
obtained only by translating the GT. The GT has global significance and its address scope is
much larger than that of DPC which is only meaningful in its signaling network. It facilitates
the transmission of the message irrelevant to circuit between any two signaling points in the
world. The powerful addressing ability of the GT is a distinctive feature of SCCP.
Address Indicator Format of SCCP Message

The addressing function of SCCP is based on the route flag field and the calling/called address
field in an SCCP message. The route flag field contains the DPC and original signaling point
code (OPC) for routing in the MTP3 layer (3rd layer routing). The calling/called address field
may include the DPC, OPC, and SSN (or GT) for routing in the SCCP layer (4th layer routing).
In an SCCP message, the calling/called address field uses the same format, as shown in Figure
6-17.
Figure 6-17 Format of the calling/called address field in an SCCP message

Address indicator
Address signal
7 6 5 4 3 2 1 0
Sub-
Routing SP
Address Reserved GT indicator system
indicator indicator
signal indicator
n* bit group (8 bits )
In Figure 6-17, the address indicator field represents the address types contained in the
address field. The meaning of each bit is as shown in Table 6-31.
Table 6-31 Meanings of the bits in the address indicator field

Bit Meaning
SP indicator Indicates whether the signaling point code (SPC), that is, OPC or DPC,
is contained in the address.
z 1: contained
z 0: not contained
Sub-system Indicates whether the SSN is contained in the address.
indicator z 1: contained
z 0: not contained.

HUAWEI MSOFTX3000
Bit Meaning
GT indicator z 0000: GT not contained in the address signal

z 0001: Type 1, the GT contains the nature of address indicator and
address information.
z 0010: Type 2, the GT contains the translation type and address
information.
z 0011: Type 3, the GT contains the translation type, numbering
scheme, coding scheme and address information.
z 0100: Type 4, the GT contains the translation type, numbering plan,
coding scheme, nature of the address indicator and address
information.
Routing indicator z 0: that SCCP selects route according to the GT in the called address.
z 1: SCCP selects route according to the DCP in MTP route flag and
SSN in the called address.
In an SCCP message, for connection-oriented services, the calling SCCP address is OPC and
SSN while the called SCCP address is DPC and SSN. For connectionless services, the calling
SCCP address can be either OPC and SSN or GT; the called SCCP address can be either DPC
and SSN or GT.
The SS7 network addresses based on OPC and DPC. So, when the calling SCCP address
contains the GT information but not SPC information, the system has to translate the GT into
corresponding OPC or DPC and thus SCCP can get the route information required by the SS7
network. The MSOFTX3000 enables the system to translate the GT into address of any of the
following formats to obtain route information.
z SPC
z SPC + SSN
z SPC + GT
z SPC + SSN + GT

Configuration Relationship
The SCCP data are for interworking with other devices. They are the data that relate to SCCP
when the MSOFTX3000 interworks with the MSC, BSC, RNC, HLR, SMC, SCP, SGSN and
GMLC.
During the configuration, some parameters defined in the office information data, MTP data,
M3UA data and MTP3B data are used in the SCCP data. Table 6-32 shows the details.
Table 6-32 Input parameters required by SCCP data

Name Defined in Source Data Category Referenced in
OPC SET OFI Office information data ADD SCCPDSP

ADD OFI

HUAWEI MSOFTX3000
Name Defined in Source Data Category Referenced in
DPC ADD N7DSP MTP data ADD SCCPDSP

ADD M3DE M3UA data
ADD MTP3BDSP MTP3B data
Key parameters defined by SCCP data include SCCP DPC and SCCP GT. These parameters are
used in configuring mobile service data and IN service data. Table 6-33 shows the details.
Table 6-33 Output parameters defined by SCCP data

Name Defined in Referenced in Destination
Data Category
DPC ADD SCCPDSP ADD BSC Mobile service

data
ADD RNC
ADD SGSN
SCCP GT ADD SCCPGT ADD GMLC Mobile service
data
ADD SCPINFO Intelligent service
data
Preparations
Before configuring SCCP data, make sure that all preparations are done as specified in Table
6-34.

SN Item Remark
1 SCCP DPC They are the parameters for interworking with

the MSC, BSC, RNC, HLR, SCP, SGSN, and
2 SCCP sub-system number GMLC.
3 SCCP GT
Configuration Steps
Table 6-35 lists the general steps for configuring SCCP data.

HUAWEI MSOFTX3000
1 Add SCCP destination signaling point (DSP). ADD SCCPDSP

2 Add originating address format translation (optional) ADD SCCPADDR
3 Add SCCP sub-system number ADD SCCPSSN
4 Add new GT (optional) ADD SCCPNGT
5 Add SCCP global title. ADD SCCPGT
6 Add SCCP shielding policy (optional). ADD SCCPPOL

Figure 6-18 shows the referencing relationship between key parameters used when SCCP data
is configured.
ADD SCCPDSP
DSP index
Network indicator
DPC
ADD SCCPSSN
SSN index
DPC
OPC
ADD SCCPNGT
New GT index
GT indicator
Translation type
ADD SCCPGT
GT index
SCCP sub-system
number
SPC
New GT index

HUAWEI MSOFTX3000
6.9.3 Adding SCCP Destination Signaling Point

Related Commands
Command Function
ADD SCCPDSP To add an SCCP DSP

RMV SCCPDSP To remove an SCCP DSP
MOD SCCPDSP To modify an SCCP DSP
LST SCCPDSP To list SCCP DSPs
DSP index
It uniquely identifies an SCCP DSP in the configuration database of the MSOFTX3000. Its
value range is 0–65534.
The DSP index here is different from the indexes as follows:
z The DSP index defined with ADD N7DSP
z The DSP index defined with ADD MTP3BDSP
z The destination entity index defined with ADD M3DE
They have no referencing relationship with each other.
Network indicator
The network indicator is one of the interworking parameters between the MSOFTX3000 and
the peer-end equipment. It specifies the signaling network to which the SPC of the peer-end
equipment belongs. The signaling network may be the following network.
z International active network
z International standby network
z National active network
z National standby network
So the network indicator should be set according to the actual networking.
DPC
The DPC is one of the interworking parameters between the MSOFTX3000 and the peer-end
equipment. It specifies the DPC in the SS7 network. It is mandatory and should be defined by
ADD N7DSP, ADD MTP3BDSP or ADD M3DE before it can be used here.
The MAP, BSSAP, RANAP, CAP and INAP are transferred through SCCP. So, when the
MSOFTX3000 is interconnected with the MSC, BSC, RNC, HLR, SMC, SCP, SGSN and
GMLC, the signaling point of the peer-end equipment should be defined as the SCCP DSP.
OPC
It is one of the parameters for the MSOFTX3000 to interwork with devices in the peer office. It
specifies an originating signaling point that the SCCP signaling message carries. The OPC

HUAWEI MSOFTX3000
should be defined by SET OFI or ADD OFI before it can be used here. By default, if you do
not enter the OPC, the OPC is regarded as the local signaling point code defined by SET OFI.
DSP name
It is a character string describing an SCCP DSP.
Load-sharing flag
It defines whether mutual-assistance function is supported for SCCP signaling route between
the MSOFTX3000 and a peer end. The default value is No standby DSP. The parameter
options are as follows:
z No standby DSP
By default, the mutual-assistance function is not supported for SCCP signaling route.
z With standby DSP
Suppose B is the standby node of A. When a local office sends SCCP signaling messages
to A, the messages directly go to A in normal conditions. If the SCCP signaling routing
from the local office to A is unavailable, the messages are sent from the local office to B
before forwarded to A at last. In other words, B has the forward function of SCCP
signaling routing.
z With load-sharing DSP
Suppose B is the load-sharing node of A. When a local office sends SCCP signaling
messages to A, half of the messages go to A. The other half go to B before forwarded to A
at last. In other words, B has the forward function of SCCP signaling routing.
When the SCCP signaling routing between the MSOFTX3000 and signaling equipment such as
HLR addresses with GT of the called subscriber address, the route indicator bit is 0. In this
case, the assistance function of the SCCP DSP can be used to improve the reliability of the
SCCP signaling routing.
Standby DSP index
When the MSOFTX3000 supports the load sharing or standby function, this parameter is
available to specify the standby SCCP signaling point. This parameter should be defined by
ADD SCCPDSP before it can be used here.
This parameter is invoked in the SCCP DSP data table. So it is recommended to define all the
SCCP DSPs with ADD SCCPDSP, and then modify it with MOD SCCPDSP.
6.9.4 Adding Originating Address Format Translation (Optional)

Related Commands
Command Function
ADD SCCPADDR To add an SCCP originating address format translation

RMV SCCPADDR To remove an SCCP originating address format translation
MOD SCCPADDR To modify the an SCCP originating address format translation
LST SCCPADDR To list SCCP originating address format translations

HUAWEI MSOFTX3000
This configuration is optional. Before starting the command, read the following descriptions.
By default, when the MSOFTX3000 sends the signaling message such as MAP, CAP or INAP
to the HLR, MSC, SGSN or SCP, the originating address (the calling SCCP address) transferred
from the TCAP to SCCP software module is in the default format of SSN+GT.
In most cases, the TCAP software module of the peer-end equipment can respond to the local
office with right messages according to the originating address message SSN+GT. That is, the
SCCP software module of the peer-end equipment can receive the local SPC messages through
GT translation.
In the exceptional cases, only the originating address transferred from the TCAP software
module of the MSOFTX3000 to the SCCP software module contains the SPC message, the
equipment can respond to the local office with right messages.
To interconnect the MSOFTX3000 and the equipment, execute ADD SCCPADDR to add the
SCCP originating address format translation. So, when the MSOFTX3000 sends the signaling
message such as MAP, CAP or INAP to some special destination addresses (called GT), the
originating address transferred from the TCAP to SCCP software module is in the format of
SPC+SSN or SPC+SSN+GT.
The configurations by using ADD SCCPADDR is valid only when Select source address
format according to destination address in the command SET MAPACCFG is set to Yes.
Destination numbering scheme
It is a condition for translating the SCCP originating address format. Within the software of the
MSOFTX3000, when the destination numbering scheme of the called GT transferred from the
TCAP software module to the SCCP software module matches the value of parameter here, the
MSOFTX3000 can translate the SCCP originating address format. Select the default value,
1-ISDN/telephony numbering scheme.
Destination address nature indicator
MSOFTX3000, only when the destination address nature indicator of the called GT transferred
from the TCAP software module to the SCCP software module matches the value of parameter
here, the MSOFTX3000 can translate the SCCP originating address format. Select the default
value, 4-international number.
Destination address
MSOFTX3000, only when the destination address of the called GT transferred from the TCAP
software module to the SCCP software module matches the value of parameter here, the
MSOFTX3000 can translate the SCCP originating address format.
According to the principle of maximum matching, the system selects a destination address
among the specified destination addresses here to match the address message of GT. That is, the
system selects the destination address closest to the address message of GT.
Originating address format
It is the combination of the preceding mentioned conditions.

HUAWEI MSOFTX3000
When the MSOFTX3000 sends the signaling message such as MAP, CAP or INAP to some
special destination addresses (GT), within the software of the MSOFTX3000, this parameter
specifies an address format for the originating address information transferred from the TCAP
software module to the SCCP software module. Then, the SCCP message transparently
transfers the address information to the TCAP software module of the peer-end equipment.
The default value of the parameter is 0-SSN+GT. You can select 1-SPC+SSN or
2-SPC+SSN+GT according to the real situation.
When the SCCP software module is in the format of SPC+SSN+GT, the MSOFTX3000 cannot
translate GT of the SCCP originating address, even GT of the SCCP originating address
matches the combination of the conditions of GT translation defined by ADD SCCPGT.
6.9.5 Adding SCCP Subsystem Number

Related Commands
Command Function
ADD SCCPSSN To add an SCCP subsystem number

RMV SCCPSSN To remove an SCCP subsystem number
MOD SCCPSSN To modify an SCCP subsystem number
LST SCCPSSN To list SCCP subsystem numbers
SSN index
The SSN index uniquely identifies an SCCP subsystem number in the configuration database of
the MSOFTX3000. Its value range is 0–65534.
Network indicator
The network indicator specifies the signaling network to where the OPC and DPC parameters
belong. It may be the following network.
z International active network
z International standby network
z National active network
z National standby network
SCCP sub-system number
It is one of the interworking parameters between the MSOFTX3000 and the peer-end
equipment. It defines an SCCP subsystem number in the configuration database of the
MSOFTX3000. That is, it defines the corresponding SSN code in the SCCP message for a
subsystem subscriber. For example, the SSN code of the MAP, HLR and MSC is 0x05, 0x06
and 0x08 respectively.
SPC
It defines the DPC of the corresponding subsystem (the local receiver of SCCP messages). For
each subsystem, you should define two DSPs:

HUAWEI MSOFTX3000
z Far-end SCCP SPC: This parameter should be defined by ADD SCCPDSP before it can
be used here.
z Local SCCP SPC: This parameter should be defined by SET OFI/ADD OFI before it can
be used here.
OPC
It defines the OPC of the corresponding subsystem (the local transmitter of SCCP messages).
For each subsystem, this originating signaling point code is the local signaling point code. It is
defined by SET OFI/ADD OFI before it can be used here.
According to the preceding description, the SCCP subsystem data should be configured for the
local SCCP signaling point and far-end SCCP signaling point. That is, two pieces of the SCCP
subsystem data should be configured as follows:
z The OPC and SPC of one piece of the SCCP subsystem data should be configured as the
local signaling point code.
z The OPC of the other piece of the SCCP subsystem data should be configured as the local
signaling point code, and the SPC as the signaling point code of the peer-end equipment.
If the local signaling point code is 001130 and the signaling point code of the HLR is 001260, to
interconnect the MSOFTX3000 and the HLR, you should configure the MSC and HLR
subsystem in the MSOFTX3000 and configure six pieces of SCCP subsystem data as follows:
Script ADD SCCPSSN: SSNX=0, NI=NAT, SSN=MSC, SPC="001130",

OPC="001130";
ADD SCCPSSN: SSNX=1, NI=NAT, SSN=MSC, SPC="001260",
OPC="001130";
ADD SCCPSSN: SSNX=2, NI=NAT, SSN=HLR, SPC="001130",
OPC="001130";
ADD SCCPSSN: SSNX=3, NI=NAT, SSN=HLR, SPC="001260",
OPC="001130";
ADD SCCPSSN: SSNX=4, NI=NAT, SSN=MAP, SPC="001130",
OPC="001130";
ADD SCCPSSN: SSNX=5, NI=NAT, SSN=MAP, SPC="001260",
OPC="001130";
Local concerned SSN1 to Local concerned SSN5

When the status of the subsystem configured by the command changes, this parameter indicates
which related subsystems the MSOFTX3000 should notify of the subsystem status information.
This parameter is used only to test some management processes of the SCCP. So it is
recommended not to configure it.
Backup SSN index
When the MSOFTX3000 supports the active/standby function of the SCCP subsystem, this
parameter is available to specify the standby SCCP subsystem. This parameter should be
defined by ADD SCCPSSN before it can be used here.
When the signaling routing between the MSOFTX3000 and signaling equipment such as HLR
addresses with the DPC of the MTP route tag and the SSN of called subscriber address, the
route indicator bit is 1. In this case, the assistance function of the SCCP subsystem can be used
to improve the reliability of the SCCP signaling routing.

HUAWEI MSOFTX3000
This parameter is invoked in the SCCP subsystem data table. So it is recommended to define all
the SCCP DSPs with SCCPSSN, and then modify it with MOD SCCPSSN. If some equipment
do not support or do not provide the standby subsystem function, set this parameter to 65535
(indicating the disability of the function).
SSN name
It is a character string identifying an SCCP subsystem number.
6.9.6 Adding SCCP New GT (Optional)

Related Commands
Command Function
ADD SCCPNGT To add an SCCP new GT

RMV SCCPNGT To remove an SCCP new GT
MOD SCCPNGT To modify an SCCP new GT
LST SCCPNGT To list SCCP new GTs
This configuration is optional. Before starting the command, read the following descriptions.
When you configure the GT data by using the ADD SCCPGT command, if the type of the
translation result is SPC + NEW GT, the new GT must have been defined by the ADD
SCCPNGT command.
New GT index
The new GT index uniquely identifies a new GT in the configuration database of the
MSOFTX3000. Its value range is 0–65534.
Handle mode
It specifies the mode in which the MSOFTX3000 handles the original GT. The options are as
follows:
z Replace
All GT fields (including translation type, numbering plan, coding scheme, nature of address
indicator and address information) can be changed. However, for the address information, the
changed result can only be a fixed address signal.
z Change
All GT fields (including translation type, numbering plan, coding scheme, nature of address
indicator and address information) can be changed. For the address information, you can insert,
modify and delete numbers as required, and thus the changed result is variable.
GT indicator

HUAWEI MSOFTX3000
When Handle mode is set to Replace, the GT indicator specifies the type of a new GT. Its
default value is ITU Type 4. The parameter options are as follows:
z ITU Type 1
The GT includes address nature indicator and address information.
z ITU Type 2
The GT includes translation type and address information.
z ITU Type 3
The GT includes translation type, numbering scheme, coding scheme and address information.
z ITU Type 4
The GT includes translation type, numbering scheme, coding scheme, address nature indicator
and address information.
z ANSI Type 1
The GT includes translation type, numbering scheme, and address information.
z ANSI Type 2
The GT includes translation type and address information.
Translation type
When Handle mode is set to Replace, it defines the translation function used for a new GT, that
is, how to translate the address information of the SCCP message into the new and different
combination of SPC, SSN and GT. Its value type is hexadecimal number, and the default value
is 00 indicating no translation type is used. At present, it is not put into use and thus set it to 00.
Numbering scheme
When Handle mode is set to Replace, it specifies the numbering scheme used for a new GT. In
general, set it to ISDN/telephony numbering plan, the default value.
Address nature indicator
When Handle mode is set to Replace, it specifies the address nature of a new GT. In general,
set it to International number, the default value.
GT address information
When Handle mode is set to Replace, it specifies the address information of a new GT. Its
value range is 0–9 and A–E. The maximum length is 20.
6.9.7 Adding SCCP Global Title

Related Commands
Command Function
ADD SCCPGT To add a GT

RMV SCCPGT To remove a GT
MOD SCCPGT To modify a GT

HUAWEI MSOFTX3000
Command Function
LST SCCPGT To list GTs
In the following two cases, the MSOFTX3000 requires GT translation. Use ADD SCCPGT to
configure GT translation strategy.
z Transmitting direction: Suppose the MSOFTX3000 sends MAP, CAP and INAP protocol
messages to an HLR, MSC, SGSN, SMC and SCP. From the perspective of the
MSOFTX3000 software, the calling and called address information is sent from MAP,
CAP and INAP software modules to SCCP software module through TCAP software
module. The address information type is SSN+GT (SPC excluded). So GT should be
translated to the corresponding OPC or DPC that conforms to SS7 and is accepted by
SCCP.
z Receiving direction: Suppose the MSOFTX3000 receives an SCCP message. If routing
indicator in address indicator is set to 0 (means routing based on GT), the MSOFTX3000
translates GT before proceeding based on GT translation result. If the DPC in the
translation result is local signaling point code, the MSOFTX3000 sends the message to the
internal TCAP software module for processing. Otherwise, it forwards the SCCP message
to the corresponding DPC.
GT index
It uniquely identifies a GT in the MSOFTX3000. The value range is from 0 to 80000.
GT name
It specifies the name of the GT. The field type is character string.
Network indicator
It is one of the parameters for interworking with peer end equipment. It identifies the signaling
network to which the SPC belongs after GT translation. The parameter options include:
international network, international reserved network, national network and national reserved
network.
GT indicator
It is a condition for GT translation. The MSOFTX3000 translate GT when the parameter
conforms to a specified value here. The default value is Type 4. The options are listed as
follows:
z Type 1: GT includes address nature address indicator and GT address information.
z Type 2: GT includes translation type and GT address information.
z Type 3: GT includes translation type, numbering scheme, coding scheme and GT
address information.
z Type 4: GT includes translation type, numbering scheme, coding scheme, address
nature address indicator and GT address information.
Translation type

HUAWEI MSOFTX3000
It is a condition for GT translation. The MSOFTX3000 translates GT when the parameter

conforms to a specified value here. The field type is hexadecimal numeral. The default value is
00 that means translation type is not to be used. The parameter is not available for use, therefore
set the default value.
Numbering scheme
conforms to a specified value here. Set the default value ISDN/mobile numbering scheme for
this parameter.
Address nature address indicator
conforms to a specified value here. Set the default value international number for this
parameter.
GT address information
conforms to a specified value here.
The matching principle for GT address information is maximum matching. In other words, the
system matches the input GT address information here with the most similar one by searching
all address information.
Translation result type
It specifies types of GT translation results. The default value is SPC + OLD GT. The parameter
options are listed as follows:
z SPC + OLD GT: It indicates that GT is translated to SPC and old GT and old SSN are
reserved in SCCP message. Besides, the routing indicator in address indicator is set to 0
and so routing is based on GT.
z SPC + SSN: It indicates that GT is translated to SPC and old GT is reserved in the SCCP
message. But the new SSN replaces the old SSN. Besides, the routing indicator in address
indicator is set to 1 and so routing is based on DPC indicated in MTP routing. Choose this
type when the address information from TCAP software module to SCCP software module
excludes SSN. In this way, SSN is added in the SCCP message.
z SPC + NEW GT: It indicates that GT is translated to SPC and old SSN is reserved in the
SCCP message. But the new GT replaces the old GT. Besides, the routing indicator in
address indicator is set to 0 and so routing is based on GT.
z SPC: It indicates that GT is translated to SPC and old GT and old SSN are reserved in the
SCCP message. Besides, the routing indicator in address indicator is set to 1 and so routing
is based on DPC indicated in MTP routing and SSN.
If the parameter is set to SPC + OLD GT or SPC + NEW GT, each signaling equipment that is
in the SCCP message routing(for example, an STP), should support GT routing function.
Otherwise, the destination signaling equipment cannot receive the SCCP message.
When the SCCP software module is in the format of SPC+SSN+GT, the MSOFTX3000 cannot
translate GT of the SCCP originating address, even GT of the SCCP originating address
matches the combination of the conditions of GT translation defined by ADD SCCPGT.
SCCP sub-system number
It defines an SSN in the translation result. The parameter is valid when translation result type
is SPC + SSN. The parameter must be defined by ADD SCCPSSN before it can be used here.

HUAWEI MSOFTX3000
SPC
It defines a DPC or OPC in the translation result. The configuration principle is as follows:
z When the GT in calling SCCP address needs to be translated, enter OPC. The parameter
must be defined by SET OFI or ADD OFI before it can be used here.
z When the GT in called SCCP address needs to be translated, enter DPC. The parameter
must be defined by ADD SCCPDSP before it can be used here.
New GT index
It defines a new GT in the translation result. The parameter is valid when translation result
type is SPC + NEW GT. The parameter must be defined by ADD SCCPNGT before it can be
used here.
6.9.8 Adding SCCP Shielding Policy (Optional)

Related Commands
Command Function
ADD SCCPPOL To add an SCCP shielding policy

RMV SCCPPOL To remove an SCCP shielding policy
MOD SCCPPOL To modify an SCCP shielding policy
LST SCCPPOL To list SCCP shielding policies
This configuration step is optional. Before you start to set the data, read the following notes.
When the MSOFTX3000 interconnects with equipment such as the HLR, VLR, MSC, SMC,
SCP and SGSN in mobile network, the traffic range of MAP or CAP incoming messages is
limited to a specified value to avoid congestion and over loading on the signaling links between
the MSOFTX3000 and these pieces of equipment. Carriers can resolve this safety problem by
using SCCP screen function.
Use ADD SCCPPOL to add an SCCP screen policy. After that, when receiving the incoming
MAP or CAP messages sent from other equipment, the local office can use the SCCP screen
function according to the SPC, SSN and GT data in the SCCP calling and called addresses. If
the number of SCCP signaling message packets received per unit time exceeds the limitation,
the local office will discard this message.
SCCP screen policy index
The SCCP screen policy index uniquely identifies an SCCP screen policy. The value range is
from 0 to 511.
The SCCP screen function is only available for the incoming and connectionless SCCP
signaling messages but unavailable for the outgoing or connection-oriented messages.
Network indicator

HUAWEI MSOFTX3000
It is a filter condition in the case that the MSOFTX3000 starts the SCCP screen function. That is,
only when the value of the Network indicator field in an SCCP signaling message corresponds
to that of this parameter, the MSOFTX3000 can start the SCCP screen function.
Screen policy
It defines the policy with which the MSOFTX3000 can start the SCCP screen function. In
addition, the MSOFTX3000 will screen the SCCP signaling messages according to it. The
system can provide 24 types of screen policy which are constituted by the following basic
policies:
z Calling address OPCSSN: indicates to start the SCCP screen function according to the
OPC + SSN information of the Calling address field in SCCP messages
z Called address DPCSSN: indicates to start the SCCP screen function according to the
DPC + SSN information of the Called address field in SCCP messages
z Calling address GTSSN: indicates to start the SCCP screen function according to the GT
+ SSN information of the Calling address field in SCCP messages
z Called address GTSSN: indicates to start the SCCP screen function according to the GT
+ SSN information of the Called address field in SCCP messages
z Calling address GTT: indicates to start the SCCP screen function according to the
routing indicator bit of the Calling address field in SCCP messages
z Called address GTT: indicates to start the SCCP screen function according to the routing
indicator bit of the Called address field in SCCP messages
Calling DPC
only when the value of the calling OPC in an SCCP signaling message corresponds to that of
this parameter, the MSOFTX3000 can start the SCCP screen function. The parameter is
available when Calling address OPCSSN is contained in the screen policy.
Calling SSN code
only when the value of the calling SSN code in an SCCP signaling message corresponds to that
of this parameter, the MSOFTX3000 can start the SCCP screen function. The parameter is
available when Calling address OPCSSN is contained in the screen policy.
Calling GT translation result type
when routing indicator bit of Address indicator field is set to 0 in an SCCP signaling message,
the MSOFTX3000 need to translate the calling and called GT code (the translation policy is
defined by ADD SCCPGT) and only when the value of the calling GT translation result
corresponds to that of this parameter, the MSOFTX3000 can start the SCCP screen function.
The parameter is available when Calling address GTT is contained in the screen policy.
Calling GT type
only when the value of the calling GT type in an SCCP signaling message corresponds to that of
available when Calling address GTSSN is contained in the screen policy. Its default value is
Type 4. The parameter options are as follows:
z Type 1
The GT includes Address nature indicator and Address information.

HUAWEI MSOFTX3000
z Type 2
The GT includes Translation type and Address information.
z Type 3
The GT includes Translation type, Numbering scheme, Coding scheme and Address
information.
z Type 4
The GT includes Translation type, Numbering scheme, Coding scheme, Address nature
indicator and Address information.
Calling translation type
only when the value of the calling GT translation type in an SCCP signaling message
The parameter is available when Calling address GTSSN is contained in the screen policy.
The value is hexadecimal and its default value is 0 (translation type is unavailable). At present,
the parameter is not put into use and you can use 0 by default.
Calling numbering scheme
only when the value of the calling GT numbering scheme in an SCCP signaling message
You can use ISDN/Telephone numbering scheme by default.
Calling address nature indicator
only when the value of the calling GT address nature indicator in an SCCP signaling message
You can use International number by default.
Calling GT address information
only when the value of the calling GT address information in an SCCP signaling message
matches with that of this parameter, the MSOFTX3000 can start the SCCP screen function. The
parameter is available when Calling address GTSSN is contained in the screen policy.
The system compares the address information of calling GT with the specified address
information following the maximum match principle. That is, for an actual GT, the system finds
the most close address information of this parameter to match with the actual GT.
Called DPC
only when the value of the called DPC in an SCCP signaling message corresponds to that of this
parameter, the MSOFTX3000 can start the SCCP screen function. The parameter is available
when Called address OPCSSN is contained in the screen policy.
Called SSN code
only when the value of the called DPC SSN code in an SCCP signaling message corresponds to

HUAWEI MSOFTX3000
that of this parameter, the MSOFTX3000 can start the SCCP screen function. The parameter is
available when Called address OPCSSN is contained in the screen policy.
Called GT translation result type
when routing indicator bit of Address indicator field is set to 0 in an SCCP signaling message,
the MSOFTX3000 need to translate the calling and called GT code (the translation policy is
defined by ADD SCCPGT) and only when the value of the called GT translation result
The parameter is available when Calling address GTT is contained in the screen policy.
Called GT type
only when the value of the called GT type in an SCCP signaling message corresponds to that of
available when Calling address GTSSN is contained in the screen policy. Its default value is
Type 4. The parameter options are as follows:
z Type 1
The GT includes Address nature indicator and Address information.
z Type 2
The GT includes Translation type and Address information.
z Type 3
The GT includes Translation type, Numbering scheme, Coding scheme and Address
information.
z Type 4
The GT includes Translation type, Numbering scheme, Coding scheme, Address nature
indicator and Address information.
Called translation type
only when the value of the called GT translation type in an SCCP signaling message
The value is hexadecimal and its default value is 0 (translation type is unavailable). At present,
the parameter is not put into use and you can use 0 by default.
Called numbering scheme
only when the value of the called GT numbering scheme in an SCCP signaling message
You can use ISDN/Telephone numbering scheme by default.
Called address nature indicator
only when the value of the called GT address nature indicator in an SCCP signaling message

HUAWEI MSOFTX3000
You can use International number by default.
Called GT address information
only when the value of the called GT address information in an SCCP signaling message
matches with that of this parameter, the MSOFTX3000 can start the SCCP screen function. The
parameter is available when Calling address GTSSN is contained in the screen policy.
The system matches the address information of calling GT to the specified address information
of this parameter by using the rule of matching at most. That is, for an actual GT, the system
finds the most close address information of this parameter to match with the actual GT.
Traffic unit
Corresponding to the combined filter conditions for starting the SCCP screen function
mentioned above, it indicates the time unit in terms of which the MSOFTX3000 controls the
traffic of the SCCP signaling messages received by the local office. Its default value is per
hour.
Traffic threshold
Corresponding to the combined filter conditions for starting the SCCP screen function
mentioned above, it defines the maximal number of the SCCP signaling message packet
(namely, the MSU) transmitted per unit time. The value range is from 0 to 2,147,483,647 and its
default value is 0.
When Traffic unit is set to per hour and Traffic threshold to 1,000, the MSOFTX3000
controls the traffic of the SCCP signaling message in hour unit. Two cases are as follows:
z Within one hour, if the number of the SCCP signaling packets received by the local office
is less than 1,000, the MSOFTX3000 do not control the traffic.
z Within one hour, if the number of the SCCP signaling packet received by the local office
has reached 1,000, the MSOFTX3000 discards all SCCP signaling packets received in the
rest time of this hour. When the next time unit begins, the MSOFTX3000 resets the related
statistic counter.
Server index
It controls the types of the data record configured by this command, that is, the data of the local
server node or the data of a virtual sever node mutually aided by the local office. Its default
value is 0. The configuration principles are as follows:
z Input zero: indicates the data record is the data of the local server node. This data record is
available only when the local server node works in independent work mode or in mutual
assistance activated state.
z Input non-zero: indicates the data record is the data of a virtual server node mutually aided
by the local office. This data record is available only when the virtual server node works in
mutual assistance activated state. In addition, this parameter is defined by ADD
SRVNODE before it can be used here.
In the networking structure of 3GPP R4 (or the later) version, carriers adopt the 1+1 or the N+1
dual homing networking scheme in MSC server layer. In this case, if the local MSOFTX3000 is
applied as a mutual aid server node of another MSOFTX3000 in the networking, you need to
configure the dual homing data of the server node mutually aided by the local MSOFTX3000.

Huawei - Configuring Signaling Transport Data

Uploaded by

Copyright:

Available Formats

You might also like

Huawei - Configuring Signaling Transport Data

Uploaded by

Document Information

Original Description:

Original Title

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

Huawei - Configuring Signaling Transport Data

Uploaded by

Copyright:

Available Formats

HUAWEI MSOFTX3000

Configuration Guide Contents

6 Configuring Signaling Transport Data..................................................................................6-1

Issue 09 (2007-05-20) Huawei Technologies Proprietary i

6.6.3 Adding MTP Destination Signaling Point..........................................................................................6-46

ii Huawei Technologies Proprietary Issue 09 (2007-05-20)

Figure 6-1 Bit structure of TOS..........................................................................................................................6-6

Figure 6-8 IUA application model....................................................................................................................6-30

Figure 6-11 Parameter referencing relationship ...............................................................................................6-45

Figure 6-14 Introduction to links of the ATM signaling...................................................................................6-56

Issue 09 (2007-05-20) Huawei Technologies Proprietary iii

Table 6-1 Input parameters required in M2UA signaling data............................................................................6-9

Table 6-8 Configuration steps...........................................................................................................................6-18

Table 6-11 Preparations ....................................................................................................................................6-31

Table 6-14 Output parameters defined in DSS1 signaling data ........................................................................6-38

Table 6-20 Configuration steps.........................................................................................................................6-45

Table 6-23 Preparations ....................................................................................................................................6-57

Table 6-26 Configuration steps.........................................................................................................................6-58

iv Huawei Technologies Proprietary Issue 09 (2007-05-20)

Table 6-27 Input parameters referencing relationship ......................................................................................6-70

Table 6-28 Output parameter referencing relationship .....................................................................................6-70

Issue 09 (2007-05-20) Huawei Technologies Proprietary v

6 Configuring Signaling Transport Data

About This Chapter

The following table lists the contents of this chapter.

Issue 09 (2007-05-20) Huawei Technologies Proprietary 6-1

6.1 Configuring SCTP Data

6-2 Huawei Technologies Proprietary Issue 09 (2007-05-20)

6.1.2 Setting SCTP Parameters

SET SCTPPARA To set an SCTP parameter

Issue 09 (2007-05-20) Huawei Technologies Proprietary 6-3

6-4 Huawei Technologies Proprietary Issue 09 (2007-05-20)

Issue 09 (2007-05-20) Huawei Technologies Proprietary 6-5

Figure 6-1 Bit structure of TOS

6.2 Configuring M2UA Signaling Data

6-6 Huawei Technologies Proprietary Issue 09 (2007-05-20)

Figure 6-2 SIGTRAN protocol model

M3UA M2UA M2PA IUA V5UA SUA

M3UA: MTP3-user adaptation layer M2UA: MTP2-user adaptation layer

Four Parameters for Identifying an SCTP Association

Issue 09 (2007-05-20) Huawei Technologies Proprietary 6-7

Client/Server Working Mode for SCTP Associations

M2UA Application Model

Figure 6-3 M2UA application model

MTP link M2UA link

6-8 Huawei Technologies Proprietary Issue 09 (2007-05-20)

6.2.2 Configuration Overview

Table 6-1 Input parameters required in M2UA signaling data

Module number of the ADD BRD Hardware Data ADD M2LNK

Table 6-2 Output parameters defined in M2UA signaling data

Table 6-3 Preparations

1 IP address of the embedded SG A parameter for interconnecting the

Issue 09 (2007-05-20) Huawei Technologies Proprietary 6-9

2 Local SCTP port number of each A parameter for interconnecting the

Table 6-4 Configuration steps

1 Add an embedded SG. ADD ESG

Relationship Between Data Tables in Database