[seminar5]_stm1

8/12/2019 [Seminar5]_STM1

1/66

B11 MR1 Ed1

Seminar of GSM Network EngineeringSTM-1 impact for BSC Evolution

Joo Frade

March 2010


2/66

Agenda

1. Theoretical overview

2. Feature activation & compatibility with previous HW

3. Telecom parameters, counters & Indicators

4. Test strategy

5. R&D system tests results

6. Reference documentation

7. Annex


3/66

Alcatel-Lucent 20103 | B11 STM1 on BSC Evolium | Edition 01 proposal 083 | B10 mCCCH | September 2008

1 Theoretical Overview


4/66

Alcatel-Lucent 20104 | B11 STM1 on BSC Evolium | Edition 01 proposal 08

B11 STM-1 impact for BSC EvolutionTheoretical overview

New transmission solution:

STM-1 connectivity at BSC site

STM-1 STM-1

BTS

BTS TransmissionNetwork

E1

TransmissionNetwork

TC/MFSSite

Up to 4 STM-1

Up to 176 E1 toBTS Sites

E1

Up to 76 E1 toTC/MFS

STM1 (Optical) connectivity4 redundant interfacesAvailable for Abis and A-ter interfacesMix of E1/STM-1 allowed up to 252 E1/VC12

New TP STM1 boardHW readiness for STM-1 introduction on topof B10-MR21 STM-1 can carry up to 63 E1 on VC-12

New TC G2.5 the only NE supporting STM1

B10 MR2B11

Support of STM-1 on Ater interfaces to further minimize bandwidth betweenBSC site and MSC site (also available on Abis)


5/66



BSS in a SDH network / architecture

STM-1 on MxBSC (B11 MR1)

STM-1 on TCG2.5 (B10 MR2)*

* Report of TC STM-1 validation available bellow:


Note: An SDH ring is comprised of anumber of network elements that allowtraffic to ingress, to egress the ring orpass through the ring. This equipment iscommonly referred to as Add/DropMultiplexers or ADM.


6/66



BSS in a SDH network / architecture

The STM-1 interface is an alternative to the TDM transport mode in order to decreasethe cost of the transport in BSS.

This feature is offered only for A9130 BSC Evolution, and 4 STM-1 can be connected onthe front plate of the new TPGSMv3 board.

Each STM-1 link includes 63 channels (VC12 containers) which can include an E1 of 2048kbps, so one STM-1 can carry 63 Abis and/or Ater, each E1 link is transported separatelyon one VC12 container.

The BTS and the MFS are still connected using E1 electrical interface; the connectionbetween MxBSC (STM-1) and BTS/MFS (E1) will be done through SDH network containingequipments for optical-electrical conversion.

A BSC Evolium can be only STM-1, only E1 or mixed.



7/66 Alcatel-Lucent 20107 | B11 STM1 on BSC Evolium | Edition 01 proposal 08

SSW W

R a

d i o N e

t w o r k

l i n

k s

Externa l Ethernet Links

LIU Shelf(21 slots)

E1

CCPy

TPr TPW

MUXW

LIU1

LIUn

ATCA Shelf (14 slots)

CCP1

OMCPw

OMCPr

SSW r

MUXr

r : RedundancyW : Workingn and y : Networ k Element Capa city

TPGSM STM-1 architecture

BSC Evolution (A9130 BSC Terminal) HW architecture reminder


Transmission Processingboard provides telecomtransmission/transportinterfaces to the MXplatform.

Line Interface Unit isresponsible of the physicalE1 connections, i.e. Abis,AterCS and AterPS.

Allows exchanges betweenall the elements of theplatform and externalIP/Ethernet equipment.

Call Control Processingboard is responsible for allthe telecom functions ofthe BSC, except the TCHResource Management.

O&M Control Processing

board is responsible for allthe O&M functions of theBSC and TCH ResourceManagement.




Board connectivity

The optical fiber is connected directly to the TPGSMv3 board and settings/mappingare done with the A9130 BSC Terminal.

With the STM-1 introduction, a BSC Evolium can be delivered without LIU shelf.

TPGSM

E1 Mux

IP

LIU 252 E1

252

252

252

IP/TDM

E1 Mux

STM

TDM switch

TPIP STM1

4 STM1 252

STM1/E1

252

TPGSM STM1

E1 Mux

IP

LIU E1

252

252

252

IP/TDM

E1

Select

STM

TDM switch

TPIP STM1

252

STM1/E1

252





Board connectivity

Each STM-1 interface has two links. One is connected to the active TPGSM and theother one is connected to the standby TPGSM. Only the payload is exchangedbetween the two boards (Active and Standby TPGSM).

The STM-1 mode is unidirectional i.e. the same frame are transmitted in parallel ontwo sections and each equipment selects autonomously the section to be used forreception.

Inside the BSC the selection of the section to be used for reception is performed bythe active TPGSM. Each TPGSM supervises the status of all sections connected to it.

The standby TPGSM reports the status of its sections to the active TPGSM.



10/66



Board connectivity


RX active in service TX working/ protection,in service

RX stand by in service RX, TX out of service


11/66



Automatic Protection Switching function

Due to the high traffic per STM-1 link, protected access is usually used. Protection isdone by automatic protection switching (APS) with one active and one standby link.

Redundancy is obtained:At link level thanks to APS. Solution is unidirectional and non-revertive.At board level thanks to active/stand-by mode TCIF & TPGSM (1+1).The same principles apply to both TC and MxBSC.

VC12 map STM-1port

VC4 STM-1framer/LIU

STM-1framer/LIU

STM-1port

status

standby

APSstatus Active board

Standby board

active



12/66



STM-1 Benefits

CAPEX

Simplified transmission equipments : removal of E1 equipments and cables

OPEX

Simplified cabling & reduced transmission costs + Integrated O&M 4 STM-1 to replace 252 E1 interfaces per BSC sub-rack 1000 TRX

Transmission requirements divided by 4 between Remote BSC and TC/MSC site (Ater-mux 1:4 over STM-1)

Reliability & Flexibility

Redundancy features in SDH networkFlexible transmission resource switching in SDH network

No static transmission allocation (E1s) towards the MSC or the BSC

No costly site intervention

Reduced CAPEX and OPEX of A, A-ter and A-bis TDM transmission networks



13/66


2 Feature activation & Compatibility withprevious HW


14/66


B11 STM-1 impact for BSC EvolutionFeature activation

The feature is optional from commercial point of view. Operators buy the feature with a

maximum number of STM1 Interface per OMC.

This maximum number concerns STM1 Interface generally speaking, that means taking intoaccount BSC STM1 interfaces but also TC ones.

An interface represents a pair of protected STM1 links.

An OMC has to check the total number of declared interfaces in all BSC and TC in front ofthe upper limit licensed (this value is given by NUMBER_OF_SDH_LINKS variable that isdefined in the limits file, which is defined by the Max-Number-STM1-Interface parameter ).

When this number is closed to the limit, the threshold has to be defined, a warning is issued atdeclaration time.

When the limit is exceeded, operator basic actions at OMC are forbidden (the interfaces usage isblocked above the license limit).


15/66



Prerequisites for STM-1 activation

The following prerequisites apply:STM1 is available only on MxBSC,2 persons are need for MxBSC commissioning and OMC/NPO supervision,All hardware resources (SFP Modules) are available at the BSC site but not yetinserted,ADM ports are available,Enough resources in SDH network to transport BSS traffic,At BSC site, the Optical Fiber must be routed,The Transmission Termination Point (TTP) configuration files are prepared back officeand ready to be set in BSC (DLS) from BSC Terminal,The tests should be performed while no overload situation occurs on the BSS.

Optical Fibre is available on the BSC/TC site

The following information or equipment to complete the scenario is required:The Atermux topology (at BSC site),The Abis topology (at BSC site),Information about connection of Optical Fiber at ADM and BSC side.


16/66



STM-1 activation

STM-1 activation is done from the OMC.

It consists in creating STM-1 interfaces and all associated STM1 SBLs in the BSC and inthe OMC.

Before launching the activation, the OMC has to check if the newly activated interfacedon t lead to exceed the maximum number of allowed STM1 interfaces.

The OMC displays for a BSC, the 4 STM1 interfaces with their current activation status (i.e. activated or not).

The operator sets a new list of required STM1 interfaces by checking off not-activated

interfaces or by unchecking off activated ones.


17/66



STM-1 activation

It has to be highlighted that a STM1 interface may be de-activated with the conditionthat no ABIS/ATER-HWAY-TP are configured connected to it.

The new list is sent to the BSC. By comparison, the BSC creates and deletes the aimedSTM1-ITF and associated STM1-TTP.

The OMC creates the new STM1 SBL from BSC report and performs deletion by its own.

The STM1 transmission Termination Points configuration is done from BSC terminal. Thepurpose is to configure the Abis and Ater HwayTP as connected to a STM1 VC12 or asconnected to an E1 (LIU board). The TP board of the BSC is then configuredaccordingly.

If a transmission termination point configuration is applied, the OMC has to betriggered for resynchronisation with the BSC.


18/66



Compatibility with previous HW generation

The feature is not supported on G2 (legacy) BSC.

Restrictions & Limitations

Replacement of TPGSMv1 with TPGSMv3 also called TPGSM STM-1 is mandatory.It is recommend having at least 1 day of observation between board replacement and featureactivation.


19/66



STM-1 Configuration rules

Each TPGSM board supports up to 4 SDH interfaces. A pair of interfaces, each one ondifferent TPGSM, forms a logical SDH interface. Each pair has an active element and astand-by one.

Depending on the BSC configuration, each Ater and Abis TP of the BSC reports its E1

port number or its tributary, including the logical SDH number. BSC's TPs might have anunmapped state.

VC12 Numbering

The logical SDH interfaces are numbered from 1 to 4.VC12 tributaries are numbered according to G.707: (K, L, M) with K = 1..3, L = 1..7, M= 1..3. The numbers go from (1,1,1) to (3,7,3). In total there are 63 tributaries.

A tributary is therefore identified by: I, K, L, M where I = 1..4 and defines the logicalSDH number.


20/66



STM-1 Configuration rules

STM1-ITF

Represents the logical SDH interface.

Numbered from 1 to 4 gives the "I" of the numbering scheme.

Note: Each STM1-ITF has two STM1-TTP parents. Protection is done between STM-1interfaces with the same number.

STM1-TTP

Represents the SDH physical interface.

Numbered from 1 to 8. The first numbers, from 1 to 4, are assigned to the firstTPGSM and the rest to the second TPGSM.

(i from 1 to 4)


21/66



STM-1 TRANSMISSION PORTS mapping (pure STM-1 case)

The table below gives the mapping of ABIS-HWAY-TP and ATER-HWAY-TP on VC12 ports:

STM-1 Itf 1

STM-1 Itf 2

STM-1 Itf 3

STM-1 Itf 4

STM-1 Itf 1

STM-1 Itf 2

STM-1 Itf 3

STM-1 Itf 4

STM-1 Itf 1

STM-1 Itf 2

STM-1 Itf 3

STM-1 Itf 4

1 1 64 127 1 22 22 85 148 22 43 43 106 169 31 2 2 65 128 2 23 23 86 149 23 44 44 107 170 32 3 3 66 129 3 24 24 87 150 24 45 45 108 171 33 4 4 67 130 4 25 25 88 151 25 46 46 109 172 34 5 5 68 131 5 26 26 89 152 26 47 47 110 173 35 6 6 69 132 6 27 27 90 153 27 48 48 111 174 36 7 7 70 133 7 28 28 91 154 28 49 49 112 175 37 8 8 71 134 8 29 29 92 155 29 50 50 113 176 38 9 9 72 135 9 30 30 93 156 30 51 51 114 71 39

10 10 73 136 10 31 31 94 157 59 52 52 115 72 40 11 11 74 137 11 32 32 95 158 60 53 53 116 73 41 12 12 75 138 12 33 33 96 159 61 54 54 117 74 42 13 13 76 139 13 34 34 97 160 62 55 55 118 75 43 14 14 77 140 14 35 35 98 161 63 56 56 119 76 44 15

15

78

141

15

36

36

99

162

64

57

57

120

52

45

16 16 79 142 16 37 37 100 163 65 58 58 121 53 46 17 17 80 143 17 38 38 101 164 66 59 59 122 54 47 18 18 81 144 18 39 39 102 165 67 60 60 123 55 48 19 19 82 145 19 40 40 103 166 68 61 61 124 56 49 20 20 83 146 20 41 41 104 167 69 62 62 125 57 50 21 21 84 147 21 42 42 105 168 70 63 63 126 58 51

Abis Ater CS

Not used Ater PS


22/66


3 Telecom Parameters, Counters, Indicators


23/66


B11 STM-1 impact for BSC EvolutionOMC-R Parameters: New Parameters

Parameter Name Definition Sub-

SystemInstance

Category/OMC-Raccess

Type Range/

Default value

Max-Number-STM1-

Interface

(already existing

for STM1 in TC in

B10)

This parameter indicates

the maximum number of

STM1 interfaces allowed to

be activated in this OMC.

This maximum applies to

the sum of TC and BSCdeclared in STM-1 Interface.

OMC OMCSite CAE)/

ChangeableNumber

[0, none] / 0

Max value

depends on the

OMC Capacity

BSC-STM1-VC12-

Identifier


the VC12 resources by

defining its 3 values K,L and

MBSC

Abis/ Ater

Hway TP

Site (CAE)

/ Displayed List of

Number

The parameter

is defined by a

list of number

s: K [1,3] L[1,7]

M[1,3] /nodefault value

BSC-STM1-Interface-

identifier


the STM1 interface numberBSC STM1- ITF Site (CAE)/ Displayed Number [1,4] none


24/66


B11 STM-1 impact for BSC EvolutionOther Parameters: Existing Parameters

Parameter

NameDefinition Sub-

SystemInstance


TypeRange/Defaultvalue

LIUShelfPresent

This parameter indicates if the LIU

shelf is present or not in the BSC.

This parameter is specific for BSC

Evolution.

Coding rules:

False (0) if the LIU shelf is notpresent.

True (1) if the LIU shelf is present

BSC BSCSite(CAE)/

None(DLS)Flag [0,1]/1

BSC-SECTION-

TRACE-TYPE

This parameter indicates the

section trace type to be

transmitted by a given STM1_TTP.

Coding rules:0 if the section trace is one byte1 if the section trace is 16 bytes

framed

BSC STM1 TTP

Site (CAE) /

None (DLS)

Changeable

at BSC

terminal

Flag [0,1]/0


25/66



ParameterName Definition

Sub-System Instance

Category/

OMC-Raccess Type

Range/

Defaultvalue

BSC-SECTION-

TRACE-

ONEBYTE-

TRANSMITTED


Section trace (J0 bytes) coded

by the BSC in messages

transmitted by a given STM1 TTP

if the BSC-SECTION-TRACE-TYPEis one byte.

BSC STM1 TTP

Site (CAE) /

None (DLS)

Changeable

at BSCterminal

Integer [0,255] /1

BSC-

SECTIONTRACE

-STRING-

TRANSMITTED



by the BSC in messages

transmitted by a given STM1 TTP

if the BSC-SECTION-TRACE-TYPE

is 16 bytes framed

BSC STM1 TTP

Site (CAE) /

None (DLS)

Changeable

at BSC

terminal

Reference

Length of the

string 1 or 15

("A" to "Z", "a

to "z and "0

to "9 and

space)/ *


26/66



ParameterName Definition Sub-System Instance Category/ OMC-R access TypeRange/Defaultvalue

BSC-SECTION-

TRACE-

ONEBYTE-

RECEIVED



by the BSC in messages received

by a given STM1 TTP if the BSC-

SECTION-TRACE-TYPE is onebyte.

BSC STM1 TTP

Site (CAE) / None

Displayed at BSC

terminal

Integer[0,255]

/none

BSC-SECTION-

TRACE-STRING-

RECEIVED



by the BSC in messages received

by a given STM1 TTP if the BSC-

SECTION-TRACE-TYPE is 16 bytes

framed.

BSC STM1 TTP

Site (CAE) / None

Displayed at BSC

terminal

Referenc

e

Length of

the string 1

or 16.

/none


27/66



ParameterName Definition Sub-System InstanceCategory/OMC-Raccess

Type Range/ Defaultvalue

BSC-LOW-PATH-

TRACE-

TRANSMITTED


Low Path Trace (J2 bytes)

coded by the BSC in

transmitted messages within

a STM1 VC12

BSCSTM1

VC12

Site (CAE) /

None (DLS)

Changeable

at BSC

terminal

Reference

Length of the

string 15 ("A" to

"Z", "a to "z and

"0 to "9 and

space)/**

BSC-LOW-PATH-

TRACE-

TRANSMITTED


Low Path Trace (J2 bytes)

received by the BSC in

transmitted messages withina STM1 VC12

BSC STM1 VC12

Site (CAE) /

None

Displayed at

BSC terminal

Reference

Length of the string

16./none


28/66




Sub-System Instance



BSC-HIGH-

PATH-TRACE-

TRANSMITTED


the High Path Trace (J1

bytes) coded by the BSC in

transmitted messages

within a STM1 VC4

BSC STM1 ITF

Site (CAE) /

None (DLS)

Changeable

at BSCterminal

Reference

Length of the

string 15 ("A" to

"Z", "a to "z

and "0 to "9

and space)/**

BSC-HIGH-

PATH-TRACE-

RECEIVED


the Low Path Trace (J1

bytes) received by the BSC

in transmitted messages

within a STM1 VC4

BSC STM1 ITF

Site (CAE) /

None

Displayed at

BSC terminal

Reference

Length of the

string 16./none


29/66




Sub-System Instance



BSC-CLOCK-

PREFERENCE


operator clock preference. It

may be chosen in the

following sets: Ater E1carried by LIU-E1 and VC12-

E1, Ater carried by VC12-E1

only or it is the STM1 clock.

BSC BSC

Site(CAE)/None(DLS)

Changeableat BSCterminal

Number

0: Ater E1 carried byLIUE1 and VC12-E1

1: Ater carried byVC12-E1;

2: STM1 clockpreferred / 0


30/66


B11 STM-1 impact for BSC EvolutionAlarms

Label Type Description

STM1-TAKEOVER 100 This alarm indicates a STM1-TTP takeover

SFP-UNEQ 10 Small Form-Factor Pluggable not equipped

LOS 11 Section Loss Of Signal

LOF 12 Section Loss Of Frame

MS-AIS 13 Multiplex Section Alarm Indication Signal

MS-RDI 14 Multiplex Section Remote Defect Indication

MS-BER-6 15 Multiplex Section Bit Error Rate 10-6 STM1-TTP

MS-BER-3 17 TPGSM standby board is not reachable (in failure)

SFP-NOTSUP 18 Small Form-Factor Pluggable not supported

AU-LOP 21 Administrative Unit 4 Loss of Pointer

AU-AIS 22 Administrative Unit 4 Alarm Indication Signal

The Impacted SBL according to the colours: STM1-TTP, STM1-ITF, ABIS-HWAY-TP, ATER-HWAY-TP (BSC side) .

There are new alarms linked to this feature.


31/66


B11 STM-1 impact for BSC EvolutionAlarms

Label Type Description HP-2MS-Failed 23 High Path 2 multiplex sections failed

HP-UNEQ * 31 High Order Path Unequipped

HP-PLM 32 High Order Path Payload Label Mismatch

HP-RDI 33 High Order Path Remote Defect Indication

HP-LOM 34 High Order Path Loss of Multiframe

TU-LOP 41 Tributary Unit 12 Loss of Pointer

TU-AIS 42 Tributary Unit 12 Alarm Indication Signal

LP-UNEQ 51 Low Path Unequipped

LP-PLM 52 Low Path Payload Label Mismatch

LP-RDI 53 Low Path Remote Defect Indication

* Open point related to the availability at OMC-R/NPO level: waiting TD feedback.

The Impacted SBL according to the colours: STM1-TTP, STM1-ITF, ABIS-HWAY-TP, ATER-HWAY-TP (BSC side) .


32/66


There are no new or modified counters linked to this feature.

New stability indicators were created due to new alarms (Laser part).

B11 STM-1 impact for BSC EvolutionTelecom Counters and Indicators (1/6)


33/66



NPO indicator refname LongName NPO Formula NPO B11 Description

STM1_TAKEOVER_Alarm_Count STM1_TAKEOVER_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[100]%''))

Count of STM1TAKEOVER activealarms

BSC_SFP_UNEQ_Alarm_Count BSC_SFP_UNEQ_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[20]%''))

Count of SFPUNEQ activealarms

BSC_Section_LOS_A_C BSC_Section_LOS_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[21]%''))

Count ofSection_LOSactive alarms

BSC_Section_LOF_A_C BSC_Section_LOF_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[22]%''))

Count ofSection_LOFactive alarms

BSC_MS_AIS_Alarms_CountBSC_MS_AIS_Alarms_Count

NZ(ALARM_COUNT_REC('SPECIFICP

ROBLEM LIKE '%_[101]%_[23]%''))

Count of MS AIS

active alarms

BSC_MS_RDI_Alarm_Count BSC_MS_RDI_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[24]%''))

Count of MS RDIactive alarms

BSC_MS_BER_10E_6_A_C BSC_MS_BER_10E_6_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[25]%''))

Count of MS BER10-6 activealarms

New Indicators for STM1 feature (Counting family):


34/66




BSC_MS_BER_10E_3_A_C BSC_MS_BER_10E_3_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[26]%''))

Count of MS BER10-3 active alarms

BSC_SFP_Not_Supp_A_C BSC_SFP_Not_Supp_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[28]%''))

Count of SFP NotSupported activealarms

BSC_AU_LOP_A_C BSC_AU_LOP_Alarm_Count


ROBLEM LIKE '%_[101]%_[31]%''))

Count of AU LOP

active alarms

BSC_AU_AIS_A_C BSC_AU_AIS_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[32]%''))

Count of AU AISactive alarms

BSC_HP_PLM_A_C BSC_HP_PLM_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[42]%''))

Count of HP PLMactive alarms

BSC_HP_RDI_A_CBSC_HP_RDI_Alarm_Count


ROBLEM LIKE '%_[101]%_[43]%''))

Count of HP RDI

active alarms

BSC_HP_LOM_A_C BSC_HP_LOM_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[44]%''))

Count of HP LOMactive alarms



35/66





BSC_TU_LOP_A_C BSC_TU_LOP_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[51]%''))

Count of TU LOPactive alarms

BSC_TU_AIS_A_C BSC_TU_AIS_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[52]%''))

Count of TU AIS activealarms

BSC_LP_UNEQ_A_C BSC_LP_UNEQ_Alarm_Count NZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[55]%'')) Count of LP UNEQactive alarms

BSC_LP_PLM_A_C BSC_LP_PLM_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[56]%''))

Count of LP PLMactive alarms

BSC_LP_RDI_A_C BSC_LP_RDI_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[57]%''))

Count of LP RDI activealarms

BSC_HP_UNEQ_A_C BSC_HP_Uneq_Alarm_count NZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[101]%_[41]%'')) Count of HP Uneqactive alarms

f l


36/66



New Indicators for TC STM1 feature B10 alarms (Counting family):


TC_SFP_UNEQ_A_C TC_SFP_UNEQ_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[102]%_[210]%''))

Count of SFP UNEQ in TCactive alarms

TC_RS_LOS_A_C TC_RS_LOS_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[102]%_[211]%''))

Count of RS LOS activealarms

TC_RS_LOF_A_C TC_RS_LOF_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[102]%_[212]%''))

Count of RS LOF activealarms

TC_MS_AIS_A_C TC_MS_AIS_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[102]%_[214]%''))

Count of MS AIS in TCactive alarms

TC_MS_RDI_A_C TC_MS_RDI_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[102]%_[215]%''))

Count of MS RDI in TCactive alarms

TC_MS_SF_Alarm_Count TC_MS_SF_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[102]%_[216]%''))

Count of MS SF activealarms

TC_MS_SD_Alarm_Count TC_MS_SD_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[102]%_[217]%''))

Count of MS SD activealarms

B11 STM 1 i f BSC E l i


37/66



New Indicators for TC STM1 feature B10 alarms (Counting family):


TC_AU_LOP_Alarm_Count TC_AU_LOP_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[102]%_[221]%''))

Count of AU LOP in TCactive alarms

TC_AU_AIS_Alarm_Count TC_AU_AIS_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[102]%_[222]%''))

Count of AU AIS in TCactive alarms

TC_HP_UNEQ_Alarm_Count TC_HP_UNEQ_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[102]%_[231]%''))

Count of HP Uneq in TCactive alarms

TC_HP_PLM_Alarm_Count TC_HP_PLM_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[102]%_[232]%''))

Count of HP PLM in TCactive alarms

TC_HP_RDI_Alarm_Count TC_HP_RDI_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[102]%_[233]%''))

Count of HP RDI in TCactive alarms

TC_HP_LOM_Alarm_Count TC_HP_LOM_Alarm_CountNZ(ALARM_COUNT_REC('SPECIFICPROBLEM LIKE '%_[102]%_[234]%''))

Count of HP LOM in TCactive alarms

B11 STM 1 i f BSC E l i


38/66


B11 STM-1 impact for BSC EvolutionNPO Reports

NPO report name Views in the report Description of the views

GLOBAL_TRANSMISSION_EVOLUTION

GLOBAL_TRANS_EVO_TIME_Ater_TP Global transmission evolution on Ater TP by time

GLOBAL_TRANS_EVO_TIME_AterMux_TP Global transmission evolution on AterMux TP by time

GLOBAL_TRANS_EVO_TIME_Abis_TP Global transmission evolution on Abis TP by time

GLOBAL_TRANS_EVO_TIME_A_TP Global transmission evolution on A TP by time

GLOBAL_TRANS_EVO_TIME_STM1 Duration of active alarms raised on stm1 TTP / stm1

ITF objects based on friendly name criterion

GLOBAL_TRANS_EVO_OCCURENCE_Ater_TP Global transmission evolution on Ater TP by time

GLOBAL_TRANS_EVO_OCCURENCE_AterMux_TP Global transmission evolution on AterMux TP by time

GLOBAL_TRANS_EVO_OCCURENCE_Abis_TP Global transmission evolution on Abis TP by time

GLOBAL_TRANS_EVO_OCCURENCE_A_TP Global transmission evolution on A TP by time

GLOBAL_TRANS_EVO_OCCURENCE_STM1

Count of occurrences of active alarms raised on stm1

TTP / stm1 ITF objects based on friendly name

criterion

New or modified views/reports with STM1 feature introduction (Stability family):

B11 STM 1 i t f BSC E l ti


39/66


B11 STM-1 impact for BSC EvolutionNPO Reports

NPO report name Views in the report Description of the views

STM1_Alarm_Synthesis

Global_NetworkCount of network elements contained in the selected

object

BSC_STM1_ALARM_SYNTHESIS Count of occurrences of active BSC alarms related to

STM1 feature based on specific problem criterion

TC_STM1_ALARM_SYNTHESIS Count of occurrences of active TC alarms related to

STM1 feature based on specific problem criterion

Availability_Stability_Dashboard

GLOBAL_TRANS_EVO_OCCURENCE (not STM1 specific)

Count of occurrences of active alarms raised on

A/Abis/Ater/AterMux/STM1 objects based on specific

problem criterion

New or modified views/reports with STM1 feature introduction (Stability family):


40/66


4 Test Strategy

B11 STM 1 impact for BSC E ol tion


41/66


The introduction and the use of STM-1 on the BSC evolution will be evaluated and

tested in order to the check the non-regression of QoS, stability and Atermux and Abis

availability.

Two different cases are proposed and defined according to the network configuration:

BSC with mixed configurationThe BSC has mixed configuration with E1 and STM-1 connections. The ABIS and ATER-Mux PS interfaces will use full E1 transport whereas ATER-Mux CS will use full STM-1transport.

BSC with Full STM-1 configuration

The BSC configuration proposed to be used on this case is a BSC with full STM-1connections. All the interfaces (Abis and Ater-Mux PS+ CS interfaces) will use full STM-1 transport.

B11 STM-1 impact for BSC EvolutionTest Strategy

B11 STM 1 impact for BSC Evolution


42/66


The test is organized around the following aspects:

* Optional test: It will be only tested in case of specific request from the operator.

B11 STM-1 impact for BSC EvolutionTest Strategy: Type of analysis

Test Reference Test Name Aim of the tests Scope

Test 1 Atermux CS QoS follow-upAllow to check Atermux CS QoS non-

regressionApplicable to case 1 and 2

Test 2 Atermux PS QoS follow-upAllow to check Atermux PS QoS non-

regressionApplicable only to case 2

Test 3 Abis QoS follow-up Allow to check Abis QoS non-regression Applicable only to case 2

Test 4 Stability

Allow to verify the stability and theavailability of ATER-Mux and Abisinterfaces, and that there is no clockproblem.

Applicable to case 1 and 2

Test 5 Non regression of global QoS Allows to check non QoS regression Applicable to case 1 and 2

Test 6*Voice Quality and PS Data

Performance

Allows to show non-regression after thefeature activation and to validate it fromend to end user point of view

Applicable to case 1 and 2


43/66



44/66


The radio parameters and Abis/Ater configurations (interfaces dimensioning, (E)GPRScoding scheme used, ) should be kept unchanged during these tests.

The bellow parameters are therefore checked before these tests start, between thetwo steps and after it ended:

Max-Number-STM1-Interface

BSC-STM1-VC12-Identifier, BSC-STM1-Interface-identifier

LIUShelfPresent

BSC-SECTION-TRACE-TYPE

BSC-SECTION-TRACE-ONEBYTE-TRANSMITTED, BSC-SECTIONTRACE-STRING-TRANSMITTED

BSC-SECTION-TRACE-ONEBYTE-RECEIVED, BSC-SECTION-TRACE-STRING-RECEIVED

BSC-LOW-PATH-TRACE-TRANSMITTED, BSC-LOW-PATH-TRACE-TRANSMITTED

BSC-HIGH-PATH-TRACE-TRANSMITTED,BSC-HIGH-PATH-TRACE-RECEIVED

BSC-CLOCK-PREFERENCE

B11 STM-1 impact for BSC EvolutionTest Strategy: Parameters setting



45/66


The analysis should be based on:

Some NPO indicators

The following indicators should be followed during the test phase:

The PM type 9 N7 Measurements and type 25 SCCP Measurements can be usedfor deeply analysis (it should be activated at OMC-R).

B11 STM-1 impact for BSC EvolutionTest Strategy: ATER-Mux CS QoS Follow-up

Ref name Long name Description

GTCTRE RTCH_Erlang_total RTCH Erlang (hourly measurement)

GSDTRE SDCCH_Erlang_total SDCCH Erlang (hourly measurement)

GBSN7NALT N7_unavailability Cumulative time while N7 signalling link is not aligned

GBSN7NAVR N7_unavailability_rate Percentage of time when N7 signalling link is not available.

GQSTRSCE SCCP_Erlang SCCP traffic

GBSN7FLN SCCP_connection_fail SCCP connection establishment failure

GBSN7FLRSCCP_connection_fail_rate

SCCP connection establishment failure rate

GBSN7SUR SCCP_connection_success_rate SCCP connection establishment success rate.

B11 STM-1 impact for BSC Evolution


46/66


The analysis should be based on NPO indicators (1/2):

B11 STM-1 impact for BSC EvolutionTest Strategy: ATER-Mux PS QoS Follow-up*

Ref-name Long name Description

GAAGCHUST GPRS_transmission_GCH_busy_timeMaximum cumulative time during which a GCH (16k

channel) is busy in the cell.

GQAGALCTT GPRS_GPU_Ater_cong_timeAtermux congestion duration (in seconds) due to a lack of

Ater nibbles on the Atermux interface.

GQRGPUCDT GPRS_GPU_DSP_cong_time Time during which a DSP enters the congestion state.GTALAPDLN GPRS_LAPD_DL_traffic_sent_to_BSC Number of kilo bytes sent to the BSC on the LapD link.

GTALAPULN GPRS_LAPD_UL_traffic_received_from_BSCNumber of kilo bytes received from the BSC on the LapD

link.

GTRGPUCOT_MA GPRS_GPU_high_Ater_usage_time_maxTime (cumulated over a granularity period) during which

the GPU remains in "high" Ater usage.

GQRDTECTN GPRS_DL_TBF_estab_fail_ater_congNumber of DL establishment failures due to congestion of

Ater(Mux).

* for case 1 (BSC with mixed configuration), it is not necessary to perform this analysis.


47/66



48/66


The analysis should be based on some NPO indicators:

The following indicators should be followed during the test phase:

The PM type 7 LAPD Measurements can be used for deeply analysis (it shouldbe activated at OMC-R).

B11 STM 1 impact for BSC EvolutionTest Strategy: ABIS QoS Follow-up*


GQSCDBIR Call_drop_BSS_int_failure_rate Rate of dropped calls due to internal BSS failure over thetotal amount of calls with a successful end.

GTCTRICDBR RTCH_drop_BSS_int_failure_rateRate of TCH call drops due to internal BSS problems.

GQSCDBIO Call_drop_BSS_int_failure_ratio Ratio of dropped calls due to internal BSS failure inrelation to all dropped calls due to system problem.

GQRDTECBN GPRS_DL_TBF_estab_fail_abis_cong Number of DL establishment failures due to congestion ofAbis.

GQRUTECBN GPRS_UL_TBF_estab_fail_abis_cong Number of UL establishment failures due to congestion ofAbis.



49/66



50/66


This is performed through the alarm surveillance on the OMC-R orNPO/Laser, and indicators/reports available from NPO/Laser.

Alarms

Class 1 CLK Alarms: These alarms are detected at the BTS and may refer clocksynchronization issues caused by the BSC E1/STM-1 interface.

Class 36 TRUNK Alarms: These alarms are detected at the BSC and refer to Atransmission or synchronization problems.

Class 52 BSC CLOCK Alarms: These alarms are detected at the BSC and refer toclock synchronization issues.

Class 66 TSC TRUNK Alarms: These alarms are detected at the BSC and refer Atransmission issues.

Class 101 BSC-Trans Alarms: These alarms are detected at the BSC and refer Atransmission issues.

B11 STM 1 impact for BSC EvolutionTest Strategy: ABIS*, ATER Mux CS and PS* stability and availability follow-up




51/66


Stability Reports

Availability

Operational

Top N occurrence alarm

GLOBAL_TRANSMISSION_EVOLUTION

Availability_Stability_Dashboard

STM1_Alarm_Synthesis alarms related to STM-1 transport





52/66


For ATER availability the following indicators should be checked:



GAALAPAVP GPRS_GSL_LAPD_unavailable_percent Percentage of time per LapD during which the LapD GSL is not available on

the AterMux interface.

GAALAPAVT GPRS_GSL_LAPD_unavailable_time Time per LapD during which the LapD GSL is not available on the AterMux

interface.

GQALAPFRESN GPRS_LAPD_establishments_resets Number of data link establishment, re-establishment and reset on the LapD

logical link.

GQALAPUFNRN GPRS_LAPD_RNR_frames_received Number of Receive Not Ready (RNR) frames received on the LapD logical link.

GQALAPDFNRN GPRS_LAPD_RNR_frames_sent Number of Receive Not Ready (RNR) frames sent on the LapD logical link.

GQAGALCTP GPRS_GPU_Ater_cong_percent Percentage of time during which AterMux interface (GICs) for this GPU is

congested (at least one PDCH group impacted).

GQAGALCTT GPRS_GPU_Ater_cong_time Atermux congestion duration (in seconds) due to a lack of Ater nibbles on the

Atermux interface.




53/66


These are the tests to check Voice Quality and PS Data Performance:

1. Set equipment and validate the proposed drive routes. (1 day)

2. Make static measurements in two cells with good radio conditions. (1 day)

3. Make static measurements in two cells with poor radio conditions. (1 day)

4. Make mobility measurements in the selected area. (2 days)

5. Make Ping and FTP measurements. (1 day)

6. Post process the results and report creation. (3 days)

All the VQ measurements should be made from mobile to ISDN and from mobileto mobile. The speech codecs to use are: FR, HR, EFR, AMR-FR and AMR-HR.

For more details about these tests please refer to the STM-1 Test Plan.

pTest Strategy: Voice Quality and PS Data Performance tests



54/66


pImpacts on the internal tools

There is only impact on NPO/LASER tool due to new Alarms.


55/66


5 R&D system tests results



56/66


pR&D system tests results: System validation status at DR4

Inter-Release Non-regression

STM1 on BSC Evolution (non-reg part): quality 96,4% Test description: BSC reduction .

3BKA20FBR272134, G3, OMC CLOSED (B11MR1ED1.1 - BSXSAZ03D) FR Description : Wrong information in prog trans report Operational Impact : The operator doesn't know if there are NEs with access

fail or download fail

System validation Status

BSC STM-1: quality 97%

Test description: Alarm management in case all the Ater links between BSC and TCare via STM1

3BKA20FBR266580 , G3, MxBSC , CLOSED (B11MR2 - BSXSAZ10E -

OMCSAZ10I) FR Description : misleading warning message, following an unlock STM-TTPaction.

Operational Impact :none



57/66


pR&D system tests results: system validation status at DR4

Test description: Display/modification of section and path traces from BSC-Terminal 3BKA20FBR274631, G3/Minor, MxBSC , FR Description : Ciphering used by BSC Terminal SW when computing STM-1 low

path trace must be changed. Operational Impact :Wrong low path trace is used Status: not blocking for DR4, accepted for PilotCLOSED (BSXSAZ06I)

Test description: Check the STM-1 parameters for BSC and TC at NPO side 3BKA20FBR272636 , G3, OMC FR Description : Some STM-1 parameters names are not displayed at OMC side. Operational Impact :The operator may get confused because one parameter

name related to STM1, present in OMC, is not in line with 'BSS O&M ParametersCatalogue document or because other parameters don't have a name and it isdifficult to identify them.

CLOSED (B11MR1ED1.1 - OMCSAZ03F)

Interoperability issue confirmed during the JST ( Joint System Tests ) with T-Mobile,between TC and NGN MGW (APS protocol incompatibility).


58/66


6 Reference documentation



59/66


Reference documentation

Doc title Doc reference Edition SFD: STM-1 impact for BSC Evolution 3BK 10204 0068 DTZZA Ed. 02 Released

SFD: STM-1 Impact for TC 3BK 10204 0067 DTZZA Ed. 01 Released

TC-STM1 board introduction NE Test Specifications --------------------- ------------

BSS capacity, connectivity and architectureImprovements System Integration Test Strategy BSS

Release B113BK 13024 0248 DSZZA Ed. 01 Released

Activate/Deactivate STM1: Interface for 9130 BSCEvolution/ 9125 TC - BSC & TC Document(Reconfiguration Method Release B11)

3BK 17438 1023 RJZZA Ed.01P06

Functional Feature Description: STM-1 connectivity inthe BSS 3DC 21144 0122 TQZZA Ed. 03 Released

B11 Network Reconfiguration Recommendations 3BK 21669 AAAA PCZZA Ed. 01P17NE B10 document: BSS Architecture Service Guideline 3DF 0190 329 8010 VAZZA 02 Ed. 02


60/66


7 Annex



61/66


Annex A

TP STM-1 board features

TP-STM1 brings the following features to the BSC Evolution 9130:

It can be used at feature parity with TPGSMv1 boards with E1 connectivityfrom B10 MR2 ed03

It is required to support high capacity MxBSC (>4500erl/1000TRX) from B10 MR2ed03

It is required for feature Optimized HR connectivity in the case: from B10 MR2ed03

>800TRX Feature used on more than 50% of the TRX

It offers up to 4 STM1-1 interfaces to transport up to 252 E1 from B11

It support E1 over ethernet (for up to 252 E1) from B11 It can host a daughter board for the introduction of IP (for up to 252 E1) from B11



62/66


Annex A

TP STM-1 board benefits

Support of high capacity MxBSC from B10

OPEX reduction from B11 :

ADM equipment not needed.

MxBSC can be installed without LIU shelf BTS connected through ethernet & full

STM-1.1 LIU shelf = 16 LIU boards = 256 E1 terminations

CAPEX reduction from B11 :

Less wiring.

O&M modifications of routing instead of rewiring.

IP ready: easier introduction of IP from B11 .


63/66



64/66


Annex A

TP STM-1 with SDH transmission

BSC

SSW A

SSW S

TP-STM1

TP-STM1 LIU E1Shelf CCP 1

CCP N

1Gbit

Eth Links

OMCP A

OMCP S

AbisE1

IP

Ater, GaterE1

Data path over E1

Legacy Flows (NE1oE) & E1

Lapd signalling (BTS) &SS7 signalling (MSC)

4xSTM1

4x STM1 A 4x STM1 S



65/66


Annex A

TP STM-1 with IP transmission

BSC

SSW W

SSW P

TPV3 P

TPV3_ w E1 Shelf

External E1

CCP 1

CCP N

1G-BTEthernet Links

OMCP W OMCP P

AbisE1

AbisUDP/IP/PPP/E

Ater, GaterUDP/IP/Eth

IP

Ater, GaterE1

SS7/M2UA/SCTP/IP/Eth

SS7 signalling (from MSC/TC)Lapd signalling (from BTS)Data path over IP

New Flows (IP)

Data path over E1

Legacy Flows (NE1oE)

Lapd signalling (fromBTS)& SS7 signalling(from MSC)

4xSTM1

4x STM1_ W 4x STM1_ P


66/66

www.alcatel-lucent.comwww.alcatel-lucent.com

[seminar5]_stm1

Documents