B9 Counter Improved

All rights reserved.
Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Evolium.
6LWH VELIZY 2ULJLQDWRUV E. BRIGANT 6\VWHP 6XEV\VWHP 'RFXPHQW &DWHJRU\ : : :
(92/,80 6$6 COUNTER IMPROVEMENTS FOR RELEASE B9
ALCATEL GSM BSS SYS-TLA PRODUCT DEFINITION
$%675$&7
This SFD describes the "COUNTER IMPROVEMENTS FOR RELEASE B9" feature. The following four subfeatures are described in this SFD: Improvement 1 Support of distributions: It introduces a new concept of counters called distributions to obtain improved statistics on (E)GPRS resource usage. Improvement 2 Consolidation of cell indicators at GPU level: It allows an operator to consolidate each indicator defined at cell level per GPU. This operation is very useful to follow possible lacks of GCH or GPU resources in a given GPU. Improvement 3 Counters defined at TRX level: It introduces a few counters defined at TRX level to follow the radio and transmission resource usage. This sub-feature would be all the more required as the dynamic Abis feature is not implemented. Improvement 4 New MFS counters: It consists in defining a few new counters to ease the dimensioning and optimisation of (E)GPRS networks.
Only the following sub-features are implemented in release B9: Improvement 1 Support of distributions. Improvement 2 Consolidation of cell indicators at GPU level. Improvement 4 New MFS counters. $SSURYDOV D. BOMY
PL
Name App.
J. ACHARD
SYT Manager
J.-P. GRUAU
PM
Name App.
G. DAEL
OSY Manager
R. MAUGER
SYT DPM
ED 01 RELEASED
0613_01.doc 22/04/2004
COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 1/34
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Evolium.
5(9,(:
Edition 01 Proposal 04 09/121/2003 See review report MND/TD/VAL/SYT/EBR/0380.2003
+,6725<
Edition 01 Proposal 01 Edition 01 Proposal 02 Edition 01 Proposal 03 Edition 01 Proposal 04 Edition 01 Proposal 05 Edition 01 Proposal 06 Edition 01 Released 07/10/2003 20/10/2003 First proposal of the SFD based on memo MND/TD/VAL/SYT/EBR/0261.2003 The document has been updated to take into account the comments reported in the review report: MND/TD/VAL/SYT/EBR/0322.2003 The document has been updated to take into account the comments reported in the review report: MND/TD/VAL/SYT/EBR/0343.2003 The document has been updated to take into account the comments reported in the review report: MND/TD/VAL/SYT/EBR/0363.2003 The document has been updated to take into account the comments reported in the review report: MND/TD/VAL/SYT/EBR/0380.2003 The document has been updated to take into account several comments received during the development preparation phase. The document has been released after taking into account the comments reported in the review report: MND/TD/VAL/SYT/EBR/0191.2004
07/11/2003
01/12/2003
19/12/2003
05/04/2004 15/04/2004
ED 01 RELEASED
0613_01.doc 22/04/2004
7$%/( 2) &217(176
,1752'8&7,21 6FRSH 'RFXPHQW 6WUXFWXUH 'HILQLWLRQV DQG SUHUHTXLVLWH +,*+/(9(/ '(6&5,37,21 )XQFWLRQDO 5HTXLUHPHQWV 2YHUDOO GHVFULSWLRQ RI WKH SURSRVHG VROXWLRQV 2.2.1 Improvement 1: Support of distributions ..................................................................................... 7 2.2.2 Improvement 2: Consolidation of cell indicators at GPU level .................................................... 8 2.2.3 Improvement 3: Counters defined at TRX level.......................................................................... 8 2.2.4 Improvement 4: New MFS counters ........................................................................................... 9 &RPSOLDQFH WR WKH 0DUNHWLQJ 5HTXLUHPHQWV &RPSOLDQFH WR *33 VWDQGDUG :RUNLQJ $VVXPSWLRQV 'HSHQGHQFLHV +: &RYHUDJH 'HFLVLRQ FULWHULD 2.8.1 Standardisation ......................................................................................................................... 11 2.8.2 Competition............................................................................................................................... 11 2.8.3 Customer .................................................................................................................................. 11 2.8.4 Gains......................................................................................................................................... 11 2.8.5 Risks ......................................................................................................................................... 11 6<67(0 ,03$&76 7HOHFRP 3.1.1 Functional-level description ...................................................................................................... 13 3.1.2 Telecom Specification impacts ................................................................................................. 14 3.1.3 Interfaces .................................................................................................................................. 15 2SHUDWLRQ DQG PDLQWHQDQFH 3.2.1 OMC-R parameters .................................................................................................................. 15 3.2.2 Modelisation of OMC-R parameters ......................................................................................... 16 3.2.3 Other parameters...................................................................................................................... 17 3.2.4 BSC PM counters ..................................................................................................................... 17 3.2.5 MFS PM counters ..................................................................................................................... 17 3.2.6 PM indicators ............................................................................................................................ 20 3.2.7 Migration ................................................................................................................................... 21 3.2.8 Java scripts ............................................................................................................................... 22 3.2.9 Fault Management .................................................................................................................... 22 3.2.10 O&M Specification impacts ....................................................................................................... 22 9DOLGDWLRQ )LHOG SURFHGXUH GHVLJQ *HQHULF &XVWRPHU GRFXPHQWDWLRQ (QJLQHHULQJ UXOHV 68%6<67(0 ,03$&76 %76 %6& 7UDQVFRGHU 0)6 20&5 4.5.1 HMI impacts .............................................................................................................................. 24 4.5.2 OMC modelization .................................................................................................................... 25 4.5.3 Optional feature ........................................................................................................................ 25 4.5.4 Overview of the impact upon OMC specs ................................................................................ 25 /$6(5 ED 01 RELEASED
0613_01.doc 22/04/2004

13$ 512 3ROR 2()

3(5)250$1&( 6<67(0 ',0(16,21,1* 7UDIILF PRGHO 3HUIRUPDQFH /RDG FRQVWUDLQWV 23(1 32,176 ,03$&76 6800$5< */266$5< $EEUHYLDWLRQV 7HUPLQRORJ\ $11(; $ 0$,1 ',))(5(1&(6 %(7:((1 5$',2 0($685(0(17 67$7,67,&6 $1' 3$&.(7 ',675,%87,216 $11(; % ,03$&76 21 13$ &$3$&,7<
ED 01 RELEASED
0613_01.doc 22/04/2004
,17(51$/ 5()(5(1&(' '2&80(176

Not applicable
5()(5(1&(' '2&80(176
$OFDWHO UHIHUHQFHV [ 1] 3BK 11203 0101 DSZZA, MFS counters catalogue, release B9 [ 2] 3BK 11203 0102 DSZZA, BSC counters catalogue, release B9 [ 3] 3BK 11204 0343 DSZZA, BSS indicators catalogue, release B9
*33 UHIHUHQFHV [ 4] 3GPP TS 23.060, 3GPP TS Group SA, GPRS Service description, Stage 2, Release 4 [ 5] 3GPP TS 44.064, 3GPP TS Group CN, MS-SGSN LLC layer specification, Release 4 [ 6] 3GPP TS 45.002, 3GPP TS Group GERAN, Multiplexing and multiple access on the radio path, Release 4
5(/$7(' '2&80(176
$OFDWHO GRFXPHQWV [ 7] MND/TD/VAL/SYT/EBR/0261.2003 Ed01, Analysis of the feature counters improvements, release B9 [ 8] 3BK 10204 0486 DTZZA, SFD: Radio Measurement Statistics, release B7.2 [ 9] 3BK 10204 0606 DTZZA, SFD: Enhanced packet cell reselections, release B9 [ 10] 3BK 10204 0605 DTZZA, SFD: Support of QoS in the BSS, release B9 *33 &5V None
35()$&(
This document is the input paper for the feature COUNTER IMPROVEMENTS FOR RELEASE B9 inside TD. It will further on be used as reference for the development of that feature in each subsystem.
ED 01 RELEASED
0613_01.doc 22/04/2004

,1752'8&7,21 6FRSH
The present document aims to be the basis for decision of a proposed change to be made on the BSS system. It provides all necessary information related to functional description, gains, description of the system impacts and subsystem impacts.

'RFXPHQW 6WUXFWXUH
The section 2 of this document presents: the functional requirements, an overall description of the features, the compliance to marketing requirements and to the 3GPP standard, which working assumptions have been made and the dependencies, as well as some decision criteria such as the risk, the gain, etc. associated to the features addressed by the present SFD. The section 3 identifies the system impacts : it gives the principles and presents the functional split of the feature between subsystems. The interactions within the BSS between the various modules, layers, etc are shown as well as the interaction with the other Network Elements. Impacts on telecom and O&M Step2 specifications are also given in this section. The validation strategy is presented as well as the impacts on GCD, methods and engineering rules. The section 4 recaps the impacts for each subsystem. The section 5 addresses the performance and system dimensioning concerns. The section 6 identifies and describes the open points that have been raised in the various reviews. The section 7 is a sum up of the system impacts. The section 8 contains the glossary of the present document.

'HILQLWLRQV DQG SUHUHTXLVLWH
In this section, we describe in a few lines the feature Radio Measurement Statistics (RMS) that was introduced on release B7.2 in order to get statistics on radio measurements such as RXLEV, RXQUAL, interference level, timing advance, MS or BS transmitted power, etc. The RMS feature is based on the following principles: The operator can launch RMS from the OMC-R on a per cell or per BSC basis for a given duration (up to 23 hours). The radio measurements are monitored the closest to the observed functions, i.e. in the BTS. During the observation period, it is possible to launch extended measurement reporting in order to get measurements on radio frequencies not used for CS/PS traffic in the cell. The measurements are usually reported in vectors made of 10 values (or matrixes made of several vectors). The ranges of each vector are defined by 9 thresholds. These thresholds are changeable at the OMC-R. The main differences between RMS and the packet distributions introduced hereafter are listed in Section 9.
ED 01 RELEASED
0613_01.doc 22/04/2004
+,*+/(9(/ '(6&5,37,21
The SFD describes the following sub-features: Improvement 1: Support of distributions Improvement 2: Consolidation of cell indicators at GPU level Improvement 3: Counters defined at TRX level Improvement 4: New MFS counters In what follows, each sub-feature is presented and analysed separately.

)XQFWLRQDO 5HTXLUHPHQWV
Analyzing the dimensioning aspects of our BSS shows that some important PS counters are missing in our BSS to dimension the resources used to carry (E)GPRS traffic. Also, until now, the MFS counters have been defined similarly as BSC counters which monitor CS traffic. The problem is that PS traffic is very different from CS traffic, which makes CS approach not really relevant in PS domain. The sub-features described hereafter propose several solutions to overcome these weaknesses.

2YHUDOO GHVFULSWLRQ RI WKH SURSRVHG VROXWLRQV
,PSURYHPHQW 6XSSRUW RI GLVWULEXWLRQV This sub-feature introduces a new concept of counters to monitor PS resource usage. The existing PS counters count a number of events occurring during the reporting period (i.e. every hour). However, such counters do not allow retrieving the distribution of the events. For instance, existing counters allow evaluating the averaged duration of the TBFs. However, it is interesting to know what is the proportion of short TBFs compared to long TBFs, to evaluate the type of GPRS traffic, to understand the throughput measured in the fields, etc.. An example of a TBF duration distribution is presented in Figure 1. In what follows, these new counters are called distribution.
'LVWULEXWLRQ RI WKH 7%) GXUDWLRQ

Q R L W X E L U W V L '

0 s <= x < 10 s 10 s <= x < 20 s 20 s <= x < 30 s 30 s <= x < 40 s 40 s <= x < 50 s 50 s <= x < 60 s 60 s <= x < 70 s 70 s <= x < 80 s 80 s <= x < 90 s 90 s <= x <100

U7Aqhvvrhy
)LJXUH ([DPSOH RI D 7%) GXUDWLRQ GLVWULEXWLRQ The feature support of distributions is non-optional and is always activated as normal PM counters.
ED 01 RELEASED
0613_01.doc 22/04/2004
,PSURYHPHQW &RQVROLGDWLRQ RI FHOO LQGLFDWRUV DW *38 OHYHO In release B8, NPA and RNO do not allow performing consolidation of cell indicators at GPU level. However, such a consolidation is useful to dimension the resources managed at GPU level (e.g. GCH resources, GPU resources).In release B9, the consolidation at GPU level is only required for the counters/indicators listed in Table 1.
Srsrrpr
P105c P105d P105e P105f P105g P105h
9rsvvv
Number of DL TBF establishment failures due to GPU congestion. Number of UL TBF establishment failures due to GPU congestion. Number of DL TBF establishment failures due to CPU processing power limitations of the GPU. Number of UL TBF establishment failures due to CPU processing power limitations of the GPU. Number of DL TBF establishment failures due to a lack of transmission resources. Number of UL TBF establishment failures due to a lack of transmission resources.
Dhpr
Cell Cell Cell Cell Cell Cell
7DEOH &RXQWHUV IRU ZKLFK D FRQVROLGDWLRQ DW *38 OHYHO LV UHTXLUHG Also, without this consolidation, it is up to the MFS to perform the consolidation, which is in contradiction with the usual principles. Indeed, it is not the role of the MFS to perform computation on counters. The sub-feature consists in allowing the operator to consolidate at GPU level cell counters indicators using P105c/d/e/f/g/h cell counters P105c/d/e/f/g/h at GPU level. For instance, let us take the example of a BSC configuration where 50 cells Ci with i = 1, 2, , 50 are mapped on a first GPU1 and 50 other cells Ci with i = 51, 52, , 100 are mapped on a second GPU2. NPA should be able to sum all counters P105x defined per cell and related to a cell mapped on GPU 1. The same sum shall be retrieved on GPU2 too. This means that if the operator is interested in a consolidation on P105g, the tool chain should be able to compute:
P105g(GPU1) =
P105g
i=1
50
where P105gi is the counter P105g counting the number of DL TBF failures due to a lack of GCH resource in Cell Ci. Similarly, on GPU2, we have:
P105g(GPU2) =
P105g
i = 51
100
NPA shall allow the operator to know whether a spatial consolidation performed per GPU on indicators defined at cell level is valid or invalid after a new GPU-cell re-mapping. One new suspected flag is then required per GPU. This flag is hereafter called GPU Configuration Suspected Flag (GCSF) and is set by the MFS per GPU when at least one cell has been created, deleted or remapped on the concerned GPU during the reporting period. From the GPU Configuration Suspected Flag, NPA shall derive a reliability indicator per GPU indicating whether or not the spatial consolidation per GPU is suspected. A spatial consolidation per GPU is suspected: - if it concerns a GPU for which the GPU Configuration Suspected Flag has been set at least once during the period considered for the consolidation, or, - If it concerns a GPU for which a GPU PM report is missing during the period considered for the consolidation. Since release B7, the MFS provides NPA with an existing suspected flag called Suspected Flag (SF). In order to avoid any confusion with the GPU Configuration Suspected Flag, this existing flag is renamed as Cell Configuration Suspected Flag (CCSF). NPA uses this flag to derive a reliability indicator per cell to indicate whether a cell have been newly created on the GPU (e.g. at O&M cell creation or after a re-mapping of the cells on the GPU. ,PSURYHPHQW &RXQWHUV GHILQHG DW 75; OHYHO This sub-feature is not implemented in release B9.
ED 01 RELEASED
0613_01.doc 22/04/2004
In release B8, no MFS counter is defined at TRX level. It then becomes difficult to dimension the number of extra Abis nibbles required per TRX based only on counters defined at cell level. This sub-feature introduces the possibility to define counters at TRX level. Also, NPA shall be able to consolidate TRX counters at cell level as it is already done for TRX counters computed in the BSC. ,PSURYHPHQW 1HZ 0)6 FRXQWHUV When studying the PS dimensioning rules in release B8, it appears that the following PS counters were missing in our BSS: Counters to differentiate GMM signalling from data traffic. Counters to quantify the overlapping of the TBFs on the PDCHs. Counters to know the number of UL or DL TBFs releases due to the suspension procedure. This sub-feature introduces the counters listed above.

&RPSOLDQFH WR WKH 0DUNHWLQJ 5HTXLUHPHQWV
The table below identifies the compliance of each sub-feature to one or more marketing requirements. )HDWXUH ,WHP Improvement 1 Improvement 2 Improvement 3 Improvement 4 &RPSOLDQFH Yes Yes Yes Yes &RPPHQWV

&RPSOLDQFH WR *33 VWDQGDUG
The sub-features described in this SFD are manufacturer dependent and therefore not described in 3GPP standard.

None
:RUNLQJ $VVXPSWLRQV 'HSHQGHQFLHV

In this section, the technical dependencies between features of this SFD and with features addressed by other SFDs or already implemented are identified.
1)
Sub-feature "Improvement 1: Support of distributions"
No dependency identified. Sub-feature ",PSURYHPHQW : &RQVROLGDWLRQ RI FHOO LQGLFDWRUV DW *38 OHYHO "
2)
No dependency identified. 3) Sub-feature ",PSURYHPHQW : &RXQWHUV GHILQHG DW 75; OHYHO " LV LQFRPSDWLEOH ZLWK i.e. identify the features which are technically incompatible with the present feature
ED 01 RELEASED
0613_01.doc 22/04/2004
Feature Dynamic Abis
Dependency If the Dynamic Abis feature is not implemented, Alcatel BSS shall provide some means to assist the operator in the dimensioning of the number of extra Abis nibbles required per TRX. One mean is to allow the definition of TRX counters to monitor the usage of Abis resources.
4)
Sub-feature ",PSURYHPHQW : 1HZ 0)6 FRXQWHUV "
No dependency identified.

+: &RYHUDJH
This section defines the HW coverage of the sub-feature(s). A synthetic and exhaustive table is provided where the different HW generation of each subsystem are listed. 6\VWHP GSM 900 DCS 1800 DCS 1900 GSM 850 Y Y Y Y
1HWZRUN HOHPHQW In the table below, the following definitions apply: sw X if feature supported by the NE with software impact, hw X if feature supported by the NE with hardware impact sw+hw if feature supported by the NE with software and hardware impact. X X : The feature is supported on the NE without hardware or software impacts. - : The feature is not supported by the NE or the NE is not concerned by the feature
7UTBrrhv)
Dhpsi Dhpsi Dhpsi Dhpsi srhr srhr srhr srhr vrr vrr! vrr" vrr#
BTS G2 with DRFU BTS MK2 with DRFU A9100 (Evolium standard) A910 (micro Evolium (M4M)) M1M, M2M BSC G2 MFS Alcatel TSC TRAU G2 with DT16 TRAU G2 with MT120 TRAU G2.5 (with MT120) MSC SGSN Data IWF HLR OMC-R POLO OEF LASER Xsw Xsw Xsw Xsw Xsw
7T8Brrhv) HAT) Uhvv) Uhpqr) HT8) TBTI) 9hhDXA) CGS) PH)
ED 01 RELEASED
0613_01.doc 22/04/2004
MPM/NPA RNO
Xsw Xsw
Xsw Xsw
Xsw Xsw
Xsw Xsw
HTUT)
MSTS

'HFLVLRQ FULWHULD
In this section, the criteria relevant for deciding whether or not to implement the feature(s) are provided. 6WDQGDUGLVDWLRQ Not applicable &RPSHWLWLRQ According to PCS, Motorola BSS already provides a set of distributions. Other competitors will likely provide means like distributions in a mature (E)GPRS BSS release. &XVWRPHU During the review of B8 BSS counters with Orange, it has been noticed that some important counters were missing in our BSS. *DLQV
7HOHFRP JDLQV No Telecom gain is expected by this SFD. 2SHUDWLRQDO JDLQV The features proposed in this SFD will ease the BSS dimensioning process and the follow up of PS QoS. The network design and network optimization departments will mainly take benefits of these gains. Table 2 gives the rationale for each packet distribution and each new cell counter introduced in the SFD. 5LVNV The following risk is today identified: The introduction of distributions shall not decrease the CPU capacity of the GPUs, nor NPA capacity.
8r ir
P453a
Hrvp
DISTRIB_UL_TBF_DUR ATION
Shvhyr
The distribution of the UL TBF duration is interesting to: Differentiate the type of traffic (GMM signalling, Web browsing, FTP transfers, etc.). Check the validity of the UL TBF duration reported by the PM counters. For instance, the average is meaningless if long TBFs are not distinguished from short TBFs. Justify certain bad throughputs observed in the fields. The corresponding thresholds should be tuneable to allow isolating a given traffic for a deep field analysis. Same rationale as P453a but for the DL direction The distribution of the UL LLC volume is interesting to: Differentiate the type of traffic (GMM signalling, Web browsing, FTP transfers, etc.). Check the validity of the UL LLC volumes (measured in bytes) reported by the PM counters. For instance, the average is meaningless if long TBFs generating high UL LLC volumes are not distinguished from short TBFs generating small UL LLC volumes. Justify certain bad throughputs observed in the fields. The corresponding thresholds should be tuneable to allow isolating a given traffic for a deep field analysis. Same rationale as P454a but for the DL direction The distribution of the number of PDCH units assigned to an UL TBF is required to check whether non-optimal allocations come from a lack of radio resources. In this case, parameters like MAX_PDCH, MAX_PDCH_HIGH_LOAD can be increased. Same rationale as P455b but for the DL direction
P453b P454a
DISTRIB_DL_TBF_DUR ATION DISTRIB_UL_TBF_VOLU ME
P454b P455a
DISTRIB_DL_TBF_VOLU ME DISTRIB_UL_PDCH_UNI T_ALLOC DISTRIB_DL_PDCH_UNI T_ALLOC
P455b
ED 01 RELEASED
0613_01.doc 22/04/2004
8r ir
P38f P38e P451a
Hrvp
CUMULATED_TIME_PD CH_USED_UL_CELL CUMULATED_TIME_PD CH_USED_DL_CELL CUMULATED_TIME_PD CH_UL_TBF_CELL CUMULATED_TIME_PD CH_DL_TBF_CELL CUMULATED_TIME_PD CH_DL_TBF_GMM_SIG_ CELL NB_SUSP_UL_TBF_REL NB_SUSP_DL_TBF_REL
Shvhyr
This counter is used with P451a to quantify the overlapping of the UL TBFs on the PDCHs. For instance, a high overlapping factor can explain why the throughputs observed in the fields are low. Same rationale as P38f but for the DL direction. This counter is used with P38f to quantify the overlapping of the UL TBFs on the PDCHs. For instance, a high overlapping factor can explain why the throughputs observed in the fields are low. Same rationale as P451a but for the DL direction.
P451b
P452
P98f P98e
This counter is used to quantify the part of the GMM signalling traffic over the whole (E)GPRS traffic. For instance, this information is required to know how many radio resources should be configured to carry only GMM signalling traffic. This counter is defined to obtain a more accurate indicator for TBF drops. Operators are carefully analysing the TBF drop rate that it is one of the main (E)GPRS QoS figures. Same rationale as P98f but for the DL direction.
7DEOH 5DWLRQDOH IRU HDFK SDFNHW GLVWULEXWLRQ DQG HDFK QHZ FHOO FRXQWHU
ED 01 RELEASED
0613_01.doc 22/04/2004

6<67(0 ,03$&76 7HOHFRP

)XQFWLRQDOOHYHO GHVFULSWLRQ ,PSURYHPHQW 6XSSRUW RI GLVWULEXWLRQV

The BSS shall manage a new type of counters, called distribution. It is proposed to denote the distribution as PD_x where P stands for Packet and D for distribution, x is a name used as a reference. A distribution will be defined as a vector made of 10 values denoted as PD_x_a to PD_x_j. Each value will be delimited by one or two O&M thresholds denoted PD_x_THR_1 to PD_x_THR_9 (See Table 3). Except for the extreme values of the vector, one threshold defines the lower limit of the value, whereas another threshold defines the upper limit of the value. These thresholds will be defined per BSS. 9DOXH RI WKH GLVWULEXWLRQ 3'B[ PD_x_a PD_x_b PD_x_c PD_x_d PD_x_e PD_x_f PD_x_g PD_x_h PD_x_i PD_x_j 7KUHVKROGV GHILQLQJ WKH ERUGHUV RI WKH GLVWULEXWLRQ YDOXHV
Incremented if PD_x < PD_x_THR_1 Incremented if PD_x_THR_1 PD_x < PD_x_THR_2 Incremented if PD_x_THR_2 PD_x < PD_x_THR_3 Incremented if PD_x_THR_3 PD_x < PD_x_THR_4 Incremented if PD_x_THR_4 PD_x < PD_x_THR_5 Incremented if PD_x_THR_5 PD_x < PD_x_THR_6 Incremented if PD_x_THR_6 PD_x < PD_x_THR_7 Incremented if PD_x_THR_7 PD_x < PD_x_THR_8 Incremented if PD_x_THR_8 PD_x < PD_x_THR_9 Incremented if PD_x_THR_9 PD_x 7DEOH 'HVFULSWLRQ RI D JLYHQ GLVWULEXWLRQ 3'B[
The following rule applies on the setting of the thresholds: PD_x_THR_1 < PD_xTHR_2 < ... < PD_x_THR_9, where x stands for the name of the packet distribution. Each distribution will be described as a set of 10 sub-counters in the MFS counters catalogue. The tool chain shall be able to provide the following facilities on the handling of distributions: The distributions shall be reported permanently i.e. every hour as any other MFS counters. RNO shall be able to provide classical statistics on the distributions: estimation of an average, estimation of the standard deviation, etc. Any function applicable to RMS can be re-used for the distributions. The tuning of the packet distribution thresholds shall be allowed from RNO and from the OMC-R. In order to simplify RNO implementation, a global tuning applicable to all BSSs is acceptable at RNO level. At OMC-R level, the tuning can be performed on a per BSS basis. Like RMS, it is acceptable that all modifications performed on the OMC-R are not taken into account by RNO in the parameter templates. NPA shall be able to consolidate the packet distributions per day. To limit the impacts on NPA, consolidations per week and per month are not supported. However, RNO shall provide some means to export files so that an operator can easily perform the consolidation per week and per month with Excel or any other tool.. NPA shall be able to consolidate the packet distributions per BSS and per GPU. Consolidations at network level are not allowed since performing a consolidation on an inconsistent set of distribution
ED 01 RELEASED
0613_01.doc 22/04/2004
thresholds may lead to irrelevant results (as explained in Section 3.2.1 the distribution thresholds are defined per BSS). In case an O&M operation has modified one of the distribution thresholds, the operator shall be informed that a consolidation involving two configurations of the same distribution may lead to irrelevant results. The MFS shall then indicate for each cell whether the distribution may contain inconsistent measurements due to a change of the distribution thresholds during the PM reporting period. For that purpose, a new flag called Distribution Suspected Flag (DSF) will be present per cell on the OMC/MFS interface to indicate such a change. This flag is here defined per cell (instead of per distribution) to reduce the impacts on NPA capacity. NPA shall then build a reliability indicator per cell for packet distributions.
The RMS feature uses parameters requiring a specific tuning at cell level. As the distribution parameters are defined at BSS level, we do not see the need for templates to assist the operator in the tuning of the distributions at the OMC-R. The value of the thresholds are reported in the cell PM report that the MFS sends to NPA. The MFS cell PM report shall contain the following information elements (on a per cell basis): The newest 9 thresholds per packet distribution received from the OMC-R, The 10 values per packet distribution, The distribution suspected flag per cell indicating whether or not at least one threshold of the packet distribution has changed during the PM reporting period. From the distribution suspected flag, NPA shall derive a reliability indicator defined per cell and indicating whether or not the packet distribution or its consolidation is suspected. A packet distribution or its consolidation is suspected: if the packet distribution has its distribution suspected flag set in the PM report, or if its consolidation contains at least one PM report for which the distribution suspected flag has changed during the period considered for the consolidation, or, if a PM report is missing to compute the packet distribution. Contrarily to RMS feature, no standard indicator needs to be derived based on the reported distributions. The foreseen distributions are described in Section 3.2.4. ,PSURYHPHQW &RQVROLGDWLRQ RI FHOO LQGLFDWRUV DW *38 OHYHO
The tool chain shall offer to operators the possibility to consolidate at GPU level cell indicators using P105c/d/e/f/g/h/ cell countersP105c/d/e/f/g/h/ cell indicators at GPU level. NPA is in charge of this new consolidation.
,PSURYHPHQW &RXQWHUV GHILQHG DW 75; OHYHO
The proposed TRX counters are described in Section 3.2.4. NPA is in charge of performing the cell aggregation on fly for these TRX counters. For the TRX to cell aggregation, the counters and the indicators are managed by NPA in the same way as for the TRX to cell aggregation used for BSC Type 110 counters. It means that counters will be stored on the source object (i.e. the TRX) and the indicators will be stored at TRX and cell levels. ,PSURYHPHQW 1HZ 0)6 FRXQWHUV
The proposed new counters are described in Section 3.2.4. 7HOHFRP 6SHFLILFDWLRQ LPSDFWV This section describes the main changes in the existing Alcatel BSS telecom specifications.
ED 01 RELEASED
0613_01.doc 22/04/2004

6WHS 6WHS 0)6 FRXQWHUV FDWDORJXH
,PSURYHPHQW 6XSSRUW RI GLVWULEXWLRQV
In the MFS counters catalogue, it is proposed to create a new type of counters called distributions. Only the main definition will be given in the database. The 10 values of the distribution will be generated automatically by specific MFS and NPA tools. A new section will be written in the header document of the MFS counters catalogue to describe the principles of packet distributions. ,PSURYHPHQW &RQVROLGDWLRQ RI FHOO LQGLFDWRUV DW *38 OHYHO
No impact ,PSURYHPHQW &RXQWHUV GHILQHG DW 75; OHYHO
See Section 3.2.5. ,PSURYHPHQW 1HZ 0)6 FRXQWHUV
See Section 3.2.5. ,QWHUIDFHV This section gives the details of the signalling changes on the various interfaces connected to the BSS. 20&0)6 LQWHUIDFH The new distribution thresholds shall be provided to the MFS (See Section 3.2.1). 51220& LQWHUIDFH The new distribution thresholds shall be provided to RNO on a per BSC basis. (See Section 3.2.1).

2SHUDWLRQ DQG PDLQWHQDQFH

20&5 SDUDPHWHUV ,PSURYHPHQW 6XSSRUW RI GLVWULEXWLRQV
The following new O&M parameters are defined at the OMC-R:
Qhhrrhr
PD_UL_TBF_DURA TION_THR_k
9rsvvv
Set of thresholds used to tune the distribution of UL TBF duration
Ti r
MFS
Dhpr
BSS
8hrt Ur PH8S hppr

Changeable List of 9 thresholds
Shtr qrshy hyr

0.5 16 383.5 (in s) Accuracy of 0.5 s 0.5 16 383.5 (in s) Accuracy of 0.5 s 1-99 999 999 (in bytes) Accuracy
PD_DL_TBF_DURA TION_THR_k
Set of thresholds used to tune the distribution of DL TBF duration
MFS
BSS
Changeable
List of 9 thresholds
PD_UL_TBF_VOLU ME_THR_k
Set of thresholds used to tune the distribution of LLC volume carried by an UL TBF
MFS
BSS
Changeable
1 2
The valid options are: Site (CAE), Network (CDE), System (CST), Not Used (NU) The valid options are: changeable, set by create, displayed, OMC local display, Virtual changeable, Virtual displayed. 3 The valid options are: abstract, flag, list of numbers, number, reference, threshold, timer. ED 01 RELEASED
0613_01.doc 22/04/2004
of 1 byte (See Note 1) 1-99 999 999 (in bytes) Accuracy of 1 byte (See Note 1) 0.1-4.9 Accuracy of 0.1 0-50.1-4.9
PD_DL_TBF_VOLU ME_THR_k
Set of thresholds used to tune the distribution of LLC volume carried by a DL TBF
MFS
BSS
Changeable
PD_UL_PDCH_UNI T_ALLOC_THR_k
Set of thresholds used to tune the distribution of nb of PDCH units allocated to a MS in UL Set of thresholds used to tune the distribution of nb of PDCH units allocated to a MS in DL
MFS
BSS
Changeable
PD_DL_PDCH_UNI T_ALLOC_THR_k
MFS
BSS
Changeable
Accuracy of 0.1 Note (1): The max value of thresholds PD_UL_TBF_VOLUME_THR_k and PD_DL_TBF_VOLUME_THR_k is computed and rounded down to 100 000 000 bytes assuming that the MS is assigned 5 TS and that all radio blocks are encoded in MCS-9: 5 x 59.2 kbit/s x 3600 = 1 065 600 kbit = 133 200 kbytes Note (2): In the notation PD_x_THR_k, k is an index in the list of thresholds, whereas the term PD_x_THR_ denotes the name of the list of thresholds.
These parameters shall be displayed in a new OMC-R view called Packet distributions. The OMC-R shall check the following mandatory rule for each set of thresholds: PD_x_THR_1 < PD_xTHR_2 < ... < PD_x_THR_9 where x stands for the name of the packet distribution. ,PSURYHPHQW &RQVROLGDWLRQ RI FHOO LQGLFDWRUV DW *38 OHYHO
No impact. ,PSURYHPHQW &RXQWHUV GHILQHG DW 75; OHYHO
No impact. ,PSURYHPHQW 1HZ 0)6 FRXQWHUV
No impact. 0RGHOLVDWLRQ RI 20&5 SDUDPHWHUV
20& *'02 LPSDFWV Each of the parameters PD_x_THR (where x stands for the name of the packet distribution) will be defined as follows: aGprsPdDlPdchUnitAllocThrx aGprsPdDlTbfDurationThrx aGprsPdDlTbfVolumeThrx aGprsPdUlPdchUnitAllocThrx aGprsPdUlTbfDurationThrx aGprsPdUlTbfVolumeThrx where x = 1, 2, ,9 Each new variable as $610RGXOH,QWHJHU9DOXH the following attribute: $775,%87( 6<17$; $J%VV$WWULEXWH
All parameters described in Section 3.2.1 are managed through the ACIE interface (export and import) following the rules specific to critical parameters.
ED 01 RELEASED
0613_01.doc 22/04/2004
20&%6& LQWHUIDFH LPSDFWV No impact. 20&0)6 LQWHUIDFH LPSDFWV All parameters described in Section 3.2.1 are managed for the aGprsBssFunction object of B9 release. It means that the values of the parameters will be sent by the OMC to the MFS only if the MFS is B9, irrespective of the RNL objects release (B8 or B9). According to the rules used to handle the critical parameters, if the corresponding RNL object release is B8, the OMC will send the migration values. If the RNL objects release is B9, the OMC will send the actual values as they are set by the user.

2WKHU SDUDPHWHUV ,PSURYHPHQW 6XSSRUW RI GLVWULEXWLRQV
No impact. ,PSURYHPHQW &RQVROLGDWLRQ RI FHOO LQGLFDWRUV DW *38 OHYHO
No impact. ,PSURYHPHQW 1HZ 0)6 FRXQWHUV
The following existing O&M parameters are modified:
Qhhrrhr
T_WAIT_FLUSH
9rsvvv Uvr vvt ur rprv s h Ayu rhtr h BQST rqrhtrsurur ryrhrsurtvtU7A
Ti r
MFS
Dhpr
MFS
8hrt Ur PH8S hppr

System (CST) / None (DLS) Timer
Shtr qrshy hyr

1-16 (in s) Accuracy of 0.5 s
Note: The modifications are indicated in bold in the table above.
%6& 30 FRXQWHUV No impact 0)6 30 FRXQWHUV ,PSURYHPHQW 6XSSRUW RI GLVWULEXWLRQV
The following distributions are created:
8r ir
P453a P453b P454a
4 5
Hrvp
DISTRIB_UL_TBF_DUR ATION DISTRIB_DL_TBF_DUR ATION DISTRIB_UL_TBF_VOLU
9rsvvv
Distribution of the UL TBF duration (expressed in s with an accuracy of 50 ms) Distribution of the DL TBF duration (expressed in s with an accuracy of 50 ms) Distribution of the LLC volume (expressed in kbyte with an
Hrhrq iwrp
Cell Cell Cell
The valid options are: Site (CAE), Network (CDE), System (CST), Not Used (NU) The valid options are: changeable, set by create, displayed, OMC local display, Virtual changeable, Virtual displayed. 6 The valid options are: abstract, flag, list of numbers, number, reference, threshold, timer. ED 01 RELEASED
0613_01.doc 22/04/2004
8r ir
P454b P455a P455b
Hrvp
ME DISTRIB_DL_TBF_VOLU ME DISTRIB_UL_PDCH_UNI T_ALLOC DISTRIB_DL_PDCH_UNI T_ALLOC
9rsvvv
accuracy of 1 byte) carried by an UL TBF (in RLC ack mode only) Distribution of the LLC volume (expressed in kbyte with an accuracy of 1 byte) carried by a DL TBF (in RLC ack mode only) Distribution of the number of PDCH units assigned to an UL TBF(computed with an accuracy of 0.001) Distribution of the number of PDCH units assigned to a DL TBF(computed with an accuracy of 0.001)
Hrhrq iwrp
Cell Cell Cell
P453a and P453b Only the active phase of the TBFs (i.e. when the TBF is not in delayed release phase) is counted in distributions P453a and P453b. P454a and P454b Only the LLC volumes exchanged in RLC acknowledged mode are counted in distributions P454a and P454b. P455a and P455b Distributions P455a and P455b are defined per TBF (one distribution per direction) and measure the number of PDCH units assigned to the MS in the corresponding direction at the release of the UL or DL TBFs. Distributions P455a and P455b are using the PDCH unit concept. An UL/DL PDCH unit represents the percentage of the PDCHs that is used by the assigned UL/DL TBF. For instance, if n UL/DL TBFs are established on a given PDCH, the UL/DL PDCH unit assigned to each UL/DL TBF on that PDCH is equal to 1/n (See Figure 2). Distribution P455a is computed at the release of each UL TBF (i.e. on receipt of the release indication received from the RLC layer). Distribution P454b is computed at the release of each DL TBF (i.e. at the expiry of timer T3192). Note that the definition of P455a and P455bmay need to be changed to consider the impacts of the feature Support of QoS in the BSS [ 10].
1 Timeslot
0.5 0.5
0.5 0.5
"
0.5 0.5
0.5 0.5
0.5 0.5
&
TBF 1 TBF 2 TBF 3 TBF 4
Sum of DL PDCH unit for TBF 1= 0.5 + 0.5 + 1 + 0.5 = 2.5 Sum of DL PDCH unit for TBF 2 = 1 + 1 + 0.5 + 0.5 = 3 Sum of DL PDCH unit for TBF 3 = 0.5 + 0.5 + 0.5 = 1.5 Sum of DL PDCH unit for TBF 4 = 0.5 + 0.5 = 1
)LJXUH ([DPSOH RI FRPSXWDWLRQ RI '/ 3'&+ XQLWV DW D JLYHQ WLPH
,PSURYHPHQW &RQVROLGDWLRQ RI FHOO LQGLFDWRUV DW *38 OHYHO
The new type of counters defined at TRX level is introduced. The following counters are proposed to be defined at TRX level:
8r ir
P_TRX_1
Hrvp
CUMULATED_TIME_PD
9rsvvv
Cumulated time during which a PDCH is used by a DL or UL TBF
Hrhrq iwrp
TRX
ED 01 RELEASED
0613_01.doc 22/04/2004
8r ir
P_TRX_2
Hrvp
9rsvvv
Hrhrq iwrp
TRX TRX TRX
CH_USED_TRX on the concerned TRX MAX_NB_PDCH_USED_ Maximum number of PDCHs used by a DL or UL TBF on the TRX concerned TRX P_TRX_3 CUMULATED_TIME_BU Cumulated time during which a GCH is used on the concerned SY_GCH_TRX TRX P_TRX_4 MAX_NB_BUSY_GCH_T Maximum number of GCHs used on the concerned TRX RX Note (*): The exact reference will be given when integrating the counters in the MFS counters catalogue.
,PSURYHPHQW 1HZ 0)6 FRXQWHUV
The following counters are proposed to be introduced:
8r ir
P38f
Hrvp
CUMULATED_TIME_PD CH_USED_UL_CELL
9rsvvv
Cumulated time during which a PDCH is used by at least one UL TBF
Hrhrq iwrp
Cell Accuracy 50 ms Cell Accuracy 50 ms Cell Accuracy 50 ms Cell Accuracy 50 ms Cell Accuracy 50 ms Cell Cell of
P38e
CUMULATED_TIME_PD CH_USED_DL_CELL
Cumulated time during which a PDCH is used by at least one DL TBF
of
P451a
CUMULATED_TIME_PD CH_UL_TBF_CELL
Cumulated time during which an UL TBF uses one PDCH
of
P451b
CUMULATED_TIME_PD CH_DL_TBF_CELL
Cumulated time during which a DL TBF uses one PDCH
of
P452
CUMULATED_TIME_PD CH_DL_TBF_GMM_SIG_ CELL
Cumulated time during which a DL TBF established for GMM signalling purposes uses a PDCH
of
P98f NB_SUSP_UL_TBF_REL Number of UL TBF releases due to the suspend procedure P98e NB_SUSP_DL_TBF_REL Number of DL TBF releases due to the suspend procedure Note (*): The exact reference will be given when integrating the counters in the MFS counters catalogue.
P38f Counter P38f is used to estimate the time during which a PDCH is used by at least one UL TBF (cumulated over all the PDCHs available in the cell). An example of computation is given in Figure 3. Note that the counter shall consider the resource allocation changes that occur further to a UL TBF re-allocation. P38e Equivalent to P38f but for the DL direction. The delayed release phase of the DL TBF is also taken into account. P451a Counter P451a is used to estimate the time during which an UL TBF uses one PDCH (cumulated over all the PDCHs used by the UL TBF and over all the UL TBFs operating in the cell). An example of computation is given in Figure 3. Note that the counter shall consider the resource allocation changes that occur further to a UL TBF re-allocation. P451b Identical to P451a but for the DL direction. The delayed release phase of the DL TBF is also taken into account.
P452
ED 01 RELEASED
0613_01.doc 22/04/2004
For a given DL TBF, Counter P452 is started at the establishment of the DL TBFs established to carry GMM signalling traffic to the MS. It is stopped at the end of the active phase of the DL TBF or on receipt of a DL LLC PDU without the T-bit set.
P98e and P98f In release B8, Counters P98a and P98b evaluate the number of UL/DL TBF releases due to the suspension procedure while the TBFs are still on-going on receipt of the Suspend message from the BSC. However, the TBFs may be released by RLC layer before the receipt of the Suspend message. In order to cover all cases, Counters P98a and P98b are replaced by Counters P98e and P98f. These two new counters are incremented in the two following cases: a Suspend message is received from BSC and the suspend procedure concerns a UL/DL TBF which is still on-going, or, a Suspend message is received from BSC and the suspend procedure concerns a UL/DL TBF which has been abnormally released in the previous T_WAIT_FLUSH seconds. The principles introduced to evaluate the number of UL/DL TBF releases due to a cell reselection (via P34a/b/c/d) are re-used here. The following counters shall be removed:
8r ir
P98a P98b
Hrvp
NB_DL_TBF_REL_SUSP NB_UL_TBF_REL_SUSP
9rsvvv
Number of DL TBF releases due to a suspension from MS. Number of UL TBF releases due to a suspension from MS.
Hrhrq iwrp
Cell Cell

30 LQGLFDWRUV ,PSURYHPHQW 6XSSRUW RI GLVWULEXWLRQV
Each new distribution shall lead to the definition of a PM indicator. ,PSURYHPHQW &RQVROLGDWLRQ RI FHOO LQGLFDWRUV DW *38 OHYHO
No impact ,PSURYHPHQW &RXQWHUV GHILQHG DW 75; OHYHO
The new type of indicators defined at TRX level is introduced. The following new indicators are proposed at TRX level:
Hrvp
9rsvvv
PDCH_TRAFFIC_TRX
PDCH traffic expressed in Erlang on the concerned TRX Formulae: CUMULATED_TIME_PDCH_USED_TRX/3600 GCH traffic expressed in Erlang on the concerned TRX Formulae: CUMULATED_TIME_BUSY_GCH_TRX/3600
GCH_TRAFFIC_TRX
In addition to those indicators, any new counter leads as usual to the creation of a new indicator. ,PSURYHPHQW 1HZ 0)6 FRXQWHUV
The following new indicators are proposed:
Hrvp
UL_OVERLAPPING_FACTOR
9rsvvv
Overlapping factor in the UL direction. This indicator gives a measure of the number of UL TBFs piled up on a PDCH
ED 01 RELEASED
0613_01.doc 22/04/2004
Hrvp
DL_OVERLAPPING_FACTOR
9rsvvv
Formulae: P451a / P38f = CUMULATED_TIME_PDCH_UL_TBF_CELL /CUMULATED_TIME_PDCH_USED_UL_CELL (See also Figure 3) Overlapping factor in the DL direction. This indicator gives a measure of the number of DL TBFs piled up on a PDCH Formulae: P451b / P38e = CUMULATED_TIME_PDCH_DL_TBF_CELL /CUMULATED_TIME_PDCH_USED_DL_CELL (See also Figure 3 for UL direction) Percentage of radio resources used for GMM signalling purposes P452 / P451b = CUMULATED_TIME_PDCH_DL_TBF_GMM_SIG_CELL / CUMULATED_TIME_PDCH_DL_TBF_CELL
GMM_SIG_USAGE_RATIO
0.5 0.5 Timeslot
0.5 0.5
0.5 0.5
0.5 0.5
"
&
TBF 1 TBF 2
Sum of UL PDCH unit for TBF 1= 0.5 + 0.5 + 0.5 + 0.5 = 2 Sum of UL PDCH unit for TBF 2 = 0.5 + 0.5 + 0.5 + 0.5 = 2
CUMULATED_TIME_PDCH_UL_TBF_CELL for TBFs 1 and 2 = 4 x T CUMULATED_TIME_PDCH_UL_TBF_CELL = 2 x (4 x T) = 8 x T CUMULATED_TIME_PDCH_USED_UL_CELL for PDCHs 1, 2, 3 and 4 = T CUMULATED_TIME_PDCH_USED_UL_CELL = 4 x T UL_OVERLAPPING_FACTOR = (8 x T) / (4 x T) = 2 (a)
1 Timeslot
0.5 0.5
0.5 0.5
"
&
TBF 1 TBF 2
Sum of UL PDCH unit for TBF 1= 0.5 + 0.5 + 1 + 1 = 3 Sum of UL PDCH unit for TBF 2 = 1 + 1 + 0.5 + 0.5 = 3
CUMULATED_TIME_PDCH_UL_TBF_CELL for TBFs 1 and 2 = 4 x T CUMULATED_TIME_PDCH_UL_TBF_CELL = 2 x (4 x T) = 8 x T CUMULATED_TIME_PDCH_USED_UL_CELL for PDCHs 1, 2, 3, 4, 5 and 6 = T CUMULATED_TIME_PDCH_USED_UL_CELL = 6 x T UL_OVERLAPPING_FACTOR = (8 x T) / (6 x T) = 4/3 = 1.33
(b) )LJXUH ([DPSOH RI 8/B29(5/$33,1*B)$&725 FRPSXWDWLRQ IRU D JLYHQ SHULRG RI 7 VHFRQGV In addition to those indicators, any new counter leads as usual to the creation of a new indicator. 0LJUDWLRQ
20& 0LJUDWLRQ In OMC all the parameters PD_x_THR (THR (where x stands for the name of the packet distribution) will be initialized with their default values for the B8 BSC instances. %6& 0LJUDWLRQ The BSC migration is not concerned with the parameters PD_x_THR (where x stands for the name of the packet distribution), but if a BSC migrates from B8 to B9, the consequence for the OMC is that these parameters become editable.
ED 01 RELEASED
0613_01.doc 22/04/2004
0)6 PLJUDWLRQ The migration is performed in two steps: - On MFS side: The MFS initializes the PD_x_THR (where x stands for the name of the packet distribution) parameters to 0 - On OMC side: the operator forces a resynchronization and consequently, the migration values of the parameters are sent by the OMC to the MFS. 2SHUDWRU FRQVWUDLQWV DIWHU %!% PLJUDWLRQ No special issue on this topic. -DYD VFULSWV No impact )DXOW 0DQDJHPHQW No impact 2 0 6SHFLILFDWLRQ LPSDFWV This section describes the main changes in the existing Alcatel BSS O&M specifications, and the new specifications to be planned when applicable. 6WHS %66 LQGLFDWRUV See Section 3.2.6 6WHS /RJLFDO FRQILJXUDWLRQ PDQDJHPHQW /&0 LCM specification has to be updated with the information defined in the SFD. 6WHS 0)620& LQWHUIDFH *'02 MFS/OMC Interface GDMO specification has to be updated with information defined in the SFD. 6WHS *356 30 ILOH IRUPDW Inclusion of the GPU configuration suspected flag (defined per GPU). Renaming of the existing suspected flag (defined per cell). The new name is Cell Configuration Suspected Flag. Inclusion of the distribution suspected flag (defined per cell). Inclusion of the packet distribution thresholds (defined per BSS cell). Inclusion of the packet distribution vectors, i.e. list of packet distribution counters (defined per cell). Note: A new format needs to be defined in B9 for classical GPRS counters due to the B8 limitation.

9DOLGDWLRQ
See B9 validation plan

)LHOG SURFHGXUH GHVLJQ
This section describes the impacts on the development and writing of Field Procedure Designs (FPD): No new document is needed: No impact is foreseen on existing B8 FPD documents:

*HQHULF &XVWRPHU GRFXPHQWDWLRQ
This section describes the impacts on the Generic Customer Documentation (GCD): No new documents is needed: The following B8 GCD documents are impacted:
9prUvyr
O&M PARAMETERS Dictionary
7'6IWIir
"7F!'$"6666Q8aa6
Dhp
editorial: 6 parameters to be added
ED 01 RELEASED
0613_01.doc 22/04/2004
9prUvyr
PM counters
7'6IWIir
"7F!'$$6666Q8aa6 "7F!'"!6666URaa6
Dhp
editorial: 6 distribution counters, 7 new MFS counters and 4 counters at TRX level to be added editorial: update of the Performance Management paragraph in the MFS O&M Functions chapter (introduction) taking into account the distribution counters editorial: update of the Performance Monitoring and Performance Management chapters taking into account the distribution counters editorial: update of the GPRS Performance Management Counters chapter taking into account the distribution counters minor: Update of the Logical Configuration Management Windows chapter to introduce the new OMC-R view called Packet Distribution editorial: update of the Performance Management chapter (introduction) taking into account the distribution counters
EVOLIUM A9135 MFS Description
BSS System Description
"7F!'!!6666URaa6 "7F!'$#6666Q8aa6 "7F!'#6666Q8aa6 "7F!'%6666Q8aa6
Operating & Maintenance Principles
A1353-RA OLH
BSS Surveillance Handbook
1RWH The O&M PARAMETERS Dictionary and PM counters documents are extracted from Access Databases. SED capital gain is the generation of these documents.

(QJLQHHULQJ UXOHV
This section describes the impacts on the engineering rules: No new document is needed No impact is foreseen on existing Engineering documents.
ED 01 RELEASED
0613_01.doc 22/04/2004

68%6<67(0 ,03$&76 %76 %6& 7UDQVFRGHU 0)6 20&5
This section identifies precisely the impacts for each subsystem.
No impact
No impact
No impact
See Section 3.1.
Additional O&M information (valid except otherwise indicated for the whole Section 3.2.1): All parameters defined in Section 3.2.1 are considered as 0)6 % FULWLFDO SDUDPHWHUV All parameters can be modified from both PRC and SC. All parameters are managed by the ACIE interface for both import and export directions. None of these parameters need to be integrated within the default filters provided by the OMC. For all the parameters the default value is fixed (i.e. not depending on other parameters). +0, LPSDFWV A new thumbnail named Packet Distribution which will contain all the parameters PD_x_THR (where x stands for the name of the packet distribution) should be added within the Edit BSC ---> GPRS screen This thumbnail should be enabled only for the B9 BSCs. Since the parameters will not fit into a single screen, it is proposed to group them into several sub-screens, as follows: A sub-screen labeled TBF duration containing a box UL TBF Duration with the parameter PD_UL_TBF_DURATION_THR and a box DL TBF Duration with the parameter PD_DL_TBF_DURATION_THR A sub-screen labeled LLC volume containing a box LLC volume carried by a UL TBF with the parameter PD_UL_TBF_VOLUME_THR and a box LLC volume carried by a DL TBF with the parameter PD_DL_TBF VOLUME_THR A sub-screen labeled PDCH Usage containing a box PDCH Usage in UL with the parameter PD_UL_PDCH_UNIT_ALLOC_THR and a box PDCH Usage in DL with the parameter PD_DL_PDCH_UNIT_ALLOC _THR It is proposed that the corresponding HMI names of the parameters to be PD_x_THR THR (where x stands for the name of the packet distribution). Each element of the lists PD_x_THR should be edited in a separate edit field. As concerning the displaying of the parameters value, in order to prevent from managing float numbers, the following rules should be applied: The values of PD_UL_TBF_DURATION_THR and PD_DL_TBF_DURATION_THR will be displayed as actual values x 10. The values of PD_UL_PDCH_UNIT_ALLOC_THR PD_DL_PDCH_UNIT_ALLOC_THR will be displayed as actual values x 100. The rest of the parameters will be displayed as they are.
ED 01 RELEASED
0613_01.doc 22/04/2004
Note: the rules above concern only the HMI. Inside RNIM and on the OMC-MFS interface, the coded values will be used. The HMI should turn red if during the editing the mandatory rule stated in Section 3.2.1is violated. 20& PRGHOL]DWLRQ See Section 3.2.2. 2SWLRQDO IHDWXUH There are no optional features involved. 2YHUYLHZ RI WKH LPSDFW XSRQ 20& VSHFV The following parts of the DFS LCM are impacted: MF-Set BSC GPRS/LCS/UMTS Telecom Parameters: the parameters PD_x_THR (where x stands for the name of the packet distribution must be added to the inputs list for MFS-side only. They have to be surrounded by If the Counters improvement feature is supported by the aim BSC Endif tags. the RNL error cases should be updated so as to take into account the mandatory rule stated in Section 3.2.1. Chapter 5.2: the release-features mapping table.

/$6(5 13$
No impact
Introduction of new counters/indicators for CELL object inside the GPRS PM files. The distribution counters will be stored in the cell block named 'LVW&HOO, inside the GPRS PM file and will be treated as usual GPRS counters. In addition, they cant be used to flexible indicators (due to the check on the formulas done when a flexible indicator is created is checked that all counters within the formula are present in the cell GPRS counter table). Among with the distribution counters, a new distribution suspected flag DSF (managed as an ordinary SF by NPA block is rejected in case the DSF is 1) will be created to specify if the thresholds have been changed. DSF will be used further in a reliability indicator formula. So the DistCell block will be rejected by NPA GPRS parser in the following cases: - SF 1, DSF 0 - SF 0, DSF 1 - SF 1, DSF 1 Distribution counters wont be created as columns in the NPA database and wont be loaded, as distribution counters have no mean alone. The distribution counters will be used to create only new indicators in NPA database. This information for the counters will be received from the BSC/MFS counters Access databases new column to be added in the export. These indicators wont be consolidated weekly and monthly and to Network level. The spatial aggregation will be only CELL - BSC. Since they need specific temporal and spatial aggregation, a new group will be created. See Improvement 2 for details about the aggregation CELL-GPU. Obsynt tool is impacted. Only new counters/indicators added for CELL and GPU in the MFS files in the existing blocks. In NPA these new indicators should be treated as the normal indicators (not like the RMS ones) so nothing special to be done for the parsing/loading of the indicators.
ED 01 RELEASED
0613_01.doc 22/04/2004
The distribution counters will be stored in a separate cell block inside the GPRS PM file so the GPRS parser, obsynt tool are impacted. Also they cant be used to flexible indicators due Metrica restriction (not possible to load a indicator having the loadmap formula from 2 different blocks). Among with the distribution counters a new suspected flag (managed as an ordinary counter by NPA) will be created to specify if the threshold have been changed. This distribution suspected flag will be used to compute an reliability indicator for the distributions. The distribution counters wont be created as columns in the NPA database and wont loaded in NPA and MPM because the distribution counters have no mean alone and in order to decrease the NPA database dimensioning. This information for the counters should be received from the MFS counters Access database new column to be added in the export. These indicators wont be consolidated weekly and monthly and to Network level (See Section 3.1.1) and to do that it is necessary to create a new group that will configure the special temporal and spatial aggregations. ,PSURYHPHQW &RQVROLGDWLRQ RI FHOO LQGLFDWRUV DW *38 OHYHO
Till B8 the object hierarchy for CELL was CELL BSC NET. The aggregation from CELL to GPU means that the B9 branch will be CELL GPU BSC NET. To allow this special spatial consolidation a new group will be created in NPA. In case the CELL change the GPU during a reporting period, the BSC block (per GPU) will have a new SF called GCSF will be set to 1. The BSC block wont be rejected by GPRS parser in case GCSF is 1. GCSF will be used further in a GPU reliability indicator formula. GPRS parser will be updated in order to reject the BSC block in the following cases: -SF 1, GCSF 0 -SF 1, GCSF 1 The migration is impacted because the CELL GPRS counters/indicators tables are already existing in B8 so the tables will be migrated to B9 in counters/indicators/hierarchy tables where the GPUID will be filled by default with not_avail for the B8 data. Also B9 cell with only GSM data will remain with not_avail GPU parent. The CELL GPRS flexible indicators wont be aggregated at GPU level and will remain as in B8 CELL - BSC - NET. To allow this special spatial consolidation a new group will be created in NPA. In case the CELL change the GPU during a reporting period the block for CELL will be have the CCSF true and the block will be rejected by GPRS parser (same behavior as in B7 and B8). The GPU change for a cell will be specified by a new counters inserted in the GPU (sub BSS ) block from the GPRS PM file, counter that will be later used as an reliability indicator. The migration is impacted because the counters are already existing in B9 so the tables should be migrated to B9 in counters/indicators/hierarchy tables where the GPU id will be filed by default with not_avail for the B8 data. The CELL GPRS flexible indicators wont be aggregated at GPU level and will remain as in B8 CELL - BSC - NET. ,PSURYHPHQW &RXQWHUV GHILQHG DW 75; OHYHO
A new block will be introduced in the B9 MFS PM files so, the B9 GPRS PM parser and the obsynt tool needs to be modified. On the fly aggregation needed from TRX object (Trx GPRS block) to CELL object (Cell GPRS block) level during the parsing phase, similar to whats done with TRX data coming from PM 110. The TRX indicator tables wont be spatially aggregated to CELL, as it is for CELL 110. This feature has an impact on performances and will imply a specific treatment during L&S campaign, NPA traffic model preparation. The GPRS CELL flexible wont use the new TRX on the fly aggregated to CELL counters. Till now there was no TRX counter in the MFS PM files so the GPRS parser and the obsynt tool should be modified to take into account the new block. The GPRS parser should be modified to make the on-the-fly
ED 01 RELEASED
0613_01.doc 22/04/2004
aggregation from TRX to CELL, in the same way as for the on the fly aggregation from TRX to CELL in the 110 files. This will have an impact on the GPRS performance and should be followed during the L&S test because the GPRS files are coming by MFS and during the fly-aggregation all the file should be kept in memory. The TRX indicator tables wont be spatially aggregated to CELL, same as for CELL 110. The GPRS CELL flexible wont use the new TRX on the fly aggregated to CELL counters. ,PSURYHPHQW 1HZ 0)6 FRXQWHUV
Only new counters/indicators to be added. No specific development foreseen.

512
This SFD implies the following impacts on RNO:
This implies the following impact on the RNO: Extension of RNO features in both cases: Hour access for vectors, matrices, mono distributed reports (impacts the RNO daemon), Main hypothesis that there will not be stored vectors by hour Introduces reliability on vectors and matrices (to be based on standard indicators and with a display in tabular view as it is done already today in other reports); New thresholds (4 lists of 4 thresholds) to be tuneable in the RNO. Main hypothesis is: Same thresholds will be used for all BSCs (BSCs B9 only); The RNO is master (like for RMS templates) and will not update the list of thresholds when import OMC logical parameters. A specific new tool (integrated in the RNO Administration toolbar) shall be developed for (like for the RMS template manager, modification possible by the administrator, reading for other users). In terms of configuration data: 6 lists of 9 thresholds (PDx_THR_1 < PDxTHR_2 < ... < PDx_THR_9 ): Note: The RNO will not allow to have equal thresholds inside a list (not allowed today for the RMS); More generally, it brings specific configuration data in the RNO. One can mention that in the RMS case, it was very difficult to stabilise.
It is not foreseen new functions on matrices and vectors (only usage of the ones already available for the RMS). However, current UDFs functions provided by the NPA shall not be usable per hour. Finally, this feature has a serious impact on performances and will imply a specific treatment in case of L&S and RNO traffic model preparation. ,PSURYHPHQW &RQVROLGDWLRQ RI FHOO LQGLFDWRUV DW *38 OHYHO
Reports (vectors/matrices) shall be introduced on GPUs (non RNO objects). A configuration data impact is also foreseen particularly for reliability aspects. ,PSURYHPHQW &RXQWHUV GHILQHG DW 75; OHYHO
Only impact on configuration data is foreseen. Finally, this feature has an impact on performances and will imply a specific treatment in case of L&S and RNO traffic model preparation.
ED 01 RELEASED
0613_01.doc 22/04/2004
,PSURYHPHQW 1HZ 0)6 FRXQWHUV
Only impact on configuration data is foreseen.

3ROR
No impact
2()
No impact
ED 01 RELEASED
0613_01.doc 22/04/2004

3(5)250$1&( 7UDIILF PRGHO 3HUIRUPDQFH /RDG FRQVWUDLQWV
6<67(0 ',0(16,21,1*
The new counters and distributions should allow us to improve the existing (E)GPRS traffic model.
No impact on Telecom performance is expected.
The PMU load may be slightly increased by the introduction of the new counters and distributions.
ED 01 RELEASED
0613_01.doc 22/04/2004
None
ED 01 RELEASED
0613_01.doc 22/04/2004
23(1 32,176
COUNTER IMPROVEMENTS FOR RELEASE B9
3BK 10204 0613 DTZZA 30/34
(TXLSPHQWV BTS
,03$&76 6800$5<
BSC MFS X TC OMC-R X LASER MPM/NPA X RNO X OEF Polo
,QWHUIDFHV Telecom Radio Abis O&M Abis-O&M
Ater
BTS-TC
MFS-BTS
MFS-BSC
Gb
BSC-O&M
TC-O&M
MFS-O&M X
Q3
/LVW RI ,PSDFWHG 7HOHFRP 6WHS The following Telecom Step 02 documents are impacted: MFS counters catalogue GPRS load and performance objectives. /LVW RI ,PSDFWHG 2 0 6WHS The following O&M Step 02 documents are impacted: BSS indicators catalogue Logical configuration management MFS/OMC interface GDMO GPRS PM file format
ED 01 RELEASED
0613_01.doc 22/04/2004

*/266$5< $EEUHYLDWLRQV
Cell Configuration Suspected Flag Distribution Suspected Flag GPU Configuration Suspected Flag Packet Distribution Radio Measurement Statistics Suspected Flag User defined functions
CCSF DSF GCSF PD RMS SF UDF

'/ 3'&+ XQLW A DL PDCH unit is defined as a unit of DL radio transmission on a PDCH. If n DL TBFs are using a given PDCH, the DL PDCH unit assigned to each TBF is 1/n on that PDCH. 8/ 3'&+ XQLW An UL PDCH unit is defined as a unit of UL radio transmission on a PDCH. If n UL TBFs are using a given PDCH, the UL PDCH unit assigned to each TBF is 1/n on that PDCH. *356 VHVVLRQ A GPRS session corresponds to the period during which the MS is in packet transfer mode. When involved in a GPRS session, the MS has always at least one UL or DL TBF established. *38 FRQILJXUDWLRQ VXVSHFWHG IODJ *&6) This flag is reported by the MFS in PM report related to a given GPU. It indicates to NPA whether a cell has been created or removed on the GPU during the PM reporting period (e.g. further to a re-mapping of the cells on the GPU). &HOO FRQILJXUDWLRQ V6XVSHFWHG IODJ &&6) This flag is reported by the MFS in PM report related to a given cell. It indicates to NPA whether a cell has been created on the GPU during the PM reporting period (e.g. further to a re-mapping of the cells on the GPU). 'LVWULEXWLRQ VXVSHFWHG IODJ '6) This flag is reported by the MFS in PM report related to a given cell. It indicates to NPA whether or not at least one of the packet distribution thresholds has been modified during the PM reporting period (e.g. further to an O&M change).
7HUPLQRORJ\
ED 01 RELEASED
0613_01.doc 22/04/2004
$11(; $ 0$,1 ',))(5(1&(6 %(7:((1 5$',2 0($685(0(17 67$7,67,&6 $1' 3$&.(7 ',675,%87,216
Apv Shqv Hrhrr Thvvp
10 (usually) 9 Up to 23 h By an RMS job X
Table 4 highlights the main differences between the feature Radio Measurements Statistics introduced in release B7 and the packet distributions presented in this SFD.
Qhpxr 9vviv
10 9 1h Always X
8r
RMS also supports matrixes. For RMS, the min and max values of the vector are set by system parameters. The packet distributions are always activated. Not required for packet distributions since they are all defined at cell level.
Number of values per vector or distribution Number of thresholds per vector or distribution Period of reporting Activation of the vector or distribution reporting Spatial consolidation per cell Spatial consolidation per BSS Spatial consolidation per GPU Spatial consolidation per network
Not defined for packet distributions since no reliability indicator is today defined at network level
Temporal consolidation per day Temporal consolidation per week Temporal consolidation per month Standard indicators derived based on the reported distributions/vectors Reliability indicators PM reporting Storage in NPA
X In RMS job 15 days
X X Available per cell (not per distribution) in order to decrease NPA capacity.
In PM files As a normal counterindicat or User defined functions (UDF) X X Not available per hour for distributions Note: X means the function is supported, whereas means that the function is not supported.
7DEOH 0DLQ GLIIHUHQFHV EHWZHHQ UDGLR PHDVXUHPHQW VWDWLVWLFV DQG SDFNHW GLVWULEXWLRQV
ED 01 RELEASED
0613_01.doc 22/04/2004
$11(; % ,03$&76 21 13$ &$3$&,7<

Table 5 shows the impacts of the sub-features described in this SFD on NPA capacity. 6XEIHDWXUHV 1XPEHU RI FRXQWHUVWKUHVKROGV UHTXLUHG &RPPHQWV
Support of distributions Thresholds 9 x 6 = 54 Per cell Counters 10 x 6 = 60 Per cell Reliability indicators 6 Per cell 7RWDO 3HU FHOO Consolidation of cell indicators at GPU level Counters 6 Per GPU Reliability indicators 1 Per GPU Counters defined at TRX level 4 Per TRX (not implemented in B9) New MFS counters 7 Per cell 7DEOH ,PSDFWV RI WKH VXEIHDWXUHV RQ 13$ FDSDFLW\
(1' 2) '2&80(17
ED 01 RELEASED
0613_01.doc 22/04/2004

B9 Counter Improved

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

B9 Counter Improved

Hochgeladen von

Copyright:

Verfügbare Formate

All rights reserved.

6LWH VELIZY 2ULJLQDWRUV E. BRIGANT 6\VWHP 6XEV\VWHP 'RFXPHQW &DWHJRU\ : : :

(92/,80 6$6 COUNTER IMPROVEMENTS FOR RELEASE B9

ALCATEL GSM BSS SYS-TLA PRODUCT DEFINITION

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 1/34

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 2/34

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 3/34

   

13$ 512 3ROR 2()

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 4/34

,17(51$/ 5()(5(1&(' '2&80(176

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 5/34

'HILQLWLRQV DQG SUHUHTXLVLWH

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 6/34

2YHUDOO GHVFULSWLRQ RI WKH SURSRVHG VROXWLRQV

'LVWULEXWLRQ RI WKH 7%) GXUDWLRQ

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 7/34

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 8/34

&RPSOLDQFH WR WKH 0DUNHWLQJ 5HTXLUHPHQWV

&RPSOLDQFH WR *33 VWDQGDUG

:RUNLQJ $VVXPSWLRQV 'HSHQGHQFLHV

Sub-feature "Improvement 1: Support of distributions"

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 9/34

Feature Dynamic Abis

Sub-feature ",PSURYHPHQW : 1HZ 0)6 FRXQWHUV "

7T8Brrhv) HAT) Uhvv) Uhpqr) HT8) TBTI) 9hhDXA) CGS) PH)

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 10/34

DISTRIB_DL_TBF_DUR ATION DISTRIB_UL_TBF_VOLU ME

DISTRIB_DL_TBF_VOLU ME DISTRIB_UL_PDCH_UNI T_ALLOC DISTRIB_DL_PDCH_UNI T_ALLOC

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 11/34

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 12/34

6<67(0 ,03$&76 7HOHFRP

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 13/34

,PSURYHPHQW  &RXQWHUV GHILQHG DW 75; OHYHO

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 14/34

6WHS  6WHS  0)6 FRXQWHUV FDWDORJXH

,PSURYHPHQW  6XSSRUW RI GLVWULEXWLRQV

No impact  ,PSURYHPHQW  &RXQWHUV GHILQHG DW 75; OHYHO

See Section 3.2.5.  ,PSURYHPHQW  1HZ 0)6 FRXQWHUV

2SHUDWLRQ DQG PDLQWHQDQFH

The following new O&M parameters are defined at the OMC-R:

8hrt  Ur PH8S hppr

Shtr  qrshy hyr

Set of thresholds used to tune the distribution of DL TBF duration

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 15/34

No impact.  ,PSURYHPHQW  &RXQWHUV GHILQHG DW 75; OHYHO

No impact.  ,PSURYHPHQW  1HZ 0)6 FRXQWHUV

No impact.  0RGHOLVDWLRQ RI 20&5 SDUDPHWHUV

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 16/34

2WKHU SDUDPHWHUV ,PSURYHPHQW  6XSSRUW RI GLVWULEXWLRQV

No impact.  ,PSURYHPHQW  &RQVROLGDWLRQ RI FHOO LQGLFDWRUV DW *38 OHYHO

No impact.  ,PSURYHPHQW  &RXQWHUV GHILQHG DW 75; OHYHO

No impact.  ,PSURYHPHQW  1HZ 0)6 FRXQWHUV

The following existing O&M parameters are modified:

9rsvvv Uvr vvt ur rprv s h Ayu rhtr h BQST rqrhtrsurur ryrhrsurtvtU7A

8hrt  Ur PH8S hppr

Shtr  qrshy hyr

Note: The modifications are indicated in bold in the table above.

The following distributions are created:

COUNTER IMPROVEMENTS FOR RELEASE B9 3BK 10204 0613 DTZZA 17/34

TBF 1 TBF 2 TBF 3 TBF 4

)LJXUH  ([DPSOH RI FRPSXWDWLRQ RI '/ 3'&+ XQLWV DW D JLYHQ WLPH

,PSURYHPHQW  &RQVROLGDWLRQ RI FHOO LQGLFDWRUV DW *38 OHYHO

No impact.  ,PSURYHPHQW  &RXQWHUV GHILQHG DW 75; OHYHO

6LWH VELIZY 2ULJLQDWRUV E. BRIGANT 6\VWHP 6XEV\VWHP 'RFXPHQW &DWHJRU\ : : :

'HILQLWLRQV DQG SUHUHTXLVLWH

&RPSOLDQFH WR *33 VWDQGDUG

Sub-feature ",PSURYHPHQW : 1HZ 0)6 FRXQWHUV "

,PSURYHPHQW &RXQWHUV GHILQHG DW 75; OHYHO

6WHS 6WHS 0)6 FRXQWHUV FDWDORJXH

,PSURYHPHQW 6XSSRUW RI GLVWULEXWLRQV

No impact ,PSURYHPHQW &RXQWHUV GHILQHG DW 75; OHYHO

See Section 3.2.5. ,PSURYHPHQW 1HZ 0)6 FRXQWHUV

8hrt Ur PH8S hppr

Shtr qrshy hyr

No impact. ,PSURYHPHQW &RXQWHUV GHILQHG DW 75; OHYHO

No impact. ,PSURYHPHQW 1HZ 0)6 FRXQWHUV

No impact. 0RGHOLVDWLRQ RI 20&5 SDUDPHWHUV

2WKHU SDUDPHWHUV ,PSURYHPHQW 6XSSRUW RI GLVWULEXWLRQV

No impact. ,PSURYHPHQW &RQVROLGDWLRQ RI FHOO LQGLFDWRUV DW *38 OHYHO

No impact. ,PSURYHPHQW &RXQWHUV GHILQHG DW 75; OHYHO

No impact. ,PSURYHPHQW 1HZ 0)6 FRXQWHUV

9rsvvv Uvr vvt ur rprv s h Ayu rhtr h BQST rqrhtrsurur ryrhrsurtvtU7A

8hrt Ur PH8S hppr

Shtr qrshy hyr

)LJXUH ([DPSOH RI FRPSXWDWLRQ RI '/ 3'&+ XQLWV DW D JLYHQ WLPH

,PSURYHPHQW &RQVROLGDWLRQ RI FHOO LQGLFDWRUV DW *38 OHYHO

No impact. ,PSURYHPHQW &RXQWHUV GHILQHG DW 75; OHYHO

,PSURYHPHQW 1HZ 0)6 FRXQWHUV

30 LQGLFDWRUV ,PSURYHPHQW 6XSSRUW RI GLVWULEXWLRQV

No impact ,PSURYHPHQW &RXQWHUV GHILQHG DW 75; OHYHO

"7F!'!!6666URaa6 "7F!'$#6666Q8aa6 "7F!'#6666Q8aa6 "7F!'%6666Q8aa6

68%6<67(0 ,03$&76 %76 %6& 7UDQVFRGHU 0)6 20&5

,PSURYHPHQW 1HZ 0)6 FRXQWHUV

,QWHUIDFHV Telecom Radio Abis O&M Abis-O&M

$11(; % ,03$&76 21 13$ &$3$&,7<