ewsd_v16.0

Overview of EWSD V16.0

Bharti Infotel Ltd,

(Long Distance Group)

Comparison between EWSD CLASSIC & POWERNODE

Bharti Infotel Limited

Hardware Configuration

Software Version

Max traffic Capability

BHCA

EWSD CLASSIC with CCNC with SN A/B with RSU

(only V14A/V15)

V11/ V12/ V13A/ V14A/ V15

Up to 25000 Erl More than 1000000

EWSD PowerNODE with SSNC with SN D with RSU

(only V15)

V13T/ V15 Up to 100000 Erl Up to 4000000

Functional units - EWSD Powernode

SND

LTG

LTG

LTG

LTG

DLU

SSNC

CPMax. 10 CAP

MBD

AMP IOP:MB

64 kbpsTrunks & SS7 Links

64 kbps orHigh SpeedSS7 Links

NetM


Hardware Overview• SN Version D (instead of SN A/B)

Connects up to 2016 LTG’sThrough connects message channels to MBD

• MB Version D (instead of MB B)Distributes the message flow CP-LTG, CP-SND, SSNC-LTG and LTG-LTG

• Netmanager (NetM) (instead of BCT or NodeCommander)Serves Locally and centrally operate and monitor EWSD Powernode

• Signaling System Network Control (SSNC)(instead of CCNC)Ensures security, message distribution and message routing of SS7 messages. The 64kbps signaling channels in the external PCM30 systems connected to the LTG’s are connected to SSNC via SN and so-called inward LTG’s.Supports direct 2Mbps links (with either 31 x 64kbps SS7 channels or a 2Mbps SS7 channel-high speed link with ATM protocol.

• Coordination ProcessorHigher BHCA, as messages are exchanged internally between LTG-LTG and LTG-SSNC directly from MB D and hence the CP is not loaded. Can be equipped with Max of 10 CAP’s.


EWSD V15Powernode Vs Classic


0-1

0-63

1-1

1-63

30-1

30-63

31-1

31-63

0

15

MBDH 0MBUL:LTG

0-0

SN MUX

SN D

MB D

LTG

MBUL:LTG0-1

MBUL:LTG0-2

MBUL:LTG0-3

MBDH 7MBUL:LTG

0-28MBUL:LTG

0-29MBUL:LTG

0-30MBUL:LTG

0-31

01

63

6465

126

01

6364

65

126

…

… …

EWSD V15 Powernode

0-1

0-63

1-1

1-63

6-1

6-63

7-1

7-63

MBUL:LTG0-0

TSG

SN B

MB

LTG

MBUL:LTG0-3

MBUL:LTG0-1

MBUL:LTG0-2

MBUL:LTG0-4

MBUL:LTG0-5

MBUL:LTG0-6

MBUL:LTG0-7

0

1

63

01

63

01

630

1

63

… …

EWSD V15 Classic

0-0

SGC0-1

SGC

0-6

SGC0-7

SGC

MML-Changes to LTG Addressing

a)EWSD V15 with SNB:

The <ltgset> represents the TSG to which the LTG is connected. Its range depends on config of SNB:

SNB for 126 LTG => <ltgset> = 0..1



b)EWSD V15 with SND:

The <ltgset> represents the SNMUX (0..15), to which the LTG is connected. As 126 LTG’s can be connected to each SUMUX, the identifier for <ltg> is counted from 1..63, two <ltgset> values are allocated to each SNMUX.

<ltgset> = 0 and 1 represent both SUNMUX 0.

<ltgset> = 2 and 3 represent both SUNMUX 1…. etc until

<ltgset> = 30 and 31 represent both SUNMUX 15

Old Format of parameter LTG:

LTG = tsg – ltg

wheretsg: 0…7ltg: 1…63

New Format of parameter LTG:

LTG = ltgset – ltg

whereltgset: 0…31ltg: 1…63


Effects of LTG Addressinga) Changes to all MML commands containing the parameter LTG.

b) Changes to AMA records:Connection ID in AMA record is only unique for one day.In the AMA Package 11 bits are used for LTG number instead of 9 bits.

c) Important Restriction in V15LTG with <ltgset> = 8…31 can only be used for Trunks (Type = C or D)DLU, PBX, ANLN and V5LINK can be connected only to the first 504 LTG of an SN


MML-Changes to Trunk Port Addressing

Old Format of parameter EQN:

EQN = tsg – ltg – ltu – channelwhere tsg : 0…7 ltg : 1…63 ltu : 0…7 Channel :0…31

New Format of parameter LTG and LC:LTG = ltgset – ltg, LC = ltu – channel whereltgset : 0…31ltg : 1…63ltu : 0…7channel : 0…31

a) In EWSD V13:

EQN = <tsg> - <ltg> - <ltu> - <channel>

e.g. CR TRUNK:…., EQN=1-10-0-1;

b)In EWSD V15:

LTG = <ltgset> - <ltg>, LC = <ltu> - <channel>

e.g. CR TRUNK:…., LTG=1-10, LC=0-1;


Effects of Trunk Port Addressing

a) The following applies to the MML command CRNUC:

The parameters NUC, TYPE, BCIC, BCOG, TYPE and FEAT are not changed

The parameters EQNIC/EQNOG have been transferred to the new parameters LTGIC & LCIC and LTGOG & LCOC.

b) The transfer of EQN/NEWEQN in LTG & LC and NEWLTG & NEWLC applies to the MML command MOD NUC for trunk ports analogous to CR NUC.

c) The transfer of EQN in LTG & LC applies to the MML command DISP NUC for the trunk ports analogous to CR NUC.


Expansion of Maximum Number of Trunks in EWSD

Conditions for the usage of the increase of trunks

a) The setup supporting 262163 trunks/exchange, installed with SN D, configured to be a pure transit exchange.

b) EWSD with SN B, cannot be configured to support 262163 trunks, as the number of the maximum connectable LTG’s does not increase.

SW changes needed for the usage of the increase of trunks

a) Expansion of all “CP trunk-related tables” with fixed size to 262136.

b) Expansion of “MTP High Performance Database HPDP” of the Message handler in the SSNC to 262136 SS7 trunks.

c) Expansion of “Trunk Index” from 2 to 3 bytes.

d) Expansion of the “ODAGEN expandable trunk related tables”, block factor increased from 1 to 4.


Expansion of Number of Trunks per Trunk Group

The present maximum achievable value of 4095 trunks per trunk group is increased to 16383.

Conditions for the usage of the increase of trunks

a) Should be capable of handling 14 bits for CIC instead of 12 bits, as the number of trunks in an SS7-ISUP is more than 4095.

b) SN D needed instead of SN B, as it is restricted to 65534 trunks.

SW changes needed for the usage of the increase of trunks

a) The “syn-constant” OVTGBPO, which determined the maximum number of trunks per trunk group, is increased from 4095 to 16383.

b) The value range of the MML parameter LNO to determine the line number of a trunk within its trunk group is expanded to 1….16383


Extending of CIC Parameter in ISUP Messages

With the usage of SSNC, the number of user channels between two exchanges can be increased from 4095(CIC=12 bits) to 16384(CIC=14bits)

EWSD internal control of the number of the usable CIC bits per partner exchange (DPC) via the new MML parameter CICSIZE of the command CR C7USER1. CICSIZE=12, ie CIC consists of 12 bits

=>CIC value range:0-1…127-31 => max.4095 trunks between 2 exchange2. CICSIZE=13, ie CIC consists of 13 bits

=>CIC value range:0-1…225-31 => max.8191 trunks between 2 exchange3. CICSIZE=14, ie CIC consists of 14 bits

=>CIC value range:0-1…511-31 => max.16384 trunks between 2 exchangeMML Command1. CR C7USER:USNAME=ISUP, DPC=dpc, NETIND=NAT0, PCMTYPE=DIU30,

CICSIZE=CIC12 or CIC13 or CIC14;

2. CR TRUNK: TGRP=tgrp, CIC=Digital_interface_unit_number-channel number;Digital_interface_unit_number= 0…127 if CICSIZE =CIC12

0…255 if CICSIZE =CIC13channel= 0…31 0…511 if CICSIZE =CIC14

Note:The setting of CIC must be same in both the partner exchanges Bharti Infotel Limited

Enhancement of the MML command STAT TRUNK

MML Command, STATTRUNK when given with the parameter “SUM”, gives

the overview about the amount of trunks with certain trunk status.

If the command STATTRUNK is entered with new parameter STATSUM=YES the

new output mask “TRUNK STATUS SUM OVERVIEW” is displayed instead of

the standard output mask “TRUNK STATUS LIST”

MML Command STATTRUNK :TGNO=, …… STATSUM=<Y or N>

Following are the 7 different trunk status groups:>BUSY INCOMING>BUSY OUTGOING>BUSY INTERNAL>BUSY NON VOICE>BUSY NUC>IDLE>OTHER


Modification of the GCOS Values PRIOPRE/PGRPPRE via

ENTRTGDATVERSION 16 gives the freedom of changing of GCOS values from PRIOPRE to

PGRPPRE or vice versa, using the MML command ENTR TGDAT

TGRP with

. TGNO = BBRCN,…,

.GCOS = CC&IUP & …& PRIOPRE

modified because

of request by e.g.

partner exchange

TGRP with

. TGNO = BBRCN,…,

.GCOS = CC&IUP & …& PGRPPRE

Up to V13:.cancellation of all trunks.cancellation of all routes the TGRP used for.cancellation of C7TGREL.cancellation of the TGRP.Recreation of TGRP, C7TGREL, trunks & routes

After V14a:.ENTR TGDAT:TGNO=BBRCN, GCOS=PGRPPRE;


Selection of a Signaling Protocol Variant by new TGRP-Parameter

SIGVARTrunk group specific assignment of a signaling variant in V13

1. CdPA of the IAM restricted to max. 16 digits (according to ISUP92) GCOS = USVERS0

2. CdPA of the IAM restricted to max. 24 digits (according to ISUP97) GCOS = USVERS1

3. Application of ISUP 767 Assignment of the according PROTTAB to the TGRP

Trunk group specific assignment of a signaling variant in V14A

1. CdPA of the IAM restricted to max. 16 digits (according to ISUP92) CR TGRP:…,SIGVAR=VAR0; MOD TGRP:…,NSIGVAR=VAR0;

2. CdPA of the IAM restricted to max. 24 digits (according to ISUP97) (N)SIGVAR=VAR1;

3. Application of ISUP 767 (N)SIGVAR=VAR15;


Circuit Supervision with ISUP Message UCIC

What is UCIC?

If an exchange receives a CCS7 ISUP message related to trunk which is not known

in the exchange database, it may send back an Unequipped Circuit Identification

UCIC is sent in response to following messages (not supported in EWSD exchanges)

1. Circuit Supervision message 2. Initial Address Message 3. Continuity Check Request

Exception: The messages Circuit Group Query (CQM), Circuit Group Query Response

(CQR) and a UCIC message itself referring to an unequipped CIC are not acknowledge

by a UCIC message2.

Receipt of a UCIC message (supported in EWSD V14A)

EWSD.Set trunk status:MOBB.rerouting or.release

NON EWSD

CIC not equipped

IAM,CCR or circuit supervision msgexcept CQM/CQR

UCIC

TS 0 TS 1 TS 3TS 0 TS 1


Solution for AmbiguousCode Points

The CP digit translation allows the creation of 2 code points CPT with different results, whereas the CODE of one CPT is 100% part of the CODE of the other CPT:

Example:

.CPT = 0802 DEST = CITY

.CPT = 08027 DEST = RURAL

All call setups with dialed digits starting with 08020, 08021, 08022… 08026, 08028, 08029 is translated with the result DEST=CITY.

All call setups with dialed digits starting with 08027 is translated with the result DEST=RURAL

Extended Solution for Ambiguous Code points in V16:

The new ambiguity feature offers the possibility of having called party addresses, whereas the code

of one CdPA is to 100% part of the code of an other CDPA. The result of the CP – digit translation

depends here additionally on the number of the dialed digits.

The new optional parameter AMBIG is used in the commands CR/MOD/DISP CPT.

The default value is NO


Alarming of NUC Failures

User Interface of the NUC Alarming:If a NUC failure is detected, following two measures are performed automatically:> LTG Alarm at the System Panel Display> Alarm message at OMT/BCT.

Administration of NUC Alarming:> The new parameter ALPROF of the commands CR/MOD NUC is used to assign an alarm profile to a NUC:CR/MOD NUC:…., ALPROF=MINESC,MAJNOESC/MAJESC/CRITICAL

> Beside the normal handling of an alarm messages (DISP/SRCH ALARM) the new parameter ALINFO of the command DISP NUC may be used display for one, several or all NUC the related alarm specific data:DISP NUC:…., ALINFO = YES/ NO(Default)


New Procedure for Reactivation of Nailed UP Connections after

failures

NUC in UNA eg, because of

recovery

First NUC activationAttempt with no success

Second NUC activationAttempt triggered by

NUCAUDIT with success

AuditInterval uo to

30min

NUC in UNA eg, because of

recovery

First NUC activationAttempt with no success

NEW NUC REACTIVATION PROCESS(tries up to 10 times to reactivate)

NEW NUC reactivation timer(5 * 30 sec, then 5 * 60 sec)

NUC reactivation in V13

NUC reactivation in V14A


Enhancement for Testing of ISDN - NUC

When a NUC failure occurs and the NUC is connected via several exchanges it is very difficult to verify the location of the NUC problem

For this purpose it is possible to activate in one of the different involved EWSD exchanges a test loop on a port of the failed NUC. Such a test loop is activated with ACT TESTPATH and loops the incoming and outgoing transmission direction in the concerned NUC port. Prerequisite: Affected NUC should be in STATE=ACT and has the TYPE=TEST.

For measuring the Bit Error Rate, a test equipment (K3000) has to be connected to one end of the exchanges of the failed NUC.


Improved Functionality ofDISP CHAREC

> New UNREL Parameter of DISP CHAREC

It reduces the time taken for retrieving the Call Data Records, by offering feature of restricting the search area to the unreleased part of a Cyclic file

> New FILEOUT Parameter of DISP CHAREC

It enables the possibility to copy the tickets to a binary file, which fulfill the search criteria of the DISP CHAREC commands.


Optional Modifications of CDR

New AMA Package 198

• Activated by ENTRCDTDAT: REC= , EXTNSD=REFINDUR

• Relevant for

REC = AMA / DEB / IACAMA / INAMA / MDR / MOB or PMOB

• Substitutes packages:

100 (DATE/TIME/DURATION)

134 (DURATIONs BEFORE ANSWER)

• Appears always together with package 116 (DATE/TIME)

Example of a DISP CHAREC printout in case of using the refined duration measurement: DURATION IN 100MS : 35

The current duration of the call was therefore 35 x 100ms = 3.5 seconds


Time Stamp Implementation in the AMA Data Records in V16By using the MML command ENTRCDTDAT, the AMA Data Records can be generated with time stamp of accuracy of 1/10th of a second

ENTR/CAN CDTDAT: REC = AMA, EXTNSD = TIMETNTH;

- TIMETNTH:

- Timestamp includes tenth of seconds.

- The parameter value TIMETNTH is not set by default

If it is not set, the timestamp is registered in seconds.


Selective Display of Tariffs and Tariff Switchovers


V15 gives the freedom to display the list of all Zone numbers that are affected by the modification of a particular tariff.

Possible parameter combinations for DISP TAR & DISP TARSW in V15

DISP TAR: ZONO= ;

DISP TAR: NAME= ;

DISP TAR: NAME= , FORMAT= ;

NEW: DISP TAR: ZONO=X, NAME=<tariff name>;

O/P=>Selective display of all ZONEs which use the tariff as current tariff

DISP TARSW;

DISP TARSW:ZONO= ;

DISP TARSW: WDCAT= ;

DISP TARSW: DATE= ;

NEW: DISP TARSW: ZONO=X, NAME=<tariff name>;

O/P=>Selective display of all ZONEs which contain a tariff switchover to this tariff

Expanded ENTR TIME / DISP TIME Command


Enhancements for ENTR TIME

In V15, using the ENTR TIME command, in addition to date, weekday and time, the OFFSET in relation to GMT and the SEASON can also be specified.

• The command can only be inputted, if the system time is in MODE=INSECURE, which can be set using MOD TIME , if RCI is not available or the RCI is in OST+UNA/PLA/UNKNOWN)

• All the 5 parameters must always be inputted for each ENTR TIME command

ENTR TIME:

DATE=y-m-d,

TIME=h-m-s,

WD=MO, TU, WE, TH, FR, SA, SU (single value)

OFFSET= min-pos or neg (Ex: 780-neg means an offset of 780 minutes to the west of Greenwich Meridian)

SEASON: STD, DST (single value)

(STD-Standard time, DST-Daylight Saving Time)

Powernode-specific HardwareMBD


MBD has less space demand: In an expansion step with 504 LTGs the number of frames are reduced from 8 to 2 and the number of modules from 104 to 8

Fulfills following system requirements

• System expansion up to 2016 LTG

• Interface to AMX (ATM Multiplexer) of SSNC over ATMB (ATM Bridge)

• Higher performance in message in message throughput.

The real advantages of the MBD can only be realized when used together with an EWSD POWERNODE(V13T or V15 with SSNC)

Powernode-specific HardwareSN D


Provides following improvements

• Connection of up to 2016 LTGs

• Allow small configurations up to 63 LTGs

• Non-blocking design with no path hunt required for single and multi channel connection

• Interworking with MBD only

• Interworking with LTGA up to LTGN and RSU

• Supports 128 kbits/s message channel

• Speech path supervision

SND uses new switching principle based on a single-stage switching matrix. Here the “Time-Space-Time” structure is no longer used. It’s been duplicated.

Powernode-specific HardwareSSNC


Features:

• MTP route Verification Test

• Multiple SS7 Networks (Max. of 32 routing domains in a network, 1500 signaling links, 4096 DPCs)

• SS7 Screening (SS7 message accounting & account verification)

• High Speed Links (64kbps to 2Mbps)

• Number Portability

• Multiple OPC (Max of 255 OPCs)

• Loadsharing via four Link sets

• Handling of UCIC messages

It requires CP113C as coordination processor. Connection to CP113C is via a new CP processor called AMP. The signal channels are supplied by means of PCM30/24 via LTGs or directly by the network. Communication with users in the LTGs is provided directly via high-speed interfaces over MBD.It has its own platform, which is operated on V24/LAN interfaces for the connection of Net Manager.

Powernode-specific HardwareLTG P / STMI


LTGP as successor to LTGN

One-to-four relation is established with new HW module GPP in LTGP

Each GPP module provides

• 4 * 4 PCM30 as external interfaces with 8 PCM30 interfaces combined in one cable

• 4 * SDC for SN0 and SN1 with

- 4 SDC is combined in one cable (for SNB)

- 16 SDC is combined in one optical interface (for SND)

STMI as variant of the LTGP

Provides STM-1 connectivity with other network nodes.

Each STMI system consists of

• 4 * GPS modules (variant of the GPP) where in PCM30 interface is replaced by STM1

• 1 * SDH multiplexer STM1I

The STM1I consists of 2 modules and hence functions in redundant mode

Instant checks after Version Upgradation

BNGLR/BTNLBGL/INDCPZ1V16312300/013 04-05-18 03:15:422097 CA RIGESH 3069/00007

STATTRUNK:TGNO=BBTSOL&BLIDO,STATSUM=Y; EXEC'D

BNGLR/BTNLBGL/INDCPZ1V16312300/013 04-05-18 03:15:432097 CA RIGESH 3069/09830TRUNK STATUS SUM OVERVIEW

TGNO STATUS SUM------+---------------+-------BBTSOL IDLE 455BBTSOL OUT 1BBTSOL INC 2END JOB 20972098


DISPNUC; EXEC'D

NUC TYPE STATE LTGIC LCIC LTGOG LCOG FEAT-------+----+------+------+-----+------+-----+-------TATA1 MUX ACTIVE 3- 1 0-16 0- 1 0- 3UMS01 MUX ACTIVE 1-16 0-16 0- 1 2- 0VSNL MUX ACTIVE 1-16 3-16 0- 1 3- 2WMSJP0 MUX ACTIVE 1-12 0-16 0- 1 2-16WMSJP1 MUX ACTIVE 1-13 0-16 0- 1 1- 1END JOB 2098


DISPTIME; EXEC'D

DATE TIME DAY OFFSET SEASON STATUS RCI-ST04-05-18 03:15:50 TU +0 STD SECURE PLAEND JOB 2099


Overview of EWSD V16E N D

Thank You

ewsd_v16.0

Documents

ltg lc

connectable ltg

ltg ltgset ltgwhereltgset

identiiier ior ltg

eqn tsg ltg

ltg tsg ltgwheretsg

socalled inward ltg

sed ior ltg n