MTP Document

Switching Core Network Signalling
Message Transfer Part

Training Document M14/U4
Nokia Siemens Networks
(76)
Legal notice Intellectual Property Rights All copyrights and intellectual property rights for Nokia Siemens Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Siemens Networks training material, are the exclusive property of Nokia Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individuals can use the Nokia Siemens Networks training material for their own personal selfdevelopment only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Siemens Networks. The Nokia Siemens Networks training material cannot be used outside of an agreed Nokia Siemens Networks training session for development of groups without the prior written agreement of Nokia Siemens Networks. Indemnity The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products are given as is and all liability arising in connection with such hardware or software products shall be defined conclusively in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document. Nokia Siemens Networks will correct errors in the document as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY MONETARY LOSSES,SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT This document and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. Wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia 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 2008. All rights reserved.
(76)
Contents
Contents
Summary of changes.............................................................................4 1 Objectives.............................................................................................5 2 Introduction..........................................................................................6 3 Signalling network................................................................................8 4 MTP layers..........................................................................................10 5 MTP alarms.........................................................................................40 6 MTP parameters handling..................................................................42 Appendix...............................................................................................73 References............................................................................................74 Glossary................................................................................................75 Index 76
(76)
Summary of changes
Summary of changes
(76)
MTP parameters handlingAppendix
Objectives
On completion of this module, you should be able to:

Describe the functionality of MTP layer Explain MTP message structure Explain the MTP procedures Output and interpret analysing results List MTP parameter in DX200 NE
(76)
Introduction
The CCS#7 Structure divides the signalling functions into Message Transfer Parts and the User Parts for different users and applications. The user part communicates with a corresponding user part in the adjoining network element. The MTP serves as a common transport system that provides reliable transmission of the signalling messages between the communicating user parts, regardless of the unreliability of the physical transmission media. MTP is covered under ITU-T specifications Q.701 707. The functions of the MTP are divided into three levels:

Level 3 Level 2 Level 1
Signalling network functions Signalling link functions Signalling data link functions
The signalling data link function (level 1) defines the physical, electrical and functional characteristics of a signalling data link and the means to access it. The level 1 function provides a bearer for a signalling link. The signalling link function (level 2) defines the functions considering message transfer between two adjacent network elements through a signalling link. It defines the message structure, framing, error detection and correction, alignment procedure, and so on. The signalling network function (level 3) can be divided into two parts: message handling, which includes message routing and distribution to the respective user part, and network management, which provides all the necessary procedures for using the signalling network in an optimal way.
(76)
Layer 4 (User Part)
ISUP
TUP
SCCP
Other User Parts
MTP3
Signalling Network Management
Signalling Message Handling
MTP2
Signalling Link Function
MTP1 MTP2
Signalling
Control signals Signalling message flow
Signalling Data Link Function
Figure 1.
MTP Layers
(76)
Signalling network
A signalling network comprises of signalling points. A distinction is made between 2 categories:

Signalling end points (SEP) Signalling transfer points (STP)
The signalling end points are the sources (origination points) and destinations (destination points) of the signalling traffic. In communications network both these points are usually switching centers. On the basis of the destination address, the signalling transfer points forward received signalling messages to another signalling transfer point or, where applicable, to a signalling end point. No processing of the message content takes places in a signalling transfer point. A signalling transfer point may be integrated in a signalling point (e.g. a switching cent) or may be a separate node in the signalling network.
3.1
Addressing signalling points

All signalling points are identified by a signalling point code (SPC) which is defined by a corresponding numbering scheme and can therefore be addressed specifically in a signalling message. The signalling point code is a 14 bit value (ITU-T SS7 standard) and can be allocated into subfield, for example, 3-8-3 bit for international use (see ITU-T Q.708). Since the signalling point code with 14 bits (016383) is insufficient to address all signalling points worldwide, it is always used together with the network indicator. The network indicator has four values: NA0, NA1, IN0, and IN1.
(76)
Signalling link
SEP
Signalling end point
SEP
SEP
Signalling link DPC = X
STP
Signalling transfer point
Signalling link DPC = X
SEP
Figure 2.
Components of a signalling network, SEP and STP
Signalling Point Codes

National use
Length: 14 bits (ITU-T SS7 standard), 16 bits (Japan SS7 standard), or 24 bits (China or ANSI SS7 standard) Format: can be allocated into subfields International use (ITU-T Q.708) 3bit-8bit-3bit meaning: Zone-Area-Signalling point
Network Indicator
NA0 NA1 IN0 IN1
National network 0 National network 1 International network 0 International network 1
Figure 3.
SPC and network indicator
(76)
4
4.1
MTP layers
MTP Layer 1: Signalling Data Link
Signalling data link level (level 1) defines the physical, electrical and functional characteristics and the physical interface (E1 or T1) towards the transmission media. In digital systems normally 64 kbps or 56 kbps channels are used, that is, a timeslot of PCM30 or PCM24 respectively. The choice of the timeslot may be any timeslot except TS 0. These are governed by the G.703 and G.704 specifications. This channel is called a link. Level 1 function is specified in Recommendation Q.702.
4.2
MTP Layer 2: Signalling Link

Signalling link level (level 2) defines the functions and procedures for and relating to the transfer of signalling messages over one individual signalling data link. The level 2 functions, together with a level 1 signalling data link as a bearer, provide a signalling link for reliable transfer of signalling messages between two directly connected signalling points. Signalling messages delivered by superior hierarchical levels are transferred over the signalling link in variable length signal units. The signal units include transfer control information for proper operation of the signalling link in addition to the signalling information. The signalling link functions comprise: 1. 2. 3. delimitation of signal unit by means of flags flag imitation prevention by bit stuffing error detection by means of check bits included in each signal units
10
(76)
4.
error correction by retransmission and signal unit sequence control by means of explicit sequence numbers in each signal unit and explicit continuous acknowledgements signalling link failure detection by means of signal unit error rate monitoring and signalling link recovery by means of special procedures
5.
Level 2 functions are specified in Recommendation Q.703.
User Part
TransmitBuffer Buffer Transmit
Controller Controller FSN BSN
ReceivedBuffer Buffer Received
SequenceNumber Number Sequence Generation Generation Checksum Checksum Generation Generation
Retransmission Retransmission Buffer Buffer
SequenceNumber Number Sequence Check Check Checksum Checksum Generationand and Generation Comparison Comparison MessageLength Length Message Check Check
BIB
FlagGeneration Generation Flag andBit-stuffing Bit-stuffing and
FlagDetection Detectionand and Flag Bit-stuffing Bit-stuffing
Level 1
Level 1
Figure 4.
MTP Layer 2 functions
4.2.1
Signal units
The message transfer part transports messages in signal units of variable length towards destination. A signal unit is formed by the function of level 2. In addition to the message it also contains control information for the message exchange. There are three different types of signal units: 1. Message signal units (MSU)
11
(76)
2. 3.
Link status signal units (LSSU) Fill-in signal units (FISU)
Types of signal units are differentiated by means of the length indicator contained in all signal units. Message signal units are used for the transport of the user part messages. Link status signal units contain information about state of the signalling link. Fill-in signal units contain no additional information. It is used when there is no message to be sent on the link. Own side has no messages to send, but the remote end expects acknowledgements for the message signal units that it has sent. Message signal units are retransmitted in case of error; link status signal unit and fill-in signal unit are not. The basic formats of the signal units are shown in Figure 5.
4.2.1.1 Function and codes of the signal unit fields
Flag (F) The signal units are of varying length. The opening flag indicates the start of a signal unit. The opening flag of one signal unit is normally the closing flag of the preceding signal unit. The bit pattern for the flag is 0111 1110 or 7Eh. The flag is also used for alignment of the signalling link at the far-end. Bit stuffing for Flag imitation prevention is done by inserting a 0 after 5 consecutive 1 in a message data stream. At the receiving end a 0 is deleted after five consecutive ones in the received data stream. Backward sequence number (BSN) It is the sequence number of a signal unit being acknowledged. Backward indicator bit (BIB) With this bit, faulty signal units are requested to be retransmitted for error correction. Forward sequence number (FSN) It is the sequence number of the signal unit in which it is carried. FSN and BSN are numbers in binary code from a cyclic sequence ranging from 0 to 127. Forward indicator bit (FIB) It indicates whether a signal unit is being sent for the first time or whether it is being retransmitted.
12
(76)
MSU F CK
SIF
SIO
LI
F I B
FSN
7
B I B
BSN F
7
First bit transmitted
8 16 8n, n>2 8 2 6 1 length indicator >2 and 63

F I B
8 [bit]
LSSU F CK
SF
LI
FSN
7
B I B
BSN F
7
8 16 8 or 16 2 6 1 length indicator = 1 or 2
8 [bit]
FISU F CK
LI
F I B
FSN
B I B
BSN F
7
8 16 2 6 1 7 length indicator = 0
F BSN BIB FSN FIB Flag Backward Sequence Number Backward Indicator Bit Forward Sequence Number Forward Indicator Bit LI SIO SIF CK SF
8 [bit]
Length Indicator Service Information Octet Signalling Information Field Check Bits Status Field
Figure 5.
Signal unit formats
Length indicator (LI) The length indicator is used to indicate the number of octets following the length indicator octet and preceding the check bits. Length indicator is a number in binary code in the range of 0-63. It differentiates between the three types of signal units as follows: Length indicator = 0: Length indicator = 1 or 2: Length indicator > 2: Fill-in signal unit Link status signal unit Message signal unit
In the case that the signalling information field (SIF) is spanning 62 octets or more, the length indicator is set to 63. Service information octet (SIO) The service information octet only exists in message signal units. It contains the service indicator and the subservice field. Signalling information field (SIF) The signalling information field only exists in message signal units. It contains the actual user message.
13
(76)
Check bits (CK) CRC16 checksum is inserted in each signal unit for error detection. A checksum is calculated for the data between the flags and inserted in the signalling unit. At the remote end the checksum is recalculated, if the calculated and received checksums do not match, a negative acknowledgement is conveyed by setting BSN to the received FSN and inverting the previously transmitted BIB. This BIB will remain in the new state till a new error occurs. Status field (SF) The status field only exists in link status signal units. It contains status indications of the signalling link. Only three bits are used to represent signal status. The possible state and corresponding messages are stated below. Their coding is shown in Figure 6.

Status indication O (SIO) Status indication N (SIN) Status indication E (SIE) Status indication OS (SIOS) Status indication PO (SIPO) Status indication B (SIB)
Link out of alignment Normal alignment Emergency alignment Link out of service Processor outage Busy
LSSU F CK
8 16
SF
8 or 16
DCBA
LI
F I B
FSN
7
B I B
BSN F
7
2 6 1
8 [bit]
XXXX
X000
Bit Bit Bit Bit Bit Bit
000 001 010 , 011 100 101
Status Status Status Status Status Status
indication indication indication indication indication indication
O (SIO) N (SIN) E (SIE) OS (SIOS) PO (SIPO) B (SIB)
Link out of alignment Normal alignment Emergency alignment Link out of service Processor outage Busy
Figure 6.
Link status indications in LSSU
14
(76)
4.2.2
Error correction
Error correction is through retransmission. Two techniques of error correction are provided, the basic method and the preventive cyclic retransmission method. Both error correction techniques apply only to MSU but not to LSSU and FISU. Basic error correction is implemented by a negative acknowledgement through BIB and retransmission after inverting FIB. All signalling units are repeated from that sequence number. Positively acknowledged signalling units are deleted from the retransmission buffer.
Signalling Terminal
Negative Acknowledgement
Signalling Terminal
Retra nsmission Buffer
Retransmission
MSU
Figure 7.
Basic error correction method
The preventive cyclic retransmission method is implemented on long distance lines, with transmission time greater than 15ms. Negative acknowledgement is not awaited., instead all unacknowledged and new signalling units are kept in the retransmission buffer and transmitted periodically. The remote end simply waits for the retransmission to correct the error.
Signalling Terminal
Send only positive acknowledgement of MSU
Signalling Terminal
Retransmission Buffer: Delete a positive acknowledgement else cyclically transmit buffer
Figure 8.
Preventive cyclic retransmission method
15
(76)
4.2.3
Signalling link failure detection

Signalling link failure detection is provided by means of Signal Unit Error Rate Monitoring (SUERM). This is a statistical method of ensuring the permitted error rate on a link. SUERM is a counter, which increments on a detection of error. If 256 signalling units are received error free it decrements by one. This is called the leaky bucket principle. If the SUERM counter reached the pre-set threshold (generally 64), then link is declared faulty and change procedure to a working link takes place. Initial alignment procedure is carried out to recover the faulty link.
Alarm level
+1 for every SU in error
-1 for 256 correctly received SUs
Figure 9.
Signal Unit Error Rate Monitoring (SUERM)
4.2.4
Level 2 procedures
Signalling link recovery is provided by means of special procedures, which are initial alignment procedure, processor outage procedure, and congestion control.
4.2.4.1
Initial alignment procedure
The initial alignment procedure is used for link activation and restoration either through MML commands or through SUERM. 5 different states are distinguished: Link out of service Internally an activate signal changes the link to an idle state.
16
(76)
Link idle On the idle link an SIO message is sent. On receiving an SIO as acknowledgement the link becomes aligned on both the local and remote end. Link aligned SIO continues to be exchanged. At this point any one side may decide to send either SIN or SIE and results in proving state. SIE is generally sent. If the entire linkset is out of service, an SIE is sent to recover each link one by one. Link proving SIN or SIE is sent in response to received SIN or SIE. This initiates either of the two types of proving:
Normal proving When SIN was the LSSU, 216 octets are exchanged via the signalling link within 8.2 sec. allowing only 4 signal units to be faulty.
Emergency proving If SIE was the LSSU exchanged, 212 octets are exchanged via the signalling link within a time of 0.5 sec with only one SU allowed to be faulty.
In either of the two proving procedures Alignment Error Rate Monitoring (AERM) is used. The AERM counter is set to zero to mark the beginning of an alignment period. Every SU in fault increments the counter by one. If threshold (four or one) is reached before the exchange of pre-requisite octets, start a new alignment period. If five periods fail, the link is marked faulty. In service After successful execution of the proving period the link becomes active. A signalling link test message (MSU) is sent on the link, containing the DPC, OPC, SLC, and a test pattern. It is acknowledged from the other side by Signalling Link Test Acknowledgement message (SLTA) with the same bit-pattern. If the test pattern is received correctly, the Link State is marked as available executing and the link can be used for signalling.
17
(76)
Link out of service Activate link SIO SIO Link Aligned SIN/SIE SIN/SIE FISU FISU FISU FISU Link Proving Link Idle
MSU (SLTM) MSU (SLTA) Link In Service
Figure 10.
Initial alignment procedure
Aligned
SIO Link activation SIN/SIE
Out of service
Idle
Proving
In service
Figure 11.
Process flow between different states
18
(76)
4.2.4.2
Processor outage
A processor outage may occur if:

Signalling messages cannot be transferred to functional level 3 and / or 4 at either network elements Else if the state of the link was changed through MML to Blocked.
In either of the cases, an LSSU (SIPO) is transmitted and received MSUs are discarded. FISU are exchanged continuously.
4.2.4.3
Congestion control
In case there is congestion on the receiving side of the signalling connection, an LSSU (SIB) is sent every 200msec, until congestion ceases. MSU and FISU continue to be transmitted as usual. The BSN and BIB values do not change, but show the last acknowledged MSU. If congestion persists beyond 10 seconds, the link is declared faulty and an LSSU (SIOS) is sent.
4.3
MTP Layer 3: Signalling Network

The signalling network functions (MTP3) can be divided into two parts, namely:

Signaling message handling, and Signaling network management
The purpose of the signaling message handling functions is to ensure that the signaling messages originated by a particular user part at a signaling point (originating point) are delivered to the same user part at the destination point indicated by the sending user part. The signalling message handling functions are based on the label contained in the messages which explicitly identifies the destination and originating points. The label part used for signalling message handling by the message transfer part is called routing label.
4.3.1
MTP3 message structure

The MTP3 message structure is shown on the Figure 12. Basically it consists of 3 main parts: the service information octet (SIO), routing label and user information field.
19
(76)
The destination of a signal unit is specified in a routing label. The routing label is a component of every user message and is transported in the signalling information filed (SIF). The routing label consists of destination point code (DPC), originating point code (OPC), and signalling link selection (SLS) field. The service information octet (SIO) contains additional address information. Using the service indicator (SI), the destination message transfer part identifies the user part for which message is intended. The subservice field (SSF) contains the network indicator which enables a message to be identified, for example, as being for national or international traffic. Link status signal units (LSSU) and fill-in signal units require no routing label as they are only exchanged between level2 of adjacent message transfer parts.
Signalling Information Field (SIF)
User Information
Routing Label
SIO
SLS
OPC
DPC
Subservice Service Field (SSF) Indicator (SI)
14
14
4
00XX (0H) : IN0 01XX (4H) : IN1 10XX (8H) : NA0 11XX (C H) : NA1
[bit]
OPC Originating Point Code DPC Destination Point Code SLS Signalling Link Selection
0000 (0H): SNM 0001 (1H): SNT 0011 (3H): SCCP 0100 (4H): TUP 0101 (5H): ISUP 1101 (DH): BICC
Figure 12.
MTP3 message structure and coding
The command group NP SERVICE INFORMATION DATA HANDLING is used to create, modify, delete, and interrogate the signalling service information data of own signalling point. Execution of ZNPI command gives the following printout:
20
(76)
Execution printout
Abbreviations used in execution printout
Figure 13.
NPI Interrogate services
Explanation of SIO parameters Signalling network NA0 NA1 IN0 IN1 national network 0 national network 1 international network 0 international network 1 a hexadecimal 0 - F
Service indicator index The service indicator index indicates the user part within the signalling network. Service indicator name 1-5 ASCII characters Service existing for STP messages The parameter may receive the following values: Y it is desired that service exists for STP messages
21
(76)
service does not exist for STP messages
Service existing for user part of own signalling point The parameter may receive the following values: Y N it is desired that service exists for the user part of own signalling point service does not exist for the user part of own signalling point a hexadecimal 1 - FFFF
Primary process family The number of the primary process family, which handles incoming signalling messages of the user part of one's own signalling point. The parameter is obligatory if service is created for the incoming signalling messages of the user part of one's own signalling point but the parameter cannot be given if no service is created for incoming signalling messages of the user part of one's own signalling point. Secondary process family a hexadecimal 1 - FFFF The number of the secondary process family which handles the incoming signalling messages of the user part of one's own signalling point. The parameter is not obligatory, and it cannot be given if no service is created for the incoming signalling messages of the user part of one's own signalling point ADDITIONAL INFORMATION One of the services at the minimum

service for STP messages service for the user part in own signalling point
must be created. If no service is created for incoming messages in one's own signalling point, the parameters PRIMARY PROCESS FAMILY and SECONDARY PROCESS FAMILY cannot be given. If service is created for incoming messages in the user part of own signalling point, the parameter PRIMARY PROCESS FAMILY must be given. If SERVICE INDICATOR INDEX = 0 and service is created for incoming messages in the user part of one's own signalling point, the default of PRIMARY PROCESS FAMILY is the process family indicator of CCNETM and the default of SECONDARY PROCESS FAMILY is the process family indicator of CCDESM. If SERVICE INDICATOR INDEX = 1 and service is created for incoming messages in the user part of one's own signalling point, the default of
22
(76)
PRIMARY PROCESS FAMILY is the process family indicator of CCNETM. PRIMARY PROCESS FAMILY and SECONDARY PROCESS FAMILY cannot have the same value (family process indicator).
4.3.2
Signalling message handling

Signalling message handling is responsible for the routing of messages to the appropriate link, and distribution of the received messages within own exchange. This can be divided into three sub functions:

Message discrimination Message distribution Message Routing
These functions and interactions between them are shown below.
User Part MTP3
ISUP
TUP
SCCP
Network Management
Signalling message handling
Message distribution
DPC own SPC DPC = own SPC
Message routing
Message discrimination
MTP2
Figure 14.
Block diagram of signalling message handling function
The discrimination function evaluates the destination point code (DPC) of the MSU. If the DPC of the received message is equal to own
23
(76)
SPC the message is sent to the distribution function. Otherwise it is sent to the routing function. The distribution function checks the service information octet (SIO) to find out the suitable user part. The routing function finds the suitable signalling link for sending the signal unit to another network element. The routing is based on DPC, SIO, and the SLS carried in the message. The SLS in turn defines load sharing, and thus link selection.
4.3.2.1 Load sharing within a linkset
Load sharing within a linkset is based on use of SLS bits (4 bits after OPC in routing label). For example in ISUP messages SLS bits are copied from 4 least significant bits of CIC (circuit identification code). All 4 bits of SLS are used for load sharing regardless of link set size. Load sharing is performed between all available signalling links in a linkset. Link priority has no meaning. In case of a link failure, traffic of the linkset is evenly distributed among all remaining available links. The following table describes the relation between SLS-bits and links.
LINK
SLS
Figure 15.
Load sharing within a linkset
24
(76)
4.3.2.2
Load sharing between link sets in a route set
For link sets in a route set the value 7 indicates the highest priority route and 0 the lowest priority route. Load sharing between link sets is independent from load sharing within a link set. Link set size has no effect on the load sharing between link sets. So link set sizes should be equal if load sharing is used. In the DX 200 implementation, 8 link sets can belong to a route set (8 routes). Route priorities are significant because traffic is shared on the routes with same priority. If only one route has highest priority (usually the direct route), no load sharing occurs. Priority is also used in forced rerouting to determine the alternative route. Load sharing between link sets also uses all 4 bits of a SLS. If route priorities are the same and load sharing is allowed load sharing is as follows:
LINK SET
SLS
Figure 16.
Load sharing between link sets
25
(76)
4.3.3
Signalling network management

The signalling network management functions provide the actions and procedures required to maintain signalling service, and to restore normal signalling conditions in the event of disruption in the signalling network, either in signalling links or at signalling points. The disruption may be in the form of complete loss of a signalling link or a signalling point, or in reduced accessibility due to congestion. There are 2 categories of signalling network management messages as indicated in the service information octet in MSU: 1. 2. Signalling network management (SNM) Signalling network testing and maintenance (SNT)
Signalling network management (SNM) messages The SNM messages contain a heading code, after the label. It comprises of two parts H0 and H1, 4 bits each, which identify the message. The message structure is shown on the Figure 17.
MSU
F CK
SIF
SIO
LI
F I B
FSN
B I B
BSN F
User Information
H1 4
H0 4
SLS 4
OPC 14
DPC 14
SSF 4
SI 0000 4 [bit]
SSF H0 H1
Subservice Field Heading code indicating which message group the message belong to Heading code indicating the message within the group in question
Figure 17.
SNM message structure and coding
The SNM messages are coded as 0000 in the Service indicator subfield in SIO. H0 and H1 indicate the type of message being sent. Figure 18 illustrates the heading code allocation of SNM messages.
26
(76)
H0 GROUP 0000 CHM ECM FCM TFM RSM MIM TRM DLM UFC 0001 0010 0011 0100 0101 0110 0111 1000 1010 COO ECO RCT TFP RST LIN TRA DLC UPU CSS CNS CNP RSR LUN LIA LUA COA ECA TFC TFR 0001 0010 0011 0100
H1 0101 0110 0111 1000
CBD
CBA
TFA
LID
LFU
LLT
LRT
Figure 18.
Heading code allocation of SNM messages
The SNM messages are listed in Table 1 and 2. Signalling network testing and maintenance (SNT) messages There are only two SNT messages: SLTM SLTA Signalling Link Test Message Signalling Link test Acknowledgement
The additional information carried by these two messages is a test pattern. The SNT messages are coded as 0001 in the Service indicator subfield in SIO
27
(76)
Table 1. Group H0 ECM ECM CHM CHM CHM CHM MIM MIM MIM MIM MIM MIM MIM MIM TRM UFC Table 2.
SNM messages related to signalling traffic management Group H1 ECA ECO COA COO CBD CBA LFU LIN LUN LIA LUA LID LLT LRT TRA UPU PDU Emergency changeover acknowledgement Emergency changeover order Changeover acknowledgement Changeover order Changeback declaration Changeback acknowledgement Link force uninhibit Link inhibit Link uninhibit Link inhibited acknowledgement Link uninhibited acknowledgement Link inhibit denied Link local inhibit test Link remote inhibit test Traffic restart allowed User part unavailable
SNM messages related to signalling route management
Group H0 RSM RSM FCM TFM TFM TFM TFM
Group H1 RST RSR RCT TFA TFC TFP TFR
PDU Signalling Route Set Test for prohibited destination Signalling Route Set Test for restricted destination Signalling Route Set Congestion Test Transfer allowed Transfer controlled Transfer prohibited Transfer restricted
The signalling network management is divided into 3 functions:
28
(76)
1.
Signalling traffic management function The signalling traffic management is responsible for the availability of a signalling link or a signalling route by using the following procedures:

changeover changeback forced rerouting controlled rerouting MTP restart management inhibiting signalling traffic flow control
2.
Signalling link management function The signalling link management function controls the signalling links and is responsible for the state changes by using the following procedures:

signalling link activation signalling link restoration signalling link deactivation signalling link set activation
3.
Signalling route management function
The signalling route management is responsible for the availability of a destination by using the following procedures:

transfer-prohibited procedure, indicating the unavailability of a destination transfer-allowed procedure, indicating the availability of a destination transfer-controlled procedure, indicating the overload situation of a destination signalling-route-set-test procedure, testing the state of a signalling route set.
4.3.4
4.3.4.1
Signalling traffic management procedures

Changeover procedure
In case of a signalling link failure the traffic from failed link is diverted to all other remaining links in a linkset, avoiding at the same time loss of
29
(76)
messages, duplication or wrong order. When a signalling link fails the load sharing table is calculated again. Changeover order signal (COO) is sent to the remote end via one of available signalling links inside the signalling linkset. It indicates the SLC of the faulty link. The new link may be on the same link set or on an alternate route. Procedure:

When a signalling link is detected as faulty (state change to SIOS) load sharing table of signalling LINKSET is recalculated. The signalling traffic on the faulty link is stopped; new signalling messages for this link are buffered in the delay buffers of alternative signalling links x, y... A changeover message (COO) is sent to the remote end. This changeover message contains the Signalling Link Code (SLC) of the faulty link and the sequence number of the last successfully RECEIVED (not transmitted) SU. The remote end proceeds in the same way. The reception of a changeover message is acknowledged by sending a changeover acknowledge message (COA). Related to the FSN included in the received changeover message the messages, which did not arrive at the remote end, will be sent via the alternative link (= retrieval procedure). After the retrieval the contents of delay buffers are released and the traffic continues normally on all remaining available links.
4.3.4.2
Changeback procedure
The objective of the changeback procedure is to ensure that the transfer of the signalling from the alternative signalling links to a signalling link that has become available again is successful, while avoiding at the same time loss, duplication or missequencing of messages. Procedure:

Automatically the traffic is returned to the now available signalling link. The signalling link selection table is updated and the new information is distributed to all CCSUs. A changeback message (CBD) is sent to the remote end and acknowledged with a (CBA) message.
30
(76)
0) Faulty link
SLC = X
SLC = Y
B
2) COA (BSN = FSN of last correctly received MSU)
1) On link Y, COO (SLC = X, BSN = FSN of last correct received MSU)
3) Change Signalling Link Selection (SLS) table in CCSU
Figure 19.
Changeover to a parallel link
SLC = X
0) Recovered link
SLC = Y
B
4) CBA
1) Traffic to signalling link with SLC = X 2) Update signalling link selection table in all CCSUs
3) CBD
Figure 20.
Changeback to a recovered link
4.3.4.3
Emergency changeover procedure
An emergency changeover takes place when the signalling terminal becomes faulty. It is not possible to obtain the last FSN of the last correctly received SU.
31
(76)
Procedure:

The signalling point initiates an emergency changeover through ECO message. (It does not contain any sequence number). The remote end, if it has the FSN of the last received message, it may acknowledge through COA, else through ECA. In cases of receiving either ECO or ECA, the retransmission buffer is not updated. Instead only new messages are transmitted. Hence some messages may be lost.
4.3.5
4.3.5.1
Signalling route management procedures

Transfer-prohibited procedure
The transfer-prohibited procedure is performed at a signalling point acting as a signalling transfer point (STP) for messages relating to a given destination, when it has to notify one or more adjacent signalling points that they must no longer route the concerned messages via that signalling transfer point. The transfer-prohibited procedure makes use of the transfer-prohibited (TFP) message which contains routing label, transfer-prohibited signal and destination for which traffic transfer is no longer possible. TFP messages are always addressed to an adjacent signalling point. Procedure followed on loss of a destination:
In case of unavailability of a signalling route set (e.g. the route between B and D is not longer available and neither B nor D have any alternative route to reach the destination), B and D send a Transfer Prohibited message including the DPC of the network element, which is no longer reachable to the adjacent signalling points. B sends the DPC of D. D sends the DPC of B. The reception of a transfer prohibited message (TFP) causes a Forced Rerouting.
Additional remark: The transfer prohibited message is not sent to the BSC.
32
(76)
1)
SP B
2) TFP (DPC=D)
SP D
2) TFP (DPC=D)
2) TFP (DPC=B)
SP A SP E SP C
Figure 21.
Transfer-prohibited procedure
4.3.5.2
Forced rerouting procedure
On reception of a transfer prohibited message the forced rerouting procedure is activated. Procedure:
Alternative route to the destination, which was named in the received TFP, is searched and the traffic is re-routed via the new route.
33
(76)
1)
SP B
1) TFP (DPC=D)
SP D
1) TFP (DPC=B) 1) TFP (DPC=D)
SP A
2) FRR: Signalling traffic to D via C
SP E SP C
2) FRR: Signalling traffic to D via E 2) FRR: Signalling traffic to B via C
Figure 22.
Forced rerouting procedure
4.3.5.3
Signalling-route-set-test procedure
The signalling-route-set-test procedure is used at a signalling point to test whether or not signalling traffic towards a certain destination may be routed via an adjacent signalling transfer point. The procedure makes use of the signalling-route-set-test message, and the transfer-allowed and the transfer-prohibited procedures. The signalling-route-set-test message contains:

The label, indicating the destination and originating points The signalling-route-set-test signal The destination, the accessibility of which to be tested The current route status of the destination being tested
Procedure to check availability of the route:
34
(76)
On reception of a TFP message initiates the signalling route set procedure. C and E periodically send an RST message to B and D respectively. This message contains the same DPC as the received TFP message. A and C send RST to B with DPC of D. E sends RST to D with DPC of B. The reception of a RST message causes B respectively D to check the availability of the route. In case the signalling point of the message is still unavailable there is no reply. In case the signalling point of the message is available again, a Transfer Allowed message is sent back.
1)
SP B
RST (DPC=D)
SP D
RST (DPC=D)
RST (DPC=B)
SP A SP E SP C
Figure 23.
Signalling-route-set-test procedure
35
(76)
4.3.5.4
Transfer-allowed procedure
The transfer-allowed procedure is performed at a signalling point, acting as signalling transfer point for messages relating to a given destination, when it has to notify one or more adjacent signalling points that they may start to route to it. The transfer-allowed procedure makes use of the transfer-allowed message which contains:

The label, indicating the destination and originating points The transfer-allowed signal The destination for which transfer is now possible
Transfer-allowed messages are always addressed to an adjacent signalling point. Procedure:
If the route set becomes available again, B and D send a transfer allowed message with the DPC of the network element, which is available again to the adjacent signalling points. B sends the DPC of D D sends the DPC of B
The reception of a TFA message may cause in a controlled rerouting
1)
SP B
2) TFA (DPC=D)
SP D
2) TFA (DPC=D)
2) TFA (DPC=B)
SP A SP E SP C
Figure 24.
Transfer-allowed procedure
36
(76)
4.3.5.5
Controlled rerouting procedure
The controlled rerouting procedure may be performed when a previous unavailable route becomes available again. It has to be distinguished between 3 different cases:
In the case the route that becomes available again has a higher priority than the route actually used, the controlled rerouting procedure is performed. In the case the route that becomes available again has the same priority as the route actually used and load sharing is allowed, the traffic is spread over both routes. In the case the route that becomes available again has the same priority as the route actually used and load sharing is denied, the traffic is still sent over the actually used route.
4.3.5.6
Congestion on link
If even one link is congested on a route, a link is said to be congested. A transfer-controlled procedure is initiated by passing a transfercontrolled (TFC) message to the final destinations. This message may start from an OPC or from a STP. It is sent in every 8th message to the DPC. The TFC message results in informing level four to slow down the signalling messages to the mentioned destination.
4.3.5.7 User part availability control
If the message transfer part is unable to distribute a received message to a local user because that user is unavailable, the message transfer part sends a user part unavailable (UPU) message to the message transfer part at the originating signalling point. When the originating signalling points MTP receives a UPU message, it send an indication to the local user designated in the message. The user should then take appropriate action in order to stop generation of normal signalling information for the unavailable user part. The UPU message contains

The label, indicating the destination and originating point The user part unavailable signal The identity of the unavailable user part The cause of the unavailability
37
(76)
A
UnavailabilityUser part cause Id
1) MSU (DPC = B) 2) Unable to deliver message, subsystem faulty
3) UPU
UPU User part unavailable message
00
2
Destination
14
H1 0001
H0 0100
Routing Label
32
Figure 25.
User part availability control
4.3.6
Signalling link management procedures

The possible states defined for a link are available, unavailable, and inhibited. If the link state is either available of inhibited, MTP level 3 traffic continues to pass. The state of a link may change due to:

Link errors Processor outage Transmission failure Operational activity Link management Processor outage Administrative inhibit procedure Signalling link test procedure
The signalling link management takes care of:

4.3.6.1
Link management
Signalling link management is required for:

Link activation, by using the initial alignment procedure Link restoration, by using the same initial alignment procedure, but initiated by the system Link deactivation
38
(76)
Emergency restart, an initial alignment for links of linkset that has no link available
4.3.6.2
Processor outage
On failure of the signalling terminal processor:

A SIPO LSSU is transmitted to the remote end This initiates a link changeover procedure If the processor fault is removed, a changeback procedure is initiated The traffic may then be rerouting through this link
4.3.6.3
Administrative inhibit procedure
This is done to administratively block a link and not allow it to come up, so as to make some changes, without loss of signalling. The steps involved are:

Checks database to find out if a destination may become unavailable as a result An LSSU (LIN) message is sent to the remote end. The remote end has a choice to reject the process. The remote end sends an LSSU (LIA) as an acknowledgement to inhibit the link. If LIA is not received within a time limit, LIN may be resent. If still no answer is received the process may be aborted. The database is updated with link state as inhibited.
To uninhibit the link: The signalling point that inhibited it may uninhibit by LUN message. A remote destination point may force uninhibit by sending an LFU message. If the link has not been inhibited through the remote signalling point, it may recover the link by performing a changeback procedure.
4.3.6.4 Signalling link test procedure
The link testing procedure may be carried out to

Activate or restore a signalling link Continuously, with a period of 30 seconds.
The procedure is initiated by one end sending an LSSU (SLTM) message with a test pattern. The test is said to be successful if, an LSSU (SLTA) is received within 10 seconds and has the same test pattern. If two consecutive tests fail, the link is declared faulty.
39
(76)
MTP alarms
There are some DX 200 alarms related to the MTP level signalling network management: 1038 UPU message received
The exchange has received a User Part Unavailable message (UPU). This message informs the sending end of a signalling message that the user part of the destination address is not available. Depending on the unavailable user part (TUP and ISUP) the telephone traffic and signalling traffic fail. In the case of SCCP, used services fail. 1072 Signalling link out of service
A signalling link has failed and changed state from IN SERVICE to OUT OF SERVICE, or its initial alignment attempt has failed. If this signalling link is the only one in the signalling link set, the system sets also alarm 2070, LINK SET UNAVAILABLE. If there is an alternative signalling link available in the link set, the system performs a changeover. In this case the signal transmission capacity is also decreased. 1548 MTP confusion message received
An MTP confusion message has been received in the exchange. The signalling point indicated by the originating point code given in the 3rd supplementary information field has not identified the signalling network management message. The heading code of the signalling network management message is given in the 6th supplementary information field. 2064 Route set unavailable
The signalling point cannot be reached because none of the signalling routes of the signalling route set can be used. Signalling traffic to the signalling point concerned is totally blocked. This might cause a situation where CCS calls to the signalling point concerned fail or where, in the worst case, all outgoing calls, for example, fail (the signalling point that cannot be reached is HLR) or all calls of a certain type fail (the signalling point that cannot be reached is for example SCP or SMSC).
40
(76)
2069
Signalling link test failed
The signalling link test has failed. Lockout of the signalling link on level 2 has succeeded, but testing the signalling link on level 3 has failed and the signalling link is not brought into use. The system restarts the signalling link and the signalling link test is repeated.
2070
Link set unavailable
All signalling links in the signalling link set are unavailable. There is no direct connection to the partner exchange to which this link set is connected. If there is an alternative connection between the exchanges, traffic is routed to that connection. If the alarm 2064 ROUTE SET UNAVAILABLE is also on, there is no connection to the partner exchange or another exchange reached through this signalling link set. There is something wrong with the data transmission connections of the links of this link set, and/or links have been blocked. The exchange automatically attempts to re-establish the connection by attempting to restart the links that are in state UA-INS. The alarm 1072 SIGNALLING LINK OUT OF SERVICE is given for each link that is in state UA-INS. 2072 Failure in signalling link activation or restoration
The activation or restoration of a signalling link fails. If there are other available signalling links in the signalling link set, signalling traffic is transmitted through them. Signalling transmission capacity is, however, decreased. The alarm 1072 SIGNALLING LINK OUT OF SERVICE has also been issued about this signalling link.
41
(76)
MTP parameters handling

It is possible to change the functions of signalling network elements by using various parameters. The parameters can be divided into the following groups:
MTP

Level 3 parameters CCS7 signalling network specific parameters Signalling route set specific parameters Signalling link specific parameters
Table 3 shows parameter sets, the effected parts, and MML commands.
Table 3. Parameter sets
Parameter set MTP level 3 parameters Signalling network parameters Signalling link parameter sets Signalling route set parameter sets
Effected parts Message Transfer Part of the signalling system Whole signalling network Signalling links Signalling routes
MML commands NMI NMO NOI NNI
You can modify the functions of the MTP in the Common Channel Signalling (CCS) system to a certain extent by modifying the related parameter values. The parameter values are stored in the parameter files, as listed in Table 4.
42
(76)
Table 4.
Parameter values Content Level 3 parameters Signalling route set parameters Signalling link parameters Signalling network parameters
Name of parameter file L3PARA RSPARA SLNPAR SNWPAR
6.1
Level 3 parameters
The level 3 parameters define the functions of the whole MTP. Some of the parameter values are related to monitoring the functions, while others define various limits. In addition, a parameter can have different values depending on the system and release level. You can handle the level 3 parameters by using the commands NMI and NMM. The command NMI displays the used parameter values grouped by the parameter sets. The command NMM is used to modify the used parameters. The first parameter in the command defines the parameter set (A-F):

A - CSS7 general parameters B overload control parameters C - timing parameters of own signalling point D - parameters for testing/SIO parameters E internal routing parameters F - parameters for CSS7 statistics
With the second parameter in the command we define which parameter we want to modify and give the new value. Error: Reference source not found lists the parameter groups, parameters and their indexes, parameter names and their meanings, the possible values of each parameter and the value range, as well as the recommended value, if that exists.
43
(76)
Table 5. Parameter
A A0-A9
Layer 3 parameters Parameter name/meaning

CSS7 COMMON PARAMETERS DISTRIB_MTP_UNIT_TYP E_0 - 9 Defines those unit types on an exchange where you can create signalling links. Note: Usually, the parameter values need not be changed in the MSC, HLR, BSC or fixed network exchanges, because unit types CCSU, BCSU and BSU have been installed. OVERLOAD CONTROL PARAMETERS MAX_NB_OF_NOTICES The largest amount of incoming messages allowed to enter a centralised unit during a message-monitoring period (100 ms). Purpose of the parameter is to control overload within the exchange. The parameter value should not be changed. TIMER PARAMETERS FOR OWN SIGNALLING POINT LINK_TEST_PERIOD
The sending period for signalling link test messages. The period applies to a group of 10signalling links. This means that when an exchange has 30 links, the test message goes to each link in every third sending period.
Value
B B0
10...30
C0
1500...45000 (10 ms)

4000 (40 sec.)
C1
Q704_T18_LINK_AVAIL_WAI T The time used controlling the availability of the links when a signalling transfer point is restarted. The value depends on the implementation and on the network.
1000... 6000 (10 ms) 2000
C2
Q704_T19_TRA_WAIT
200... 1000 (10 ms)
44
(76)
Parameter
Parameter name/meaning
The timer controlling the reception of all TRA messages while the signalling transfer point is being restarted, when the restarting is made as defined in the CCITT Blue Book. The timer is defined by parameter P7 when the system follows the White Book.
Value
400
C3
Q704_T20_TRAF_RESTARTI NG_TIME The timer controlling the sending of all TRA messages when the signalling transfer point is being restarted.
200... 1000 (10 ms) 400
C4
T111_T26 Defines the timer for resending of TRW messages when the signalling transfer point is being restarted, the timer is defined in the ANSI standards.
1000... 2000 (10 ms) 1500
C5
Q714_T_GUARD Defines the monitoring time used for the signalling connections when the signalling transfer point is being restarted.
600... 9600 (100 ms) 6000
C6
T111_T27 After commencing the restart procedure of a signalling point, all the signalling links of the exchange keep sending the processor outage state indicator to the partner exchanges for a given time (defined in this parameter). This is to make sure that all adjacent signalling points recognise that this point cannot be reached any more.
300... 500 (10 ms)
D D0
PARAMETERS FOR TESTING L2_TEST_MSG_SIO The service information octet used by the CCS System Test Message Generator (MSGGEN) reads the data only when it starts up. After changing the parameter values, the MSGGEN has to be restarted before new values can be included in the contents of the test messages. 0 ... FF 8F (NA0 network user part F)
45
(76)
Parameter
D1
TEST_MSG_LENGTH The length of the SIF part in the MSGGEN messages of the CCS System Test Message Generator. This parameter effects only those messages whose length can be modified. Value for this parameter can be changed while the MSGGEN is running, and the MSGGEN needs not be restarted.
Value
0...272 smaller than 272
E E0
INTERNAL ROUTING PARAMETERS INT_ST7_ROUTE Defines the number of the internal routes that include the PCM time slots used by the signalling link terminals between the unit and the switching network.
E1
EXT_ST7_ROUTE Defines the number of the external routes that include the external PCM timeslots used by the signalling link terminals.
E2
INT_ST7_ROUTE_NAME Defines the name of the internal route that includes the PCM timeslots used by the signalling link terminals between the unit and the switching network.
E3
EXT_ST7_ROUTE_NAME Defines the name of the external route that includes the external PCM timeslots used by the signalling link terminals.
E4
INTERNAL_ROUTING_FO R_SL Defines whether the system tries to update the signalling link related PCM/TSL data into the
46
(76)
Parameter
routing data of the CM3PRO. Used only on test exchanges that have no group switch (GSW).
Value
F F0
CSS7 STATISTICS PARAMETERS SUCC_UNIT_COLL_COU NT_5 Defines the number of MTP decentralised units from which the statistics counters are collected during a 5-minute monitoring period. 2... 10 4
F1
SUCC_UNIT_COLL_COU NT_30 Defines the number of MTP decentralised units from which the statistics counters are collected one by one during a 30-minute monitoring period.
2... 20 10
F2
SL_LOG_TYPE Type of signalling link event log, which can be either NORMAL or CYCLIC. When the event log is stored in the normal buffer, the buffer can be emptied with command OLE.
CYCLIC CYCLIC
F3
SP_LOG_TYPE Type of the signalling point event log, which can be either NORMAL or CYCLIC. When the event log is stored in the normal buffer, the buffer can be emptied with command ONE.
CYCLIC CYCLIC
F4
SL_LOG_MAX_COUNT The maximum amount of changes in the state of a signalling link that can be stored in the buffer.
16... 32 16
F5
SP_LOG_MAX_COUNT The maximum amount of changes in the state of a
16... 32 16
47
(76)
Parameter
signalling point that can be stored in the buffer.
Value
F6
USER_NOTICE_ACT Controls the notices for the users statistics output.
ACTIVE, PASSIVE
F7
SCCP_LOG_TYPE Type of the SCCP event log buffer. ZOTE to clear the buffer.
CYCLIC
F8
TC_LOG_TYPE
CYCLIC
Type of the TC event log buffer. ZOTE to clear the buffer
6.2
CCS7 signalling network-specific parameters

These parameters apply to the whole signalling network. All parameters that are used specifically in the CSS7 signalling network are listed in this section. There are also short descriptions on their meanings. Parameter values vary depending on the system used and the release level. The CSS7 signalling network-specific parameters are managed by using the commands NMO and NMC. The command NMO outputs the used parameter values in each parameter set. The command NMC is used to modify the used parameters. The first parameter in the command defines the parameter set (J-M) of the parameter that you want to modify:

J - network-specific parameters K - parameters for controlling international congestion L - parameters for controlling national congestion M - SLS parameters
The second parameter in the command defines the parameter you want to modify and its new value. Table 6 lists the parameter groups, parameters and their indexes, parameter names and their meanings, all possible values, and quality of parameter value and the recommended value, if any.
48
(76)
Table 6. Parameter
J J0
CCS7 signalling network-specific parameters Parameter name/meaning

NETWORK SPECIFIC PARAMETERS CONGESTION_METHOD Three congestion methods exist: international method (INT), national method without prioritisation of signalling messages (NAT) and national method with prioritisation of messages (NATP). INT method: The congestion criteria is the filling degree (1 limit) of the sending buffer whose limit values are defined in the Signalling Link Parameter File (SLNPAR). The congestion level directly follows the occupancy of the buffer. Timers T29 and T30 are used to control traffic restriction according to definitions made with parameters K0-K5. NAT method: The congestion criteria is the filling degree (1 limit) of the sending buffer whose limit values are defined in the Signalling Link Parameter File (SLNPAR). Timers Tx and Ty determine the congestion level. The congestion level can have values 1-3, and traffic is restricted as required by the prevailing congestion level and as defined in parameters L1-L3. NATP method: The congestion criteria is the occupancy (3 limits) of the sending buffer whose limit values are defined in the Signalling Link Parameter File (SLNPAR). The NO, INT, NAT, NATP
Value
49
(76)
Parameter
congestion level determines how the messages are handled (for example, on congestion level 3, only messages with priority 3 or higher are routed forwards).
Value
INTERNATIONAL CONGESTION CONTROL METHOD PARAMETERS NB_OF_UP_LEVELS The amount of restriction levels for the originating traffic concerning the INT method. 1 ... 5
K0
K1
RESTRICT_PR_OF_UP_L 1 The restriction percentage for the originating traffic on restriction level 1. Timers T29 and T30 determine the restriction level. The default value is 40%.
0 ... 40 %
K2
20 ... 60 %
K3
40 ... 80 %
K4
60 ... 90 %
50
(76)
Parameter
K5
Value
80 ...100 %
K6
Q764_T29 When the first congestion indication is received by the ISDN User Part (ISUP), the traffic load into the affected destination point code is reduced by one step. At the same time timers T29 and T30 are started. During T29 all received congestion indications for the same destination point code are ignored in order to not reduce traffic too rapidly. Reception of a congestion indication after the expiry of T29, but still during T30, will decrease the traffic load by one more step and restart T29 and T30. This step-by-step reduction of the ISUP signalling traffic is continued until maximum reduction is obtained by arriving at the last step. If T30 expires (for example, no congestion indications are no more received during the T30 period) traffic will be increased step-by-step and T30 will be restarted unless full traffic load has been resumed.
30 ... 60 50
K7
Q764_T30 See K6.
500 ... 1000 600
NATIONAL CONGESTION CONTROL METHOD PARAMETERS PREDETERMINED_CONG _LEVEL Defines the default value 1 ... 3
L0
51
(76)
Parameter
for the congestion level that is reached when the buffer occupancy limit is exceeded for the first time, or when the congestion level is coded as 0 in a received TFC message.
Value
L1
RESTRICT_PR_OF_MTP_ L1 The restriction percentage for originating traffic on congestion level 1.
0 ... 50 %
L2
20 ... 80 %
L3
50 ...100 %
L4
Q704_TX The timer raises the congestion level when the filling limit of the transmit buffer has been exceeded. The smaller the parameter value is, the faster the congestion level is raised. (If the signalling link congestion status is set to s and the buffer occupancy continues to be above the set congestion threshold during Tx, the signalling link congestion status is updated by the new value s + 1.)
5 ... 200 200 ms
L5
Q704_TY The timer lowers the congestion level when congestion has been on but then the filling degree of the sending buffer is decreased and goes below the set limit. The smaller the Ty is, the faster the congestion level
5 ... 200
52
(76)
Parameter
decreases. (If the signalling link congestion status is set to s and the buffer occupancy continues to be below the abatement threshold during Ty, the signalling link congestion status is updated by the new value s - 1.)
Value
M M0
SLS BITS LINK_SLS_BIT_MASK Defines which SLS bits are used in load sharing within the link set. ITU: 00001111 ANSI: 11111110
M1
ROUTE_SLS_BIT_MASK Defines which SLS bits are used in load sharing between the routes. ITU: 00001111 ANSI: 00000001 4,5,8
M2
SLS_LENGTH Defines the length of SLS within the signalling network. In ITU networks, the SLS is 4 bits, while in ANSI networks it is 5 or 8 bits. ITU: 4 ANSI: 5 or 8.
6.3
Signalling link specific parameters

The parameters in the signalling link specific parameter set define how the signalling links function. All signalling link-specific parameters are listed in this section. There are also short descriptions on their purposes. Parameter values vary depending on system and release level. The signalling link -specific parameters are managed by using the commands in the command group NO. The commands can be used to modify existing parameter sets or to create new ones. Before you start modifying an existing parameter set, check that all signalling links using this parameter set have been deactivated. The new values become effective when the links are activated again. To create a new parameter set, you can replicate (copy and rename) an old parameter set and modify its values.
53
(76)
The command NOI outputs the values of parameters belonging to the defined sets, and the command NOM can be used to modify the parameter values in an existing parameter set. In the command, the name and number of the parameter set are defined. In addition, the identifier of the parameter group is defined according to the parameter that you want to change:

A - miscellaneous parameters on MTP level 2 B - control parameters for the error ratio on MTP level 2 (as defined by ITU) C - timer parameters for MTP level 2 (as defined by ITU) D - miscellaneous parameters on MTP level 3 E - signalling congestion control parameters F - timer parameters for MTP level 3
The second parameter in the command defines which parameter from the parameter set you want to modify, and gives the new value. Table 7 lists the parameter groups, parameters and their indexes, parameter names and their meanings, all possible values, quality of the value and the recommended value, if any
Table 7. Parameter
A A0
Signalling link specific parameters Parameter name/meaning

MISCELLANEOUS MTP LEVEL 2 PARAMETERS LI_CODING Controlling the LI coding. BTNR is a specific method in BTNR Spec. (UK). STANDARD, BTNR STANDARD
Value
A1
BIT_D_CODING_IN_LSSU Controlling the D bit coding in the LSSUs. BTNR is a specific method in BTNR Spec. (UK).
STANDARD, BTNR STANDARD
A2
BIT_D_CHECK_IN_LSSU Controlling the D bit checking in the received LSSUs. (1H Bit D checked from the received LSSU).
YES, NO YES
A3
L2_ERROR_CORRECTIO
BASIC, PCR
54
(76)
Parameter
N Controlling the error rate monitoring in the transmission direction. PCR is for preventive cyclic retransmission for satellite links.
Value
BASIC
A4
SN_RANGE Maximum value for backward sequence number and forward sequence number of signalling unit.
404095 127
A5
JT_Q703_K Defines the number of transmitted MSU messages without positive acknowledgement. This parameter is relevant only in Japanese signalling network.
40127 40
MTP LEVEL 2 ERROR RATE MONITORING PARAMETERS SUERM_T Controlling the error rate of the message unit: SUERM_T, SUERM_D and SUERM_N (see CCITT Q703 10.2). 8 ... 512 64
B0
B1
SUERM_D Controlling the error rate of the message unit: SUERM_T, SUERM_D and SUERM_N (see CCITT Q703 10.2).
16 ... 1024 256
B2
SUERM_N Controlling the error rate of the message unit: SUERM_T, SUERM_D and SUERM_N (see CCITT Q703 10.2).
8 ... 24 16
B3
AERM_TIN Controlling the error rate of
1 ... 16 4
55
(76)
Parameter
the alignment AERM_TIN, (see CCITT Q703 10.3).
Value
B4
AERM_TIE Controlling the error rate of the alignment AERM_TIE (see CCITT Q703 10.3).
1 ... 8 1
B5
AERM_M Controlling the error rate of the alignment AERM_M (see CCITT Q703 10.3).
1 ... 16 5
B6
AERM_N Controlling the error rate of the alignment AERM_N (see CCITT Q703 10.3).
8 ... 24 16
B7
PCR_N1 (preventive cyclic retransmission) PCR_N1, number of MSUs that can be resent.
1 ... 127 127 300 ... 6000 800 8 ... 793544 99193
B8
PCR_N2 PCR_N2, number of MSUs that can be resent.
B9
EIM_TE Error interval monitor parameter (see ITU-T Q703 A.10.2)
B10
EIM_UE Error interval monitor parameter (see ITU-T Q703 A.10.2)
1 ... 198384 24798
B11
EIM_DE Error interval monitor parameter (see ITU-T Q703 A.10.2)
1 ... 11328 1416
B12
JT_Q703_TE Defines the normalized time for error rate monitoring. This parameter is relevant only in Japanese signalling network.
20 ... 30 (1 ms) 24
56
(76)
Parameter
C C0
MTP LEVEL 2 TIMER PARAMETERS Q703_T1 Q703_T1, Alignment Completed timer.
Value
130 ... 500 (0.1s) 400 50 ... 1500 (0.1s) 100 10 ... 116 (0.1s) 10 23 ... 95 (0.1s) 82 8 ... 30 (0.1s) 10 30 ... 72 (0.1s) 50 5 ... 20 (0.1s) 10 8 ... 12 (0,01 s) 10
C1
Q703_T2 Q703_T2, No Alignement timer.
C2
Q703_T3 Q703_T3, Alignment timer.
C3
Q703_T4 Q703_T4, Length of Test Period timer.
C4
Q703_T5 Q703_T5, SIB Transmission timer.
C5
Q703_T6 Q703_T6, Remote End Congestion timer.
C6
Q703_T7 Q703_T7, Delayed Acknowledgement timer.
C7
Q703_T8 Error interval monitor timer
C8
JT_Q703_TF Defines interval for sending FISU when there is no MSUs transmitted. This parameter is relevant only in Japanese signalling network.
20 ... 30 (1 ms
24
C9
JT_Q703_TO Defines interval for transmitting SIO and SIE messages used for initial set-up and during verification. This parameter is relevant only in Japanese signalling network.
20 ... 30 (1 ms) 24
57
(76)
Parameter
C10
JT_Q703_TS Defines interval of SIOS to be transmitted during suspension. This parameter is relevant only in Japanese signalling network.
Value
10 ... 30 (1 ms) 24
D D0
MISCELLANEOUS MTP LEVEL 3 PARAMETERS PERIODIC_LINK_TEST_D ENIED Controlling the transmission of signalling link test messages. YES, NO NO
D1
MAX_LENGTH_OF_SIF Maximum length of the SIF field in the MSU message.
272 272 1 ... 5 3 YES, NO NO YES, NO ITU-T: YES ANSI: YES JAPAN: NO (NTT), YES (TTC YES, NO NO
D2
INHIBIT_ATTEMPT_LIMIT Limit for repeated attempts to inhibit a link.
D3
INHIBIT_TEST_DENIED Controlling the inhibition of a test procedure.
D4
ECO_SENDING_ALLOWE D Defines the control of Emergency Changeover procedure.
D5
INHIBITION DENIED
D6
SIN DENIED
YES, NO NO
D7
SIPO DENIED
YES, NO NO
D8
LINK SUSPEND DENIED
YES, NO YES
D9
FALSE CONG DENIED
YES, NO YES
58
(76)
Parameter
D10
LINK SRT DENIED
Value
YES, NO YES
SIGNALLING CONGESTION CONTROL PARAMETERS CONG_FILTERING_TIME Defines the time after which continuing congestion on a signalling link is reported to level 3. This feature keeps the signalling traffic control procedures from starting during very short-time peak loads. 30 (0.3s). 10 ... 100 (0.01s) 1
E0
E1
BUFF_FILTERING_TIME Defines the time after which continuing congestion on a signalling link is reported to level 3 while signalling message buffering is active. This feature keeps the signalling traffic control procedures from starting in special situations such as changeovers, changeback, and controlled rerouting. 150 (1,5s).
50 ... 300 (0.01s) 1
E2
CONG_ONSET_THRESH OLD1 Reports the occupancy of the transmission buffer that is interpreted as level 1 congestion. Congestion can be set for threshold values 0-127; if the value is 128-255, signalling link congestion is never on. The limit for congestion onset (messages) is 49.
2 ... 1000 49
E3
CONG_ABATE_THRESHO LD1 Reports the occupancy of the transmission buffer that is interpreted as ending for level 1 congestion (that has been on). It is advisable to set the release level of
1 ... 800 2
59
(76)
Parameter
congestion lower than the activation level to avoid vibrations. The limit for congestion reset (messages) is 2.
Value
E4
CONG_DISC_THRESHOL D1 Reports the occupancy of the transmission buffer that enables the signalling terminal software to set the signalling message. This sets the destroy status in the transmission mailbox. When the CCSEND program block notices that the destroy status is set, it destroys the signalling messages addressed to the mentioned signalling terminal. The threshold values for the destroy status are selected from the range 0-127; if the value is 128-255, the status is not set. However, when the transmission buffer fills up, signalling messages have to be destroyed. The status value must therefore be higher than the limit for signalling link congestion in order to avoid unnecessary message destruction. The limit for message discarding (messages) is NOT IN USE.
0 ... 2500, NOT IN USE
E5
CONG_ONSET_THRESH OLD2 CONG_ONSET_THRESH OLD2,CONG_ABATE_TH RESHOLD2,CONG_DISC_ THRESHOLD2,CONG_ON SET_THRESHOLD3,CON G_ABATE_THRESHOLD3 and CONG_DISC_THRESHOL D3 are similar to the abovementioned parameters when the congestion control method that is used has several levels. The parameter values on level 2
2 ... 1000, NOT IN USE
60
(76)
Parameter
must be higher than the corresponding values on level 1, and values on level 3 must be higher than those on level 2 in order to get the congestion method to work properly. When the congestion method uses only one level, set the parameter values on levels 2 and 3 as 255 = 0FFH. See parameters E2, E3.
Value
E4 & E6 E7 E8 E9 E10 E11
CONG_ABATE_THRESHO LD2 CONG_DISC_THRESHOL D2 CONG_ONSET_THRESH OLD3 CONG_ABATE_THRESHO LD3 ONG_DISC_THRESHOLD 3 T111_T31_ONSET_THRE SHOLD Congestion threshold for starting timer T111_T31.
1 ... 800, NOT IN USE See parameters E5 and E3 10 ... 2500, NOT IN USE See parameters E5 and E4 2 ... 1000, NOT IN USE See parameters E5 and E2 1 ... 800, NOT IN USE See parameters E5 and E3 10 ... 2500, NOT IN USE See parameters E5 and E4 1, 2, 3, NOT IN USE 0 1, 2, 3, NOT IN USE 0 100 ... 900 200
E12
T111_T31_RESET_THRE SHOLD Congestion threshold for resetting timer T111_T31.
E13
SL_LOAD_THRESHOLD Allows maximum value for signalling link load in Merlangs without notification.
F F0
MTP LEVEL 3 TIMING PARAMETERS Q704_T1 Delay to avoid message mis-sequencing on changeover. 5 ... 12 (0.1s) 8
F1
Q704_T2 Waiting for changeover acknowledgement.
7 ... 20 (0.1s) 14
61
(76)
Parameter
F2
Q704_T3 Time controlled diversiondelay to avoid missequencing on changeback.
Value
7 ... 12 (0.1s) 8
F3
Q704_T4 Waiting for changeback acknowledgement (first attempt).
5 ... 12 (0.1s) 8
F4
Q704_T5 Waiting for changeback acknowledgement (second attempt).
5 ... 12 (0.1s) 8
F5
Q704_T12 Waiting for un-inhibition acknowledgement.
8 ... 12 (0.1s) 10 6 ... 15 (0.1s) 10
F6
Q704_T13 Waiting for force uninhibition acknowledgement.
F7
Q704_T14 Waiting for inhibition acknowledgement.
8 ... 30 (0.1s) 20 8 ... 60 (0.1s) 10
F8
Q704_T17 Delay to avoid oscillation of initial alignment failure and link restart.
F9
Q704_T22 Local inhibit test timer.
180 ... 600 (1s) 180 180 ... 600 (1s) 180 8 ... 120 (0.1s) 80
F10
Q704_T23 Remote inhibit test timer.
F11
Q707_T1 Waiting for signalling link test message acknowledgement.
F12
T111_T19 Time supervision for setting an alarm about a signalling link that refuses to start up, as defined in ANSI standards.
120 ... 600 (1s) 120
62
(76)
Parameter
F13
T111_T20 Control for local inhibition testing as defined in ANSI standards.
Value
90 ... 120 (1s) 120
F14
T111_T21 Control for remote end inhibition testing as defined in ANSI standards.
90 ... 120 (1s) 120
F15
T111_T31 False link congestion detection timer.
10 ... 120 (1s) 10 5 ... 120 (1s) 5 0 ...600 (1 s) 30
F16
T111_T32 Link oscillation timer Procedure A.
F17
JT_Q704_TS Defines the time for transmitting SIOS on a periodical basis during suspension. This parameter is relevant only in Japanese signalling network.
F18
JT_Q707_T10 This parameter is relevant only in Japanese signalling network.
0..600 (0.1s) 100
F19
ALIGN_RESPONSE_WAIT
40
6.4
Signalling route set specific parameters

The parameters included in the parameter set of the signalling route set are used to handle the functions of the whole Message Transfer Part (MTP). This section introduces all parameters that are specific to each signalling route set and describes their purposes briefly. The parameter values vary depending on the used system and release level. The signalling route set-specific parameters are managed using the commands in the command group NN. You can use the commands to create new parameter sets or to modify the values of individual
63
(76)
parameters included in the parameter sets. When you have modified the values of existing parameters, the new values become effective immediately. To create a new parameter set, you can replicate (copy and rename) an old parameter set and modify its values so that they suit the present needs. The command NNI outputs the values of the parameters in the selected parameter sets. The command NNM is used to modify the parameter values in an existing parameter set. In the command, the name and number of the parameter set are defined. In addition, the identifier of the parameter group is defined according to the parameter that you want to change:

A Common timers for all destinations B Signalling point restart timers C Adjacent signalling point parameters D Common parameters of all signalling points
Signalling route set specific parameters (* -parameter valid locally only) Parameter name/meaning
COMMON TIMERS OF ALL DESTINATIONS Q704_T6 Delay to avoid message mis-sequencing on controlled rerouting. The parameter sets the time that is waited during controlled rerouting before traffic is activated to the destination point via a new or alternative transfer point. 5 ... 20 (0.1s) 8
Table 8.
Parameter
A A0
Value
A1
Q704_T8 Time supervision for inhibition of the Transfer Prohibited messages. The Transfer Prohibited messages generated by the reply system are not sent to the destination point, if othersimilar messages have been sent there during the time specified by the parameter.
5 ... 20 (0.1s) 10
64
(76)
Parameter
A2
Q704_T10 Time supervision for repetition of test messages in the signalling route set. Test messages related to another signalling point are sent at intervals defined by the time parameter.
Value
10 ... 120 (1s) 31
A3
Q704_T11 Transfer restricted time supervision. This parameter sets the time for how long a signalling link set, that uses another signalling point as the transfer point, has to be faulty before it is set in a long-term failure state. When this state is set for a signalling link set, transfer restricted messages are sent to the adjoining signalling points. The messages concern all route sets where one of the primary routes has been using the failed link set and where the traffic is now directed to secondary routes.
30 ... 90 (1s) 60
A4
Q704_T15 Signalling point Z receives another transfer-controlled message related to the same destination within T15 after the reception of the last transfer-controlled message related to destination X. If the value of the congestion status carried in the new transfer controlled message is higher than the current value of the congestion status of the signalling route set towards destination X, then the current value is updated to the higher one. If T15 expires after the last update of the signalling
20 ... 30 (0.1s) 25
65
(76)
Parameter
route set toward destination X in a transfer-controlled message related to the same destination, the signalling-route-setcongestion-test procedure is invoked.
Value
A5
Q704_T16 If a Transfer Controlled message related to the concerned destination is received within T16 after sending a signalling-routeset-congestion-test message, the signalling point updates the congestion status of the signalling route set. If T16 expires after sending a signalling-route-setcongestion-test message without a Transfer Controlled message related to the concerned destination having been received, the signalling point changes the congestion status associated with the signalling route set.
14 ... 20 (0.1s) 15
A6
T111_T18 A signalling point starts the MTP restart procedure when its first link is in service at level 2. Restarting the MTP: - if it has the transfer function, it starts timer T18;
2 ... 20 (1s) 3
A7 B B0 *
JT_Q707_T10 SIGNALLING POINT RESTART TIMERS Q704_T21/T111_T25 Q704_T21: The waiting period before traffic is restarted via an adjacent signalling point. Traffic on the routes using the adjacent signalling point is started only when the time
100
20.70 (1s) Blue Book 31 White Book 64 ANSI 64
66
(76)
Parameter
defined in this parameter has past after the restart of the adjacent point (or when the point has sent the Traffic Restart Allowed message). T111_T25: Waiting for the Traffic Restart Active message.
Value
B1
T111_T28 Signalling point X starts timer T28 either when the first signalling link goes into state In Service on level 2, or when the first signalling link becomes available on level 3. This parameter is used only in networks built according to the ANSI standards.
3..35 (1s) 30
B2
Q704_T19_WHITE/T111_T 29 Supervision timer during the MTP restart to avoid possible ping-pong (back and forward) of TFP, TFR and TRA messages.
60 ..80 (1s) 68
B3 *
T111_T30 If the receiving point has the transfer function, it starts timer T30 and then sends a Traffic Restart Waiting message followed by the necessary Transfer Restricted and Transfer Prohibited messages. Preventive Transfer Prohibited messages are required for traffic currently being routed via the point from which the unexpected Traffic Restart Allowed or Traffic Restart Waiting messages were received. It also sends a Traffic Restart Allowed message.
20 ... 40 (1s) 30 ANSI
ADJACENT SIGNALLING POINT PARAMETERS
67
(76)
Parameter
C0 *
TRM_DENIED Use of message pair TRA/TRW is denied in network management. In an ANSI network, the use of TRW in connection with the SP restart is denied.
Value
YES, NO NO
C1 *
TRM_EXPECTED This parameter controls the use of message pair TRA/TRW. TRA_EXPECTED means that traffic restart is allowed. When the signalling link set is used, it controls the wait for the message reception. TRA_WAITING controls the waiting of message reception when the signalling link set is taken into use. TRA_DENIED means that sending of Traffic Restart Allowed messages is denied.
YES, NO YES
C2 *
SP_RESTART_TYPE Controlling the denial of the signalling point restart procedure. When this procedure is denied, the restart procedure of the adjacent signalling point is not used. When its own signalling point is restarted, the Traffic Restart Allowed message is not sent to the adjacent SP, either.
BLUE, NONE /WHITE/ANSI BLUE
C3 *
INDIRECT_ROUTES_DEF AULT
AVAILABLE, RESTRICTED, UNAVAILABLE, TFM BASED AVAILABLE
Parameter for controlling the signalling link set restarts in situations when the adjacent SP has not been started. The possible parameter values are available, restricted, unavailable, and TFM based.
68
(76)
Parameter
C4 *
TFM_CONTROL
Value
ALL ALLOWED, BROADCAST DENIED, ALL DENIED ALL ALLOWED
Control parameter for broadcasting messages: Transfer Allowed, Transfer Restricted, and Transfer Denied. When the parameter denies broadcasting of messages, and an SP becomes either available or unavailable, it is not reported to the adjacent SP. C5 * RESP_TFM_CONTROL
TFR ALLOWED, TFP ALLOWED, TFPFOR KNOWN, TFM DENIED TFP ALLOWED
Control parameter for the response method messages. Possible parameter values are TFR allowed, TFP allowed, TFP for known, and TFN denied. C6 * TFR_DENIED Control parameter for the use of the Transfer Restricted procedure. If the use of this procedure is denied, the Transfer Restricted messages coming from the source point are not handled, and Transfer Restricted messages are not sent to the destination point. Instead, the system sends Transfer Allowed messages (unless their use is also denied). D COMMON PARAMETERS OF ALL SIGNALLING POINTS TFR_SENDING_BASIS Control parameter for managing overload on a spare route when the last available route becomes unavailable. Possible parameter values are
YES, NO YES
D0
NONE, ITU, ANSI NONE
69
(76)
Parameter
NONE (no TFR messages broadcast), ITU (follows ITU-T Rec. Q704), and ANSI (examines state of timer T11).
Value
D1
CIRC_ROU_PREV_IN_US E Control parameter for restricting the occurrence possibilities of circularly routed messages. When this parameter has the value YES, an extra Transfer Prohibited message is used for one of the destination signalling points. If traffic to the point travels via alternative routes, the system sends the Transfer Prohibited message about that point to all adjoining signalling points. It then orders all traffic to switch to the point via other signalling points.
YES, NO NO
D2
TFC_DENIED Control parameter for the Transfer Controlled message. If the parameter has the value NO and denies the message, the Transfer Controlled messages are not sent to the destination point.
YES, NO NO
D3
CONG_LEVEL_SUPPORT Control parameter for the Transfer Controlled messages congestion level encoding. If the parameter has the value NO and the message control is inactive, the system sets congestion level 0 for the TFC messages directed to the destination point. Otherwise they get a congestion level that is defined by the over loaded signalling terminal. This control parameter can also be used to define the
NONE, TFC TFC
70
(76)
Parameter
overload of a destination point to be monitored using the Congestion Level Test messages.
Value
D4
CONFUSION_MSG_DENI ED Control parameter for the MTP Confusion message. If sending the messages is prohibited, the messages are not transmitted to the destination point. This feature is implemented as defined in standard BTNR 146.
YES, NO YES
D5
UPU_ALLOWED This parameter either allows (YES) or denies (NO) UPU message sending.
YES, NO NO
D6
RST_ON_TFP_ALLOWED This parameter either allows (YES) or denies (NO) immediate sending of route set test (RST) message when transfer prohibited message (TFP) is received. When this parameter has value NO, the RST message is sent after the Q704_T10 timer has expired.
YES, NO ITU: YES ANSI: YES JAPAN: NO
D7
SUPPORT_OF_M3UA_N W_APP Control of using Network Appearance parameter in the "M3UA signalling network management messages".
YES, NO YES
D8
USE_OF_M3UA_NW_SN M Control of sending M3UA signalling network management messages.
YES, NO NO
D9
SRT DENIED
YES, NO
71
(76)
Parameter
D10
USN DENIED
Value
YES, NO
72
(76)
Appendix
Appendix
73
(76)
References
References
74
(76)
Glossary
Glossary
75
(76)
Index
Index
76
(76)

MTP Document

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

MTP Document

Загружено:

Авторское право:

Доступные форматы

Switching Core Network Signalling

Message Transfer Part

Nokia Siemens Networks

Nokia Siemens Networks

Nokia Siemens Networks

Nokia Siemens Networks

MTP parameters handlingAppendix

Nokia Siemens Networks

MTP parameters handlingAppendix

Level 3 Level 2 Level 1

Nokia Siemens Networks

MTP parameters handlingAppendix

Layer 4 (User Part)

Other User Parts

Signalling Network Management

Signalling Message Handling

Signalling Data Link Function

Nokia Siemens Networks

MTP parameters handlingAppendix

Signalling end points (SEP) Signalling transfer points (STP)

Addressing signalling points

Nokia Siemens Networks

MTP parameters handlingAppendix

Signalling link DPC = X

Signalling link DPC = X

Components of a signalling network, SEP and STP

Signalling Point Codes

SPC and network indicator

Nokia Siemens Networks

MTP parameters handlingAppendix

MTP Layer 2: Signalling Link

Nokia Siemens Networks

MTP parameters handlingAppendix

Level 2 functions are specified in Recommendation Q.703.

TransmitBuffer Buffer Transmit

Controller Controller FSN BSN

ReceivedBuffer Buffer Received

SequenceNumber Number Sequence Generation Generation Checksum Checksum Generation Generation

Retransmission Retransmission Buffer Buffer

FlagGeneration Generation Flag andBit-stuffing Bit-stuffing and

FlagDetection Detectionand and Flag Bit-stuffing Bit-stuffing

MTP Layer 2 functions

Nokia Siemens Networks

MTP parameters handlingAppendix

Link status signal units (LSSU) Fill-in signal units (FISU)

Nokia Siemens Networks

MTP parameters handlingAppendix

First bit transmitted

8 16 8n, n>2 8 2 6 1 length indicator >2 and 63

First bit transmitted

First bit transmitted

Signal unit formats

Nokia Siemens Networks

MTP parameters handlingAppendix

First bit transmitted

Bit Bit Bit Bit Bit Bit

000 001 010 , 011 100 101

Status Status Status Status Status Status

indication indication indication indication indication indication

O (SIO) N (SIN) E (SIE) OS (SIOS) PO (SIPO) B (SIB)

Link status indications in LSSU

Nokia Siemens Networks

MTP parameters handlingAppendix

Basic error correction method