Huawei BSC_Operation Manual - Performance Measurement

M900/M1800 Operation Manual - Performance Measurement Contents

Issue 04 (2006-09-30) Huawei Technologies Proprietary i

Contents

1 Overview......................................................................................................................................1-1 1.1 Basic Concepts Related to Performance Measurement .................................................................................1-2

1.1.1 Statistics Item.......................................................................................................................................1-2 1.1.2 Measurement Time...............................................................................................................................1-2 1.1.3 Measurement Object ............................................................................................................................1-2 1.1.4 Status of Performance Measurement Task ...........................................................................................1-3 1.1.5 Measure Type.......................................................................................................................................1-3 1.1.6 Measuring Point ...................................................................................................................................1-3

1.2 Functional Characteristics of Performance Measurement.............................................................................1-3 1.2.1 Creating Performance Measurement Task ...........................................................................................1-3 1.2.2 Collecting and Processing Performance Measurement Result .............................................................1-3 1.2.3 Querying the Status of Performance Measurement Task .....................................................................1-4 1.2.4 Querying the Result of Performance Measurement Task.....................................................................1-4 1.2.5 Performance Measurement Data Backup.............................................................................................1-4 1.2.6 Deleting Performance Measurement Task ...........................................................................................1-4 1.2.7 Deleting Performance Measurement Result.........................................................................................1-4

2 Performance Measurement Operations.................................................................................2-1 2.1 Setting Performance Measurement Task .......................................................................................................2-2

2.1.1 Creating Performance Measurement Task ...........................................................................................2-2 2.1.2 Deleting Performance Measurement Task .........................................................................................2-10 2.1.3 Modifying Performance Measurement Task Name............................................................................2-10

2.2 Querying Performance Measurement Task .................................................................................................2-11 2.2.1 Querying Information and Status of Performance Measurement Task...............................................2-11 2.2.2 Querying Statistical Result of Performance Measurement Task ........................................................2-12

2.3 Setting Performance Measurement Template..............................................................................................2-15 2.3.1 Creating Item Template......................................................................................................................2-16 2.3.2 Creating Time Template.....................................................................................................................2-17 2.3.3 Creating Object Template ..................................................................................................................2-17

3 M2000 Performance Measurement .........................................................................................3-1 3.1 Performance Measurement Objects...............................................................................................................3-2

3.1.1 Hierarchy of Performance Measurement Objects ................................................................................3-2

Contents M900/M1800

Operation Manual - Performance Measurement

ii Huawei Technologies Proprietary Issue 04 (2006-09-30)

3.1.2 Hierarchy of Performance Measurement Counters ..............................................................................3-2 3.1.3 Type of Performance Measurement Counters ......................................................................................3-3

3.2 Measurement Results Query .........................................................................................................................3-3 3.2.1 Setting up a Real-Time Measurement Query Task.............................................................................3-11 3.2.2 Querying Through Templates.............................................................................................................3-11 3.2.3 Displaying the Query Results ............................................................................................................3-12

3.3 Template Management Query .....................................................................................................................3-15 3.3.1 Creating a Query Template ................................................................................................................3-15 3.3.2 Modifying a Query Template .............................................................................................................3-16 3.3.3 Viewing a Query Template.................................................................................................................3-17 3.3.4 Deleting a Query Template ................................................................................................................3-17 3.3.5 Managing the Sub-Catalog.................................................................................................................3-17

3.4 Measurement Maintenance .........................................................................................................................3-20 3.4.1 Querying the Measurement Counters and Objects.............................................................................3-20 3.4.2 Querying Missing Measurement Results ...........................................................................................3-21 3.4.3 Synchronizing Measurement Results .................................................................................................3-22 3.4.4 Subscribing to Measurement Results .................................................................................................3-23 3.4.5 Querying the Reliability of Measurement Results .............................................................................3-24 3.4.6 Suspending NE Measurement ............................................................................................................3-25 3.4.7 Recovering NE Measurement ............................................................................................................3-25

3.5 Real-Time Measurement Maintenance........................................................................................................3-25 3.6 Threshold Management...............................................................................................................................3-26

3.6.1 Adding Thresholds .............................................................................................................................3-26 3.6.2 Modifying Thresholds........................................................................................................................3-28 3.6.3 Deleting Thresholds ...........................................................................................................................3-29 3.6.4 Suspending Thresholds ......................................................................................................................3-29 3.6.5 Activating Thresholds ........................................................................................................................3-29

3.7 Customer Counter Management..................................................................................................................3-29 3.7.1 Creating a User-Defined Counter.......................................................................................................3-30 3.7.2 Modifying a User-Defined Counter ...................................................................................................3-32 3.7.3 Deleting a User-Defined Counter.......................................................................................................3-32 3.7.4 Importing a User-Defined Counter ....................................................................................................3-32 3.7.5 Exporting a User-Defined Counter ....................................................................................................3-33 3.7.6 Showing or Hiding a User-Defined Counter......................................................................................3-33 3.7.7 Editing the Formula for the User-Defined Counter............................................................................3-33

4 Performance Measurement Tasks...........................................................................................4-1 4.1 Instructions of Performance Measurement Task ...........................................................................................4-2

4.1.1 Classification of Performance Measurement Items..............................................................................4-2 4.2 CPU Performance Measurement ...................................................................................................................4-3

4.2.1 Average CPU Occupancy (%)..............................................................................................................4-3 4.2.2 Maximum CPU Occupancy (%) ..........................................................................................................4-4

M900/M1800 Operation Manual - Performance Measurement Contents

Issue 04 (2006-09-30) Huawei Technologies Proprietary iii

4.3 BSC Overall Performance Measurement ......................................................................................................4-4 4.3.1 Number of Uplink TBF Establishment Attempts .................................................................................4-5 4.3.2 Number of Successful Uplink TBF Establishment ..............................................................................4-6 4.3.3 Number of Uplink TBF Normal Release .............................................................................................4-6 4.3.4 Number of Downlink TBF Establishment Attempts ............................................................................4-6 4.3.5 Number of Successful Downlink TBF Establishment..........................................................................4-6 4.3.6 Number of Downlink TBF Normal Release.........................................................................................4-6 4.3.7 Total Number of Uplink LLC_PDUs Sent ...........................................................................................4-6 4.3.8 Total Bytes of Uplink LLC_PDUs Sent ...............................................................................................4-6 4.3.9 Total Number of Downlink LLC_PDUs Received ..............................................................................4-7 4.3.10 Total Bytes of Downlink LLC_PDUs Received ................................................................................4-7 4.3.11 Number of Packet Paging Requests Sent ...........................................................................................4-7 4.3.12 Number of Circuit Paging Requests Sent...........................................................................................4-7 4.3.13 Mean Number of Available PDCHs...................................................................................................4-7 4.3.14 Mean Number of Occupied PDCHs...................................................................................................4-7

4.4 NS Performance Measurement......................................................................................................................4-7 4.4.1 NS Transmission Performance Measurement ......................................................................................4-7

4.5 BSSGP Performance Measurement.............................................................................................................4-18 4.5.1 BSSGP Performance Measurement ...................................................................................................4-18

4.6 G-Abis Interface Performance Measurement ..............................................................................................4-21 4.6.1 TRAU Link Measurement..................................................................................................................4-21

4.7 Pb Interface Performance Measurement .....................................................................................................4-25 4.7.1 LAPD Link Measurement..................................................................................................................4-25

4.8 Cell Performance Measurement ..................................................................................................................4-36 4.8.1 Packet Access Performance Measurement on CCCH ........................................................................4-37 4.8.2 Packet Access Performance Measurement on PCCCH......................................................................4-40 4.8.3 Packet Access Performance Measurement on PACCH ......................................................................4-41 4.8.4 Rate of Successful Packet Assignment ..............................................................................................4-43 4.8.5 Paging Request Measurement ............................................................................................................4-56 4.8.6 Uplink TBF Establishment/Release Measurement.............................................................................4-63 4.8.7 Downlink TBF Establishment/Release Measurement........................................................................4-78 4.8.8 Uplink LLC Data Transmission Measurement...................................................................................4-91 4.8.9 Downlink LLC Data Transmission Measurement..............................................................................4-94 4.8.10 Uplink RLC Data Transmission Measurement ................................................................................4-99 4.8.11 Downlink RLC Data Transmission Measurement..........................................................................4-106 4.8.12 Cell Radio Channel Performance Measurement ............................................................................4-112 4.8.13 Resource Maintenance Performance Measurement .......................................................................4-117 4.8.14 PDCH Resource Performance Measurement .................................................................................4-122 4.8.15 PDCH Extremum Value Measurement ..........................................................................................4-129 4.8.16 Uplink EGPRS TBF Establishment/Release Measurement ...........................................................4-130 4.8.17 Downlink EGPRS TBF Establishment/Release Measurement ......................................................4-133 4.8.18 Uplink EGPRS RLC Data Transmission Measurement .................................................................4-136

Contents M900/M1800


iv Huawei Technologies Proprietary Issue 04 (2006-09-30)

4.8.19 Downlink EGPRS RLC Data Transmission Measurement ............................................................4-138 4.8.20 EGPRS GMSK_MEAN_BEP Different Value Measurement........................................................4-141 4.8.21 EGPRS 8PSK_MEAN_BEP Different Value Measurement ..........................................................4-143 4.8.22 Uplink GMSK EGPRS RLC Data Retransmission Rate Measurement .........................................4-147 4.8.23 Uplink 8PSK EGPRS RLC Data Retransmission Rate Measurement ...........................................4-150 4.8.24 Downlink GMSK EGPRS RLC Data Retransmission Rate Measurement ....................................4-152 4.8.25 Downlink 8PSK EGPRS RLC Data Retransmission Rate Measurement ......................................4-155

5 Procedures of Traffic Statistics Analysis...............................................................................5-1 5.1 Overview.......................................................................................................................................................5-2 5.2 Preparation for the Traffic statistics Analysis................................................................................................5-2

5.2.1 Traffic Statistics Register Items ...........................................................................................................5-2 5.2.2 Data Preparation...................................................................................................................................5-5

5.3 Overall Idea for Traffic Statistics Analysis....................................................................................................5-5

6 BSC-level Traffic Statistics Analysis......................................................................................6-1 6.1 Analyzing the Quality of LAPD of Pb Interface ...........................................................................................6-2 6.2 Analyzing the BSC Overall Performance......................................................................................................6-3

6.2.1 Analyzing the Network Congestion Rate .............................................................................................6-3 6.2.2 Analyzing the Network Call-drop Rate................................................................................................6-3

6.3 Analyzing the Data of PDCH ........................................................................................................................6-4

7 Cell-level Traffic Statistics Analysis ......................................................................................7-1 7.1 Analyzing the Quality of the Transmission Link of Cell...............................................................................7-2

7.1.1 Analyzing the Um Interface .................................................................................................................7-2 7.1.2 Analyzing the G-Abis Interface ...........................................................................................................7-4

7.2 Analyzing the Congestion .............................................................................................................................7-5 7.2.1 Definition .............................................................................................................................................7-5 7.2.2 Analyzing the Congestion Rate............................................................................................................7-5

7.3 Analyzing the Call-drop Rate ........................................................................................................................7-9 7.3.1 Items to Be Analyzed ...........................................................................................................................7-9 7.3.2 Analyzing Call-drop Rate.....................................................................................................................7-9

7.4 Analyzing Cell Traffic .................................................................................................................................7-11 7.4.1 Measuring the Traffic of LLC Layer..................................................................................................7-11 7.4.2 Measuring the Traffic of RLC/MAC Layer .......................................................................................7-11 7.4.3 Measuring the MS Behaviors.............................................................................................................7-13

8 Introduction to GPCU KPIs in Huawei BSS network ........................................................8-1

M900/M1800 Operation Manual - Performance Measurement Figures

Issue 04 (2006-09-30) Huawei Technologies Proprietary v

Figures

Figure 2-1 Creating new performance measurement task ..................................................................................2-2

Figure 2-2 Time definition interface...................................................................................................................2-6

Figure 2-3 Object definition interface ................................................................................................................2-8

Figure 2-4 Successful task registration interface................................................................................................2-9

Figure 2-5 Task details .....................................................................................................................................2-11

Figure 2-6 Interface for viewing task status .....................................................................................................2-12

Figure 2-7 Result time definition interface.......................................................................................................2-13

Figure 2-8 Task result interface ........................................................................................................................2-14

Figure 2-9 Interface of details ..........................................................................................................................2-14

Figure 2-10 Data chart interface.......................................................................................................................2-15

Figure 2-11 Item template setting.....................................................................................................................2-16

Figure 3-1 Hierarchy of performance measurement counters ............................................................................3-3

Figure 3-2 Query Result .....................................................................................................................................3-4

Figure 3-3 Query ................................................................................................................................................3-4

Figure 3-4 Object Selection................................................................................................................................3-5

Figure 3-5 Counter Selection..............................................................................................................................3-8

Figure 3-6 Other Setting.....................................................................................................................................3-9

Figure 3-7 Set Counter Filter Conditions .........................................................................................................3-10

Figure 3-8 Querying Through Templates .........................................................................................................3-12

Figure 3-9 Displaying query results in table.....................................................................................................3-13

Figure 3-10 Displaying query Results in line chart ..........................................................................................3-14

Figure 3-11 Displaying query results in bar chart ............................................................................................3-15

Figure 3-12 Saving the template.......................................................................................................................3-16

Figure 3-13 Modifying template attributes.......................................................................................................3-17

Figure 3-14 Creating Dir menu option .............................................................................................................3-18

Figure 3-15 Typing the name of the newly created sub-catalog .......................................................................3-19

Figures M900/M1800


vi Huawei Technologies Proprietary Issue 04 (2006-09-30)

Figure 3-16 Measure Management...................................................................................................................3-20

Figure 3-17 Please Select Time Segment .........................................................................................................3-21

Figure 3-18 Missing Result Inquiry (1)............................................................................................................3-22

Figure 3-19 Missing Result Inquiry (2)............................................................................................................3-22

Figure 3-20 Newly reported measurement results............................................................................................3-23

Figure 3-21 Result reliability (100%)...............................................................................................................3-24

Figure 3-22 Result reliability (lower than 100%).............................................................................................3-24

Figure 3-23 Unreliable Result Info...................................................................................................................3-25

Figure 3-24 Threshold Setting..........................................................................................................................3-26

Figure 3-25 Add Threshold ..............................................................................................................................3-27

Figure 3-26 Modify Threshold .........................................................................................................................3-28

Figure 3-27 Customer Counter Management ...................................................................................................3-30

Figure 3-28 Add User Defined Counter ...........................................................................................................3-31

Figure 4-1 NSVC reset procedure originated by PCU .....................................................................................4-11

Figure 4-2 NSVC reset procedure originated by SGSN...................................................................................4-13

Figure 4-3 NSVC block procedure originated by PCU ....................................................................................4-14

Figure 4-4 NSVC block procedure originated by SGSN..................................................................................4-15

Figure 4-5 NSVC unblock procedure originated by PCU ................................................................................4-16

Figure 4-6 NSVC unblock procedure originated by SGSN..............................................................................4-17

Figure 4-7 FLUSH_LL PDUs received by BSSGP sublayer............................................................................4-19

Figure 4-8 SUSPEND PDU sent by BSSGP sublayer......................................................................................4-20

Figure 4-9 RESUME PDU sent by BSSGP sublayer .......................................................................................4-20

Figure 4-10 RADIO STATUS PDU sent by BSSGP sublayer..........................................................................4-21

Figure 4-11 Normal burst frames received from G-Abis interface...................................................................4-22

Figure 4-12 Out-of-Synchronization frames received from G-Abis interface..................................................4-23

Figure 4-13 Check error frames received from G-Abis interface.....................................................................4-24

Figure 4-14 Valid TRAU frames sent to G-Abis interface ...............................................................................4-24

Figure 4-15 Empty TRAU frames sent to G-Abis interface .............................................................................4-25

Figure 4-16 Send the SABM frame to request link establishment by PCU......................................................4-27

Figure 4-17 Send the SABM frame to request link establishment by BSC......................................................4-28

Figure 4-18 Send the UA frame to acknowledge link establishment by PCU..................................................4-28

Figure 4-19 Send the UA frame to acknowledge link establishment by BSC ..................................................4-29

Figure 4-20 REJ frame sent by PCU to request retransmission LAPD frame..................................................4-30


Issue 04 (2006-09-30) Huawei Technologies Proprietary vii

Figure 4-21 REJ frame sent by BSC to request retransmission LAPD frame ..................................................4-31

Figure 4-22 REJ frame received and Information frame retransmitted ............................................................4-33

Figure 4-23 Channel Request message received on CCCH .............................................................................4-38

Figure 4-24 One phase access requests received on RACH.............................................................................4-39

Figure 4-25 Single block channel requests received on RACH .......................................................................4-39

Figure 4-26 Channel Request message received on PCCCH ...........................................................................4-41

Figure 4-27 Two phase packet access...............................................................................................................4-42

Figure 4-28 Establish uplink TBF in downlink TBF........................................................................................4-43

Figure 4-29 Immediate assignment ..................................................................................................................4-44

Figure 4-30 Uplink assignment on PACCH .....................................................................................................4-45

Figure 4-31 Uplink assignment on PCCCH .....................................................................................................4-45

Figure 4-32 Uplink data block received ...........................................................................................................4-46

Figure 4-33 Packet resource request or measurement report received .............................................................4-47

Figure 4-34 Uplink immediate assignment ......................................................................................................4-48

Figure 4-35 Single block immediate assignment..............................................................................................4-49

Figure 4-36 Successful uplink assignment on PACCH ....................................................................................4-50

Figure 4-37 Downlink immediate assignments ................................................................................................4-51

Figure 4-38 Downlink assignments on PACCH...............................................................................................4-52

Figure 4-39 Successful Downlink immediate assignments ..............................................................................4-53

Figure 4-40 Successful Downlink assignments on PACCH.............................................................................4-53

Figure 4-41 Packet paging requests received ...................................................................................................4-57

Figure 4-42 Circuit paging requests received...................................................................................................4-57

Figure 4-43 Packet paging request sent............................................................................................................4-58

Figure 4-44 Circuit paging request sent ...........................................................................................................4-59

Figure 4-45 Packet paging requests sent on PCH.............................................................................................4-59

Figure 4-46 Packet paging requests sent on PPCH ..........................................................................................4-60

Figure 4-47 Circuit paging requests sent on PCH ............................................................................................4-61

Figure 4-48 Circuit paging requests sent on PPCH..........................................................................................4-61

Figure 4-49 Number of discarded paging messages in PPCH..........................................................................4-62

Figure 4-50 Circuit paging requests sent on PACCH .......................................................................................4-63

Figure 4-51 Uplink TBF establishment attempt using one phase access..........................................................4-64

Figure 4-52 Uplink TBF establishment attempt using single block .................................................................4-65

Figure 4-53 Uplink TBF Establishment attempt during a downlink TBF ........................................................4-65

Figures M900/M1800


viii Huawei Technologies Proprietary Issue 04 (2006-09-30)

Figure 4-54 Successful uplink TBF establishment using one phase access......................................................4-67

Figure 4-55 Successful uplink TBF establishment using single block .............................................................4-67

Figure 4-56 Successful uplink TBF establishment on PACCH ........................................................................4-68

Figure 4-57 Uplink TBF establishment failure due to no channel using one phase access ..............................4-69

Figure 4-58 Uplink TBF establishment failure due to no channel using single block......................................4-69

Figure 4-59 Uplink TBF establishment failure due to no channel on PACCH.................................................4-70

Figure 4-60 Uplink TBF establishment failure due to MS no response using one phase access......................4-71

Figure 4-61 Uplink TBF establishment failure due to MS no response using single blocks ............................4-71

Figure 4-62 Uplink TBF establishment failure due to MS no response on PACCH.........................................4-72

Figure 4-63 Uplink TBF normal release...........................................................................................................4-73

Figure 4-64 Uplink TBF abnormal release due to N3101 overflow.................................................................4-73

Figure 4-65 Uplink TBF abnormal release due to N3103overflow..................................................................4-74

Figure 4-66 Uplink TBF abnormal release due to SUSPEND .........................................................................4-75

Figure 4-67 Uplink TBF abnormal release due to FLUSH...............................................................................4-76

Figure 4-68 Uplink TBF abnormal release due to no channel..........................................................................4-77

Figure 4-69 Downlink TBF establishment attempt on CCCH..........................................................................4-79

Figure 4-70 Establishment of Downlink TBF on PACCH ...............................................................................4-80

Figure 4-71 Successful establishment of Downlink TBF on CCCH ................................................................4-81

Figure 4-72 Successful establishment of Downlink TBF on PACCH ..............................................................4-82

Figure 4-73 Downlink TBF establishment failures due to no channel .............................................................4-83

Figure 4-74 Downlink TBF establishment failure initiated on CCCH due to MS no response........................4-84

Figure 4-75 Downlink TBF establishment failure initiated on PACCH due to MS no response......................4-84

Figure 4-76 Downlink TBF normal release......................................................................................................4-86

Figure 4-77 Downlink TBF abnormal release due to N3105 overflow ............................................................4-87

Figure 4-78 Downlink TBF abnormal release due to SUSPEND.....................................................................4-88

Figure 4-79 Downlink TBF abnormal release due to FLUSH..........................................................................4-89

Figure 4-80 Downlink TBF abnormal release due to no channel .....................................................................4-90

Figure 4-81 Uplink TBF established successfully............................................................................................4-92

Figure 4-82 A Uplink LLC PDU sent to Gb interface ......................................................................................4-93

Figure 4-83 A Downlink LLC PDU received from Gb interface......................................................................4-95

Figure 4-84 Network receives the PACKET DOWNLINK ACK/NACK message..........................................4-96

Figure 4-85 Downlink LLC_PDUs discarded due to time-out.........................................................................4-97

Figure 4-86 Downlink LLC_PDUs discarded due to FLUSH_LL received.....................................................4-98


Issue 04 (2006-09-30) Huawei Technologies Proprietary ix

Figure 4-87 Uplink GPRS TBF data transfer with CS upgrades ....................................................................4-104

Figure 4-88 Uplink GPRS TBF data transfer with CS demotions..................................................................4-104

Figure 4-89 Uplink TBF with RLC control block with PAKCET UPLINK ACK/NACK message...............4-105

Figure 4-90 Downlink RLC data blocks with CS-1 CS type transmission.....................................................4-108

Figure 4-91 Downlink RLC data blocks transmission ...................................................................................4-109

Figure 4-92 Downlink TBF with RLC control block with PAKCET DOWNLINK ACK/NACK message ..4-110

Figure 4-93 Downlink RLC dummy block transmission................................................................................ 4-111

Figure 4-94 RLC data blocks in use on PDCH...............................................................................................4-113

Figure 4-95 BSC-originated cell reset ............................................................................................................4-118

Figure 4-96 BSC-originated cell blocking......................................................................................................4-119

Figure 4-97 BSC-originated cell unblocking..................................................................................................4-119

Figure 4-98 Gb-originated cell blocking ........................................................................................................4-120

Figure 4-99 Gb-originated cell unblocking ....................................................................................................4-121

Figure 4-100 BSC-originated channel blocking .............................................................................................4-121

Figure 4-101 BSC-originated channel unblocking .........................................................................................4-122

Figure 4-102 Attempts at converting TCH to PDTCH ...................................................................................4-124

Figure 4-103 Successful conversions from TCH to PDTCH..........................................................................4-125

Figure 4-104 Dynamic PDCHs reclaimed by BSC ........................................................................................4-126

Figure 4-105 EGPRS PACKET DOWNLINK ACK/NACK with GMSK_MEAN_BEP..............................4-142

Figure 4-106 EGPRS PACKET DOWNLINK ACK/NACK with 8PSK_MEAN_BEP ................................4-144

Figure 4-107 Downlink RLC data blocks with CS-1 CS type transmission...................................................4-153

Figure 4-108 Downlink EGPRS RLC data blocks transmission ....................................................................4-154

Figure 5-1 Traffic statistics analysis flow...........................................................................................................5-7

Figure 7-1 High congestion rate .........................................................................................................................7-6

Figure 7-2 PS call-drop rate .............................................................................................................................7-10

M900/M1800 Operation Manual - Performance Measurement Tables

Issue 04 (2006-09-30) Huawei Technologies Proprietary xi

Tables

Table 2-1 Description on statistics item page of new task register interface ......................................................2-3

Table 2-2 Description on statistics function type and the corresponding measure type .....................................2-3

Table 2-3 Description on statistics item setting interface ...................................................................................2-5

Table 2-4 Description on each domain in the time definition interface ..............................................................2-6

Table 2-5 Statistics function type and its corresponding measurement object....................................................2-8

Table 2-6 Description of task registration response information ......................................................................2-10

Table 3-1 Measurement function sets and relevant measurement units..............................................................3-5

Table 3-2 Measurement function sets and relevant measurement objects ..........................................................3-7

Table 3-3 Description of the parameters.............................................................................................................3-9

Table 3-4 Description of filter conditions.........................................................................................................3-11

Table 3-5 Parameters in Counter Info...............................................................................................................3-20

Table 3-6 Parameters in Object Info .................................................................................................................3-21

Table 3-7 Threshold Parameters .......................................................................................................................3-27

Table 3-8 Description of the parameters in the Add User Defined Counter dialog box ...................................3-31

Table 4-1 CPU performance Measurement.........................................................................................................4-3

Table 4-2 BSC over performance measurement .................................................................................................4-4

Table 4-3 NS transmission performance measurement.......................................................................................4-8

Table 4-4 BSSGP performance measurement...................................................................................................4-18

Table 4-5 TRAU link measurement..................................................................................................................4-21

Table 4-6 LAPD link measurement ..................................................................................................................4-25

Table 4-7 Cell performance measurement ........................................................................................................4-36

Table 4-8 Packet access performance measurement on CCCH ........................................................................4-37

Table 4-9 Packet access performance measurement on PCCCH ......................................................................4-40

Table 4-10 .Packet access performance measurement on PACCH ...................................................................4-41

Table 4-11 Packet assignment success rate. ......................................................................................................4-43

Table 4-12 Paging request measurement ..........................................................................................................4-56

Tables M900/M1800


xii Huawei Technologies Proprietary Issue 04 (2006-09-30)

Table 4-13 Uplink TBF establishment/release measurement............................................................................4-63

Table 4-14 Downlink TBF establishment/release measurement.......................................................................4-78

Table 4-15 Uplink LLC data transmission measurement..................................................................................4-91

Table 4-16 Downlink LLC data transmission measurement.............................................................................4-94

Table 4-17 Uplink RLC data transmission measurement ...............................................................................4-100

Table 4-18 Downlink RLC data transmission measurement...........................................................................4-106

Table 4-19 Cell radio channel performance measurement..............................................................................4-112

Table 4-20 Resource maintenance performance measurement .......................................................................4-117

Table 4-21 PDCH resource performance measurement..................................................................................4-122

Table 4-22 PDCH extreum value measurement..............................................................................................4-129

Table 4-23 Uplink EGPRS TBF establishment/release measurement ............................................................4-130

Table 4-24 Downlink EGPRS TBF establishment/release measurement .......................................................4-133

Table 4-25 Uplink EGPRS RLC data transmission measurement ..................................................................4-136

Table 4-26 Downlink EGPRS RLC data transmission measurement .............................................................4-138

Table 4-27 EGPRS GMSK-MEAN-BEP different value measurement .........................................................4-141

Table 4-28 EGPRS 8PSK-MEAN-BEP different value measurement............................................................4-143

Table 4-29 8PSK MCS selection based on BEP reports .................................................................................4-145

Table 4-30 Uplink GMSK EGPRS RLC Data Retransmission Rate Measurement........................................4-147

Table 4-31 Uplink 8PSK EGPRS RLC Data Retransmission Rate Measurement..........................................4-150

Table 4-32 Downlink GMSK EGPRS RLC Data Retransmission Rate Measurement...................................4-152

Table 4-33 Downlink 8PSK EGPRS RLC Data Retransmission Rate Measurement .....................................4-155

Table 5-1 Traffic register items...........................................................................................................................5-2

Table 8-1 GPCU KPIs in Huawei BSS network.................................................................................................8-1

M900/M1800 Operation Manual - Performance Measurement 1 Overview

Issue 04 (2006-09-30) Huawei Technologies Proprietary 1-1

1 Overview

About This Chapter

The following table lists the contents of this chapter.

Title Description

1.1 Basic Concepts Related to Performance Measurement

This section decribes the basic concepts involved in the creation of the PCU performance measurement.

1.2 Functional Characteristics of Performance Measurement

This section decribes the functional Characteristics of Performance Measurement

1 Overview M900/M1800


1-2 Huawei Technologies Proprietary Issue 04 (2006-09-30)

For the convenience of network performance analysis, network optimization and internal fault locating of the telecom network, the PCU system provides perfect performance measurement system. The PCU performance measurement system provides measurement of the CPU performance, BSC overall performance, NS performance and overall BSSGP performance, etc. It provides reliable data reference for understanding the performance of the PCU system, optimizing the overall GPRS system and locating any possible fault in the overall GPRS system.

1.1 Basic Concepts Related to Performance Measurement The basic concepts involved in the creation of the PCU performance measurement task are as follows:

1.1.1 Statistics Item The statistics item can be the quantity that should be collected for describing one measurement task, such as “Total Bytes of Downlink LLC_PDUs Received”. Such statistics items are the original materials that can be processed to obtain other results. The statistics item can also be the quantity obtained via simple calculation (plus, minus, multiplication and division) of certain statistics items. For example, the statistics item “Mean Length of Uplink LLC_PDUs” is the ratio of “Total Bytes of Uplink LLC_PDUs Sent” to “Total Number of Uplink LLC_PDUs Sent”. Generally, such item is quite visual.

1.1.2 Measurement Time The measurement time includes all necessary time information of a performance measurement task such as start date, statistic period, statistic type, time segment, time type, etc.

The start date refers to the date when the performance measurement starts.

The performance measurement period refers to the interval when the performance measurement is implemented to obtain certain original measurement data and when the data are processed to output the first group of statistical results.

The statistic type includes limited period task and semi-permanent task. The limited period task will trigger the measurement and output the statistical result within the set period of time. Once the semi-permanent task is created, the performance measurement will be made and the statistical result will be output fixedly everyday or on certain days of a week or in certain time segments on certain days of a month.

The performance measurement time segment refers to a period of time when the performance measurement is made on a certain day. The ratio of the performance measurement time segment to the measuring period should be an integer.

The performance measurement time type includes: statistic by day, statistic by week and statistic by month.

1.1.3 Measurement Object The measurement object refers to various measured physical or logic entities and their combinations, such as cell, RPPU board, etc.

M900/M1800 Operation Manual - Performance Measurement 1 Overview


1.1.4 Status of Performance Measurement Task The status of the performance measurement task can be divided into three kinds: not started, running, completed. All the task status refers to the status of the performance measurement task at the time when it is viewed.

The status not started indicates that the current time is earlier than the start time of that day's measurement task.

The status running indicates that the current time is between the start time of that day's measurement task and the end time of that day's measurement task.

The status completed indicates that the current time is later than the end time of that day's measurement task.

1.1.5 Measure Type The measure type is the special combination of the statistics items and objects.

1.1.6 Measuring Point The measuring point refers to the processing points for obtaining the statistical results within the PCU system.

1.2 Functional Characteristics of Performance Measurement

There are two typesof O&M terminals, OMC and M2000, which are published and used in commercial network. Because the performance measurement implementation in PCU system is completely same, no matter using OMC or M2000, we only take OMC O&M terminal for example to show how to maintain performance measurement above PCU.

1.2.1 Creating Performance Measurement Task After receiving the operations of creating performance measurement task sent by the OMC console and checking the parameter validity, the performance measurement module on the POMU board will determine whether the task can be created successfully based on the task resources within the POMU performance measurement module. Once the performance measurement task is successfully created, then the system will allocate a task number to the performance measurement task and create a file uniquely corresponding to the task in the hard disk of the POMU board to save the statistical result.

1.2.2 Collecting and Processing Performance Measurement Result To determine whether a performance measurement task is to be activated, the following three conditions should be satisfied simultaneously:

The current date of the task should be between the “measurement start date” and the “measurement end date” or the set date in a week or in a month.

The current time of the task should be between the “measurement start time” and the “measurement end time”.

1 Overview M900/M1800



The difference between the current time of the task and the “measurement start time” should be an integer multiple of the “measuring period”.

The POMU board packs the task number list of the activated task into message packet and broadcasts it to each RPPU board. After receiving the message, the RPPU board extracts the measured value snapshot corresponding to each task in the message at the moment and returns it to the POMU board.

What the RPPU board returns is the measurement status value. The result of a measuring period should be the difference between the “measured value at the end of the measuring period” and the “measured value in the beginning of the measuring period”. Therefore, the POMU needs to record the previous measured value sent by the RPPU board and calculates the difference between it and the measured value currently sent by the RPPU board. The result should be saved in the corresponding performance measurement file.

1.2.3 Querying the Status of Performance Measurement Task The O&M terminal or OMC can be used to query the information on the task which has already been successfully created.

1.2.4 Querying the Result of Performance Measurement Task The O&M terminal or OMC can be used to query the statistical result of a certain performance measurement task in a specified time segment.

1.2.5 Performance Measurement Data Backup The system will automatically back up the last generated performance measurement data to the standby POMU board.

1.2.6 Deleting Performance Measurement Task After receiving the operations of deleting the performance measurement task sent by the OMC and passing the parameter check, the performance measurement module on the POMU board will clear the task resources and delete the corresponding performance measurement file in the hard disk of the POMU board.

1.2.7 Deleting Performance Measurement Result Due to the limited hard disk capacity of the PCU system, the system will automatically delete the earliest results when the hard disk does not have enough space. The user can also delete historical performance statistical results stored in the hard disk of the POMU board at the OMC console.

M900/M1800 Operation Manual - Performance Measurement 2 Performance Measurement Operations


2 Performance Measurement Operations

About This Chapter


Title Description

2.1 Setting Performance Measurement Task

This section decribes the Setting Performance Measurement Task.

2.2 Querying Performance Measurement Task

This section decribes the Querying Information and Status of Performance Measurement Task.

2.3 Setting Performance Measurement Template

This section decribes the Setting Performance Measurement Template.

2 Performance Measurement Operations M900/M1800



2.1 Setting Performance Measurement Task In the PCU system, the performance measurement task can only be created or deleted at the OMC console.

2.1.1 Creating Performance Measurement Task Before creating a performance measurement task, please log in to the OMC console either in the OMC Shell mode or in the OMC LocalWS mode.

At the OMC console, the user can enter the interface for creating performance measurement task by the following means:

Selecting the menu Task list > New. Using the shortcut key Ctrl+N.

Click the button in the tool bar.

Figure 2-1 shows the interface for creating the performance measurement task. Table 2-1 shows the description related to this interface.

Figure 2-1 Creating new performance measurement task

After entering the interface, please follow the following steps to create the performance measurement task.



Set Basic Information In this step, please set the statistics functional type and the measure type and name the performance measurement concisely. The upper part of Figure 2-1 shows the corresponding interface and Table 2-1 shows the corresponding description.

Table 2-1 Description on statistics item page of new task register interface

Domain name Meaning Remarks

Task name Name of the statistics task. 1-30 characters

Statistics function type The collection of statistics types. Please refer to Table 2-2

Measure type The specific combination of statistics items and statistics objects.

Please refer to Table 2-2

Table 2-2 Description on statistics function type and the corresponding measure type

Statistics function type Measure type

CPU Performance Measurement CPU Performance Measurement

BSC Overall Performance Measurement


NS Performance Measurement NS Transmission Performance Measurement

BSSGP Performance Measurement


G-Abis Interface Performance Measurement

TRAU Link Measurement

Pb Interface Performance Measurement

LAPD Link Measurement

Packet Access Performance Measurement on CCCH

Packet Access Performance Measurement on PCCCH

Packet Access Performance Measurement on PACCH

Rate of Successful Packet Assignment

Paging Request Measurement

Uplink TBF Establishment/Release Measurement

Downlink TBF Establishment/Release Measurement

Uplink LLC Data Transmission Measurement

Downlink LLC Data Transmission Measurement

Uplink RLC Data Transmission Measurement

Cell Performance Measurement

Downlink RLC Data Transmission Measurement




Statistics function type Measure type

Cell Radio Channel Performance Measurement

Resource Maintenance Performance Measurement

PDCH Resource Performance Measurement

PDCH Extremum Value Measurement

Uplink EGPRS TBF Establishment/Release Measurement

Downlink EGPRS TBF Establishment/Release Measurement

Uplink EGPRS RLC Data Transmission Measurement

Downlink EGPRS RLC Data Transmission Measurement

EGPRS GMSK_MEAN_BEP Different Value Measurement

EGPRS 8PSK_MEAN_BEP Different Value Measurement

Uplink GMSK EGPRS RLC Data Retransmission Rate Measurement

Uplink 8PSK EGPRS RLC Data Retransmission Rate Measurement

Downlink GMSK EGPRS RLC Data Retransmission Rate Measurement

Downlink 8PSK EGPRS RLC Data Retransmission Rate Measurement

Set Statistics Item In this step, please set the statistics item of the performance measurement. The lower part of Table 2-3 shows the corresponding interface and Figure 2-1 shows the corresponding description.



Table 2-3 Description on statistics item setting interface

All statistics items All statistics items belonging to the same measure type. The statistics items describe the quantity that should be collected for one measurement task.

Selected statistics items

The statistics items in this list refer to the statistics items to be measured for the performance measurement task. The statistics items not in the list will not be measured.

Please select template

Please select the created statistics item template

After the statistics function type and measure type are definitely selected, all the statistics items will be listed in the lower left part of the interface. Please select the statistics items using the mouse and add them to the selected statistics item list in the lower right part of the

interface using the button .

If the statistics item template has already been defined, please directly select the template for measurement. For example, Figure 2-1 shows the measurement of Maximum CPU occupancy.

Set Time Figure 2-2 shows the interface for setting the measurement time and Table 2-4 shows the description of each domain in the interface.




Figure 2-2 Time definition interface

Table 2-4 Description on each domain in the time definition interface

Domain name

Meaning Range Remarks

Start date The date on which the implementation of a task starts.

xxxx-xx-xx Later than or being the date a task is registered.

Measuring period

The period of statistics data collection.

5-1440 minutes Can be divided exactly by statistics time segment.

Time segment

The start and end time of the time segment in a statistics day

00:00-24:00 None

Limited period task (day)

The preset duration of time the task lasts for.

1-9999 days None

Semi-permanent task

The task will be always under way since its registration.

None None



Domain name

Meaning Range Remarks

Time type The period of the performance measurement task start

Statistic by day, Statistic by week, Statistic by month

Please refer to Caution 2

Please select template

Select the created time template.

Created template None.

When the user fetches the performance statistical result of that day at the OMC console, the start time of the performance measurement is the POMU time, while the end time is the OMC console time (PC time). If there is a relatively great difference between the POMU time and the OMC console time, the performance measurement result will be inaccurate. Therefore, please synchronize the OMC console time with the POMU time. If the user fetches the previous performance statistical result, the OMC console time will not exert any influence upon the correctness of the statistical result. If the time type is selected as “statistic by week”, then the user can select one day or several days in each week for implementing the performance measurement task. If the time type is selected as “statistic by month”, then the user can select one day or several days in each month for implementing the performance measurement task.

As shown in the setting example in Figure 2-2, the performance measurement task starts on March 19 2002. The measurement will be made on seven consecutive days. It will start at 15:00 everyday and be made every five minutes till 20: 00.

Set Object The object definition interface is used to set the performance measurement object, as shown in Figure 2-3. Table 2-5 shows the measurement object of the current statistics function type.




Figure 2-3 Object definition interface

Table 2-5 Statistics function type and its corresponding measurement object

Statistics function type Measurement object Range

CPU Performance Measurement

Board No. Frame No.: always 0. All board numbers, specified board numbers (0-6, 8, 10-15)


BSC No. All BSC Specified BSC No.

NS Performance Measurement

Network service virtual connection identifier (NSVCI)

0 to 65534 All NSVCI


Cell No. All cells Board No. (0-5, 10-15) Specified cell No. Specified BSC No.



Statistics function type Measurement object Range




LAPD link All LAPD links Specified LAPD link No



If the object template has already been defined, please directly select the template for measurement. As shown in the example in Figure 2-3, the CPU Performance Measurement is made on boards 0, 1, 2, 6, 8 and 15 in the PCU processing subrack.

Register Performance Measurement Task After setting the statistics item, measurement time and object, please click the button Register in the lower part of the interface, the Task registration response interface will be popped up, as shown in Figure 2-4. Table 2-6 shows the description of the interface. What Figure 2-4 shows is the interface of successful task registration.

Figure 2-4 Successful task registration interface




Table 2-6 Description of task registration response information

Domain name Meaning

Task registration response Confirm the registration of a task, responding with either the success or failure message of the registration. The causes of registration failures are also displayed in this interface.

Task registration details in each module

Confirm the registration of a task in each module. When a task is registered in several modules, note that if the registration in one module fails, the statistical results will not be reliable.

Module ID. The module number.

Registration status Confirm the registration of a task, responding with either the success or failure message of the registration in a certain module.

The objects failed to be registered in this module

The statistics object is invalid in certain module. For example, if for a task registration the object is No. 7 cell, but No. 7 cell does not exist in the module the task is registered in, then No. 7 cell is the object that failed to be registered in this module.

2.1.2 Deleting Performance Measurement Task Firstly, select the performance measurement task to be deleted. Then, select any of the following three modes to complete the deleting operation:

Selecting the menu Task list

> Delete

Using the key Delete

.

Clicking the button in the toolbar.

2.1.3 Modifying Performance Measurement Task Name This operation should be implemented at the command terminal. And only the user who logs on the system in the senior maintenance mode or above can implement such operation.

Related Command ms rename <TaskNo> <TaskName>

Command Description TaskNo: Task number.

TaskName: Task name after modification.



2.2 Querying Performance Measurement Task This operation can be conducted either at the OMC console or at the command terminal. Since operation at the OMC console is relatively convenient and easy, it is described in the following.

2.2.1 Querying Information and Status of Performance Measurement Task

Querying Task Information Firstly, select the performance measurement task to be viewed.

Selecting the menu Task Management > Details. Use the shortcut key F7.

Enter the Details interface, as shown in Figure 2-5.

Figure 2-5 Task details

The interface of task details includes the following three sub-interfaces:

General task information, including task name, time attribute, etc. Statistics items information, including name and serial No. of statistics items Task objects information, including object No. and object name.

The three sub-interfaces give the relevant information to be set during creation of the performance measurement task.




Querying Task Status To query the task status, please enter the related interface by the following means:

Selecting the menu Task Management > Status Inquiry.

Clicking the button in the tool bar.

View the Task status interface as shown in Figure 2-6.

Figure 2-6 Interface for viewing task status

2.2.2 Querying Statistical Result of Performance Measurement Task

This operation is used to view the statistic task result within the specified range. The user can enter the interface by the following three means.

Selecting the menu Task Management > Get Results. Using the shortcut key F8.

Clicking the button in the tool bar.

Set The Viewing Time In this interface, the user can make setting to view the performance measurement result of the special time and define the result ordering mode, as shown in Figure 2-7.



Figure 2-7 Result time definition interface

View Task Result The task result interface includes three sub-interfaces, such as interfaces Display Results, Details and Chart.

The interface Display Results gives all results in the form of table and each row of the table indicates a group of statistical results. The column title of the table indicates the statistics item name and the row title indicates the statistics time and object, as shown in Figure 2-8.




Figure 2-8 Task result interface

The Details interface gives the information of a piece of statistical result in the form of table, as shown in Figure 2-9. The table includes two columns, such as Statistic item and Result.

Figure 2-9 Interface of details

The measurement time and object are shown above the table. The result status of each module is shown below the table. If the module registered in the task reports the statistical result, then the module status is shown as valid. Otherwise, the status is shown as invalid. You can select the previous or next result using the functional buttons above the table.



The Chart interface gives the statistical result in the form of chart, as shown in Figure 2-10.

Figure 2-10 Data chart interface

Above the chart display area is the chart setting area where the following information can be set:

X-coordinate, indicating statistic by time or by object.

Mode, including curve mode, bar mode and dot mode.

Other attributes, such as Y-coordinate range, 3D display or not, graticule shown or not, and the number of X-coordinates.

The statistics item table below the chart display area is used to specify the statistics item displayed in the chart. The statistics item selected (ticked off) will be shown in this table.

2.3 Setting Performance Measurement Template PCU's performance measurement system provides performance measurement template management function. User can use created template to create tasks with similar properties, thus improving the efficiency of task creation.

There are three types of templates: item template, time template and object template.




2.3.1 Creating Item Template

Access Click Template Management > Item Template.

Or click .

Operation The interface of item template setting is shown in Figure 2-11.

Figure 2-11 Item template setting

In the dialog box above, select the items needed from All statistics items and add them to Selected statistics items. And then, click Save template and type a name for this template in the next dialog box and click OK to finish the creation.

When creating an item template, please make sure that all items of this template belong to the same measurement type.



2.3.2 Creating Time Template

Access Click Template Management > Time Template.

Or click .

Operation The operation of creating time template is similar to the setting of time properties when creating a task. See 2.1.1 “Set Time”.

2.3.3 Creating Object Template

Access Click Template Management > Object Template.

Or click .

Operation The operation of creating object template is similar to the setting of object properties when creating a task. See 2.1.1 “Set Object”.

M900/M1800 Operation Manual - Performance Measurement 3 M2000 Performance Measurement


3 M2000 Performance Measurement

About This Chapter


Title Description

3.1 Performance Measurement Objects

This section decribes the Performance Measurement Objects by M2000 Client.

3.2 Measurement Results Query

This section decribes the Measurement Results Query by M2000 Client.

3.3 Template Management Query

This section decribes the Template Management Query by M2000 Client.

3.4 Measurement Maintenance This section decribes the Measurement Maintenance by M2000 Client.

3.5 Real-Time Measurement Maintenance

This section decribes the Real-Time Measurement Maintenance by M2000 Client.

3.6 Threshold Management This section decribes the Threshold Management by M2000 Client.

3.7 Customer Counter Management

This section decribes the Customer Counter Management by M2000 Client.

3 M2000 Performance Measurement M900/M1800



The command terminal and the OMC maintenance console of the PCU system supports creating and deleting the performance measurement tasks. The M2000 Client does not support these tasks because the NE automatically reports the first object type and the common counter values after the NEs are successfully created on the M2000 Client. These values are performance measurement results. The M2000 Client has only to provide relevant query operations.

3.1 Performance Measurement Objects 3.1.1 Hierarchy of Performance Measurement Objects

Class 1 Objects For class 1 objects, you do not need to specify a measurement object. The system measures all the objects of a certain type by default. The NE reports all the obtained measurement results of all the objects of this type to the M2000. Therefore, you do not need to add these objects manually into the measurement range. For this type of objects, you cannot add or remove them, or select only some of these objects for measurement.

Class 2 Objects For class 2 objects, you need to specify a measurement object. After you add this type of measurement objects into the measurement range, the NE notifies the M2000 of the adding, and the M2000 displays these objects in the Measurement Object Management window.

Class 3 Objects For class 3 objects, you need to type the specific characteristics of the object, because the measurement is based on these characteristics. The M2000 adds this type of objects and notifies the NE, and the NE reports the corresponding measurement results to the M2000.

3.1.2 Hierarchy of Performance Measurement Counters Counters in a measurement function set form multiple measurement units for better utilization and management. Therefore, for one NE type, the measurement counters are organized in the hierarchy of Measurement function set -> Measurement unit -> Measurement counter. In M2000, the measurement counters are organized in the hierarchy of NE type, Measurement function set, Measurement unit, and Measurement counter, as shown in Figure 3-1.



Figure 3-1 Hierarchy of performance measurement counters

NE typeMeasurementfunction set

Measurementunit

Measurementcounter

Measurementcounter 2

Measurementcounter 1

............

Measurementunit 2

Measurementunit1

......

Measurementfunction set 2

Measurementfunction set1

......

NE type 2

NE type 1

Measurementcounter3

Measurementunit n

Measurementfunction setn

NE type n

3.1.3 Type of Performance Measurement Counters

Key Performance Counters The key performance counters are the part continuously measured by the system. You do not have to care whether they are measured. You cannot cancel the measurement of the key performance counters. For a unit to be measured, the NE determines which counters are the key performance counters.

Extension Performance Counters Counters other than the key performance counters are called extension performance counters. You need to set manually whether they are to be measured. You can add or cancel the measurement of the extension performance counters.

User Defined Counters When the M2000 is running, you can perform combined operation on the original system counters to obtain a new measurement counter. The counter generated in this way is called a user defined counter. However, you cannot use it to generate another

3.2 Measurement Results Query Perform the following steps:

Step 1 After logging in to the M2000 Client, choose Performance > Query Result.

The Query Result window is displayed, as shown in Figure 3-2.




Figure 3-2 Query Result

Step 2 Click New Query.

The Query dialog box is displayed, as shown in Figure 3-3.

Figure 3-3 Query

You can set the query conditions as described subsequently.

----End



Selecting Objects In the Query dialog box shown in Figure 3-3, select Object Selection. The available objects are displayed, as shown in Figure 3-4.

Figure 3-4 Object Selection

Table 3-1 lists the measurement function sets and relevant measurement units.

Table 3-1 Measurement function sets and relevant measurement units

Measurement Function Set

Measurement Unit






NS Transmission Performance Measurement



G-Abis interface Performance Measurement






Measurement Unit

















PDCH Maximum Value Measurement

Uplink EGPRS TBF establishment/release Measurement


Uplink EGPRS RLC data Transmission Measurement

Downlink EGPRS RLC data Transmission Measurement

EGPRS GMSK_MEAN_BEP different value Measurement

EGPRS 8PSK_MEAN_BEP different value Measurement

Uplink GMSK EGPRS RLC data retransmission rate measurement

Uplink 8PSK EGPRS RLC data retransmission rate measurement

Downlink GMSK EGPRS RLC data retransmission rate measurement


Downlink 8PSK EGPRS RLC data retransmission rate measurement



Table 3-2 lists the measurement function sets and relevant measurement objects.

Table 3-2 Measurement function sets and relevant measurement objects


Measurement Object

Value Range


Board number Subrack number (0) All the board numbers Specified board numbers (0–6, 8, 10–15)


Network Service Virtual Connection Identity (NSVCI)

0–65534


Cell number All the cells Specified cell number Board numbers (0–5, 10–15) Specified BSC number

G-Abis interface Performance Measurement

Cell number All the cells Board numbers (0–5, 10–15) Specified cell number Specified BSC number


LAPD number All the LAPD links Specified LAPD link number


Cell number All the cells Board numbers (0–5, 10–15) Specified cell number Specified BSC number


BSC number All the BSCs Specified BSC number

Slecting Counters In the Query dialog box shown in Figure 3-3, select Counter Selection. The selected counters are displayed, as shown in Figure 3-5.




Figure 3-5 Counter Selection

Available Counters lists all the current available counters. Selected Counters lists the current selected counters.

Click . The selected counters in Available Counters can be added to Selected Counters.

Click . All the counters in Available Counters can be added to Selected Counters.

Setting Others In the Query dialog box shown in Figure 3-3, select Other Setting. The parameters are displayed, as shown in Figure 3-6.



Figure 3-6 Other Setting

Table 3-3 lists the descriptions of the parameters.

Table 3-3 Description of the parameters

Parameter Value Range Description

Type Consecutive and Fragmental The time mode for querying the results. Consecutive: To query the measurement results within a consecutive time period. Fragmental: To query the measurement results for separate time segments. This time mode applies to querying results for the period with high traffic.

Default All, Specified, Today, Yesterday, This Week, and Last Week

The time range for querying the measurement results. All: To query all the measurement results. Specified: To query the measurement results for the specified time segment.





Start The start time. Default: the day before. When you select "Consecutive" as the time mode, you need to set the start and end time.

Time

End The end time. Default: the current time. When you select "Consecutive" as the time mode, you need to set the start and end time.

When you select "Consecutive" as the time mode, you need to set the start and end time, and the time period. The system provides three time periods. The first is set by default with the start time 00:00 and the end time 24:00. If you need to set more than one time period, select the second and third time periods and set the start and end time.

Query Period 30 minutes, 60 minutes and 24 hours

The M2000 queries and collects the measurement results according to the selected period.

Sort Object, Time and Counter In what sequence the queried measurement results are sorted and displayed.

Setting Filter Conditions In the dialog box shown in Figure 3-6, click Counter Filter. The Set Counter Filter Conditions dialog box is displayed, as shown in Figure 3-7.

Figure 3-7 Set Counter Filter Conditions

You can set the filter conditions for each measurement counter. Only the counter that meets the filter conditions can be displayed.



Table 3-4 lists the description of filter conditions.

Table 3-4 Description of filter conditions


Counter Name All measurement counters of the selected measurement object

Select in the drop-down list the name of the counter for which the filter condition is to be set.

Comparator ">", ">=", "=", "<", and "<=" For comparing the actual value and the compare value of the measurement counter.

Compare Value

–9999999999.98 to 9999999999.98

The measurement counter value set as the filter condition.

Logical Operator

"AND", "OR", and "None" The logical relationship between the set filter conditions.

Click Close in the Set Counter Filter Conditions dialog box after setting the filter conditions. Then click Query in the dialog box as shown in Figure 3-6.

Some counters can only be displayed after period query.

3.2.1 Setting up a Real-Time Measurement Query Task In the Query Result dialog box shown in Figure 2-1, click Real Query. The Add Real-Time Query Task window is displayed.

The operation of setting up a real-time measurement query task is the same as that of setting up a query task. But the value range of "Measurement Cycle" is different. When setting up a real-time measurement query task, the period can only be "5 minutes" or "15 minutes".

3.2.2 Querying Through Templates In the Query Result window shown in Figure 2-1, right-click a template and select Query in the floating menu. The query results are displayed in the column on the right, as shown in Figure 3-8.




Figure 3-8 Querying Through Templates

3.2.3 Displaying the Query Results The query results are displayed in three ways: table, line chart, and bar chart.



Displaying Query Results in Table

Figure 3-9 Displaying query results in table

Click Save. The query results are exported in the format of *.xls, *.txt, *.html.




Displaying Query Results in Line Chart

Figure 3-10 Displaying query Results in line chart

Different objects have different colors. You can set the color and background color of the objects. The line chart can be zoomed in or out.

Click Save. The query results are exported in the format of *.bmp and *.jpg.



Displaying Query Results in Bar Chart

Figure 3-11 Displaying query results in bar chart

Different objects have different colors. You can set the color and background of the objects. The bar chart can be zoomed in or out.

Click Save. The query results are exported in the format of *.bmp and *.jpg.

3.3 Template Management Query 3.3.1 Creating a Query Template

After setting the query conditions, click Save Template. The Save as dialog box is displayed, as shown in Figure 3-12. Type the template name and then select a directory. Click OK.

The template name cannot be the used one.




Figure 3-12 Saving the template

3.3.2 Modifying a Query Template

Modifying the Template Name In the Query Result window shown in Figure 2-1, right-click the template to be modified, and select Rename.

The template name cannot be the used one.

Modifying the Attributes of the Template In the Query Result window shown in Figure 2-1, right-click the template to be queried, and select Attribute, as shown in Figure 3-13.



Figure 3-13 Modifying template attributes

After modifying the attributes, click Save. Click Save as to save the modified results to a new template.

3.3.3 Viewing a Query Template In the Query Result window shown in Figure 2-1, right-click the template to be viewed and select View.

3.3.4 Deleting a Query Template In the Query Result window shown in Figure 2-1, right-click the template to be deleted and select Delete. A confirmation dialog box is displayed. Click OK.

3.3.5 Managing the Sub-Catalog The M2000 Client provides sub-catalog management function to help the users manage the user-defined query templates more easily.

Setting up a Sub-Catalog Perform the following steps:

Step 1 In the window as shown in Figure 2-1, right-click a node in the template tree.

Step 2 Select Create Dir in the floating menu, as shown in Figure 3-14.




Figure 3-14 Creating Dir menu option

Step 3 Type the name of the sub-catalog on the newly created node and press Enter, as shown in Figure 3-15.



Figure 3-15 Typing the name of the newly created sub-catalog

----End

Re-Name the Sub-Catalog Perform the following steps:

Step 1 In the window as shown in Figure 2-1, right-click the node to be re-named in the template tree.

Step 2 Select Rename in the floating menu.

Step 3 Type the new name of the sub-catalog.

----End

Deleting a Sub-Catalog Perform the following steps:

Step 1 In the window as shown in Figure 2-1, right-click the node to be deleted in the template tree.

Step 2 Select Delete in the floating menu.

A confirmation dialog box is displayed.

Step 3 Click OK.




All the templates in the sub-catalog are deleted if it is deleted.

----End

3.4 Measurement Maintenance 3.4.1 Querying the Measurement Counters and Objects

Perform the following steps:

Step 1 Choose Performance > Measure Management.

The Measure Management window is displayed, as shown in Figure 3-16.

Step 2 Select an NE under a node.

Figure 3-16 Measure Management

Table 3-5 and Table 3-6 list the description of the parameters on in the Measure Management window.

Table 3-5 Parameters in Counter Info

Parameter Description

Counter Name Enumeration. All currently measured counters under a measurement unit of an NE.



Parameter Description

Status Measurement status of the counter.

Status Description Information Describes the counter measurement status.

Table 3-6 Parameters in Object Info

Parameters Description

Object Name Enumeration. All currently measured objects under a measurement unit of an NE.

Status Measurement status of the object.

Status Description Information Describes the counter measurement status.

3.4.2 Querying Missing Measurement Results During the running of the M2000, many reasons may cause the loss of the measurement results. For example, when the M2000 NE is disconnected for a period of time. For these missing measurement results, the M2000 provides the querying and recollecting functions.

Step 1 In the window as shown in Figure 3-16, click LostResult….

The Please Select Time Segment dialog box is displayed, as shown in Figure 3-17.

Figure 3-17 Please Select Time Segment

Step 2 Select the start and end time.

Step 3 Click OK.

If the measurement results in the set time period are lost, a confirmation dialog box is displayed, describing details of the lost measurement results, as shown in Figure 3-18.




Figure 3-18 Missing Result Inquiry (1)

If no measurement results in the set time period are lost, a prompt is returned, indicating no result is missing, as shown in Figure 3-19.

Figure 3-19 Missing Result Inquiry (2)

----End

3.4.3 Synchronizing Measurement Results If some performance measurement results are lost, you can get them back from the NE by synchronizing results of the periodic measurement.

Step 1 In the window as shown in Figure 3-16, click Sync….



The start and end time is when the measurement results are lost.

Step 3 Click OK.

Step 4 If operation succeeds, a prompt is returned.



----End

3.4.4 Subscribing to Measurement Results To facilitate querying the periodic measurement results, you can subscribe to the measurement results according to the object or the counter.

Step 1 Choose Performance > Measure Management or click .

The Measure Management window is displayed.

Step 2 In the tree on the left on Measure Management, select an NE type node.

Step 3 In the right part on Measurement Maintenance, select the tab for the corresponding periodic measurement to subscribe to the measurement results.

The tab is named after the measurement period of the measurement counters.

Step 4 Click Subscribe.

The Subscribe Result window is displayed. The newly reported measurement results are displayed in the window, as shown in Figure 3-20.

Figure 3-20 Newly reported measurement results

For each periodic measurement, you can subscribe measurement results of up to five measurement

units. Up to 500 newly reported measurement results for each measurement unit can be displayed in the Subscribe Result window. If there are more than 500 results for a measurement unit, results reported earlier are not displayed but saved in the system.

To unsubscribe the measurement results for a measurement unit, select the tab in Subscribe Result corresponding to this measurement unit, and then click Unsubscribe.

You cannot subscribe the results of the NE in the status of Unmeasured.

----End




3.4.5 Querying the Reliability of Measurement Results When the NE reports measurement results, the reliability information is contained in the measurement results, indicating whether these results are Reliable or Unreliable. If the data in the measurement result is described as Unreliable, this result record is considered Unreliable.

The measurement result reliability is expressed by the rate of Unreliable results against all the measurement results. In the M2000, this rate is expressed in percentage.

To query the reliability of measurement results, perform the following steps:

Step 1 In the window as shown in Figure 3-16, click Reliability.



Step 3 Click OK.

If the reliability of the measurement result is 100%, as shown in Figure 3-21, click OK. The dialog box is closed.

If the reliability of the measurement result is lower than 100%, as shown in Figure 3-22, click OK. The Unreliable Result Info is displayed, as shown in Figure 3-23.

Figure 3-21 Result reliability (100%)

Figure 3-22 Result reliability (lower than 100%)



Figure 3-23 Unreliable Result Info

----End

3.4.6 Suspending NE Measurement The measurement status refers to whether to collect from the NE the setting status (Suspended and Activated) of measurement results. You can set one or more Activated NEs under a measurement unit to Suspended. The suspended NEs cannot generate results.

3.4.7 Recovering NE Measurement You can recover a suspended NE. The recovered NE continues to generate the measurement results and reports the results to the M2000.

In the Measure Management window, select the NE to be recovered and click Active.

3.5 Real-Time Measurement Maintenance The real-time measurement maintenance is similar to the measurement tasks. The difference lies in the value range of the measurement cycle.

The cycle of the real-time measurement maintenance is five minutes or 15 minutes. The cycle of a measurement task is 30 minutes, 60 minutes, or 24 hours.




3.6 Threshold Management For measurements of different periods, the M2000 supports counter value threshold alarms. The alarm function helps to monitor automatically the key performance counters and the currently measured extension counters. You can set the alarm threshold of every periodic measurement according to the actual situation. When the counter value exceeds this threshold, the system generates an alarm.

For one counter, you can set alarm thresholds for various time periods, or an alarm threshold for all time periods in every periodic measurement. These thresholds can be set for all objects of a measurement type, or for one or more objects.

Choose Performance > Threshold Setting. The Threshold Setting window is displayed, as shown in Figure 3-24.

Figure 3-24 Threshold Setting

3.6.1 Adding Thresholds Perform the following steps:

Step 1 In the window as shown in Figure 3-24, click Add.

The Add Threshold dialog box is displayed, as shown in Figure 3-25.



Figure 3-25 Add Threshold

Table 3-7 describes the parameters in the Add Threshold dialog box.

Table 3-7 Threshold Parameters


Select Object

Enumeration. All counters in the measurement unit.

You can set a threshold for all the objects, or for one or more objects.

Counter Name

Enumeration. Key performance counters and currently measured extension performance counters in the measurement unit.

Name of the counter with the threshold to be set. Click the dropdown list after Counter Name, and select the counter to set the threshold.

Direction Enumeration. Increasing, Descreasing.

"Value", "Hysterisis", and "Direction" determine the value of a counter threshold altogether.

Status Enumeration. Active, Inactive.

This parameter determines whether to activate the threshold alarm when the counter value exceeds the value range.

Time Segment

00:00–24:00 Indicates in which time segment of a day this performance threshold setting is valid.

Period Enumeration. "30 Minutes", "60 Minutes", and "24 Hours".

This means to set the threshold for which of the 30-minute, 60-minute and 24-hour periodic measurements.





Value Numeric "Value", "Hysteresis", and "Direction" determine the value of a counter threshold altogether.

Hysteresis Numeric "Value", "Hysteresis", and "Direction" determine the value of a counter threshold altogether.

Alarm Level

Enumeration. Critical, Major, Minor, Warning.

Level of the threshold alarms.

3.6.2 Modifying Thresholds Perform the following steps:

Step 1 In the window as shown in Figure 3-24, select the threshold to be modified.

Step 2 Click Modify.

The Modify Threshold dialog box is displayed, as shown in Figure 3-26.

The Select Object and Counter Name cannot be modified.

Figure 3-26 Modify Threshold

----End



3.6.3 Deleting Thresholds Perform the following steps:

Step 1 In the window as shown in Figure 3-24, select the threshold to be modified and click Delete.


Step 2 Click OK.

----End

3.6.4 Suspending Thresholds When a threshold setting is currently not needed, you can suspend it.

In the window as shown in Figure 3-24, select the threshold to be modified and click Suspend.

3.6.5 Activating Thresholds You can activate a suspended threshold setting.

In the window as shown in Figure 3-24, select the threshold to be modified and click Activate.

3.7 Customer Counter Management The customer counter management is used to manage the key counters, two categories counter: the system counter and the user defined counter. The system counter is obtained when the system performs the logic operation on the original counters in the system by default. It is attached with the system.

When the M2000 is running, you can perform a logic operation on the original system counters to obtain a new measurement counter. The counter generated in this way is called the user defined counter. The customer counter applies only to the periodic measurement results. The customer counter is measured only when all the original counters contained in the formula are measured. The customer counter cannot be used to create other user defined counters.

Choose Performance > Customer Counter management.

The Customer Counter Management window is displayed, as shown in Figure 3-27.




Figure 3-27 Customer Counter Management

3.7.1 Creating a User-Defined Counter Perform the following steps:

Step 1 In the window as shown in Figure 3-27, select an NE in the tree on the left.

Step 2 Click Add.

The Add User Defined Counter dialog box is displayed, as shown in Figure 3-28.



Figure 3-28 Add User Defined Counter

Table 3-8 lists the description of the parameters in the Add User Defined Counter dialog box.

Table 3-8 Description of the parameters in the Add User Defined Counter dialog box


Counter Name

100 characters at most. Cannot be null.

The name of a user defined counter. A meaningful name is recommended.

Unit Default: none. Units of the existing counters are available. You can select a unit from the drop-down list according to the meaning of the user defined counter. For example, if a user defined counter measures the times of the occurrence, the unit can be "times". The unit specified for a user defined counter measures the times of the occurrence, the unit can be "Times". The unit specified for an user defined counter is for referenced purpose only. It does not affect the calculation of the counter.

Calculation Formula

255 characters at most. Cannot be null.

Formula for the user defined counter. For details, see 3.7.7 "Editing the Formula for the User-Defined Counter."

When the user-defined counter is successfully created, it is displayed on the left of the window as shown in Figure 3-27.




When creating a user defined counter, you need to specify it to a measurement function set and

measurement unit. A measurement unit contains at most 100 user defined counters. All primitive counters of a user defined counter must belong to the same measurement function set. You cannot create a user defined counter from another user defined counter.

You can create user defined counters in batch by importing the user defined counter information. You cannot create a user defined counter from primitive counters, none of which is supported by at

least one version of an NE. This window does not close after you create a user defined counter. When creation failed, a prompt

is returned.

----End

3.7.2 Modifying a User-Defined Counter Perform the following steps:

Step 1 In the window as shown in Figure 3-27, select the user-defined counter to be modified.

Step 2 Click Modify….

The Add User Defined Counter dialog box is displayed, as shown in Figure 3-28.

Step 3 After modifying the user-defined counter, click Modify.

----End

3.7.3 Deleting a User-Defined Counter Perform the following steps:

Step 1 In the window as shown in Figure 3-27,select the user-defined counter to be deleted.

Step 2 Click Delete.


Step 3 Click OK.

----End

3.7.4 Importing a User-Defined Counter Perform the following steps:

Step 1 In the window as shown in Figure 3-27, click Import….

A dialog box is displayed.

Step 2 Find the file to be imported and click Open.

If importing succeeds, a prompt is returned.

----End



3.7.5 Exporting a User-Defined Counter Perform the following steps:

Step 1 In the window as shown in Figure 3-27, click Export….

A dialog box is displayed.

Step 2 Select the saving directory for the file and click Save.

If saving succeeds, a prompt is returned.

----End

3.7.6 Showing or Hiding a User-Defined Counter In the window as shown in Figure 3-27, you can select the user-defined counters to be shown or hidden in the Show All Customer Counters check box. The system shows the user-defined counters by default.

3.7.7 Editing the Formula for the User-Defined Counter The user-defined counters are calculated through a formula. The formula defines the calculation principles.

Principles The editing principles are as follows:

Supporting arithmetic operations (add, subtract, multiply, and divide). Supporting symbols such as "+", "–", "*", "/", "(", and ")". The measurement counters are identified by measurement counter ID. The counter ID is

added "[]" You can directly type the constant with the symbol "{}". In the formula, {GP} indicates the measurement cycle of the user-defined counter. If the

measurement cycle is 60, the value of the {GP} is 60.

For example, in "([198615] + ([198617]-[198618])*{100}/ [198615])*{GP}",

"[198615]", "[198617]", and "[198618]" represent the measurement counters with the IDs 198615, 198617, and 198618.

{100} indicates constant 100. {GP} indicates the measurement cycle of the user-defined counter.

Points for Attention You can type the calculation symbols, constant, and {GP} or by the button. You can directly type the ID of the measurement counters or double-click the

measurement counters in the "counter list". When a user-defined counter is defined, the M2000 cannot detect the consistency of the

data, so you must ensure the correctness of the formula. The constant is a number with at most tem characters and cannot be 0.

M900/M1800 Operation Manual - Performance Measurement 4 Performance Measurement Tasks


4 Performance Measurement Tasks

About This Chapter


Title Description

4.1 Instructions of Performance Measurement Task

This section decribes the Instructions of Performance Measurement Task.

4.2 CPU Performance Measurement

This section decribes the CPU performance measurement.

4.3 BSC Overall Performance Measurement

This section decribes the BSC overall performance measurement.

4.4 NS Performance Measurement

This section decribes the Ns transmission performance measurement.

4.5 BSSGP Performance Measurement

This section decribes the BSSGP performance measurement.

4.6 G-Abis Interface Performance Measurement

This section decribes the G-Abis Interface Performance Measurement.

4.7 Pb Interface Performance Measurement

This section decribes the Pb Interface Performance Measurement.

4.8 Cell Performance Measurement

This section decribes the Cell Performance Measurement.

4 Performance Measurement Tasks M900/M1800



4.1 Instructions of Performance Measurement Task 4.1.1 Classification of Performance Measurement Items

The PCU system provides full line of performance measurement items which can be functionally divided into the following types:

Traffic model creating type Different from the radio circuit switched service and the wired packet switched service, the radio packet data service still does not have typical traffic model at present. To help the network equipment operator to accumulate data so as to establish the service model, Huawei PCU system provides related performance measurement items.

Network performance optimization type After established, the GPRS network may become below the actual requirements due to city construction, transfer of downtown or change of user quantity. Huawei PCU system provides related performance measurement items that can keep the network operator synchronously informed of any traffic change. Accordingly, the operator can optimize the GPRS network in time.

Fault handling type The performance measurement plays an important role in fault locating of the PCU system. The results obtained from a period of measurement on the PCU system can provide reliable support for fault handling.

Recommendations and Cautions on Creating Performance Measurement Task The PCU system provides various performance measurement items. In practice, Huawei recommends the following types of performance measurement tasks:

Step 1 Traffic model creating type

Packet Access Performance Measurement on CCCH Packet Access Performance Measurement on PACCH

For the above measurement items, it is recommended the performance measurement task be created in a 60-minute cycle.

Step 2 Network performance optimization type

TRAU Link Measurement LAPD Link Measurement Rate of Successful Packet Assignment Uplink TBF Establishment/Release Measurement Downlink TBF Establishment/Release Measurement Uplink RLC Data Transmission Measurement (at CS-1 and CS-2) Downlink RLC Data Transmission Measurement (at CS-1 and CS-2)

For the above measurement items, it is recommended the performance measurement task be created in a 1440-minutes (one-day) cycle.



Too many performance measurement tasks will consume too much resource of the PCU system. If finding that the CPU occupancy is too high for a long time, please delete some performance measurement tasks.

----End

4.2 CPU Performance Measurement Table 4-1 lists the measurement items of the CPU performance measurement.

Table 4-1 CPU performance Measurement

No. Measurement item

1 Average CPU Occupancy (%)

2 Maximum CPU Occupancy (%)

The object of the measurement is board, which includes POMU and RPPU. The maximum CPU occupancy of one or more boards should only be measured in one task.

The measured value reflects the CPU load of the board. If the CPU occupancy exceeds the reference range, the CPU system may be unstable.

4.2.1 Average CPU Occupancy (%)

Description This measurement item is used to measure the percentage of the CPU in non-idle state.

Measurement Point To measure all sampled CPU occupancies during the measuring period as follow:

%100_

×=PeriodSampling

PeriodSamplingDuringTimeCPUIdleNonOccupancyCPU

Obtain and accumulate CPU occupancy during sampling period for N times during the measuring period, and the Average CPU occupancy (%) is equal to the total number of CPU occupancy (%) divided by N.

Effect of the Item It reflects the running situation of CPU system of the measured board.




Huawei Recommendation Normally, the value of average CPU occupancy is not above 50%.

If the value of average CPU occupancy is above 80%, it means that the measured board probably overload, which may impact upon the provision of the GPRS, while if the value of average CPU occupancy is lower than 5%, it means that the measured board is probably no traffic.

However, if the value of average CPU occupancy is above 80% occasionally, the normal running of the system will not be affected.

Check whether the operations such as FTP, performance measurement task register and file operating are being implemented. If so, terminate the operations, or else, please check other performance measurements to confirm whether it is due to heavy traffic. If the traffic is too much heavy, system expansion is recommended.

4.2.2 Maximum CPU Occupancy (%)

Description This statistics item is used to measure the maximum CPU occupancy during the measuring period.

Measurement Point To measure all sampled CPU occupancies during the measuring period comparatively and fetch the maximum value.

Effect of the Item None

Huawei Recommendation None

4.3 BSC Overall Performance Measurement Table 4-2 lists the measurement items of the BSC overall performance measurement.

Table 4-2 BSC over performance measurement


1 Number of Uplink TBF Establishment Attempts

2 Number of Successful Uplink TBF Establishment

3 Number of Uplink TBF Normal Release

4 Number of Downlink TBF Establishment Attempts

5 Number of Successful Downlink TBF Establishment




6 Number of Downlink TBF Normal Release

7 Total Number of Uplink LLC_PDUs Sent

8 Total Bytes of Uplink LLC_PDUs Sent

9 Total Number of Downlink LLC_PDUs Received

10 Total Bytes of Downlink LLC_PDUs Received

11 Number of Packet Paging Requests Sent

12 Number of Circuit Paging Requests Sent

13 Mean Number of Available PDCHs

14 Mean Number of Occupied PDCHs

The object of the measurement is BSC.

The BSC overall performance analysis is to check the overall running state of the BSS. If any data is abnormal, which means the network quality is poor, the cell-level traffic analysis should be executed to improve the network quality. The main analysis items are congestion rate and call-drop rate.

The results of the measurement are used to:

Step 1 Analyze the traffic load of GPRS BSS. By observing a daily or weekly trend of the results, the information may be used to determine the traffic load model for engineering design and network planning. For example as follows:

Traffic load model: Number of Uplink TBF Establishment Attempts and Number of Downlink TBF Establishment Attempts;

GPRS output: Total Number of Uplink LLC_PDUs Sent, Total Bytes of Uplink LLC_PDUs Sent, Total Number of Downlink LLC_PDUs Received and Total Bytes of Downlink LLC_PDUs Received;

Paging load: Number of Circuit Paging Requests Sent and Number of Packet Paging Requests Sent;

Packet channel resource: Mean Number of Available PDCHs and Mean Number of Occupied PDCHs.

Step 2 Analyze the QoS of GPRS BSS. If the measurement result exceeds the reference range, the radio environment, network parameter configuration, network resource configuration and network equipment should be optimized, such as Number of Successful Uplink TBF Establishment, Number of Successful Downlink TBF Establishment, Number of Uplink TBF Normal Release and Number of Downlink TBF Normal Release.

----End

4.3.1 Number of Uplink TBF Establishment Attempts Please refer to the instruction of the item “Cell Performance Measurement->Number of Uplink TBF Establishment Attempts”, while the only difference is that the measurement




object is the whole BSC, which including all the cells providing packet service that configured in the BSC.

4.3.2 Number of Successful Uplink TBF Establishment Please refer to the instruction of the item “Cell Performance Measurement-> Number of Successful Uplink TBF Establishment”, while the only difference is that the measurement object is the whole BSC, which including all the cells providing packet service that configured in the BSC.

Please refer to 6.2.1 “Analyzing the Network Congestion Rate” for recommendation.

4.3.3 Number of Uplink TBF Normal Release Please refer to the instruction of the item “Cell Performance Measurement->Number of Uplink TBF Normal Release”, while the only difference is that the measurement object is the whole BSC, which including all the cells providing packet service that configured in the BSC.

Please refer to 6.2.2 “Analyzing the Network Call-drop Rate” for recommendation.

4.3.4 Number of Downlink TBF Establishment Attempts Please refer to the instruction of the item “Cell Performance Measurement-> Number of Downlink TBF Establishment Attempts”, while the only difference is that the measurement object is the whole BSC, which including all the cells providing packet service that configured in the BSC.

4.3.5 Number of Successful Downlink TBF Establishment Please refer to the instruction of the item “Cell Performance Measurement-> Number of Successful Downlink TBF Establishment”, while the only difference is that the measurement object is the whole BSC, which including all the cells providing packet service that configured in the BSC.

Please refer to 6.2.1 “Analyzing the Network Congestion Rate”for recommendation.

4.3.6 Number of Downlink TBF Normal Release Please refer to the instruction of the item “Cell Performance Measurement-> Number of Downlink TBF Normal Release”, while the only difference is that the measurement object is the whole BSC, which including all the cells providing packet service that configured in the BSC.

Please refer to 6.2.2 “Analyzing the Network Call-drop Rate” for recommendation.

4.3.7 Total Number of Uplink LLC_PDUs Sent Please refer to the instruction of the item “Cell Performance Measurement-> Total Number of Uplink LLC_PDUs Sent”, while the only difference is that the measurement object is the whole BSC, which including all the cells providing packet service that configured in the BSC.

4.3.8 Total Bytes of Uplink LLC_PDUs Sent Please refer to the instruction of the item “Cell Performance Measurement-> Total Bytes of Uplink LLC_PDUs Sent”, while the only difference is that the measurement object is the whole BSC, which including all the cells providing packet service that configured in the BSC.



4.3.9 Total Number of Downlink LLC_PDUs Received Please refer to the instruction of the item “Cell Performance Measurement-> Total Number of Downlink LLC_PDUs Received”, while the only difference is that the measurement object is the whole BSC, which including all the cells providing packet service that configured in the BSC.

4.3.10 Total Bytes of Downlink LLC_PDUs Received Please refer to the instruction of the item “Cell Performance Measurement-> Total Bytes of Downlink LLC_PDUs Received”, while the only difference is that the measurement object is the whole BSC, which including all the cells providing packet service that configured in the BSC.

4.3.11 Number of Packet Paging Requests Sent Please refer to the instruction of the item “Cell Performance Measurement-> Number of Packet Paging Requests Sent”, while the only difference is that the measurement object is the whole BSC, which including all the cells providing packet service that configured in the BSC.

4.3.12 Number of Circuit Paging Requests Sent Please refer to the instruction of the item “Cell Performance Measurement-> Number of Circuit Paging Requests Sent”, while the only difference is that the measurement object is the whole BSC, which including all the cells providing packet service that configured in the BSC.

4.3.13 Mean Number of Available PDCHs Please refer to the instruction of the item “Cell Performance Measurement-> Mean Number of Available PDCHs”, while the only difference is that the measurement object is the whole BSC, which including all the cells providing packet service that configured in the BSC.

Please refer to 6.3 “Analyzing the Data of PDCH” for recommendation.

4.3.14 Mean Number of Occupied PDCHs Please refer to the instruction of the item “Cell Performance Measurement-> Mean Number of Occupied PDCHs”, while the only difference is that the measurement object is the whole BSC, which including all the cells providing packet service that configured in the BSC.

Please refer to 6.3 “Analyzing the Data of PDCH” for recommendation.

4.4 NS Performance Measurement 4.4.1 NS Transmission Performance Measurement

Table 4-3 lists the measurement items of the Ns transmission performance measurement.




Table 4-3 NS transmission performance measurement


1 Number of NS PDUs Sent by NS Sublayer

2 Number of NS PDUs Received by NS Sublayer

3 Number of NS PDUs Discarded by NS Sublayer

4 Total Bytes of NS PDUs Sent by NS Sublayer

5 Total Bytes NS PDUs Received by NS Sublayer

6 Number of RESET Messages Sent by NS Sublayer to Peer End

7 Number of RESET ACK Messages Received from Peer End

8 Number of RESET Messages Received by NS Sublayer from Peer End

9 Number of RESET ACK Messages Sent by NS Sublayer to Peer End

10 Number of BLOCK Messages Sent by NS Sublayer to Peer End

11 Number of BLOCK ACK Messages Received from Peer End

12 Number of BLOCK Messages Received from Peer End

13 Number of BLOCK ACK Messages Sent by NS Sublayer to Peer End

14 Number of UNBLOCK Messages Sent by NS Sublayer to Peer End

15 Number of UNBLOCK ACK Messages Received from Peer End

16 Number of UNBLOCK Messages Received from Peer

17 Number of UNBLOCK ACK Messages Sent by NS Sublayer to Peer End

18 Peak Throughput(Bytes) of the Sent NS PDU

19 Peak Throughput(Bytes) of the Received NS PDU

The object of the measurement is NSVC.

The results of the measurement are used to:

Step 1 Analyze the traffic load of GPRS BSS. By observing a daily or weekly trend of the results, the information may be used to determine the traffic load model for engineering design and network planning. For example, Number of NS PDUs sent by NS sublayer reflects the load sharing condition of NS sub-layer.

Step 2 Monitor the service of NS layer of Gb interface.

Analyze the available transmission bandwidth of NS layer. If the value of Number of NS PDUs discarded by NS sublayer is relatively high and if each NSVC in the same NSE is in normal state, it can be concluded that the available transmission bandwidth at the NS layer is insufficient and that packet discarding is due to such insufficiency. Therefore, the available timeslot of the BC should be increased.

Get reset information in Gb interface from the items such as Number of RESET Messages Received by NS Sublayer from Peer End, etc.



Get the block and unblock information of NS layer of Gb interface from the items such as Number of BLOCK Messages Received from Peer End, etc.

----End

Number of NS PDUs Sent by NS Sublayer Description

This statistics item is used to measure the total number of sent NS PDUs in a certain NSVC during the measuring period.

Measurement Point During measuring period, there are two types of measure point:

When receiving NS PDUs from higher layer (here referring to the BSSGP layer), the local Gb board will first find available NSVC to send the NS PDUs. If failed, PCU will send these NS PDUs to other Gb board to choose another available NSVC to send the NS PDUs.

When receiving NS PDUs transmit from other Gb board, local Gb board will first find available NSVC to send the NS PDUs.

There are three reasons for local Gb board to receive NS PDUs from other Gb board:

− Sending from other Gb board because of transmit failure; − Sending from other Gb board because of traffic congestion; − Sending from other Gb board because of normal reason; After successfully sending this NS PDUs through one NSVC, the measured value of the NSVC will be increased by one.



Number of NS PDUs Received by NS Sublayer Description

This statistics item is used to measure the total number of the received NS PDUs in a certain NSVC during the measuring period.

Measurement Point During measuring period, when receiving NS PDUs from lower layer (here referring to Frame Relay layer), before sending this NS PDUs to higher layer (here referring to BSSGP layer), the measured value will be increased by one.

Effect of the Item It reflects downlink NS PDU throughput of every measured NSVC in NS layer.


Number of NS PDUs Discarded by NS Sublayer Description

This statistics item is used to measure the total number of the discarded NS PDUs in a certain NSE during the measuring period.




Measurement Point When receiving NS PDUs from higher layer (here referring to the BSSGP layer), the local Gb board will first find available NSVC to send the NS PDUs. If failed, PCU will send these NS PDUs to other Gb board to choose another available NSVC to send the NS PDUs. There are three reasons for local Gb board to receive NS PDUs from other Gb board: − Sending from other Gb board because of transmit failure; − Sending from other Gb board because of traffic congestion; − Sending from other Gb board because of normal reason; If failure still occurs in finding other Gb board or another available NSVC, PCU will discard this NS PDU through the first NSVC configured in the certain NSE, and the measured value of the NSVC will be increased by one.

Effect of the Item It reflects uplink NS PDU transmission failure caused by traffic congestion or NSVC link fault in NS layer, which will impact upon the performance of packet service.

Huawei Recommendation If the value of Number of NS PDUs Discarded by NS Sublayer is relatively high compared to the value of Number of NS PDUs Sent by NS Sublayer, check and confirm normal state in every NSVC configured in the certain NSE first. Then check other performance measurements to confirm whether it is due to heavy traffic, which will cause NSVC congestion all the time. If the traffic is too much heavy, system expansion in Gb interface is recommended.

Total Bytes of NS PDUs Sent by NS Sublayer Description

This statistics item is used to measure the number of total bytes number of NS PDUs sent in a certain NSVC during the measuring period.

Measurement Point During measuring period, there are two type of measure point: 1. When receiving NS PDUs from higher layer (here referring to the BSSGP layer), the local G board will first find available NSVC to send the NS PDUs. If failed, PCU will send these NS PDUs to other Gb board to choose another available NSVC to send the NS PDUs. There are three reasons for local Gb board to receive NS PDUs from other Gb board: − Sending from other Gb board because of transmit failure; − Sending from other Gb board because of traffic congestion; − Sending from other Gb board because of normal reason; 2. When receiving NS PDUs transmit from other Gb board, local Gb board will first find available NSVC to send the NS PDUs. After successfully sending this NS PDUs, the measured value will be increased by the size of the sending NS PDUs.

Effect of the Item It reflects uplink NS PDU throughput of every measured NSVC in NS layer. This item can reflect the Mean Downlink NS_PDUs Throughput, which is used to measure the mean payload of the downlink NS PDU throughput of every NSVC at the NS layer during the measuring period.



( ) 6010248/_ ××

×= PeriodMeasuringSublayerNSbySentPDUsNSofBytesTotalskbitsThroughputPDUsNSDownlinkMean

Huawei Recommendation

None

Total Bytes NS PDUs Received by NS Sublayer Description

This statistics item is used to measure the total byte number of received NS PDUs in a certain NSVC during the measuring period.

Measurement Point During measuring period, when receiving NS PDUs from lower layer (here referring to Frame Relay layer), before sending this NS PDUs to higher layer (here referring to BSSGP layer), the measured value will be increased by the size of the sending NS PDUs.

Effect of the Item It reflects downlink NS PDU throughput of every measured NSVC in NS layer.


Number of RESET Messages Sent by NS Sublayer to Peer End Description

This statistics item is used to measure the number of RESET messages sent from the local end to the SGSN for NSVC resetting during the measuring period.

Measurement Point Both PCU and SGSN can notify each other to reset some NSVC. When PCU originates to reset some NSVC, a NSVC RESET message will be sent to SGSN, as the measurement point A referred in Figure 4-1, and the measured value will be increased by one.

Figure 4-1 NSVC reset procedure originated by PCU

PCU SGSN

A

B

NSVC RESET

NSVC RESET ACK

Effect of the Item




None Huawei Recommendation

If the measured value is relatively high, it is caused by fault in physical link of the Gb interface, Data configuration error or data configuration of PCU inconsistency with that of SGSN. As a result, please check the link state of the Gb interface and related data configuration to exclude this problem.

Number of RESET ACK Messages Received from Peer End Description

This statistics item is used to measure the number of RESET ACK messages received at the local end from the SGSN during the measuring period.

Measurement Point Both PCU and SGSN can notify each other to reset some NSVC. When PCU originates to reset some NSVC, a NSVC RESET message will be sent to SGSN. When the NSVC RESET ACK message is received by PCU from the peer end, as the measurement point B referred in Figure 4-1, this measured value will be increased by one.


Huawei Recommendation The Number of RESET ACK Messages Received from Peer End should be equal to Number of RESET ACK Messages Sent by NS Sublayer to Peer End. If not equal, please check the link state of the Gb interface and related data configuration.

Number of RESET Messages Received by NS Sublayer from Peer End Description

This statistics item is used to measure the number of RESET messages received at the local end from the SGSN during the measuring period.

Measurement Point Both PCU and SGSN can notify each other to reset some NSVC. When SGSN originates to reset some NSVC, a NSVC RESET message will be received by PCU, as the measurement point A referred in Figure 4-2, and the measured value will be increased by one.



Figure 4-2 NSVC reset procedure originated by SGSN

PCU SGSN

A

B

NSVC RESET

NSVC RESET ACK


Huawei Recommendation If the measured value is relatively high, it is caused by fault in physical link of the Gb, Data configuration error or data configuration of PCU inconsistence with that of SGSN. As a result, please check the link state of the Gb interface and related data configuration to exclude this problem.

Number of RESET ACK Messages Sent by NS Sublayer to Peer End Description

This statistics item is used to measure the number of RESET ACK messages sent from the local end to the SGSN during the measuring period.

Measurement Point Both PCU and SGSN can notify each other to reset some NSVC. When SGSN originates to reset some NSVC, a NSVC RESET message will be received by PCU. When the NSVC RESET ACK message is sent by PCU from the peer end, as the measurement point B referred in Figure 4-2, this measured value will be increased by one.


Huawei Recommendation The Number of RESET ACK Messages Sent by NS Sublayer to Peer End should be equal to Number of RESET Messages Received by NS Sublayer from Peer End. If not equal, please check the link state of the Gb interface and related data configuration.

Number of BLOCK Messages Sent by NS Sublayer to Peer End Description

This statistics item is used to measure the number of BLOCK messages sent from the local end to the SGSN during the measuring period.

Measurement Point




Both PCU and SGSN can notify each other to block some NSVC. When PCU originates to block some NSVC, a NSVC BLOCK message will be sent to SGSN, as the measurement point A referred in Figure 4-3, and the measured value will be increased by one.

Figure 4-3 NSVC block procedure originated by PCU

PCU SGSN

A

B

NSVC BLOCK

NSVC BLOCK ACK


Huawei Recommendation The possible reasons of NSVC block procedure originated by PCU include: physical link fault of the Gb interface, data configuration error of the physical link, NSVC blocking initiated by the OM, or NSVC data configuration inconsistency between the PCU and SGSN, etc. Please check the link state of the Gb interface and related data configuration to confirm no problem in Gb interface and data configuration.

Number of BLOCK ACK Messages Received from Peer End Description

This statistics item is used to measure the number of BLOCK ACK messages received at the local end from the SGSN during the measuring period.

Measurement Point Both PCU and SGSN can notify each other to block some NSVC. When PCU originates to block some NSVC, a NSVC BLOCK message will be sent to SGSN. When the NSVC BLOCK ACK message is received by PCU from the peer end, as the measurement point B referred in Figure 4-3, this measured value will be increased by one.


Huawei Recommendation The Number of BLOCK ACK Messages Received from Peer Endshould be equal to Number of BLOCK Messages Sent by NS Sublayer to Peer End. If not equal, please check the link state of the Gb interface and related data configuration.



Number of BLOCK Messages Received from Peer End Description

This statistics item is used to measure the number of BLOCK messages received at the local end from the SGSN during the measuring period.

Measurement Point Both PCU and SGSN can notify each other to block some NSVC. When SGSN originates to block some NSVC, a NSVC BLOCK message will be received by PCU, as the measurement point A referred in Figure 4-4, and the measured value will be increased by one.

Figure 4-4 NSVC block procedure originated by SGSN

PCU SGSN

A

B

NSVC BLOCK

NSVC BLOCK ACK


Huawei Recommendation The possible reasons of NSVC block procedure originated by SGSN include: physical link fault of the Gb interface, data configuration error of the physical link, NSVC blocking initiated by SGSN, or NSVC data configuration inconsistency between the PCU and SGSN, etc. Please check the link state of the Gb interface and related data configuration to confirm no problem in Gb interface and data configuration.

Number of BLOCK ACK Messages Sent by NS Sublayer to Peer End Description

This statistics item is used to measure the number of BLOCK ACK messages sent from the local end to the SGSN during the measuring period.

Measurement Point Both PCU and SGSN can notify each other to block some NSVC. When SGSN originates to block some NSVC, a NSVC BLOCK message will be received by PCU. When the NSVC BLOCK ACK message is sent by PCU from the peer end, as the measurement point B referred in Figure 4-4, this measured value will be increased by one.

Effect of the Item





The Number of BLOCK ACK Messages Sent by NS Sublayer to Peer End should be equal to the Number of BLOCK Messages Received from Peer End. If not equal, please check the link state of the Gb interface and related data configuration.

Number of UNBLOCK Messages Sent by NS Sublayer to Peer End Description

This statistics item is used to measure the number of UNBLOCK messages sent from the local end to the SGSN during the measuring period.

Measurement Point Both PCU and SGSN can notify each other to unblock some NSVC. When PCU originates to unblock some NSVC, a NSVC UNBLOCK message will be sent to SGSN, as the measurement point A referred in Figure 4-5, and the measured value will be increased by one.

Figure 4-5 NSVC unblock procedure originated by PCU

PCU SGSN

A

B

NSVC UNBLOCK

NSVC UNBLOCK ACK



Number of UNBLOCK ACK Messages Received from Peer End Description

This statistics item is used to measure the number of UNBLOCK ACK messages received at the local end from the SGSN during the measuring period.

Measurement Point Both PCU and SGSN can notify each other to unblock some NSVC. When PCU originates to unblock some NSVC, a NSVC UNBLOCK message will be sent to SGSN. When the NSVC UNBLOCK ACK message is received by PCU from the peer end, as the measurement point B referred in Figure 4-5, this measured value will be increased by one.





Number of UNBLOCK Messages Received from Peer End Description

This statistics item is used to measure the number of UNBLOCK messages received at the local end from the SGSN during the measuring period.

Measurement Point Both PCU and SGSN can notify each other to unblock some NSVC. When SGSN originates to unblock some NSVC, a NSVC UNBLOCK message will be received by PCU, as the measurement point A referred in Figure 4-6, and the measured value will be increased by one.

Figure 4-6 NSVC unblock procedure originated by SGSN

PCU SGSN

A

B

NSVC UNBLOCK

NSVC UNBLOCK ACK



Number of UNBLOCK ACK Messages Sent by NS Sublayer to Peer End Description

This statistics item is used to measure the number of UNBLOCK ACK messages sent from the local end to the SGSN during the measuring period.

Measurement Point Both PCU and SGSN can notify each other to unblock some NSVC. When SGSN originates to unblock some NSVC, a NSVC UNBLOCK message will be received by PCU. When the NSVC UNBLOCK ACK message is sent by PCU from the peer end, as the measurement point B referred in Figure 4-6, this measured value will be increased by one.






Peak Throughput(Bytes) of the Sent NS PDU Description

This statistics item is used to measure the peak throughput of NS PDU sent on a NSVC within a measurement period.

Measurement Point During the measuring period, total bytes of NS PDUs sent by NS sublayer will be accumulated in every sampling period (5 seconds) and the maximum will be kept. At the end of the measuring period, the maximum value will be returned to user.



Peak Throughput(Bytes) of the Received NS PDU Description

This statistics item is used to measure the peak throughput of NS PDU received on a NSVC within a measurement period.

Measurement Point During the measuring period, total bytes NS PDUs received by NS sublayer will be accumulated in every sampling period (5 seconds) and the maximum will be kept. At the end of the measuring period, the maximum value will be returned to user.



4.5 BSSGP Performance Measurement 4.5.1 BSSGP Performance Measurement

Table 4-4 liststhe measurement items of the BSSGP performance measurement.

Table 4-4 BSSGP performance measurement


1 Number of FLUSH_LL PDUs Received by BSSGP Sublayer

2 Number of SUSPEND PDUs Sent by BSSGP Sublayer

3 Number of RESUME PDUs Sent by BSSGP Sublayer




4 Number of RADIO_STATUS PDUs Sent by BSSGP Sublayer

The object of the measurement is cell.

The results of the measurement are used to create traffic model.

Number of FLUSH_LL PDUs Received by BSSGP Sublayer Description

This statistics item is used to measure the total number of FLUSH LL PDUs received in a certain cell during the measuring period. When the SGSN detects cell update of the MS, it will send the FLUSH LL message to the BSS.

Measurement Point When the FLUSH LL PDU message is received by PCU, as the measurement point A referred in Figure 4-7, the measured value will be incremented by one.

Figure 4-7 FLUSH_LL PDUs received by BSSGP sublayer

PCU SGSN

A

FLUSH LL PDU

Effect of the Item If PCU receives FLUSH LL PDU message, it will remove all the PDUs saved in the send PDU buffer of old cell, or transmit some of them to the send PDU buffer of new cell. As a result, the removed PDU will be retransmitted by SGSN, which will affect the performance of packet service.


Number of SUSPEND PDUs Sent by BSSGP Sublayer Description

This statistics item is used to measure the total number of SUSPEND PDUs sent in a certain cell during the measuring period. When MSs of Class B implement the circuit service, they will send the SUSPEND PDU message to the SGSN to request packet service interruption.

Measurement Point When the SUSPEND PDU message is sent to SGSN by PCU, as the measurement point A referred in Figure 4-8, the measured value will be incremented by one.




Figure 4-8 SUSPEND PDU sent by BSSGP sublayer

PCU SGSN

A

SUSPEND PDU

Effect of the Item If PCU sends SUSPEND PDU message to request packet service interruption, the packet service will be interrupted as a result, which will affect the performance of packet service.


Number of RESUME PDUs Sent by BSSGP Sublayer Description

This statistics item is used to measure the total number of RESUME PDUs sent in a certain cell during the measuring period. When MSs of Class B end the circuit service, they will send the RESUME PDU message to the SGSN to request the resume of the packet service.

Measurement Point When the RESUME PDU message is sent to SGSN by PCU, as the measurement point A referred in Figure 4-9, the measured value will be incremented by one.

Figure 4-9 RESUME PDU sent by BSSGP sublayer

PCU SGSN

A

RESUME PDU





Number of RADIO_STATUS PDUs Sent by BSSGP Sublayer Description

This statistics item is used to measure the total number of RADIO STATUS PDUs sent in a certain cell during the measuring period. When the communication cannot be continued due to poor radio channel quality or when the BSS requests the MS to make cell reselection, the BSS will send the RADIO STATUS PDU message to the SGSN.

Measurement Point When the RADIO STATUS PDU message is sent to SGSN by PCU, as the measurement point A referred in Figure 4-10, the measured value will be incremented by one.

Figure 4-10 RADIO STATUS PDU sent by BSSGP sublayer

PCU SGSN

A

RADIO STATUS PDU

Effect of the Item It reflects the air interface transmission quality of the cell. When the MS is outside the coverage of the radio, or the communication can not proceed due to the bad radio channel quality, the PCU will send the “RADIO-STATUS PDU” to the SGSN.

Huawei Recommendation Please refer to “Number of RADIO_STATUS PDUs Sent by BSSGP Sublayer” in 7.1.1 “Analyzing the Um Interface”.

4.6 G-Abis Interface Performance Measurement 4.6.1 TRAU Link Measurement

Table 4-5 lists the measurement items of the TRAU link measurement.

Table 4-5 TRAU link measurement


1 Number of Normal Burst frames Received

2 Number of Out-of-Synchronization Frames Received

3 Number of Check Error Frames Received

4 Number of Valid TRAU Frames Sent

5 Number of Empty TRAU Frames Sent





The initial items can be used to form the following items to reflect the performance of G-Abis interface.

Step 1 Ratio of normal burst frames received: Number of Normal Burst frames Received \ (Number of Normal Burst frames Received + Number of Out-of-Synchronization Frames Received + Number of Check Error Frames Received).

Step 2 Ratio of received Out-of-Synchronization frames received: Number of Out-of-Synchronization Frames Received \ (Number of Normal Burst frames Received + Number of Out-of-Synchronization Frames Received + Number of Check Error Frames Received)

Step 3 Ratio of check error frames received: Number of Check Error Frames Received \ (Number of Normal Burst frames Received + Number of Out-of-Synchronization Frames Received + Number of Check Error Frames Received)

Step 4 Ratio of valid TRAU frames sent: Number of Valid TRAU Frames Sent \ (Number of Valid TRAU Frames Sent + Number of Empty TRAU Frames Sent)

Step 5 Ratio of empty TRAU frames sent: Number of Empty TRAU Frames Sent \ (Number of Valid TRAU Frames Sent + Number of Empty TRAU Frames Sent)

----End

Number of Normal Burst frames Received Description

This statistics item is used to measure the number of normal TRAU frames received during the measuring period.

Measurement Point When an uplink normal TRAU frame is received from G-Abis interface, as the measurement point A referred in Figure 4-11, the number of normal burst frames received will be incremented by one.

Figure 4-11 Normal burst frames received from G-Abis interface

BTS PCU

A

NORMAL TRAU FRAME

Effect of the Item Together with Number of Check Error Frames Received, this item can reflect the G-Abis Frame Error Rate, which is used to measure the occupation of check error frames received in normal burst frames received during the measuring period and reveals the G-Abis link quality directly.



%100Re

Re ×=−ceivedFramesBurstNormalofNumber

ceivedFramesErrorCheckofNumberRateErrorFrameAbisG

Huawei Recommendation Please refer to 7.1.1 “Analyzing the Um Interface”.

Number of Out-of-Synchronization Frames Received Description

This statistics item is used to measure the number of Out-of-Synchronization frames received during the measuring period.

Measurement Point When an uplink Out-of-Synchronization TRAU frame is received from G-Abis interface, as the measurement point A referred in Figure 4-12, the number of Out-of-Synchronization frames received is incremented by one.

Figure 4-12 Out-of-Synchronization frames received from G-Abis interface

BTS PCU

A

OUT-OF-SYNCHRONIZATION TRAU FRAME



Number of Check Error Frames Received Description

This statistics item is used to measure the number of check error frames received during the measuring period.

Measurement Point When an uplink check error TRAU frame is received from G-Abis interface, as the measurement point A referred in Figure 4-13, the number of check error frames received is incremented by one.




Figure 4-13 Check error frames received from G-Abis interface

BTS PCU

A

CHECK ERROR TRAU FRAME

Effect of the Item Together with Number of Normal Burst frames Received, this item can reflect the G-Abis Frame Error Rate, which is used to measure the occupation of check error frames received in normal burst frames received during the measuring period and reveals the G-Abis link quality directly.

%100Re

Re ×=−ceivedFramesBurstNormalofNumber

ceivedFramesErrorCheckofNumberRateErrorFrameAbisG


Number of Valid TRAU Frames Sent Description

This statistics item is used to measure the number of valid TRAU frames sent during the measuring period.

Measurement Point When a downlink valid TRAU frame carrying a valid data block is sent to G-Abis interface, as the measurement point A referred in Figure 4-14, the number of valid TRAU frames sent is incremented by one.

Figure 4-14 Valid TRAU frames sent to G-Abis interface

BTS PCU

A

VALID TRAU FRAME





Please refer to 7.1.1 “Analyzing the Um Interface”.

Number of Empty TRAU Frames Sent Description

This measurement is used to measure the number of empty TRAU frames sent during the measuring period.

Measurement Point When a downlink empty TRAU frame not including valid RLC/MAC block data is sent to G-Abis interface, as the measurement point A referred in Figure 4-15, the number of empty TRAU frames sent is incremented by one.

Figure 4-15 Empty TRAU frames sent to G-Abis interface

BTS PCU

A

EMPTY TRAU FRAME



4.7 Pb Interface Performance Measurement 4.7.1 LAPD Link Measurement

Table 4-6 lists the measurement items of the LAPD link measurement.

Table 4-6 LAPD link measurement


1 Number of SABM Frames Sent

2 Number of SABM Frames Received

3 Number of UA Frames Sent

4 Number of UA Frames Received

5 Number of REJ Frames Sent

6 Number of REJ Frames Received





7 Number of Information Frames Sent

8 Number of Information Frames Received

9 Bytes of Information Frames Sent

10 Bytes of Information Frames Received

11 Number of Information Frame Resend Times

12 Number of Data Transmit Requests From L3 to LAPD

13 Bytes of Data Transmit Requests From L3 to LAPD

14 Number of Received Frames with Wrong Receiving Number

15 Number of Downlink Message Queue Overflows

16 Number of Uplink Message Queue Overflows

17 Total Number of Frames Received

18 Total Number of Error Frames Received

19 Total Number of Frames Sent

The object of the measurement is LAPD.

The initial items can be used to reflect the performance of Pb interface, and they are also helpful for troubleshooting of the GPRS network. Please refer to the analysis and application part of each item for the detailed usage.

Number of SABM Frames Sent Description

This statistics item is used to measure the number of SABM frames requesting link establishment sent during the measuring period.

Measurement Point If the LAPD module link is not established or link disconnection is detected at the local end, the local end will send the SABM frame to the peer end to request link establishment. Both PCU and BSC can initiate request link establishment. When the protocol layer of the LAPD module of PCU sends the SABM frame to request link establishment, as the measurement point A referred in Figure 4-16, the measured value will be incremented by one.



Figure 4-16 Send the SABM frame to request link establishment by PCU

BSC PCU

A

SABM

Effect of the Item This statistical result can indicate whether the LAPD link is normal.

Huawei Recommendation This frame should appear for one or zero time(s) only when the LAPD link is initialized and it should not show up any longer after the LAPD link establishment. If the measured values of all statistics items in the statistical result are zero except that of this statistics item, it can be considered that the link is completely disconnected. Please check whether the corresponding E1 link is normally connected and whether the LAPD data configuration of the PCU is consistent with that of the BSC. If the measured values of other statistics items in the statistical result are not zero besides that of this statistics item, it can be considered that the local end attempts to reestablish link for N times, i.e., the link is disconnected for N times. In such case, it can be considered that the E1 line is connected but it is of poor transmission quality. Please check and confirm the following items. The various interfaces in the E1 line are well contacted. The sending end is correctly grounded. The E1 line is not in single-pass state. The E1 clock source of the PCU is set as the slave clock. The clock of the BSC is stable and its error is not greater than 0.1Hz. And there is no strong EMC interference source in the surroundings. Please refer to 6.1 “Analyzing the Quality of LAPD of Pb Interface”.

Number of SABM Frames Received Description

This statistics item is used to measure the number of SABM frames requesting link establishment received during the measuring period.

Measurement Point If the LAPD module link is not established or link disconnection is detected at the local end, the local end will send the SABM frame to the peer end to request link establishment. Both PCU and BSC can initiate request link establishment. When the SABM frame to request link establishment sent by the protocol layer of the LAPD module of BSC is received, as the measurement point A referred in Figure 4-17, the measured value will be incremented by one.




Figure 4-17 Send the SABM frame to request link establishment by BSC

BSC PCU

A

SABM


Huawei Recommendation Please refer the instruction of corresponding part of Number of SABM Frames Sent.

Number of UA Frames Sent Description

This statistics item is used to measure the number of link establishment response frames sent during the measuring period.

Measurement Point If the local end receives the SABM frame (for link establishment) from the peer end and if everything at the local end is normal, then the local end will enter into the link establishment state and send the UA frame to the peer end to indicate its acceptance of the link establishment request. Both PCU and BSC can initiate request link establishment, and the other peer end should response the request. When the UA frame to acknowledge request link establishment sent by the protocol layer of the LAPD module of BSC is received, as the measurement point A referred in Figure 4-18, the measured value will be incremented by one.

Figure 4-18 Send the UA frame to acknowledge link establishment by PCU

BSC PCU

A

UA

Effect of the Item This statistical result can indicate whether the LAPD link is normal.




This frame should appear for one or zero times only when the LAPD link is initialized and it should not show up any longer after the LAPD link establishment. If the measured value is greater than 1, it can be considered that the E1 line is connected but it is of poor transmission quality. Please check and confirm the following items. The various interfaces in the E1 line are well contacted. The sending end is correctly grounded. The E1 line is not in single-pass state. The E1 clock source of the PCU is set as the slave clock. The clock of the BSC is stable and its error is not greater than 0.1Hz. And there is no strong EMC interference source in the surroundings.

Number of UA Frames Received Description

This statistics item is used to measure the number of link establishment response frames received during the measuring period.

Measurement Point If the local end receives the SABM frame (for link establishment) from the peer end and if everything at the local end is normal, then the local end will enter into the link establishment state and send the UA frame to the peer end to indicate its acceptance of the link establishment request. Both PCU and BSC can initiate request link establishment, and the other peer end should response the request. When the UA frame to acknowledge link establishment request sent by the protocol layer of the LAPD module of BSC is received, as the measurement point A referred in Figure 4-19, the measured value will be incremented by one.

Figure 4-19 Send the UA frame to acknowledge link establishment by BSC

BSC PCU

A

UA


Huawei Recommendation Please refer the instruction of corresponding part of Number of UA Frames Sent.

Number of REJ Frames Sent Description

This statistics item is used to measure the number of REJECT (REJ) frames sent during the measuring period.

Measurement Point If the sending sequence number of the LAPD frame received by the local end from the peer end is different from the expected sequence number (for example, the local end expects to receive frame 2 from the peer end, however, it receives frame 4 actually), then




the local end will send the REJECT frame to the peer end to request retransmission. As a result, both PCU and BSC will send the REJECT frame to the peer end to request retransmission. When the REJECT frame to request retransmission sent by the protocol layer of the LAPD module of BSC is received, as the measurement point A referred in Figure 4-20, the measured value will be incremented by one.

Figure 4-20 REJ frame sent by PCU to request retransmission LAPD frame

BSC PCU

A

LAPD FRAME transmission

REJECT

LAPD FRAME retransmission

Effect of the Item This statistical result reveals the transmission quality of the LAPD link.

Huawei Recommendation The reference range of this measurement item is 0~5 per 15 minutes. If the measured value is not within the reference range, it can be considered that the E1 line is connected but it is of poor transmission quality. Please check and confirm the following items. The various interfaces in the E1 line are well contacted. The sending end is correctly grounded. The E1 line is not in single-pass state. The E1 clock source of the PCU is set as the slave clock. The clock of the BSC is stable and its error is not greater than 0.1Hz. And there is no strong EMC interference source in the surroundings.

Number of REJ Frames Received Description

This statistics item is used to measure the number of REJECT (REF) frames received during the measuring period.

Measurement Point If the sending sequence number of the LAPD frame received by the local end from the peer end is different from the expected sequence number (for example, the local end expects to receive frame 2 from the peer end, however, it receives frame 4 actually), then the local end will send the REJECT frame to the peer end to request retransmission. As a result, both PCU and BSC will send the REJECT frame to the peer end to request retransmission. When the REJECT frame to request retransmission sent by the protocol layer of the LAPD module of BSC is received, as the measurement point A referred in Figure 4-21, the measured value will be incremented by one.



Figure 4-21 REJ frame sent by BSC to request retransmission LAPD frame

BSC PCU

A

LAPD FRAME transmission

REJECT

LAPD FRAME retransmission


Huawei Recommendation Please refer the instruction of corresponding part of Number of REJ Frames Sent.

Number of Information Frames Sent Description

This statistics item is used to measure the number of information frames sent during the measuring period.

Measurement Point PCU will get information frame from downlink message queue which is from the PCU higher layer and send it to BSC. When the protocol layer of the LAPD module sends the information frame bearing the message to the BSC, the measured value will be incremented by one.


Huawei Recommendation The reference range of this measurement item is 0~100 per second which is based on the configuration of one 64kbit/s LAPD signalling link. If the measured value is not within the reference range, it can be considered that the transmission load exceeds the bearing capacity of the LAPD, more LAPD links should be added. Please refer to 6.1 Analyzing the Quality of LAPD of Pb Interface”.

Number of Information Frames Received Description

This statistics item is used to measure the number of information frames received during the measuring period.

Measurement Point PCU will put information frame bearing the message from the BSC higher layer into uplink message queue and send it to higher layer. When the protocol layer of the LAPD module receives the information frame, the measured value will be incremented by one.






Please refer to 6.1 Analyzing the Quality of LAPD of Pb Interface

Bytes of Information Frames Sent Description

This statistics item is used to measure the byte number of information frames sent during the measuring period.

Measurement Point PCU will get information frame from downlink message queue which is from the PCU higher layer and send it to BSC. When the protocol layer of the LAPD module sends the information frame bearing the message to the BSC, the measured value will be incremented by the byte number of the corresponding information frames.

Effect of the Item This item reflects the capacity of LAPD transmission. The reference range of this measurement item is 0-6000 byte(s) per second which is based on the configuration of one 64kbit/s LAPD signalling link.

Huawei Recommendation Please refer to 6.1 Analyzing the Quality of LAPD of Pb Interface”.

Bytes of Information Frames Received Description

This statistics item is used to measure the byte number of information frames received during the measuring period.

Measurement Point PCU will put information frame bearing the message from the BSC higher layer into uplink message queue and send it to higher layer. When the protocol layer of the LAPD module receives the information frame, the measured value will be incremented by the byte number of the corresponding information frames.

Effect of the Item Please refer the instruction of corresponding part of Bytes of Information Frames Sent.

Huawei Recommendation Please refer to 6.1 Analyzing the Quality of LAPD of Pb Interface”.

Number of Information Frame Resend Times Description

This statistics item is used to measure the number of information frame resend times during the measuring period.

Measurement Point If the sending sequence number of the information frame received by the local end from the peer end is different from the expected sequence number (for example, the local end expects to receive frame 2 from the peer end, however, it receives frame 4 actually), then the local end will sends the REJECT frame to the peer end to request retransmission. When the REJECT frame to request retransmission sent by the protocol layer of the LAPD module of BSC is received, PCU will retransmit the previous Information frame rejected by BSC, as the measurement point A referred in Figure 4-21, and the measured value will be incremented by one.



Figure 4-22 REJ frame received and Information frame retransmitted

BSC PCU

A

Information FRAME transmission

REJECT

Information FRAME retransmission

Effect of the Item This statistical result reveals the transmission quality of the LAPD link.

Huawei Recommendation The reference range of this measurement item is 0~10 per 15 minutes. If the measured value is not within the reference range, it can be considered that the E1 line is connected but it is of poor transmission quality. Please check and confirm the following items. The various interfaces in the E1 line are well contacted. The sending end is correctly grounded. The E1 line is not in single-pass state. The E1 clock source of the PCU is set as the slave clock. The clock of the BSC is stable and its error is not greater than 0.1Hz. And there is no strong EMC interference source in the surroundings. Please refer to 6.1 Analyzing the Quality of LAPD of Pb Interface”.

Number of Data Transmit Requests From L3 to LAPD Description

This statistics item is used to measure the number of data transmit requests initiated by Layer 3 (L3) to LAPD during the measuring period.

Measurement Point When the protocol layer of the LAPD module receives the information transmit request from the higher layer, the measured value will be incremented by one, and PCU will put the information frame bearing the message into downlink message queue to send it to BSC.

Effect of the Item This statistical result reveals the transmission load of the local LAPD link. This measured value indicates the number of messages the PCU higher layer requests the LAPD module to transmit.

Huawei Recommendation The reference range of this measurement item is 0~100 per second. If the measured value is not within the reference range, more LAPD links should be added. If the measured value is greater than that of Number of Information Frames Sent, it can be considered that the transmission load exceeds the bearing capacity of the LAPD, more LAPD links should be added.

Bytes of Data Transmit Requests From L3 to LAPD Description

This statistics item is used to measure the byte number of information that L3 requests LAPD to send during the measuring period.




Measurement Point When the protocol layer of the LAPD module receives the information transmit request from the higher layer, the measured value will be incremented by the size of the data packet, and PCU will put the information frame bearing the message into downlink message queue to send it to BSC.

Effect of the Item This statistical result reveals the transmission load of the local LAPD link. This measured value indicates the number of messages the PCU higher layer requests the LAPD module to transmit.

Huawei Recommendation The reference range of this measurement item is 0~5000 bytes per second. If the measured value is not within the reference range, more LAPD links should be added. If the measured value is greater than that of Bytes of Information Frames Sent, it can be considered that the transmission load exceeds the bearing capacity of the LAPD, more LAPD links should be added.

Number of Received Frames with Wrong Receiving Number Description

This statistics item is used to measure the number of frames whose receiving sequence number are not right during the measuring period.

Measurement Point The NR value in the remote LAPD frame from the LAPD frame is illegal. The NR value indicates the sequence number of the local LAPD information frame the peer end expects to receive. If the NR value is not within the legal range of the local sending sequence number, error will be caused. When the receiving sequence number in the information frame received by the protocol layer of the LAPD module is illegal, which indicates that there must be error in the LAPD link, the measured value will be incremented by one, and the LAPD link should be re-established.


Huawei Recommendation If the measured value is not 0, it can be considered that the E1 link is connected but it is of poor transmission quality. Please check and confirm the following items. The various interfaces in the E1 line are well contacted. The sending end is correctly grounded. The E1 line is not in single-pass state. The E1 clock source of the PCU is set as the slave clock. The clock of the BSC is stable and its error is not greater than 0.1Hz. And there is no strong EMC interference source in the surroundings.

Number of Downlink Message Queue Overflows Description

This statistics item is used to measure the number of overflows occurring in the queue from L3 to the LAPD module during the measuring period.

Measurement Point When the protocol layer of the LAPD module receives the information transmit request from the higher layer, PCU will put the message into downlink message queue to send it to BSC. If the downlink message queue is already full, PCU will discard the message due to the queue overflow, and the measured value will be incremented by one.




Huawei Recommendation This measured value can be used to judge whether the higher layer traffic requirement exceeds the LAPD link load capacity. If the measured value is not 0, more LAPD links should be added. Please refer to 6.1 Analyzing the Quality of LAPD of Pb Interface”.

Number of Uplink Message Queue Overflows Description

This statistics item is used to measure the number of overflows occurring in the queue from the LAPD module to L3 during the measuring period.

Measurement Point When the protocol layer of the LAPD module receives the information frame from BSC, PCU will put the message into uplink message queue to send it to high layer. If the uplink message queue is already full, PCU will discard the message due to the queue overflow, and the measured value will be incremented by one.


Huawei Recommendation This measured value can be used to judge whether the higher layer traffic requirement exceeds the LAPD link load capacity. If the measured value is not 0, more LAPD links should be added.

Total Number of Frames Received Description

This statistics item is used to measure the total number of frames received during the measuring period.

Measurement Point When the physical layer of the LAPD module receives the frame, the measured value will be incremented by one.

Effect of the Item Together with the item Total Number of Error Frames Received, this statistics can reflect Error Frames Rate, which is used to measure the error frames rate during the measuring period and reveals the transmission quality of the LAPD link.

%100Re

Re ×=ceivedFramesofNumberTotal

ceivedFramesErrorofNumberTotalRateFramesError


Total Number of Error Frames Received Description

This statistics item is used to measure the total number of error frames received during the measuring period.

Measurement Point




When the physical layer of LAPD module receives the error frames, such as the frames with non-octet bytes, the frames with aborted receiving, the frames with CRC check error, the measured value will be incremented by one.

Effect of the Item Together with the item Total Number of Frames Received, this statistics can reflect Error Frames Rate, which is used to measure the error frames rate during the measuring period and reveals the transmission quality of the LAPD link.

%100Re

Re ×=ceivedFramesofNumberTotal

ceivedFramesErrorofNumberTotalRateFramesError

Huawei Recommendation This measured value can be used to judge the transmission quality of the line. This statistical result reveals the transmission quality of the LAPD link. If this value is increased constantly, or the value of the item Error Frames Rate is more than 0.02%, please check and confirm the following items. The various interfaces in the E1 line are well contacted. The sending end is correctly grounded. The E1 line is not in single-pass state. The E1 clock source of the PCU is set as the slave clock. The clock of the BSC is stable and its error is not greater than 0.1Hz. And there is no strong EMC interference source in the surroundings.

Total Number of Frames Sent Description

This statistics item is used to measure the total number of frames sent during the measuring period.

Measurement Point When the physical layer of the LAPD module sends the frame, the measured value will be incremented by one.


Huawei Recommendation The comparison between the measured value and the corresponding measured value of the BSC can help to analyze the transmission quality of the LAPD module of the BSC.

4.8 Cell Performance Measurement Table 4-7 lists the measurement items of the cell performance measurement.

Table 4-7 Cell performance measurement


1 Packet Access Performance Measurement on CCCH

2 Packet Access Performance Measurement on PCCCH

3 Packet Access Performance Measurement on PACCH

4 Rate of Successful Packet Assignment

5 Paging Request Measurement




6 Uplink TBF Establishment/Release Measurement

7 Downlink TBF Establishment/Release Measurement

8 Uplink LLC Data Transmission Measurement

9 Downlink LLC Data Transmission Measurement

10 Uplink RLC Data Transmission Measurement

11 Downlink RLC Data Transmission Measurement

12 Cell Radio Channel Performance Measurement

13 Resource Maintenance Performance Measurement

14 PDCH Resource Performance Measurement

15 PDCH Extremum Value Measurement

16 Uplink EGPRS TBF Establishment/Release Measurement

17 Downlink EGPRS TBF Establishment/Release Measurement

18 Uplink EGPRS RLC Data Transmission Measurement

19 Downlink EGPRS RLC Data Transmission Measurement

20 EGPRS GMSK_MEAN_BEP Different Value Measurement

21 EGPRS 8PSK_MEAN_BEP Different Value Measurement


4.8.1 Packet Access Performance Measurement on CCCH Table 4-8 lists the measurement items of the packet access performance measurement on CCCH.

Table 4-8 Packet access performance measurement on CCCH


1 Number of Packet Channel Requests Received on

2 Number of One Phase Access Requests Received on RACH

3 Number of Single Block Channel Requests Received on RACH

4 Mean Inter-arrival Time of Packet Access Requests on CCCH (s)

The items can be used to reveal the traffic load of the cell and thus help to create the traffic model.




Number of Packet Channel Requests Received on CCCH Description

This item is used to measure the total number of packet channel requests received on CCCH within a measurement period.

Measurement Point The mobile station initiates the packet access procedure by scheduling the sending of CHANNEL REQUEST message on RACH. The packet access includes following types: single block packet access, one phase access and two phase access, the CHANNEL REQUEST messages contain the parameters of an establishment cause which indicates the type of packet access. When the PCU receives the CHANNEL REQUEST messages on CCCH from the MS, as the measurement point A referred in Figure 4-23, the value of this item is incremented by one.

Figure 4-23 Channel Request message received on CCCH

MS

A

CHANNEL REQUEST

NETWORK

Effect of the Item This statistic item can affect the item Mean Inter-arrival Time of Packet Access Requests on CCCH (s), which is used to measure the mean inter-arrival time of packet access requests on the CCCH during the measuring period. You can get more detailed instruction from Mean Inter-arrival Time of Packet Access Requests on CCCH (s)


Number of One Phase Access Requests Received on RACH Description

This item is used to measure the total number of one phase access requests received on RACH within a measurement period.

Measurement Point When the PCU receives one phase access requests on RACH from the MS, as the measurement point A referred in Figure 4-24 the CHANNEL REQUEST message contain the parameters of establishment cause which indicates one phase access, the value of this item is incremented by one.



Figure 4-24 One phase access requests received on RACH

MS

A

CHANNEL REQUEST(One phase access)

NETWORK



Number of Single Block Channel Requests Received on RACH Description

This item is used to measure the total number of single block access requests received on RACH within a measurement period.

Measurement Point When the PCU receives single block access requests on RACH from the MS, as the measurement point A referred in Figure 4-25, the CHANNEL REQUEST messages contain the parameters of establishment cause which indicates single block access procedure; the value of this item is incremented by one.

Figure 4-25 Single block channel requests received on RACH

MS

A

CHANNEL REQUEST(Single block access)

NETWORK



Mean Inter-arrival Time of Packet Access Requests on CCCH (s) Description




This statistics item is used to measure the mean inter-arrival time of packet access requests on CCCH within a measurement period.

Measurement Point The item Mean Inter-Arrival Time of Packet Access Requests on CCCH is calculated by the time length of the measuring period and the item Number of Packet Channel Requests Received on CCCH during the measuring period as follow.

( )APeriodMeasuring

sCCCHonquestsAccessPacketofTimeArrivalInterMean60

Re×

=−

CCCHonceivedquestsChannelPacketofNumberA ReRe− Effect of the Item

This item reveals the packet access frequency on the CCCH. Huawei Recommendation

The random radio access conflict situation can be analyzed according to this item together with uplink and downlink packet assignment successful rate, and the random radio access conflict can be decreased through modifying parameters concerning access threshold of CCCH and mean inter-arrival time of packet access requests on CCCH.

4.8.2 Packet Access Performance Measurement on PCCCH Table 4-9 lists the measurement items of the packet access performance measurement on PCCCH.

Table 4-9 Packet access performance measurement on PCCCH


1 Number of Packet Channel Requests Received on PCCCH

2 Mean Inter-arrival Time of Packet Access Requests on PCCCH (s)


Number of Packet Channel Requests Received on PCCCH Description

This statistics item is used to measure the number of packet channel requests received on the PCCCH within a measurement period. The mobile station shall initiate the packet access procedure by scheduling the sending of PACKET CHANNEL REQUEST message on the PRACH If PCCCH is allocated in the cell.

Measurement Point When the PCU receives the PACKET CHANNEL REQUEST messages on PCCCH from the MS, as the measurement point A referred in Figure 4-26, the value of this item is incremented by one.



Figure 4-26 Channel Request message received on PCCCH

MS

A

PACKET CHANNEL REQUEST

NETWORK

Effect of the Item This item can reflect Mean inter-arrival time of packet access requests on PCCCH, which is used to measure the mean inter-arrival time of packet access requests on the PCCCH during the measuring period. You can get more detailed instruction from Mean Inter-arrival Time of Packet Access Requests on PCCCH (s).


Mean Inter-arrival Time of Packet Access Requests on PCCCH (s) Description

This statistics item is used to measure the mean inter-arrival time of packet access requests on PCCCH within a measurement period.

Measurement Point This item is calculated by the time length of measuring period and the number of packet access requests received on the PCCCH during the measuring period as follow.

( )APeriodMeasuring

sPCCCHonquestsAccessPacketofTimeArrivalInterMean60

Re×

=−

PCCCHonceivedquestsChannelPacketofNumberA ReRe− Effect of the Item

This item reveals the packet access frequency on the PCCCH. Huawei Recommendation

The random radio access conflict situation can be analyzed according to this item together with uplink and downlink packet assignment successful rate, and the random radio access conflict can be decreased through modifying parameters concerning access threshold of PCCCH and mean inter-arrival time of packet access requests on PCCCH.

4.8.3 Packet Access Performance Measurement on PACCH Table 4-10 lists the measurement items of the packet access performance measurement on PACCH.

Table 4-10 .Packet access performance measurement on PACCH


1 Number of Uplink Resource Requests Received on Uplink PACCH





2 Number of Uplink Resource Requests Received on Downlink PACCH


Number of Uplink Resource Requests Received on Uplink PACCH Description

This statistics item is used to measure the number of uplink resource requests received on the PACCH within a measurement period.

Measurement Point In the two phase packet access, the MS requests additional resources by sending PACKET RESOURCE REQUEST message to establish uplink TBF. When the PACKET RESOURCE REQUEST message is received on the uplink PACCH, as the measurement point A referred in Figure 4-27, the measured value will be incremented by one.

Figure 4-27 Two phase packet access

MS

A

CHANNEL REQUEST(Single block access)

NETWORK

IMMEDIATE ASSIGNMENT(Single block)

PACKET RESOURCE REQUEST



Number of Uplink Resource Requests Received on Downlink PACCH Description

This statistics item is used to measure the number of uplink channel request messages sent by the MS in PACKET DOWNLINK ACK/NACK messages within a measurement period. The mobile station may request establishment of an uplink transfer during a downlink TBF by including a Channel Request Description information element in the PACKET DOWNLINK ACK/NACK message.

Measurement Point



When MS want to establish uplink TBF in existed downlink TBF, it will attach the PACKET RESOURCE REQUEST description in PACKET DOWNLINK ACK/NACK message sent to network, which is used to ackowledge the downlink transmission results. When the PACKET DOWNLINK ACK/NACK message including a Channel Request Description information element is received, as the measurement point A referred in Figure 4-28, the measured value will be incremented by one.

Figure 4-28 Establish uplink TBF in downlink TBF

MS

A

NETWORK

DOWNLINK DATA BLOCKS

PACKET DOWNLINK ACK/NACK(Channel Request Description)



4.8.4 Rate of Successful Packet Assignment Table 4-11 lists the measurement items of the packet assignment success rate.

Table 4-11 Packet assignment success rate.


1 Number of Uplink Assignments

2 Number of Successful Uplink Assignments

3 Number of Uplink Immediate Assignments

4 Number of Successful Uplink Immediate Assignments

5 Number of Uplink Assignments on PACCH

6 Number of Successful Uplink Assignment on PACCH

7 Number of Downlink Assignments

8 Number of Successful Downlink Assignments

9 Number of Downlink Immediate Assignments

10 Number of Successful Downlink Immediate Assignments





11 Number of Downlink Assignments on PACCH

12 Number of Successful Downlink Assignments on PACCH

Number of Uplink Assignments Description

This statistics item is used to measure the number of all uplink assignment (including single block assignment) messages within a measurement period.

Measurement Point

The uplink assignments include the following situations:

Step 1 Immediate assignment.

On receipt of a CHANNEL REQUEST message which indicates a packet access, the network may assign the packet uplink resource to the mobile station in an IMMEDIATE ASSIGNMENT message. When the uplink assignment is sent, as the measurement point A referred in Figure 4-29, the measured value will be incremented by one.

Figure 4-29 Immediate assignment

NETWORK

A

MS

CHANNEL REQUEST

IMMEDIATE ASSIGNMENT

Step 2 Uplink assignment on PACCH

On receipt of an uplink resource requests message on uplink or downlink PACCH, the network may assign a radio resource on one or more PDCH(s) to be used by the MS in a PACKET UPLINK ASSIGNMENT message. When the uplink assignment is sent, as the measurement point A referred in Figure 4-30, the measured value will be incremented by one.



Figure 4-30 Uplink assignment on PACCH

NETWORK

A

MS

PACKET RESOURCE REQUEST orPACKET DOWNLINK ACK/NACK

(Channel Request Decription)

PACKET UPLINK ASSIGNMENT

Step 3 Uplink assignment on PCCCH

If PCCCH is allocated in the cell, on receipt of a PACKET CHANNEL REQUEST message on the PRACH, the network may assign a radio resource on one or more PDCH(s) to be used by the MS in a PACKET UPLINK ASSIGNMENT message. When the uplink assignment is sent on PCCCH channel, as the measurement point A referred in Figure 4-31, the measured value will be incremented by one.

Figure 4-31 Uplink assignment on PCCCH

NETWORK

A

MS

PACKET CHANNEL REQUEST


Effect of the Item

None


None

----End




Number of Successful Uplink Assignments Description

This statistics item is used to measure the number of uplink assignment successes within a measurement period. The assignment success means that the uplink data block is received or that the single block uplink message successfully received.

Measurement Point

The successful uplink assignments include the following situations:

Step 1 Uplink data block received

On receipt of uplink data block after sending immediate assignment or packet uplink assignment from network to MS, it indicates that the MS has received uplink assignment successfully. When the uplink data block is received, as the measurement point A referred in Figure 4-32, the number of successful uplink assignment is incremented by one.

Figure 4-32 Uplink data block received

NETWORK

A

MS

UPLINK DATA BLOCK

IMMEIDATE ASSIGNMENT orPACKET UPLINK ASSIGNMENT

Step 2 Packet resource request or measurement report received.

On receipt of packet resource requests after sending immediate assignment, it indicates that the MS has received immediate assignment for single block successfully. When the PACKET RESOURCE REQUEST message received, as the measurement point A referred in Figure 4-33, the number of successful uplink assignment is incremented by one.



Figure 4-33 Packet resource request or measurement report received

NETWORK

A

MS


IMMEIDATE ASSIGNMENT(Single block)

Effect of the Item

Together with Number of uplink assignments, this item can reflect the Uplink Assignment Successful Rate, which is used to measure the uplink assignment success rate during the measuring period.


If the value of Number of Successful Uplink Assignments is relatively low compared to that of Number of Uplink Assignments, some problems may lie in radio environment, network parameter configuration, network resource configuration and network equipment. Please check which is the lowest, the rate of uplink immediate assignment successes, the rate of uplink assignment successes on the PCCCH or the rate of uplink assignment successes on the PACCH. Then handle the different problems accordingly and properly.

No channel resource or MS no response will cause uplink assignment failure. Therefore, please see more detailed analysis from the corresponding part of Number of Uplink TBF Establishment Failures due to No Channel and Number of Uplink TBF Establishment Failures due to Ms No Response

----End

Number of Uplink Immediate Assignments Description

This statistics item is used to measure the number of uplink immediate assignment messages within a measurement period.

Measurement Point On receipt of a CHANNEL REQUEST message which indicates a packet access, the network may assign the packet uplink resource to the mobile station in an IMMEDIATE ASSIGNMENT message. When the uplink assignment is sent, as the measurement point A referred in Figure 4-29, the measured value will be incremented by one.

Effect of the Item Together with Number of Successful Uplink Immediate Assignments, this item can reflect the Uplink Immediate Assignment Successful Rate, which is used to measure the uplink immediate assignment successful rate during the measuring period.




%100Im ×=BARateSuccessAssignmentmediateUplink

sAssignmentmediateUplinkSuccessfulofNumberA Im−sAssignmentmediateUplinkofNumberB Im−


Number of Successful Uplink Immediate Assignments Description

This statistics item is used to measure the number of uplink immediate assignment successes within a measurement period.

Measurement Point

The successful uplink immediate assignments include the following situations:

Step 1 Uplink immediate assignment.

On receipt of uplink data block after sending immediate assignment on AGCH channel from network to MS, it indicates that the MS has received uplink immediate assignment successfully. When the uplink data block is received, as the measurement point A referred in Figure 4-34, the number of successful uplink assignment is incremented by one.

Figure 4-34 Uplink immediate assignment

NETWORK

A

MS

UPLINK DATA BLOCK

IMMEIDATE ASSIGNMENT

Step 2 Single block immediate assignment

On receipt of a packet resource requests after sending immediate assignment on AGCH channel, it indicates that the MS has received immediate assignment for single block successfully. When the PACKET RESOURCE REQUEST message received, as the measurement point A referred inFigure 4-35, the number of successful uplink assignment is incremented by one.



Figure 4-35 Single block immediate assignment

NETWORK

A

MS


IMMEIDATE ASSIGNMENT(Single block)

Effect of the Item

Together with the item Number of Uplink Immediate Assignments, this item can reflect Uplink Immediate Assignment Success Rate, which is used to measure the uplink immediate assignment successful rate during the measuring period.

%100Im ×=BARatesuccessAssignmentmediateUplink

sAssignmentmediateUplinkSuccessfulofNumberA Im−sAssignmentmediateUplinkofNumberB Im−


If the value is lower than 85%, some problems may lie in radio environment, network parameter configuration, network resource configuration and network equipment. They should be optimized.

Uplink assignment is comprised of uplink immediate assignment and uplink assignment on PACCH. Therefore, please refer to the corresponding part of Number of Successful Uplink Assignments.

----End

Number of Uplink Assignments on PACCH Description

This statistics item is used to measure the number of uplink assignment messages received on the PACCH within a measurement period.

Measurement Point On receipt of an uplink resource requests message on uplink or downlink PACCH, the network may assign a radio resource on one or more PDCH(s) to be used by the MS in a PACKET UPLINK ASSIGNMENT message. When the uplink assignment is sent, as the measurement point A referred in Figure 4-30,, the measured value will be incremented by one.

Effect of the Item




Together with the item Number of Successful Uplink Assignment on PACCH, this item can reflect Uplink Assignment Success Rate on PACCH, which is used to measure the uplink assignment successful rate on PACCH during the measuring period.

%100×=BAPACCHonRateSuccessAssignmentUplink

PACCHonsAssignmentUplinkSuccessfulofNumberA −PACCHonsAssignmentUplinkofNumberB −


Number of Successful Uplink Assignment on PACCH Description

This statistics item is used to measure the rate of uplink assignment successes on the PACCH within a measurement period.

Measurement Point When the uplink data of the MS are received or when the single block uplink message received (such as packet resource request or measurement report) after sending uplink assignment on PACCH, as the measurement point A referred in Figure 4-36, the number of uplink assignments on the PACCH will be incremented by one.

Figure 4-36 Successful uplink assignment on PACCH

NETWORK

A

MS

UPLINK DATA BLOCK


Effect of the Item Together with the item Number of Uplink Assignments on PACCH, this item can reflect Uplink Assignment Success Rate on PACCH, which is used to measure the uplink assignment successful rate on PACCH during the measuring period.

%100×=BAPACCHonRateSuccessAssignmentUplink

PACCHonsAssignmentUplinkSuccessfulofNumberA −PACCHonsAssignmentUplinkofNumberB −

Huawei Recommendation If the value is lower than 85%, some problems may lie in radio environment, network parameter configuration, network resource configuration and network equipment. They should be optimized.



Uplink assignment is comprised of uplink immediate assignment and uplink assignment on PACCH. Therefore, please refer to the corresponding part of Number of Successful Uplink Assignments.

Number of Downlink Assignments Description

This statistics item is used to measure the number of downlink assignment messages within a measurement period.

The network initiates the packet downlink assignment procedure by sending an IMMEDIATE ASSIGNMENT message on the CCCH timeslot corresponding to CCCH group the mobile station belongs to.

Measurement Point

The downlink assignments include the following situations:

Step 1 Downlink immediate assignments

The network initiates the immediate downlink assignment procedure by sending an IMMEDIATE ASSIGNMENT message on the CCCH. When the downlink assignment message is sent, as the measurement point A referred in Figure 4-37, the measured value will be incremented by one.

Figure 4-37 Downlink immediate assignments

NETWORK

A

MS


Step 2 Downlink assignments on PACCH

The network may initiate packet downlink assignment by sending a PACKET DOWNLINK ASSIGNMENT message to the mobile station on the PACCH. When the downlink assignment message is sent, as the measurement point A referred in Figure 4-38, the measured value will be incremented by one.




Figure 4-38 Downlink assignments on PACCH

NETWORK

A

MS

PACKET DOWNLINK ASSIGNMENT

Effect of the Item

None


None

----End

Number of Successful Downlink Assignments Description

This statistics item is used to measure the number of downlink assignment successes within a measurement period.

Measurement Point

The successful downlink assignments include the following situations:

Step 1 On receipt of PACKET CONTROL ACKNOWLEDGEMENT after immediate assignment on CCCH and then polling request message on assigned control PDCH channel, it indicates that the MS has received downlink immediate assignment successfully. When the network received PACKET CONTROL ACKNOWLEDGEMENT message from the MS after downlink assignment, as the measurement point A referred in Figure 4-39, the number of downlink assignment successes will be incremented by one.



Figure 4-39 Successful Downlink immediate assignments

NETWORK

A

MS

IMMEDIATE ASSIGNMENT(downlink)

PACKET POLLING REQUEST

PACKET CONTROL ACKNOWLEDGEMENT

Step 2 On receipt of PACKET CONTROL ACKNOWLEDGEMENT after PACKET DOWNLINK ASSIGNMENT message on PACCH, it indicates that the MS has received downlink assignment successfully. When the network received PACKET CONTROL ACKNOWLEDGEMENT message from the MS after packet downlink assignment, as the measurement point A referred in Figure 4-40, the number of downlink assignment successes will be incremented by one.

Figure 4-40 Successful Downlink assignments on PACCH

NETWORK

A

MS



Effect of the Item

None


If the value of Number of Successful Downlink Assignments is relatively low compared to that of Number of Downlink Assignments, some problems may lie in radio environment, network parameter configuration, network resource configuration and network equipment. Please check which is the lowest, the rate of downlink immediate assignment successes, the rate of downlink assignment successes on the PAGCH or the rate of downlink assignment successes on the PACCH. Then handle the different problems accordingly and properly. What’s more, lots of cell change and update procedure will also inevitably cause downlink assignment successful rate relatively low.




No channel resource or MS no response will cause downlink assignment failure. Therefore, please see more detailed analysis from the corresponding part of Number of Downlink TBF Establishment Failures due to No Channeland Number of Downlink TBF Establishment Failures due to MS No Response.

----End

Number of Downlink Immediate Assignments Description

This statistics item is used to measure the number of downlink immediate assignment messages within a measurement period.

Measurement Point The network initiates the packet downlink assignment procedure by sending an IMMEDIATE ASSIGNMENT message on the CCCH. When the downlink assignment message is sent, as the measurement point A referred in Figure 4-37, the measured value will be incremented by one.

Effect of the Item Together with the item Number of Successful Downlink Immediate Assignments, this item can reflect Downlink Immediate Assignment Success Rate, which is used to measure the downlink immediate assignment successful rate during the measuring period.

%100Im ×=BARateSuccessAssignmentmediateDownlink

sAssignmentmediateDownlinkSuccessfulofNumberA Im−sAssignmentmediateDownlinkofNumberB Im−


Number of Successful Downlink Immediate Assignments Description

This statistics item is used to measure the number of uplink immediate assignment successes within a measurement period.

Measurement Point On receipt of PACKET CONTROL ACKNOWLEDGEMENT after immediate assignment on CCCH and then polling request message on assigned control PDCH channel, it indicates that the MS has received downlink immediate assignment successfully. When the network received PACKET CONTROL ACKNOWLEDGEMENT message from the MS after downlink assignment, as the measurement point A referred in Figure 4-39, the number of downlink assignment successes will be incremented by one.

Effect of the Item Together with the item Number of Downlink Immediate Assignments, this item can reflect Downlink Immediate Assignment Success Rate, which is used to measure the downlink immediate assignment successful rate during the measuring period.

%100Im ×=BARateSuccessAssignmentmediateDownlink

sAssignmentmediateDownlinkSuccessfulofNumberA Im−



sAssignmentmediateDownlinkofNumberB Im− Huawei Recommendation

If the value is lower than 70%, some problems may lie in radio environment, network parameter configuration, network resource configuration and network equipment. They should be optimized. Downlink assignment is comprised of downlink immediate assignment and downlink assignment on PACCH. Therefore, please refer to the corresponding part of Number of Successful Downlink Assignments.

Number of Downlink Assignments on PACCH Description

This statistics item is used to measure the number of downlink assignment messages on the PACCH within a measurement period.

Measurement Point The network may initiate a downlink by sending a PACKET DOWNLINK ASSIGNMENT message to the mobile station on the PACCH. When the downlink assignment message is sent, as the measurement point A referred in Figure 4-38, the measured value will be incremented by one.

Effect of the Item Together with the item Number of Successful Downlink Assignments on PACCH, this item can reflect Downlink Assignment Success Rate on PACCH, which is used to measure the downlink assignment successful rate on PACCH during the measuring period.

%100×=BAPACCHonRateSuccessAssignmentDownlink

PACCHonsAssignmentDownlinkSuccessfulofNumberA − PACCHonsAssignmentDownlinkofNumberB −


Number of Successful Downlink Assignments on PACCH Description

This measurement is used to measure the rate of downlink assignment successes on the PACCH within a measurement period.

Measurement Point On receipt of PACKET CONTROL ACKNOWLEDGEMENT after PACKET DOWNLINK ASSIGNMENT message on PACCH, it indicates that the MS has received downlink assignment successfully. When the network received PACKET CONTROL ACKNOWLEDGEMENT message from the MS after packet downlink assignment, as the measurement point A referred in Figure 4-40, the number of downlink assignment successes will be incremented by one.

Effect of the Item Together with the item Number of Downlink Assignments on PACCH, this item can reflect Downlink Assignment Success Rate on PACCH, which is used to measure the downlink assignment successful rate on PACCH during the measuring period.




%100×=BAPACCHonRateSuccessAssignmentDownlink

PACCHonsAssignmentDownlinkSuccessfulofNumberA − PACCHonsAssignmentDownlinkofNumberB −

Huawei Recommendation If the value is lower than 70%, some problems may lie in radio environment, network parameter configuration, network resource configuration and network equipment. They should be optimized. Downlink assignment is comprised of downlink immediate assignment and downlink assignment on PACCH. Therefore, please refer to the corresponding part of Number of Successful Downlink Assignments.

4.8.5 Paging Request Measurement Table 4-12 lists the measurement items of the paging request measurement.

Table 4-12 Paging request measurement


1 Number of Packet Paging Requests Received

2 Number of Circuit Paging Requests Received

3 Number of Packet Paging Requests Sent

4 Number of Circuit Paging Requests Sent

5 Number of Packet Paging Requests Sent on PCH

6 Number of Packet Paging Requests Sent on PPCH

7 Number of Circuit Paging Requests Sent on PCH

8 Number of Circuit Paging Requests Sent on PPCH

9 Number of Discarded Paging Messages in PPCH Queue on PCCCH

10 Number of Circuit Paging Requests Sent on PACCH


Number of Packet Paging Requests Received Description

This statistics item is used to measure the number of packet paging request messages received by the cell within a measurement period.

Measurement Point The network may initiate the paging procedure for downlink packet transfer in order to obtain the mobile station cell location required for the downlink packet transfer. When an SGSN initiates the paging procedure for GPRS services, it shall send one or more PAGING-PS PDUs to the BSS. This statistics item is used to measure the number of



PAGING PS that will generate a PAGING REQUEST to be sent out over the cell. When the packet paging request message is received, as the measurement point A referred in Figure 4-41, the measured value will be incremented by one.

Figure 4-41 Packet paging requests received

PCU SGSN

A

PS PAGING REQUEST



Number of Circuit Paging Requests Received Description

This statistics item is used to measure the number of circuit paging messages received by the cell within a measurement period.

Measurement Point When an MSC/VLR inform SGSN to initiate a paging procedure for a circuit switched connection establishment if Gs interface is allocated in the cell, SGSN shall send one or more PAGING-CS PDUs to the BSS. This statistics item is used to measure the number of PAGING CS which will generate a PAGING REQUEST to be sent out over the cell. When the circuit paging request message is received, as the measurement point A referred in Figure 4-42, the measured value will be incremented by one.

Figure 4-42 Circuit paging requests received

PCU SGSN

A

CS PAGING REQUEST

Effect of the Item





None

Number of Packet Paging Requests Sent Description

This statistics item is used to measure the number of packet paging messages delivered by the network within a measurement period.

Measurement Point The network may initiate the paging procedure for downlink packet transfer by sending a PS PAGING REQEUST message on the appropriate paging subchannel of CCCH, or PCCCH if it is allocated in the cell. When the PS PAGING REQEUST message is delivered by PCU to MS, as the measurement point A referred in Figure 4-43, the measured value will be incremented by one.

Figure 4-43 Packet paging request sent

M S PCU

A

PS PAGING REQUEST



Number of Circuit Paging Requests Sent Description

This statistics item is used to measure the number of circuit paging messages delivered by the network within a measurement period.

Measurement Point The network may initiate the paging procedure for circuit switched connection establishment by sending a CS PAGING REQUEST message on the appropriate paging subchannel of CCCH or PACCH which depends whether the MS is in transfer mode or not. If the PCCCH is allocated in the cell, a CS PAGING REQUEST message may also be sent on the subchannel of PCCCH. When the CS PAGING REQEUST message is delivered by PCU to MS, as the measurement point A referred in Figure 4-44, the measured value will be incremented by one.



Figure 4-44 Circuit paging request sent

M S PCU

A

CS PAGING REQUEST



Number of Packet Paging Requests Sent on PCH Description

This statistics item is used to measure the number of packet paging messages delivered on the PCH by the network within a measurement period.

Measurement Point The paging request message is sent on paging subchannel of CCCH if PCCCH is not allocated in the cell. When the PCU sends the PS PAGING REQUEST message on the PCH, as the measurement point A referred in Figure 4-45, the measured value will be incremented by one.

Figure 4-45 Packet paging requests sent on PCH

M S PCU

A

PS PAGING REQUEST






Number of Packet Paging Requests Sent on PPCH Description

This statistics item is used to measure the number of packet paging messages delivered on the PPCH by the network within a measurement period.

Measurement Point The PS PAGING REQUEST message is sent on paging subchannel of PCCCH if PCCCH is allocated in the cell. When the PCU sends the packet paging message on the PPCH, as the measurement point A referred in Figure 4-46, the measured value will be incremented by one.

Figure 4-46 Packet paging requests sent on PPCH

M S PCU

A

PS PAGING REQUEST



Number of Circuit Paging Requests Sent on PCH Description

This statistics item is used to measure the number of circuit paging requests delivered on PCH by the network within a measurement period.

Measurement Point This statistics item is used to measure the number of CS paging messages delivered on the PCH by the network. Three network operation modes (mode I, II, or III) are defined for the network to choose to send CS paging message on which paging channel. Only when network operation mode I is defined for the network, and GS interface exists in the cell, but PCCCH channel has not been configured, if the MS is not in transfer mode, the network will send a CS PAGING REQUEST message on PCH subchannel of CCCH. When the PCU delivers the circuit paging message on the PCH, as the measurement point A referred in Figure 4-47, the measured value will be incremented by one.



Figure 4-47 Circuit paging requests sent on PCH

M S PCU

A

CS PAGING REQUEST



Number of Circuit Paging Requests Sent on PPCH Description

This statistics item is used to measure the number of circuit paging messages delivered on the PPCH by the network within a measurement period.

Measurement Point Only when network operation mode I is defined for the network and GS interface exists in the cell and PCCCH channel has been configured, if the MS is not in transfer mode, the network will send a CS PAGING REQUEST message on PPCH subchannel of PCCCH. When the PCU delivers the circuit paging message on the PPCH, as the measurement point A referred in Figure 4-48, the measured value will be incremented by one.

Figure 4-48 Circuit paging requests sent on PPCH

M S PCU

A

CS PAGING REQUEST






Number of Discarded Paging Messages in PPCH Queue on PCCCH Description

This statistics item is used to measure the number of paging request messages that are discarded due to congestion within a measurement period.

Measurement Point When the PPCH message queue on the PCCCH is full if PCCCH is allocated in the cell, as the measurement point A referred in Figure 4-49, and if there is still paging message on the PPCH is received, the paging message will be discarded, as the measurement point B referred in Figure 4-49, and the measured value will be incremented by one.

Figure 4-49 Number of discarded paging messages in PPCH

PCU SGSN

A

PAGING REQUEST

B


Huawei Recommendation If the value of this item is relatively high all the time, which indicates that the CS/PS PAGING business in the network is quite large and so many CS/PS PAGING REQUEST messages are discarded at PCU side, you should consider expand the network capability.

Number of Circuit Paging Requests Sent on PACCH Description

This statistics item is used to measure the number of circuit paging messages delivered on the PACCH by the network within a measurement period.

Measurement Point Only when network operation mode I is defined for the network and GS interface exists in the cell, if the MS is in transfer mode, the CS PAGING REQUEST message will be sent on PACCH, while it will not be sent to other cells to page the MS. When the PCU delivers the circuit paging message on the PACCH, as the measurement point A referred in Figure 4-50, the measured value will be incremented by one.



Figure 4-50 Circuit paging requests sent on PACCH

M S PCU

A

CS PAGING REQUEST



4.8.6 Uplink TBF Establishment/Release Measurement Table 4-13 lists the measurement items of the uplink TBF establishment/release measurement.

Table 4-13 Uplink TBF establishment/release measurement


1 Number of Uplink TBF Establishment Attempts

2 Number of Successful Uplink TBF Establishment

3 Number of Uplink TBF Establishment Failures due to No Channel

4 Number of Uplink TBF Establishment Failures due to Ms No Response

5 Number of Uplink TBF Normal Release

6 Number of Uplink TBF Abnormal Release due to N3101 Overflow (Ms No Response)

7 Number of Uplink TBF Abnormal Release due to N3103 Overflow (Ms No Response)

8 Number of Uplink TBF Abnormal Release due to SUSPEND

9 Number of Uplink TBF Abnormal Release due to FLUSH

10 Number of Uplink TBF Abnormal Release due to No Channel

11 Mean Number of Concurrent Uplink TBFs

12 Mean Duration Time of Uplink TBF(s)





Number of Uplink TBF Establishment Attempts Description

This item is used to measure the total number of the uplink TBF establishment attempts within a measurement period.

The purpose of establish an uplink TBF is to support the transfer of LLC PDUs in the direction from the mobile station to the network, and MS will initiate uplink TBF establishment on CCCH, PACCH, or PCCCH if present in the cell.

Measurement Point

The uplink TBF establishment attempt occurs in the following situations:

Step 1 Uplink TBF establishment using one phase access.

The mobile station initiates one phase access procedure by sending of CHANNEL REQUEST messages on RACH. When the PCU receives the CHANNEL REQUEST message which indicates one phase access for establishing uplink TBF from the MS, as the measurement point A referred in Figure 4-51, the value of this item is incremented by one.

Figure 4-51 Uplink TBF establishment attempt using one phase access

MS

A

CHANNEL REQUEST

NETWORK

Step 2 Uplink TBF establishment using single block.

The same procedures as for one phase access are used until the network sends a IMMEDIATE ASSIGNMENT message including a Single Block Allocation structure or Multi Block Allocation structure, denoting two phase access to the mobile station. In the IMMEDIATE ASSIGNMENT message, the network reserves a limited resource on one PDCH to the mobile station where the mobile station may transmit a PACKET RESOURCE REQUEST message. The mobile station initiates two phase access procedure by sending of CHANNEL REQUEST messages on RACH.

When the PCU receives PACKET RESOURCE REQUEST message for establishing uplink TBF from the MS, as the measurement point A referred in Figure 4-52, the value of this item is incremented by one.



Figure 4-52 Uplink TBF establishment attempt using single block

M S Network

A

CHANNEL REQUEST



Step 3 Uplink TBF establishment during a downlink TBF.

The mobile station may request establishment of an uplink transfer during a downlink TBF by including a Channel Request Description information element in the PACKET DOWNLINK ACK/NACK message Initiation is triggered by a request from upper layers to transfer a LLC PDU.

When the PCU receives the request message for establishing uplink TBF from the MS, as the measurement point A referred in Figure 4-53, the value of this item is incremented by one.

Figure 4-53 Uplink TBF Establishment attempt during a downlink TBF

M S Network

A


Effect of the Item

Firstly, together with the item Number of Uplink TBF Establishment Failures due to No Channel and Number of Uplink TBF Abnormal Release due to No Channel, this statistics item can reflect Uplink GPRS TBF Congestion Rate, which is used to measure the uplink TBF establishment congestion due to no radio resource during the measuring period.

%100×+=C

BARateC ongestionTBFU plink G PRS

ChannelNotodueFailuresentEstablishmTBFUplinkofNumberA −ChannelNotodueleaseAbnormalTBFUplinkofNumberB Re−

AttemptsentEstablishmTBFUplinkofNumberC −

Secondly, together with the item Number of Successful Uplink TBF Establishment, this statistics can reflect Uplink Assignment Success Rate, which is used to measure the uplink assignment success rate during the measuring period.




%100×=ABRateSuccessAssignmentUplink

AttemptsentEstablishmTBFUplinkofNumberA −entEstablishmTBFUplinkSuccessfulofNumberB −

Thirdly, together with other 7 measurement items, this statistics item can reflect PDCH Allocation Success Rate, which is used to measure PDCH allocation successful rate during the measuring period.

%1001 ×⎟⎠⎞

⎜⎝⎛

++++++−=

GECAHFDBRateSuccessAllocationPDCH

AttemptsentEstablishmTBFUplinkofNumberA −sponseNoMStodueFailuresentEstablishmTBFUplinkofNumberB Re−

AttemptsentEstablishmTBFDownlinkofNumberC −sponseNoMStodueFailuresentEstablishmTBFDownlinkofNumberD Re−

AttemptsentEstablishmTBFEGPRSUplinkofNumberE −sponseNoMStodueFailuresentEstablishmTBFEGPRSUplinkofNumberF Re−

AttemptsentEstablishmTBFEGPRSDownlinkofNumberG −sponseNoMStodueFailuresentEstablishmTBFEGPRSDownlinkofNumberH Re−


None

----End

Number of Successful Uplink TBF Establishment Description

This statistics item is used to measure the number of uplink TBF establishment successes within a measurement period.

Measurement Point

The successful uplink TBF establishment occurs in the following situations:

Step 1 Successful uplink TBF establishment using one phase access

Uplink TBF establishment will be successfully established using one phase access if uplink data blocks on PDCH assigned received after IMMEDIATE ASSIGNMENT sent. When the PCU receives the uplink data block from the MS after it sends immediate assignment message, as the measurement point A referred in Figure 4-54, the measured value will be incremented by one.



Figure 4-54 Successful uplink TBF establishment using one phase access

M S Network

A

CHANNEL REQUEST


UPLINK DATA BLOCK

Step 2 Successful uplink TBF establishment using single block

Uplink TBF establishment will be successfully establishmented using two phase access if uplink data blocks on PDCH assigned received after PACKET UPLINK ASSIGNMENT sent. When the PCU receives the uplink data block from the MS after it sends the uplink assignment message, as the measurement point A referred in Figure 4-55, the measured value will be incremented by one.

Figure 4-55 Successful uplink TBF establishment using single block

M S Network

A

RESOURCE REQUEST


UPLINK DATA BLOCK

Step 3 Successful uplink TBF establishment on PACCH

Uplink TBF establishment will be successfully establishmented on PACCH if uplink data blocks on PDCH assigned received after PACKET UPLINK ASSIGNMENT sent on PACCH. When the PCU receives the uplink data block from the MS after it sends the uplink assignment message, as the measurement point A referred in Figure 4-56, the measured value will be incremented by one.




Figure 4-56 Successful uplink TBF establishment on PACCH

M S Network

A


UPLINK DATA BLOCK

Effect of the Item

Firstly, together with the item Number of Uplink TBF Establishment Attempts, this statistics can reflect Uplink Assignment Success Rate, which is used to measure the Uplink assignment success rate during the measuring period.


AttemptsentEstablishmTBFUplinkofNumberA −entEstablishmTBFUplinkSuccessfulofNumberB −

Secondly, together with Number of Uplink TBF Abnormal Release due to N3101 Overflow (Ms No Response) and Number of Uplink TBF Abnormal Release due to N3103 Overflow (Ms No Response), this statistics item can reflect Uplink GPRS TBF Drop Rate, which is used to measure the uplink TBF drop rate during the measuring period.

%100×⎟⎠⎞⎜

⎝⎛ +=

ACBRateDropTBFUplink GRPS

entEstablishmTBFUplinkSuccessfulofNumberA −OverflowNtodueleaseAbnormalTBFUplinkofNumberB 3101Re−OverflowNtodueleaseAbnormalTBFUplinkofNumberC 3103Re−


Firstly, if the value of Uplink Assignment Successful rate is lower than 85%, some problems may lie in radio environment, network parameter configuration, network resource configuration and network equipment.

No channel resource or MS no response will cause uplink assignment failure. Therefore, please see more detailed analyzation from the corresponding part of Number of Uplink TBF Establishment Failures due to No Channeland Number of Uplink TBF Establishment Failures due to Ms No Response.

Number of Uplink TBF Establishment Failures due to No Channel Description

This statistics item is used to measure the number of uplink TBF establishment failures due to no radio channel resource within a measurement period.



Measurement Point

The uplink TBF establishment failures due to no channel occur in the following situations:

Step 1 Uplink TBF establishment failure due to no channel using one phase access

When the PCU receives a CHANNEL REQUEST message and finds that the uplink TBF can not be established because there is no more PDCH resource assigned to it or the resource assignment falls in with exception and fail, IMMEDIATE REJECT message will be sent on CCCH to MS to reject the access, as the measurement point A referred in Figure 4-57, the number of uplink TBF establishment failures due to no channel will be incremented by one.

Figure 4-57 Uplink TBF establishment failure due to no channel using one phase access

M S Network

A

CHANNEL REQUEST

IMMEDIATE REJECT

Step 2 Uplink TBF establishment failure due to no channel using single block

In two phase access procedure or when MS wants to change the current resource assignment, PCU will receive a RESOURCE REQUEST message from MS for establishing or re-establishing the uplink TBF.

If PCU finds that the uplink TBF can not be established because there is no more PDCH resource assigned to it or the resource assignment falls in with exception and fail, PACKET ACCESS REJECT message will be sent on PACCH to MS to reject the access, as the measurement point A referred in Figure 4-58, the number of uplink TBF establishment failures due to no channel will be incremented by one.

Figure 4-58 Uplink TBF establishment failure due to no channel using single block

M S Network

A

RESOURCE REQUEST

PACKET ACCESS REJECT

Step 3 Uplink TBF establishment failure due to no channel on PACCH




When the PCU receives CHANNEL REQUEST description in PACKET DOWNLINK ACK/NACK message, and finds that the uplink TBF can not be established because there is no more PDCH resource assigned to it or the resource assignment falls in with exception and fail, PACKET ACCESS REJECT message will be sent on PACCH to MS to reject the access, as the measurement point A referred in Figure 4-59, the number of uplink TBF establishment failures due to no channel will be incremented by one.

Figure 4-59 Uplink TBF establishment failure due to no channel on PACCH

M S Network

A


PACKET ACCESS REJECT

Effect of the Item

Together with the item Number of Uplink TBF Establishment Attempts and Number of Uplink TBF Abnormal Release due to No Channel, this statistics item can reflect Uplink GPRS TBF Congestion Rate, which is used to measure the uplink TBF establishment congestion due to no radio resource during the measuring period.

%100×+=C

BARateCongestionTBFUplink GPRS


AttemptsentEstablishmTBFUplinkofNumberC −


If the value of Uplink GPRS TBF Congestion rate is higher than 10% mainly caused by Number of uplink TBF establishment failures due to no channel, the cell uplink traffic may have exceeded the system capacity.

Please refer to “No Packet Resources” in 7.2.2 “Analyzing the Congestion Rate”.

Number of Uplink TBF Establishment Failures due to Ms No Response Description

This statistics item is used to measure the number of uplink TBF establishment failures due to MS no response within a measurement period.

Measurement Point

The uplink TBF establishment failures due to MS no response occurs in the following situations:

Step 1 Uplink TBF establishment failure due to MS no response using one phase access.



After sending IMMEDIATE ASSIGNMENT on CCCH, network begins to allocate valid USF for scheduling the uplink block resource. N3101 will be incremented by one everytime no data block received on corresponding frame, otherwise N3101 will be reset. The TBF will be released by network if N3101 reachs the threshold, and as the measurement point A referred in Figure 4-60, the Number of Uplink TBF Establishment Failures due to Ms No Response will be incremented by one as well.

Figure 4-60 Uplink TBF establishment failure due to MS no response using one phase access

M S Network

A

CHANNEL REQUEST


MS no response

N3101=N3101_MAX

Step 2 Uplink TBF establishment failure due to MS no response using single blocks

After sending PACKET UPLINK ASSIGNMENT on PDCH, network begins to allocate valid USF for scheduling the uplink block resource. N3101 will be incremented by one everytime no data block received on corresponding frame, otherwise N3101 will be reset. The TBF will be released by network if N3101 reachs the threshold, and as the measurement point A referred in Figure 4-61 the Number of Uplink TBF Establishment Failures due to Ms No Response will be incremented by one as well.

Figure 4-61 Uplink TBF establishment failure due to MS no response using single blocks

M S Network

A

RESOURCE REQUEST


MS no response....

N3101=N3101_MAX

Step 3 Uplink TBF establishment failure due to MS no response on PACCH

After sending IMMEDIATE ASSIGNMENT on PACCH, network begins to allocate valid USF for scheduling the uplink block resource. N3101 will be incremented by one everytime no data block received on corresponding frame, otherwise N3101 will be reset. The TBF will be released by network if N3101 reachs the threshold, and as the measurement point A referred in Figure 4-62, the Number of Uplink TBF Establishment Failures due to Ms No Response will be incremented by one as well.




Figure 4-62 Uplink TBF establishment failure due to MS no response on PACCH

M S Network

A


MS no response....

N3101=N3101_MAX

Effect of the Item

Together with other 7 measurement items, this statistics item can reflect PDCH Allocation Success Rate, which is used to measure PDCH allocation successful rate during the measuring period.

%1001 ×⎟⎠⎞

⎜⎝⎛

++++++−=







It is concluded that uplink TBF establishment failures due to MS no response mainly reflect uplink assignment successful rate directly, which will cause uplink TBF congestion rate effected.

Therefore, please refer to “ Low Successful Assignment Rate” in 7.2.2 “Analyzing the Congestion Rate”.

Number of Uplink TBF Normal Release Description

This statistics item is used to measure the number of uplink TBF normal releases within a measurement period.

Measurement Point When count down procedure begins and then the network receives the uplink RLC data block with CV=0, it will send PACKET UPLINK ACK/NACK with FAI=1 to initiate uplink TBF release procedure. When the uplink TBF is normally released, the network then will receive the PACKET CONTROL ACKOWNLEDGEMENT from MS, as the measurement point A referred in Figure 4-63, the number of normal uplink releases will be incremented by one.



Figure 4-63 Uplink TBF normal release

M S Network

A

PACKET UPLINK ACK/NACK FAI=1




Number of Uplink TBF Abnormal Release due to N3101 Overflow (Ms No Response)

Description This statistics item is used to measure the number of uplink TBF abnormal releases due to overflow of the uplink monitoring counter N3101 within a measurement period.

Measurement Point Network schedule every uplink data block resource by allocating valid USF for every MS which has been got accessed, and attach the USF information in every downlink block. N3101 will be incremented by one everytime no uplink data block received on corresponding frame, otherwise N3101 will be reset. The TBF will be released by network if N3101 reachs the threshold, and as the measurement point A referred in Figure 4-64, the number of uplink TBF abnormal release due to N3101 overflow will be incremented by one as well.

Figure 4-64 Uplink TBF abnormal release due to N3101 overflow

M S Network

A

RLC block(with USF valid)

RLC block (with USF valid)

NO RESPONSE FROM MS

N3101=N3101_MAX

Effect of the Item Together with Number of Successful Uplink TBF Establishment and Number of Uplink TBF Abnormal Release due to N3103 Overflow (Ms No Response), this statistics item




can reflect Uplink GPRS TBF Drop Rate, which is used to measure the uplink TBF drop rate during the measuring period.

%100×⎟⎠⎞⎜

⎝⎛ +=

ACBRateDropTBFUplink GPRS

entEstablishmTBFUplinkSuccessfulofNumberA −

OverflowNtodueleaseAbnormalTBFUplinkofNumberB 3101Re−OverflowNtodueleaseAbnormalTBFUplinkofNumberC 3103Re−

Huawei Recommendation It is concluded that uplink TBF abnormal release due to N3101 and N3103 overflow mainly reflect uplink TBF drop rate directly. There are two counters (N3101, N3103) monitor the uplink TBF link quality. If the uplink TBF is abnormally released due to the abnormality of these counters, it means the link is abnormal. If the abnormality rate of N3101 or N3103 is higher, it means maybe the quality of the transmission link is not good. Therefore, if the value of uplink GPRS TBF drop rate higher than 8%, please check TBF link quality including Abis link quality, G-Abis link quality and especially radio air interface quality.

Number of Uplink TBF Abnormal Release due to N3103 Overflow (Ms No Response)

Measurement Point Network initiates uplink TBF release procedure by sending a PACKET UPLINK ACK/NACK message with FAI=1, and wait MS reply PACKET CONTROL ACKOWNLEDGEMENT message to release the uplink TBF normally. N3103 will be incremented by one everytime no expected message received on corresponding frame, otherwise N3103 will be reset. The TBF will be released by network if N3103 reachs the threshold, and as the measurement point A referred in Figure Figure 4-65, the number of uplink TBF abnormal release due to N3103 overflow will be incremented by one as well.

Figure 4-65 Uplink TBF abnormal release due to N3103overflow

M S Network

A

PACKET UPLINK ACK/NACK(FAI=1)

NO RESPONSE FROM MS

N3103=N3103_MAX

PACKET UPLINK ACK/NACK(FAI=1)

Effect of the Item Together with Number of Successful Uplink TBF Establishment and Number of Uplink TBF Abnormal Release due to N3101 Overflow (Ms No Response), this statistics item can reflect Uplink GPRS TBF Drop Rate, which is used to measure the uplink TBF drop rate during the measuring period.



%100×⎟⎠⎞⎜

⎝⎛ +=

ACBRateDropTBFUplink GPRS

entEstablishmTBFUplinkSuccessfulofNumberA −

OverflowNtodueleaseAbnormalTBFUplinkofNumberB 3101Re−OverflowNtodueleaseAbnormalTBFUplinkofNumberC 3103Re−

Huawei Recommendation Refer to corresponding part introduction of the item Number of Uplink TBF Abnormal Release due to N3103 Overflow (Ms No Response).

Number of Uplink TBF Abnormal Release due to SUSPEND Description

This statistics item is used to measure the number of uplink TBF abnormal releases due to GPRS SUSPEND initiated by the MS within a measurement period.

Measurement Point While a circuit business request occurs with MS of Class B, no matter the MS in what status, the network will interrupt all the packet business of this MS. When the MS is in transfer mode with active uplink TBF, the MS will initiate suspend procedure by sending GPRS SUSPEND message, and as a result, the network will release the uplink TBF as response, and as the measurement point A referred in Figure 4-66, the number of uplink TBF abnormal releases due to SUSPEND will be incremented by one.

Figure 4-66 Uplink TBF abnormal release due to SUSPEND

M S Network

A

Uplink TBF Transfering

SUSPEND

Uplink TBF Release


Huawei Recommendation GPRS suspend procedure belongs to MS behavior, and it also causes the uplink TBF released abnormally, which will affect the uplink TBF drop rate indirectly.

Number of Uplink TBF Abnormal Release due to FLUSH Description

This statistics item is used to measure the number of uplink TBF abnormal releases due to the message FLUSH LL from SGSN to PCU within a measurement period.




Measurement Point While migrate to a new cell, SGSN will initiate cell update procedure and send FLUSH LL PDU to inform BSS. As a result, no matter the MS in what status, PCU will interrupt all the packet business of this MS in the old cell. When the MS is in transfer mode with active uplink TBF and the network receives FLUSH LL PDU from SGSN, the network will release the uplink TBF, and as the measurement point A referred in Figure 4-67, the Number of Uplink TBF Abnormal Release due to FLUSH will be incremented by one.

Figure 4-67 Uplink TBF abnormal release due to FLUSH

M S Network

A


Uplink TBF Release

FLUSH LL (SGSN)


Huawei Recommendation GPRS suspend due to FULSH procedure belongs to MS behavior, and it also causes the uplink TBF released abnormally, which will affect the uplink TBF drop rate indirectly. When the MS carries out the cell reselection during the process of PS service, it will lead to the FLUSH LL and make the uplink TBF released abnormally. In this situation, you shall focus on the items “Number of Uplink TBF Abnormal Release due to FLUSH”, “Number of Cell Selection by MS”, “Number of Cell Reselection at Short Interval by MS”, and “Number of Cell Ping-pong Reselection by MS” to check if MS migration between cells takes place frequently.

Number of Uplink TBF Abnormal Release due to No Channel Description

This statistics item is used to measure the number of uplink TBF abnormal release due to no channel.

Measurement Point If the PDCH channel resource is seized by BSC because of high priority of circuit business requests or the PDCH channel resource reached the max limitation, no matter the MS in what status, PCU will fail to get the PDCH channel resource. When the MS is in transfer mode with active uplink TBF and some PDCH channel resource is seized that there is no resource left with the uplink TBF, the network will release this uplink TBF, and as the measurement point A referred in Figure 4-68, the Number of Uplink TBF Abnormal Release due to FLUSH will be incremented by one.



Figure 4-68 Uplink TBF abnormal release due to no channel

M S Network

A


Uplink TBF Release

PDCH Unavailable

Effect of the Item Together with the item Number of Uplink TBF Establishment Failures due to No Channel and Number of Uplink TBF Establishment Attempts, this statistics item can reflect Uplink GPRS TBF Congestion Rate, which is used to measure the uplink GPRS TBF establishment congestion due to no radio resource during the measuring period.

%100×+=C

BARateCongestionTBFUplink GPRS


AttemptsentEstablishmTBFUplinkofNumberC − Huawei Recommendation

If the value of Uplink GPRS TBF Congestion rate is higher than 10% mainly caused by Number of Uplink TBF Abnormal Release due to No Channel, the cell uplink traffic may have exceeded the system capacity or the CS traffic in the cell shall be high which preempts dynamic channel resource. Make sure whether it is due to no packet resource caused by the reset of equipment, manual blocking of channel. Otherwise, the PS resources should be preempted by the CS service, you can analyze it with reference to the “Number of Dynamic PDCHs Reclaimed by BSC” and the traffic statistics items related to PDCH conversion. To ensure the stability of the PS service in the cell where the CS traffic is heavy, you can add the fixed channel to the cell. The increase of fixed channel may affect the coverage of GPRS service, thus you shall plan it in a whole.

Mean Number of Concurrent Uplink TBFs Description

This statistics item is used to measure the number of concurrent uplink TBFs have been setted up in a certain cell. This item indicates the uplink load of the cell.

Measurement Point Obtain the total number of uplink TBFs by measuring the number of concurrent uplink TBFs in the cell for N times during the measuring period. The mean number of uplink TBFs is equal to the total number of uplink TBFs divided by N.

12×=

PeriodMeasuringTBFsUplinkofNumberTotal

TBFsUplinkConcurrentofNumberMean




The sampling period is 5 seconds. Effect of the Item


None

Mean Duration Time of Uplink TBF(s) Description

This statistics item is used to measure the mean duration of uplink TBFs in a certain cell. Measurement Point

The total duration time of uplink TBFs can be obtained by measuring the duration time of all the uplink TBFs which were normal released during the measuring period. The meas duration time of uplink TBFs is equal to the total duration time of uplink TBFs divided by number of normal release uplink TBF. The PCU internal system clock is used unit Tick for timing, and 1 second equals 100 ticks.

( ) ( )100Re ×

=leaseNormalTBFUplinkofNumber

sTBFUplinkofTimeDurationTotalsTBFUplinkofTimeDurationMean

Effect of the Item


None

4.8.7 Downlink TBF Establishment/Release Measurement Table 4-14 lists the measurement items of the downlink TBF establishment/release measurement.

Table 4-14 Downlink TBF establishment/release measurement


1 Number of Downlink TBF Establishment Attempts

2 Number of Successful Downlink TBF Establishment

3 Number of Downlink TBF Establishment Failures due to No Channel

4 Number of Downlink TBF Establishment Failures due to MS No Response

5 Number of Downlink TBF Normal Release

6 Number of Downlink TBF Abnormal Release due to N3105 Overflow

7 Number of Downlink TBF Abnormal Release due to SUSPEND

8 Number of Downlink TBF Abnormal Release due to FLUSH

9 Number of Downlink TBF Abnormal Release due to No Channel

10 Mean Number of Concurrent Downlink TBFs

11 Mean Duration Time of Downlink TBF(s)




Number of Downlink TBF Establishment Attempts Description

This item is used to measure the total number of the downlink TBF establishment attempts within a measurement period.

The purpose of network initiated TBF establishment is to establish a TBF to support the transfer of LLC PDUs in the direction from the network to the mobile station. Network initiates downlink TBF establishment on CCCH(PCCCH) or PACCH.

Measurement Point

The downlink TBF establishment attempt occurs in the following situations:

Step 1 Establishment of Downlink TBF on CCCH.

The network initiates the packet downlink assignment procedure by sending an IMMEDIATE ASSIGNMENT message on the CCCH timeslot corresponding to CCCH group the mobile station belongs to. When the PCU sends the IMMEDIATE ASSIGNMENT message to attempt to establish downlink TBF, as the measurement point A referred in Figure 4-69, the value of this item is incremented by one.

Figure 4-69 Downlink TBF establishment attempt on CCCH

M S Network

A

IMMEDIATE ASSIGNMENT(On CCCH)　

Step 2 Establishment of Downlink TBF on PACCH.

The network may initiate a downlink TBF by sending a PACKET DOWNLINK ASSIGNMENT message to the mobile station on the PACCH during uplink transfer or release procedure of previous downlink TBF. When the PCU sends the PACKET DOWNLINK ASSIGNMENT message to attempt to establish downlink TBF, as the measurement point A referred in Figure 4-70, the value of this item is incremented by one.




Figure 4-70 Establishment of Downlink TBF on PACCH

M S Network

A


Effect of the Item

Firstly, together with the item Number of Downlink TBF Establishment Failures due to No Channel and Number of Downlink TBF Abnormal Release due to No Channel, this statistics item can reflect Downlink GPRS TBF Congestion Rate, which is used to measure the downlink TBF establishment congestion due to no radio resource during the measuring period.

%100×+=C

BARateCongestionTBFDownlink GPRS

ChannelNotodueFailuresentEstablishmTBFDownlinkofNumberA −ChannelNotodueleaseAbnormalTBFDownlinkofNumberB Re−

AttemptsentEstablishmTBFDownlinkofNumberC −

Secondly, together with the item Number of Successful Downlink TBF Establishment, this statistics can reflect Downlink Assignment Success Rate, which is used to measure the downlink assignment success rate during the measuring period.

%100×=ABRateSuccessAssignmentDownlink

AttemptsentEstablishmTBFDownlinkofNumberA −entEstablishmTBFDownlinkSuccessfulofNumberB −

Thirdly, together with other 7 measurement items, this statistics item can reflect PDCH Allocation Success Rate, which is used to measure PDCH allocation successful rate during the measuring period.

%1001 ×⎟⎠⎞

⎜⎝⎛

++++++−=


AttemptsentEstablishmTBFUplinkofNumberA −sponseNoMStoDueFailuresentEstablishmTBFUplinkofNumberB Re−







None

----End

Number of Successful Downlink TBF Establishment Description

This statistics item is used to measure the number of TBF establishment successes within a measurement period.

Measurement Point

The successful downlink TBF establishment occurs in the following situations:

Step 1 Successful establishment of Downlink TBF on CCCH

The downlink TBF will be establishment on CCCH by sending IMMEDIATE ASSIGNMENT message to MS with Starting Time value until which is timeout, network will send POLLING message to MS for get TA value for transmission.

When corresponding PACKET CONTROL ACKNOWLEDGEMENT to POLLING message is received by network, network will be able to calculate TA value and establish downlink TBF successfully, and as the measurement point A referred in Figure 4-71, the measured value will be incremented by one.

Figure 4-71 Successful establishment of Downlink TBF on CCCH

M S Network

A

IMMEDIATE ASSIGNMENT (CCCH)

POLLING(RRBP)

PACKET Control Acknowledgement

Step 2 Successful establishment of Downlink TBF on PACCH

When corresponding PACKET CONTROL ACKNOWLEDGEMENT to PACKET DOWNLINK ASSIGNMENT message on PACCH is received by network, network will be able to establish downlink TBF successfully, and as the measurement point A referred in Figure 4-72, the measured value will be incremented by one.




Figure 4-72 Successful establishment of Downlink TBF on PACCH

M S Network

A

Packet downlink assignment

PACKET Control Acknowledgement

Effect of the Item

Firstly, together with the item Number of Downlink TBF Establishment Attempts, this statistics can reflect Downlink Assignment Success Rate, which is used to measure the Uplink assignment success rate during the measuring period.


AttemptsentEstablishmTBFDownlinkofNumberA −entEstablishmTBFDownlinkSuccessfulofNumberB −

Secondly, together with Number of Downlink TBF Abnormal Release due to N3105 Overflow, this statistics item can reflect Downlink GPRS TBF Drop Rate, which is used to measure the uplink TBF drop rate during the measuring period.

%100×⎟⎠⎞⎜

⎝⎛=

ABRateDropTBFDownlink GPRS

entEstablishmTBFDownlinkSuccessfulofNumberA −OverflowNtodueleaseAbnormalTBFDownlinkofNumberB 3105Re−


Firstly, if the value of Downlink Assignment Successful rate is lower than 70%, some problems may lie in radio environment, network parameter configuration, network resource configuration and network equipment.

No channel resource or MS no response will cause downlink assignment failure. Therefore, please see more detailed analysis from the corresponding part of Number of Downlink TBF Establishment Failures due to No Channel and Number of Downlink TBF Establishment Failures due to MS No Response.

----End

Number of Downlink TBF Establishment Failures due to No Channel Description

This statistics item is used to measure the number of downlink TBF establishment failures due to no radio channel resource within a measurement period.



Measurement Point When the PCU receives new downlink PDUs from LLC layer but finds that the downlink TBF cannot be established due to no more channel resource, as the measurement point A referred in Figure 4-73, the number of downlink TBF establishment failures due to no radio channel resource will be incremented by one.

Figure 4-73 Downlink TBF establishment failures due to no channel

PCU SGSN

A

Downlink PDU

Discard

No channel

Effect of the Item Together with the item Number of Downlink TBF Establishment Attempts and Number of Downlink TBF Abnormal Release due to No Channel, this statistics item can reflect Downlink GPRS TBF Congestion Rate, which is used to measure the uplink TBF establishment congestion due to no radio resource during the measuring period.

%100×+=C



AttemptsentEstablishmTBFDownlinkofNumberC − Huawei Recommendation

If the value of Downlink GPRS TBF Congestion rate is higher than 10% mainly caused by Number of downlink TBF establishment failures due to no channel, the cell uplink traffic may have exceeded the system capacity. Please refer to “No Packet Resources” in 7.2.2 “Analyzing the Congestion Rate”.

Number of Downlink TBF Establishment Failures due to MS No Response Description

This statistics item is used to measure the number of downlink TBF establishment failures due to MS no response within a measurement period.

Measurement Point

The downlink TBF establishment failures due to MS no response occurs in the following situations:

Step 1 Downlink TBF establishment failure initiated on CCCH due to MS no response




In downlink TBF establishment procedure, network will send POLLING message and wait the response from MS for calculating TA value, and network will re-initiate downlink immediate assignment procedure several times if no response from MS until exceeding the maximum times, as the measurement point A referred in Figure 4-74, the number of downlink TBF establishment failures due to MS no response will be incremented by one.

Figure 4-74 Downlink TBF establishment failure initiated on CCCH due to MS no response

MS Network

A


POLLING(RRBP)



POLLING(RRBP)

POLLING(RRBP)

MS No Response....

Step 2 Downlink TBF establishment failure initiated on PACCH due to MS no response

The network may initiate a downlink TBF by sending a PACKET DOWNLINK ASSIGNMENT message to the mobile station on the PACCH during uplink transfer, release procedure of previous downlink TBF or re-assignment downlink resource for the current downlink TBF, and network will resend PACKET DOWNLINK ASSIGNMENT message several times if no response from MS until exceeding the maximum times, as the measurement point A referred in Figure 4-75, the number of downlink TBF establishment failures due to MS no response will be incremented by one.

Figure 4-75 Downlink TBF establishment failure initiated on PACCH due to MS no response

MS Network

A

PACKET DOWNLINK ASSIGNMENT(RRBP)

MS No Response....





Effect of the Item

Together with other 7 measurement items, this statistics item can reflect PDCH Allocation Success Rate, which is used to measure PDCH allocation successful rate during the measuring period.

%1001 ×⎟⎠⎞

⎜⎝⎛

++++++−=







It is concluded that downlink TBF establishment failures due to MS no response mainly reflect downlink assignment successful rate directly, which will cause downlink TBF congestion rate effected.

Therefore, please refer to “Low Successful Assignment Rate” in 7.2.2 “Analyzing the Congestion Rate”.

----End

Number of Downlink TBF Normal Release Description

This statistics item is used to measure the number of downlink TBF normal release within a measurement period.

Measurement Point Network will send the last data block with FBI=1 to initiate downlink TBF release procedure. When network receives the final DOWNLINK ACK/NACK with FAI=1, which indicates that MS has received all the blocks, network will release the downlink TBF successfully, and as the measurement point A referred in Figure 4-76, the number of downlink TBF normal releases will be incremented by one.




Figure 4-76 Downlink TBF normal release

MS Network

A

DOWNLINK DATA BLOCK FBI=1

DOWNLINK ACK/NACK FAI=1



Number of Downlink TBF Abnormal Release due to N3105 Overflow Description

This statistics item is used to measure the number of TBF abnormal releases due to overflow of the downlink monitoring counter N3105 within a measurement period.

Measurement Point Network will send the RLC data block with RRBP periodically to wait response of PACKET DOWNLINK ACK/NACK message from MS. N3105 will be incremented by one everytime no PACKET DOWNLINK ACK/NACK received on the same corresponding frame, otherwise N3105 will be reset. The TBF will be released by network if N3105 reaches the threshold, and as the measurement point A referred in Figure 4-77, the number of downlink TBF abnormal release due to N3105 overflow will be incremented by one as well.



Figure 4-77 Downlink TBF abnormal release due to N3105 overflow

MS Network

A

DOWNLINK DATA BLOCK (RRBP)



MS no response.....

Effect of the Item Together with Number of Successful Downlink TBF Establishment, this statistics item can reflect Downlink GPRS TBF Drop Rate, which is used to measure the downlink TBF drop rate during the measuring period.

%100×⎟⎠⎞⎜

⎝⎛=

ABRateDropTBFDownlink GPRS

entEstablishmTBFDownlinkSuccessfulofNumberA −

OverflowNtodueleaseAbnormalTBFDownlinkofNumberB 3105Re− Huawei Recommendation

It is concluded that downlink TBF abnormal release due to N3101 and N3103 overflow mainly reflect downlink TBF drop rate directly. There is a counter (N3105) monitors the downlink TBF link quality. If the downlink TBF is abnormally released due to the abnormality of the counter, it means the link is abnormal. If the abnormality rate of N3105 is higher, it means maybe the quality of the transmission link is not good. Therefore, if the value of downlink GPRS TBF drop rate is higher than 8%, please check TBF link quality including radio air interface quality, Abis link quality and G-Abis link quality.

Number of Downlink TBF Abnormal Release due to SUSPEND Description

This statistics item is used to measure the number of downlink TBF abnormal releases due to GPRS SUSPEND initiated by the MS within a measurement period.

Measurement Point While a circuit business request occurs with MS of Class B, no matter the MS in what status, the network will interrupt all the packet business of this MS. When the MS is in transfer mode with active downlink TBF, the MS will initiate suspend procedure by sending GPRS SUSPEND message, and as a result, the network will release the downlink TBF as response, and as the measurement point A referred in Figure 4-78, the Number of Downlink TBF Abnormal Release due to SUSPEND will be incremented by one.




Figure 4-78 Downlink TBF abnormal release due to SUSPEND

MS Network

A

DOWNLINK TBF Transfering

SUSPEND

DOWNLINK TBF Release


Huawei Recommendation GPRS suspend procedure belongs to MS behavior, and it also causes the downlink TBF released abnormally, which will affect the downlink TBF drop rate indirectly.

Number of Downlink TBF Abnormal Release due to FLUSH Description

This statistics item is used to measure the number of downlink TBF abnormal releases due to FLUSH LL message from SGSN to PCU within a measurement period.

Measurement Point While migrate to a new cell, SGSN will initiate cell update procedure and send FLUSH LL PDU to inform BSS. As a result, no matter the MS in what status, PCU will interrupt all the packet business of this MS in the old cell. When the MS is in transfer mode with active downlink TBF and the network receives FLUSH LL PDU from SGSN, the network will release the downlink TBF, and as the measurement point A referred in Figure 4-79, the number of downlink TBF abnormal releases due to FLUSH will be incremented by one.



Figure 4-79 Downlink TBF abnormal release due to FLUSH

MS Network

A



FLUSH LL (SGSN)


Huawei Recommendation GPRS suspend procedure belongs to MS behavior, and it also causes the downlink TBF released abnormally, which will affect the downlink TBF drop rate indirectly. When the MS carries out the cell reselection during the process of PS service, it will lead to the FLUSH LL and make the downlink TBF released abnormally. In this situation, you shall focus on the items “Number of Downlink TBF Abnormal Release due to FLUSH”, “Number of Cell Selection by MS”, “Number of Cell Reselection at Short Interval by MS”, and “Number of Cell Ping-pong Reselection by MS” to check if MS migration between cells takes place frequently.

Number of Downlink TBF Abnormal Release due to No Channel Description

This statistics item is used to measure the number of downlink TBF abnormal releases due to no channel within a measurement period.

Measurement Point If the PDCH channel resource is seized by BSC because of high priority of circuit business requests or the PDCH channel resource reached the max limitation, no matter the MS in what status, PCU will fail to get the PDCH channel resource. When the MS is in transfer mode with active downlink TBF and some PDCH channel resource is seized that there is no resource left with the downlink TBF, the network will release this downlink TBF, and as the measurement point A referred in Figure 4-80, the number of downlink TBF abnormal releases due to no channel will be incremented by one.




Figure 4-80 Downlink TBF abnormal release due to no channel

MS Network

A



PDCH Unavailable

Effect of the Item Together with the item Number of Downlink TBF Establishment Failures due to No Channeland Number of Downlink TBF Establishment Attempts, this statistics item can reflect Downlink GPRS TBF Congestion Rate, which is used to measure the downlink TBF establishment congestion due to no radio resource during the measuring period.

%100×+=C



AttemptsentEstablishmTBFDownlinkofNumberC − Huawei Recommendation

If the value of Downlink GPRS TBF Congestion rate is higher than 10% mainly caused by Number of Downlink TBF Abnormal Release due to No Channel, the cell downlink traffic may have exceeded the system capacity or the CS traffic in the cell shall be high which preempts dynamic channel resource. Make sure whether it is due to no packet resource caused by the reset of equipment, manual blocking of channel. Otherwise, the PS resources should be preempted by the CS service, you can analyze it with reference to the “Number of Dynamic PDCHs Reclaimed by BSC” and the traffic statistics items related to PDCH conversion. To ensure the stability of the PS service in the cell where the CS traffic is heavy, you can add the fixed channel to the cell. The increase of fixed channel may affect the coverage of GPRS service, thus you shall plan it in a whole.

Mean Number of Concurrent Downlink TBFs Description

This statistics item is used to measure the number of concurrent downlink TBFs have been setted up in a certain cell. This item indicates the downlink load of the cell.

Measurement Point Obtain the total number of downlink TBFs by measuring the number of concurrent downlink TBFs in the cell for N times during the measuring period. The mean number of downlink TBFs is equal to the total number of downlink TBFs divided by N.



12×=

PeriodMeasuringTBFsDownlinkofNumberTotal

TBFsDownlinkConcurrentofnumberMean



None

Mean Duration Time of Downlink TBF(s) Description

This statistics item is used to measure the mean duration of downlink TBFs in a certain cell.

Measurement Point The total duration time of downlink TBFs can be obtained by measuring the duration time of all the downlink TBFs which were normal released during the measuring period. The mean duration time of downlink TBFs is equal to the total duration time of downlink TBFs divided by number of normal release downlink TBF. The PCU internal system clock is used unit Tick for timing, and 1 second equals 100 ticks.

( ) ( )100Re ×

=leaseNormalTBFDownlinkofNumber

sTBFDownlinkofTimeDurationTotalsTBFDownlinkoftimeDurationMean



4.8.8 Uplink LLC Data Transmission Measurement Table 4-15 lists the measurement items of the uplink LLC data transmission measurement.

Table 4-15 Uplink LLC data transmission measurement


1 Total Number of Uplink TBFs

2 Total Number of Uplink LLC_PDUs Sent

3 Total Bytes of Uplink LLC_PDUs Sent

4 Mean Length of Uplink LLC_PDUs

5 Mean LLC_PDU Bytes per Uplink TBF

6 Uplink Throughput (kbit/s)





Total Number of Uplink TBFs Description

This measurement is used to measure the total number of uplink TBFs established during the measuring period.

Measurement Point When the network has established an uplink TBF successfully, the total number of uplink TBFs will be incremented by one. Please refer to Figure 4-81, the total number of uplink TBFs will be incremented by one.

Figure 4-81 Uplink TBF established successfully

MS Network

A

Packet Uplink Assignment

Uplink RLC data block (FIRST)


Huawei Recommendation Please refer to.“Measuring the TBF Traffic” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer”.

Total Number of Uplink LLC_PDUs Sent Description

This statistics item is used to measure the total number of uplink LLC PDUs sent during the measuring period.

Measurement Point When the UPLINK LLC PDU is sent to the Gb interface, as the measurement point A referred in Figure 4-82, the measured value will be incremented by one.



Figure 4-82 A Uplink LLC PDU sent to Gb interface

PCU SGSN

A

Uplink LLC PDU



Total Bytes of Uplink LLC_PDUs Sent Description

This statistics item is used to measure the total byte number of uplink LLC PDUs during the measuring period.

Measurement Point When the UPLINK LLC PDU is sent to the Gb interface, as the measurement point A referred in Figure 4-82, the measured value will be incremented by the byte number of the corresponding LLC PDU.

Effect of the Item This item can reflect the item Uplink LLC PDU Payload, which is used to measure the mean payload (kbit/s) of the uplink data at the LLC layer during the measuring period.

( )1024

8_ ×=

SentPDUsLLCUplinkofBytesTotalkbitsPayloadPDULLCUplink


None

Mean Length of Uplink LLC_PDUs Description

This statistics item is used to measure the total byte number of uplink LLC PDUs during the measuring period.

Measurement Point

( )SentPDUsLLCUplinkofNumberTotal

SentPDUsLLCUplinkofBytesTotalbytesPDUsLLCUplinkofLengthMean

__

_ =

Effe Effect of the Item


Please refer to 7.4.1 “Measuring the Traffic of LLC Layer”.




Mean LLC_PDU Bytes per Uplink TBF Description

This statistics item is used to measure the mean byte number of LLC PDUs transmitted in per uplink TBF during the measuring period.

Measurement Point

( )TBFsUplinkofNumberTotal

SentPDUsLLCUplinkofBytesTotalbytesTBFUplinkperBytesPDULLCMean __ =


Huawei Recommendation Please refer to 7.4.1 “Measuring the Traffic of LLC Layer”.

Uplink Throughput (kbit/s) Description

This statistics item is used to measure the mean rate (kbit/s) of the uplink data at the LLC layer during the measuring period.

Measurement Point

( ) ( )6010248_

/××

×=

PeriodMeasuringSentPDUsLLCUplinkofBytesTotal

skbitsThroughputUplink



4.8.9 Downlink LLC Data Transmission Measurement Table 4-16 lists the measurement items of the downlink LLC data transmission measurement.

Table 4-16 Downlink LLC data transmission measurement


1 Total Number of Downlink TBFs

2 Total Number of Downlink LLC_PDUs Received

3 Total Bytes of Downlink LLC_PDUs Received

4 Total Number of LLC_PDUs Sent

5 Total Bytes of LLC_PDUs Sent

6 Number of Downlink LLC_PDUs Discarded due to Time-

7 Number of Downlink LLC_PDUs Discarded due to FLUSH_LL Received

8 Mean Length of Downlink LLC_PDUs

9 Mean LLC_PDU Bytes per Downlink TBF




10 Downlink Throughput (kbit/s)


Total Number of Downlink TBFs Description

This statistics item is used to measure the total number of downlink TBFs established during the measuring period.

Measurement Point When the network has established a downlink TBF successfully, the total number of downlink TBFs will be incremented by one. Please refer to Number of Successful Downlink TBF Establishment.


Huawei Recommendation Please refer to 268.5.807017750 “Measuring the TBF Traffic” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer”.

Total Number of Downlink LLC_PDUs Received Measurement Item

“Total number of downlink LLC_PDUs received” Description

This statistics item is used to measure the total number of downlink LLC_PDUs during the measuring period.

Measurement Point When the DOWNLINK LLC PDU is received, as the measurement point A referred in Figure 4-83, the measured value will be incremented by one.

Figure 4-83 A Downlink LLC PDU received from Gb interface

PCU Network

A

Downlink LLC PDU






None

Total Bytes of Downlink LLC_PDUs Received Description

This statistics item is used to measure the total bytes number of downlink LLC PDUs received during the measuring period.

Measurement Point When the DOWNLINK LLC PDU is received, as the measurement point A referred in Figure 4-83, the measured value will be incremented by the byte number of the corresponding LLC PDU.



Total Number of LLC_PDUs Sent Description

This statistics item is used to measure the total number of LLC PDUs successfully delivered during the measuring period.

Measurement Point When Network receives the PACKET DOWNLINK ACK/NACK message sent by Mobile Station, the network will get to know which LLC PDU is successfully delivered and should be removed from the PDU queue.

Figure 4-84 Network receives the PACKET DOWNLINK ACK/NACK message

MS Network

A

PACKET DOWNLINK ACK/NACK

When the LLC PDU is successfully delivered and removed from the PDU queue, as the measurement point A referred in Figure 4-84, the measured value will be incremented by one.



Total Bytes of LLC_PDUs Sent Description



This statistics item is used to measure the total byte number of LLC PDUs successfully delivered during the measuring period.

Measurement Point When network receives the PACKET DOWNLINK ACK/NACK message sent by Mobile Station, the network will get to know which LLC PDU is successfully delivered and should be removed from the PDU queue. When the LLC PDU is successfully delivered, as the measurement point A referred in Figure 4-84, the measured value will be incremented by the byte number of the corresponding LLC PDU.

Effect of the Item This item can reflect the item Downlink LLC PDU Payload, which is used to measure the mean payload (kbit/s) of the downlink data at the LLC layer during the measuring period.

( )1024

8_ ×=

SentPDUsLLCDownlinkofBytesTotalkbitsPayloadPDULLCDownlink


None

Number of Downlink LLC_PDUs Discarded due to Time-out Description

This statistics item is used to measure the number of downlink LLC PDUs discarded due to timeout during the measuring period.

Measurement Point When network receives the PACKET DOWNLINK ACK/NACK message sent by Mobile Station, the network will get to know which LLC PDU is successfully delivered and should be removed from the PDU queue, while others which are not received successfully should be saved in the send queue for some time. Periodically, the network will check every PDUs’ lifetime which is defined by core network and discard those PDUs whose lifetime timeout, and then send LLC DISCARDED message to SGSN to inform the LLC PDU retransmission. When the LLC PDU is discarded due to timeout of life cycle, as the measurement point A referred in Figure 4-85, the number of downlink LLC PDUs discarded due to timeout will be incremented by one.

Figure 4-85 Downlink LLC_PDUs discarded due to time-out

PCU SGSN

A

LLC DISCARDED





Huawei Recommendation If the number of downlink LLC PDUs discarded due to timeout is relatively high, which indicates that many PDUs haven’t been transmitted by PCU immediately, and consequently retransmission will take place in Gb interface which will lead to poor performance. You should check Uplink/Downlink GPRS TBF Congestion Rate and Uplink/Downlink GPRS TBF Drop Rate and make further analysis.

Number of Downlink LLC_PDUs Discarded due to FLUSH_LL Received Description

This statistics item is used to measure the number of downlink LLC PDUs discarded due to the message FLUSH LL received by PCU during the measurement.

Measurement Point When an SGSN detects a cell change of an MS from a cell update or a routing area update, the SGSN shall send a FLUSH-LL PDU to the old BVC to initiate the following procedures: at a cell change within one NSE (e.g. the BSS is a NSE) and within one routing area, LLC-PDUs for a given TLLI stored at an "old" BVCI (corresponding to the old cell) are either deleted or transferred to a "new" BVCI (corresponding to the new cell) with which the TLLI is currently associated; or at a cell change between two NSEs within one routing area, LLC PDUs for a given TLLI stored at an “old” BVCI (corresponding to the old cell) are either deleted or transferred to a “new” BVCI (corresponding to the new cell) with which the TLLI is currently associated. In that case, transferring of LLC PDUs can only be requested by the SGSN if the NSE underlying the “old” BVCI indicated support for the “Inter-NSE re-routing”; or at a cell change between two routing areas, LLC-PDUs stored at the "old" BVCI for the TLLI are deleted. As a result, when the LLC PDU is discarded due to the message FLUSH LL received by PCU, as the measurement point A referred in Figure 4-86, the number of LLC PDUs discarded due to FLUSH will be incremented by one.

Figure 4-86 Downlink LLC_PDUs discarded due to FLUSH_LL received

PCU SGSN

A

LLC DISCARDED

FLUSH LL PDU

FLUSH LL ACK PDU





Mean Length of Downlink LLC_PDUs Description

This statistics item is used to measure the mean byte number of downlink LLC PDUs during the measuring period. The LLC PDU size for the FTP service is relatively large, while that for the WAP service is relatively small.

Measurement Point

( )ceivedPDUsLLCDownlinkofNumberTotal

ceivedPDUsLLCDownlinkofBytesTotalbytesPDUsLLCDownlinkofLengthMean

Re_Re_

_ =



Mean LLC_PDU Bytes per Downlink TBF Description

This statistics item is used to measure the mean byte number of downlink LLC_PDUs transmitted in per downlink TBF during the measuring period. The mean LLC_PDU bytes per TBF of the FTP service are relatively large, while those of the WAP service are relatively small.

Measurement Point

( )TBFsDownlinkofNumberTotalSentPDUsLLCofBytesTotal

bytesTBFDownlinkperBytesPDULLCMean_

_ =



Downlink Throughput (kbit/s) Measurement Item

This statistics item is used to measure the mean rate (kbit/s) of the downlink data at the LLC layer during the measuring period.

Measurement Point

( ) ( )6010248_

/××

×=

PeriodMeasuringSentPDUsLLCofBytesTotal

skbitsThroughputDownlink



4.8.10 Uplink RLC Data Transmission Measurement Table 4-17 lists the measurement items of the uplink RLC data transmission measurement.




Table 4-17 Uplink RLC data transmission measurement


1 Total Number of Uplink RLC Data Blocks

2 Mean Payload of Uplink Single TBF (kbit/s)

3 Number of Uplink RLC Data Blocks Using CS-1




7 Retransmission Rate of Uplink RLC Data Block Using CS-1 (%)




11 Number of CS Upgrades on Uplink TBF

12 Number of CS Demotions on Uplink TBF

13 Number of Uplink RLC Control Blocks

14 Mean Throughput of Uplink RLC (kbit/s)


Total Number of Uplink RLC Data Blocks Description

This statistics item is used to measure the number of uplink RLC data blocks sent during the measuring period.

Measurement Point This item is calculated by the item Number of Uplink RLC Data Blocks Using CS-1, the item Number of Uplink RLC Data Blocks Using CS-2, the item Number of Uplink RLC Data Blocks Using CS-3, and the item Number of Uplink RLC Data Blocks Using CS-4 during the measuring period as follow.

DCBA +++= Blocks DataRLC Uplink ofNumber Total1-CS UsingBlocks Data RLC Uplink ofNumber −A2-CS UsingBlocks Data RLC Uplink ofNumber −B3-CS UsingBlocks Data RLC Uplink ofNumber −C4-CS UsingBlocks Data RLC Uplink ofNumber −D

Effect of the Item Together with the item Retransmission Rate of Uplink RLC Data Block Using CS-1 (%), the item Retransmission Rate of Uplink RLC Data Block Using CS-2 (%), the item Retransmission Rate of Uplink RLC Data Block Using CS-3 (%), and the item Retransmission Rate of Uplink RLC Data Block Using CS-4 (%), this item can reflect



the item Retransmission Rate of Uplink RLC Data Block, which is used to measure the ratio of retransmitted uplink RLC data blocks using CS-1~CS-4 during the measuring period.

100% )E

DCA - (1 (%)Block Data RLC Uplink of Ratesion Retransmis ×+++= B

1CSgUBlocksDataRLCUplinkofRateontransmissiA −− sinRe2CSgUBlocksDataRLCUplinkofRateontransmissiB −− sinRe3CSgUBlocksDataRLCUplinkofRateontransmissiC −− sinRe4CSgUBlocksDataRLCUplinkofRateontransmissiD −− sinRe

Blocks Data RLC Uplink ofNumber Total−E Huawei Recommendation

If the value of Retransmission rate of uplink RLC data block is higher than 2%, the quality of the transmission link of cell may be poor. Therefore, please check TBF link quality including Abis link quality, G-Abis link quality and especially radio air interface quality.

Mean Payload of Uplink Single TBF (kbit/s) Description

This statistics item is used to measure the mean throughput of each uplink TBF during the measuring period.

Measurement Point This item is calculated by the item Number of Uplink RLC Data Blocks Using CS-1, the item Number of Uplink RLC Data Blocks Using CS-2, the item Number of Uplink RLC Data Blocks Using CS-3, and the item Number of Uplink RLC Data Blocks Using CS-4 during the measuring period as follow.

( ) 1024E

8 54 D 40 C 34 B 23A TBF Single Uplink of Throughputean ×

××+×+×+×=M

1-CS UsingBlocks Data RLC Uplink ofNumber −A2-CS UsingBlocks Data RLC Uplink ofNumber −B3-CS UsingBlocks Data RLC Uplink ofNumber −C4-CS UsingBlocks Data RLC Uplink ofNumber −D

Successesent Establishm TBF Uplink ofNumber −E The length of RLC blocks using code scheme with CS-1, CS-2, CS-3 and CS-4 is respectively 23, 34, 40 and 54 octets.


Huawei Recommendation Please refer to 268.5.807017750 .“Measuring the TBF Traffic” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer”.

Number of Uplink RLC Data Blocks Using CS-1 Description

This statistics item is used to measure the number of RLC data blocks using CS-1 sent during the measuring period.

Measurement Point




Total number of uplink RLC data blocks using CS-1 sent by MS is measured as follow:

Step 1 If the specified uplink RLC data block is received by BSS for the first time and it has been sent by MS for more than once, which indicates that its corresponding element in V(N) at network side has got the value NACKED, the number of uplink RLC data block with CS-1 sent by MS will be incremented by two.

Step 2 If the specified uplink RLC data block with CS-1 is received by BSS for the first time and it has been sent by MS only once, which indicates that its corresponding element in V(N) at network side has got the value UNRECEIVED, the number of uplink RLC data block with CS-1 sent by MS will be incremented by one.

Step 3 If the specified uplink RLC data block with CS-1 received by BSS has already been received, which indicates that its corresponding element in V(N) at network side has got the value RECEIVED, the number of uplink RLC data block with CS-1 sent by MS will be incremented by one.

Effect of the Item

None


None

----End

Number of Uplink RLC Data Blocks Using CS-2 Please refer to the instruction of the item Number of Uplink RLC Data Blocks Using CS-1, while the only difference is that uplink RLC data blocks using CS-2 code scheme are involved for measurement.



Retransmission Rate of Uplink RLC Data Block Using CS-1 (%) Description

This statistics item is used to measure the retransmission rate of uplink RLC data block using CS-1 received during the measuring period.

Measuring point This item is calculated by the item Number of Uplink RLC Data Blocks Using and the item “Number of uplink RLC data blocks using CS-1 received by BSS” which will be incremented by one when an uplink RLC data block using CS-1 is received by BSS.



%1001sinRe ×⎟⎠⎞

⎜⎝⎛ −=−

ABACSgUBlockDataRLCUplinkofRateontransmissi

1sin −− CSgUBlocksDataRLCUplinkofNumberABSSbyceivedCSgUBlocksDataRLCUplinkofNumberB Re1sin −−


Huawei Recommendation This measured value is used to analyze the transmission quality of the uplink radio channel. If the value of the item is out of the reference value of 0%~10%, it means that the link for transmission in the cell is relatively bad.

Retransmission Rate of Uplink RLC Data Block Using CS-2 (%) Please refer to the instruction of the item Retransmission Rate of Uplink RLC Data Block Using CS-1 (%), while the difference is that only uplink RLC data blocks using CS-2 code scheme are involved for measurement.



Number of CS Upgrades on Uplink TBF Description

This statistics item is used to measure the number of CS upgrades on the uplink TBF during the measuring period. This measured value is used to analyze the transmission quality of the uplink radio channel.

Measurement Point Every time network changes the CS type, it will compare the current CS type with the previous one, and get to know the CS type change is upgrade or demotions. When the CS type used by the uplink RLC data blocks is upgraded, as the measurement point A referred in Figure 4-87, the Number of CS upgrades on uplink TBF will be incremented by one.




Figure 4-87 Uplink GPRS TBF data transfer with CS upgrades

MS Network

A

UPLIINK RLC DATA BLOCK (LOWER CS TYPE)

UPLIINK RLC DATA BLOCK (HIGHER CS TYPE)


Huawei Recommendation If the number of CS upgrades on uplink or downlink TBF is quite large, it indicates that the CS code scheme is always changing because of unstable quality of Um interface, which also causes poor performance in packet transmission.

Number of CS Demotions on Uplink TBF Description

This statistics item is used to measure the number of CS demotions on the uplink TBF during the measuring period. This measured value is used to analyze the transmission quality of the uplink radio channel.

Measurement Point Every time network changes the CS type, it will compare the current CS type with the previous one, and get to know the CS type change is upgrade or demotions. When the CS type used by the uplink RLC data blocks is demoted, as the measurement point A referred in Figure 4-88, the Number of CS demotions on uplink TBF will be incremented by one.

Figure 4-88 Uplink GPRS TBF data transfer with CS demotions

MS PCU

A

UL GPRS RLC DATA BLK (LOWER CS )

UL GPRS RLC DATA BLK (HIGHER CS)





If the number of CS upgrades on uplink or downlink TBF is quite large, it indicates that the CS code scheme is always changing because of unstable quality of Um interface, which also causes poor performance in packet transmission.

Number of Uplink RLC Control Blocks Description

This statistics item is used to measure the number of RLC control blocks on the uplink TBF during the measuring period.

Measurement Point When PACKET UPLINK ACK/NACK message for acknowledgement to uplink RLC data blocks transmission is sent by network, as the measurement point A referred in Figure 4-89, the number of uplink RLC control blocks is incremented by one.

Figure 4-89 Uplink TBF with RLC control block with PAKCET UPLINK ACK/NACK message

MS Network

A

PACKET UPLINK ACK/NACK

Besides, when PACKET CONTROL ACKNOWLEDGEMENT message of uplink TBF is received by network, the number of uplink RLC control blocks is incremented by one.



Mean Throughput of Uplink RLC (kbit/s) Description

This statistics item is used to measure the mean data transmission rate of uplink RLC layer within the measuring period.

Measurement Point First of all, the item Uplink RLC Payload is calculated by the item Number of Uplink RLC Data Blocks Using CS-1, the item Number of Uplink RLC Data Blocks Using CS-2, the item Number of Uplink RLC Data Blocks Using CS-3, the item Number of Uplink RLC Data Blocks Using CS-4 during the measuring period as follow.

( ) ( )1024

854D40C34B23A ××+×+×+×=kbitsPayloadRLCUplink

1-CS UsingBlocks Data RLC Uplink ofNumber −A2-CS UsingBlocks Data RLC Uplink ofNumber −B3-CS UsingBlocks Data RLC Uplink ofNumber −C4-CS UsingBlocks Data RLC Uplink ofNumber −D




The length of RLC blocks using code scheme with CS-1, CS-2, CS-3 and CS-4 is respectively 23, 34, 40 and 54 octets. Furthermore, this item is calculated by the item Uplink RLC Payload and the time length of the measuring period during the measuring period as follow.

( )60PeriodtMeasuremen

kbits/sRLC UplinkofThroughputMean×

= PayloadRLCUplink

Effect of the Item

Together with the item Uplink EGPRS RLC Payload referred in “Mean rate of uplink EGPRS RLC”, the item Downlink RLC Payload referred in “Mean rate of downlink RLC”, the item “Downlink EGPRS RLC Payload” referred in “Mean rate of downlink EGPRS RLC”, this item can reflect the item Packet Data Rate on Air Interface (UL/DL), which is used to measure the packet data rate between uplink and downlink RLC payload on air interface during the measuring period.

PayloadRLCEGPRSDownlinkPayloadRLCDownlinkPayloadRLCEGPRSUplinkPayloadRLCUplink InterfaceAironRateDataacketP

++

=

Huawei Recommendation Please refer to “Measuring the TBF Traffic” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer”.

4.8.11 Downlink RLC Data Transmission Measurement Table 4-18 lists the measurement items of the downlink RLC data transmission measurement.

Table 4-18 Downlink RLC data transmission measurement


1 Total Number Downlink RLC Data Blocks

2 Mean Payload of Downlink Single TBF (kbit/s)

3 Number of Downlink RLC Data Blocks Using CS-1




7 Retransmission Rate of Downlink RLC Data Blocks Using CS-1(%)




11 Number of CS Upgrades on Downlink TBF

12 Number of CS Demotions on Downlink TBF

13 Number of Downlink RLC Control Blocks

14 Number of Downlink RLC Dummy Blocks




15 Mean Throughput of Downlink RLC (kbit/s)


Total Number Downlink RLC Data Blocks Description

This statistics item is used to measure the number of downlink RLC data blocks sent during the measuring period.

Measurement Point This item is calculated by the item Number of Downlink RLC Data Blocks Using CS-1, the item Number of Downlink RLC Data Blocks Using CS-2, the item Number of Downlink RLC Data Blocks Using CS-3, and the item Number of Downlink RLC Data Blocks Using CS-4 during the measuring period as follow.

DCBA blocks dataRLC downlink of numberTotal +++=1-CS using blocks data RLC downlink of NumberA −2-CS using blocks data RLC downlink of NumberB −3-CS using blocks data RLC downlink of NumberC −4-CS using blocks data RLC downlink of NumberD −

Effect of the Item Together with the item Retransmission Rate of Downlink RLC Data Blocks Using CS-1(%), the item Retransmission Rate of Downlink RLC Data Blocks Using CS-2(%),the item Retransmission Rate of Downlink RLC Data Blocks Using CS-3(%), and the item Retransmission Rate of Downlink RLC Data Blocks Using CS-4(%), this item can reflect the item Retransmitted Rate of RLC Downlink Data Block, which is used to measure the ratio of retransmitted downlink RLC data blocks using CS-1~CS-4 during the measuring period.

100% )E

DCA - (1 (%)Block DataRLCDownlink of Ratesion Retransmis ×+++= B

1CSgUBlocksDataRLCDownlinkofRateontransmissiA −− sinRe2CSgUBlocksDataRLCDownlinkofRateontransmissiB −− sinRe3CSgUBlocksDataRLCDownlinkofRateontransmissiC −− sinRe4CSgUBlocksDataRLCDownlinkofRateontransmissiD −− sinRe

Blocks Data RLCDownlink ofNumber Total−E Huawei Recommendation

If the value of Retransmission rate of downlink RLC data block is higher than 15%, the quality of the transmission link of cell may be poor. Therefore, please check TBF link quality including Abis link quality, G-Abis link quality and especially radio air interface quality.

Mean Payload of Downlink Single TBF (kbit/s) Description

This statistics item is used to measure the mean throughput of each downlink TBF during the measuring period.




Measurement Point This item is calculated by the item Number of Downlink RLC Data Blocks Using CS-1, the item Number of Downlink RLC Data Blocks Using CS-2, the item Number of Downlink RLC Data Blocks Using CS-3, and the item Number of Downlink RLC Data Blocks Using CS-4 during the measuring period as follow.

( ) 1024E

8 54 D 40 C 34 B 23A TBF SingleDownlink of Throughputean ×

××+×+×+×=M

1-CS UsingBlocks Data RLCDownlink ofNumber −A2-CS UsingBlocks Data RLCDownlink ofNumber −B3-CS UsingBlocks Data RLCDownlink ofNumber −C4-CS UsingBlocks Data RLCDownlink ofNumber −D

Successesent Establishm TBFDownlink ofNumber −E The length of RLC blocks using code scheme with CS-1, CS-2, CS-3 and CS-4 is respectively 23, 34, 40 and 54 octets.


Huawei Recommendation Please refer to 61757428.5.807017750 .“Measuring the TBF Traffic” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer”.

Number of Downlink RLC Data Blocks Using CS-1 Description

This statistics item is used to measure the number of RLC data blocks using CS-1 sent during the measuring period.

Measurement Point When the RLC data block with CS-1 CS type is sent to MS by BSS, as the measurement point A referred in Figure 4-90, the measured value will be incremented by one.

Figure 4-90 Downlink RLC data blocks with CS-1 CS type transmission

MS Network

A

DOWNLINK RLC DATA BLOCK(CS-1)



Number of Downlink RLC Data Blocks Using CS-2 Please refer to the instruction of the item Number of Downlink RLC Data Blocks Using CS-1, while the only difference is that downlink RLC data blocks using CS-2 code scheme are involved for measurement.





Retransmission Rate of Downlink RLC Data Blocks Using CS-1(%) Description

This statistics item is used to measure the ratio of retransmitted RLC data blocks using CS-1 during the measuring period.

Measuring point This item is calculated by the item Number of Downlink RLC Data Blocks Using CS-1 and the item “Number of downlink RLC data blocks using CS-1 received by MS”, which will be measured according to the bitmap information in the message PACKET DOWNLINK ACK/NACK received by BSS, and incremented by one when the bitmap information indicates that the block received by MS has not been measured, as the measurement point A referred in Figure 4-91.

Figure 4-91 Downlink RLC data blocks transmission

MS PCU

A

DOWNLINK RLC DATA BLOCK(

PACKET DOWNLINK ACK/NACK(Bitmap)

%sinRe 100A

BA1CSgublockdatadownlinkRLCofrateontransmissi ×⎟⎠⎞

⎜⎝⎛ −=−

1CSgublocksdataRLCdownlinkofNumberA −− sinBSSbyreceived1CSgublocksdataRLCdownlinkofNumberB −− sin


Huawei Recommendation This measured value is used to analyze the transmission quality of the downlink radio channel. If the value of the item is out of the reference value of 0-10%, it means that the link for transmission in the cell is relatively bad.




Retransmission Rate of Downlink RLC Data Blocks Using CS-2(%) Please refer to the instruction of the item Retransmission Rate of Downlink RLC Data Blocks Using CS-1(%), while the difference is that only downlink RLC data blocks using CS-2 code scheme are involved for measurement.



Number of CS Upgrades on Downlink TBF Please refer to the instruction of the item Number of CS Upgrades on Uplink TBF, while the only difference is that the measurement object is downlink TBF.

Number of CS Demotions on Downlink TBF Please refer to the instruction of the item Number of CS Demotions on Uplink TBF, while the only difference is that the measurement object is downlink TBF.

Number of Downlink RLC Control Blocks Description

This statistics item is used to measure the number of RLC control blocks on the downlink TBF during the measuring period.

Measurement Point When PACKET DOWNLINK ACK/NACK message for acknowledgement to downlink RLC data blocks transmission is received by network, as the measurement point A referred in Figure 4-92, the number of downlink RLC control blocks is incremented by one.

Figure 4-92 Downlink TBF with RLC control block with PAKCET DOWNLINK ACK/NACK message

MS Network

A

PACKET DOWNLINK ACK/NACK



Besides, when PACKET CONTROL ACKNOWLEDGEMENT message of downlink TBF is received by network, the number of downlink RLC control blocks is incremented by one.



Number of Downlink RLC Dummy Blocks Description

This statistics item is used to measure the number of RLC dummy blocks on the downlink TBF during the measuring period.

Measurement Point When there is no downlink data transmission requirement, network will send DOWNLINK RLC DUMMY BLOCK for a while to keep the downlink TBF active. When downlink RLC dummy block is transmitted, as the measurement point A referred in Figure 4-93, the number of downlink RLC dummy blocks is incremented by one. Besides, when PACKET CONTROL ACKNOWLEDGEMENT message of downlink TBF is received by network, the number of downlink RLC control blocks is incremented by one.

Figure 4-93 Downlink RLC dummy block transmission

MS Network

A

DOWNLINK RLC DUMMY BLOCK



Mean Throughput of Downlink RLC (kbit/s) Description

This statistics item is used to measure the mean data transmission rate of downlink RLC layer during the measuring period.

Measurement Point First of all, the item Downlink RLC Payload is calculated by the item Number of Downlink RLC Data Blocks Using CS-1, the item Number of Downlink RLC Data Blocks Using CS-2, the item Number of Downlink RLC Data Blocks Using CS-3, and




the item Number of Downlink RLC Data Blocks Using CS-4 during the measuring period as follow.

( ) ( )1024

854D40C34B23A ××+×+×+×=kbitsPayloadRLCDownlink

1-CS UsingBlocks Data RLCDownlink ofNumber −A2-CS UsingBlocks Data RLCDownlink ofNumber −B3-CS UsingBlocks Data RLCDownlink ofNumber −C4-CS UsingBlocks Data RLCDownlink ofNumber −D

The length of RLC blocks using code scheme with CS-1, CS-2, CS-3 and CS-4 is respectively 23, 34, 40 and 54 octets. Furthermore, this item is calculated by the item Downlink RLC Payload and the time length of the measuring period during the measuring period as follow.

( )60PeriodtMeasuremen

kbits/sRLCDownlinkofThroughputMean×

= PayloadRLCDownlink

Effect of the Item

Together with the item Uplink RLC Payload referred in “Mean rate of uplink RLC”, the item Uplink EGPRS RLC Payload referred in “Mean rate of uplink EGPRS RLC”, the item Downlink EGPRS RLC Payload referred in “Mean rate of downlink EGPRS RLC”, this item can reflect the item Packet Data Rate on Air Interface (UL/DL), which is used to measure the packet data rate between uplink and downlink RLC payload on air interface during the measuring period.

PayloadRLCEGPRSDownlinkPayloadRLCDownlinkPayloadRLCEGPRSUplinkPayloadRLCUplink

InterfaceAironRateDataacketP++

=

Huawei Recommendation Please refer to “Measuring the TBF Traffic” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer”.

4.8.12 Cell Radio Channel Performance Measurement Table 4-19 lists the measurement items of the cell radio channel performance measurement.

Table 4-19 Cell radio channel performance measurement


1 Number of RLC Data Blocks in Use on PDCH

2 Number of RLC Data Blocks Received on Uplink PDTCH/PACCH

3 Number of RLC Data Blocks Received on Downlink PDTCH/PACCH

4 Cell Mean PDCH Bearer Rate (%)

5 Uplink PDTCH/PACCH Utilization Rate (%)

6 Downlink PDTCH/PACCH Utilization Rate (%)

7 Mean PPCH Queue Lengths




8 Mean PAGCH Queue Lengths

9 Number of Cell Selection by MS

10 Number of Cell Reselection at Short Interval by MS

11 Number of Cell Ping-pong Reselection by MS


Number of RLC Data Blocks in Use on PDCH Description

This statistics item is used to measure the number of RLC data blocks transmitted on the uplink/downlink TBFs during the measuring period.

Measurement Point During the measuring period, when the PCU sends or receives the valid RLC data block, the measured value will be incremented by one. Here “send” referrers to PCU sends data block to MS, as the measurement point A referred in Figure 4-94; while “receive” referrers to PCU receive data block from MS and send it to network, as the measurement point B referred in Figure 4-94.

Figure 4-94 RLC data blocks in use on PDCH

MS PCU

A

DOWNLINK RLC DATA BLOCK

UPLINK RLC DATA BLOCK

B

Effect of the Item This statistic item can affect the item Cell Mean PDCH Bearer Rate (%), which is used to measure the cell mean PDCH bearer rate during the measuring period. You can get more detailed instruction from Cell Mean PDCH Bearer Rate (%).

Huawei Recommendation If the statistical result in the defined traffic model keeps being higher than the model value, it is recommended to make capacity expansion.

Number of RLC Data Blocks Received on Uplink PDTCH/PACCH Description

This statistics item is used to measure the number of RLC data blocks received on the uplink PDTCH/PACCH during the measuring period.




Measurement Point During the measuring period, when the RLC data is received on the uplink PDTCH/PACCH from MS, as the measurement point B referred in Figure 4-94, the measured value will be incremented by one.

Effect of the Item This statistic item can affect the item Uplink PDTCH/PACCH Utilization Rate (%), which is used to measure the channel utilization ratio of the uplink PDTCH/PAGCCH during the measuring period. You can get more detailed instruction from Uplink PDTCH/PACCH Utilization Rate (%).


None

Number of RLC Data Blocks Received on Downlink PDTCH/PACCH Description

This statistics item is used to measure the number of RLC data blocks received on the downlink PDTCH/PACCH during the measuring period.

Measurement Point During the measuring period, when the RLC data is sent on the downlink PDTCH/PACCH to MS, as the measurement point A referred in Figure 4-94, the measured value will be incremented by one.

Effect of the Item This statistic item can affect the item Downlink PDTCH/PACCH Utilization Rate (%), which is used to measure the channel utilization ratio of the downlink PDTCH/PAGCCH during the measuring period. You can get more detailed instruction from Downlink PDTCH/PACCH Utilization Rate (%).


None

Cell Mean PDCH Bearer Rate (%) Description

This statistics item is used to measure the cell mean PDCH bearer rate during the measuring period.

Measurement Point When a valid block is scheduled on PDCH, the number of blocks scheduled on PDCH will be incremented by one. This item is calculated by the item Number of RLC Data Blocks in Use on PDCH and the number of blocks scheduled on PDCH as follow.

%100PDCH on scheduledblocks RLC of NumberPDCH on use inblocks data RLC of Numberrate bearer PDCH mean Cell ×=

Effect of the Item

Please refer to “Measuring the PDCH Channel Utilization Rate” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer”.

Huawei Recommendation If the statistical result in the defined traffic model keeps being far higher than the model value, it is recommended to make capacity expansion.



Uplink PDTCH/PACCH Utilization Rate (%) Description

This statistics item is used to measure the channel utilization ratio of the uplink PDTCH/PAGCCH during the measuring period.

Measurement Point When the block is scheduled on the uplink PDCH, the number of blocks scheduled on the number of blocks scheduled on uplink PDCH will be incremented by one. This item Uplink PDTCH/PACCH Utilization Rate is calculated by the item Number of RLC Data Blocks Received on Uplink PDTCH/PACCH and the number of blocks scheduled on uplink PDCH as follow.

%100PDCHon Uplink Scheduled Blocks RLC ofNumber

HPDTCH/PACCon Uplink Received Blocks Data RLC ofNumber Rateon UtilizatiHPDTCH/PACCUplink

×

=

Effect of the Item


Please refer to “Measuring the PDCH Channel Utilization Rate” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer”.

Downlink PDTCH/PACCH Utilization Rate (%) Description

This statistics item is used to measure the channel utilization ratio of the downlink PDTCH/PAGCCH during the measuring period.

Measurement Point When the block is scheduled on the downlink PDCH, the number of blocks scheduled on the number of blocks scheduled on downlink PDCH will be incremented by one. This item Downlink PDTCH/PACCH Utilization Rate is calculated by the item Number of RLC Data Blocks Received on Downlink PDTCH/PACCH and the number of blocks scheduled on downlink PDCH as follow.

%100PDCHDownlink on ScheduledBlocksRLCofNumber

HPDTCH/PACCDownlink on Received Blocks Data RLC ofNumber Rateon UtilizatiHPDTCH/PACCDownlink

×

=

Effect of the Item


Please refer to “Measuring the PDCH Channel Utilization Rate” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer.

Mean PPCH Queue Lengths Description

This measurement is used to measure the mean PPCH queue lengths during the measuring period.

Measurement Point




Obtain the total number of PPCH queue lengths by measuring the length of PPCH queue, which refer to the number of node in the queue, N times during the measuring period. The mean PPCH queue length is equal to the total number of PPCH queue length divided by N.

12×=

PeriodMeasuringLengthsQueuePPCHofNumberTotal

LengthsQueuePPCHMean



Reference range: 0-9

Mean PAGCH Queue Lengths Description

This measurement is used to measure the mean PAGCH queue lengths during the measuring period.

Measurement Point Obtain the total number of PAGCH queue lengths by measuring the length of PAGCH queue, which refer to the number of node in the queue, N times during the measuring period. The mean PAGCH queue length is equal to the total number of PAGCH queue length divided by N.

12×=

PeriodMeasuringLengthsQueuePAGCHofNumberTotal

LengthsQueuePAGCHMean



None

Number of Cell Selection by MS Description

This statistics item is used to measure the total number of times that the duration between the MS switches into and out of the cell is less than the specified time.

Measurement Point During measuring period, when a new context of one MS has been established by BSS, the measured value will be incremented by one. Here MS context is used to record information of MS during the traffic.


Huawei Recommendation This item reflects the statistic results of MS behaviors in the certain serving cell. Please refer to 7.4.3 “Measuring the MS Behaviors”.



Number of Cell Reselection at Short Interval by MS Description

This statistics item is used to measure the total number of times that the duration between the MS switches into and out of the cell is less than the specified time.

Measurement Point Network will record the timestamp when the context of the MS has been established, and will also record the timestamp when MS left the cell and get the difference between them as duration time staying in the cell. During the measuring period and in a cell, if the time is less than the specified time whose default value is 2 seconds, the measured value will be incremented by one.


Huawei Recommendation This item reflects the statistic results of MS behaviors in the certain serving cell. Please refer to 7.4.3 “Measuring the MS Behaviors”.

Number of Cell Ping-pong Reselection by MS Description

This statistics item is used to measure the number of time for MS who switches from cell A to cell B and switch back to cell A in the configured time.

Measurement Point During the measuring the period, when a MS switched from cell A to cell B and switches back to cell A in the configured time whose default value is 2 seconds, the measured value will be incremented by one.


Huawei Recommendation This item reflects the statistic results of MS behaviors in the certain serving cell. Please refer to 7.4.3 “Measuring the MS Behaviors”..

4.8.13 Resource Maintenance Performance Measurement Table 4-20 lists the measurement items of the resource maintenance performance measurement.

Table 4-20 Resource maintenance performance measurement


1 Number of BSC-originated Cell Resets

2 Number of BSC-originated Cell Blocking

3 Number of BSC-originated Cell Unblocking

4 Number of GB-originated Cell Blocking

5 Number of GB-originated Cell

6 Number of BSC-originated Channel Blocking





7 Number of BSC-originated Channel Unblocking

Number of BSC-originated Cell Resets Description

The measured value indicates the number of cell resets originated by the BSC during the measuring period. The possible reasons for the BSC-originated cell reset include base station reset, cell reset originated by the OM at BSC, fault recovery of LAPD link at Pb interface, etc.

Measurement Point When the cell reset message from the BSC is received, as the measurement point A referred in Figure 4-95, the measured value will be incremented by one.

Figure 4-95 BSC-originated cell reset

BSC PCU

A

CELL RESET

Effect of the Item This item sums up such operation as blocking channel from BSC side, which will cause the cell can not provide packet service until it startup again.


Number of BSC-originated Cell Blocking Description

The measured value indicates the number of the cell blocking originated by the BSC during the measuring period.

Measurement Point When the cell blocking operation message from the BSC is received, as the measurement point A referred in Figure 4-96, the measured value will be incremented by one.



Figure 4-96 BSC-originated cell blocking

BSC PCU

A

RF RES BLOCK(CELL BLOCK)

Effect of the Item This item sums up such operation as blocking channel from BSC side, which will cause the cell can not provide packet service until such operation as unblocking cell from BSC side executed again.


Number of BSC-originated Cell Unblocking Description

The measured value indicates the number of the cell unblocking originated by the BSC during the measuring period.

Measurement Point When the cell unblocking operation message from the BSC is received, as the measurement point A referred in Figure 4-97, the measured value will be incremented by one.

Figure 4-97 BSC-originated cell unblocking

BSC PCU

A

RF RES UNBLOCK(CELL UNBLOCK)



Number of GB-originated Cell Blocking Description




The measured value indicates the number of cell blocking originated by the Gb during the measuring period. The possible reasons for Gb-originated cell blocking include link fault at Gb interface, SGSN-originated BVC PTP blocking, PCU OM-originated BVC PTP blocking, etc.

Measurement Point When the BVC BLOCK message from the Gb is received, as the measurement point A referred in Figure 4-98, the measured value will be incremented by one. If the message has been received for more than twice, only the first time will lead to the result incremented.

Figure 4-98 Gb-originated cell blocking

PCU SGSN

A

BVC BLOCK

Effect of the Item This item sums up such operation as blocking channel from SGSN side, which will cause the cell can not provide packet service until such operation as unblocking cell from SGSN side executed again.


Number of GB-originated Cell Unblocking Description

The measured value indicates the number of cell unblocking originated by the Gb during the measuring period. The possible reasons for Gb-originated cell unblocking include fault recovery of link at the Gb interface, SGSN-originated BVC PTP unblocking, PCU OM-originated BVC PTP unblocking, etc.

Measurement Point When the BVC UNBLOCK message from the Gb is received, as the measurement point A referred in Figure 4-99, the measured value will be incremented by one.



Figure 4-99 Gb-originated cell unblocking

PCU SGSN

A

BVC UNBLOCK



Number of BSC-originated Channel Blocking Description

The measured value indicates the number of BSC-originated channel blocking in the cell during the measuring period.

Measurement Point When the BSC-originated channel blocking message is received, as the measurement point A referred in Figure 4-100, the measured value will be incremented by one.

Figure 4-100 BSC-originated channel blocking

BSC PCU

A

RF RES BLOCK(CHANNEL BLOCK)

Effect of the Item This item sums up such operation as blocking channel from BSC side, which will cause the channel can not be used in the cell until such operation as unblocking channel from BSC side executed again, and consequently affect the PS capacity of the target cell.


Number of BSC-originated Channel Unblocking Description

The measured value indicates the number of BSC-originated channel unblocking in a cell during the measuring period.




Measurement Point When the BSC-originated channel unblocking message is received, as the measurement point A referred in Figure 4-101, the measured value will be incremented by one.

Figure 4-101 BSC-originated channel unblocking

BSC PCU

A

RF RES UNBLOCK(CHANNEL UNBLOCK)



4.8.14 PDCH Resource Performance Measurement Table 4-21 lists the measurement items of the PDCH resource performance measurement.

Table 4-21 PDCH resource performance measurement


1 Mean Number of Available PDCHs

2 Mean Number of Occupied PDCHs

3 Number of Attempts at Converting TCH to PDTCH

4 Number of Successful Conversions from TCH to PDTCH

5 Number of Dynamic PDCHs Reclaimed by BSC

6 Number of Pre-empted PDCHs Carrying Packet Traffic

7 Mean occupied Duration of All Available PDCHs( s )

8 Number of PDCHs Occupied by Uplink

9 Number of PDCHs Occupied by Downlink TBF

10 Total Number of PDCHs

Mean Number of Available PDCHs Description



The measured value indicates the mean number of the available PDCHs in the cell during the measuring period. The available PDCHs here refer to the applied PDCH whose state is normal and can be used.

Measurement Point Obtain the total number of available PDCHs by measuring the available PDCHs in the cell for N times during the measuring period. The mean number of available PDCHs is equal to the total number of available PDCHs divided by N.

Effect of the Item Together with the item Mean Number of Occupied PDCHs, this item can reflect the PDCH Occupation Rate, which is used to measure the channel utilization ratio of the downlink PDTCH/PACCH during the measuring period.

%100PDCHsAvailableofNumberMeanPDCHsOccupiedofNumberMean ×=RateOccupationPDCH


Please refer to 61757428.5.807017750 “Measuring the PDCH Occupation” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer”.

Mean Number of Occupied PDCHs Description

The measured value indicates the mean number of PDCHs in use in the cell during the measuring period. The occupied PDCHs here refer to the PDCH with TBF.

Measurement Point Obtain the total number of occupied PDCHs by measuring the occupied PDCHs in the cell for N times during the measuring period. The mean number of occupied PDCHs is equal to the total number of available PDCHs divided by N.

Effect of the Item Together with the item Mean Number of Available PDCHs, this item can reflect the PDCH Occupation Rate, which is used to measure the channel utilization ratio of the downlink PDTCH/PACCH during the measuring period.

%100PDCHsAvailableofNumberMeanPDCHsOccupiedofNumberMean ×=RateOccupationPDCH


The PDCH Occupied rate can reflect the traffic volume of the cell in some manner. Please refer to 7.5.2 “Measuring the PDCH Occupation” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer”.

Number of Attempts at Converting TCH to PDTCH Description

This item indicates the number of attempts at converting the TCH to the PDTCH in the cell during the measuring period.

Measurement Point During the measuring period, when PDCH REQUEST message for dynamic channel request is sent to the BSC, as the measurement point A referred in Figure 4-102, the measured value will be incremented by one.




Figure 4-102 Attempts at converting TCH to PDTCH

BSC PCU

A

PDCH REQUEST

PDCH REQUEST ACK/NACK

Effect of the Item Together with the item Number of Successful Conversions from TCH to PDTCH, this measured value can be used to calculate the Dynamic PDCH Request Successful Rate.

%100ABRate SuccessfulRequest PDCH Dynamic ×=

PDTCH toTCH Convertingat Attempts ofNumber -APDTCH toTCH from sConversion Successful ofNumber -B

Huawei Recommendation Through measuring the PDCH occupation, you can know the preemption done by the CS service to the PS service. Please refer to“Measuring the PDCH Occupation” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer”.

Number of Successful Conversions from TCH to PDTCH Description

The measured value indicates the number of successful conversions from TCH to PDTCH in the cell during the measuring period.

Measurement Point During the measuring period, after PDCH REQUEST message for dynamic channel request is sent to the BSC, PCU will wait PDCH REQUEST ACK message which indicates successful application for PDCH from BSC, as the measurement point B referred in Figure 4-103, the measured value will be incremented by one.



Figure 4-103 Successful conversions from TCH to PDTCH

BSC PCU

A

PDCH REQUEST

PDCH REQUEST ACK

Effect of the Item Together with the item Number of Attempts at Converting TCH to PDTCH, this measured value can be used to calculate the Dynamic PDCH Request Successful Rate.

%100ABRate SuccessRequest PDCH Dynamic ×=

PDTCH toTCH Convertingat Attempts ofNumber -APDTCH toTCH from sConversion Successful ofNumber -B

Huawei Recommendation If the requests fail for times or Dynamic PDCH request successful rate lower than 80%, the possible reason may lie in heavy BSC traffic or BSC channel state abnormity and you may consider increase fixed PDCH to expand the packet service capacity. Please refer to“Measuring the PDCH Occupation” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer”.

Number of Dynamic PDCHs Reclaimed by BSC Description

The measured value indicates the number of attempts at converting from PDCH to TCH in the cell during the measuring period. This measured value can reveal the number of attempts initiated by the circuit service to preempt the packet service and to convert PDCH to TCH during the measuring period. This conversion can succeed under any condition.

Measurement Point During the measuring period, when receiving TCH REQUEST message for reclaiming dynamic channel request from the BSC, PCU will release specified PDCH passively under any condition, and as the measurement point A referred in Figure 4-104, the measured value will be incremented by one.




Figure 4-104 Dynamic PDCHs reclaimed by BSC

BSC PCU

A

TCH REQUEST

TCH REQUEST ACK

Effect of the Item Together with the item Number of Pre-empted PDCHs Carrying Packet Traffic, this item can reflect Pre-Empted Dynamic PDCH Carrying Packet TrafficReclaimed Success Rate, which is used to measure the pre-empted dynamic PDCH carrying packet traffic reclaimed success rate during the measuring period.

%100ABRateSuccess Reclaimed TrafficPacket Carrying PDCH Dynamic Empted-Pre ×=

BSCby Reclaimed PDCHs Dynamic of Num-ATrafficPacket Carrying PDCHs Empted-Pre of Num-B

Huawei Recommendation Through measuring the PDCH occupation, you can know the preemption done by the CS service to the PS service. Please refer to “Measuring the PDCH Occupation” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer”.

Number of Pre-empted PDCHs Carrying Packet Traffic Description

The measured value indicates the number of attempts at converting from PDCH with packet service on it to TCH in the cell during the measuring period. This measured value can reveal the number of attempts initiated by the circuit service to preempt the packet service and to convert PDCH (with packet service on it) to TCH during the measuring period. This conversion can succeed under any condition.

Measurement Point During the measuring period, when receiving TCH REQUEST message for reclaiming dynamic channel request from the BSC, PCU will release specified PDCH passively under any condition, as the measurement point A referred in Figure 4-104. If there is uplink or downlink TBF on the PDCH to be reclaimed, the measured value will be incremented by one.

Effect of the Item Together with the item Number of Dynamic PDCHs Reclaimed by BSC, this item can reflect Pre-Empted Dynamic PDCH Carrying Packet Traffic Reclaimed Success Rate, which is used to measure the pre-empted dynamic PDCH carrying packet traffic reclaimed success rate during the measuring period.



%100ABRate Success Reclaimed TrafficPacket Carrying PDCH Dynamic Empted-Pre ×=

BSCby Reclaimed PDCHs Dynamic of Num-ATrafficPacket Carrying PDCHs Empted-Pre of Num-B

Huawei Recommendation Please refer to “Measuring the PDCH Occupation” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer”.

Mean occupied Duration of All Available PDCHs( s ) Description

The measured value indicates the duration when all the available PDCHs are occupied. Here, occupied PDCHs refer to the PDCHs with TBFs on it, and the available PDCH refers to the applied PDCH with normal status and can be used.

Measurement Point The start time is the time that the last free PDCH is occupied, and the end time is the time that any occupied PDCH is released its last TBF. During the measuring period, when all the available PDCHs have TBFs on them, the time will be accumulated, while there is free PDCH or there is no PDCH in the cell, the time will not be accumulated. The total occupied duration time will return to user.


Huawei Recommendation The PDCH Occupied rate can reflect the traffic volume of the cell in some manner. Please refer to “Measuring the PDCH Occupation” in 7.4.2 “Measuring the Traffic of RLC/MAC Layer”.

Number of PDCHs Occupied by Uplink TBF Description

The measured value indicates the mean number of PDCHs in use by uplink TBF in the cell during the measuring period. The occupied PDCHs by uplink TBF here refer to the PDCH with uplink TBF.

Measurement Point Obtain the total number of PDCHs occupied by uplink TBF by measuring the number of occupied PDCHs with uplink TBF for N times during the measuring period. The mean number of uplink occupied PDCHs is equal to the total number of PDCHs occupied by uplink TBF divided by N.

12 Period MeasuringPDCHs Occupied TBF Uplink ofNumber TotalN

×=PDCHsOccupiedTBFUplinkofumber

Effect of the Item

Together with the item Uplink RLC Payload and the item Uplink EGPRS RLC Payload, the item Uplink RLC Data Throughput per PDCH can be calculated by Number of uplink TBF occupied PDCHs as follows, which is used to measure the mean uplink GPRS&EGPRS RLC data throughput per PDCH during the measuring period.




60 Period MeasuringPDCHsOccupiedTBFUplinkofumberNPayloadRLCEGPRSUplinkPayloadRLCUplink

PDCHperThroughputDataRLCUplink

××+

=


Number of PDCHs Occupied by Downlink TBF Description

The measured value indicates the mean number of PDCHs in use by downlink TBF in the cell during the measuring period. The occupied PDCHs by downlink TBF here refer to the PDCH with downlink TBF.

Measurement Point Obtain the total Number of PDCHs Occupied by uplink TBF by measuring the number of occupied PDCHs with downlink TBF for N times during the measuring period. The mean number of downlink occupied PDCHs is equal to the total Number of PDCHs Occupied by uplink TBF divided by N.

12 Period MeasuringPDCHs Occupied TBFDownlink ofNumber TotalN

×=PDCHsOccupiedTBFDownlinkofumber

Effect of the Item

Together with the item Downlink RLC Payload and the item Downlink EGPRS RLC Payload, the item Downlink RLC Data Throughput per PDCH can be calculated by Number of downlink TBF occupied PDCHs as follows, which is used to measure the mean downlink GPRS&EGPRS RLC data throughput per PDCH during the measuring period.

60 Period MeasuringPDCHsOccupiedTBFDownlinkofumberNPayloadRLCEGPRSDownlinkPayloadRLCownlinkD

PDCHperThroughputDataRLCDownlink

××+

=


Total Number of PDCHs occupied by TBF Description

The measured value indicates the accumulative total number of PDCHs in use by TBF in the cell during the measuring period, including uplink and downlink TBF.

Measurement Point Obtain the accumulative Total Number of PDCHs occupied by TBF by measuring the number of occupied PDCHs by both uplink and downlink TBF for N times during the measuring period. The total number of all TBF occupied PDCHs is equal to the accumulative Total Number of TBF Occupied PDCHs divided by N.

12 Period MeasuringPDCHs Occupied TBF ofNumber Total veAccumulatiPDCHs Occupied TBF ofNumber Total

×=

Effect of the Item




None

4.8.15 PDCH Extremum Value Measurement Table 4-22 lists the measurement items of the PDCH extremum value measurement.

Table 4-22 PDCH extreum value measurement


1 PDCH Extremum Value Measurement

2 Minimum Number of Available PDCHs

3 Maximum Number of Occupied PDCHs

4 Minimum Number of Occupied PDCHs

Maximum Number of Available PDCHs Description

The measured value indicates the maximum number of available PDCHs in the cell during the measuring period. The available PDCHs here refer to the applied PDCH whose state is normal and can be used.

Measurement Point During the measuring period, the number of available PDCHs which can be assigned for traffic will be fetched for times. The maximum will be kept until to the end of the measuring period and returned to user. That means the returned value is the maximum among all samples of this period.

Effect of the Item The higher the maximum number is, the more channels can be used for packet service.


Minimum Number of Available PDCHs Description

The measured value indicates the minimum available PDCHs number of a cell during a measurement period. The available PDCHs here refer to the applied PDCH whose state is normal and can be used.

Measurement Point During the measuring period, the number of available PDCHs which can be assigned for traffic will be fetched for times. The Minimum will be kept until to the end of the measuring period and returned to user. That means the returned value is the Minimum among all samples of this period.






Maximum Number of Occupied PDCHs Description

The measured value indicates the maximum PDCHs number occupied by subscribers in one cell during a measurement period. The occupied PDCHs here refer to the PDCH with TBF.

Measurement Point During the measuring period, the number of occupied PDCHs which has already been assigned for traffic will be fetched for times. The maximum will be kept until to the end of the measuring period and returned to user. That means the returned value is the maximum among all samples of this period.



Minimum Number of Occupied PDCHs Description

The measured value indicates the minimum PDCHs number occupied by subscribers in one cell during a measurement period. The occupied PDCHs here refer to the PDCH with TBF.

Measurement Point During the measuring period, the number of occupied PDCHs which has already been assigned for traffic will be fetched for times. The minimum will be kept until to the end of the measuring period and returned to user. That means the returned value is the minimum among all samples of this period.



4.8.16 Uplink EGPRS TBF Establishment/Release Measurement Table 4-23 lists the measurement items of the uplink EGPRS TBF establishment/release measurement.

Table 4-23 Uplink EGPRS TBF establishment/release measurement


1 Number of Uplink EGPRS TBF Establishment Attempts

2 Number of Successful Uplink EGPRS TBF Establishment

3 Number of Uplink EGPRS TBF Establishment Failures due to No Channel

4 Number of Uplink EGPRS TBF Establishment Failures due to Ms No Response

5 Number of Uplink EGPRS TBF Normal Release




6 Number of Uplink EGPRS TBF Abnormal Release due to N3101 Overflow (Ms No Response)

7 Number of Uplink EGPRS TBF Abnormal Release due to N3103 Overflow (Ms No Response)

8 Number of Uplink EGPRS TBF Abnormal Release due to SUSPEND

9 Number of Uplink EGPRS TBF Abnormal Release due to FLUSH

10 Number of Uplink EGPRS TBF Abnormal Release due to No Channel

11 Mean Number of Concurrent Uplink EGPRS TBFs

12 Mean Duration Time of Uplink EGPRS TBF(s)


Concerning the effect of these items, Uplink EGPRS TBF Congestion Rate and Uplink EGPRS TBF Drop Rate can be calculated by them, and the measurement object is only EGPRS uplink TBF, while comparably in Uplink GPRS TBF congestion rate and Uplink GPRS TBF drop rate, the measurement object are both GPRS and EGPRS uplink TBF

%100×+=C

BARateCongestionTBFEGPRSUplink

ChannelNotodueFailuresentEstablishmTBFEGPRSUplinkofNumberA −ChannelNotodueleaseAbnormalTBFEGPRSUplinkofNumberB Re−

AttemptsentEstablishmTBFEGPRSUplinkofNumberC −

%100×⎟⎠⎞⎜

⎝⎛ +=

ACBRateDropTBFEGPRSUplink

entEstablishmTBFEGPRSUplinkSuccessfulofNumberA −OverflowNtodueleaseAbnormalTBFEGPRSUplinkofNumberB 3101Re−OverflowNtodueleaseAbnormalTBFEGPRSUplinkofNumberC 3103Re−

Please refer to the instruction of those items in 4.8.6 ”Uplink TBF Establishment/Release Measurement”.

Number of Uplink EGPRS TBF Establishment Attempts Description

Please refer to the instruction of the item Number of Uplink TBF Establishment Attempts, while the only difference is that the measurement object is only EGPRS uplink TBF.

Number of Successful Uplink EGPRS TBF Establishment Description

Please refer to the instruction of the item Number of Successful Uplink Assignments, while the only difference is that the measurement object is only EGPRS uplink TBF.




Number of Uplink EGPRS TBF Establishment Failures due to No Channel Description

Please refer to the instruction of the item Number of Uplink TBF Establishment Failures due to No Channel, while the only difference is that the measurement object is only EGPRS uplink TBF.

Number of Uplink EGPRS TBF Establishment Failures due to Ms No Response Description

Please refer to the instruction of the item Number of Uplink TBF Establishment Failures due to Ms No Response, while the only difference is that the measurement object is only EGPRS uplink TBF.

Number of Uplink EGPRS TBF Normal Release Description

Please refer to the instruction of the item Number of Uplink TBF Normal Release, while the only difference is that the measurement object is only EGPRS uplink TBF.

Number of Uplink EGPRS TBF Abnormal Release due to N3101 Overflow (Ms No Response)

Description

Please refer to the instruction of the item Number of Uplink TBF Abnormal Release due to N3101 Overflow (Ms No Response), while the only difference is that the measurement object is only EGPRS uplink TBF.

Number of Uplink EGPRS TBF Abnormal Release due to N3103 Overflow (Ms No Response)

Description

Please refer to the instruction of the item Number of Uplink TBF Abnormal Release due to N3103 Overflow (Ms No Response), while the only difference is that the measurement object is only EGPRS uplink TBF.

Number of Uplink EGPRS TBF Abnormal Release due to SUSPEND Description

Please refer to the instruction of the item Number of Uplink TBF Abnormal Release due to SUSPEND, while the only difference is that the measurement object is only EGPRS uplink TBF.

Number of Uplink EGPRS TBF Abnormal Release due to FLUSH Description

Please refer to the instruction of the item Number of Uplink TBF Abnormal Release due to FLUSH, while the only difference is that the measurement object is only EGPRS uplink TBF.



Number of Uplink EGPRS TBF Abnormal Release due to No Channel Description

Please refer to the instruction of the item Number of Uplink TBF Abnormal Release due to No Channel, while the only difference is that the measurement object is only EGPRS uplink TBF.

Mean Number of Concurrent Uplink EGPRS TBFs Description

Please refer to the instruction of the item Mean Number of Concurrent Uplink TBFs, while the only difference is that the measurement object is only EGPRS uplink TBF.

Mean Duration Time of Uplink EGPRS TBF(s) Description

Please refer to the instruction of the item Mean Duration Time of Uplink TBF(s), while the only difference is that the measurement object is only EGPRS uplink TBF.

4.8.17 Downlink EGPRS TBF Establishment/Release Measurement

Table 4-24 lists the measurement items of the downlink EGPRS TBF establishment/release measurement.

Table 4-24 Downlink EGPRS TBF establishment/release measurement


1 Number of Downlink EGPRS TBF Establishment Attempts

2 Number of Successful Downlink EGPRS TBF Establishment

3 Number of Downlink EGPRS TBF Establishment Failures due to No Channel

4 Number of Downlink EGPRS TBF Establishment Failures due to Ms No Response

5 Number of Downlink EGPRS TBF Normal Release

6 Number of Downlink EGPRS TBF Abnormal Release due to N3105 Overflow

7 Number of Downlink EGPRS TBF Abnormal Release due to SUSPEND

8 Number of Downlink EGPRS TBF Abnormal Release due to FLUSH

9 Number of Downlink EGPRS TBF Abnormal Release due to No Channel

10 Mean Number of Concurrent Downlink EGPRS TBFs

11 Mean Duration Time of Downlink EGPRS TBF(s)





Concerning the effect of these items, Downlink EGPRS TBF Congestion Rate and Downlink EGPRS TBF Drop Rate can be calculated by them, and the measurement object is only EGPRS downlink TBF, while comparably in Downlink GPRS TBF Congestion Rate and Downlink GPRS TBF Drop Rate, the measurement object are both GPRS and EGPRS downlink TBF

%100×+=C

BARateCongestionTBFEGPRSDownlink

ChannelNotodueFailuresentEstablishmTBFEGPRSDownlinkofNumberA −ChannelNotodueleaseAbnormalTBFEGPRSDownlinkofNumberB Re−

AttemptsentEstablishmTBFEGPRSDownlinkofNumberC −

( ) %100×= ABRateDropTBFEGPRSDownlink

entEstablishmTBFEGPRSDownlinkSuccessfulofNumberA −

Overflow3105NtodueleaseAbnormalTBFEGPRSDownlinkofNumberB Re−

Please refer to the instruction of those items in 4.8.7 “Downlink TBF Establishment/Release Measurement”.

Number of Downlink EGPRS TBF Establishment Attempts Description

Please refer to the instruction of the item Number of Downlink TBF Establishment Attempts, while the only difference is that the measurement object is only EGPRS downlink TBF.

Number of Successful Downlink EGPRS TBF Establishment Description

Please refer to the instruction of the item Number of Successful Downlink TBF Establishment, while the only difference is that the measurement object is only EGPRS downlink TBF.

Number of Downlink EGPRS TBF Establishment Failures due to No Channel Description

Please refer to the instruction of the item Number of Downlink TBF Establishment Failures due to No Channel, while the only difference is that the measurement object is only EGPRS downlink TBF.

Number of Downlink EGPRS TBF Establishment Failures due to Ms No Response

Description

Please refer to the instruction of the item Number of Downlink TBF Establishment Failures due to MS No Response, while the only difference is that the measurement object is only EGPRS downlink TBF.



Number of Downlink EGPRS TBF Normal Release Description

Please refer to the instruction of the item Number of Downlink TBF Normal Release, while the only difference is that the measurement object is only EGPRS downlink TBF.

Number of Downlink EGPRS TBF Abnormal Release due to N3105 Overflow Description

Please refer to the instruction of the item Number of Downlink TBF Abnormal Release due to N3105 Overflow, while the only difference is that the measurement object is only EGPRS downlink TBF.

Number of Downlink EGPRS TBF Abnormal Release due to SUSPEND Description

Please refer to the instruction of the item Number of Downlink TBF Abnormal Release due to SUSPEND, while the only difference is that the measurement object is only EGPRS downlink TBF.

Number of Downlink EGPRS TBF Abnormal Release due to FLUSH Description

Please refer to the instruction of the item Number of Downlink TBF Abnormal Release due to FLUSH, while the only difference is that the measurement object is only EGPRS downlink TBF.

Number of Downlink EGPRS TBF Abnormal Release due to No Channel Description

Please refer to the instruction of the item Number of Downlink TBF Abnormal Release due to No Channel, while the only difference is that the measurement object is only EGPRS downlink TBF.

Mean Number of Concurrent Downlink EGPRS TBFs Description

Please refer to the instruction of the item Mean Number of Concurrent Downlink TBFs, while the only difference is that the measurement object is only EGPRS downlink TBF.

Mean Duration Time of Downlink EGPRS TBF(s) Description

Please refer to the instruction of the item Mean Duration Time of Downlink TBF(s), while the only difference is that the measurement object is only EGPRS downlink TBF.




4.8.18 Uplink EGPRS RLC Data Transmission Measurement Table 4-25 lists the measurement items of the uplink EGPRS RLC data transmission measurement.

Table 4-25 Uplink EGPRS RLC data transmission measurement


1 Total Number of Uplink EGPRS RLC Data Blocks

2 Number of MCS Upgrades on Uplink EGPRS TBF

3 Number of MCS Demotions on Uplink EGPRS TBF

4 Number of Uplink EGPRS RLC Control Blocks

First of all, the item Uplink EGPRS RLC Payload is calculated based on the formula below:

( )( )

1024874I68H56G74F56E44D73C82B 22A

kbitsPayloadRLCEGPRSUplink××+×+×+×+×+×+×+×+×

=

1- MCSUsing BlocksData RLC EGPRS Uplink of NumberA −2- MCSUsing BlocksData RLC EGPRS Uplink of NumberB −3- MCSUsing BlocksData RLC EGPRS Uplink of NumberC −4- MCSUsing BlocksData RLC EGPRS Uplink of NumberD −5- MCSUsing BlocksData RLC EGPRS Uplink of NumberE −6- MCSUsing BlocksData RLC EGPRS Uplink of NumberF −7- MCSUsing BlocksData RLC EGPRS Uplink of NumberG −8- MCSUsing BlocksData RLC EGPRS Uplink of NumberH −

9- MCSUsing BlocksData RLC EGPRS Uplink of NumberI −

Because an uplink EGPRS RLC data block with MCS-7/MCS-8/MCS-9 MCS type is separated to 2 parts and measured as 2 blocks in our statistic measurement for more accuracy, the length of uplink EGPRS RLC blocks using code scheme with MCS-1, MCS-2, MCS-3, MCS-4, MCS-5, MCS-6, MCS-7, MCS-8 and MCS-9 is respectively 22, 28, 37, 44, 56, 74, 56, 68 and 74 octets.

Secondly, this item is calculated by the item Uplink EGPRS RLC Payload and the time length of the measuring period during the measuring period as follow.

( )60Period tMeasuremen

PayloadRLCEGPRSUplink kbits/sRLCEGPRS Uplink of Throughput Mean

×=

Furthermore, together with the item Uplink RLC Payload referred in “Mean rate of uplink RLC”, the item Downlink RLC Payload referred in “Mean rate of downlink RLC”, the item Downlink EGPRS RLC Payload referred in “Mean rate of downlink EGPRS RLC”, this item can reflect the item Packet Data Rate on Air Interface (UL/DL), which is used to measure the packet data rate between uplink and downlink RLC payload on air interface during the measuring period.



PayloadRLCEGPRSDownlinkPayloadRLCDownlinkPayloadRLCEGPRSUplinkPayloadRLCUplink InterfaceAironRateDataacketP

++

=


Total Number of Uplink EGPRS RLC Data Blocks Description

This statistics item is used to measure the number of uplink EGPRS RLC data blocks received during the measuring period.

Measurement Point This item is calculated based on the formula below:

IHGFEDCBA blocks dataRLC EGPRS uplink of numberTotal ++++++++= Where,

1- MCSusing blocksdata RLC EGPRS uplink of NumberA −2- MCSusing blocksdata RLC EGPRS uplink of NumberB −3- MCSusing blocksdata RLC EGPRS uplink of NumberC −4- MCSusing blocksdata RLC EGPRS uplink of NumberD −5- MCSusing blocksdata RLC EGPRS uplink of NumberE −6- MCSusing blocksdata RLC EGPRS uplink of NumberF −7- MCSusing blocksdata RLC EGPRS uplink of NumberG −8- MCSusing blocksdata RLC EGPRS uplink of NumberH −

9- MCSusing blocksdata RLC EGPRS uplink of NumberI − Effect of the Item

The item of Total Number of Uplink EGPRS RLC Data Blocks can reflect the item Retransmission Rate of Uplink EGPRS RLC Data Block, which is used to measure the ratio of retransmitted uplink EGPRS RLC data blocks using MCS-1~MCS-9 during the measuring period.

100% )Blocks Data RLC Uplink ofNumber Total

IHGFEDCA - (1

(%)Block DataRLCEGPRSUplinkofRatesion Retransmis

×++++++++= B

1MCSgUBlockDataRLCEGPRSUplinkofRateontransmissiA −− sinRe2MCSgUBlockDataRLCEGPRSUplinkofRateontransmissiB −− sinRe3MCSgUBlockDataRLCEGPRSUplinkofRateontransmissiC −− sinRe4MCSgUBlockDataRLCEGPRSUplinkofRateontransmissiD −− sinRe5MCSgUBlockDataRLCEGPRSUplinkofRateontransmissiE −− sinRe6MCSgUBlockDataRLCEGPRSUplinkofRateontransmissiF −− sinRe7MCSgUBlockDataRLCEGPRSUplinkofRateontransmissiG −− sinRe8MCSgUBlockDataRLCEGPRSUplinkofRateontransmissiH −− sinRe

9MCSgUBlockDataRLCEGPRSUplinkofRateontransmissiI −− sinRe

Huawei Recommendation If the value of Retransmission rate of uplink EGPRS RLC data block is higher than 2%, the quality of the transmission link of cell may be poor. Therefore, please check TBF link quality including Abis link quality, G-Abis link quality and especially radio air interface quality.




Number of MCS Upgrades on Uplink EGPRS TBF Description

Please refer to the instruction of the item Number of CS Upgrades on Uplink TBF, while the only difference is that uplink EGPRS RLC data blocks using MCS code scheme are involved for measurement.

Number of MCS Demotions on Uplink EGPRS TBF Description

Please refer to the instruction of the item Number of CS Demotions on Uplink TBF, while the only difference is that uplink EGPRS RLC data blocks using MCS code scheme are involved for measurement.

Number of Uplink EGPRS RLC Control Blocks Description

Please refer to the instruction of the item Number of Uplink RLC Control Blocks, while the only difference is that uplink EGPRS RLC control blocks are involved for measurement.

4.8.19 Downlink EGPRS RLC Data Transmission Measurement Table 4-26 lists the measurement items of the downlink EGPRS RLC data transmission measurement.

Table 4-26 Downlink EGPRS RLC data transmission measurement


1 Total Number Downlink EGPRS RLC Data Blocks

2 Number of MCS Upgrades on Downlink EGPRS TBF

3 Number of MCS Demotions on Downlink EGPRS TBF

4 Number of Downlink EGPRS RLC Control Blocks

5 Number of Downlink EGPRS RLC Dummy Blocks

First of all, the item Downlink EGPRS RLC Payload is calculated based on the formula below:

( )( )

1024874I68H56G74F56E44D73C82B 22A

kbitsPayloadRLCEGPRSDownlink××+×+×+×+×+×+×+×+×

=

1-MCS UsingBlocksData RLC EGPRSDownlink ofNumber −A2-MCS UsingBlocksData RLC EGPRSDownlink ofNumber −B3-MCS UsingBlocksData RLC EGPRSDownlink ofNumber −C4-MCS UsingBlocksData RLC EGPRSDownlink ofNumber −D5-MCS UsingBlocksData RLC EGPRSDownlink ofNumber −E



6-MCS UsingBlocksData RLC EGPRSDownlink ofNumber −F7-MCS UsingBlocksData RLC EGPRSDownlink ofNumber −G8-MCS UsingBlocksData RLC EGPRSDownlink ofNumber −H9-MCS UsingBlocksData RLC EGPRSDownlink ofNumber −I

Because an downlink EGPRS RLC data block with MCS-7/MCS-8/MCS-9 MCS type is separated to 2 parts and measured as 2 blocks in our statistic measurement for more accuracy, the length of downlink EGPRS RLC blocks using code scheme with MCS-1, MCS-2, MCS-3, MCS-4, MCS-5, MCS-6, MCS-7, MCS-8 and MCS-9 is respectively 22, 28, 37, 44, 56, 74, 56, 68 and 74 octets.

Secondly, this item is calculated by the item Downlink EGPRS RLC Payload and the time length of the measuring period during the measuring period as follow.

( )60Period tMeasuremen

PayloadRLCEGPRSDownlink kbits/sRLCEGPRS Downlink of Throughput Mean

×=

Furthermore, together with the item Uplink RLC Payload referred in “Mean rate of uplink RLC”, the item Downlink RLC Payload referred in “Mean rate of downlink RLC”, the item Uplink EGPRS RLC Payload referred in “Mean rate of uplink EGPRS RLC”, this item can reflect the item Packet Data Rate on Air Interface (UL/DL), which is used to measure the packet data rate between uplink and downlink RLC payload on air interface during the measuring period.


InterfaceAironRateDataacketP++

=


Total Number Downlink EGPRS RLC Data Blocks Description

This statistics item is used to measure the number of downlink EGPRS RLC data blocks sent during the measuring period.

Measurement Point This item is calculated based on the formula below:

IHGFEDCBAN ++++++++= Blocks DataRLC EGPRSDownlink ofumber Total Where,

1-MCS UsingBlocksData RLC EGPRSDownlink ofNumber −A2-MCS UsingBlocksData RLC EGPRSDownlink ofNumber −B3-MCS UsingBlocksData RLC EGPRSDownlink ofNumber −C4-MCS UsingBlocksData RLC EGPRSDownlink ofNumber −D5-MCS UsingBlocksData RLC EGPRSDownlink ofNumber −E6-MCS UsingBlocksData RLC EGPRSDownlink ofNumber −F7-MCS UsingDlocksData RLC EGPRSDownlink ofNumber −G8-MCS UsingDlocksData RLC EGPRSDownlink ofNumber −H

9-MCS UsingDlocksData RLC EGPRSDownlink ofNumber −I Effect of the Item




This item can reflect Retransmission Rate of Downlink EGPRS RLC Data Block(%), which is used to measure the ratio of retransmitted downlink EGPRS RLC data blocks using MCS-1~MCS-9 during the measuring period. Retransmission Rate of Downlink EGPRS RLC Data Block (%) is calculated based on the formula below:

100% )BlocksDataRLCDownlink ofNumber TotalIHGFEDCA - (1

(%)Block DataRLCEGPRSDownlinkofRatesion Retransmis

×++++++++= B

1MCSgUBlockDataRLCEGPRSDownlinkofRateontransmissiA −− sinRe2MCSgUBlockDataRLCEGPRSDownlinkofRateontransmissiB −− sinRe3MCSgUBlockDataRLCEGPRSDownlinkofRateontransmissiC −− sinRe4MCSgUBlockDataRLCEGPRSDownlinkofRateontransmissiD −− sinRe5MCSgUBlockDataRLCEGPRSDownlinkofRateontransmissiE −− sinRe6MCSgUBlockDataRLCEGPRSDownlinkofRateontransmissiF −− sinRe7MCSgUBlockDataRLCEGPRSDownlinkofRateontransmissiG −− sinRe8MCSgUBlockDataRLCEGPRSDownlinkofRateontransmissiH −− sinRe

9MCSgUBlockDataRLCEGPRSDownlinkofRateontransmissiI −− sinRe

Huawei Recommendation If the value of Retransmission rate of downlink EGPRS RLC data block is higher than 15%, the quality of the transmission link of cell may be poor. Therefore, please check TBF link quality including Abis link quality, G-Abis link quality and especially radio air interface quality.

Number of MCS Upgrades on Downlink EGPRS TBF Description

Please refer to the instruction of the item Number of CS Demotions on Downlink TBF, while the only difference is that downlink EGPRS RLC data blocks using MCS code scheme are involved for measurement.

Number of MCS Demotions on Downlink EGPRS TBF Description

Please refer to the instruction of the item Number of CS Demotions on Downlink TBF, while the only difference is that downlink EGPRS RLC data blocks using MCS code scheme are involved for measurement.

Number of Downlink EGPRS RLC Control Blocks Description

Please refer to the instruction of the item Number of Downlink RLC Control Blocks, while the only difference is that downlink EGPRS RLC control blocks are involved for measurement.

Number of Downlink EGPRS RLC Dummy Blocks Description



Please refer to the instruction of the item Number of Downlink RLC Dummy Blocks, while the only difference is that downlink EGPRS RLC dummy blocks are involved for measurement.

4.8.20 EGPRS GMSK_MEAN_BEP Different Value Measurement Table 4-27 lists the measurement items of the EGPRS GMSK_MEAN_BEP different value measurement.

Table 4-27 EGPRS GMSK-MEAN-BEP different value measurement

No. Measure item

1 Times of GMSK_MEAN_BEP=1



























No. Measure item









The following uses the item with GMSK_MEAN_BEP=1 as an example to illustrate the description, measuring point of it.

Times of GMSK_MEAN_BEP=1 Description

This item is used to measure the number of EGPRS PACKET DOWNLINK ACK/NACK messages carrying EGPRS BEP Link Quality Measurements with GMSK_MEAN_BEP of 1 received by BSS.

Measurement Point When the EGPRS PACKET DOWNLINK ACK/NACK message is received by BSS and the GMSK_MEAN_BEP field equals 1 if support GMSK_MEAN_BEP, as the measurement point A referred in Figure 4-105, the measured value will be incremented by one.

Figure 4-105 EGPRS PACKET DOWNLINK ACK/NACK with GMSK_MEAN_BEP

MS Network

A

EGPRS PACKET DOWNLINK ACK/NACK(GMSK_MEAN_BEP=1)





Please refer the corresponding part of EGPRS 8PSK_MEAN_BEP Different Value Measurement to get more information.

4.8.21 EGPRS 8PSK_MEAN_BEP Different Value Measurement Table 4-28 lists the measurement items of the EGPRS 8PSK_MEAN_BEP different value measurement.

Table 4-28 EGPRS 8PSK-MEAN-BEP different value measurement


1 Times of 8PSK_MEAN_BEP=1

2 Times of 8MSK_MEAN_BEP=2


4 Times of 8MSK _MEAN_BEP=4

































The following uses the item with 8PSK_MEAN_BEP=1 as an example to illustrate the description, measuring point of it.

Times of 8PSK_MEAN_BEP=1 Description

This item is used to measure the number of EGPRS PACKET DOWNLINK ACK/NACK messages carrying EGPRS BEP Link Quality Measurements with 8PSK_MEAN_BEP of 1 received by BSS.

Measurement Point When the EGPRS PACKET DOWNLINK ACK/NACK message is received by BSS and the 8PSK_MEAN_BEP field equals 1 if support 8PSK _MEAN_BEP, as the measurement point A referred in Figure 4-106, the measured value will be incremented by one.

Figure 4-106 EGPRS PACKET DOWNLINK ACK/NACK with 8PSK_MEAN_BEP

MS Network

A

EGPRS PACKET DOWNLINK ACK/NACK(8PSK_MEAN_BEP=1)

Effect of the Item The Table 4-29 below gives examples of Modulation and Coding Scheme (MCS) selection based on the reported link quality estimates 8PSK_MEAN_BEP and 8PSK_CV_BEP. The selection is designed to maximize the link throughput. Further optimization e.g. for the IR mode is possible. In the same manner the MCS-1 to MCS-4 can be chosen based on GMSK_MEAN_BEP and GMSK_CV_BEP.



Table 4-29 8PSK MCS selection based on BEP reports

8PSK_CV_BEP

1 2 3 4 5 6 7 8

1 MCS-5 MCS-5 MCS-5

MCS-5 MCS-5 MCS-5 MCS-5 MCS-5

2 MCS-5 MCS-5 MCS-5


3 MCS-5 MCS-5 MCS-5


4 MCS-5 MCS-5 MCS-5


5 MCS-5 MCS-5 MCS-5


6 MCS-5 MCS-5 MCS-5


7 MCS-5 MCS-5 MCS-5


8 MCS-5 MCS-5 MCS-5


9 MCS-5 MCS-5 MCS-5


10 MCS-5 MCS-5 MCS-5
















8 P S K M E A N B E P






8PSK_CV_BEP

1 2 3 4 5 6 7 8





























It indicates that the Measurement Report from MS can reflect the quality of radio environment which will affect the transmission performance directly.




4.8.22 Uplink GMSK EGPRS RLC Data Retransmission Rate Measurement

Table 4-30 lists the measurement items of the Uplink GMSK EGPRS RLC Data Retransmission Rate Measurement.

Table 4-30 Uplink GMSK EGPRS RLC Data Retransmission Rate Measurement


1 Number of Uplink EGPRS RLC Data Blocks Using MCS-1




5 Retransmission Rate of Uplink EGPRS RLC Data Block Using MCS-1 (%)




Number of Uplink EGPRS RLC Data Blocks Using MCS-1 Description

This statistics item is used to measure the number of uplink EGPRS RLC data blocks using MCS-1 sent during the measuring period.

Measurement Point

For uplink EGPRS RLC data blocks using MCS-1 will be received as transmission in MCS-1 radio block mode or retransmission in MCS-4 radio block mode, total number of uplink EGPRS RLC data blocks using MCS-1 sent by MS is measured as follow:

Step 1 In the case that retransmitting MCS-4 data block in MCS-1 radio block mode does not occur:

Please refer to the instruction of the item Number of Uplink RLC Data Blocks Using CS-1, while the only difference is that uplink EGPRS RLC data blocks using MCS-1 code scheme are involved for measurement.

Step 2 In the case of retransmitting MCS-4 data block in MCS-1 radio block mode:

When only part of the MCS-4 data block as well as the rear half MCS-1 radio block is received, the number of uplink EGPRS RLC data block with MCS-1 sent by MS will be incremented by one.

When the whole MCS-4 data block (including the whole MCS-1 radio block) is received, the number of uplink EGPRS RLC data block with MCS-1 sent by MS will be incremented by one.




When the corresponding rear half MCS-1 radio block is received after the whole MCS-4 data block is received, the number of uplink EGPRS RLC data block with MCS-1 sent by MS will be incremented by one.



----End



Measurement Point





Please refer to the corresponding part of instruction of the item Number of Uplink EGPRS RLC Data Blocks Using MCS-1, while the only difference is that uplink EGPRS RLC data blocks using MCS-2 code scheme are involved for measurement.

Effect of the Item

None


None

----End



Measurement Point







Please refer to the corresponding part of instruction of the item, while the only difference is that uplink EGPRS RLC data blocks using MCS-3 code scheme are involved for measurement.

Effect of the Item

None


None

----End



Retransmission Rate of Uplink EGPRS RLC Data Block Using MCS-1 (%) Description:

This statistics item is used to measure the retransmission rate of Uplink EGPRS RLC data block using MCS-1 received during the measuring period.

Measuring point: This item is calculated by the item Number of Uplink EGPRS RLC Data Blocks Using MCS-1 and the item “the number of uplink EGPRS RLC data block using MCS-1 received by BSS" which will be incremented by one when an uplink EGPRS RLC data block with MCS-1 is received by BSS.

%1001sinRe ×⎟⎠⎞

⎜⎝⎛ −=−

ABAMCSgUBlockDataRLCEGPRSUplinkofRateontransmissi

1sin −− MCSgUBlocksDataRLCEGPRSUplinkofNumberABSSbyceivedMCSgUBlocksDataRLCEGPRSUplinkofNumberB Re1sin −−


Huawei Recommendation This measured value is used to analyze the transmission quality of the uplink radio channel. If the value of the item is out of the reference value of 0~10%, it means that the link for transmission in the cell is relatively bad.




Retransmission Rate of Uplink EGPRS RLC Data Block Using MCS-2 (%) Description

Please refer to the instruction of the item Retransmission Rate of Uplink EGPRS RLC Data Block Using MCS-1 (%), while the only difference is that uplink EGPRS RLC data blocks using MCS-2 code scheme are involved for measurement.





4.8.23 Uplink 8PSK EGPRS RLC Data Retransmission Rate Measurement

Table 4-31 lists the measurement items of the Uplink 8PSK EGPRS RLC Data Retransmission Rate Measurement.

Table 4-31 Uplink 8PSK EGPRS RLC Data Retransmission Rate Measurement
































This statistics item is used to measure the retransmission rate of Uplink EGPRS RLC data block using MCS-7 received during the measuring period.

Measuring point This item is calculated by the item Number of Uplink EGPRS RLC Data Blocks Using MCS-7 and the item “Number of uplink EGPRS RLC data block using MCS-7 received by BSS” which will be incremented by two when an uplink EGPRS RLC data block with MCS-7 (two RLC data blocks with MCS-7) is received by BSS.

%1007sinRe ×⎟⎠⎞

⎜⎝⎛ −=−

ABAMCSgUBlockDataRLCEGPRSUplinkofRateontransmissi

7sin −− MCSgUBlocksDataRLCEGPRSUplinkofNumberABSSbyceivedMCSgUBlocksDataRLCEGPRSUplinkofNumberB Re7sin −−


Huawei Recommendation This measured value is used to analyze the transmission quality of the uplink radio channel. If the value of the item is out of the reference value of 0-10%, it means that the link for transmission in the cell is relatively bad.





4.8.24 Downlink GMSK EGPRS RLC Data Retransmission Rate Measurement

Table 4-32 lists the measurement items of the Downlink GMSK EGPRS RLC Data Retransmission Rate Measurement.

Table 4-32 Downlink GMSK EGPRS RLC Data Retransmission Rate Measurement


1 Number of Downlink EGPRS RLC Data Blocks Using MCS-1







5 Retransmission Rate of Downlink EGPRS RLC Data Blocks Using MCS-1(%)




Number of Downlink EGPRS RLC Data Blocks Using MCS-1 Description

This statistics item is used to measure the number of EGPRS RLC data blocks using MCS-1 sent during the measuring period.

Measurement Point When the DOWNLINK EGPRS RLC data block with MCS-1 CS type is sent to MS by BSS, as the measurement point A referred in Figure 4-107, the measured value will be incremented by one.

Figure 4-107 Downlink RLC data blocks with CS-1 CS type transmission

MS Network

A

DOWNLINK EGPRS RLC DATA BLOCK(MCS-1)




Please refer to the instruction of the item Number of Downlink EGPRS RLC Data Blocks Using MCS-1, while the only difference is that downlink EGPRS RLC data blocks using MCS-2 code scheme are involved for measurement.








Retransmission Rate of Downlink EGPRS RLC Data Blocks Using MCS-1(%) Description

This statistics item is used to measure the ratio of retransmitted EGPRS RLC data blocks using MCS-1 during the measuring period.

Measuring point This item is calculated by the item Number of Downlink EGPRS RLC Data Blocks Using MCS-1 and the item “Number of downlink EGPRS RLC data block using MCS-1 received by MS”, which will be measured according to the bitmap information in the message EGPRS PACKET DOWNLINK ACK/NACK received by BSS, and incremented by one when the bitmap information indicates that the block received by MS has not been measured, as the measurement point A referred in Figure 4-108.

Figure 4-108 Downlink EGPRS RLC data blocks transmission

MS PCU

A

DOWNLINK EGPRS RLC DATA BLOCK

EGPRS PACKET DOWNLINK ACK/NACK (Bitmap)

%1001sinRe ×⎟⎠⎞

⎜⎝⎛ −=−

ABAMCSgUBlockDataRLCEGPRSDownlinkofRateontransmissi

1sin −− MCSgUBlocksDataRLCEGPRSDownlinkofNumberABSSbyceivedMCSgUBlocksDataRLCEGPRSDownlinkofNumberB Re1sin −−




Huawei Recommendation This measured value is used to analyze the transmission quality of the downlink radio channel. If the value of the item is out of the reference value of 0~10%, it means that the link for transmission in the cell is relatively bad.







4.8.25 Downlink 8PSK EGPRS RLC Data Retransmission Rate Measurement

Table 4-33 lists the measurement items of the Downlink 8PSK EGPRS RLC Data Retransmission Rate Measurement.

Table 4-33 Downlink 8PSK EGPRS RLC Data Retransmission Rate Measurement






































M900/M1800 Operation Manual - Performance Measurement 5 Procedures of Traffic Statistics Analysis


5 Procedures of Traffic Statistics Analysis

About This Chapter


Title Description

5.1 Overview This section decribesthe focus and main purpose on the PCU traffic statistics analysis.

5.2 Preparation for the Traffic statistics Analysis

This section decribes the Preparation for the Traffic statistics Analysis.

5.3 Overall Idea for Traffic Statistics Analysis

This section decribes the Overall Idea for Traffic Statistics Analysis.

5 Procedures of Traffic Statistics Analysis M900/M1800



5.1 Overview This article focuses on the PCU traffic statistics analysis. The readers are assumed to be familiar with the use of traffic statistics. The main purpose of analyzing the traffic statistics data is to handle the faults, optimize the network, and establish the packet traffic model.

5.2 Preparation for the Traffic statistics Analysis 5.2.1 Traffic Statistics Register Items

The PCU provides complete traffic measurement items, including seven traffic statistics types and 22 measurement types, among which, there are 16 cell-level measurement types.

Table 5-1 Traffic register items

Statistics type Measurement type Recommended register time (minutes)

Recommendation level



60 Recommended



60 Mandatory


NS Transmission Performance Measurement

60 Optional



60 Optional



60 Mandatory



60 Mandatory






60 Optional


Not necessary


60 Optional


60 Mandatory


60 Optional


60 Mandatory


60 Mandatory


60 Optional


60 Optional


60 Recommended


60 Recommended


60 Recommended



60 Recommended







60 Mandatory

PDCH Extremum Value Measurement

60 Recommended

Uplink EGPRS TBF Establishment/Release Measurement

60 Mandatory


60 Mandatory

Uplink EGPRS RLC Data Transmission Measurement

60 Recommended

Downlink EGPRS RLC Data Transmission Measurement

60 Recommended

EGPRS GMSK_MEAN_BEP Different Value Measurement

60 Not necessary

EGPRS 8PSK_MEAN_BEP Different Value Measurement

60 Not necessary

Uplink GMSK EGPRS RLC Data Retransmission Rate Measurement

60 Not necessary

Uplink 8PSK EGPRS RLC Data Retransmission Rate Measurement

60 Not necessary

Downlink GMSK EGPRS RLC Data Retransmission Rate Measurement

60 Not necessary

Downlink 8PSK EGPRS RLC Data Retransmission Rate Measurement

60 Not necessary



Descriptions about the above table are as follows:

Seven items are mandatory, which covers all the main aspects of the PCU, including BSC overall measurement and the measurement on the Pb, G-Abis, and Um interface.

Six items are recommended, which are the detailed cell-level measurement items. These items reflect the running state of the cell. They are used to optimize the network and locate the fault. In the new deployed network, registering these items can further monitor the running of the network and thus ensure the stability of the network.

Other items are of less importance. For example, although the Gb interface is an important interface for PCU, the interface is simple and stable. Thus the abnormal traffic is not big. Unless necessary, this interface is not the focus of the traffic analysis.

BSC overall performance measurement reflects the running state of the packet services of the whole BSC. The BSC measurement period and the cell measurement period shall be the same. This makes the traffic analysis easier. The measurement period is recommended to be 60 minutes. For example, the measurement period of the busy time traffic in the traffic model is suggested to be 60 minutes. Currently the traffic is not too heavy, it is also ok to set the period as 120 minutes.

The register period of the cell-level traffic measurement items shall be short. It is recommended to be 60 minutes. Because these measurement items are tightly related to each other, all the periods are suggested to be set as 60 minutes.

NS, BSSGP and LLC transmission performance measurement in GB interface are less important, so they are optional items.

5.2.2 Data Preparation Before analyzing the traffic statistics, you shall know the GPRS network parameters and the GPRS network settings, such as:

The PCU data configuration The PDCH configuration of cell The packet traffic distribution

In addition, you shall also know the GSM network structure, especially the setting of the network parameters related to the GPRS, and the GSM CS traffic state.

When locating the faults, we need to analyze the traffic data of one or some individual statistical period(s). But more often, the traffic data macroscopically reflects the MS behaviors and the network running state.

For example, when we analyze the packet traffic model or optimize the network, the analysis of the traffic data of individual statistical period is not enough. You can master the network performance only by means of analyzing the traffic data of a long period. Therefore, we recommend analyzing the traffic data every week, especially the traffic data of the BSCs or cells, in which the GPRS traffic is relatively heavy.

The traffic data of PCU is unavailable for offline browsing. You can save the traffic data as .txt file in the traffic statistics console and then open the file with Microsoft Excel or Lotus 1-2-3 to analyze it.

5.3 Overall Idea for Traffic Statistics Analysis The principle of traffic statistics analysis is: from BSC to cell, from lower layer link to upper layer service, from fault location to traffic model analysis.




Regular traffic data analysis is very important. When the network runs abnormally or is faulty, you can locate the fault by analyzing the alarms and the traffic data of the period near the time when the fault occurs.

For the original traffic data, check the following items according to the checklist:

Whether the data is correct Whether the data relevance is correct Whether there is any abnormal item

If the data relevance or the data is incorrect, the traffic statistics mechanism may be faulty. Submit this problem to the R&D department for solution.

If the traffic statistics item is abnormal, the network may run abnormally, then:

Step 1 Check the change trend of the traffic data of the last week or the all day.

Step 2 Analyze the traffic data of the BSC in the order from key items to less important items to make sure the abnormality range.

Step 3 If the abnormality occurs in the whole BSC, analyze the problem from the aspects of BSC hardware, transmission and network optimization.

Step 4 If the abnormality only occurs in some cells, analyze the cell traffic data to find the fault. If necessary, analyze the cell with the help of the drive test and signaling analyzer.

----End

All the GPRS performance measurement results include GPRS performance measurement results and EDGE performance measurement results. As a result, you can still make analysis for performance measurement results in EDGE cells based on GPRS related measurement results. Consequently, all the analysis instruction according to statistic measurement below is relevant to GPRS and there is no instruction dedicated for EDGE performance measurement results analysis.

In the early operation period of GPRS network, there is no mature traffic model for packet service. Therefore, after eliminating the abnormality during the regular traffic data analysis, it is important to accumulate and analyze the packet traffic model data.

The analysis shall focus on the relevance of the items, such as, congestion rate, call-drop rate and so on.

Also, the absolute value of the traffic statistical items shall also be focused. If the absolute value is too high or too low, analyze it according to the actual situation and experience.

In the actual operation, the analysis of PCU traffic data is always associated with the analysis of PCU alarm, drive test data and other related BSC data.

The figure below shows the traffic statistics analysis flow:



Figure 5-1 Traffic statistics analysis flow

Start

Regular analysis of traffic data

Whether the trafficdata is faulty? Locate the fault

Whether the trafficstatistical item is faulty?

BSC overall ananlysis

Traffic modelaccumulationand analysis

Whether the BSCitem is faulty?

Faulty occurs

Checklist

Analyze the BSC traffic data

Locate the abnormal cell

Analyze the cell traffic data

Analyzetransmisson link

Analyzecongestion rate

Analyze cell-drop rate

Solve theequipment fault

Solve thetransmission

fault

optimize thenetwork

End

Yes

No

No

Yes

Yes

No

M900/M1800 Operation Manual - Performance Measurement 6 BSC-level Traffic Statistics Analysis


6 BSC-level Traffic Statistics Analysis

About This Chapter


Title Description

6.1 Analyzing the Quality of LAPD of Pb Interface

This section decribes the LAPD of Pb Interface Quality analysis.

6.2 Analyzing the BSC Overall Performance

This section decribes the BSC overall performance analysis.

6.3 Analyzing the Data of PDCH

This section decribes the PDCH Data analysis.

6 BSC-level Traffic Statistics Analysis M900/M1800



6.1 Analyzing the Quality of LAPD of Pb Interface The Pb interface is the signaling interface between the PCU and the BSC. One PCU can connect to multiple BSCs. Thus, the PCU and the BSC needs the transmission equipment to connect to each other. Based on the LAPD traffic statistics data, you can analyze the transmission quality of the Pb interface and the basic information of the upper layer data. The traffic statistics data of the LAPD which needs to be analyzed are as follows:

Number of SABM Frames Sent Number of UA Frames Received

Number of Information Frames Sent Number of Information Frames Received Bytes of Information Frames Sent Bytes of Information Frames Received

Number of Information Frame Resend Times Number of Downlink Message Queue Overflows

Generally, the LAPD link quality is stable. Only under some special situation, you need to analyze the LAPD lower layer data to support the analysis of the upper layer data. The analysis of the LAPD data focuses on the following points:

Analyzing the LAPD link broken The value of the item “Number of SABM frames sent” shall be less than or equal to 1. If the value of it is bigger than 10 and close to the value of the item “Number of UA frames received”, it means that the LAPD is broken frequently. This fault is generally due to the unstable transmission. Check the transmission. If the response times of link establishment are 0 and the link establishment attempt times are bigger, it means that the LAPD is broken in this period.

Analyzing the LAPD traffic model The main LAPD data to be analyzed are the LAPD traffic on busy time and the ratio of LAPD occupied transmission to free transmission. The LAPD traffic on busy time refers to the maximum traffic data on the busy time. The analysis items mainly include the Number of I frames received and the Bytes of I frames sent. If the traffic is heavy, the capacity expansion is necessary. The ratio of LAPD occupied transmission to free transmission means the ratio between the LAPD transmission bandwidth and the LAPD theoretical bandwidth. The bigger the ratio is, the higher the LAPD utilization rate is. If the ratio is small even on the busy time, it means the LAPD traffic is small and the LAPD still has margin. For example, if the Bytes of I frames received is 15,292,463 bytes, the LAPD transmission rate is 15,292,463/3600s = 4248 Bytes/s = 34 Kbps, then the ratio of LAPD occupied transmission to free transmission is 34kbps / 64kbps = 53%. Generally, the ratio of LAPD occupied transmission to free transmission is less than 30%. If the ratio is higher, it means the LAPD has heavy load. At this time, the value of the “Number of downlink message queue overflows” is also big. The heavy load of LAPD may cause the transmission delay of LAPD and the loss of high layer message. Thus, the quality of the network is affected. If the LAPD load is heavy, the capacity expansion is necessary.

M900/M1800 Operation Manual - Performance Measurement 6 BSC-level Traffic Statistics Analysis


6.2 Analyzing the BSC Overall Performance The BSC overall performance analysis is to check the overall running state of the BSS. If any data is abnormal, it means network quality is bad, and then carries out the cell-level traffic analysis to improve the network quality. The main analysis items are congestion rate and call-drop rate.

6.2.1 Analyzing the Network Congestion Rate The original meaning of the network congestion rate refers to the rate that the MS’s failure to access to the network due to congestion.

In the GPRS network, the access flow of MS is different from that of the GSM voice system. Thus the conception of the congestion rate of the two systems is different.

The congestion rate mainly means the successful immediate assignments rate. It is affected by the following factors:

Data configuration Network capacity Channel quality Busy degree of the PS service and CS service

The relevant traffic statistics items are as follows:

Number of Uplink TBF Establishment Attempts Number of Successful Uplink TBF Establishment Number of Downlink TBF Establishment Attempts Number of Successful Downlink TBF Establishment

In the GPRS system, the congestion rate is much higher than in the GSM voice system. This is due to

The system does not optimize the network regarding the PS service. Because of the uniqueness of the GPRS flow (refer to the resending times of the message

are high) the assignment failure does not quite affect the service and the resource utilization. Thus a little bit higher congestion rate is acceptable.

The reference value of the congestion rate ≤10%.

If the congestion rate is too high,

Step 1 Check the cell traffic statistics data of the suspicious time to find the cell whose congestion rate is much high and thus affects the overall performance.

Step 2 Analyze the specific cell to find the details and take corresponding measures. see 7.2.2 “Analyzing the Congestion Rate”

----End

6.2.2 Analyzing the Network Call-drop Rate The relevant traffic statistics data of the network call-drop rate are as follows:

Number of Successful Uplink TBF Establishment

6 BSC-level Traffic Statistics Analysis M900/M1800



Number of Uplink TBF Normal Release Number of Successful Downlink TBF Establishment Number of Downlink TBF Normal Release

The reference value of the call-drop rate ≤8%

The current GPRS network has not realized the cell handover; the cell reselection is done by the MS itself. If the MS reselects the cell during the transmission process, the call is sure to be dropped. But thanks to the fact that the TBF transmission time is short (average 2 s– 3 s), although the call-drop rate of the GPRS system is higher than that of the voice system, the service is not much affected.

Similar to the congestion rate, if the call-drop rate is too high,

Step 1 Check the cell traffic statistics data of the suspicious time to find the cell whose call-drop rate is much high and thus affects the overall performance.

Step 2 Analyze the specific cell to find the details (generally the causes are the incorrect cell channel status or the network optimization problem) and take corresponding measures. See 7.3.2 “Analyzing Call-drop ”.

----End

6.3 Analyzing the Data of PDCH The purpose of this analysis is to find whether the system is overloaded. The relevant PDCH traffic statistics items are as follows:

Mean Number of Available PDCHs Mean Number of Occupied PDCHs

Reference value: Mean number of available PDCHs ≤ 100

Mean number of occupied PDCHs ≤ 80

The PDCH has two types: dynamic and static. One Pb board of PCU can support up to 120 PDCH (if upgraded to support EDGE, the maximum supported PDCH number decrease to 100). Currently, the GPRS traffic is not too heavy, most of the PCUs on the network take the configuration of cell number more than channel number to reduce the cost. Thus, the channels may be insufficient sometimes.

The traffic statistics data is the average value. Therefore, if the value of the item “Mean Number of Available PDCHs” is more than 100, the maximum value may reach 120. This may affect the services of some cells.

If the services of some cells are affected, check the value of the item “Mean Number of Available PDCHs”.

If the value is small (for instance, 40), it means the actual traffic is not heavy, the problem may be caused by the configuration of too many fixed channels. This configuration leads to the low utilization rate of the channel. Reduce the fixed channel number to solve the problem.

If the value is big, it means the traffic is heavy, recommend the operator to expand the network capacity.

M900/M1800 Operation Manual - Performance Measurement 7 Cell-level Traffic Statistics Analysis


7 Cell-level Traffic Statistics Analysis

About This Chapter


Title Description

7.1 Analyzing the Quality of the Transmission Link of Cell

This section decribes the Transmission Link of Cell Quality analysis.

7.2 Analyzing the Congestion This section decribes the congestion analysis.

7.3 Analyzing the Call-drop Rate This section decribes the call-drop rate analysis.

7.4 Analyzing Cell Traffic This section decribes the Cell Traffic analysis.

7 Cell-level Traffic Statistics Analysis M900/M1800



7.1 Analyzing the Quality of the Transmission Link of Cell

The transmission link of cell here refers to the whole transmission link from the MS to the CN of the GPRS, including the Um interface, the G-Abis interface, the Pb interface, and the Gb interface.

For the analysis of the Pb interface, see “6.1 Analyzing the Quality of LAPD of Pb Interface”.

7.1.1 Analyzing the Um Interface

N3101, N3103 and N3105 The three counters monitor the uplink and downlink TBF link quality. If the uplink TBF or the downlink TBF is abnormally released due to the abnormality of these counters, it means the link is abnormal. If the abnormality rate of N3101, N3103 or N3105 is higher, it means maybe the quality of the transmission link is not good.

The relevant traffic statistics data of the network call-drop rate are as follows:

Number of Uplink TBF Abnormal Release due to N3101 Overflow (Ms No Response) Number of Uplink TBF Abnormal Release due to N3103 Overflow (Ms No Response) Number of Downlink TBF Abnormal Release due to N3105 Overflow Number of Uplink EGPRS TBF Abnormal Release due to N3101 Overflow (Ms No

Response) Number of Uplink EGPRS TBF Abnormal Release due to N3103 Overflow (Ms No

Response) Number of Downlink EGPRS TBF Abnormal Release due to N3105 Overflow

The calculation formula of the abnormality rate of N3101, N3103, and N3105 are as follows:

%10entestablishm TBF uplink l successfuof Number

response) no (MS overflow N3101 to due release abnormal TBF uplink of Numberrateyabnormalit3101N ≤=

%10entestablishm TBF uplink l successfuof Numberresponse) no (MS overflow N3103 to due release abnormal TBF uplink of Numberrateyabnormalit3103N ≤=

%10entestablishm TBF downlink l successfuof Number

overflow N3105 to due release abnormal TBF downlink of Numberrateyabnormalit3105N ≤=

RLC Data Transmission Performance The retransmission rate of RLC uplink and downlink data block, and the number of CS upgrade and demolition also reflect the quality of the transmission link of cell. The relevant traffic statistics items are as follows:

Retransmission Rate of Uplink RLC Data Block Using CS-1 (%) Retransmission Rate of Uplink RLC Data Block Using CS-2 (%) Retransmission Rate of Uplink RLC Data Block Using CS-3 (%) Retransmission Rate of Uplink RLC Data Block Using CS-4 (%) Retransmission Rate of Downlink RLC Data Blocks Using CS-1(%) Retransmission Rate of Downlink RLC Data Blocks Using CS-2(%)



Retransmission Rate of Downlink RLC Data Blocks Using CS-3(%) Retransmission Rate of Downlink RLC Data Blocks Using CS-4(%) Number of CS Upgrades on Uplink TBF Number of CS Demotions on Uplink TBF Number of CS Upgrades on Downlink TBF Number of CS Demotions on Downlink TBF

If EDGE business exists, more relevant traffic statistics items as follows should be concerned about:

Retransmission Rate of Uplink EGPRS RLC Data Block Using MCS-1 (%) Retransmission Rate of Uplink EGPRS RLC Data Block Using MCS-2 (%) Retransmission Rate of Uplink EGPRS RLC Data Block Using MCS-3 (%) Retransmission Rate of Uplink EGPRS RLC Data Block Using MCS-4 (%) Retransmission Rate of Uplink EGPRS RLC Data Block Using MCS-5 (%) Retransmission Rate of Uplink EGPRS RLC Data Block Using MCS-6 (%) Retransmission Rate of Uplink EGPRS RLC Data Block Using MCS-7 (%) Retransmission Rate of Uplink EGPRS RLC Data Block Using MCS-8 (%) Retransmission Rate of Uplink EGPRS RLC Data Block Using MCS-9 (%) Retransmission Rate of Downlink EGPRS RLC Data Blocks Using MCS-1(%) Retransmission Rate of Downlink EGPRS RLC Data Blocks Using MCS-2(%) Retransmission Rate of Downlink EGPRS RLC Data Blocks Using MCS-3(%) Retransmission Rate of Downlink EGPRS RLC Data Blocks Using MCS-4(%) Retransmission Rate of Downlink EGPRS RLC Data Blocks Using MCS-5(%) Retransmission Rate of Downlink EGPRS RLC Data Blocks Using MCS-6(%) Retransmission Rate of Downlink EGPRS RLC Data Blocks Using MCS-7(%) Retransmission Rate of Downlink EGPRS RLC Data Blocks Using MCS-8(%) Retransmission Rate of Downlink EGPRS RLC Data Blocks Using MCS-9(%) Number of MCS Upgrades on Uplink EGPRS TBF Number of MCS Demotions on Uplink EGPRS TBF Number of MCS Upgrades on Downlink EGPRS TBF Number of MCS Demotions on Downlink EGPRS TBF

Besides, EDGE MS will report measurement report to network in every EGPRS PACKET DOWNLINK ACK/NACK message to indicate current network radio quality. Therefore, you can get more information about Um interface from relevant traffic statistics as follows:

EGPRS GMSK_MEAN_BEP Different Value Measurement EGPRS 8PSK_MEAN_BEP Different Value Measurement

Number of RADIO_STATUS PDUs Sent by BSSGP Sublayer The relevant traffic statistics data of the network call-drop rate are as follows:

Number of RADIO_STATUS PDUs Sent by BSSGP Sublayer




This item can also reflect the air interface transmission quality of the cell. When the MS is outside the coverage of the radio, or the communication can not proceed due to the bad radio channel quality, the PCU sends the “RADIO-STATUS PDU” to the SGSN.

When you find the transmission quality of the cell is abnormal, analyze the transmission quality of:

the BSC that the cell belongs to the site that the cell belongs to the air interface of the cell

If the transmission quality of the Pb interface and the G-Abis interface is good, but the BLER of the cell is still high, it means that the Um interface may be faulty. Check the equipment of the cell or adjust the network parameters to improve the transmission quality of the Um interface.

7.1.2 Analyzing the G-Abis Interface The G-Abis interface is the interface between the PCU and the BTS, whose traffic analysis is based on cell Analyzing the G-Abis interface is to analyze the transmission quality of the network link layer. The main traffic statistics items are as follows:

Number of Normal Burst frames Received Number of Out-of-Synchronization Frames Received Number of Check Error Frames Received Number of Valid TRAU Frames Sent Number of Empty TRAU Frames Sent

The sending side does not know the quality of the link after the link synchronization. Only the receiving side can analyze the receive data to judge the link quality.

Thus, the G-Abis traffic statistics analysis is to analyze the frame error rate of the received data.

The out-of-synchronization frames in the received frames refer to the data frames before the synchronization of the channel link. The synchronization process is always accompanying the dynamic channel conversion. Thus, the rate of out-of-synchronization frame is related to channel type, link quality and synchronization algorithm.

The check error frame is caused by the check error and calculation error of the transmission link data after the channel synchronization. This item directly reflects the link quality. The formula of the frame error ate is as follows: (the normal frame number shall be more than 0)

00050

numberframenormalreceivednumberframeeerrorcheckreceivedrateerrorframeAbisG .≤=−

Based on the data from the network, in normal condition, the frame error rate is less than 10e-5. This means each channel has one error frame every 4 minutes. The link quality is fairly good and the MS under this condition can transmit the data stably

The frame error rate is less than 10e-4 when the transmission link quality is bad. Each channel has 1 – 3 error frames every minute. Because of the burst of the transmission frame error, the affected MSs may have the following symptoms:

Rate is lowered Transmission delay is extended



Call-drop

When the frame error rate is bigger than 10e-4, the link is extremely unstable. This leads to

the out-of-synchronization rate rises MSs can only carry out the services of small traffic volume (such as, high layer signaling,

little of WAP)

In fact, the transmission equipment is always rent (such as microwave, satellite and so on), so mobile sponsor can’t control it. Actually the 5‰ frame error rate is acceptable. If the frame error rate of a cell is extremely high, the transmission may be faulty. Suggest the operator to check the transmission to improve the network.

7.2 Analyzing the Congestion 7.2.1 Definition

The congestion analysis is to analyze the uplink and downlink TBF establishment. The relevant traffic statistics items are as follows:

Number of Uplink TBF Establishment Attempts Number of Successful Uplink TBF Establishment Number of Downlink TBF Establishment Attempts Number of Successful Downlink TBF Establishment Number of Uplink EGPRS TBF Establishment Attempts Number of Successful Uplink EGPRS TBF Establishment Number of Downlink EGPRS TBF Establishment Attempts Number of Successful Downlink EGPRS TBF Establishment

7.2.2 Analyzing the Congestion Rate When the congestion rate is high, analyze it as follows:




Figure 7-1 High congestion rate

No Packet Resources When the MSs access to the network through the CCCH, the PCU sends the immediate

assignment rejected message to the MS if no packet resources When the MSs access to the network through the PACCH, the PCU sends the packet

access rejected message to the MS if no packet resources. When the MSs access to the network through the downlink of CCCH/PACCH, the PCU

does not send any message to the MS if no packet resources. The relevant traffic statistics items are incremented by 1.

Check the two items “Number of Uplink TBF Establishment Failures due to No Channel” and “Number of Downlink TBF Establishment Failures due to No Channel “within a statistics period. The high congestion rate may be due to:



Cause Solution

Heavy PS traffic If the cell has no fixed PDCH, configure the cell with a fixed PDCH. If the cell has fixed PDCH, increase the number of dynamic PDCH.

Channel being blocked manually Check the Log file to see whether the channel of the cell is blocked. If yes, unblock it. Check the items “Number of BSC-originated channel blocking” and “Number of BSC-originated channel unblocking” to see whether the BSC blocks the PS channel. If yes, unblock it.

MS number of the PS channel in the cell is saturated

Adjust the two fields “MaxUlHighLd” and “MaxDlHighLd” in the “Pdchpara” table to allow the cell to bear more PS traffic.

CCCH random access collision Adjust the CCCH access threshold and the PS access request interval on the CCCH.

Channel type and channel quantity of the cell. In the current network, one cell is configured with a fixed channel and two dynamic channels, or three dynamic channels. When the MS access to the network through the CCCH, if the concurrent cell has no fixed channel, or the fixed channel is occupied, the PCU applies for the dynamic channel to BSC. Before the application succeeds, the access request of the MS can not be met. This also affects the congestion rate.

Check the Mean number of available PDCHs, the channel configuration of the cell, the “Pdchpara” table of the cell and the actual traffic in the cell. Adjust the channel configuration of the cell and the parameters in the “Pdchpara” table.

When implement the wide coverage, one RPPU (Pb) boar of PCU may be configured with more than 120 (maximum activated PDCH number that a RPPU (Pb) board can support if only GPRS traffic is provided) or 100 (maximum activated PDCH number that a RPPU (Pb) board can support if EDGE traffic is provided) When the PS traffic of the board is busy (the occupied PDCH number exceeds 100), if the cell is not configured with fixed channel but just with dynamic channel, it will lead to congestion due to channel not enough.

Recommend the operator to reduce the coverage of the RPPU (Pb) board and to expand the system capacity.




Cause Solution

PDCH out of synchronization Check whether there are the following alarms in the statistics period: Whether the BTS has the PCM alarm Whether the PCU has the link fault alarm Whether there is the PDCH out of synchronization alarm (this alarm is the internal debugging alarm). If YES, check whether the links between the PCU and the BSC, between the BTS and the BSC are normal.

Low Successful Assignment Rate The traffic statistics items related to Low Successful Assignment Rate are as follows:

The main traffic statistics items are as follows:

Number of Uplink Immediate Assignments Number of Successful Uplink Immediate Assignments Number of Uplink Assignments on PACCH Number of Successful Uplink Assignment on PACCH Number of Downlink Immediate Assignments Number of Successful Downlink Immediate Assignments Number of Downlink Assignments on PACCH Number of Successful Downlink Assignments on PACCH

Low assignment rate must lead to the high congestion rate. The items “Number of Uplink TBF Establishment Failures due to Ms No Response” and “Number of Downlink TBF Establishment Failures due to MS No Response” is the main reason for the low assignment rate. The high congestion rate may be due to:

The quality of the transmission link of the cell is bad, and the block error rate is high. See “Analysis of the cell transmission link quality” for the specific analysis. Under the bad transmission quality, the successful TBF access rate can be improved by adjusting the GPRS network parameters. For example, adjust the value of T3168 (it is the parameter of GPRS Cell Option. It means the waiting time for the “Packet Uplink Assignment” message after the MS sends the “Packet Resource Request” message). When the transmission quality is bad, increase the value of T3168 to delay the TBF setup. This can improve the successful access rate. When the transmission quality is good, the value of T3168 can be properly decreased. Thus the MS can resend the access request more quickly. This can improves the network’s response time to the TBF setup request. Normally (2%≤BLER≤10%), the T3168 can be adjusted between 500 ms – 2000 ms. Because most MSs seldom initiates two-phase access request, adjusting the T3168 in the common cell does not affect the successful TBF establishment rate. But in the satellite



cell, the PCU forces the MS to carry two-phase access, adjusting the T3168 can improve the successful TBF establishment rate. When adjusting the value of T3192, you shall completely analyze the PS traffic load of the current cell and the uplink/downlink PS traffic model. You shall pay special attention when adjusting the T3192 value in the cells whose downlink is heavily loaded.

Too heavy PS traffic The heavy traffic leads to the queue congested in the network and thus the assignment message is delayed, which further leads to the failure of TBF establishment. You can adjust the value of “g_N3101Max” (N3101 is the monitoring of network on the USF) and the value of “g_N3105Max” (N3105 is the monitoring of network on the RRBP on the uplink/downlink TBF) to extend the delay time. If the heavy PS traffic lasts for long time, suggest the operator to expand the capacity.

7.3 Analyzing the Call-drop Rate 7.3.1 Items to Be Analyzed

Analyzing the call-drop rate is to analyze the uplink and downlink TBF release. The traffic statistics items related to the cell-level call-drop rate are as follows:

Number of Uplink TBF Normal Release Number of Uplink TBF Abnormal Release due to N3101 Overflow (Ms No Response) Number of Uplink TBF Abnormal Release due to N3103 Overflow (Ms No Response) Number of Uplink TBF Abnormal Release due to SUSPEND Number of Uplink TBF Abnormal Release due to FLUSH Number of Uplink TBF Abnormal Release due to No Channel Number of Downlink TBF Normal Release Number of Downlink TBF Abnormal Release due to N3105 Overflow Number of Downlink TBF Abnormal Release due to SUSPEND Number of Downlink TBF Abnormal Release due to FLUSH Number of Downlink TBF Abnormal Release due to No Channel

7.3.2 Analyzing Call-drop Rate The PS call-drop rate is related to the radio quality, traffic, and even the MS behaviors. Therefore, you shall take various factors into consideration when analyzing the call-drop rate.

Figure 7-2 below is the recommended flow to analyze the call-drop




Figure 7-2 PS call-drop rate

Step 1 Determine whether the high TBF call-drop rate occurs in the whole BSC or just in some sites or some cells. If it’s the BSC-level TBF high call-drop rate, see “BSC traffic statistics analysis method”. If it is just in some sites or some cells make sure whether it is due to the equipment fault and the transmission fault as follows:

Check the BTS and PCU hardware Check the air interface of cell, TRAU link, and Pb link.

The equipment fault and the transmission fault are always accompanied by alarms. You can clear the fault with reference to these alarms.

Step 2 Make sure whether it is due to no packet resource caused by the reset of equipment, manual blocking of channel. The two items ” Number of Uplink TBF Abnormal Release due to No Channel” and “Number of Downlink TBF Abnormal Release due to No Channel “ of a statistics period can reflect whether the TBF call-drop is caused by the CS service preempting the PS resources. If YES, the CS traffic in the cell shall be high, you can analyze it with reference to the “Number of dynamic PDCHs reclaimed by BSC” and the traffic statistics items related to PDCH conversion. To ensure the stability of the PS service in the cell where



the CS traffic is heavy, you can add the fixed channel to the cell. The increase of fixed channel may affect the coverage of GPRS service, thus you shall plan it in a whole.

Step 3 The behavior of the MS also affects the TBF call-drop. The two items “Number of Uplink TBF Abnormal Release due to SUSPEND” and “Number of Downlink TBF Abnormal Release due to SUSPEND” reflects the whether the TBF call-drop is caused by the CS service of MS preempting the PS resources of MS. If the MS updates the location area or the updating of the location area regularly or the MS initiates the CS service at the same time with the PS services, the value of the above two items increases

The abnormal release of TBF due to SUSPEND is not the main cause of the TBF call-drop.

When the MS carries out the cell reselection during the process of PS service, it will lead to the FLUSH LL and make the TBF released abnormally. In this situation, you shall focus on the items “Number of Uplink TBF Abnormal Release due to FLUSH” and “Number of Downlink TBF Abnormal Release due to FLUSH”, “Number of Cell Selection by MS”, “Number of Cell Reselection at Short Interval by MS”, and “Number of Cell Ping-pong Reselection by MS”.

----End

7.4 Analyzing Cell Traffic There is no typical traffic model for the PS service. The Huawei PCU system provides relevant performance measurement function to accumulate the PS traffic data to help the operator to establish the PS service model.

7.4.1 Measuring the Traffic of LLC Layer With reference to the measurement items in the “Uplink LLC Data Transmission Measurement” and “Downlink LLC Data Transmission Measurement”, you can obtain the

Mean Length of Uplink LLC_PDUs Mean Length of Downlink LLC_PDUs Uplink Throughput (kbit/s) Downlink Throughput (kbit/s)

The throughput here is the throughput of a statistics period. It reflects the traffic size on the LLC layer within the statistics period. See Appendix for the calculation formula of the throughput.

7.4.2 Measuring the Traffic of RLC/MAC Layer

Measuring the TBF Traffic The relevant measurement items are as follows:

Total Number of Uplink TBFs Total Number of Downlink TBFs Mean Throughput of Uplink RLC (kbit/s) Mean Throughput of Downlink RLC (kbit/s) Mean LLC_PDU Bytes per Uplink TBF




Mean LLC_PDU Bytes per Downlink TBF

The throughput here is the throughput of a statistics period. It reflects the TBF traffic size within the statistics period. See Appendix for the calculation formula of the throughput.

Measuring the PDCH Channel Utilization Rate The channel utilization rate considers the block utilization rate on the PDCH both when the PCU is busy and when it is idle.

Thus if the channel utilization rate is low, it may be due to that there is no PS traffic in the cell or the PS traffic is small. The uplink/downlink PDTCH/PACCH channel utilization rate can to some extent reflect the PS traffic size of the current cell. The relevant measurement items are as follows:

Cell Mean PDCH Bearer Rate (%) Uplink PDTCH/PACCH Utilization Rate (%) Downlink PDTCH/PACCH Utilization Rate (%)

Measuring the PDCH Occupation Through measuring the PDCH occupation, you can know the preemption done by the CS service to the PS service. PDCH of the cell is configured with one fixed channel and two dynamic channels, or PDCH is configured with three dynamic channels thus, the following two items can even better reflect the preemption done by the CS service to the PS service: “Number of Dynamic PDCHs Reclaimed by BSC” and “Number of Successful Conversions from TCH to PDTCH.

The utilization rate of PDCH can to some extent reflect the traffic volume of the cell. The relevant statistics times are as follows:

Mean Number of Available PDCHs Mean Number of Occupied PDCHs Mean occupied Duration of All Available PDCHs( s )

If the cell is configured with fixed channel, in normal condition (except that the cell just starts), the value of item “ Mean Number of Available PDCHs” shall be equal to the fixed channel number of the cell. Otherwise, it means that the abnormality occurs in the cell in the statistics period.

If the channels configured to the cell are all dynamic, then you can judge whether there is any dynamic channel applied within the statistics period through the two items ” Mean Number of Available PDCHs” and “Mean Number of Occupied PDCHs”. If the values of the two items are close to “0”, it means that there is no PS traffic in the cell within the statistics period. You can also refer to other TBF statistics items to prove this.

Based on the “Mean Number of Occupied PDCHs”, you can judge whether the PS traffic in the cell is busy or idle. Then you can adjust the channel configuration according to the judgment. The idle cell shall be configured with more dynamic channel and the busy cell shall be configured with more fixed channel.



7.4.3 Measuring the MS Behaviors

Access frequency on the CCCH The relevant statistics item is:

Mean Inter-arrival Time of Packet Access Requests on CCCH (s)

Number of MS accessing to the network. The relevant statistics items are:

Number of Cell Selection by MS Number of Cell Reselection at Short Interval by MS

Number of cell update during the data transmission The relevant statistics item is:

Number of FLUSH_LL PDUs Received by BSSGP Sublayer

Number of SUSPEND/RESUME The relevant statistics items are:

SUSPEND PDU sent by BSSGP sublayer Number of RESUME PDUs Sent by BSSGP Sublayer

M900/M1800 Operation Manual - Performance Measurement

8 Introduction to GPCU KPIs in Huawei BSS network



Huawei GPCU has supported saving the result of cell-related KPI automatically since G3PCUV300R005C05 version, and as a result, you can use KPI Convert Tool to convert KPI result files which are automatically saved in PCU system everyday, to CSV format files, and then use KPI Analyzer Tool, which is a excel file has dedicated format, to browse all cell-related KPI results.

GPCU KPIs in Huawei are listed in Table 8-1.

Table 8-1 GPCU KPIs in Huawei BSS network

Item Definition Expression

Resource utilization rate

Uplink PDTCH/PACCH Utilization Rate (%)

This statistics item is used to measure the channel utilization ratio of the uplink PDTCH/PACCH during the measuring period.

( ) %100%Rateon UtilizatiHPDTCH/PACCUplink ×=BA

A − Number of RLC Data Blocks Received on Uplink PDTCH/PACCH B–Number of RLC Blocks Scheduled on Uplink PDCH

Downlink PDTCH/PACCH Utilization Rate (%)

This statistics item is used to measure the channel utilization ratio of the downlink PDTCH/PACCH during the measuring period.

%100BARate nUtilizatio HPDTCH/PACCDownlink ×=

A − Number of RLC Data Blocks Received on Downlink PDTCH/PACCH B − Number of RLC Blocks Scheduled on Downlink PDCH

PDCH Occupation Rate (%)

This statistics item is used to measure the PDCH channel occupation rate during the measuring period.

%100BARateOccupationPDCH ×=

A − Mean Number of Occupied PDCHs B − Mean Number of Available PDCHs

8 Introduction to GPCU KPIs in Huawei BSS network M900/M1800




Pre-Empted Dynamic PDCH Carrying Packet Traffic Reclaimed Success Rate (%)

This statistics item is used to measure the pre-empted dynamic PDCH carrying packet traffic reclaimed success rate during the measuring period.

%100ABRateSuccess Reclaimed TrafficPacket Carrying PDCH Dynamic Empted-Pre ×=

A − Number of Dynamic PDCHs Reclaimed by BSC B − Number of Pre-empted PDCHs Carrying Packet Traffic

PDCH Allocation Success Rate(%)

This statistics item is used to measure PDCH allocation success Rate during the measuring period.

%1001 ×⎟⎠⎞

⎜⎝⎛

++++++−=


A–Number of Uplink TBF Establishment Attempts

B–Number of Uplink TBF Establishment Failures due to Ms No Response C–Number of Downlink TBF Establishment Attempts

D– Number of Downlink TBF Establishment Failures due to MS No Response E–Number of Uplink EGPRS TBF Establishment Attempts

F–Number of Uplink EGPRS TBF Establishment Failures due to Ms No Response G–Number of Downlink EGPRS TBF Establishment Attempts

H–Number of Downlink EGPRS TBF Establishment Failures due to Ms No Response

Downlink RLC Data Throughput Per PDCH

This statistics item is used to measure the mean downlink GPRS&EGPRS RLC data throughput per PDCH during the measuring period.

60 Period MeasuringAPayloadRLCEGPRSDownlinkPayloadRLCownlinkD

PDCHperThroughputDataRLCDownlink

××+

=

A–Number of PDCHs Occupied by Downlink TBF

Uplink RLC Data Throughput per PDCH

This statistics item is used to measure the mean uplink GPRS&EGPRS RLC data throughput per PDCH during the measuring period.

60 Period MeasuringAPayloadRLCEGPRSplinkUPayloadRLCplinkU

PDCHperThroughputDataRLCUplink

××+

=

A–Number of PDCHs Occupied by Uplink TBF

Packet access performance

Mean inter-arrival time of packet access requests on CCCH( s )

This statistics item is used to measure the mean inter-arrival time of packet access requests on the CCCH during the measuring period.

( )

A60PeriodMeasuring

sCCCHonquestsAccessPacketofTimeArrivalInterMean×

=

− Re

A − Number of Packet Channel Requests Received on CCCH





Uplink assignment success rate (%)

This statistics item is used to measure the uplink assignment success rate during the measuring period.


A − Number of Uplink TBF Establishment Attempts B − Number of Successful Uplink TBF Establishment

Downlink assignment success rate (%)

This statistics item is used to measure the downlink assignment success rate during the measuring period.


A − Number of Downlink TBF Establishment Attempts B − Number of Successful Downlink TBF Establishment

Uplink GPRS TBF congestion rate (%)

This statistics item is used to measure the uplink GPRS TBF establishment congestion due to no radio resource during the measuring period.

%100C

BARateCongestionTBFGPRSUplink ×+=

A − Number of Uplink TBF Establishment Failures due to No Channel B − Number of Uplink TBF Abnormal Release due to No Channel C − Number of Uplink TBF Establishment Attempts

Downlink GPRS TBF congestion rate (%)

This statistics item is used to measure the downlink GPRS TBF establishment congestion due to no radio resource during the measuring period.

%100C

BARateCongestionTBFGPRSDownlink ×+=

A − Number of Downlink TBF Establishment Failures due to No Channel B − Number of Downlink TBF Abnormal Release due to No Channel C − Number of Downlink TBF Establishment Attempts

Uplink EGPRS TBF congestion rate (%)

This statistics item is used to measure the uplink EGPRS TBF establishment congestion due to no radio resource during the measuring period.

%100×+=C

BARateCongestionTBFEGPRSUplink

A − Number of Uplink EGPRS TBF Establishment Failures due to No Channel B − Number of Uplink EGPRS TBF Abnormal Release due to No Channel C − Number of Uplink EGPRS TBF Establishment Attempts

Downlink EGPRS TBF congestion rate (%)

This statistics item is used to measure the downlink EGPRS TBF establishment congestion due to no radio resource during the measuring period.

%100×+=C

BARateCongestionTBFEGPRSDownlink

A − Number of Downlink EGPRS TBF Establishment Failures due to No Channel B − Number of Downlink EGPRS TBF Abnormal Release due to No Channel C − Number of Downlink EGPRS TBF Establishment Attempts





Packet drop rate

Uplink GPRS TBF drop rate (%)

This statistics item is used to measure the uplink GPRS TBF drop rate during the measuring period.

%100A

CBRateDropTBFGPRSUplink ×⎟⎠⎞⎜

⎝⎛ +=

A − Number of Successful Uplink TBF Establishment B − Number of Uplink TBF Abnormal Release due to N3101 Overflow (Ms No Response) C − Number of Uplink TBF Abnormal Release due to N3103 Overflow (Ms No Response)

Downlink GPRS TBF drop rate (%)

This statistics item is used to measure the downlink GPRS TBF drop rate during the measuring period.

%100ABRateDropTBFGPRSDownlink ×⎟⎠⎞⎜

⎝⎛=

A − Number of Successful Downlink TBF Establishment B − Number of Downlink TBF Abnormal Release due to N3105 Overflow

Uplink EGPRS TBF drop rate (%)

This statistics item is used to measure the uplink EGPRS TBF TBF drop rate during the measuring period.

%100×⎟⎠⎞⎜

⎝⎛ +=

ACBRateDropTBFEGPRSUplink

A − Number of Successful Uplink EGPRS TBF Establishment B − Number of Uplink EGPRS TBF Abnormal Release due to N3101 Overflow (Ms No Response) C − Number of Uplink EGPRS TBF Abnormal Release due to N3103 Overflow (Ms No Response)

Downlink EGPRS TBF drop rate (%)

This statistics item is used to measure the downlink EGPRS TBF TBF drop rate during the measuring period.

%100ABRateDropTBFEGPRSDownlink ×⎟⎠⎞⎜

⎝⎛=

A − Number of Successful Downlink EGPRS TBF Establishment B − Number of Downlink EGPRS TBF Abnormal Release due to N3105 Overflow

Transmission performance at Um interface

Retransmission rate of uplink RLC data block (%)

This statistics item is used to measure the ratio of retransmitted RLC uplink data blocks using CS1~CS4 during the measuring period.

100% )E

DCBA - (1 (%) Block Data RLC Uplink of Rate sionRetransmis ×+++=

A–Number of Uplink RLC Data Blocks Using CS-1 Received by BSS B–Number of Uplink RLC Data Blocks Using CS-2 Received by BSS C–Number of Uplink RLC Data Blocks Using CS-3 Received by BSS D–Number of Uplink RLC Data Blocks Using CS-4 Received by BSS E–Total Number of Uplink RLC Data Blocks





uplink RLC payload( kbits )

This statistics item is used to measure the mean uplink GPRS data block payload (kbits)at the RLC layer during the measuring period.

( ) ( )1024

854D40C34B 23AkbitsPayloadRLCUplink ××+×+×+×=

A − Number of Uplink RLC Data Blocks Using CS-1 B − Number of Uplink RLC Data Blocks Using CS-2 C − Number of Uplink RLC Data Blocks Using CS-3 D − Number of Uplink RLC Data Blocks Using CS-4

Retransmission rate of downlink RLC data block (%)

This statistics item is used to measure the ratio of retransmitted RLC downlink data blocks using CS1~CS4 during the measuring period.

100% )E

DCBA - (1 (%) Block DataRLC Downlink of Rate sionRetransmis ×+++=

A − Retransmission Rate of Downlink RLC Data Blocks Using CS-1(%) B − Retransmission Rate of Downlink RLC Data Blocks Using CS-2(%) C − Retransmission Rate of Downlink RLC Data Blocks Using CS-3(%) D − Retransmission Rate of Downlink RLC Data Blocks Using CS-4(%) E − Total Number Downlink RLC Data Blocks

Downlink RLC payload( kbits )

This statistics item is used to measure the mean downlink GPRS data block payload (kbits)at the RLC layer during the measuring period.

( ) ( )1024

854D40C34B 23AkbitsPayloadRLCDownlink ××+×+×+×=

A − Number of Downlink RLC Data Blocks Using CS-1 B − Number of Downlink RLC Data Blocks Using CS-2 C − Number of Downlink RLC Data Blocks Using CS-3 D − Number of Downlink RLC Data Blocks Using CS-4





Retransmission rate of uplink EGPRS RLC data block (%)

This statistics item is used to measure the ratio of retransmitted uplink EGPRS RLC data blocks using MCS1~MCS9 during the measuring period.

100% )J

IHGFEDCBA - (1

Block Data RLCEGPRSUplinkofRatesionRetransmis

×++++++++=

A–Number of Uplink EGPRS RLC Data Blocks Using MCS-1 Received by BSS B–Number of Uplink EGPRS RLC Data Blocks Using MCS-2 Received by BSS C–Number of Uplink EGPRS RLC Data Blocks Using MCS-3 Received by BSS D–Number of Uplink EGPRS RLC Data Blocks Using MCS-4 Received by BSS E–Number of Uplink EGPRS RLC Data Blocks Using MCS-5 Received by BSS F–Number of Uplink EGPRS RLC Data Blocks Using MCS-6 Received by BSS G–Number of Uplink EGPRS RLC Data Blocks Using MCS-7 Received by BSS H–Number of Uplink EGPRS RLC Data Blocks Using MCS-8 Received by BSS I–Number of Uplink EGPRS RLC Data Blocks Using MCS-9 Received by BSS J–Total Number of Uplink EGPRS RLC Data Blocks

Uplink EGPRS RLC payload( kbits )

This statistics item is used to measure the mean uplink EGPRS data block payload (kbits)at the RLC layer during the measuring period.

( )( )

102474I68H56G74F56E44D73C82B 22A

8kbitsPayloadRLCEGPRSUplink×+×+×+×+×+×+×+×+×

×=

A– Number of Uplink EGPRS RLC Data Blocks Using MCS-1 B–Number of Uplink EGPRS RLC Data Blocks Using MCS-2

C–Number of Uplink EGPRS RLC Data Blocks Using MCS-3

D–Number of Uplink EGPRS RLC Data Blocks Using MCS-4

E– Number of Uplink EGPRS RLC Data Blocks Using MCS-5 F–Number of Uplink EGPRS RLC Data Blocks Using MCS-6

G–Number of Uplink EGPRS RLC Data Blocks Using MCS-7

H–Number of Uplink EGPRS RLC Data Blocks Using MCS-8

I–Number of Uplink EGPRS RLC Data Blocks Using MCS-9





Retransmission rate of downlink EGPRS RLC data block (%)

This statistics item is used to measure the ratio of retransmitted downlink EGPRS RLC data blocks using MCS1~MCS9 during the measuring period.

100% )J

IHGFEDCBA - (1

BlockData RLCEGPRSDownlinkofRatesionRetransmis

×++++++++=

A–Number of Downlink EGPRS RLC Data Blocks Using MCS-1 Received by MS B–Number of Downlink EGPRS RLC Data Blocks Using MCS-2 Received by MS C–Number of Downlink EGPRS RLC Data Blocks Using MCS-3 Received by MS D–Number of Downlink EGPRS RLC Data Blocks Using MCS-4 Received by MS E–Number of Downlink EGPRS RLC Data Blocks Using MCS-5 Received by MS F–Number of Downlink EGPRS RLC Data Blocks Using MCS-6 Received by MS G–Number of Downlink EGPRS RLC Data Blocks Using MCS-7 Received by MS H–Number of Downlink EGPRS RLC Data Blocks Using MCS-8 Received by MS I–Number of Downlink EGPRS RLC Data Blocks Using MCS-9 Received by MS J–Total Number Downlink EGPRS RLC Data Blocks

Downlink EGPRS RLC payload( kbits )

This statistics item is used to measure the mean downlink EGPRS data block payload (kbits)at the RLC layer during the measuring period.

( )( )

102474I68H56G74F56E44D73C82B 22A

8kbitsPayloadRLCEGPRSDownlink×+×+×+×+×+×+×+×+×

×=

A– Number of Downlink EGPRS RLC Data Blocks Using MCS-1 B–Number of Downlink EGPRS RLC Data Blocks Using MCS-2

C–Number of Downlink EGPRS RLC Data Blocks Using MCS-3

D–Number of Downlink EGPRS RLC Data Blocks Using MCS-4

E– Number of Downlink EGPRS RLC Data Blocks Using MCS-5 F–Number of Downlink EGPRS RLC Data Blocks Using MCS-6

G–Number of Downlink EGPRS RLC Data Blocks Using MCS-7

H–Number of Downlink EGPRS RLC Data Blocks Using MCS-8

I–Number of Downlink EGPRS RLC Data Blocks Using MCS-9

Packet data rate on air interface(UL / DL)

This indicator measures the packet data rate per cell on air interface in the uplink\downlink direction.


InterfaceAironRateDataacketP

++

=





Transmission performance at GB interface

Downlink LLC PDU payload(kbits )

This statistics item is used to measure the mean payload (kbits) of the downlink data at the LLC layer during the measuring period.

( )1024

8AkbitsPayloadPDULLCDownlink ×=

A − Total Number of Uplink LLC_PDUs Sent

Uplink LLC PDU payload( kbits )

This statistics item is used to measure the mean payload (kbits) of the uplink data at the LLC layer during the measuring period.

( )1024

8AkbitsPayloadPDULLCUplink ×=

A − Total Bytes of Uplink LLC_PDUs Sent

Mean Downlink NS_PDUs throughput(kbits/s)

This statistics item is used to measure the mean throughput (kbps) of the downlink NS_PDUs in a certain NSVC during the measuring period.

( )

60PeriodMeasuring10248A

skbitsThroughputPDUsNSDownlinkMean

×××

=/_

A − Total Bytes of NS PDUs Sent by NS Sublayer

Documents

Huawei BSC_Operation Manual - Performance Measurement