Technical Support Note

TS-BSC-SW-0807-I14.0

Interface Parameters (MTP/SCCP)

SR20, SR40, S16_2, BSC16, BSC17, SRAN16.2,

SRAN16.10

Approval date: (08-Nov-2004)

This document contains following

type of information
Informative X
Preventive
Corrective
Additional categorization
Urgent
Security
Release Upgrade
SW Update
Parameterization
Information is classified as
Internal
Public X
Customer Specific

TS-BSC-SW-0807-I14.0 - Page 1/11 © Nokia Solutions and Networks 2016

Version 14.0
Confidential
Table of Contents
1. Validity .....................................................................................................................................3
2. Compatibility / Dependencies to other products ......................................................................3
3. Keywords.................................................................................................................................3
4. Executive Summary ................................................................................................................3
5. Detailed description .................................................................................................................3
5.1 .....Signalling Parameter Sets .................................................................................................4
5.2 .....Signalling Transfer Point ...................................................................................................5
5.3 .....Traffic Restarting Time ......................................................................................................5
5.4 .....Inactivity Control Timers ....................................................................................................5
5.5 .....Multivendor Environment...................................................................................................5
5.6 .....False Link congestion procedure (ANSI)...........................................................................5
6. Solution / INSTRUCTIONS .....................................................................................................6
7. note .........................................................................................Error! Bookmark not defined.
8. References ............................................................................................................................10

Contact:

Contact your local Nokia Solutions and Networks support

Summary of changes:

08-Nov-2004 0.1 First version

08-Nov-2004 1.0 Approval date
08-07-2005 1.1 Checked the validity for S11.5 SW Release
Modified the sentence for the parameter change.
Added the definitions for Restriction Status.
02-06-2006 1.2 Added ANSI and support of indirect routes,
clarified statements about recommended
parameter set and parameter values.
05-09-2008 2.0 S12 & S13 validation check
23-06-2009 3.0 Update to S14 level
12-10-2010 4.0 Validation to S15 level
19-12-2011 5.0 SR10 and S15mcBSC validation
21-11-2012 6.0 SR20 and S16 validation
21-05-2013 7.0 SR10 removed and add S16.1
12-Sep-2014 8.0 S16_2 validation
31-Dec-2014 9.0 Some clarification to description section, validity
table corrected, references updated
13-Jan-2015 10.0 ZOCI parameter set name corrected
26-May-2015 11.0 Sigtran/M3UA information added
14-Sept-2015 12.0 Chapter 5 Modified
10-Nov-2015 13.0 SRAN16.2 Validation, Removing S16 & S16.1
12-Oct-2016 14.0 SRAN16.10 & BSC17 validation

TS-BSC-SW-0807-I14.0 - Page 2/11 © Nokia Solutions and Networks 2016

Version 14.0
Confidential
Purpose
This document contains generic information about products. These can be instructions that
explain problem situations in the field, instructions on how to prevent or how to recover from
problem situations, announcements about changes or preliminary information as requirements
for new features or releases.

1. VALIDITY

Product SR20 S16_2 SR40 BSC16 SRAN16.2/ BSC17

SRAN16.10
BSC3i X X X
Flexi BSC X X X X X
TCSM2A/E
TCSM3i
mcBSC X X X
mcTC
Single X
RAN

2. COMPATIBILITY / DEPENDENCIES TO OTHER PRODUCTS

None.

3. KEYWORDS

A-Interface, SS7, Sigtran, M3UA, MTP, SCCP, parameter set, MGW, MSC, MSS

4. EXECUTIVE SUMMARY

This Technical Note provides information on how to set up A-interface parameters.

5. DETAILED DESCRIPTION

This technical note gives instructions how to setup A-interface parameters so that it can more
easily adapt to changes in the MSC signalling software.

All the other parameter values than Q704_T20_TRAF_RESTARTING_TIME should be

adjusted in both ends (BSC and MSC) to ensure the optimum functionality. It should be
always verified that the MSC is congruent with the parameter set and values of the BSC to
prevent any possible issues related to A-interface recovery.

In some cases the A-interface parameter default values might differ between network
elements, it is important to use same document in both ends while defining optimal parameter
values.

TS-BSC-SW-0807-I14.0 - Page 3/11 © Nokia Solutions and Networks 2016

Version 14.0
Confidential
 MTP is used in TDM based signaling networks and not supported by box controller node
(BCN) mechanics. M3UA based on IP traffic.

The Message Transfer Part can be divided into three levels:

 Signaling Data Link level (level 1) defines the physical, electrical, and functional
characteristics.
 Signaling Link level (level 2) defines the functions considering message transfer
between two adjacent network elements through a signaling link.
 Signaling Network level (level 3) can be divided into two parts: message handling and
network management.

M3UA is a protocol for supporting the transport of any SS7 MTP3-User signaling over IP. The
Signaling Connection Control Part provides two different services, the connection-oriented and
the connectionless services for other applications.

A TC user can access the network services of the signaling system through the TC.
The TC protocol is implemented in the Nokia network element through two different processes:
 ETSI, ITU-T Q.771 - Q.775 Recommendations
 ANSI T1.114 Recommendation.

5.1 SS7 Signalling Network Parameter Sets

With the signaling parameters it is possible to control and modify certain functions of the
signaling network. The signaling parameters are divided into six different levels, depending on
which part of the signaling system they affect.

There are few parameter sets predefined for a different kind of SS7 signaling standards (for
example, ITU-T, ANSI, JAPAN). It is recommended to use these parameter sets or at least to
start with them. If there is a need to change them, it is reasonable to create a new one on the
basis of the predefined one.

Parameter Set to be used:

No signaling transfer point (STP), 1 - A-Interface
Signalling transfer point , 0 - ITU-T
Sigtran (M3UA) links used 6 - IETF M3UA

TS-BSC-SW-0807-I14.0 - Page 4/11 © Nokia Solutions and Networks 2016

Version 14.0
Confidential
 ANSI: 3 - ANSI T111

5.2 Signalling Transfer Point

If the signalling network includes signalling transfer point (Example MGW), parameter set 0
ITU-T should be used and restriction status set to “no restrictions”. The ITU-T parameter set
supports indirect routes on A-interface.

5.3 Traffic Restarting Time

The parameter Q704_T20_TRAF_RESTARTING_TIME (199) prevents the transmission

brakes under 2s reported to MTP3 level.

In the MSC the parameter Q704_T20_TRAF_RESTARTING_TIME should not be changed to

199 as there are other interfaces using MTP-restart procedure.

5.4 Inactivity Control Timers

Two inactivity control timers, the receive inactivity control timer T(iar) and the send inactivity
control timer T(ias), are required at each end of a connection section. The length of the receive
inactivity timer must be longer than the length of the longest inactivity timer in the surrounding
nodes.

Q714_T_IAR (receive inactivity control timer) value should be at least 2 times the value of
Q714_T_IAS (send inactivity control timer).

5.5 Multivendor Environment

GSM/GPRS/UMTS/LTE system consists of several network elements. Open standardized

interfaces enable multivendor configurations. Multivendor configurations occur in all networks
as many networks have infrastructure from more than one vendor.

The parameter modifications required to optimize multivendor configuration are not covered in
this technical note.
Contact to local CSI team to get further information about MultiVendor Interface Verification
(MVIV) Service.

5.6 False Link congestion procedure (ANSI)

In the ANSI environment “False Link Congestion” procedure is used handle congestion
situation on MTP level. ANSI specifies three congestion levels. MTP-L3 differentiates between
congested and failed links.

The recommended parameters:

D9 FALSE_CONG_DENIED NO
F15 T111_T31 120 1 S
E2 CONG_ONSET_THRESHOLD1 49
E3 CONG_ABATE_THRESHOLD1 40
E5 CONG_ONSET_THRESHOLD2 69
E6 CONG_ABATE_THRESHOLD2 60
E8 CONG_ONSET_THRESHOLD3 89
E9 CONG_ABATE_THRESHOLD3 80

TS-BSC-SW-0807-I14.0 - Page 5/11 © Nokia Solutions and Networks 2016

Version 14.0
Confidential
6. SOLUTION / INSTRUCTIONS

MTP:

Signalling Transfer Point (STP) not used:

Check that parameter set 1 (A-interface) and Restriction Status is A-Interface are used.

ZNRI:NA0;

LOADING PROGRAM VERSION 8.7-0

DX 200 OLOS 2004-10-11 09:37:51

INTERROGATING SIGNALLING POINT DATA

NET SP CODE H/D NAME RS STATE PAR SET

--- ------------------ ----- -------- -------
NA0 0200/00512 MSCBS AV 1 A INTERFACE
LOAD SHARING BETWEEN SIGNALLING ROUTES DENIED

ROUTES: SP CODE H/D NAME STATE PRIO

------------------ ----- ------ ----
0200/00512 MSCBS AV-EX 0

SS7 SUBFIELD INFO

NET SP CODE H/D SP NAME SP TYPE STAND COUNT BIT LENGTHS
--- ------------------ ------- ------- ----- ----- -----------
NA0 1571/05489 OLOS SEP ITU-T 1 14 OWN SP

COMMAND EXECUTED

Signalling Transfer Point (STP) used:

Check that parameter set 1 (A-interface) and Restriction Status is A-Interface are used.

ZNRI:NA0;

LOADING PROGRAM VERSION 8.7-0

DX 200 OLOS 2004-10-11 09:37:51

INTERROGATING SIGNALLING POINT DATA

NET SP CODE H/D NAME RS STATE PAR SET

--- ------------------ ----- -------- -------
NA0 0200/00512 MSCBS AV 0
LOAD SHARING BETWEEN SIGNALLING ROUTES DENIED

ROUTES: SP CODE H/D NAME STATE PRIO

------------------ ----- ------ ----
0200/00512 MSCBS AV-EX 0

TS-BSC-SW-0807-I14.0 - Page 6/11 © Nokia Solutions and Networks 2016

Version 14.0
Confidential
 SS7 SUBFIELD INFO
NET SP CODE H/D SP NAME SP TYPE STAND COUNT BIT LENGTHS
--- ------------------ ------- ------- ----- ----- -----------
NA0 1571/05489 OLOS SEP ITU-T 1 14 OWN SP

COMMAND EXECUTED

Change the parameter set to parameter set 1 (A-interface) if needed.

ZNRB:NA0,<sp>:PARA=1;

Change the Restriction Status to A-Interface if needed. This parameter is actually some type
information for the signalling point. The type is given in order to allow checking that MML
commands given concerning the signalling point are reasonable.

ZNRB:NA0,<sp>:REST=R;

The status R defines the signalling point to be used according to the MTP specification for the
A-interface. It defines that only associative signalling mode is allowed to the signalling point.

Signalling Transfer Point (STP) in use:

Change the parameter set to parameter set 0 (ITU-T) if needed.

ZNRB:NA0,<sp>:PARA=0;

Change the restriction status to “no restrictions” if needed:

ZNRB:NA0,<sp>:REST=N;

Common parameter changes :

Check the timer values with command:

ZNMI:C;

LOADING PROGRAM VERSION 8.10-0

DX 200 OLOS 2004-10-11 09:38:40

INTERROGATING CCS7 LEVEL 3 PARAMETERS

GROUP C: TIMER PARAMETERS FOR OWN SIGNALLING POINT

==================================================
INDEX NAME VALUE UNIT
----- ---- ----- ----
C0 LINK_TEST_PERIOD 4000 0.01 S
C1 Q704_T18_LINK_AVAIL_WAIT 2000 0.01 S

TS-BSC-SW-0807-I14.0 - Page 7/11 © Nokia Solutions and Networks 2016

Version 14.0
Confidential
 C2 Q704_T19_TRA_WAIT 400 0.01 S
C3 Q704_T20_TRAF_RESTARTING_TIME 199 0.01 S
C4 T111_T26 1500 0.01 S
C5 Q714_T_GUARD 6000 0.1 S
C6 T111_T27 300 0.01 S

COMMAND EXECUTED

The parameter Q704_T20_TRAF_RESTARTING_TIME (199) prevents the transmission

brakes under 2s reported to MTP3 level.

In the MSC the parameter Q704_T20_TRAF_RESTARTING_TIME should not be changed

to 199 as there are other interfaces using MTP-restart procedure.

The parameter T111_T27 (300) extends the transmission brake over 128ms to 3s on MTP2
level.

If needed change the values with commands:

ZNMM:C:C3=199;
ZNMM:C:C6=300;

Check the parameters TRM_DENIED and TRM_EXPECTED with command:

ZNNI:1,C;

LOADING PROGRAM VERSION 8.7-0

DX 200 OLOS 2004-10-11 09:39:00

INTERROGATING SIGNALLING ROUTE SET PARAMETER SETS

PARAMETER SET: 00001 A INTERFACE

==================================

GROUP C: ADJACENT SIGNALLING POINT PARAMETERS

=============================================
INDEX NAME VALUE
----- ---- -----
C0 TRM_DENIED YES
C1 TRM_EXPECTED NO
C2 SP_RESTART_TYPE NONE
C3 INDIRECT_ROUTES_DEFAULT AVAILABLE
C4 TFM_CONTROL ALL DENIED
C5 RESP_TFM_CONTROL TFM DENIED
C6 TFR_DENIED YES

COMMAND EXECUTED

The parameter values should be as in example above. Change the values if needed.

ZNNM:1,A INTERFACE,C:C0=Y:;
ZNNM:1,A INTERFACE,C:C1=N:;

TS-BSC-SW-0807-I14.0 - Page 8/11 © Nokia Solutions and Networks 2016

Version 14.0
Confidential
 SCCP:

Check that parameter set 1 (A-interface) is used on the A-interface.

ZNFI:NA0,:A;

LOADING PROGRAM VERSION 8.3-0

DX 200 OLOS 2004-10-11 09:39:19

SCCP STATES

DESTINATION: SP ROUTING: SP PAR

NET SP CODE H/D NAME ST RM NET SP CODE H/D NAME STATE SET
--- ------------------ ----- -- -- --- ------------------ ----- ------- ---
NA0 0200/00512 MSCBS AV - NA0 0200/00512 MSCBS AV-EX 1

PAR
SUBSYSTEMS: NO H/D SS NAME STATE SET SST
=========== ------- ------- ------- --- ---
01/001 SCMG AV-EX N
FE/254 BSSAP AV-EX 1 Y

DESTINATION: SP ROUTING: SP PAR

NET SP CODE H/D NAME ST RM NET SP CODE H/D NAME STATE SET
--- ------------------ ----- -- -- --- ------------------ ----- ------- ---
NA0 1571/05489 OLOS OWN SP 1

PAR
SUBSYSTEMS: NO H/D SS NAME STATE SET SST
=========== ------- ------- ------- --- ---
01/001 SCMG AV-EX N
FE/254 BSSAP AV-EX 1 Y

COMMAND EXECUTED
If parameter set 1 (A-interface) is not used change the used parameter set to 1 (A-interface).
Note that traffic is disturbed during this step!

ZNHC:NA0,<sp_msc>:FE:INA; Change subsystem state

ZNHC:NA0,<sp_bsc>:FE:INA; Change subsystem state
ZNGC:NA0,<sp_msc>:INA; Change SCCP state
ZNFL:NA0,:1; Modify used parameter set SCCP
ZNFM:NA0,:FE:1:; Modify used parameter set for
subsystems
ZNHC:NA0,<sp_bsc>:FE:ACT; Change subsystem state
ZNGC:NA0,<sp_msc>:ACT; Change SCCP state
ZNHC:NA0,<sp_msc>:FE:ACT; Change subsystem state

Change the value of the timer SSP_FILTER_TIMER from 10 to 110 ( 11s ) with command:

ZOCM:1:25,110;

Change the value of the timer Q714_T_STAT_1ST from 600 to 50 ( 5s ) with command:

ZOCM:1:8,50;

Verify the SCCP parameter values after these changes with command:

ZOCI:1;

TS-BSC-SW-0807-I14.0 - Page 9/11 © Nokia Solutions and Networks 2016

Version 14.0
Confidential
 DX 200 OLOS 2004-10-11 09:40:01

INTERROGATING SCCP SIGNALLING POINT PARAMETER SETS

SET NUMBER: 00001 SET NAME: A-INT

========================================================================
NO: NAME VALUE UNIT
--- ---- --------------------------- ------
1 Q714_T_CONN_EST 90 1 S
2 Q714_T_IAS 90 1 S
3 Q714_T_IAR 270 1 S
4 Q714_T_REL 150 0.1 S
5 Q714_T_INT 60 1 S
6 Q714_T_RES 15 1 S
7 Q714_T_REP_REL 100 0.1 S
8 Q714_T_STAT_1ST 50 0.1 S
9 Q714_T_STAT_INC 300 0.1 S
10 Q714_T_STAT_MAX 9000 0.1 S
11 A_INTERFACE YES -
12 WHITE_BOOK_MGMT_USED NO -
13 SS_MANAGEMENT_USED YES -
14 XUDT_USED NO -
15 UDT_DENIED NO -
16 SEG_X_THRES 272 OCTETS
17 SEG_Y_THRES 272 OCTETS
18 TCAP_LOAD_SHARING_USED NO -
19 ADD_DPC_IF_RI_SSN NO -
20 ADD_GT_IF_RI_SSN NO -
21 ADD_DPC_IF_RI_GT NO -
22 ANALYSE_ROOT_OF_CALLING_GT NO -
23 ALLOWED_GTI_VALUES 1-4,5,6,7,8,9,10,11, -
12,13,14,15 -
24 SSA_FILTER_TIMER 10 0.1 S
25 SSP_FILTER_TIMER 110 0.1 S
26 LUDT_USED NO -
27 CO_SEGM_USED NO -

COMMAND EXECUTED

7. NOTE

This TSN replaces the TS-BSC-0847, TS-BSC-0869 and TS-BSC-0892.

8. REFERENCES

GSM/EDGE BSS, Operating Documentation, Administer, BSC/TCSM, Common Channel

Signalling (MTP, SCCP and TC)

TS-BSC-0821, MTP, False Link congestion procedure (ANSI)

BSC: Integrate and Configure, BSS integration: Creating the A-interface

MSC: MSS integration, Configuring BSS/RAN network for MSS

MGW: Integrate and Configure, Integrating MGW into the MSC Server System
Creating Ater interface (MGW – BSC)
Creating local signaling configuration for MGW

TS-BSC-SW-0807-I14.0 - Page 10/11 © Nokia Solutions and Networks 2016

Version 14.0
Confidential
 Disclaimer
The information in this document applies solely to the hardware/software product (“Product”) specified
herein, and only as specified herein.
This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may
not be used except for the purposes defined in the agreement between You and Nokia Solutions and
Networks (“Agreement”) under which this document is distributed. No part of this document may be used,
copied, reproduced, modified or transmitted in any form or means without the prior written permission of
Nokia Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if
that Agreement has expired or has been terminated, You may not use this document in any manner and
You are obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You
assume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part of
the process of continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements
concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on
an “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the right
to change any such information and statements without notice. Nokia Solutions and Networks has made all
reasonable efforts to ensure that the content of this document is adequate and free of material errors and
omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But,
Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction
of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product
will be uninterrupted or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE
LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,
INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF
PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY
ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF
ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not be
distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and
Networks.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
may be trademarks of their respective owners, and they are mentioned for identification purposes only.
Copyright © 2016 Nokia Solutions and Networks. All rights reserved.

TS-BSC-SW-0807-I14.0 - Page 11/11 © Nokia Solutions and Networks 2016

Version 14.0
Confidential