administration signaling
Post on 15-Nov-2014
142 Views
Preview:
TRANSCRIPT
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
1
Contents
1 Control of the signaling network 3
1.1 SSNC as signaling network controller 4 1.2 Functions within the SSNC 6
1.3 Multiple SS7 networks 8 1.4 Message flows 10
2 Message transfer part 19
2.1 Level 1 path creation 20 2.2 Level 3 objects 50
3 User parts 69 3.1 Overview 70
3.2 Administration of the SCCP and its user parts 72
Administration of the Signaling Network
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
2
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
3
1 Control of the signaling network
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
4
1.1 SSNC as signaling network controller
To control the SS7 signaling system, the Signaling System Network Controller (SSNC) is used in D900
It provides the protocol functions of the message transfer part (MTP) and parts of 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.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
5
SN B
LTG
LTG
SSNC
MB D
CPAMPC IOP:MB
D900 Configuration with SSNC
Trunks and SS7 Links
SS7 Links
207Mb/s
PCM30/24
SSNC: Signaling SystemNetworkControl
LTG: Line TrunkGroup
SN: SwitchingNetwork
MB: MessageBuffer Typ D
IOP: Input/OutputProcessor
AMP: ATM BridgeProcessor
CP: CoordinationProcessor
SC: SwitchCommander
SC
207Mb/s
Fig. 1 D900 with SSNC
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
6
1.2 Functions within the SSNC
The SSNC implements the functions of the message transfer part MTP and parts of the SCCP (SCCP global title translation and SCCP management). This is shown in the following diagram, using a protocol stack.
Signaling System No.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.
Message Transfer Part
The message transfer part (MTP) is used in CCS7 by all user parts as a transport system for message exchange. 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, without information loss, duplication or sequence alteration and without any bit errors.
Functional levels of the MTP
Level 1 defines the physical, electrical and functional characteristics of a signaling data link and the access units. Level 1 represents the bearer for a signaling link. In a digital network, 64-kbit/s channels are generally used as signaling data links.
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, e.g. after disruption of the signaling data link.
Level 3 defines the interworking of the individual signaling links. 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). The MP:SLT performs MTP-level 1 (message transfer), MTP-level 2 (error correction) and MTP-level 3 (message handling incl. allocation). These SLT functions are logically combined and are performed by one or more MPs. Depending on system usage of the network node, the SSNC can be provided with up to 47 MP:SLT. Per SLT up to 60 signaling channels (64kbit/s) may be connected, but not more than 1500 links in total!
The MP:SM functional unit supports MTP-Level 3 network management and hosts the routing database for the signaling network. Thus, each MP:SLT has an internal connection to the MP:SM.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
7
User Parts
The function, structure, format and coding of the messages as well as the connection sequences and the procedures for cooperating with other signaling systems (interworking) are stipulated in the user parts. The user parts therefore control the setup and release of circuit connections, the handling of service features as well as administration and maintenance functions for the signaling channels (SCCP management). The ISDN- and telephone user parts (ISUP/TUP) are located in the LTGs. The SCCP is located in the SSNC and is the only user part in case the SSNC is operated as Signaling Relay Point (SRP).
MTP L1
MTP L2 MTP L2
ISUP
GTT GTT
TCAP
MAPs etc.BSSAP
USER PartL4
MTP L3 MTP L3
TCAP ISUP
BSSAP
USER PartL4
SCCP SCCP
ITU-T SS7 Protocol Stack
MAPs etc.
Fig. 2 MTP and user parts
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
8
1.3 Multiple SS7 networks
The feature 'Multiple SS7 Networks' expands the range of network planning options in deregulated markets with many operating companies. With this feature, up to 32 Signaling System No. 7 (SS7) routing domains (internal networks) can be administered in one signaling network node with SSNC. This feature affects MTP, SCCP and the SS7 user parts.
This means that a node can be connected to up to 32 separate signaling networks, which are allocated to the ITU standard networks (NAT0/1, INAT0/1).
The 'Multiple SS7 Networks' feature is fully compatible with ITU-T SS7 standards, i.e. it is transparent to all SS7 protocols.
Each SS7 network can be individually administered; in this way up to 32 own signaling addresses can be set up in one node. Signaling point allocation is completely flexible.
The maximum capacity of the signaling network elements (1500 signaling links, 1024 signaling trunk groups, 4096 DPC) remains unchanged. They can flexibly be distributed over all internal networks.
The message format within the SS7 network remains unchanged. The SSNC internal format contains the parameter 'Network Name' or 'Network ID' to identify the respective signaling network.
Operator benefits
• Different operators can share one network node with SSNC
• Support of multiple point codes in one network node (e.g. for network consolidation)
• Incoming linkset-specific routing domains
• Enhanced interworking with other operators
• Internal separation of SS7 traffic belonging to different operators
• Separation of traffic for different applications (e.g. MTP user parts)
• Free assignment of the network indicator (NI) per internal MTP network
• Addressing of up to 4 million trunks between two nodes
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
9
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NAT0
SSNCup to 32 internal SS7 networks
on top of the four ITU standardized neworks
ITU:4 standardized
networks
OP25
OP1
OP5OP32
OP18
NAT0/1, INAT0/1
NAT1
INAT0
INAT1
SSNC
Fig. 3 Multiple SS7 networks
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
10
1.4 Message flows
1.4.1 Signaling end point traffic
SEP messages are either messages that are generated by a user- or application part of an exchange and sent to the SS7 network, or that are received from the SS7 network and are evaluated by a user- or application part in the exchange.
TIP The involvement of global title translation in the message flow is described in the chapter "Global Title Translation".
Signaling end point traffic, 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. 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, transporting the message to it's destination (DPC in routing label of MSU). The latter connection has to be created by Q3 command. The routing database for outgoing links is hosted by the MP:SM, to which all MP:SLTs have an internal connection.
Since the SSNC internal message flow is based on ATM connections, a LIC converts the MSU format from ATM to STM (E1).
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
11
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MP/SM
MP/SLT
LTG
LTG
MP/SLT
LIC
LIC
SC
ASN
SN
CP113C
SSNC
MB D
LTG
LTG
SS7-Links 64 kbit/s
HS-Links 2 Mbit/s
SS7-Links 64 kbit/s,trunks
MP/STAT
MP/OAM
MSU
Fig. 4 SEP, outgoing signaling messages
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
12
Signaling end point traffic, incoming
Any incoming signaling message will be converted from STM to ATM in a LIC before it is forwarded to an MP:SLT by means of a 'nailed up connection', created by Q3 command. There, message discrimination, allocation and distribution is being performed. 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.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
13
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MP/SM
MP/SLT
MP/SLT
LIC
LIC
MP/OAM
SC
ASN
SSNC
SS7-Links 64 kbit/s
HS-Links 2 Mbit/s
SS7-Links 64 kbit/s,trunks
CP113CCP113C
LTG
LTG
SNSN
LTG
LTG
MP/STAT
MSU
MB D
Fig. 5 SEP, incoming signaling message
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
14
1.4.2 Signaling transfer point traffic
Signaling transfer points don’t use level 4 functions for processing SS7 messages. They either just forward a message within the same signaling network or, in case of a ‚signaling relay point‘, 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.
Signaling Transfer Point Traffic without GTT An MSU, coming from node A is forwarded to a LIC where the conversion from STM to ATM takes place. According to the created level 1 path, it will be processed by an MP:SLT. Message routing in that MP determines the link, leading to the next/final DPC for that MSU and because a link is connected to a timeslot and the timeslot to another MP:SLT, this MSU will be sent to that MP.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
15
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MP/SM
MP/SLT
MP/SLT
LIC
LIC
MP/OAM
SC
ASN
SSNC
MB D
SS7-Links 64 kbit/s
HS-Links 2 Mbit/s
SS7-Links 64 kbit/s,trunks
CP113CCP113C
LTG
LTG
SNSN
LTG
LTG
MP/STAT
MSU
MP/GTT
MSU
Fig. 6 STP without GTT
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
16
Signaling Transfer Point Traffic with GTT The message flow for an STP with GTT is very similar to the one described before. The difference is another MP:SLT, especially created for doing global title translations. After the message has been received by the first MP:SLT, the need for GTT is detected (routing indicator = 0) and the MSU will be forwarded to the ‚GTT-MP‘. From there, it is given to that MP:SLT, that is connected to the link, leading to the DPC that was calculated during GTT.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
17
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MP/SM
MP/SLT
MP/SLT
LIC
LIC
MP/OAM
SC
ASN
SSNC
MB D
SS7-Links 64 kbit/s
HS-Links 2 Mbit/s
SS7-Links 64 kbit/s,trunks
CP113CCP113C
LTG
LTG
SNSN
LTG
LTG
MP/STAT
MSU
MP/GTT
MSU
Fig. 7 STP with GTT
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
18
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
19
2 Message transfer part
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
20
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, linking a timeslot of a PCM to an MP:SLT that performs level 2 and level 3 tasks for that link.
This database is different, depending on whether the link is connected to the SSNC via LTG or whether it is directly connected to a LIC port.
The level 1 administration of high-speed links with 2Mb/s is again different but will not be discussed in this course.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
21
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MP:SLTSN
LTG
LTG
ASN/AMX
TS
2Mb/s
MP:SLT
MP:SLT
D900 SSNC
High SpeedLink 2Mb/s
Low Speed Link64kb/s
CRSIGDLLTG (EQN - MP)
CRSIGDLLIC (IWP - MP)
CRIWPSS7LIC-IDPort
Time slotIWP-ID
SIGN-TRUNKCR TRUNKCR TGRP
IW- TRUNKCR TRUNKCR TGRP
IWP
TS
CRLICPRTLicPort
TrafficType
STM
ATM orSTM
LIC
STM
IWP
CRPDCLNKLTG,LICLIC.Port
TS
Low Speed Link64kb/s
CRTCSUBLLIC-ID
LIC Port
CRVPATHTCS-ID
VPI
CRVCHANTCS-IDVPI/VCI
CRSIGDLHS (VC - MP) for ATM /CRSIGDLHSITU (IWP – MP) for STM
ATM
CRHSIWPLIC-IDPort
IWP-ID
STM
Fig. 8 Creation of the level 1 path through the SSNC
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
22
2.1.1 Signaling links connected via D900
Like with the CCNC, links may be routed to the SSNC via a PCM line, connected to a DIU of an LTG ('outward LTG' ). Through the D900 switching network these links are routed to a dedicated LTG ('inward LTG' , may be the same as the 'outward LTG' but different LTU) that provides the connection to a LIC of the SSNC.
Both kinds of LTG are of load type 46.
Creation sequence:
• CRLTG Inward and outward LTGs have to be created and active.
• CRLTU LTU type D30 for inward and outward LTG is created.
• ENTRPDCCHR The PDC-characteristics of the INWARD LTGs have to be set to CRC4MF.
• CRLICREDG A LIC redundancy group is necessary before a LIC pair is created.
• 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.
• CRTGRP / CR TRUNK Creating trunks on the EQNs of the outward LTGs on which the links, coming from the signaling network, are connected.
• CRTGRP / CR TRUNK Creating the interworking trunks between the inward LTG and the LIC port.
• CRIWPSS7 Translating the STM connection parameters into ATM connection parameters.
• 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 p oints than interworking trunks can cause problems! New signaling links migh t not get active!
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
23
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MP:SLTSN
LTG
LTG
ASN/AMX
MP:SLT
MP:SLT
EWSDSSNC
CRSIGDLLTG (EQN - MP)
CRIWPSS7LIC-IDPort
Time slotIWP-ID
SIGN-TRUNKCR TRUNKCR TGRP
IW- TRUNKCR TRUNKCR TGRP
TS
CRLICPRTLic
PortTrafficType
STM
LIC
IWP
CRPDCLNKLTG,LICLIC.Port
TSLow Speed Link
64kb/s
Fig. 9 L1 path for links, connected via LTG
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
24
2.1.1.1 SS7 trunks at outward LTG
Before setting up the Signaling Data Link (nailed up connection), the ports required for the signaling links must be reserved by means of CRTGRP (GCOS=CCSLGRP) and CRTRUNK (LCOS=DIGSIG8) in the outward LTG.
2.1.1.2 Interworking trunks at inward LTG
The connection between D900 and SSNC is realized by one (min) or two (max) 'interworking' trunk groups, at the inward LTGs.
1. 'Interworking' trunks (IWTR) are reserved via MML commands on the inward LTG. Each IWTR is allocated to one of the two possible 'interworking' trunk groups (IWTGRP).
2. All IWTRs of one inward LTG belong to the same IWTGRP.
3. Only 2 PCM lines per LTG are used for the LIC connection. The other two PCM lines may be used for speech connections.
4. When creating the links in a linkset, these links are automatically allocated alternately to one of two existing IWTGRP. The operator only specifies the port of a link on the outward LTG and the MP:SLT on which the link should terminate. (If there are just link sets with one link only, 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.
TIP Trunks and trunk groups are still created in the D900 by MML commands.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
25
CR TGRP: TGNO=IWTG01,GCOS=IWTGRP,OPMODE=OG;
CR TRUNK: TGNO=IWTG01, LTG=0-1, LC=2-1, TRRANGE=31, LCOS=DIGSIG8;
CR PDCLNK
SNSN
LTG 0-1inward
LIC
LTG 0-2inward
LTG 0-3inward
LTG 0-4inward
ASN/AMX
ASN/AMX
IWTG01
IWTG02
MP5(SLT)
MP5(SLT)
LTG 0-5outward
LTG 0-6outward
MP 2(SM)
MP 2(SM)
MP6(SLT)
MP6(SLT)
0123
1
2
3
4
5
6
7
8
0123
0123
0123
CR IWPSS7
CR TGRP: TGNO=C7TG01,GCOS=CCSLGRP,OPMODE=IC;
CR TRUNK: TGNO=C7TG01, LTG=0-5, LC=1-31,LCOS=DIGSIG8;
0123
0123
Fig. 10 SS7- and interworking trunks (example)
Create SS7 trunk group at outward LTG
CRTGRP: TGNO=<name> ,OPMODE=IC, GCOS=CCSLGRP;
Create trunks in SS7 trunk group
CRTRUNK: TGNO=<name>, LTG=<a-b> ,LC=<LTU-TS>, LCOS=DIGSIG8, [TRRANGE= ,]BLK=NONE;
Fig. 11 Outward trunks
Create interworking trunk group at inward LTG
CRTGRP: TGNO=<name> ,OPMODE=OG, GCOS=IWTGRP;
Create trunks in interworking trunk group
CRTRUNK: TGNO=<name> ,LTG=<a-b> ,LC=<LTU-TS>, LCOS=DIGSIG8, [TRRANGE= ,]BLK=NONE;
Fig. 12 Interworking trunks
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
26
2.1.1.3 Create PDC link
The PCM lines between the LIC ports and the ports of the inward LTG (DIU) must be defined.
All ports of the inward LTGs are divided into a maximum of two groups, which make up the two interworking trunk groups 0 and 1.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
27
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create PDC link
CRPDCLNK: LIC = , LICPORT = <1...8>, LTG = <a-b>, PDCLNK = <0…3> ;
Fig. 13 PDC link between inward LTG and LIC
DISPPDCLNK:LIC=1;
DISPLAY PDCLNK DATA
LIC LICPORT LTG PDCLNK-----+---------+-------+------
1 1 0-1 2 1 2 0-1 3 1 3 0-2 2 1 4 0-2 3 1 5 0-3 0 1 6 0-3 1 1 7 0-4 0 1 8 0-4 1
Fig. 14 Display PDC-link (example)
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
28
2.1.1.4 Creation of LIC ports
Each LIC has 8 connectable ports. Depending on the connection (high speed/low speed links, direct connection or via D900), the ports must be created accordingly. In the SSNC both, E1- (2Mb/s, PCM30) and DS1-connections (1.5 Mb/s, PCM24) may be used.
CR LICPRTDS1 (for PCM 24 LIC ports)
CR LICPRTE1 (for PCM 30 LIC ports)
If the traffic type is 'STM' (for 64kb/s links), the port is created with 31 time slots of 64 kb/s each. In case of 'ATM' (for high speed links) only one object with 2 Mb/s is created on a LIC port.
The timing source for the transmitted line signal may be the SSNC internal system clock ACCG ('System Time') or may be derived from the incoming line ('Loop').
The 'E1 frame format' describes the kind of error detection method of the PCM line. 'CRC' stands for 'cyclic redundancy check' (CRC4) and will be used as default value.
If a LIC port is not created with the 'Administrative State = Unlocked', it has to be unlocked afterwards, using the task MODLICPRTE1.
TIP Since the LICs are created as a pair of one active and one redundant LIC, one must make sure, that the LIC-ports are created at the active LIC only (DISP LICREDG;). Nevertheless, the redundant LIC has to be entered too.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
29
Create LIC ports for 64kb/s links (PCM 30)
CRLICPRTE1: LIC = ,LIC port = <1...8>,Traffic type = <STM/ATM>,Redundant LIC = ,[Timing source= <System time/Loop>,][E1 frame format = CRC,][E-Bit = TRUE,][E-Bit polarity = TRUE,][National Bit = FALSE,][Admin. state= Locked/Unlocked,][Alarm profile MP= ];
Fig. 15 LIC port for PCM30 link
LIC | 1 LIC port | 5 Redundant LIC | 2Admin. state | Unlocked Operational state | EnabledAlarm status | Cleared Current problem list | Alarm profile MP | "MAJNOESC"Traffic type | STMTiming source | System timeE-bit | TRUE E-bit polarity | TRUE National bit | FALSE E1 frame format | CRC
DISP LICPRTE1:LIC=1, LIC port=5;
Fig. 16 DISP LICPRTE1 (example)
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
30
2.1.1.5 Interworking points
For every 64kb/s link, virtual connection data must be created to translate the STM connection parameters into ATM connection parameters that are used SSNC internally. Virtual connections for narrow band links (64kb/s) have to be created as interworking points (IWP).
The operator specifies only the physical location of each time slot (LIC, LIC-port, time slot) for which a virtual connection should be created and the system generates all necessary data for the ATM connection itself. Most of the ATM description data are internally predefined and don't need to be specified by the operator.
The virtual connection is identified by an interworking point number (IWP ID), which can be entered by the operator or is assigned automatically by the system. It makes sense to assign an IWP ID from which the relation between LIC-port and timeslot can be derived:
Example:
IWP ID: "a b c" 1304
LIC: a 1
LIC Port: b 3
Time Slot: c 04
The task CRIWP has to be entered once for each single timeslot on the connection between inward LTG and LIC. A parameter similar to "TRRANGE" in CRTRUNK does not exist.
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.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
31
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create interworking point for SS7
CRIWPSS7: LIC = , LIC Port =<1...8>, Time Slot =<1...31>, [IWP ID = ,] [Admin State = <Locked/Unlocked>,] [Alarm Profile MP = ];
Fig. 17 Virtual connections for 64kb/s links
DISP IWPSS7: IWP ID=1103; IWP ID | 1103 LIC | 1 LIC port | 1 Time slot | 03 Admin. state | Unlocked Operational state | Enabled Alarm status | Cleared Current problem list | Alarm profile MP | "CRITICAL"
Fig. 18 Display interworking point SS7 (example)
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
32
2.1.1.6 Create a signaling data link
Signaling Data Links form the connection between the SS7 links from the network and the MP:SLT. This involves nailed up connections, which are connected on the D900 side as STM-NUC and on the SSNC side as ATM-NUC (PVC).
Specifying both end points, i.e. network (time slot of the outward LTG) and MP sets up data links between them automatically. Depending on the kind of signaling connection (Low Speed/High Speed, direct or via EWSD to the LIC port), different tasks with different parameters have to be used.
In the CRSIGDLLTG task, the end points are defined by the time slot location of the outward LTG and the MP:SLT.
The time slots between D900 (LTG- inward port) and SSNC (LIC) are selected by the system automatically.
It is sufficient if the signaling network and the data link are identified by their given names. The identification number (ID) is then found/allocated automatically.
The parameter 'Bit inversion' indicates whether the level 1 bit stream is inverted for a signaling data link or not.
The bandwidth of the internal through connection will always be 64kb/s in case of low speed links.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
33
Create signaling data link for 64kb/s links via LTG
CRSIGDLLTG: Data link name = , [Data link ID = ,] Net name = <name>, [Net ID = ,] Adjacent DPC = <DPC of partner exchange>, MP = <no. of MP:SLT>, Outward EQN = <LTG SET, LTG, DIU, TS>, [Transmission rate = 64 kBit,] [Bit inversion = No Inversion];
Fig. 19 Signaling data link for low speed links via LTG
DISPSIGDLLTG:Net ID=1;
Net name | Data link | Data | MP | LIC Port | I nward 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 | | | | | | DI U ID | 2 | DIU ID | 1 | | | | | | ST M 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 | | | | | | DI U ID | 0 | DIU ID | 3 | | | | | | STM channel | 23 | STM channel | 17 |
DISPSIGDLLTG:Net ID=1,Data link ID=1;
Net name | “TELECOM1" Net ID | 1Data link name | “DL1T-Munich" Data link ID | 1Adjacent DPC | 2-2-2-2 MP | 5 LIC Port | LIC = 1
| LIC port = 1 Inward EQN | LTG SET | 0
| LTG ID | 1| DIU ID | 2 | STM channel | 7
SN Info | .Outward EQN | LTG SET | 0
| LTG ID | 5| DIU ID | 1 | STM channel | 16
Interworking point ref. | -Operational state | EnabledTransmission rate | 64 kBitBit inversion | No inversion Used | TRUE
Fig. 20 Display of a signaling data link LTG (example)
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
34
2.1.2 Signaling links directly connected to a LIC
In opposite to the CCNC, a PCM line with signaling links may also be connected to the SSNC directly without an LTG. In that case, each timeslot of the PCM represents one 64kb/s signaling link.
Since no trunk groups and no trunks are needed here, the necessary database is simpler than in the case described before.
Creation sequence:
• CRLICREDG A LIC redundancy group is necessary before a LIC pair is created.
• 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.
• CRSIGDLLIC Nailed up connection between a timeslot of the SS7-PCM and an MP:SLT.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
35
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MP:SLT
ASN/AMX
TS
MP:SLT
MP:SLT
SSNC
Low Speed Link64kb/s
CRSIGDLLIC (IWP - MP)
CRIWPSS7LIC-IDPort
Time slotIWP-ID
CRLICPRTLIC-ID
PortTrafficType
LIC
STM
Fig. 21 L1 path for links, directly connected to SSNC
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
36
2.1.2.1 Creation of LIC ports
Each LIC has 8 connectable ports. Depending on the connection (high speed/low speed links, direct connection or via D900), the ports must be created accordingly. In the SSNC both, E1- (2Mb/s, PCM30) and DS1-connections (1.5 Mb/s, PCM24) may be used.
TIP The LIC ports have to be created in the same manner as for low speed links, connected via LTG, described before:
2.1.2.2 Interworking points
For every 64kb/s link, virtual connection data must be created to translate the STM connection parameters into ATM connection parameters that are used SSNC internally. Virtual connections for narrow band links (64kb/s) have to be created as interworking points (IWP).
TIP The interworking points have to be created in the same manner as for low speed links connected via LTG and described before.
2.1.2.3 Create a signaling data link
Signaling Data Links form the connection between the SS7 links from the network and the MP:SLT. This involves nailed up connections, which are connected on the D900 side as STM-NUC and on the SSNC side as ATM-NUC (PVC).
In the CRSIGDLLIC task, the endpoints are defined by the interworking point (i.e. the LIC-port, defined in CRIWPSS7) and the MP:SLT.
It is sufficient if the signaling network and the data link are identified by their given names. The identification number (ID) is then found/allocated automatically.
The parameter 'Bit inversion' indicates whether the level 1 bit stream is inverted for a signaling data link or not.
The bandwidth of the internal through connection will always be 64kBit in case of low speed links.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
37
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create signaling data link for 64kb/s links
CRSIGDLLIC: Data link name = , [Data link ID = ,] [Net name = <name>,] [Net ID = ,] Adjacent DPC = <DPC of partner exchange>, MP = <no. of MP:SLT>, Interworking point ref. = , [Transmission rate = 64 kBit,] [Bit inversion = No inversion];
Fig. 22 Signaling data link for low speed links, directly connected to a LIC port
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
38
2.1.3 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. The bandwidth of the high-speed connection is fixed to the bandwidth of the physical carrier (2Mbit/sec for PCM30).
2.1.3.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). User information, as e.g. signaling messages, is divided into portions of 48 byte, packed into the cells and sent through the ATM network light freight in a container on a truck.
ATM divides each physical transmission into logical connections (virtual connections ) that are assigned to the services that require transportation. Such a virtual connection consists of a virtual path (similar to a TGRP), an administrative group of one or more virtual channels (similar to a trunk in a TGRP). The information, to which virtual connection a specific cell belongs, is contained in the header of each cell as virtual path identifier (VPI) and virtual channel identifier (VCI).
The different tasks like packing the user information into the payload of an ATM cell and inserting these cells into the continuous cell-stream, are described by a four-layer ATM model:
• The higher layers (layer 4) represent the users that provide information to be transmitted.
• The ATM Adaptation Layer AAL (layer 3) is responsible for segmentation, i.e. cutting the user information into portions that fit into the ATM cells and stuff them with security information because ATM does not care for the error free transmission of the payload inside the cells.
• The ATM Layer (layer 2) forms the ATM cells by adding header information like VPI and VCI to each payload.
• 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.
TIP VPI, 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.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
39
SIEMENS
SIEMENS SIEMENS
SIEMENS
SIEMENS SIEMENS
D900
SSNC
D900
SSNCATM High Speed Link
Virtual Connection
Virtual Path
Virtual Channels
Fig. 23 ATM virtual connection
Higher Layer
ATM Adaptation Layer
ATM Layer
Physical Layer
PAYLOAD
PAYLOAD
PAYLOAD PAYLOADTransmission Convergence
Sublayer
Physical Medium Sublayer
Fig. 24 ATM layers
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
40
2.1.3.2 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.
The task CRTCSSUBL creates this sublayer for a given LIC port. It returns a TCS Id that has to be entered when creating VPI and VCI afterwards.
Cell scrambling is an option that scrambles/descrambles the content of ATM cells according to a given, fixed algorithm.
2.1.3.3 Virtual path
The task CRVPATH defines the virtual path identifier of an ATM connection. The chosen VPI value entered here will be present in the header of the corresponding ATM cells. It must be equal at both sides of a virtual path.
The TCS Id to be entered is the one, given by the previous command.
2.1.3.4 Virtual channel
The task CRVCHAN creates a virtual channel within the previously created virtual path. This virtual channel may be used by a signaling data link to connect a high speed-signaling link. The VCI must be equal at both sides of a virtual channel.
This task returns a VC TTP ID that has to be entered as "Virtual channel" when creating the signaling data link.
2.1.3.5 Signaling data link for high-speed links
High-speed connections in this context are always 2 Mb/s ATM connections. The data link connection is a switch from a virtual ATM connection (VC TTP ID) to an MP:SLT. The LIC port must be set up as an ATM port accordingly (Traffic type = ATM).
The logical ATM connection was created with the tasks described above. Using the command CRSIGDLHS, a "permanent virtual connection“ PVC is set up between the created virtual channel and the specified MP.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
41
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create Transmission Control Sublayer
CRTCSUBL: LIC = <no.>, LIC port = <1…8>, Alarm profile MP = , Cell scrambling enable = <TRUE, FALSE>;
Create Virtual Path
CRVPATH: TCS id = <output of CRTCSUBL>, VPI = , Alarm profile MP = , Admin state = <locked, unlocked>;
Create Virtual Channel
CRVCHAN: TCS id = <output of CRTCSUBL>, VPI = , VCI = , Admin state = <locked, unlocked>;
Create Signaling Data Link for ATM High Speed Links
CRSIGDLHS: Net name = <name> [Net ID = ,] Data link name = <name>; [Data link ID = <1…1500>,] Adjacent DPC = DPC of partner exchange>, MP = <no. of MP:SLT> , Virtual channel = <output of CRVCHAN>;
Fig. 25 Q3 tasks
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
42
2.1.4 SS7 high speed link (STM)
In cases where links with high data rates are required, but the ATM standard is not desired, the SS7 High Speed Links (HSL) offer a possibility to connect a 1,5 or 2Mb/s signaling connection, based on STM technology, directly to a LIC-port.
For this purpose all timeslots of a PCM carrier (PCM 24/30), and thus of a LIC port, are bundled, thus representing the mentioned, high data rates for one single link.
The new data rates are transparent to the higher layers of CCS7; adaptation is done on layer 2 level only.
TIP This is NOT the ATM link that may be connected to an ATM port of a LIC, offering similar data rates!
WARNING Although the software to realize SS7 HSL with 1,5 M b/s over a PCM 24 line is available and administration is possible, this soft ware is neither tested nor released for the world market. If requested, this s oftware has to be tested and released for the concerned project.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
43
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MP/SM
LTG
LTG
MP/SLT
LIC
LIC
SC
ASN
SN
CP113
SSNC
MB D
LTG
LTG
SS7-Links 64 kbit/s
SS7-Links 64 kbit/s,
MP/STAT
MP/OAM
LIC
SS7-Links ATM
SS7 High Speed Links1,5 / 2Mb/s STM
Fig. 26 Connection possibilities for SS7 links to SSNC
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
44
2.1.4.1 Differences to narrow-band links
The only differences between a 64kb/s link and the new 1,5/2Mb/s HSL are, apart from the transmission rate, the length of some fields in the MSU header and the applied error rate monitoring method.
Signal unit format
When link data rates of 1.5 Mb/s and 2.0 Mb/s are used, the format of the sequence numbers changes from 7 bits to 12 bits. In this case, the forward sequence number FSN and backward sequence number BSN are in binary code from a cyclic sequence from 0 to 4095.
If the extended sequence number format as described above is used, the length indicator format changes from 6 to 9 bit.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
45
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FBSNBIB
FSNFIB
SIOSIFCKF LI
812
112
19
28273>n>2 bytes168 776
FBSNBIB
FSNFIB
SFCKF LI
812
112
19
28 or 16168 776
FBSNBIB
FSNFIB
CKF LI
812
112
19
2168 776
MSU-formatfor SS7 HSL:
LSSU-formatfor SS7 HSL:
FISU-formatfor SS7 HSL:
Fig. 27 Adapted SU formats for SS7 HSL
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
46
2.1.4.2 Administration of SS7 HSL
The administration of SS7 HSL is very similar to the administration of narrowband links. But: HSL must not be connected via LTG.
Two new Q3 tasks are available for HSL and the layer-2 profile of these links must be selected according to their transmission rate and network type.
CR HSIWPSS7
'Create high speed interworking point' is very much like creating a narrow band IWP. Difference to CR IWP, which is used for LIC NB links: no parameter "Time Slot" because not a single timeslot is carrying the signaling information but the whole PCM line. Thus all ts of a LIC port are grouped together to form one interworking point.
CR SIGDLLIC
Difference to CR SIGDLLIC, which is used for narrow band links: parameter "Transmission rate” supports 2Mb/s (and 1,5Mb/s but not released).
CR SIGLINK - DISP MTPL2PF
The layer-2 profile for high-speed links acc. ITU Q703 is predefined in the SSNC and does not need to be defined manually. Nevertheless, it has to be entered in the link-definition (parameter: 'Profile name').
Depending on the network type, ITU or ANSI, and the applied error correction method, four different profiles are available:
• ITU BAS2.0_H: ITU network, basic error correction, 2Mbit/s, high-speed link
• ITU PCR2.0_H: ITU network, preventive cyclic retransmission, 2Mbit/s, high-speed link
• ANS BAS2.0_H: ANSI network, basic error correction, 2Mbit/s, high-speed link
• ANS PCR2.0_H: ANSI network, preventive cyclic retransmission, 2Mbit/s, high-speed link
Create interworking point for SS7 high speed links
CRHSIWPSS7: LIC = , LIC Port =<1...8>, [IWP ID = ,] [Admin State = <Locked/Unlocked>,] [Alarm Profile MP = ];
Fig. 28 Q3 task to create interworking point for HSL
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
47
Create signaling data link for high speed links
CRSIGDLLIC: Data link name = , [Data link ID = ,] Net name = <name>, [Net ID = ,] Adjacent DPC = <DPC of partner exchange>, MP = <no. of MP:SLT>, Interworking point ref. = , [Transmission rate = <1984 kb/s, 1536 kb/s>,] [Bit inversion = No Inverse];
Create signaling link for high speed links
CRSIGLINK: Data link ID = , Net ID = , Link set name = Link code = , Protocol profile name = … ;
Fig. 29 Q3 task to create a signaling data link for HSL
DISPMTPL2PF;
L2 profile name | L2 profile ID
=============================================
::
---------------------------------------------
"ITU BAS2.0_H" | 65
---------------------------------------------
"ITU PCR2.0_H" | 66
---------------------------------------------
"ANS BAS1.5_H" | 67
---------------------------------------------
"ANS PCR1.5_H" | 68
---------------------------------------------
"ANS BAS2.0_H" | 69
---------------------------------------------
"ANS PCR2.0_H" | 70
---------------------------------------------
"ITU BAS1.5_H" | 71
---------------------------------------------
"ITU PCR1.5_H" | 72
Can‘t be used because feature is not released for 1.5 Mbit/s
Fig. 30 MTP layer 2 profiles
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
48
2.1.4.3 Required hardware
The MPs to which the SS7 HSL are connected via a signaling data link must have a MPUE+ as processing units. MPUD will not work.
The MPUE+ has a modified ASIC 'ATM230 V2.4' on board to offer the 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).
• 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.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
49
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
50
2.2 Level 3 objects
A signaling network consisting of
• signaling points
• signaling links
• signaling link sets
• signaling routes
and must be created by the operator via Q3 tasks in the SSNC.
With the aid of the appropriate database, the MTP is then able to carry out its tasks.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
51
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Destination Point
Originating Point
Signaling Point (STP or SRP)
1...
1631
...
1... 16
31...
Circuit relatedor non circuit
relatedsignaling
information
Signalinglinks
Signaling links
Signaling link set
1... 16
31...
Signalinglink set
SIEMENS D 900 SIEMENS D 900
SIEMENS D 900 SIEMENS D 900
SIEMENS D 900 SIEMENS D 900
SIEMENS D 900 SIEMENS D 900
Signaling Point (STP or SRP)
Signalingroute
CRSIGROUTE
CRSIGLINK
CRSIGLSET
CRSIGDPCRSIGDP
CRSIGPOINT
Fig. 31 Signaling network
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
52
2.2.1 Own signaling point code
Every signaling point must have an own signaling address, consisting of SPC and network indicator that is unique in the signaling networks this node belongs to. Depending on the project specific structure, this SPC has to be entered as a decimal value or structured (see chapter "Introduction to CCS7"). Furthermore, it must be defined how the SP shall handle signaling- and status messages (TFA, TFP).
Due to the feature 'Multiple SS7 Networks', up to 32 different signaling networks can be handled by a single SSNC. Thus, an own signaling address must be assigned for each of the handled networks. It is sufficient to specify their 'Net Name', the 'NetID' will be assigned automatically.
If a different MSU length than 272 octets is required, the parameter 'Supported data length' has to be set accordingly.
The 'Signaling point type' determines the usage of the own SP:
STP Signaling point functions purely as a signaling transfer point, i.e. level 4 of CCS7 will not be used to evaluate the message, not even SCCP for GTT.
SEP Signaling point functions purely as signaling end point, i.e. it can distribute a received message to its own users only. Should the routing label of an MSU indicate that a transfer to another signaling point is required, the message is discarded and the discarded-message counter is incremented.
STEP Signaling point functions as signaling transfer point and signaling end point.
In case the own node is a standalone signaling relay point with GTT, it has to be set up as STEP.
The parameter 'TFP TFA broadcast' determines, whether a received TFA-/TFP message shall be broadcasted to no, all, or just a limited number of neighboring signaling points.
'TFR compatibility' determines where message rerouting will be done in case a TFR-msg from an STP is received.
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.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
53
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create own signaling point
CRSIGPOINT: Net Name = <name>,[Net ID = <1...32>,]Net Indicator = <Nat0/1 Inat0/1>,SPC = ,Signal. point type = <SEP/STP/STEP>,TFP TFA broadcast=<YES/NO/Restricted> ,TFR compatibility= ,[Supported data length= length272,][Alarm profile MP = ,].... ;
Fig. 32 Own signaling point
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
54
The opposite page shows typical signaling point data. Apart from the parameters mentioned, many others are shown, mainly timer values and parameters, indicating how to handle transfer allowed- and transfer prohibited messages.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
55
DISP SIGPOINT
Net name | "TELECOM1" Net ID | 1 Net indicator | National network 0 SPC | 1-1-1-1 SPC structure | No. of bit | Component | Component | s | minimum | maximum | ====================================== | 4 | 0 | 15 | -------------------------------------- | 3 | 0 | 7 | -------------------------------------- | 4 | 0 | 15 | -------------------------------------- | 3 | 0 | 7 Operational state | Enabled Alarm status | Cleared Alarm Profile MP | "CRITICAL" RST after conf DP | FALSE TFP for unknown DP | TRUE MTP restart | Off TFR compatibility | TRUE Ni screening | Activated TFP TFA broadcast | Yes Signaling point type | STEP TFC sampling rate | 8 Number of TFA | 100 Number of TFP | 100 TFA interval | 600 TFP interval | 600 Supported data length | Length 272 TUP | - Send UCIC indicator | FALSE LPO control bit | TRUE ITU-Timers Q704 timer T1 | 1000 Q704 timer T2 | 2000 Q704 timer T3 | 1000 Q704 timer T4 | 1000 Q704 timer T5 | 1000 Q704 timer T6 | 1000 Q704 timer T7 | 1000 Q704 timer T8 | 1100 Q704 timer T10 | 40000 Q704 timer T11 | 60000 Q704 timer T12 | 1500 Q704 timer T13 | 1500 Q704 timer T14 | 3000 Q704 timer T15 | 2000 Q704 timer T16 | 1400 Q704 timer T17 | 1500 Q704 timer T18 | 30000 Q704 timer T19 | 68000 Q704 timer T20 | 60000 Q704 timer T21 | 64000 Q704 timer T22 | 190000 Q704 timer T23 | 190000 Q704 timer T24 | 500 Q707 timer T1 | 12000 Q707 timer T2 | 90000
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
56
2.2.2 Signaling destination point
In every signaling point of a network, all other signaling points of the same signaling network, to which messages can be sent and received respectively, must be created as destination points. Destination points are uniquely identified by a signaling network 'Net Name/ID' and an SPC, which has to be unambiguous in that signaling network. Depending on the project specific structure, this DPC has to be entered as a decimal value or structured (see chapter "Introduction to CCS7").
The destination points can be reached from the own signaling point either via a direct signaling link set (i.e. destination point is adjacent) or via one or more intermediate signaling points, so called signaling transfer points.
A loadsharing key defines, how the signaling messages towards that destination point are offered to the possible linksets.
All linksets, leading to one other signaling point of the own network are known as signaling routes. Loadsharing can be set for the first two active linksets of a signaling route at most. Loadsharing is only effective if at least two linksets are created for the same destination, which are entered in the routing table with the same priority using 'CR SIGROUTE' (see below).
Loadsharing is carried out by evaluation of one of the SLS-bits (Signaling Link Selection), found in the routing label of each MSU. The operator determines the bit by entering a 'Loadsharing key' between 0 and 4:
Loadsharing key =
Loadsharing algorithm
none 0 No loadsharing. All MSUs are offered to the linkset with the highest priority
SLS1...SLS4 Loadsharing between the first two linksets having the same highest priority
LSK = SLS1...SLS4 defines a bit position within the SLS field of an MSU. A binary '0' at this position routes the MSU to the first linkset, a binary '1' routes it to the second linkset.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
57
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create signaling destination point
CRSIGDP: DPC = , DPC Name = , Net Name = , [Net ID = ,] [Loadsharing key = ,] [Alarm profile MP = ,] [Alarm smoothing time = ];
Fig. 33 Signaling destination point
LSK = Bitposition inSLS field
Selected linkset fromsignaling route
none 0 XXXX first LS with highest priority
SLS1 XXX0XXX1
first LS with highest prioritysecond LS with highest priority
SLS2 XX0XXX1X
first LS with highest prioritysecond LS with highest priority
SLS3 X0XXX1XX
first LS with highest prioritysecond LS with highest priority
SLS4 0XXX1XXX
first LS with highest prioritysecond LS with highest priority
Fig. 34 Loadsharing between linksets towards a destination point
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
58
By means of the task MOD SIGDP, the administrative state of a destination point has to be set to 'UNLOCKED' before it can be reached. As a prerequisite at least one signaling linkset must be contained in the signaling route, leading to that destination point.
The administrative state attribute describes whether it is administratively permitted to route SS7 MSUs towards the respective destination point. The possible values supported in the NE are ’LOCKED' and ’UNLOCKED’.
The operational state attribute describes whether the respective destination signaling point is accessible (ENABLED) or not (DISABLED). If the operational states of all signaling linksets leading to the signaling destination point are ’DISABLED’, 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 operational state is 'DISABLED'.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
59
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify signaling destination point
MODSIGDP: [DPC = ,] [DPC name = ,] [Net Name = ,] [Net ID = ,] [Admin. state = <Locked / Unlocked>,] [Loadsharing key = ,] [Alarm smoothing time = ];
Fig. 35 Administrative state change
Net name |Net|DPC name | DPC | Admin. | Opera | Lo ad | Alarm | Alarm |Alarm | Extended|Con |Con | US| | | | | state | key | | MP |thing | problem |gested |gested| routing | | | | | | | time | list | | |stat e |level |
=================================================== =================================================== ========================"TELECOM1" |1 |“Munich" |2-2-2-2| Unlocked| Enable d | "sls 0" |Cleared |"MAJNOESC"| 0 | { } |Not | - |
| | | | | | | | | | |Congested| | --------------------------------------------------- --------------------------------------------------- ----------------------
"TELECOM1" |1 |“Berlin" |4-4-4-4| Unlocked| Enable d | "sls 0" |Cleared |"MAJNOESC | 0 | { } |Not | - | | | | | | | | | | | |Congested| |
--------------------------------------------------- --------------------------------------------------- ------------------------"TELECOM1" |1 |“Hamburg"|3-3-3-3| Unlocked| Enable d | "sls 3" |Cleared |"MAJNOESC | 0 | { } |Not | - |
| | | | | | | | | | |Congested| |
DISP SIGDP:Net ID =1;
Fig. 36 Signaling destination point
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
60
2.2.3 Signaling link set
A signaling link set, consisting of up to 16 links, 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. Only one link set can be created between two adjacent signaling points that are specified via their SPC and Network Name/ID. Regardless of this, the same neighbor signaling point may also be reached via other, not directly running Linksets, grouped together in a signaling route (see below).
The 'max MSU length' defines the maximum length for message signal units. At creation of a Linkset the maximum MSU length can be given as part of the Linkset specific data. The maximum MSU length can be modified to a different value up to the default value of 272 octets.
'Congestion method' reflects the control method within a signaling network, i.e. it defines the reaction upon signaling network congestion. In networks with 14 or 24 bit SPCs 'International' is the only allowed value.
Loadsharing between the links of one Linkset is hard coded (SR9) and can't be modified. The MSUs are offered equally to all links in the Linkset.
Since SR10, the Load share algorithm can be set to a value between 0 and 15.
In ITU networks, the only allowed value for Link set type is F-link (CCS7 links).
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
61
SP
100
SP
300
SP
400
Signaling link set X :Group of up to 16 signaling linksto one adjacent signaling point
STP200
Signaling link set Y
Fig. 37 Signaling link sets
Create signaling link set
CRSIGLSET: Link set name = , [Link set ID = ,] Adjacent DPC = , [Net name = ,] [Net ID = <1...32>,] [Periodic link set test = ,] [Alarm profile MP = ,] Congestion method = International, [Alarm smoothing time = ,] [Load share algorithm = ,] [Link set type = F-link,] [Virtual SLS = ,] [MTP restart = ,] [Maximum MSU length = ];
Fig. 38 Creation of a signaling link set
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
62
If the 'Periodic link set test' parameter is set to ON, a link test of the links allocated to the link set is carried out every 90 seconds. The test checks the L2 functions and corrects MSU transfer between two adjacent SPs.
Testing and maintenance sends a Signaling Link Test Message (SLTM) to the adjacent MTP, which includes a test pattern. The partner responds with a Signaling Link Test Acknowledgement (SLTA) containing the reflected test pattern.
The following data are checked during the test:
1. the Signaling Link Code (SLC, must be the same at both sides of a link)
2. the OPC (SLTM-DPC = SLTA-OPC)
3. the test pattern (which is merely looped back in the acknowledgement)
The test is positive only if the link status is "enabled".
General principles on linkset state information:
• The states of a signaling link set can only be displayed.
• Activation and deactivation of a linkset may be done via operations on the links.
Operational state: It is ’ENABLED’ when at least one link of the signaling link set is enabled. Otherwise it is ’DISABLED’.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
63
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SP A
1) Testing of A-Side2) Testing of B-Side
SP BSLTM
SLTA
SLTM
SLTA
1
2
SLTM: Signaling Link Test MessageSLTA: Signaling Link Test Acknowledge
Fig. 39 Periodic link test
DISPSIGLSET:Link set name=C7LSRNC1;
Net name | "NAT0"Net ID | 3 Link set name | "C7LSRNC1" Link set ID | 50Adjacent DPC | bit14 : 769 Operational state | Disabled Periodic link set test | O ff Alarm status | Major Alarm profile MP | "MAJNOESC" Alarm smoothing time | 60 Max.MSU length | 272 VMS | Off Congestion method | International
Fig. 40 Signaling link set
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
64
2.2.4 Signaling routes
Every signaling destination point may be reached by a maximum of eight signaling linksets. These linksets are called signaling routes and have to be defined with the task CR SIGROUTE.
The loadsharing between all signaling routes, leading to the same signaling destination point is determined by the 'Priority', assigned to the single routes (1=highest and 8=lowest priority). Loadsharing can take place between two linksets, leading to the same DPC, at most; both must have the same priority assigned and the 'Priority mode' must be 'Equal'.
If one of several linksets, having the same priority, fails and there is still an additional linkset with the same priority existing, loadsharing will continue. Only if all linkset of one priority fail a switch over will take place to a linkset with the next lower priority.
In the example on the opposite page, three cases are shown from point of view of 'A':
• towards DPC = B, loadsharing takes place between linksets LS_B and LS_C.
• towards DPC = C, loadsharing takes place between the linksets LS_B and LS_D only, if linkset LS_C fails.
• towards DPC = D, no loadsharing is possible.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
65
SPCC
SPCB
SPCA
SPCD
CR SIGLSET
LS_B
LS_C
LS_D
CR SIGROUTE
DPC = B: Prio1: LS_BPrio1: LS_CPrio2: LS_D
DPC = C: Prio1: LS_CPrio2: LS_BPrio2: LS_D
DPC = D: Prio1: LS_DPrio2: LS_C
Fig. 41 Signaling routes
Create signaling routes
CRSIGROUTE: Net name = ,[Net ID = ,]DPC = ,[DPC name = ,]Link set name = ,Priority = ,[Route ID = ,][Priority mode = Equal];
Fig. 42 Creation of signaling routes
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
66
2.2.5 Signaling links
A signaling link is part of a link set and can be uniquely identified by a link code (0...15), which must be the same value at both ends of a link. A maximum of 16 links may be created in one signaling linkset.
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. The corresponding signaling data link must have been created before with CR SIGDLLTG/LIC/HS (see ch. 2.1).
When allocating SIGLINK- SIGDL(LTG,LIC,HS), care should be taken that the signal channels of one linkset are distributed to two MP. In this way it is ensured, that if one MP (both MPU) fails, this does not result in the failure of a complete signaling relation.
The signaling link is assigned certain characteristics such as transmission rate, the communications protocol, necessary timer and correction procedure by means of a 'Profile name'. If the standard profiles are not sufficient (they will be sufficient in 99,9% of all cases), additional profiles may be created by CRMTPL2PRF.
The most commonly used profiles are
• ITU BASIC64 transmission rate: 64 kb/s, basic error correction, PCM30, world market version
• ANSI BASIC64 transmission rate: 64 kb/s, basic error correction, PCM24, US version
Before a signaling link can be seized, the administrative state must be set to 'UNLOCKED' by the task MODSGLINK.
Create signaling link
CRSIGLINK: Net name = ,[Net ID = ,]Link set name = ,[Link set ID = ,]Link code = ,Data link name = ,Protocol Profile name = ,.... ;
Fig. 43 Creation of a signaling link
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
67
DISPSIGLINK:Display names=Yes, Link set name=C7LSRNC1 ;
Nr. | Net name | Net ID | Link set name | Link set | Lin k code | Admin. sta | Operational || | | | ID | | te | state || | | | | | | |
=================================================== ===================================================1 | "NAT0" | 3 | "C7LSRNC1" | 50 | 0 | Unlocked | Disabled |
Data link | Data link name | Protocol profi | Bandwidth | VM S ID | | le name | identifier |
| | | | =================================================== ===============50 | "C7LSRNC1" | "ITU64" | Broadb and | Off
Fig. 44 Signaling link
L2 profile name | "ITU BASIC64" L2 profile ID | 1 Transmission rate | 64 kBit Correction Method | Basic L2 timer T1 [ms] | 45000 L2 timer T2 [ms] | 25000 L2 timer T3 [ms] | 1500 L2 timer T4E [ms] | 500 L2 timer T4N [ms] | 8200 L2 timer T5 [ms] | 100 L2 timer T6 [ms] | 4500 L2 timer T7 [ms] | 1000Trm.cong.onset L1 | {
| messages 100,| octets 2000| }
Trm.cong.abatement L1 | { | messages 15, | octets 300 | }
Max.MSU for retrm. | 127 Max.oct.for retrm. | 300
DISP MTPL2PF:L2 Profile name=ITU BASIC64;
Fig. 45 MTP layer 2 profile "ITU BASIC 64"
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
68
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
69
3 User parts
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
70
3.1 Overview
The user parts are those parts of the signaling software that make use of the message transfer part. 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, addressing and address conversion of non-traffic channel orientated signaling.
With the help of the MML command CRC7USER, the MTP users ISUP and TUP are allocated to a destination point code and a network indicator. These allocations must be set up to all known DPCs to which traffic channel related signaling messages are sent (i.e. to which trunks are seized).
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.
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 BSSAP uses the SCCP "with logical signaling connections" (connection oriented) and can therefore do without the TCAP.
The mobile application parts MAPHLR, MAPVLR, MAPMSC, MAPEIR and the INAP or CAP (so-called SCCP USER) use the TCAP for message control, i.e. the SCCP is used here "without logical signaling connections" (connectionless). 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, MAPVLR etc.). These subsystems are addressed by means of subsystem numbers; the subsystem numbers are, as a rule, GSM (or 3GPP) standardized. National applications with national subsystem numbers may also exist, though.
A distinction must be made here between:
• Local subsystems (SCCP Access Point local) must be created for each local user in each network node.
• Remote subsystems (SCCP Access Point remote). For every destination point to which an SCCP message is signaled directly, the remote subsystem must be created in the own node in accordance with the function of the respective network node.
Each subsystem identifies itself by an SCCP calling party address, which may be included in the SCCP part of a signaling message for rerouting of the answer.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
71
MTP
SCCP
TCAP
MAPHLR
6
SCCP Linkage Local(CRSPLNKLOC)SCCP Linkage Remote(CRSPLNKREM)
SCCP Access Point Local(CRSPAPLOC)SCCP Access Point Remote(CRSPAPREM)
SCCP Subsystem Number(CRSPSSN)
SCCP Calling Party Address(CRSPCLGPA)
MAPVLR
7
MAPMSC
8
BSSAP254
CAP146
ISUPTUP
TUP+
CCS7 User(CRC7USER)
. . . MAPEIC
9
Fig. 46 Creation of user parts
Create CCS7 User ISUP and TUP
CRC7USER: USNAME = <ISUP / SCCP>, DPC = , NETNAME = ,…;
Fig. 47 Creation of MTP users ISUP and TUP
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
72
3.2 Administration of the SCCP and its user parts
Creation sequence:
• CR SPLNKLOC Stores data about the SCCP in the own node.
• CR SPSSN Linking a subsystem name with a subsystem number
• CR SPAPLOC Announces the local SCCP subsystems.
• CR SPCLGPA Creates a global title address for a local SCCP subsystem.
• CR SPLNKREM Creates a link to an SCCP in a remote signaling node, with which SCCP messages are exchanged.
• CR SPAPREM Announces the SCCP subsystems in the other signaling nodes, with which MAP-messages are exchanged.
TIP This sequence is not the one-and-only possible sequence, but it is tested and makes sense. First create all LOCAL objects, then all REMOTE objects.
3.2.1 Creation of a local SCCP linkage
This task stores data about the specific capabilities of the own SCCP, such as the supported global title format, the possibility of segmentation or the supported protocol classes for connection oriented and connectionless communication. Since the own signaling address is well known, only the signaling network on that the SCCP will send and receive messages has to be entered. In mobile networks, usually global titles of type 4 are used and extended UDT messages are in use, thus segmentation of messages is allowed.
WARNING Do not set the parameter Extd. Unit Data Req. to Tr ue, because this will force the system to ALWAYS use this type of message and t his may lead to a malfunction in the network! Additionally, a lower v alue than 255 for the Upper Limit Segment makes no sense (waste of signaling ca pacity).
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
73
Create local SCCP linkage
CRSPLNKLOC: SPLNKLOC name = , [SPLNKLOC ID = ], Net name = , [Net ID = <1...32>,] [GT Format = GT Type 4,] [Extd. Unit Data Req. = FALSE,] [Segm. Reass. Flag = TRUE,] [Upper Limit Segment = 255,] [SCL Prot Classes = class0-class1,] [SCO Prot Classes = class2-class3,] ... ;
Fig. 48 Creation of a local SCCP linkage
DISP SPLNKLOC------------------------------------------------------------------------------------------------------------------SPLNKLOC Identification | Congestion Timer Data | Globle Title | Operat. 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. | Extended Unit Data | Segmentation Limits | Flags | Subsystems--------------------|--------------------|---------------------|---------------------------|--------------ID | Name | Required | Lower | Upper | Screening | Segm. & Reass.| Allowed
==========================================================================================================1 | localN0DTAG | TRUE | 150 | 150 | TRUE | TRUE | 11
| | | | | | |
Fig. 49 Local- and remote SCCP linkage example
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
74
3.2.2 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. Project specific applications with project specific subsystem numbers are also possible (e.g. SSID=INAP, SSN=241).
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.
Some typical applications, running via these subsystems are:
• MAP HLR: Inserting subscriber data into a VLR during a location update.
• MAP VLR: Requesting a location update.
• MAP MSC: Starts the MTC interrogation when an MSISDN of the own PLMN was received.
• ISDN Supplementary Services: Generates a CCBS request.
• IN Application in SSP 2 (CAP): Starts an IN-dialog for subscriber, having an IN-service according to the CAMEL standard.
• IN Application in SSP 3 (SINAP): Starts an IN-dialog for subscriber, having an IN-service according to the Siemens specific IN standard.
• GSM Service Control Function: Forms the interface between HLR and service control point at the SCP-side.
• Serving GPRS Support Node: Forms the interface between HLR and SGSN for GPRS location updates.
• BS System Appl Part: Responsible for communication with the BSC, e.g. to start paging for a mobile station.
• Radio Access Network Application Part (RANAP) Used for UMTS applications, controlling the communication between the U-MSC and the RNC.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
75
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. Services 11 GSM
Radio Access Netw. Appl. 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. 50 Subsystem ID vs. subsystem number
Create SCCP subsystem number
CRSPSSN: SPSS name = ,SPLNKLOC name = ,[SPLNKLOC id = ,]SSID = ,SSN = ;
Fig. 51 SCCP subsystem number
DISPSPSSN;
SPLNKLOC Id | SPLNKLOC Name | SSN | SPSSN Name | SSID =========================================================================================803 | sccpLi_NAT0 | 6 | ------------ | Mobile Application Part HLR
-----------------------------------------------------------------------------------------803 | sccpLi_NAT0 | 7 | ------------ | Mobile Application Part VLR
-----------------------------------------------------------------------------------------803 | sccpLi_NAT0 | 8 | ------------ | Mobile Application Part MSC
-----------------------------------------------------------------------------------------803 | sccpLi_NAT0 | 9 | ------------ | Mobile Application Part EIR
-----------------------------------------------------------------------------------------803 | sccpLi_NAT0 | 142 | ------------ | Radio Access Netw. Appl.
-----------------------------------------------------------------------------------------803 | sccpLi_NAT0 | 149 | ------------ | Serving GPRS Support Node
-----------------------------------------------------------------------------------------803 | sccpLi_NAT0 | 254 | ------------ | BS System Application Part
-----------------------------------------------------------------------------------------805 | sccpLi_INAT0 | 142 | ------------ | Radio Access Netw. Appl.
-----------------------------------------------------------------------------------------805 | sccpLi_INAT0 | 254 | ------------ | BS System Application Part
Fig. 52 SCCP subsystem numbers, example
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
76
3.2.3 Local SCCP access point
This command creates the subsystem control data for the own (local) signaling point. 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.g. for the MAPHLR in an HLR). It tells the own node, which subsystems may be used to initiate a communication.
Example:
In an MSC/VLR, at least the subsystems MAPMSC, MAPVLR and BSSAP must be created as local SCCP access points. Should the MSC be able to handle CCBS-requests (completion of calls to busy subscriber), the subsystem ISS (ISDN supplementary services) must also be installed as a local access point. If an EIR is used in the network, the MAPEIC has to be installed as local access point as well. The MAPHLR that is addressed for interrogations will only be a remote SCCP access point, since it is the MAPMSC that starts this communication.
The ISDN User Part ISUP must not be created as SCCP access point since it is no SCCP user.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
77
HLR
EIR
MSC / VLR
MAPMSC
MAPVLR
MAPEIC
BSSAP
TCAP
SCCP
MTP
Fig. 53 Local SCCP access points, example
Create local SCCP access point
CRSPAPLOC: SPAPLOC name = ,[SPAPLOC id = ,]SSID = <name>,SSN = <number as in CRSPSSN>,... ;
Fig. 54 Local SCCP access point, creation
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
78
3.2.4 SCCP calling party address
If an SCCP message is sent, the corresponding calling party address must also be entered. The SCCP calling party address has to be defined for each local subsystem. 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.
A calling party address field may contain a global title – e.g., for international signaling. A global title is not required in an SCCP calling party address for network internal signaling. 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. Even if the setting of 'CLGPA Type Indicator' is Programmed, 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, 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, refer to the Global Title chapter for more details.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
79
Create SCCP calling party address
CRSPCLGPA: SPCLGPA name = , [SPCLGPA id = ,] SPAPLOC name / ID = , SPLNKLOC name / ID = , GT Address Info = <GT digits>, TTID = Unknown , NP = ISDN-Tel. Numbering Plan , NA = International Nr. , CLGPA Type Indicator = Programmed , [Include SPC = False ,] [Include GT = False];
Fig. 55 SCCP calling party address
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
80
3.2.5 Creation of a remote SCCP linkage
Each SCCP in an external signaling node, with which SCCP messages are exchanged, has to be made known in the own node. SCCP messages from nodes, which were not announced in this way, will be discarded. As a prerequisite, the DPC must have been created with CRSIGDP before.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
81
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 SPLNKREMSPLNKREM 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
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
82
3.2.6 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 so-called broadcast list. Such a broadcast list is a list of remote SCCPs, created manually by CR SPCAREA.
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
83
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
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
84
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.
100
200
300
CRSPCAREA:SPCAREA=bclst,SPLNKREM List=sccp100&sccp200;
CRSPAPREM:SCCP Managem=TRUE,SPCAREA=bclst,SPLNKREM=remo500,SSID=MAPHLR,...;
SS_PROHIBITEDSS_ALLOWED
SP 1
MTP
SCCP
TCAP
BSSAP254
OTHEER
MAPVLR7
CAP146
MAPEIR9
MAPMSC8
MAPHLR6
INAP241
500
MTP
SCCP
TCAP
BSSAP254
OTHEER
MAPVLR7
CAP146
MAPEIR9
MAPMSC8
MAPHLR6
INAP241
SS_PROHIBITEDSS_ALLOWED
SS_PROHIBITEDSS_ALLOWED
SS_PROHIBITEDSS_ALLOWED
Fig. 60 Remote broadcast
Administration of the Signaling Network Siemens
MN2513EU11MN_0001
© 2002 Siemens AG
85
SP 1
MTP
SCCP
TCAP
MAPVLR7
BSSAP254
OTHEER
INAP241
MAPEIR9
MAPMSC8
MAPHLR6
SP 500 SS_PROHIBITEDSS_ALLOWED
MTP
SCCP
TCAP
MAPVLR7
BSSAP254
OTHEER
INAP241
MAPEIR9
MAPMSC8
MAPHLR6
CRSPAPREM:SPAPREM name=remo500SCCP Managem=TRUE,LocalBroadcast=TRUE,SSID=MAPVLR......;
Fig. 61 Local broadcast
SP 1
MTP
SCCP
TCAP
MAPVLR7
BSSAP254
OTHEER
INAP241
MAPEIR9
MAPMSC8
MAPHLR6
SP 500 TF_ALLOWED
MTP
SCCP
TCAP
MAPVLR7
BSSAP254
OTHEER
INAP241
MAPEIR9
MAPMSC8
MAPHLR6
CRSPAPREM:SCCP Managem=TRUE,SPAPREM Name=remo500,SPAP Avail.Restart=FALSE;
CRSPAPREM:SCCP Managem=TRUE,SPAPREM Name=remo500,SPAP Avail.Restart=TRUE;
SS_ALLOWED
&
Fig. 62 Access point availability
Siemens Administration of the Signaling Network
MN2513EU11MN_0001
© 2002 Siemens AG
86
top related