Professional Documents
Culture Documents
Siemens
Contents
1
1.1
1.2
2
2.1
2.2
3
3.1
3.2
3.3
4
4.1
4.2
4.3
4.4
5
5.1
5.2
5.3
5.4
6
6.1
6.2
EWSD in ISDN
Applications of EWSD in the ISDN
EWSD Feature Overview
EWSD Hardware Overview
Mechanical Design
Overview: System Architecture
Functional Structure of the Digital Line Unit (DLU)
Function Overview DLU B/D
Overview of DLU G Functions
xDSL Interfaces at EWSD DLU
Functional Structure of the Line Trunk Group (LTG)
External 2 Mbps Interfaces to LTG
Function Overview LTG
LTG Functional Types
Functional Units of the LTG
Functional Structure of the Remote Switching Unit RSU
Function Overview
RSU Functional Units
RSU Capacity Stage
RSU Emergency Operation
Functional Structure of the Switching Network (SN)
Internal EWSD Interfaces on the SN
Function Overview SN
SN2010EU13SN_0002
2002 Siemens AG
3
4
6
9
10
12
19
20
32
44
47
48
50
52
54
57
58
60
62
64
67
68
70
Siemens
6.3
6.4
7
7.1
7.2
7.3
7.4
8
8.1
8.2
8.3
9
9.1
9.2
10
11
12
SN B (EWSD-CLASSIC)
SN D (EWSD-POWERNODE)
Functional Structure of the Coordination Processor (CP)
Function Overview CP
System Features of the CP113
Functional Units of the CP
Input-Output Processors of the CP113
Functional Structure of the SS7 Network Control
Function Overview of the SS7 Network Control
Structure of the CCNC
Structure of the Signaling System Network Control SSNC
Application Program System (APS)
Components of the APS
APS Facts
Overview: EWSD Internal Call Setup
Exercise
Solution
72
76
81
82
84
86
88
91
92
96
100
107
108
110
113
119
123
SN2010EU13SN_0002
2002 Siemens AG
Siemens
EWSD in ISDN
SN2010EU13SN_0002
2002 Siemens AG
Siemens
1.1
The fully digital switching system EWSD was released on the world market in 1981
and has since then been constantly further developed.
In addition to the standard EWSD exchange which is offered in different hardware
configurations, the following special solutions are also available:
l
For lightly populated areas, it is however possible to use very small exchanges
from the EWSCountry range (e.g. the Small Digital Exchange SDE for up to 3000
subscribers).
SN2010EU13SN_0002
2002 Siemens AG
Siemens
Transit Node
SIEMENS
SIEMENS
SIEMENS
SIEMENS
SIEMENS
SIE MENS
SIEME NS
EWSD
V5 interfaces to the
access networks
SIEMENS
Gateway Node
Local Node
(optional with
internet traffic
off-loading)
SIEMENS
SIEMENS
SIE MENS
Fig. 1
TIP
It is also possible to configure EWSD in such a way that it can be used as a very
powerful stand alone Signaling Transfer Point STP (called hiS700).
SN2010EU13SN_0002
2002 Siemens AG
Siemens
1.2
ISDN
subscriber
features
e.g.
Call
diversion
Automatic
callback
Malicious
Call tracing
as with
analog
subscribers,
but in addition
e.g.
Closed user
group
Multiple
subscriber
numbers
Interface to
subscriber
equipment
features
e.g.
analog a/b
interface
digital U
interface
V5
interfaces
System
features
e.g.
Control
of the system
time with
a radio clock
File transfer
to the postprocessing
center
Interexchange
Charging
signaling
features
features
e.g.
e.g.
Channel
Metering
associated
procedure
signaling such
Automatic
as MFCR2, E&M...
message
accounting
Common
channel signaling
Billing
CCS7 with
between
user/application
network
parts such as
operators
ITUP, ISUP,
SCCP, TCAP,
INAP...
Fig. 2
SN2010EU13SN_0002
2002 Siemens AG
Siemens
GEOcentrex features
Implementation of exchange
features for one group of
subscribers directly connected to
EWSD (CENTREX group) such
as
Common abbreviated
directory number list
Call Pick Up
The possibility to administrate
the database of the CENTREX
group from one subscriberequivalent connected control
terminal
O&M features
e.g.
Decentralized O&M terminals:
operation and maintenace
terminal (NetM-boot or
BCT/BOOT)
Centralized operation via a
network management center
with net manager NetM
ADMOSS features
ADMOSS (Advanced
multifunctional operator service
system), with its multifunctional
operator's position (MSB) facilitates
the provisioning of operator
services in the network such as
Directory number information
with immediate forwarding
Language assistance for
international calls
Booking of calls
Setup of large conference
circuits
Intelligent network features
Service handling point tasks for
handling IN features such as
Freephone
Televoting
Universal personal
telecommunication
Fig. 3
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SN2010EU13SN_0002
2002 Siemens AG
Siemens
2.1
l
Mechanical Design
Rackrow
One or several network elements of the same or different types can be installed in
an installation room. The individual installation units are installed in rows. Such a
row is called a rackrow. These rackrows are numbered consecutively (rackrow
number) inside a room to make it possible to find them for maintenance.
Rack
A rack is subdivision within a rackrow. A rack has two doors on both the front and
rear side for reaching the HW modules or the cabling of the rack. A rack is
identified by the rack number.
Frame
The frames are located inside the rack. A frame comprises a metal frame as a
mechanical carrier, plastic shelves on the front side for holding the hardware
modules, and a multilayer backplane on the back side for the electric connections
within a frame and for plugging the cable to other frames or external equipment. A
frame can hold one or two horizontal rows of modules, depending on the size of
the backplane. A frame is identified by the so-called mounting unit or MUT. The
MUT serially numbers the individual horizontal sections of a rack from top to
bottom.
Two types of frames are used in the moment: SIPAC and SIVAPAC. Both types
mainly differ in the structure of the backplane and the plugs.
Module
The HW modules are located within the frame. The module rows within a MUT
are identified with the letter A or C in order to facilitate finding the modules even
with frames of several rows. The position of the modules within a module row are
identified by the module location or MOLOC (with SSNC called PITCH), which
is stamped on the metal carriers of the frame.
10
The entire rear wall cabling is pluggable. The cables are delivered with connected
cable connectors and in the required length.
EWSD installations get their supply voltage (48 V or 60 V DC) from central power
supply systems with battery.
SN2010EU13SN_0002
2002 Siemens AG
Siemens
Rack rows
SIEMENS
SIEMENS
3
SIEMENS
SIEMENS
SIEMENS
2
SIEMENS
SIEMENS
SIEMENS
MUT
1
01
02
03
04
05
06
SIEMENS
D 900
Racks
SIEMENS
Module frame
Module
SIEMENS
001 007 013 019 025 031 037 043 049 055 061 067 073 079 085 091 097 103 109 115 121
Module location
Fig. 4
SN2010EU13SN_0002
2002 Siemens AG
11
Siemens
2.2
2.2.1
Currently EWSD is used in over 100 countries where the hardware configurations
and software releases in the table below are mainly used.
The different HW units are described on the following pages.
12
SN2010EU13SN_0002
2002 Siemens AG
Siemens
Hardware
Configuration
Software
Version
EWSD CLASSIC
V11 / V12 /
up to 25000
V13A / V14A /
V15
more than
1000000
V13T / V15
up to 4000000
with Common
Channel Network
Controller CCNC
with Switching
Network SN A/B
with Remote
Switching Unit RSU
(only V14A / V15)
EWSD POWERNODE
l
with Signaling
System Network
Control SSNC
with Switching
Network SN D
with Remote
Switching Unit RSU
(only V15)
max. switched
traffic volume
in ERLANG
up to 100000
Busy Hour
Call Attempts
Fig. 5
TIP
Following additional features can be also used with EWSD SW versions V12I, V13I,
V14A and V15:
l
SN2010EU13SN_0002
2002 Siemens AG
13
Siemens
2.2.2
EWSD-CLASSIC includes the following HW units which are all equipped with their
own control processors.
l
14
SN2010EU13SN_0002
2002 Siemens AG
Siemens
LTG
PBX
LTG
Main station
subscribers
DLU
LTG
SN
0&1
RSU
DLU
LTG
HTI
RTI
CCNC
EWSD CLASSIC
CCG
CP
MOD
MDD
MB
max. 6 CAP
BCT
SIEMENS
NIXDORF
X.25 connections
to NetM and
postprocessing
centers
Fig. 6
SN2010EU13SN_0002
2002 Siemens AG
15
Siemens
2.2.3
Compared with the CLASSIC configuration, the following new HW units are used in
the EWSD POWERNODE:
l
MB Version D (instead of MB B)
Serves to distribute the message flow CP-LTG, CP-SND, SSNC-LTG and LTGLTG.
Netmanager (NetM)
The Netmanager is used for local and central operation and monitoring of the
EWSD Powernode.
Coordination Processor
The CP is connected via an so called ATM bridge processor (AMP) to the SSNC.
The switching efficiency of the CP (BHCA) is considerably better with the
POWERNODE then when used in the CLASSIC configuration. This is because
messages between LTG - LTG and LTG - SSNC directly passed by the MB D and
are not routed through the CP (CP is not loaded by the EWSD internal message
exchange.
16
SN2010EU13SN_0002
2002 Siemens AG
Siemens
LTG
EWSD
Powernode
DLU
LTG
2Mbps with
Trunks and
64kbps SS7 Links
LTG
SND
LTG
64 kbps or
High Speed
SS7 Links
NetM
SSNC
207Mb/s
MBD
207Mb/s
CP
Fig. 7
SN2010EU13SN_0002
2002 Siemens AG
17
Siemens
18
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SN2010EU13SN_0002
2002 Siemens AG
19
Siemens
3.1
3.1.1
Connectivity
Main station lines with pulse dialing, pushbutton dialing, call charge display
Coinbox telephones
3.1.2
up to 32 V5.1 interfaces
Mixture of analog subscribers, digital subscribers and V5.1 interfaces in view of the
fact that max. 120 calls can be held simultaneously
Each with a subscriber line module (SLMX) for two V5.1 interfaces with 30
subscribers each (access network AN)
Note:
The DLU type DLUV can be used as an alternative to SLMX in the standard DLU.
Only V5.1 access networks can be connected to a DLUV (max. 10 x V5.1 per DLUV).
20
SN2010EU13SN_0002
2002 Siemens AG
Siemens
digital
DLU B/D
Concentration
of the subscriber accesses
Analog/digital conversion
for analog subscribers
Modules
SLM for the connection of
a/b interfaces
(SLMA with 16 subscriber
line circuits SLCA)
U interfaces
(SLMD with 16 subscriber
line circuits SLCD)
2 Mbps PDC
V5.1 interfaces
(SLMX with
two V5.1 interfaces)
maximum
120 user
channels
with 64 kbps
Fig. 8
SN2010EU13SN_0002
2002 Siemens AG
21
Siemens
3.1.3
The DLU is connected to the LTG by a maximum of four primary digital carriers
(PDC), whereas a DLU is linked with two LTG as a rule for reasons of availability. As
an exception the HW type DLUV provides up to two PDC which may be regarded as
PDC0 and PDC2 in the following text.
The DLU can be used locally in the exchange or remotely in the vicinity of the
subscriber.
It is possible to connect the local DLUB to the LTG by two 4096 kbps routes instead
of four 2Mbps routes.
All features are regardless of whether the DLUB is operated locally or remotely.
Common channel signaling (CCS)
Channel 16 in the first and third PDC is used for the transmission of control
information messages between the DLUB and the line/trunk groups (LTG).
Here channel 16 on the first PDC transmits the control information messages for the
60 user channels to PDC 0 and 1, and channel 16 on the third PDC the control
information messages for the user channels to PDC 2 and 3.
For the local DLU interface, channel 32 on both 4096-kbps connections is used for
CCS.
High reliability
High reliability is yielded by:
22
SN2010EU13SN_0002
2002 Siemens AG
Siemens
Local application
PDC0
CCS
PDC1
DLU
PDC2
PDC3
Remote application
PDC0
LTG
CCS
CCS
PDC1
DLU
PDC2
CCS
LTG
PDC3
PDC0
DLU
PDC1
CCS
LTG
60 user channels
one CCS time slot between DLU control DLUC
and LTG control GP
alternative: 1 x 4 Mbit/s for local DLU interface
Fig. 9
SN2010EU13SN_0002
2002 Siemens AG
23
Siemens
3.1.4
l
24
SN2010EU13SN_0002
2002 Siemens AG
Siemens
DLU
PDC
0
SLM
Control
network 0
Subscriber
accesses
DIUD
DLU-System
0
Control
network 1
User information
network 0
DLUC
User information
network 1
2
SLM
DIUD
DLU-System
1
Testbus
to all SLM
TU
DLUC
Fig. 10
SN2010EU13SN_0002
2002 Siemens AG
25
Siemens
3.1.5
Special SLMA modules are available for special cases (e.g. connection of
subscribers via pair gain, connection of non-ISDN exchanges with direct-inwarddialing). If use is made of those special SLMA modules or of SLMA:FPE with external
ringing generator, the TU is still needed.
26
SN2010EU13SN_0002
2002 Siemens AG
Siemens
Analog
subscriber
line
Standard SLMA
4096-kbps-bus 0
(DIUD0 or
DIU:LDID0)
4096-kbps-bus 1
(DIUD1 or
DIU:LDID1)
15
SLCA
Control bus 0
(DLUC0)
Test bus
(not in case of
ILTF-SLMA)
Control bus 1
(DLUC1)
Battery Supply
Overvoltage Protection
Ringing
Signaling
Coding
Hybrid 2/4-Wire
Testing
Fig. 11
SN2010EU13SN_0002
2002 Siemens AG
27
Siemens
TIP
ILTF-SLMA can provide for SLMDs the necessary test functions which otherwise are
performed by the TU. This works for the so called ILTF-SLMD (ILTF = integrated line
test function). Therefore no SLMD-modules with integrated ILTF is existing.
28
SN2010EU13SN_0002
2002 Siemens AG
Siemens
ISDN
subscriber
lines
0
SLMD
4096-kbps-bus 0
(DIUD0 or DIU:LDID0)
4096-kbps-bus 1
(DIUD1 or DIU:LDID1)
15
SLCD
Control bus 0 (DLUC0)
Test bus
Control part
Overvoltage protection
Provisioning of the time multiplex interface with the 2B and D channel with a total
of 144kbps and the 16kbps for the clock synchronization (layer 1 of the DSS1)
Echo compensation for the bidirectional digital transmission on the 2-wire
subscriber line (layer 1 of the DSS1)
2-wire/4-wire conversion and adaption of the line code used on the subscriber
line (layer 1 of the DSS1)
Separation of the DSS1 signaling messages from the X.25 data packets of the
subscriber (layer 2 of the DSS1)
Protection of the transfer of the DSS1 signaling messages in the D channel
(layer 2 of the DSS1)
Test access to the subscriber line/circuit
Fig. 12
SN2010EU13SN_0002
2002 Siemens AG
29
Siemens
3.1.6
If both control units of a DLU lose their signaling channel to the LTG owing to
transmission faults (failure of the PDC) or LTG failures, a DLU can continue to work
in stand alone service. This feature is as a rule available to all remote DLU. For this
the DLU must be equipped with a stand alone service control module (SASC-E).
This module assumes the control of the call setup between subscribers of the same
DLU when in stand alone service. The through-connection of the voice
communication follows internally in the DLU. Metering does not take place.
TIP
If several remote DLU are next to one another, they can be aggregated to a remote
control unit (RCU). Up to 6 remotes DLU are linked to one another for this (interDLU connections).
If the individual DLU of an RCU go into stand alone service, calls between
subscribers on different DLU of the RCU are still possible.
The inter-DLU connections are used in stand alone service only.
30
SN2010EU13SN_0002
2002 Siemens AG
Siemens
PDC0
PDC1
DLU1
PDC2
LTG
PDC3
Links
between
the DLUs
of an RCU
DLU2
DLU3
DLU4
DLU5
PDC0
PDC1
DLU6
PDC2
LTG
PDC3
with CCS
without CCS
Fig. 13
SN2010EU13SN_0002
2002 Siemens AG
31
Siemens
3.2
From software release V15 the DLUG can be used as a digital concentrator to
connect subscribers to EWSD. This section only deals with connecting analog and
ISDN-BA subscribers, the xDSL solutions for high bit rate Internet access are dealt
with in a later section.
3.2.1
coin telephones
ISDN -
3.2.2
up to 40 x V5.1 interfaces
32
each with one analog subscriber line module (SLMA for 32 subscribers)
each with one digital subscriber line module (SLMD for 16 subscribers)
each with one V5.1 line module DLU-V for 10 V5.1 interfaces with 30 subscribers
per interface (Access Network AN)
SN2010EU13SN_0002
2002 Siemens AG
Siemens
DLU G
Concentration
of the subscriber accesses
Analog/digital conversion
for analog subscribers
Modules
SLM for the connection of
a/b interfaces
(SLMA with 32 subscriber
line circuits SLCA)
U interfaces
(SLMD with 16 subscriber
line circuits SLCD)
V5.1 interfaces
(DLUV with
ten V5.1 interfaces)
Fig. 14
SN2010EU13SN_0002
2002 Siemens AG
33
Siemens
3.2.3
The DLU is connected to LTG's via a maximum of 16 primary multiplex lines (PDC),
although for reasons of availability, a DLUG is usually connected to four LTG's.
The DLU can be used locally in the exchange or remotely close to the subscribers.
For the local DLU interface it is possible to connect the DLU to the LTG via 4096
kbps routes (local digital interface LDI) instead of two 2Mbps routes.
All features are independent of whether the DLU is operated locally or remotely.
Each DLUV module (10 V5.1 interfaces) is connected independently of the other DLU
parts via 2 PDC's.
Common Channel Signaling (CCS)
For the transmission of control information between the DLU and the line modules
(LTG), a 64kbps channel is used by default per LTG which is located in PDC0 time
slot 16.
This channel transmits the control information for all user channels on all PDC's to
this LTG. Here a modified CCS7 protocol is used.
High service reliability
High service reliability results from:
34
constant self-testing
SN2010EU13SN_0002
2002 Siemens AG
Siemens
TS16
SLMD16
LTGN
DLUG
TS16
SASC-G
LTGN
option.
ALEX
DLUC 1,
MTA
DLUC:LDI
for local DLUG
or
DLUC30
for remote
DLUG
option.
option.
TS16
LTGN
TS16
Special 2)
module types
4x
TS16
LTGN
(2Mbps)
or
2x
(4Mbps)
per LTG
signaling channel between DLU and LTG for controlling all speech channels
between DLU and LTG
Fig. 15
SN2010EU13SN_0002
2002 Siemens AG
35
Siemens
3.2.4
36
SN2010EU13SN_0002
2002 Siemens AG
Siemens
DLUG
SLMA32
SLMD16
DLUC 0,
1)
DLUC:LDI
for local DLUG
or
DLUC30
for remote
DLUG
LTGN
1)
LTGN
SASC-G
option.
ALEX
option.
MTA
option.
DLUC 1,
1)
DLUC:LDI
for local DLUG
or
DLUC30
for remote
DLUG
Special 2)
module types
LTGN
1)
LTGN
Fig. 16
DLU Bussystem
(control & user info)
BDs 0
SLMA
(SLMD only
connected to
one bus per
DLUC)
I
O
P
DLUC 0
I
O
P
DLUC 1
LTG x 0
LTG x 1
LTG y 0
LTG y 1
max.
4 PDC
per LTG
BDs 1
Fig. 17
SN2010EU13SN_0002
2002 Siemens AG
37
Siemens
3.2.5
38
SLMA:ITHG (with Metallic Test Access and increased power supply for coin
telephones)
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SLIC
Port 0
subscriber line
interface circuit
.
.
.
.
SLMCP
2x PCM-bus
to DLUC0
overvoltage protection
2x PCM-bus
to DLUC1
2/4 wire
line feeding
ringing and metering
analog/digital conversion
testing
2x Control-bus
to DLUC0
Port 31
2x Control-bus
to DLUC1
feedinginterface
Powersupply
DC- DC
converter
FEprom
SLMA:ITFG
Fig. 18
SN2010EU13SN_0002
2002 Siemens AG
39
Siemens
TIP
ILTF-SLMA can provide for SLMDs the necessary test functions which otherwise are
performed by the TU. This works for the so called ILTF-SLMD (ILTF = integrated line
test function). Therefore no SLMD-modules with integrated ILTF is existing.
40
SN2010EU13SN_0002
2002 Siemens AG
Siemens
ISDN
subscriber
lines
SLMD
4096-kbps-PCM bus 0
(DLUC0)
4096-kbps-PCM bus 1
(DLUC1)
15
SLCD
Control bus 0 (DLUC0)
Test bus
(not in case of
ILTF-SLMD)
Control part
Overvoltage protection
Provisioning of the time multiplex interface with the 2B and D channel with a total
of 144kbps and the 16kbps for the clock synchronization (layer 1 of the DSS1)
Echo compensation for the bidirectional digital transmission on the 2-wire
subscriber line (layer 1 of the DSS1)
2-wire/4-wire conversion and adaption of the line code used on the subscriber
line (layer 1 of the DSS1)
Separation of the DSS1 signaling messages from the X.25 data packets of the
subscriber (layer 2 of the DSS1)
Protection of the transfer of the DSS1 signaling messages in the D channel
(layer 2 of the DSS1)
Test access to the subscriber line/circuit
Fig. 19
SN2010EU13SN_0002
2002 Siemens AG
41
Siemens
3.2.6
If both DLUC lose all their signaling channels to the LTG because of transmission
errors (PDC failure) or LTG failure, a DLU can continue to work in emergency
operation (stand alone service). This feature is usually available to all remote DLU's.
The DLU must be equipped with an emergency operation control module SASC-G.
In emergency operation, this module takes over the control of setting up a connection
between subscribers of the same DLUG. Voice connections are through connected
internally in the DLU. Calls are not metered. There is no connection to subscribers at
other DLU's.
42
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SLM
LTG
L
U
SLM
traffic
LTG
LTG
SASC G
control
LTG
Fig. 20
SN2010EU13SN_0002
2002 Siemens AG
43
Siemens
3.3
Subscriber modules which provide xDSL subscriber line interfaces can also be
integrated into a DLU. The administration of these modules require the NetM.
Such a DLU is then called a hiA7100 which belongs to the ATTANE product family.
The xDSL technology provides the subscriber simultaneously with
l
The POTS / ISDN connections of the xDSL subscriber are routed to an LTG as with
other analog / digital EWSD subscribers via the DLU-internal control and payload
network and the DLUC.
With high bit rate Internet access the useful information must by contrast be handed
over directly from the DLU into the IP network of the Internet Service Providers ISP.
This means, here is no circuit-switched connection setup by EWSD towards a Point
of Presence PoP of the ISP as is the case with conventional remote dial-in users.
Therefore neither the DLUC of the DLU nor any other EWSD system unit is loaded by
the data transfer of these high bit rate accesses.
The DLU must be upgraded by three components to become a hiA7100:
Packet Hub SLMI:PHx with interface to the ISP's packet network
The Packet Hub offers access to the ISP's data network for maximum 14 xDSL
subscriber modules. Here the Packet Hub supports the following interfaces toward
ISP: Ethernet, Frame Relay or ATM.
DLU-internal ATM connection between the individual xDSL subscriber modules
and the Packet Hub
These connections are implemented individually for each xDSL subscriber module
either using plug-in cable (front side of the subscriber module for the front side of the
Packet Hub) or via the backplane of the DLU.
Subscriber modules with xDSL interfaces
44
SN2010EU13SN_0002
2002 Siemens AG
Siemens
ADSL
(HBR data
plus
POTS/BA)
DLU
DLU System
ADSL.Lite
S
IE
ME
NR
S
N
IXD
O
F
SLMI:FMx
Micro
filter
ADSL NT
SIEM
ENS
NIXD
ORF
NT BA
Voice via
DLU Bus
HBR data
via ATM
Ethernet
SIEME
N
S
NIXDO
F
R
to
LTG
Voice
Splitter
ADSL
SLMI:AMx
+ SLMA/D
Packet
Hub
to ISP via
ATM/FR/
Ethernet
Fig. 21
SN2010EU13SN_0002
2002 Siemens AG
45
Siemens
46
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SN2010EU13SN_0002
2002 Siemens AG
47
Siemens
4.1
48
for the connection of digital trunks with CAS signaling from/to nodes of the PSTN
for the connection of digital trunks from/to nodes of the ISDN, for the connection of
CCS7 signaling channels from/to nodes of the ISDN or central databanks such as
the service control point (SCP) of the IN
For the connection of large PSTN private branch exchanges with CAS signaling
for the connection of large ISDN private branch exchanges, intelligent peripherals
(IP) of the IN, or packet handlers of a X.25 packet network (PSPDN) by the
primary access (PA) with DSS1 signaling
SN2010EU13SN_0002
2002 Siemens AG
Siemens
LTG
4x
2 Mbps
PDC
Fig. 22
SN2010EU13SN_0002
2002 Siemens AG
49
Siemens
4.2
The line trunk group (LTG) forms the interface between the digital environment of the
node and the digital switching network (SN).
Connection to the duplicated switching network:
8Mbps SDC with 128 time slots
(If the LTG is part of an RSU the SDC are connected to the RTI of the RSU. The RTI
itself is connected to the SN via the so called HTI.)
Function of the LTG:
The LTG take on decentralized control tasks for reducing the load on the coordination
processor (CP).
The LTG communicate with the CP / SSNC or CCNC / other LTG via message
channels (MCH) for this.
The LTG always sends and receives the speech information via both switching
networks (SN0 and SN1).
However the LTG only relays the speech information from the active switching
network outward. The other SN is designated as inactive. The LTG can immediately
send and receive the current user information with it in case of a fault.
50
SN2010EU13SN_0002
2002 Siemens AG
Siemens
LTG
Call processing:
decentralized control
tasks for call setup to
reduce the load of the CP
PDC 0
PDC 1
Interface conversion
between duplicated SN
and the digital
environment of the node
(through-connection
of the user information)
PDC 2
PDC 3
8Mbps SDC
8Mbps SDC
SN0
SN1
Fig. 23
SN2010EU13SN_0002
2002 Siemens AG
51
Siemens
4.3
In order to optimally realize various line types and signaling systems, several LTG
functional types each with specific application programs are available.
These various functional types of the LTG SW determine the connecting capabilities
to an LTG.
Different types of LTG frames exist simultaneously.
The table opposite shows which LTG software functional type is compatible with
which hardware implementation.
52
SN2010EU13SN_0002
2002 Siemens AG
Siemens
LTG
Software Functional Type
Funktional type B
Compatible
LTG
HW - Type
LTG G/M/N
DLU
PBX
Intelligent peripheral
Packet handler of a X.25 packet network
V5.2 Access Network (only to LTG M/N )
Funktional type C
LTG G/M/N
LTG D
LTG H
Fig. 24
SN2010EU13SN_0002
2002 Siemens AG
53
Siemens
4.4
l
Group switch GS
The group switch realizes the following at the instigation of the GP:
The through-switching of individual speech channels between the PDC and the
SDC with and without attenuation.
The interconnection of tones of the TOG and of code receivers to the user
channels of the PDC.
The formation of three-way conferences
The link to the LTU is realized by speech highways (SPH), the link to the SN by
the LIU.
54
SN2010EU13SN_0002
2002 Siemens AG
Siemens
LTU
Speech
route
DIU
SPH
PDC
S
N
0
LIU
GS
8Mbps
S
N
1
SPH
DIU
SPH
Special
module
SPH
SIH
Signal Unit
CR / TOG
SIH
GP
SIH
PDC
Fig. 25
SN2010EU13SN_0002
2002 Siemens AG
55
Siemens
56
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SN2010EU13SN_0002
2002 Siemens AG
57
Siemens
5.1
Function Overview
The RSU enables the operation of up to 50,000 subscribers with DLU`s and LTG's at
one of the sites remote from the host exchange. The connection from the host
exchange to the LTG's of the RSU is realized from the switching network (host) via
the Host Timeslot Interchange HTI via PCM30 with Interface Trunks to the Remote
Timeslot Interchange RTI.
The heart of the RTI is a switching network which should be considered an extension
of the host switching network. Connections between Subscriber-, trunk- or PBXLineports connected at the same RSU are directly switched in the RSU switching network
without having to route the connection via the host exchange.
It is possible to connect the RSU via Backdoor trunks to other exchanges or via
Sidedoor trunks to another RSU (the same host exchange).
In the event of a fault (e.g. failure of the host exchange or failure of the transmission
routes from the host exchange to the RSU), RSU enables stand-alone operation.
This means that calls between subscribers of an RSU are possible.
58
SN2010EU13SN_0002
2002 Siemens AG
Siemens
LTG
SN
SN LTG
HTI
DLU
Interface
trunks
CCNC/
SSNC
CP
Interface
trunks
Backdoor
trunks
DLU
Sidedoor trunks
LTG
RTI
EWSD RSU
RTI
LTG
DLU
EWSD RSU
Backdoor
trunks
Other exchange
Other exchange
Fig. 26
SN2010EU13SN_0002
2002 Siemens AG
59
Siemens
5.2
Each HTI and RTI is internally duplicated with the exception of the interface module
DIU240 (Plane 0 and 1 of HTI / RTI). The essential functional units of HTI and RTI
are:
TSI (AMUX and TSIM)
The core of the HTI/RTI is the TSI (Time Slot Interchange) unit which consists of the
AMUX modules (0 to 7) and the TSIM module. The TSI forms the switching network
in the RSU with a matrix 128 x 8 Mbit/s.
MH module
The message channels (MCH) between the LTG's and the host message buffer are
administered in the HTI/RTI by the MH modules. The message channels have their
own transmission protocol (High Speed Link HSL) for transmission on the interface
trunks. Each MH module administers 16 MCH the individual MH modules together
form an MH pool.
RSUC module
The RSUC module is responsible for controlling the HTI/RTI. It communicates with
the host CP in a similar manner to the CP with the GP (Group Processor) of the LTG.
The RSUC module communicates internally with the TSI and MH modules for
connection setup, connection release and OA&M.
DIU240 module
The interfaces module for the interface trunks/sidedoor trunks is the DIU240. Each
DIU240 has 8 x 2 Mbit/s interfaces. Each DIU240 is connected to both redundant
system halves (plane 0 & 1) of their RTI and HTI.
60
SN2010EU13SN_0002
2002 Siemens AG
Siemens
M
H
R
S
U
C
M
H
M
H
TSI
R
S
U
C
M
H
SN 0
TSI
DIU
240
DIU
240
plane0
T
DIU
240
plane1
DIU
240
TSI
M
H
M
H
TSI
R
S
U
C
M
H
RTI
HTI
M
H
R
S
U
C
SN1
Fig. 27
SN2010EU13SN_0002
2002 Siemens AG
61
Siemens
5.3
SNA/B = 8 HTI
SND = 32 HTI.
62
SN2010EU13SN_0002
2002 Siemens AG
Siemens
TSIM +
AMUX
LTG
DLU
Backdoor
Trunks
DIU 240
DIU 240
DIU 240
DIU 240
DIU 240
up to
RSUC
71 LTGs
SN
up to
24 DIUs
DIU 240
192 PCM30
(E1 links)
up to
24 DIUs
RSUC
MH
RTI
HTI
RSU
TSIM +
AMUX
up to
MH
up to 254 RSU
LTG
LTG
Interface
Trunks
Sidedoor
to other
Trunks
RSUs
32 HTIs with SN D
CP
Host Exchange
to other
RSUs
Fig. 28
SN2010EU13SN_0002
2002 Siemens AG
63
Siemens
5.4
If an RTI looses all signaling channels to the host owing to transmission errors (PCM
failure) or HTI/host total failure, the RSU can continue working in emergency
operation (stand alone service).
In emergency operation, this RTI tasks over controlling the connection setup between
all subscribers connected to this RTI. The voice connection is through connected
internally in the RTI (TSI).
During stand alone operation no charge registration is performed.
Call set ups via sidedoor trunks or via SS7ISUP backdoor trunks are not possible.
Only connections between 2 subscribers of the same RSU and connections via
specially administered "default backdoor trunks with CAS signaling" are set up.
64
SN2010EU13SN_0002
2002 Siemens AG
Siemens
sidedoor
RSU
LTG
LTG
CSS7
predefined CAS-
backdoor
backdoor trunks
tunks
or PAslave
trunks
LTG
LTG
DLU
DLU
sub-
sub-
scriber
scriber
Host
possible trafficpaths
Signaling
Fig. 29
SN2010EU13SN_0002
2002 Siemens AG
65
Siemens
66
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SN2010EU13SN_0002
2002 Siemens AG
67
Siemens
6.1
The internal interfaces from LTG, HTI, CCNC and MB to the SN are implemented
using Secondary Digital Carrier SDC with 8Mbps (the SSNC has no direct interface
to the SN).
Here the SN serves to establish the transient bi-directional through connecting of
data of a 64kbps connection between two LTG's (payload) and also to the semipermanent through connecting of the 64kbps message channels MCH to exchange
internal messages between the LTG, SSNC/CCNC and CP.
The CP and SSNC have access to this internal message channel system via the MB.
(The CCNC of EWSD Classic has access via the CP.)
The processor of each LTG (Group Processor GP) uses the time slot 0 on the SDC
to the SN as its message channel.
In the case of the RSU the interfaces on the SN and the LTG are as described. Only
between HTI and RTI are the SDC implemented in several 2Mbps PCM.
68
SN2010EU13SN_0002
2002 Siemens AG
Siemens
Time slot 0:
Message channel (MCH) between
LTG and MB (semipermanent through-connection)
for communication between LTG/CP/SSNCorCCNC
Time slot 1-127:
Used for the transient
through-connection of the calls
between two subscribers/trunks
SN
LTG
LTG
SSNC
MB
or
CP
CCNC
2 Mbps PDC
8 Mbps SDC
Fig. 30
SN2010EU13SN_0002
2002 Siemens AG
69
Siemens
6.2
Function Overview SN
the EWSD internal message exchange between the controls of the LTG,
SSNC/CCNC, and CP via the fixed message channels (MCH)
the CCS7 signaling messages between the CCS7 signaling channels on the PCM
routes connected to the LTG and the SSNC/CCNC (by MML command
established nailed-up connections NUC, in case of SSNC the NUC is established
via a so called "inward LTG").
The switching network is completely duplicated (SN0 and SN1). All calls are always
simultaneously through-connected through both SN, whereas the LTG only thoughconnects the user channel information coming from the active SN to the PCM routes.
If the active SN fails, the other SN (stand-by SN) is switched to without any loss.
The through-connection in the SN B takes place according to the time - space - time
principle (change of the time slot, change of the highway, change of the time slot), in
the SN D a so called switching matrix is used. Every through-connection
guarantees in both cases a transparent bi-directional 64kbps path through the SN.
Sequence for the temporary through-connection of the circuit connections:
l
The CP call-processing programs look for a free call path in the software switching
network image of the CP database from the LTG of the calling party to the LTG
of the called party, for instance.
The SN - control units execute the setting instructions in the responsible modules.
The call path from the LTG of the calling party through the SN to the LTG of the
called party is thus through-connected.
Along with the temporary through-connections (transient connections), there are also
the semi-permanent connections:
70
SN2010EU13SN_0002
2002 Siemens AG
Siemens
EWSD-CLASSIC
SN A or SN B
LTG
SN 0 & SN 1
Switching modules
handling
User channels between 2LTG
EWSD internal messages
between LTG, SSNC/CCNC,
and CP (message channels)
LTG
CCNC
Message
channels
of all LTG
MB
Setting
instructions
Control
SSNC
CP
8 Mbps
Fig. 31
SN2010EU13SN_0002
2002 Siemens AG
71
Siemens
6.3
SN B (EWSD-CLASSIC)
6.3.1
The SN is offered in various increments. Except for the small switching networks for
max. 31 or 63 LTG (combined space-time stages), the SN comprise the subdivisions
time stage group (TSG) and space stage group (SSG).
Time stage group (TSG):
l
Every time stage group serves to connect the SDC to/from the LTG, the CCNC,
and the MB (together with max. 64 of this SDC). An SN can consist of a maximum
of 8 duplicated TSGs.
There is a switch group control (SGC) in every TSG which is connected to the CP
by means of an own SDC via the message buffer (MB). The SGC receives the
setting instructions for the temporary or permanent bi-directional 64 kbps throughconnection from the CP. The SGC realizes the through-connection by setting the
individual time stage modules (TSM) of a TSG. Every TSM can change the
position in time and space of any time slot in any manner for a group of 8
connected SDC in a TSG.
SDC:LTG, secondary digital carrier between SN and every LTG for the circuit
connections (time slots 1-127) and for the message exchange between the LTG
control unit GP and the CP (message channel to time slot 0).
SDC:CCNC, one or two secondary digital carrier for through-connecting the CCS7
messages between CCNC and the signaling channels on the PCM routes to the
LTG.
SDC:SGC, a secondary digital carrier between the control unit SGC of this TSG
and the MB for relaying the setting instructions of the CP to the TSG.
72
The SSGs serve to through-connect the calls between TSMs in the same or in
different TSGs. An SN can consist of a maximum of 4 duplicated SSGs.
There is a switch group control (SGC) in the SSG which is connected to the CP via
the message buffer (MB). The SGC receives the setting instructions for the
temporary or permanent bi-directional 64 kbps through-connection from the CP.
The SGC realizes the through-connection by setting the individual space stage
modules (SSM) of an SSG. Every SSM can change the highway of the time slot for
all connected SDC in any manner.
SN2010EU13SN_0002
2002 Siemens AG
Siemens
The individual TSGs and SSGs are connected to one another by SDC:SSG. Here the
TSGs and the SSGs of the same switching network (SN0 or SN1) normally work
together. In the case of an error, a TSG of SN0 can work together with an SSG of
SN1, for instance. This possibility of protection switching grants the duplicated SN a
very high failure security.
SSG0-0
CCNC
SSM
TSM
SSM
SGC
MB
SGC
SSG0-3
TSG0-7
SSM
TSM
CP
SSM
TSM
SGC
SGC
time slot x
time slot x
SSM
TSM
time slot x
SDC
time slot y
SDC
Time Stage module TSM
Fig. 32
SN2010EU13SN_0002
2002 Siemens AG
73
Siemens
6.3.2
Since the SN is offered in many capacity stages, the actual size of the SN can be
adapted to the expected amount of traffic of an exchange. Here the traffic to be
through-connected measured in Erlang as dimensioning sizes is to be observed.
Remark:
Except the beside shown capacity stages there are also offered a SN for 31LTG and
a SN for 63 LTG.
Notes on capacity/ space requirements of the SN capacity stages
l
For the given values, the highest technically possible values are concerned.
74
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SN for
max.
126 LTG
SN for
max.
252 LTG
SN for
max.
504 LTG
6300
12600
25200
60000
120000
240000
15000
30000
60000
Ratings
Traffic (ERL.)
SN:126LTG
TSG
0.0
TSG
0.1
SSG
0.0
SN0
SN1
TSG
1.0
TSG
1.1
SSG
1.0
SN:252LTG
TSG
0.0
TSG
1.0
TSG
0.1
TSG
1.1
TSG
0.2
TSG
1.2
TSG
0.3
TSG
1.3
SSG0.0
SN0
SSG0.1
SN1
SSG1.0
&
SSG1.1
SN:504LTG
TSG
0.0
TSG
1.0
TSG
0.1
TSG
1.1
TSG
0.2
TSG
1.2
TSG
0.3
TSG
1.3
TSG
0.4
TSG
1.4
TSG
0.5
TSG
1.5
TSG
0.6
TSG
1.6
TSG
0.7
TSG
1.7
SSG0.0 SSG0.2
&
&
SSG0.1 SSG0.3
SN0
SN1
SSG1.0 SSG1.2
&
&
SSG1.1 SSG1.3
Fig. 33
SN2010EU13SN_0002
2002 Siemens AG
75
Siemens
6.4
6.4.1
SN D (EWSD-POWERNODE)
Functional Units of the SN D
A multiplexer and a demultiplexar are provided for the existing environment with
F:SNMUXA which bundle 2 x 64 x 8 Mbit/s LTG lines to two optical lines connected
to F:SNMAT. Switching is implemented by F:SNMAT.
In smaller exchanges (up to 252 LTG's) F:SNMUXA can execute switching by itself
(without SNMAT). Here the two required SNMUX's (per SN side) are connected
directly to one another using the optical lines.
To connect the SND with the co-ordination processor CP, an MBD message
distributor is required.
The following interfaces can be differentiated:
76
SDC:LTG
Secondary multiplex line between SN (SNMUX) and each LTG for the user
channel connections (time slots 1-127) as well as for the message exchange
between the LTG control GP and the CP (Message Channel on time slot 0). The
SDC:LTG are identical to the SDC:LTG at the SN B.
MBD-Sx
Secondary multiplex line between the control module in SNMUX / SNMAT and the
MB-D to relay the setting instructions of the CP to the switching network.
SN2010EU13SN_0002
2002 Siemens AG
Siemens
LTG 0-1
..
.
LTG 0-63
SNMUX
0
..
.
LTG 1-1
LTG 1-63
127
8 Mbit/s
SDC-interface
LTG 30-63
SNMUX
15
..
.
LTG 31-1
LTG 31-63
920 Mbit/s
optical interface
(1 x MBD-S3
only with SN252 LTG)
..
.
LTG 30-1
..
.
2 x MBD-S1
920 Mbit/s
optical interface
127
920 Mbit/s
optical interface
30
920 Mbit/s
optical interface
31
2 x MBD-S1
MBDH
..
..
..
SNMAT
1 x MBD-S3
MBD
CP
Fig. 34
SN2010EU13SN_0002
2002 Siemens AG
77
Siemens
6.4.2
SN D Capacity Stages
max.
DE-TYPE
number of
LTG
max.
number
of
SNMUX
per SN
side
SNMAT- Traffic
per SN
Erl
side
252
DE6.0
12600
252
DE6.1 *)
12600
504
DE6.2
25200
756
DE6.3
37800
1.008
DE6.4
50400
1.260
DE6.5
10
63000
1.512
DE6.6
12
75600
1.764
DE6.7
14
88200
2.016
DE6.8
16
100800
*)
use DE6.0 instead of DE6.1 if not more thane 252 LTG are
planned (because DE6.0 does not require an SNMAT).
78
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SN D - DE6.0
for 126 LTG
SN D - DE6.0
for 252 LTG
F:SNMUXA 0
F:SNMUXA 0
F:SNMUXA 0
F:SNMUXA 1
F:SNMUXA 1
F:SNMUXA 1
SN D - DE6.8
for 2016 LTG
15
F:SNMUXA 0
F:SNMUXA 0
F:SNMUXA 0
F:SNMUXA 0
F:SNMUXA 1
F:SNMUXA 1
F:SNMUXA 1
F:SNMUXA 1
F:SNMAT 0
F:SNMAT 1
Fig. 36
SN2010EU13SN_0002
2002 Siemens AG
79
Siemens
80
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SN2010EU13SN_0002
2002 Siemens AG
81
Siemens
7.1
Function Overview CP
82
For call processing, the CP assumes the central tasks for a call setup. In the
course of this, LTG and the SSNC/CCNC reduce the load on it.
For operation and maintenance, the CP makes the interfaces available for the
man-machine dialogue (input of commands, output of messages and alarms) and
to the mass storage devices (magnetic tape/magnetic disk).
For safeguarding, the CP assumes the master-function for monitoring the EWSD
hardware and software.
SN2010EU13SN_0002
2002 Siemens AG
Siemens
CP113C / CP113CR
Call processing:
Digit translation
Routing
Zoning
Path selection through the
SN
Charging
Traffic data administration
Network management
Safeguarding:
Self-supervision
Supervision of all EWSD functional units
Fault detection
Fault analysis
Fig. 37
SN2010EU13SN_0002
2002 Siemens AG
83
Siemens
7.2
CP types:
l
84
Redundancy by duplication of major functional units and pool formation with the
call processors
Common memory with a capacity of (at present) 64 Mbyte to 1024 Mbyte (1Gbyte)
(used chip at present: 16 Mbit DRAM)
Local memory per processor with a capacity of max. 64 Mbyte (used chip at
present: 16 Mbit DRAM)
SN2010EU13SN_0002
2002 Siemens AG
Siemens
Interfaces of the CP
Input/output processors to:
EWSD functional units
Mass storage devices
Local O&M terminals for manual Boot
NetM
Post processing center
Fig. 38
SN2010EU13SN_0002
2002 Siemens AG
85
Siemens
7.3
By adding functional unit of the same type, it is possible to expand the basic capacity
of the CP113C, depending on necessity. This applies both for the arithmetic and
storage capacity and for the connection of call processing and administrative
peripherals.
Base processors (BAP)
One of the two base processors is operated as master (BAPM) and the other as
spare (BAPS). The BAPM handles the administrative tasks and in addition call
processing tasks proportionally. The BAPS handles only call processing tasks. If the
BAPM fails, the BAPS becomes master and assumes the administrative tasks
(active/stand-by redundancy for the administrative tasks).
Call processors (CAP)
The call processors (CAP) of the CP113C exclusively handle call processing tasks.
They work in according to the load sharing principle. The CAP generate a pool
redundancy for call processing tasks together with the BAPS and BAPM in that one
more processor is available than required for the fulfillment of the nominal call
processing handling capacity (n + 1 redundancy). The CP113C can therefore
continue to produce the full nominal load even if one processor (BAP or CAP) fails.
With EWSD CLASSIC the maximum number of CAPs is 6 while with EWSD
POWERNODE you can have up to 10 CAPs in the CP.
Input-output controls (IOC)
The IOC each generate a common interface to bus B:CMY for max. 12 in-output
processors (IOP) via bus B:IOC. The input-output controls (IOC) and the connected
input-output processor (IOP) for the connection of administrative/data
communication devices (e.g. input device, mass storage device) and the peripheral
EWSD system units (e.g. LTG/SN via message buffer) are so dimensioned that they
can assume the tasks of the partner device if it should fail.
Common memory (CMY)
The content of both CMY is always the same; all write and read cycles of the
processors always run simultaneously in both CMY. While the content of the local
memory (LMY) of the BAP and CAP are only accessible to their own respective
processors, all processors of the CP have read and write access to the duplicated
CMY. All programs and data (resident components of the EWSD software) which are
relevant to the work of the processors of the CP are stored in the CMY.
Bus to the common memory (BCMY)
Every BAP, CAP, IOC, and CMY is connected to both common bus systems B:CMY.
Normally the data and addresses between processor and CMY are transmitted when
a write or read cycle takes place via the B:CMY0 to the CMY0 and via the B:CMY1 to
the CMY1. In the case of an error (e.g. failure of B:CMY0 and CMY1), the processors
can, for instance, also communicate with the CMY0 via the B:CMY1.
86
SN2010EU13SN_0002
2002 Siemens AG
Siemens
CP113C
Basic capacity of the CP113C,
Capacity of the CP113CR
11
CAP
CAP
BAPM
BAPS
IOP
IOP
B:IOC
IOC1
IOC0
IOC3/
AMP1
IOC2/
AMP0
B:CMY0
B:CMY1
CMY1
CMY0
Fig. 39
SN2010EU13SN_0002
2002 Siemens AG
87
Siemens
7.4
The duplicated operating and data equipment (O&M periphery) are always connected
to two different IOC's. If an IOC or the corresponding input-output processor fails,
input or output occurs via the partner IOC from and too redundant operating and data
equipment.
IOP:MB to connect the peripheral EWSD system units
The input-output processors for message distributors IOP:MB are the interfaces of
the CP113C/CR to the peripheral EWSD system units. The EWSD internal
communication with the controls of the peripheral system units is processed via this.
The number of IOP:MB used is dependent of the size of the network node. The
connection from the IOP:MB's to the peripheral EWSD system units is cross-jointed.
If one of the two IOP:MB's fails, then the other takes over the data exchange on its
own.
If the ProfiBus is used instead of the SYPC, the HW variant IOP:MB/PB (PB =
ProfiBus) must be used. It can be used for each IOP:MB. Mixed equipping is
possible.
The following are connected to the IOP:MB's:
l
the controls for the network of the central common channel signaling channels
CCNC (does not apply if the SSNC is used).
optionally a terminal for operation and maintenance (BCT) and two data lines or
three data lines (data line with switching protocol)
The input-output processor IOP:LAU (also called IOP:SCDP) allows two data lines
to be connected using the packet-switched protocol X.25. Both remote input
equipment/Network Management Center and Post-processing Centers can be
connected via this.
88
SN2010EU13SN_0002
2002 Siemens AG
Siemens
hardware time of the CP: master for the system time managed in the BAPM
CCNC
The time in the IOP:TA is clocked by the CCG. The applicable time can be entered
during commissioning per command from the operator. This does not apply if a radio
clock (Radio Clock Device RCD) is connected to the IOP:TA. In this case the time in
the IOP:TA is always adjusted to the radio clock time.
IOP:MB
CCNP
0
CCNP
1
MOD
IOP:UNI
MDD
IOP:MB
MTD
IOP:MB
MB
0/1
BCT
IOP:MB
SI EMENS
NIXDORF
IOP:MB
CCG
0/1
Data lines
(V.24/V.28, X.21/V.35
IOP:MB
IOP:UNI
IOP:TA
MOD
MDD
IOP:TA
Radio
Clock
Device
MTD
BCT
SYPC
IOP:MB
Alarm
Input
Alarm
Output
Profibus
SYPC or
Profibus
CT
SIEMENS
NI XDORF
IOP:MB
Data lines
(V.24/V.28, X.21/V.35
B:IOC1
IOP:MB/PB
IOP:LAU
Connection
of data lines
(X25LINK)
IOP:MB/PB
IOP:LAU
B:IOC0
IOC0
IOC1
B:CMY0
B:CMY1
Fig. 40
SN2010EU13SN_0002
2002 Siemens AG
89
Siemens
90
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SN2010EU13SN_0002
2002 Siemens AG
91
Siemens
8.1
For the CCS7 signaling between exchanges, the individual signaling messages
(MSU) are transmitted on the central signaling channels. These signaling channels
are called signaling links. They generate an independent signaling network in an
ISDN next to the user channel network. In this signaling network the individual
exchanges function as Signaling Points SP. Each signaling point is identified by its
Signaling Point Code SPC .
User channel- and signaling networks use the same PCM transmission routes
between the exchanges. Whether a 64kbps channel is used on a PCM route as user
or signaling channel must be administered in the database of the exchanges.
92
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SP
MSU
SP
MSU
PCM
PCM
PCM
MSU
SP
SP
Message
Transfer
Part MTP
MSU
MSU
MSU
User
User
SP
MSU
ISUP
ISUP-Trunk
PCM
PCM
User
ISUPTrunk
User
(here ISUP)
User
Signaling Point
Message Signal Unit
ISDN User Part
SN2010EU13SN_0002
2002 Siemens AG
93
Siemens
The users of this signaling network are the LTG in the EWSD. In the GP of the LTG,
the CCS7 user part software (with ISDN, CCS7ISUP) is responsible for the
generation/evaluation of the MSU (Level 4 of the CCS7).
The CCS7 message transfer part (MTP) handles the transfer of the MSU between
the users in two exchanges. It comprises:
l
the physical signaling network established by the signaling links (level 1 of the
CCS7)
the control of the signaling network, with EWSD the common channel network
control CCNC or the Signaling System Network Control SSNC (level 2 and 3 of
the CCS7). The CCNC/SSNC thus generates the link between the users (LTG) of
the CCS7 and the signaling links.
94
Error control of the MSU on the signaling links against transmission errors and
monitoring of the signaling network (level 2 of the CCS7)
Selection of the signaling link when sending an MSU to the partner exchange
(level 3 routing)
Test of whether an MSU received via a signaling link is specifically for a user of the
own exchange or whether the MSU must be relayed to another exchange (level 3
discrimination)
Distribution of an MSU received via a signaling link to the users concerned (LTG)
(level 3 distribution)
SN2010EU13SN_0002
2002 Siemens AG
Siemens
EWSD
Partner Exchange X
PCM routes
to the partner
exchanges
LTG
CCS7/ISUP
level 4
LTG
CCS7/ISUP
level 4
CCNC/SSNC
MTP
level 2 & 3
Partner
Exchange Y
CCNC/SSNC
Protection of the transport of the MSU
Routing of the MSU to be sent
Discrimination of the received MSU
Distribution of the received MSU
to the LTG concerned
Fig. 42
SN2010EU13SN_0002
2002 Siemens AG
95
Siemens
8.2
8.2.1
96
SN2010EU13SN_0002
2002 Siemens AG
Siemens
PCM
Signaling
Link
LTG
SN0&1
SDC:LTG
CCS7 / ISUP
Trunks
LTG
PCM
NUC
SDC:LTG
CCS7 / ISUP
CCNC
SDC:CCNC
CCS7
Level 2
&
Level 3
MB
SDC:TSG
Message
Channel
Message Channel
of all LTG
CP
SN2010EU13SN_0002
2002 Siemens AG
97
Siemens
8.2.2
The functional units of the CCNC are divided into three groups:
l
Per signaling link an own module for carrying out the error control of the
transmission (SILTD, maximum 254), 8 SILTD each are merged into one SILT
group and have a common interface to the duplicated CCNP
Duplicated unit for carrying out routing, discrimination, and distribution including
the interface to the CP (CCNP0 and CCNP1), work in active/stand-by mode)
The fitting-out of the multiplex system and the number of the SILTD's depends on the
number of signaling links that are connected to this CCNC.
98
SN2010EU13SN_0002
2002 Siemens AG
Siemens
CCNC
S
I
L
T
D
S
I
L
T
D
S
I
L
T
D
SILT-group 0
SILT-group 31
CCNP 0
CCNP 1
to 2 IOP:MB of the CP
Fig. 44
SN2010EU13SN_0002
2002 Siemens AG
99
Siemens
8.3
8.3.1
In the EWSD powernode the SSNC takes over the control of the SS7 network instead
of the CCNC. Here the SSNC can be used as signaling end or signaling transfer
point:
l
interface between the signaling network and the user programs in the LTG's
(Signaling End Point SEP function)
transfer from SS7 MSU without relaying to the user in the same exchange
(Signaling Transfer Point STP function)
The SSNC fulfills, like the CCNC, the so-called SS7 Message Transfer Part MTP
functions (discrimination, distribution, routing and message back-up).
Furthermore the SSNC can also take over the tasks of a SCCP Relay Point SRP
(Global Title Translation GTT for MTP users at non-user channel related SS7
signaling) and can function as a so called Local Number Portability Database Server.
In contrast to the CCNC, the SSNC is equipped with its own O&M interface to the
Netmanager NetM (Ethernet IP interface with Q3 protocol) and with back-up
memories (magnetic disk / magneto-optic disk). Therefore with regard to the OAM, it
is independent of the CP. Thus it is possible to also use the SSNC outside of EWSD
as a stand-alone Signaling Transfer Point STP (product is then called hiS700).
100
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SSNC
Version 15
500,000
100,000
Signaling Links
1500
254
Fig. 45
SN2010EU13SN_0002
2002 Siemens AG
101
Siemens
8.3.2
SSNC Interfaces
direct connection of 2 Mbps PCM transmission routes (E1) with 32 x 64kbps time
slots (Synchronous Transfer Mode STM) where the time slot 1-31 is used
exclusively for 64kbps SS7 signaling channels
(usually used when using the SSNC as stand-alone signaling transfer point STP)
direct connection of 2 Mbps PCM transmission route (E1) with a 2 Mbps highspeed SS7 signaling channel (Asynchronous Transfer Mode ATM)
(usually used when using the SSNC as stand-alone Signaling Transfer Point STP)
102
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SN
Signaling link
Outward LTG
Inward LTG
31 SS7-Links
with 64 kbit/s
or
1 HS -Link
with 2 Mbit/s
SSNC
Level 2 & 3
(MTP)
Message
Channel
OAM
ATM-bridges
(optical)
direct connected E1
exclusively used
for SS7 links
AMP
NetM
MB-D (MBDA)
CP
Fig. 46
SN2010EU13SN_0002
2002 Siemens AG
103
Siemens
8.3.3
Three types of module frames are used for the SSNC. The SSNC racks are
manufactured in the ICN construction, i.e. they are somewhat deeper and wider than
EWSD structure.
ATM Switching Network ASN (2 module frames for ASN 0 and 1)
The ASN is a switch matrix which
l
Main Processor MP
The Main Processors (MP) are the central components of the SSNC. Each MP is
duplicated internally (MPU0 and MPU1). The different MP's fulfill different tasks:
MP:OAM (MP for OAM functions of the SSNC)
The MP:SA is used once in the SSNC and contains interfaces to connect the
Netmanagers NetM (Ethernet), the hard disks (SCSI bus for MDD and MOD ) and
the connection unit for alarm lines ALIB.
MP:SLT (MP for signaling link termination)
Each MP:SLT carries out the MTO tasks of an SS7 network control for maximum
127 signaling channels (depending on signaling traffic) when dealing with SS7
messages (discrimination, distribution, routing and back-up).
The total number of the MP:SLT in the SSNC depends on the signaling
requirement of the network node (maximum 47 MP:SLT).
MP:SM (MP for the SSNC database administration)
The MP:SM is used once in the SSNC. Its signaling manager function serves to
permanently update the SSNC database. This also guarantees that each MP:SLT
always has an up-to-date picture of the signaling database.
MP:STATS (MP for statistics)
The MP:STAT is used once in the SSNC and administers the different SS7
statistics data which are collected in the individual MP:SLT.
104
SN2010EU13SN_0002
2002 Siemens AG
Siemens
LTG
LTG
SS7 Links
(64kbps)
SSNC
LTG
LIC
High Speed
Links (/2Mbps)
DLU
LIC
AMXE
MP:SLT
SN
ASN
MP:SLT
NetM
LTG
MBDA
MP:STATS
MP:SM
MB D
Ethernet
MP:OAM
AMPC
X.25
IOP:MB
CP113C
LIC
MP:SLT
MP:SM
MP:STATS
MP:OAM
MP
ASN
AMXE
NETM
Fig. 47
SN2010EU13SN_0002
2002 Siemens AG
105
Siemens
106
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SN2010EU13SN_0002
2002 Siemens AG
107
Siemens
9.1
The APS comprises all of the software necessary for operating an EWSD exchange;
that is, all necessary programs for the control units of the individual EWSD system
units and the complete database.
The APS software parts relevant for the CP, CCNC and LTG are completely stored
on the on the magnetic disk of the CP. Furthermore, the SW components relevant to
the individual system units are located in the memory of these control units as
resident software. (The SSNC part of the APS of a Powermode is stored on the disks
of the SSNC.)
The database of the APS disintegrates into semipermanent and transient data.
l
The semipermanent data such as the directory number of the subscriber are
entered and changed by the operator via the man machine interfaces. This happens
in the form of man machine language (MML) commands (CP) or Q3 Requests
(SSNC).
The transient data such as the current status of a subscriber (idle or busy) are
independently administered by the control units in the systems units.
The programs of the APS can be corrected by incorporating PATCH commands
during operation. These changes must not be carried out without prior consultation
with Siemens.
Data recorded by the EWSD during operation (e.g. charges or traffic measurement
results) are stored on the magnetic disk of the CP in files. They can be transmitted
and evaluated by the network operator either with copies on magnetic tapes or via
electronic file transfer to a post-processing center. (Same happens to the statistic
data collected and stored in the SSNC.)
The software of an exchange is supplemented by firmware components, which is
stored in EPROM of the individual system units.
108
SN2010EU13SN_0002
2002 Siemens AG
Siemens
Software
Firmware
(e.g. recovery
programs for
the individual
control units)
CODE
Database
Stored in
EPROM of the
system units
Transient
data
Can be
corrected
per patch
Independently
administrated
by the
system
control
(e.g. status
of the
subscriber)
Semipermanent
data
Created by
the operator
per MML
(e.g. DN
of the
subscriber)
Files for
collecting
data
(e.g. charges)
Stored in files
on the magnetic
disks, transfer
to the postprocessing
center possible
Fig. 48
SN2010EU13SN_0002
2002 Siemens AG
109
Siemens
9.2
APS Facts
APS production:
Siemens periodically produces new APS versions with new features. Therefore the
principle scope of features of an APS is marked by its version number.
Such a basic APS does not yet have a database.
The basic APS of a version is then adapted to the needs of any network operator.
The result is a customer APS with the scope of features for the network operator
negotiated by contract. Since this APS is not yet exchange-specific, it also does not
have a database yet.
This customer APS is then delivered as a magnetic tape or a magneto-optical disk
and installed in the individual exchanges (commissioning procedure).
During this procedure, the prepared database in the form of command files is also
installed. Customer APS plus database then form the exchange-specific customer
APS.
APS Upgrade:
If, upon installation of the APS, a first-time start-up is not involved but rather a new
version for an existing exchange. the complete loading procedure is carried out
during normal operation of the exchange. After the new APS is loaded, the switchover to the new APS takes place with only a short interruption (approx. 1 minute) of
call processing. This fast upgrade is achieved by the OSU procedure (OSU=
Optimized System Upgrade). It requires specially sufficiently dimensioned memory in
all LTG..
APS backup
While in operation, backups of the current APS are periodically made. These backup
APS generations are stored both onto the magnetic disks (frozen condition) and
magnetic tapes/magneto-optical disk. If the current APS is destroyed, the CP/SSNC
can start-up again with these backups.
110
SN2010EU13SN_0002
2002 Siemens AG
Siemens
transferred
new
Feature not
purchased by
network operator
SN2010EU13SN_0002
2002 Siemens AG
111
Siemens
112
SN2010EU13SN_0002
2002 Siemens AG
Siemens
SN2010EU13SN_0002
2002 Siemens AG
113
Siemens
The call setup described below refers to analog pushbutton subscribers who are
connected to a DLU. Here the functional units assigned to the calling party are
designated with A and those assigned to the called party with B. The duplication of
the SN is not explicitly taken into consideration in the description of the bi-directional
through-connection of the user channel through EWSD.
1. The calling party lifts the handset, SLCA in A-DLU detects the loop closure, A
SLMCP establishes the call attempt upon querying the SLCA.
2. The A-DLUC notices the call attempt upon the cyclical querying of the SLMCP
and sends a corresponding message to the A-GP in time slot 16 of the PDC.
3. The A-GP determines the class of service and the authorization of the calling
party from its database and selects a time slot on the SDC for the call. Then the
A-GP reports the call attempt and the SDC time slot selected for this call to the
CP via message channel (MCH).
4. The A-GP allocates a channel on the PDC to the call attempt and reports this via
the A-DLUC to the A-SLMCP. This sets the A-SLCA onto this channel. The ASLCA inserts a loop-around for send and receive direction.
5. The A-GP sets its GS for the testing of the speech route between A-SLCA and A
LTG (loop check):
a) Test tone of the TOG is through connected in the A-SLCA direction
b) Receive direction from the SLCA is through-connected to the CR
6. After successful testing:
a) A-GP through-connects the dial tone to the A-SLCA per GS
b) A-SLMCP sets the through-connection of the dial tone to the subscriber in the
A-SLCA on command of the A-GP
c) CR remains connected for the evaluation of the DTMF dialed digits
7. The calling party begins with the pushbutton dialing:
a) CR evaluates the received DTMF tones and relays the dialed digits to the AGP
b) GP switches off the through-connection of the dial tone in the GS after
receiving the first digit
c) GP picks up the dialed digits and sends the complete called partys directory
number to the CP via message channel
8. The CP locates the port (DLU/SLMA/SLCA) of the called party from the dialed
digits and checks whether it is idle. If this is the case, the status of the called
party is changed in the database from idle to busy.
114
SN2010EU13SN_0002
2002 Siemens AG
Siemens
9. The CP selects the B-LTG and the time slot on the corresponding SDC and
reports this to the B-GP via message channel. The A-GP is also notified of the
number of the selected B-LTG.
Furthermore the CP transfers the command for setting the through-connection of
the call between A and B LTG to the SGC. The SGC sets the concerned modules
of TSG and SSG accordingly.
10. The A-LTG arranges for a test of the SN through-connection between A-GS and
B-GS (cross office check COC) on command of the CP.
11. When the COC is successful:
a) The A-GP sets the GS through-connection between the time slots selected for
this call on the PDC to the A-DLU and the SDC to the SN.
b) The A-GP notifies the B-GP that the COC was successful via message
channel.
12. The B-GP:
a) Selects a channel on the PDC and notifies the B-SLMCP of this via the BDLUC. The B-SLMCP sets the B-SLCA accordingly (loop-around from receive
and send direction).
b) Carries out the loop check (see 5.)
13. After a successful loop check:
a) The B-GP sends the command for ringing via B-DLUC to the B-SLMCP. This
arranges for the creation of the ringing current.
b) The B-GP sets its GS to the through-connection of the TOG ring-back tone to
the calling party. The ring-back tone is relayed via the through-connection to
the A-SLCA set in the SN and A-GS and from there is relayed to the calling
party.
14. If the called party lifts the handset (answering):
a) The B-SLCA detects the loop closure and the B-SLMCP switches the ringing
current off.
b) The B-DLUC recognizes that the called party has answered upon cyclical
querying of the B-SLMCP and notifies the B-GP of this.
15. The B-GP:
a) Switches off the through-connection of the ring-back tone in its GS.
b) Sets the through-connection between the time slots selected for this call on the
PDC to the B-DLU and the SDC to the SN in its GS. The calling party and the
called party can now speak to one another.
c) Notifies the A-GP of the start of the call via message channel. This begins with
the metering.
SN2010EU13SN_0002
2002 Siemens AG
115
Siemens
116
SN2010EU13SN_0002
2002 Siemens AG
Siemens
A-DLU
SN
SLMA
A-LTG
PDC
a/b
SLCA
16
DIUD
Calling party
TOG
DIU
SDC
MCH
GS
SLMCP
GP
CR
DLUC
B-DLU
SLMA
a/b
SLCA
DIUD
Called party
TSG/
SSG
B-LTG
PDC
16
TOG
DIU
SDC
MCH
GS
SLMCP
GP
CR
DLUC
MB
CP
SDC
...
MCH
of the
A-LTG
MCH
of the
B-LTG
SGC
CP
CR
DIU
DIUD
DLU
DLUC
GP
GS
LTG
MCH
Coordination processor
Code receiver
Digital interface unit
Digital interface unit for DLU
Digital line unit
DLU control
Group processor
Group switch
Line trunk group
Message channel
MB
SGC
SLCA
SLMA
SLMCP
SN
SSG
TOG
TSG
Message Buffer
Switching network control
Subscriber line circuit analog
Subscriber line module analog
Processor for SLMA
Switching network
Space stage group
Tone generator
Time stage group
Fig. 50
SN2010EU13SN_0002
2002 Siemens AG
117
Siemens
118
SN2010EU13SN_0002
2002 Siemens AG
Siemens
11 Exercise
SN2010EU13SN_0002
2002 Siemens AG
119
Siemens
120
SN2010EU13SN_0002
2002 Siemens AG
Siemens
Exercise
Title:
Objectives:
Pre-requisite:
None
Task
Answer the questions on the next page!
SN2010EU13SN_0002
2002 Siemens AG
121
Siemens
Questions:
Answers:
122
SN2010EU13SN_0002
2002 Siemens AG
Siemens
12 Solution
SN2010EU13SN_0002
2002 Siemens AG
123
Siemens
124
SN2010EU13SN_0002
2002 Siemens AG
Siemens
Solution
Title:
Objectives:
Pre-requisite:
None
Task
Answer the questions on the next page!
SN2010EU13SN_0002
2002 Siemens AG
125
Siemens
Questions:
Answers:
DLU
How many LTG (max.) can be connected to an SN with 252, if no CCNC is being
4 TSGs per switching network?
used
Which double faults lead to a failure of the CP113?
CCNC or SSNC
LTG
126
DLU
LTG in B function
LTG in C function
LTG in B function
SN2010EU13SN_0002
2002 Siemens AG