04 Mn2513eu11mn 0001 Administration Signaling

8/10/2019 04 Mn2513eu11mn 0001 Administration Signaling

1/87

Administration of the Signaling Network Siemens

MN2513EU11MN_0001 2002 Siemens AG

1

Contents1 Control of the signaling network 3 1.1 SSNC as signaling network controller 4 1.2 Functions within the SSNC 6 1.3 Multiple SS7 networks 9 1.4 Message flows 11 2 Message transfer part 20 2.1 Level 1 path creation 21 2.2 Level 3 objects 51 3 User parts 70

3.1

Overview 71

3.2 Administration of the SCCP and its user parts 73

Administration of the Signaling Network


2/87

Siemens Administration of the Signaling Network

MN2513EU11MN_0001

2002 Siemens AG

2


3/87



3

1 Control of the signaling network


4/87


MN2513EU11MN_0001

2002 Siemens AG

4

1.1 SSNC as signaling network controller

To control the SS7 signaling system, the Signaling System Network Controller(SSNC) is used in D900

It provides the protocol functions of the message transfer part (MTP) and parts of thesignaling connection control part (SCCP). The open architecture of the SSNC isbased on Solution O.N.E (optimized network evolution) technology, i.e. messagetransfer within the SSNC is based on ATM.

Connection to the CP113 is done via a CP processor, the AMP. The signalingchannels are supplied by means of PCM30/24 via LTGs or directly by the network.Communication with users in the LTGs is provided directly via high-speed interfacesover the MBD.

The SSNC has its own OAM platform "Switch Commander". For operation, it isprovided with V24/LAN interfaces for the connection of NM systems.

Thanks to its own OAM platform, the SSNC can also be used as a standalonenetwork element (i.e. without D900 environment).

TIPThis document only describes the functionality of the SSNC as signaling networkcontroller. It does not describe special signaling interfaces like the signaling on the Iuinterface for UMTS or on the Gb interface for GPRS. These interfaces are discussedin the corresponding UMTS and GPRS courses.


5/87


6/87


MN2513EU11MN_0001

2002 Siemens AG

6

1.2 Functions within the SSNC

The SSNC implements the functions of the message transfer part MTP and parts ofthe SCCP (SCCP global title translation and SCCP management). This is shown inthe following diagram, using a protocol stack.

Signaling System No.7 is divided into two main parts so that it can be adaptedoptimally to the diverse requirements of its various users:

the message transfer part MTP and the user parts UP.

Message Transfer PartThe message transfer part (MTP) is used in CCS7 by all user parts as a transportsystem for message exchange. Messages to be transferred from one user part toanother are given to the message transfer part which ensures that the messagesreach the addressed user part in the correct order, without information loss,duplication or sequence alteration and without any bit errors.

Functional levels of the MTP

Level 1 defines the physical, electrical and functional characteristics of a signalingdata link and the access units. Level 1 represents the bearer for a signaling link. In adigital network, 64-kbit/s channels are generally used as signaling data links.

Level 2 defines the functions and procedures for a correct exchange of usermessages via a signaling link. The following tasks must be carried out in level 2:

delimitation of the signal units by flags and elimination of superfluous flags error detection using check bits and error correction by retransmitting signal units restoration of fault-free operation, e.g. after disruption of the signaling data link.Level 3 defines the interworking of the individual signaling links. A distinction is madebetween the two following functional areas:

message routing and message distribution signaling network managementIn the SSNC these functional levels are mapped on the functional units MP:SLT(signaling link terminal) and MP:SM (signaling manager). The MP:SLT performsMTP-level 1 (message transfer), MTP-level 2 (error correction) and MTP-level 3(message handling incl. allocation). These SLT functions are logically combined andare performed by one or more MPs. Depending on system usage of the networknode, the SSNC can be provided with up to 47 MP:SLT. Per SLT up to 60 signalingchannels (64kbit/s) may be connected, but not more than 1500 links in total!

The MP:SM functional unit supports MTP-Level 3 network management and hoststhe routing database for the signaling network. Thus, each MP:SLT has an internalconnection to the MP:SM.


7/87


8/87


MN2513EU11MN_0001

2002 Siemens AG

8

User Parts

The function, structure, format and coding of the messages as well as the connection

sequences and the procedures for cooperating with other signaling systems(interworking) are stipulated in the user parts. The user parts therefore control thesetup and release of circuit connections, the handling of service features as well asadministration and maintenance functions for the signaling channels (SCCPmanagement). The ISDN- and telephone user parts ( ISUP/TUP ) are located in theLTGs. The SCCP is located in the SSNC and is the only user part in case the SSNCis operated as Signaling Relay Point (SRP).

MTP L1

MTP L2 MTP L2

ISUP

GTT GTT

TCAP

MAPs etc.BSSAP

USER PartL4

MTP L3 MTP L3

TCAP ISUP

BSSAP

USER PartL4

SCCP SCCP

ITU-T SS7 Protocol Stack

MAPs etc.

Fig. 2 MTP and user parts


9/87



9

1.3 Multiple SS7 networks

The feature 'Multiple SS7 Networks' expands the range of network planning optionsin deregulated markets with many operating companies. With this feature, up to 32Signaling System No. 7 (SS7) routing domains (internal networks) can beadministered in one signaling network node with SSNC. This feature affects MTP,SCCP and the SS7 user parts.

This means that a node can be connected to up to 32 separate signaling networks,which are allocated to the ITU standard networks (NAT0/1, INAT0/1).

The 'Multiple SS7 Networks' feature is fully compatible with ITU-T SS7 standards, i.e.it is transparent to all SS7 protocols.

Each SS7 network can be individually administered; in this way up to 32 ownsignaling addresses can be set up in one node. Signaling point allocation iscompletely flexible.

The maximum capacity of the signaling network elements (1500 signaling links, 1024signaling trunk groups, 4096 DPC) remains unchanged. They can flexibly bedistributed over all internal networks.

The message format within the SS7 network remains unchanged. The SSNC internalformat contains the parameter 'Network Name' or 'Network ID' to identify therespective signaling network.

Operator benefits

Different operators can share one network node with SSNC Support of multiple point codes in one network node (e.g. for network

consolidation)

Incoming linkset-specific routing domains Enhanced interworking with other operators Internal separation of SS7 traffic belonging to different operators Separation of traffic for different applications (e.g. MTP user parts) Free assignment of the network indicator (NI) per internal MTP network Addressing of up to 4 million trunks between two nodes


10/87


MN2513EU11MN_0001

2002 Siemens AG

10

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NAT0

SSNCup to 32 internal SS7 networks

on top of the four ITU standardized neworks

ITU:4 standardized

networks

OP25

OP1

OP5OP32

OP18

NAT0/1, INAT0/1

NAT1

INAT0

INAT1

SSNC

Fig. 3 Multiple SS7 networks


11/87



11

1.4 Message flows

1.4.1 Signaling end point trafficSEP messages are either messages that are generated by a user- or application partof an exchange and sent to the SS7 network, or that are received from the SS7network and are evaluated by a user- or application part in the exchange.

TIPThe involvement of global title translation in the message flow is described in thechapter "Global Title Translation".

Signaling end point traffic, outgoing

An application part in either LTG or CP generates a signaling message that isforwarded to an idle MP:SLT automatically via a message channel. There level 3tasks are performed before the message is forwarded to another MP:SLT doing level2 and 1 tasks and that is connected to a trunk, transporting the message to it'sdestination (DPC in routing label of MSU). The latter connection has to be created byQ3 command. The routing database for outgoing links is hosted by the MP:SM, to

which all MP:SLTs have an internal connection.Since the SSNC internal message flow is based on ATM connections, a LIC convertsthe MSU format from ATM to STM (E1).


12/87


MN2513EU11MN_0001

2002 Siemens AG

12

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MP/SM

MP/SLT

LTG

LTG

MP/SLT

LIC

LIC

SC

ASN

SN

CP113C

SSNC

MB D

LTG

LTG

SS7-Links 64 kbit/s

HS-Links 2 Mbit/s

SS7-Links 64 kbit/s,trunks

MP/STAT

MP/OAM

MSU

Fig. 4 SEP, outgoing signaling messages


13/87



13

Signaling end point traffic, incoming

Any incoming signaling message will be converted from STM to ATM in a LIC before

it is forwarded to an MP:SLT by means of a 'nailed up connection', created by Q3command. There, message discrimination, allocation and distribution is beingperformed. In case the message is intended for one of the own user parts, it will beforwarded to the respective application part in an LTG or in the CP.


14/87


MN2513EU11MN_0001

2002 Siemens AG

14

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MP/SM

MP/SLT

MP/SLT

LIC

LIC

MP/OAM

SC

ASN

SSNC

SS7-Links 64 kbit/s

HS-Links 2 Mbit/s

SS7-Links 64 kbit/s,trunks

CP113CCP113C

LTG

LTG

SNSN

LTG

LTG

MP/STAT

MSU

MB D

Fig. 5 SEP, incoming signaling message


15/87



15

1.4.2 Signaling transfer point traffic

Signaling transfer points dont use level 4 functions for processing SS7 messages.They either just forward a message within the same signaling network or, in case of asignaling relay point, do global title translation with the received called party addressin order to forward the message to a signaling node in a different signaling network.

Signaling Transfer Point Traffic without GTT An MSU, coming from node A is forwarded to a LIC where the conversion from STMto ATM takes place. According to the created level 1 path, it will be processed by anMP:SLT.Message routing in that MP determines the link, leading to the next/final DPC for that

MSU and because a link is connected to a timeslot and the timeslot to anotherMP:SLT, this MSU will be sent to that MP.


16/87


MN2513EU11MN_0001

2002 Siemens AG

16

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MP/SM

MP/SLT

MP/SLT

LIC

LIC

MP/OAM

SC

ASN

SSNC

MB D

SS7-Links 64 kbit/s

HS-Links 2 Mbit/s

SS7-Links 64 kbit/s,

trunks

CP113CCP113C

LTG

LTG

SNSN

LTG

LTG

MP/STAT

MSU

MP/GTT

MSU

Fig. 6 STP without GTT


17/87



17

Signaling Transfer Point Traffic with GTTThe message flow for an STP with GTT is very similar to the one described before.

The difference is another MP:SLT, especially created for doing global titletranslations. After the message has been received by the first MP:SLT, the need for GTT isdetected (routing indicator = 0) and the MSU will be forwarded to the GTT-MP. Fromthere, it is given to that MP:SLT, that is connected to the link, leading to the DPC thatwas calculated during GTT.


18/87


MN2513EU11MN_0001

2002 Siemens AG

18

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MP/SM

MP/SLT

MP/SLT

LIC

LIC

MP/OAM

SC

ASN

SSNC

MB D

SS7-Links 64 kbit/s

HS-Links 2 Mbit/s


trunks

CP113CCP113C

LTG

LTG

SNSN

LTG

LTG

MP/STAT

MSU

MP/GTT

MSU

Fig. 7 STP with GTT


19/87



19


20/87


MN2513EU11MN_0001

2002 Siemens AG

20

2 Message transfer part


21/87



21

The creation of the database for the message transfer part comprises two steps:

Creation of the level 1 path through the SSNC Creation of level 3 objects

2.1 Level 1 path creationThe aim of the level 1 path through the SSNC is to create a nailed up connection,linking a timeslot of a PCM to an MP:SLT that performs level 2 and level 3 tasks forthat link.

This database is different, depending on whether the link is connected to the SSNC

via LTG or whether it is directly connected to a LIC port.The level 1 administration of high-speed links with 2Mb/s is again different but will notbe discussed in this course.


22/87


MN2513EU11MN_0001

2002 Siemens AG

22

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MP:SLTSN

LTG

LTG

ASN/ AMX

TS

2Mb/s

MP:SLT

MP:SLT

D900 SSNC

High SpeedLink 2Mb/s

Low Speed Link64kb/s

CRSIGDLLTG (EQN - MP)

CRSIGDLLIC (IWP - MP)

CRIWPSS7LIC-ID

PortTime slotIWP-ID

SIGN-TRUNKCR TRUNKCR TGRP

IW- TRUNKCR TRUNKCR TGRP

IWP

TS

CRLICPRTLic

PortTrafficType

STM

ATM or STM

LIC

STM

IWP

CRPDCLNKLTG,LICLIC.Port

TS


CRTCSUBLLIC-ID

LIC Port

CRVPATHTCS-ID

VPI

CRVCHAN

TCS-IDVPI/VCI

CRSIGDLHS (VC - MP) for ATM /CRSIGDLHSITU (IWP MP) for STM

ATM

CRHSIWPLIC-ID

PortIWP-ID

STM

Fig. 8 Creation of the level 1 path through the SSNC


23/87



23

2.1.1 Signaling links connected via D900

Like with the CCNC, links may be routed to the SSNC via a PCM line, connected to aDIU of an LTG ( 'outward LTG' ). Through the D900 switching network these links arerouted to a dedicated LTG ( 'inward LTG' , may be the same as the 'outward LTG' butdifferent LTU) that provides the connection to a LIC of the SSNC.

Both kinds of LTG are of load type 46.

Creation sequence:

CRLTGInward and outward LTGs have to be created and active.

CRLTULTU type D30 for inward and outward LTG is created.

ENTRPDCCHRThe PDC-characteristics of the INWARD LTGs have to be set to CRC4MF.

CRLICREDG A LIC redundancy group is necessary before a LIC pair is created.

CRLICCreation of the LICs connected to the inward LTGs

CRLICPRTE1Which ports of the LIC are used and to what kind of link will they get connected?

CRPDCLNKDefinition of the PCM line between the inward LTG and the LIC port.

CRTGRP / CR TRUNKCreating trunks on the EQNs of the outward LTGs on which the links, coming fromthe signaling network, are connected.

CRTGRP / CR TRUNKCreating the interworking trunks between the inward LTG and the LIC port.

CRIWPSS7Translating the STM connection parameters into ATM connection parameters.

CRSIGDLLTGNailed up connection between a timeslot of an outward LTG and an MP:SLT.

WARNINGAll interworking trunks need an interworking point! Creating more trunks than

interworking points or creating more interworking points than interworkingtrunks can cause problems! New signaling links might not get active!


24/87


MN2513EU11MN_0001

2002 Siemens AG

24

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MP:SLTSN

LTG

LTG

ASN/ AMX

MP:SLT

MP:SLT

EWSD SSNC

CRSIGDLLTG (EQN - MP)

CRIWPSS7LIC-ID

PortTime slotIWP-ID

SIGN-TRUNKCR TRUNKCR TGRP

IW- TRUNKCR TRUNKCR TGRP

TS

CRLICPRTLic

PortTrafficType

STM

LIC

IWP

CRPDCLNKLTG,LICLIC.Port

TSLow Speed Link

64kb/s

Fig. 9 L1 path for links, connected via LTG


25/87



25

2.1.1.1 SS7 trunks at outward LTG

Before setting up the Signaling Data Link (nailed up connection), the ports required

for the signaling links must be reserved by means of CRTGRP (GCOS=CCSLGRP)and CRTRUNK (LCOS=DIGSIG8) in the outward LTG.

2.1.1.2 Interworking trunks at inward LTG

The connection between D900 and SSNC is realized by one (min) or two (max)'interworking' trunk groups, at the inward LTGs.

1. 'Interworking' trunks (IWTR) are reserved via MML commands on the inwardLTG. Each IWTR is allocated to one of the two possible 'interworking' trunkgroups (IWTGRP).

2. All IWTRs of one inward LTG belong to the same IWTGRP.

3. Only 2 PCM lines per LTG are used for the LIC connection. The other two PCMlines may be used for speech connections.

4. When creating the links in a linkset, these links are automatically allocatedalternately to one of two existing IWTGRP. The operator only specifies the port ofa link on the outward LTG and the MP:SLT on which the link should terminate. (Ifthere are just link sets with one link only, these are always set up automatically inthe first IWTGRP).

This connection through the SN will be switched through as soon as the links areactivated.

TIPTrunks and trunk groups are still created in the D900 by MML commands.


26/87


MN2513EU11MN_0001

2002 Siemens AG

26

CR TGRP: TGNO=IWTG01,GCOS=IWTGRP,OPMODE=OG;

CR TRUNK: TGNO=IWTG01, LTG=0-1, LC=2-1,TRRANGE=31, LCOS=DIGSIG8;

CR PDCLNK

SNSN

LTG 0-1inward

LI

C

LTG 0-2inward

LTG 0-3inward

LTG 0-4inward

ASN/AMX

ASN/AMX

IWTG01

IWTG02

MP5(SLT)

MP5(SLT)

LTG 0-5outward

LTG 0-6outward

MP 2(SM)

MP 2(SM)

MP6(SLT)

MP6(SLT)

0123

1

2

3

4

5

6

7

8

0

123

0123

0123

CR IWPSS7

CR TGRP: TGNO=C7TG01,GCOS=CCSLGRP,OPMODE=IC;

CR TRUNK: TGNO=C7TG01, LTG=0-5, LC=1-31,LCOS=DIGSIG8;

0123

0123

Fig. 10 SS7- and interworking trunks (example)

Create SS7 trunk group at outward LTGCRTGRP: TGNO= ,OPMODE=IC, GCOS=CCSLGRP;

Create trunks in SS7 trunk group

CRTRUNK: TGNO=, LTG= ,LC=,LCOS=DIGSIG8, [TRRANGE= ,]BLK=NONE;

Fig. 11 Outward trunks

Create interworking trunk group at inward LTG

CRTGRP: TGNO= ,OPMODE=OG, GCOS=IWTGRP;

Create trunks in interworking trunk group

CRTRUNK: TGNO= ,LTG= ,LC=,LCOS=DIGSIG8, [TRRANGE= ,]BLK=NONE;

Fig. 12 Interworking trunks


27/87



27

2.1.1.3 Create PDC link

The PCM lines between the LIC ports and the ports of the inward LTG (DIU) must be

defined. All ports of the inward LTGs are divided into a maximum of two groups, which makeup the two interworking trunk groups 0 and 1.


28/87


MN2513EU11MN_0001

2002 Siemens AG

28

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create PDC link

CRPDCLNK: LIC = ,LICPORT = ,LTG = , PDCLNK = ;

Fig. 13 PDC link between inward LTG and LIC

DISPPDCLNK:LIC=1;

DISPLAY PDCLNK DATA

LIC LICPORT LTG PDCLNK-----+---------+-------+------

1 1 0-1 2 1 2 0-1 3 1 3 0-2 2 1 4 0-2 3 1 5 0-3 0

1 6 0-3 1 1 7 0-4 0 1 8 0-4 1

Fig. 14 Display PDC-link (example)


29/87



29

2.1.1.4 Creation of LIC ports

Each LIC has 8 connectable ports. Depending on the connection (high speed/low

speed links, direct connection or via D900), the ports must be created accordingly. Inthe SSNC both, E1- (2Mb/s, PCM30) and DS1-connections (1.5 Mb/s, PCM24) maybe used.

CR LICPRTDS1 (for PCM 24 LIC ports)

CR LICPRTE1 (for PCM 30 LIC ports)

If the traffic type is 'STM' (for 64kb/s links), the port is created with 31 time slots of 64kb/s each. In case of 'ATM' (for high speed links) only one object with 2 Mb/s iscreated on a LIC port.

The timing source for the transmitted line signal may be the SSNC internal system

clock ACCG ('System Time') or may be derived from the incoming line ('Loop').The 'E1 frame format' describes the kind of error detection method of the PCM line.'CRC' stands for 'cyclic redundancy check' (CRC4) and will be used as default value.

If a LIC port is not created with the 'Administrative State = Unlocked', it has to beunlocked afterwards, using the task MODLICPRTE1.

TIPSince the LICs are created as a pair of one active and one redundant LIC, one mustmake sure, that the LIC-ports are created at the active LIC only (DISP LICREDG;).

Nevertheless, the redundant LIC has to be entered too.


30/87


MN2513EU11MN_0001

2002 Siemens AG

30

Create LIC ports for 64kb/s links (PCM 30)

CRLICPRTE1: LIC = ,LIC port = ,Traffic type = ,Redundant LIC = ,[Timing source= ,][E1 frame format = CRC,][E-Bit = TRUE,][E-Bit polarity = TRUE,][National Bit = FALSE,][Admin. state= Locked/Unlocked,]

[Alarm profile MP= ];

Fig. 15 LIC port for PCM30 link

LIC | 1LIC port | 5Redundant LIC | 2

Admin. state | UnlockedOperational state | Enabled

Alarm status | ClearedCurrent problem list |

Alarm profile MP | "MAJNOESC"Traffic type | STM Timing source | System timeE-bit | TRUEE-bit polarity | TRUE

National bit | FALSEE1 frame format | CRC

DISP LICPRTE1:LIC=1, LIC port=5;

Fig. 16 DISP LICPRTE1 (example)


31/87



31

2.1.1.5 Interworking points

For every 64kb/s link, virtual connection data must be created to translate the STM

connection parameters into ATM connection parameters that are used SSNCinternally. Virtual connections for narrow band links (64kb/s) have to be created asinterworking points (IWP).

The operator specifies only the physical location of each time slot (LIC, LIC-port, timeslot) for which a virtual connection should be created and the system generates allnecessary data for the ATM connection itself. Most of the ATM description data areinternally predefined and don't need to be specified by the operator.

The virtual connection is identified by an interworking point number (IWP ID), whichcan be entered by the operator or is assigned automatically by the system. It makessense to assign an IWP ID from which the relation between LIC-port and timeslot can

be derived:

Example:

IWP ID: "a b c" 1304

LIC: a 1

LIC Port: b 3

Time Slot: c 04

The task CRIWP has to be entered once for each single timeslot on the connectionbetween inward LTG and LIC. A parameter similar to "TRRANGE" in CRTRUNKdoes not exist.

TIPThe IWP-ID is used in the Signaling Data Link task (CRSIGDLLTG) for directlyconnected low speed links to set up a permanent virtual connection (PVC) from atime slot of a PCM to an MP:SLT.


32/87


MN2513EU11MN_0001

2002 Siemens AG

32

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create interworking point for SS7

CRIWPSS7: LIC = ,LIC Port =,Time Slot =,[IWP ID = ,][Admin State = ,][Alarm Profile MP = ];

Fig. 17 Virtual connections for 64kb/s links

DISP IWPSS7: IWP ID=1103;

IWP ID | 1103LIC | 1LIC port | 1Time slot | 03

Admin. state | UnlockedOperational state | Enabled

Alarm status | ClearedCurrent problem list |

Alarm profile MP | "CRITICAL "

Fig. 18 Display interworking point SS7 (example)


33/87



33

2.1.1.6 Create a signaling data link

Signaling Data Links form the connection between the SS7 links from the network

and the MP:SLT. This involves nailed up connections, which are connected on theD900 side as STM-NUC and on the SSNC side as ATM-NUC (PVC).

Specifying both end points, i.e. network (time slot of the outward LTG) and MP setsup data links between them automatically. Depending on the kind of signalingconnection (Low Speed/High Speed, direct or via EWSD to the LIC port), differenttasks with different parameters have to be used.

In the CRSIGDLLTG task, the end points are defined by the time slot location of theoutward LTG and the MP:SLT.

The time slots between D900 (LTG- inward port) and SSNC (LIC) are selected by thesystem automatically.

It is sufficient if the signaling network and the data link are identified by their givennames. The identification number (ID) is then found/allocated automatically.

The parameter 'Bit inversion' indicates whether the level 1 bit stream is inverted for asignaling data link or not.

The bandwidth of the internal through connection will always be 64kb/s in case of lowspeed links.


34/87


MN2513EU11MN_0001

2002 Siemens AG

34

Create signaling data link for 64kb/s links via LTG

CRSIGDLLTG: Data link name = ,[Data link ID = ,]Net name = ,[Net ID = ,]

Adjacent DPC = ,MP = ,Outward EQN = ,[Transmission rate = 64 kBit,][Bit inversion = No Inversion];

Fig. 19 Signaling data link for low speed links via LTG

DISPSIGDLLTG:Net ID=1;

Net nam e | D ata link | Data | MP | L IC Port | Inward EQN | Outward EQ N | Operational| name | link ID | | | | | state

=====================================================================================================================TELECOM1" |DL1T-Munich"| 1 | 5 | LIC = 1 | LTG SET | 0 | LTG SET | 0 | Enabled

| | | | LIC port = 1 | LTG ID | 1 | LTG ID | 5 || | | | | DIU ID | 2 | DIU ID | 1 || | | | | STM channel | 7 | STM channel | 16 |

----------------------------------------------------------------------------------------------------------------------TELECOM1" |DL2T-Munich "| 2 | 6 | LIC = 1 | LTG SET | 0 | LTG SET | 0 | Enabled

| | | | LIC port = 2 | LTG ID | 3 | LTG ID | 5 || | | | | DIU ID | 0 | DIU ID | 3 || | | | | STM channel | 23 | STM channel | 17 |

DISPSIGDLLTG:Net ID=1,Data link ID=1;Net name | TELECOM1"Net ID | 1Data link name | DL1T-Munich"Data link ID | 1Adjacent DPC | 2-2-2-2MP | 5LIC Port | LIC = 1

| LI C po rt = 1Inward EQN | LTG SET | 0

| LTG ID | 1| DIU ID | 2| STM channel | 7

SN Info | .Outward EQN | LTG SET | 0| LTG ID | 5| DIU ID | 1| ST M ch an ne l | 16

Interworking point ref. | -Operational state | EnabledTransmission rate | 64 kBitBit inversion | No inversionUsed | TRUE

Fig. 20 Display of a signaling data link LTG (example)


35/87



35

2.1.2 Signaling links directly connected to a LIC

In opposite to the CCNC, a PCM line with signaling links may also be connected tothe SSNC directly without an LTG. In that case, each timeslot of the PCM representsone 64kb/s signaling link.

Since no trunk groups and no trunks are needed here, the necessary database issimpler than in the case described before.

Creation sequence:

CRLICREDG A LIC redundancy group is necessary before a LIC pair is created.

CRLICCreation of the LICs connected to the inward LTGs

CR LICPRTE1Which ports of the LIC are used and to what kind of link will they get connected?

CR IWPSS7Translating the STM connection parameters into ATM connection parameters.

CRSIGDLLICNailed up connection between a timeslot of the SS7-PCM and an MP:SLT.


36/87


MN2513EU11MN_0001

2002 Siemens AG

36

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MP:SLT

ASN/

AMX

TS

MP:SLT

MP:SLT

SSNC


CRSIGDLLIC (IWP - MP)

CRIWPSS7LIC-ID

PortTime slotIWP-ID

CRLICPRTLIC-ID

PortTrafficType

LIC

STM

Fig. 21 L1 path for links, directly connected to SSNC


37/87



37

2.1.2.1 Creation of LIC ports

Each LIC has 8 connectable ports. Depending on the connection (high speed/low

speed links, direct connection or via D900), the ports must be created accordingly. Inthe SSNC both, E1- (2Mb/s, PCM30) and DS1-connections (1.5 Mb/s, PCM24) maybe used.

TIPThe LIC ports have to be created in the same manner as for low speed links,connected via LTG, described before:

2.1.2.2 Interworking pointsFor every 64kb/s link, virtual connection data must be created to translate the STMconnection parameters into ATM connection parameters that are used SSNCinternally. Virtual connections for narrow band links (64kb/s) have to be created asinterworking points (IWP).

TIPThe interworking points have to be created in the same manner as for low speedlinks connected via LTG and described before.

2.1.2.3 Create a signaling data link

Signaling Data Links form the connection between the SS7 links from the networkand the MP:SLT. This involves nailed up connections, which are connected on theD900 side as STM-NUC and on the SSNC side as ATM-NUC (PVC).

In the CRSIGDLLIC task, the endpoints are defined by the interworking point (i.e. theLIC-port, defined in CRIWPSS7) and the MP:SLT.

It is sufficient if the signaling network and the data link are identified by their given

names. The identification number (ID) is then found/allocated automatically.The parameter 'Bit inversion' indicates whether the level 1 bit stream is inverted for asignaling data link or not.

The bandwidth of the internal through connection will always be 64kBit in case of lowspeed links.


38/87


MN2513EU11MN_0001

2002 Siemens AG

38

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create signaling data link for 64kb/s links

CRSIGDLLIC: Data link name = ,[Data link ID = ,][Net name = ,][Net ID = ,]

Adjacent DPC = ,MP = ,Interworking point ref. = ,[Transmission rate = 64 kBit,][Bit inversion = No inversion];

Fig. 22 Signaling data link for low speed links, directly connected to a LIC port


39/87



39

2.1.3 High-speed (ATM) signaling links

High-speed links are ATM connections between an SSNC and another ATM node onwhich signaling messages are transmitted as payload. The bandwidth of the high-speed connection is fixed to the bandwidth of the physical carrier (2Mbit/sec forPCM30).

2.1.3.1 ATM terminology

Transmitting information in ATM is done by a continuous stream of "ATM cells" offixed length (48 byte payload and 5 byte header). User information, as e.g. signalingmessages, is divided into portions of 48 byte, packed into the cells and sent through

the ATM network light freight in a container on a truck. ATM divides each physical transmission into logical connections ( virtualconnections ) that are assigned to the services that require transportation. Such avirtual connection consists of a virtual path (similar to a TGRP), an administrativegroup of one or more virtual channels (similar to a trunk in a TGRP). Theinformation, to which virtual connection a specific cell belongs, is contained in theheader of each cell as virtual path identifier (VPI) and virtual channel identifier (VCI).

The different tasks like packing the user information into the payload of an ATM celland inserting these cells into the continuous cell-stream, are described by a four-layer ATM model:

The higher layers (layer 4) represent the users that provide information to betransmitted.

The ATM Adaptation Layer AAL (layer 3) is responsible for segmentation, i.e.cutting the user information into portions that fit into the ATM cells and stuff themwith security information because ATM does not care for the error freetransmission of the payload inside the cells.

The ATM Layer (layer 2) forms the ATM cells by adding header information likeVPI and VCI to each payload.

The Physical Layer (layer 1) is subdivided into a Transmission ConvergenceSublayer that fits the ATM cells into the physical transmission medium (PCM) anda Physical Medium Sublayer that is responsible for the electrical adaptations to thetransmission medium.

TIPVPI, VCI and the transmission convergence sublayer have to be created in the SSNCdatabase for each LIC port at which a high-speed link terminates.


40/87


MN2513EU11MN_0001

2002 Siemens AG

40

SIEMENS

SIEMENS SIEMENS

SIEMENS

SIEMENS SIEMENS

D900

SSNC

D900

SSNC

ATM High Speed Link

VirtualConnection

VirtualPath

VirtualChannels

Fig. 23 ATM virtual connection

Higher Layer

ATMAdaptation Layer

ATM Layer

Physical Layer

PAYLOAD

PAYLOAD

PAYLOAD PAYLOADTransmission Convergence

Sublayer

Physical Medium Sublayer

Fig. 24 ATM layers


41/87


42/87


MN2513EU11MN_0001

2002 Siemens AG

42

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create Transmission Control Sublayer

CRTCSUBL: LIC = ,LIC port = , Alarm profile MP = ,Cell scrambling enable = ;

Create Virtual Path

CRVPATH: TCS id = ,VPI = ,

Alarm profile MP = , Admin s tate = ;

Create Virtual Channel

CRVCHAN: TCS id = ,VPI = ,VCI = ,

Admin s tate = ;

Create Signaling Data Link for ATM High Speed Links

CRSIGDLHS: Net name = [Net ID = ,]Data link name = ;[Data link ID = ,]

Adjacent DPC = DPC of partner exchange>,

MP = ,Virtual channel = ;

Fig. 25 Q3 tasks


43/87



43

2.1.4 SS7 high speed link (STM)

In cases where links with high data rates are required, but the ATM standard is notdesired, the SS7 High Speed Links (HSL) offer a possibility to connect a 1,5 or 2Mb/ssignaling connection, based on STM technology, directly to a LIC-port.

For this purpose all timeslots of a PCM carrier (PCM 24/30), and thus of a LIC port,are bundled, thus representing the mentioned, high data rates for one single link.

The new data rates are transparent to the higher layers of CCS7; adaptation is doneon layer 2 level only.

TIP

This is NOT the ATM link that may be connected to an ATM port of a LIC, offeringsimilar data rates!

WARNINGAlthough the software to realize SS7 HSL with 1,5 Mb/s over a PCM 24 line isavailable and administration is possible, this software is neither tested norreleased for the world market. If requested, this software has to be tested andreleased for the concerned project.


44/87


MN2513EU11MN_0001

2002 Siemens AG

44

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MP/SM

LTG

LTG

MP/SLT

LIC

LIC

SC

ASN

SN

CP113

SSNC

MB D

LTG

LTG

SS7-Links 64 kbit/s


MP/STAT

MP/OAM

LIC

SS7-Links ATM

SS7 High Speed Links1,5 / 2Mb/s STM

Fig. 26 Connection possibilities for SS7 links to SSNC


45/87



45

2.1.4.1 Differences to narrow-band links

The only differences between a 64kb/s link and the new 1,5/2Mb/s HSL are, apart

from the transmission rate, the length of some fields in the MSU header and theapplied error rate monitoring method.

Signal unit format

When link data rates of 1.5 Mb/s and 2.0 Mb/s are used, the format of the sequencenumbers changes from 7 bits to 12 bits. In this case, the forward sequence numberFSN and backward sequence number BSN are in binary code from a cyclicsequence from 0 to 4095.

If the extended sequence number format as described above is used, the lengthindicator format changes from 6 to 9 bit.


46/87


MN2513EU11MN_0001

2002 Siemens AG

46

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FBSNBIB

FSNFIB

SIOSIFCKF L

I

812

112

19

28273>n>2 bytes168 776

FBSNBIB

FSNFIB

SFCKF LI

812

112

19

28 or 16168 776

FBSNBIB

FSNFIB

CKF LI

812

112

19

2168 776

MSU-formatfor SS7 HSL:

LSSU-formatfor SS7 HSL:

FISU-formatfor SS7 HSL:

Fig. 27 Adapted SU formats for SS7 HSL


47/87



47

2.1.4.2 Administration of SS7 HSL

The administration of SS7 HSL is very similar to the administration of narrowband

links. But: HSL must not be connected via LTG.Two new Q3 tasks are available for HSL and the layer-2 profile of these links must beselected according to their transmission rate and network type.

CR HSIWPSS7

'Create high speed interworking point' is very much like creating a narrow band IWP.Difference to CR IWP, which is used for LIC NB links: no parameter "Time Slot"because not a single timeslot is carrying the signaling information but the whole PCMline. Thus all ts of a LIC port are grouped together to form one interworking point.

CR SIGDLLICDifference to CR SIGDLLIC, which is used for narrow band links: parameter "Transmission rate supports 2Mb/s (and 1,5Mb/s but not released).

CR SIGLINK - DISP MTPL2PF

The layer-2 profile for high-speed links acc. ITU Q703 is predefined in the SSNC anddoes not need to be defined manually. Nevertheless, it has to be entered in the link-definition (parameter: 'Profile name').

Depending on the network type, ITU or ANSI, and the applied error correction

method, four different profiles are available: ITU BAS2.0_H: ITU network, basic error correction, 2Mbit/s, high-speed link ITU PCR2.0_H: ITU network, preventive cyclic retransmission, 2Mbit/s, high-speed

link

ANS BAS2.0_H: ANSI network, basic error correction, 2Mbit/s, high-speed link ANS PCR2.0_H: ANSI network, preventive cyclic retransmission, 2Mbit/s, high-

speed link

Create interworking point for SS7 high speed links

CRHSIWPSS7: LIC = ,LIC Port =,[IWP ID = ,][Admin State = ,][Alarm Profile MP = ];

Fig. 28 Q3 task to create interworking point for HSL


48/87


MN2513EU11MN_0001

2002 Siemens AG

48

Create signaling data link for high speed links

CRSIGDLLIC: Data link name = ,[Data link ID = ,]Net name = ,[Net ID = ,]

Adjacent DPC = ,MP = ,Interworking point ref. = ,[Transmission rate = ,][Bit inversion = No Inverse];

Create signaling link for high speed links

CRSIGLINK: Data link ID = ,Net ID = ,Link set name =Link code = ,Protocol profile name = ;

Fig. 29 Q3 task to create a signaling data link for HSL

DISPMTPL2PF;

L2 profile name | L2 profile ID

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

::

---------------------------------------------

"ITU BAS2.0_H" | 65

---------------------------------------------

"ITU PCR2.0_H" | 66

---------------------------------------------

"ANS BAS1.5_H" | 67

---------------------------------------------

"ANS PCR1.5_H" | 68

---------------------------------------------

"ANS BAS2.0_H" | 69

---------------------------------------------

"ANS PCR2.0_H" | 70

---------------------------------------------

"ITU BAS1.5_H" | 71

---------------------------------------------

"ITU PCR1.5_H" | 72

Cant be used becausefeature is not releasedfor 1.5 Mbit/s

Fig. 30 MTP layer 2 profiles


49/87



49

2.1.4.3 Required hardware

The MPs to which the SS7 HSL are connected via a signaling data link must have a

MPUE+ as processing units. MPUD will not work.The MPUE+ has a modified ASIC 'ATM230 V2.4' on board to offer the requiredfunctionality:

processing of SS7 HSL implementation of a SS7 'Error Interval Monitor' for HSL

adaptation to the new signaling unit format with extended header fields (seeabove).

up to four SS7 HSL may be connected to one MP via signaling data links all other features of the MPUE will remain the same a mixture of HSL and narrow band links at one MP is not possible.


50/87


MN2513EU11MN_0001

2002 Siemens AG

50

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


51/87



51

2.2 Level 3 objects

A signaling network consisting of signaling points signaling links signaling link sets signaling routes and must be created by the operator via Q3 tasks in the SSNC.

With the aid of the appropriate database, the MTP is then able to carry out its tasks.


52/87


MN2513EU11MN_0001

2002 Siemens AG

52

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Destination Point

Originating Point

Signaling Point(STP or SRP)

1 . . . 1 6

3 1

. . .

1 .

.. 1 6

3 1 .

..

C i r c u i t r e l a t e d o r n o n c i r c u i t

r e l a t e d s i g n a l i n g i n f o r m a t i o n

Signalinglinks

Signaling links

Signaling link set

1 .

.. 1 6

3 1 .

..

Signal inglink set

SI EME NS D 9 00 S IE ME NS D 9 00

SIEMEN S D 900 SIEMENS D 900

SIE ME NS D 9 00 S IE ME NS D 9 00

S IE ME NS D 9 00 S IE ME NS D 9 00

Signaling Point(STP or SRP)

Signalingroute

CRSIGROUTE

CRSIGLINK

CRSIGLSET

CRSIGDPCRSIGDP

CRSIGPOINT

Fig. 31 Signaling network


53/87



53

2.2.1 Own signaling point code

Every signaling point must have an own signaling address, consisting of SPC andnetwork indicator that is unique in the signaling networks this node belongs to.Depending on the project specific structure, this SPC has to be entered as a decimalvalue or structured (see chapter "Introduction to CCS7"). Furthermore, it must bedefined how the SP shall handle signaling- and status messages (TFA, TFP).

Due to the feature 'Multiple SS7 Networks', up to 32 different signaling networks canbe handled by a single SSNC. Thus, an own signaling address must be assigned foreach of the handled networks. It is sufficient to specify their 'Net Name', the 'NetID'will be assigned automatically.

If a different MSU length than 272 octets is required, the parameter 'Supported data

length' has to be set accordingly.The 'Signaling point type' determines the usage of the own SP:

STP Signaling point functions purely as a signaling transfer point, i.e. level 4 ofCCS7 will not be used to evaluate the message, not even SCCP for GTT.

SEP Signaling point functions purely as signaling end point, i.e. it candistribute a received message to its own users only. Should the routinglabel of an MSU indicate that a transfer to another signaling point isrequired, the message is discarded and the discarded-message counteris incremented.

STEP Signaling point functions as signaling transfer point and signaling endpoint.

In case the own node is a standalone signaling relay point with GTT, it has to be setup as STEP.

The parameter 'TFP TFA broadcast' determines, whether a received TFA-/TFPmessage shall be broadcasted to no, all, or just a limited number of neighboringsignaling points.

'TFR compatibility' determines where message rerouting will be done in case a TFR-msg from an STP is received.

TIPCRSIGPOINT is the task in which all the handled signaling networks for 'Multiple SS7Networks' are defined by creating an own signaling address on these networks.


54/87


MN2513EU11MN_0001

2002 Siemens AG

54

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create own signaling point

CRSIGPOINT: Net Name = ,[Net ID = ,]Net Indicator = ,SPC = ,Signal. point type = ,TFP TFA broadcast= ,TFR compatibility= ,[Supported data length= length272,][Alarm profile MP = ,].... ;

Fig. 32 Own signaling point


55/87



55

The opposite page shows typical signaling point data. Apart from the parametersmentioned, many others are shown, mainly timer values and parameters, indicatinghow to handle transfer allowed- and transfer prohibited messages.


56/87


MN2513EU11MN_0001

2002 Siemens AG

56

DISP SIGPOINT

Net name | "TELECOM1"

Net ID | 1Net indicator | National network 0SPC | 1-1-1-1SPC structure | No. of bit | Component | Component

| s | minimum | maximum| ======================================| 4 | 0 | 15| --------------------------------------| 3 | 0 | 7| --------------------------------------| 4 | 0 | 15| --------------------------------------| 3 | 0 | 7

Operational state | EnabledAlarm status | ClearedAlarm Profile MP | "CRITICAL"RST after conf DP | FALSETFP for unknown DP | TRUEMTP restart | OffTFR compatibility | TRUENi screening | ActivatedTFP TFA broadcast | YesSignaling point type | STEPTFC sampling rate | 8Number of TFA | 100Number of TFP | 100TFA interval | 600TFP interval | 600Supported data length | Length 272

TUP | -Send UCIC indicator | FALSELPO control bit | TRUEITU-TimersQ704 timer T1 | 1000Q704 timer T2 | 2000Q704 timer T3 | 1000Q704 timer T4 | 1000Q704 timer T5 | 1000Q704 timer T6 | 1000Q704 timer T7 | 1000Q704 timer T8 | 1100Q704 timer T10 | 40000Q704 timer T11 | 60000Q704 timer T12 | 1500Q704 timer T13 | 1500Q704 timer T14 | 3000Q704 timer T15 | 2000Q704 timer T16 | 1400Q704 timer T17 | 1500Q704 timer T18 | 30000Q704 timer T19 | 68000Q704 timer T20 | 60000Q704 timer T21 | 64000Q704 timer T22 | 190000Q704 timer T23 | 190000Q704 timer T24 | 500Q707 timer T1 | 12000Q707 timer T2 | 90000


57/87



57

2.2.2 Signaling destination point

In every signaling point of a network, all other signaling points of the same signalingnetwork, to which messages can be sent and received respectively, must be createdas destination points. Destination points are uniquely identified by a signaling network'Net Name/ID' and an SPC, which has to be unambiguous in that signaling network.Depending on the project specific structure, this DPC has to be entered as a decimalvalue or structured (see chapter "Introduction to CCS7").

The destination points can be reached from the own signaling point either via a directsignaling link set (i.e. destination point is adjacent) or via one or more intermediatesignaling points, so called signaling transfer points.

A loadsharing key defines, how the signaling messages towards that destination

point are offered to the possible linksets. All linksets, leading to one other signaling point of the own network are known assignaling routes. Loadsharing can be set for the first two active linksets of a signalingroute at most. Loadsharing is only effective if at least two linksets are created for thesame destination, which are entered in the routing table with the same priority using'CR SIGROUTE' (see below).

Loadsharing is carried out by evaluation of one of the SLS-bits (Signaling LinkSelection), found in the routing label of each MSU. The operator determines the bitby entering a 'Loadsharing key' between 0 and 4:

Loadsharingkey =

Loadsharing algorithm

none 0 No loadsharing. All MSUs are offered to the linkset with the highestpriority

SLS1...SLS4 Loadsharing between the first two linksets having the same highestpriority

LSK = SLS1...SLS4 defines a bit position within the SLS field of an MSU. A binary '0'

at this position routes the MSU to the first linkset, a binary '1' routes it to the secondlinkset.


58/87


MN2513EU11MN_0001

2002 Siemens AG

58

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create signaling destination point

CRSIGDP: DPC = ,DPC Name = ,Net Name = ,[Net ID = ,][Loadsharing key = ,][Alarm profile MP = ,][Alarm smoothing time = ];

Fig. 33 Signaling destination point

LSK = Bitposition inSLS field

Selected linkset fromsignaling route

none 0 XXXX first LS with highest priority

SLS1 XXX0XXX1

first LS with highest prioritysecond LS with highest priority

SLS2 XX0XXX1X


SLS3 X0XXX1XX


SLS4 0XXX1XXX


Fig. 34 Loadsharing between linksets towards a destination point


59/87



59

By means of the task MOD SIGDP, the administrative state of a destination pointhas to be set to 'UNLOCKED' before it can be reached. As a prerequisite at least onesignaling linkset must be contained in the signaling route, leading to that destination

point.The administrative state attribute describes whether it is administratively permitted toroute SS7 MSUs towards the respective destination point. The possible valuessupported in the NE are LOCKED' and UNLOCKED.

The operational state attribute describes whether the respective destinationsignaling point is accessible (ENABLED) or not (DISABLED). If the operational statesof all signaling linksets leading to the signaling destination point are DISABLED,then the operational state of the signaling destination point is DISABLED, in anyother case it remains ENABLED. If the administrative state is 'LOCKED', theoperational state is 'DISABLED'.


60/87


MN2513EU11MN_0001

2002 Siemens AG

60

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Modify signaling destination point

MODSIGDP: [DPC = ,][DPC name = ,][Net Name = ,][Net ID = ,][Admin. state = ,][Loadsharing key = ,][Alarm smoothing time = ];

Fig. 35 Administrative state change

Net name |Net|DPC name | DPC | Admin. | Opera | Load | Alarm | Alarm |Alarm | Extended|Con |Con |US| | | | | state | key | | MP |thing | problem |gested |gested|routing| | | | | | | t im e | l is t | | | st at e | le ve l |

=============================================================================================================================="TELECOM1" |1 |Munich" |2-2-2-2| Unlocked| Enabled | "sls 0" |Cleared |"MAJNOESC"| 0 | { } |Not | - |

| | | | | | | | | | |Congested| |------------------------------------------------------------------------------------------------------------------

Documents

04 Mn2513eu11mn 0001 Administration Signaling