Administration of the Signaling Network

Siemens

Administration of the Signaling Network

Contents
1
1.1
1.2
1.3
1.4
2
2.1
2.2
3
3.1
3.2

Control of the signaling network
SSNC as signaling network controller
Functions within the SSNC
Multiple SS7 networks
Message flows
Message transfer part
Level 1 path creation
Level 3 objects
User parts
Overview
Administration of the SCCP and its user parts

MN2513EU11MN_0001
© 2002 Siemens AG

3
4
6
9
11
20
21
51
70
71
73

1

Siemens

2

Administration of the Signaling Network

MN2513EU11MN_0001
© 2002 Siemens AG

Administration of the Signaling Network

1

Siemens

Control of the signaling network

MN2513EU11MN_0001
© 2002 Siemens AG

3

Siemens

1.1

Administration of the Signaling Network

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 the
signaling connection control part (SCCP). The open architecture of the SSNC is
based on Solution O.N.E (optimized network evolution) technology, i.e. message
transfer within the SSNC is based on ATM.
Connection to the CP113 is done via a CP processor, the AMP. The signaling
channels 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 interfaces
over the MBD.
The SSNC has its own OAM platform "Switch Commander". For operation, it is
provided with V24/LAN interfaces for the connection of NM systems.
Thanks to its own OAM platform, the SSNC can also be used as a standalone
network element (i.e. without D900 environment).
TIP
This document only describes the functionality of the SSNC as signaling network
controller. It does not describe special signaling interfaces like the signaling on the Iu
interface for UMTS or on the Gb interface for GPRS. These interfaces are discussed
in the corresponding UMTS and GPRS courses.

4

MN2513EU11MN_0001
© 2002 Siemens AG

Administration of the Signaling Network Siemens D900 Configuration with SSNC SSNC: Trunks and SS7 Links LTG PCM30/24 LTG: LTG SN B SS7 Links SN: MB: IOP: SC SSNC AMP: 207Mb/s MB D SC: 207Mb/s AMPC CP: CP Signaling System Network Control Line Trunk Group Switching Network Message Buffer Typ D Input/Output Processor ATM Bridge Processor Coordination Processor Switch Commander IOP:MB Fig. 1 D900 with SSNC MN2513EU11MN_0001 © 2002 Siemens AG 5 .

Message Transfer Part The message transfer part (MTP) is used in CCS7 by all user parts as a transport system for message exchange.2 Functions within the SSNC The SSNC implements the functions of the message transfer part MTP and parts of the SCCP (SCCP global title translation and SCCP management). but not more than 1500 links in total! The MP:SM functional unit supports MTP-Level 3 network management and hosts the routing database for the signaling network. the SSNC can be provided with up to 47 MP:SLT. allocation). each MP:SLT has an internal connection to the MP:SM. The MP:SLT performs MTP-level 1 (message transfer). A distinction is made between the two following functional areas: • message routing and message distribution • signaling network management In the SSNC these functional levels are mapped on the functional units MP:SLT (signaling link terminal) and MP:SM (signaling manager). Level 1 represents the bearer for a signaling link. after disruption of the signaling data link. without information loss. Messages to be transferred from one user part to another are given to the message transfer part which ensures that the messages reach the addressed user part in the correct order. 6 MN2513EU11MN_0001 © 2002 Siemens AG . e. electrical and functional characteristics of a signaling data link and the access units. In a digital network. Level 3 defines the interworking of the individual signaling links. Thus. MTP-level 2 (error correction) and MTP-level 3 (message handling incl. Level 2 defines the functions and procedures for a correct exchange of user messages 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. These SLT functions are logically combined and are performed by one or more MPs. using a protocol stack. Per SLT up to 60 signaling channels (64kbit/s) may be connected. Depending on system usage of the network node.7 is divided into two main parts so that it can be adapted optimally to the diverse requirements of its various users: • the message transfer part MTP and the • user parts UP. This is shown in the following diagram.g. 64-kbit/s channels are generally used as signaling data links.Administration of the Signaling Network Siemens 1. Signaling System No. duplication or sequence alteration and without any bit errors. Functional levels of the MTP Level 1 defines the physical.

Administration of the Signaling Network MN2513EU11MN_0001 © 2002 Siemens AG Siemens 7 .

Administration of the Signaling Network Siemens User Parts The function. MAPs etc. 2 MTP and user parts 8 MN2513EU11MN_0001 © 2002 Siemens AG . structure. TCAP TCAP ISUP SCCP GTT GTT BSSAP ISUP SCCP MTP L3 MTP L3 MTP L2 MTP L2 MTP L1 Fig. The ISDN. The SCCP is located in the SSNC and is the only user part in case the SSNC is operated as Signaling Relay Point (SRP). The user parts therefore control the setup and release of circuit connections.and telephone user parts (ISUP/TUP) are located in the LTGs. 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 handling of service features as well as administration and maintenance functions for the signaling channels (SCCP management). ITU-T SS7 Protocol Stack USER Part L4 BSSAP USER Part L4 MAPs etc.

The message format within the SS7 network remains unchanged. The maximum capacity of the signaling network elements (1500 signaling links. which are allocated to the ITU standard networks (NAT0/1. They can flexibly be distributed over all internal networks.g. SCCP and the SS7 user parts.g. This feature affects MTP. in this way up to 32 own signaling addresses can be set up in one node. 7 (SS7) routing domains (internal networks) can be administered in one signaling network node with SSNC. With this feature. 4096 DPC) remains unchanged. Operator benefits • Different operators can share one network node with SSNC • Support of multiple point codes in one network node (e. This means that a node can be connected to up to 32 separate signaling networks. The SSNC internal format contains the parameter 'Network Name' or 'Network ID' to identify the respective signaling network. INAT0/1). 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. i. up to 32 Signaling System No. The 'Multiple SS7 Networks' feature is fully compatible with ITU-T SS7 standards.Administration of the Signaling Network 1. MTP user parts) • Free assignment of the network indicator (NI) per internal MTP network • Addressing of up to 4 million trunks between two nodes MN2513EU11MN_0001 © 2002 Siemens AG 9 . Signaling point allocation is completely flexible. 1024 signaling trunk groups.e.3 Siemens Multiple SS7 networks The feature 'Multiple SS7 Networks' expands the range of network planning options in deregulated markets with many operating companies. it is transparent to all SS7 protocols. Each SS7 network can be individually administered.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Multiple SS7 networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens SSNC up to 32 internal SS7 networks on top of the four ITU standardized neworks ITU: 4 standardized networks NAT0/1. . . . . . . . . . . INAT0/1 INAT1 OP1 INAT0 OP32 OP5 NAT1 SSNC NAT0 OP18 OP25 Fig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

or application part of an exchange and sent to the SS7 network. a LIC converts the MSU format from ATM to STM (E1). There level 3 tasks are performed before the message is forwarded to another MP:SLT doing level 2 and 1 tasks and that is connected to a trunk. The latter connection has to be created by Q3 command. Signaling end point traffic.1 Siemens Message flows Signaling end point traffic SEP messages are either messages that are generated by a user. The routing database for outgoing links is hosted by the MP:SM. MN2513EU11MN_0001 © 2002 Siemens AG 11 .4 1. transporting the message to it's destination (DPC in routing label of MSU). or that are received from the SS7 network and are evaluated by a user.or application part in the exchange. to which all MP:SLTs have an internal connection.Administration of the Signaling Network 1. TIP The involvement of global title translation in the message flow is described in the chapter "Global Title Translation". outgoing An application part in either LTG or CP generates a signaling message that is forwarded to an idle MP:SLT automatically via a message channel. Since the SSNC internal message flow is based on ATM connections.4.

. . . . . . . . . . . . . . 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens MSU LTG SS7-Links 64 kbit/s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . outgoing signaling messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 SEP. trunks LTG SSNC LTG LIC SS7-Links 64 kbit/s ASN LTG LIC HS-Links 2 Mbit/s SN MP/SLT MB D SC MP/SLT MP/STAT MP/SM MP/OAM CP113C Fig. . . . . . . . . . . . . . . . . . . . . . . . . .

In case the message is intended for one of the own user parts. it will be forwarded to the respective application part in an LTG or in the CP. allocation and distribution is being performed. There.Administration of the Signaling Network Siemens Signaling end point traffic. created by Q3 command. message discrimination. MN2513EU11MN_0001 © 2002 Siemens AG 13 . 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'.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 SEP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . trunks LTG SSNC LTG LIC SS7-Links 64 kbit/s ASN LTG LIC HS-Links 2 Mbit/s SN SN MP/SLT MB D MP/SLT SC MP/STAT MP/SM MP/OAM CP113C CP113C Fig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . incoming signaling message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens MSU LTG SS7-Links 64 kbit/s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

in case of a ‚signaling relay point‘. MN2513EU11MN_0001 © 2002 Siemens AG 15 .Administration of the Signaling Network 1. According to the created level 1 path. coming from node A is forwarded to a LIC where the conversion from STM to ATM takes place. do global title translation with the received called party address in order to forward the message to a signaling node in a different signaling network.4. They either just forward a message within the same signaling network or. it will be processed by an MP:SLT. leading to the next/final DPC for that MSU and because a link is connected to a timeslot and the timeslot to another MP:SLT. Signaling Transfer Point Traffic without GTT An MSU. Message routing in that MP determines the link. this MSU will be sent to that MP.2 Siemens Signaling transfer point traffic Signaling transfer points don’t use level 4 functions for processing SS7 messages.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 STP without GTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens MSU SS7-Links 64 kbit/s. . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . trunks LTG MSU LTG SSNC LTG LIC SS7-Links 64 kbit/s ASN LTG HS-Links 2 Mbit/s LIC SN SN MP/SLT MP/GTT MB D MP/SLT SC MP/STAT MP/SM MP/OAM CP113C CP113C Fig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

that is connected to the link. MN2513EU11MN_0001 © 2002 Siemens AG 17 .Administration of the Signaling Network Siemens Signaling Transfer Point Traffic with GTT The message flow for an STP with GTT is very similar to the one described before. the need for GTT is detected (routing indicator = 0) and the MSU will be forwarded to the ‚GTT-MP‘. After the message has been received by the first MP:SLT. The difference is another MP:SLT. From there. leading to the DPC that was calculated during GTT. it is given to that MP:SLT. especially created for doing global title translations.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 . . . . . . . . . . .Administration of the Signaling Network Siemens MSU SS7-Links 64 kbit/s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . trunks LTG MSU LTG SSNC LTG LIC SS7-Links 64 kbit/s ASN LTG HS-Links 2 Mbit/s LIC SN SN MP/SLT MP/GTT MB D MP/SLT SC MP/STAT MP/SM MP/OAM CP113C CP113C Fig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 STP with GTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Administration of the Signaling Network MN2513EU11MN_0001 © 2002 Siemens AG Siemens 19 .

Siemens 2 20 Administration of the Signaling Network Message transfer part MN2513EU11MN_0001 © 2002 Siemens AG .

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 not be discussed in this course. MN2513EU11MN_0001 © 2002 Siemens AG 21 . linking a timeslot of a PCM to an MP:SLT that performs level 2 and level 3 tasks for that link.Administration of the Signaling Network Siemens 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 creation The aim of the level 1 path through the SSNC is to create a nailed up connection.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens CRSIGDLLTG (EQN . . . . . . . . . . . . . .LIC LIC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 .MP) D900 SIGN-TRUNK CR TRUNK CR TGRP Low Speed Link 64kb/s CRPDCLNK LTG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .MP) for ATM / CRSIGDLHSITU (IWP – MP) for STM CRVCHAN TCS-ID VPI/VCI Fig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Creation of the level 1 path through the SSNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Port L L T SN T G G TS LIC TS STM IWP MP:SLT TS High Speed Link 2Mb/s ASN/ AMX STM CRHSIWP LIC-ID Port IWP-ID STM MP:SLT CRIWPSS7 LIC-ID Port Time slot IWP-ID IWP Low Speed Link 64kb/s SSNC IW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .MP) CRSIGDLHS (VC . . . . . . . .TRUNK CR TRUNK CR TGRP CRLICPRT Lic Port TrafficType MP:SLT 2Mb/s ATM or STM CRTCSUBL LIC-ID LIC Port CRVPATH TCS-ID VPI ATM CRSIGDLLIC (IWP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

• CRLICREDG A LIC redundancy group is necessary before a LIC pair is created. are connected. may be the same as the 'outward LTG' but different LTU) that provides the connection to a LIC of the SSNC. • CRSIGDLLTG Nailed up connection between a timeslot of an outward LTG and an MP:SLT. WARNING All interworking trunks need an interworking point! Creating more trunks than interworking points or creating more interworking points than interworking trunks can cause problems! New signaling links might not get active! MN2513EU11MN_0001 © 2002 Siemens AG 23 . links may be routed to the SSNC via a PCM line. • CRTGRP / CR TRUNK Creating trunks on the EQNs of the outward LTGs on which the links.1 Siemens Signaling links connected via D900 Like with the CCNC. connected to a DIU of an LTG ('outward LTG').1. Through the D900 switching network these links are routed to a dedicated LTG ('inward LTG'. coming from the signaling network. • CRLIC Creation of the LICs connected to the inward LTGs • CRLICPRTE1 Which ports of the LIC are used and to what kind of link will they get connected? • CRPDCLNK Definition of the PCM line between the inward LTG and the LIC port. Creation sequence: • CRLTG Inward and outward LTGs have to be created and active. • CRIWPSS7 Translating the STM connection parameters into ATM connection parameters. • ENTRPDCCHR The PDC-characteristics of the INWARD LTGs have to be set to CRC4MF.Administration of the Signaling Network 2. Both kinds of LTG are of load type 46. • CRTGRP / CR TRUNK Creating the interworking trunks between the inward LTG and the LIC port. • CRLTU LTU type D30 for inward and outward LTG is created.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Port IW. . . . . . . . . . .Administration of the Signaling Network Siemens CRSIGDLLTG (EQN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .LIC LIC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 . . . . . . . . . . . . .MP) EWSD SIGN-TRUNK CR TRUNK CR TGRP Low Speed Link 64kb/s CRPDCLNK LTG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . connected via LTG . . . . . . . . . . . . . . . . . . . . . 9 L1 path for links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .TRUNK CR TRUNK CR TGRP LIC L L T SN T G G TS SSNC TS MP:SLT STM IWP CRIWPSS7 LIC-ID Port Time slot IWP-ID MP:SLT ASN/ AMX CRLICPRT Lic Port TrafficType MP:SLT Fig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4. at the inward LTGs. When creating the links in a linkset.1.1 Siemens SS7 trunks at outward LTG Before setting up the Signaling Data Link (nailed up connection). Each IWTR is allocated to one of the two possible 'interworking' trunk groups (IWTGRP). 1. Only 2 PCM lines per LTG are used for the LIC connection. 2. these are always set up automatically in the first IWTGRP). This connection through the SN will be switched through as soon as the links are activated. 'Interworking' trunks (IWTR) are reserved via MML commands on the inward LTG. The other two PCM lines may be used for speech connections. the ports required for the signaling links must be reserved by means of CRTGRP (GCOS=CCSLGRP) and CRTRUNK (LCOS=DIGSIG8) in the outward LTG.1. All IWTRs of one inward LTG belong to the same IWTGRP. these links are automatically allocated alternately to one of two existing IWTGRP. TIP Trunks and trunk groups are still created in the D900 by MML commands.1.1. 3.2 Interworking trunks at inward LTG The connection between D900 and SSNC is realized by one (min) or two (max) 'interworking' trunk groups.Administration of the Signaling Network 2. 2. (If there are just link sets with one link only. MN2513EU11MN_0001 © 2002 Siemens AG 25 . The operator only specifies the port of a link on the outward LTG and the MP:SLT on which the link should terminate.

LTG=0-5. LCOS=DIGSIG8. Fig. LTG=<a-b> . [TRRANGE= . OPMODE=IC. 11 Outward trunks Create interworking trunk group at inward LTG CRTGRP: TGNO=<name> .LTG=<a-b> .]BLK=NONE. LCOS=DIGSIG8.LC=<LTU-TS>. LCOS=DIGSIG8. Fig. TRRANGE=31. OPMODE=OG.and interworking trunks (example) Create SS7 trunk group at outward LTG CRTGRP: TGNO=<name> .Administration of the Signaling Network Siemens CR TGRP: TGNO=IWTG01. GCOS=CCSLGRP.OPMODE=OG. 10 SS7. [TRRANGE= .]BLK=NONE. CR TRUNK: TGNO=IWTG01. 12 Interworking trunks 26 MN2513EU11MN_0001 © 2002 Siemens AG . Create trunks in SS7 trunk group CRTRUNK: TGNO=<name>. GCOS=IWTGRP. CR TRUNK: TGNO=C7TG01. CR TGRP: TGNO=C7TG01.LC=<LTU-TS>.GCOS=IWTGRP. Create trunks in interworking trunk group CRTRUNK: TGNO=<name> . LC=1-31. LCOS=DIGSIG8. LTG=0-1. CR PDCLNK SN SN 0 1 2 3 LTG 0-5 outward CR IWPSS7 IWTG01 LTG 0-1 inward 0 1 2 3 LTG 0-2 inward 0 1 2 3 1 3 4 0 1 2 3 LTG 0-6 outward LTG 0-3 inward 0 1 2 3 LTG 0-4 inward 0 1 2 3 MP MP22 2 5 6 (SM) (SM) L I C ASN/ ASN/ AMX AMX MP5 MP5 (SLT) (SLT) 7 8 MP6 MP6 (SLT) (SLT) IWTG02 Fig.GCOS=CCSLGRP. LC=2-1.OPMODE=IC.

which make up the two interworking trunk groups 0 and 1.3 Siemens Create PDC link The PCM lines between the LIC ports and the ports of the inward LTG (DIU) must be defined.1. All ports of the inward LTGs are divided into a maximum of two groups.Administration of the Signaling Network 2.1. MN2513EU11MN_0001 © 2002 Siemens AG 27 .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8>. . . . . . . . . . . . . . . . . . . . . . . . PDCLNK = <0…3> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens Create PDC link CRPDCLNK: LIC = . . . . . . . . . . . . . . . . . 13 PDC link between inward LTG and LIC DISPPDCLNK:LIC=1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Display PDC-link (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LTG = <a-b>. . . . . . . . . . . . . LICPORT = <1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISPLAY PDCLNK DATA LIC LICPORT LTG PDCLNK -----+---------+-------+-----1 1 1 1 1 1 1 1 1 2 3 4 5 6 7 8 0-1 0-1 0-2 0-2 0-3 0-3 0-4 0-4 2 3 2 3 0 1 0 1 Fig. . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 . . . . . . .

the ports must be created accordingly.4 Siemens Creation of LIC ports Each LIC has 8 connectable ports. Depending on the connection (high speed/low speed links.).1. 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'). PCM24) may be used. TIP Since the LICs are created as a pair of one active and one redundant LIC. the port is created with 31 time slots of 64 kb/s each.1. CR LICPRTDS1 (for PCM 24 LIC ports) CR LICPRTE1 (for PCM 30 LIC ports) If the traffic type is 'STM' (for 64kb/s links). PCM30) and DS1-connections (1. E1. direct connection or via D900). one must make sure. MN2513EU11MN_0001 © 2002 Siemens AG 29 .(2Mb/s. In the SSNC both. If a LIC port is not created with the 'Administrative State = Unlocked'. that the LIC-ports are created at the active LIC only (DISP LICREDG. 'CRC' stands for 'cyclic redundancy check' (CRC4) and will be used as default value. it has to be unlocked afterwards. the redundant LIC has to be entered too.5 Mb/s. Nevertheless. using the task MODLICPRTE1.Administration of the Signaling Network 2. In case of 'ATM' (for high speed links) only one object with 2 Mb/s is created on a LIC port. The 'E1 frame format' describes the kind of error detection method of the PCM line.

state Operational state Alarm status Current problem list Alarm profile MP Traffic type Timing source E-bit E-bit polarity National bit E1 frame format | | | | | | | | | | | | | | 1 5 2 Unlocked Enabled Cleared "MAJNOESC" STM System time TRUE TRUE FALSE CRC Fig.] [E-Bit polarity = TRUE.. 16 DISP LICPRTE1 (example) 30 MN2513EU11MN_0001 © 2002 Siemens AG . [Timing source= <System time/Loop>. Redundant LIC = .] [Alarm profile MP= ].] [National Bit = FALSE.] [Admin.. LIC LIC port Redundant LIC Admin. 15 LIC port for PCM30 link DISP LICPRTE1:LIC=1. state= Locked/Unlocked. Fig. Traffic type = <STM/ATM>. LIC port=5.8>. LIC port = <1.] [E1 frame format = CRC.] [E-Bit = TRUE.Administration of the Signaling Network Siemens Create LIC ports for 64kb/s links (PCM 30) CRLICPRTE1: LIC = .

1. LIC-port. The operator specifies only the physical location of each time slot (LIC. time slot) for which a virtual connection should be created and the system generates all necessary data for the ATM connection itself. MN2513EU11MN_0001 © 2002 Siemens AG 31 .1. It makes sense to assign an IWP ID from which the relation between LIC-port and timeslot can be derived: Example: "a b c" 1304 LIC: a 1 LIC Port: b 3 Time Slot: c 04 IWP ID: The task CRIWP has to be entered once for each single timeslot on the connection between inward LTG and LIC.5 Siemens Interworking points For every 64kb/s link. The virtual connection is identified by an interworking point number (IWP ID). TIP The IWP-ID is used in the Signaling Data Link task (CRSIGDLLTG) for directly connected low speed links to set up a permanent virtual connection (PVC) from a time slot of a PCM to an MP:SLT. which can be entered by the operator or is assigned automatically by the system.Administration of the Signaling Network 2. Virtual connections for narrow band links (64kb/s) have to be created as interworking points (IWP). A parameter similar to "TRRANGE" in CRTRUNK does not exist. Most of the ATM description data are internally predefined and don't need to be specified by the operator. virtual connection data must be created to translate the STM connection parameters into ATM connection parameters that are used SSNC internally.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens Create interworking point for SS7 CRIWPSS7: LIC = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Virtual connections for 64kb/s links DISP IWPSS7: IWP ID=1103. . . . . . . . . . . . . .. . . . . . . . . . . 32 . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8>. . . . . . .] [Admin State = <Locked/Unlocked>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [IWP ID = . . . . . . . . . LIC Port =<1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31>. . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . state Operational state Alarm status Current problem list Alarm profile MP | | | | | | | | | 1103 1 1 03 Unlocked Enabled Cleared "CRITICAL" Fig. Fig. . . . . . . . . . . . 18 Display interworking point SS7 (example) . . IWP ID LIC LIC port Time slot Admin. . . . .. . . . . . . . . . . . . . . . . . . . . .] [Alarm Profile MP = ]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time Slot =<1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Administration of the Signaling Network 2. Specifying both end points. In the CRSIGDLLTG task.1. The time slots between D900 (LTG.6 Siemens 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. the end points are defined by the time slot location of the outward LTG and the MP:SLT. It is sufficient if the signaling network and the data link are identified by their given names. The parameter 'Bit inversion' indicates whether the level 1 bit stream is inverted for a signaling data link or not. direct or via EWSD to the LIC port). The identification number (ID) is then found/allocated automatically. which are connected on the D900 side as STM-NUC and on the SSNC side as ATM-NUC (PVC). The bandwidth of the internal through connection will always be 64kb/s in case of low speed links.inward port) and SSNC (LIC) are selected by the system automatically. MN2513EU11MN_0001 © 2002 Siemens AG 33 . network (time slot of the outward LTG) and MP sets up data links between them automatically. i.e. Depending on the kind of signaling connection (Low Speed/High Speed.1. different tasks with different parameters have to be used.

] Net name = <name>. TS>. [Data link ID = . Outward EQN = <LTG SET. Net name | Data link | Data | MP | LIC Port | Inward EQN | Outward EQN | 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. [Net ID = .Administration of the Signaling Network Siemens Create signaling data link for 64kb/s links via LTG CRSIGDLLTG: Data link name = . MP = <no.] Adjacent DPC = <DPC of partner exchange>. LTG. 19 Signaling data link for low speed links via LTG DISPSIGDLLTG:Net ID=1. DIU. [Transmission rate = 64 kBit. Net name Net ID Data link name Data link ID Adjacent DPC MP LIC Port Inward EQN SN Info Outward EQN Interworking point ref. 20 Display of a signaling data link LTG (example) 34 MN2513EU11MN_0001 © 2002 Siemens AG . Operational state Transmission rate Bit inversion Used | | | | | | | | | | | | | | | | | | | | | | “TELECOM1" 1 “DL1T-Munich" 1 2-2-2-2 5 LIC = 1 LIC port = 1 LTG SET | LTG ID | DIU ID | STM channel | . of MP:SLT>. LTG SET | LTG ID | DIU ID | STM channel | Enabled 64 kBit No inversion TRUE 0 1 2 7 0 5 1 16 Fig.] [Bit inversion = No Inversion]. Fig.Data link ID=1.

• CRSIGDLLIC Nailed up connection between a timeslot of the SS7-PCM and an MP:SLT. each timeslot of the PCM represents one 64kb/s signaling link.Administration of the Signaling Network 2. Since no trunk groups and no trunks are needed here. • CRLIC Creation of the LICs connected to the inward LTGs • CR LICPRTE1 Which ports of the LIC are used and to what kind of link will they get connected? • CR IWPSS7 Translating the STM connection parameters into ATM connection parameters. In that case.1. MN2513EU11MN_0001 © 2002 Siemens AG 35 . a PCM line with signaling links may also be connected to the SSNC directly without an LTG. the necessary database is simpler than in the case described before.2 Siemens Signaling links directly connected to a LIC In opposite to the CCNC. Creation sequence: • CRLICREDG A LIC redundancy group is necessary before a LIC pair is created.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens CRSIGDLLIC (IWP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .MP) SSNC LIC MP:SLT MP:SLT Low Speed Link 64kb/s TS ASN/ AMX STM CRIWPSS7 LIC-ID Port Time slot IW P-ID MP:SLT CRLICPRT LIC-ID Port TrafficType Fig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 L1 path for links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . directly connected to SSNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

the LIC-port. virtual connection data must be created to translate the STM connection parameters into ATM connection parameters that are used SSNC internally. the ports must be created accordingly. connected via LTG. In the CRSIGDLLIC task. E1. TIP The LIC ports have to be created in the same manner as for low speed links.1.2. Depending on the connection (high speed/low speed links. which are connected on the D900 side as STM-NUC and on the SSNC side as ATM-NUC (PVC).1. defined in CRIWPSS7) and the MP:SLT.1. This involves nailed up connections. The identification number (ID) is then found/allocated automatically. It is sufficient if the signaling network and the data link are identified by their given names. The parameter 'Bit inversion' indicates whether the level 1 bit stream is inverted for a signaling data link or not. The bandwidth of the internal through connection will always be 64kBit in case of low speed links. described before: 2.e. Virtual connections for narrow band links (64kb/s) have to be created as interworking points (IWP).2 Interworking points For every 64kb/s link.2. TIP The interworking points have to be created in the same manner as for low speed links connected via LTG and described before. direct connection or via D900). 2. MN2513EU11MN_0001 © 2002 Siemens AG 37 . PCM24) may be used.2.1 Siemens Creation of LIC ports Each LIC has 8 connectable ports. the endpoints are defined by the interworking point (i.5 Mb/s. PCM30) and DS1-connections (1. In the SSNC both.Administration of the Signaling Network 2.3 Create a signaling data link Signaling Data Links form the connection between the SS7 links from the network and the MP:SLT.(2Mb/s.

. . . . . . . . . . . directly connected to a LIC port 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .] [Net name = <name>. . . . . . . . . . [Data link ID = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . Interworking point ref. . . . . . of MP:SLT>. . . . . . . .] Adjacent DPC = <DPC of partner exchange>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Signaling data link for low speed links. . . . . . . . . . . . = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [Transmission rate = 64 kBit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens Create signaling data link for 64kb/s links CRSIGDLLIC: Data link name = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .] [Bit inversion = No inversion]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MP = <no. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .] [Net ID = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Such a virtual connection consists of a virtual path (similar to a TGRP). The information.g. signaling messages. The different tasks like packing the user information into the payload of an ATM cell and inserting these cells into the continuous cell-stream. VCI and the transmission convergence sublayer have to be created in the SSNC database for each LIC port at which a high-speed link terminates. is contained in the header of each cell as virtual path identifier (VPI) and virtual channel identifier (VCI). • The Physical Layer (layer 1) is subdivided into a Transmission Convergence Sublayer that fits the ATM cells into the physical transmission medium (PCM) and a Physical Medium Sublayer that is responsible for the electrical adaptations to the transmission medium. The bandwidth of the highspeed connection is fixed to the bandwidth of the physical carrier (2Mbit/sec for PCM30). as e. • The ATM Layer (layer 2) forms the ATM cells by adding header information like VPI and VCI to each payload. cutting the user information into portions that fit into the ATM cells and stuff them with security information because ATM does not care for the error free transmission of the payload inside the cells. • The ATM Adaptation Layer AAL (layer 3) is responsible for segmentation. User information.3. packed into the cells and sent through the ATM network light freight in a container on a truck. an administrative group of one or more virtual channels (similar to a trunk in a TGRP).1.3 Siemens High-speed (ATM) signaling links High-speed links are ATM connections between an SSNC and another ATM node on which signaling messages are transmitted as payload. is divided into portions of 48 byte. 2. are described by a fourlayer ATM model: • The higher layers (layer 4) represent the users that provide information to be transmitted. TIP VPI.e. ATM divides each physical transmission into logical connections (virtual connections) that are assigned to the services that require transportation. i. to which virtual connection a specific cell belongs.1 ATM terminology Transmitting information in ATM is done by a continuous stream of "ATM cells" of fixed length (48 byte payload and 5 byte header). MN2513EU11MN_0001 © 2002 Siemens AG 39 .Administration of the Signaling Network 2.1.

23 ATM virtual connection Higher Layer PAYLOA D ATM Adaptation Layer PAYLOA D ATM Layer Transmission Convergence Sublayer PAYLOAD PAYLOAD Physical Layer Physical Medium Sublayer Fig. 24 ATM layers 40 MN2513EU11MN_0001 © 2002 Siemens AG .Administration of the Signaling Network Siemens SIEMENS SIEMENS SIEMENS D900 SIEMENS D900 SIEMENS SIEMENS SSNC SSNC ATM High Speed Link Virtual Path Virtual Channels Virtual Connection Fig.

3. This virtual channel may be used by a signaling data link to connect a high speed-signaling link. The TCS Id to be entered is the one. 2. It must be equal at both sides of a virtual path. Using the command CRSIGDLHS. The logical ATM connection was created with the tasks described above.1.4 Virtual channel The task CRVCHAN creates a virtual channel within the previously created virtual path. given by the previous command.1.1. Cell scrambling is an option that scrambles/descrambles the content of ATM cells according to a given.Administration of the Signaling Network 2.3. The task CRTCSSUBL creates this sublayer for a given LIC port. The chosen VPI value entered here will be present in the header of the corresponding ATM cells.5 Signaling data link for high-speed links High-speed connections in this context are always 2 Mb/s ATM connections.3. a "permanent virtual connection“ PVC is set up between the created virtual channel and the specified MP. MN2513EU11MN_0001 © 2002 Siemens AG 41 . The LIC port must be set up as an ATM port accordingly (Traffic type = ATM).3.3 Virtual path The task CRVPATH defines the virtual path identifier of an ATM connection. fixed algorithm. 2.1. It returns a TCS Id that has to be entered when creating VPI and VCI afterwards. The data link connection is a switch from a virtual ATM connection (VC TTP ID) to an MP:SLT. The VCI must be equal at both sides of a virtual channel.2 Siemens Transmission convergence sublayer The Transmission Convergence Sublayer fits the ATM cells that are available at the LIC port into the physical transmission medium (PCM) and vice versa. 2. This task returns a VC TTP ID that has to be entered as "Virtual channel" when creating the signaling data link.

. . . . . . . . . . . . . . . . . . . . . Cell scrambling enable = <TRUE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .] Adjacent DPC = DPC of partner exchange>. . . . . . . . . . . . . Alarm profile MP = . . . . . . . . . . . Create Signaling Data Link for ATM High Speed Links CRSIGDLHS: Net name = <name> [Net ID = . . . . . Create Virtual Channel CRVCHAN: TCS id = <output of CRTCSUBL>. . . . . . . . . . . of MP:SLT> . . . . . . . . . . . . . . . . 42 . . . . . . . . . . . . . . . unlocked>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LIC port = <1…8>. . . . . . . . . Alarm profile MP = . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens Create Transmission Control Sublayer CRTCSUBL: LIC = <no. . . . . . . . . .] Data link name = <name>. . . . . . . . . . . . Admin state = <locked. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [Data link ID = <1…1500>. . . . . . . . . . . . . . . FALSE>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Admin state = <locked. . . . . . . . . . . . . . . . . . . . . . . Create Virtual Path CRVPATH: TCS id = <output of CRTCSUBL>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MP = <no. . . . . VCI = . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual channel = <output of CRVCHAN>. .>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . 25 Q3 tasks . . . . . . . . . . . . . . . . . . . . . . . . Fig. . VPI = . . . . . . . . . . VPI = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . unlocked>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TIP This is NOT the ATM link that may be connected to an ATM port of a LIC. directly to a LIC-port. high data rates for one single link. but the ATM standard is not desired.4 Siemens SS7 high speed link (STM) In cases where links with high data rates are required. are bundled. this software has to be tested and released for the concerned project. offering similar data rates! WARNING Although the software to realize SS7 HSL with 1. this software is neither tested nor released for the world market. MN2513EU11MN_0001 © 2002 Siemens AG 43 .5 or 2Mb/s signaling connection. and thus of a LIC port. For this purpose all timeslots of a PCM carrier (PCM 24/30). thus representing the mentioned.1. adaptation is done on layer 2 level only. based on STM technology.Administration of the Signaling Network 2. the SS7 High Speed Links (HSL) offer a possibility to connect a 1. The new data rates are transparent to the higher layers of CCS7. If requested.5 Mb/s over a PCM 24 line is available and administration is possible.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Connection possibilities for SS7 links to SSNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens LTG SS7-Links 64 kbit/s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 / 2Mb/s STM MB D SC MP/SLT MP/STAT MP/SM MP/OAM CP113 Fig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LTG SSNC LTG LIC SS7-Links 64 kbit/s ASN LTG LIC SS7-Links ATM SN LIC SS7 High Speed Links 1. . . . . . . . . . . . . . . . . . . . . . . . . .

5 Mb/s and 2. the length of some fields in the MSU header and the applied error rate monitoring method.1.4.0 Mb/s are used. apart from the transmission rate. the forward sequence number FSN and backward sequence number BSN are in binary code from a cyclic sequence from 0 to 4095.5/2Mb/s HSL are. the format of the sequence numbers changes from 7 bits to 12 bits.Administration of the Signaling Network 2. If the extended sequence number format as described above is used.1 Siemens Differences to narrow-band links The only differences between a 64kb/s link and the new 1. Signal unit format When link data rates of 1. MN2513EU11MN_0001 © 2002 Siemens AG 45 . the length indicator format changes from 6 to 9 bit. In this case.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Adapted SU formats for SS7 HSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens MSU-format for SS7 HSL: F CK 8 16 LSSU-format for SS7 HSL: SIF 273>n>2 bytes F CK SF 8 16 8 or 16 FISU-format for SS7 HSL: 8 F B I FSN I BSN B B L I SIO 2 6 1 9 7 1 12 2 6 1 9 CK 8 16 7 12 8 F B I FSN I BSN B B L I F F 7 1 12 F 7 12 8 F B I FSN I BSN B B L I 2 6 1 9 7 1 12 7 12 F 8 Fig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LIC Port =<1. Depending on the network type. Difference to CR IWP.Administration of the Signaling Network 2.4. preventive cyclic retransmission.0_H: ITU network.DISP MTPL2PF The layer-2 profile for high-speed links acc. and the applied error correction method. Fig. But: HSL must not be connected via LTG..0_H: ANSI network.1. high-speed link • ANS PCR2.] [Admin State = <Locked/Unlocked>. it has to be entered in the linkdefinition (parameter: 'Profile name'). CR SIGLINK . [IWP ID = . highspeed link Create interworking point for SS7 high speed links CRHSIWPSS7: LIC = .] [Alarm Profile MP = ]. 2Mbit/s. 2Mbit/s. CR HSIWPSS7 'Create high speed interworking point' is very much like creating a narrow band IWP. ITU or ANSI.. which is used for LIC NB links: no parameter "Time Slot" because not a single timeslot is carrying the signaling information but the whole PCM line. Nevertheless. high-speed link • ANS BAS2. basic error correction. Two new Q3 tasks are available for HSL and the layer-2 profile of these links must be selected according to their transmission rate and network type. which is used for narrow band links: parameter "Transmission rate” supports 2Mb/s (and 1. ITU Q703 is predefined in the SSNC and does not need to be defined manually. preventive cyclic retransmission. four different profiles are available: • ITU BAS2. 2Mbit/s. high-speed link • ITU PCR2. Thus all ts of a LIC port are grouped together to form one interworking point.0_H: ITU network.2 Siemens Administration of SS7 HSL The administration of SS7 HSL is very similar to the administration of narrowband links.0_H: ANSI network.5Mb/s but not released).8>. CR SIGDLLIC Difference to CR SIGDLLIC. 28 Q3 task to create interworking point for HSL MN2513EU11MN_0001 © 2002 Siemens AG 47 . 2Mbit/s. basic error correction.

5 Mbit/s --------------------------------------------"ITU BAS1. L2 profile name | L2 profile ID ============================================= : : --------------------------------------------"ITU BAS2. Link set name = Link code = .0_H" | 69 --------------------------------------------"ANS PCR2.0_H" | 66 --------------------------------------------"ANS BAS1. Create signaling link for high speed links CRSIGLINK: Data link ID = .5_H" | 72 Fig. Interworking point ref.] [Bit inversion = No Inverse]. Net ID = . = . Fig. [Data link ID = . 1536 kb/s>.5_H" | 68 --------------------------------------------"ANS BAS2. 30 MTP layer 2 profiles 48 MN2513EU11MN_0001 © 2002 Siemens AG .0_H" | 65 --------------------------------------------"ITU PCR2.0_H" | 70 Can‘t be used because feature is not released for 1.] Adjacent DPC = <DPC of partner exchange>.] Net name = <name>.5_H" | 71 --------------------------------------------"ITU PCR1.5_H" | 67 --------------------------------------------"ANS PCR1.Administration of the Signaling Network Siemens Create signaling data link for high speed links CRSIGDLLIC: Data link name = . Protocol profile name = …. [Net ID = . of MP:SLT>. 29 Q3 task to create a signaling data link for HSL DISPMTPL2PF. [Transmission rate = <1984 kb/s. MP = <no.

• 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. The MPUE+ has a modified ASIC 'ATM230 V2.1.3 Siemens Required hardware The MPs to which the SS7 HSL are connected via a signaling data link must have a MPUE+ as processing units. MN2513EU11MN_0001 © 2002 Siemens AG 49 .Administration of the Signaling Network 2.4' on board to offer the required functionality: • processing of SS7 HSL – implementation of a SS7 'Error Interval Monitor' for HSL – adaptation to the new signaling unit format with extended header fields (see above).4. MPUD will not work.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

With the aid of the appropriate database.Administration of the Signaling Network 2. MN2513EU11MN_0001 © 2002 Siemens AG 51 . the MTP is then able to carry out its tasks.2 Siemens 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.

. . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 . . . . . . . . . . . . . . . . . Signaling link set 16 16 . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens Originating Point SIEMENS D 900 SIEMENS Signaling links D 900 CRSIGPOINT CRSIGLINK 1 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CRSIGLSET 31 Signaling Point (STP or SRP) 31 SIEMENS 1 Signaling route CRSIGROUTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 16 . 31 Signaling network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . Signaling links D 900 SIEMENS D 900 Signaling link set SIEMENS Signaling Point (STP or SRP) D 900 SIEMENS D 900 Destination Point CRSIGDP CRSIGDP Fig. . . . . . . . . . . . . . . . . . . . . . . . 31 SIEMENS D 900 SIEMENS D 900 t ui n rc o ci ti n ma no for or g in ed in at al el n t r ig ui d s irc te C ela r . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

it has to be set up as STEP. the message is discarded and the discarded-message counter is incremented. Depending on the project specific structure. It is sufficient to specify their 'Net Name'.Administration of the Signaling Network 2. MN2513EU11MN_0001 © 2002 Siemens AG 53 . it can distribute a received message to its own users only. not even SCCP for GTT.1 Siemens Own signaling point code Every signaling point must have an own signaling address. 'TFR compatibility' determines where message rerouting will be done in case a TFRmsg from an STP is received. If a different MSU length than 272 octets is required.e. whether a received TFA-/TFP message shall be broadcasted to no. consisting of SPC and network indicator that is unique in the signaling networks this node belongs to. Furthermore.2. the parameter 'Supported data length' has to be set accordingly. TFP).and status messages (TFA. it must be defined how the SP shall handle signaling. Should the routing label of an MSU indicate that a transfer to another signaling point is required. the 'NetID' will be assigned automatically. this SPC has to be entered as a decimal value or structured (see chapter "Introduction to CCS7"). SEP Signaling point functions purely as signaling end point. STEP Signaling point functions as signaling transfer point and signaling end point. The parameter 'TFP TFA broadcast' determines.e. i. or just a limited number of neighboring signaling points. TIP CRSIGPOINT is the task in which all the handled signaling networks for 'Multiple SS7 Networks' are defined by creating an own signaling address on these networks. an own signaling address must be assigned for each of the handled networks. all. Thus. level 4 of CCS7 will not be used to evaluate the message. The 'Signaling point type' determines the usage of the own SP: STP Signaling point functions purely as a signaling transfer point. In case the own node is a standalone signaling relay point with GTT. Due to the feature 'Multiple SS7 Networks'. up to 32 different signaling networks can be handled by a single SSNC. i.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Own signaling point . . . . . . . . . . . . . . . . . . . . . . . . .32>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SPC = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [Supported data length= length272. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TFR compatibility= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [Net ID = <1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens Create own signaling point Net Name = <name>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .] . . . Signal. . . . . . . . . . . . . . . . . . . . . point type = <SEP/STP/STEP>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CRSIGPOINT: Fig. . . . . . . . . . . . . . . . . . . . . . . . 54 . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .] Net Indicator = <Nat0/1 Inat0/1>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . TFP TFA broadcast=<YES/NO/Restricted> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .] [Alarm profile MP = . . . . . . . . . . . . . . . .

MN2513EU11MN_0001 © 2002 Siemens AG 55 . Apart from the parameters mentioned.Administration of the Signaling Network Siemens The opposite page shows typical signaling point data.and transfer prohibited messages. many others are shown. mainly timer values and parameters. indicating how to handle transfer allowed.

Administration of the Signaling Network Siemens DISP SIGPOINT Net Net Net SPC SPC | | | | structure | | | | | | | | | | Operational state | Alarm status | Alarm Profile MP | RST after conf DP | TFP for unknown DP | MTP restart | TFR compatibility | Ni screening | TFP TFA broadcast | Signaling point type | TFC sampling rate | Number of TFA | Number of TFP | TFA interval | TFP interval | Supported data length | TUP | Send UCIC indicator | LPO control bit | ITU-Timers Q704 timer T1 | Q704 timer T2 | Q704 timer T3 | Q704 timer T4 | Q704 timer T5 | Q704 timer T6 | Q704 timer T7 | Q704 timer T8 | Q704 timer T10 | Q704 timer T11 | Q704 timer T12 | Q704 timer T13 | Q704 timer T14 | Q704 timer T15 | Q704 timer T16 | Q704 timer T17 | Q704 timer T18 | Q704 timer T19 | Q704 timer T20 | Q704 timer T21 | Q704 timer T22 | Q704 timer T23 | Q704 timer T24 | Q707 timer T1 | Q707 timer T2 | 56 name ID indicator "TELECOM1" 1 National network 0 1-1-1-1 No. of bit | Component | Component s | minimum | maximum ====================================== 4 | 0 | 15 -------------------------------------3 | 0 | 7 -------------------------------------4 | 0 | 15 -------------------------------------3 | 0 | 7 Enabled Cleared "CRITICAL" FALSE TRUE Off TRUE Activated Yes STEP 8 100 100 600 600 Length 272 FALSE TRUE 1000 2000 1000 1000 1000 1000 1000 1100 40000 60000 1500 1500 3000 2000 1400 1500 30000 68000 60000 64000 190000 190000 500 12000 90000 MN2513EU11MN_0001 © 2002 Siemens AG .

Destination points are uniquely identified by a signaling network 'Net Name/ID' and an SPC.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. so called signaling transfer points. leading to one other signaling point of the own network are known as signaling routes.2. All MSUs are offered to the linkset with the highest priority SLS1. Loadsharing is only effective if at least two linksets are created for the same destination... MN2513EU11MN_0001 © 2002 Siemens AG 57 . Loadsharing can be set for the first two active linksets of a signaling route at most. to which messages can be sent and received respectively.. Depending on the project specific structure. Loadsharing is carried out by evaluation of one of the SLS-bits (Signaling Link Selection).SLS4 Loadsharing between the first two linksets having the same highest priority LSK = SLS1. found in the routing label of each MSU. how the signaling messages towards that destination point are offered to the possible linksets. all other signaling points of the same signaling network. The destination points can be reached from the own signaling point either via a direct signaling link set (i. this DPC has to be entered as a decimal value or structured (see chapter "Introduction to CCS7")..Administration of the Signaling Network 2. A loadsharing key defines. which has to be unambiguous in that signaling network. destination point is adjacent) or via one or more intermediate signaling points.2 Siemens Signaling destination point In every signaling point of a network.e. which are entered in the routing table with the same priority using 'CR SIGROUTE' (see below). All linksets. must be created as destination points. a binary '1' routes it to the second linkset. The operator determines the bit by entering a 'Loadsharing key' between 0 and 4: Loadsharing key = Loadsharing algorithm none 0 No loadsharing.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Net Name = . . . . . . . . . . . . . . . . . . . . . . . . . . . .] [Alarm smoothing time = ]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [Net ID = . . . . . . . . . . . . . . Fig. . . . . . . . . . . . . . . . . . . . . . . . .] [Alarm profile MP = . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Signaling destination point LSK = Bitposition in SLS field Selected linkset from signaling route none 0 XXXX first LS with highest priority SLS1 XXX0 XXX1 first LS with highest priority second LS with highest priority SLS2 XX0X XX1X first LS with highest priority second LS with highest priority SLS3 X0XX X1XX first LS with highest priority second LS with highest priority SLS4 0XXX 1XXX first LS with highest priority second LS with highest priority Fig. . . . . . . . . . . . . . . . . . . . . . . . .] [Loadsharing key = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DPC Name = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens Create signaling destination point CRSIGDP: DPC = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Loadsharing between linksets towards a destination point 58 . . . . . . . . . . . . . . . . . . . .

The operational state attribute describes whether the respective destination signaling point is accessible (ENABLED) or not (DISABLED). the administrative state of a destination point has to be set to 'UNLOCKED' before it can be reached. the operational state is 'DISABLED'. If the operational states of all signaling linksets leading to the signaling destination point are ’DISABLED’. As a prerequisite at least one signaling linkset must be contained in the signaling route. The possible values supported in the NE are ’LOCKED' and ’UNLOCKED’. leading to that destination point. then the operational state of the signaling destination point is ’DISABLED’. in any other case it remains ’ENABLED’. If the administrative state is 'LOCKED'. The administrative state attribute describes whether it is administratively permitted to route SS7 MSUs towards the respective destination point.Administration of the Signaling Network Siemens By means of the task MOD SIGDP. MN2513EU11MN_0001 © 2002 Siemens AG 59 .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | Opera | Load | Alarm | Alarm |Alarm | Extended|Con |Con |US | | | | | state | key | | MP |thing | problem |gested |gested|routing | | | | | | | time | list | | |state |level | ============================================================================================================================== "TELECOM1" |1 |“Munich" |2-2-2-2| Unlocked| Enabled | "sls 0" |Cleared |"MAJNOESC"| 0 | { } |Not | | | | | | | | | | | | |Congested| | ---------------------------------------------------------------------------------------------------------------------------"TELECOM1" |1 |“Berlin" |4-4-4-4| Unlocked| Enabled | "sls 0" |Cleared |"MAJNOESC | 0 | { } |Not | | | | | | | | | | | | |Congested| | -----------------------------------------------------------------------------------------------------------------------------"TELECOM1" |1 |“Hamburg"|3-3-3-3| Unlocked| Enabled | "sls 3" |Cleared |"MAJNOESC | 0 | { } |Not | | | | | | | | | | | | |Congested| | Fig. . . . . . . . . . . . . . . Fig. . . . . . . . . . . . . . state = <Locked / Unlocked>.] [Net ID = . . . . . . . . . . . .] [Admin. . . . . . . . . . . . . .] [Alarm smoothing time = ]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .] [Net Name = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Signaling destination point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .] [DPC name = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Net name |Net|DPC name | DPC | Admin. . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens Modify signaling destination point MODSIGDP: [DPC = . . . . 35 Administrative state change DISP SIGDP:Net ID =1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .] [Loadsharing key = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

the same neighbor signaling point may also be reached via other.2. consisting of up to 16 links. MN2513EU11MN_0001 © 2002 Siemens AG 61 .e. In ITU networks. i. the only allowed value for Link set type is F-link (CCS7 links). Loadsharing between the links of one Linkset is hard coded (SR9) and can't be modified.Administration of the Signaling Network 2. the Load share algorithm can be set to a value between 0 and 15. The 'max MSU length' defines the maximum length for message signal units. The maximum MSU length can be modified to a different value up to the default value of 272 octets. Since SR10. connects the own signaling point to a neighbor signaling point ('adjacent DPC') which can either be a signaling end point or a signaling transfer point. In networks with 14 or 24 bit SPCs 'International' is the only allowed value. not directly running Linksets. it defines the reaction upon signaling network congestion. At creation of a Linkset the maximum MSU length can be given as part of the Linkset specific data. The MSUs are offered equally to all links in the Linkset. Only one link set can be created between two adjacent signaling points that are specified via their SPC and Network Name/ID. grouped together in a signaling route (see below).3 Siemens Signaling link set A signaling link set. Regardless of this. 'Congestion method' reflects the control method within a signaling network.

38 Creation of a signaling link set 62 MN2513EU11MN_0001 © 2002 Siemens AG .Administration of the Signaling Network Siemens SP 100 Signaling link set X: Group of up to 16 signaling links to one adjacent signaling point Signaling link set Y SP 300 STP 200 SP 400 Fig. [Link set ID = .] [Load share algorithm = ..] Adjacent DPC = . [Net name = .] [Virtual SLS = .] [Net ID = <1.] [Periodic link set test = .32>..] Congestion method = International. Fig. 37 Signaling link sets Create signaling link set CRSIGLSET: Link set name = .] [Maximum MSU length = ].] [MTP restart = .] [Link set type = F-link.] [Alarm profile MP = . [Alarm smoothing time = .

The partner responds with a Signaling Link Test Acknowledgement (SLTA) containing the reflected test pattern. • Activation and deactivation of a linkset may be done via operations on the links. MN2513EU11MN_0001 © 2002 Siemens AG 63 . General principles on linkset state information: • The states of a signaling link set can only be displayed. Testing and maintenance sends a Signaling Link Test Message (SLTM) to the adjacent MTP.Administration of the Signaling Network Siemens If the 'Periodic link set test' parameter is set to ON. the OPC (SLTM-DPC = SLTA-OPC) 3. the Signaling Link Code (SLC. a link test of the links allocated to the link set is carried out every 90 seconds. must be the same at both sides of a link) 2. The following data are checked during the test: 1. Otherwise it is ’DISABLED’. which includes a test pattern. Operational state: It is ’ENABLED’ when at least one link of the signaling link set is enabled. the test pattern (which is merely looped back in the acknowledgement) The test is positive only if the link status is "enabled". The test checks the L2 functions and corrects MSU transfer between two adjacent SPs.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Net name Net ID Link set name Link set ID Adjacent DPC Operational state Periodic link set test Alarm status Alarm profile MP Alarm smoothing time Max. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Signaling link set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Periodic link test DISPSIGLSET:Link set name=C7LSRNC1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Administration of the Signaling Network Siemens SP A SP B SLTM 1 SLTA SLTM 2 1) 2) SLTA Testing of A-Side Testing of B-Side SLTM: Signaling Link Test Message SLTA: Signaling Link Test Acknowledge Fig. . . . . . . . . . . . . . . . . . . . . . . . Fig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .MSU length VMS Congestion method | | | | | | | | | | | | | "NAT0" 3 "C7LSRNC1" 50 bit14 : 769 Disabled Off Major "MAJNOESC" 60 272 Off International . . . . . . . . . . . . . . . . . . . . . . . . . . . . MN2513EU11MN_0001 © 2002 Siemens AG . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

• towards DPC = C. three cases are shown from point of view of 'A': • towards DPC = B. both must have the same priority assigned and the 'Priority mode' must be 'Equal'. having the same priority. loadsharing takes place between linksets LS_B and LS_C. If one of several linksets. Only if all linkset of one priority fail a switch over will take place to a linkset with the next lower priority. no loadsharing is possible. Loadsharing can take place between two linksets.2. loadsharing takes place between the linksets LS_B and LS_D only. at most. • towards DPC = D. leading to the same signaling destination point is determined by the 'Priority'. if linkset LS_C fails. In the example on the opposite page. These linksets are called signaling routes and have to be defined with the task CR SIGROUTE. fails and there is still an additional linkset with the same priority existing. loadsharing will continue. assigned to the single routes (1=highest and 8=lowest priority).4 Siemens Signaling routes Every signaling destination point may be reached by a maximum of eight signaling linksets.Administration of the Signaling Network 2. MN2513EU11MN_0001 © 2002 Siemens AG 65 . The loadsharing between all signaling routes. leading to the same DPC.

] DPC = .Administration of the Signaling Network Siemens CR SIGROUTE DPC = B: Prio1: LS_B Prio1: LS_C Prio2: LS_D DPC = C: Prio1: LS_C Prio2: LS_B Prio2: LS_D DPC = D: Prio1: LS_D Prio2: LS_C SPC B B LS_ LS_C SPC A SPC C LS_ D CR SIGLSET SPC D Fig. 41 Signaling routes Create signaling routes CRSIGROUTE: Net name = . [Route ID = .] Link set name = . 42 Creation of signaling routes 66 MN2513EU11MN_0001 © 2002 Siemens AG . [Net ID = . Priority = .] [Priority mode = Equal]. [DPC name = . Fig.

2.2. basic error correction. world market version • ANSI BASIC64 transmission rate: 64 kb/s.LIC. Fig. this does not result in the failure of a complete signaling relation.Administration of the Signaling Network 2.SIGDL(LTG.] Link code = . which must be the same value at both ends of a link. A maximum of 16 links may be created in one signaling linkset. . . that if one MP (both MPU) fails.15). PCM24. [Link set ID = . Protocol Profile name = . In this way it is ensured.9% of all cases). basic error correction.. necessary timer and correction procedure by means of a 'Profile name'. The most commonly used profiles are • ITU BASIC64 transmission rate: 64 kb/s. Data link name = .. Create signaling link CRSIGLINK: Net name = .5 Siemens Signaling links A signaling link is part of a link set and can be uniquely identified by a link code (0. the communications protocol. The 'Data link name' sets up the relation between the administrative object 'link' on one hand and the timeslot it is received on and the MP:SLT by which it will be processed on the other hand. US version Before a signaling link can be seized. When allocating SIGLINK..] Link set name = . The corresponding signaling data link must have been created before with CR SIGDLLTG/LIC/HS (see ch.HS). [Net ID = . care should be taken that the signal channels of one linkset are distributed to two MP. the administrative state must be set to 'UNLOCKED' by the task MODSGLINK. 43 Creation of a signaling link MN2513EU11MN_0001 © 2002 Siemens AG 67 . If the standard profiles are not sufficient (they will be sufficient in 99.. additional profiles may be created by CRMTPL2PRF.1). The signaling link is assigned certain characteristics such as transmission rate.. PCM30.

octets 2000 } { messages 15. Max. 44 Signaling link DISP MTPL2PF:L2 Profile name=ITU BASIC64.for retrm. | | | | | | | | | | | | | | | | | | | | | | "ITU BASIC64" 1 64 kBit Basic 45000 25000 1500 500 8200 100 4500 1000 { messages 100.abatement L1 Max. octets 300 } 127 300 Fig.oct.Siemens Administration of the Signaling Network DISPSIGLINK:Display names=Yes.cong. Link set name=C7LSRNC1.onset L1 Trm. Nr. | Net name | Net ID | Link set name | Link set | Link code | Admin. L2 profile name L2 profile ID Transmission rate Correction Method L2 timer T1 [ms] L2 timer T2 [ms] L2 timer T3 [ms] L2 timer T4E [ms] L2 timer T4N [ms] L2 timer T5 [ms] L2 timer T6 [ms] L2 timer T7 [ms] Trm. 45 MTP layer 2 profile "ITU BASIC 64" 68 MN2513EU11MN_0001 © 2002 Siemens AG . sta | Operational | | | | | ID | | te | state | | | | | | | | | ====================================================================================================== 1 | "NAT0" | 3 | "C7LSRNC1" | 50 | 0 | Unlocked | Disabled | Data link | Data link name | Protocol profi | Bandwidth | VMS ID | | le name | identifier | | | | | ================================================================== 50 | "C7LSRNC1" | "ITU64" | Broadband | Off Fig.MSU for retrm.cong.

Administration of the Signaling Network MN2513EU11MN_0001 © 2002 Siemens AG Siemens 69 .

Administration of the Signaling Network Siemens 3 70 User parts MN2513EU11MN_0001 © 2002 Siemens AG .

i.). With the help of the MML command CRC7USER. MAPVLR. These allocations must be set up to all known DPCs to which traffic channel related signaling messages are sent (i. GSM (or 3GPP) standardized. MN2513EU11MN_0001 © 2002 Siemens AG 71 . MAPVLR etc. The user parts currently in use are the ISDN User Part (ISUP) or Telephone User Part (TUP) for traffic channel related signaling and the Signaling Connection Control Part (SCCP) for the control. For every destination point to which an SCCP message is signaled directly. though. The SCCP offers an interface to the BSSAP (Base Station Application Part) on one hand and to the TCAP (Transaction Capabilities Application Part) with its users on the other. the SCCP is used here "without logical signaling connections" (connectionless). the subsystem numbers are.e.Administration of the Signaling Network 3. A distinction must be made here between: • Local subsystems (SCCP Access Point local) must be created for each local user in each network node. National applications with national subsystem numbers may also exist. MAPEIR and the INAP or CAP (so-called SCCP USER) use the TCAP for message control. The SCCP of the own node (SCCP linkage local) as well as the SCCPs of other nodes with which SCCP messages are exchanged (SCCP linkage remote) have to be announced in the own SSNC by Q3 tasks as described below. Each subsystem identifies itself by an SCCP calling party address. MAPMSC. the MTP users ISUP and TUP are allocated to a destination point code and a network indicator. the remote subsystem must be created in the own node in accordance with the function of the respective network node. These subsystems are addressed by means of subsystem numbers. • Remote subsystems (SCCP Access Point remote). to which trunks are seized).e. as a rule. The BSSAP uses the SCCP "with logical signaling connections" (connection oriented) and can therefore do without the TCAP.1 Siemens Overview The user parts are those parts of the signaling software that make use of the message transfer part. which may be included in the SCCP part of a signaling message for rerouting of the answer. In this case the SCCP is mainly used for address logic and address conversion towards other signaling points and for internal addressing of the corresponding SCCP subsystems (MAPHLR. addressing and address conversion of non-traffic channel orientated signaling. The mobile application parts MAPHLR.

BSSAP 254 ISUP TUP TUP+ SCCP Calling Party Address (CRSPCLGPA) TCAP SCCP Linkage Local (CRSPLNKLOC) SCCP Linkage Remote (CRSPLNKREM) SCCP CCS7 User (CRC7USER) MTP Fig. 47 Creation of MTP users ISUP and TUP 72 MN2513EU11MN_0001 © 2002 Siemens AG . DPC = ... 46 Creation of user parts Create CCS7 User ISUP and TUP CRC7USER: USNAME = <ISUP / SCCP>.Administration of the Signaling Network Siemens SCCP Access Point Local (CRSPAPLOC) SCCP Access Point Remote (CRSPAPREM) MAP HLR 6 MAP VLR 7 MAP MSC 8 MAP EIC 9 CAP 146 SCCP Subsystem Number (CRSPSSN) .…. Fig. NETNAME = .

MN2513EU11MN_0001 © 2002 Siemens AG 73 . Since the own signaling address is well known. • CR SPLNKREM Creates a link to an SCCP in a remote signaling node. with which SCCP messages are exchanged. Unit Data Req. usually global titles of type 4 are used and extended UDT messages are in use. • CR SPSSN Linking a subsystem name with a subsystem number • CR SPAPLOC Announces the local SCCP subsystems. because this will force the system to ALWAYS use this type of message and this may lead to a malfunction in the network! Additionally. 3. In mobile networks. only the signaling network on that the SCCP will send and receive messages has to be entered. TIP This sequence is not the one-and-only possible sequence. thus segmentation of messages is allowed. such as the supported global title format.1 Creation of a local SCCP linkage This task stores data about the specific capabilities of the own SCCP.Administration of the Signaling Network 3. WARNING Do not set the parameter Extd. the possibility of segmentation or the supported protocol classes for connection oriented and connectionless communication. then all REMOTE objects.2. • CR SPAPREM Announces the SCCP subsystems in the other signaling nodes. but it is tested and makes sense.2 Siemens Administration of the SCCP and its user parts Creation sequence: • CR SPLNKLOC Stores data about the SCCP in the own node. • CR SPCLGPA Creates a global title address for a local SCCP subsystem. to True. with which MAPmessages are exchanged. First create all LOCAL objects. a lower value than 255 for the Upper Limit Segment makes no sense (waste of signaling capacity).

& Reass..| Allowed ========================================================================================================== 1 | localN0DTAG | TRUE | 150 | 150 | TRUE | TRUE | 11 | | | | | | | Fig..] ..Administration of the Signaling Network Siemens Create local SCCP linkage CRSPLNKLOC: SPLNKLOC name = . 48 Creation of a local SCCP linkage DISP SPLNKLOC -----------------------------------------------------------------------------------------------------------------SPLNKLOC Identification | Congestion Timer Data | Globle Title | Operat. [Net ID = <1. = FALSE.] [GT Format = GT Type 4.] [SCL Prot Classes = class0-class1..] [Extd.] [Upper Limit Segment = 255. Net name = . Unit Data Req. Flag = TRUE. 49 Local.32>. Fig.] [SCO Prot Classes = class2-class3. . Reass. Protocols ----------------------------------------|--------------------------|--------------|------------------------------ID | Name | Net ID | Net name | Incr | Decr | NrOfLevels | GT Format | | | | =================================================================================================================== 1 | localN0DTAG | 1 | N0DTAG | 2 | 2 | 10 | GT Type 4 | Class0 | Class1 | Class2 | -----------------------------------------------------------------------------------------------------------SPLNKLOC Id.] [Segm.and remote SCCP linkage example 74 MN2513EU11MN_0001 © 2002 Siemens AG . | Extended Unit Data | Segmentation Limits | Flags | Subsystems --------------------|--------------------|---------------------|---------------------------|-------------ID | Name | Required | Lower | Upper | Screening | Segm. [SPLNKLOC ID = ].

controlling the communication between the U-MSC and the RNC. SSN=241).2. e. Some typical applications. • BS System Appl Part: Responsible for communication with the BSC.g. running via these subsystems are: • MAP HLR: Inserting subscriber data into a VLR during a location update. • IN Application in SSP 2 (CAP): Starts an IN-dialog for subscriber. • Radio Access Network Application Part (RANAP) Used for UMTS applications. Project specific applications with project specific subsystem numbers are also possible (e. MN2513EU11MN_0001 © 2002 Siemens AG 75 . having an IN-service according to the Siemens specific IN standard. • MAP MSC: Starts the MTC interrogation when an MSISDN of the own PLMN was received. • Serving GPRS Support Node: Forms the interface between HLR and SGSN for GPRS location updates. The Siemens specific subsystem ID (SSID) has to be translated into the standardized subsystem number (SSN) that is transmitted in the SCCP messages as shown in the table below.Administration of the Signaling Network 3. • ISDN Supplementary Services: Generates a CCBS request.g. • GSM Service Control Function: Forms the interface between HLR and service control point at the SCP-side. • IN Application in SSP 3 (SINAP): Starts an IN-dialog for subscriber. to start paging for a mobile station. having an IN-service according to the CAMEL standard. • MAP VLR: Requesting a location update. SSID=INAP.2 Siemens Creation of SCCP subsystem numbers The SCCP subsystems (application parts) that are responsible for the generation and evaluation of the signaling message content are addressed by means of an internationally standardized subsystem number.

Services 11 GSM Radio Access Netw. [SPLNKLOC id = .| Mobile Application Part HLR ----------------------------------------------------------------------------------------803 | sccpLi_NAT0 | 7 | -----------. ----------------------------------------------------------------------------------------805 | sccpLi_INAT0 | 254 | -----------.| Radio Access Netw.] SSID = . example 76 MN2513EU11MN_0001 © 2002 Siemens AG .Administration of the Signaling Network Siemens Subsystem ID Subsystem number Specified Mobile Application Part HLR 6 GSM Mobile Application Part VLR 7 GSM Mobile Application Part MSC 8 GSM Mobile Application Part EIC 9 GSM ISDN Suppl. Fig. 52 SCCP subsystem numbers. SPLNKLOC Id | SPLNKLOC Name | SSN | SPSSN Name | SSID ========================================================================================= 803 | sccpLi_NAT0 | 6 | -----------. SSN = . 51 SCCP subsystem number DISPSPSSN. 142 3GPP IN Application in SSP 2 146 GSM GSM Service Control Function 147 GSM Serving GPRS Support Node 149 GSM IN Application in SSP 3 241 projectspecific BS System Application Part 254 GSM Fig. subsystem number Create SCCP subsystem number CRSPSSN: SPSS name = . Appl.| Mobile Application Part EIR ----------------------------------------------------------------------------------------803 | sccpLi_NAT0 | 142 | -----------. Appl.| Mobile Application Part VLR ----------------------------------------------------------------------------------------803 | sccpLi_NAT0 | 8 | -----------.| Radio Access Netw. ----------------------------------------------------------------------------------------803 | sccpLi_NAT0 | 149 | -----------.| Mobile Application Part MSC ----------------------------------------------------------------------------------------803 | sccpLi_NAT0 | 9 | -----------.| BS System Application Part ----------------------------------------------------------------------------------------805 | sccpLi_INAT0 | 142 | -----------.| Serving GPRS Support Node ----------------------------------------------------------------------------------------803 | sccpLi_NAT0 | 254 | -----------. Appl. SPLNKLOC name = . 50 Subsystem ID vs.| BS System Application Part Fig.

Example: In an MSC/VLR. The MAPHLR that is addressed for interrogations will only be a remote SCCP access point. Should the MSC be able to handle CCBSrequests (completion of calls to busy subscriber). MAPVLR and BSSAP must be created as local SCCP access points. at least the subsystems MAPMSC. It tells the own node. which subsystems may be used to initiate a communication. since it is the MAPMSC that starts this communication.Administration of the Signaling Network 3. the subsystem ISS (ISDN supplementary services) must also be installed as a local access point.3 Siemens Local SCCP access point This command creates the subsystem control data for the own (local) signaling point.2. MN2513EU11MN_0001 © 2002 Siemens AG 77 . for the MAPHLR in an HLR). If an EIR is used in the network. The ISDN User Part ISUP must not be created as SCCP access point since it is no SCCP user. the MAPEIC has to be installed as local access point as well.g. It has to be entered once for each local application part that may be used to start a signaling transaction from the own signaling node (e.

] SSID = <name>. example Create local SCCP access point CRSPAPLOC: SPAPLOC name = . .Administration of the Signaling Network Siemens MSC / VLR MAP MSC MAP VLR MAP EIC BSS AP HLR TCAP SCCP MTP EIR Fig.. Fig. 53 Local SCCP access points.. . creation 78 MN2513EU11MN_0001 © 2002 Siemens AG . SSN = <number as in CRSPSSN>. 54 Local SCCP access point. [SPAPLOC id = .

The parameter 'CLGPA Type Indicator' defines whether the calling party address field of an SCCP message contains a global title or an SPC or both.. The SCCP calling party address has to be defined for each local subsystem. Even if the setting of 'CLGPA Type Indicator' is Programmed. but this makes no sense and is therefore not recommended! 'CLGPA Type Indicator' Content of SCCP calling party address GT (not recommended) global title of sending subsystem SPC (not recommended) SPC of sending network element Programmed same type as in the called party address field (depending on RI) TIP As this command belongs more to Global Title Translation. MN2513EU11MN_0001 © 2002 Siemens AG 79 . refer to the Global Title chapter for more details.4 Siemens SCCP calling party address If an SCCP message is sent. the corresponding calling party address must also be entered. A global title is not required in an SCCP calling party address for network internal signaling. A calling party address field may contain a global title – e.2.Administration of the Signaling Network 3. the parameters 'Include SPC' and 'Include GT' may force the global title or the SPC to be included as additional information in a called party address field.g. It is used as the sender address in the SCCP message for addressing with a global title and as the address to which the receiver of such a message will send it's response. for international signaling.

[SPCLGPA id = .] SPAPLOC name / ID = . NP = ISDN-Tel. . CLGPA Type Indicator = Programmed . [Include SPC = False . TTID = Unknown .Administration of the Signaling Network Siemens Create SCCP calling party address CRSPCLGPA: SPCLGPA name = . NA = International Nr. Numbering Plan . 55 SCCP calling party address 80 MN2513EU11MN_0001 © 2002 Siemens AG .] [Include GT = False]. GT Address Info = <GT digits>. SPLNKLOC name / ID = . Fig.

As a prerequisite.2.5 Siemens Creation of a remote SCCP linkage Each SCCP in an external signaling node. will be discarded. has to be made known in the own node. MN2513EU11MN_0001 © 2002 Siemens AG 81 . SCCP messages from nodes. the DPC must have been created with CRSIGDP before.Administration of the Signaling Network 3. which were not announced in this way. with which SCCP messages are exchanged.

Administration of the Signaling Network

Siemens

Create remote SCCP linkage
CRSPLNKREM:

SPLNKREM name = ,
[SPLNKREM ID = ],
Net name = ,
[Net ID = <1...32>,]
DPC = ;

Fig. 56 Creation of a remote SCCP linkage

DISP SPLNKREM
SPLNKREM ID | SPLNKREM Name | Net ID | Net name
| DPC
| DPC name
| Ass.Conn.SectionFl
==========================================================================================================
101
| N0DT 3-3-3-3 | 1
| N0DTAG
| 3-3-3-3
| 3483#N0DTAG
| FALSE
---------------------------------------------------------------------------------------------------------102
| N0DT 2-1-0-0 | 1
| N0DTAG
| 2-1-0-0
| 1-GTT-LOOP1
| FALSE
---------------------------------------------------------------------------------------------------------103
| N0DT 2-1-0-1 | 1
| N0DTAG
| 2-1-0-1
| 1-GTT-LOOP2
| FALSE

Fig. 57 Local- and remote SCCP linkage example

82

MN2513EU11MN_0001
© 2002 Siemens AG

Administration of the Signaling Network

3.2.6

Siemens

Remote SCCP access point

For every SCCP user (=application part, SSID) in a remote signaling node with which
messages are exchanged, a remote SCCP access point must have been created in
the own node with CRSPAPREM that is identified by the SPAPREM name or -ID.
The linkage with the remote SCCP in the other DPC is via the SPLNKREM name.
Example:
If the MSC (MAPMSC) starts interrogation towards an HLR, the MAPHLR, as the
receiver of the message Send_Routing_Information, has to be entered as remote
SCCP access point in that MSC.
Once a remote access point is created, its administrative state must be set to
'unlocked' before it is fully operable

SCCP management
Furthermore, the SCCP management is controlled via this task. SCCP management
means that local or remote subsystems (=access points) are informed of failure
(SS_PROHIBITED) or renewed accessibility (SS_ALLOWED) of those remote
subsystems, described by CRSPAPREM. The advantage of SCCP management is
that unnecessary messages e.g. to remote subsystems are omitted in the event that
these systems are down. The prerequisite for SCCP management is that the SCCP
Management parameter in the CR SPAPREM task is set to TRUE or has not been
input (default).

Remote Broadcast (SPCAREA Name=<name>)
The failures or renewed accessibility of a remote SS (CRSPAPREM) is reported to
SCCPs in other signaling points. This distribution is carried out with the aid of a socalled broadcast list. Such a broadcast list is a list of remote SCCPs, created
manually by CR SPCAREA.

MN2513EU11MN_0001
© 2002 Siemens AG

83

Administration of the Signaling Network

Siemens

Create remote SCCP access point
CRSPAPREM:

SPAPREM name = ,
[SPAPREM id = ,]
SSID = ,
SPLNKREM name / ID = ,
[SCCP Management = TRUE/FALSE,]
[SPCAREA name / ID = ,]
[SPAP Avail. Restart = TRUE/FALSE,]
[Local Broadcast = TRUE/FALSE];

Configure remote SCCP access point
CONFSPAPREM:

SPAPREM name = ,
[SPAPREM id = ,]
Admin.State = <locked/unlocked>;

Fig. 58 Remote SCCP access point and SCCP management

Create remote broadcast list
CRSPCAREA: SPCAREA name = ,
[SPCAREA id = ,]
SPLNKREM list = <name>&<name>&.... ;
Fig. 59 Definition of a remote broadcast list

84

MN2513EU11MN_0001
© 2002 Siemens AG

Administration of the Signaling Network

Siemens

Local broadcast (Local Broadcast = TRUE)
Here failures or renewed accessibility of remote SS (SPAPREM Name) are forwarded
or not forwarded to the local subsystems.

SCCP access point availability after restart (SPAP Avail. Restart = TRUE)
It is determined here whether messages for the individual subsystem's return to
service (SS_ALLOWED) are necessary or not after a remote signaling point has
returned to service (TRANSFER_ALLOWED).

• SPAP Avail. Restart = TRUE(default): No individual SS_ALLOWED messages are
required.

• SPAP Avail. Restart = FALSE: Individual SS_ALLOWED messages are required.

MAPHLR
6

MAPVLR
7

MAPMSC
8

MAPEIR
9

CAP
146

INAP
241

O
T
H
E
E
R

BSSAP
254

TCAP

SCCP

MAPHLR MAPVLR
6
7

MTP

MAPMSC
8

MAPEIR
9

CAP
146

INAP
241
BSSAP
254

TCAP

SCCP

500

O
T
H
E
E
R

MTP

SS_PROHIBITED
SS_ALLOWED

SP 1
CRSPCAREA:
SPCAREA=bclst,
SPLNKREM List=sccp100&sccp200;
CRSPAPREM:
SCCP Managem=TRUE,
SPCAREA=bclst,
SPLNKREM=remo500,
SSID=MAPHLR,...;

SS_PROHIBITED
SS_ALLOWED
SS_PROHIBITED
SS_ALLOWED
SS_PROHIBITED
SS_ALLOWED

200
100

300

Fig. 60 Remote broadcast

MN2513EU11MN_0001
© 2002 Siemens AG

85

MAPHLR 6 MAPVLR 7 MAPMSC 8 MAPEIR 9 INAP 241 BSSAP 254 TCAP MAPHLR MAPVLR 6 7 MAPMSC 8 MAPEIR 9 SCCP INAP 241 BSSAP 254 TCAP SCCP O T H E E R O T H E E R MTP MTP SP 500 SP 1 SS_PROHIBITED SS_ALLOWED Fig. LocalBroadcast=TRUE. SPAP Avail.Restart=FALSE. SPAPREM Name=remo500.. 61 Local broadcast MAPHLR 6 MAPVLR 7 MAPMSC 8 MAPEIR 9 INAP 241 BSSAP 254 TCAP SS_ALLOWED MAPHLR 6 MAPVLR 7 MAPMSC 8 MAPEIR 9 INAP 241 BSSAP 254 TCAP SCCP O T H E E R MTP & MTP SP 500 SCCP O T H E E R TF_ALLOWED CRSPAPREM: SCCP Managem=TRUE... SSID=MAPVLR. SP 1 CRSPAPREM: SCCP Managem=TRUE. Fig.. SPAPREM Name=remo500.. 62 Access point availability 86 MN2513EU11MN_0001 © 2002 Siemens AG . SPAP Avail..Administration of the Signaling Network Siemens CRSPAPREM: SPAPREM name=remo500 SCCP Managem=TRUE.Restart=TRUE.

Administration of the Signaling Network MN2513EU11MN_0001 © 2002 Siemens AG Siemens 87 .