Configuring Signalling Connections in ATM Network

Configuring SignallingConnections in ATM Network(RNC)

DN02143262Issue 16-1 en30/01/2009

# Nokia Siemens Networks 1 (229)

Nokia Siemens Networks WCDMA RAN, Rel.RU10, System Library, v. 1

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2009. All rights reserved.

2 (229) # Nokia Siemens Networks DN02143262Issue 16-1 en

30/01/2009

Configuring Signalling Connections in ATM Network (RNC)

Contents

Contents 3

Summary of changes 7

1 Signalling in 3G 9

2 SS7 signalling 13

3 SS7 transport medium in RNC 17

4 SS7 network concepts 19

5 SS7 configurations in RNC 21

6 SAAL UNI signalling 29

7 AAL type 2 signalling protocol 35

8 Signalling states 378.1 States of signalling route sets 378.2 States of signalling routes 378.3 States of signalling link sets 398.4 States of signalling links 398.5 States of SCCP signalling points 438.6 States of SCCP subsystems 44

9 Error messages in MTP commands 479.1 MTP command major errors 479.2 MTP command minor errors 48

10 SS7 signalling network parameters 6510.1 SS7 signalling network parameters 6510.2 MTP level 3 parameters 6810.3 SS7 signalling network specific parameters 7310.4 Signalling link parameters 7710.5 Signalling route set parameters 8910.6 SCCP signalling point parameters 9810.7 SCCP subsystem parameters 102

11 Planning SS7 network 10711.1 SS7 network planning principles 10711.2 SS7 network structures 10811.3 MTP level signalling network 11311.4 SCCP level signalling network 123

12 Creating SAAL UNI signalling links 135

13 Creating local signalling configuration for RNC 137

DN02143262Issue 16-1 en30/01/2009


Contents

14 Creating remote MTP configuration 141

15 Activating MTP configuration 147

16 Setting MTP level signalling traffic load sharing 151

17 Creating remote SCCP configuration 15317.1 Creating remote SCCP configuration 15317.2 Activating SCCP configuration 156

18 Optimizing MTP configuration 15918.1 Modifying MTP level 3 signalling parameters 15918.2 Modifying SS7 signalling network parameters 16018.3 Modifying the values of signalling link parameter set 16018.4 Creating new signalling link parameter set 16118.5 Modifying the values of signalling route set parameter set 16318.6 Creating new signalling route set parameter set 16418.7 Setting/modifying MTP level signalling traffic restrictions 16518.8 Modifying MTP level signalling traffic load sharing 16718.9 Using the signalling link set of another signalling network 16818.10 Removing an MTP signalling point 170

19 Optimizing SCCP configuration 17319.1 Modifying SCCP signalling point parameter set 17319.2 Creating new SCCP signalling point parameter set 17419.3 Defining SCCP signalling point and/or subsystem to own signalling point

17619.4 Removing SCCP signalling point and/or subsystem from own signalling

point 17719.5 Modifying the values of SCCP subsystem parameter set 17819.6 Creating new SCCP subsystem parameter set 17919.7 Setting/modifying broadcasts of local SCCP subsystem 18119.8 Setting/modifying signalling point based traffic restrictions 18219.9 Calling GT checking based traffic restrictions 18319.10 Setting/modifying GT based traffic restrictions 18719.11 Creating/modifying GT translation result and GT modification 19319.12 Creating global title analysis for called GT 19419.13 Creating calling GT routing configuration 195

20 Deleting SAAL UNI signalling links 199

21 Monitoring SS7 signalling network objects 201

22 Optimising AAL type 2 signalling 205

23 Signalling troubleshooting 20723.1 MTP and SCCP configuration-related problems 20723.1.1 Signalling route goes to or stays in state UA-INR 20723.1.2 The system sets frequently alarm 0026 SIGNALLING LINK LOAD OVER

THRESHOLD 20823.1.3 Signalling link activation succeeds but traffic fails 20823.1.4 All MTP and SCCP level objects are in state available (AV) but location


30/01/2009


update fails 21023.1.5 Mobile calls are cut frequently after 4.5 min 21123.1.6 AAL2 connection release delay too short for short-term Iu/Iur (NNI) link

failures 21123.1.7 Global title translation fails although translation exists 21223.1.8 Errors in the global translation result 21323.1.9 The state of all subsystems in the remote network element is unavailable

(UA) although MTP route set is in state available-executing (AV-EX) 216

23.1.10 Some remote subsystems do not recover after route setunavailability 217

23.1.11 A signalling point parameter or a subsystem parameter does not have thedescribed effect 218

23.1.12 SCCP screening does not come into effect 21923.1.13 Manual routing test fails 220

Related Topics 223

DN02143262Issue 16-1 en30/01/2009


Contents


30/01/2009


Summary of changes

Changes between document issues are cumulative. Therefore, the latestdocument issue contains all changes made to previous issues.

Changes between issues 16-1 and 16-0

Editorial corrections have been made, no changes in technical content.

Changes between issues 16-0 and 15-5

The name of this document has been changed from Signalling in ATMNetwork (RNC) to Configuring Signalling Connections in ATM Network(RNC).

Signalling in 3G

. In this release, the maximum number of active connectionssupported at an AAL2 Signalling Entity instance ( = one computerunit) is approximately 16000.

. Information on signalling in IP network has been added to thischapter. At the Iu-PS, Iu-CS and Iur interfaces, the signalling datacan be carried on ATM-based, IP-based or IP over ATM-basedprotocol stacks. At the Iub interface, the signalling data can becarried either on ATM-based or IP-based protocol stack.

SS7 configurations in RNC

. Information on the requirements for other network elements due tothe Signalling Point Management Cluster (SPMC) has been added.

. IP-based protocol stacks have been added to the Iur and Iuinterfaces.

SAAL UNI signalling

. Information has been added on the IP-based Iub interface.

DN02143262Issue 16-1 en30/01/2009


Summary of changes

MTP level signalling network

. Information on the migration from Mobile Switching Centers to MSCServers and Multimedia Gateways has been removed as obsolete.

SCCP level signalling network

. This section has been updated because in this release, it is possibleto configure SCCP traffic routing based on the Calling Party globaltitle (GT).

. Contents of this chapter have been rewritten and reorganised,especially in the steps for planning SCCP level STP trafficrestrictions and planning SCCP load sharing.

Setting/modifying GT based traffic restrictions

. This section has been updated because in this release, it is possibleto configure SCCP traffic routing based on the Calling Party globaltitle (GT). The MML command group OD has been replaced by NI inthe steps for calling GT translation result for screening and callingGT analysis.

Creating global title analysis for called GT

. The name of this section has changed from Creating global titleanalysis to Creating global title analysis for called GT.

Creating calling GT routing configuration

This is a new section.


30/01/2009


1 Signalling in 3G

The signalling data is carried by the SS7 signalling network on SAAL NNI(network node interface) protocol stack in ATM network or on SIGTRAN inIP network. At the Iub interface in ATM network, between RNC andWCDMA BTSs the signalling links are permanent ATM virtual channelconnections on the SAAL UNI (user-network interface) protocol stackwithout the SS7 signalling network layer. In IP network, the signalling linksare direct SCTP associations.

The figure below shows the different logical interfaces and networkelements in a 3G network. The transport medium can be either ATM-basedor IP-based. The SAAL NNI / SS7 signalling network ends at the RNCnetwork element. The WCDMA Base Stations can be connected to theRNCs at the Iub interface either through permanent SAAL UNI signallinglinks in ATM-based signalling, or the signalling links can be direct SCTPassociations in IP-based signalling.

DN02143262Issue 16-1 en30/01/2009


Signalling in 3G

BTS WCDMA Base Transceiver Station

MSS MSC Server

RNC Radio Network Controller

PSTN Public Switched Telephone Network

MGW Multimedia Gateway

SGSN Serving GPRS Support Node

Figure 1. Signalling transport in 3G

MSS

PSTN

SAAL NNI/SS7 signallingSAAL UNI signalling

RNC

Iu-CS (ATM/IPoA)

Iur (ATM/IPoA)

Iub (IP)

RNC

Iub (ATM)

Iu-CS (IP)

MGW

Iu-PS (ATM/IPoA/IP)

SGSN

MGW

Sigtran

Sigtran

BS

BS

BTSs

BS

BS

BTSs

SCTP/IP signalling


30/01/2009


Capacity of ATM and IP signalling protocols

MTP level 3 supports 128 signalling links per computer unit (CU). In ATMsignalling, SAAL-UNI supports 448 signalling links per computer unit (CU).In IP signalling, SCTP/IP supports 150 associations per computer unit(CU) for transporting C-NBAP and D-NBAP signalling messages.However, the CU processing capacity may limit the number of supportedsignalling links, because the capacity of the computer unit depends onother features sharing the same CU.

MTP level 3 supports 4096 signalling route sets (12 bits). However,processing capacity or memory consumption may limit the number ofsignalling points to less than 4096.

MTP level 3 supports eight signalling routes in one route set.

In ATM signalling, MTP level 3 supports 16 signalling links in one link set.This value is limited by the SLC, which is four bits. In IP signalling, MTPlevel 3 supports one signalling link in one link set and up to 16 SCTPassociations in the association set. One SCTP association setcorresponds to one signalling link.

MTP level 3 does not restrict the number of CUs performing signallingmessage handling.

SCCP recognises and manages any of the signalling points known by SS7protocol stack and 20 subsystems in each of them.

SCCP can handle a minimum of 5000 GT translation entries.

SCCP can handle 16383 signalling connections simultaneously in onecomputer unit. This means that 16383 different SORPRO hands can bealive simultaneously. A message is directed to a hand using a specificreference number in the message. This reference number is 24 bits wide;10 bits of it are used to point to the correct computer unit and the other 14bits to point to the correct hand.

Connectionless service needs a hand when segmentation is required.Hand count is a parameter which is set to the software package. Handcount must be estimated according to need.

GT analyses are tree-like analyses. The number of GT analyses dependson how many digits GT numbers contain and how big is the dispersion ofthe numbers. One record of the GANFIL file can contain 1–16 digits (digitsin the same record cannot belong to the same analysis) and the maximumnumber of records is 49000.

DN02143262Issue 16-1 en30/01/2009


Signalling in 3G

The maximum number of active connections supported at an AAL2Signalling Entity instance ( = one computer unit) is approximately 16000.

The number of AAL2 paths (ATM VCC) between two adjacent AAL2 nodescan be up to 65535.


30/01/2009


2 SS7 signallingSS7 Broadband MTP3

The Message Transfer Part (MTP) provides functions that enable MTPUser Part (upper layer) information transport across the SS7 network tothe required destination. MTP has network management functions toguarantee error-free message transfer and avoid network and systemfailures that would affect the transfer of signalling information.

MTP level 3 defines transport functions that are common to andindependent of the operation of individual signalling links. These functionsfall into two major categories, which are signalling message handlingfunctions and signalling network management functions.

MTP3 Signalling message handling

Signalling message handling comprises of message routing,discrimination and distribution functions which are performed at eachsignalling point in the signalling network.

Message routing is used when messages are sent, while messagedistribution to appropriate User Part is used when messages are received.Message discrimination is used to determine whether an incomingmessage is destined to another signalling point.

Message routing selects a suitable signalling link, and if two or more linksare used to carry traffic to the same destination, then the load sharingfunction is used to distribute traffic among the links.

Message routing, discrimination and distribution are based on the part ofthe label called the routing label, on the service indicator and, in nationalnetworks, also on the network indicator.

The maximum message length in narrowband MTP level 2 is 272 SIFoctets, while the maximum SDU size in broadband links is 4091 octets(maximum SDU size supported by SSCF-NNI is 4096 octets).

DN02143262Issue 16-1 en30/01/2009


SS7 signalling

No specific features for MTP3 message interworking between broadbandand narrowband sides are used. Messages from narrowband tobroadband and vice versa go via the User Parts.

MTP3 Signalling network management

The signalling network management functions provide the actions andprocedures required to maintain signalling service, and to restore normalsignalling conditions in the event of disruption in the signalling network,either in signalling links or at signalling points. The disruption may be in theform of complete loss of a signalling link or a signalling point, or in reducedaccessibility due to congestion. For example, in the case of a link failure,the traffic conveyed over the faulty link should be diverted to one or morealternative links. The link failure may also result in unavailable signallingroutes and this, in turn, may cause diversion of traffic to other signallingpoints in the signalling network (signalling points to which no faulty linksare connected).

The signalling network management functions are divided into:

. signalling traffic management

. signalling link management

. signalling route management

SS7 SCCP

SCCP (Signalling Connection Control Part) provides additional functionsto MTP level 3 services to serve both connection-oriented andconnectionless network services to transfer circuit related and non-circuitrelated signalling information and other information between networkelements via SS7 network. SCCP provides also more complicatedaddressing mechanisms to those of MTP. SCCP manages the status ofsignalling points and subsystems (SCCP users) and informs theconcerned signalling points and subsystems about subsystem statechanges. In the broadband network, two new message types, long unitdata (LUDT) and long unit data service (LUDTS) will be introduced.

SCCP Connectionless service

The connectionless network service allows a user of the SCCP to requesttransfer of up to 3560–3952 octets of user data without first requestingestablishment of a signalling connection. The amount of transferred datamay vary depending on the message used (XUDT or LUDT), the usedaddresses and possible optional parameters.


30/01/2009


SCCP connectionless service handles the n-unit data primitives that comefrom subsystems (SCCP User Part) and UDT, UDTS, XUDT, XUDTS,LUDT and LUDTS messages that are received from the network. Bothprotocol classes 0 and 1 are supported. Connectionless service routesmessages and either sends them to the network in appropriate format ordelivers them to local subsystems.

SCCP is able to handle UDT (Unit Data) and UDTS (Unit Data Service)messages. The maximum length of transferred user data is 255 but it maybe even shorter if the called and calling address include GT or if there areoptional parameters in messages.

SCCP is able to handle XUDT (Extended Unit Data) and XUDTS(Extended Unit Data Service) messages. The maximum length oftransferred user data is 3560 but it may be even shorter if the called andcalling address include GT or if there are optional parameters inmessages.

SCCP is able to handle LUDT (Long Unit Data) and LUDTS (Long UnitData Service) messages. The maximum length of transferred user data is3952.

If a message cannot be delivered to its destination, the message returnprocedure will be initiated. If the return option is set in the message, it isreturned to the originator in UDTS, XUDTS or LUDTS message.

SCCP connection-oriented service

Connection-oriented procedures include the functions to establish andrelease a temporary signalling connection between two subsystems andthe functions to transfer data on a signalling connection.

SCCP supports packed data also in other than data messages. It ispossible to transfer user data also in CR (Connection Request), CC(Connection Confirm), CREF (Connection Refused) and RLSD (Released)messages.

SCCP supports connection-oriented segmentation. It is possible totransfer more data in one data primitive than what can be transferred inone narrowband MTP level 3 message.

SCCP connection-oriented service has a hand process for each signallingconnection. The master process routes the n-connect-req primitive orincoming CR message and if the routing succeeds, it reserves a hand forthe connection. After that the hand process takes care of the procedures ofthe signalling connection until the connection is released. SCCPconnection-oriented service uses protocol class 2.

DN02143262Issue 16-1 en30/01/2009


SS7 signalling

SCCP routing

The SCCP routing procedures are common for both connectionless andconnection-oriented service. The routing function provides global titletranslation (GTT) for the messages where routing is based on Global Title(GT). With a GTTa new destination signalling point or subsystem is found.After that the routed message is forwarded to a destination with routingbased on GT or Subsystem Number (SSN).

SCCP supports international and national network standards. The maindifference between these standards is the size of the signalling point code(SPC) which can be 14–, 16– or 24–bit wide. Other differences are, forexample, the format of the SCCP address and the format of the GT.

SCCP Signalling network administration

SCCP administration enables the operator to configure the SCCPsignalling network, manage the status of signalling points and subsystems,define the concerned signalling points and subsystems of broadcast andlocal broadcast procedures and manage SCCP addresses.

A subsystem is a user of the SCCP which is recognised in a signallingpoint by a subsystem number (SSN). The subsystem may use SCCPdirectly or indirectly via TCAP.

SCCP Signalling network management

SCCP management maintains the dynamic states of signalling points andsubsystems. SCCP management receives signalling point statusinformation from MTP and subsystem status information from other nodesin SCCP management messages. SCCP management informs theconcerned subsystems about subsystem and signalling point statechanges.


30/01/2009


3 SS7 transport medium in RNC

SS7 signalling network services over ATM network requires SignallingAAL (SAAL) to deliver MTP3 signalling messages between networkelements. SAAL is responsible for the correct transfer of signallingmessages on an ATM-based SS7 signalling link.

SAAL-NNI contains the following sublayers:

. SSCF-NNI (Service Specific Co-ordination Function at the NetworkNode Interface)

. SSCOP (Service Specific Connection Oriented Protocol)

. AAL5.

Signalling messages are transferred with SSCOP protocol which is thepeer-to-peer data link protocol defined for high speed data transfer.

SSCF-NNI layer performs mapping of MTP3 primitives to SSCOPprimitives and enhances the services provided by the SSCOP suitable toMTP3.

SAAL user manages the used signalling link state with primitives, which,for example, start and stop the signalling link. Other primitives are used totransfer the L3 signalling message units and during changeoverprocedure.

SSCF-NNI performs proving to ensure that the signalling link is capable oftransferring signalling information. The proving period can be either normalor emergency. During the proving period and normal signalling transfer,layer management monitors errors and makes the decisions whether thequality of the signalling link is adequate.

SSCF-NNI controls the signalling link flow control. It informs the SAAL userif the used link is congested or if the congestion of the link is ceased. Thecriticality of the congestion is defined by using four different levels.

DN02143262Issue 16-1 en30/01/2009


SS7 transport medium in RNC

SSCF-NNI also provides local retrieve. This function enables to retrievethose messages which are delivered to the SSCOP but which are not yettransmitted to the peer entity. SAAL user uses local retrieve during thechangeover procedure.

SSCF-NNI also offers signalling link usability information. With theinformation it offers, it is possible to calculate events and durations. Thisenables the SS7 statistics to maintain signalling link dependentinformation.


30/01/2009


4 SS7 network concepts

The following introduces the main concepts of the signalling network.

Signalling point (SP), signalling transfer point (STP) and signallingend point (SEP)

Signalling point is a network element which sends and receives signallingmessages. A signalling point can operate as signalling transfer point (STP)which means that signalling traffic goes through the signalling transferpoint towards the destination signalling point. There can be severalsignalling transfer points between two signalling end points (SEP), seefigure below.

Figure 2. Example of two signalling end points (SEP) which transfer thesignalling messages through two signalling transfer points (STP)

A signalling transfer point does not necessary need all functional parts thatsignalling end points have. Two different network elements can exchangeSS7 signalling even when only the minimum configuration exists in bothelements.

For example, in the figure below, if network element A has RNSAP andoperates with network element B, then both elements have to haveRNSAP, SCCP and MTP configuration, but in the STP between A and B,there can exist only MTP or MTP and SCCP.

SEP STP STP SEP

DN02143262Issue 16-1 en30/01/2009


SS7 network concepts

Figure 3. Signalling between two network elements and the STP in between

MTP

RNSAP

SCCP

MTP

RNSAP

SCCP

MTP

SCCP

Network element A Signalling transfer point Network element B


30/01/2009


5 SS7 configurations in RNC

The implementation of a SS7 signalling system in a Nokia networkelement consists of different functional parts. The main idea is that allfunctional parts offer their services to the other parts. Between differentinterfaces there are different functional parts. In the figures below, thefunctional parts are presented by interface and by type of network element.

RNC between Iur and Iu interfaces (RNC — RNC — MGW )

Figure 4. The functional parts in RNC between Iu and Iur interfaces (RNC —RNC — MGW)

RNC

ATM

Physical layer

RANAP

SCCP

SAAL NNI

Iuinterface

Iurinterface

RNSAP

MTP3

MGWRNC

M3UA

SCTP

IP

Ethernet ATM

M3UA

SCTP

IP

EthernetATM

DN02143262Issue 16-1 en30/01/2009



RANAP The Radio Access Network Application Part providesthe radio access network signalling protocol thatconsists of mechanisms which handle all theprocedures between the core network and radioaccess network (RAN).

RNSAP The Radio Network Subsystem Application Partprovides a protocol over Iur interface which enables,for example, soft handover between two RNCs.

SCCP The Signalling Connection Control Part provides twodifferent services, the connection-oriented and theconnectionless services for other applications. TheSCCP itself uses the MTP as a service.

The connection-oriented service is used for virtualconnections between network elements, and itprovides the procedures for establishment andrelease of those virtual connections.

The connectionless service enables non-call-relatedcommunication between network elements whichhave to exchange information only for short periods.Furthermore, the connectionless service provides aglobal title translation function, which enablescommunication with network elements in othersignalling networks.

MTP3 MTP Level 3, Signalling Network level (level 3) canbe divided into two parts: message handling, whichincludes message routing and distribution to therespective user part, and network management,which provides all necessary procedures for using thesignalling network in an optimal way.

SAAL NNI Signalling ATM Adaptation Layer, Network NodeInterface (NNI) consists of protocol stacks SSCF-NNI(service specific coordination function — NNI),SSCOP (service specific connection orientedprotocol) and AAL5 (ATM adaptation layer 5). Thisprotocol stack provides reliable transport ofmessages over the ATM layer.

M3UA SS7 MTP3 User adaptation Layer is a part of theIETF signalling transport (SIGTRAN) stack for thetransport of any signalling system No.7 (SS7) MTP3-user signalling over IP using the services of thestream control transmission protocol (SCTP)

SCTP Stream Control Transmission Protocol is aapplication-level datagram transfer protocol whichoperates on top of an unreliable routed packet-switched network such as IP.


30/01/2009


When the Signalling Point Management Cluster (SPMC) with two MGWsand an MSC Server (MSS) is in use, there are additional requirements forsome of the network elements involved in SS7 signalling. Theserequirements are mainly related to the Radio Network Controller (RNC):

. RNC needs to have the capability to handle RANAP and ALCAP/AAL2 signalling independently. RANAP is terminated to the MSSwith the cluster concept, but ALCAP/AAL2 is terminated to theMGWs. That is why RNC needs to have two signalling link sets andneeds to see both DPCs of the MSS with the cluster concept forRANAP and the DPC of the MGW for ALCAP.

. For the user plane, it is the MSC Server that selects the MGW. TheRNC needs to enable at least two destinations and routes for the Iu-CS traffic for the two MGWs. The RNC should be able to get thetransport address, that is, the E.164 address of the selected MGW,from the RANAP RAB Assignment Request operation and thenperform digit analysis, find a route for the selected destination, andestablish the ALCAP/AAL2 signalling setup to the MGW which theMSC Server has allocated.

. If the RNC in question supports alternative routing between twosubdestinations/AAL2 routes for the selected destination (that is, theMGW) that will provide transmission protection between the RNCand the MGWwithout SDH protection (that is, without an SDH ring orMSP 1+1).

DN02143262Issue 16-1 en30/01/2009



RNC between Iur and Iu-PS interfaces (RNC — RNC — SGSN)

Figure 5. The functional parts in RNC between Iur and Iu-PS





RNC

ATM

Physical layer

RANAP

SCCP

SAAL NNI

Iu-PSinterface

Iurinterface

RNSAP

MTP3

Combi-SGSNRNC

M3UA

SCTP

IP

Ethernet ATM

M3UA

SCTP

IP

EthernetATM


30/01/2009







DN02143262Issue 16-1 en30/01/2009



RNC between Iur and Iur interface (RNC — RNC — RNC)

Figure 6. RNC between Iur and Iur interface (RNC — RNC — RNC)





RNC

ATM

Physical layer

SCCP

SAAL NNI

Iurinterface

Iurinterface

RNSAP

MTP3

RNCRNC

M3UA

SCTP

IP

Ethernet ATM

M3UA

SCTP

IP

EthernetATM


30/01/2009






RNC at Iub interface (RNC — WCDMA BTS)

See SAAL UNI signalling.

DN02143262Issue 16-1 en30/01/2009




30/01/2009


6 SAAL UNI signalling

SAAL UNI (Signalling ATM Adaptation Layer, User-Network Interface)provides SSCOP transport service to signalling protocols. A signalling linkis configured using ATM VCC and terminated to a CPU with AAL5adaptation.

The SSCOP (Service Specific Connection Oriented Protocol) providesmechanisms for the establishment and release of connections, and thereliable exchange of information between peer entities.

The SSCOP performs the following functions:

. Sequence integrity

. Error correction by selective retransmission

. Flow control

. Error reporting to Layer Management

. Keep alive

. Local data retrieval (for SSCF-NNI use)

. Connection control

. Transfer of user data

. Protocol error detection and recovery

. Status reporting

. Signalling link management functions (own development)

. Suspend and resume assured data transfer (SSCF-NNI specificfunction according to Generic MTP level 3)

. Transmitting side congestion adjust, detection and inform (SSCF-NNI specific function according to Generic MTP level 3)

DN02143262Issue 16-1 en30/01/2009


SAAL UNI signalling

The SSCF (Service Specific Coordination Function) performs acoordination function between the service required by the signalling layer 3user (SAAL user) and the service provided by SSCOP.

SSCF-UNI provides the following services to the SAAL user:

. Establishment and release of SAAL connections for assured transferof data

. Assured transfer of data

. Unacknowledged transfer of data (optional)

. Transparency of transferred information

. Signalling link management functions (own development)

The AAL type 2 signalling protocol and NBAP application protocol use UNISAAL in point-to-point signalling connections where there is no SS7signalling network available.

At the ATM-based Iub interface, between RNC and WCDMA BTSs themessages of the AAL type 2 signalling protocol are transported on top ofthe SAAL UNI stack. The figure below presents the SAAL UNI as well asSCTP/IP signalling stacks at the Iub interface.

Figure 7. The functional parts in RNC between Iub and Iur/Iu interfaces

RNC

ATM

Physicallayer

SAALUNI

Iur/Iuinterface

Iubinterface

AAL2

RNC/MGW/SGSN

BTS

SCTP

IP

Ethernet

M3UA

SCTP

IP

EthernetATM

SAALNNI

MTP3

NBAP


30/01/2009


AAL2 ATM adaptation layer type 2. The control planefunctions which establish and release AAL2connections and the maintenance functionsassociated with the AAL2 signalling.


SAAL UNI Signalling ATM Adaptation Layer, User-NetworkInterface (UNI) consists of protocol stacks SSCF-UNI(service specific coordination function — UNI),SSCOP (service specific connection orientedprotocol) and AAL5 (ATM adaptation layer 5). Thisprotocol stack can carry the AAL2 signallingmessages directly without using the MTP3B.




RANAP signalling in Iu-PS can also be transported over SCCP/M3UA/SCTP/IP stack, and NBAP signalling in Iub can also be transported overSCTP/IP stack. The figure below presents the IP-based signalling protocolstacks at the Iu-PS and Iub interfaces.

DN02143262Issue 16-1 en30/01/2009


SAAL UNI signalling

Figure 8. The functional parts in RNC between Iub and Iu-PS


NBAP Node B Application Part controls protocol betweenthe base transceiver station (BTS) and radio networkcontroller (RNC)



RNC

ATM

Physical layer

Iu-PSinterface

Iubinterface

Combi-SGSNBTS

NBAP

SCTP

IP

Ethernet

M3UA

SCTP

IP

EthernetATM

SCCP

RANAP

SAALUNI

SAALNNI

MTP3


30/01/2009



SAAL UNI Signalling ATM Adaptation Layer, User-NetworkInterface (UNI) consists of protocol stacks SSCF-UNI(service specific coordination function — UNI),SSCOP (service specific connection orientedprotocol) and AAL5 (ATM adaptation layer 5). Thisprotocol stack can carry the AAL2 signallingmessages directly without using the MTP3B.

M3UA SS7 MTP3 User adaptation Layer is a part of theIETF signalling transport (SIGTRAN) stack for thetransport of any signalling system No.7 (SS7) MTP3-user signalling over IP using the services of thestream control transmission protocol (SCTP).


DN02143262Issue 16-1 en30/01/2009


SAAL UNI signalling


30/01/2009


7 AAL type 2 signalling protocol

The AAL type 2 (ATM adaptation layer type 2) signalling protocol providessignalling services for establishing, maintaining and releasing AAL type 2point to point data connections between two AAL type 2 end users. Theconnections can be created across a network that consists of both ATMand AAL type 2 switches.

ATM adaptation layer type 2

ATM adaptation layer type 2 (AAL type 2) is an ATM adaptation layerdesigned exclusively to serve the needs of wireless applications such asmobile telephony. AAL type 2 allows low bit rate and delay-sensitiveapplications to share a single ATM connection to maximise the networkutilisation. At the same time the protocol also guarantees the delayrequirements. Since AAL type 2 enables multiplexing of voice packetsfrom many users on a single ATM connection, it increases the number ofmobile telephony users who can be accommodated in a certain fixedbandwidth.

AAL type 2 switching

The AAL type 2 switching network is an overlay network atop ATM. AALtype 2 switching is performed at the AAL level. The traditional VPI/VCItable used for ATM cell switching has been extended by one more level byintroducing CID entries to identify AAL type 2 connections. AAL packetsencapsulated within an ATM cell are switched based on their VPI/VCI/CIDvalues.

An ATM cell received at an AAL type 2 switch is first de-multiplexed intoAAL type 2 connections (CIDs), then switched and assembled into anoutgoing ATM cells according to the entries found in the VPI/VCI/CIDtable.

DN02143262Issue 16-1 en30/01/2009


AAL type 2 signalling protocol


30/01/2009


8 Signalling states

8.1 States of signalling route sets

The state of a signalling route set depends on the states of the signallingroutes included in the route set. The signalling route set has four states;available (AV), unavailable (UA), restricted (AR) and congested (CONG).

The signalling route set is available (in state AV) when one or more of itssignalling routes are available, i.e. can be used by signalling traffic. Theroute set is unavailable (in state UA) when all its routes are out of service.The state of the route set changes automatically to AV when the firstsignalling route proves to be available.

The signalling route set is congested (in state CONG), if the signalling linkon the active route is overloaded. The signalling route set assumes stateCONG, if a signalling point on the route receives a 'transfer controlled'message (TFC) that concerns the signalling point served by the route set.Time supervision takes care of changing the state automatically into AVwhen the overload situation is over.

You can use the NER command to interrogate the states of the signallingroute sets.

8.2 States of signalling routes

You can define both main states and substates for a signalling route. Themain state indicates whether the route is available (AV) or unavailable(UA). The substates give more information on the working state, forexample, who has set the route and whether it is in spare state. By settingdifferent working states, you can change the signalling traffic over toanother signalling route without causing breaks in the traffic flow.

DN02143262Issue 16-1 en30/01/2009


Signalling states

Table 1. States of the signalling routes

Main state - substate Name of the state Meaning/reason

AV-EX available-executing The signalling route istransferring signallingtraffic.

AV-SP available-spare The signalling route doesn'ttransfer signalling traffic butcan be taken into use.

UA-INU unavailable-deactivated byuser

User has deactivated theroute.

UA-INS unavailable-deactivated bysystem

The system hasdeactivated the route./Thesignalling route istransferring signallingtraffic.

UA-INR unavailable-deactivated byremote exchange

The remote end hasdeactivated the route./Thesignalling route istransferring signallingtraffic.

UA-AD unavailable-activationdenied

Activation of the route isdenied./The signalling routeis transferring signallingtraffic.

AR-EX available but restricted-executing

See the text.

AR-SP available but restricted-spare

See the text.

Available but restricted, ARThis state is a parallel state for "available" (AV): inthis state, the signalling route can transfer signallingtraffic and it also has the substates "executing" (EX)and "spare" (SP) in service.

The state is possible only if the signalling route setuses the procedure "transfer restricted" (moreinformation in SS7signalling network parameters. Thesignalling route which is in this state has received a"transfer restricted" message from the transfer point,which lowers the priority of the route to some extent.


30/01/2009


8.3 States of signalling link sets

The state of a signalling link set depends on the states of its links. The linkset has two states, available (AV) and unavailable (UA).

The signalling link set is in state AV when at least one of the links includedin the link set is available.

The link set is in state UA if all its links are in state unavailable. The statechanges automatically into AV, when one (or more) of the signalling links(included in the link set) assume state AV.

You can use the NES or NSI commands to interrogate the states ofsignalling link sets.

8.4 States of signalling links

A signalling link has two main states: available (AV) and unavailable (UA).State AV has one substate and state UA can have one or two substates atthe same time.

Table 2. States of the signalling links.

Main state -substate 1-substate 2

Name of the state Meaning and thechange made

AV-EX available-executing Link is working normally

UA-AD unavailable-activationdenied

Operator has taken the linkout of use and has deniedthe activation. See the text.

UA-TST unavailable-testing User has started a data linktest and only test traffic canbe transferred by the link,while no signalling traffic isallowed. See the text.


Operator has taken the linkout of use. To activate thelink use command NLC.


System has taken the linkout of use. Link has notcompleted the initialalignment or the signallinglink test proceduresuccessfully. See the text

DN02143262Issue 16-1 en30/01/2009


Signalling states

Table 2. States of the signalling links. (cont.)



UA-BLU unavailable-blocked byuser

User has blocked thesignalling link.

UA-BLR unavailable-blocked byremote exchange

Remote end exchange hasblocked the signalling link,or there is a processoroutage condition at theremote end.

UA-BLB unavailable-blocked byuser and remote exchange

The signalling link hasbeen blocked at both ends.

UA-IBL unavailable-inhibited local User has inhibited the link.

UA-IBR unavailable-inhibitedremote

Remote end has inhibitedthe link.

UA-IBB unavailable-inhibited localand remote

The signalling link isinhibited at both ends.

UA-INU-IBL unavailable-deactivated byuser-inhibited local

User has deactivated andinhibited the signalling link.

UA-INU-IBR unavailable-deactivated byuser-inhibited remote

User has deactivated andthe remote end hasinhibited the signalling link.

UA-INU-IBB unavailable-deactivated byuser-inhibited local andremote

User has deactivated andinhibited and the remoteend has inhibited thesignalling link.

UA-INS-IBL unavailable-deactivated bysystem-inhibited local

System has deactivatedand user has inhibited thesignalling link.

UA-INS-IBR unavailable-deactivated bysystem-inhibited remote

System has deactivatedand remote end hasinhibited the signalling link.

UA-INS-IBB unavailable-deactivated bysystem-inhibited local andremote

System has deactivatedand user has inhibited thesignalling link at both ends.

UA-BLU-IBL unavailable-blocked byuser-inhibited local

User has blocked andinhibited the signalling link.

UA-BLU-IBR unavailable-blocked byuser-inhibited remote

User has blocked andremote end has inhibitedthe signalling link.

UA-BLU-IBB unavailable-blocked byuser-inhibited local andremote

User has blocked thesignalling link and thesignalling link is inhibited atboth ends.


30/01/2009


Table 2. States of the signalling links. (cont.)



UA-BLR-IBL unavailable-blocked byremote exchange-inhibitedlocal

The signalling link isblocked in remote end anduser has inhibited thesignalling link.

UA-BLR-IBR unavailable-blocked byremote exchange-inhibitedremote

The signalling link isblocked and inhibited atremote end.

UA-BLR-IBB unavailable-blocked byremote exchange-inhibitedlocal and remote

The signalling link isblocked at the remote endand inhibited by user atboth ends.

UA-BLB-IBL unavailable-blocked byuser and remote exchange-inhibited local

User has blocked andinhibited the signalling linkand the remote end andhas blocked the signallinglink.

UA-BLB-IBR unavailable-blocked byuser and remote exchange-inhibited remote

User has blocked thesignalling link and thesignalling link is blockedand inhibited at remoteend.

UA-BLB-IBB unavailable-blocked byuser and remote exchange-inhibited local and remote

The signalling link isblocked and inhibited atboth ends.

Inhibiting a signalling link

You can inhibit the signalling link from the local end. Then the signallinglink gets into state 'unavailable-inhibited local' (UA-IBL). If you want to takethe signalling link back into use, use the NLC command.

Signalling link inhibition means that the signalling link is inhibited from thesignalling traffic of the user part but it can transfer maintenance and testmessages. The inhibition does not cause any measures on level 2. It istaken care of by the signalling link control function on level 3. The inhibitionis accepted only if it does not make any accessible destinations (signallingpoint) inaccessible at either end.

DN02143262Issue 16-1 en30/01/2009


Signalling states

If a signalling link is in state 'unavailable-inhibited remote' (UA-IBR), theoperator of the exchange at the remote end of the signalling link hasinhibited it. You cannot uninhibit such signalling links but they can be takeninto use by applying a system in case some signalling point wouldotherwise become inaccessible.

When the signalling link is inhibited at both ends, the state of the signallinglink is 'unavailable-inhibited local and remote' (UA-IBB). In this case youcan change it to state UA-IBR by using the NLC command, if you want touninhibit it locally.

Blocking a signalling link

You can block the signalling link. It means that the signalling link is set toprocessor outage state at the local end and no signalling messages aretransferred over the link. In this case the signalling link is in state'unavailable-blocked by user' (UA-BLU).

The signalling link can also be blocked at the remote end network elementor at both ends. Then the user of the remote end network element hasblocked the signalling link which is in state 'unavailable-blocked by remote'(UA-BLR). This means that a processor outage condition exists at theremote end. If the signalling link has been blocked at both ends, thesignalling link is in state 'unavailable blocked by user and remote' (UA-BLB).

Signalling link in state UA-AD

If a signalling link is in state 'unavailable, activation denied (UA-AD)' itmeans that the operator has taken it out of service and has denied itsactivation. If you want to activate it, first you should use the NLC commandto activate the signalling link.

If a signalling link is in state 'unavailable deactivated by user (UA-INU)' itmeans that the operator has taken it out of service. If the link is in thisstate, you should activate it by using the NLC command.

Signalling link in state UA-INS

If a signalling link is in state 'unavailable-deactivated by system' (UA-INS)it means that the signalling link has not completed the initial alignment orthe signalling link test procedure successfully.


30/01/2009


Signalling data link test procedure

The signalling link can be also in state Tested (TST). This means that theuser has started a data link test and only test traffic can be transferred bythe link, while no signalling traffic is allowed. Before the user can place alink in state TST, the link must first be in state 'unavailable-activationdenied' (UA-AD). You can change the state with the NLD command. Afterthat, you can define how to test the link by using the NLT command.

8.5 States of SCCP signalling points

Two states can be seen in the execution printouts. The first one has twopossible values: AV (available) or UA (unavailable). The normal state isalways AV, if a primary destination point or the replicated destination pointis available. The state of SCCP signalling point should normally follow thestate of the signalling route set on the MTP level. The second state showsthe state of an individual signalling point.

For instructions, see Activating SCCP configuration.

Table 3. States of SCCP signalling points.

Main state - substate Name of the state Meaning

AV-EX available-executing The SCCP signalling pointtransfers signalling traffic.

AV-SP available-spare The state of replicatedsignalling point is availableand the point is ready tohandle traffic, if the primarysignalling point becomesunavailable.

AV-CONG available-congested The SCCP signalling pointtransfers signalling trafficwhile the signalling routeset is in an overloadcondition.


The user has taken theSCCP signalling point outof service.


The system has taken theSCCP signalling point outof service, because thesignalling point isunavailable on the MTPlevel.

DN02143262Issue 16-1 en30/01/2009


Signalling states

SCCP signalling point in state AV-CONG

In state AV-CONG (available-congested), the signalling point handles thesignalling traffic while the signalling route set is in an overload condition. Inan ANSI network, the messages have priorities and it is possible that alower priority message routing has terminated due to this overloadcondition. In an ITU network, the AV-CONG state does not have mucheffect on the SCCP level, so it is for information only. If the state ofsignalling point is AV-SP (available-spare), the state of replicated signallingpoint is available and it is ready to handle traffic should the primarysignalling point become unavailable.

SCCP signalling point in state UA-INS

If the state of a signalling point is UA-INS, it has been set to inactive stateby the system. This means that the route set on the MTP level has becomeunavailable and it should be verified.

SCCP signalling point in state UA-INU

If the state of a signalling point is UA-INU, it has been set to inactive stateby the user and it can be taken into use by using the NGC command.

Note

The state of signalling point is UA-INU when it is first created. Thismeans that you have to remember to change the state and take the SPinto use after creation. Note also that the replicated signalling point is instate UA-UD (unavailable-user denied), when it is created. You cantake the SCCP signalling point in use with the NGD command.

8.6 States of SCCP subsystems

The local subsystem must be registered, before it is allowed to use theSCCP services. The subsystem is in state AV-EX when it has beenregistered. State UA-INU (set inactive by user) is the state when the localsubsystem is created, and it should be activated using the NHC command.For instructions, see Activating SCCP configuration.


30/01/2009


Table 4. States of SCCP subsystems.

Main state-substate Name of the state Meaning

AV-EX available-executing The subsystem istransferring signallingtraffic.

AV-SP available-spare The subsystem is nottransferring signallingtraffic, but it canimmediately be taken intoservice, when necessary.Such can be the case forexample when there is afailure in the executingsubsystem.


The user has taken thesubsystem out of service.


The signalling point wherethe subsystem is located isunavailable.

UA-INR unavailable-deactivated byremote exchange

An SSP message isreceived or, alternatively,when the user is activatingthe signalling point, thesignalling point does notrespond to the subsystemstate test message with anSSA message.

UA-UD unavailable-use of replicadenied

Activation of a replicatedsubsystem is not permitted.When a new replicatedsubsystem is created, it isset into this state.

UA-UR unavailable-use as replicadenied

Use as a replicatedsubsystem is not permitted.

SCCP subsystem in state UA-INS

If the local subsystem is in state UA-INS, it has not been registered and nomessages can be delivered to it. Subsystem registration situation can beseen with the NHJ command. You can see from registration info if thesubsystem is using connection-oriented service, connectionless service,or local broadcast service. The FE subsystem is always using connection-oriented service. You can also see if the subsystem is using TC. Forexample, MAP, INAP and OMAP are subsystems that use TC.

DN02143262Issue 16-1 en30/01/2009


Signalling states

SCCP management subsystem (SCMG = 01) is automatically createdwhen you create a SCCP for signalling point. The state of SCMG shouldnormally follow the state of SCCP signalling. Nevertheless, it is possiblethat remote SCMG subsystems are in state UA-INS while signalling pointis in state AV-EX. This happens when the remote signalling point's MTPhas detected that the SCCP is out of service and sends the UPU message(User Part Unavailable) to your signalling point. Note that all actions toclear this situation have to be done at the remote signalling point.

SCCP subsystem in state UA-UD

If the state of a subsystem is unavailable - use of replica denied (UA-UD),it means that the activation of a replicated subsystem is not permitted.When a new replicated subsystem is created, it is set into this state. Thisstate can be changed by giving the NHD command.

Remote SCCP subsystem state

The states of other remote subsystems should normally be available (AV-EX). State UA-INU (set inactive by user) is set on when the subsystem iscreated. You can activate the subsystem by using the NHC command. If thestate of a subsystem is unavailable - inactive by system (UA-INS), itmeans that the state of the signalling point should also be unavailable (seeStates of SCCP signalling points).

If the state of a remote subsystem is unavailable — set inactive by remoteend (UA-INR), it means that a subsystem prohibited message (SSP) hasbeen received or, alternatively, when the user is activating the signallingpoint, the signalling point does not respond to the subsystem status testmessage (SST) with a subsystem allowed message (SSA). This state cannot be changed active by the user.


30/01/2009


9 Error messages in MTP commands

9.1 MTP command major errors

Major errors are indicated by the text:

COMMAND EXECUTION ABORTED

In such cases, the files may contain indefinite data or the contents of thefile of the active unit and those of the spare unit may differ from each other.

In addition, one of the error messages below is output.

/*** COMMUNICATION ERROR BETWEEN CCADMI IN CM AND CCADMI IN CCMU ***/

The Common Channel Signalling Management Unit (CCMU) may beoverloaded, preventing the exchange of messages between the units.

Re-enter the command after the overload is over.

Use the command AHO to see if the system has set Alarm 1004. If so,follow the alarm instructions.

One way to circumvent the failure is to perform a controlled switchover forthe CCMU.

This failure may also result if the CCADMI is missing from the CCMU.Check whether the CCADMI process exists and if not, start it by usingservice terminal commands.

/*** DISK UPDATING FAILED ***/

The disk updating has failed.

Use the command AHO to check if the system has set Alarm 1065. If so,follow the alarm instructions.

DN02143262Issue 16-1 en30/01/2009


Error messages in MTP commands

Use the command DUD to check that the disk updating queue is empty andcancel the change you made with the previous command (e.g. remove thecreated signalling link). After this, re-enter the command.

/*** DISTRIBUTION AND DISK UPDATING FAILED ***/

The data distribution and the disk updating have failed. The updating of asignalling file may have failed in some units.

Use the command AHO to check the alarms of the main memory andfollow the alarm instructions.

/*** DISTRIBUTION ERROR ***/

The data distribution has failed. The updating of a signalling file may havefailed in some units.

Use the command AHO to check the alarms of the main memory and followthe alarm instructions.

/*** INCORRECT MESSAGE ***/

An error is detected within the system's internal information flow. Thecontents or the length of the message received from the MML program orthe CCADMI is incorrect.

The problem may be due to a faulty software build.

/*** L3PARA FILE ERROR ***/

There may be an error in the L3PARA file. Copy the L3PARA file from theOMU's disk to the memory. If there is an error in the file taken from theOMU's disk as well, use the backup copy (if there is one).

9.2 MTP command minor errors

Minor errors are indicated by the text:

COMMAND EXECUTION FAILED

If a minor error interrupts the command's execution, the files are notmodified. In other words, the system is in the same state as it was beforethe command was given.


30/01/2009


Minor errors may be due to many different things. The most commonreasons are listed below:

. the parameter value given in the command is not permitted or isalready in use

. the system is not able to execute the given command, because thestate of some other part of the system is incorrect (for example, asignalling link is active)

. the change to be performed by the command applies to a computerunit which has not been created or which is not in a state compatiblewith the execution of the command

Check the parameters given in the command and re-enter the command.

In the case of interrogation commands, only minor errors can occur.

In addition, one of the error messages below is output.

/*** ABATE VALUE MUST BE SMALLER THAN ONSET VALUE ***/

When changing the abate value, it must be smaller than the onset value.Use the NOI command for the limit values of congestion thresholds andthe NOM command for the interdependencies of the limit values.

/*** ACTIVE UNIT STATE INCORRECT ***/

The active unit is in some other working state than WO-EX.

/*** ALL DESTINATION POINT INDEXES ALREADY USED ***/

All destination point indexes of matrix measurement are already in use.The OID command shows the destination point indexes of matrixmeasurement.

/*** ALL ORIGINATING POINT INDEXES ALREADY USED ***/

All originating point indexes of matrix measurement are already in use.The OID command shows the originating point indexes of matrixmeasurement.

/*** ALL SERVICE INDICATOR INDEXES ALREADY USED ***/

All service indicator indexes are already in use. The OIP command showsthe service indicator indexes.

/*** ALL SIGNALLING ROUTES CREATED ***/

DN02143262Issue 16-1 en30/01/2009



A maximum number of signalling routes have already been created. TheNRI command shows the created signalling routes.

/*** ALREADY CONNECTED TO GIVEN UNIT ***/

The signalling link to be transferred is already connected to the unit.

/*** ATTEMPT TO GIVE MORE THAN ONE ASSOCIATE

SIGNALLING ROUTE TO SIGNALLING POINT ***/

Only one of the signalling routes leading to the adjacent signalling pointcan be associated. For the other routes, the same network should be givenas the transfer point, but a different signalling point code from that of thesignalling route set.

/*** ATTEMPT TO HAVE RESTRICTED MTP (A INTERFACE)

IN SIGNALLING ROUTE SET TOGETHER WITH INDIRECT ROUTES ***/

The signalling route set can be created to support a restricted MTP only ifits only signalling route is associated (direct). In the case of trying tosupport a restricted MTP in a routing set with indirect signalling routes, thetask is interrupted and the above execution error message is output.

/*** ATTEMPT TO USE SIGNALLING POINT AS A SIGNALLING

TRANSFER POINT ALTHOUGH THIS IS DENIED BY ITS PARAMETER SET ***/

A signalling point cannot be used as a signalling transfer point if this isdenied by the parameter set of the signalling point. An execution errormessage may also be output if the signalling route set which the signallingpoint is part of has been created to support a restricted MTP and the userattempts to use the signalling point as a signalling transfer point.

/*** CCNETM NOT YET IN ACTIVE STATE ***/

The Signalling Links Management Program Block (CCNETM) could notprocess the data of the signalling link in the state in question.

/*** CCSU DOES NOT EXIST ***/

The CCSU does not exist.

/*** COMMUNICATION ERROR BETWEEN CCADMI AND CCDESM ***/

Communication between the MTP Data Management Program Block andthe Signalling Network Management Program Block failed.

/*** COMMUNICATION ERROR BETWEEN CCADMI AND CCNETM ***/


30/01/2009


Communication between the MTP Data Management Program Block andthe Signalling Links Management Program Block failed.

/*** COMMUNICATION ERROR BETWEEN CCADMI AND CM3PRO ***/

Communication between the MTP Data Management Program Block andthe Routing Working State Administration Program Block failed.

/*** COMMUNICATION ERROR BETWEEN CCADMI AND CS2PRO ***/

Communication between the MTP Data Management Program Block andthe Statistical Program Block for MTP (Centralized Part) failed.

/*** COMMUNICATION ERROR BETWEEN CCADMI AND SMNPRO ***/

Communication between the MTP Data Management Program Block andthe SCCP Management Program Block failed.

/*** COMMUNICATION ERROR BETWEEN CCADMI AND USPMAN ***/

Communication between the MTP Data Management Program Block andthe User Part Manager failed.

/*** CONFLICT BETWEEN CDIS66 RECORD COUNT AND L3PARA MAX INDEX VALUES ***/

The maximum index values of matrix measurement are outside CDIS66record count.

/*** CS2PRO BUSY WHEN ASKING MAXIMUM VALUES OF STATISTICAL INDEXES ***/

The Statistical Program Block for MTP (Centralised Part) is busy andcannot respond to the interrogation of the maximum values of statisticalindexes.

/*** DESTINATION POINT CODE ALREADY CONNECTED TO MATRIX MEASUREMENT ***/

The signalling destination point code is already connected to the MTPstatistics matrix measurement.

/*** DESTINATION POINT CODE DOES NOT CONNECT TO MATRIX MEASUREMENT ***/

The signalling destination point does not connect to the MTP statisticsmatrix measurement.

/*** DIRECT ROUTE FROM ROUTE SET CANNOT BE DELETED BECAUSE

THE LINK SET IS USED IN ANOTHER NETWORK ***/

DN02143262Issue 16-1 en30/01/2009



The direct route cannot be deleted if its route set is used in anothersignalling network.

/*** DISCARDING VALUE MUST BE BIGGER THAN ONSET VALUE ***/

When changing the discarding value, it must be taken care that it is biggerthan the onset value. Use the NOI command for the limit values ofcongestion thresholds and the NOM command for the interdependencies ofthe limit values.

/*** ERROR IN READING L3PARA FILE ***/

The reading of L3PARA failed.

/*** EXTERNAL ROUTING FAILURE ***/

The external routing by the Routing Administration Library (RTLLIB) failed.

/*** EXCHANGE TERMINAL INACTIVE ***/

The exchange terminal is in some other working state than active in theSignalling Link Control File (SLCONT).

/*** FAILED TO CLARIFY UPPER LIMIT OF PCM NUMBER ***/

A failure to clarify the upper limit of the number of the PCMs.

/*** FILE ACCESS ERROR ***/

The File System Library (FISLIB) has sent a file access error message tothe MTP Data Management Program Block (CCADMI). CCADMI has notbeen able either to read or write the file, depending on which task the errorhas occurred in. For further information on the error, see the log recordssaved in the central memory by CCADMI.

/*** ILLEGAL MESSAGE LENGTH BETWEEN MML AND CCADMI ***/

The length of the message between the MML and the CCADMI is illegal.

/*** ILLEGAL PARAMETER ***/

One of the parameters given by the user is illegal.

/*** ILLEGAL PCM ***/

An illegal PCM.


30/01/2009


/*** INCORRECT LINK STATE ***/

The signalling link is in a state where the modification command isimpossible.

/*** INCORRECT MESSAGE FROM CCADMI ***/

The MML received an incorrect message from the CCADMI.

/*** INCORRECT PARAMETER SET NAME ***/

The parameter set name is incorrect.

/*** INCORRECT SERVICE NAME ***/

The service name is incorrect.

/*** INCORRECT SIGNALLING LINK SET NAME ***/

The signalling link set name is incorrect.

/*** INCORRECT SIGNALLING LINK TABLE IN CCXHAN ***/

The signalling link table used by the Signalling Link Data Handling MML isincorrect. The signalling link table contains the signalling point codes givenby the user.

/*** INCORRECT SIGNALLING POINT NAME ***/

The signalling point name is incorrect.

/*** INCORRECT SIGNALLING TRANSFER POINT NAME ***/

The signalling transfer point name is incorrect.

/*** INSUFFICIENT NUMBER OF PARAMETERS ***/

The user has not given the data of the signalling link to be modified.

/*** GIVEN PARAMETER VALUE MUST BE BIGGER THAN VALUE OF THE LOWER LEVEL ***/

When modifying the limit values of congestion thresholds, it must be takencare that the limit values increase as the threshold value increases. Usethe NOI command for limit values of congestion thresholds and the NOMcommand for the interdependencies of the limit values.

/*** LAST SIGNALLING LINK IN SIGNALLING LINK SET ***/

DN02143262Issue 16-1 en30/01/2009



Deleting the signalling link fails if the signalling link is the last one in thesignalling link set. In such a case, the signalling link set must first bedeleted by the NSD command.

/*** MEASUREMENT 6.6 NOT STOPPED ***/

The MTP measurements must be stopped when modifying the MTPstatistics indexes. The measurement 6.6 has not been stopped. Themeasurement accords with the ITU-T recommendation Q.752. Themeasurements can be stopped by the OSD command.

/*** NEITHER SIGNALLING TERMINAL NOR SIGNALLING LINK SET INITIALIZED ***/

The signalling link terminal has not been initialized, and the signalling linkhas not been connected to any signalling link set.

/*** NO ASSOCIATE SIGNALLING ROUTE IN SIGNALLING ROUTE SET

TO SIGNALLING TRANSFER POINT ***/

The signalling point cannot be used as the signalling transfer point,because there is no associate signalling route to it.

/*** NO EXCHANGE TERMINAL FOR SIGNALLING DATA LINK ***/

There is no exchange terminal for the external PCM.

/*** NO FREE TERMINAL FUNCTION ***/

The user is trying to create more signalling links than allowed.

/*** NO FREE TERMINAL IN UNIT ***/

The transfer of the signalling link to another unit fails, because there is nofree terminal in the unit. A new signalling link terminal must be equipped inthe unit.

/*** ONLY ONE SIGNALLING ROUTE IN SIGNALLING ROUTE SET ***/

The last route in the signalling route set cannot be deleted by the NRRcommand, but the whole signalling route set must be deleted by the NRDcommand.

/*** ORIGINATING POINT CODE ALREADY CONNECTED TO MATRIX MEASUREMENT ***/

The originating point is already connected to the MTP matrix measurementQ.752 6.6.

/*** ORIGINATING POINT CODE DOES NOT CONNECT TO MATRIX MEASUREMENT ***/


30/01/2009


The originating point is not connected to the MTP matrix measurementQ.752 6.6.

/*** OTHER SIGNALLING POINTS EXIST IN SIGNALLING NETWORK ***/

The deletion of the signalling point is not allowed if there are othersignalling points in the signalling network.

/*** OWN ADDITIONAL SIGNALLING POINT EXISTS ***/

There is another signalling point code for the signalling point in thesignalling network. The data of the other signalling point code is defined inthe L3PARA (CCITT7 Level 3 Parameter File). Check the data by the NMIcommand and delete the other signalling point code unless it is necessary.

/*** OPC/DPC BUFFER OVERFLOW ***/

An overflow in the buffer which the MML program CCZHAN (SignallingRoute Set Data Handling) uses for transferring the originating point codes(OPC) or destination point codes (DPC) in the CCADMI message.

/*** OWN SIGNALLING POINT ***/

The function cannot be performed for own signalling point.

/*** OWN SIGNALLING POINT DOES NOT EXIST ***/

The function cannot be performed until own signalling point has beencreated. The signalling point can be created by the NRP command.

/*** OWN SIGNALLING POINT IS END POINT ***/

The user has attempted to define functions that are impossible for thesignalling point which is the end point.

/*** PARAMETER SET ALREADY EXISTS ***/

The parameter set exists already.

/*** PARAMETER SET DOES NOT EXIST ***/

The parameter set does not exist.

/*** PARAMETER SET IN USE ***/

DN02143262Issue 16-1 en30/01/2009



You are trying to delete or modify a parameter set which is in use. Checkthe parameter sets used by the signalling data links by the NCI commandor those used by the signalling route sets by the NRI command.

/*** PARAMETER SET NAME ALREADY RESERVED ***/

The parameter set name has already been reserved.

/*** PASSIVE UNIT STATE INCORRECT ***/

The passive unit is in SP-RE state. Wait until the passive unit is in SP-EXstate.

/*** PCM CIRCUITS EXIST TO SIGNALLING POINT ***/

The deletion of the signalling route set is impossible, because PCMcircuits have been connected to the signalling point.

/*** PREPARING FOR SWITCHOVER ***/

The switchover is being prepared. The MML commands are not received.

/*** REMOTE ACKNOWLEDGEMENT MISSED ***/

The remote acknowledgement has been missed.

/*** REQUESTED STATE ALREADY EXISTS ***/

The requested state already exists.

/*** RSPARA FILE ACCESSING ERROR ***/

An attempt to access files outside the RSPARA (Signalling Route SetParameter File).

/*** SEMIPERMANENT FILE UPDATING BUSY ***/

The semipermanent file updating is in progress. A new task requiringsemipermanent file updating will not be received simultaneously. Give anew command.

/*** SERVICE ALREADY EXISTS ***/

The service which the user tried to create already exists.

/*** SERVICE NAME ALREADY EXISTS ***/


30/01/2009


The service name is already used by another user part.

/*** SIGNALLING LINK ACTIVATION DENIED ***/

The signalling link activation is denied. Use the NLA command to enablethe activation.

/*** SIGNALLING LINK ACTIVATION FAILED ***/

The signalling link activation failed. This may be caused by a fault in thedata link connection or the remote end. If the signalling link activation fails,alarm 2072 is given.

/*** SIGNALLING LINK ACTIVATION NOT DENIED ***/

The signalling link activation is not denied. Deny the activation by the NLDcommand.

/*** SIGNALLING LINK ALREADY EXISTS ***/

The signalling link exists already.

/*** SIGNALLING LINK BLOCKING FAILED ***/

The signalling link blocking failed. The connection to the signalling linkterminal may be faulty. Check the alarms.

/*** SIGNALLING LINK DEBLOCKING FAILED ***/

The signalling link deblocking failed. The connection to the signalling linkterminal may be faulty. Check the alarms.

/*** SIGNALLING LINK DOES NOT EXIST ***/

The signalling link does not exist.

/*** SIGNALLING LINK INACTIVATION FAILED ***/

The signalling link inactivation failed. The connection to the signalling linkterminal may be faulty. Check the alarms.

/*** SIGNALLING LINK INHIBITING FAILED ***/

The signalling link inhibiting failed.

/*** SIGNALLING LINK INHIBITING LOCALLY DENIED ***/

DN02143262Issue 16-1 en30/01/2009



The signalling link inhibiting is locally denied. The inhibiting would makeone of the signalling points to be out of reach. Therefore, the signalling linkinhibiting is denied.

/*** SIGNALLING LINK INHIBITING REMOTELY DENIED ***/

The remote end denied the signalling link inhibiting. The inhibiting wouldmake one of the signalling points to be out of reach of the remote end.Therefore, the remote end denies the signalling link inhibiting.

/*** SIGNALLING LINK IS CONNECTED TO SIGNALLING LINK SET ***/

The deletion of the signalling link is denied, because the signalling link isconnected to the signalling link set.

/*** SIGNALLING LINK IS NOT CONNECTED TO SIGNALLING LINK SET ***/

The modification of the signalling link state is denied, because thesignalling link is not connected to the signalling link set.

/*** SIGNALLING LINK NOT ACTIVATED ***/

The signalling link activation failed.

/*** SIGNALLING LINK NOT INACTIVATED BY USER ***/

To deny the signalling link activation, the signalling link must be in UA-INUstate. Use the NLC command to set the UA-INU state.

/*** SIGNALLING LINK NOT IN SIGNALLING LINK SET ***/

The signalling link has not been connected to the signalling link set.

/*** SIGNALLING LINK SET ALREADY EXISTS ***/

The signalling link set exists already.

/*** SIGNALLING LINK SET DOES NOT EXIST ***/

The signalling link set does not exist.

/*** SIGNALLING LINK SET FILE FULL ***/

The signalling link set file is full. The creation of a signalling link set isdenied. The exchange needs a new file set.

/*** SIGNALLING LINK SET IS CONNECTED TO SIGNALLING ROUTE SET ***/


30/01/2009


The deletion of the signalling link set is denied, because the signalling linkset is connected to the signalling route set.

/*** SIGNALLING LINK SET IS NOT CONNECTED TO SIGNALLING ROUTE SET ***/

Modifying the signalling link state is denied, because the signalling link setis not connected to the signalling route set.

/*** SIGNALLING LINK SET NAME ALREADY RESERVED ***/

The signalling link set name is already reserved.

/*** SIGNALLING LINK STARTING FAILED ***/

The signalling link starting failed. The data link connection or the remoteend may be faulty.

/*** SIGNALLING LINK STATE CHANGE BUSY ***/

The signalling link state is being changed.

/*** SIGNALLING LINK UNINHIBITING FAILED ***/

The signalling link uninhibiting failed.

/*** SIGNALLING LINK UNINHIBITING IMPOSSIBLE ***/

The signalling link uninhibiting is impossible, because there is noconnection to the remote end.

/*** SIGNALLING NETWORK DOES NOT EXIST ***/

The signalling network does not exist.

/*** SIGNALLING POINT ALREADY BELONGS TO PERIODIC MRVT ***/

The signalling point already belongs to the MTP routing verification test.

/*** SIGNALLING POINT ALREADY EXISTS ***/

The signalling point already exists.

/*** SIGNALLING POINT CODE ALREADY EXISTS ***/

The signalling point code already exists.

/*** SIGNALLING POINT DOES NOT BELONG TO PERIODIC MRVT ***/

DN02143262Issue 16-1 en30/01/2009



The signalling point does not belong to the MTP routing verification test.

/*** SIGNALLING POINT DOES NOT EXIST ***/

The signalling point does not exist.

/*** SIGNALLING POINT IS USED BY SCCP ***/

The signalling point which the user is trying to delete is used by thesignalling control connection part (SCCP).

/*** SIGNALLING POINT NAME ALREADY RESERVED ***/

The signalling point name is already reserved.

/*** SIGNALLING ROUTE ACTIVATION DENIED ***/

The signalling route activation is denied. Use the NVA command to enablethe route activation.

/*** SIGNALLING ROUTE ACTIVATION FAILED ***/

The signalling route activation failed. Check with the NRI command if thesignalling route set of the route is in AV state.

/*** SIGNALLING ROUTE ACTIVATION NOT DENIED ***/

The signalling route activation is not denied. Set the route in UA-AD statewith the NVD command.

/*** SIGNALLING ROUTE ALREADY EXISTS ***/

The signalling route already exists in the signalling route set. Check withthe NRI command.

/*** SIGNALLING ROUTE DOES NOT EXIST ***/

The signalling route does not exist in the signalling route set.

/*** SIGNALLING ROUTE INACTIVATION FAILED ***/

The signalling route inactivation failed.

/*** SIGNALLING ROUTE SET ALREADY EXISTS ***/

The signalling route set already exists. Check with the NRI command.


30/01/2009


/*** SIGNALLING ROUTE SET DOES NOT EXIST ***/

The signalling route set does not exist. Check with the NRI command.

/*** SIGNALLING ROUTE SET FILE FULL ***/

The Signalling Route Set File (ROSETF) is full, i.e. the maximum numberof signalling route sets have been created in the exchange. The exchangeneeds a new file set.

/*** SIGNALLING ROUTE SET STATE NOT AVAILABLE ***/

The signalling route set state is not available. Therefore, the load sharingof the signalling route links is denied. Check the signalling route set statewith the NRI command.

/*** SIGNALLING ROUTE STATE CHANGE BUSY ***/

The signalling route state is being changed in the central memory.

/*** SIGNALLING ROUTE STATE IS NOT UA-INU ***/

The signalling route is not in UA-INU state. Change the state with the NVCcommand.

/*** SIGNALLING ROUTE TO ADJACENT SP ALREADY EXISTS ***/

There is already a direct signalling route to the adjacent signalling point.Check with the NRI command.

/*** SIGNALLING ROUTES AND ROUTE SET STATES INQUIRY FROM CCM BUSY ***/

The signalling routes and route set states are being inquired from theCCM.

/*** SIGNALLING TERMINAL NOT INITIALIZED ***/

The signalling terminal has not been initialized. There is a lack ofterminals.

/*** SIGNALLING TERMINAL UNIT DOES NOT EXIST ***/

The signalling terminal unit (CCSU, BCSU or equivalent) does not exist.

/*** SIGNALLING TRANSFER POINT DOES NOT EXIST ***/

DN02143262Issue 16-1 en30/01/2009



The signalling transfer point does not exist or no signalling link set hasbeen created to it. Check the signalling point and the signalling link set withthe NSI command.

/*** SIGNALLING TRANSFER POINT POLICING DEFINED TO SIGNALLING POINT ***/

An STP policing has been defined for the signalling transfer point.

/*** SIGNALLING UNIT SWITCHOVER IS REQUIRED AND LINK NOT IN LINK SET ***/

Signalling unit switchover is required and signalling link is not connected tothe signalling link set before the signalling link can be activated.

/*** SIGNALLING UNIT SWITCHOVER IS REQUIRED BEFORE LINK CAN BE ACTIVATED ***/

Initialize the signalling terminal unit by signalling unit switchover or restartthe unit.

/*** SIO ALREADY CONNECTED TO MATRIX MEASUREMENT ***/

The service information octet is already connected to the MTP statisticsmatrix measurement.

/*** SIO DOES NOT CONNECT TO MATRIX MEASUREMENT ***/

The service information octet is not connected to the MTP statistics matrixmeasurement.

/*** SLC RESERVED FOR OTHER SIGNALLING LINK ***/

The signalling link code has been reserved for another signalling link in thesignalling link set. Check with the NSI command.

/*** SLINKF FILE ACCESSING ERROR ***/

An attempt to access files outside the Signalling Link File (SLINKF).

/*** SLNPAR FILE ACCESSING ERROR ***/

An attempt to access files outside the Signalling Link Parameter File(SLNPAR).

/*** SLN PARAMETER SET ALREADY EXISTS ***/

The user is trying to create an SLN parameter set which already exists.The NOI command shows the existing parameter sets.


30/01/2009


/*** SLN PARAMETER SET DOES NOT EXIST ***/

The SLN parameter set does not exist. Check the identifiers of theparameter set. The NOI command shows the existing SLN parameter sets.

/*** SLN PARAMETER SET IS IN USE ***/

The SLN parameter set is in use. The NCI command shows the links usingthe parameter set.

/*** SOURCE PARAMETER SET DOES NOT EXIST ***/

The source parameter set does not exist. Check the identifiers of theparameter set.

/*** SOURCE PARAMETER SET IS NOT USED ***/

The source parameter set is not used by any signalling point.

/*** SOURCE SLN SET DOES NOT EXIST ***/

The source SLN parameter set does not exist. Check the identifiers of theparameter set with the NOI command.

/*** SP IS USED AS OWN ADDITIONAL SP ***/

The signalling point is used as own additional signalling point which issaved in the CCITT7 Level 3 Parameter File (L3PARA). Check with theNMI command.

/*** SP IS USED AS SIGNALLING TRANSFER POINT IN OTHER

SIGNALLING ROUTE SET***/

The signalling point which the direct signalling route to be deleted isconnected to is used as a signalling transfer point in another signallingroute set.

/*** STATE CHANGE IS IMPOSSIBLE ***/

The state change is impossible. Check the route state with the NVIcommand.

/*** THE HANDLING OF THE LINK IN THE JAPANESE NETWORK IS DENIED ***/

It is not possible to block the signalling link in the Japanese SS7 network(specification of NTT and TTC).

/*** TIME LIMIT EXCEEDED ***/

DN02143262Issue 16-1 en30/01/2009



The message set by CCADMI was not answered before the time-out.

/*** UNKNOWN SERVICE ***/

The service indicator is unknown.


30/01/2009


10 SS7 signalling network parameters

10.1 SS7 signalling network parameters

With the signalling parameters it is possible to control and modify certainfunctions of the signalling network. The signalling parameters are dividedin six different levels depending on which part of the signalling system theyaffect.

MTP level parameters

. MTP level 3 parameters

. CCS7 signalling network specific parameters

. signalling link specific parameters

. signalling route set specific parameters

SCCP and TC level parameters

. SCCP signalling point parameters

. SCCP subsystem parameters

Table 5. Parameter levels, affected parts and the MML command to handlethem

Parameter level Affected parts MML commands

MTP level 3 parameters message transfer part(MTP) of the networkelement

NMI, NMM

signalling networkparameters

signalling network (NA0,NA1, IN0 or IN1) i.e. allfour signalling networkshave own networkparameters

NMO, NMC

DN02143262Issue 16-1 en30/01/2009


SS7 signalling network parameters

Table 5. Parameter levels, affected parts and the MML command to handlethem (cont.)

Parameter level Affected parts MML commands

signalling link parameters signalling links command group NO

signalling route setparameters

signalling route set command group NN

SCCP signalling pointparameters

SCCP signalling point OC, NFL, NFN

SCCP subsystemparameters

SCCP subsystems OC, NFM, NFO

For some levels it is possible to define number of special parameter sets.The parameter sets can be connected so that different parts of thesignalling system use different parameter sets. That way it is possible touse different kinds of signalling in different directions.

For example, there can be two different signalling link parameter setsdefined and one is connected to signalling links leading to networkelement X and another is connected to signalling links leading to networkelement Y. In this case the signalling functions are different towards thenetwork element X than it is towards the network element Y.

There are few parameter sets predefined for a different kind of SS7signalling standards (e.g. ITU-T, ANSI, JAPAN). It is recommended to usethese parameter sets or at least to start with them. If there is a need tochange them it is reasonable to create a new one on the basis of thepredefined one.

The following table lists the signalling levels and the predefined parametersets within the level. Note that there can be also some country specificparameter sets predefined or some of the below listed sets can be left outdepending on the used software release.

Table 6. Signalling levels and their predefined parameter sets

Signalling level Predefined parameter sets

MTP level 3parameters

All parameters have a default value.

Signalling networkparameters

These parameters can be separately defined for eachsignalling network (IN0, IN1, NA0 and NA1). All parametershave a default value.


30/01/2009


Table 6. Signalling levels and their predefined parameter sets (cont.)


Signalling linkparameters

The following parameter sets are predefined:

ITU-T for signalling parameters defined by ITU (InternationalTelecommunications Union) in Q.703 and Q.704.

BTNR 146 for signalling parameters defined by BTNR (BritishTelecommunications Network Requirement).

ANSI T111 for signalling parameters defined by ANSI(American National Standards Institute) in T1.111 and T1.114.

JAPAN TTC for signalling parameters defined by TTC(Telecommunication Technology Committee) in JT.Q703 andJT.Q704.

JAPAN NTT for signalling parameters defined by NTT (NipponTelegraph and Telecommunication Corporation) in JT.Q703and JT.Q704.

ITU-T 2.0M for large capacity signalling links defined by ITU(International Telecommunications Union).

ITU-T 1.5M for large capacity signalling links defined by ITU(International Telecommunications Union).

IETF M3UA for IP type signalling links defined by IETF(Internet Engineering Task Force).

Signalling route setparameters


ITU-T for signalling parameters defined by ITU (InternationalTelecommunications Union) in Q.703 and Q.704.

A INTERFACE for A interface e.g. between MSC and BSC orATM Module and MSC.

BTNR 146 for signalling parameters defined by BTNR (BritishTelecommunications Network Requirement).

ANSI T111 for signalling parameters defined by ANSI(American National Standards Institute) in T1.111 and T1.114.

JAPAN TTC for signalling parameters defined by TTC(Telecommunication Technology Committee) in JT.Q703 andJT.Q704.

JAPAN NTT for signalling parameters defined by NTT (NipponTelegraph and Telecommunication Corporation) in JT.Q703and JT.Q704.

IETF M3UA for routes using IP type signalling links defined byIETF (Internet Engineering Task Force).

DN02143262Issue 16-1 en30/01/2009



Table 6. Signalling levels and their predefined parameter sets (cont.)


SCCP signalling pointparameters


BLUE for signalling parameters defined by ITU (InternationalTelecommunications Union) in Q.700 - Q.716, Blue Book.

A-INT for A interface e.g. between MSC and BSC or ATMModule and MSC.

WHITE for signalling parameters defined by ITU (InternationalTelecommunications Union) in Q.700 - Q.716 3/93, WhiteBook.

SCCP subsystemparameters


GENER for general use in other than with A interface.

A-INT for A interface e.g. between MSC and BSC or ATMModule and MSC.

10.2 MTP level 3 parameters

The level 3 parameters define the functions of the whole MTP. Some of theparameter values are related to monitoring the functions, while othersdefine various limits.

For instructions, see Modifying MTP level 3 signalling parameters.

The parameters are divided into six groups (A-F):

. A SS7 general parameters

. B Parameters for managing overload

. C Timing parameters of own signalling point

. D Parameters for testing / SIO parameters

. E Internal routing parameters

. F Parameters for SS7 statistics

The following table lists the parameter groups, parameters and theirindexes, parameter names and their meanings, the possible values ofeach parameter and the value range, as well as the recommended value, ifthat exists.


30/01/2009


Table 7. MTP level 3 parameters

Parametergroup

Parametergroup andnumber

Parameter name

Parameter explanation

Value range (quality ofvalue)

Recommended value

A SS7 COMMON PARAMETERS

A0-A9 DISTRIB_MTP_UNIT_TYPE_0 - 9

Defines those unit types on an exchange whereyou can create signalling links. Note: Usually, theparameter values need not be changed in theMSC, HLR, BSC or fixed network exchanges,because unit types CCSU, BCSU and BSU havebeen prebuilt. In the PMR, units CM and CCChave been prebuilt.

B OVERLOAD CONTROL PARAMETERS

B0 MAX_NB_OF_NOTICES 1...30

10

The largest amount of incoming messagesallowed to enter a centralized unit during amessage monitoring period (100 ms). Purpose ofthe parameter is to control overload within theexchange. The parameter value should not bechanged.

C TIMER PARAMETERS FOR OWN SIGNALLINGPOINT

C0 LINK_TEST_PERIOD 1500...45000 (10 ms)

The sending period for signalling link testmessages. The period applies to a group of 10signalling links. This means that when anexchange has 30 links, the test message goes toeach link in every third sending period.

4000 (40 sec.)

C1 Q704_T18_LINK_AVAIL_WAIT 1000...6000 (10 ms)

The time used controlling the availability of thelinks when a signalling transfer point is restarted.The value depends on the implementation andon the network.

2000

C2 Q704_T19_TRA_WAIT 200...1000 (10 ms)

The timer controlling the reception of all TRAmessages while the signalling transfer point isbeing restarted, when the restarting is made asdefined in the CCITT Blue Book. The timer isdefined by parameter P7 when the systemfollows the White Book.

400

DN02143262Issue 16-1 en30/01/2009



Table 7. MTP level 3 parameters (cont.)

Parametergroup


Parameter name



Recommended value

C3 Q704_T20_TRAF_RESTARTING_TIME 200...6100 (10 ms)

The timer controlling the sending of all TRAmessages when the signalling transfer point isbeing restarted.

400

C4 T111_T26 1000...2000 (10 ms)

Defines the timer for resending of TRWmessages when the signalling transfer point isbeing restarted, the timer is defined in the ANSIstandards.

1500

C5 Q714_T_GUARD 600...15000 (100 ms)

Defines the monitoring time used for thesignalling connections when the signallingtransfer point is being restarted.

6000

C6 T111_T27 200...500 (10 ms)

300

After commensing the restart procedure of asignalling point, all the signalling links of theexchange keep sending the processor outagestate indicator to the partner exchanges for agiven time (defined in this parameter), in order tomake sure that all adjacent signalling pointsrecognise that this point cannot be reached anymore.

D PARAMETERS FOR TESTING

D0 L2_TEST_MSG_SIO 0 ...FF

The service information octet used by the CCSSystem Test Message Generator (MSGGEN)reads the data only when it starts up. Afterchanging the parameter values, the MSGGENhas to be restarted before new values can beincluded in the contents of the test messages

8F (NA0 network user part F)

D1 TEST_MSG_LENGTH 0...272


30/01/2009



Parametergroup


Parameter name



Recommended value

The length of the SIF part in the MSGGENmessages of the CCS System Test MessageGenerator. This parameter effects only thosemessages whose length can be modified. Valuefor this parameter can be changed while theMSGGEN is running, and the MSGGEN needsnot be restarted.

smaller than 272

E INTERNAL ROUTING PARAMETERS

E0 INT_ST7_ROUTE

246

Defines the number of the internal route whichincludes the PCM time slots used by thesignalling link terminals between the unit and theswitching network.

E1 EXT_ST7_ROUTE

247

Defines the number of the external route whichincludes the external PCM timeslots used by thesignalling link terminals.

E2 INT_ST7_ROUTE_NAME

Defines the name of the internal route whichincludes the PCM timeslots used by thesignalling link terminals between the unit and theswitching network.

E3 EXT_ST7_ROUTE_NAME

Defines the name of the external route whichincludes the external PCM timeslots used by thesignalling link terminals.

E4 INTERNAL_ROUTING_FOR_SL

Defines whether the system tries to update thesignalling link related PCM/TSL data into therouting data of the CM3PRO. Used only on testexchanges that have no group switch (GSW).

F SS7 STATISTICS PARAMETERS

F0 SUCC_UNIT_COLL_COUNT_5 2...10

DN02143262Issue 16-1 en30/01/2009




Parametergroup


Parameter name



Recommended value

Defines the amount of MTP decentralized unitsfrom which the statistics counters are collected ata time during a 5 minute monitoring period.

4

F1 SUCC_UNIT_COLL_COUNT_30 2...20

Defines the amount of MTP decentralized unitsfrom which the statistics counters are collectedone by one during a 30 minute monitoring period.

10

F2 SL_LOG_TYPE NORMAL,CYCLIC

Type of the signalling link event log can be eitherNORMAL or CYCLIC. The buffer can be emptiedwith the OLE command.

CYCLIC

F3 SP_LOG_TYPE NORMAL,CYCLIC

Type of the signalling point event log can beeither NORMAL or CYCLIC. The buffer can beemptied with the ONE command.

CYCLIC

F4 SL_LOG_MAX_COUNT 16...32

The maximum amount of changes in the state ofa signalling link that can be stored in the buffer.

F5 SP_LOG_MAX_COUNT 16...32

The maximum amount of changes in the state ofa signalling point that can be stored in the buffer.

F6 USER_NOTICE_ACT ACTIVE, PASSIVE

Controls the notices that the statistics output forthe user.

F7 SCCP_LOG_TYPE NORMAL, CYCLIC

Type of the SCCP event log buffer. The buffercan be emptied with the OTE command.

F8 TC_LOG_TYPE NORMAL, CYCLIC

Type of the TC event log buffer. The buffer canbe emptied with the OTE command.


30/01/2009


10.3 SS7 signalling network specific parameters

These parameters apply to the whole signalling network.

For instructions, see Modifying SS7 signalling network parameters.

Table 8. SS7 signalling network -specific parameters

Parametergroup


Parameter name


Value range (qualityof value)

Recommended value

J NETWORK SPECIFIC PARAMETERS

J0 CONGESTION_METHOD NO, INT, NAT, NATP

Three congestion methods exist: internationalmethod (INT), national method withoutprioritization of signalling messages (NAT) andnational method with prioritization of messages(NATP).

INT method: The congestion criteria is thefilling degree (1 limit) of the sending bufferwhose limit values are defined in the SignallingLink Parameter File (SLNPAR). Thecongestion level directly follows the occupancyof the buffer. Timers T29 and T30 are used tocontrol traffic restriction according to definitionsmade with parameters K0-K5.

NAT method: The congestion criteria is thefilling degree (1 limit) of the sending bufferwhose limit values are defined in the SignallingLink Parameter File (SLNPAR). Thecongestion level is determined by timers Txand Ty. The congestion level can have values1-3, and traffic is restricted as required by theprevailing congestion level and as defined inparameters L1-L3.

NATP method: The congestion criteria is theoccupancy (3 limits) of the sending bufferwhose limit values are defined in the SignallingLink Parameter File (SLNPAR). Thecongestion level determines how themessages are handled (for example, oncongestion level 3, only messages with priority3 or higher are routed forwards).

K INTERNATIONAL CONGESTION CONTROLMETHOD PARAMETERS

DN02143262Issue 16-1 en30/01/2009



Table 8. SS7 signalling network -specific parameters (cont.)

Parametergroup


Parameter name



Recommended value

K0 NB_OF_UP_LEVELS 1 ... 5

The amount of restriction levels for theoriginating traffic concerning internationalcongestion method.

K1 RESTRICT_PR_OF_UP_L1 0 ... 60 (%)

The restriction percentage for the originatingtraffic on restriction level 1. Timers T29 andT30 determine the restriction level. The defaultvalue is 40%


The restriction percentage for the originatingtraffic on restriction level 2. Timers T29 andT30 determine the restriction level. The defaultvalue is 60%


The restriction percentage for the originatingtraffic on restriction level 3. Timers T29 andT30 determine the restriction level. The defaultvalue is 70%.



K5 RESTRICT_PR_OF_UP_L5 80 ...100 (%)


K6 Q764_T29 30 ... 60 (0.01s)


30/01/2009



Parametergroup


Parameter name



Recommended value

When the first congestion indication isreceived by the ISDN User Part, the trafficload into the affected destination point code isreduced by one step. At the same time twotimers T29 and T30 are started. During T29 allreceived congestion indications for the samedestination point code are ignored in order notto reduce traffic too rapidly. Reception of acongestion indication after the expiry of T29,but still during T30, will decrease the trafficload by one more step and restart T29 andT30. This step-by-step reduction of the ISDNUser Part signalling traffic is continued untilmaximum reduction is obtained by arriving atthe last step. If T30 expires (i.e. no congestionindications are no more received during theT30 period) traffic will be increased step-by-step and T30 will be restarted unless full trafficload has been resumed.

K7 Q764_T30 500 ... 1000 (0.01s)

See K6. 600

L NATIONAL CONGESTION CONTROLMETHOD PARAMETERS

L0 PREDETERMINED_CONG_LEVEL 1 ... 3

Defines the default value for the congestionlevel that is reached when the bufferoccupancy limit is exceeded for the first time,or when the congestion level is coded as 0 ina received TFC message.

L1 RESTRICT_PR_OF_MTP_L1 0 ... 60 (%)

The restriction percentage for originating trafficon congestion level 1.

L2 RESTRICT_PR_OF_MTP_L2 30 ... 90 (%)


L3 RESTRICT_PR_OF_MTP_L3 60 ...100 (%)


L4 Q704_TX 5 ... 200 (0.01s)

DN02143262Issue 16-1 en30/01/2009




Parametergroup


Parameter name



Recommended value

The timer raising the congestion level whenthe filling limit of the transmit buffer has beenexceeded. The smaller the parameter value is,the quicker the congestion level is raised. (Ifthe signalling link congestion status is set to sand the buffer occupancy continues to beabove the set congestion threshold during Tx,the signalling link congestion status is updatedby the new value s + 1.)

20

L5 Q704_TY 5 ... 200 (0.01s)

The timer lowering the congestion level whencongestion has been on but then the fillingdegree of the sending buffer has decreasedand gone below the set limit. The smaller theTy is, the quicker the congestion leveldecreases. (If the signalling link congestionstatus is set to s and the buffer occupancycontinues to be below the abatement thresholdduring Ty, the signalling link congestion statusis updated by the new value s - 1.)

M SLS BITS

M0 LINK_SLS_BIT_MASK

Defines which SLS bits are used in loadsharing within the link set.

ITU: 11111111

ANSI: 11111110

JAPAN: 00001110

M1

ROUTE_SLS_BIT_MASK

Defines which SLS bits are used in loadsharing between the routes.

ITU: 11111111

ANSI: 00000001

JAPAN: 00000001

M2 SLS_LENGTH 4,5,8

Defines the length of SLS within the signallingnetwork. In ITU networks, the SLS is 4 bits,while in ANSI networks it is 5 or 8 bits.

ITU: 4

ANSI: 5 or 8

JAPAN: 4 (TTC) or 5(NTT)


30/01/2009



Parametergroup


Parameter name



Recommended value

M3 INTERNAL_SLS_LENGTH

Define the number of extra internal SLS bitsfor LSDTAB file referencing'

5, 6, 7, 8

5

M4 NEW_SLS_IN_SCCP0CLASS YES, NO

Indicates whether MTP reselects an SLS codefor STP messages whose senders (SCCPusers) do not care about SLS codes.

M5 LS_LICENCE_KEY_1

Licence key 1 for advanced load sharingprocidures.

M6 LS_LICENCE_KEY_2

Licence key 2 for advanced load sharingprocidures.

10.4 Signalling link parameters

The parameters in the signalling link -specific parameter set define howthe signalling links function.

For instructions, see Modifying the values of signalling link parameter set.

You can interrogate the values of the parameters of an existing signallinglink parameter set with the NOI command.

The parameters are divided into seven groups (A-G):

. A Miscellaneous parameters on MTP level 2

. B Control parameters for the error ratio on MTP level 2 (as definedby ITU)

. C Timer parameters for MTP level 2 (as defined by ITU)

. D Miscellaneous parameters on MTP level 3

DN02143262Issue 16-1 en30/01/2009



. E Signalling congestion control parameters

. F Timer parameters for MTP level 3.

. G ATM specific parameters (SAAL level)

The following table lists the parameter groups, parameters and theirindexes, parameter names and their meanings, all possible values, qualityof the value and the recommended value, if any.

Table 9. Signalling link parameters

Parametergroup


Parameter name


Value range(quality ofvalue)

Recommended value

A MISCELLANEOUS MTP LEVEL 2 PARAMETERS

A0 LI_CODING STANDARD,BTNR, JT_PRI

Controlling the LI coding.

BTNR is specific method in BTNR Spec. (UK).

STANDARD

A1 BIT_D_CODING_IN_LSSU STANDARD,BTNR

Controlling the D bit coding in the LSSUs

BTNR is specific method in BTNR Spec. (UK).

STANDARD

A2 BIT_D_CHECK_IN_LSSU YES, NO

Controlling the D bit checking in the received LSSUs (1HBit D checked from the received LSSU).

NO

A3 L2_ERROR_CORRECTION BASIC, PCR

Controlling the error rate monitoring in the transmissiondirection. PCR is for preventive cyclic retransmission forsatellite links. (See parameters B7, PCR_N1 and B8,PCR_N2.)

BASIC

A4 SN_RANGE 40 ... 4095

Maximum value for backward sequence number andforward sequence number of signalling unit.

A5 JT_Q703_K 40 ... 127

Defines the number of transmitted MSU messageswithout positive acknowledgement.

This parameter is relevant only in Japanese signallingnetwork.

JAPAN: 40


30/01/2009


Table 9. Signalling link parameters (cont.)

Parametergroup


Parameter name



Recommended value

B MTP LEVEL 2 ERROR RATE MONITORINGPARAMETERS

B0 SUERM_T 8 ... 512

Controlling the error rate of the message unit:SUERM_T, SUERM_D and SUERM_N (see CCITTQ703 10.2).

ITU: 64

ANSI: 64

JAPAN: 285

B1 SUERM_D 16 ... 1024


ITU: 256

ANSI: 256

JAPAN: 16

B2 SUERM_N 8 ... 24


16

B3 AERM_TIN 1 ... 16

Controlling the error rate of the alignment AERM_TIN,(see CCITT Q703 10.3).

4

B4 AERM_TIE 1 ... 8

Controlling the error rate of the alignment AERM_TIE(see CCITT Q703 10.3).

1

B5 AERM_M 1 ... 16

Controlling the error rate of the alignment AERM_M (seeCCITT Q703 10.3).

5

B6 AERM_N 8 ... 24

Controlling the error rate of the alignment AERM_N (seeCCITT Q703 10.3).

16

B7 PCR_N1 (preventive cyclic retransmission) 1 ... 127

DN02143262Issue 16-1 en30/01/2009




Parametergroup


Parameter name



Recommended value

PCR_N1, number of MSUs that can be resent. Theparameter is valid only if the parameter A3,L2_ERROR_CORRECTION has value PCR.

Parameter is normally used with satellite signalling links.Note that both link ends must support this method.

For more information, refer to the ITU-TRecommendation Q.703 (07/96) - Signalling link (chapter6).

127

B8 PCR_N2 300 ... 6000

PCR_N2, number of MSUs that can be resent. Theparameter is valid only if the parameter A3,L2_ERROR_CORRECTION has value PCR.

Parameter is normally used with satellite signalling links.Note that both link ends must support this method.

For more information, refer to the ITU-TRecommendation Q.703 (07/96) - Signalling link (chapter6).

800

B9 EIM_TE 8 ... 793544

Errored interval monitor parameter (see ITU-T Q703A.10.2)

B10 EIM_UE 1 ... 198384


B11 EIM_DE 1 ... 11328


B12 JT_Q703_TE 20 ... 30 (1 ms)

Defines the normalized time for error rate monitoring.


JAPAN: 24

C MTP LEVEL 2 TIMER PARAMETERS

C0 Q703_T1 130 ... 3500(0.1s)


30/01/2009



Parametergroup


Parameter name



Recommended value

Q703_T1, Alignment Completed timer ITU: 400

ANSI: 130

JAPAN: 150

C1 Q703_T2 50 ... 1500(0.1s)

Q703_T2, No Alignment timer ITU: 100

ANSI: 115

JAPAN: 500

C2 Q703_T3 10 ... 116 (0.1s)

Q703_T3, Alignment timer ITU: 10

ANSI: 115

JAPAN: 30

C3 Q703_T4 23 ... 700 (0.1s)

Q703_T4, Length of Test Period timer ITU: 82

ANSI: 23

JAPAN: 30

C4 Q703_T5 8 ... 30 (0.01s)

Q703_T5, SIB Transmission timer ITU: 10

ANSI: 10

JAPAN: 20

C5 Q703_T6 30 ... 72 (0.1s)

Q703_T6, Remote End Congestion timer ITU: 50

ANSI: 60

JAPAN: 30 forSEP, 50 forSTP

C6 Q703_T7 5 ... 20 (0.1s)

Q703_T7, Delayed Acknowledgement timer ITU: 10

ANSI: 15

JAPAN: 20

C7 Q703_T8 8 ... 12 (0.01 s)

DN02143262Issue 16-1 en30/01/2009




Parametergroup


Parameter name



Recommended value

Errored interval monitor timer

C8 JT_Q703_TF 20 ... 30 (1 ms)

Defines interval for sending FISU when there is noMSUs transmitted.


JAPAN: 24

C9 JT_Q703_TO 20 ... 30 (1 ms)

Defines interval for transmitting SIO and SIE messagesused for initial set-up and during verification.


JAPAN: 24

C10 JT_Q703_TS 10 ... 30 (1 ms)

Defines interval of SIOS to be transmitted duringsuspension.


JAPAN: 24

D MISCELLANEOUS MTP LEVEL 3 PARAMETERS

D0 PERIODIC_LINK_TEST_DENIED YES, NO

Controlling the transmission of signalling link testmessages.

NO

D1 MAX_LENGTH_OF_SIF 62, 272

Maximum length of the SIF field in the MSU message. 272

D2 INHIBIT_ATTEMPT_LIMIT 1 ... 5

Limit for repeated attempts to inhibit a link. 3

D3 INHIBIT_TEST_DENIED YES, NO

Controlling the inhibition of a test procedure. NO

D4 ECO_SENDING_ALLOWED YES, NO

Defines the control of Emergency Changeoverprocedure.

ITU-T: YES

ANSI: YES

JAPAN: NO(NTT), YES(TTC)

D5 INHIBITION_DENIED YES, NO


30/01/2009



Parametergroup


Parameter name



Recommended value

Defines the control of link inhibition procedure.

D6 SIN_DENIED YES, NO

Defines the control of link alignment procedure.

D7 SIPO_DENIED YES, NO

Defines the control of local processor outage procedure.

D8 LINK_SUSPEND_DENIED YES, NO

Defines the control of link oscillation preventionprocedure.

D9 FALSE_CONG_DENIED YES, NO

Defines the control of false link congestion detectionprocedure.

D10 LINK_SRT_DENIED YES, NO

Defines the control of signal routing test procedure.

E SIGNALLING CONGESTION CONTROL PARAMETERS

E0 CONG_FILTERING_TIME 0 ... 100 (0.01s)

Defines the time after which continuing congestion on asignalling link is reported to level 3. This feature keepsthe signalling traffic control procedures from startingduring very short-time peak loads.

1

E1 BUFF_FILTERING_TIME 0 ... 300 (0.01s)

Defines the time after which continuing congestion on asignalling link is reported to level 3 while signallingmessage buffering is active. This feature keeps thesignalling traffic control procedures from starting inspecial situations such as changeovers, changebacksand controlled reroutings.

1

E2 CONG_ONSET_THRESHOLD1 2 ... 1000, NOTIN USE

DN02143262Issue 16-1 en30/01/2009




Parametergroup


Parameter name



Recommended value

Defines the occupancy of the transmit buffer which isinterpreted as level 1 congestion on the signalling link.For SAAL based signalling links, this means theoccupacy of both the delay buffer and the transmissionbuffer, as the size of the occupied area is divided by thetotal size of the transmission buffer and the resultingpercentage is compared to theCONG_ONSET_THRESHOLD1 value. For those links,values greater than 200 behave as the value NOT INUSE.

Normally, only values between 0 and 100 are used.Values between 100 and 200 are not recommended forsubscriber traffic, since they can be reached onlymomentarily during buffering procedures.

49 Limit forcongestiononset(messages)

E3 CONG_ABATE_THRESHOLD1 1 ... 800, NOTIN USE

Reports the occupancy of the transmission buffer that isinterpreted as ending for level 1 congestion (that hasbeen on). It is advisable to set the release level ofcongestion clearly lower than the activation level toavoid vibrations.

2 Limit forcongestionreset(messages)

E4 CONG_DISC_THRESHOLD1 10 ... 2500,NOT IN USE

Reports the occupancy of the transmission buffer thatmakes the signalling terminal software to set thesignalling message destroying status on in thetransmission mail box. When the CCSEND programblock notices that the destroying status is set to "on", itdestroys signalling messages addressed to thementioned signalling terminal. The threshold values forthe destroying status are selected from range 0-127; ifthe value is 128-255, the status is never set on.However, when the transmission buffer fills up, signallingmessages have to be destroyed. The status value musttherefore be higher than the limit for signalling linkcongestion in order to avoid unnecessary destroying ofmessages.

The range 0-127 is a percentage. It is valid for SAALbased signalling links. All the values 100-127 behavethe same with SAAL based signalling links (100%).

NOT IN USELimit formessagediscarding(messages)



30/01/2009



Parametergroup


Parameter name



Recommended value

CONG_ONSET_THRESHOLD2,CONG_ABATE_THRESHOLD2,CONG_DISC_THRESHOLD2,CONG_ONSET_THRESHOLD3,CONG_ABATE_THRESHOLD3 andCONG_DISC_THRESHOLD3 are similar to the abovementioned parameters when the used congestion controlmethod has several levels. The parameter values onlevel 2 must be higher than the corresponding values onlevel 1. Similarly, the values on level 3 must be higherthan those on level 2. This is necessary in order to getthe congestion method work properly with several levels.When the congestion method uses only one level, setthe parameter values on levels 2 and 3 as 255 = 0FFH.See parameters E2, E3 and E4.

NOT IN USE


See parameters E5 and E3. NOT IN USE

E7 CONG_DISC_THRESHOLD2 10 ... 2500,NOT IN USE






E10 ONG_DISC_THRESHOLD3 10 ... 2500,NOT IN USE


E11 T111_T31_ONSET_THRESHOLD 0,1, 2, 3, INUSE

Congestion threshold for starting timer T111_T31. IN USE

E12 T111_T31_RESET_THRESHOLD 0,1, 2, 3, INUSE

Congestion threshold for reseting timer T111_T31. IN USE

E13 SL_LOAD_THRESHOLD 100 ... 900

DN02143262Issue 16-1 en30/01/2009




Parametergroup


Parameter name



Recommended value

Allows maximum value for signalling link load inMerlangs without notification.

F MTP LEVEL 3 TIMING PARAMETERS

F0 Q704_T1 5 ... 12 (0.1s)

Delay to avoid message mis-sequencing on changeover. ITU: 8

ANSI: 8

JAPAN: 10

F1 Q704_T2 7 ... 20 (0.1s)

Waiting for changeover acknowledgement. ITU: 14

ANSI: 14

JAPAN: 10

F2 Q704_T3 5 ... 12 (0.1s)

Time controlled diversion-delay to avoid mis-sequencingon changeback.

ITU: 8

ANSI: 8

JAPAN: 10

F3 Q704_T4 5 ... 12 (0.1s)

Waiting for changeback acknowledgement (first attempt). ITU: 8

ANSI: 8

JAPAN: 10

F4 Q704_T5 5 ... 12 (0.1s)

Waiting for changeback acknowledgement (secondattempt).

8

F5 Q704_T12 8 ... 15 (0.1s)

Waiting for uninhibition acknowledgement. 10

F6 Q704_T13 6 ... 15 (0.1s)

Waiting for force uninhibit. 10

F7 Q704_T14 8 ... 30 (0.1s)

Waiting for inhibition acknowledgement. 20

F8 Q704_T17 8 ... 60 (0.1s)

Delay to avoid oscillation of initial alignment failure andlink restart.

10


30/01/2009



Parametergroup


Parameter name



Recommended value

F9 Q704_T22 180 ... 600 (1s)

Local inhibit test timer. 180

F10 Q704_T23 180 ... 600 (1s)

Remote inhibit test timer. 180

F11 Q707_T1 8 ... 120 (0.1s)

Waiting for signalling link test messageacknowledgement.

80

F12 T111_T19 120 ... 600 (1s)

Time supervision for setting an alarm about a signallinglink that refuses to start up, as defined in ANSIstandards.

120

F13 T111_T20 90 ... 120 (1s)

Control for local inhibition testing as defined in ANSIstandards.

120

F14 T111_T21 90 ... 120 (1s)

Control for remote end inhibition testing as defined inANSI standards.

120

F15 T111_T31 10 ... 120 (1s)

False link congestion detection timer. ITU: 10

ANSI: 30

F16 T111_T32 5 ... 120 (1s)

Link oscillation timer - Procedure A 5

F17 JT_Q704_TS 5 ...150 (1 s)

Defines the time for transmitting SIOS on a periodicalbasis during suspension.


JAPAN: 30

F18 JT_Q707_T10 20...150 (0.1 s)

Waiting time for signal routing test confirmation 100

F19 ALIGN_RESP_WAIT 10...7000 (0.1s)

Supervision time for inherently short alignment phases 40

DN02143262Issue 16-1 en30/01/2009




Parametergroup


Parameter name



Recommended value

G ATM SPECIFIC PARAMETERS (SAAL LEVEL)

G0 Q2140_T1 2 ... 60 (1 s)

Time between the link release action and the next linkre-establish action during the alignment.

5

G1 Q2140_T2 10 ... 120 (1 s)

Maximum time SSCF-NNI will attempt alignment. 30

G2 Q2140_PROVING_LOAD 10 ... 90 (%)

The load percent of the signalling link during alignment.SSCF—NNI n1 and T3 are derived from this parameter.

T3 = 1 / (PCR * G2 / 100)

n1 = 10000000 / T3 (T3 value is given in

microsecond)

50

G3 Q2110_MAXCC 2 ... 20

Maximum count which SSCOP tries connectionestablishment, release, resynchronization and rocovery.

4

G4 Q2110_MAXPD 50 ... 1000

Maximum count of SD PDUs before SSCOP sends apoll.

500

G5 Q2110_TIMER_CC 50 ... 1000(1ms)

TIMER_CC ensures successfull SSCOP connectionmanagement actions. Maximum time which SSCOPwaits for acknowledgement for connectionestablishment, release, resynchronization and recoveryPDUs.

200

G6 Q2110_TIMER_KEEP_ALIVE 100 (1 ms)

Timer to ensure that the peer SSCOP is still working in atransient phase when there are no SD PDUs to betransferred.

100

G7 Q2110_TIMER_NO_RESP 100 ... 3000 (1ms)

Timer to recognize that the SSCOP connection isavailable. Maximum time SSCOP waits for STAT PDU.

1500

G8 Q2110_TIMER_POLL 10 ... 100 (1ms)


30/01/2009



Parametergroup


Parameter name



Recommended value

TIMER_POLL is running to assure that the peer SSCOPreceiver is polled often enough.

100

G9 Q2110_TIMER_IDLE 100 ... 3000 (1ms)

TIMER_IDLE defines the time for SSCOP idle phase. Atthe expiry of TIMER_IDLE, SSCOP enters the transientphase again.

100

G10 Q2110_MAXSTAT 10 ... 200

Maximum number of list elements placed in a SSCOPSTAT PDU.

67

G11 Q2144_MAXNRP 0 ... 100

Maximum permissible SSCOP retransmissions during aproving attempt.

0

G12 Q2144_TIMER_REPEAT_SREC 10 ... 300 (1min)

TIMER_REPEAT_SREC is used to recognize closelyspaced SSCOP connection recoveries. Minimum timebetween SSCOP connection recoveries.

60

G13 Q2144_TIMER_NO_CREDIT 100 ... 5000 (1ms)

TIMER_NO_CREDIT supervices the unavailability ofSSCOP credit. Maximum time LM allowes SSCOP to bewithout credit.

1500

10.5 Signalling route set parameters

The parameters included in the parameter set of the signalling route setare used to handle the functions of the whole Message Transfer Part(MTP).

For instructions, see Modifying the values of signalling route set parameterset.

DN02143262Issue 16-1 en30/01/2009



You can interrogate the values of the parameters of an existing signallingroute set parameter set with the NNI command.

The parameters are divided into four groups (A-D):

. A Common timers of all destinations

. B Signalling point restart timers

. C Adjacent signalling point parameters

. D Common parameters of all signalling points.

The following table lists the signalling route set parameters, their names,all possible values, quality of the given value and the recommended value,if any.

Table 10. Signalling route set parameters (* The parameters are significantonly to the local signalling points.)

Parametergroup


Parameter name

Parameter name

Value range(quality of value)

Recommendedvalue

A COMMON TIMERS OF ALLDESTINATIONS

A0 Q704_T6 5 ... 20 (0.1s)

Delay to avoid message mis-sequencing on controlled rerouting. Theparameter sets the time that is waitedduring controlled rerouting before trafficis activated to the destination point viaa new or alternative transfer point.

ITU: 8

ANSI: 8

JAPAN: 10

A1 Q704_T8 5 ... 20 (0.1s)

Time supervision for inhibition of theTransfer Prohibited messages. TheTransfer Prohibited messagesgenerated by the reply system are notsent to the destination point, if other -similar - messages have been sentthere during the time specified by theparameter.

10

A2 Q704_T10 10 ... 120 (1s)


30/01/2009


Table 10. Signalling route set parameters (* The parameters are significantonly to the local signalling points.) (cont.)

Parametergroup


Parameter name

Parameter name


Recommendedvalue

Time supervision for repetition of testmessages in the signalling route set.Test messages related to anothersignalling point are sent at intervalsdefined by the time parameter.

ITU: 31

ANSI: 31

JAPAN: 30

A3 Q704_T11 30 ... 90 (1s)

Transfer Restricted time supervision.This parameter sets the time for howlong a signalling link set, that usesanother signalling point as the transferpoint, has to be faulty before it is set instate 'long-term failure'. When this stateis set for a signalling link set, TransferRestricted messages are sent to theadjoining signalling points. Themessages concern all route sets whereone of the primary routes has beenusing the failed link set and where thetraffic is now directed to secondaryroutes.

60

A4 Q704_T15 20 ... 30 (0.1s)

If within T15, after the reception of thelast Transfer Controlled messagerelated to destination X, signalling pointZ receives another Transfer Controlledmessage related to the samedestination, the following action istaken: If the value of the congestionstatus carried in the new TransferControlled message is higher than thecurrent value of the congestion statusof the signalling route set towardsdestination X, then the current value isupdated to the higher one. If T15expires after the last update of thesignalling route set towards destinationX in a Transfer Controlled messagerelated to the same destination, thesignalling-route-set-congestion-testprocedure is invoked.

25

A5 Q704_T16

JT_Q704_TC

14 ... 25 (0.1s)

26 ... 250 (0.1s)

DN02143262Issue 16-1 en30/01/2009




Parametergroup


Parameter name

Parameter name


Recommendedvalue

If within T16, after sending a signalling-route-set-congestion-test message, aTransfer Controlled message related tothe concerned destination, is received,the signalling point updates thecongestion status of the signalling routeset towards the concerned destinationwith the value of the congestion statuscarried in the Transfer Controlledmessage. If T16 expires after sending asignalling-route-set-congestion-testmessage without a Transfer Controlledmessage related to the concerneddestination having been received, thesignalling point changes the congestionstatus associated with the signallingroute set towards the concerneddestination to the next lower status.

ITU: 15 (for Q704_T16)

ANSI: 15 (forQ704_T16)

JAPAN: 200 (forJT_Q704_TC)

A6 T111_T18 2 ... 20 (1s)

A signalling point starts the MTP restartprocedure when its first link is in serviceat level 2. Restarting the MTP: - if it hasthe transfer function, it starts timer T18;

3

A7 JT_Q707_T10 20...150 (0.1s)

Waiting time for signal routing testconfirmation

100

B SIGNALLING POINT RESTARTTIMERS

B0 * Q704_T21

T111_T25

20 ... 70 (1s)


30/01/2009



Parametergroup


Parameter name

Parameter name


Recommendedvalue

Q704_T21: The waiting period beforetraffic is restarted via an adjacentsignalling point. Traffic on the routesusing the adjacent signalling point isstarted only when the time defined inthis parameter has past after the restartof the adjacent point (or when the pointhas sent the Traffic Restart Allowedmessage).

T111_T25: Waiting for the TrafficRestart Active message.

Blue Book 31

White Book 64

ANSI 64

B1 T111_T28 3 ... 35 (1s)

Signalling point X starts timer T28 eitherwhen the first signalling link goes intostate In Service on level 2, or when thefirst signalling link becomes availableon level 3.

This parameter is used only in networksbuilt according to the ANSI standards.

30

B2 Q704_T19_WHITE

T111_T29

60 ... 80 (1s)

Supervision timer during the MTPrestart to avoid possible ping-pong(back and forward) of TFP, TFR andTRA messages.

68

B3 * T111_T30 20 ... 40 (1s)

If the receiving point has the transferfunction, it starts timer T30, sends aTraffic Restart Waiting messagefollowed by the necessary TransferRestricted and Transfer Prohibitedmessages (preventive TransferProhibited messages are required fortraffic currently being routed via thepoint from which the unexpected TrafficRestart Allowed or Traffic RestartWaiting messages were received) and aTraffic Restart Allowed message.

ANSI: 30

C ADJACENT SIGNALLING POINTPARAMETERS

DN02143262Issue 16-1 en30/01/2009




Parametergroup


Parameter name

Parameter name


Recommendedvalue

C0 * TRM_DENIED YES, NO

Use of message pair TRA/TRW isdenied in network management. In anANSI network, the use of TRW inconnection with the SP restart isdenied.

ITU: NO

ANSI: NO

JAPAN: YES

C1 * TRM_EXPECTED YES, NO

This parameter controls the use ofmessage pair TRA/TRW:

TRA_EXPECTED means that trafficrestart is allowed - control for waiting ofmessage reception when the signallinglink set is taken into use.

TRA_WAITING controls the waiting ofmessage reception when the signallinglink set is taken into use.

TRA_DENIED means that sending ofTraffic Restart Allowed messages isdenied.

ITU: YES

ANSI: YES

JAPAN: NO

C2 * SP_RESTART_TYPE BLUE, NONE, WHITE,ANSI

Controlling the denial of the signallingpoint restart procedure. When use ofthe procedure is denied, the restartprocedure of the adjacent signallingpoint is not used. When the ownsignalling point is restarted, the TrafficRestart Allowed message is not sent tothe adjacent SP, either.

ITU: BLUE

ANSI: ANSI

JAPAN: NONE

C3 * INDIRECT_ROUTES_DEFAULT AVAILABLE,RESTRICTED,UNAVAILABLE, TFMBASED

Parameter for controlling the signallinglink set restarts in situations when theadjacent SP has not been started. Thepossible parameter values areavailable, restricted, unavailable andTFM based.

ITU: AVAILABLE

ANSI: AVAILABLE

JAPAN: AVAILABLE


30/01/2009



Parametergroup


Parameter name

Parameter name


Recommendedvalue

C4 * TFM_CONTROL ALL ALLOWED,BROADCASTDENIED, ALL DENIED

Control parameter for broadcastingmessages: Transfer Allowed, TransferRestricted and Transfer Denied. Whenthe parameter denies broadcasting ofmessages and an SP becomes eitheravailable or unavailable, it is notreported to the adjacent SP.

ALL ALLOWED

C5 * RESP_TFM_CONTROL TFR ALLOWED, TFPALLOWED, TFP FORKNOWN, TFMDENIED

Control parameter for the responsemethod messages. Possible parametervalues are TFR allowed, TFP allowed,TFP for known and TFN denied.

ITU: TFP ALLOWED

ANSI: TFR ALLOWED

JAPAN: TFPALLOWED

C6 * TFR_DENIED YES, NO

Control parameter for the use of theTransfer Restricted procedure. If theuse of procedure is denied, the TransferRestricted messages coming from thesource point are not handled, andTransfer Restricted messages are notsent to the destination point. Instead,the system sends Transfer Allowedmessages (unless their use is alsodenied).

ITU: YES

ANSI: NO

JAPAN: YES (TTC),NO(NTT)

D COMMON PARAMETERS OF ALLSIGNALLING POINTS

D0 TFR_SENDING_BASIS NONE, ITU, ANSI

Control parameter for managingoverload on a spare route when the lastavailable route becomes unavailable.Possible parameter values are NONE(no TFR messages broadcast), ITU(follows ITU-T Rec. Q704) and ANSI(examines state of timer T11 ).

ITU: NONE

ANSI: ANSI

JAPAN:NONE (TTC),ITU (NTT)

DN02143262Issue 16-1 en30/01/2009




Parametergroup


Parameter name

Parameter name


Recommendedvalue

D1 CIRC_ROU_PREV_IN_USE YES, NO

Control parameter for restricting theoccurrence possibilities of circularlyrouted messages. When this parameterhas value YES, an extra TransferProhibited message is used concerningone of the destination signalling points.If traffic to the point goes via alternativeroutes, the system sends the TransferProhibited message about that point toall adjacent signalling points, andorders them to switch all traffic to thepoint via other signalling points.

ITU: NO

ANSI: YES

JAPAN: NO

D2 TFC_DENIED YES, NO

Control parameter for the TransferControlled message sending. If theparameter has value NO and deniesthe message sending, the TransferControlled messages are not sent tothe destination point.

NO

D3 CONG_LEVEL_SUPPORT NONE, TFC, TFC ANDRCT

Control parameter for the encoding ofthe congestion level of the TransferControlled messages. If the parameterhas value NO and the message controlis inactive, the system sets congestionlevel 0 for the TFC messages directedto the destination point, but otherwisethey get congestion level as defined bythe over loaded signalling terminal. Thiscontrol parameter can also be used todefine the overload of a destinationpoint to be monitored using theCongestion Level Test messages.

ITU: TFC

ANSI: TFC AND RCT

JAPAN: TFC (NTT),TFC AND RCT (TTC)

D4 CONFUSION_MSG_DENIED YES, NO


30/01/2009



Parametergroup


Parameter name

Parameter name


Recommendedvalue

Control parameter for the MTPConfusion message sending. If sendingof the messages is prohibited, themessages are not transmitted to thedestination point. This feature isimplemented as defined in standardBTNR 146.

YES

D5 UPU_ALLOWED YES, NO

This parameter either allows (YES) ordenies (NO) the sending of the UPUmessage (user part unavailable).

ITU: NO

ANSI: YES

JAPAN: NO

D6 RST_ON_TFP_ALLOWED YES, NO

This parameter either allows (YES) ordenies (NO) immediate sending of routeset test (RST) message when transferprohibited message (TFP) is received.When this parameter has value NO, theRST message is sent after theQ704_T10 timer has expired.

ITU: YES

ANSI: YES

JAPAN: NO

D7 USE_OF_M3UA_NW_APP YES, NO

Control of using Network Appearanceparameter in the “M3UA signallingnetwork management messages”.

YES

D8 SUPPORT_OF_M3UA_SNM YES, NO

Control of sending M3UA signallingnetwork management messages.

NO

D9 SRT_DENIED YES, NO

Control of signal routing test. ITU: YES

ANSI: YES

JAPAN: NO

D10 USN_DENIED YES, NO

Control of sending unallocatedsignalling.

ITU: YES

ANSI: YES

JAPAN: NO

DN02143262Issue 16-1 en30/01/2009



10.6 SCCP signalling point parameters

The parameter set related to the SCCP signalling point defines theparameters for certain timers that are used in monitoring the signallingconnections, and for managing the subsystems (ITU-T Rec Q.714). Theparameter set also defines some of the signalling network functions.

For instructions, see Creating new SCCP signalling point parameter setand Modifying SCCP signalling point parameter set.

The parameter values vary according to the release level and delivery.Usually the default parameter values are suitable and it is not necessary tochange them. But of course, the values can be changed, if for example thenational definition of signalling differs from the set default values.

You can interrogate the values of the parameters of an existing SCCPsignalling point parameter set with the OCI command.

The following table lists the parameter names, all possible parametervalues, quality of the value and the recommended values, if any, that arerelated to the SCCP signalling point.

Table 11. SCCP signalling point parameters

Parameternumber

Parameter name


Value range (quality of value)

Recommended value

1 Q714_T_CONN_EST 30 ... 240 (1 s)

Timer for connection setup. Defines thetime for waiting for a response to theconnection request message.

90

Usually, you do not need tochange the parameter value.

2 Q714_T_IAS 60 ... 600 (1 s)

Send inactivity timer. When timer expires,an inactivity test -message (IT) is sent tothe connection section.

90

Note that this timer shouldnormally be at least two timessmaller than Q714_T_IAR at theother end.

3 Q714_T_IAR 150 ... 1260 (1 s)

Receive inactivity timer. Connection isreleased if no messages have beenreceived when the timer expires.

270

Note that this timer shouldnormally be at least two timesgreater than Q714_T_IAS at theother end.

4 Q714_T_REL 100 ... 200 (100 ms)


30/01/2009


Table 11. SCCP signalling point parameters (cont.)

Parameternumber

Parameter name



Recommended value

If the first connection release message(Released, RLSD) produces noacknowledgement ( release message orRelease Completed, RLC), the releasemessage is repeated and new timesupervision is started for it(Q714_T_REP_REL).

150

5 Q714_T_INT 45 ... 90 (1 s)

Control parameter for connection releasetime. The release message is beingrepeated during that time. After time-out,the resources allocated for the connectionare frozen for a certain time and an alarmis set.

60

6 Q714_T_RES 10 ... 20 (1 s)

Time supervision for resetting thesignalling connection, service class 3timer that is not in use.

15

7 Q714_T_REP_REL 40 ... 200 (100 ms)

If a repeated connection release message(Released, RLSD) produces noacknowledgement ( release message orRelease Completed, RLC) during the settime supervision period, the releasemessage is repeated and new timesupervision is started for it(Q714_T_REP_REL).

100

8 Q714_T_STAT_1ST 50 ... 600 (100 ms)

Time supervision, after which the firstSubsystem Status Test (SST) message issent out.

BLUE: 600

A_INT: 100

WHITE: 100

9 Q714_T_STAT_INC 150 ... 3000 (100 ms)

Time that is added to the repeat intervalof the SST message after each repeatevent unless the message SubsystemAllowed (SSA) is not received.

300

10 Q714_T_STAT_MAX 600 ... 12000 (100 ms)

The maximum time for the repeat intervalof the SST message.

BLUE: 600

A_INT: 9000

WHITE: 9000

DN02143262Issue 16-1 en30/01/2009




Parameternumber

Parameter name



Recommended value

11 A_INTERFACE YES, NO

Defines whether the system uses Ainterface specification in the direction ofthe SP.

BLUE: NO

A_INT: YES

WHITE: NO

12 WHITE_BOOK_MGMT_USED YES, NO

Defines whether the system uses SCCPmanagement procedures ITU-T, Q711-Q714, 1993/3 (defined in the White Book)in the direction of the SP.

BLUE: NO

A_INT: NO

WHITE: YES

13 SS_MANAGEMENT_USED YES, NO

Defines whether the subsystem statusmanagement functions are used.

YES

14 XUDT_USED YES, NO

Defines whether Extended Unit Data(XUDT) messages can be sent to thementioned SP. The parameter value isread from the parameter set of the calledSP.

NO

15 UDT_DENIED YES, NO

Defines when the sending of Unit Data(UDT) messages to the mentioned SP isdenied. The parameter value is read fromthe parameter set of the called SP.

NO

16 SEG_X_THRES 1 ... 272

The local segmentation threshold value isX for connectionless messages. Theparameter value defines the length of thedata part in the connectionless messagesthat are sent to the network. The X valuecan define segmentation on, if the valueis smaller than Y depending on the localimplementation. (This feature is not yet inuse.)

272

Usually, this parameter has thesame value as parameterSEG_Y_THRES.

17 SEG_Y_THRES 67 ... 272

Threshold value Y for the segmentation ofthe connectionless messages. The valuecan be used to adjust the length of datapart in the connectionless messages thatare sent to the network. Value Y mainlycontrols the segmentation.

272

Usually, this parameter has thesame value as parameterSEG_X_THRES.


30/01/2009



Parameternumber

Parameter name



Recommended value

18 TCAP_LOAD_SHARING_USED YES, NO

Defined whether load sharing is used onTCAP messages. The load sharingapplies only to messages that start aTCAP transaction. Load sharing meansthat the SCCP connectionless servicedistributes the TCAP messages comingfrom the network to the TC units in acircular sequence. The parameter value isread from the parameter set of the SPthat has sent the message.

NO

It is advisable to use value YESfor this parameter if the trafficcoming in to the CCSU is notevenly distributed.

19 ADD_DPC_IF_RI_SSN YES, NO

Defines whether a signalling point codehas to be added or left into the calledaddress when routing is done accordingto the subsystem number. Adding thecode is only possible with messagesgoing out into the network. The parametervalue is read from the parameter set ofthe called SP.

NO

Usually, you do not need to modifythis parameter value.

20 ADD_GT_IF_RI_SSN YES, NO

Defines whether a global title has to beleft into the called address when routingis done according to the subsystemnumber. Adding the address is onlypossible with messages going out into thenetwork. The parameter value is readfrom the parameter set of the destinationSP.

NO


21 ADD_DPC_IF_RI_GT YES, NO

Defines whether a signalling point codehas to be added or left into the calledaddress when routing is done accordingto the global title. Adding the code is onlypossible with messages going out into thenetwork. The parameter value is readfrom the parameter set of the destinationSP

NO


22 ANALYSE_ROOT_OF_CALLING_GT YES, NO

Parameter indicates if global title root ofcalling address is analysed or not.

NO

23 ALLOWED_GTI_VALUES 1 ... 15

DN02143262Issue 16-1 en30/01/2009




Parameternumber

Parameter name



Recommended value

Parameter declares global title indicatorvalues that use are allowed in callingaddress.

ALL: 1-4,5,6,7,8,9,10,11,12,13,14,15

24 SSA_FILTER_TIMER 5 ... 3000 (100 ms)

Defines the delay of local broadcast ofsubsystem allowed (SSA) stateinformation.

10

25 SSP_FILTER_TIMER 5 ... 3000 (100 ms)

Defines the delay of local broadcast ofsubsystem prohibited (SSP) stateinformation.

10

26 LUDT_USED YES, NO

Defines whether the long unit data(LUDT) messages are used. Note thatremote SP must support this function.

NO

27 CO_SEGM_USED YES, NO

Usage of connection-orientedsegmentation.

10.7 SCCP subsystem parameters

The parameter set related to the SCCP subsystems defines, for example,the timers monitoring the various subsystems.

For instructions, see Creating new SCCP subsystem parameter set andModifying the values of SCCP subsystem parameter set.

The parameter values vary depending on the release level and delivery.Usually, it is not necessary to change the parameter values. But forexample, if the national definitions on signalling are different from thedefault values, the parameter values can naturally be modified.

You can interrogate the values of the parameters of an existing SCCPsubsystem parameter set with the OCJ command.


30/01/2009


The following table lists the parameter names, possible parameter values,quality of the given parameter value, and the recommended values, if any,for parameters related to the SCCP subsystems.

Table 12. SCCP subsystem parameters

Parameternumber

Parameter name



Recommendedvalue

1 Q714_T_COORD_CHG 30 ... 240 (1s)

The time supervision period spent waiting fora reply (Subsystem-Out-of-Grant, SOG,message) as an acknowledgement to theSubsystem-Out-of-Service-Request (SOR)message, when the subsystem is beingremoved from service in a controlled manner.

90

2 Q714_T_IGN_SST 30 ... 300 (1s)

Time supervision during which the SSTmessage is not answered after receiving aSOG message.

60

3 A_INTERF_APPLIC YES, NO

Defines whether the A interface specificationparameter of an SP is applied for thissubsystem.

GENER:NO

A_INT:YES

4 A_INTERF_ERR_IGNORED YES, NO

Defines whether the system ignores ProtocolData Unit Errors (ERR) received from the Ainterface.

GENER:NO

A_INT:YES

5 TRANSLATION_SELECTION SCCP, REDIGO

Defines where the global address is modifiedif the SCCP routing address (the result of themodification) is the own SP. Routing is madeaccording to the global address. Theparameter value is read from the parameterset of the called subsystem.

SCCP

6 CALLING_ADDR_MODIFICATION YES, NO

DN02143262Issue 16-1 en30/01/2009



Table 12. SCCP subsystem parameters (cont.)

Parameternumber

Parameter name



Recommendedvalue

Defines whether the calling address ismodified if the routing is based on thesubsystem number when the global addresshas been modified, and the message hasbeen received from the SCCP user. In thecalling address, the global title is replaced bythe own point code. The parameter value isread from the parameter set of the callingsubsystem.

NO

7 CSCC_ALLOWED_OUT YES, NO

Defines whether the subsystem is allowed torequest coordinated state transition.

NO

8 CSCC_ALLOWED_IN YES, NO

Defines whether the request on coordinatedstate transition is sent to the subsystem.

NO

9 TRANSLATE_AT_DPC_IF_DPC_SSN_GT YES, NO

Defines whether the global title is translated inthe SP which signalling point code is includedin called address or message is sent to theSP so that the routing indicator is route onSSN although the called address includes alsoGT when the called address of incomingmessage includes a signalling point code,subsystem number and global title. Thisparameter only applies to the messagesreceived from the own user part. Theparameter value is read from the parameterset of the called subsystem.

YES

10 TC_TRANSACTION_IDS_THRESHOLD 25...90 (%)

Threshold for open TC transaction. If thethreshold is exceeded a statistics event log isset.

75

11 SEND_CALLING_SSN_IF_RI_SSN YES, NO

Indicates whether the calling address ismodified so that it includes only SSN whenthe routing of called address is based onSSN.

NO

12 SEND_CALLING_SPC_SSN_IF_RI_GT YES, NO


30/01/2009


Table 12. SCCP subsystem parameters (cont.)

Parameternumber

Parameter name



Recommendedvalue

Indicates wheter the calling address ismodified so that it includes SPC and SSNwhen the routing of called address is basedon GT.

NO

13 KEEP_CLD_GT_IF_RI_SSN YES, NO

Indicates if the gt is kept in the called address,even if routing of the called address is basedon SSN. The parameter concerns messagesgoing to a local SCCP user.

NO

14 IMMEDIATE_STATE_INFO YES, NO

Indicates whether subsystem state informationis transferred immediately to a local SCCPuser.

NO

DN02143262Issue 16-1 en30/01/2009




30/01/2009


11 Planning SS7 network

11.1 SS7 network planning principles

Before you start

To plan a whole signalling network you have to have experience intelecommunications and professional knowledge about signallingsystems.

Before the SS7 configuration is created the whole signalling network hasto be planned carefully. Define or settle the following issues before startingthe creation of the SS7 signalling configuration:

Steps

1. Get the signalling point code allocation scheme fromtelecommunications administration

The allocation scheme contains the signalling point codes to beused in the signalling network.

2. Define the format of signalling point code (SPC): length 14, 16or 24 bits

Also define if the signalling point code should be allocated intosubfields, for example, 3-8-3 bits or 8-8-8 bits format (see ITU-TQ.708).

3. Define the signalling network allocation

Find out if, for example, RNCs are configured to NA1 signallingnetwork and MGW to NA0 signalling network.

4. Define the physical transmission paths between differentnetwork elements in MGW

DN02143262Issue 16-1 en30/01/2009


Planning SS7 network

In case of SAAL NNI, define VPI, VCI parameters. In case of PCMconnection, define PCM, TSL parameters. In case of IPtransmission, define source and destination IP addresses.

5. Identify the signalling links within a link set by definingsignalling link code (SLC) and time slot (TSL) mapping in MGW

In case of IP transmission that step is not required, because thesystem makes that allocation automatically.

6. Determine the type and amount of signalling traffic in order todefine the link set size between two network elements

7. Find out if there are any restrictions concerning the othervendors' interconnecting network elements

8. Define what kind of connection management and circuitsupervision messages (CCM) will be used

9. Define the network structure concerning signalling end points(SEP) and signalling transfer points (STP)

10. Find out what network elements are included in the signallingnetwork where the SCCP exists

11. Define the applications (SCCP subsystems) that exist indifferent network elements and the type of addressing (GT orSPC and SSN) used to send messages to them

12. Find out what kind of global titles are used (for example, ifroaming agreements and used IN services affect the globaltitles)

13. Determine if there are any restrictions concerning timer values,address field of messages or management procedures forinterconnected network elements made by other vendors

11.2 SS7 network structures

Before you start

Consider the following points:


30/01/2009


The signalling system can be used with different types of signallingnetwork structures. The choice between different types of signallingnetwork structures may be influenced by factors such as administrativeaspects and the structure of the telecommunication network to be servedby the signalling system.

In case the provision of the signalling system is planned purely on a persignalling relation basis, the likely result is a signalling network largelybased on associated signalling, typically supplemented by a limited degreeof quasi-associated signalling for low volume signalling relations. Thestructure of such a signalling network is mainly determined by the patternsof the signalling relations.

Another approach is to consider the signalling network as a commonresource that should be planned according to the total needs for commonchannel signalling. The high capacity of digital signalling links incombination with the needs for redundancy for reliability then typicallyleads to a signalling network based on a high degree of quasi-associatedsignalling with some provision for associated signalling for high volumesignalling relations. The latter approach to signalling network planning ismore likely to allow exploitation of the potential of common channelsignalling to support network features that require communication forpurposes other than the switching of connections.

The signalling network structures presented in this section is based on ITU—T Rec. Q.705–Q.706, Blue Book.

Summary

You should take into account the following points that are related tonetwork structures when planning SS7 signalling

Steps

1. Consider the availability of the network

The signalling network structure must be selected to meet the moststringent availability requirements of any user part served by aspecific network. The availability of the individual components of thenetwork (signalling links, signalling points and signalling transferpoints) must be considered in determining the network structure (seeRecommendation Q.709).

Attention has to be paid to the STP routing tables to ensure thatcircular routing does not occur.

2. Consider message transfer delay

DN02143262Issue 16-1 en30/01/2009



In order to take account of signalling message delay considerations,when structuring a particular signalling network, regard should begiven to the overall number of signalling links (where there are anumber of signalling relations in tandem) related to a particular usertransaction (for example to a specific call in the telephoneapplication) (see Recommendation Q.706).

In other words, there should be as few signalling transfer points aspossible in the signalling network.

3. Estimate signalling link load

When estimating the need of signalling links, it is recommended thatone signalling link load should not overrun 0,2 Erl (Erlang, the unit ofmeasure of carried traffic intensity).

4. Consider message sequence control

For all messages for the same transaction (for example a telephonecall) the MTP will maintain the same routing, if the connectionremains functional, provided that the same signalling link selectioncode is used. However, a transaction does not necessarily have touse the same signalling route for both forward and backwardmessages.

5. Estimate the number of signalling links used in load sharing

The number of signalling links used to share the load of a given flowof signalling traffic typically depends on. the total traffic load. the availability of the links. the required availability of the path between the two signalling

points concerned. the bit rate of the signalling links.

Load sharing requires at least two signalling links for all bit rates, butmore may be needed at lower bit rates.

When two links are used, one of the links should be able to carry allthe signalling traffic in case the other link fails.

Example Planning network structure: basic network structures

This is an example of the basic mesh network structure and threesimplified versions derived from it. More complex signalling networks canbe built using these models as building components.


30/01/2009


SEP signalling end point

STP signalling transfer point

Figure 9. Basic mesh network structure

In this example network, each signalling point with level 4 functions isconnected by two link sets to two signalling transfer points. Each pair ofsignalling transfer points is connected to every other pair by four link sets.There is a link set between the two signalling transfer points in each pair.The simplified versions (cases A, B and C) of the basic signalling networkare obtained by deleting respectively:

. in case A, two out of the four intersignalling transfer point link sets

. in case B, link sets between signalling transfer points of the samepair

. in case C, two out of the four intersignalling transfer point link setsand link sets between signalling transfer points of the same pair

It should be noted that for a given signalling link availability, the moresignalling link sets are removed from the basic signalling network (in goingfrom basic mesh network to cases A, B and C), the lower the availability ofthe signalling network is. However, an increase in the availability of thesimplified signalling network may be attained by adding one or moreparallel signalling links to each of the remaining signalling link sets.

SEP

STP STP

STPSTP

SEP

DN02143262Issue 16-1 en30/01/2009





Figure 10. Case A: Two out of four inter-STP link sets deleted



Figure 11. Case B: Link sets between STPs of the same pair deleted

SEP

STP STP

STPSTP

SEP

SEP

STP STP

STPSTP

SEP


30/01/2009




Figure 12. Case C: All four inter-STP link sets between STPs of the same pairdeleted

11.3 MTP level signalling network

Before you start

Consider the basic structure of the signalling network. The MTP gives theoperator many possibilities to configure the network. It is possible to createup to eight signalling routes to each destination and these routes can workin load sharing mode or backup mode. It must be considered carefullywhether it is necessary to use more than three routes, because themanagement of the whole network becomes very complex. Also the use ofload sharing between signalling routes needs careful planning, because itaffects the adjacent signalling points and their opportunities to usealternative routing. Typically, load sharing between signalling routes isused in signalling end points (SEP), if it is used in the signalling transferpoints (STP), the risk of message loops increases especially in largernetworks, if the network topology has not been planned carefully.

Steps

1. Define signalling routes

When signalling routes are defined, it must be understood that thewhole path across the network cannot be defined at the originatingsignalling point. Only the destination point and the adjacentsignalling transfer point are defined. The adjacent STP further routes

SEP

STP STP

STPSTP

SEP

DN02143262Issue 16-1 en30/01/2009



the messages according to its own routing rules and the messageoriginator cannot determine it. For example in the figure below, whenthe signalling routes from SP A to SP D are defined, SP A does notknow how SP B is going to route the messages originated from Afurther to D; either direct to D or via some STP X.

For instructions, see Creating remote MTP configuration.

STP Signalling Transfer Point

SEP Signalling End Point

Figure 13. Example of basic network

2. Define MTP load sharing

Load sharing between signalling routes is defined when thesignalling route set is created, and it can be modified afterwards withthe NRB command. Route priority is important in load sharing (priorityvaries from 0 to 7, 7 being the highest). The route with the highestpriority carries traffic. If there are two or more routes with the samepriority, they work with load sharing if load sharing is allowed. If loadsharing is denied, each priority should be defined only for one route,because if the same priority is defined for several routes, it is notpossible to know, which route becomes active (the route that

SEPA

STPC

SEPD

STPB

STPX


30/01/2009


becomes available first enters state AV-EX and the others enterstate AV-SP). Within a link set, signalling traffic is always sharedacross all the available signalling links, so the priority of thesignalling link has no effect there (according to SLS values).

As a general rule, the highest priority is assigned to the direct route(the route using the link set which connects the originating signallingpoint to the destination signalling point) and the second highestpriority to the route which is selected to be the primary alternative ifthe direct route fails, and so on. If there is no direct route (only routesvia STP) it is useful to choose the priorities so that the signallingrelations in both directions use the same path (example 1).Otherwise it is possible to end up with one-direction-signalling(example 2) which may cause more disturbance than no signalling atall.

You can use the NEO command to check which signalling linkstransmit each of the Signalling Link Selection Field (SLS) values.You can use this command to separately interrogate the load sharingdata concerning either messages generated by the own signallingpoint or STP signalling traffic (for example, for STP traffic accordingto the ANSI standards, the load sharing system is different).

For instructions, see Setting MTP level signalling traffic load sharing

For example scenarios, see below.

3. Define MTP level STP traffic restrictions

With the MTP level STP traffic restrictions, you can define howunauthorised STP messages are identified and how they aretreated. Messages are either transferred further or they aredestroyed. It is also possible to define, if an alarm indication is set.For instructions, see Setting/modifying MTP level signalling trafficrestrictions.

Administrations may make bilateral agreements on how to operatewith SS7 between their networks. These agreements may replacerestrictions on the SS7 messages authorised for one administrationto send to the other. Restrictions could be made, for example, in theinterest of network security or as a result of service restrictions.Unauthorised signalling traffic can be, for example, STP traffic forcalls setup via networks other than that containing the STP, whichhas not been agreed bilaterally.

DN02143262Issue 16-1 en30/01/2009



An administration making an agreement with restrictions may wish toidentify and provide special treatment to unauthorised SS7messages.

4. Allocate signalling point codes

Usually the national telecommunications authorities allocate acertain range of signalling point codes for each operator, and theoperators can use those point codes within their own networks asthey wish. In addition, it may be possible to use some other networkindicators apart from the PSTN network within the operator's ownnetwork and this would make it possible to have more networkelements connected (for example, in GSM network the BSCs areworking in NA1 network while the signalling point codes of NA0network are allocated only for MSCs and HLRs).

You have to take into account the national instructions whenallocating the signalling point codes in your signalling network.

5. Plan the use of additional signalling point codes

The Additional Own Signalling Point Codes functionality is designedto increase the signalling capacity between two (or more) networkelements by utilizing free signalling point codes and unused networkindicators available in the network. The Additional Own SignallingPoint Codes functionality is implemented on the MTP level. Sincethe functionality has not been implemented on the SCCP level, itoffers only limited value to applications using SCCP addresses inDPC format. But since very few applications are tied to using SCCPaddresses in DPC format, the majority of SCCP users can benefitfrom the feature when routing their messages based on Global Title(as subsystem states, and so on, maintained by SCCP managementhave no effect). Also, the fact that each additional own signallingpoint code occupies one out of the 1000 DPCs supported is a reallimitation to very few applications (if any). The Interworking FunctionAdditional Point Code allows the MTP to recognize the concernedsignalling point code as an address of the own network element. Inthe outgoing direction, each DPC can be connected to oneadditional own signalling point code, other than Reception AdditionalPoint Code. Such definitions guide the MTP to replace theoriginating point codes of User Part messages sent towards theDPCs with the additional own signalling point codes.

Interworking Function Additional Point Codes are needed, forexample, in cases when gateway switches forwarding Global Titlebased application traffic need several signalling link sets to handlethe SS7 traffic between them.


30/01/2009


Another use for own signalling point codes is the introduction ofSIGTRAN into the signalling network. When replacement of SS7transport with SIGTRAN begins, Interworking Function AdditionalPoint Codes make it possible to define circuit by circuit whetherrelated signalling to a partner switch is carried on traditional SS7 orby SIGTRAN. This smooth transition is accomplished by dividing thecircuits to the partner switch into two groups, one for each signallingtransport layer, with different DPCs. As there are two signalling linksets, implemented by MTP level 3 and M3UA, between the switchesand each User Part is able to distribute its traffic towards the severalDPCs of the partner switch, the DPC selected for a circuit choosesalso the signalling link set and hence the signalling transport layer forrelated User Part messages.

Migration to using SIGTRAN between switches can also be done sothat MTP users do not even have to distribute their traffic towards theseveral DPCs of the partner switch. One DPC and signalling routeset for the partner switch satisfy operator needs for redundancywhen the SS7 link set to the partner switch is used as a back-uproute for the SIGTRAN M3UA connection to the InterworkingFunction additional signalling point of the partner switch. In thisconfiguration, recoveries and failures of SS7 and SIGTRANconnection determine which transport layer carries the signallingtraffic between the switches.

Furthermore, the operator can use Interworking Function additionalpoint codes to support several signalling links between two switchesin order to implement combined link set functionality. Thisfunctionality, which brings additional signalling link sets between theswitches without showing any additional signalling point codes to theUser Parts, is implemented by applying load sharing between thedirect routes to the partner switches and the signalling link sets totheir Interworking Function signalling points. However, it is feasibleonly as long as user traffic destined to the partner switches is reallydiverted to all the links in the several signalling link sets between theswitches. This condition is met, for example, in ANSI networks andJapanese signalling networks where the maximum number of linksin a signalling link set is smaller than the number of SLS codecombinations.

The signalling management cluster is also a configuration in whichtwo network elements share a signalling point code. It consists of aSignalling Gateway and an application node but is visible to othernetwork elements only with one signalling point identity: that ofapplication Node. MTP level 2 connections and other MTPfunctionalities of a signalling management cluster is in the Signalling

DN02143262Issue 16-1 en30/01/2009



Gateway, while the User Part functionality of the cluster is in theapplication node. When the MTP of the Signalling Gateway receivesa User Part message destined to the management cluster, itforwards the message to the application node.

The signalling management cluster is recommended when asignalling point becomes an application Node as it is connected to aSignalling Gateway and therefore stripped of its MTP level 2connections to other network elements. Then, other networkelements need no configuration changes as they see nothing fromthe management cluster but the same old signalling point code.

The Management Cluster Signalling Point Code is designed to bringadditional functionality to the operator networks, but not necessarilyto increase signalling capacity between two (or more) networkelements.

6. Plan signalling parameters and parameter sets

There can be some network elements in the network which areworking according to some older specifications or which have somerestrictions in their functions (for example, it is forbidden to sendtraffic restart allowed message (TRA) to the adjacent networkelement), and these cases should be examined before the networkis configured. In the Nokia RNC and Multimedia Gateway, it ispossible to define parameters which are related to signallingnetwork, signalling route sets or signalling links. With proper settingsthe Nokia network elements are compatible with most other vendorsnetwork elements.

With the signalling parameters it is possible to control and modifycertain functions of the signalling network. The signalling parametersare divided into six different levels depending on which part of thesignalling system they affect.

For some levels it is possible to define a number of specialparameter sets. The parameter sets can be connected so thatdifferent parts of the signalling system use different parameter sets,that is, it is possible to use different kinds of signalling in differentdirections.

For example, there can be two different signalling link parametersets defined, one connected to signalling links leading to networkelement X and another connected to signalling links leading tonetwork element Y. In this case the signalling functions are differenttowards the network element X than towards the network element Y.


30/01/2009


In the Nokia RNC and MGW, there are few parameter setspredefined for a different kind of SS7 signalling standards (forexample ITU-T, ANSI, JAPAN). It is recommended to use theseparameter sets or at least to start with them. If there is a need tochange them, it is reasonable to create a new parameter set on thebasis of the predefined one.

All parameters, their values and detailed explanations are given inSS7 signalling network parameters

7. Plan loop signalling route sets

A network element can simulate several network elements by usingloop signalling route sets. The loop signalling route sets can becreated either like normal route sets where the signalling links haveto be in active state (L-LOOP) or they can be created by using linksthat are not in service (T-LOOP). In a route set like this, the signallingmessages are transferred from one signalling unit to another along amessage bus. You can select any free address from the signallingdestination point range used by the signalling network and define itas the loop route point address. The number of loop signalling routesets is not restricted.

The loop-back feature used by the TUP/ISUP needs two loopsignalling route sets in call setup. The initial messages of a call aresent to the first loop signalling route set and the same messagereturns to the home network element with the point code of the otherloop signalling route set as its originating point code. This gives theuser an impression that the own point starts a call to the first pointand the second point starts a call to the own point.

The loop-back feature is activated and the type of the loop is chosenwhen the signalling route set is created with the NRC command.

8. Plan use of the link set of another network

If there is need to use more than one network indicator (e.g. NA0and NA1), and the signalling traffic in the other one is very low, it ispossible to use the signalling link set of another network. This meansthat there is physically only one link set between two networkelements but there are two route sets using that link set.

For instructions, see Using the signalling link set of anothersignalling network.

Example Scenario for message loop

DN02143262Issue 16-1 en30/01/2009



Figure 14. Example of a message loop

Configuration in the example network:

Route set from A to D: direct route with priority 7 and indirect route via STPB with priority 7.

Route set from B to D: direct route with priority 7 and indirect route via STPC with priority 7, load sharing allowed.

Route set from C to D: direct route with priority 7 and indirect route via STPA with priority 7, load sharing allowed.

Problem:

In a configuration like this, when a message comes to any of the STPpoints (A, B, C), the result is a message loop C -> A -> B -> C -> .... forcertain parts of the traffic (messages with certain SLS codes).

Example Scenario for one directional signalling

STPC

SEPD

STPB

STPA

loopprior.=7

prior.=7

prior.=7

prior.=7

prior.=7prior.=7 STPC

SEPD

STPB

STPA

1) 2)


30/01/2009


Figure 15. Example of scenario for one directional signalling


Route set from A to D: direct route with priority 7 and indirect route via STPB with priority 6.

Route set from D to A: direct route with priority 7 and indirect route via STPC with priority 6.

Problem:

If link set A-D fails, the SP A routes messages destined to D via B and theSP D routes messages destined to A via C. Then if link set C-D fails (oralternatively, the SP C sends transfer prohibited (TFP) message to SP Dconcerning SPA), A still routes messages destined to D via B but D can nolonger reach A.

Example Possible negative consequences of using load sharingbetween routes

STPC

SEPD

STPB

STPA

STPC

SEPD

STPB

STPA

1) 2)

prior.=7

prior.=7

prior.=6

prior.=6

DN02143262Issue 16-1 en30/01/2009



Figure 16. Example of possible negative consequences of using load sharingbetween routes


Route set from A to D: direct route with priority 7 and indirect route via STPB also with priority 7, load sharing mode allowed in the route set.

Route set from D to A: direct route with priority 7 and indirect route via STPB with priority 7, load sharing mode allowed in the route set.

Problem:

This kind of configuration (stage 1) causes a short unnecessary break inthe signalling traffic from B to D.

In case link set B-D fails, STP B sends TFP message (concerning D, stage2) to STP A. After forced rerouting (stage 3), SEP A sends TFA message(concerning D, stage 4) to STP B, and then STP B is able to access SEPD.

SEPD

STPB

STPA

1)

prior.=7

prior.=7

prior.=7 prior.=7

SEPD

STPB

STPA

2)

SEPD

STPB

STPA

3)

TFA(conc. D)

SEPD

STPB

STPA

4)

TFP(conc. D)

FR


30/01/2009


11.4 SCCP level signalling network

Before you start

The signalling connection control part (SCCP) must be configured in thelocal network elements which have mobile applications, IN applications orwhich perform SCCP global title translations. SCCP has to be configuredalso for those remote network elements to which the SCCP messages aresent. SCCP does not need to be configured to the network elements if theSCCP messages are only sent through them and not to them.

Applications that use the SCCP services are defined as subsystems whichare identified by the subsystem number (SSN). Subsystems are SCCPmanagement (SCMG), RANAP, RNSAP and possibly some network-specific subsystems like BSSAP. How the subsystems are defined in theSCCP network depends on what kind of addresses are used in thesignalling message transfer.

When you plan the SCCP network, remember that the SCCP network isconfigured on the MTP network, and that there should be a route set onthe MTP level to all signalling points (SP) that are known by the SCCP.

For instructions, see Creating remote SCCP configuration.

Steps

1. Plan SCCP addressing (GT or SPC/SSN)

There are two types of addresses that are used for routing in theSCCP:. Signalling point code (SPC) and subsystem number (SSN)

addresses

In this case, the SCCP has to know all signalling points andsubsystems to which it may send messages because theSCCP routing checks the status of the called SPC and SSNbefore sending the message to the MTP.

. Global title (GT)

In this case, the SCCP only checks the status of the signallingpoint to which a message is sent for the next global titletranslation (GTT)

All local subsystems have to be defined to the SCCP because theSCCP checks their status before it passes incoming messages tothem. The SCCP and SCMG subsystems have to be defined for theremote nodes if any SCCP messages are sent to the SCCP. Thesubsystems to which the messages are sent with the SPC and SSN

DN02143262Issue 16-1 en30/01/2009



addresses also have to be defined in the remote nodes. This is thecase with the A interface. Elsewhere in the network it is alwayspossible to use global title for addressing. When roaming to/fromanother operator's network, the global title has to be used, but insideone operator's networks it is also possible to use the SPC and SSN.

For example, in the figure below, the RNSAP applications have to bedefined for local SCCPs in both network elements. In networkelement A, the RNSAP application of B must be defined, and innetwork element B, the RNSAP application of A must be defined.The RANAP application of network element A does not necessarilyneed to be defined in network element B if there is no need forchanging messages.

Figure 17. Two network elements with different SCCP subsystems

The global titles that have to be defined in a GSM network dependon the roaming agreements made by the operator. How and wherethe translations have to be defined, depends on the structure of thenetwork.

For example, it is possible to have one or two gateway STPs thathandle all outgoing and incoming signalling traffic. In that case allglobal titles of outgoing messages are translated so that messagesare sent to those STPs for further translation. In the STPs, theoutgoing global titles can be translated to international gateways orto other operator's gateway STPs.

MTP

SCCP

MTP

SCCP

Network element A Network element B

RANAP RNSAP RNSAP


30/01/2009


Figure 18. Example of SS7 SCCP routing and GT analysis in case of locationupdate (LOC.UPD.)

This is what happens in each network element.

MSC1 Local BSC indicates a location update of amobile. MSC/VLR sends a location updatemessage to HLR. This message is sent as aUDT message and the global title of the calledparty address of the message is derived fromthe IMSI number of the mobile. The countrycode part of the GT is translated in MSC1 tofind out the MTP address of the internationalgateway node and the message is sent to it.

PSTN1 The PSTN1 transfers the messages throughMTP to PSTN2.

PSTN2 The UDT message is received from thenational network. After the global titletranslation, where only the header informationand the country code of the called GT istranslated, the message is passed to theinternational gateway of the destinationnetwork.

PSTN2IN0SP=1102HNA0SP=102H

PSTN1NA0SP=101H

MSC1/VLRNA0SP=301H

PSTNXIN0SP=1XNA0SP=X

HLRZNA0SP=Z

IN0

MSCYNA0SP=Y

DPC=102/NA0route=GT

DPC=1X/IN0route=GT

DPC=Y/NA0route=GT

DPC=Z/NA0route=GT

DPC=301/NA0route=GT

DPC=1102/IN0route=GT

DPC=X/NA0route=GT

DPC=Y/NA0route=GT

IN0

NA0 NA0

RNC

MGW

DN02143262Issue 16-1 en30/01/2009



PSTNX PSTNX receives the UDT message from theinternational network and after the GTtranslation of the header information, thecountry code and the operator code, it passesthe message to the gateway MSC of thedestination operator in the national network.

MSCY MSCY receives the messages and performs aGT translation to find out the destination nodeof the message in the operator's network.

HLRZ HLRZ performs the last GT translation (if it isnot already done in the MSCY) to find out thatthe message is coming to it. SCCP passes theUDT message to the local subsystem.

Figure 19. The points where the global title translation is made (GTT 1-5)

Figure 20. The parts of the global title used in different global title translations

VLRMAP

TC

SCCP

MTP MTP

SCCP

MTP

SCCP

MTP

SCCP

MTP

HLRMAP

TC

SCCP

MTP

GTT2

GTT1

GTT3 GTT4

MSC1 PSTN1 PSTN2 PSTNX MSCY HLRZ

GTT5

GTT1 CC NDC MSIN

GTT2 CC NDC MSIN

GTT3 CC NDC MSIN

GTT4 CC NDC MSIN

GTT5 CC NDC MSIN


30/01/2009


CC country code

NDC national destination code

MSIN mobile subscriber identification number

With an IN application, the first message is most often received fromthe local subsystem with an address including the global title. Therest of the signalling may use SPC and SSN addressing. If the SPCand SSN addressing is used, the IN SSP has to know all SCPs that itcan use and vice versa, and the global title used by the INsubsystem is immediately translated to the SPC and SSN of theSCP subsystem. If the STP is used between SSP and SCP, theglobal title translation can lead to the STP and, if global titles areused for addressing throughout the signalling, the SSP does notneed to know about the SCP and vice versa.

2. Plan SCCP services

SCCP has two different message handling services. Connectionlessservice is used for database inquires, for broadcast-like services aswell as for passing of SCCP management messages. Connection-oriented service is currently used only at Iu and A interfaces (RNC-MGW-MSC) for call signalling. For more information, see SS7signalling.

3. Plan the needed SCCP subsystems

In the MGW, the following SCCP subsystem is needed if MGW isused as an SCCP level STP:. SCMG — SCCP Management Subsystem (The system

creates SCMG automatically when an SCCP signalling point isdefined.)

In RNC, the following SCCP subsystems are needed:. SCMG — SCCP Management Subsystem (The system

creates SCMG automatically when an SCCP signalling point isdefined.)

. RANAP — Radio Access Network Application Part

. RNSAP — Radio Network Subsystem Application Part

4. Plan global titles of SCCP

In the GSM network the global titles used for roaming are derivedfrom IMSI numbers of mobile subscribers by replacing the E.212number mobile country code and mobile network code with E.164number country code and network code so that the result is E.214number.

DN02143262Issue 16-1 en30/01/2009



The depth of translation should not be more than what is needed todistinguish the SP to which the message is sent.

For instructions, see Creating/modifying GT translation result andGT modification and Creating global title analysis for called GT.

5. Plan SCCP routing based on Calling Party global title

This is an optional feature.

After the called GT analysis is made, SCCP can route the traffic asdescribed below:

a. If the attribute ACGT (Analyse Calling GT) in the called GTanalysis result is on, the calling GT analysis is made. If thecalling GT analysis leads to a calling GT result where thedestination is reachable, the signalling message is routed tothis destination. If the destination in the calling GT result is notreachable, the destination in the called GT result is used.

b. If the attribute ACGT is off, the final destination in the calledGT result is used.

The calling GTanalyses are stored in a different table than the calledGT analyses. For instructions on how to configure the calling GTbased routing, see Creating calling GT routing configuration.

The following two use cases describe the feature:


30/01/2009


Figure 21. Use Case 1

The SCCP level STP and the GW1, GW2, and GW3 are all SCCPlevel STP points. The routing based on the SCCP calling partyaddress (CgPA) is implemented in the network element named‘SCCP level STP’ in figure Use Case 1. In the figure, the messageswith the same GT in an SCCP called party address (CdPA) arrive atthe common SCCP level STP and then are routed in a different waybased on where the messages come from:. GW1 if the calling GT is the GT of ‘Src NE1’. GW2 if the calling GT is the GT of ‘Src NE2’. GW3 if the calling GT is the GT of ‘Src NE3’

SCCP CdPA = Destination NESCCP CgPA = Src NE3MTP DPC = SCCP level STP

DestinationNE

SCCP level STP

GW2

GW2

GW3

Src NE3


GW2

Src NE2

GW1

Src NE1

SCCP level STP


DestinationNE

DN02143262Issue 16-1 en30/01/2009



Figure 22. Use Case 2

It is important for an operator to protect the network against spamSMSs. All SMSs originated from a secure source, for example, fromthe operator's own network have to be routed normally (see DEST inFigure Use Case 2). Other SMSs have to be routed to a controlcenter. The SMS is routed in a different way based on where itcomes from. The called GT analysis result holds the SPC of thecontrol center. The calling GT analysis is created for the trustedoriginators so that they lead to the normal destination (see DEST inFigure Use case 2). If there is no analysis for the calling GT (possiblespam), the SPC in the called GT analysis result is used.

6. Plan distribution of status data (broadcasts)

There are two types of broadcasts: to the network and localbroadcasts.

To network:

There is no absolute need for the definition of broadcast to thenetwork because the response method is always active and allnecessary status data is delivered to the network; it only takes a littlelonger. The broadcasts can be set, for instance, to inform someSCCP level STPs about the status of the subsystems to which theSTP sends messages with the SPC and SSN address.

Local:

Controlcenter

NE1

DESTNE2

STP


30/01/2009


Depending on the network element, the subsystems needing thebroadcast function are the BSSAP, RANAP and RNSAP. Forexample, the local BSSAP of the MSC has to know the status data ofthe BSSAP located in the BSCs, and accordingly, the local BSSAPof the BSC has to know the status data of the BSSAP in the MSC.

7. Plan SCCP level STP traffic restrictions

The system supports the following types of SCCP level STP trafficrestrictions, that is, SCCP screening:. SCCP signalling point screening. GT screening. calling GT checking and screening

These types of screening can be switched on or off separately fromeach other. They restrict the traffic of all subsystems, that is, youcannot use them to restrict the traffic of a given subsystem.

SCCP signalling point screening and GT screening

There are two methods to define the SCCP signalling pointscreening:. OPC/DPC method, where the screening method is set for

messages coming from a certain signalling network andOriginating Point Code (OPC) and are addressed to a certainsignalling network and Destination Point Code (DPC).

. Linkset/DPC method, where the screening method is set formessages coming from a certain signalling link set and areaddressed to a certain signalling network and DPC.

In the case of SCCP signalling point screening, it is also possible tocopy the existing MTP policing (STP access) to correspond to theSCCP level. However, it is not possible to copy an unauthorised typeof MTP policing to correspond to the SCCP level.

In the case of GT screening, the calling GT is analysed and thescreening method can be defined between the calling GT result andthe called GT result. If some GT modification is defined in the GTTresult, for example, adding or deleting digits of called or calling GT,the modification is done after the GT screening.

For SCCP signalling point screening and GT screening, thescreening method can be set as follows:

DN02143262Issue 16-1 en30/01/2009



. The message is deleted.

. An alarm is set for the deleted message.

. An alarm can be set without deleting the message.

The system sets one alarm per signalling message: 1029 SCCPSTP MESSAGE PREVENTION (for signalling point screening) or1293 SCCP GT SCREENING APPLIED (for GT screening).

The priority order for setting the alarm is the following:

a. Linkset/DPC

b. OPC/DPC

c. GT screening

The order is then decided by the traceability, the incoming link set isthe strictest way to trace the message.

The message is deleted if any of the three screening methodsindicate it. For example, if the Linkset/DPC screening methodindicates that only the alarm should be set and the GT screeningmethod indicates that the message must be deleted, the alarm isgenerated according to the Linkset/DPC method and later ondeleted according to the GT screening method.

Calling GT checking

In the case of Calling GT checking, there are two methods to defineSCCP level screening:. Restrictions according to the calling Global Title Indicator

(GTI): it is possible to define a set of allowed GTI values whichare transmitted.

. Restrictions according to the calling GT translator selectorvalues (calling GT root). It is possible to set the screening sothat messages with known GT translator selector values aretransmitted. This analysis is based on the existing called GTanalysis.

If either Calling GT checking method shows that the message mustbe deleted, alarm 1029 SCCP STP MESSAGE PREVENTION is setfor the message.


30/01/2009


The SCCP level STP messages that are screened cause theregistration of statistical information in the network element. Thereare no screening-specific statistical counters, so all the information isseen as 'unqualified' counters. You can see these routing failureevents with the OTR command. This concerns SCCP signalling pointbased screening and calling GT checking, but not GT screening.

8. Plan SCCP backups

On the SCCP level, the backups (replicas) may be those of eithersignalling points or subsystems. Signalling point backups are GTTbackups. This means that messages are normally sent to oneprimary STP for GTT, but in case of failure, another STP capable ofthe same GTT can be used.

Currently, the only relevant backups for subsystems could bedatabases (that is, IN SCPs). Backups can be defined for SPs,subsystems and also for global title translation results.

Only one backup is active, so when a global title translation resulthas a backup other possible backups are not used.

9. Plan SCCP load sharing

On the SCCP level, it is possible to define load sharing for up to 16destinations. Each load sharing destination has a destination priority.The traffic is shared between the primary destinations, that is, priorityvalue 1 destinations, as long as there is at least one primarydestination available. If there is no primary destination available, thetraffic is shared between the backup destinations, that is,destinations with priority value 2. Fallback to the primarydestinations is done when at least one primary destination becomesavailable.

SCCP routing selects the destination based on different methods forprotocol class 0 messages and protocol class 1 messages.

For protocol class 0 messages, SCCP routing selects thedestinations according to the order in the called GT result. SCCProuting keeps track of which the next destination to be selected is. Ifthere are, for example, four available priority value 1 destinations(that is, highest priority destination) in the result, they are selected in1, 2, 3, 4, 1, 2, 3, 4, order and so on.

DN02143262Issue 16-1 en30/01/2009



For protocol class 1 messages, SCCP routing selects the destinationaccording to the SLS value in the incoming message. The incomingSLS is not used directly, but an internal SLS value is calculatedbased on the incoming SLS and the OPC. The selection of thedestination index is done by mapping the internal SLS value to adestination index. Mapping is based on the SLS value range divisioninto as many parts as many destinations are in a result. Thedestination count is the amount of available highest prioritydestinations in the result; if none, the available lower prioritydestinations are used in load sharing.

If there are two destinations in the GT result, and load sharing is notused, the secondary result is used as a normal backup destination ofthe primary result.

For instructions on how to define SCCP load sharing, see Creating/modifying GT translation results and GT modifications.

In addition, on the SCCP level, MTP load sharing can be used whenmessages are sent to the STPs for GTT. This can be done so that inthe STP nodes a common MTP alias point code is defined for them,and in the sending node, a route set using the two STPs with loadsharing, is defined for the alias point. SCCP is also defined for thatalias point in the sending node and GTT is defined so that it leads tothe alias point. In this case, messages are sent to these two STPsthrough load sharing.


30/01/2009


12 Creating SAAL UNI signalling linksPurpose

The SAAL UNI signalling links are used at the ATM-based Iub interface fortransporting AAL2 signalling protocol messages, C-NBAP signallingmessages, and D-NBAP signalling messages. When adding or removingBase Transceiver Stations (BTS) under a Radio Network Controller (RNC)in ATM network, you need to add and delete SAAL UNI signalling linksaccordingly. See also Deleting SAAL UNI signalling links.

Before you start

Before creating SAAL UNI signalling links, check that there are VCLtpsavailable. For instructions, see Creating ATM resources in RNC.

Note

At the Iub interface, the primary tool for adding SAAL UNI signallinglinks is the RNW Object Browser. You should use this tool instead ofMML commands. To add SAAL UNI signalling links using the RNWObject Browser, see Creating radio network connection configuration(ATM, Dual Iub).

To add SAAL UNI signalling links for AAL2 signalling protocol by usingMML commands, see the command LSC.

Steps

1. Add SAAL UNI signalling link for AAL2 signalling protocol(LSC)

To create SAAL UNI signalling links for AAL2 signalling protocol,give the following command:

ZLSC:<sl interface id>,<sl VPI>,<sl VCI>;

DN02143262Issue 16-1 en30/01/2009


Creating SAAL UNI signalling links


30/01/2009


13 Creating local signalling configurationfor RNC

Before you start

Check that the network element has all the necessary equipment andsoftware.

Note

Note the following in relation to the NPC command when using NodalFunction to connect two adjacent RNCs via MGW Rel.4:

Since the signalling links are used for SCCP signalling, the value ofboth the service existing for STP messages and the service existing foruser part of own signalling point parameter must be Y.

ZNPC:<signalling network>,03,SCCP:Y:Y,208,10F;

Note

In Japan, you must read the subfields of the signalling point code forcommands NRP, NSC and NRC in reverse order. This differs from thestandard procedure used elsewhere in the world. For example, inJapan, the signalling point code 23–8–115, would be read as 115–8–23.

Steps

1. Create SS7 services

DN02143262Issue 16-1 en30/01/2009


Creating local signalling configuration for RNC

Before you start

The signalling messages coming into the network element can betransmitted to the network element's own user parts, or they can beswitched forwards, or both. Depending on the services configured to thenetwork element, some of the signalling messages are unnecessary. Dataon service information determines how the signalling messages cominginto the network element are received and switched.

Steps

a. Check that all necessary services exist (NPI)

Check that all needed services exist in the network element byusing the NPI command. The services SNM and SNT usuallyexist automatically in the network element.

The needed services depend on the type and use of thenetwork element. In Radio Network Controller (RNC) orMultimedia Gateway Rel.4 (MGW Rel.4) type of networkelements at least the following services are needed:. SNM — signalling network management messages. SNT — signalling network testing and maintenance

messages. SCCP — signalling connection control part. AAL2 — AAL type 2 signalling protocol

b. Create the necessary services (NPC)

Use the parameters service existing for STP messagesand service existing for user part of own signalling

point to choose whether the service is active for the STPmessages and/or to the user parts of the own signalling point.

Check the process family identifiers from the Site SpecificDocuments as there can be some exceptions to the valuesgiven in the following example commands.

ZNPC:<signalling network>,00,SNM:Y:Y,07F,06D;

ZNPC:<signalling network>,01,SNT:Y:Y,07F,;

ZNPC:<signalling network>,03,SCCP:Y:Y,208,10F;

ZNPC:<signalling network>,0C,AAL2:Y:Y,452;


30/01/2009


2. Create own MTP signalling point (NRP)

The own signalling point has to be defined before you can create theother objects of the signalling network. Use the command NRP tocreate the own MTP signalling point. A network element can beconnected to several signalling networks. The NRI commanddisplays all existing signalling points.

There are special network-specific parameters related to thesignalling networks, and you can output them using the NMOcommand. These parameters define, for example, the congestionmethod used in the signalling network. For more information aboutthe network-specific parameters, see SS7 signalling networkparameters.

Note

The same NRP command is used to create a new signalling network.

ZNRP:<signalling network>,<signalling point code>,<signalling point name>,STP:<ss7 standard>:<numberof spc subfields>:<spc subfield lengths>;

3. Create own SCCP signalling point (NFD)

Before you start creating the signalling point, check what theSignalling Point Code (SPC) of the system's own signalling point isby using the NRI command.

ZNFD:<signalling network>, <signalling point code>,<signalling point parameter set number>:<subsystemnumber>,<subsystem name>,<subsystem parameter setnumber>,[<subsystem status test>]: ::: ;

Note

The value YES for the subsystem status test parameter is valid onlywhen the parameter WHITE_BOOK_MGMT_USED (12) of the used SCCPsignalling point parameter set has value YES (check this with the OCIcommand).

DN02143262Issue 16-1 en30/01/2009



When an SCCP signalling point and SCCP subsystems are created,a parameter set is attached to them. In most cases the predefinedparameter sets are the most suitable, but if the predefined parametersets do not cover all occurring situations, you can create moreparameter sets, modify the relevant parameters and then attach thenew parameter set to the SCCP signalling point and SCCPsubsystem. For more information, see SCCP signalling pointparameters and SCCP subsystem parameters.

4. Add local subsystems to the signalling point (NFB), ifnecessary

ZNFB:[<signalling network>],<signalling pointcodes>:<subsystem number>,<subsystem name>,<subsystem parameter set number>,[<subsystem statustest>];

5. Activate local SCCP subsystems (NHC), if necessary

ZNHC:<signalling network>, <signalling point codes>:<subsystem>:ACT;

To display the subsystem states, use the NHI or NFJ command.

For more information, see States of SCCP subsystems.


30/01/2009


14 Creating remote MTP configurationPurpose

In most cases the MTP needs to be configured to the network element.Before configuring the MTP, the signalling network has to be planned withgreat care. See SS7 network planning principles.

The SS7 signalling configuration is needed for the following interfaces:

DN02143262Issue 16-1 en30/01/2009


Creating remote MTP configuration

. Iu-CS interface, between MGW and RNC. The configuration isbased on ATM or IP (SIGTRAN). For the ATM configuration, see theinstructions in this chapter. For information on configuring SS7signalling over IP (SIGTRAN), see Planning site configuration forsignalling and Creating M3UA configuration.

. Iur interface, between RNC and RNC; nodal functionality in MGW(see Figure AAL bearer establishment from RNC 1 to RNC 2 forillustration). The configuration is based on ATM or IP (SIGTRAN).For the ATM configuration, see the instructions in this chapter. Forinformation on configuring SS7 signalling over IP (SIGTRAN), seePlanning site configuration for signalling and Creating M3UAconfiguration.

Figure 23. AAL bearer establishment from RNC 1 to RNC 2

. Iu-PS interface, between RNC and SGSN. The configuration isbased on ATM or IP (SIGTRAN). For the ATM configuration, see theinstructions in this chapter. For information on configuring SS7signalling over IP (SIGTRAN), see Planning site configuration forsignalling and Creating M3UA configuration.

Before you start

Before you start to create signalling links, check that the SS7 services andthe MTP signalling point have been created. For instructions, see Creatinglocal signalling configuration for RNC.

MGW 1

RNC 1

MGW 2

RNC 2

Iur

Iu-CS

Iu-CS

MGW 3

Nb Nb

H.248

RANAP

BICC

Iur

MSCServer

MSCServer


30/01/2009


The parameter set related to the signalling link can be used to handleseveral signalling link timers and functions. If the ready-made parameterpackages do not cover all occurring situations, you can create moreparameter sets, modify the relevant parameters and then attach the newparameter set to the signalling link. It is advisable to find out if there will besuch special situations before you start configuring the MTP. SeeSignalling link parameters. The following are two examples of specialsituations in which TDM signalling links require modifications in theparameter set:

. One of the signalling links goes via satellite, and the level 2 errorcorrection method has to be preventive_cyclic_retransmissioninstead of the usual basic_method.

. National SS7 specification defines some of the timer values so thatthey are different from the general recommendations.

Steps

1. Check that the signalling links are distributed evenly betweendifferent ICSUs

Use the following command to display the existing signalling links.

ZNCI;

It is recommended that you allocate signalling links between allworking ICSU units to distribute the load.

Caution

It is very important that signalling links belonging to the same linkset areallocated to different ICSU units to avoid the whole linkset to becomeunavailable in an ICSU switchover.

2. Create signalling links (NCS)

Note

Before creating ATM signalling links, check that there are free VCLtpsavailable and that they are correctly configured. For instructions, seeCreate VCLtps for CBR traffic in Creating ATM resources in RNC.

DN02143262Issue 16-1 en30/01/2009



Note

Remember to check that the network element is adequately equippedbefore you start creating signalling links. You can do this with the WFIcommand.

To create ATM signalling links, give the command:

ZNCS:<signalling link number>:<external interface idnumber>,<external VPI-VCI>:<unit type>,<unitnumber>:<parameter set number>;

It is advisable to create the signalling links belonging to the samesignalling link set into different signalling units, if this is possible. Thisway a switchover of the signalling unit does not cause the wholesignalling link set to become unreachable.

Note

The Signalling Link Code (SLC) and the Time Slot (TSL) have to bedefined so that they are the same at both ends of the signalling link.

You can number the signalling links within the network element as youwish. The default value for the number is always the next free number.

To interrogate existing signalling links, use the NCI or NEL command.

3. Create SS7 signalling link set (NSC)

Create a signalling link set for each destination.

A signalling link set consists of one or several links. The signallinglinks belonging to the signalling link set cannot be activated until thesignalling link set is connected to a signalling route set.

You can reserve more links for a link set with the NSC command. Youcan later add links to a signalling link set with the NSA command.

ZNSC:<signalling network>,<signalling point code>,<signalling link set name>:<signalling link number>,<signalling link code>;


30/01/2009


The parameters signalling network and signalling pointcode define the network element where the signalling link set leadsto.

To interrogate the existing signalling link sets, use the NSI or NEScommand.

4. Create signalling route set to MGW (NRC)

When a signalling route set is created, a parameter set is attached toit. The parameter set can be used to handle several MTP3 levelfunctions. If the predefined parameter sets do not cover all occurringsituations, you can create more parameter sets, modify the relevantparameters and then attach the new parameter set to the signallingroute set. See Signalling route set parameters.

Create a signalling route set for each destination.

You can create all signalling routes that belong to the same route setat the same time with the same command.

ZNRC:<signalling network>,<signalling point code>,<signalling point name>,<parameter set number>,<loadsharing status>,<restriction status>:<signalingtransfer point network>,<signalling transfer pointcode>,<signalling transfer point name>,<signallingroute priority>;

The parameters signalling transfer point code andsignalling transfer point name are used when the createdsignalling route is indirect, that is, the route goes via signallingtransfer point (STP). There is no need to use those two parameterswhen the RNC is directly connected to the MGW.

Note

A signalling point cannot be used as an STP unless it is first equippedwith a direct signalling route.

For more information about signalling route set priorities, see SS7network planning principles.

To add signalling routes to an existing signalling route set, use the NRAcommand.

DN02143262Issue 16-1 en30/01/2009



5. Create signalling route set to MSS via MGW (NRC)

Create a signalling route set for each destination.

You can create all signalling routes that belong to the same route setat the same time with the same command. Later you can addsignalling routes to a route set with the NRA command.

ZNRC:<signalling network>,<signalling point code>,<signalling point name>,<parameter set number>,<loadsharing status>,<restriction status>:<signalingtransfer point network>,<signalling transfer pointcode>,<signalling transfer point name>,<signallingroute priority>;

The route goes via MGW which is working as a signalling transferpoint (STP) when the created signalling route is indirect.

The parameters signalling transfer point code andsignalling transfer point name are the same as the MGW'ssignalling point code and the name of the MGW.


30/01/2009


15 Activating MTP configurationSteps

1. Allow activation of the signalling links (NLA)

Use the following command to allow the activation of the previouslycreated signalling links:

ZNLA:<signalling link numbers>;

2. Activate the signalling links (NLC)

Use the following command to activate the previously createdsignalling links:

ZNLC:<signalling link numbers>,ACT;

The signalling links assume either state AV-EX (active) or UA-INS ifthe activation did not succeed. Activation may fail because links atthe remote end are inactive or the transmission link is not workingproperly.

For more information, see States of signalling links.

Note

To interrogate the states of signalling links, use the commands NLI orNEL.

3. Allow activation of the signalling routes (NVA)

Use the following command to allow the activation of the previouslycreated signalling routes:

DN02143262Issue 16-1 en30/01/2009


Activating MTP configuration

ZNVA:<signalling network>,<signalling point code>:<signalling transfer point network>,<signallingtransfer point code>;

4. Activate signalling routes (NVC)

The following command activates the previously created signallingroutes:

ZNVC:<signalling network>,<signalling point code>:<signalling transfer point network>,<signallingtransfer point code>:ACT;

Note

To interrogate the states of signalling routes, use the NVI, NER or NRIcommands.

When you are dealing with a direct signalling route, the signallingroute set assumes the state AV-EX if the related link set is active;otherwise it assumes the state UA-INS. A signalling route goingthrough an STP can also assume the state UA-INR if the STP hassent a Transfer Prohibited (TFP) message concerning thedestination point of the route set. For more information, see States ofsignalling routes.

Example Example of activating an MTP configuration

In this example, you change the state of a signalling route which isleading to the signalling point 302. The route is defined in thesignalling point 301 that is located in the national signalling networkNA0.

First, you change the signalling route state to ACTIVATIONALLOWED, and then you can take the signalling route into service.

ZNVA:NA0,302:;

The execution printout can be as follows:


30/01/2009


ALLOWING ACTIVATION OF SIGNALLING ROUTE

DESTINATION: SP ROUTES: SP

NET SP CODE H/D NAME NET SP CODE H/D NAME

--- ------------------ ----- --- --------------- -----

NA0 0302/00770 MSS2 NA0 0302/00770 MSS2 ACTIVATION ALLOWED

COMMAND EXECUTED

After this, you use the NVC command to activate the route:

ZNVC:NA0,302::ACT;

The execution printout can be as follows:

CHANGING SIGNALLING ROUTE STATE

DESTINATION: SP ROUTES: SP OLD NEW

NET SP CODE H/D NAME NET SP CODE H/D NAME STATE STATE PRIO

--- ------------------ ----- --- -------------- ------- ------- ------ ----

NA0 0302/00770 MSS2 NA0 0302/00770 MSS2 UA-INU AV-EX 2

COMMAND EXECUTED

DN02143262Issue 16-1 en30/01/2009




30/01/2009


16 Setting MTP level signalling traffic loadsharing

Purpose

With MTP level signalling traffic load sharing you can share the signallingtraffic between signalling routes and between signalling links belonging tothe same link set.

Within a signalling link set, load sharing is implemented so that itautomatically covers all links that are in active state.

Load sharing between signalling routes takes effect only after you haveallowed load sharing by defining the same priority for all signalling routesand by allowing load sharing in that route set.

Before you start

Before setting the load sharing, plan carefully which kind of load sharing issuitable in the signalling network. For more information, see MTP levelsignalling network.

See also Modifying MTP level signalling traffic load sharing.

Steps

1. Check signalling route priorities and load sharing status, ifneeded (NRI)

ZNRI:<signalling network>,<signalling point code>;

2. Check MTP load sharing data (NEO)

Check which signalling links transmit each of the Signalling LinkSelection Field (SLS) values.

DN02143262Issue 16-1 en30/01/2009


Setting MTP level signalling traffic load sharing

You can use this command to separately interrogate the load sharingdata concerning either messages generated by the own signallingpoint or STP signalling traffic.

Notice that the load sharing system is different for STP trafficaccording to the ANSI standards.

ZNEO:;

3. Modify signalling route priority, if needed (NRE)

The priority can vary between 0-7, the primary priority being 7.

ZNRE:<signalling network>,<signalling point code>:<signalling transfer point network>,<signallingtransfer point code>,<new signalling route priority>;

4. Allow load sharing in the signalling route set, if needed (NRB)

If load sharing is not allowed in the signalling route set (output of theNRI command), you have to change the load sharing status.

ZNRB:<signalling network>,<signalling point codes>:LOAD=<load sharing status>;


30/01/2009


17 Creating remote SCCP configuration

17.1 Creating remote SCCP configuration

Purpose

The SCCP is needed on a network element if the element:

. is used for switching calls

. is used for switching IN services

. acts as SCCP-level Signalling Transfer Point (STP).

Before you start

Check that the whole network has been carefully planned, that allnecessary hardware has been installed on the network element, and thatthe Message Transfer Part (MTP) has already been configured.

Verify the following items:

. Check that the signalling points have been created on the MTP (theNRI command).

. Check which parameter set is used, and whether it is necessary tomodify the values of existing parameter sets to meet the presentconditions and requirements (the OCI command).

. Check which subsystems are used.

. Check the data on subsystem parameter sets (the OCJ command),and the possible modifications on them (the OCN command).

. Check that the SCCP service has been created on the MTP level(the NPI command).

DN02143262Issue 16-1 en30/01/2009


Creating remote SCCP configuration

Before you can create the SCCP to the network element, the SCCPservice has to be created. To check that the service has beencreated, use the NPI command. If there is no SCCP service createdon the MTP level, create it with the NPC command (more informationin Creating remote MTP configuration).

Note

The SCCP management subsystem (SCMG) is automatically createdwhen you create the SCCP for the signalling point.

Note

The subsystems which use the Transaction Capabilities are configuredin a similar way, and no further configuration is needed (as the TC isautomatically used for suitable subsystems).

Steps

1. Create remote SCCP signalling points and subsystems (NFD)

In addition to creating the SCCP signalling point and its subsystems,you need to define the other SCCP signalling points and thesubsystems of the other SCCP signalling points of the network,which are involved in SCCP level traffic.

ZNFD:<signalling network>, <signalling point code>,<signalling point parameter set>: <subsystem number>,<subsystem name>, <subsystem parameter set number>,Y;

You can add more subsystems to a signalling point later by using theNFB command. The system may need new subsystems, forexample, when new services are installed, software is upgraded ornetwork is expanded.

When you are adding subsystems, you need to know whichparameter set you want the subsystems to use or which one has tobe used.

You can display the existing parameter sets by using the OCJcommand. When you want to modify the parameters, use the OCNcommand, and to create a new parameter set, use the OCAcommand.


30/01/2009


2. Create translation results, if necessary (NAC)

The translation result refers to those routes where messages can betransmitted. All the signalling points that are meant to handle SCCPlevel traffic must be defined at a signalling point.

At this stage you have to decide whether the routing is based onglobal title (GT) or on subsystem number.

ZNAC:NET=<primary network>,DPC=<primary destinationpoint code>,RI=<primary routing indicator>;

If you want to have a back-up system for routes or the network, youcan create alternative routes that will then be taken into service if theprimary route fails. Also it is possible to use load sharing for up to 16destinations by giving value YES for parameter <load sharing>.

3. Create global title analysis, if necessary (NBC)

Before creating the global title analysis, check the number of thetranslation result so you can attach the analysis to a certain result.Use the NAI command.

For more information about global title analysis, see SS7 networkplanning principles.

ZNBC:ITU=<itu-t global title indicator>,LAST=<lastglobal title to be analysed>:TT=<translation type>,NP=<numbering plan>,NAI=<nature of addressindicator>:<digits>:<result record index>;

4. Set broadcast status (OBC)

It is recommended to add local broadcast status of SCCPsubsystem to RNC. The local broadcast status (using the OBCcommand) informs the subsystems of the own signalling point aboutchanges in the subsystems of the remote signalling points.

Note

When setting the broadcasts, consider carefully what broadcasts areneeded. Incorrect or unnecessary broadcasts can cause problems and/or unnecessary traffic in the signalling network.

Depending on the network element, the subsystems needing thebroadcast function are the following:

DN02143262Issue 16-1 en30/01/2009



. RANAP Radio Access Network Application Part

. RNSAP Radio Network Subsystem Application Part

Local broadcasts:

ZOBC:<network of affected subsystem>,<signallingpoint code of affected subsystem>,<affected subsystemnumber>:<network of local subsystem>,<localsubsystem number>:<status>;

'BROADCAST STATUS OF SCCP SIGNALLING POINTS'definitions (using the OBM and OBI commands) are not needed in theRNSAP and RANAP interfaces connected to RNC, because theycause too much unnecessary signalling.

For more information, see SCCP level signalling network.

17.2 Activating SCCP configuration

Steps

1. Activate remote SCCP signalling points (NGC)

ZNGC:<signalling network>, <signalling point codes>:ACT;

You do not have to activate the own SCCP signalling point.

2. Check that the signalling point is active (NFI/NGI)

ZNFI;

OR

ZNGI;

Notice that if you use the default values in this command, only thesignalling points of network NA0 are shown. For more information,see States of SCCP signalling points.

Expected outcome


30/01/2009


In the command printout, the state of signalling point should be AV-EX.

Unexpected outcome

If the signalling point assumes state UA-INS, there is a fault on theMTP level.

Example

When you examine an example system using the NFI or NGIcommands, all signalling points should be in normal state AV-EX.Note that the signalling point 101H cannot be seen because theSCCP is not defined in it.

For command ZNGI:NA0,:N; the execution printout can be asfollows:

SCCP STATES

DESTINATION: SP ROUTING: SP

NET SP CODE H/D NAME STATE RM NET SP CODE H/D NAME STATE

--- ------------------ ----- ----- -- --- ------------------ ----- -------

NA0 0102/00258 PSTN2 AV - NA0 0102/00258 PSTN2 AV-EX

NA0 0301/00769 RNC1 OWN SP

NA0 0302/00770 MSS2 AV - NA0 0302/00770 MSS2 AV-EX

NA0 0311/00785 RNC1 AV - NA0 0311/00785 RNC1 AV-EX

NA0 0312/00786 BSC2 AV - NA0 0312/00786 BSC2 AV-EX

COMMAND EXECUTED

3. Activate remote SCCP subsystems (NHC)

ZNHC:<signalling network>, <signalling point codes>:<subsystem>:ACT;

To display the subsystem states, use the NHI or NFJ command.

When remote subsystems are being activated, their status is notchecked from the remote node. The remote subsystem statusbecomes AV-EX if the remote node is available, although the actualsubsystem may be unavailable or even missing. The status of theunavailable subsystem will be corrected with the response methodas soon as a message is sent to it.

DN02143262Issue 16-1 en30/01/2009



Use the NHI command to check that the subsystems have assumedstate AV-EX. If not, the reason may be faulty or missing distributiondata. Correct the distribution data and check the state again.Another reason for the subsystems not to be operating is that thesubsystem at the remote end is out of service.

For more information, see States of SCCP subsystems.

4. Set the SS7 network statistics, if needed

By setting the SS7 network statistics, you can monitor theperformance of the SS7 network. You do not have to do it in theintegration phase; you can do it later.


30/01/2009


18 Optimizing MTP configuration

18.1 Modifying MTP level 3 signalling parameters

Purpose

The MTP level 3 signalling parameters define the functions of the wholeMTP of the network element. Some of the parameter values are related tomonitoring the functions, while others define various limits and timers.

Modify the values of these parameters, when you think that some of theMTP level 3 timers have unsuitable values.

For more information on the parameters, see MTP level 3 parameters.

Before you start

As the MTP level 3 parameters affect to the whole network element's SS7signalling, make sure that the change will not cause any malfunctions tothe signalling system.

In most cases the predefined parameters are the most suitable ones.

Steps

1. Check MTP level 3 parameters (NMI)

You can display the used parameter values grouped by parametersets with the command NMI.

2. Modify MTP level 3 parameter (NMM)

ZNMM:<parameter group>:<parameter index>=<parametervalue>;

DN02143262Issue 16-1 en30/01/2009


Optimizing MTP configuration

18.2 Modifying SS7 signalling network parameters

Purpose

SS7 signalling network parameters apply to the whole signalling network.This means that the SS7 signalling network parameters can be separatelydefined for each signalling network (NA0, NA1, IN0 and IN1).

For more information on the parameters, see SS7 signalling networkspecific parameters.

Before you start

As the SS7 signalling network parameters affect to the whole signallingnetwork, make sure that the change will not cause any malfunctions to thesignalling system.

In most cases the predefined parameters are the most suitable ones.

Steps

1. Check parameter values (NMO)

You can display the used parameters in each signalling network withthe command NMO.

2. Modify SS7 signalling network parameters (NMC)

ZNMC:<signalling network>:<parameter group>:<parameter index>=<parameter value>;

18.3 Modifying the values of signalling link parameterset

Steps

1. Check signalling links and the parameter sets they use (NCI)

As the modifying of the values of an existing parameter set affects allsignalling links using that signalling link parameter set, checkwhether this can be done. If you want only a certain group ofsignalling links to have different signalling link parameter values, youshould create a new signalling link parameter set and attach it tothose signalling links.


30/01/2009


You can output all signalling links and the signalling link parametersets they are using with the command NCI.

If you want to create a new signalling link parameter set, seeinstructions from Creating new signalling link parameter set.

2. Deactivate signalling links using the parameter set you want tomodify (NLC)

The new values of the parameter set become active after thesignalling links that use the parameter set are first deactivated andactivated again.

ZNLC:<signalling link numbers>,INA;

3. Modify values of signalling link parameter set (NOM)

ZNOM:<signalling link parameter set number>,<signalling link parameter set name>, <parametergroup>: <parameter number>, <parameter value>;

For more information on the parameters, see Signalling linkparameters.

4. Activate signalling links using the modified parameter set (NLC)


18.4 Creating new signalling link parameter set

Steps

1. Check signalling links and the parameter sets they use (NCI)

You can output all signalling links and the signalling link parametersets they are using with the following command.

ZNCI;

If you only want to modify the values of a certain signalling linkparameter set, see instructions from Modifying the values ofsignalling link parameter set.

DN02143262Issue 16-1 en30/01/2009



2. Copy existing signalling link parameter set with a new name(NOE)

The best way to create a new signalling link parameter set is to copyan old parameter set with a new name. Choose the best suitableparameter set to be the source parameter set.

ZNOE:<source signalling link parameter set number>,<source signalling link parameter set name>:<signalling link parameter set number>, <signallinglink parameter set name>;

3. Modify values of the new signalling link parameter set (NOM)

ZNOM:<signalling link parameter set number>,<signalling link parameter set name>,<parametergroup>:<parameter number>,<parameter value>;

For more information on the parameters, see Signalling linkparameters.

4. Deactivate the signalling links that you want to use with the newparameter set (NLC)

It is reasonable to deactivate only a few of the signalling links at thesame time, if you want signalling traffic to be transmitted normallyduring the modification.

ZNLC:<signalling link numbers>,INA;

5. Change parameter set of signalling link (NCL)

Replace the existing parameter set of the signalling link with the newsignalling link parameter set.

ZNCL:<signalling link number>:<parameter setnumber>;

6. Activate signalling links using the new parameter set (NLC)



30/01/2009


18.5 Modifying the values of signalling route setparameter set

Steps

1. Check signalling route sets and the parameter sets they use(NRI)

As the modifying of the values of an existing parameter set affects allsignalling route sets using that signalling route set parameter set,consider if this can be done. If you want only certain signalling routesets to have different values in the signalling route set parameters,you should create a new signalling route set parameter set andattach it to those signalling route sets.

You can output all signalling route sets and the signalling route setparameter sets they are using with the following command.

ZNRI:NA0;

If you only want to modify the values of a certain signalling route setparameter set, continue to the next step, but if you want to createnew signalling route set parameter set, continue from Creating newsignalling route set parameter set.

2. Modify values of signalling route set parameter set (NNM)

ZNNM:<signalling route set parameter set number>,<signalling route set parameter set name>,<parametergroup>:<parameter number>=<parameter value>;

For more information on the parameters, see Signalling route setparameters.

3. Deactivate signalling route sets using the modified parameterset (NVC)

The new values of the parameter set become active until thesignalling route set that uses the parameter set is first deactivatedand activated again.

ZNVC:<signalling network>,<signalling point code>:<signalling transfer point network>,<signallingtransfer point code>:INA;

DN02143262Issue 16-1 en30/01/2009



4. Activate signalling route sets using the modified parameter set(NVC)

ZNVC:<signalling network>,<signalling point code>:<signalling transfer point network>,<signallingtransfer point code>:ACT;

18.6 Creating new signalling route set parameter set

Steps

1. Check signalling route sets and the parameter sets they use(NRI)

As the modifying of the values of an existing parameter set affects allsignalling route sets using that signalling route set parameter set,consider if this can be done. If you want only certain signalling routesets to have different values in the signalling route set parameters,you should create a new signalling route set parameter set andattach it to those signalling route sets.

You can output all signalling route sets and the signalling route setparameter sets they are using with the following command.

ZNRI:NA0;

If you just want to modify the values of a certain signalling route setparameter set, continue from Modifying the values of signalling routeset parameter set, but if you want to create new signalling route setparameter set, continue to the next step.

2. Copy existing signalling route set parameter set with a newname (NNE)

The best way to create a new signalling route set parameter set is tocopy an old parameter set with a new name. Choose the bestsuitable parameter set to be the source parameter set.

ZNNE:<source signalling route set parameter setnumber>,<source signalling route set parameter setname>:<signalling route set parameter set number>,<signalling route set parameter set name>;

3. Modify values of the new signalling route set parameter set(NNM)


30/01/2009


ZNNM:<signalling route set parameter set number>,<signalling route set parameter set name>,<parametergroup>:<parameter number>=<parameter value>;

For more information on the parameters, see Signalling route setparameters.

4. Change parameter set of signalling route set (NRB)

Replace the existing parameter set of the signalling route set withthe new signalling route set parameter set.

ZNRB:<signalling network>,<signalling point codes>:PARA=<parameter set number>;

Example Creating new signalling route set parameter set

With the following example we create a new signalling route set parameterset with name MIKA (number 7) by copying an existing parameter setnumber 0 (ITU-T). We change the value of the parameter D2(TFC_DENIED) to be YES. Then we change the signalling route sets insignalling network NA0 leading to signalling point 300 to use thisparameter set.

1. Check the signalling route sets and the parameter sets they use.

2. Copy one of the existing signalling route set parameter set with anew name.

ZNNE:0,:7,MIKA;

3. Modify the values of the new signalling route set parameter set.

ZNNM:7,MIKA,D:D2=Y;

4. Change the parameter set of the signalling route set.

ZNRB:NA0,300:PARA=7;

18.7 Setting/modifying MTP level signalling trafficrestrictions

Before you start

You do not have to define the policing at the same time when configuringthe signalling network. You can do it later when you see how the network isworking.

DN02143262Issue 16-1 en30/01/2009



Plan carefully the needed traffic restrictions. For more information, seeMTP level signalling network.

Before setting any traffic restrictions it is necessary to plan carefully whatkind of signalling traffic you want to allow and deny. Remember thefollowing issues:

. When signalling traffic is denied in MTP level, the SCCP levelsignalling is also denied.

. If STP messages coming from a certain node are denied (nottransferred) it is possible that the node in question is not able to sendany messages to any direction (e.g. when links to some otherdirection are down).

. It is also possible to set reports from the STP traffic to check if trafficrestrictions are necessary.

. You cannot remove a signalling route set which is included in thetraffic restrictions.

When you want to change the existing traffic restrictions, there might beneed for removing some traffic restrictions. Before you can remove anMTP signalling point, you have to clear all traffic restrictions that are set tothe MTP signalling point.

Steps

1. Check existing signalling traffic restriction data (NRT)

When you are going to modify signalling traffic restrictions, it isreasonable to first check the existing restrictions, just to ensure thatyou are removing the appropriate restrictions, and consider whateffects the removing has on your network.

ZNRT::<signalling network>;

2. Modify signalling traffic restriction data (NRS)

ZNRS:<policing method>:<signalling network>,<originating/adjacent point codes>,<destinationpoint codes>:<STP message treatment>;

3. Check signalling traffic restriction data (NRT)

ZNRT::<signalling network>;


30/01/2009


18.8 Modifying MTP level signalling traffic load sharing

Purpose

With MTP level signalling traffic load sharing you can share the signallingtraffic between signalling routes and between signalling links belonging tothe same link set.

Within a signalling link set, load sharing is implemented so that itautomatically covers all links that are in active state. The priority of asignalling link does not affect the load sharing system.

Load sharing between signalling routes takes effect only after you haveallowed load sharing by defining the same priority for all signalling routesand by allowing load sharing in that route set.

Before you start

Before setting the load sharing, plan carefully which kind of load sharing issuitable in the signalling network. For more information, see MTP levelsignalling network.

Steps

1. Check signalling route priorities and load sharing status (NRI)

ZNRI:<signalling network>, <signalling point code>;

2. Check MTP load sharing data (NEO)

Check which signalling links transmit each of the Signalling LinkSelection Field (SLS) values. You can use this command toseparately interrogate the load sharing data concerning eithermessages generated by the own signalling point or STP signallingtraffic (for example, for STP traffic according to the ANSI standards,the load sharing system is different).

ZNEO;

3. Modify signalling route priority, if needed (NRE)

The priority can vary between 0-7, the primary priority being 7.

DN02143262Issue 16-1 en30/01/2009



ZNRE:<signalling network>, <signalling point code>:<signalling transfer point network>, <signallingtransfer point code>, <new signalling routepriority>;

4. Allow load sharing in the signalling route set, if needed (NRB)

If you want to activate the load sharing and in the signalling route setin question it is not already allowed (output of the NRI command),you have to change the load sharing status.

ZNRB:<signalling network>, <signalling point codes>:LOAD=<load sharing status>;

18.9 Using the signalling link set of another signallingnetwork

Before you start

If there is need to use more than one network indicator (e.g. NA0, NA1 andIN0), it is possible to utilise the signalling link set of any other network.

This means that any signalling network can use the signalling link sets ofany other signalling network. In other words, there is a link set betweentwo network elements but there are two or more route sets using the samelink set (see following example).

For more information, see MTP level signalling network.

Note

This feature is possible only between two IPA2800 network elements.

This kind of arrangement is reasonable to use for example for backupconnections or when traffic between two network elements in a certainsignalling network is low.

Steps

1. Create own signalling point to the signalling network which youwant to use the signalling link set of another signalling network(NRP)


30/01/2009


ZNRP:<signalling network>, <signalling point code>,<signalling point name>, <own signalling pointhandling>: <ss7 standard>: <number of spc subfields>:<spc subfield lengths>;

2. Create signalling route set to the signalling network which isusing the signalling link set defined to the another signallingnetwork (NRC)

ZNRC:<signalling network>, <signalling point code>,<signalling point name>, <parameter set number>,<load sharing status>, <restriction status>:<signalling transfer point network>, <signallingtransfer point code>, <signalling transfer pointname>, <signalling route priority>;

3. Create route set to the destination point like normal STP route(NRC)

ZNRC:<signalling network>, <signalling point code>,<signalling point name>, <parameter set number>,<load sharing status>, <restriction status>:<signalling transfer point network>, <signallingtransfer point code>, <signalling transfer pointname>, <signalling route priority>;

Example Using link set of another signalling network

This example presents how and when it is useful to use a link set ofanother network.

SP signalling point

Figure 24. Example network where one network element belongs to twosignalling networks (NA0 and NA1)

NA0:SP=234

NA1:SP=1234

NA0:SP=123

SP A

NA1:SP=1456

SP B SP C

NA1:SP=1123

DN02143262Issue 16-1 en30/01/2009



The example network consists of the following network elements

. signalling point A, which SPC in NA0 is 123 and in NA1 is 1123

. signalling point B, which SPC in NA0 is 234 and in NA1 is 1234

. signalling point C, which SPC in NA1 is 1456.

In the example, network element C operates only in network NA1. Networkelements A and B are mainly working in network NA0, though they havesome traffic in network NA1. Signalling traffic from A to C is so low that it isnot economical to configure a link and link set also to network NA1between A and B. In this case it is possible to utilise the link set defined forNA0 between A and B for NA1 network traffic as follows.

Create own point to NA1 signalling network in SP A:

ZNRP:NA1,1123,S1123,STP:STAND=ITU-T:1:;

Create route set in NA1 network to SP B. This uses the link set defined forNA0.

ZNRC:NA1,1234,S1234,0,D,N:NA0,234,SP234,7;

Create route set to SP C like a normal STP route:

ZNRC:NA1,1456,S1456,0,D,N:NA1,1234,S1234,7;

18.10 Removing an MTP signalling point

Purpose

This procedure describes how to remove an MTP signalling point. You canfollow these steps also when you only want to remove certain signallinglinks, signalling routes or signalling route sets.

Before you start

Before removing MTP level signalling configuration the upper level userparts (e.g. SCCP) have to be removed. See Removing SCCP signallingpoint and/or subsystem from own signalling point.

Steps

1. Deactivate the signalling route (NVC)


30/01/2009


ZNVC:NA0,312::INA;

2. Deny the activation of the signalling route (NVD)

ZNVD:NA0,312;

3. Deactivate the signalling links (NLC)

ZNLC:12&13,INA;

4. Deny the activation of signalling links (NLD)

ZNLD:12&13;

5. Check that there is no policing (NRT)

Check with the NRT command that there is no policing defined to thesignalling point which you are removing.

6. Remove the policing, if needed (NRS).

You can remove the policing with the NRS command.

ZNRS:A:NA0,312,:A;

ZNRS:O:NA0,312,:A;

7. Delete signalling route set (NRD)

ZNRD:NA0,312,BSC2;

8. Delete ATM/TDM signalling links

a. Delete signalling links from the link set (NSR)

ZNSR:NA0,312,BS312:12; The last link cannot be deletedthis way.

b. Delete signalling link set (NSD)

c. Delete signalling links (NCD)

ZNCD:12;

9. Delete IP signalling links

Delete the signalling link set (NSD)

Delete the signalling link set with the command NSD.

DN02143262Issue 16-1 en30/01/2009




30/01/2009


19 Optimizing SCCP configuration

19.1 Modifying SCCP signalling point parameter set

Steps

1. Check SCCP signalling points and the parameter sets they use(NFI)

As the modifying of the values of an existing SCCP signalling pointparameter set affects all SCCP signalling points using thatparameter set, consider whether this can be done. If you want only acertain group of SCCP signalling points to have different values forthe SCCP signalling point parameters, you should create a newSCCP signalling point parameter set and attach it to those SCCPsignalling points.

You can output all known SCCP signalling points and the SCCPsignalling point parameter sets they are using with the followingcommand.

ZNFI:;

If you want to create a new SCCP signalling point parameter set, seeCreating new SCCP signalling point parameter set.

2. Modify values of SCCP signalling point parameter set (OCM)

ZOCM:<signalling point parameter set number>:<parameter number>,<parameter value>;

For more information on the parameters, see SCCP signalling pointparameters.

DN02143262Issue 16-1 en30/01/2009


Optimizing SCCP configuration

19.2 Creating new SCCP signalling point parameter set

Steps

1. Check SCCP signalling points and the parameter sets they use(NFI)

As the modifying of the values of an existing SCCP signalling pointparameter set affects all SCCP signalling points using thatparameter set, consider whether this can be done. If you want only acertain group of SCCP signalling points to have different values forthe SCCP signalling point parameters, you should create a newSCCP signalling point parameter set and attach it to those SCCPsignalling points.

You can output all known SCCP signalling points and the SCCPsignalling point parameter sets they are using with the followingcommand.

ZNFI;

If you only want to modify the values of a certain SCCP signallingpoint parameter set, see Modifying SCCP signalling point parameterset.

2. Copy existing SCCP signalling point parameter set with a newname (OCE)

The best way to create a new SCCP signalling point parameter set isto copy an old parameter set with a new name. Choose the bestsuitable parameter set to be the source parameter set.

ZOCE:<source signalling point parameter set number>:<signalling point parameter set number>,<signallingpoint parameter set name>;

3. Modify values of the new SCCP signalling point parameter set(OCM)

ZOCM:<signalling point parameter set number>:<parameter number>,<parameter value>;

For more information on the parameters, see SCCP signalling pointparameters.


30/01/2009


4. Inactivate the SCCP signalling point you want to use the newparameter set (NGC)

ZNGC:<signalling network>,<signalling point codes>:INA;

5. Change parameter set of SCCP signalling point (NFL)

Replace the existing parameter set of the SCCP signalling point linkwith the new SCCP signalling point parameter set.

ZNFL:<signalling network>,<signalling point codes>:<signalling point parameter set number>;

6. Activate the SCCP signalling point you want to use the newparameter set (NGC)

ZNGC:<signalling network>,<signalling point codes>:ACT;

Example Creating new SCCP signalling point parameter set

With the following example we create a new SCCP signalling pointparameter set with name MIKA (number 4) by copying an existingparameter set number 2 (WHITE). We change the value of the parameter3 (timer Q714_T_IAR) to be 300 s. Then we change the own SCCPsignalling point to use this parameter set towards the signalling point 300in signalling network NA0.

1. Check SCCP signalling points and the parameter sets they use.

ZNFI;

2. Copy existing SCCP signalling point parameter set with a new name.

ZOCE:2:4,MIKA;

3. Modify values of the new SCCP signalling point parameter set.

ZOCM:4:3,300;

4. Inactivate the SCCP signalling point you want to use the newparameter set.

ZNGC:NA0,300:INA;

5. Change parameter set of SCCP signalling point.

ZNFL:NA0,300:4;

DN02143262Issue 16-1 en30/01/2009



6. Activate the SCCP signalling point you want to use the newparameter set.

ZNGC:NA0,300:ACT;

19.3 Defining SCCP signalling point and/or subsystemto own signalling point

Purpose

This procedure describes how to add a local or remote SCCP signallingpoint and/or local or remote SCCP subsystems to the own signalling point.

Before you start

Before you can carry out this procedure, you have to know the signallingpoint code of the local or remote signalling point and the name of the localor remote subsystem to be added.

Note that the signalling point has to be defined at the MTP level, before itcan be added to the SCCP configuration.

Steps

1. Check existing SCCP signalling points and subsystems (NFI,NFJ)

To output the defined SCCP signalling point, use the command

ZNFI:;

To output the defined SCCP subsystems, use the command

ZNFJ:;

2. Define SCCP signalling point and needed subsystems, ifneeded (NFD)

If the SCCP signalling point is already defined to the own signallingpoint and you only want to add new subsystems, continue from thenext step.

With the following command you can define the new SCCPsignalling point and up to 5 subsystems in it.


30/01/2009


ZNFD:<signalling network>,<signalling point code>,<signalling point parameter set number>:<subsystemnumber>,<subsystem name>,<subsystem parameter setnumber>,Y;

3. Add local or remote subsystems to own signalling point (NFB)

ZNFB:<signalling network>,<signalling point codes>:<subsystem number>,<subsystem name>,<subsystemparameter set number>,Y;

4. Activate defined SCCP signalling point, if needed (NGC)

When you have defined a new SCCP signalling point you have toactivate it, before you can activate the new SCCP subsystems.

ZNGC:<signalling network>,<signalling point codes>:ACT;

5. Activate defined SCCP subsystems (NHC)

ZNHC:<signalling network>,<signalling point codes>:<subsystem>: ACT;

19.4 Removing SCCP signalling point and/or subsystemfrom own signalling point

Before you start

Before you can carry out this procedure, you have to know the signallingpoint code of the local or remote signalling point and the name of the localor remote subsystem to be removed.

Steps

1. Check existing SCCP signalling points and subsystems (NFIand NFJ)

To output the defined SCCP signalling point, use the command

ZNFI:;

To output the defined SCCP subsystems, use the command

DN02143262Issue 16-1 en30/01/2009



ZNFJ:;

2. Deactivate the SCCP subsystems that you want to remove(NHC)

ZNHC:<signalling network>,<signalling point codes>:<subsystem>: INA;

3. Remove local or remote subsystems from the own signallingpoint (NFT)

ZNFT:<signalling network>,<signalling point codes>:<subsystem number>;

4. Deactivate the SCCP signalling point that you want to remove, ifneeded (NGC)

You have to deactivate all subsystems before you can deactivate theSCCP signalling point.

ZNGC:<signalling network>, <signalling point codes>:INA;

5. Remove the local or remote SCCP signalling point from the ownsignalling point, if needed (NFR)

ZNFR:<signalling network>,<signalling point codes>;

19.5 Modifying the values of SCCP subsystemparameter set

Steps

1. Check SCCP subsystems and the parameter sets they use(NFJ)

As the modifying of the values of an existing SCCP subsystemparameter set affects all SCCP subsystems using that parameterset, consider if this can be done. If you want only a certain group ofSCCP subsystems to have different values in the SCCP subsystemparameters, you should create a new SCCP subsystem parameterset and attach it to those SCCP subsystems.


30/01/2009


You can output all known SCCP subsystems and the SCCPsubsystem parameter sets they are using with the followingcommand.

ZNFJ;

If you want to create a new SCCP subsystem parameter set, seeCreating new SCCP subsystem parameter set.

2. Modify values of SCCP subsystem parameter set (OCN)

ZOCN:<subsystem parameter set number>:<parameternumber>,<parameter value>;

19.6 Creating new SCCP subsystem parameter set

Steps

1. Check SCCP subsystems and the parameter sets they use(NFJ)

As the modifying of the values of an existing SCCP subsystemparameter set affects all SCCP subsystems using that parameterset, consider if this can be done. If you want only a certain group ofSCCP subsystems to have different values in the SCCP subsystemparameters, you should create a new SCCP subsystem parameterset and attach it to those SCCP subsystems.

You can output all known SCCP subsystems and the SCCPsubsystem parameter sets they are using with the followingcommand.

ZNFJ;

If you only want to modify the values of a certain SCCP subsystemparameter set, see Modifying the values of SCCP subsystemparameter set.

2. Copy existing SCCP subsystem parameter set with a new name(OCF)

The best way to create a new SCCP subsystem parameter set is tocopy an old parameter set with a new name. Choose the bestsuitable parameter set to be the source parameter set.

DN02143262Issue 16-1 en30/01/2009



ZOCF:<source subsystem parameter set number>:<subsystem parameter set number>,<subsystemparameter set name>;

3. Modify values of the new SCCP subsystem parameter set (OCN)

ZOCN:<subsystem parameter set number>:<parameternumber>,<parameter value>;

For more information on the parameters, see SCCP subsystemparameters.

4. Inactivate the SCCP subsystem in which you want to use thecreated parameter set (NHC)

ZNHC:<signalling network>,<signalling point codes>:<subsystem>:INA;

5. Change the parameter set of the SCCP subsystem (NFM)

Replace the existing parameter set of the SCCP subsystems withthe new SCCP subsystem parameter set.

ZNFM:<signalling network>,<signalling point code>:<subsystem numbers>:<subsystem parameter setnumber>;

6. Activate the SCCP subsystem in which you want to use thecreated parameter set (NHC)

ZNHC:<signalling network>,<signalling point codes>:<subsystem>:ACT;

Example Creating new SCCP subsystem parameter set

With the following example we create a new SCCP subsystem parameterset with name MIKA (number 4) by copying an existing parameter setnumber 0 (GENER). We change the value of the parameter 2 (timerQ714_T_IGN_SST) to be 70 s. Then we change the own SCCP signallingpoint to use this parameter set towards the subsystem number 06 (MAPH)located signalling point 300 in signalling network NA0.

1. Check the SCCP subsystems and the parameter sets they use.

ZNFJ;

2. Copy existing SCCP subsystem parameter set with a new name.


30/01/2009


ZOCF:0:4,MIKA;

3. Modify values of the new SCCP subsystem parameter set.

ZOCN:4:2,70:;

4. Inactivate the SCCP subsystem you want to use the createdparameter set.

ZNHC:NA0,300:06:INA;

5. Change parameter set of SCCP subsystem.

ZNFM:NA0,300:06:4;

6. Activate the SCCP subsystem you want to use the createdparameter set.

ZNHC:NA0,300:06:ACT;

19.7 Setting/modifying broadcasts of local SCCPsubsystem

Purpose

This procedure describes how to set broadcast status of SCCPsubsystems.

There are two different kind of broadcasts you can set:

. The local broadcast status (the OBC command) is used to inform theSCCP subsystems of the own signalling point about changes in theSCCP subsystems of the remote signalling points.

. The broadcast status (the OBM command) is used to inform othersignalling points about changes in the SCCP subsystems of the ownsignalling point or the SCCP subsystems of the signalling pointsconnected to the own signalling point.


Before you start

When setting broadcasts, consider carefully what broadcasts are needed.If the broadcasts are set wrong or there are needless broadcasts, it can setthe alarm 2247 or cause unnecessary traffic in the signalling network.

DN02143262Issue 16-1 en30/01/2009



Steps

1. Interrogate existing broadcasts (OBL, OBI)

ZOBL:;

ZOBI:;

2. Set local broadcast status (OBC)

ZOBC:<network of affected subsystem>,<signallingpoint code of affected subsystem>,<affected subsystemnumber>:<network of local subsystem>,<localsubsystem number>:<status>;

3. Set broadcast status (OBM)

ZOBM:<network of affected subsystem>,<signallingpoint code of affected subsystem>,<affected subsystemnumber>:<network of concerned signalling point>,<concerned signalling point code>:<status>;

19.8 Setting/modifying signalling point based trafficrestrictions

Before you start

Before setting any SCCP level signalling traffic restrictions, it is necessaryto plan carefully what kind of signalling traffic you want to allow and deny.Remember that the restrictions can affect the operation of the wholesignalling network. For more information, see section 6 Plan SCCP levelSTP traffic restrictions in SCCP level signalling network.

For the whole topic summary, see SS7 signalling.

Steps

1. Inactivate SCCP level signalling traffic restrictions (ODS)

ZODS:INA;

2. Check and copy the existing MTP level signalling trafficrestrictions to correspond to the SCCP level, if suitable (NRT,ODC)


30/01/2009


Before you set any restrictions on SCCP level, it is instructive tocheck the restrictions defined at MTP level. If there are restrictionsdefined at MTP level meet your needs, you can copy them tocorrespond to the SCCP level.

To check the MTP level restrictions use the command NRT.

Note that if the type of the MTP level restriction is UNAUTHORIZED, itis not possible to copy it to correspond to the SCCP level.

According to the output of the previous command, consider whetherthe existing restrictions are suitable for the SCCP level, if yes, copythem with the following command:

ZODC:<screening method>:<signalling network>,<originating/adjacent point codes>;

3. Modify SCCP level signalling traffic restrictions, if needed(ODM)

In this step, you either define new or modify the existing SCCP levelsignalling traffic restrictions. For example, if you copied some MTPlevel restrictions in the previous step, you may want to make somemodifications to them on SCCP level.

Note that when defining SCCP level signalling traffic restrictions, it ispossible to set an alarm when an unauthorized message is received.

ZODM:<screening method>:<signalling network>,<originating/adjacent point codes>:<signallingnetwork>,<destination point codes>:<STP messagetreatment>;

4. Activate SCCP level signalling traffic restrictions (ODS)

ZODS:ACT;

19.9 Calling GT checking based traffic restrictions

Steps

1. Modify SCCP level signalling traffic restrictions according tothe calling GTI, if needed (OCM)

DN02143262Issue 16-1 en30/01/2009



By modifying the ALLOWED_GTI_VALUES parameter in the SCCPSignalling Point Parameter Set of the parameter set defined for thedestination point code (DPC), it is possible to define which GTIvalues are allowed in the calling address.

ZOCM:<signalling point parameter set>:<parameternumber>,<parameter value>;

2. Modify SCCP level signalling traffic restrictions according tothe calling GT, if needed (OCM)

Because the restrictions according to the GT are based on theexisting global title analysis, the first is to check the existing analysiswith the NBI command.

To activate the restrictions so that only STP messages with knownGT translation selector values are transmitted, give the value 1(YES). To inactivate, give the value 0 (NO), for theANALYSE_ROOT_OF_CALLING_GT parameter in the SCCP SignallingPoint Parameter Set, (analysing takes effect only for the STPmessages), with the following command:

ZOCM:<signalling point parameter set>:22,<parametervalue>:;

Further information

Example Setting SCCP level signalling traffic restrictions

In this example, we copy the existing MTP level signalling trafficrestrictions to correspond to the SCCP level signalling traffic. After this, wemodify the SCCP level signalling traffic restrictions to concern moresignalling points than the existing MTP restrictions. We also set restrictionsof the GTI and GT types. The example commands are given in the NE301network element of the example network.


30/01/2009


Figure 25. Example network where the SCCP level signalling traffic restrictionsare configured

1. Activate SCCP level signalling traffic restrictions

ZODS:ACT;

2. Check and copy the existing MTP level signalling traffic restrictionsto correspond to the SCCP level

ZNRT:O:NA0,301;

In our example case, the output of the command could be thefollowing:

STP ACCESS BETWEEN THE FOLLOWING OPC AND DPC COMBINATIONS

OPC (H) TREATMENT / DPC (H)

--------------------------------------------------------------

0101 DISCARDED / 0103

0103 DISCARDED / 0101

COMMAND EXECUTED

For example, if you want to discard all SCCP level STP messagescoming from signalling point NE101 (101H) and addressed to NE103(103H), you can copy the existing MTP restrictions with the followingcommands:

ZODC:O:NA0,101;

NE101NA0SPC=101H

NE302NA0SPC=302H

NE301NA0SPC=301H

NE103NA0SPC=103H

DN02143262Issue 16-1 en30/01/2009



ZODC:O:NA0,103;

After copying you can check the result by giving the followingcommand:

ZODI:O:NA0,:;

You get the following output:

INQUIRING SCCP SCREENING

ORIGINATING: DESTINATION:

NET SP CODE H/D NET SP CODE (HEX) TREATMENT

--- ------------------ --- ------------------ ----------------

NA0 0101/00257 NA0 0103 DISCARDED/ALARM


COMMAND EXECUTED

3. Modify SCCP level signalling traffic restrictions

For example, if you want to set the SCCP screening so thatmessages originating from NE302 (302H) are discarded when theyare addressed to NE103 (103H), and you do not want an alarm to begenerated, use the following command:

ZODM:O:NA0,302:NA0,103:U;


MODIFYING SCCP SCREENING

ORIGINATING: DESTINATION:


--- ------------------ --- ------------------ ------------

NA0 0302/00770 NA0 0103 DISCARDED

COMMAND EXECUTED

And for example, if you want that messages coming from theadjacent signalling point (link set) NE103 (103H) are discarded andthat an alarm is set when the destination is NE302 (302H), thecommand would be

ZODM:A:NA0,103:NA0,302:D;

And the output would be:

MODIFYING SCCP SCREENING

ADJACENT: DESTINATION:


30/01/2009



--- ------------------ --- ------------------ ---------------


COMMAND EXECUTED

4. Modify SCCP level signalling traffic restrictions according to thecalling GTI

For example, if you want to deny the use of the GTI value 2 in thecalling address of the STP messages, use the following command:

ZOCM:0:23,102;

5. Modify SCCP level signalling traffic restrictions according to thecalling GT

To set the screening so that only STP messages with known GTtranslation selector values are transmitted, give value 1 (YES) for theANALYSE_ROOT_OF_CALLING_GT parameter in the SCCPSignalling Point Parameter Set, (analysing takes effect only for theSTP messages) with the following command:

ZOCM:0:22,1:;


MODIFYING SCCP SIGNALLING POINT PARAMETER SET

SET NUMBER: 00000 SET NAME: BLUE

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

NO: NAME OLD VALUE NEW VALUE

--- ---- --------- ---------

22 ANALYSE_ROOT_OF_CALLING_GT NO YES

COMMAND EXECUTED

19.10 Setting/modifying GT based traffic restrictions

Steps

1. Activate/deactivate SCCP level signalling traffic restrictions

Activate/deactivate SCCP level signalling traffic restrictions basedon calling and called GT (ODG)

ZODG:<screening status>;

2. Activate GT screening for called GT translation result records

DN02143262Issue 16-1 en30/01/2009



Activate GT screening for called GT translation result records whichyou need to use in GT screening (ODT):

ZODT:<called GTT result>:<ACT/INA>;

3. Create SCCP calling GT translation result for screening (NIE)

ZNIE:<result record number>;

4. Create SCCP calling GT analysis (NIA)

Create calling GT analysis leading to the created calling GTtranslation result record (NIA):

ZNIA:<ss7 standard and global title indicator>,<lastglobal title element to be analyzed>:<translationtype>,<numbering plan>,<nature of addressindicator>:<digits>:<result record index forscreening>;

5. Modify GT screening data (ODN)

In this step, you can either define new or modify the existing SCCPlevel signalling traffic restrictions based on calling GT and called GTtranslation results.

Note that when defining SCCP level signalling traffic restrictions, it ispossible to set an alarm when an unauthorised message is received.ZODN:<calling GTT result>:<called GTT result>:<STPmessage treatment>;

Further information

Example Setting SCCP level signalling traffic restrictions based oncalling GT and called GT

In this example, you modify the SCCP level signalling traffic restrictionsbased on the calling GTand called GT translation result combination. First,we activate SCCP level GT screening activity and GT screening for acalled GTT result. After this, we create the calling GTT result and callingGTanalysis leading to that result. Finally, we modify the SCCP level trafficrestrictions based on the calling GTT and called GTT result combination.The example commands are given in the NE101 network element of theexample network, as stated in Figure Example network, where BSC2 ismoved under MSC2.


30/01/2009


In this example, we do not want to use NE101 to deliver SCCP levelsignalling traffic coming from calling GT:

TT=0

NP=1

NAI=4

digits=4641

And going to called GT:

TT=0

NP=1

NAI=4

digits=35850

The desired screening method is that the message has to be deleted andan alarm set.

1. Activate SCCP level GT screening

ZODG:ACT;

2. Activate GT screening for called GT translation result record

Check the result record for the following called GT:

TT=0

NP=1

NAI=4

digits=35850; by giving the the following command:

ZNBI;

In our example case, the output of the command could be thefollowing:

DN02143262Issue 16-1 en30/01/2009



INTERROGATE OR SEARCH GLOBAL TITLE ANALYSIS

DIGITS: * ... FFFFFFFFFFFFFFFFFFFFFFFF

RESULT: 00001 ... 05119

ROOT PARAMETER VALUE DESCRIPTIONS

------------------------------------------------

SS7= ITU ... ITU-T RECOMMENDATION Q.713

GTI= 4 ... GT INCLUDES TT, ES, NP AND NAI

TT = 0 ... TRANSLATION TYPE NOT USED

NP = 1 ... ISDN/TELEPHONY (REC. E.164/E.163)

NAI= 4 ... INTERNATIONAL NUMBER

RESULT ANALYSIS

SS7 GTI TT NP NAI DIGITS RECORD TYPE

---- --- --- --- --- ------------------------ ------ --------

ITU 4 0 1 4 12345 1 BASIC

ITU 4 0 1 4 37 2 BASIC

ITU 4 0 1 4 35850 3 BASIC

The analysis leads to the GT translation result record 3. Activate GTscreening for that result record 3 by giving the ZODT command:

ZODT:3:ACT;

After activating, you can check the result by giving the followingcommand:

ZODR;


DX 220 MAGIA 2004-07-16 09:14:05

INTERROGATING GT SCREENING ACTIVATION STATUS OF CALLED GTT RESULTS

CLD RESULT STATUS

---------- --------

00003 ACTIVE

SCCP GLOBAL TITLE SCREENING IS ACTIVE

COMMAND EXECUTED

3. Create calling GT translation result record

ZNIE;

After creation, you can check the result by giving the followingcommand:

ZNIL;


30/01/2009



INTERROGATING CALLING GLOBAL TITLE TRANSLATION RESULTS

RESULT RECORD

-------------

00001

COMMAND EXECUTED

4. Create calling GT analysis leading to the created calling GTT resultrecord

ZNIA:ITU=4,LAST=DIG:TT=0,NP=1,NAI=4:4641:1;

After creation, you can check the result by giving the followingcommand:

ZNIJ;


INTERROGATING SCCP CALLING GT ANALYSES

DIGITS: * ... FFFFFFFFFFFFFFFFFFFFFFFF

SCREENING RESULT: 00001 ... 00255

ROUTING RESULT: 00001 ... 00255

ROOT PARAMETER VALUE DESCRIPTIONS

------------------------------------------------

SS7= ITU ... ITU-T RECOMMENDATION Q.713

GTI= 4 ... GT INCLUDES TT, ES, NP AND NAI

TT = 0 ... TRANSLATION TYPE NOT USED

NP = 1 ... ISDN/TELEPHONY (REC. E.164/E.163)

NAI= 4 ... INTERNATIONAL NUMBER

SCR RTG ANALYSIS

SS7 GTI TT NP NAI DIGITS RECORD RECORD TYPE

---- --- --- --- --- ------------------------ ------ ------ --------

ITU 4 0 1 4 4641 1 0 BASIC

NUMBER OF DISPLAYED ANALYSIS = 1

NUMBER OF DISPLAYED ROOTS = 1

COMMAND EXECUTED

5. Create GT screening between the calling GTT and called GTTresults

ZODN:1:3:D;

DN02143262Issue 16-1 en30/01/2009



After creation you can check the result by giving the followingcommand.

ZODF;


INTERROGATING SCCP GLOBAL TITLE SCREENING DATA

CLG RESULT CLD RESULTS

---------- -----------

00001 AUTHORIZED : 00001, 00002

DISCARD :

ALARM :

DISCARD+ALARM : 00003

DEFAULT TREATMENT IS AUTHORIZED

UNKNOWN AUTHORIZED : 00001, 00002, 00003

DISCARD :

ALARM :

DISCARD+ALARM :

DEFAULT TREATMENT IS AUTHORIZED

SCCP GLOBAL TITLE SCREENING IS ACTIVE

COMMAND EXECUTED

Example Removing SCCP level signalling traffic restrictions

To remove all SCCP level signalling traffic restrictions, first set theparameters in the SCCP Signalling Point Parameter Set so that neither theGTI nor GT type of screening is done (if there are these types ofrestrictions in use). Then deactivate the OPC/DPC and linkset/DPC typesof screening with the ODS command (if there are these types of screeningin use) and the GT screening with the ODG command (if that type ofscreening is in use).

1. Deactivate the calling GT type SCCP restrictions.

ZOCM:0:22,0;

2. Deactivate the calling GTI type SCCP restrictions

In the following command, add GTI value 2 to the list of allowedvalues.

ZOCM:0:23,202;

3. Deactivate the OPC/DPC and linkset/DPC type SCCP restrictions

ZODS:INA;


30/01/2009


4. Deactivate the SCCP restrictions based on GT

ZODG:INA;

19.11 Creating/modifying GT translation result and GTmodification

Purpose

With this procedure you can modify an existing global title (GT) translationresult or create a new one. You can modify an existing or define a newglobal title modification for a certain global title translation result. Thetranslation result refers to those routes where SCCP level signallingmessages can be transmitted. You have to define translation result for allsignalling points where there will be SCCP level signalling traffic. Therouting of SCCP level traffic can be based on a global title (GT) or on asubsystem number (SSN).

It is also possible to create alternative routes and use them as backuproutes or use the alternative route for load sharing.

Before you start

Before creating or modifying a global title translation result, you have toplan whether the routing is based on a global title (GT) or on a subsystemnumber (SSN). Also, if you are defining global title modification, it has to beplanned carefully before configuration.

Note

All signalling points that are meant to handle SCCP level traffic must bedefined on the MTP level of the own signalling point.

Steps

1. Check existing GT translation results (NAI)

Before creating any new global title translation result, it is reasonableto check existing translation results, to ensure that there is noneeded translation result already defined.

ZNAI;

DN02143262Issue 16-1 en30/01/2009



2. Interrogate existing global title modification records, if needed(NAX)

Before creating any new global title modification, it is reasonable tocheck existing modifications, to ensure that there is no neededmodification already defined.

ZNAX;

3. Create or modify global title modification record, if needed(NAA or NAS)

To create a new global title modification record, use the commandNAA.(Not supported in MGW!)

To modify an existing global title modification record, use thecommand NAS.

4. Create new or modify existing translation result (NAC or NAM)

To create a new translation result, use the command NAC.

To modify existing translation result, use the command NAM.

19.12 Creating global title analysis for called GT

Purpose

This procedure describes how to modify or create global title (GT) analysisfor the called GT.

Before you start

Before creating any global title analysis it is important to plan carefully theneeded GT analysis. For more information, see SCCP level signallingnetwork.

Steps

1. Check existing GT translation results (NAI)


30/01/2009


Before creating a new global title analysis, check the number of thetranslation result where you want to use the global title analysis (theanalysis is attached to a certain translation result). It is reasonable tocheck if the translation result already uses a GT analysis and if thechange has effect on it.

ZNAI;

2. Check existing GT analyses (NBI)

Before creating a new global title analysis, it is reasonable to checkexisting analyses, to ensure that there is no needed analyse alreadydefined. If you are going to modify an existing GT analysis, ensurethat the change does not have unwanted effects to the existingtranslation results.

ZNBI:;

3. Create GT analysis (NBC)

ZNBC:<ss7 standard and global title indicator>,<lastglobal title element to be analysed>:<translationtype>,<numbering plan>,<nature of addressindicator>:<digits>:<result record index>;

19.13 Creating calling GT routing configuration

Purpose

With this procedure, you can configure the calling GT based routing. First,you need to check that there are a called GT analysis and a called GTresult for which you need to define the calling GT routing. Then check theAnalyse Calling GTattribute (ACGT) in the called GT result. Last define thecalling GT result and calling GT analysis needed.

For more information, see step Plan SCCP routing based on Calling Partyglobal title in SCCP level signalling network.

DN02143262Issue 16-1 en30/01/2009



Before you start

Before creating or modifying a calling GT translation result, you have toplan whether the routing is based on a global title (GT) or on a subsystemnumber (SSN). Also, if you define the global title modification (shown bythe NAX command), it has to be planned carefully before the configuration.Note that all signalling points that handle SCCP level traffic must bedefined on the MTP level of the own signalling point.


The calling GT analyses are stored in a different analysis tree than thecalled GT analyses.

Steps

1. Check the configuration for the called GT analysis and calledGT analysis results (NBI, NAI)

ZNBI;

ZNAI;

The calling GT analysis is made for specific called GTs only. Withthese commands, you can check if the analysis exists for the calledGT.

See Creating and modifying called GT translation result and GTmodification and Creating global title analysis for called GT.

Check the ACGT (Analyse Calling GT) attribute from the called GTresult (NAI command).

Note that when the calling GT routing is set on for the called GTresult, the GTanalysis made for the calling GT determines where themessage is sent. When a message has a different calling GT to theones configured, the destination in the called GT result is used. So ifyou need specific routing for few calling GTs only, you can minimisethe number of the calling GT analyses as follows:. by defining calling GT analyses for those few calling GTs

and. defining the mostly used destination in the called GT result

2. Modify Analyse Calling GT attribute in the called GT result ifneeded (NAM)


30/01/2009


If NAI command shows that the ACGT is off, set it on with thefollowing command:

ZNAM:<result index>::OPTION:ACGT=Y;

3. Check existing GT translation results for calling GT (NII)

Before creating any new global title translation result, it is advisableto check the existing translation results to ensure that there is noneeded translation result already defined.

ZNII;

4. Create new or modify existing translation result (NIC or NIM)

To create a new translation result, use the NIC command.

To modify an existing translation result, use the NIM command.

5. Check existing GT analyses for calling GTs (NIJ)

Before creating a new global title (GT) analysis for calling GT, checkthe existing analyses to ensure that there is no needed analysisalready defined. Before creating a new calling GT analysis, checkthe number of the calling GT translation results where the calling GTanalysis leads to. Check if the translation result already uses a GTanalysis and if the change has an effect on it.

ZNIJ;

6. Create GT analysis for the calling GT (NIA)

ZNIA:<ss7 standard and global title indicator><lastglobal title element to be analysed>:<translationtype>,<numbering plan>,<nature of addressindicator>:<digits>::<result record index forrouting>;

DN02143262Issue 16-1 en30/01/2009




30/01/2009


20 Deleting SAAL UNI signalling linksPurpose

Note

At Iub interface, the primary tool for deleting SAAL UNI signalling linksis the RNW Object Browser. You should use this tool instead of MMLcommands. To delete a SAAL UNI signalling link using the RNW ObjectBrowser, see Deleting radio network managed objects.

Use this procedure to delete an unnecessary SAAL UNI signalling linkused for AAL2 signalling protocol from the Iub interface between RNC andWCDMA BTS. See also Creating SAAL UNI signalling links.

Steps

1. Set the administrative states of the AAL2 paths controlled bythe signalling link into state LOCKED (LCS)

ZLCS:<interface id>,<VPI>,[<VCI>]:(UNLOCK | LOCK |FLOCK);

The system will now prevent any new user data connections fromentering the specified AAL2 paths. Wait for the administrative statesof the AAL2 paths to change into state LOCKED. The state of thepaths will automatically change into LOCKED, after all the AAL2connections on the path have been terminated.

2. Delete the unnecessary SAAL UNI signalling link (LSD)

ZLSD:<sl interface id>,<sl VPI>,<sl VCI>:[YES|NO];

DN02143262Issue 16-1 en30/01/2009


Deleting SAAL UNI signalling links

Note

Before deleting a SAAL UNI signalling link used for AAL2 signallingprotocol, make sure that there are no active AAL2 connections in theAAL2 paths controlled by the SAAL UNI signalling link you are deleting.You cannot delete the SAAL UNI signalling link used for AAL2 signallingprotocol before all connections have been cleared from the AAL2 userdata paths that the link controls.


30/01/2009


21 Monitoring SS7 signalling networkobjects

Steps

1. Interrogate SS7 network configuration (NET)

To output the created objects of the signalling network configuration,give the following command. In the output you can check createdsignalling route sets, signalling link sets, signalling links and theirstates.

ZNET:;

2. Interrogate signalling route set states (NER)

To check the states of the created signalling route sets, give thefollowing command.

The possible states and their meanings are described in States ofsignalling route sets.

ZNER:;

3. Interrogate and modify signalling route state (NVI, NRI, NVC)

With these commands you can check and modify the states of thecreated signalling routes.

The possible states and their meaning is described in States ofsignalling routes.

a. Interrogate signalling route states (NVI, NRI)

To interrogate the states of all signalling routes in a givensignalling network, give the following command.

ZNVI:<signalling network>,;

DN02143262Issue 16-1 en30/01/2009


Monitoring SS7 signalling network objects

To interrogate the signalling points in a given signallingnetwork and the signalling routes leading to them, give thefollowing command.

ZNRI:<signalling network>,;

b. Change the state of signalling route, if needed (NVC)

ZNVC:<signalling network>, <signalling pointcode>: <signalling transfer point network>,<signalling transfer point code>: <statechange>;

4. Interrogate signalling link set states (NES)

To interrogate the states of all signalling link sets, give the followingcommand.

The possible states and their meaning is described in States ofsignalling link sets.

ZNES:;

You cannot directly change the state of an signalling link set by anycommands. The signalling link set state depends on the state of thesignalling link in that signalling link set.

5. Interrogate and modify signalling link state (NEL, NLI, NLC)

With these commands you can check and modify the states of thecreated signalling links.

The possible states and their meaning is described in States ofsignalling links.

a. Interrogate signalling link states (NEL, NLI)

To interrogate the states of all signalling links, give one of thefollowing commands:

ZNEL:;

or

ZNLI:;

b. Change the state of signalling link, if needed (NLC)

ZNLC:<signalling link numbers>, <state change>;

6. Interrogate MTP level load sharing (NEO)


30/01/2009


To interrogate the current settings of MTP level load sharing definedin own network element, give the following command. You can limitthe output by giving appropriate values for the parameters of thecommand.

For more information, see MTP level signalling network.

ZNEO:<signalling network>, <destination pointcodes>, <message originator>: <sort mode (SLS range/SLS output)>;

7. Interrogate MTP level STP traffic restrictions (NEP)

To interrogate the MTP level STP traffic restrictions, give thefollowing command. You can limit the output by giving appropriatevalues for the parameters of the command.

ZNEP:<authorizing method>: <signalling network>,<incoming direction signalling point code>,<destination point code>;

8. Interrogate and modify SCCP signalling point state (NGI, NGC)

With these commands you can check and change the states of thecreated SCCP signalling points.

The possible states and their meaning is described in States ofSCCP signalling points.

a. Interrogate SCCP signalling point states (NGI)

To interrogate the SCCP signalling point states, give thefollowing command. You can limit the output by givingappropriate values for the parameters of the command.

ZNGI:<signalling network>, <signalling pointcodes>: <display mode>;

b. Change the state of SCCP signalling point, if needed (NGC)

ZNGC:<signalling network>, <signalling pointcodes>: <state change>;

9. Interrogate and modify SCCP subsystem state (NHI, NHC)

With these commands you can check and change the states of thecreated SCCP subsystems.

The possible states and their meaning is described in States ofSCCP subsystems.

DN02143262Issue 16-1 en30/01/2009



a. Interrogate SCCP subsystem states (NHI)

To interrogate the SCCP subsystem states, give the followingcommand. You can limit the output by giving appropriatevalues for the parameters of the command.

ZNHI:<signalling network>, <signalling pointcodes>: <subsystem>;

b. Change the state of SCCP subsystem, if needed (NHC)

ZNHC:<signalling network>, <signalling pointcodes>: <subsystem>: <state change>;

10. Interrogate SCCP subsystem broadcast status (OBL, OBI)

With these commands you can check the local and remote SCCPsubsystems' broadcast status.

a. Interrogate local SCCP subsystem broadcast status (OBL)

To interrogate the local SCCP subsystem broadcast status,give the following command. You can limit the output by givingappropriate values for the parameters of the command.

ZOBL:<network of affected subsystem>,<signalling point code of affected subsystem>,<affected subsystem number>: <network of localsubsystem>, <local subsystem number>: <mode>;

b. Interrogate remote SCCP subsystem broadcast status (OBI)

To interrogate the remote SCCP subsystem broadcast status,give the following command. You can limit the output by givingappropriate values for the parameters of the command.

ZOBI:<network of affected subsystem>,<signalling point code of affected subsystem>,<affected subsystem number>: <network ofconcerned signalling point>, <concernedsignalling point code>: <mode>;


30/01/2009


22 Optimising AAL type 2 signallingPurpose

This procedure provides instructions on how to modify timer values(Timer_ERQ and Timer_REL) to optimise AAL2 signalling. Theparameters are defined in PRFILE, which controls how the functionalitieswork.

Before you start

Note

If the timers expire, AAL2 reset procedure is started for the channel thatwas being established or released.

You can check the current parameter value by using the WOIcommand.

Steps

1. Check the parameter value (WOI). TIMER_ERQ (002:0840)

This parameter defines the waiting time in seconds foroutgoing AAL2 connection establishment on AAL2 signallinglevel.

ZWOI:2,840;. TIMER_REL (002:0841)

This parameter defines the waiting time in seconds for AAL2connection release on AAL2 signalling level.

ZWOI:2,841;

2. Change the parameter value (WOC)

DN02143262Issue 16-1 en30/01/2009


Optimising AAL type 2 signalling

Note

Set the timer value according to your network element responding timeto avoid wasting network element resources.

. TIMER_ERQ (002:0840)

ZWOC:2,840,<value>;. TIMER_REL (002:0841)

ZWOC:2,841,<value>;


30/01/2009


23 Signalling troubleshooting

23.1 MTP and SCCP configuration-related problems

23.1.1 Signalling route goes to or stays in state UA-INR

Description

The signalling route goes to or stays in state UA-INR.

Symptoms

The signalling route goes to or stays in state UA-INR.

Recoveryprocedures

Checking why the signalling route goes to or stays in state UA-INR

Steps

1. Find out the states of adjacent and destination signalling points

State UA-INR means that the signalling route is unavailable becausethe adjacent signalling point has sent a transfer prohibited signal(TFP) to the local signalling point concerning the destination point.

Either the adjacent signalling point has no access to the destinationpoint or the route defined to the destination point goes through thesignalling point that has sent the message.

The routes that are in UA-INR state are periodically tested with routeset test messages (RST). If TFA (transfer allowed) message isreceived as a reply to the RST, the route is considered available. Theroute can temporarily be in the state UA-INR even when there is noparticular fault in the configuration or hardware.

DN02143262Issue 16-1 en30/01/2009


Signalling troubleshooting

If the route is often in this state, the reason has to be cleared with theholder of the adjacent signalling point.

23.1.2 The system sets frequently alarm 0026 SIGNALLING LINK LOADOVER THRESHOLD

Description

The system sets the alarm 0026 when the signalling link load exceeds thesignalling link load threshold value. In some cases the threshold value canbe too small. Then you can change the value.

Symptoms

The system sets frequently the alarm 0026 SIGNALLING LINK LOADOVER THRESHOLD.

Recoveryprocedures

Checking why the system sets frequently the alarm 0026 SIGNALLING LINKLOAD OVER THRESHOLD

Steps

1. Interrogate and follow the load of the signalling links.

Find out what is the reason for the overload.

For more information how to monitor signalling network, seeMonitoring SS7 signalling network objects.

2. Change the value of the signalling link load threshold.

If you think that it is safe to increase the threshold value of the alarm,you can change the value with the NOM command (parameter groupE, parameter E13).

For more information, see Modifying the values of signalling linkparameter set

23.1.3 Signalling link activation succeeds but traffic fails

Description

Signalling link activation succeeds but traffic fails.


30/01/2009


Symptoms

Signalling link activation succeeds but traffic fails.

Recoveryprocedures

Checking why signalling link activation succeeds but traffic fails

Steps

1. Check that all network items are in state AV (available) (NVI,NSI, NLI, NLC)

Check the states of the signalling route set and signalling route byusing the command:

ZNVI:<network indicator>,<sp code>;

Check the state of signalling link set by using the command:

ZNSI:<network indicator>,<sp code>;

Check the state of signalling link by using the command:

ZNLI:<link numbers>;

If the link state is not AV-EX try to activate it with the NLC command.

ZNLC:<link number>,ACT;

2. Check traffic distribution (NEO)

ZNEO:<network indicator>,<sp code>;

The load sharing between links within the link set should be as evenas possible. If one or more links have much more SLS codes thanother links, or if there are some links in the link set in the active state,but with no place in the load sharing table, the load sharing has beencorrupted.

One way to fix the load sharing table is to change the states of somelinks in the link set. The load sharing algorithm tries to spread SLSvalues evenly to all links.

ZNLC:<link number>,INA;

DN02143262Issue 16-1 en30/01/2009



ZNLC:<link number>,ACT;

3. Check that there are services defined for all necessary userparts (NPI)

ZNPI:<network indicator>;

Create missing services with the NPC command.

4. Check if the system has set the alarm 2224 (AHP)

ZAHP::NR=2224;

If the alarm 2224 ERROR IN MSU HANDLING is set, follow thealarm instructions.

23.1.4 All MTP and SCCP level objects are in state available (AV) butlocation update fails

Description

All MTP and SCCP level objects are in state available (AV) but locationupdate fails.

Symptoms

All MTP and SCCP level objects are in state available (AV) but locationupdate fails.

Recoveryprocedures

Checking why all MTP and SCCP level objects are in state available (AV) butlocation update fails

Steps

1. Check that the SCCP service is defined on MTP level in allneeded signalling networks (NPI)

ZNPI:<signalling network>;

Create the missing service with the command NPC.


30/01/2009


23.1.5 Mobile calls are cut frequently after 4.5 min

Description

Mobile calls are cut frequently after 4.5 min.

Symptoms

Mobile calls are cut frequently after 4.5 min.

Recoveryprocedures

Checking why mobile calls are cut frequently after 4.5 min

Steps

1. Check the values of SCCP timer parameters Q714_T_IAR andQ714_T_IAS from both MSC and RNC sites (OCI)

ZOCI:<signalling point parameter set numbers>;

The timers that are used for certain direction are defined in thesignalling point parameter set of the remote node. If the timerQ714_T_IAR of one node (typically 4.5 min) is shorter that theQ714_T_IAS of the remote node, SCCP signalling connections willbe released after Q714_T_IAR.

Change the Q714_T_IAR timer value in the own node to be greaterthan the Q714_T_IAS timer value in the remote node with the OCMcommand.

23.1.6 AAL2 connection release delay too short for short-term Iu/Iur (NNI)link failures

Description

In some cases, the system releases AAL2 connections due to failure inMTP connectivity earlier than you have desired - for example, beforeRANAP release. You can set a timer AAL2_NNI_CONN_REL_TIMER forAAL2 connection release delay in order to prevent the AAL2 connectionsfrom being released prematurely.

If a transmission failure has cut the connections to Iu/Iur partner forQ2110_TIMER_NO_RESP + 2 seconds, NNI signalling links towards ithave failed and the unavailability of partner signalling point has beeninformed by MTP to ALCAP. After this, a new timer

DN02143262Issue 16-1 en30/01/2009



AAL2_NNI_CONN_REL_TIMER is started and AAL2 connections with thepartner signalling point are released only after it has expired. If thesignalling point is declared available before the timer expires, AAL2connections are not released.

Symptoms

A failure in the Iu/Iur signalling connection releases AAL2 connectionsprematurely.

Recoveryprocedures

Changing the value of the AAL2 connection releasing timerAAL2_NNI_CONN_REL_TIMER

Summary

The timer is located in PRFILE and the value range is 0 - 255 seconds.The default value is 0.

Steps

1. Set the new value for the AAL2 timer

ZWOC:2,1047,<value in seconds>;

23.1.7 Global title translation fails although translation exists

Description

Global title translation fails although translation exists.

Symptoms

Global title translation fails although translation exists.

Recoveryprocedures

Checking why global title translation fails although translation exists

Steps

1. Check that the header information of GT translation is the sameas the one used in the addresses (NBI).

ZNBI:;


30/01/2009


Check that not only the digits are matching but also the followingvalues correspond to the needed translation:. global title indicator (ITU-T or ANSI). translation type. numbering plan. nature of address indicator.

To modify the values, first you have to delete the existing analysiswith the NBD command, and then create a new analysis with thecorrect values with the NBC command.

For more instructions, see Creating/modifying GT translation resultand GT modification

23.1.8 Errors in the global translation result

Description

There are errors in the global translation result.

Symptoms

There are errors in the global translation result.

Recoveryprocedures

Checking the global translation result

Steps

1. Check that a translation result exists for each global title (NAI)

ZNAI;

Check that a translation result (GTRFIL record) exists for eachglobal title to be translated and that they contain the required data.

Note that one translation result may serve several global titles.

2. Confirm that the network and the destination point code (DPC)are the required ones

DN02143262Issue 16-1 en30/01/2009



Note

You cannot create a global title result where the DPC is unknown to theSCCP and you cannot delete the DPC from the SCCP if it has beenattached to the global title result.

3. Check the RESULT STATE field

There are two possible values ACT (active) and INA (inactive). Thenormal state of the global title result is active and it is in this stateafter creation. If the result state is inactive, the global title result is outof service and it should not be used for routing. You can change thestate with the NAM command.

4. Check that the routing indicator (RI) setting is appropriate forthe desired routing

If RI is SSN (route-on-label) there should be no reference to globaltitle modification data record number (GTM). If RI is GT (route-on-gt),then GTM is optional.

5. Check the subsystem number, SSN

If the subsystem number (SSN) is included in the result, all outgoingmessages will also contain this new SSN. New subsystem numbersreplace the original subsystem numbers fetched from the calledaddress and the original subsystem has no effect on this.

6. Confirm that the subsystem translation is as required andcheck the validity of the indicated SSN

7. Check the global title modification data (NAX)

If a global title modification data record number (GTM) exists in theresult, check the global title modification data using the GTM as aparameter in the NAX command.

ZNAX:DN=;

The global title data (GTMFIL) is used to change or replace theglobal title that is being translated (for example,. delete/add digits orreplace the header information). Check the validity of each change,as represented in the displayed data, against the requirements fortranslation. Check also that each listed global title data record isreferenced by a translation result record (GTRFIL record).


30/01/2009


Note

When the global title number is changed, it is analysed again during therouting procedure. This means that the global title analysis for themodified global title number should also exist.

Example Checking GT translation result

In this example we have an existing digit string 123456 in a global title. Theglobal title translation result contains modification record number 00001. InGTMFIL record is ADC=2 (add digits count), ADP=5 (add digits pointer)and DIGITS=99 (digits to be added). This will add digits 99 just in front ofthe fifth digit in the original digit string. The resulting digit string is then12349956.


In this example we have an existing digit string 123456 in a global title. Theglobal title translation result contains modification record number 00002. InGTMFIL record is DDC=1 (delete digits count) and DDP=5 (delete digitspointer). This will delete the fifth digit from the original digit string (number5), and the resulting digit string is 12346.


In this example we have an existing digit string 123456 in a global title. Theglobal title translation result contains modification record number 00003. InGTMFIL record is DDC=1 (delete digits count), DDP=5 (delete digitspointer), ADC=2 (add digits count), ADP=5 (add digits pointer) andDIGITS=99 (digits to be added). This will delete the fifth digit from theoriginal digit string (number 5) and add digits 99 just in front of the fifth digitin the original digit string. The resulting digit string is then 1234996.


In this example we have the header information in a global title: SS7standard = ITU, GTI = 4, TT = 0, NP = 1 and NAI = 4. The global titletranslation result contains modification record number 00004. In GTMFILrecord no digit modification is made, but the NP (numbering plan) isdifferent from the one in the original global title. This will replace the headerinformation so that the NP is changed (new NP = 7). Digits remainunchanged.

Example Example modification records as seen in the MML executionprintouts

DN02143262Issue 16-1 en30/01/2009



GTMFIL DIGITS

RECORD SS7 GTI ENC TT NP NAI DDC DDP ADC ADP 123456789012345

------ ---- --- --- --- --------- -------- --- --- --- --- ---------------

00001 ITU 4 BCD 000 1 (E.164) 4 (INT.) - - 2 5 99

00002 ITU 4 BCD 000 1 (E.164) 4 (INT.) 1 5 - -

00003 ITU 4 BCD 000 1 (E.164) 4 (INT.) 1 5 2 5 99

00004 ITU 4 BCD 000 7 (E.214) 4 (INT.) - - - -

To check the references from the translation results (GTRFIL) use the NAXcommand, where parameter RN means referenced global title modificationdata record number.

For each global title to be translated, check that there is a numberanalysis, so that the intended translation result (GTRFIL record index) canbe reached. Note that not all digits in the global title are used in theanalysis, but only those needed to reach the intended translation result.This can be done with the NBI command where you can give the headerinformation, digits and result record indexes.

23.1.9 The state of all subsystems in the remote network element isunavailable (UA) although MTP route set is in state available-executing (AV-EX)

Description

The state of all subsystems in the remote network element is unavailable(UA) although MTP route set is in state available-executing (AV-EX).

Symptoms

The state of all subsystems in the remote network element is unavailable(UA) although MTP route set is in state available-executing (AV-EX).

Recoveryprocedures

Checking why the state of all subsystems in the remote network element isunavailable (UA) although MTP route set is in state available-executing (AV-EX)

Steps

1. Check the state of the remote SCCP (NGI)

ZNGI:;

2. Change the state to AV, if necessary (NGC)


30/01/2009


If the SCCP of the remote node is in state UA-INU, change the stateto AV with the following command:

ZNGC:<signalling network>,<signalling point code>:ACT;

23.1.10 Some remote subsystems do not recover after route setunavailability

Description

Some remote subsystems do not recover after route set unavailability.

Symptoms

Some remote subsystems do not recover after route set unavailability.

Recoveryprocedures

Checking why some remote subsystems do not recover after route setunavailability

Steps

1. Check the defined subsystems

Check that the defined subsystems exist in the remote networkelement and whether they should exist. This means for examplechecking whether the remote network element should only be usedas a signalling transfer point (STP), or whether the subsystems inquestion should exist there.

If the subsystems should exist, the reason for unavailability could betemporary, caused by changes in configuration or a fault situation. Ifthe subsystems really are down (unavailable) in the remote networkelement, you cannot bring them up from your local network element.

Depending on who the remote network element belongs to, this kindof matters should be considered in the appropriate forum, forexample in negotiations between operators.

DN02143262Issue 16-1 en30/01/2009



23.1.11 A signalling point parameter or a subsystem parameter does nothave the described effect

Description

A signalling point parameter or a subsystem parameter does not have thedescribed effect.

To find out the problem, check the item (signalling point or subsystem),which the parameter set applies to.

Symptoms

A signalling point parameter or a subsystem parameter does not have thedescribed effect.

Recoveryprocedures

Checking why a signalling point parameter or a subsystem parameter doesnot have the described effect

Steps

1. If the parameter set applies to the SCCP signalling point

Then

Check the parameter set of the SCCP signalling point (NFI)

Use the NFI command to check which parameter set the SCCPsignalling point uses.

2. If the parameter set applies to the SCCP subsystem

Then

Check the parameter set of the SCCP subsystem (NFJ)

Use the NFJ command to check which parameter set the SCCPsubsystem uses.

3. If the parameter set applies to the SCCP signalling point parametersets

Then

Check the values of the SCCP signalling point parameter sets(OCI)


30/01/2009


Use the OCI command to interrogate the values of the SCCPsignalling point parameter sets.

4. If the parameter set applies the SCCP subsystemn parameter sets

Then

Check the values of the SCCP subsystem parameter sets (OCJ)

Use the OCJ command to interrogate the values of the SCCPsubsystem parameter sets.

23.1.12 SCCP screening does not come into effect

Description

SCCP screening does not come into effect

Symptoms

SCCP screening does not come into effect

Recoveryprocedures

Checking why SCCP screening does not come into effect

Steps

1. Check that the SCCP signalling point based screening is active(ODI)

ZODI:;

2. Activate the SCCP signalling point based screening, ifnecessary (ODS)

If the SCCP signalling point based screening is not active, activate itby the ODS command.

ZODS:ACT;

3. Check that the SCCP GT screening is active (ODF)

ZODF:;

4. Activate the SCCP GT screening, if necessary (ODG)

DN02143262Issue 16-1 en30/01/2009



If the SCCP GT screening is not active, activate it by the ODGcommand.

ZODG:ACT;

23.1.13 Manual routing test fails

Description

Here are presented failures that can occur in the manual routing test. Themanual routing test is needed only in the Japanese network. In othernetworks, the signalling link test is done automatically.

Symptoms

Manual routing test fails.

Recoveryprocedures

Manual routing test fails

Steps

1. Check why the test pattern of the test message has changed

a. Check the network configuration

Check the network configuration to the signalling point that youwere testing.

b. Run the routing test again

c. Check the hardware, if the test is still unsuccessful

2. Check why no acknowledgement message was received

a. Check the parameters

The destination signalling point must be in a state wheretesting is allowed.

b. Check the configurations

Check the state of the signalling route to the tested signallingpoint.

3. Check why the tested signalling point is inaccessible for thesignalling transfer point

The signalling transfer point may send a message saying that thetest message has been sent to an inaccessible signalling point.


30/01/2009


Check the state of the signalling route to the tested signalling point.

DN02143262Issue 16-1 en30/01/2009




30/01/2009


Related Topics

Signalling in 3G

Descriptions

SS7 signalling

SAAL UNI signalling

Instructions



AAL type 2 signalling protocol

Instructions



Descriptions

SS7 signalling

SAAL UNI signalling

DN02143262Issue 16-1 en30/01/2009


Related Topics

States of signalling route sets

Instructions


States of signalling routes

Instructions


States of signalling link sets

Instructions


States of signalling links

Instructions




30/01/2009


States of SCCP signalling points

Instructions


States of SCCP subsystems

Instructions


SS7 signalling network specific parameters

Instructions

Modifying SS7 signalling network parameters

Signalling link parameters

Instructions

Creating new signalling link parameter set

Signalling route set parameters

Instructions

Modifying the values of signalling route set parameter set

DN02143262Issue 16-1 en30/01/2009


Related Topics

Creating new signalling route set parameter set

SS7 network planning principles

Instructions

SS7 network structures


Instructions


MTP level signalling network

Instructions



SCCP level signalling network

Instructions




30/01/2009



Instructions




Instructions





Instructions



Instructions


DN02143262Issue 16-1 en30/01/2009


Related Topics


Instructions

Creating local signalling configuration

Activating SCCP configuration

Activating SCCP configuration

Instructions

Creating local signalling configuration


Setting/modifying MTP level signalling trafficrestrictions

Instructions

Setting/modifying signalling point based traffic restrictions

Calling GT checking based traffic restrictions

Setting/modifying GT based traffic restrictions

Modifying MTP level signalling traffic load sharing

Instructions



30/01/2009


Modifying SCCP signalling point parameter set

Descriptions

SCCP signalling point parameters

Creating new SCCP signalling point parameter set

Descriptions

SCCP signalling point parameters

Removing SCCP signalling point and/or subsystemfrom own signalling point

Instructions

Removing an MTP signalling point

Modifying the values of SCCP subsystemparameter set

Descriptions

SCCP subsystem parameters

DN02143262Issue 16-1 en30/01/2009


Related Topics