05_sn2073eu01sn_0002_v5_interface_admin

V5 Interface Administration Siemens
V5 Interface Administration
Contents
1 Overview: V5 Interfaces in EWSD 3
1.1 Specifications 4
1.1 Realization of V5.1 Interface in EWSD 6
1.2 Realization of V5.2 Interface in EWSD 10
2 V5 Protocols between EWSD and AN 21
2.1 Overview of Protocols for V5.1 and V5.2 22
2.2 Application of the Protocols for a Call Setup 24
2.3 V5.2: Protection Groups for Vital and Non-vital Protocols 26
2.4 Communication Paths V5CMPATH 28
3 Administration of V5 Interface 31
3.1 Configuration Example V5.2 Interface 32
3.2 Configuration Example V5.1 Interface 42
3.3 Special Aspects of V5 Subscriber Administration 48
4 Exercise 51
5 Solution 55
SN2073EU01SN_0002
1
© 2002 Siemens AG
Siemens V5 Interface Administration
2 SN2073EU01SN_0002
© 2002 Siemens AG
1 Overview: V5 Interfaces in EWSD
SN2073EU01SN_0002
3
© 2002 Siemens AG
1.1 Specifications
With the V5 Interfaces the protocol requirements for the interface between an Access
Network (AN) and the Local Exchange (LE) has been specified for various access
types.
Using the V5.1 or V5.2 interface, it is possible to link to the network node hardware
produced by different manufacturers used for the connection of subscriber lines. The
hardware for connecting subscriber lines is described as the access network (AN).
Both interfaces have a flexible (provisioned) allocation of the information channel
(bearer channel).
The V5.1IF has no concentration capability within the AN and uses only one 2 Mbit/s
link.
The V5.2IF can be used parallel with the V5.1IF and is inherently designed to
concentrate user channels with a dedicated protocol. V5.2IF may use up to 16
(EWSD: 8) 2 Mbit/s links on one interface.
ETS 300 324-1 ETS 300 347-1

2/94 9/94
V5.1 Interface V5.2 Interface
Fig. 1
4 SN2073EU01SN_0002
© 2002 Siemens AG
Supported access types

l analog subscriber (a/b): with and without meter pulses, coinboxes also.
l analog PBXs (a/b) without direct dialing.
l CENTREX, including DSB-ISDN
l semipermanent connections (transparent NUC with 64 kbit/s)
l Euro-ISDN basic access (2B+D, with DSS1 protocol).
l The V5.2 interface enables a permanent packet network access for
subscribers via the D channel on basic access (BA). B channel access
(B0 or B1) is only supported as a transparent 64kBit/s connection.
l (not in EWSD) ISDN primary rate access (PA) and n x 64kBit/s
connections.
l (not in EWSD) permanent 2Mbit/s leased circuits. These are
connected, independently of the V5.2 interface, from the AN e.g. to an
LTGB
Functions of the AN
l Physical subscriber access unit
l Conversion of the analog signaling into PSTN messages (and vice-versa)
l Digit integration for pulse dialing
l Alarm signaling to the subscriber connection modules via Q AN (Q
interface)
l Test equipment for subscriber connection
l Physical activation/deactivation of ISDN BA
Tasks within the network node
l Signaling, including directory administration and metering messages
l Tone generator, pushbutton dialing receivers, announcements
l Control of activation/deactivation of ISDN BA
l timeslot assignment (Bearer Channel Control, BCC)
l Communication channel protection switching
Fig. 2
SN2073EU01SN_0002
5
© 2002 Siemens AG
1.1 Realization of V5.1 Interface in EWSD

The DLUV („virtual DLU“) provides an open interface between EWSD and the access
network based on the V5.1 standard.
The DLUV is based on the previous solution for the 5.1 interface, which is the SLMX
card.
The SLMX card is located in DLUA or DLUB and permits the connection of two V5.1
interfaces. Up to 30 analog subscribers or 15 ISDN subscribers with two B-channel,
can be connected via a V5.1 interface. Package data transmission is supported for a
max. of 32 subscribers .
Of the 32 time slots on the V5link a maximum of 30 are used for user channels. Time
slot 0 is used for frame synchronization, the control protocol runs in the time slot 16
and, unless otherwise defined, the signaling as well. For V5.1 interface at the DLU
channels 15 and 31 can be used in addition to channel 16 as a signaling channel or
as a channel for packet data. These channels (16,15 and 31) are called
communication channels (C-channels). This of course reduces the number of user
channel to 28.
DSS1
signaling
TE
AN
1 ... 14 15 16 17.. 31
TE LE
X.25
data in D
PSTN
Analog
TE
V5.1
Fig. 3
6 SN2073EU01SN_0002
© 2002 Siemens AG
V5 INTERFACE
V5LINK(1)
V5TS(1)............V5TS(31)
used as
BCH or CCH
DEFAULT value for DEFAULT value for V5TS 16
V5TS 1-15 and 17-31
(may be defined with MOD V5TS
for TS 15 / 31)
used as
V5CMCHAN
each V5CMCHAN gets as fixed characteristics:
- a V5CHANID
- list of transported protocols
(allocation of a protocol to a V5CHANID is
done through the object V5CMPATH)
Fig. 4
SN2073EU01SN_0002
7
© 2002 Siemens AG
In comparison to the SLMX in DLUA or DLUB the DLUV brings advantages in cost
and space requirement. It consists of a single module called DLUV which permits the
connection of up to 10 V5.1 interfaces remotely via the module DIUD on the LTG
side or locally via the module LDIB on the LTG side.
The module DLUV is the combination of the central modules of the DLUB: DLUC
(Control Unit), DIU/LDI (Interface Unit), GCG (Clock Generator Unit), BD (Bus
Distribution Unit), ALEX (Interface to external alarms), DCC (Direct current
Converter) and 5 SLMX (Subscriber Line Module X).
For APS-version >11 the DLUV can be created with the new shelf type V. Only the
ALEX function (position 0-11) has then to be configured separately. Packet data
access is given with MOD DLUMOD for the SLMX ports. The virtual SLMX modules
are located in the positions 1-0 till 1-4.
Up to 16 DLUV modules can be plugged into the new frame F:DLUV(A) with the
ordering code S30804-B2730-X. Up to 4 DLUVs can also be plugged into the
F:DLU(G). In this case only the power connection is used and no other connection to
the DLU system exists.
Up to 4800 analog / 2400 digital subscribers are connected to the frame F:DLUV(A).
The new frame is built in two rows employing the SIPAC system. The power
connection is made over the rear connectors. 4 DLUV modules are connected with 1
cable to the fuse panel.
Like a DLUB a DLUV can be connected over a local DLU Interface (LDI) or in case of
remote operation over PCM30 links (120 Ohm symmetrical or 75 Ohm coaxial). The
two different operation modes are distinguished by a bridge connection in the LDI
connectors.
TIP
Each DLUV is connected to an LTG pair by in total 60 (and never 120) speech
channels. These 60 channels are either transported by 2 fully used 2 Mb/s links or by
2 only to 50% used 4 Mb/s links.
8 SN2073EU01SN_0002
© 2002 Siemens AG
EWSD >= V11

V5.1 IF1
D DIU
· acc. to ETSI
·
I or
ETS300 324 and DLUV 0 U
· ITU-G.964 LDIB
D
AN
· V5.1 IF10
· D
LTGx
· I
SIEMENS
NIXDORF
DLUV 1 U
D
Remote:
30 ts, 2Mbit/s
15 ISDN D Local:
or I 60 ts, 4 Mbit/s
DLUV 2 U
30 analog subscriber
per V5.1 Interface D LTGx
V5.1 IF31
DIU
· D or
· I LDIB
· DLUV 3 U
V5.1 IF40
D
SLMX
DLUC
SLMX
DIU:DLU
DLUV SLMX
LDID
SLMX
BD
SLMX
GCG DCC ALEX
Fig. 5
SN2073EU01SN_0002
9
© 2002 Siemens AG
1.2 Realization of V5.2 Interface in EWSD

The V5.2 interface is connected to two LTGM or LTGN via a max. of 8 PCM30-
routes. (EWSD limit)
The AN subscribers are concentrated on the 8 PCM30 routes. The V5.2 is therefore
a concentrating interface (around 8:1) between the connected access network and
the EWSD.
Hardware requirements
CP: CP113, CP113C, CP113CR
MB: MB(B) HW, FW from version V10 or higher
LTG: LTG M/N in B function with 32MB GP memory capacity with high
performance SILC as M:PHMA on the special mounting position of the LTG
M/N (or integrated SILC). Mixed operation of V5.2 interfaces with DLU or PA
on the same LTG M/N is not possible.
Subscriber capacity of a V5.2 in EWSD

with PHMA module:
l up to 2048 analog subscribers, if there are no ISDN subscribers with BA (2B+D).
l no analog subscribers and up to 2048 ISDN subscribers with BA (2B+D)
l every equivalent mixture according to the following formula:
1 x number of analog subscribers + 1 x number of ISDN subscribers <2048
with integrated SILC:
The number of ISDN subscribers is reduced to about 100 for integrated SILC.
Further EWSD limits

for the CP:
maximum 3000 V5 interfaces per exchange (sum of V5.1 and V5.2 interfaces)
maximum 1000 V5.2 interfaces per exchange.
maximum 3500 V5 LINKs per exchange.
maximum 262 140 usable V5 PORTs (subscribers on the ANs)
for the LTG:

maximum 4 V5.2 interfaces per LTG
maximum 4 V5.2 LINKs per LTG
10 SN2073EU01SN_0002
© 2002 Siemens AG
Analog
Analog
subs.
LTG-x
LTG-x SN
SN
subs.
(M
(M or
or N)
N)
Up to 4
Analog
Analog V5LINK
subs.
subs.
M:PHMA
ISDN
ISDN
BA
BA
ISDN
ISDN
BA
BA AN LTG-y
LTG-y
(M
(M or
or N)
N)
Up to 4
V5.1
V5.1 V5LINK
V5.2 IF M:PHMA
transparent
ISDN
ISDN
PA
PA
LTGB
LTGB
Fig. 6 The V5.2 Interface
SN2073EU01SN_0002
11
© 2002 Siemens AG
1.2.1 Configuration Possibilities for V5.2 Interfaces
AN1
LTG
LTG
AN1
AN2
LTG AN3
AN4
AN2
AN1
LTG LTG
LTG AN1 LTG

AN2
AN3
AN2 AN4
AN1
LTG LTG
LTG LTG
AN1
AN2
AN3
Fig. 7
12 SN2073EU01SN_0002
© 2002 Siemens AG
LE
V5.2
LTGM/N 1
SIEM ENS
NIXDORF
HICOM LTGM/N 2
ISDN PA LTG
CMCHAN: active log. communication channel, for signaling between AN and LE
Standby CCH: assumes the function of a CMCHAN in the event of a malfunction
Bearer Channel: available as user channel
V5 LINK: 2 Mb/s route
Fig. 8 Implementing V5.2 interface in EWSD
SN2073EU01SN_0002
13
© 2002 Siemens AG
1.2.2 Rules for V5.2 Connection to EWSD

l The maximum 8 PCM30 routes of an V5.2 interface are called V5LINK and are
distributed between 2 LTGs. A uniform distribution with less than 8 PCM routes is
not necessary. Possible configurations: 1, 2, 3, 4, 5, 6, 7 or 8 V5LINK per V5.2
interface
l Each V5LINK consists of timeslots which are reserved as user channels BCH
(max.31).
l Furthermore, timeslots can be reserved for signaling between AN and EWSD.
Those are called communication channels CCH (max. 3, Time slots 15, 16 and
31).
l An V5.2 interface has a max. total of 8 communication channels.
These must be distributed uniformly between the two LTGs, otherwise the V5.2
interface cannot be activated (verification by CONF V5LINK).
l The max. 8 timeslots, which are reserved as CCH must first be created, without
neglecting uniform distribution in the two LTG, in the timeslots 16 of the
existing PCM30 routes.
If all existing timeslots 16 are already being used as communication channels,
then there a usage of timeslots 15 or 31 is possible (verification by MODV5TS).
l Of the max. 8 timeslots which are defined as CCH half are created as active
signaling channels. Hence, there are max. 4 so-called active logical
communication channels CMCHAN.
Each CMCHAN gets the following characteristics:
V5CHANID: unique identification number within the V5.2 interface
V5CMPATH: list of the communication protocols which pass through
The other CCH are standby and are available for switch over in case of the failure
of a CMCHAN.
At switch over a CMCHAN changes to a CCH, i.e. it changes the PCM timeslot.
The CMCHAN retains all of its characteristics in the process (V5CHANID and
the list of transported protocols).
l The expansion or reduction of the number of communication channels is
possible during operation (be sure to observe the rules regarding the distribution of
communication channels in the LTG and timeslots). The V5LINK concerned must,
however, be blocked for this.
l The expansion of the number of V5LINKs is also possible during operation.
Then It is permitted to use timeslot 16 on this link as a user channel when
timeslots 15/31 of the V5LINKs already available are used together with timeslot
16 as communication channels.
14 SN2073EU01SN_0002
© 2002 Siemens AG
Overview: Objects of the V5 Data Base
V5 INTERFACE
V5 LINK(1)...................................V5LINK(8)
V5TS(1)............................ V5TS(31)
used as
BCH or CCH
DEFAULT value must be defined with MOD
V5TS (max. 3 per LINK on TS
16/15/31, max. 8 per interface)
used as
V5CMCHAN or standby CCH

(max.4 per V5 interface) each For switch over of the V5CMCHAN
V5CMCHAN gets as fixed reserved PCM-TS
characteristics:
- a V5CHANID
- list of transported protocols
(allocation of a protocol
to a V5CHANID is done
through the object V5CMPATH)
These characteristics are retained
during switch over,
i.e. changing of the PCM timeslot
Fig. 9
SN2073EU01SN_0002
15
© 2002 Siemens AG
1.2.3 EWSD Hardware for V5.2 Interface
Rules for the selection of LTGs for the usage of the Report Mirror function
(only important for EWSD Classic)
As is known, the (max.) 63 LTGs of a TSG are connected to SN0 and the SN1
always via two 8Mbit/s routes (SDC). The message channels (timeslots 0) with the
same operational conditions (ACT or STB) are distributed uniformly between both
switching networks for reasons of security in case of failure.
When selecting the two LTGs of an V5.2 interface, make sure that the message
channels (MCH) of both LTGs all have the same operating mode for each MBU:LTG
(ACT or STB). Which LTGs of a TSG fulfill this criterion and therefore form a "V5.2
LTG group", can be derived from the following list. Both LTGs of a V5.2 pair must be
selected from the same "V5.2 LTG group" within a TSG.
"V5.2 LTG group 1":
1, 3, 4, 6, 9, 11, 12, 14, 17, 19, 20, 22, 25, 27, 28, 30, 33, 35, 36, 38, 41, 43, 44, 46,
49, 51, 52, 54, 57, 59, 60, 62
"V5.2 LTG group 2":

2, 5, 7, 8, 10, 13, 15, 16, 18, 21, 23, 24, 26, 29, 31, 32, 34, 37, 39, 40,42,45, 47, 48,
50, 53, 55, 56, 58, 61, 63.
With two LTGs from the same group, it is guaranteed that MBU:LTG REPORT
MIRROR can be used for REPORTs between these LTGs.
This prevents the many REPORTs between the two LTGs of an V5.2 interface
from burdening the interface to CP (IOP:MB).
16 SN2073EU01SN_0002
© 2002 Siemens AG
CP
TSG 0 MBU: LTG 0-0 MBU:LTG 1-0 0 TSG

0-0 1 1 1-0
2 127 0 2
3 3
4 Aktive MCH 4
Active MCH
5 0 127 5
127 0
6 6
63 63
LTG LTG LTG LTG LTG

0-3 0-4 0-5 0-6 0-63
AN
0 31
Fig. 10 Message channel distribution
LTG LTG LTG
DMBU
MCH ACT MCH ACT
MBUL MBUL
with
mirror
function
DMBU =
DMBU = MBU number
MBU number
IOP:MB IOP:MB
CP
(IOCP/
CMY)
Fig. 11 Mirror function of MBUL(C)
SN2073EU01SN_0002
17
© 2002 Siemens AG
Affected Hardware of the LTG M/N

Normally the LTGM/N has to be supplied with the module PHMA to offer enough
capacity for the ISDN subscriber signaling on the V5.2 interface.
If no or only a few ISDN subscribers are connected it is also possible to use the
integrated SILC of the LTG M/N instead of the module PHMA
18 SN2073EU01SN_0002
© 2002 Siemens AG
... with integrated SILC ... with PHMA

Protocol handler module A
D P G G
I H S P
U M M L
A S
SILC integrated on GPLS
module on the free
* new HW
LTGM plug-in position
* special V5.2 FW
Administration of the LTGM for V5.2

CR LTG: LTG=..., TYPE=LTGB, LDPARP=52; LTGM/N for V5.2
CR LTU: LTG=..., LTU= 5, TYPE=INS / PMA; integrated SILC / PHMA
CR LTU: LTG=..., LTU=..., TYPE=D30, APPLIC=V52IF; V5LINK DIUs

PDC characteristics on
V5LINK identical in AN and
LE :CRC4MF
Fig. 12
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SN2073EU01SN_0002
19
© 2002 Siemens AG
20 SN2073EU01SN_0002
© 2002 Siemens AG
2 V5 Protocols between EWSD and AN
SN2073EU01SN_0002
21
© 2002 Siemens AG
2.1 Overview of Protocols for V5.1 and V5.2
Carried on Carried on
Protocol type a separate a separate
(C-Path) Purpose Layer 3 per ... Layer 2 per ...
User Port · activation/deactivation of

Control ISDN-BA Layer 1 (AN-TERM INAL)
... ISDN and PSTN
· block/unblock/block request for PSTN and ISDN-BA user port
... V5
user ports
Com m on · check of (current) provisioning variant and interface interface
Control ID of the
Control V5.1/V5.2 interface
· restart (PSTN))
... V5 interface
Link Control *) · check of Link ID ... 2048 kbit/s ... V5
· link block/unblock/block request for link interface

2048 kbit/s links **)
BCC *) · timeslot assignment/release ... BCC process ... V5 interface
· timeslot audit
Protection *) **) · protection sw itching of 1 comm on Layer 3 2 separate Layer
com munication channels (C channels) per 2 per
V5 interface V5 interface
PSTN · signaling for analog subscribers ... PSTN ... V5 interface

user port
ISDN-Ds-type data · signaling for ISDN basic access not relevant for the ... ISDN term inal
V5 interface ***)
ISDN-p-type data · packet data for ISDN-BA, not relevant for the ... ISDN term inal
(SAPI = 16) V5 interface ***)
*) Not used in case of V5.1 interface.

**) Not used in case of V5.2 interface with a single 2048 kbit/s Link.
***) Up to 8 ISDN terminals per ISDN user port may be possible.
Fig. 13 V5 protocols overview
22 SN2073EU01SN_0002
© 2002 Siemens AG
15 16 31 Timeslot
V5.2
AN LE
PROTOCOL
Control Protocol ISDN-D Protocol

Link Control Protocol
BCC-Protocol PSTN Protocol
Protection Protocol
ISDN-P Data
Port Control Protocol
Fig. 14 Protocols for V5.2 interface
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SN2073EU01SN_0002
23
© 2002 Siemens AG
2.2 Application of the Protocols for a Call Setup

The following example shows the application of the different protocols on a V5.2
interface in case of an originating call setup.
TIP
In case of the V5.1 interface the BCC protocol is not used because for each
subscriber is fixed timeslot assignment is stored in the database of EWSD and AN.
24 SN2073EU01SN_0002
© 2002 Siemens AG
SIEMENS SIEMENS
V5LINK
A-sub.
(ISDN- AN
TE) V5
ISDN-
BA CMCHAN
Signaling between Communication between

ISDN-TE and AN in D-Channel AN and EWSD in V5CMCHAN
(the V5ACCID with the same value in EWSD
and AN is used for the identification
of the subscriber concerned)
Sub. goes off hook: Control Protocol:

Activation of layer 1 Message to LTG (SILC/PHMA):
set up of layer 1 between AN and TE
Setup of layer 2 ISDN-D Protocol:

Transparent layer 2 between TE and LTG
for signaling (DSS1 layer 3)
Layer 3: SETUP ISDN-D Protocol:

LTG processes SETUP message (checks sub.
authorization for the requested service...)
LTG selects free BCH
BCC Protocol:
LTG informs the AN which BCH
timeslot should be used
Result: transparent layer 1 between TE and GS of the LTG for the B-channel
Fig. 15
SN2073EU01SN_0002
25
© 2002 Siemens AG
2.3 V5.2: Protection Groups for Vital and Non-vital

Protocols
In case of a V5.2 interface the different communication channels are assigned either
to the protection group1 or 2. The protection group defines the kind of protection
switching in case of e.g. a link failure.
l CMCHAN with vital protocols (protection group 1):
There is exactly one active CMCHAN and one corresponding standby CCH for the
vital protocols.
For protection switching:
After correction of an error, no switch over back to the previously active CCH.
l CMCHAN with non-vital protocols (protection group 2):
There are just as many standby CCH as CMCHAN for the non-vital protocols
(determined with MML command MOD V5TS). These standby CCH form a pool
for protective switching, i.e. each can be used as a substitute for each failed
CMCHAN from the system.
For protective switching:
After correction of an error, no switch over back to the previously active CCH.
It can also be manually switched over with MOD V5CMCHAN.
26 SN2073EU01SN_0002
© 2002 Siemens AG
Vital protocols (CCH belongs to protection group 1)
Assignment
CCH reserved for: using
MOD V5TS
Non-Vital protocols (CCH belongs to protection group 2)
Fig. 16 Assignments of CCH
Control ISDN - p
BCC ISDN-Ds
Link Control PSTN
Protection
Protection Prot. Group 1 or 2

Group 1
'Vital protocols'
Master Link at Stand By Link

CMCHAN Corresponding
Master LTG at another LTG:
for standby
non-vital CCH:
e.g. TS 16 on e.g. TS 16 on
protocols
LINK 1 at LTGX LINK 2 at LTGY
one CMCHAN one inactive CCH e.g. e.g.
with vital for vital protocols TS 16 on TS 16 on
protocols V5LINK V5LINK
3 and 4 5 and 6
to to
master LTG another LTG
If the CMCHAN fails, then there is
switchover to the replacement CCH (LTGX) (LTGY)
If, for example, the CMCHAN on V5LINK 2 fails,

then there is a switch over to the substitute CCH
("free selection")
Fig. 17 Protection groups
SN2073EU01SN_0002
27
© 2002 Siemens AG
2.4 Communication Paths V5CMPATH

The allocation of a protocol to an active communication channel is done by
creating communication paths CMPATH (CR V5CMPATH).
V5CMPATH
protocol ¾¾¾¾¾¾¾¾¾¾¾® V5CMCHAN
By this, every V5CMPATH gets a V5PATHID
Assignment rules for V5.2 interface:

l Control prot. (common and port) 1x on the CMCHAN which is created on
l Link control prot. 1x on CCH of protection group 1
l Bearer channel control prot. 1x on (TS16 of
l Protection prot. 1x on MASTER LINK)
l ISDN-Ds prot. 4x on any CMCHAN (TS 16/15/31)
l ISDN-P-data prot. 4x on any CMCHAN (TS 16/15/31)
l PSTN prot. 1x on any CMCHAN (TS 16/15/31)
Protection protocol
This protocol is automatically set up by the system on both CCHs of protection
group 1. This way, the AN or the EWSD receives the same switchover instructions
twice during the failure of a CMCHAN of protection group 2, the instruction received
second is ignored.
The two communication paths of the protection protocol both get the V5PATHID 13.
The remaining V5PATHID (0-12) can be made available for the other protocols when
creating the max. 12 communication paths.
Supervision of the standby CCH

As a rule, no protocols run on the standby CCH, which means that the
corresponding messages are always sent and received solely on the CMCHAN. The
supervision of the standby CCH takes place via FLAG-MONITORING.
Exception: Standby CCH of protection group 1 transports the protection protocol.
TIP
For V5.1 interface the vital protocols are automatically assigned to the CCH on TS16.
The PSTN protocol has max. 1 CMPATH (on TS16, or 15 or 31) and the ISDN
protocol has max 3 CMPATH (one on each CCH).
28 SN2073EU01SN_0002
© 2002 Siemens AG
V5.2-Interface: Protection Protection

2 ...8 CCH Group 1 Group 2
physical C-channels
(active and standby) Link1 Link2 max. 6 CCH distributed to:
to LTGx to LTGy Link 3..8: TS16 and
TS16 TS 16 Link 1..8: TS15&31
CMPATH Protection
Switching
PROTECTION act. logical

CMCHAN
CONTROL
LINK CONTROL
BCC
PSTN
ISDN Ds
(group 1)
ISDN Ds
(group 4)
ISDN p-data
(group 1)
ISDN p-data
(group 4)
Fig. 18 Distribution of protocols to physical C-channels in case of V5.2
SN2073EU01SN_0002
29
© 2002 Siemens AG
30 SN2073EU01SN_0002
© 2002 Siemens AG
3 Administration of V5 Interface
SN2073EU01SN_0002
31
© 2002 Siemens AG
3.1 Configuration Example V5.2 Interface

Setting up a LTGM pair
The message channels (MCH) of both LTGs must lead to the same MBU:LTG!
CR LTG: LTG=0-45, TYPE=LTGB, LDPARP=52;
CR LTG: LTG=0-55, TYPE=LTGB, LDPARP=52;
Creating the SILC or the PHMA as LTU 5

The integrated SILC is created with TYPE=INS. The supplementary module M:PHMA
is created with TYPE=PMA.
CR LTU: LTG=0-45, LTU=5, TYPE=PMA or INS;
CR LTU: LTG=0-55, LTU=5, TYPE=PMA or INS;
Creating DIUs for the physical connection

CR LTU: LTG=0-45, LTU=0, TYPE=D30, APPLIC=V52IF;

Creating the V5.2 interface

CR V5IF: V5IF=6054, V5IFID=4444444, IFTYPE=V52, PROVAR=0;
· optional parameter V5TS is used to define the max. number of subscribers per
V5IF (0…2048, default value is 256)
· optional parameter PROTVAR is used to choose between different methods of
port unblocking (single port unblocking (0) or accelerated port alignment (1)) in
case of (re)activation of a V5IF
Creating the V5LINKs (PCM30 systems)

CR V5LINK: V5IF=6054, V5LINK=0-45-2, V5LINKID=1;
Fig. 19
32 SN2073EU01SN_0002
© 2002 Siemens AG
LTG 0-45
V5LINKID1
2
V5LINKID3
3
AN
LTG 0-55
V5LINKID2
0
V5LINKID4
1
2
V5IF=6054
3
Fig. 20
SN2073EU01SN_0002
33
© 2002 Siemens AG
Functional adaptation of PCM channels
MOD V5TS: V5IF= 6054, V5LINKID=1, V5TS=16, USAGE=CCH,

PROTGRP=1;
PROTGRP=1;

PROTGRP=2;
PROTGRP=2;
Fig. 21
34 SN2073EU01SN_0002
© 2002 Siemens AG
Fig. 22
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SN2073EU01SN_0002
35
© 2002 Siemens AG
Creating the logical V5 communication channel

CR V5CMCHAN: V5IF=6054, V5LINKID=1, V5TS=16, V5CHANID=0;
CR V5CMCHAN: V5IF=6054, V5LINKID=3, V5TS=16, V5CHANID=1;
Creating the protocol paths

CR V5CMPATH: V5IF=6054, V5CHANID=0, V5PATHID=0,
PATHTYPE=CNT;
PATHTYPE=LCNT;
PATHTYPE=BCC;
PATHTYPE=PSTN;
PATHTYPE=ISDN, ISDNTYPE=DS;
PATHTYPE=ISDN, ISDNTYPE=P;
Fig. 23
36 SN2073EU01SN_0002
© 2002 Siemens AG
Fig. 24
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SN2073EU01SN_0002
37
© 2002 Siemens AG
Database Objects which are exchanged between AN an EWSD

The data shown beside is exchanged between the AN and the EWSD and must have
the same values in both.
TIP
Also the logical communication channels CMCHAN must be created on the
same timeslots with the same protocols CMPATH and the V5CHANID must be
the same in the AN and the EWSD.
Furthermore, it is important that the standby communication channels (CCH)
reserved for protection switching are also set up on the same timeslots in the
EWSD and the AN.
38 SN2073EU01SN_0002
© 2002 Siemens AG
l V5IFID
l V5LINKID
l V5CHANID
l PROVAR
l V5 ACCID
Fig. 25
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SN2073EU01SN_0002
39
© 2002 Siemens AG
Activation of the V5 Interface and the V5 Port
TIP
The activation of the V5PORTs must be performed in both the AN and the EWSD
40 SN2073EU01SN_0002
© 2002 Siemens AG
Activation of the V5LINKs (LTGs are already ACT)
CONF V5LINK: V5IF=6054, OST=MBL;
CONF V5LINK: V5IF=6054, OST=ACT;
The DIU is configured together with the V5LINK and can not be configured
separately
Activation of the Subscribers in EWSD
CONF V5PORT: V5IF=6054, V5PORT= <0... 2047 or X >, OST=MBL;
CONF V5PORT: V5IF=6054, V5PORT= <0...2047 or X >, OST=ACT;
Fig. 26
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SN2073EU01SN_0002
41
© 2002 Siemens AG
3.2 Configuration Example V5.1 Interface

The diagram shows an example of a V5.1 interface which has to be configured. As
regards hardware, the new DLUV hardware was used in this example. The V5.1
interface comprises 28 data channels (BCH channels) and 3 communication
channels (C channels).
DLUV 10
28 Data channels
(Bearer Channel) virtual
SLMX 0
virtual
SLMX 1
AN
31 30 17 16 15 2 1 virtual
SLMX 2
virtual
SLMX 3
3control virtual
channels SLMX 4
(C-Channel)
Fig. 27
42 SN2073EU01SN_0002
© 2002 Siemens AG
Setting up the Hardware

Because the DLUV is used, the creation commands relate accordingly to virtual
components.
CR DLU:
DLU = 10,
SHELF = V; Creating a virtual DLU (DLUV)
DLUC0= < LTG – DIU for first of the two 2Mb/s or 4 Mb/s links >
DLUC1= < LTG – DIU for second of the two 2Mb/s or 4 Mb/s links >
CR DLUMOD:
DLU = 10,
MOD = 1-2, Creating the third virtual SLMX
SLMXID = 2,
TYPE = SLMX;
Fig. 28
Creating the V5.1 Interface
CR V5IF:
V5IF = 6000, V5.1 interface
V5IFID = 4711, V5.1 interface identification
IFTYPE = V51, Interface type: V5.1
PROVAR = 0; Provisioning variant
CR V5LINK:
V5LINK = 10-2-0; 10 = DLU number
2 = SLMX-ID
0 = PCM system at the virt. SLMX
Fig. 29
SN2073EU01SN_0002
43
© 2002 Siemens AG
Creation of communication channels

l Timeslot 16 is automatically created as communication channel (C channel).
l The timeslots 15 and 31 must be explicitly modified from BCH (data channel) to
CCH (C channel)
ISDN
Packet Data
TE
AN
... 13 14 15 16 17 ... 31
ISDN-
DSign.
LE
PSTN Vital
Analog Protocols
TE
V5.1
Fig. 30
44 SN2073EU01SN_0002
© 2002 Siemens AG
MOD V5TS:
V5TS = 15, Timeslot 15
USAGE = CCH; Used as a C channel
CR V5CMCHAN:
V5CHANID = 1, TS16 autom. has V5CHANID = 0
V5TS = 15;
MOD V5TS:
V5TS = 31, Timeslot 31
USAGE = CCH; Used as a C channel
CR V5CMCHAN:
V5CHANID = 2,
V5TS = 31;
Fig. 31
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SN2073EU01SN_0002
45
© 2002 Siemens AG
Assignment of the protocols

The following commands assign the protocols, which are used on the interface
between the access network (AN) and the EWSD, to the logical control channels.
Several protocol paths can be assigned to a logical C channel.
TIP
Timeslot 16 automatically contains the protocols which are absolutely necessary for
the operation of the V5 interface (the vital protocols).
timeslot V5CHANID protocols

16 0 V5PATHID = automatic:
1 vital protocols
PSTN with V5PATHID = 0
15 1 V5PATHID =
2
ISDN/DS
31 2 V5PATHID =
3
ISDN/P
Fig. 32
ISDN
Packet Data
TE
AN
ISDN-
... 13 14 15 16 17 ... 31
DSign.
LE
PSTN Vital
Analog Protocols
TE
V5.1
Fig. 33
46 SN2073EU01SN_0002
© 2002 Siemens AG
CR V5CMPATH:
V5CHANID = 0, refers indirectly to the timeslot 16
V5PATHID = 1, ID for the following protocol path
PATHTYPE = PSTN;
Fig. 34
CR V5CMPATH:
PATHTYPE = ISDN,
ISDNTYPE = DS;
CR V5CMPATH:
PATHTYPE = ISDN,
ISDNTYPE = P;
Fig. 35
SN2073EU01SN_0002
47
© 2002 Siemens AG
3.3 Special Aspects of V5 Subscriber Administration

V5.2 Subscriber Administration
l V5PORT
In contrast to the DLUPORT for directly connected subscribers, the V5PORT has
only a symbolic equipment number EQN, which is not referring to physical
subscriber line circuit.
Information on a V5PORT is displayed using the MML command DISPV5PORT.
V5 ports with V5.2 V5 interface fixed value 0 logical V5 port no.
EQN = number
Example 6010 0 00 - 22
value range (6000,...8999) (0) (00 - 00 .... 20 - 47)
l V5ACCID
The access ID is used in the signaling protocol between AN and EWSD for
identification of V5 subscribers. Therefore the ACCID for every subscriber must
have the same value in AN and in the EWSD. The ACCID is allocated in EWSD
with the MML command CRSUB using the parameters COSDAT=V5ACCID-
<0....32767> (for ISDN subscribers <0...8175>).
l Preparation (creating the LAC, DN and CPT)
CR DN: LAC=0804, DN=552200&&552299;
CR CPT: CODE=5522, LAC=0804, TRATYP=CPTDN;
l Creating subscribers
Creating subscribers, PBX and PBXLNs at the V5.2 interface V5IF=6054:
CR SUB:
LAC=0804,DN=552202,CAT=IBA,SERV=TEL3K,
EQN=6054-0-0-2, COSDAT=V5ACCID-2&V5DSDAT-4;
TIP
Overview of the use of protocol paths according at V5IF=6054:
1 PSTN PATH (V5PATHID=3) for analog subscribers
1 DS PATH (V5PATHID=4) for ISDN subscribers
1 P PATH (V5PATHID=5) for D channel packet network access
V5DSDAT must always be created, if more than one DS path exists at the V5
interface.
48 SN2073EU01SN_0002
© 2002 Siemens AG
CR SUB / PBXLN for V5.2 subscribers:

* EQN V5IF - 0 - xx - yy
with port address = xxyy
e.g. 6000 - 0 - 20 - 47
* COSDAT V5ACCID - x (0..8175 for ISDN, 0..32767 for analog)

Layer 3 addresses, under which both the
EWSD and the AN recognize the subscriber
&
V5DSDAT - PATHid & V5DSDAT- PATHid
Only necessary if V5IF has more than one
CMPATH for ISDN-DS
Fig. 36
V5.1 Subscriber Administration

l V5ACCID
The access ID is used in the signaling protocol between AN and EWSD for
identification of V5 subscribers. Therefore the ACCID for every subscriber must
have the same value in AN and in the EWSD. The ACCID is allocated in EWSD
with the MML command CRSUB using the parameters COSDAT=V5ACCID-
<0....32767> (for ISDN subscribers <0...8175>).
l V5EQBCH for V5.1 subscribers
Subscribers connected via V5.1 have an additional parameter which specifies the
port in the SLMX module for their user channel (one for analogue and two for
ISDN) on the 2Mbps V5.1 interface.
l V5PORT
Every AN subscriber in EWSD requires his own so-called V5PORT. In contrast to
the DLUPORT for directly connected subscribers, the V5PORT has only a
symbolic equipment number EQN, which is not referring to physical subscriber line
circuit.
Information on a V5PORT is displayed using the MML command DISPV5PORT.
V5 ports with V5.1 V5 interface fixed value fixed value logical V5
EQN = number 0 0 port no.
Example 6011 0 0 3
value range (6000,...8999) (0) (0) (0.1....31)
SN2073EU01SN_0002
49
© 2002 Siemens AG
50 SN2073EU01SN_0002
© 2002 Siemens AG
4 Exercise
SN2073EU01SN_0002
51
© 2002 Siemens AG
52 SN2073EU01SN_0002
© 2002 Siemens AG
Exercise
Title: Functional Structure of V5 Interfaces
Objectives: The participant is able to describe the V5 database objects
Pre-requisite: none
Task
Please answer the following questions!

Query
Question Answer
How many V5 links can max. be created for
l one V5.1 interface
l one V5.2 interface
How many communication channels of one V5.1 interface
can max. carry
l the vital protocols
l the PSTN protocol
l the ISDN DS protocol
can max. carry
l the vital protocols
l the PSTN protocol
the ISDN DS protocol
SN2073EU01SN_0002
53
© 2002 Siemens AG
54 SN2073EU01SN_0002
© 2002 Siemens AG
5 Solution
SN2073EU01SN_0002
55
© 2002 Siemens AG
56 SN2073EU01SN_0002
© 2002 Siemens AG
Solution
Title: Functional Structure of V5 Interfaces
Objectives: The participant is able to describe the V5 database objects
Pre-requisite: none
Task
Please answer the following questions!

Query
Question Answer
How many V5 links can max. be created for
l one V5.1 interface 1
l one V5.2 interface 8
can max. carry
l the vital protocols l TS16 only
l the PSTN protocol l one CCH only
l the ISDN DS protocol l all three TS used as
CCH
can max. carry
l the vital protocols l TS16 of the Master
link
l the PSTN protocol l one active CCH only
l the ISDN DS protocol l 4 active CCH
SN2073EU01SN_0002
57
© 2002 Siemens AG
58 SN2073EU01SN_0002
© 2002 Siemens AG

05_sn2073eu01sn_0002_v5_interface_admin

Uploaded by

Copyright:

Available Formats

You might also like

05_sn2073eu01sn_0002_v5_interface_admin

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

05_sn2073eu01sn_0002_v5_interface_admin

Uploaded by

Copyright:

Available Formats

V5 Interface Administration Siemens

1 Overview: V5 Interfaces in EWSD

ETS 300 324-1 ETS 300 347-1

V5.1 Interface V5.2 Interface

Supported access types

1.1 Realization of V5.1 Interface in EWSD

EWSD >= V11

GCG DCC ALEX

1.2 Realization of V5.2 Interface in EWSD

Subscriber capacity of a V5.2 in EWSD

Further EWSD limits

for the LTG:

Fig. 6 The V5.2 Interface

1.2.1 Configuration Possibilities for V5.2 Interfaces

LTG AN1 LTG

CMCHAN: active log. communication channel, for signaling between AN and LE

Standby CCH: assumes the function of a CMCHAN in the event of a malfunction

Bearer Channel: available as user channel

V5 LINK: 2 Mb/s route

Fig. 8 Implementing V5.2 interface in EWSD

1.2.2 Rules for V5.2 Connection to EWSD

Overview: Objects of the V5 Data Base

V5CMCHAN or standby CCH

1.2.3 EWSD Hardware for V5.2 Interface

"V5.2 LTG group 2":

TSG 0 MBU: LTG 0-0 MBU:LTG 1-0 0 TSG

LTG LTG LTG LTG LTG

Fig. 10 Message channel distribution

LTG LTG LTG

MCH ACT MCH ACT

Fig. 11 Mirror function of MBUL(C)

Affected Hardware of the LTG M/N

... with integrated SILC ... with PHMA

Administration of the LTGM for V5.2

CR LTU: LTG=..., LTU= 5, TYPE=INS / PMA; integrated SILC / PHMA

CR LTU: LTG=..., LTU=..., TYPE=D30, APPLIC=V52IF; V5LINK DIUs

2 V5 Protocols between EWSD and AN

2.1 Overview of Protocols for V5.1 and V5.2

User Port · activation/deactivation of

· link block/unblock/block request for link interface

PSTN · signaling for analog subscribers ... PSTN ... V5 interface

*) Not used in case of V5.1 interface.

Control Protocol ISDN-D Protocol

BCC-Protocol PSTN Protocol

Fig. 14 Protocols for V5.2 interface

2.2 Application of the Protocols for a Call Setup

Signaling between Communication between

Sub. goes off hook: Control Protocol:

Setup of layer 2 ISDN-D Protocol:

Layer 3: SETUP ISDN-D Protocol:

LTG selects free BCH

2.3 V5.2: Protection Groups for Vital and Non-vital

Vital protocols (CCH belongs to protection group 1)

Non-Vital protocols (CCH belongs to protection group 2)

Fig. 16 Assignments of CCH

Link Control PSTN

Protection Prot. Group 1 or 2

Master Link at Stand By Link

If, for example, the CMCHAN on V5LINK 2 fails,