B9B10-Nonregression CS Ed03

ED 3 RELEASED
WBG B9B10-nonregression_CS_ed03.doc 2009-07-09 3DF 01906 8011 WAZZA 1/41

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

Domain :
NETWORK OPTIMIZATION
Product :
GSM B10
Division :
METHODS
Rubric :
MIGRATION
Type :
GUIDELINE
Distrib. codes
Internal: External:

PREDISTRIBUTION

NE F. Colin
NE France M. Palumbo NE Egypt M. Sayed
NE Romania I. Inta NE Portugal P. Henriques

ABSTRACT
The aim of this document is to explain how to set the B10 GSM parameters in order to obtain the
same behavior than in B9 release.

KEYWORDS
B10, non-regression, QoS, 2G, 3G, AMR, BSC, counters, parameters, mCCCH, MX capacity
improvement, STM1

Approvals
NE F.COLIN NE France M.PALUMBO
Date:

Signature:

Date: Signature:

Site
VELIZY
Carrier Business Group
MOBILE ACCESS / PSS TI / NETWORK ENGINEERING
Originator
TIS / Network Engineering
B9-B10 migration : non-regression of the circuit mode
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

HISTORY

Edition Status Date Comments
01 RELEASED 11/02/2008 Creation of the document
02 RELEASED 04/11/2008 Updated paragraphs:
MX BSC CAPACITY IMPROVEMENT
OPTIMZED HR CONNECTIVITY
MCCCH
COUNTERS/PARAMETERS IMPROVEMENTS
New paragraph:
DIFFERENTIATED RADIOLINK TIMEOUT FOR AMR
CALLS

03 RELEASED 09/07/2009 Addition of STM1, new B10MR2ed7 counters/indicators,
QoS variations

REFERENCED DOCUMENTS
Table 1: Referenced Documents
Cross-
Reference
Document Title Document Number
[DocTemp]
1
PCS Document Template 3DF 01900 0000 PTZZA
[Layout] Alcatel-Lucent Forms, Sizes and Layout 1AA 00014 0000 ASZZA
[SFD] Multiple CCCH 3BK 10204 0028 DTZZA
[RFD] Compressed Inter RAT HO info 3BKA55CBR194412
[SFD] MX capacity improvement 3BK 10204 031 DTZZA
[memo] Analysis of Proposals from PCS for B10 release MRD/TD/SYT/205402
[SFD] SFD STM-1 impact for TC 3BK 10204 0067 DTZZA

1
The cross reference may be in format like [1] or in words like [DocTemp]
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

TABLE OF CONTENTS
1 SCOPE........................................................................................... 5
1.1 PURPOSE OF THE DOCUMENT ................................................................................. 5
1.2 AREA OF APPLICATION........................................................................................... 5
2 OVERVIEW...................................................................................... 5
2.1 B10 FEATURES ..................................................................................................... 5
3 MX BSC CAPACITY IMPROVEMENT.......................................................... 6
3.1 1000 TRX AND HSL ............................................................................................... 6
3.1.1 FEATURE DESCRIPTION........................................................................................................ 6
3.1.2 FEATURE ACTIVATION ......................................................................................................... 6
3.1.3 PARAMETERS .................................................................................................................... 7
3.1.4 COUNTERS...................................................................................................................... 7
3.1.5 MIGRATION RULES............................................................................................................. 7
3.1.6 FIELD FEEDBACK ............................................................................................................... 8
3.2 OPTIMIZED HR CONNECTIVITY ................................................................................ 10
3.2.1 FEATURE DESCRIPTION....................................................................................................... 10
3.2.2 FEATURE ACTIVATION ........................................................................................................ 11
3.2.3 PARAMETERS ................................................................................................................... 11
3.2.4 COUNTERS..................................................................................................................... 12
3.2.5 MIGRATION RULES............................................................................................................ 12
4 MULTIPLE CCCH..............................................................................13
4.1 FEATURE DESCRIPTION.......................................................................................... 13
4.2 FEATURE ACTIVATION ........................................................................................... 13
4.3 PARAMETERS ...................................................................................................... 13
4.4 COUNTERS........................................................................................................ 14
4.5 MIGRATION RULES............................................................................................... 18
5 2G INTEROPERABILITY .......................................................................19
5.1 2G TO 3G HANDOVER BASED ON 2G LOAD AND SERVICE CRITERIA................................... 19
5.1.1 FEATURE DESCRITPION....................................................................................................... 19
5.1.3 PARAMETERS ................................................................................................................... 20
5.1.4 COUNTERS..................................................................................................................... 20
5.1.5 MIGRATION RULES............................................................................................................ 23
5.2 SUPPORT OF COMPRESSED INTER-RAT INFO ELEMENT .................................................... 23
5.2.1 FEATURE DESCRITPION....................................................................................................... 23
5.2.3 PARAMETERS ................................................................................................................... 23
5.2.4 COUNTERS..................................................................................................................... 23
5.2.5 MIGRATION RULES............................................................................................................ 23
6 COUNTERS / PARAMETERS IMPROVEMENTS.............................................24
6.1 CALL SETUP SUCCESS RATE METRIC........................................................................... 24
6.1.3 PARAMETERS ................................................................................................................... 24
6.1.4 NEW COUNTERS .............................................................................................................. 24
6.1.5 NEW INDICATOR .............................................................................................................. 25
6.1.6 MIGRATION RULES............................................................................................................ 26
6.2 PARAMETERS IMPROVEMENTS .................................................................................. 26
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

6.2.3 PARAMETERS ................................................................................................................... 26
6.2.4 COUNTERS..................................................................................................................... 26
6.2.5 MIGRATION RULES............................................................................................................ 26
6.3 NEW COUNTERS FOR CALL DROP WITH SPECIFIC RADIO CAUSES ...................................... 27
6.3.3 PARAMETERS ................................................................................................................... 28
6.3.4 COUNTERS..................................................................................................................... 28
6.3.5 MIGRATION RULES............................................................................................................ 29
6.4 NEW COUNTERS FOR SDCCH ASSIGNMENT SUCCESS RATE ............................................. 30
6.4.3 NEW COUNTERS .............................................................................................................. 30
6.4.4 NEW INDICATORS............................................................................................................. 31
6.4.5 RELATED PARAMETERS ........................................................................................................ 31
6.4.6 MIGRATION RULES............................................................................................................ 31
6.5 NEW COUNTERS FOR SDCCH ASSIGNMENT REQUEST FOR LOCATION UPDATE ..................... 31
6.5.3 NEW COUNTER ............................................................................................................... 32
6.5.4 NEW INDICATORS............................................................................................................. 32
6.5.5 RELATED PARAMETERS ........................................................................................................ 33
6.5.6 MIGRATION RULES............................................................................................................ 33
7 DIFFERENTIATED RADIOLINK TIMEOUT FOR AMR CALLS...............................34
7.3 PARAMETERS ...................................................................................................... 35
7.4 COUNTERS........................................................................................................ 35
7.5 MIGRATION RULES............................................................................................... 35
8 STM1 CONNECTIVITY IN TC................................................................37
8.3 PARAMETERS ...................................................................................................... 38
8.4 COUNTERS / INDICATORS...................................................................................... 38
8.5 MIGRATION RULES............................................................................................... 38
9 GENERAL B10 QOS FEEDBACK.............................................................39
9.1 PARAMETERS VARIATIONS....................................................................................... 39
9.1.1 PARAMETERS INSTANCE CHANGES......................................................................................... 39
9.2 QOS VARIATIONS ................................................................................................ 39
9.2.1 BULGARIA ...................................................................................................................... 39
9.2.2 GERMANY ....................................................................................................................... 40

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

1 SCOPE
1.1 PURPOSE OF THE DOCUMENT

The target group is: engineers optimizing GSM radio networks.
1.2 AREA OF APPLICATION

The aim of this document is to explain how to set the B10 GSM parameters in order to obtain the
same behavior than in B9 release.
The services described in this document are applicable for networks where Alcatel is the current
supplier for BSS.
This document is valid for B10 release up to B10MR2ed7.
2 OVERVIEW

This document presents the differences between B9 and B10 releases and explains how to set the B10
GSM parameters in order to have the same behavior as in B9 release after a B9 to B10 migration.
It describes the main new features and algorithms evolutions that can have an impact on the circuit
QoS during a B9 to B10 migration. For features that are activated automatically in B10, a field result
is given when available.
Finally this document contains a last part giving a general feedback on QoS variation.

2.1 B10 FEATURES

Feature Activation
MX Capacity improvement
1000 TRX Optional
HSL Optional
Optimized HR connectivity Optional
Multiple CCCH Optional
2G interoperability
2G-3G HO based on 2G load & service criteria Optional
Support of compressed inter-rat info element Optional
Counters/parameters improvements
Call setup success rate metrics Automatic
Parameters Automatic
Call drop specific cause Automatic
Differentiated RLT for AMR calls Optional
TC-STM1 Optional

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

3 MX BSC CAPACITY IMPROVEMENT

3.1 1000 TRX AND HSL
3.1.1 FEATURE DESCRIPTION

In B9 the MX BSC supports up to 600 TRXs with 3 CCP boards in one ATCA shelf; each CCP board
supports up to 200 TRX. The TP GSM board supports the traffic of these 600 TRXs. A MX BSC
supports a maximum of 264 cells. The committed capacity on the A interface is 2600 Erlangs.

In B10 the capacity of a CCP board is kept unchanged (i.e. it supports up to 200 TRX); the capacity of
the MX BSC is extended to 1000 TRX by adding 2 CCP boards in the ATCA shelf. The TP GSM board
shall support the traffic of 1000 TRXs. The capacity is extended to 500 cells for the MX BSC.
The targeted capacity on the A interface is 4500 Erlangs (4.5 Erlang/TRX) with the Alcatel traffic
model. HSL links shall be supported to reach this capacity.
In case HSL is not used, the capacity of the MX BSC shall be limited to approximately 3000 Erlangs
via the overload mechanisms on the A interface.
It shall be possible to connect a MFS with GPU AB, GPU AC and GP (MX MFS) to a MX BSC
configured with 1000 TRXs.

3.1.2 FEATURE ACTIVATION

In order to take advantage of the feature, it is needed to extend BSC capacity taking into account the
following hardware configurations:
- The MX BSC supports up to 200 TRX with 1 CCP board
- The MX BSC supports up to 400 TRX with 2 CCP boards

The MX BSC boards (TP GSM and 5 CCPs) support a traffic of up to 4500 Erlangs (4500 Erlangs for
the TP GSM board and 900 Erlangs per CCP board).

MX BSC general SS7 configurations:
- The MX BSC supports two modes of operation for SS7: HSL and LSL
- The selection of the mode of operation is exclusive (mixed mode is not allowed)

The use of HSL is optional and may be used if this option is supported by the MSC. It is the choice of
the operator to decide whether the HSL links are used. The HSL can be used on any MX BSC
configuration type (whatever the number of Erlangs supported by the MX BSC). During installation of
the network, the configuration of HSL is done with POLO. When the network is operational, the
switching between the LSL and HSL mode or vice versa is done by an operator command at the BSC
Terminal.

A new parameter in OMC-R - EN_HSL is used to activate/deactivate HSL.

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

3.1.3 PARAMETERS

Name Instance Range/
Default
Definition
EN_HSL BSC [0;1];0 Enables SS7 HSL (High speed
Signalling Link).
MAX_CELLS_GP MFS 500
Maximum number of cells configured
by GP board (Mx-MFS)
MAX_CELLS_GPUAB MFS 240
by GPUAB board (MFS)
MAX_CELLS_GPUAC MFS 264
by GPUAC board (MFS)
MAX_TCH_PER_CCP BSC 1100
Maximum number of active TCHs per
CCP board
MTP_Sequence_Number_Format BSC
0=Normal,
1=Extended
Default 0
Defines the format to be used for the
sequence number of MTP2

3.1.4 COUNTERS

There is one new counter added:

Ref. name Mnemonic Definition Trigger condition
MC926 TCH_BLOCKING_
OCCURENCES_BS
C
Number of TCH channel
allocation rejected for cause:
Maximum TCH processing
capacity of CCP reached.
Whenever a TCH cannot be
allocated due to the TCH
processing capacity of CCP
reaches the limit defined by
the MAX_TCH_PER_CCP
parameter.

Based on this counter one indicator has been defined:

Ref. name Mnemonic Definition Formula
GTCRRCGTS
N
TCH_block_BSC_cong Number of TCH channel allocation
rejected for cause Maximum TCH
capacity of the
BSC reached at BSC level.
MC926

3.1.5 MIGRATION RULES

No migration rules can be defined for this feature as it is automatically activated during migration to
B10.

However, it is important to know the following limitations which may occur in case of MxBSC
extension:
The TP GSM board capacity is of 512 HDLC in TPv1, and is extended to 1024 HDLC in TPv3.
In Mx BSC, for each HDLC logical link, e.g. RSL, OML, GSL and PPP there is a logical HDLC
channel number and a physical HDLC device number associated. HDLC channels for RSL and
OML are assigned dynamically in the range [40..480], so only 441 HDLC channels are
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

available in TPv1. All signalling links that are not multiplexed or that are statically multiplexed
have their own logical HDLC channel. All signalling links that are statistically multiplexed share
the same logical HDLC channel. The max number of DR TRE which may be mapped on TPv1,
if Statistical multiplexing is used, is up to 882 with low signalling load and up to 441 with high
signalling load. With TPv3, the max number of DR TRE which may be mapped, if Statistical
multiplexing is used, is up to 984 with high signalling load. So, the Statistical multiplexing with
MCB64K is strongly recommended.
The CIC numbering scheme defined in ITUT Q.763 is coded on 12-bits field, permitting to
address a maximum of 4096 circuits between MSC and BSC elements. The BSC Evolution
supports CIC-numbers coded on 16 bits from release B10 onwards. It must be connected to
an MSC also supporting coding on 16 bits, such as the A5060 Spatial Atrium Call Server
(NGN solution from Alcatel-Lucent) in order to address more than 4096 CICs.
The HSL usage may become mandatory for more than 600 TRX mapped on MxBSC.
Introduction of HSL (High Speed Signaling Link) is possible with the next conditions:
The HSL links are physically connected on two LIU ports, corresponding to Atermux CS;
The Atermux for HSL are directly cabled to MSC;
These two links will work on load sharing mode, not active/standby mode.
Mixed mode (LSL+HSL) is not allowed;
There is no Qmux configured on the Atermux for HSL
Any Atermux defined in the BSC configuration could be used to support HSL, but the BSC
checks that these two Atermux:
Do not carry Qmux (Atermux 1 and 2, Atermux 7 and 8, )
Are configured for CS traffic only,
Are on two different LIU boards, and each LIU boards must be available in BSC.
HSL is always defined on the first Atrunk of the selected Atermux.
If HSL is actived, N7 can have 2 different frame formats:
Normal frame format (MSU contains 6 bytes as fix part + SIF&SIO as variable part).
Extended frame format (MSU contains 9 bytes as fix part + SIF&SIO as variable part).
The MxBSC is supporting both formats. Extended format may not be used if HSL is not
activated. To be checked which format is supported by MSC.
The Alcatel-Lucent Core Network elements supporting the HSL feature are RCP A8362M +
Umax EP6 or above, and NGN release W4.21.

NE Recommendations:
Estimate the final load in terms of traffic and connectivity before BSC extension
Check if HSL is needed and may be supported by CN
Traffic follow-up during the cutover process
Check the BSC and CCP load after cutover
Check the Mux rule used on Abis and Change it to StatisticMux64 to reduce the HDLC
occupancy

3.1.6 FIELD FEEDBACK

The Feature MxBSC Capacity improvement was tested in B10 China first off. The plan was to reach
more than 800 TRX per BSC. The BTSs were moved from old BSCs to the new MxBSC.

After last cutover, the MxBSC with 5+1 CCP boards has reached the following configuration:
- 157 cells (31.4% of total capacity);
- 156 BTSs (61.18% of total capacity);
- 158 Abis links (89.77% of total capacity);
- 834 TRXs (803 FR TRX + 31 HR TRX), so 865 FReq TRXs (86.5% of total capacity);
- 30 AterMux CS links (28 for CS traffic + 2 for HSL);
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

- 18 AterMux PS links;
- 4 GP boards.

The max traffic values reached during BH, after last cutover, were:
- Max TCH traffic = 1239.56 Erlang
- Max Nb of TCH needed = 1509
- Max SCCP traffic = 1469.69 Erlang
- Max Nb of SS7 TS needed = 18
- Max GCH traffic = 1472.1 Erlang
- Max Nb of GCH needed = 1832
- Max Nb of GP boards needed = 2

QoS Follow-up for CS

QoS Indicator
Before 3rd
cutover
After 3nd
cutover
Delta
% SDCCH Assign Congestion 2.14% 2.34% 0.20%
% SDCCH Assign Fail 4.92% 5.57% 0.65%
% SDCCH Drop 0.72% 0.91% 0.19%
SDCCH Traffic Erl Total 3372 3575 204
RTCH Traffic Erl Total 13852 14112 259
% RTCH Assign Congestion 0.02% 0.01% -0.02%
% RTCH Assign Success 99.51% 99.31% -0.20%
%Call Setup Suc 98.79% 98.41% -0.38%
% RTCH fail Radio 0.46% 0.67% 0.20%
% Call Drop 0.34% 0.38% 0.04%
% RTCH Drop 0.17% 0.19% 0.02%
% HO Inc Intra Fail 2.51% 4.86% 2.35%
% HO Inc Intra Cong 0.30% 0.17% -0.13%
% HO Inc Intra Success 96.99% 94.83% -2.16%
% HO Out Intra ROC 2.34% 4.72% 2.38%
% HO Out Intra Drop 0.16% 0.20% 0.04%
% HO Out Intra Success 97.00% 94.79% -2.21%
% HO Inc Inter Fail 5.51% 11.84% 6.33%
% HO Inc Inter Cong 0.22% 0.30% 0.07%
% HO Inc Inter Success 94.25% 87.85% -6.40%
% HO Out Inter ROC 3.53% 3.56% 0.02%
% HO Out Inter Drop 0.06% 0.07% 0.01%
% HO Out Inter Success (*) 70.88% 57.85% -13.03%
%HO Better Cell 56.92% 55.38% -1.53%
(*) recovered after 5 days to initial value

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

QoS Follow-up for PS

QoS Indicator
Before3rd
cutover
After 3rd
cutover
Delta
%DL TBF Success 95.88% 97.25% 1.37%
%DL TBF Fail Radio 3.70% 2.32% -1.37%
%UL TBF Success 84.27% 86.27% 2.00%
%UL TBF Fail Radio 15.11% 13.12% -1.98%
%GPRS DL Resource Reallocation
Success
58.27% 54.75% -3.51%
%GPRS UL Resource Reallocation
Success
75.84% 73.73% -2.11%
% DL TBF Drop 4.12% 3.36% -0.76%
% DL TBF Acc Release 0.61% 0.59% -0.02%
% DL TBF Norm Release 95.27% 96.05% 0.78%
% UL TBF Drop 2.73% 1.99% -0.74%
% UL TBF Acc Release 0.03% 0.03% 0.00%
% UL TBF Norm Release 97.25% 97.98% 0.74%
DL CSx retr rate 3.88% 3.25% -0.63%
DL MCSx retr ratio 15.98% 16.20% 0.22%
UL CSx retr rate 0.78% 0.82% 0.04%
UL MCSx retr rate 3.54% 3.41% -0.13%

The QoS follow-up, based on unitary and statistical tests, shown non regression for CS and PS
services. No issues related to MxBSC have been discovered.
3.2 OPTIMIZED HR CONNECTIVITY

In B9, the number of TREs that can be mapped to a CCP board of the MX BSC depends on the type
of TRE (FR or DR). 50 VTCUs are allocated per CCP and per VTCU it is possible to map:
- four FR TREs or
- two DR TREs or
- one DR TREs and two FR TREs

With these rules up to 200 FR TREs can be mapped on a CCP with VTCU handling FR TREs while only
up to 100 DR TREs can be mapped to a CCP with VTCU handling DR TREs and with mixed FR/DR
VTCUs configurations the number of TREs that can be mapped on a CCP is in between these two
values.
Therefore the number of TREs a CCP can handle (i.e. the connectivity of the CCP) decreases when the
number of VTCUs mapped with DR TREs increases.

Furthermore when a CCP board is added on a MX BSC or when a BTS is removed from a MX BSC,
the load is not reshuffled between the boards and therefore it may happens that some boards are
highly loaded while some others are not loaded.

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

In B10, the maximum number of TREs mapped to a CCP shall be independent on whether the TREs
are FR or DR. It shall be always possible to map up to four TREs (FR and/or DR) per VTCU, i.e. up to
200 TREs per CCP.

The load on a CCP board shall be kept at the same level as in B9. For that reason the maximum
number of TCH a CCP can handle shall be limited to MAX_TCH_PER_CCP. The PDCHs channels
used for PS traffic are not taken into account in the evaluation of the load. To avoid having
unbalanced load between the CCP boards when a CCP board is added on a MX BSC or when a BTS
is removed from a MX BSC, it is requested to have a remap-bts-on-ccp command at the OMC-R to
spread the load between the CCPs boards.
This feature is optional.

This feature shall be supported by TP GSM V1 and TP GSM V3.

The removal of HR impact on BSC connectivity feature is optional

For mapping the TREs on a TCU, two mapping rules are supported: The B9 rules and a new B10
rule.
For an operator who has bought the feature, it shall be possible to activate/deactivate the feature
from the OMC-R (i.e. it can choose the mapping rule it wants).

The maximum number of TREs mapped to a CCP shall be independent on whether the TREs are FR or
DR. This maximum number shall be 200.

It shall be possible to map up to four TREs on a VTCU independently whether they are FR or DR.

The command remap-bts-on-ccp is not optional and shall be supported at the OMC-R.

It shall be possible to trigger the command remap-bts-on-ccp at any time, e.g. when a BTS is
removed or when a CCP is added. The call can be lost during BTS remapping.

As this feature is optional a new parameter EN_4_DR_TRE_PER_TCU is received from the OMC-R to
enable/disable the feature. This parameter defines if the limitation of TRE (per CCP board) is static or
dynamic:
- For static limitation B9 rule is applied.
- For dynamic limitation new B10 rule is applied.
- Range / default value: False = Static or 0 ; True = Dynamic or 1

This parameter is used only by the O&M part of the MX BSC. It should be possible for the telecom
part of the MX BSC to use the new algorithm to count the active TCH whatever the feature is active or
not.
3.2.3 PARAMETERS

Default
Definition
EN_4_DR_TRE_PER_TCU BSC [0;1]; 0 Defines if the limitation of TRE is static or
dynamic.
For static limitation only
Nb FR TRE + 2 x DR TRE < 200 is allowed.
For dynamic limitation only
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

Nb TRE < 200 is allowed.

3.2.4 COUNTERS
No specific counters or indicators.

For ... Parameter name in B9 Parameter value
in B9
Parameter name in B10 Parameter value
in B10
BSC EN_4_DR_TRE_PER_TCU Default=0
Activated=1

The Optimized HR connectivity feature activation is impacting the CCP board capacity. It is
extended from 100 DR TRX to 200 DR TRX. The feature has no impact on TP GSM capacity.

The limitation factors presented in case of MxBSC Capacity Improvement feature must be followed
also for this feature activation.

NE Recommendations:
Estimate the final load of BSC in terms of connectivity before feature activation
User and Signaling Traffic follow-up before and after feature activation
Check the BSC load after activation

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

4 MULTIPLE CCCH
4.1 FEATURE DESCRIPTION

The multiple CCCH is required to support the increasing signalling load on the common channels,
due to either big CS cells with high peak throughput or to PS traffic.

In circuit mode the mobile station listens to the CCCH and the BCCH channels. A mobile in packet
transfer or idle mode must also listen to the BCCH and CCCH.

The multiple CCCH feature is implemented in both G2BSC and MxBSC. Only TS0 and TS2 on
beacon TRX will be used for multiple CCCH. When there is only one CCCH, it is on TS0 only.

The number of CCCH is given by configuration. No dynamic algorithm is implemented to change the
number of CCCH as a function of the CCCH load.

It is not allowed to active a second CCCH when the CCCH in the cell is combined with SDCCH.
Duplicating system information messages on TS0 and TS2 BCCH blocks is performed by the BTS to
save RSL resources.

Computing of CCCH_Groups to determine on which CCCH TS0 or TS2 to send the AGCH message
is done by BSC, because BTS does not have any knowledge of IMSI.
4.2 FEATURE ACTIVATION

Feature activation may be obtained using the parameter CCCH_CONF which indicates the
organization of the common control channels at cell level:

4.3 PARAMETERS

Default
Definition
CCCH_CONF Cell [0;2];0 Configuration of the CCCH.
0 = "one CCCH not combined"
1 = "one CCCH combined"
2 = "two CCCH not combined"
NB_MAX_MSG_MULTIPLE_
PAGING_CMD
BSC

[1;10];5 Number of paging messages that shall
be included in the Abis message
MULTIPLE PAGING COMMAND before
sending it to the BTS (except if
T_SEND_MULTIPLE_PAGING_CMD
expires before this limit is reached).
T_SEND_MULTIPLE_PAGI
NG_CMD
BSC [50;250];5
0
Maximum time between two sendings of
MULTIPLE PAGING COMMAND
message (i.e. at
T_SEND_MULTIPLE_PAGING_CMD
expiry, the message is sent even if it
does not contain yet
NB_MAX_MSG_MULTIPLE_PAGING_CM
D messages).
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

4.4 COUNTERS

There are several new counters added:

Ref.
name
Mnemonic Definition Trigger condition
MC925
a
NB_AGCH_USEFUL_B
LOCKS_SENT

Number of useful blocks
sent on AGCH channel
(The dummy blocks are
not counted).

This counter is increased each time
an IMMEDIATE ASSIGNMENT or
IMMEDIATE ASSIGNMENT
EXTENDED or IMMEDIATE
ASSIGNMENT REJECT or PACKET
UPLINK ASSIGNMENT or PACKET
DOWNLINK ASSIGNMENT
message is taken from one AGCH
queue and put on AGCH channel.
MC925
b
NB_PCH_USEFUL_BL
OCKS_SENT

Number of useful blocks
sent on PCH channel
(The dummy blocks are
not counted).
a PAGING REQUEST message is
taken from one Paging_Group
FIFO and put on PCH channel.
MC925
c
NB_BUSY_RACH_SLO
TS

Number of busy RACH
slots.
Each 51-multiframes the Layer 1
reports the load on the RACH via
the
RACH_MEASUREMENTS_RESULTS
message, which contains the
following information:
- N_VRACH: number of Access
Bursts successfully decoded
- N_BUSY: number of RACH busy
slots
On reception of this message, the
following counters are updated:
- NB_BUSY_RACH_SLOTS =
NB_BUSY_RACH_SLOTS +
N_BUSY
MC925
d
NB_CHANNEL_RQ_R
ADIO

Number of channel
request messages
received on the radio
interface or number of
access bursts successfully
decoded.
Each 51-multiframes the Layer 1
reports the load on the RACH via
the
RACH_MEASUREMENTS_RESULTS
message, which contains the
following information:
- N_VRACH: number of Access
Bursts successfully decoded
- N_BUSY: number of RACH busy
slots

On reception of this message, the
following counters are updated:
- NB_CHANNEL_RQ_RADIO =
NB_CHANNEL_RQ_RADIO +
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

Ref.
name
N_VRACH
MC925
e

NB_ASSIGN_CMD_RE
CEIVED_ABIS

Number of 48.058
IMMEDIATE ASSIGN
COMMAND messages
received by the BTS on
Abis and had to be sent
for CS and PS traffic to
the MS.
an IMMEDIATE ASSIGNMENT
COMMAND message is received
on Abis interface.
MC925
f

NB_ASSIGN_CMD_DI
SCARDED

Number of 48.058
IMMEDIATE ASSIGN
COMMAND messages
received by the BTS on
Abis and discarded due
to congestion.
an IMMEDIATE ASSIGNMENT
COMMAND messages is discarded
on detection of AGCH FIFO
overload.
MC925
g

NB_PAGING_CMD_R
ECEIVED_ABIS

Number of PAGING
COMMAND received by
the BTS on Abis and had
to be sent for CS and PS
traffic to the MS.
1) Applicable to the legacy BSC
only: this counter is increased by
one each time a PAGING
on Abis interface.
2) Applicable to the BSC Evolution
only:
a) This counter is increased by one
each time a PAGING COMMAND
message is received on Abis
interface.
b) This counter is increased by "n"
each time a MULTIPLE PAGING
on Abis interface ("n" is the number
of PAGING COMMAND contained
in the received MULTIPLE PAGING
COMMAND message).
MC925
h
NB_PAGING_CMD_DI
SCARDED

Number of PAGING
COMMAND received by
the BTS on Abis and
discarded due to
congestion.
1) Applicable to the legacy BSC
only: this counter is increased by
one each time a PAGING
COMMAND is discarded on
detection of Paging_Group FIFO
overload.
2) Applicable to the BSC Evolution
only:
This counter is increased by one
is discarded on detection of Paging
Group FIFO overloaded (Note 1).
Note 1: It does not matter whether
the discarded (and counted)
PAGING COMMAND was received
in an individual PAGING
COMMAND message or if it was
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

Ref.
name
received (as one of several
PAGING COMMANDs) within a
message.
MC930

NB_ABIS_PAGING_ME
SSAGE_RECEIVED

Number of PAGING
COMMAND / MULTIPLE
PAGING COMMAND
message received by the
BTS on Abis.
For legacy BSC, the value of this
counter shall be set to "0".
For BSC EVOLUTION:
a) This counter is increased by one
message is received on Abis
interface.
b) This counter is increased by one
each time a MULTIPLE PAGING
on Abis interface.

Based on this counters several indicators have been defined:

GCCIARQUSN CCCH_AGCH_u
seful_blocks_sen
t
Number of useful blocks sent on AGCH
channel.
MC925a
GCCPGRQUS
N
CCCH_PCH_use
ful_blocks_sent
Number of useful blocks sent on PCH
channel.
MC925b
GCCRARQBU
N
CCCH_RACH_b
usy_slots
Number of busy RACH slots. MC925c
GCCRACRQN CCCH_channel_
request_radio
Number of channel request messages
received on the radio interface or
number of access bursts successfully
decoded.
MC925d
GCCIACMABN CCCH_Immedia
te_Assign_Com
mand_Abis
Number of 48.058 IMMEDIATE ASSIGN
COMMAND messages received by the
BTS on Abis and had to be sent for CS
and PS traffic to the MS.
MC925e
GCCIACMAC
N
CCCH_Immedia
te_Assign_Com
mand_Abis_disc
arded_cong
Number of 48.058 IMMEDIATE ASSIGN
BTS on Abis and discarded due to
congestion.
MC925f
GCCPGRQAB
N
CCCH_Paging_
Command_recei
ved_Abis
Number of 48.058 PAGING
MC925g
GCCPGRQAC
N
CCCH_Paging_
Command_Abis
_discarded_cong
Number of 48.058 PAGING
BTS on Abis and discarded due to
congestion.
MC925h
GCCMPGRQA
BN
CCCH_Paging_
Multiple_Paging
_Command_rec
Number of PAGING COMMAND /
message received by the BTS on Abis.
MC930
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

eived_Abis
GCCPGRQAC
R
CCCH_Paging_
Command_Abis
_discarded_cong
_rate
Rate of discarded "PAGING
COMMAND" messages received by the
BTS on Abis interface over the number
of "48.058 PAGING COMMAND"
messages received by the BTS on Abis
and had to be sent for CS and PS traffic
to the MS.
NZ(MC925h)/
(MC925g)
GCCIACMACR CCCH_Immedia
te_Assign_Com
mand_Abis_disc
arded_cong_rat
e
Rate of discarded "IMMEDIATE ASSIGN
BTS on Abis interface over the number
of "48.058 IMMEDIATE ASSIGN
NZ(MC925f)/
NZ(MC925e)
GCCRARQER CCCH_RACH_ef
ficiency_radio_ra
te
Rate of decoded RACH requests in
relation to the Number of busy RACH
slots.
NZ(MC925d)/
NZ(MC925c)
GCCPGRQO CCCH_PCH_loa
d_radio
Load of the Paging Channel. MC925g/
((1000/235)*(N
1-
BS_AG_BLK_RES
)*GSM_obs_peri
od * N2)
N1=9 for
BCCH noncomb
N1=3 for
BCCH comb
N2=3
GCCPGRQO_
MA
CCCH_PCH_loa
d_radio_max
Max Nb of Paging Commands received
on Abis / PCHcapacity
Max value for
previous
formula
GCCIARQRO CCCH_AGCH_l
oad_radio
Load of the Access Grant Channel for
CS traffic on radio interface.
MC925a/
((1000/235)*BS
_AG_BLK_RES*
GSM_obs_perio
d)
GCCIARQRO_
MA
CCCH_AGCH_l
oad_radio_max
Max Nb of AGCH useful blocks sent /
AGCH Capacity
Max value for
previous
formula
GCCRARQRO CCCH_RACH_lo
ad_radio
Load of the Random Access Channel in
radio interface.
MC925d/
((1000/235)*N1
*GSM_obs_peri
od)
GCCRARQRO_
MA
CCCH_RACH_lo
ad_radio_max
Max Nb of Channel requests on RACH/
RACH capacity
Max value for
previous
formula

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

4.5 MIGRATION RULES

The feature must be activated in all cells inside a LAC in order to take benefit from more resources
available on CCCH.

For ... Parameter name in B9 Parameter
value in B9
Parameter name in B10 Parameter
value in B10
Cell CCCH_CONF 0 and 1 CCCH_CONF 0, 1 and 2
Activated=2

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

5 2G INTEROPERABILITY
5.1 2G TO 3G HANDOVER BASED ON 2G LOAD AND SERVICE CRITERIA
5.1.1 FEATURE DESCRITPION
This feature enables the operator to:
Offload 3G cells; by avoiding handover to 3G when serving 2G cell is not loaded.
Take into account service preference provided in Service HO IE.

The mechanism implemented for this feature is described in table below:
Service HO IE
value
2G_3G_HO_Allowed= allowed
2G_3G_HO_Allowed=
forbidden
Missing/Undefined
value
If
EN_2G_3G_HO_NO_SERVICE_HO
=1 then Try HO to 3G
If
= 0 then Stay in GSM
Stay in GSM
HO to UTRAN Shall
not be performed
Stay in GSM Stay in GSM
HO to UTRAN Should
not be performed
Stay in GSM Stay in GSM
HO to UTRAN Should
be performed
Try HO to 3G Try HO to 3G
Table 2 - 2G3G HO based on Service HO IE message
2G_3G_HO_Allowed value is determined based on the following algorithm:

Traffic Evaluation is a long term sliding window averaging process

Traffic evaluation for outgoing 3G HO:
If the last N_TRAFFIC_LOAD averages AV_TRAFFIC_LOAD (including the new one) verify:
AV_TRAFFIC_LOAD > THR_CELL_LOAD_3G_REQ
Then 2G_3G_HO_Allowed = allowed
Else if
AV_TRAFFIC_LOAD THR_CELL_LOAD_3G_REQ
Then 2G_3G_HO_Allowed = forbidden
1 - LOAD A_TRAFFIC_
0
100 *
i) - (k NB_TS
i) - (k NB_USED_TS
LOAD A_TRAFFIC_
1
_LOAD(k) AV_TRAFFIC
i
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

The feature may be activated or not on a per cell basis, by the O&M parameter:
5.1.3 PARAMETERS
Parameter Description Range Object Conditions/Rules
EN_2G_3G_HO_NO_SERVICE_HO Allows handovers towards 3G cells
for a given MS when I.E. Service
Handover is missing and the load
in the serving cell is high
0:
Disable
1:
Enable
Cell
THR_CELL_LOAD_3G_REJECT Load threshold on the serving cell
below which handovers towards
3G cells are forbidden when I.E.
Service Handover is missing and
= 1
0-100
%
Cell 0 = disable
(default)

5.1.4 COUNTERS
Ref. name Mnemonic Definition
R118,
R218,
R318 to
R818
SCRAMBLING_CODE The scrambling code of a 3G FDD
neighboring cell
R119.
R219,
R319 to
R819
FDD_FREQ The UTRAN Absolute Radio
Frequency Number of a 3G FDD
neighboring cell
R120,
R220,
R320 to
R820
AV_ECNO The average receive Ec/No of a 3G
FDD neighboring cell as seen by
the Mobile
HO1101,
HO2101,
HO3101
to HO8101
SCRAMBLING_CODE The scrambling code of a 3G FDD
neighboring cell
HO1102,
HO2102,
HO3102
to HO8102
FDD_FREQ The UTRAN Absolute Radio
Frequency Number of a 3G FDD
neighboring cell
HO1103,
HO2103,
HO3103
to HO8103
AV_ECNO The average receive Ec/No of a 3G
FDD neighboring cell as seen by
the Mobile
MC924b NB_OUT_2G_3G_HO_REQ Number of outgoing 2G to 3G
handover requests
MC924c NB_OUT_2G_3G_HO_SUC Number of outgoing 2G to 3G
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

Ref. name Mnemonic Definition
C handover successes towards a 3G
neighbor cell
MC924d NB_OUT_2G_3G_HO_ATP
T
Number of outgoing 2G to 3G
handover attempts
MC924e NB_OUT_2G_3G_HO_EXE
C_FAIL_NO_REV
handover execution failures without
reversion to old channel
MC924f NB_OUT_2G_3G_HO_EXE
C_FAIL_REV
handover execution failures with
reversion to old channel
MC924g NB_OUT_2G_3G_HO_PRE
P_FAIL
handover preparation failures
MC924h NB_2G_3G_HO_8 Provision for 2G to 3G HO
MC924i NB_2G_3G_HO_9 Provision for 2G to 3G HO
MC924j NB_2G_3G_HO_10 Provision for 2G to 3G HO
MC924k NB_2G_3G_HO_11 Provision for 2G to 3G HO

Based on the counters defined several indicators are now available in B10 to check the feature
behavior:

HOOMSU
UN
HO_Out_MSC_2G_3G_suc
cess
Number of Outgoing External 2G-
>3G HO successes (TCH).This
includes both inter-PLMN and
intra-PLMN events.
MC924c
HOOMSU
UR
HO_Out_MSC_2G_3G_suc
cess_rate
Rate of Outgoing External 2G-
>3G HO successes (TCH).This
intra-PLMN events.
MC924c /
MC924b
HOOMCD
UN
HO_Out_MSC_2G_3G_dro
p
>3G HO execution failures due to
BSS problems (transmission) and
radio problem (TCH). As the
problem is located on the serving
cell, the call is dropped. This
intra-PLMN events.
MC924d-
MC924c-
MC924e-
MC924f+MC
924e
HOOMCD
UR
p_rate
Rate of Outgoing External 2G-
BSS problems (transmission ) and
intra-PLMN events
(MC924d-
MC924c-
MC924e-
MC924f+MC
924e) /
MC924d
HOOMCD
BUN
p_BSS
BSS problems (transmission)
(TCH). As the problem is located
on the serving cell, the call is
dropped. This includes both inter-
MC924d-
MC924c-
MC924e-
MC924f
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

PLMN and intra-PLMN events.
HOOMCD
RUN
p_radio
intra-PLMN events.
MC924e
HOOMEFU
R
HO_Out_MSC_2G_3G_effi
ciency_rate
Rate of Outgoing 2G->3G
handovers successes over the total
amount of outgoing handovers
requests. This includes both inter-
MC924c /
MC924d
HOOMCG
UN
HO_Out_MSC_2G_3G_pre
p_fail
>3G HO preparation failures
(TCH). This includes both inter-
MC924g

HOOMFLP
UR
p_fail_rate
Outgoing External 2G->3G HO
preparation failure rate (TCH). This
intra-PLMN events.
MC924g /
MC924b
HOOMPFU
R
p_fail_reject_rate
Rate of outgoing TCH HO
preparation failures due to Cause
"HANDOVER REQUIRED REJECT"
over the number of Outgoing
External 2G->3G HO required.
This includes both inter-PLMN and
intra-PLMN events.
MC924g /
MC924b
HOOMRQ
UN
HO_Out_MSC_2G_3G_req
uest
>3G HO requests (TCH).This
intra-PLMN events.
MC924d
HOOMRQT
O
uest_ratio
Ratio of Outgoing external 2G 3G
HO in relation to all external HO.
MC924d /
(MC924d +
MC650)
HOOMRD
UN
uired
>3G HO required (TCH).This
intra-PLMN events.
MC924b
HOOMOC
UN
HO_Out_MSC_2G_3G_RO
C
to radio problem with reversion of
the mobile to the old channel.
(TCH). This includes both inter-
MC924f
HOOMOC
UR
HO_Out_MSC_2G_3G_RO
C_rate
Rate of Return to old Channel in
External 2G 3G HO in relation to
the 2G 3G Ho requests.
MC924f /
MC924d

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

value in
B9
value in
B10
All
cells
---- ---- EN_2G_3G_HO_NO_SERVICE_HO Disabled
5.2 SUPPORT OF COMPRESSED INTER-RAT INFO ELEMENT
5.2.1 FEATURE DESCRITPION
The main objective of this feature is reduction of call setup time for dual mode mobiles.
Enhance End user perception.
Avoid loading SDCCH.
In Rel5, a mandatory change is introduced for reduction of InterRAT Handover INFO message size.
In the Immediate Assignment message, the Compressed_Inter_RAT_HO_INFO_IND indicates to
the MS whether a compressed version of the InterRAT Handover Info message shall be used or
not.

The feature may be activated or not on a per cell basis, by the O&M parameter:
EN_Compressed_InterRAT_HO_Info

5.2.3 PARAMETERS
Parameter Description Range Object Conditions/Rules
EN_Compressed_InterRAT_HO_Info Enables the BSS
to require the
usage by a dual
mode mobile of
the compressed
format of INTER
RAT HO INFO IE
(when supported
by the mobile)
1 -
compressed
format of
INTER RAT
HO INFO IE is
required from
the MS.
0 -
compressed
format of
INTER RAT
HO INFO IE is
not required
from the MS;
BSC Only if
EN_3G_HO = 1
Shall be set to 1
only if all RNCs
neighbor to this
BSS support the
feature.

5.2.4 COUNTERS
See Counters paragraph of 2G to 3G handover based on 2G load and service criteria
value in
B9
value in
B10
All
cells
---- ---- EN_Compressed_InterRAT_HO_Info 0
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

6 COUNTERS / PARAMETERS IMPROVEMENTS
6.1 CALL SETUP SUCCESS RATE METRIC

The goal is to provide a new metric, giving a view of the call setup success rate from the end user
point-of-view. This means that the event call established would be compared to the event call
requested, instead of combining metrics related to the protocol mechanisms like it is done today
(SDCCH drops, TCH allocation and assignation, etc.).

Operators would have a global view of the end-user perceived quality of their GSM network,
whatever the problems encountered. Fastest detection and correction of problems would be possible,
leading to improved quality.

Unlike the current implementation of Call Setup Success Rate indicator in B9 (CSSR = (1 -
SDCCH_drop_rate) * (1 - RTCH_assign_unsuccess_rate)), the new B10 metric includes all failures that
could impact the end-user call setup even those related to core network problems.

Automatic
6.1.3 PARAMETERS
None
6.1.4 NEW COUNTERS

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

C191 (type 19) becomes MC191 (type 110): Number of Mobile Terminating SMS connections on
SDCCH.

6.1.5 NEW INDICATOR

The formula used for the new indicator End_to_End_Call_setup_success_rate =
[RTCH_assign_success + DR_Out_internal_success + DR_Out_external_success] /
[(MT_SDCCH_assign_success - SDCCH_SMS_MT_PP_connection) + SDCCH_success_Call_reestab +
SDCCH_success_LU_follow_on + SDCCH_success_other_MO + SDCCH_success_NA_Emergency)].
This formula excludes SDCCH HO (HO_SDCCH_INHIBIT=1)

From counters perspective, this formula can be written as follows:

Where:

MC718: Number of TCH (HR or FR) normal assignment successes, per TRX. This counter also takes
into account normal assignment successes for TCH establishment in signalling mode (FR usage only),
for DTM
MC142e=C142a+C142c: Number of outgoing normal or forced internal directed retry (towards a
TCH channel in HR or FR usage) successes
MC142f=C142b+C142d: Number of outgoing normal or forced external directed retry (towards a
TCH channel in HR or FR usage) successes
MC01: Number of immediate assignment plus SDCCH normal assignment successes for Mobile
Terminating procedure
MC191: Number of Mobile Terminating SMS connections on SDCCH
MC02e: Number of SDCCHs successfully seized for Call Re-establishment
MC02d: Number of SDCCHs successfully seized for LU with follow-on bit set to 1 (means that the
SDCCH phase will be followed by a TCH assignment for speech call establishment)
MC02f: number of immediate assignment successes for Mobile Originating procedure, in case of L3
Info (within 48.058 ESTABLISH INDICATION) unknown by the BSC but transferred to the MSC
MC02h: Number of SDCCHs successfully seized for Normal or Emergency call

The new indicator is available in the Call_Success view within the NPO report Alc_Mono_call;
here is an extract:

Short
name name Definition
MC191
NB_SMS_PP_CON_MT_SDCC
H
Number of Mobile Terminating
SMS connections on SDCCH.
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

Call success - BSC: Stuttgart124_O ( Stuttgart124_O ) - 05/12/2008 To 05/25/2008 (Working
Zone: Global - Medium)
0
1000
2000
3000
4000
5000
6000
0
5
/
1
2
/
2
0
0
8
0
5
/
1
3
/
2
0
0
8
0
5
/
1
4
/
2
0
0
8
0
5
/
1
5
/
2
0
0
8
0
5
/
1
6
/
2
0
0
8
0
5
/
1
7
/
2
0
0
8
0
5
/
1
8
/
2
0
0
8
0
5
/
1
9
/
2
0
0
8
0
5
/
2
0
/
2
0
0
8
0
5
/
2
1
/
2
0
0
8
0
5
/
2
2
/
2
0
0
8
0
5
/
2
3
/
2
0
0
8
0
5
/
2
4
/
2
0
0
8
0
5
/
2
5
/
2
0
0
8
n
b
95.5%
96.%
96.5%
97.%
97.5%
98.%
98.5%
99.%
99.5%
100.%
%
Assign Unsucc
Call drop
SDCCH drop
% End to End Call setup
% Call success
% Call setup

As the new indicator provides an end-user perception of call setup phase, taking into account the
possible core network problems; it is normal that E2E CSSR values are less than those provided by
classical CSSR. Indeed, the strong benefit of this new feature comes from the fact that all failures are
considered (unlike classical CSSR)

None
6.2 PARAMETERS IMPROVEMENTS

EN_AMR_CA shall be removed and replaced by 2 parameters: EN_AMR_CA_FR_HR and
EN_AMR_CA_HR_FR. These parameters shall have the same configuration as EN_AMR_CA.
HO algorithms in the BSC shall be modified so that cause 26 and cause 27 are enabled separately.

Cause 26 and cause 27 are enabled separately with EN_AMR_CA_FR_HR and EN_AMR_CA_HR_FR.
6.2.3 PARAMETERS

HMI name Definition
Sub-
system Instance
OMC-R
access Type
Def
value Range Unit
EN_AMR_CA_FR_HR
This flag enables/disables intracell HO
for AMR channel adaptation
(Handover Cause 27). BSC cell
Changeab
le Flag 0 [0,1] None
EN_AMR_CA_HR_FR
This flag enables/disables intracell HO
for AMR channel adaptation
(Handover Cause 26). BSC cell
Changeab
le Flag 0 [0,1] None

6.2.4 COUNTERS
None

Shall be initiated at migration to the value given to EN_AMR_CA in B9.
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

6.3 NEW COUNTERS FOR CALL DROP WITH SPECIFIC RADIO CAUSES

Each time a BSS triggered call release happens, the BSC shall use the last valid measurements
received for this MS to compute what is the probable cause of the drop (according to some thresholds
to be defined, which are the same as those used for emergency handover causes). This information
(bad level DL, bad quality UL, etc.) could then be used to increment the appropriate counters.
Notes:
1. The goal is not to modify the way the CLEAR REQUEST is triggered. It shall still be based on
missing SACCH measurements. However, the last measurements received before the drop
(and before the SACCH measurements are missing of course) should be stored to compute
what is the probable cause of the drop (according to some thresholds to be defined).
2. If parameters used in the equations are not correctly tuned (e.g. the corresponding HO cause
is not enabled), then it will result in incorrect reporting.
3. The window sizes used to calculate the averaged RxLev/RxQual measurements are based on
the HO window sizes: A_QUAL_HO, A_LEV_HO and A_RANGE_HO.
4. "Last valid measurements" mean the last received 48.058 MEASUREMENT RESULT messages
with S-BFI flag set to 0.
5. The new counters are triggered by BOTH TCH drop due to radio link failure (radio drops)
AND TCH drop during internal/external handover without reversion to old channel (handover
drops).
This new feature would provide a fast and efficient way to know the cause of radio related call drops,
and therefore to know which actions should be taken (parameters tuning, frequency planning, site re-
engineering, etc.) to solve these call drop issues.

The below table shows the conditions that should be fulfilled in order to trigger the corresponding
radio cause (the O&M parameters acting as thresholds are marked in blue).
Condition verified by last MS measurements
Cause to be
reported in
counters
Priority
AV_RXQUAL_UL_HO > L_RXQUAL_UL_H +
OFFSET_RXQUAL_FH
And
AV_RXLEV_UL_HO <= RXLEV_UL_IH
Too low quality in UL 1
AV_RXQUAL_DL_HO > L_RXQUAL_DL_H +
OFFSET_RXQUAL_FH
And
AV_RXLEV_DL_HO <= RXLEV_DL_IH
Too low quality in DL 2
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

AV_RXQUAL_UL_HO <= L_RXQUAL_UL_H +
OFFSET_RXQUAL_FH
And
AV_RXLEV_UL_HO < L_RXLEV_UL_H
Too low level in UL 3
AV_RXQUAL_DL_HO <= L_RXQUAL_DL_H +
OFFSET_RXQUAL_FH
And
AV_RXLEV_DL_HO < L_RXLEV_DL_H
Too low level in DL 4
AV_RANGE_HO > U_TIME_ADVANCE
Too long MS-BS
distance
5
AV_RANGE_HO L_TIME_ADVANCE
Too short MS-BS
distance
6
AV_RXQUAL_UL_HO > THR_RXQUAL_CAUSE_15 +
OFFSET_RXQUAL_FH
And
AV_RXLEV_UL_HO > RXLEV_UL_IH
Too high interference
in the uplink
7
AV_RXQUAL_DL_HO > THR_RXQUAL_CAUSE_16 +
OFFSET_RXQUAL_FH
And
AV_RXLEV_DL_HO > RXLEV_DL_IH
Too high interference
in the downlink
8

Automatic
6.3.3 PARAMETERS
None
6.3.4 COUNTERS
9 new counters (MC928a, MC928b, MC928c, MC928d, MC928e, MC928f, MC928g, MC928h and
MC928i) at cell level in type 110:

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

Short Name Name Definition
MC928a
NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_
UL
Number of TCH drops due to Cause 2 (Too low
quality in UL).
MC928b NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_UL
level in UL).
MC928c
NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_
DL
quality on the downlink).
MC928d NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_DL
level in DL).
MC928e
NB_TCH_DROP_CAUSE_TOO_LONG_MS_BS_D
ISTANCE
Number of TCH drops due to Cause 6 (Too long
MS-BS distance).
MC928f
NB_TCH_DROP_CAUSE_TOO_SHORT_MS_BS_
DISTANCE
Number of TCH drops due to Cause 22 (Too short
MS-BS distance).
MC928g
NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFER
ENCE_UPLINK
Number of TCH drops due to Cause 15 (Too high
interference level on the uplink).
MC928h
NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFER
ENCE_DOWNLINK
Number of TCH drops due to Cause 16 (Too high
interference level on the downlink).
MC928i NB_TCH_DROP_OTHER_CAUSES
Number of TCH drops due to other causes than
Cause 2 (Too low quality in UL), Cause 3 (Too low
level in UL), Cause 4 (Too low quality on the
downlink), Cause 5 (Too low level in DL), Cause 6
(Too long MS-BS distance), Cause 15 (Too high
interference level

The new counters are available on a new NPO report Alc_Mono_Drop_Causes, here is an example
of Call drop radio causes view embedded in this report.

None

Call drop radio causes - CELL2G: S-Sued-B27-Weinsteige_1_B (28934/37576) (
262/F01/28934/37576 ) - 05/19/2008 To 05/21/2008 (Working Zone:
BSC_Stuttgart124_O_and_Stuttgart163_K - Medium)
0
2
4
6
8
10
12
14
16
05/19/2008 05/20/2008 05/21/2008
n
b
.%
.5%
1.%
1.5%
2.%
2.5%
3.%
%
DL_Quality
DL_Level
DL_Interference
UL_Quality
UL_Level
UL_Interference
Short_Distance
Other_Causes
Long_Distance
% Call_drop_radio
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

6.4 NEW COUNTERS FOR SDCCH ASSIGNMENT SUCCESS RATE
Based on CMCC requirement (CR 3BKA20CBR243517), new counters were defined to better monitor
SDCCH establishment phase taking into account invalid 48.058 CHANNEL REQUIRED messages
received by the BSC.
These counters are available from B10MR2Ed7 release.

Before B10 MR2 Ed7, the available counters used to monitor SDCCH allocation phase are:
1. MC8b (NB_IMM_ASS_CMD): Number of 48.058 IMMEDIATE ASSIGN COMMAND
messages (for non-(E)GPRS related establishment cause) sent on Abis to the MS
2. MC8c (NB_CELL_CHAN_REQD): Number of 48.058 CHANNEL REQUIRED received via the
selected cell (for all establishment cause)
3. MC959 (NB_PS_CHAN_REQD): Number of 48.058 CHANNEL REQUIRED (for packet
service) received via the selected cell
4. MC960 (NB_DISCARDED_PS_CHAN_REQD_BECAUSE_GSL_CONGESTION): Number
of 48.058 CHANNEL REQUIRED (for packet service) received and discarded by the BSC in
case of GSL congestion
Accordingly, it was not possible to detect invalid CHANNEL REQUIRED messages. One possibility to
estimate the number of such messages was to apply the following formula:
Number of Invalid CS CHANNEL REQUIRED messages = (MC8c MC959) MC04 MC148,
where MC04 counts the number of SDCCH channel rejections due to congestion and MC148 counts
the number of SDCCH allocations.
The figure below shows a part of successful SDCCH establishment procedure and the related existing
counters.

With the new counters provided in Ed7, it is now possible to count all the invalid CHANNEL
REQUIRED messages for both CS and PS establishments.
It is also possible to count the number of Non PS Channel Requests discarded due to congestion.
The detailed description of new counters is presented in next section.
Automatic

6.4.3 NEW COUNTERS
MC962 (NB_INVALID_CHAN_REQD_RECEIVED_BY_BSC): Number of invalid 48.058
CHANNEL REQUIRED (for all establishment cause) received by the BSC
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

MC963 (NB_NON_PS_CHAN_REQD_DISCRADED_BECAUSE_CONGESTION): Number
of valid 48.058 CHANNEL REQUIRED (for non-(E)GPRS related establishment cause)
discarded by the BSC due to the congestion

6.4.4 NEW INDICATORS

Indicator Ref name Indicator Long Name Formula
GCCRAINVN CCCH_RACH_invalid MC962
GCCRACSCGN CCCH_RACH_discarded_CS_cong MC963
GCCRARQVAN CCCH_RACH_valid CCCH_RACH - CCCH_RACH_invalid
6.4.5 RELATED PARAMETERS
The following parameters are strongly linked to the new counter MC963:
WI_OP: Value of Wait Indication for Establishment cause = Location updating or Other
procedures which can be completed with an SDCCH
WI_EC: Value of Wait Indication for Establishment cause = Emergency call
WI_CR: Value of Wait Indication for Establishment cause = Call Re-establishment
WI_OC: Value of Wait Indication for Establishment cause = Originating call

MC963 is incremented only if WI_OP, WI_EC, WI_CR & WI_OC are 255.
If these parameters are set to be 255, MC04 (which also counts the number of immediate assignment
preparation failures due to congestion) should be equal to MC963.
Counters are available only starting from B10MR2Ed7.
No specific migration rules.

6.5 NEW COUNTERS FOR SDCCH ASSIGNMENT REQUEST FOR LOCATION
UPDATE
Based on Orange requirement (CR 3BKA20CBR260411), a new counter was created in B10MR2Ed7
to monitor SDCCH establishment requests for Location Update procedure.
The existing counter (MC02A) provides the number of successful SDCCH seizure for Location Update.
This corresponds to LU traffic, but there was no information before B10MR2Ed7 about the number of
LU requests.
Thus, with the new counter (MC964), it will be possible to calculate the SDCCH success rate for LU.

Moreover, it will be possible to compare SDCCH assign success with and without Location update.
This will be useful to analyze the impact of some bugged mobiles (not correctly managing LU
procedure between 3G and 2G) on global SDCCH assignment success rate.
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

Below is a comparison of SDCCH assign success with & without LU from a BSC in Ed7.
BSC : TARNOVO_9 (TARNOVO_9) - 05/01/2009 to 05/31/2009 (Working Zone:
Global - Medium)
.%
20.%
40.%
60.%
80.%
100.%
120.%
0
5
/
0
1
/
2
0
0
9
0
5
/
0
3
/
2
0
0
9
0
5
/
0
5
/
2
0
0
9
0
5
/
0
7
/
2
0
0
9
0
5
/
0
9
/
2
0
0
9
0
5
/
1
1
/
2
0
0
9
0
5
/
1
3
/
2
0
0
9
0
5
/
1
5
/
2
0
0
9
0
5
/
1
7
/
2
0
0
9
0
5
/
1
9
/
2
0
0
9
0
5
/
2
1
/
2
0
0
9
0
5
/
2
3
/
2
0
0
9
0
5
/
2
5
/
2
0
0
9
0
5
/
2
7
/
2
0
0
9
0
5
/
2
9
/
2
0
0
9
0
5
/
3
1
/
2
0
0
9
%
SDCCH_assign_success_rate(GSDNASUR) SDCCH_assign_success_wo_lu_rate(GSDNAWLUSUR)

It is clear that SDCCH assignment success rate is better when LU is not included.

Automatic

6.5.3 NEW COUNTER
MC964 (NB_VALID_LOCATION_UPDATE_RECEIVED_BY_BSC): Number of valid 48.058
CHANNEL REQUIRED message, received by the BSC, indicating the location update in their
"establishment cause For future usage.

6.5.4 NEW INDICATORS

Indicator B10-
refname
Long Name NPO Formula
GSDNARQLUN SDCCH_assign_request_lu MC964
GSDNALUFLN SDCCH_assign_fail_lu SDCCH_assign_request_lu - SDCCH_traffic_lu
GSDNALUSUR SDCCH_assign_success_lu_rate SDCCH_traffic_lu / SDCCH_assign_request_lu
GSDNAWLUSUR SDCCH_assign_success_wo_lu_rate
(SDCCH_assign_success - SDCCH_traffic_lu) /
(SDCCH_assign_request - SDCCH_assign_request_lu)

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

6.5.5 RELATED PARAMETERS
None

Counters are available only starting from B10MR2Ed7.
No specific migration rules.

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

7 DIFFERENTIATED RADIOLINK TIMEOUT FOR AMR CALLS
The main objective of the feature is to allow operators to fully enable AMR in their network,
including the most robust AMR-FR codecs.
The use of AMR in B9 and previous releases networks is limited. This is mainly because in these
releases an increase of call drops with radio or handover causes was generally observed after
activation of AMR, especially AMR-FR. This is a known issue, which was acknowledge by 3GPP in the
document GP-041926.
This is because the signalling channels are less robust than some of the AMR voice codecs, which
leads to call drops (cause: radio link failure) in bad radio conditions, where the SACCH frames are
not decoded but the voice quality is still correct. Consequently, the call drop rate for AMR-FR calls is
higher than for EFR calls.
In such bad radio conditions, the voice quality in AMR-FR can still be fair where as in EFR, it is poor
and the end-user ends the call himself in most cases.
Here below is the level of redundancy of EFR, AMR-FR and AMR-HR codecs:
Codec Redundancy
EFR (12.2 kb/s) 46.5%
AMR-FR 12.2 kb/s 46.5%
AMR-FR 10.2 kb/s 55.3%
AMR-FR 7.95 kb/s 65.1%
AMR-FR 7.40 kb/s 67.5%
AMR-FR 6.70 kb/s 70.6%
AMR-FR 5.90 kb/s 74.1%
AMR-FR 5.15 kb/s 77.4%
AMR-FR 4.75 kb/s 79.2%
AMR-HR 7.95 kb/s 30.3%
AMR-HR 7.40 kb/s 35.1%
AMR-HR 6.70 kb/s 41.2%
AMR-HR 5.90 kb/s 48.2%
AMR-HR 5.15 kb/s 54.8%
AMR-HR 4.75 kb/s 58.3%

The AMR-FR codecs 4.75 kb/s to 7.95 kb/s (highlighted in yellow in the above table) are more robust
than the SACCH frames which have a 60% redundancy.

In B9, the BSS uses the same Radio Link Timeout value for all calls. There are two parameters:
RADIOLINK_TIMEOUT for the counter on MS side and RADIOLINK_TIMEOUT_BS for the BSS one.
The solution in B10MR2 was to differentiate the Radio Link Timeout for AMR calls (both AMR-FR and
AMR-HR) versus the one for FR, EFR and HR calls. The Radio Link Timeout can thus be increased
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

specifically for AMR calls to delay the detection of the radio link failure. Consequently, the end-user
behaviour can be closer than with FR, EFR and HR.


The Radio Link Timeout for AMR is set on a per-cell basis.
The feature is automatically activated upon migration to or installation of B10. Starting from this
release, one set of parameter defines the Radio Link Timeout for legacy codecs (FR, HR and EFR i.e.
speech versions 1 and 2) and another set defines the Radio Link Timeout for AMR calls.
On the other hand, the feature is disabled from a technical point of view as soon as the same values
are set for the Radio Link Timeout for AMR and for legacy codecs.
7.3 PARAMETERS

Parameter name Definition Sub-
system
Instance OMC-R
Category
Default
value
Range Type
RADIOLINK_TIMEOUT_AMR Initial and max
value of MS radio
link counter,
when an AMR
codec is used.
OMC-R 2G cell changeable 16 4..64 Number
RADIOLINK_TIMEOUT_BS_AMR

Initial and max
value of BSS
radio link
counter, when an
AMR codec is
used.
OMC-R 2G cell changeable 18 1..128 Threshold
Notes:
o The HMI name of RADIOLINK_TIMEOUT_BS_AMR is: RADIOLINK_FAILURE_THRES_AMR
o RADIOLINK_TIMEOUT_AMR is coded from 0 to 15 (0 = 4 Samfr, 1 = 8 Samfr ... 15 = 64
Samfr); the step size is 1 = 4 Samfr
7.4 COUNTERS

No counter specific to this feature.

Standard CS Quality of Service and stability follow-up of the network should be performed during
migration.
7.5 MIGRATION RULES

At migration from B9 to B10, the feature is actually idle as logical parameters
RADIOLINK_TIMEOUT_AMR and respectively RADIOLINK_TIMEOUT_BS_AMR take the values of
RADIOLINK_TIMEOUT and respectively RADIOLINK_TIMEOUT_BS.

For Parameter
name in B9
Parameter
value in
B9
Parameter name in B10 Parameter value in
B10
All
cells
N/A N/A RADIOLINK_TIMEOUT_AMR Same as
RADIOLINK_TIMEOUT
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

All
cells
N/A N/A RADIOLINK_TIMEOUT_BS_AMR Same as
RADIOLINK_TIMEOUT_BS

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

8 STM1 CONNECTIVITY IN TC
This feature aims at reducing transmission cost which usually represents a significant part of the Total
Cost of Ownership for a Network Operator. Traditionally based on E1 transport links, solutions for the
GSM transport network have evolved to other technologies, such as SDH. This feature allows STM1
connectivity at transcoder level.
STM-1 is available to the A and the Ater interfaces. However, depending on the operator's network,
STM-1 transport may be used over the A interface only until there is a native support of STM-1 by the
BSC (in B11MR1), alternatively an ADM equipment may be used for the Ater interface.
The speech transcoding function remains handled by the MT120 board (legacy MT120, or MT120-
NB or MT120-WB), there is therefore no foreseeable impact on speech QoS. Any possible impact of
STM-1 is limited to the QoS of the transmission over the A interface, and possibly of the Ater interface
when applicable.
The new JBTC-STM1 board offers four STM-1 (155Mb/s) optical interfaces to the TC A9125
transcoder. The JBTC-STM1 boards are always paired off to provide a 1+1 redundancy, known as
Automatic Protection Switching (APS).
The board can be used in a mixed mode where a subset of its optical interfaces is used while part of
the TC A9125 E1 interfaces remain in service. The granularity is at MT120 board level i.e. the whole
A interface of an MT120 board has to be transported over STM-1. The granularity is applicable to A
and Ater interfaces.
The OMC-R can supervise the JBTC-STM1 board and the STM-1 interface.
TC-STM1 feature is supported only by TC G2.5; it is available from B10MR2Ed7 release.
This feature doesnt offer telecom gains; only operational gains are offered, described below.

Feature benefits:
Integrated STM-1 interfaces on the BSS network elements help to:
Reduce cost on interface equipment to SDH network: Removal of E1 to STM-1 boards to
connect the TC to the SDH network (CAPEX saving).
Reduce drastically time/error of installation/cabling: Only 4 STM-1 interfaces are needed in
TC to replace the 192 E1 links for A interface and 48 E1 links for Ater interface (OPEX saving).
Reduce the space needed for cables and distribution frames: The 8 STM1 fibers use much less
cable ways and distribution frames than the 252 PCM links (OPEX saving).
Simplify cabling & assignment changes: Modification of routing of a VC12 can be done
remotely by computer command, as there is no cabling change (OPEX saving).
Increase the reliability and availability: STM-1 connectivity provides excellent availability
thanks to the combination of APS (Automatic Protection Switching) & EPS (Equipment
Protection Switching), as well as its benefit from the reliability of SDH network architecture
(OPEX saving). Due to the high traffic per STM-1 link, protection is done by APS in
unidirectional/non-revertive configuration (this means that over longer time a link can be
distributed over two TCIF), coupled with EPS 1+1 for transmission board protection, providing
high reliability and availability of the transmission links.

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

This feature is optional from commercial point of view. It is activated as soon as the following actions
are completed:
Installation of JBTC-STM1 board, optical cables, HSI (High Speed Links)
STM1 configuration through the TC NEM
Declaration of STM1 links at OMC-R
8.3 PARAMETERS

Among the different parameters related to this feature; the below ones are those that can be relevant
for this documents reader. Other TC parameters are set by TC-NEM during TC-STM1 feature
commissioning.

Parameter name Definition
Sub-
system
Instance
OMC-R
Category
Default
value
Range Type
Max-Number-STM1-
Interface

Indicates the maximum
number of STM1 interfaces
allowed to be declared in the
considered OMC
OMC-R OMC-R SITE (CAE) 0
[0
None]
Number
WarnThreshold-Limited-
Features

Threshold above which a
warning message shall be
displayed to the user. It is
expressed as percentage of
the upper limits defined for
the
locked features.
When the number of objects
configured with any of the
locked features exceeds this
threshold, but is still below the
upper limit, the user receives
a
warning message
OMC-R OMC-R SITE (CAE) 95% [0100] Threshold

8.4 COUNTERS / INDICATORS

No new PM counters / indicators

8.5 MIGRATION RULES

None

ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

9 GENERAL B10 QOS FEEDBACK

9.1 PARAMETERS VARIATIONS

9.1.1 PARAMETERS INSTANCE CHANGES

In B10 some parameters has changed its instance. For the further list, special attention should be
given after BSC migration to obtain the same parameterization as previous release,
launching a MLU / PRC action if needed. Otherwise some variation might be observed in QoS
indicators.

EN_DTM - This parameter changed instance from BSS -> cell
T200_TF - This parameter became OMC-R changeable and changed instance from BTS ->
cell
T200_TH - This parameter became OMC-R changeable and changed instance from BTS ->
cell

9.2 QOS VARIATIONS

9.2.1 BULGARIA
9.2.1.1 from B10MR2Ed3QD6 to B10MR2Ed6QD2

in Veliko Tarnovo, pilot area consists in 1 BSC : Tarvono_9.

QoS feedback:
All KPIs are stable before and after the migration, no regression was observed CS domain.

9.2.1.2 from B10MR2Ed6QD2 to Ed7a then to ED7QD1

in Veliko Tarnovo, pilot area consists in 1 BSC : Tarvono_9.

QoS feedback: along different s/w versions
All main KPIs are stable, for CS domains and PS domains
A interface measurements show stable performances
voice quality results confirmed non regression

9.2.1.3 from B10MR2Ed3QD6 to Ed7a then to Ed7QD1 then to Ed7QD2

pilot on BSC : Varna_96

QoS feedback:
Main CS indicators are stable along different s/w versions
CS indicators remain stable in Ed7QD2
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

9.2.2 GERMANY

9.2.2.1 from B9MR4ed7 to B10MR2

the call drop remote TC was affected by the migration from B9MR4ed7 to B10MR2ed3.1
while it remains unaffected on the non migrated BSCs (Stuttgart179_M) still in B9.

the root cause was not found, no clear link with B10 relesase as been identified.

Call Drop BSS Remote TC - BSC - 14/07/2008 to 17/08/2008
0
50
100
150
200
250
300
1
4
-
0
7
-
2
0
0
8
1
6
-
0
7
-
2
0
0
8
1
8
-
0
7
-
2
0
0
8
2
0
-
0
7
-
2
0
0
8
2
2
-
0
7
-
2
0
0
8
2
4
-
0
7
-
2
0
0
8
2
6
-
0
7
-
2
0
0
8
2
8
-
0
7
-
2
0
0
8
3
0
-
0
7
-
2
0
0
8
0
1
-
0
8
-
2
0
0
8
0
3
-
0
8
-
2
0
0
8
0
5
-
0
8
-
2
0
0
8
0
7
-
0
8
-
2
0
0
8
0
9
-
0
8
-
2
0
0
8
1
1
-
0
8
-
2
0
0
8
1
3
-
0
8
-
2
0
0
8
1
5
-
0
8
-
2
0
0
8
1
7
-
0
8
-
2
0
0
8
n
b
Stuttgart156_L
Stuttgart_Esslingen135_I
Stuttgart179_M
BSC
BSC : Stuttgart156_L - 27/07/2008 00:00 to 05/08/2008 23:00
0
5
10
15
20
25
30
35
40
45
2
7
-
0
7
-
2
0
0
8
0
0
:
0
0
2
8
-
0
7
-
2
0
0
8
0
0
:
0
0
2
9
-
0
7
-
2
0
0
8
0
0
:
0
0
3
0
-
0
7
-
2
0
0
8
0
0
:
0
0
3
1
-
0
7
-
2
0
0
8
0
0
:
0
0
0
1
-
0
8
-
2
0
0
8
0
0
:
0
0
0
2
-
0
8
-
2
0
0
8
0
0
:
0
0
0
3
-
0
8
-
2
0
0
8
0
0
:
0
0
0
4
-
0
8
-
2
0
0
8
0
0
:
0
0
0
5
-
0
8
-
2
0
0
8
0
0
:
0
0
n
b
Call_drop_BSS_remote_TC(GQSCDBTN)
BSC
ED 3 RELEASED

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

After migration, only peaks of Drop BSS RTC were observed, as opposed to the regular distribution
over traffic hours observed in B9 (see example here above of hourly distribution for Stuttgart156_L).
All cells having Drop BSS RTC in B9 improved after migration.

The same improvement was observed on other pilot BSCs areas.

END OF DOCUMENT

B9B10-Nonregression CS Ed03

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

B9B10-Nonregression CS Ed03

Încărcat de

Drepturi de autor:

Formate disponibile

ED 3 RELEASED

WBG B9B10-nonregression_CS_ed03.doc 2009-07-09 3DF 01906 8011 WAZZA 1/41

S-ar putea să vă placă și