B9 Counter Improved

7/28/2019 B9 Counter Improved

1/34


2/34

ED 01 RELEASED COUNTER IMPROVEMENTS FOR RELEASE B90613_01.doc22/04/2004 3BK 10204 0613 DTZZA 2/34

Allrightsreserved.

Passingonandcopyingofthis

document,useandcommunicationofitscontents

notpermittedwithoutwrittenauthorizationfromE

volium.

5(9,(:Edition 01Proposal 04

09/121/2003 See review report MND/TD/VAL/SYT/EBR/0380.2003

+,6725


3/34


Allrightsreserved.




volium.

7$%/(2)&217(176

,1752'8&7,21

6FRSH

'RFXPHQW6WUXFWXUH 'HILQLWLRQVDQGSUHUHTXLVLWH

+,*+/(9(/'(6&5,37,21

)XQFWLRQDO5HTXLUHPHQWV

2YHUDOOGHVFULSWLRQRIWKHSURSRVHGVROXWLRQV 2.2.1 Improvement 1: Support of distributions ..................................................................................... 72.2.2 Improvement 2: Consolidation of cell indicators at GPU level .................................................... 82.2.3 Improvement 3: Counters defined at TRX level.......................................................................... 82.2.4 Improvement 4: New MFS counters ........................................................................................... 9

&RPSOLDQFHWRWKH0DUNHWLQJ5HTXLUHPHQWV

&RPSOLDQFHWR*33VWDQGDUG

:RUNLQJ$VVXPSWLRQV

'HSHQGHQFLHV

+:&RYHUDJH

'HFLVLRQFULWHULD 2.8.1 Standardisation......................................................................................................................... 112.8.2 Competition............................................................................................................................... 112.8.3 Customer .................................................................................................................................. 112.8.4 Gains......................................................................................................................................... 112.8.5 Risks ......................................................................................................................................... 11

6


4/34


Allrightsreserved.




volium.

13$

512

3ROR

2()

3(5)250$1&(6


5/34


Allrightsreserved.




volium.

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

5()(5(1&(''2&80(176$OFDWHOUHIHUHQFHV

[ 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

*33UHIHUHQFHV[ 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$OFDWHOGRFXPHQWV[ 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&5VNone

35()$&(This document is the input paper for the feature COUNTER IMPROVEMENTS FOR RELEASE B9 insideTD. It will further on be used as reference for the development of that feature in each subsystem.


6/34


Allrightsreserved.




volium.

,1752'8&7,21

6FRSHThe present document aims to be the basis for decision of a proposed change to be made on the BSSsystem. It provides all necessary information related to functional description, gains, description of the systemimpacts and subsystem impacts.

'RFXPHQW6WUXFWXUH

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 thefeature between subsystems. The interactions within the BSS between the various modules, layers, etc areshown as well as the interaction with the other Network Elements. Impacts on telecom and O&M Step2specifications are also given in this section. The validation strategy is presented as well as the impacts onGCD, 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.

'HILQLWLRQVDQGSUHUHTXLVLWHIn this section, we describe in a few lines the feature Radio Measurement Statistics (RMS) that wasintroduced 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 getmeasurements 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 severalvectors). The ranges of each vector are defined by 9 thresholds. These thresholds are changeable at theOMC-R.

The main differences between RMS and the packet distributions introduced hereafter are listed in Section 9.


7/34


Allrightsreserved.




volium.

+,*+/(9(/'(6&5,37,21The 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 countersIn what follows, each sub-feature is presented and analysed separately.

)XQFWLRQDO5HTXLUHPHQWVAnalyzing the dimensioning aspects of our BSS shows that some important PS counters are missing in ourBSS 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. Theproblem is that PS traffic is very different from CS traffic, which makes CS approach not really relevant in PSdomain.

The sub-features described hereafter propose several solutions to overcome these weaknesses.

2YHUDOOGHVFULSWLRQRIWKHSURSRVHGVROXWLRQV

,PSURYHPHQW6XSSRUWRIGLVWULEXWLRQVThis sub-feature introduces a new concept of counters to monitor PS resource usage. The existing PScounters count a number of events occurring during the reporting period (i.e. every hour). However, suchcounters do not allow retrieving the distribution of the events.

For instance, existing counters allow evaluating the averaged duration of the TBFs. However, it is interestingto 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 ispresented in Figure 1.

In what follows, these new counters are called distribution.

'LVWULEXWLRQRIWKH7%)GXUDWLRQ

0 s


8/34


Allrightsreserved.




volium.

,PSURYHPHQW&RQVROLGDWLRQRIFHOOLQGLFDWRUVDW*38OHYHOIn 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, GPUresources).In release B9, the consolidation at GPU level is only required for the counters/indicators listed inTable 1.

S r s r r p r 9 r s v v v D h p r

P105c Number of DL TBF establishment failures due to GPU congestion. CellP105d Number of UL TBF establishment failures due to GPU congestion. Cell

P105e Number of DL TBF establishment failures due to CPU processing power limitations of the GPU. Cell

P105f Number of UL TBF establishment failures due to CPU processing power limitations of the GPU. CellP105g Number of DL TBF establishment failures due to a lack of transmission resources. Cell

P105h Number of UL TBF establishment failures due to a lack of transmission resources. Cell

7DEOH&RXQWHUVIRUZKLFKDFRQVROLGDWLRQDW*38OHYHOLVUHTXLUHG

Also, without this consolidation, it is up to the MFS to perform the consolidation, which is in contradiction withthe 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 BSCconfiguration where 50 cells Ci with i = 1, 2, , 50 are mapped on a first GPU1 and 50 other cells C i with i =51, 52, , 100 are mapped on a second GPU2. NPA should be able to sum all counters P105x defined percell and related to a cell mapped on GPU 1. The same sum shall be retrieved on GPU2 too. This means thatif the operator is interested in a consolidation on P105g, the tool chain should be able to compute:

( ) =

=

50

1i

iP105gGPU1P105g

where P105gi is the counter P105g counting the number of DL TBF failures due to a lack of GCH resource inCell Ci. Similarly, on GPU2, we have:

( ) =

=100

1i

iP105gGPU2P105g

5

.

NPA shall allow the operator to know whether a spatial consolidation performed per GPU on indicatorsdefined at cell level is valid or invalid after a new GPU-cell re-mapping. One new suspected flag is thenrequired per GPU. This flag is hereafter called GPU Configuration Suspected Flag (GCSF) and is set by theMFS per GPU when at least one cell has been created, deleted or remapped on the concerned GPU duringthe reporting period.

From the GPU Configuration Suspected Flag, NPA shall derive a reliability indicator per GPU indicatingwhether 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). Inorder to avoid any confusion with the GPU Configuration Suspected Flag, this existing flag is renamed asCell Configuration Suspected Flag (CCSF). NPA uses this flag to derive a reliability indicator per cell toindicate whether a cell have been newly created on the GPU (e.g. at O&M cell creation or after a re-mappingof the cells on the GPU.

,PSURYHPHQW&RXQWHUVGHILQHGDW75;OHYHOThis sub-feature is not implemented in release B9.


9/34


Allrightsreserved.




volium.

In release B8, no MFS counter is defined at TRX level. It then becomes difficult to dimension the number ofextra 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 toconsolidate TRX counters at cell level as it is already done for TRX counters computed in the BSC.

,PSURYHPHQW1HZ0)6FRXQWHUVWhen studying the PS dimensioning rules in release B8, it appears that the following PS counters weremissing 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.

&RPSOLDQFHWRWKH0DUNHWLQJ5HTXLUHPHQWVThe table below identifies the compliance of each sub-feature to one or more marketing requirements.

)HDWXUH,WHP &RPSOLDQFH &RPPHQWV

Improvement 1 Yes

Improvement 2 YesImprovement 3 Yes

Improvement 4 Yes

&RPSOLDQFHWR*33VWDQGDUGThe sub-features described in this SFD are manufacturer dependent and therefore not described in 3GPPstandard.

:RUNLQJ$VVXPSWLRQVNone

'HSHQGHQFLHVIn this section, the technical dependencies between features of this SFD and with features addressed byother SFDs or already implemented are identified.

1) Sub-feature "Improvement 1: Support of distributions"

No dependency identified.

2) Sub-feature ",PSURYHPHQW: &RQVROLGDWLRQRIFHOOLQGLFDWRUVDW*38OHYHO"


3) Sub-feature ",PSURYHPHQW: &RXQWHUVGHILQHGDW75;OHYHO"

LVLQFRPSDWLEOHZLWK i.e. identify the features which are technically incompatible with the present feature


10/34


Allrightsreserved.




volium.

Feature Dependency

Dynamic Abis If the Dynamic Abis feature is not implemented, Alcatel BSSshall provide some means to assist the operator in thedimensioning of the number of extra Abis nibbles required perTRX. One mean is to allow the definition of TRX counters to

monitor the usage of Abis resources.

4) Sub-feature ",PSURYHPHQW: 1HZ0)6FRXQWHUV"


+:&RYHUDJHThis section defines the HW coverage of the sub-feature(s). A synthetic and exhaustive table is providedwhere the different HW generation of each subsystem are listed.

6\VWHP

GSM 900 Y

DCS 1800 YDCS 1900 Y

GSM 850 Y

1HWZRUNHOHPHQWIn the table below, the following definitions apply:X

swif feature supported by the NE with software impact,

Xhw

if feature supported by the NE with hardware impactX

sw+hwif feature supported by the NE with software and hardware impact.

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

D h p s i

s r h r

v r r

D h p s i

s r h r

v r r !

D h p s i

s r h r

v r r "

D h p s i

s r h r

v r r #

7 U T B r r h v )

BTS G2 with DRFU BTS MK2 with DRFU A9100 (Evolium standard) A910 (micro Evolium (M4M)) M1M, M2M 7 T 8 B r r h v )

BSC G2 H A T )

MFS Xsw Xsw Xsw Xsw

U h v v )

Alcatel TSC U h p q r ) TRAU G2 with DT16 TRAU G2 with MT120 TRAU G2.5 (with MT120) H T 8 )

MSC T B T I )

SGSN 9 h h D X A )

Data IWF C G S )

HLR P H )

OMC-R Xsw POLO OEF

LASER


11/34


Allrightsreserved.




volium.

MPM/NPA Xsw Xsw Xsw Xsw

RNO Xsw Xsw Xsw Xsw

H T U T )

MSTS

'HFLVLRQFULWHULDIn this section, the criteria relevant for deciding whether or not to implement the feature(s) are provided.

6WDQGDUGLVDWLRQNot applicable

&RPSHWLWLRQAccording to PCS, Motorola BSS already provides a set of distributions. Other competitors will likely providemeans like distributions in a mature (E)GPRS BSS release.

&XVWRPHUDuring the review of B8 BSS counters with Orange, it has been noticed that some important counters weremissing in our BSS.

*DLQV

7HOHFRPJDLQVNo Telecom gain is expected by this SFD.

2SHUDWLRQDOJDLQVThe features proposed in this SFD will ease the BSS dimensioning process and the follow up of PS QoS. Thenetwork 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.

8 r

i r

H r v p

S h v h y r

P453a DISTRIB_UL_TBF_DURATION

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 shortTBFs.

- Justify certain bad throughputs observed in the fields.

The corresponding thresholds should be tuneable to allow isolating a given traffic for adeep field analysis.

P453b DISTRIB_DL_TBF_DURATION

Same rationale as P453a but for the DL direction

P454a DISTRIB_UL_TBF_VOLUME

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 ULLLC volumes are not distinguished from short TBFs generating small UL LLCvolumes.

- Justify certain bad throughputs observed in the fields.

The corresponding thresholds should be tuneable to allow isolating a given traffic for adeep field analysis.

P454b DISTRIB_DL_TBF_VOLUME

Same rationale as P454a but for the DL direction

P455a DISTRIB_UL_PDCH_UNIT_ALLOC

The distribution of the number of PDCH units assigned to an UL TBF is required to checkwhether non-optimal allocations come from a lack of radio resources. In this case,parameters like MAX_PDCH, MAX_PDCH_HIGH_LOAD can be increased.

P455b DISTRIB_DL_PDCH_UNIT_ALLOC Same rationale as P455b but for the DL direction


12/34


Allrightsreserved.




volium.

8 r

i r

H r v p

S h v h y r

P38f CUMULATED_TIME_PDCH_USED_UL_CELL

This counter is used with P451a to quantify the overlapping of the UL TBFs on thePDCHs. For instance, a high overlapping factor can explain why the throughputsobserved in the fields are low.

P38e CUMULATED_TIME_PD

CH_USED_DL_CELL

Same rationale as P38f but for the DL direction.

P451a CUMULATED_TIME_PDCH_UL_TBF_CELL

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 thefields are low.

P451b CUMULATED_TIME_PDCH_DL_TBF_CELL

Same rationale as P451a but for the DL direction.

P452 CUMULATED_TIME_PDCH_DL_TBF_GMM_SIG_CELL

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 radioresources should be configured to carry only GMM signalling traffic.

P98f NB_SUSP_UL_TBF_REL This counter is defined to obtain a more accurate indicator for TBF drops. Operators arecarefully analysing the TBF drop rate that it is one of the main (E)GPRS QoS figures.

P98e NB_SUSP_DL_TBF_REL Same rationale as P98f but for the DL direction.7DEOH5DWLRQDOHIRUHDFKSDFNHWGLVWULEXWLRQDQGHDFKQHZFHOOFRXQWHU


13/34


Allrightsreserved.




volium.

6


14/34


Allrightsreserved.




volium.

thresholds may lead to irrelevant results (as explained in Section 3.2.1 the distribution thresholds aredefined per BSS).

- In case an O&M operation has modified one of the distribution thresholds, the operator shall be informedthat 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 thatpurpose, a new flag called Distribution Suspected Flag (DSF) will be present per cell on the OMC/MFSinterface to indicate such a change. This flag is here defined per cell (instead of per distribution) toreduce the impacts on NPA capacity. NPA shall then build a reliability indicator per cell for packetdistributions.

The RMS feature uses parameters requiring a specific tuning at cell level. As the distribution parameters aredefined at BSS level, we do not see the need for templates to assist the operator in the tuning of thedistributions 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 PMreport 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 indicatingwhether or not the packet distribution or its consolidation is suspected. A packet distribution or itsconsolidation is suspected:

if the packet distribution has its distribution suspected flag set in the PM report, or if its consolidationcontains at least one PM report for which the distribution suspected flag has changed during the periodconsidered 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&RQVROLGDWLRQRIFHOOLQGLFDWRUVDW*38OHYHO

The tool chain shall offer to operators the possibility to consolidate at GPU level cell indicators usingP105c/d/e/f/g/h/ cell countersP105c/d/e/f/g/h/ cell indicators at GPU level. NPA is in charge of this newconsolidation.

,PSURYHPHQW&RXQWHUVGHILQHGDW75;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 cellaggregation, the counters and the indicators are managed by NPA in the same way as for the TRX to cellaggregation 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.

,PSURYHPHQW1HZ0)6FRXQWHUV

The proposed new counters are described in Section 3.2.4.

7HOHFRP6SHFLILFDWLRQLPSDFWVThis section describes the main changes in the existing Alcatel BSS telecom specifications.


15/34


Allrightsreserved.




volium.

6WHS6WHS0)6FRXQWHUVFDWDORJXH

,PSURYHPHQW6XSSRUWRIGLVWULEXWLRQV

In the MFS counters catalogue, it is proposed to create a new type of counters called distributions. Only themain definition will be given in the database. The 10 values of the distribution will be generated automaticallyby specific MFS and NPA tools.

A new section will be written in the header document of the MFS counters catalogue to describe theprinciples of packet distributions.


No impact


See Section 3.2.5.

,PSURYHPHQW1HZ0)6FRXQWHUVSee Section 3.2.5.

,QWHUIDFHVThis section gives the details of the signalling changes on the various interfaces connected to the BSS.

20&0)6LQWHUIDFHThe new distribution thresholds shall be provided to the MFS (See Section 3.2.1).

51220&LQWHUIDFHThe new distribution thresholds shall be provided to RNO on a per BSC basis. (See Section 3.2.1).

2SHUDWLRQDQGPDLQWHQDQFH

20&5SDUDPHWHUV


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

Q h h r r h r 9 r s v v v T i r

D h p r 8 h r t P H 8 S

h p p r

U r S h t r q r s h y

h y r

PD_UL_TBF_DURATION_THR_k

Set of thresholds used to tune thedistribution of UL TBF duration

MFS BSS Changeable List of 9thresholds

0.5 16383.5(in s)Accuracyof 0.5 s

PD_DL_TBF_DURATION_THR_k

Set of thresholds used to tune thedistribution of DL TBF duration


0.5 16383.5(in s)Accuracyof 0.5 s

PD_UL_TBF_VOLUME_THR_k

Set of thresholds used to tune thedistribution of LLC volume carriedby an UL TBF


1-99 999999(in bytes)Accuracy

1

The valid options are: Site (CAE), Network (CDE), System (CST), Not Used (NU)2

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.


16/34


Allrightsreserved.




volium.

of 1 byte(See Note1)

PD_DL_TBF_VOLUME_THR_k

Set of thresholds used to tune thedistribution of LLC volume carriedby a DL TBF


1-99 999999(in bytes)Accuracyof 1 byte(See Note1)

PD_UL_PDCH_UNIT_ALLOC_THR_k

Set of thresholds used to tune thedistribution of nb of PDCH unitsallocated to a MS in UL


0.1-4.9Accuracyof 0.1

PD_DL_PDCH_UNIT_ALLOC_THR_k

Set of thresholds used to tune thedistribution of nb of PDCH unitsallocated to a MS in DL


0-50.1-4.9Accuracyof 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 x3600 = 1 065 600 kbit = 133 200 kbytesNote (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 thelist 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.


No impact.


No impact.


No impact.

0RGHOLVDWLRQRI20&5SDUDPHWHUV

20&*'02LPSDFWVEach of the parameters PD_x_THR (where x stands for the name of the packet distribution) will be definedas follows:

aGprsPdDlPdchUnitAllocThrxaGprsPdDlTbfDurationThrxaGprsPdDlTbfVolumeThrxaGprsPdUlPdchUnitAllocThrxaGprsPdUlTbfDurationThrxaGprsPdUlTbfVolumeThrxwhere x = 1, 2, ,9

Each new variable as the following attribute: $775,%87( 6


17/34


Allrightsreserved.




volium.

20&%6&LQWHUIDFHLPSDFWVNo impact.

20&0)6LQWHUIDFHLPSDFWVAll 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 valuesas they are set by the user.

2WKHUSDUDPHWHUV


No impact.


No impact.


No impact.


The following existing O&M parameters are modified:

Q h h r r h r 9 r s v v v T i r

D h p r 8 h r t P H 8 S

h p p r

U r S h t r q r s h y

h y r

T_WAIT_FLUSH U v r v v t u r r p r v s h A y u r h t r h B Q S T

r q r h t r s u r u r

r y r h r s u r t v t U 7 A

MFS MFS System (CST)/ None (DLS)

Timer 1-16(in s)Accuracyof 0.5 s

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

%6&30FRXQWHUVNo impact

0)630FRXQWHUV

,PSURYHPHQW6XSSRUWRIGLVWULEXWLRQVThe following distributions are created:

8 r

i r

H r v p

9 r s v v v

H r h r q

i w r p

P453a DISTRIB_UL_TBF_DURATION

Distribution of the UL TBF duration (expressed in s with anaccuracy of 50 ms)

Cell

P453b DISTRIB_DL_TBF_DURATION

Distribution of the DL TBF duration (expressed in s with anaccuracy of 50 ms)

Cell

P454a DISTRIB_UL_TBF_VOLU Distribution of the LLC volume (expressed in kbyte with an Cell4

The valid options are: Site (CAE), Network (CDE), System (CST), Not Used (NU)5

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.


18/34


Allrightsreserved.




volium.

8 r

i r

H r v p

9 r s v v v

H r h r q

i w r p

ME accuracy of 1 byte) carried by an UL TBF (in RLC ack mode only)P454b DISTRIB_DL_TBF_VOLU

MEDistribution of the LLC volume (expressed in kbyte with anaccuracy of 1 byte) carried by a DL TBF (in RLC ack mode only)

Cell

P455a DISTRIB_UL_PDCH_UNI

T_ALLOC

Distribution of the number of PDCH units assigned to an UL

TBF(computed with an accuracy of 0.001)

Cell

P455b DISTRIB_DL_PDCH_UNIT_ALLOC

Distribution of the number of PDCH units assigned to a DLTBF(computed with an accuracy of 0.001)

Cell

P453a and P453bOnly the active phase of the TBFs (i.e. when the TBF is not in delayed release phase) is counted indistributions P453a and P453b.

P454a and P454bOnly the LLC volumes exchanged in RLC acknowledged mode are counted in distributions P454a andP454b.

P455a and P455bDistributions 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 thepercentage of the PDCHs that is used by the assigned UL/DL TBF. For instance, if n UL/DL TBFs areestablished on a given PDCH, the UL/DL PDCH unit assigned to each UL/DL TBF on that PDCH is equal to1/n (See Figure 2).

Distribution P455a is computed at the release of each UL TBF (i.e. on receipt of the release indicationreceived from the RLC layer). Distribution P454b is computed at the release of each DL TBF (i.e. at theexpiry of timer T3192).

Note that the definition of P455a and P455bmay need to be changed to consider the impacts of the featureSupport of QoS in the BSS [ 10].

0.5 0.5 0.5 0.5 0.51 1 0.5 0.5 1 0.5 0.5 0.5

Timeslot ! " # $ % &

TBF 1 Sum of DL PDCH unit for TBF 1= 0.5 + 0.5 + 1 + 0.5 = 2.5

TBF 2 Sum of DL PDCH unit for TBF 2 = 1 + 1 + 0.5 + 0.5 = 3

TBF 3 Sum of DL PDCH unit for TBF 3 = 0.5 + 0.5 + 0.5 = 1.5

TBF 4 Sum of DL PDCH unit for TBF 4 = 0.5 + 0.5 = 1

)LJXUH([DPSOHRIFRPSXWDWLRQRI'/3'&+XQLWVDWDJLYHQWLPH


No impact.


The new type of counters defined at TRX level is introduced.

The following counters are proposed to be defined at TRX level:

8 r

i r

H r v p

9 r s v v v

H r h r q

i w r p

P_TRX_1 CUMULATED_TIME_PD Cumulated time during which a PDCH is used by a DL or UL TBF TRX


19/34


Allrightsreserved.




volium.

8 r

i r

H r v p

9 r s v v v

H r h r q

i w r p

CH_USED_TRX on the concerned TRXP_TRX_2 MAX_NB_PDCH_USED_

TRXMaximum number of PDCHs used by a DL or UL TBF on theconcerned TRX

TRX

P_TRX_3 CUMULATED_TIME_BUSY_GCH_TRX Cumulated time during which a GCH is used on the concernedTRX TRX

P_TRX_4 MAX_NB_BUSY_GCH_TRX

Maximum number of GCHs used on the concerned TRX TRX

Note (*): The exact reference will be given when integrating the counters in the MFS counters catalogue.


The following counters are proposed to be introduced:

8 r

i r

H r v p

9 r s v v v

H r h r q

i w r p

P38f CUMULATED_TIME_PDCH_USED_UL_CELL

Cumulated time during which a PDCH is used by at least one ULTBF

Cell

Accuracy of50 msP38e CUMULATED_TIME_PD

CH_USED_DL_CELLCumulated time during which a PDCH is used by at least one DLTBF

CellAccuracy of50 ms

P451a CUMULATED_TIME_PDCH_UL_TBF_CELL

Cumulated time during which an UL TBF uses one PDCH CellAccuracy of50 ms

P451b CUMULATED_TIME_PDCH_DL_TBF_CELL

Cumulated time during which a DL TBF uses one PDCH CellAccuracy of50 ms

P452 CUMULATED_TIME_PDCH_DL_TBF_GMM_SIG_

CELL

Cumulated time during which a DL TBF established for GMMsignalling purposes uses a PDCH

Cell

Accuracy of50 msP98f NB_SUSP_UL_TBF_REL Number of UL TBF releases due to the suspend procedure CellP98e NB_SUSP_DL_TBF_REL Number of DL TBF releases due to the suspend procedure CellNote (*): The exact reference will be given when integrating the counters in the MFS counters catalogue.

P38fCounter P38f is used to estimate the time during which a PDCH is used by at least one UL TBF (cumulatedover all the PDCHs available in the cell). An example of computation is given in Figure 3. Note that thecounter shall consider the resource allocation changes that occur further to a UL TBF re-allocation.

P38eEquivalent to P38f but for the DL direction. The delayed release phase of the DL TBF is also taken intoaccount.

P451aCounter P451a is used to estimate the time during which an UL TBF uses one PDCH (cumulated over all thePDCHs used by the UL TBF and over all the UL TBFs operating in the cell). An example of computation isgiven in Figure 3. Note that the counter shall consider the resource allocation changes that occur further to aUL TBF re-allocation.

P451bIdentical to P451a but for the DL direction. The delayed release phase of the DL TBF is also taken intoaccount.

P452


20/34


Allrightsreserved.




volium.

For a given DL TBF, Counter P452 is started at the establishment of the DL TBFs established to carry GMMsignalling traffic to the MS. It is stopped at the end of the active phase of the DL TBF or on receipt of a DLLLC PDU without the T-bit set.

P98e and P98fIn release B8, Counters P98a and P98b evaluate the number of UL/DL TBF releases due to the suspensionprocedure while the TBFs are still on-going on receipt of the Suspend message from the BSC. However, theTBFs 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 areincremented in the two following cases:

a Suspend message is received from BSC and the suspend procedure concerns a UL/DL TBF which isstill on-going, or,

a Suspend message is received from BSC and the suspend procedure concerns a UL/DL TBF which hasbeen 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 (viaP34a/b/c/d) are re-used here.

The following counters shall be removed:

8 r

i r

H r v p

9 r s v v v

H r h r q

i w r p

P98a NB_DL_TBF_REL_SUSP Number of DL TBF releases due to a suspension from MS. Cell

P98b NB_UL_TBF_REL_SUSP Number of UL TBF releases due to a suspension from MS. Cell

30LQGLFDWRUV


Each new distribution shall lead to the definition of a PM indicator.


No impact


The new type of indicators defined at TRX level is introduced.

The following new indicators are proposed at TRX level:H r v p

9 r s v v v

PDCH_TRAFFIC_TRX PDCH traffic expressed in Erlang on the concerned TRXFormulae:

CUMULATED_TIME_PDCH_USED_TRX/3600GCH_TRAFFIC_TRX GCH traffic expressed in Erlang on the concerned TRXFormulae:CUMULATED_TIME_BUSY_GCH_TRX/3600

In addition to those indicators, any new counter leads as usual to the creation of a new indicator.


The following new indicators are proposed:

H r v p

9 r s v v v

UL_OVERLAPPING_FACTOR Overlapping factor in the UL direction. This indicator gives a measure of the number of ULTBFs piled up on a PDCH


21/34


Allrightsreserved.




volium.

H r v p

9 r s v v v

Formulae:P451a / P38f = CUMULATED_TIME_PDCH_UL_TBF_CELL/CUMULATED_TIME_PDCH_USED_UL_CELL (See also Figure 3)

DL_OVERLAPPING_FACTOR Overlapping factor in the DL direction. This indicator gives a measure of the number of DLTBFs 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)

GMM_SIG_USAGE_RATIO Percentage of radio resources used for GMM signalling purposesP452 / P451b = CUMULATED_TIME_PDCH_DL_TBF_GMM_SIG_CELL /CUMULATED_TIME_PDCH_DL_TBF_CELL

0.5 0.5 0.5 0.50.5 0.5 0.5 0.5


TBF 1 Sum of UL PDCH unit for TBF 1= 0.5 + 0.5 + 0.5 + 0.5 = 2

TBF 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 TCUMULATED_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 = TCUMULATED_TIME_PDCH_USED_UL_CELL = 4 x T

UL_OVERLAPPING_FACTOR = (8 x T) / (4 x T) = 2(a)

0.5 0.51 1 0.5 0.5 1 1


TBF 1 Sum of UL PDCH unit for TBF 1= 0.5 + 0.5 + 1 + 1 = 3

TBF 2 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 TCUMULATED_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 = TCUMULATED_TIME_PDCH_USED_UL_CELL = 6 x T

UL_OVERLAPPING_FACTOR = (8 x T) / (6 x T) = 4/3 = 1.33

(b))LJXUH([DPSOHRI8/B29(5/$33,1*B)$&725FRPSXWDWLRQIRUDJLYHQSHULRGRI7VHFRQGV

In addition to those indicators, any new counter leads as usual to the creation of a new indicator.

0LJUDWLRQ

20&0LJUDWLRQIn OMC all the parameters PD_x_THR (THR (where x stands for the name of the packet distribution) will beinitialized with their default values for the B8 BSC instances.

%6&0LJUDWLRQThe BSC migration is not concerned with the parameters PD_x_THR (where x stands for the name of thepacket distribution), but if a BSC migrates from B8 to B9, the consequence for the OMC is that theseparameters become editable.


22/34


Allrightsreserved.




volium.

0)6PLJUDWLRQThe 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. 2SHUDWRUFRQVWUDLQWVDIWHU%!%PLJUDWLRQNo special issue on this topic.

-DYDVFULSWVNo impact

)DXOW0DQDJHPHQWNo impact

206SHFLILFDWLRQLPSDFWVThis section describes the main changes in the existing Alcatel BSS O&M specifications, and the new

specifications to be planned when applicable.

6WHS%66LQGLFDWRUVSee Section 3.2.6

6WHS/RJLFDOFRQILJXUDWLRQPDQDJHPHQW/&0LCM specification has to be updated with the information defined in the SFD.

6WHS0)620&LQWHUIDFH*'02MFS/OMC Interface GDMO specification has to be updated with information defined in the SFD.

6WHS*35630ILOHIRUPDW

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.

9DOLGDWLRQSee B9 validation plan

)LHOGSURFHGXUHGHVLJQThis 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&XVWRPHUGRFXPHQWDWLRQThis section describes the impacts on the Generic Customer Documentation (GCD):

No new documents is needed:

The following B8 GCD documents are impacted:

9 p r U v y r

7 ' 6 I W I i r

D h p

O&M PARAMETERS Dictionary" 7 F ! ' $ " 6 6 6 6 Q 8 a a 6

editorial: 6 parameters to be added


23/34


Allrightsreserved.




volium.

9 p r U v y r

7 ' 6 I W I i r

D h p

PM counters" 7 F ! ' $ $ 6 6 6 6 Q 8 a a 6

editorial: 6 distribution counters, 7 new MFScounters and 4 counters at TRX level to beadded

EVOLIUM A9135 MFS Description" 7 F ! ' " ! 6 6 6 6 U R a a 6

editorial: update of the PerformanceManagement paragraph in the MFS O&M

Functions chapter (introduction) taking intoaccount the distribution counters

BSS System Description" 7 F ! ' ! ! 6 6 6 6 U R a a 6

editorial: update of the Performance Monitoringand Performance Management chapters takinginto account the distribution counters

Operating & Maintenance Principles" 7 F ! ' $ # 6 6 6 6 Q 8 a a 6

editorial: update of the GPRS PerformanceManagement Counters chapter taking intoaccount the distribution counters

A1353-RA OLH" 7 F ! ' # 6 6 6 6 Q 8 a a 6

minor: Update of the Logical ConfigurationManagement Windows chapter to introduce thenew OMC-R view called Packet Distribution

BSS Surveillance Handbook" 7 F ! ' % 6 6 6 6 Q 8 a a 6

editorial: update of the PerformanceManagement chapter (introduction) taking intoaccount the distribution counters

1RWH The O&M PARAMETERS Dictionary and PM counters documents are extracted from AccessDatabases. SED capital gain is the generation of these documents.

(QJLQHHULQJUXOHVThis section describes the impacts on the engineering rules:

No new document is needed

No impact is foreseen on existing Engineering documents.


24/34


Allrightsreserved.




volium.

68%6 GPRS screenThis 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 parameterPD_UL_TBF_DURATION_THR and a box DL TBF Duration with the parameterPD_DL_TBF_DURATION_THR

A sub-screen labeled LLC volume containing a box LLC volume carried by a UL TBF with theparameter PD_UL_TBF_VOLUME_THR and a box LLC volume carried by a DL TBF with theparameter 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 parameterPD_DL_PDCH_UNIT_ALLOC _THR

It is proposed that the corresponding HMI names of the parameters to be PD_x_THR THR (where x standsfor the name of the packet distribution). Each element of the lists PD_x_THR should be edited in a separateedit field.As concerning the displaying of the parameters value, in order to prevent from managing float numbers, thefollowing rules should be applied:

The values of PD_UL_TBF_DURATION_THR and PD_DL_TBF_DURATION_THR will be displayedas actual values x 10.

The values of PD_UL_PDCH_UNIT_ALLOC_THR PD_DL_PDCH_UNIT_ALLOC_THR will bedisplayed as actual values x 100.

The rest of the parameters will be displayed as they are.


25/34


Allrightsreserved.




volium.

Note: the rules above concern only the HMI. Inside RNIM and on the OMC-MFS interface, the coded valueswill be used.The HMI should turn red if during the editing the mandatory rule stated in Section 3.2.1is violated.

20&PRGHOL]DWLRQSee Section 3.2.2.

2SWLRQDOIHDWXUHThere are no optional features involved.

2YHUYLHZRIWKHLPSDFWXSRQ20&VSHFVThe 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 distributionmust beadded 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(5No impact

13$


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 betreated as usual GPRS counters.In addition, they cant be used to flexible indicators (due to the check on the formulas done when a flexibleindicator is created is checked that all counters within the formula are present in the cell GPRS countertable).Among with the distribution counters, a new distribution suspected flag DSF (managed as an ordinary SF byNPA 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 1Distribution counters wont be created as columns in the NPA database and wont be loaded, as distributioncounters have no mean alone. The distribution counters will be used to create only new indicators in NPAdatabase. 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 willbe 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 thesenew indicators should be treated as the normal indicators (not like the RMS ones) so nothing special to bedone for the parsing/loading of the indicators.


26/34


Allrightsreserved.




volium.

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 toload 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 tocompute an reliability indicator for the distributions.

The distribution counters wont be created as columns in the NPA database and wont loaded in NPA andMPM because the distribution counters have no mean alone and in order to decrease the NPA databasedimensioning. 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 todo that it is necessary to create a new group that will configure the special temporal and spatial aggregations.


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 SFcalled GCSF will be set to 1. The BSC block wont be rejected by GPRS parser in case GCSF is 1. GCSF willbe used further in a GPU reliability indicator formula. GPRS parser will be updated in order to reject the BSCblock in the following cases:-SF 1, GCSF 0-SF 1, GCSF 1The migration is impacted because the CELL GPRS counters/indicators tables are already existing in B8 sothe tables will be migrated to B9 in counters/indicators/hierarchy tables where the GPUID will be filled bydefault with not_avail for the B8 data. Also B9 cell with only GSM data will remain with not_avail GPUparent.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 trueand the block will be rejected by GPRS parser (same behavior as in B7 and B8). The GPU change for a cellwill be specified by a new counters inserted in the GPU (sub BSS ) block from the GPRS PM file, counter thatwill be later used as an reliability indicator.

The migration is impacted because the counters are already existing in B9 so the tables should be migratedto B9 in counters/indicators/hierarchy tables where the GPU id will be filed by default with not_avail for theB8 data.

The CELL GPRS flexible indicators wont be aggregated at GPU level and will remain as in B8 CELL -

- BSC - NET.


A new block will be introduced in the B9 MFS PM files so, the B9 GPRS PM parser and the obsynt tool needsto be modified.On the fly aggregation needed from TRX object (Trx GPRS block) to CELL object (Cell GPRS block) levelduring the parsing phase, similar to whats done with TRX data coming from PM 110. The TRX indicatortables 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, NPAtraffic 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


27/34


Allrightsreserved.




volium.

aggregation from TRX to CELL, in the same way as for the on the fly aggregation from TRX to CELL in the110 files. This will have an impact on the GPRS performance and should be followed during the L&S testbecause the GPRS files are coming by MFS and during the fly-aggregation all the file should be kept inmemory. 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.


Only new counters/indicators to be added. No specific development foreseen.

512This 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 hypothesisthat there will not be stored vectors by hour

- Introduces reliability on vectors and matrices (to be based on standard indicators and with a display intabular 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 importOMC logical parameters. A specific new tool (integrated in the RNO Administration toolbar) shall bedeveloped 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 tohave 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, itwas very difficult to stabilise.

It is not foreseen new functions on matrices and vectors (only usage of the ones already available for theRMS). 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&Sand RNO traffic model preparation.


Reports (vectors/matrices) shall be introduced on GPUs (non RNO objects).

A configuration data impact is also foreseen particularly for reliability aspects.


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 andRNO traffic model preparation.


28/34


Allrightsreserved.




volium.


Only impact on configuration data is foreseen.

3RORNo impact

2()No impact


29/34


Allrightsreserved.




volium.

3(5)250$1&(6


30/34

ED

01RELEASED

COUNTER

IMPROVEMENTS

FOR

RELEASEB9

0613_01.doc

22/04/200

4

3BK102040613D

TZZA

30/34

All rdoc

not per


31/34


Allrightsreserved.




volium.

,03$&766800$5


32/34


Allrightsreserved.




volium.

*/266$5<

$EEUHYLDWLRQVCCSF Cell Configuration Suspected FlagDSF Distribution Suspected FlagGCSF GPU Configuration Suspected FlagPD Packet DistributionRMS Radio Measurement StatisticsSF Suspected FlagUDF User defined functions

7HUPLQRORJ\'/3'&+XQLWA 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'&+XQLWAn UL PDCH unit is defined as a unit of UL radio transmission on a PDCH. If n UL TBFs are using a givenPDCH, the UL PDCH unit assigned to each TBF is 1/n on that PDCH.

*356VHVVLRQA GPRS session corresponds to the period during which the MS is in packet transfer mode. When involved ina GPRS session, the MS has always at least one UL or DL TBF established.

*38FRQILJXUDWLRQVXVSHFWHGIODJ*&6)This flag is reported by the MFS in PM report related to a given GPU. It indicates to NPA whether a cell hasbeen created or removed on the GPU during the PM reporting period (e.g. further to a re-mapping of the cells

on the GPU).

&HOOFRQILJXUDWLRQV6XVSHFWHGIODJ&&6)This flag is reported by the MFS in PM report related to a given cell. It indicates to NPA whether a cell hasbeen created on the GPU during the PM reporting period (e.g. further to a re-mapping of the cells on theGPU).

'LVWULEXWLRQVXVSHFWHGIODJ'6)This flag is reported by the MFS in PM report related to a given cell. It indicates to NPA whether or not atleast one of the packet distribution thresholds has been modified during the PM reporting period (e.g. furtherto an O&M change).


33/34


Allrightsreserved.




volium.

$11(;$0$,1',))(5(1&(6%(7:((15$',20($685(0(1767$7,67,&6$1'3$&.(7',675,%87,216

Table 4 highlights the main differences between the feature Radio Measurements Statistics introduced in

release B7 and the packet distributions presented in this SFD.

A p v S h q v

H r h r r

T h v v p

Q h p x r

9 v v i v

8 r

Number of values per vector or distribution 10 (usually) 10 RMS also supports matrixes.

Number of thresholds per vector or distribution 9 9 For RMS, the min and max values of thevector are set by system parameters.

Period of reporting Up to 23 h 1 h

Activation of the vector or distribution reporting By an RMS job Always The packet distributions are alwaysactivated.

Spatial consolidation per cell X Not required for packet distributions sincethey are all defined at cell level.

Spatial consolidation per BSS X

Spatial consolidation per GPU -

Spatial consolidation per network Not defined for packet distributions sinceno reliability indicator is today defined atnetwork level

Temporal consolidation per day XTemporal consolidation per week

Temporal consolidation per month

Standard indicators derived based on the reporteddistributions/vectors

X

Reliability indicators X Available per cell (not per distribution) inorder to decrease NPA capacity.

PM reporting In RMS job In PM files

Storage in NPA 15 days As a normalcounterindicat

orUser 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.7DEOH0DLQGLIIHUHQFHVEHWZHHQUDGLRPHDVXUHPHQWVWDWLVWLFVDQGSDFNHWGLVWULEXWLRQV


34/34

Allrightsreserved.




volium.

$11(;%,03$&762113$&$3$&,7

Date post:	03-Apr-2018
Category:	Documents
Upload:	phuong-le
View:	222 times
Download:	0 times

B9 Counter Improved

Documents