Vous êtes sur la page 1sur 195

B11 MR1 Ed1.x / Ed2.

x
Seminar of GSM Network Engineering
Counters/Parameters Improvements

Pedro Henriques, Patricia Eusbio


March 2010

Publication Information
Author:
Pedro Henriques, Operational Network Engineering
Patricia Eusbio, Operational Network Engineering

Publication history:
- 01/21/2010: V0.1, Draft
-

02/04/2010: V1 Release

02/19/2010: V2 Release

Reference documentation:
-

NE Proposal of evolutions of PM counters in release B11 Edition 1 Proposal 3

SYT Memo Improvement of PS counters for GSL and for data/signalling differentiation and for
GPRS/EDGE differentiation Edition 8 (Wireless/GSM/R&D/SYT/207082_8)

NE B10 document: BSS Architecture Service Guideline Edition 2 (3DF 0190 329 8010 VAZZA 02)

B11 MFS-BSC interface BSCGP layer Edition 2 Rl (3BK 11202 0507 DSZZA)

CR246115 changed from CDE/none/MFS + migration + external + reco + internal

CR266950: recommended added - cell level (B10 alignt - MFS level)

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Agenda
New and Modified Call Drop Radio and HO Drop counters
New CS counters discarded messages / SS7 clear request
GSL (or BSCGP) interface counters
PS traffic differentiation between user data traffic and the signalling
traffic
PS traffic differentiation between GPRS and EDGE (in case of abnormal
release)
Parameters Improvement (Ater Usage Optimization)
Reference documentation
Annex
All Rights Reserved Alcatel-Lucent 2009, XXXXX

Agenda
New and Modified Call Drop Radio and HO Drop counters
Theoretical overview
Feature activation & compatibility with previous HW
Telecom parameters, counters & Indicators
Test strategy
R&D system tests results
CMCC FO results B11 MR1 ed1.0

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview: New and Modified Call Drop Radio and HO Drop counters
With the spread of the usage of AMR codec in the networks, it was needed to
introduce the 3GPP feature Repeated SACCH/FACCH. This new feature will
provide more robust signalization for AMR calls, consequently will impact
the call drop radio and the HO drop.
To allow better detection of the call drop radio and HO drop, it is implemented
in B11 a segmentation of the respective counters for AMR and non-AMR
calls. Inside AMR calls it was split between AMR calls using or not Repeated
SACCH/FACCH feature.

Call Drop Radio:


a. 1 modified counter
b. 2 new counters

HO Drop:
a. 1 modified counter
b. 2 new counters

Expected Benefits: Better optimisation of the networks and AMR features


follow-up
All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview: New and Modified Call Drop Radio and HO Drop counters
The former indicators are split in:

Indicator

Old Formula

Call drop
radio

All dropped calls

Call drop HO

All dropped calls


during HO exec

New Formula
dropped non-AMR calls
+ dropped AMR calls w/o Repeated SACCH
+ dropped AMR calls w Repeated SACCH
dropped non-AMR calls HO
+ dropped AMR calls HO exec w/o Repeated FACCH
+ dropped AMR calls HO exec w Repeated FACCH

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Feature activation & compatibility with


previous HW

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Feature Activation
Feature activation per default.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Compatibility with previous HW generation and restrictions


Compatibility with previous HW generation
Inline with B11
Restrictions & Limitations
None

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Parameters, Counters, Indicators

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Parameters

No new or modified parameters linked to this feature.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Counters: New and Modified Call Drop Radio and HO Drop counters
Modified TRX counters
Counter
refname

Long Name

Definition

Measured
object

Domain

Type

TRX

Quality
of
Service

110

TRX

Quality
of
Service

110

Number of non-AMR TCH (in HR or FR


usage) drops in TCH established phase
MC736

due to radio link failure (radio link


NB_TCH_DROP_EST_PHAS_
timeout or Lapdm timer expiry), per TRX.
RLF_TRX
This counter takes into account TCH in
traffic or in signaling mode. MC736 =
C736
Number of non-AMR TCH drops during
the execution of any TCH outgoing

MC621

NB_TCH_DROP_OUT_HO_E handover, per TRX. This counter takes


XEC_TRX

into account handovers from TCH in


traffic or in signaling mode. MC621 =
C621

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Counters: New and Modified Call Drop Radio and HO Drop counters
New TRX counters (1/2)
Counter
refname

Long Name

Definition

Measured
object

Domain

Type

TRX

Quality
of
Service

110

TRX

Quality
of
Service

110

Number of AMR TCH (NB or WB AMR) for


MC993

NB_AMR_TCH_DROP_RLF_
TRX

which Repeated SACCH is not activated,


dropped in TCH established phase due to
radio link failure (radio link timeout or
Lapdm timer expiry), per TRX.
Number of AMR TCH (NB or WB AMR) for

MC994

NB_AMR_TCH_DROP_RLF_
TRX_RSACCH

which Repeated SACCH is activated,


dropped in TCH established phase due to
radio link failure (radio link timeout or
Lapdm timer expiry), per TRX.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Counters: New and Modified Call Drop Radio and HO Drop counters
New TRX counters (2/2)
Counter
refname

Long Name

Definition

Measured
object

Domain

Type

TRX

Quality
of
Service

110

TRX

Quality
of
Service

110

Number of TCH using AMR codecs (NB or


WB)
MC995

but

with

Repeated

FACCH

not

NB_AMR_TCH_DROP_OUT_ activated, dropped during the execution


HO_TRX
of any TCH outgoing handover, per TRX.
This

counter

takes

into

account

handovers from TCH in traffic.


Number of TCH using AMR codecs (NB or
WB) and with Repeated FACCH activated,
MC996

NB_AMR_TCH_DROP_OUT_ dropped during the execution of any TCH


HO_TRX_RSACCH
outgoing handover, per TRX. This counter
takes into account handovers from TCH in
traffic or in signaling mode.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Indicators: New and Modified Call Drop Radio and HO Drop counters
New/Modified Indicators:
The list of new/modified indicators is large, it is presented the most relevant
ones.
Indicator
refname

Long Name

Formula

GQSNACDRN NonAMR_Call_drop_radio MC736

GTCNRSACN

GTCRSACN

AMR_TCH_DROP_No_RSA
MC993
CCH_Activated

AMR_TCH_DROP_RSACCH
_Activated

MC994

Description

Number of non-AMR TCH (in HR or FR usage)


drops in TCH established phase due to radio
link failure (radio link timeout or Lapdm timer
expiry), per TRX. This counter takes into
account TCH in traffic or in signaling mode.
Counts the number of AMR TCH (NB or WB
AMR) for which Repeated SACCH is not
activated, dropped in TCH established phase
due to radio link failure (radio link timeout or
Lapdm timer expiry), per TRX.
Counts the number of AMR TCH (NB or WB
AMR) for which Repeated SACCH is activated,
dropped in TCH established phase due to
radio link failure (radio link timeout or Lapdm
timer expiry), per TRX. This counter takes
into account TCH in traffic.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Indicators: New and Modified Call Drop Radio and HO Drop counters
New/Modified Indicators:
Indicator
refname

Long Name

GQSNACDHN NonAMR_Call_drop_HO

Formula

MC621

GTCNRFACN

AMR_TCH_DROP_OUT_HO
MC995
_No_RFACCH_Activated

GTCRFACN

AMR_TCH_DROP_OUT_HO
MC996
_RFACCH_Activated

Description

Number of non-AMR TCH drops during the


execution of any TCH outgoing handover, per
TRX. This counter takes into account
handovers from TCH in traffic or in signaling
mode.
Counts the number of TCH using AMR codecs
(NB or WB) but with Repeated FACCH not
activated, dropped during the execution of
any TCH outgoing handover, per TRX. This
counter takes into account handovers from
TCH in traffic.
Counts the number of TCH using AMR codecs
(NB or WB) and with Repeated FACCH
activated, dropped during the execution of
any TCH outgoing handover, per TRX. This
counter takes into account handovers from
TCH in traffic or in signaling mode.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Indicators: New and Modified Call Drop Radio and HO Drop counters
New/Modified Indicators:
Indicator
refname

Long Name

GQSCDRN

Call_drop_radio

GQSCDRR

Call_drop_radio_rate

GQSCDHN

Call_drop_HO

GQSCDHR

Call_drop_HO_rate

Formula

Description

Number of calls dropped due to radio


problems.
Rate of dropped calls due to radio
Call_drop_radio /
problem over the total amount of
RTCH_success_end
calls with a successful end.
Number of calls dropped during
handover execution.
MC621+MC995+MC996
This indicator takes into account 2G3G HO drop.
Rate of calls dropped during
handover execution over the total
Call_drop_HO / amount of calls with a successful
RTCH_success_end end.
This indicator takes into account 2G3G HO drop.
MC736+MC993+MC994

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Indicators: New and Modified Call Drop Radio and HO Drop counters
New/Modified Indicators:
Indicator
refname

GQSCDN

GQSCDR

Long Name

Call_drop

Call_drop_rate

Formula

Description

Call_drop_radio +
Call_drop_HO +
Call_drop_BSS +
Call_drop_preemption

Number of dropped calls (system +


handover + radio + preemption)

Call_drop /
RTCH_success_end

Rate of dropped calls (system +


radio + handover + preemption) over
the total amount of calls with a
successful end

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Indicators: New and Modified Call Drop Radio and HO Drop counters
New and impacted Reports:

Indicator
refname

Alc_Mono_Call
Alc_Mono_Drop_Causes
Alc_mono_Repeated_ACCH

Description

This report provides all the views related to the different


steps of a call.
This report gives the drop causes and the drop radio
Causes: UL/DL Quality, UL/DL Level, UL/DL Interference,
Short/Long Distance and Other causes.
Assessment on Repeated ACCH feature.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Test Strategy

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Test Strategy: New and Modified Call Drop Radio and HO Drop counters
Requirements
type of tests: statistical tests
type of analysis: QoS
objective of each test type:

It is intended to correlate the new and existing counters in order to be validate


correctly the new counters.

Only in case of issues detected the following traces should be collected


Radio traces
Ater/Abis/A traces

required tools: NPO, K15 tools and DT tool chain.


required means: 1 RNE and 1 TSC (L1) Support
estimated duration of the tests (post-processing included): 2 weeks

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Impacts on the internal tools

Tool

Follow-up status

NPO/NPO4U

closed

AnaQoS

On-going

Comments

Specific counters/indicators/reports already created

Counters will be updated in the information of the


feature slides. No specific extra work from expert
group

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Tool version with feature


data configuration

since NPO30D19

Version 3.5.1.

R&D system test results

All Rights Reserved Alcatel-Lucent 2009, XXXXX

System validation tests of the feature


Not available

All Rights Reserved Alcatel-Lucent 2009, XXXXX

CMCC FO Results B11 MR1 ed1.0

All Rights Reserved Alcatel-Lucent 2009, XXXXX

New and Modified Call Drop Radio and HO Drop counters


CMCC FO results
The validation of the feature in CMCC was only partially done, as the AMR
codecs are not used in CMCC. The validation will be limited to:
Check if new counters for AMR calls are 0
Check if Call drop radio and Call drop HO are stable.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

New and Modified Call Drop Radio and HO Drop counters


CMCC FO results
Check if new counters (basic indicators) for AMR are 0

Indicator
refname

Long Name

Formula Value equal to


0

GTCNRFACN

AMR_TCH_DROP_OUT_HO_No_RFACCH_Activated

MC995

Partial*

GTCRFACN

AMR_TCH_DROP_OUT_HO_RFACCH_Activated

MC996

Partial*

GTCNRSACN

AMR_TCH_DROP_No_RSACCH_Activated

MC993

Partial*

GTCRSACN

AMR_TCH_DROP_RSACCH_Activated

MC994

Partial*

* Inconsistency detected at TRX level for unused TRXs: some counters have value 0 others have
blank value. The problem was not reproduced in TMO.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

New and Modified Call Drop Radio and HO Drop counters


CMCC FO results
Check if Call drop radio and Call drop HO are stable.
Call drop radio and call drop radio rate
B11 Migration

Call drop HO and call drop HO rate


B11 Migration

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Conclusions
compromised with the
several network issues

Variation of the indicators due to


parameter changes in the network and to
issues in the Adj parameters after BSS
migration

TMO FO Results B11 MR1 ed1.2

All Rights Reserved Alcatel-Lucent 2009, XXXXX

New and Modified Call Drop Radio and HO Drop counters


TMO FO results
The validation of the counters in TMO was done in 2 ways:
During the Repeated xACCH feature assessment
In the non-regression of the migration process.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

New and Modified Call Drop Radio and HO Drop counters


TMO FO results
Check if new counters (basic indicators) for AMR
Indicator
refname

Long Name

Formula

Value

GTCNRFACN

AMR_TCH_DROP_OUT_HO_No_RFACCH_Activated

MC995

OK

GTCRFACN

AMR_TCH_DROP_OUT_HO_RFACCH_Activated

MC996

OK

GTCNRSACN

AMR_TCH_DROP_No_RSACCH_Activated

MC993

OK

GTCRSACN

AMR_TCH_DROP_RSACCH_Activated

MC994

OK

* Inconsistency detected at TRX level in CMCC are not seen in TMO

All Rights Reserved Alcatel-Lucent 2009, XXXXX

New and Modified Call Drop Radio and HO Drop counters


TMO FO results
Check if Call drop radio and Call drop HO are stable.
Essen1_E
RTCH_success_end
Call_drop_radio
Call_drop_HO
Call_drop_BSS_int_failure
Call_drop_BSS_remote_TC
Call_drop_preemption
Call_drop
Call_drop_rate
RTCH_drop_rate
RTCH_success_begin
Call_drop_Long_Distance
Call_drop_Other_Causes
Call_drop_Short_Distance
Call_drop_UL_Interference
Call_drop_UL_Level
Call_drop_UL_Quality
Call_drop_DL_Interference
Call_drop_DL_Level
Call_drop_DL_Quality
Call_drop_radio_rate
Call_drop_HO_rate

B10MR2Ed6.2

B11MR1Ed1.2

125278
685
231
4
10
0
930
0.74%
0.32%
292619
0
300
0
1
85
183
7
70
270
0.55%
0.18%
All Rights Reserved Alcatel-Lucent 2009, XXXXX

Delta (B11 avg -

B10 avg)

118408
653
209
4
2
0
867
0.73%
0.31%
278845
0
303
0
0
81
153
5
64
255
0.55%
0.18%

-6871
-32
-23
0
-7
0
-62
-0.01%
-0.01%
-13774
0
3
0
0
-4
-31
-2
-6
-15
0.00%
-0.01%

Agenda
New CS counters discarded messages / SS7 clear request
Theoretical overview
Feature activation & compatibility with previous HW
Telecom parameters, counters & Indicators
Test strategy
R&D system tests results
CMCC FO results B11 MR1 ed1.0
TMO FO results B11 MR1 ed1.1

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview: New CS counters discarded messages


Currently there is no counter to have the information related to the paging messages
received on A interface.

In real networks, RNE in China often face the following situations:


1. BSC1 and BSC 2 belong to same LAC but numbers of paging messages are
different for the same period (for example 100000 per hour for BSC 1 but
200000 per hour for BSC2).
2. Only one LAC is mapped on a BSC but the number of paging messages grows
suddenly and abnormally (for example from 100000 per hour to 200000 per
hour).

These situations may happen if wrong data exists in MSC to which the BSCs are
connected.

This problem can be detected on the LAC information in paging messages on A


interface through A interface traces which is too costly.

A new counter was created to give the number of PAGING messages received by the BSC
from any MSC!
Expected Benefits: Easier analysis of CCCH load
All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview: New CS counters SS7 clear request


Currently the counter C182 (type 18), that gives the number of 48.008 CLEAR REQUEST
sent to the MSC for calls in TCH established phase, is only available when is activated in
OMC.
A new counter was created to give it in a permanent way (type 110 counter)

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Feature activation & compatibility with


previous HW

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Feature Activation
Feature activation per default.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Compatibility with previous HW generation and restrictions


Compatibility with previous HW generation
Inline with B11
Restrictions & Limitations
None

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Parameters, Counters, Indicators

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Parameters

No new or modified parameters linked to this feature.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Counters: New CS counters discarded messages/SS7 clear request


New BSC Counters (1/2)
Counter
refname
MC940

Definition

Measured
object

Domain

Type

Number of 48.008 PAGING messages


received by the BSC from any MSC

BSC

Traffic
Load

110

BSC

Quality
of
Service

110

Long Name
NB_A_PAGING_MSG

Number of 48.008 CLEAR REQUEST sent to


the MSC for calls in TCH established
phase, and for internal inter-cell and
external TCH handover failures. Intra-cell
MC182

NB_N7_CLEAR_REQ_EST_P handover failures are not taken into


HAS
account.
This counter takes into account TCH in
traffic

mode

or

in

signaling

mode.

C182=MC182

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Indicators: New CS counters discarded messages/SS7 clear request


New BSC Indicators:
Indicator
refname

Long Name

Formula

GTCNAAPRN A_Paging_Message_received MC940

GQSACDMN

A_call_drop

MC182

Description
Number of 48.008 PAGING messages received by the
BSC from any MSC.
Number of 08.08 CLEAR REQUEST sent to the MSC
for calls in TCH established phase, and for internal
inter-cell and external TCH handover failures.
Intra-cell handover failures are not taken into
account.

GQSACDMR

A_call_drop_rate

GQSTCACDMR A_RTCH_drop_rate

Rate of CLEAR REQUEST sent to the MSC for calls in


TCH established phase, and for internal inter-cell
A_call_drop
/
and external TCH handover failures. Intra-cell
RTCH_success_end
handover failures are not taken into account. Intracell handover failures are not taken into account.
Rate of CLEAR REQUEST sent to the MSC for calls in
TCH established phase, and for internal inter-cell
A_call_drop
/
RTCH_success_begin and external TCH handover failures over the total
amount of calls established in the cell. Intra-cell
handover failures are not taken into account.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

LA & CCCH
PCH counters

MC8a
Pagingrequest
message

MS

PCHblocks
onCCCH

MC925g

Pagingcommand
message(CS+PSPaging)

Pagingrequest
(PS/CSPaging)
or
Packetdownlink
assignmentmessage

MSC

MC940

AterMUX-CS

BTS
Cell

TC

CSPaging
(SS7)

Abis(RSL)

BSC

Pagingcommandmessage
(PS/CSPaging)
or
Immediateassigncommand
message

Gs

AterMUX-PS
P53a + P53b

(GSL)

PS/CSPagingmessage
or
Channelassignment
downlinkmessage

MC805b
P53c

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Gb
MFS
GPU

SGSN

Test Strategy

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Test Strategy: New CS counters discarded messages/SS7 clear request


Requirements
type of tests: statistical tests
type of analysis: QoS
objective of each test type:

It is intended to correlate the new and existing counters in order to be validate


correctly the new counters.

Only in case of issues detected the following traces should be collected


Radio traces
Ater/Abis/A traces

required tools: NPO and K15 tools


required means: 1 RNE and 1 TSC (L1) Support
estimated duration of the tests (post-processing included): 2 weeks

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Impacts on the internal tools

Tool

Follow-up status

NPO/NPO4U

closed

AnaQoS

On-going

Comments

Specific counters/indicators/reports already created

Counters will be updated in the information of the


feature slides. No specific extra work from expert
group

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Tool version with feature


data configuration
since NPO30D06 for MC182
since NPO30D15 for MC940

Version 3.5.1.

R&D system test results

49 | B10 mCCCH | September 2008

All Rights Reserved Alcatel-Lucent 2009, XXXXX

System validation tests of the feature


Not available

All Rights Reserved Alcatel-Lucent 2009, XXXXX

CMCC FO Results B11 MR1 ed1.0

All Rights Reserved Alcatel-Lucent 2009, XXXXX

New CS counters discarded messages/SS7 clear request


CMCC FO results
1. Check Counters availability in NPO
Counter
refname

Long Name

Available in NPO

MC940

NB_A_PAGING_MSG

YES

MC182

NB_N7_CLEAR_REQ_EST_PHAS

YES

All Rights Reserved Alcatel-Lucent 2009, XXXXX

New CS counters discarded messages/SS7 clear request


CMCC FO results
3. Check new indicator availability with values

A_Paging_Message_received Hourly Daily Weekly Monthly


BSC

OK

OK

OK

OK

Network

OK

OK

OK

OK

A_call_drop

Hourly Daily Weekly Monthly

BSC

OK

OK

OK

OK

Network

OK

OK

OK

OK

All Rights Reserved Alcatel-Lucent 2009, XXXXX

New CS counters discarded messages/SS7 clear request


CMCC FO results
4. Correlate the new and the existing indicators:
For MC940 counter validation the following formula must be verified:

BSC with only one LAC mapped


Counters formula: MC8a - P53a - P53b =< MC940
Indicators formula: CCCH_PCH - GPRS_PS_Paging_Request_in_PS GPRS_CS_Paging_Request_in_PS =< A_Paging_Message_received

BSC with more than one LAC mapped


Sum of LAC (MAX (MC8a - P53a - P53b) for each cell) <= MC940 for BSC

The condition is not always verified!

See next slide

All Rights Reserved Alcatel-Lucent 2009, XXXXX

New CS counters discarded messages/SS7 clear request


CMCC FO results
4. Correlate the new and the existing indicators:
For MC940 counter validation

Per Hour

Impact of including in the formula counters coming


from different NE, ones from MFS others BSC. No
synchronization exist. This issue is relevant when the
traffic considerably increase or decrease
All Rights Reserved Alcatel-Lucent 2009, XXXXX

New CS counters discarded messages/SS7 clear request


CMCC FO results
4. Correlate the new and the existing indicators:
For MC182 counter validation the following formula must be verified:

The number of dropped calls (system + handover + radio + preemption) should


be similar to the number of drops in A interface:
Counters formula: ((MC736+MC993+MC994) + (MC621+MC995+MC996) +
(MC14c+MC739) + MC921c) MC182
Indicators formula: (Call_drop_radio + Call_drop_HO + Call_drop_BSS +
Call_drop_preemption) A_call_drop

The sum of the call drop measured per cell is higher than the call drop
measured per BSC in the A interface.

See next slide

All Rights Reserved Alcatel-Lucent 2009, XXXXX

New CS counters discarded messages/SS7 clear request


CMCC FO results
4. Correlate the new and the existing indicators:

For MC182 counter validation

The deviation
The trigger condition of MC182 was under analysis by SYT.
observed was
considered

One issue already detected but not impacting this case, the intracell HO drops are not taken
in account in
acceptable
the MC182.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

TMO FO Results B11 MR1 ed1.1

All Rights Reserved Alcatel-Lucent 2009, XXXXX

New CS counters discarded messages/SS7 clear request


TMO FO results
1. Check Counters availability in NPO
Counter
refname

Long Name

Available in NPO

MC940

NB_A_PAGING_MSG

YES

MC182

NB_N7_CLEAR_REQ_EST_PHAS

YES

All Rights Reserved Alcatel-Lucent 2009, XXXXX

New CS counters discarded messages/SS7 clear request


TMO FO results
2. Check new indicator availability with values

A_Paging_Message_received Hourly Daily


BSC

OK

OK

Network

OK

OK

A_call_drop

Hourly Daily

BSC

OK

OK

Network

OK

OK

All Rights Reserved Alcatel-Lucent 2009, XXXXX

New CS counters discarded messages/SS7 clear request


TMO FO results
3. Correlate the new and the existing indicators:
For MC940 counter validation the following formula must be verified:

BSC with only one LAC mapped


Counters formula: MC8a - P53a - P53b =< MC940
Indicators formula: CCCH_PCH - GPRS_PS_Paging_Request_in_PS GPRS_CS_Paging_Request_in_PS =< A_Paging_Message_received

BSC with more than one LAC mapped


Sum of LAC (MAX (MC8a - P53a - P53b) for each cell) <= MC940 for BSC

The condition is not verified!

See next slide

All Rights Reserved Alcatel-Lucent 2009, XXXXX

New CS counters discarded messages/SS7 clear request


TMO FO results
3. Correlate the new and the existing indicators:
For MC940 counter validation

Per day

Several FRs open for this counter:


3BKA36FBR287650 In S221 (TDM 2G-B11MR2) MC940 is always counter lower than reality
3BKA36FBR279758 In S221 (TDM 2G-B11) Wrong values for MC940 Nb of Pagings from
MSC(see 3BKA20FBR273881) - Corrected in MR1ED2/BSCSAZ06F
3BKA45FBR293010 [TMO - B11MR1Ed1.2] [NE] Inconsistencies on Paging counters (MC940,
P53b)
All Rights Reserved Alcatel-Lucent 2009, XXXXX

New CS counters discarded messages/SS7 clear request


TMO FO results
3. Correlate the new and the existing indicators:
For MC182 counter validation the following formula must be verified:

The number of dropped calls (system + handover + radio + preemption) should be


similar to the number of drops in A interface:
Counters formula: ((MC736+MC993+MC994) + (MC621+MC995+MC996) + (MC14c+MC739)
+ MC921c) MC182
Indicators formula: (Call_drop_radio + Call_drop_HO + Call_drop_BSS +
Call_drop_preemption) A_call_drop

The condition is verified, the delta is less than 0.1%

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Agenda
GSL (or BSCGP) interface counters
Theoretical overview
Feature activation & compatibility with previous HW
Telecom parameters, counters & Indicators
Test strategy
R&D system tests results
CMCC FO results B11 MR1 ed1.0
TMO FO results B11 MR1 ed1.2

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview: GSL (or BSCGP) interface counters (1/5)


1. GSL (or BSCGP) interface counters

GSL

BSCGP: BSC GPRS Protocol


GSL: GPRS Signalling Link

GSL or BSCGP interface:

Its an interface for PS signalling between BSC and MFS. It handles signalling for GPRS
paging and for all synchronization between the BSC and the MFS (TS 28).
Its composed by several GSL links.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview: GSL (or BSCGP) interface counters (2/5)


Two cases are possible as regards BSCGP transport mode:
In TDM mode the architecture layer up to BSCGP is:
Existing MFS counters
AterMux interface

GSL link = LAPD l


ink
18 GSL links
per G2 BSC
24 GSL links
per Mx BSC
No counters on BSC side!
Existing counters only for each LAPD
link associated to a RSL link

BSCGP

BSCGP

LAPD
E1

LAPD

BSC

MFS

E1

8 GSL links
(4 tested) per
GP(U)
1 GSL link
per AterMux

In IP mode it changed to:


IP GSL link =
TCP connection
12 IP GSL links
per Mx BSC

BSCGP

BSCGP

TCP/IP

TCP

Ethernet

Ethernet

BSC

MFS
All Rights Reserved Alcatel-Lucent 2009, XXXXX

1 GSL link
per GP
1 GSL link
per AterMux

No counters
for BSCGP
level!

Theoretical Overview: GSL (or BSCGP) interface counters (3/5)


In B9/B10 is not possible to properly dimension the GSL configuration, due to
lack of counters.

The transmitting window size is very important, specially in case of satellite


GSL links (due to the longer acknowledgement timer and longer round trip
delay), because it limits the number of BSCGP messages per second.

The scope of this feature is to have new counters related to the GSL interface
in order to ease the BSCGP protocol dimensioning for both possible
configurations: terrestrial and satellite configurations*.

* Improvement supported in TDM mode and in IP mode and both terrestrial and
satellite configurations.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview: GSL (or BSCGP) interface counters (4/5)


Benefits
Ease the dimensioning assessment of GSL interface for both TDM and IP
transport architectures currently the GSL load is manually estimated by
using a very complex method.

Estimate in a more precise way the percentage of signalling in order to be able


to better characterise the traffic profile of a given network

These new counters will be very important due to the GSL exchange increased
in B10 and B11 with new BSCGP messages such as DTM Shared Info or paging
coordination.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview: GSL (or BSCGP) interface counters (5/5)


New counters are defined at BSCGP application level to configure window size
and acknowledgement timer:
For BSC:
Number of UL GSL messages;
Maximum number of UL GSL messages;
Average Number Max of UL GSL messages.
For MFS:
Number of DL GSL messages;
Maximum number of DL GSL messages;
Average Number Max of DL GSL messages

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Feature activation & compatibility with


previous HW

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Feature Activation
Feature activation per default.
The type 7 new counters must be activated in OMC-R in order to be
available.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Compatibility with previous HW generation and restrictions


Compatibility with previous HW generation
Depending on the transport mode:
the TDM mode is available on G2/MX BSC and on Legacy/MX MFS.
the IP mode is available on MX BSC and MX MFS.

Restrictions & Limitations


None

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Parameters, Counters, Indicators

74 | B10 mCCCH | September 2008

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Parameters

No new or modified parameters linked to this feature.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Counters: GSL (or BSCGP) interface counters


New BSC Counters (1/3)
Counter
refname

Long Name

MC1060

NB_GSL_MSG_SENT

MC1061

NB_GSL_MSG_DISCARDED

MC1062

NB_GSL_MSG_RESENT

MC1063

NB_GSL_MSG_RECEIVED

MC1064

NB_GSL_BYTES_SENT

Definition
Number of GSL messages sent by the BSC
to the MFS on one GSL link (this could be
BSCGP or BSCLP messages).
Number of GSL messages discarded by the
BSC (i.e not sent to the MFS) on one GSL
link (this could be BSCGP or BSCLP
messages).
Number of GSL messages resent by the
BSC to the MFS on one GSL link (this could
be BSCGP or BSCLP messages).
Number of BSCGP messages received by
the BSC from the MFS on one GSL link.
Number of bytes sent to the MFS on 1 GSL
link. There is only 1 GSL link per GP(U) in
the MFS.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Measured
object

Domain

Type

GSL

Traffic
Load

110

GSL

Traffic
Load

110

GSL

Traffic
Load

110

GSL

Traffic
Load

110

GSL

Traffic
Load

110

Telecom Counters: GSL (or BSCGP) interface counters


New BSC Counters (2/3)
Counter
refname

Long Name

Definition

Counts the maximum number of bytes of


the GSL flow sent by the BSC to a given
MC1065 MAX_NB_GSL_BYTES_SENT
GPU in one minute during the
granularity period of monitoring.
Counts the maximum number of GSL
messages (BSCGP or BSCLP) sent by the
BSC on a given GSL link to the MFS in one
MC1066 MAX_NB_GSL_MSG_SENT
minute during the granularity period of
monitoring.
There is only 1 GSL link per GP in the
MFS.
Average number of GSL messages (BSCGP
or BSCLP) queued in the BSC
MC1067 AVERAGE_NB_MSG_IN_GSL_QUEUE
transmission buffer of one GSL link (at
Layer 2 level).
Number of data link establishment, reL2.1
NB_GSL_LAPD_ESTAB
establishment and reset on the GSL LapD
link.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Measured
object

Domain

Type

GSL

Traffic
Load

110

GSL

Traffic
Load

110

GSL

Traffic
Load

110

GSL

Quality
of
Service

07

Telecom Counters: GSL (or BSCGP) interface counters


New BSC Counters (3/3)
Counter
refname
L2.2
L2.3
L2.4
L2.5

L2.6

L2.7

Long Name

Definition

Number of frames received with


CRC error on the GSL LapD link.
Number of Information frames reNB_GSL_LAPD_INFO_FRAME_RESENT
transmitted on the GSL LapD link.
Number of Receive Not Ready (RNR)
NB_GSL_LAPD_RNR_SENT
frames transmitted on the GSL LapD
link.
Number of Receive Not Ready (RNR)
NB_GSL_LAPD_RNR_REC
frames received on the GSL LapD
link.
Time (in seconds) during which the
TIME_GSL_LAPD_UNAVAIL
GSL LapD link is unavailable for any
cause.
NB_GSL_LAPD_CRC_ERROR

TIME_GSL_LAPD_CONG

Time in seconds during which the


GSL LapD link is congested in
transmission in the BSC.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Measured
object

Domain

Type

GSL

Quality of
Service
Quality of
Service

GSL

Quality of
Service

07

GSL

Quality of
Service

07

GSL

Quality of
Service

07

GSL

Quality of
Service

07

GSL

07
07

Telecom Counters: GSL (or BSCGP) interface counters


New MFS Counters (1/2)
Counter
refname
P7a
P7b
P7c_1

P7c_2
P7d
P7e

LongName

Definition

Number of BSCGP messages sent by


the MFS to the BSC.
Number of BSCGP messages sent by
NB_BSCGP_MSG_DISCARDED
MFS that are discarded.
This counter cumulates the time
CUMULATED_TIME_ONGOING_QUEUE
during which the on going QUEUE_A
_A_FULL
is full during the GP.
This counter cumulates the time
CUMULATED_TIME_ONGOING_QUEUE
during which the on going QUEUE_B
_B_FULL
is full during the GP.
Number of BSCGP messages resent
NB_BSCGP_MSG_RESENT
by the MFS to the BSC.
Number of
BSCGP messages
NB_BSCGP_MSG_RECEIVED
received by the MFS from the BSC
NB_BSCGP_MSG_SENT

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Measured
object

Domain

Type

GPU

GSL

MFS

GPU

GSL

MFS

GPU

GSL

MFS

GPU

GSL

MFS

GPU

GSL

MFS

GPU

GPU

MFS

Telecom Counters: GSL (or BSCGP) interface counters


New MFS Counters (2/2)
Counter
refname
P7f

P7g

P7h

P7i

Measured
object

Domain

Type

of
BSCGP
CHANNEL
and
DTM
REQUEST
received by the MFS from

GPU

GPU

MFS

of bytes of BSCGP
sent by the MFS to the

GPU

GPU

MFS

MAX_NB_BSCGP_BYTES_SENT

Maximum number of bytes of


BSCGP messages sent by the MFS
to the BSC in one minute.

GPU

GPU

MFS

MAX_NB_BSCGP_MSG_SENT

Maximum
number
of
BSCGP
messages sent by the MFS to the
BSC in one minute.

GPU

GPU

MFS

LongName

NB_BSCGP_CHANNEL_REQ_RECEIVED

NB_BSCGP_BYTES_SENT

Definition
Number
REQUEST
messages
the BSC.
Number
messages
BSC.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Counters: GSL (or BSCGP) interface counters: Table summary


L2-GSL
Obs.
Inst.

At BSC side
-----------------------

P41
Nb kB sent
P42
Nb kB rec
P2b
Nb rnr frames sent
P2c
Nb rnr frames received
-----------P2a
Nb info frame resent
P32
Time LAPD link unavail
P2d
Nb estab reset
------------

(per IP GSL
ie per TCP connection)

IP mode

(per LAPD link)

TDM mode

L2.4
Nb rnr frames sent
L2.5
Nb rnr frames received
L2.2
Nb frames received with
crc error
L2.3
Nb info frame resent
L2.6
Time LAPD link unavail
L2.1
Nb estab reset
L2.7
Time LAPD link cong

At MFS side

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Counters: GSL (or BSCGP) interface counters: Table summary


BSCGP (TDM and IP mode)
Obs.
inst.

At BSC side

At MFS side

(for BSC : per GSL link


and for MFS : per GSL link)

MC1060
Nb GSL msg sent
MC1061
Nb GSL msg discarded
MC1067
Nb GSL msg avg sent queued
MC1062
Nb GSL msg resent
MC1063
Nb GSL msg received
Nb of channel required sent
by BSC = MC804 a + b
MC1064
Nb GSL bytes sent
MC1065
Max nb GSL bytes sent (one
minute)
MC1066
Max nb GSL msg sent (one
minute)

P7a
Nb GSL msg sent
P7b
Nb GSL msg discarded
P7c_1 and P7c_2
Nb GSL msg avg queued
P7d
Nb GSL msg resent
P7e
Nb GSL msg received
P7f
Nb channel req rec
P7g
Nb GSL bytes sent
P7h
Max nb GSL bytes sent (one
minute)
P7i
Max nb GSL msg sent (one minute)

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Indicators: GSL (or BSCGP) interface counters


New BSC Indicators (1/3):
Indicator
refname
GGSLBSMFMSN
GGSLBSMFMDN

Long Name

Formula

GSL_BSC_MFS_Message_Discarded MC1061

Number of GSL messages sent by the BSC to the


MFS on one GSL link (this could be BSCGP or BSCLP
messages).
Number of GSL messages discarded by the BSC (i.e
not sent to the MFS) on one GSL link (this could be
BSCGP or BSCLP messages).

GSL_BSC_MFS_Message_Resent

Number of GSL messages resent by the BSC to the


MFS on one GSL link (this could be BSCGP or BSCLP
messages).

GSL_BSC_MFS_Message_Sent

MC1060

GGSLBSMFMRSN

GGSLBSMFMRN

Description

MC1062

Number of BSCGP messages received by the BSC


GSL_BSC_MFS_Message_Received

MC1063

from the MFS on one GSL link.


Number of bytes sent to the MFS on 1 GSL link.

GGSLBSMFSBYN

GSL_BSC_MFS_Sent_Bytes

MC1064

There is only 1 GSL link per GP(U) in the MFS.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Indicators: GSL (or BSCGP) interface counters


New BSC Indicators (2/3):
Indicator
refname

Long Name

Formula

MC1065

Maximum number of bytes of the GSL flow sent


by the BSC to a given GPU in one minute during
the granularity period of monitoring.

MC1066

Maximum number of GSL messages (BSCGP or


BSCLP) sent by the BSC on a given GSL link to
the MFS in one minute during the granularity
period of monitoring.
There is only 1 GSL link per GP in the MFS.

MC1067

Average number of GSL messages (BSCGP or


BSCLP) queued in the BSC transmission buffer of
one GSL link (at Layer 2 level).

MC1062 /
MC1060

Ratio of the number of GSL messages resent by


the BSC to the MFS on one GSL link (this could
be BSCGP or BSCLP messages).

MC1061 /
GSL_BSC_MFS_Message_Discarded_ratio MC1060

Ratio of the number of GSL messages discarded


by the BSC (i.e not sent to the MFS) on one GSL
link (this could be BSCGP or BSCLP messages).

GGSLBSMFSBYMN GSL_BSC_MFS_Sent_Bytes_Max

GGSLBSMFMSMN GSL_BSC_MFS_Message_Sent_Max

GGSLBSMFMSA

GGSLBSMFMRSO

GGSLBSMFMDO

Description

GSL_BSC_MFS_Message_Sent_Avg

GSL_BSC_MFS_Message_Resent_ratio

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Indicators: GSL (or BSCGP) interface counters


New BSC Indicators (3/3):
Indicator
refname
GGSLLPDDN
GGSLLPDCRERN
GGSLLPDIFRSN
GGSLLPDRNRSN
GGSLLPDRNRRN
GGSLLPDUNT
GGSLLPDCNGT

Long Name

Formula

Description

GSL_LAPD_Data

L2_1

GSL_LAPD_CRC_Er_Received

L2_2

Number of data link establishment, re-establishment


and reset on the GSL LapD link.
Number of frames received with CRC error on the
GSL LapD link.

GSL_LAPD_Info_Frame_Resent L2_3

Number of Information frames re-transmitted on the


GSL LapD link.

GSL_LAPD_RNR_Sent

L2_4

Number of Receive Not Ready


transmitted on the GSL LapD link.

L2_5

Number of Receive Not Ready (RNR) frames received


on the GSL LapD link.

GSL_LAPD_Unavailable_Time L2_6

Time (in seconds) during which the GSL LapD link is


unavailable for any cause.

GSL_LAPD_Congestion_Time

Time in seconds during which the GSL LapD link is


congested in transmission in the BSC.

GSL_LAPD_RNR_Received

L2_7

All Rights Reserved Alcatel-Lucent 2009, XXXXX

(RNR)

frames

Telecom Indicators: GSL (or BSCGP) interface counters


New MFS Indicators (1/2):
Indicator
refname
GGSLMFBSMSN
GGSLMFBSMDN
GGSLMFBSAT
GGSLMFBSBT

Long Name
GSL_MFS_BSC_BSCGP_Message_Sent
SL_MFS_BSC_BSCGP_Message_Discarded
GSL_Full_QueueA_Cumulated_Time
GSL_Full_QueueB_Cumulated_Time

GGSLMFBSMRSN GSL_MFS_BSC_BSCGP_Message_Resent
GGSLMFBSMRN

GSL_MFS_BSC_BSCGP_Message_Received

Formula

Description

P7a

Number of BSCGP messages sent by the MFS to


the BSC.

P7b

Number of BSCGP messages sent by MFS that


are discarded.

P7c_1

Cumulated time during which the on going


QUEUE_A is full during the GP.

P7c_2

Cumulated the time during which the on going


QUEUE_B is full during the GP.

P7d

Number of BSCGP messages resent by the MFS


to the BSC.

P7e

Number of BSCGP messages received by the


MFS from the BSC.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Indicators: GSL (or BSCGP) interface counters


New MFS Indicators (2/2):
Indicator
refname

Long Name

Formula

GGSLBSMFCRN

GSL_BSC_MFS_BSCGP_Channel_Request

P7f

GGSLMFBSSBYN

GSL_MFS_BSC_BSCGP_Sent_Bytes

P7g

GGSLMFBSSBYMN GSL_MFS_BSC_BSCGP_Sent_Bytes_Max

P7h

GGSLMFBSMSMN

P7i

GSL_MFS_BSC_BSCGP_Message_Sent_max

Description
Number of BSCGP CHANNEL REQUEST and
DTM REQUEST messages received by the MFS
from the BSC.
Number of bytes of BSCGP messages sent by
the MFS to the BSC.
Maximum number of bytes of BSCGP
messages sent by the MFS to the BSC in one
minute.
Maximum number of BSCGP messages sent by
the MFS to the BSC.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Test Strategy

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Test Strategy: GSL (or BSCGP) interface counters


Requirements
type of tests: statistical tests
type of analysis: QoS
objective of each test type:

It is intended to correlate the new and existing counters in order to be validate


correctly the new counters.

required tools: NPO, AMT/Traffic and K15 tools


required means: 1 RNE + 1 TSC Engineer for trace collection
estimated duration of the tests (post-processing included): 2 weeks

* Possibility of feature validation in FOA platform.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Impacts on the internal tools

Tool

Follow-up status

NPO/NPO4U

closed

Comments
Specific counters/indicators/reports already created

AnaQoS

On-going

Counters will be updated in the information of the


feature slides. No specific extra work from expert
group

AMT (Traffic
tool)

On-going

Counters will be updated in the information of the


feature slides. No specific extra work from expert
group

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Tool version with feature data


configuration
NPO30D10 / AX30D10 / MA30D07

Version 3.5.1.

End of July

R&D system test results

All Rights Reserved Alcatel-Lucent 2009, XXXXX

System validation tests of the feature


Not available

All Rights Reserved Alcatel-Lucent 2009, XXXXX

CMCC FO Results B11 MR1 ed1.0

All Rights Reserved Alcatel-Lucent 2009, XXXXX

GSL (or BSCGP) interface counters


CMCC FO results
1. Check Counters availability in NPO (1/2)
No counters available at MFS side for GSL and BSCGP interfaces

3BKA20FAG287268: CMCC B11MR1Ed1 pilot: After B11 migration, the MFS


counters P7a, P7b, P7c_1, P7c_2, P7d, P7e, P7f, P7g, P7h & P7i are always
equal to zero.

Correction confirmed in ed1.2

Transferred to FR 3BKA20FAG286626
B11MR1ED1.2 - MFS.PATCH_MX.11_ rl50 .02UP _00D (GP on top of MFSXAZ02U) /
B11MR1ED2 - MFSXAZ06B

3BKA20FAG286626: CMCC B11MR1Ed1 pilot: After B11 migration, the MFS


counters P41 and P42 are without values.

Not Corrected
Closed
B11MR1ED1.2 - MFS.PATCH_MX.11_ rl50 .02UP _00D (GP on top of MFSXAZ02U) /
B11MR1ED2 - MFSXAZ06B

No counters available at BSC side for BSCGP interface

3BKA20FAG286649: CMCC B11MR1Ed1 pilot: The new B11 BSC GSL Counters
(MC1060 -> MC1067) in type 110 are empty. Corrected confirmed in ed1.2
B11MR1ED1.2 - patch OMC3.ADD.11_0.287772_03L on top of AZ03L / B11MR1ED2 OMCSAZ06G - W948
All Rights Reserved Alcatel-Lucent 2009, XXXXX

GSL (or BSCGP) interface counters


CMCC FO results
1. Check Counters availability in NPO (2/2)
BSC GSL counters - L2 family (L2.1 to L2.7) - OK

The counters are available in NPO

All Rights Reserved Alcatel-Lucent 2009, XXXXX

GSL (or BSCGP) interface counters


CMCC FO results
2. Check new indicators availability in NPO
BSC GSL counters - L2 family - OK
Group

Hourly

Daily

Weekly Monthly

GSL

OK

OK

OK

OK

BSS

OK

OK

OK

OK

Network

OK

OK

OK

OK

MFS

OK

OK

OK

OK

All Rights Reserved Alcatel-Lucent 2009, XXXXX

GSL (or BSCGP) interface counters


CMCC FO results
2. Correlate New and existing indicators
BSC GSL counters - L2 family

L2.4 >= P2c

P2b >= L2.5

MC1060 >= P7e

P7a >= MC1063

Not possible to verify due to missing


counter at GSL

All Rights Reserved Alcatel-Lucent 2009, XXXXX

TMO FO Results B11 MR1 ed1.2

All Rights Reserved Alcatel-Lucent 2009, XXXXX

GSL (or BSCGP) interface counters


TMO FO results
1. Check Counters/Indicators availability in NPO (1/3)
BSC GSL counters/indicators - L2 family (L2.1 to L2.7) - OK

The counters are available in NPO, although the value is 0, the reason looks
linked to no issues existing in the network

Long Name

Formula

Value on day 29/01/2010

GSL_LAPD_Data

L2_1

GSL_LAPD_CRC_Er_Received

L2_2

GSL_LAPD_Info_Frame_Resent

L2_3

GSL_LAPD_RNR_Sent

L2_4

GSL_LAPD_RNR_Received

L2_5

GSL_LAPD_Unavailable_Time

L2_6

GSL_LAPD_Congestion_Time

L2_7

All Rights Reserved Alcatel-Lucent 2009, XXXXX

GSL (or BSCGP) interface counters


TMO FO results
1. Check Counters/Indicators availability in NPO (2/3)

OK

BSC BSCGP counters/indicators MC106X family (MC1060 to MC1067)

The counters are available in NPO

Indicator
refname

Formula

Long Name

GGSLBSMFMSN

GSL_BSC_MFS_Message_Sent

GGSLBSMFMDN
GGSLBSMFMRSN

MC1060

Value per hour


29/01/2010 14:00

Value per day


29/01/2010

348125

6623922

GSL_BSC_MFS_Message_Discarded MC1061

GSL_BSC_MFS_Message_Resent

MC1062

GGSLBSMFMRN

GSL_BSC_MFS_Message_Received

MC1063

649764

12345183

GGSLBSMFSBYN

GSL_BSC_MFS_Sent_Bytes

MC1064

11789760

218220257

GGSLBSMFSBYMN GSL_BSC_MFS_Sent_Bytes_Max

MC1065

449298

450009

GGSLBSMFMSMN GSL_BSC_MFS_Message_Sent_Max

MC1066

GGSLBSMFMSA

MC1067

12839
0

13066
0

GSL_BSC_MFS_Message_Sent_Avg

All Rights Reserved Alcatel-Lucent 2009, XXXXX

GSL (or BSCGP) interface counters


TMO FO results
1. Check Counters/Indicators availability in NPO (3/3)

OK

MFS BSCGP counters/indicators P7X family (MC1060 to MC1067)

The counters are available in NPO

Indicator
refname

Long Name

Value per hour


29/01/2010 14:00

Formula

Value per day


29/01/2010

GGSLMFBSMSN

GSL_MFS_BSC_BSCGP_Message_Sent

P7a

649690

12351286

GGSLMFBSMDN

SL_MFS_BSC_BSCGP_Message_Discarded

P7b

GGSLMFBSAT

GSL_Full_QueueA_Cumulated_Time

P7c_1

GGSLMFBSBT

GSL_Full_QueueB_Cumulated_Time

P7c_2

GGSLMFBSMRSN

GSL_MFS_BSC_BSCGP_Message_Resent

P7d

GGSLMFBSMRN

GSL_MFS_BSC_BSCGP_Message_Received

P7e

348106

6627624

GGSLBSMFCRN

GSL_BSC_MFS_BSCGP_Channel_Request

P7f

103072

1758912

GGSLMFBSSBYN

GSL_MFS_BSC_BSCGP_Sent_Bytes

P7g

21620471

404831837

GGSLMFBSSBYMN GSL_MFS_BSC_BSCGP_Sent_Bytes_Max

P7h

6149

9438

GGSLMFBSMSMN

P7i

173

260

GSL_MFS_BSC_BSCGP_Message_Sent_max

All Rights Reserved Alcatel-Lucent 2009, XXXXX

GSL (or BSCGP) interface counters


TMO FO results
1. FR Status
3BKA20FAG287268: CMCC B11MR1Ed1 pilot: After B11 migration, the
MFS counters P7a, P7b, P7c_1, P7c_2, P7d, P7e, P7f, P7g, P7h & P7i are
always equal to zero.

Transferred to FR 3BKA20FAG286626
B11MR1ED1.2 - MFS.PATCH_MX.11_ rl50 .02UP _00D (GP on top of MFSXAZ02U)
/ B11MR1ED2 - MFSXAZ06B
CORRECTION CONFIRMED

3BKA20FAG286626: CMCC B11MR1Ed1 pilot: After B11 migration, the


MFS counters P41 and P42 are without values.

Closed
B11MR1ED1.2 - MFS.PATCH_MX.11_ rl50 .02UP _00D (GP on top of MFSXAZ02U)
/ B11MR1ED2 - MFSXAZ06B
CORRECTION CONFIRMED

3BKA20FAG286649: CMCC B11MR1Ed1 pilot: The new B11 BSC GSL


Counters (MC1060 -> MC1067) in type 110 are empty.

B11MR1ED1.2 - patch OMC3.ADD.11_0.287772_03L on top of AZ03L /


B11MR1ED2 - OMCSAZ06G - W948
CORRECTION CONFIRMED
All Rights Reserved Alcatel-Lucent 2009, XXXXX

GSL (or BSCGP) interface counters


TMO FO results
2. Correlate New and existing indicators

OK

L2.4 >= P2c

Both are 0

P2b >= L2.5

Both are 0

MC1060 >= P7e

The condition is not always verified but with delta less than 0.06%, we consider
acceptable

P7a >= MC1063

The condition is not always verified but with delta less than 0.05%, we consider
acceptable

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Agenda
PS traffic differentiation between user data traffic and the
signalling traffic
Theoretical overview
Feature activation & compatibility with previous HW
Telecom parameters, counters & Indicators
Test strategy
R&D system tests results
CMCC FO results B11 MR1 ed1.0
TMO FO results B11 MR1 ed1.1

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview: PS traffic differentiation between user data traffic and


the signaling traffic (1/3)
The BSS handles the signalling traffic differently from the user traffic, especially
at the resource (radio and transmission) management.

Currently there are no separate counters (or indicators) to evaluate the signalling
percentage, in terms of TBFs number.

In order to evaluate weight of signalling traffic, in terms of number of TBFs, NE


requested to have dedicated MFS counters to give the DL(UL) TBF successfully
established to carry signalling traffic.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview: PS traffic differentiation between user data traffic and


the signaling traffic (2/3)
The current algorithm allows transition from Signalling to Data (T3 reallocations
and concurrent TBF establishment may occur during the TBF life, changing the
traffic type value), but not the reverse.
So considering the establishment time may lead to over-estimate the UL signalling
part, it was proposed to consider the traffic type value at TBF release time only
(whatever the release end, normal or abnormal) instead of TBF establishment
success.
The total DL(UL) TBF releases number (data + signalling) is already known, in
consequence is also possible to retrieve the data traffic weight in term of TBFs
releases.
WARNING : since these new counters definition is closed to the RRM-PCC algorithm, any
change in this algorithm has impact on these counters (no impact on the definition, but on
the implementation). Discussions are currently on going on this algorithm in the B10 scope.
All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview: PS traffic differentiation between user data traffic and


the signaling traffic (3/3)
Benefits
More information about the PS traffic is available.
This information will be firstly used by ALU team to enhance the Traffic Model definition
in order to be as close as possible to the real traffic, and secondly by the system
validation team to load the BSS with a nominal traffic load corresponding to that traffic
model.
The signaling-user traffic distribution is also an input of the GSL dimensioning tool used
by the NE team.
The available information will be useful also for network optimization and for
investigations of PS indicators variations.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Feature activation & compatibility with


previous HW

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Feature Activation
Feature activation per default.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Compatibility with previous HW generation and restrictions


Compatibility with previous HW generation
Inline with B11

Restrictions & Limitations


None

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Parameters, Counters, Indicators

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Parameters

No new or modified parameters linked to this feature.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Counters: PS traffic differentiation between user data traffic and the
signalling traffic
New Counters
Counter
refname

Long Name

Definition

Measured
object

P181a

NB_DL_TBF_REL_SIG

Number of DL TBF released which carries


signalling data.

CELL

Number of UL TBF released which carries


signalling data.

CELL

P181b

NB_UL_TBF_REL_SIG

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Domain
Quality of
service
Quality of
service

Type

MFS

MFS

Telecom Indicators: PS traffic differentiation between user data traffic and the
signalling traffic (1/2)
New MFS Indicators:
Indicator
refname

GTRDRSGN

Long Name

GPRS_DL_TBF_Rel_Signalling

Formula

P181a
GPRS_DL_TBF_Success

GTRDRDTN

GPRS_DL_TBF_Rel_Data

GPRS_DL_TBF_Rel_Signalling

Description
Number of DL TBF released (normal
and abnormal) which carries signalling
data.
Number of DL TBF released (normal
and abnormal) which carries data
traffic.

GPRS_DL_TBF_Rel_Data /

GTRDRDTR

GTRDRSGR

Rate of DL TBF released (normal and


GPRS_DL_TBF_Rel_Data_rate
GPRS_DL_TBF_Success
abnormal) which carries data traffic.
Rate of DL TBF released (normal and
GPRS_DL_TBF_Rel_Signalling /
abnormal) which carries signalling
GPRS_DL_TBF_Rel_Signalling_rate GPRS_DL_TBF_Success
traffic.

P181a + DL_TBF_rel_data = sum of P90x (for all the cells of the GPU)

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Indicators: PS traffic differentiation between user data traffic and the
signalling traffic (2/2)
New MFS Indicators:
Indicator
refname
GTRURSGN

Long Name
GPRS_UL_TBF_Rel_Signalling

Formula
P181b

Description
Number of UL TBF released (normal and
abnormal) which carries signalling data.

GPRS_UL_TBF_Success
GTRURDTN

GPRS_UL_TBF_Rel_Data

Number of UL TBF released (normal and


GPRS_UL_TBF_Rel_Signalling abnormal) which carries data traffic.
GPRS_UL_TBF_Rel_Data /

GTRURDTR

GPRS_UL_TBF_Rel_Data_rate

GPRS_UL_TBF_Success
GPRS_UL_TBF_Rel_Signalling

GTRURSGR

GPRS_UL_TBF_Rel_Signalling_rate / GPRS_UL_TBF_Success

Rate of UL TBF released (normal and


abnormal) which carries data traffic.
Rate of UL TBF released (normal and
abnormal) which carries signalling traffic.

P181b + UL_TBF_rel_data = sum of P30x (for all the cells of the GPU)

All Rights Reserved Alcatel-Lucent 2009, XXXXX

NPO reports

Two new views was included in Alc_Mono_GPRS_Telecom:

NPO report name

Views in the report

Description of the views

Alc_GPRS_DL_TBF_tra This view provides information related to


DL TBF Traffic type: Signalling or data.
Alc_Mono_GPRS_T ffic_type
elecom
Alc_GPRS_UL_TBF_tra This view provides information related to
ffic_type
UL TBF Traffic type: Signalling or data.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Test Strategy

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Test Strategy: PS traffic differentiation between user data traffic and the
signalling traffic
Requirements

type of tests: statistical tests

type of analysis: QoS

objective of each test type:

It is intended to correlate the new and existing counters in order to be validate correctly
the new counters.

required tools: NPO and K15

required means: 1 RNE + 1 TSC Engineer for trace collection

estimated duration of the tests (post-processing included): 2 weeks

* Possibility of feature validation in FOA platform.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Impacts on the internal tools

Follow-up status

NPO/NPO4U

closed

Specific counters/indicators/reports already created

NPO31D17

On-going

Counters will be updated in the information of the


feature slides. No specific extra work from expert
group

Version 3.5.1.

On-going

Counters will be updated in the information of the


feature slides. No specific extra work from expert
group

End of July

AnaQoS
AMT (Traffic
tool)

Comments

Tool version with feature data


configuration

Tool

All Rights Reserved Alcatel-Lucent 2009, XXXXX

R&D system test results

All Rights Reserved Alcatel-Lucent 2009, XXXXX

System validation tests of the feature


Not available

All Rights Reserved Alcatel-Lucent 2009, XXXXX

CMCC FO results B11 MR1 ed1.0

All Rights Reserved Alcatel-Lucent 2009, XXXXX

PS traffic differentiation between user data traffic and the signalling traffic
CMCC FO results
1. Check Counters availability in NPO OK

Counter
refname

Long Name

Definition

Measured
object

Domain

Type

P181a

NB_DL_TBF_REL_SIG

Number of DL TBF released which


carries signalling data.

CELL

Quality of service

MFS

P181b

NB_UL_TBF_REL_SIG

Number of UL TBF released which


carries signalling data.

CELL

Quality of service

MFS

Both counters are available in NPO

All Rights Reserved Alcatel-Lucent 2009, XXXXX

PS traffic differentiation between user data traffic and the signalling traffic
CMCC FO results

2. Check indicators availability in NPO - OK


Indicator
refname

Long Name

Formula

GTRDRSGN

GPRS_DL_TBF_Rel_Signalling

P181a

GTRURSGN

GPRS_UL_TBF_Rel_Signalling

P181b

Description
Number of DL TBF released
(normal and abnormal) which
carries signalling data.
Number of UL TBF released
(normal and abnormal) which
carries signalling data.

Group

Hourly

Daily

Weekly Monthly

Cell
BSS

OK
OK

OK
OK

OK
OK

OK
OK

Network
BTS
GPU

OK
OK
OK

OK
OK
OK

OK
OK
OK

OK
OK
OK

All Rights Reserved Alcatel-Lucent 2009, XXXXX

PS traffic differentiation between user data traffic and the signalling traffic
CMCC FO results
3. Correlate the new and existing indicators
GPRS_DL_TBF_Success > GPRS_DL_TBF_Rel_Signalling - OK

GPRS_UL_TBF_Success > GPRS_UL_TBF_Rel_Signalling - OK

All Rights Reserved Alcatel-Lucent 2009, XXXXX

TMO FO results B11 MR1 ed1.1

All Rights Reserved Alcatel-Lucent 2009, XXXXX

PS traffic differentiation between user data traffic and the signalling traffic
TMO FO results
1. Check Counters availability in NPO OK

Counter
refname

Long Name

Definition

Measured
object

Domain

Type

P181a

NB_DL_TBF_REL_SIG

Number of DL TBF released which


carries signalling data.

CELL

Quality of service

MFS

P181b

NB_UL_TBF_REL_SIG

Number of UL TBF released which


carries signalling data.

CELL

Quality of service

MFS

Both counters are available in NPO

All Rights Reserved Alcatel-Lucent 2009, XXXXX

PS traffic differentiation between user data traffic and the signalling traffic
TMO FO results

2. Check indicators availability in NPO - OK


Indicator
refname

Long Name

Formula

GTRDRSGN

GPRS_DL_TBF_Rel_Signalling

P181a

GTRURSGN

GPRS_UL_TBF_Rel_Signalling

P181b

Description
Number of DL TBF released
(normal and abnormal) which
carries signalling data.
Number of UL TBF released
(normal and abnormal) which
carries signalling data.

Group

Hourly

Daily

Weekly Monthly

Cell
BSS

OK
OK

OK
OK

OK
OK

OK
OK

Network
BTS
GPU

OK
OK
OK

OK
OK
OK

OK
OK
OK

OK
OK
OK

All Rights Reserved Alcatel-Lucent 2009, XXXXX

PS traffic differentiation between user data traffic and the signalling traffic
TMO FO results
3. Correlate the new and existing indicators
GPRS_DL_TBF_Success > GPRS_DL_TBF_Rel_Signalling - OK

GPRS_UL_TBF_Success > GPRS_UL_TBF_Rel_Signalling - OK

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Agenda
PS traffic differentiation between GPRS and EDGE (in case
of abnormal release)
Theoretical overview
Feature activation & compatibility with previous HW
Telecom parameters, counters & Indicators
Test strategy
R&D system tests results
CMCC FO results B11 MR1 ed1.0
TMO FO results B11 MR1 ed1.1

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview: PS traffic differentiation between GPRS and EDGE (in


case of abnormal release)
The TBF establishment rates and TBF release rates are based on counters which
apply both to GPRS and EGPRS MS.
Reminder

The purpose is to have simple way to distinct counters for GPRS and EGPRS.
Currently there is already a way to identify the EDGE penetration, through the
indicator GPRS_GPU_R99_EGPRS_MS_context_ratio which is the ratio of MS contexts
created for R99 mobile stations (EGPRS capable MS).

GPRS_GPU_R99_EGPRS_MS_context_ratio
= GPRS_GPU_R99_EGPRS_MS_context / (GPRS_GPU_R97_R98_MS_context
GPRS_GPU_R99_MS_context + GPRS_GPU_R99_EGPRS_MS_context)
= P450c / (P450a + P450b + P450c)

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview: PS traffic differentiation between GPRS and EDGE (in


case of abnormal release)
New counters for EGPRS are created in B11:
D/UL EGPRS TBF establishment request

There is no differentiation
for the TBF establishment
failures (Radio, Gb, BSS
and congestion) too
many counters

PIM (already existing)

PTM with concurrent TBF established

PTM during T3192 (only for DL)

D/UL EGPRS TBF establishment success

PIM (already existing)

PTM with concurrent TBF established

PTM during T3192 (only for DL)

D/UL EGPRS TBF normal releases

No differentiation for
TBF drop rate since no
counters for acceptable
releases.

Consequently, it is possible to retrieve the same information for GPRS TBFs.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Theoretical Overview: PS traffic differentiation between GPRS and EDGE (in


case of abnormal release)
Benefits
GPRS and EDGE use different modulation and coding schemes, therefore they
have different link adaptation algorithms and different impact to the radio
conditions.
In the previous releases it was not easily to correlate the TBF behavior with
the GPRS and EGPRS technologies.
The new counters will allow a better radio optimization by understanding
the impact of those radio conditions on different GPRS and EDGE traffic.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Feature activation & compatibility with


previous HW

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Feature Activation

Feature activation per default.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Compatibility with previous HW generation and restrictions


Compatibility with previous HW generation
Inline with B11

Restrictions & Limitations


None

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Parameters, Counters, Indicators

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Parameters

No new or modified parameters linked to this feature.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Counters: PS traffic differentiation between GPRS and EDGE (in case of
abnormal release)
New Counters (1/2)
Counter
refname
P90h

P90i

P91h

P91i

Long Name

Definition

NB_DL_TBF_EST_SUCC_EGPRS_ Number of DL TBF successfully established in


EGPRS mode when MS is in uplink packet transfer
MS_TRANSFER_UL
mode.
Number of DL TBF successfully established in
NB_DL_TBF_EST_SUCC_EGPRS_ EGPRS mode on PACCH while the timer T3192 is
T3192
running at BSS side.
Note: This counter applies to EGPRS MS.
Number of DL TBF establishment requests when
NB_DL_TBF_EST_REQ_EGPRS_
MS is in uplink packet transfer mode.
MS_TRANSFER_UL
Note: This counter applies to EGPRS MS.
Number of DL TBF establishment requests
NB_DL_TBF_EST_REQ_EGPRS_ received while the timer T3192 is running at BSS
T3192
side.
Note: This counter applies to EGPRS MS.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Measured
object

Domain

Type

CELL

Quality of
service

MFS

CELL

Quality of
service

MFS

CELL

Quality of
service

MFS

CELL

Quality of
service

MFS

Telecom Counters: PS traffic differentiation between GPRS and EDGE (in case of
abnormal release)
New Counters (2/2)
Counter
refname

Measured
object

Domain

Type

P62e

Number of UL TBF establishment


NB_UL_TBF_EST_REQ_EGPRS_
requests when the EGPRS MS is in
MSTRANSDL
downlink packet transfer mode.

CELL

Quality of
service

MFS

P30e

Number
of
UL
TBF
successfully
NB_UL_TBF_EST_SUCC_EGPRS
established in EGPRS mode when the MS
_MSTRANSDL
is in downlink packet transfer mode.

CELL

Quality of
service

MFS

Long Name

Definition

P9a

NB_DL_TBF_NORM_REL_EGPRS

Number of DL TBF in EGPRS mode normal


release.

CELL

Quality of
service

MFS

P22a

NB_UL_TBF_NORM_REL_EGPR Number of UL TBF in EGPRS mode normal


S
release.

CELL

Quality of
service

MFS

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Counters: PS traffic differentiation between GPRS and EDGE (in case of
abnormal release) Table Summary (1/2)

DL

EGPRS mode

GPRS mode

TBF normal release


TBF establishment requests

P9
P9a
GPRS + EGPRS mode
EGPRS mode

P9 - P9a
GPRS mode

Request Transfer mode

P91b

P91h

P91b - P91h

Request While T3192 running

P91e

P91i

P91e - P91i

TBF establishment successes

GPRS + EGPRS mode

GPRS + EGPRS mode

Success Transfer mode

P90b

Success While T3192 running

P90e

EGPRS mode
P90h
P90i

All Rights Reserved Alcatel-Lucent 2009, XXXXX

GPRS mode
P90b - P90h
P90e - P90i

Telecom Counters: PS traffic differentiation between GPRS and EDGE (in case of
abnormal release) Table Summary (2/2)

UL

GPRS + EGPRS mode

EGPRS mode

GPRS mode

GPRS + EGPRS mode

P22a
EGPRS mode

P22 - P22a
GPRS mode

P62e

(P62b-P438c)
P62e
GPRS mode

TBF normal release


TBF establishment requests

P22

Idle mode + no MPDCH

P62b-P438c

TBF establishment success


Transfer mode

GPRS + EGPRS mode


P30b

EGPRS mode
P30e

P30b P30e

P62b: Number of UL TBF establishment requests when the MS is in downlink packet


transfer mode. Note: This counter applies to GPRS and EGPRS MS.
P438c: Number of UL RLC control blocks received on PACCH/U for MS in packet idle
mode and used to carry NC2 signaling messages (when no PCCCH is established in
the cell)

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Indicators: PS traffic differentiation between GPRS and EDGE (in case
of abnormal release)
New MFS Indicators (1/7):
indicator refname

LongName

Formula

GTRDEGTSV5N

GPRS_DL_EGPRS_TBF_MS_
transfer_success
P90h

GTRDEGTRV5N

GPRS_DL_EGPRS_TBF_MS_
transfer_request
P91h

GTRDEGTSV4N

GPRS_DL_EGPRS_TBF_MS_
T3192_success
P90i

GTRDEGTRV4N

GPRS_DL_EGPRS_TBF_MS_
T3192_request
P91i

Description
Number of DL TBF successfully established in EGPRS mode
when MS is in uplink packet transfer mode.
Number of DL TBF establishment requests when MS is in
uplink packet transfer mode. Note: This counter applies to
EGPRS MS.
Number of DL TBF successfully established in EGPRS mode
on PACCH while the timer T3192 is running at BSS side.
Number of DL TBF establishment requests received while
the
timer
T3192
is
running
at
BSS
side.
Note: This counter applies to EGPRS MS.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Indicators: PS traffic differentiation between GPRS and EDGE (in case
of abnormal release)
New MFS Indicators (2/7):
Indicator refname

Long Name

Formula

Description

GTRDEGTESUN GPRS_DL_EGPRS_TBF_success

P90g + P90h + P90i Number of EGPRS DL TBF establishment


+ P506a
successes (seized by the mobile).

GTRDEGTERQN GPRS_DL_EGPRS_TBF_request

P91g + P91h + P91i Number of EGPRS DL TBF establishment


+ P505a
requests.
GPRS_DL_EGPRS_T
BF_success/
GPRS_DL_EGPRS_T

GTRDEGTESUR GPRS_DL_EGPRS_TBF_success_rate

BF_request

GTRUEGTRV5N GPRS_UL_EGPRS_TBF_MS_transfer_request P62e

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Rate of EGPRS DL TBF establishment


-successes (seized by the mobile).
Number of UL TBF establishment
requests when the EGPRS MS is in
downlink
packet
transfer
mode.
Note: This counter applies to EGPRS MS.

Telecom Indicators: PS traffic differentiation between GPRS and EDGE (in case
of abnormal release)
New MFS Indicators (3/7):
Indicator
- refname

Long Name

Formula

Description
Number of UL TBF successfully established

GPRS_UL_EGPRS_TBF_MS_transfer
GTRUEGTSV5N

_success

in EGPRS mode when the MS is in downlink


P30e

packet transfer mode.


Number of EGPRS UL TBF establishment

GTRUEGTESUN

GPRS_UL_EGPRS_TBF_success

P30d + P30e + P508a

successes (seized by the mobile).


Number of EGPRS UL TBF establishment

GTRUEGTERQN

GPRS_UL_EGPRS_TBF_request

P62d + P62e + P507a

requests.

GPRS_UL_EGPRS_TBF_s
uccess/GPRS_UL_EGPRS Rate of EGPRS UL TBF establishment
GTRUEGTESUR

GPRS_UL_EGPRS_TBF_success_rate _TBF_request

All Rights Reserved Alcatel-Lucent 2009, XXXXX

-successes (seized by the mobile).

Telecom Indicators: PS traffic differentiation between GPRS and EDGE (in case
of abnormal release)
New MFS Indicators (4/7):

Indicator
- refname

Long Name

Formula

GQRUEGDTNRN GPRS_UL_EGPRS_TBF_normal_release

Description
Number of DL TBF in EGPRS
P9a
mode normal release .
GPRS_DL_EGPRS_TBF_no Rate of EGPRS DL TBF normal
rmal_release /
release.
GPRS_DL_EGPRS_TBF_su Reference: number of EGPRS DL
ccess
TBF establishment - successes
Number of UL TBF in EGPRS
P22a
mode normal release.

GQRUEGDTNRR GPRS_UL_EGPRS_TBF_normal_release_rate

GPRS_UL_EGPRS_TBF_no Rate of EGPRS UL TBF normal


rmal_release /
releases.
GPRS_UL_EGPRS_TBF_su Reference: number of EGPRS UL
ccess
TBF establishment - successes

GQRDEGDTNRN GPRS_DL_EGPRS_TBF_normal_release

GQRDEGDTNRR

GPRS_DL_EGPRS_TBF_normal_release_rate

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Indicators: PS traffic differentiation between GPRS and EDGE (in case
of abnormal release)
New MFS Indicators (5/7):
Indicator
- refname

Long Name

Formula

GPRS_DL_GPRS_TBF_MS_trans
P90b - P90h
GQRDGPTMTSN fer_success

Description

GPRS_DL_GPRS_TBF_MS_T319
P90e - P90i
GQRDGPTMTMSN 2_success

Number of DL TBF successfully established in GPRS


mode when MS is in uplink packet transfer mode.
Number of DL TBF establishment requests when MS is
in uplink packet transfer mode. Note: This counter
applies to GPRS MS.
Number of DL TBF successfully established in GPRS
mode on PACCH while the timer T3192 is running at
BSS side.

GPRS_DL_GPRS_TBF_MS_T319
P91e - P91i
GQRDGPTMTMRN 2_request

Number of DL TBF establishment requests received


while the timer T3192 is running at BSS side.

GPRS_DL_GPRS_TBF_MS_trans
P91b - P91h
GQRDGPTMTRN fer_request

Number of UL TBF successfully established in GPRS


GPRS_UL_GPRS_TBF_MS_trans
GQRUGPTMTSN fer_success

mode when the MS is in downlink packet transfer

P30b P30e

mode.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Indicators: PS traffic differentiation between GPRS and EDGE (in case
of abnormal release)
New MFS Indicators (6/7):
Indicator
- refname
GQRDGPTRN

Long Name
GPRS_DL_GPRS_TBF_request

Formula
GPRS_DL_TBF_request
GPRS_DL_EGPRS_TBF_request

Description
Number of GPRS DL TBF establishment
requests.
Number

GQRDGPTSN

GPRS_DL_GPRS_TBF_success

GQRDTESUR

GPRS_DL_TBF_success_rate

GPRS_DL_TBF_success
GPRS_DL_EGPRS_TBF_success
GPRS_DL_GPRS_TBF_success /
GPRS_DL_GPRS_TBF_request

of

GGPRS

establishment successes

DL

TBF

(seized by

the mobile).
Rate of GPRS DL TBF establishment
-successes (seized by the mobile).

GPRS_DL_GPRS_TBF_normal_rel
GQRDGPTNRN ease
P9 P9a

Number of DL TBF in GPRS mode


normal release.
Rate of GPRS DL TBF normal releases.
GPRS_DL_GPRS_TBF_normal_rel GPRS_DL_GPRS_TBF_normal_rel/ Reference: number of GPRS DL TBF
GQRDGPTNRR ease_rate
GPRS_DL_GPRS_TBF_success
establishment successes
GQRUGPTRN

GPRS_UL_GPRS_TBF_request

of
GPRS
(P62a+P62b+P62c-P438c+P507) Number
(P62d+P62e+P507a)
establishment requests.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

UL

TBF

Telecom Indicators: PS traffic differentiation between GPRS and EDGE (in case
of abnormal release)
New MFS Indicators (7/7):

Indicator
- refname

Long Name

Formula

Description
Number

GQRUGPTSN

GPRS_UL_GPRS_TBF_success

of

GGPRS

UL

TBF

GPRS_UL_TBF_success
GPRS_UL_EGPRS_TBF_success

successes
establishment
(seized by the mobile).

GPRS_UL_GPRS_TBF_success
GPRS_UL_GPRS_TBF_request

Rate
of
GPRS
UL
TBF
/ establishment
-successes
(seized by the mobile).

GQRUGPTSR

GPRS_UL_GPRS_TBF_success_rate

GQRUGPTNRN

GPRS_UL_GPRS_TBF_normal_releas
e
P22-P22a

GQRUGPTNRR

GPRS_UL_GPRS_TBF_normal_releas GPRS_UL_GPRS_TBF_normal_rel
e_rate
/ GPRS_UL_GPRS_TBF_success

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Number of UL TBF in GPRS


mode normal release.
Rate of GPRS UL TBF normal
releases.
Reference: number of GPRS DL
TBF establishment successes

NPO reports
The Alc_Mono_GPRS_EDGE_differentiation report was created:
NPO report name

Views in the report

Description of the views

Alc_GPRS_EDGE_DL_T
BF_estab_success

This view provides information related to GPRS +


EDGE DL TBF establishment Requested and
Success.

Alc_EDGE_DL_TBF_est This view provides information related to EDGE DL


ab_success
TBF establishment Requested and Success.
Alc_GPRS_DL_TBF_est This view provides information related to GPRS DL
ab_success
TBF establishment Requested and Success.
This view provides information related to GPRS +
Alc_GPRS_EDGE_UL_T
Alc_Mono_GPRS_EDGE
EDGE UL TBF establishment Requested and
BF_estab_success
_differentiation
Success.
Alc_EDGE_UL_TBF_est This view provides information related to EDGE
ab_success
UL TBF establishment Requested and Success.
Alc_GPRS_UL_TBF_est This view provides information related to GPRS UL
ab_success
TBF establishment Requested and Success.
Alc_GPRS_EDGE_DL_T This view provides information related to GPRS
BF_normal_release
and EDGE DL TBF normal release.
Alc_GPRS_EDGE_UL_T This view provides information related to GPRS
BF_normal_release
and EDGE UL TBF normal release.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Test Strategy

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Test Strategy: PS traffic differentiation between GPRS and EDGE (in case of
abnormal release)
Requirements
type of tests: statistical tests
type of analysis: QoS
objective of each test type

It is intended to correlate the new and existing counters in order to be validate


correctly the new counters.

required tools: NPO and K15


required means: 1 RNE + 1 TSC Engineer for trace collection
estimated duration of the tests (post-processing included): 2 weeks (Reference &
observation periods)

* Possibility of feature validation in FOA platform.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Impacts on the internal tools

Tool

Follow-up status

NPO/NPO4U

closed

AnaQoS

On-going

AMT (Traffic
tool)

On-going

Tool version with feature data


configuration

Comments
Specific counters/indicators/reports already created
Counters will be updated in the information
feature slides. No specific extra work from
group
Counters will be updated in the information
feature slides. No specific extra work from
group

All Rights Reserved Alcatel-Lucent 2009, XXXXX

NPO31D17

of the
expert

Version 3.5.1.

of the
expert

End of July

R&D system test results

All Rights Reserved Alcatel-Lucent 2009, XXXXX

System validation tests of the feature

Main fault reports or change requests opened during the test campaigns up to now:

Test Package

FR number

FRs Description
NewMFScountersonGPRS/EDGEdifferentiationforDTMlinked
PS End to End - 3BKA20CBR242072 toFR3BKA20FBR241210.
GPRS

All Rights Reserved Alcatel-Lucent 2009, XXXXX

CMCC FO results B11 MR1 ed1.0

All Rights Reserved Alcatel-Lucent 2009, XXXXX

PS traffic differentiation between GPRS and EDGE (in case of abnormal release)
CMCC FO results

Counter
refname
P90h
P90i

P91h
P91i

Long Name

Definition

NB_DL_TBF_EST_SUCC_EGPRS_MS_TRANSF Number of DL TBF successfully established in EGPRS mode


ER_UL
when MS is in uplink packet transfer mode.
Number of DL TBF successfully established in EGPRS mode
NB_DL_TBF_EST_SUCC_EGPRS_T3192
on PACCH while the timer T3192 is running at BSS side.
Note: This counter applies to GPRS and EGPRS MS.
Number of DL TBF establishment requests when MS is in
NB_DL_TBF_EST_REQ_EGPRS_MS_TRANSFE
uplink packet transfer mode.
R_UL
Note: This counter applies to EGPRS MS.
Number of DL TBF establishment requests received while
NB_DL_TBF_EST_REQ_EGPRS_T3192
the timer T3192 is running at BSS side.
Note: This counter applies to EGPRS MS.

Measured
object
CELL
CELL

CELL
CELL

P62e

NB_UL_TBF_EST_REQ_EGPRS_MSTRANSDL

Number of UL TBF establishment requests when the EGPRS


MS is in downlink packet transfer mode.

CELL

P30e

NB_UL_TBF_EST_SUCC_EGPRS_MSTRANSDL

Number of UL TBF successfully established in EGPRS mode


when the MS is in downlink packet transfer mode.

CELL

P9a

NB_DL_TBF_NORM_REL_EGPRS

Number of DL TBF in EGPRS mode normal release.

CELL

P22a

NB_UL_TBF_NORM_REL_EGPRS

Number of UL TBF in EGPRS mode normal release.

CELL

All Rights Reserved Alcatel-Lucent 2009, XXXXX

PS traffic differentiation between GPRS and EDGE (in case of abnormal release)
CMCC FO results

2. Check indicators availability in NPO (1/2)


indicator refname

LongName
GPRS_DL_EGPRS_TBF_MS_tra
GTRDEGTSV5N nsfer_success
GPRS_DL_EGPRS_TBF_MS_tra
GTRDEGTRV5N nsfer_request
GPRS_DL_EGPRS_TBF_MS_T31
GTRDEGTSV4N 92_success

Formula
P90h
P91h
P90i

GPRS_DL_EGPRS_TBF_MS_T31
GTRDEGTRV4N 92_request
P91i
GPRS_UL_EGPRS_TBF_MS_tra
GTRUEGTRV5N nsfer_request

P62e

GPRS_UL_EGPRS_TBF_MS_tra

Description
Number of DL TBF successfully established in EGPRS mode when
MS is in uplink packet transfer mode.
Number of DL TBF establishment requests when MS is in uplink
packet transfer mode. Note: This counter applies to EGPRS MS.
Number of DL TBF successfully established in EGPRS mode on
PACCH while the timer T3192 is running at BSS side.
Number of DL TBF establishment requests received while the
timer
T3192
is
running
at
BSS
side.
Note: This counter applies to EGPRS MS.
Number of UL TBF establishment requests when the EGPRS MS is
in
downlink
packet
transfer
mode.
Note: This counter applies to EGPRS MS.
Number of UL TBF successfully established in EGPRS mode when

GTRUEGTSV5N nsfer_success
P30e
GPRS_DL_EGPRS_TBF_normal
GQRDEGDTNRN _release
P9a
GPRS_UL_EGPRS_TBF_normal
GQRUEGDTNRN_release
P22a

the MS is in downlink packet transfer mode.


Number of DL TBF in EGPRS mode normal release .
Number of UL TBF in EGPRS mode normal release.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

PS traffic differentiation between GPRS and EDGE (in case of abnormal release)
CMCC FO results

2. Check indicators availability in NPO (2/2) - OK

Group

Hourly

Daily

Weekly Monthly

Cell
BSS

OK
OK

OK
OK

OK
OK

OK
OK

Network

OK

OK

OK

OK

BTS

OK

OK

OK

OK

GPU

OK

OK

OK

OK

All Rights Reserved Alcatel-Lucent 2009, XXXXX

PS traffic differentiation between GPRS and EDGE (in case of abnormal release)
CMCC FO results
1. Correlate the new and existing indicators (1/7)
DL
TBF normal release
TBF establishment
requests
Request Transfer mode
Request While T3192
running
TBF establishment
successes
Success Transfer mode
Success While T3192
running
TBF establishment
requests vs TBF
establishment successes
Transfer mode
While T3192 running

GPRS + EGPRS mode


P9 > P9a
GPRS + EGPRS mode

UL

GPRS + EGPRS mode

P91b > P91h

TBF normal release


TBF establishment
requests
Idle mode + no MPDCH

P22 > P22a

P91e > P91i


GPRS + EGPRS mode
P90b > P90h
P90e > P90i
EGPRS

GPRS + EGPRS mode


P62b-P438c > P62e

TBF establishment success GPRS + EGPRS mode


Transfer mode
P30b > P30e
TBF establishment
requests vs TBF
EGPRS
establishment successes
Transfer mode
P62e >= P30e

P91h >= P90h


P91i >= P90i

All Rights Reserved Alcatel-Lucent 2009, XXXXX

PS traffic differentiation between GPRS and EDGE (in case of abnormal release)
CMCC FO results
1. Correlate the new and existing indicators (2/7)

OK
DL
TBF normal release

GPRS + EGPRS mode


P9 > P9a

All Rights Reserved Alcatel-Lucent 2009, XXXXX

PS traffic differentiation between GPRS and EDGE (in case of abnormal release)
CMCC FO results
1. Correlate the new and existing indicators (3/7)
TBF establishment requests

GPRS + EGPRS mode

Request Transfer mode

P91b > P91h

Request While T3192 running

P91e > P91i

All Rights Reserved Alcatel-Lucent 2009, XXXXX

OK

PS traffic differentiation between GPRS and EDGE (in case of abnormal release)
CMCC FO results
1. Correlate the new and existing indicators (4/7)
TBF establishment successes

GPRS + EGPRS mode

Success Transfer mode

P90b > P90h

Success While T3192 running

P90e > P90i

All Rights Reserved Alcatel-Lucent 2009, XXXXX

OK

PS traffic differentiation between GPRS and EDGE (in case of abnormal release)
CMCC FO results
1. Correlate the new and existing indicators (5/7)

OK
UL
TBF normal release

GPRS + EGPRS mode


P22 > P22a

All Rights Reserved Alcatel-Lucent 2009, XXXXX

PS traffic differentiation between GPRS and EDGE (in case of abnormal release)
CMCC FO results
1. Correlate the new and existing indicators (6/7)
TBF establishment requests

GPRS + EGPRS mode

Idle mode + no MPDCH

P62b-P438c > P62e

TBF establishment success

GPRS + EGPRS mode

Transfer mode

P30b > P30e

All Rights Reserved Alcatel-Lucent 2009, XXXXX

OK

PS traffic differentiation between GPRS and EDGE (in case of abnormal release)
CMCC FO results
1. Correlate the new and existing indicators (7/7)
DL
TBF estab requests vs
EGPRS
TBF estab successes
Transfer mode
P91h >= P90h (P91h - P90h >= 0)
While T3192 running

P91i >= P90i (P91i - P90i >= 0)


UL

TBF estab requests vs


EGPRS
TBF estab successes
Transfer mode
P62e >= P30e (P62e P30e >= 0)

Open FR: 3BKA20FAG290838 CMCC B11MR1Ed1.1


pilot: Number counted by TBF establish success
for EGPRS only (P30e,p90h,p90i) is higher than
the request number (P62e,P91h,p91i).
The current hypothesis by R&D is bad decoding
(or a bad format) of some mobile radio access
capabilities, the problem was reproduced in
platform.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

NOK

TMO FO results B11 MR1 ed1.1

All Rights Reserved Alcatel-Lucent 2009, XXXXX

PS traffic differentiation between GPRS and EDGE (in case of abnormal release)
TMO FO results

1. Check Counters availability in NPO - OK

2. Check indicators availability in NPO - OK

3. Correlate the new and existing indicators - OK


Except TBF establishment requests vs TBF establishment successes

All Rights Reserved Alcatel-Lucent 2009, XXXXX

PS traffic differentiation between GPRS and EDGE (in case of abnormal release)
TMO FO results
1. Correlate the new and existing indicators (7/6)
DL
TBF estab requests vs
EGPRS
TBF estab successes
Transfer mode
P91h >= P90h (P91h - P90h >= 0)
While T3192 running

P91i >= P90i (P91i - P90i >= 0)


UL

TBF estab requests vs


EGPRS
TBF estab successes
Transfer mode
P62e >= P30e (P62e P30e >= 0)

NOK

Open FR: 3BKA20FAG290838 CMCC


B11MR1Ed1.1 pilot: Number counted by
TBF establish success for EGPRS
only(P30e,p90h,p90i)is higher than the
request number(P62e,P91h,p91i).
The current hypothesis by R&D is bad
decoding (or a bad format) of some
mobile radio access capabilities, the
problem was reproduced in platform

Not possible to verify the


condition P91i >= P90i due
to missing data. Counters
equal to 0.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Agenda
Parameters Improvement (Ater Usage Optimization)
Telecom parameters
Test strategy
R&D system tests results
TMO FO results B11 MR1 ed1.1

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Telecom Parameters

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Parameters Improvement (Ater Usage Optimization)


Telecom Parameters
The parameters improvement in B11 are from the B10 feature Ater Usage
Optimization.
In B10 the parameters were implemented at DLS,
although the feature brings to the network a significant improvement in
the Ater usage, to allow an easy way for the feature implementation
several parameters were made changeable at OMC-R

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Parameters Improvement (Ater Usage Optimization)


Telecom Parameters
Parameters changed from DLS to Changeable (1/2).

Parameter Name

Ater_Usage_Threshold_Short_Data

INIT_PDCH_SHORT_DATA_EGPRS

INIT_PDCH_SHORT_DATA_GPRS

Definition

SubSyste
m

Threshold (percentage of used Ater


nibbles, in a GPU) above which the Ater
MFS
usage isoptimized for short data MS
transfers
Number
of
PDCHs
on
which
MAX_EGPRS_MCS_SHORT_DATA_DL
and
MAX_EGPRS_MCS_SHORT_DATA_UL
are
MFS
targeted when establishing GCHs for an
EGPRS TBF associated to a short data MS
transfer.
Number
of
PDCHs
on
which
MAX_EGPRS_CS_SHORT_DATA_DL
and
MAX_EGPRS_CS_SHORT_DATA_UL
are
MFS
targeted when establishing GCHs for an
GPRS TBF associated to a short data MS
transfer.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Instance

Category/
OMC-R
access
Site (CAE)/

BSS
Changeable

Site (CAE)/
Cell
Changeable

Site (CAE)/
Cell
Changeable

Range/
Type /
Default
Unit
value
Number
/%

[0, 100] /
100

Number
/ None

[1, 8] / 3

Number
/ None

[1, 8] / 2

Parameters Improvement (Ater Usage Optimization)


Telecom Parameters
Parameters changed from DLS to Changeable (2/2) .
SubSyste
m

Instance

Category/
OMC-R
access

Range/
Type /
Default
Unit
value

Parameter Name

Definition

MAX_EGPRS_MCS_SHORT_DATA_DL

Maximum Modulation and Coding Scheme


used for the DL EGPRS TBFs associated to a MFS
short data MS transfer.

Cell

Site (CAE)/
Changeable

Number
/ None

[1, 9] / 1

MAX_EGPRS_MCS_SHORT_DATA_UL

Maximum Modulation and Coding Scheme


used for the UL EGPRS TBFs associated to MFS
a short data MS transfer.

Cell

Site (CAE)/
Changeable

Number
/ None

[1, 9] / 2

MAX_EGPRS_CS_SHORT_DATA_DL

Maximum Modulation and Coding Scheme


used for the DL GPRS TBFs associated to a MFS
short data MS transfer.

Cell

Site (CAE)/
Changeable

Number
/ None

[1, 4] / 1

MAX_EGPRS_CS_SHORT_DATA_UL

Maximum Modulation and Coding Scheme


used for the UL GPRS TBFs associated to a MFS
short data MS transfer.

Cell

Site (CAE)/
Changeable

Number
/ None

[1, 4] / 2

N_DATA_BYTES_MAX_TRANS

Number of bytes below which an MS


MFS
transfer is considered to be short data.

Cell

Site (CAE)/
Changeable

Number
/ byte

[20,
10000]
150

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Test Strategy

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Parameters Improvement (Ater Usage Optimization)


Test Strategy
Requirements

type of tests: Statistical tests and parameters specification

type of analysis: QoS + parameter specification check

objective of each test type

QoS
Verify if no impact exist in the Ater usage with B11 introduction

Parameter specification check


Verify if the parameters are according to the new changes

required tools: NPO, Smart_MCT and OMC

required means: 1 RNE

estimated duration of the tests (post-processing included): 2 weeks (Reference &


observation periods)

* Possibility of partial feature validation in FOA platform.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Impacts on the internal tools

Tool

Follow-up status

Comments

NPO/NPO4U

closed

Specific Parameters already created

Smart_MCT
(Traffic tool)

closed

Parameters will be updated in the information of the


feature slides. No specific extra work from expert
group

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Tool version with feature data


configuration
NPO31D17
9.0.2

R&D system test results

All Rights Reserved Alcatel-Lucent 2009, XXXXX

System validation tests of the feature

Not available

All Rights Reserved Alcatel-Lucent 2009, XXXXX

TMO FO results B11 MR1 ed1.1

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Parameters Improvement (Ater Usage Optimization)


TMO FO results
1. Check Parameters availability in OMC - OK

2. Check Parameters availability in NPO - OK

3. Check migration rule OK


B11 default value

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Reference documentation

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Reference documentation
NE Proposal of evolutions
Edition 1 Proposal 3

of

PM

counters

in

release

B11

SYT Memo Improvement of PS counters for GSL and for data/signalling


differentiation
and
for
GPRS/EDGE
differentiation
Edition 8 (Wireless/GSM/R&D/SYT/207082_8)
NE B10 document: BSS Architecture Service Guideline Edition 2 (3DF 0190
329 8010 VAZZA 02)
B11 MFS-BSC interface BSCGP layer Edition 2 Rl (3BK 11202 0507 DSZZA)
CR246115 changed from CDE/none/MFS + migration + external + reco +
internal
CR266950: recommended added - cell level (B10 alignt - MFS level)

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Annex

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Annex A: LAPD in TDM mode versus TCP on IP mode

Back
All Rights Reserved Alcatel-Lucent 2009, XXXXX

Annex B: MFS counters/ indicators at LAPD level (1/2)


Counters related to transport bandwidth usage and transport availability for LAPD links of
a GSL link (BSC_MFS_LAPD).
Counter
refname

LongName

Definition

Measured
object

Domain

Type

Resource
availability
and usage

MFS

P32

TIME_LAPD_NOT_AVAIL

Time during which the LapD is not


BSC_MFS_LAPD
available.

P2a

NB_LAPD_INFO_FRAME_RESENT

Number of Info frames retransmitted


BSC_MFS_LAPD
on the logical LapD link.

Quality of

Number of Receive Not Ready (RNR)


BSC_MFS_LAPD
frames sent on the LapD logical link.

Quality of

P2b

P2c

P2d
P41
P42

NB_LAPD_RNR_SENT

NB_LAPD_RNR_REC

NB_LAPD_EST

Number of Receive Not Ready (RNR)


frames received on the LapD logical BSC_MFS_LAPD
link.
Number of data link establishment,
re-establishment and reset on the BSC_MFS_LAPD
LapD logical link.

service

service
Quality of
service
Quality of
service

Number of kilo bytes sent to the BSC


BSC_MFS_LAPD Traffic Load
on the LapD link.
NB_KBYTES_RECEIVED_FROM_BS Number of kilo bytes received from
BSC_MFS_LAPD Traffic Load
C
the BSC on the LapD link.
NB_KBYTES_SENT_TO_BSC

All Rights Reserved Alcatel-Lucent 2009, XXXXX

MFS

MFS

MFS

MFS
MFS
MFS

Annex B: MFS counters/ indicators at LAPD level (2/2)


Indicators related to transport bandwidth usage and transport availability for LAPD links of a GSL
link.
Indicator refname
GAALAPAVT

Long Name
GPRS_GSL_LAPD_unavailable_time

Definition
Time per LapD during which the
LapD GSL is not available on the P32
AterMux interface.

Formula

Percentage of time per LapD during GPRS_GSL_LAPD_unavaila


GPRS_GSL_LAPD_unavailable_percent which the LapD GSL is not available ble_time /
on the AterMux interface.
GPRS_obs_period_LAPD_M
FS
GPRS_LAPD_retransmitted_info_frame Number of Info frames retransmitted
GQALAPFRREN
P2a
s
on the logical LapD link.
GAALAPAVP

GQALAPDFNRN GPRS_LAPD_RNR_frames_sent
GQALAPUFNRN GPRS_LAPD_RNR_frames_received
GQALAPFRESN
GTALAPDLN
GTALAPULN

GPRS_LAPD_establishments_resets
NB_KBYTES_SENT_TO_BSC
NB_KBYTES_RECEIVED_FROM_BSC

Number of Receive Not Ready (RNR)


frames sent on the LapD logical link.
Number of Receive Not Ready (RNR)
frames received on the LapD logical
link.
Number of data link establishment,
re-establishment and reset on the
LapD logical link.
Number of kilo bytes sent to the BSC
on the LapD link.
Number of kilo bytes received from
the BSC on the LapD link.

P2b
P2c
P2d
P41
P42

Back
All Rights Reserved Alcatel-Lucent 2009, XXXXX

Annex C: BSC counters/ indicators at LAPD level for RSL (1/2)


Counters related to transport bandwidth usage and transport availability for LAPD links
associated to a RSL link (BTS_BSC_LAPD)
Counter
refname

Long Name

Definition

Measured
object

Domain

Type

L1.1

Number
of
Information
frames
NB_LAPD_INFO_FRAME_S
transmitted on the LapD link, excluding BTS_BSC_LAPD
ENT
the re-transmissions.

Traffic Load

07

L1.2

Number of Information frames received


NB_LAPD_INFO_FRAME_R
on the LapD link, excluding the re- BTS_BSC_LAPD
EC
transmissions.

Traffic Load

07

L1.5

NB_LAPD_RNR_SENT

Quality of Service

07

Quality of Service

07

Quality of Service

07

L1.6
L1.15
L1.16

Number of Receive Not Ready (RNR)


BTS_BSC_LAPD
frames transmitted on the LapD link.
Number of Receive Not Ready (RNR)
NB_LAPD_RNR_REC
BTS_BSC_LAPD
frames received on the LapD link.
NB_LAPD_INFO_FRAME_R Number of Information frames reBTS_BSC_LAPD
ESENT
transmitted on the LapD link
TIME_LAPD_UNAVAIL

L1.17

NB_LAPD_EST

L1.18

TIME_LAPD_CONG

Time (in seconds) during which the LapD


BTS_BSC_LAPD
link is unavailable for any cause.
Number of data link establishment, reestablishment and reset on the LapD BTS_BSC_LAPD
link.
Time in seconds during which the LapD
link is congested in transmission in the BTS_BSC_LAPD
BSC.

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Resource
Availability & Usage

07

Quality of Service

07

Quality of Service

07

Annex C: BSC counters/ indicators at LAPD level for RSL (2/2)


Indicators related to transport bandwidth usage and transport availability for LAPD links of
a RSL link (BTS_BSC_LAPD)
Indicator
refname
GQALAPDLIFRN
GQALAPULIFRN

Long Name

Definition

Formula

Number of Information frames transmitted on the


LapD link, excluding the re-transmissions.

L1.1

GPRS_LAPD_info_frame_recei Number of Information frames received on the LapD


ved
link, excluding the re-transmissions.

L1.2

GPRS_LAPD_info_frame_sent

GQALAPDRNRN GPRS_LAPD_RNR_frame_sent
GPRS_LAPD_RNR_frame_recei
ved
GPRS_LAPD_Info_frame_retra
GQALAPIFRREN
nsmited
GQALAPURNRN

GQALAPURNRN GPRS_LAPD_unavailable_time
GAALAPDESTN GPRS_LAPD_data_link_estab
GAALAPCTT

GPRS_LAPD_Time_LAPD_Cong

GAALAPEFR

GPRS_LAPD_Efficiency

Number of LAPD Receive Not Ready (RNR) status


frames sent.
Number of LAPD Receive Not Ready (RNR) status
frames received.
Number of Information frames re-transmitted on the
LapD link
Time (in seconds) during which the LapD link is
unavailable for any cause.
Number of data link establishment, re-establishment
and reset on the LapD link.
Duration of congestion of LAPD link on Tx side.Time
in seconds during which the LapD link is congested in
transmission in the BSC.
This indicator gives the LAPD efficiency.

L1.5
L1.6
L1.15
L1.16
L1.17
L1.18
L1.1/(L1.1 + L1.15)

Back
All Rights Reserved Alcatel-Lucent 2009, XXXXX

Annex D: GSL Dimensioning


Purpose: To estimate the number of AterMUX-PS links needed per GP(U), according to the
signalling traffic.
The GSL dimensioning process is composed of two dimensioning methods that allow to assess
the GSL load in terms of:
Channel bandwidth,
Number of messages per second sent by the MFS to the BSC (the opposite direction, BSC to
MFS, being considered as less critical in terms of GSL load).

Counters related TBF


estab. and PS/CS
paging requests in GPU

Counters P41
and P42

For more details see BSS Architecture Service Guideline document.


All Rights Reserved Alcatel-Lucent 2009, XXXXX

Back

Annex E: TBF establishment and Release Rates (GPRS + EGPRS)

Indicator
refname
GQRDTESUR

Long Name

Description

Rate of DL TBF establishment GPRS_DL_TBF_success /


-successes (seized by the mobile). GPRS_DL_TBF_request

GPRS_DL_TBF_success_rate

GTRDTERQN

GPRS_DL_TBF_request

GTRDTESUN

GPRS_DL_TBF_success

Formula

Number of DL TBF establishment P91a + P91b + P91c + P91d +


requests.
P91e + P91f + P505
Number of DL TBF establishment P90a + P90b + P90c + P90d +
successes (seized by the mobile). P90e + P90f + P506

GPRS_DL_TBF_normal_release_rat

GPRS_DL_TBF_normal_release /
GPRS_DL_TBF_success

GQRDDTNRR

Rate of DL TBF normal release.

GQRDDTNRN

GPRS_DL_TBF_normal_release

Number of DL TBF normal release. P9

All Rights Reserved Alcatel-Lucent 2009, XXXXX

Annex E: TBF establishment and Release Rates (GPRS + EGPRS)

Indicator
refname
GQRUTESUR

Long Name

GPRS_UL_TBF_success_rate

GTRUTERQN

GPRS_UL_TBF_request

GTRUTESUN

GPRS_UL_TBF_success

Formula
GPRS_UL_TBF_success /
GPRS_UL_TBF_request

Rate of UL TBF estab success.

Number
of
UL
TBF
establishment requests per
P62a + P62b + P62c - P438c + P507 cell.
Number
of
UL
TBF
establishment successes (seized
P30a + P30b + P30c + P508
by the mobile).

GPRS_UL_TBF_normal_release /
GQRUDTNRR GPRS_UL_TBF_normal_release_rate GPRS_UL_TBF_success
GQRUDTNRN GPRS_UL_TBF_normal_release

Description

P22

Rate of UL TBF normal releases.


Number of
releases.

UL TBF

normal

Back
All Rights Reserved Alcatel-Lucent 2009, XXXXX

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

All Rights Reserved Alcatel-Lucent 2009, XXXXX