performance management guide

Airbridge Radio Access Subsystem Performance Management Guide Contents

Issue 02 (2007-10-26) Huawei Technologies Proprietary i

Contents

1 Overview of the Performance Management .........................................................................1-1 1.1 Performance Data System .............................................................................................................................1-2

1.1.1 Level 1 Data (KPI for the Daily Performance Monitoring) .................................................................1-2 1.1.2 Level 2 Data (Performance Data for Initial Analysis)..........................................................................1-3 1.1.3 Level 3 Data (Performance Data for Deep Locating Problems) ..........................................................1-4

1.2 Performance Management Process ...............................................................................................................1-6 1.2.1 Daily Performance Monitoring ............................................................................................................1-7 1.2.2 Problem Isolation and Location .........................................................................................................1-10

1.3 Performance Management Tool ..................................................................................................................1-15 1.3.1 M2000 Performance Management Tool.............................................................................................1-16 1.3.2 Nastar CDMA2000 ............................................................................................................................1-16

1.4 Starting the Performance Measurement ......................................................................................................1-17 1.4.1 Registering the System Task ..............................................................................................................1-17 1.4.2 Setting the Performance Alarm ..........................................................................................................1-17

1.5 Recommended Value of the Specification Threshold..................................................................................1-19 1.5.1 Purpose...............................................................................................................................................1-19 1.5.2 Recommended value of the 1X KPI specification threshold..............................................................1-19 1.5.3 Recommended value of the DO KPI specification threshold.............................................................1-20

1.6 Common Test Calls and Load Loading Functions ......................................................................................1-21

2 KPI of the 1X Daily Performance Monitoring......................................................................2-1 2.1 Service Quality..............................................................................................................................................2-2

2.1.1 Call Setup Success Ratio......................................................................................................................2-2 2.1.2 Paging Success Ratio ...........................................................................................................................2-3 2.1.3 Call Drop Ratio ....................................................................................................................................2-4 2.1.4 TCH Congestion Ratio.........................................................................................................................2-5 2.1.5 Soft HO Success Ratio.........................................................................................................................2-6 2.1.6 Hard HO Success Ratio........................................................................................................................2-6 2.1.7 Traffic/Call Drop Ratio ........................................................................................................................2-7 2.1.8 Reverse Link FER of Carrier ...............................................................................................................2-8

2.2 Traffic............................................................................................................................................................2-9 2.2.1 TCH, CE , and Walsh Traffic ...............................................................................................................2-9 2.2.2 Average Flow of PCF Data [kbit/s] ......................................................................................................2-9

Contents Airbridge Radio Access Subsystem

Performance Management Guide

ii Huawei Technologies Proprietary Issue 02 (2007-10-26)

2.3 Resource Usage...........................................................................................................................................2-10 2.3.1 Load of carrier....................................................................................................................................2-10 2.3.2 Public channel load Stat .....................................................................................................................2-11 2.3.3 Soft HO Ratio ....................................................................................................................................2-12 2.3.4 CSPU CPU Load [%].........................................................................................................................2-12 2.3.5 Forward Transmission power of the Carrier ......................................................................................2-13

3 KPI of the Daily EV-DO Performance Monitoring.............................................................3-1 3.1 Service Quality..............................................................................................................................................3-2

3.1.1 Connection Success Ratio....................................................................................................................3-2 3.1.2 IP Flow Setup Success Ratio................................................................................................................3-2 3.1.3 HRPD Session Setup Success Ratio ....................................................................................................3-3 3.1.4 Intra-BS Soft HO Success Ratio ..........................................................................................................3-3 3.1.5 Intra-AN Hard HO Success Ratio ........................................................................................................3-4

3.2 Traffic............................................................................................................................................................3-4 3.2.1 TCH, CE , and MacIndex Traffic.........................................................................................................3-4 3.2.2 RLP Octets Sent on Forward Channels (Including those resent)[KB/S]..............................................3-5

3.3 Resource Usage.............................................................................................................................................3-6 3.3.1 DO CCH Synchronization Control Channel Usage [%] ......................................................................3-6

4 Performance Data for Initial Analysis of CDMA2000 1X Problems ................................4-1 4.1 Service Quality..............................................................................................................................................4-2

4.1.1 Call Setup Success Ratio......................................................................................................................4-2 4.1.2 Paging Success Ratio .........................................................................................................................4-15 4.1.3 Call Drop Ratio ..................................................................................................................................4-18 4.1.4 Congestion Ratio................................................................................................................................4-22 4.1.5 Performance Stat of Packet Call Activation .......................................................................................4-36 4.1.6 Short Message Success Ratio.............................................................................................................4-41 4.1.7 Soft HO Success Ratio.......................................................................................................................4-44 4.1.8 Hard HO Success Ratio......................................................................................................................4-52 4.1.9 PCF HO Success Ratio ......................................................................................................................4-59 4.1.10 Data Rate Assignment......................................................................................................................4-64 4.1.11 Location Update Success Ratio........................................................................................................4-72 4.1.12 FCH FER Performance Stat .............................................................................................................4-73 4.1.13 SCH FER Measurement Stat............................................................................................................4-75

4.2 Traffic..........................................................................................................................................................4-76 4.2.1 Traffic Performance Stat(FCH)..........................................................................................................4-76 4.2.2 SCH Traffic Performance Measurement ............................................................................................4-78 4.2.3 1X Traffic Performance Measurement...............................................................................................4-80 4.2.4 Data Flow...........................................................................................................................................4-80

4.3 Resource Usage...........................................................................................................................................4-85 4.3.1 System Load Items.............................................................................................................................4-85 4.3.2 PCH Performance Measurement........................................................................................................4-89


Issue 02 (2007-10-26) Huawei Technologies Proprietary iii

4.3.3 ACH/EACH Performance Measurement ...........................................................................................4-91

5 Performance Data for Initial Measurement Point of CDMA2000 1xProblems..............5-1 5.1 Service Quality..............................................................................................................................................5-2

5.1.1 Connection Performance......................................................................................................................5-2 5.1.2 IP Flow Performance..........................................................................................................................5-14 5.1.3 Congestion Ratio................................................................................................................................5-20 5.1.4 Soft Handoff Performance .................................................................................................................5-23 5.1.5 Intra-AN Hard Handoff Performance ................................................................................................5-25

5.2 Traffic..........................................................................................................................................................5-26 5.2.1 TCH Traffic Performance Measurement............................................................................................5-26 5.2.2 CE Traffic Performance Measurement...............................................................................................5-27 5.2.3 MAC Index Traffic Performance Measurement.................................................................................5-27 5.2.4 DO Traffic Performance Measurement ..............................................................................................5-28 5.2.5 Throughput.........................................................................................................................................5-35 5.2.6 EVDO Rev.A QoS Performance Measurement..................................................................................5-40

5.3 Resource Usage...........................................................................................................................................5-42 5.3.1 Items About System Load ..................................................................................................................5-42 5.3.2 System Link Measurement Items.......................................................................................................5-44

6 Performance Data for Deeply Locating Problems ...............................................................6-1 6.1 Subscriber Interface Tracing .........................................................................................................................6-2

6.1.1 Introduction to Subscriber Interface Tracing .......................................................................................6-2 6.1.2 Functions of Subscriber Interface Tracing ...........................................................................................6-2 6.1.3 Operation .............................................................................................................................................6-2 6.1.4 Saving the Data and Processing the Data.............................................................................................6-3 6.1.5 Application Scenario ............................................................................................................................6-4

6.2 RFMT............................................................................................................................................................6-4 6.2.1 Introduction to RFMT..........................................................................................................................6-4 6.2.2 Functions of the RFMT........................................................................................................................6-4 6.2.3 Operation .............................................................................................................................................6-5 6.2.4 Saving the Data and Processing the Data.............................................................................................6-5 6.2.5 Application Scenario ............................................................................................................................6-5

6.3 CDR ..............................................................................................................................................................6-5 6.3.1 Introduction to the CDR.......................................................................................................................6-5 6.3.2 Functions of the CDR ..........................................................................................................................6-5 6.3.3 Operation .............................................................................................................................................6-6 6.3.4 Saving the Data and Processing the Data.............................................................................................6-6 6.3.5 Application Scenario ............................................................................................................................6-6

6.4 PSMM Data Collection .................................................................................................................................6-6 6.4.1 Introduction to PSMM Data Collection ...............................................................................................6-6 6.4.2 Functions of the PSMM .......................................................................................................................6-7 6.4.3 Operation .............................................................................................................................................6-7

Contents Airbridge Radio Access Subsystem


iv Huawei Technologies Proprietary Issue 02 (2007-10-26)

6.4.4 Saving the Data and Processing the Data.............................................................................................6-7 6.4.5 Application Scenario ............................................................................................................................6-7

6.5 BTS Reverse RSSI Exceptional Check .........................................................................................................6-8 6.5.1 Introduction to BTS Reverse RSSI Exceptional Check .......................................................................6-8 6.5.2 Functions of BTS Reverse RSSI Exceptional Check...........................................................................6-8 6.5.3 Operation .............................................................................................................................................6-8 6.5.4 Saving the Data and Processing the Data.............................................................................................6-8 6.5.5 Application Scenario ............................................................................................................................6-8

6.6 IMSI Tracing of the BTS...............................................................................................................................6-9 6.6.1 Introduction to IMSI Tracing of the BTS.............................................................................................6-9 6.6.2 Functions of IMSI Tracing of the BTS ................................................................................................6-9 6.6.3 Operation .............................................................................................................................................6-9 6.6.4 Saving the Data and Processing the Data.............................................................................................6-9 6.6.5 Application Scenario ............................................................................................................................6-9

6.7 Walsh Channel Monitoring..........................................................................................................................6-10 6.7.1 Introduction to Walsh Channel Monitoring........................................................................................6-10 6.7.2 Functions of Walsh Channel Monitoring ...........................................................................................6-10 6.7.3 Operation ...........................................................................................................................................6-10 6.7.4 Saving the Data and Processing the Data...........................................................................................6-12 6.7.5 Application Scenario ..........................................................................................................................6-12

7 Common Test Calls and Loading Simulation ......................................................................7-1 7.1 Markov Test Call ...........................................................................................................................................7-2

7.1.1 Introduction to Markov Test Call .........................................................................................................7-2 7.1.2 Scenario for Markov Test Call .............................................................................................................7-2 7.1.3 Making a Markov Test Call..................................................................................................................7-3 7.1.4 Measuring Forward and Reverse FERs of a Markov Test Call ............................................................7-3

7.2 Loopback Test Call........................................................................................................................................7-4 7.2.1 Introduction to Loopback Test Call......................................................................................................7-4 7.2.2 Scenario for Loopback Test Call ..........................................................................................................7-4 7.2.3 Making a Loopback Test Call ..............................................................................................................7-4 7.2.4 Observing the Results of Making a Loopback Test Call ......................................................................7-4

7.3 TDSO Test Call .............................................................................................................................................7-5 7.3.1 Introduction to TDSO Test Call ...........................................................................................................7-5 7.3.2 Scenario for TDSO Test Call ...............................................................................................................7-5 7.3.3 Making a TDSO Test Call ....................................................................................................................7-6 7.3.4 Observing the Results of Making a TDSO Test Call............................................................................7-6

7.4 OCNS............................................................................................................................................................7-6 7.4.1 Introduction to OCNS ..........................................................................................................................7-6 7.4.2 Scenario for OCNS ..............................................................................................................................7-6 7.4.3 Methods of OCNS Simulation .............................................................................................................7-6

7.5 OUNS............................................................................................................................................................7-7


Issue 02 (2007-10-26) Huawei Technologies Proprietary v

7.5.1 Introduction to OUNS..........................................................................................................................7-7 7.5.2 Scenario for OUNS..............................................................................................................................7-7 7.5.3 Methods of OUNS Loading .................................................................................................................7-7

Figures Airbridge Radio Access Subsystem


vi Huawei Technologies Proprietary Issue 02 (2007-10-26)

Figures

Figure 1-1 Performance management process....................................................................................................1-6

Figure 1-2 Procedure of performance analysis.................................................................................................1-11

Figure 1-3 Setting the performance alarm........................................................................................................1-18

Figure 4-1 CS Call Setup Performance Stat (calling procedure) ........................................................................4-4

Figure 4-2 CS Call Setup Performance Stat (calling procedure_call early released and call released by MS in connection state)..................................................................................................................................................4-5

Figure 4-3 CS Call Setup Performance Stat (called procedure) .........................................................................4-6

Figure 4-4 CS Call Setup Performance Stat (called procedure_call early released and call released by MS in connection state)..................................................................................................................................................4-7

Figure 4-5 PS Call Setup Performance Stat (calling procedure) ......................................................................4-11

Figure 4-6 PS Call Setup Performance Stat (calling procedure_call early released and call released by MS in connection state)................................................................................................................................................4-12

Figure 4-7 PS Call Setup Performance Stat (called procedure)........................................................................4-13

Figure 4-8 PS Call Setup Performance Stat (called procedure_call early released and call released by MS in connection state)................................................................................................................................................4-14

Figure 4-9 process of paging MSs originated by the CS domain .....................................................................4-16

Figure 4-10 process of call activation originated by the PS domain ................................................................4-17

Figure 4-11 CS call drop procedure..................................................................................................................4-20

Figure 4-12 PS call drop procedure..................................................................................................................4-22

Figure 4-13 TCH Congestion Performance Stat-CS Orig ................................................................................4-26

Figure 4-14 TCH Congestion Performance Stat-CS Term ...............................................................................4-27

Figure 4-15 TCH Congestion Performance Stat-PS Orig.................................................................................4-31

Figure 4-16 TCH Congestion Performance Stat-PS Term................................................................................4-32

Figure 4-17 TCH Congestion Performance Stat--Inter-RAC Hard HO............................................................4-33

Figure 4-18 TCH Congestion Performance Stat-Intra-RAC HHO...................................................................4-34

Figure 4-19 TCH Congestion Performance Stat--Inter-RAC SHO ..................................................................4-35

Figure 4-20 TCH Congestion Performance Stat-Intra-RAC Soft HO ..............................................................4-36

Figure 4-21 Performance Stat of Packet Call Activation-MS/AT Originated Activation .................................4-38

Airbridge Radio Access Subsystem Performance Management Guide Figures

Issue 02 (2007-10-26) Huawei Technologies Proprietary vii

Figure 4-22 Performance Stat of Packet Call Activation-Network Originated Activation ...............................4-39

Figure 4-23 Performance Stat of Packet Call Activation-MS/AT Originated Call ...........................................4-40

Figure 4-24 MT/PP Short Messages on PCHs[Times] .....................................................................................4-42

Figure 4-25 Broadcast Short Messages[Times]................................................................................................4-42

Figure 4-26 MO/PP Short Messages on ACHs[Times] ....................................................................................4-43

Figure 4-27 TCH Downlink Short Messages[Times] .......................................................................................4-43

Figure 4-28 TCH Uplink Short Messages[Times]............................................................................................4-44

Figure 4-29 Inter-RAC Soft HO Performance Stat ..........................................................................................4-47

Figure 4-30 Intra-RAC Soft HO Performance Stat ..........................................................................................4-51

Figure 4-31 Performance Stat of Inter-RAC Outgoing Hard HO.....................................................................4-54

Figure 4-32 Performance Stat of Inter-RAC Incoming Hard HO.....................................................................4-57

Figure 4-33 Inter-PCF Handoff Performance Stat (within the same PDSN and with MS/AT active) ..............4-61

Figure 4-34 Inter-PCF Handoff Performance Stat (inter-AN handoff with MS/AT dormant)..........................4-62

Figure 4-35 Inter-PCF Handoff Performance Stat (within the same PDSN and with MS/AT dormant) ..........4-63

Figure 4-36 Performance Stat of Forward SCH Request..................................................................................4-69

Figure 4-37 Performance Stat of Reverse SCH Request. .................................................................................4-72

Figure 4-38 Location Update Performance Stat ...............................................................................................4-73

Figure 5-1 HRPD session performance measurement (UATI assignment) ........................................................5-9

Figure 5-2 HRPD session performance measurement (access authentication).................................................5-10

Figure 5-3 HRPD session performance measurement (HRPD session release initiated by the AT).................5-10

Figure 5-4 HRPD session performance measurement (HRPD session release initiated by the AN)................5-11

Figure 5-5 HRPD session performance measurement (inter-AN dormant handoff) ........................................5-12

Figure 5-6 Performance Stat of RAC IP Flow Setup (AT-originated) ..............................................................5-17

Figure 5-7 Performance Stat of RAC IP Flow Setup (AN-originated) .............................................................5-18

Figure 5-8 Performance Stat of RAC IP Flow Release (AT-originated)...........................................................5-19

Figure 5-9 Performance Stat of RAC IP Flow Release (AN-originated)..........................................................5-19

Figure 5-10 Performance Stat of RAC IP Flow Configuration ........................................................................5-20

Figure 5-11 Flowchart of the AT calling process..............................................................................................5-22

Figure 5-12 Flowchart of soft handoff/softer handoff ......................................................................................5-24

Figure 5-13 EV-DO Intra-AN Hard Handoff Performance Measurement-RAC ..............................................5-26

Figure 6-1 Subscriber Interface Tracing Setting dialog box...............................................................................6-3

Figure 6-2 CDMA2000 1x Radio Resource Monitoring ..................................................................................6-11

Figure 6-3 CDMA2000 1X Radio Resource Monitoring .................................................................................6-12

Airbridge Radio Access Subsystem Performance Management Guide Tables

Issue 02 (2007-10-26) Huawei Technologies Proprietary ix

Tables

Table 1-1 Description of level 3 data..................................................................................................................1-4

Table 1-2 Key resources for traffic analysis .......................................................................................................1-9

Table 1-3 Recommended value of the 1X KPI specification threshold ............................................................1-19

Table 1-4 Recommended value of the DO KPI specification threshold ...........................................................1-20

Table 4-1 Measurement items about CS Call Setup Success Ratio ....................................................................4-2

Table 4-2 Measurement items about PS Call Setup Success Ratio.....................................................................4-8

Table 4-3 Measurement items about CS Call Drop Ratio.................................................................................4-18

Table 4-4 Measurement items about PS Call Drop Ratio .................................................................................4-21

Table 4-5 Measurement items about CS TCH Congestion Ratio......................................................................4-23

Table 4-6 Measurement items about PS TCH Congestion Ratio ......................................................................4-28

Table 4-7 Measurement items about Short Message Success Ratio .................................................................4-41

Table 4-8 Measurement items about Inter-BS Soft HO Success Ratio.............................................................4-45

Table 4-9 Measurement items about Intra-RAC Soft HO Success Ratio .........................................................4-49

Table 4-10 Measurement items about Inter-BS Outgoing Hard HO Success Ratio..........................................4-52

Table 4-11 Measurement items about Inter-RAC Incoming Hard HO Success Ratio ......................................4-55

Table 4-12 Measurement items about Performance Stat of Hard HO Decision Algorithm ..............................4-58

Table 4-13 Measurement items about Inter-PCF Handoff Performance Stat....................................................4-59

Table 4-14 Measurement items about Performance Stat of SCH Rate Assignment..........................................4-64

Table 4-15 Measurement items about Successful Forward SCH requests Ratio ..............................................4-68

Table 4-16 Measurement subsets related to Successful Forward SCH requests Ratio .....................................4-68

Table 4-17 Measurement items about Successful Reverse SCH requests Ratio...............................................4-70

Table 4-18 Measurement items related to Successful Reverse SCH requests Ratio.........................................4-70

Table 4-19 Measurement items about FCH FER Performance Stat..................................................................4-73

Table 4-20 Measurement items about Carrier FER and Eb/Nt Performance Stat .............................................4-75

Table 4-21 Measurement items about SCH FER Performance Measurement ..................................................4-75

Table 4-22 Measurement items about Density of Traffic Carried on TCH (Excluding HO) ............................4-76

Tables Airbridge Radio Access Subsystem


x Huawei Technologies Proprietary Issue 02 (2007-10-26)

Table 4-23 Measurement items about CE Traffic Density................................................................................4-77

Table 4-24 Measurement items about Walsh Traffic Density ...........................................................................4-77

Table 4-25 Measurement items about SCH Traffic Performance Measurement...............................................4-78

Table 4-26 Original items of CE seizure duration ............................................................................................4-79

Table 4-27 Measurement items about BTS STRM Transmitter Power Performance Measurement.................4-87

Table 4-28 Measurement items about BTS Channel Element Performance Measurement ..............................4-87

Table 4-29 Measurement items about License Performance Stat. ....................................................................4-89

Table 5-1 Description of Connection Success Ratio...........................................................................................5-2

Table 5-2 Measurement items about fast connection failure ..............................................................................5-3

Table 5-3 HRPD Session Setup Success Ratio ...................................................................................................5-5

Table 5-4 Measurement items about the causes of HRPD session release .........................................................5-6

Table 5-5 Measurement items about Session Information Query Success Ratio................................................5-8

Table 5-6 Measurement items of EV-DO Connection Performance Measurement-Carrier..............................5-13

Table 5-7 Measurement item of HRPD Session Performance Measurement-Carrier.......................................5-14

Table 5-8 Measurement items about IP Flow Setup Success Ratio with the real-time voice service as an example .............................................................................................................................................................5-14

Table 5-9 Measurement items about IP Flow Drop Ratio with the real-time voice service as an example ......5-16

Table 5-10 Measurement items about IP Flow Configuration Success Ratio ...................................................5-16

Table 5-11 Measurement items about Intra-BS Soft HO Success Ratio ...........................................................5-23

Table 5-12 Measurement items about Intra-AN Hard HO Success Ratio.........................................................5-25

Table 5-13 Other items of the same kinds ........................................................................................................5-29

Table 5-14 Other items of the same kinds ........................................................................................................5-30

Table 5-15 Other items of the same kind ..........................................................................................................5-31

Table 5-16 Items about DO RTCH PER Performance Stat...............................................................................5-33

Table 5-17 Other items of the same kind ..........................................................................................................5-41

Table 5-18 Items of BTS Channel Element Performance Measurement ..........................................................5-43

Table 5-19 Items of DO CCH Performance Measurement ...............................................................................5-44

Table 5-20 Items of DO CCH Performance Measurement ...............................................................................5-45

Airbridge Radio Access Subsystem Performance Management Guide 1 Overview of the Performance Management

Issue 02 (2007-10-26) Huawei Technologies Proprietary 1-1

1 Overview of the Performance Management

About This Chapter

The following table lists the contents of this chapter.

Section Describes

1.1 Performance Data System The performance data system.

1.2 Performance Management Process

The performance management process.

1.3 Performance Management Tool The performance management tool.

1.4 Starting the Performance Measurement

How to start the performance measurement.

1.5 Recommended Value of the Specification Threshold

The recommended value of the specification threshold.

1.6 Common Test Calls and Load Loading Functions

The common test calls and load loading functions.


Airbridge Radio Access Subsystem


1-2 Huawei Technologies Proprietary Issue 02 (2007-10-26)

1.1 Performance Data System The performance data is used to evaluate the network performance and the performance management is a process of analyzing different performance data to find out problems, locating problems, and solving problems.

Based on different performance management activities, the performance data can be classified into three levels

LEVEL 1: KPI of the daily performance monitoring − Indicates the KPI used in the daily monitoring. The KPI includes: − Service quality − Traffic − Resource usage Through these KPIs, you can evaluate the condition of the network and find out the performance problems existed in the network.

LEVEL 2: Performance data for initial analysis Indicates the KPI used in initial isolation and location after the problem is found out. Through the data, you can determine the cause of the performance problem and take the relative network optimization measures.

LEVEL 3: performance data for deeply locating problems Indicates other data resources used for deeply locating problems. The data resource includes: − Single user tracing − RF measurement tool (RFMT)

For different activities, you only need to collect the related data. For example, for a network, normally problems are found by monitoring network. Thus, you need to focus to only the basic KPIs. After finding out the problems, you need more detailed performance data to isolate and locate the problems. For some problems, deeper data are needed for locating.

The following contents detail the three types of data.

1.1.1 Level 1 Data (KPI for the Daily Performance Monitoring)

Description The KPI for the daily performance monitoring is the KPI used when evaluating the network performance and condition, such as the traffic, call drop rate, and call setup success rate. Through the KPIs, you can judge whether the network has problems.

Collection Collecting the level 1 data is collecting the traffic measurement data.

The equipment automatically collects the traffic measurement data. You do not need to operate. The traffic measurement data is reported every 30 minutes. All reported data are saved in the BAM of the RAC as a binary file and the BAM reports the counter that is used to measure the performance KPI to the M2000.



Saving the Data By default, the traffic data is stored in the FTP directory of the BAM. You can use the data through the FTP mode. The data is stored in the binary format. The daily traffic measurement file is saved in different folders and the folder is named as the date of that day. For example, 20060728. The traffic measurement file is named as the name of the measurement object plus the file generated time. For example, RACOVERALL 2006040000. DAT. Because the local server does not exist, you need to obtain the original traffic measurement data from the BAM through the FTP mode.

Browse and Analysis The following two methods are used for browsing and analyzing the data:

Browsing the traffic measurement data in real time through the M2000 client Browsing and analyzing the traffic measurement data by using the Nastar CDMA2000

analysis tool to import the traffic measurement data

1.1.2 Level 2 Data (Performance Data for Initial Analysis)

Description The performance data for initial analysis is the division of the daily performance monitoring KPI. Through these data, you can determine the specific causes of problems. Normally, the analysis is needed only when the problem occurs. For example, only when the call setup success rate is low, you need to collect and analyze the performance index to check what causes the problem.

Collection Refer to "Collection" in 1.1.1 "Level 1 Data (KPI for the Daily Performance Monitoring)."

The biggest difference between the performance data for initial analysis and the KPI for the daily performance monitoring is that you need to collect and analyze the performance data for initial analysis only when the problem is found out.

Saving the Data Refer to "Saving the Data" in 1.1.1 "Level 1 Data (KPI for the Daily Performance Monitoring)."

Browse and Analysis Refer to "Browse and Analysis" in 1.1.1 "Level 1 Data (KPI for the Daily Performance Monitoring)."





1.1.3 Level 3 Data (Performance Data for Deep Locating Problems)

Description The performance data for deeply locating problems is the performance data excluding the KPI. It includes:

RFMT Call history record (CDR) Pilot strength measurement message (PSMM) Checking the BTS reverse signal strength indicator (RSSI) Tracing the international mobile subscriber identity (IMSI) of the BTS Monitoring the Walsh channel

The level 3 data is the deepest and narrowest. It is used by the on-site engineers to precisely locate and solve problems.

Collection Collect the level 3 data only when deeply locating the performance problems. Table 1-1 lists the performance data.

Table 1-1 Description of level 3 data

Type Description Collection Storage Location Analysis Tools

Subscriber Interface Tracing

Trace the signaling of the special user during a call and display the result in the maintenance window is real time.

Use the user IMSI as an identifier to trace the signaling message of several interfaces and to choose the interface to be traced.

The data is stored in . . \RAC\OutputFile\trace\user, and the file name is date_time_user. dat.

LMT service maintenance system

RFMT Record the forward and reverse wireless environment information and call features during a call.

The following methods are used to collect the RFMT:

Tracing the call information of the sector carrier frequency

Collecting the optimization of the neighboring cell

Tracing the specified and random IMSI call

F:\CDMA2000\TRACE\RFMT

Nastar



Type Description Collection Storage Location Analysis Tools

CDR Records the key event and information during a call.

Export the record when a call ends. You can choose to export the record of all calls or the record of abnormal calls.

F:\CDMA2000\TRACE\CDR

Nastar

PSMM Pilot strength measurement message, such as the PSMM, PPSMM, and EPSMM messages or the air interface messages like CFSRPT.

The following two methods are used to collect the PSMM:

Periodical report Pilot triggering report

The data is stored in ..\RAC\TRACE\PSMM\PSMMTRACE********.dat.

Nastar

BTS reverse RSSI

Collect the BTS reverse main and diversity received signal strength.

The following two methods are used to collect the BTS reverse RSSI:

30S periodical record 2S threshold triggering

The data is stored in ..\RAC\Services\BTSITFLOG. The BTSXXX_ITF_LOG. LOG and BTSXXX_ITF_LOG. LOG are used to distinguish the BTS record.

Nastar

Tracing the IMSI of the BTS

Record the forward and reverse wireless environment information and call features of the user with specified IMSI during a call made in a specified BTS.

Tracing the IMSI of the BTS is achieved by the 2S periodical report. The collected data include:

Forward transmission power

Reverse RSSI Branch handoff status

Reverse error frame rate of the BTS level

Reverse capture

The data is stored in ..\RAC\Services\BTSITFLOG. The BTSXXX_ITF_LOG. LOG and BTSXXX_ITF_LOG. LOG are used to distinguish the BTS record.

Nastar

Monitoring the Walsh channel

Monitoring the Walsh channel power to check the integrity of the Walsh tree and the assignment ability of the SCH.

Collecting the quantity of the assigned and remained Walsh Collecting the allocated and remained Walsh space

The path to the radio resources monitoring data is:

. ..\RAC\OutputFile\RMON\RADIO_RESOURCE

. . \RAC\OutputFile\RMON\\EV-DORADIO_RESOURCE

LMT service maintenance system





Saving the Data Refer to "Collection."

Browse and Analysis Refer to "Collection."

1.2 Performance Management Process Normally, a performance management process consists of the following two phases:

Daily performance monitoring Problem isolation and location

Figure 1-1 shows the performance management process and its related performance data.

Figure 1-1 Performance management process

Network qualitymonitoring

Isolate problems

Deeply locateproblems

Adjust resources orexpand the capacity

Problemsdiscovered?

Thresholdsappear？

Daily perform

ance monitoring

Problem

Isolation and location

KPI of dailyperformance

monitoring (quality,traffic, resources)

Detailedmeasurement items

and alarm logs

Data for deeplocation (single

subscriber tracing,CDR)

No

Yes

No

Yes

Network qualitymonitoring



Daily Performance Monitoring The daily performance monitoring monitors the KPI to check whether the network has performance problems. The problems include: − The network quality cannot meet the expectation. − The resource is insufficient.

Problem Isolation and Location Problem isolation and location is how to locate and solve the problem when the problem occurs. Based on the complexity of the problem, the problem isolation and location is classified into: − Initial analysis − Deep locating The performance data needed by them are different.

1.2.1 Daily Performance Monitoring The daily performance monitoring is a process to find out the problem. It is the first phase of the performance management.

Based on the monitored object, the daily performance monitoring is classified into:

Network quality monitoring: used to evaluate whether the network service quality meets the requirement and find out problems.

Network resource bottleneck analysis: focuses on the measurement index that combines the traffic and resources. It is used to analyze whether the network resource has the bottleneck.

For detailed description of the KPI of daily performance monitoring, refer to 2 "KPI of the 1X Daily Performance Monitoring" and 3 "KPI of the Daily EV-DO Performance Monitoring."

Network Quality Monitoring The quality of the wireless network is shown by the KPI. The KPI includes:

Traffic Call setup success rate Call drop rate Congestion rate

These items directly reflect the network quality.

The KPI for the network quality monitoring is collected and measured through the traffic measurement. Then, compare the KPI with the threshold and analyze the KPI to find out the existing problems and the KPI to be optimized. Monitoring normally focuses to the whole network or some key areas.

The methods to monitor the network quality include:

Quasi real time monitoring The purpose of the quasi real time monitoring is to quickly know the change of the network KPI in certain scenarios by monitoring the KPI and take measures to improve the KPI if the KPI is getting worse.





The operation and management (OM) system can count the KPI and display and monitor the KPI in real time. When the network quality decreases, the OM system generates an alarm. The quasi real time monitoring is performed in the M2000. The monitoring period is the same as the collection period of the traffic measurement data. You can configure the period in the M2000. The period can be 30 or 60 minutes. You can set the KPI alarm threshold in the M2000. If the KPI reaches the alarm threshold, the M2000 automatically generates the performance alarm.

Routine report The routine report is used by the network planning engineers, network optimization engineers, or on-site engineers to know the network KPI and change of the network quality and to monitor the network quality. Compared to the quasi real time monitoring, the routine report requires analyzing and organizing the data.

The Nastar can export the report of the network health check. The report includes:

Network mark VIP user group mark VIP cell group mark Network interference cell check Neighboring cell configuration check

Handling method When finding out problems during the network quality monitoring, start the problem isolation and location. You need to collect the level 2 and level 3 data. For details, refer to 1.2.2 "1.2.2 Problem Isolation and Location." This document provides solutions to the problems that occur to each common KPI. For details, refer to 2 "KPI of the 1X Daily Performance Monitoring" and 3 "KPI of the Daily EV-DO Performance Monitoring."

Network Resource Bottleneck Analysis The network resource bottle analysis is to associate the KPIs such as the network congestion rate and resource usage and then analyze the KPIs. Together with the traffic change, the analysis is used to check whether the network has a resource bottleneck. In addition, the development trend and capacity expansion time are predicted based on the long-term running data of the network. Then based on the predicted data, find out the bottleneck that affects the network service development in advance and take measures to optimize the network.

Purpose The bottleneck of the network resource must lead to the decrease of the network quality. As a result, you need to know the running conditions of the network and the possibly existing bottleneck in advance. Take optimization measures before the network quality getting worse. The following are the causes of the resource bottleneck of a network: − Unbalanced resource usage of different services − Unbalanced traffic distribution in different areas The usages of the network resources have great differences. If the resources are not used in balance, some system resource becomes the network bottleneck.

Method to analyze the bottleneck



Based on the statistic such as the traffic change, resource assignment congestion, and resource usage, monitor, record, and measure the key points in the networking running. Summarize and measure the following performance index in a fixed interval: − Success and failure of related service − Delay − Throughput Refer to all performance indexes and the KPI measurement results, consider the software and hardware configuration of the network, and use the methods such as measurement, count, and comparison to know the network running condition and predict the possibly existing network bottleneck. Periodically monitor the traffic change. The monitor period can be: − A week − Half a month − A month − Two months At the same time, pay attention to the traffic congestion of each service. Avoid that the traffic in some area is too heavy and the network is partly overloaded. The traffic congestion rate is a key index to judge whether the resource bottleneck appears. Through the comparison and analysis of the traffic measurement data, you can know the cell which has the most serious congestion. Table 1-2 lists the key resources for traffic analysis.

Table 1-2 Key resources for traffic analysis

Contents Focus

CSPU load Measures the system load.

Public channel load Measures the public channel signaling of the carrier frequency and traffic load.

Carrier frequency load Measures the forward and reverse load of the carrier frequency.

Forward transmission power of the carrier frequency

Measures the usage of the carrier frequency power.

Usage of the CE, Walsh, and Licence

Measures the traffic load of the carrier frequency.

Power consumption per unit of traffic

Measures the relation between the traffic and the power.

For details, refer to 2 "KPI of the 1X Daily Performance Monitoring" and 3 "KPI of the Daily EV-DO Performance Monitoring."

Handling the resource bottleneck For the resource bottleneck of part of the system, you can add the system hardware or carrier frequency to share the traffic. You can also modify the configuration, adjust the parameter, and replace the equipment.





For the hot areas, if increasing resource and adjusting the parameter cannot meet the requirement of the traffic, you need to expand the system capacity. Otherwise, the service quality and user satisfaction are directly affected.

The Nastar provides a system solution to analyze the resource bottleneck.

1.2.2 Problem Isolation and Location In the daily performance monitoring, when the network has performance problems, you need to isolate and locate the problems.

Based on the object of the problem, the problem isolation and location is classified into:

Problems of the network quality Problems of the resource bottleneck

For problems of the resource bottleneck, the key point of the analysis is based on the index measurement data to judge which resource has the bottleneck. You can find out the resource bottleneck by checking the following during the call assignment:

Congestion of each resource Resource usage

For details, refer to the explanation of the congestion index. When you discover a problem, expand or adjust the resources. For details, refer to 1.3.1 "M2000 Performance Management Tool."

The following sections focus on the solutions to problems in network quality.

Common Procedure of Performance Analysis Performance analysis is based on the collected performance data to determine the causes of the problem and then to solve the problem. Based on the difficulty and depth of the problem, the performance analysis is classified into:

Initial analysis The initial analysis is to associate the alarm, configuration data, and index measurement data to check the causes of the problem. In addition, through the relation between index measurement data, you can refine the problem to an area, a time segment, or a network element. It also provides the general causes of the problem and the adjustment measures. For details about the performance data used in the deep locating, refer to 4 Performance Data for Initial Analysis of CDMA2000 1X Problems" and 5 "Performance Data for Initial Measurement Point of CDMA2000 1xEV-DOProblems."

Deep locating The deep locating is to deeply locate some difficult problems. It needs more specific data. In addition, it analyzes the data that collected both at the system and the road test. The logs, CDR, RFMT signaling tracing, and road test provide materials for the deep analysis of the part network performance.

For details about the performance data used in the deep locating, refer to 6 "Performance Data for Deeply Locating Problems."

Figure 1-2 shows the common procedure of performance analysis. It points out the data used in every activity.



Figure 1-2 Procedure of performance analysis

Daily performancemonitoring

Abnormal KPI

Take optimizationmeasures

Isolate and analyzeproblems

Check configurationdata

Alarm analysis

Analyze thecauses

Put carriers in order

Worst hours

Related m

easurement

items

Detailed measurementitems, alarm analysis, and

parameter statistics

Configurationdata abnormal?

Abnormalalarms?

Modify parameterconfiguration Clear alarms

Recheck abnormalKPIs

Problem solved?

Deep problemlocation

Coverage

Pilot pollution

Terminal problem

....

Take optimizationmeasures

CDR, RFMT, PSMM,drive test

Initial analysis ofproblems

Yes

No

Yes

No

Yes

No

YesNoProblem solved?





Initial Analysis Phase The input of the initial analysis phase is the abnormal KPIs found in the daily performance monitoring. The KPIs reflect whether the network quality has problems. For the common KPI definitions, refer to 2 "KPI of the 1X Daily Performance Monitoring" and 3 "KPI of the Daily EV-DO Performance Monitoring."

To isolate the problem, the cBSS provides more specific measurement indexes to the KPI. In the problem isolation phase, the traffic measurement data, alarm logs, and parameter configuration list are used. For detailed measurement items of each KPI, refer to 4 "Performance Data for Initial Analysis of CDMA2000 1X Problems" and 5 "Performance Data for Initial Measurement Point of CDMA2000 1xEV-DOProblems."

To obtain the overall network performance, you need to obtain the traffic measurement data of busy hour for more than a week. The way to handle the traffic measurement index is:

From the overall to a point, that is, check the whole performance of the RAC and find out the worst carrier frequency and the worst time segment.

From the main indexes to the specific indexes

As a result, the causes that lead to the decrease of the network quality are found out.

After finding out the problem, check the problem causes. You need to know the recent alarm of the system and whether the configurations of the parameter and resource are changed. Specifically, pay attention to the following information:

Equipment alarm analysis The equipment alarm reflects the operation status of the equipment in the whole network. When an index in the traffic measurement is abnormal, it is possibly that the equipment generates an alarm. You can save time by distinguishing the different alarms and associating them with the traffic measurement indexes. You can query the equipment alarm in the M2000 centralized fault management system and the cBSS alarm management system. If the alarms exist in the system, clear the alarms in time, estimate the impact to the KPI, and determine whether the fault causes the problem.

System parameter configuration check Unreasonable configuration of parameters affects the network quality. The system upgrade or resource adjustment causes the change of the parameter configuration. If you analyze only the phenomenon of the problem, the cost of analysis is high. As a result, during the initial analysis, check the basic network parameters and correct the wrongly configured parameters, including the PN planning, power control parameter, paging parameter, and register parameter.

Isolation analysis After excluding the equipment fault and system parameter configuration fault, according to the performance data, do the isolation analysis. The common ways are as follows: − Collating the carrier frequency − By collating the carrier frequency of abnormal indexes, you can obtain the analysis of

the TOPN cell whose index is abnormal. With the geography display of tools, you can obtain information such as the location, start time, and type of the problem.

− Worst time segment − Obtain the worst time segment when the indexes are abnormal. − Causes division



− Through the detailed traffic measurement indexes, further analyze the causes of the problem. The traffic measurement can analyze the following problems:

VCN interface problem Resource assignment failure Wireless interface fault

The reflection of these problems to the KPI is the abnormality of the indexes such as the call drop rate and call setup success rate. More specific traffic measurement indexes are needed to isolate the KPI problems. For example, the call failure is divided into:

VCN interface failure Call resource assignment failure Capture of the reverse service channel preamble failure Layer 2 handshake failure

Through the division of causes, you can effectively isolate the problem. − Index association − Many indexes are associated. For example, the interference and coverage

simultaneously affect several indexes. Thus, analyze the key KPI together with other indexes.

Take related measures to the network problem that is located by the traffic measurement, such as adjusting the antenna system, excluding the interference, and optimizing the parameters. Continue to focus on the change of the KPI.

Deep Locating Phase Due to the complexity and uncertainty of the wireless network, analyze only the traffic measurement data cannot deeply locate problems. The system provides the following data to help the analysis:

CDR RFMT PSMM

These data provide materials for deep locating. For details, refer to 7 "Common Test Calls and Loading Simulation."

With the CDR, RFMT, and PSMM, you can evaluate the network performance from several aspects. The aspect includes:

Analysis of the call setup failure and call drop Through the analysis of the CDR, distinguish the cause type of the call setup failure and call drop and determine the specific cause that lead to the call setup failure and call drop. The type of the causes includes: − Equipment abnormality − Wireless link failure If the failure is caused by the abnormal equipment, locate the abnormal equipment. If the wireless link fails, locate whether the failure is the forward link failure, reverse link failure, or handoff failure.





Analysis of the paging duration Through the analysis of the call access duration, you can precisely evaluate the connection and paging of the network, locate the carrier frequency and mobile phone that have problems, and distinguish whether the problem is caused by the equipment or the air interface access probe.

Analysis of the voice quality Analyze from the aspect of the system, the voice quality is affected by: − Source coding − Channel coding − Transmission bit error You can evaluate and analyze the voice quality and locate the carrier frequency and mobile phone that have problems through the analysis of the following: − Forward and reverse air interface bit error − Distribution of the uplink and downlink rate frames of the CFMR − Distribution of the uplink and downlink rate frames of the EVC

Optimization of the neighboring search window Using the analysis of the PSMM and the existed search window configuration in the BAM, check the rationality of the search window size of the active set and neighbor set. Then you can locate the carrier frequency whose search window is configured unreasonable. The analysis also provides configuration suggestions.

Optimization of the PSMM neighboring cell The analysis of the PSMM provides the optimization solution for the network structure, finds out the problem existed in the neighboring cells, and guides you to improve the network structure.

Analysis of the data service Through the analysis of the CDR, you can obtain the following information: − The average throughput at the user level − RLP average retransmission rate − Release times of the SCH application − Average FER − Forward and reverse load Thus, you can effectively evaluate the performance of the VIP data users and locate the data service transmission performance.

Analysis of the mobile phone abnormal power control Through the abnormal power control events recorded in the CDR, analyze all the IMSI call to check whether many abnormalities exist and collate them. Thus, you can locate the mobile phone whose power control is abnormal and the affected sector carrier frequency.

For the problems located by analyzing the CDR, RFMT, and PSMM, take the corresponding optimization measures and continuously trace the optimization results.

To deeply locate the problem, you need also analyze the data collected by the drive test.



The Nastar provides full solution for deeply locating problems. Use the Nastar to import the CDR, RFMT, PSMM, and interference logs. The Nastart provides associated analysis of call detailed record and helps you to locate the deeply problems, including:

Paging duration Voice quality Neighboring search window Unreasonable neighboring cell Data service Mobile phone

Collection of the Drive Test Data The drive test is that a mobile phone does a simulated call test in the specific line. It collects the related information through the drive test software. The drive test is irreplaceable in obtaining the information of the coverage structure of the wireless network. It checks whether the following problems exist:

Cross coverage Coverage dead zone Unbalanced uplink and downlink Reversely installed antenna

Normally, the following methods are used to analyze the network performance:

Comparison analysis of the data collected by the receiver and test MS Network coverage analysis Pilot pollution analysis Handoff analysis Access analysis Call drop analysis Analysis of the data service throughput and assignment strategy

During the drive test, test calls and load loading are used to simulate a real network. For details, refer to 7 "Common Test Calls and Loading Simulation."

1.3 Performance Management Tool The performance management tool collects, processes, displays, and analyzes the performance data.

M2000 Performance Management Tool Nastar CDMA2000





1.3.1 M2000 Performance Management Tool

Functions The M2000 performance management tool is a component of the M2000 mobile network element (NE) management system. Its functions include:

Collect and display the performance measurement data of a specified NE in real time. By defining a task, automatically collect and store the performance measurement data of

a specified NE and provide the data to users for analysis.

The M2000 can monitor all the NEs of the core network and access network, such as the VCN and RAC.

Application Scenario The following are the scenarios of the M2000 performance management tool:

Query and display the NE performance data of the core network and access network in real time.

Periodically collect and store the performance data of a specified NE and provide them to users for analysis.

Users The M2000 performance management tool is suitable for the maintenance engineers of the core network and access network.

1.3.2 Nastar CDMA2000

Functions The Nastar CDMA2000 is a background processing tool for network optimization. Its functions include:

Import and display the traffic measurement data and the CDR and RFMT for deeply locating problems.

According to the traffic measurement data, generate the daily monitoring report of the network performance.

Check the network configuration and automatically find out the wrongly or unreasonable configuration.

Analyze the CDR, helps to locate the network problem, and generate the solutions or optimization suggestions.

Application Scenario The following are the scenarios of the Nastar CDMA2000:

Daily monitoring of the network performance Deep locating of the network performance problems



Users The Nastar CDMA2000 is suitable for the maintenance engineers and network optimization engineers of the access network.

1.4 Starting the Performance Measurement The M2000 is a mobile NE management system. It performs the following functions:

Managing the NE Supporting the network management Centralized configuration management Centralized fault management Centralized performance management

1.4.1 Registering the System Task

Functions The system task provides performance data for the performance measurement report template of the self-defined report tool of the M2000 system. Because the performance measurement report needs the result form of the system task, you must register the system measure task before using the templates in the self-defined report system.

Only the administrator of the whole network and the super administrator can register the system measure task.

Procedure In the centralized performance management system, choose Task > Register System Task. A window is displayed, showing whether the registration succeeds and the cause of failure if the registration fails.

When all the NEs involved in the task are registered, the system displays the success information in the overall result report.

1.4.2 Setting the Performance Alarm

Functions Through the establishment of the monitoring of the performance specifications related to the task and setting of the performance alarm, the alarm is generated when the measurement specifications reach the threshold. The monitoring period is the same as the collection period of the traffic measurement data. You can configure the period in the M2000. The period can be 5, 15, 30, or 60 minutes.





Procedure Step 1 Select the task to be set the performance alarm from the task list of the centralized

performance management system. Choose Task > Setting the Performance Alarm from the menu. The Setting the Performance Alarm window is displayed, as shown in Figure 1-3.

Figure 1-3 Setting the performance alarm

Step 2 The list of the window displays all the settings of the performance alarm of the specifications registered in the task. The alarm status of the specification that does not set the performance alarm is Unset. Select the specification that needs to set the performance alarm. The specification name is displayed in Specification Name.

Select Activate under Alarm Status. The performance alarm setting of the specification is enabled.

Step 3 Set the alarm severity and threshold. Each specification can be classified into critical, major, minor, and warning. You can set different threshold for different severity. When the specification value is smaller than the lower limit, the alarm set by the lower limit is generated. When the specification value is greater than the upper limit, the alarm set by the upper limit is generated.

Step 4 Click Add after setting. The setting of the performance alarm is added to the list. Click Clear can clear the contents of the fields.

Step 5 Click OK when all specifications are set.

----End



1.5 Recommended Value of the Specification Threshold 1.5.1 Purpose

To ensure the monitoring of the KPI change and find out the exceptions of the KPI in time, the system sets the recommended threshold value for some specified KPI. When the KPI value is smaller than the threshold, the system automatically generates an alarm.

1.5.2 Recommended value of the 1X KPI specification threshold Table 1-3 lists the recommended value of KPI specification threshold in the 1X daily monitoring. The setting of the threshold varies with the network configuration. Table 1-3 is only for reference.

Table 1-3 Recommended value of the 1X KPI specification threshold

Property Item Name Referred Threshold RAC Level

Carrier Level

Call Setup Success Ratio (CS) Call Setup Success Ratio (CS) < 98%

√ √

Call Setup Success Ratio (PS) Call Setup Success Ratio (PS) < 95%

√ √

Paging Success Ratio Paging Success Ratio < 88% √ /

Call Drop Ratio (CS) Call Drop Ratio (CS) > 1.0% √ √

Call Drop Ratio (PS) Call Drop Ratio (PS) > 5% √ √

TCH Congestion Ratio TCH Congestion Ratio > 2% √ √

Successful Soft HO (CS) Successful Soft HO (CS) < 97% √ √

Successful Soft HO (PS) Successful Soft HO (PS) < 95% √ √

Traffic-Call Drop Ratio Traffic-Call Drop Ratio < 95 minutes

√ √

Service quality

Reverse FER Reverse FER > 2% / √

Density of Traffic Carried on TCH

Density of Traffic Carried on TCH (Excluding HO) > 25 Erl

/ √ Traffic

Average Flow of PCF Data Traffic excluding the soft HO > 400 Erl

√ /





Property Item Name Referred Threshold RAC Level

Carrier Level

Load of carrier Forward Load of Carrier > 85% Reverse Load of Carrier ≥ 50%

/ √

Public channel load Stat ACH Average Usage > 50% / √

Soft HO Ratio Soft HO Ratio > 50% √ √

CSPU CPU Load CSPU CPU Load > 50% √ /

Resource Usage

Forward transmission power of the carrier frequency

Average forward transmit power > 43 dBm

/ √

1.5.3 Recommended value of the DO KPI specification threshold Table 1-4 lists the recommended value of KPI specification threshold in the EV-DO daily monitoring. The setting of the threshold varies with the network configuration. Table 1-4 is only for reference.

Table 1-4 Recommended value of the DO KPI specification threshold

Property Item Name Referred Threshold

RAC Level

Carrier Level

Connection Setup Success Ratio Connection Setup Success Ratio < 95%

√ √

HRPD Session Setup Success Ratio Not available √ √

Call Drop Ratio Call Drop Ratio > 5%

√ √

Service quality

Intra-BS Soft HO Success Ratio Successful Soft HO < 95%

√ √

TCH Seizure Duration Not available / √ Traffic

RLP Octets Sent on Forward Channels Not available √ /

Resource Usage

DO CCH Synchronization Control Channel Usage

Not available √ √



1.6 Common Test Calls and Load Loading Functions In the performance analysis, to represent the problem or verify the problem, you need test calls to simulate the problem and load loading functions to simulate the forward and reverse loads.

The cBSS supports the following common test calls and load simulation functions:

Markov test call Loopback test call TDSO test call OCNS OUNS

For details, refer to 7 "Common Test Calls and Loading Simulation."

Airbridge Radio Access Subsystem Performance Management Guide 2 KPI of the 1X Daily Performance Monitoring


2 KPI of the 1X Daily Performance Monitoring

About This Chapter


Section Describes

2.1 Service Quality The CDMA2000 1X service quality measurement.

2.2 Traffic The CDMA2000 1X traffic measurement.

2.3 Resource Usage The CDMA2000 1X resource usage measurement.





2.1 Service Quality 2.1.1 Call Setup Success Ratio

Formula Call Setup Success Ratio = (Successful call setups/Call attempts) x 100%

Meaning This specification reflects the successful TCH assignment of the WLL wireless system. The situations include the call setup of:

Caller Callee Voice service Data service

The short message and handoff are excluded.

Explanation If the wireless link failure happens before the MS sends the Assignment Completion message, the call setup fails. Call setup failure ratio is a key specification in measuring the network performance. The network optimization is to locate the failure causes and reduce the call setup failure ratio.

If the call fails to be set up, a step in the signaling procedure fails to be executed. From the RAC, the call setup signaling has the following key points:

The RAC receives Origination Message. The RAC receives Assignment Request. The RAC sends Extended Channel Assignment Message. The RAC captures the reverse Traffic Channel Preamble frame. The RAC receives Service Connect Complete.

The RAC receiving Origination Message is a calling attempt. The failure of the following procedure points leads to the failure of the call setup. The causes of the failure in different procedure points are different.

Normally, the RAC fails to receive Assignment Request is because the call rejection from the VCN. The RAC fails to send Extended Channel Assignment Message is because the RAC fails to allocate the calling resource. The RAC fails to capture the Traffic Channel Preamble frame and fails to send Service Connect Complete are because that the wireless link quality is poor.

In the call setup procedure, users may actively terminate the call. This situation does not belong to the call setup failure. If the failure points are measured, you can take the related optimization measures.



Solution If the A interface fails, check the A interface link and alarms and adjust the relevant timer.

You can also analyze the failure causes of the CDR to check whether other abnormalities exist.

If the calling resource assignment fails a lot, it is possibly because that the terrestrial link congestion or internal software and hardware problems of the equipment. If the transmission link capacity is properly planned, you can check the transmission link congestion through the link fault alarms. Obtain the detailed release reasons from the CDR and further locate the problem from the equipment.

Failed to capture the reverse service preamble and TCH signaling are the causes of the call failure. The failure may be caused by poor forward and reverse signaling or timeout of the BTS timer. The detailed causes include: − Unreasonable network structure − Unreasonable setting of the power control parameters − Unreasonable setting of the access parameters − Interference − Unreasonable setting of the message resend times − Handoff conflict

For details, refer to 4.1.1 "Call Setup Success Ratio."

2.1.2 Paging Success Ratio

Formula Paging Success Ratio = (Successful pagings/Paging requests) x 100%

The Paging Success Ratio is the ratio of the number of responses that the RAC sends to the VCN to the number of the paging requests that the RAC receives from the VCN.

Meaning This specification reflects the paging performance of the WLL wireless system. The paging performance includes the paging success conditions of the callee, voice service, and data service.

Explanation The analysis method is similar to that of the call setup success ratio. The following factors affect the paging success ratio:

Wireless coverage: Because the paging success ratio is a key specification to reflect the network coverage, the network must be fully covered by the wireless.

Paging cooperation between the RAC and the VCN Unreasonable division of the registration area and the LAC area: For example, the plans

of the registration area and LAC area are inconsistent. The border of the LAC is planned to the area where the traffic is heavy.

Congestion exists in the paging channel, which leads to the loss of the paging message.





Solution When the paging success ratio decreases, check the factors listed in the explanation one by one.

For details, refer to 4. 1. 1"Call Setup Success Ratio. "

2.1.3 Call Drop Ratio

Formula Call drop ratio = [Number of call drops (forward and reverse channel)/Call setup success times] x 100%

Meaning Call drop is the abnormal release during the call hold, including the voice and data services.

Explanation This specification reflects the wireless environment and system quality of the WLL wireless system. A certain ratio of call drop is normal in the wireless network. Some cells which have high call drop ratio, however, need to be optimized. In the WLL system, the call drop is caused by the following causes:

Forward signal coverage is inadequate. The quality of the reverse link is poor and therefore the reverse FER is high. Handoffs fail because of improper handoff parameters. The neighboring cell is, by mistake, not configured. The PN that is not configured cannot

be added to the active set and causes interference, or that PN is not in the neighboring set and therefore handoffs cannot succeed.

The search window is not properly configured and therefore handoffs fail. Reverse interference has great impact on the quality of the network. The quality of the transmission link is poor, or the equipment is faulty.

When the call drop rate rises, take into consideration measurement items such as the soft handoff success ratio and the RSSI.

Solution When the call drop rate is high, check and analyzes the forward and reverse coverage.

For example, if the Ec/IO\o is poor, the receiving level and the coverage are poor. The cause may be that the antenna is not installed in a proper position, the angle of the antenna is not proper, or the connector of the feeder is worn.

If the reverse FER is high, it may be cause by problems in the reverse link. In such cases, you can add BTSs or adjust system parameters, such as the reverse power control threshold Eb/Nt. Serious reverse interference between multiple users may also result in a high FER.

Besides, improper neighboring cell relations, improper search window configuration, interference, poor link qualities, and faults in repeaters may cause a high call drop rate.




2.1.4 TCH Congestion Ratio

Formula TCH Congestion Ratio = (TCH Assignment Requests – Successful TCH Assignments) / TCH Assignment Requests x 100%

Meaning This measurement item reflects the occupation of WLL radio resources and is the basis of network capacity expansion.

Explanation TCH congestion refers to TCH assignment failures during call setup or handoffs. TCH setup failures are caused by insufficiency of resources such as Walsh codes, CE resources, forward and reverse powers, transmission links from the BTS to the RAC. When these resources are insufficient, control channels and traffic channels cannot be successfully assigned.

By monitoring the TCH congestion ratio, you can estimate the heavy traffic areas in the network and analyze whether the resources are reasonably assigned. In this way, you obtain some data to base network capacity expansion and network planning on.

For detailed measurement items about the congestion, refer to 5 "Performance Data for Initial Measurement Point of CDMA2000 1xEV-DOProblems

Solution When a type of resources is insufficient, check whether the resources are faulty. If the resources are not faulty, consider expanding the resources. Pay special attention to the insufficiency of the following resources:

When the Walsh codes are insufficient, the cause may only be extremely heavy traffic or code assignment failures owing to data services. In such cases, expand the network capacity.

When the forward power is insufficient, check the power configuration of the forward channel. Focus the check on: − Whether the pilot power occupies too much of the forward power − Whether the initial transmit power and maximum transmit power of the paging

channel, the synchronization channel, and the forward traffic channel are in proper proportion to the pilot power.

When the reverse power is insufficient, check whether parameters, such as the reverse load control parameters, are reasonably configured.

When the CE resources are insufficient, the number of subscribers probably exceeds the construction requirements. In such cases, expand the network capacity. Besides, a high proportion of soft handoffs may occupy too many CE resources. In such cases, lower the proportion of soft handoffs.






2.1.5 Soft HO Success Ratio

Formula Soft HO Success Ratio = (Successful Intra-BS Soft HOs + Successful Inter-BS Soft HOs)/(Intra-BS Soft HO Requests + Inter-BS Soft HO Requests) % 100%

Meaning The Soft HO Success Ratio is the success ratio of intra- and inter-RAC soft handoffs, including softer handoffs. When a leg is added or deleted, a soft handoff request is counted. When the addition or deletion of a leg fails, a soft handoff failure is counted.

Explanation The soft handoff is a feature of the WLL network. The Soft HO Success Ratio reflects the mobility performance and the system quality of the WLL network. In practice, you can analyze the Soft HO Success Ratio together with the Call Drop Ratio and the Congestion Ratio. In the WLL system, various factors affect the Soft HO Success Ratio. The common factors are as follows:

There is no main pilot coverage. The number of received legs exceeds the number of RAKE receivers, and these signals exceed the specified threshold. In such cases, the useful signals are severely interfered with, and the Soft HO Success Ratio is affected.

The soft handoff threshold and the soft handoff parameters are not reasonably configured.

Neighboring relations are, by mistake, not configured. The prioritization of neighboring cells is not reasonably configured. The search window is not reasonably configured Resources congestion occurs.

Solution Optimize the soft handoff parameters, adjust the network structure to reduce pilot

pollution, and improve the neighboring cell configuration. If soft handoff failures occur because of insufficiency of resources, expand the relevant

resources.


2.1.6 Hard HO Success Ratio

Formula Hard HO Success Ratio = (Successful Intra-BS Hard HOs + Successful Inter-BS Hard HOs)/(Intra-BS Hard HO Requests + Inter-BS Hard HO Requests) % 100%



Meaning The Hard HO Success Ratio is the success ratio of inter- and intra-frequency hard handoffs within RACs and between RACs. Within an RAC, there are different signaling points, and hard handoffs between signaling points follow the hard handoff procedure between RACs. Therefore, the traffic statistics distinguishes hard handoffs between signaling points from hard handoffs within the same signaling point. For inter-RAC hard handoffs, incoming handoffs and outgoing handoffs are measured.

When a hard handoff fails, a hard handoff failure is counted, regardless of the number of legs. Hard handoffs are measured according to the messages.

Explanation Hard handoffs consist of intra- and inter-frequency hard handoffs. In the WLL system, the success ratio of intra-frequency handoffs is low, and the success ratio of inter-frequency handoffs is subject to the hard handoff decision algorithm that is used. The hard handoff decision algorithms that are currently used are as follows:

Direct hard handoff algorithm MS-assisted hard handoff algorithm Pseudo-pilot hard handoff algorithm

Various factors affect the Hard HO Success Ratio. The analysis method is roughly the same as that for soft handoffs.

Solution Choose an appropriate hard handoff algorithm. Optimize hard handoff parameters. Reasonably plan the hard handoff areas. Optimize the neighboring cell configuration.

For details, refer to the relevant guide to parameters.

If hard handoff failures occur because of insufficiency of resources, expand the relevant resources. Refer to the solution to the congestion problem.


2.1.7 Traffic/Call Drop Ratio

Formula Traffic/Call Drop Ratio = (Density of Traffic Carried on TCH (Excluding HO) x 60/Call Drops)

Meaning The traffic well reflects the load on the network. A joint analysis of the traffic and the call drop performance of the system reflects the radio environment and system quality of the WLL network.





Explanation The Traffic/Call Drop Ratio is analyzed in the same way as the Call Drop Ratio. Note, however, that the fluctuation of the Traffic/Call Drop Ratio in a network with light traffic is relatively large and the fluctuation of the Traffic/Call Drop Ratio in a network with heavy traffic is relatively small.

Solution For details, refer to 4.1.1 "Call Setup Success Ratio."

2.1.8 Reverse Link FER of Carrier

Formula Reverse Link FER of Carrier = Packet Errors on Reverse Channels/Total Frames Sent on Reverse Frames

Meaning The Reverse Link FER of Carrier reflects the carrier voice quality and bit errors.

Explanation The FER of the channel is an important yardstick to measure the voice quality of the network. The analysis of the reverse link FER helps us to be aware of the quality of the reverse channel.

Generally, the reverse link FER goes too high because of interference. The reverse interference may come from the system itself or from the outside. When the system is subject by external interference, the reverse link FER and RSSI generally go too high. The interference deteriorates with the increase of subscribes. This results in a high reverse link FER. Therefore, the system load must be controlled properly.

Solution The major cause of a high FER is reverse interference. In such cases, clear the interference. A high FER may also be caused by improper configuration of power control parameters. In such cases, refer to the FER statistics to optimize the parameter configuration




2.2 Traffic 2.2.1 TCH, CE , and Walsh Traffic

Formula Density of Traffic Carried on TCH (Excluding HO) = TCH Seizure Duration (Excluding

HO) / (measurement period x 60) CE Traffic Density = CE Seizure Duration/(Measurement period x 60) Walsh Traffic Density = Walsh Seizure Duration/(Measurement period x 60)

Meaning This item measures the traffic on the TCH, excluding handoff traffic, CE (soft handoffs only) traffic, and Walsh (soft and softer handoffs) traffic. In this way, the actual subscriber traffic is measured.

Explanation The traffic measured here does not include handoffs so that the network load is directly and clearly measured. According to the traffic, figure out network optimization goals and strategies. When analyzing the measurement items, only the measurement data under heavy traffic has statistical sense. This is especially true of overall performance measurement items. Pay attention to sectors that bear heavy traffic and solve problems of such sectors with priority.

When the traffic drops, decrease in the call setup performance, call setup success rate, and call drop rate may all be the cause. Make efforts to optimize them. The charging policies may also affect traffic.

Solution When the traffic is so heavy that the system the system cannot bear, expand the system

capacity. When the traffic is light, check whether the network quality–related measurement items

deteriorate. If they do, optimize them.


2.2.2 Average Flow of PCF Data [kbit/s]

Formula Average Flow of PCF Uplink Data [Kbps] = (8 x PCF Uplink Bytes)/(60 x measurement

period) Average Flow of PCF Downlink Data [Kbps] = (8 x PCF Downlink Bytes)/(60 x

measurement period)





Meaning Average Flow of PCF Uplink Data [Kbps]: Average flow of uplink data that the PCF

receives from the BS Average Flow of PCF Downlink Data [Kbps]: Average flow of downlink data that the

PCF receives from the PDSN.

Explanation The Average Flow of PCF Uplink Data and Average Flow of PCF Downlink Data reflect the ability of the system to provide data services and the busyness state of the data service. If the flow is low, it may be caused by the following factors:

The number of data service subscribers is small. The uplink or the downlink is faulty. Buffer overflow occurs. The rate allocated to the air interface is low.

Solution When the Average Flow of PCF Uplink Data or Average Flow of PCF Downlink Data drops, check whether:

The uplink or the downlink is faulty Buffer overflow occurs The rate allocated to the air interface is low.

Also, consider the network operation strategy, which may cause the Average Flow of PCF Uplink Data or Average Flow of PCF Downlink Data to drop.

2.3 Resource Usage 2.3.1 Load of carrier

Formula Forward Load of Carrier[%] = Current transmit Power of Carriers/Nominal Transmit

Power Reverse Load of Carrier[%] = Number of Reverse Equivalent Subscribers/Maximum

Number of Subscribers

Meaning Forward Load of Carrier: It is the ratio of the current transmit power of carriers to the

maximum transmit power Reverse Load of Carrier: It is the ratio of number of reverse equivalent subscribers to the

maximum number of subscribers.



Explanation The carrier load statistics helps us be aware of the load on the network. In this way, we can find out the hot areas in the network and obtain basic data for capacity expansion and network planning.

Solution Generally, when the carrier load is too heavy, expand the capacity. Note that the carrier load needs to be measured constantly and that random fluctuation in the load may mislead your judgments.


2.3.2 Public channel load Stat

Formula ACH Average Using Ratio [%] PCH Average Using Ratio [%]

Meaning ACH Average Using Ratio: It indicates the busyness state of the ACH within the

measurement period. PCH Average Using Ratio: It indicates the busyness state of the PCH within the

measurement period.

Explanation The ACH Average Using Ratio and PCH Average Using Ratio reflect the load on the common channels of the network. These two items have an impact on the call setup success rate and the paging success rate. When the call setup rate and the paging success rate is quite low, check whether the using ratio of the ACH and the PCH is too high. If using ratio of the ACH or the PCH is abnormal, analyze the problem and take measures to lower the using ratio of the ACH or the PCH.

Solution When the using ratio of the common channel is too high, check and adjust the registration area planning and registration parameters. If the problem persists, check whether there is a bottleneck for the common channels, and add common channels, paging channels, ACHs, or PCHs if necessary.





2.3.3 Soft HO Ratio

Formula Soft HO Ratio = [CE Traffic Density – Density of Traffic Carried on TCH (Excluding HO)]/Density of Traffic Carried on TCH (Excluding HO)

Meaning This item is used to measure the proportion of resources occupied by soft handoffs.

Explanation Soft handoffs use multiple sectors to support main and diversity gains for calls. In this way, the link quality in the border areas of cells is improved. The power control function of the soft handoff reduces the interference caused by an MS to other MSs.

Therefore, proper soft handoffs improve call quality, enlarge the coverage, and expand the system capacity. However, if the proportion of soft handoffs is too high, call drops are more likely to occur, the signaling load on the system increases, CE resources of the system are occupied, and the forward capacity is affected. Generally, it is believe that the proportion of soft handoffs should remain above 50%. The major factors that affect the proportion of soft handoffs are as follows:

There are too many soft handoff areas. There is no main pilot coverage. The soft handoff threshold is not reasonably configured.

Solution Soft handoff areas refer to the belt areas that are close to the border of neighboring cells

and have overlapping coverage from the neighboring cells. If there are so many soft handoff areas that soft handoffs are triggered too frequently, check the areas at the borders of neighboring cells.

When the number of legs of the received signals exceeds the threshold, there is no main pilot coverage. In such cases, adjust the threshold.

If the soft handoff threshold is not properly set, adjust the values of the parameters T_ADD, T_DROP, T_COMP, and T_TDROP.

2.3.4 CSPU CPU Load [%]

Formula CPU load of the CSPU, measured by the RAC periodically.

Meaning CPU load of the CSPU



Explanation This item helps monitor the system load. Generally, the normal value of this item is less below 70%. The value of this item may be excessively in the following situations:

Sudden increase in traffic, as on festivals or at ceremonies Exceptions in the signaling board software The CSPU encounters a bottleneck.

Solution If exceptions occur during the operation of the singling board, check the related signaling

board. If it is a bottleneck problem, expand the capacity.

2.3.5 Forward Transmission power of the Carrier

Formula Max Transmit Power of Carrier [dBm] Average Transmit Power of Carrier [dBm]

Meaning Max Transmit Power of Carrier [dBm]: maximum of the transmit power of the carrier

(including common control channel and the TCH) Average Transmit Power of Carrier [dBm]: average of the transmit power of the carrier

(including common control channel and the TCH)

Explanation The Max Transmit Power of Carrier and Average Transmit Power of Carrier measure the forward transmit power level. This item reflects the load on the carrier and the traffic of the carrier. If the carrier is constantly overloaded, the power amplification module is easily broken. If the transmit power of the carrier is constantly high, expand the capacity or take other measures to free the carrier from the heavy load.

The factors that cause the forward transmit power to be too high are as follows"

The traffic is too heavy, and the forward power encounters a bottleneck. The power control parameters are not reasonably configured.

Solution If it is a bottleneck problem, expand the capacity. If the power control parameters are not reasonably configured, adjust them.

Airbridge Radio Access Subsystem Performance Management Guide 3 KPI of the Daily EV-DO Performance Monitoring


3 KPI of the Daily EV-DO Performance Monitoring

About This Chapter


Section Describes

3.1 Service Quality The CDMA2000 1xEV-DO service quality measurement.

3.2 Traffic The CDMA2000 1xEV-DO traffic measurement.

3.3 Resource Usage The CDMA2000 1xEV-DO resource usage measurement.





3.1 Service Quality 3.1.1 Connection Success Ratio

Formula Connection Success Ratio = Successful Connection Times/Connection Requests x 100%

Meaning This item reflects the proportion of the A9-Update A8 Ack messages that the AN receives from the PCF after the AN receives the ConnectionRequest messages from the AT during the establishment of EV-DO connections.

Explanation The major factors that cause EV-DO connection failures are as follows:

Allocation of call resources fails. Reverse TCH search fails. The trafficChannelComplete message is not received.

The analysis method is similar to that of the 1X call setup success rate.

Solution If such problems occur, adjust the switch configuration and improve the condition of the air interface (for example, by clearing interference) to improve the connection success rate.


3.1.2 IP Flow Setup Success Ratio

Formula IP Flow Setup Success Ratio = ([Successful IP Flow setup]/[IP Flow setup Requests]) X 100%

Meaning This item reflects the ratio of the number of the A9-Update A8 Ack messages that the AN receives from the PCF to the number of the ReservationOnRequest messages that the AN receives from the AT during the setup of the IP flow..

Explanation The major factors that cause EV-DO connection failures are failures in the request for Abis and air interface resources.



Solution Refer to 5.1.2 " IP Flow Performance."

3.1.3 HRPD Session Setup Success Ratio

Formula HRPD Session Setup Success Ratio = ([Successful HRPD Session setup]/[HRPD Session setup Requests]) X 100%

Meaning This item reflects the proportion of the UATIComplete messages returned by the AT after the AT sends the UATIRequest message to the AN through the access channel and receives the UATIAssignment message.

Explanation The factors that cause EV-DO session failures are as follows:

The AN fails to process the UATIRequest message. The AN does not receive the HardwareIDResponse message from the AT after sending

the HardwareIDRequest message. The AN does not receive the UATIComplete message from the AT after sending the

UATIAssignment message.

Solution If such problems occur, adjust the switch configuration and improve the condition of the air interface (for example, by clearing interference) to improve the connection success rate.


3.1.4 Intra-BS Soft HO Success Ratio

Formula Intra-BS Soft HO Success Ratio = ([Successful Intra-BS Soft HO EV-DO]/[Intra-BS Soft HO Requests-EV-DO]) x 100%

Meaning This item reflects the success rate of the AT's requests for reverse soft handoff channels.

Explanation The factors that cause EV-DO soft handoff failures are as follows:

The target cell does not have adequate resources. The Abis link is not available. The radio coverage is not adequate.





The analysis method is similar to that of the 1X call soft handoff success rate.

Solution For details, refer to 4.1.1 "Call Setup Success Ratio."

3.1.5 Intra-AN Hard HO Success Ratio

Formula Intra-AN Hard HO Success Ratio = ([Successful Intra-AN Hard HO]/[Intra-AN Hard HO Requests]) x 100%

Meaning This item reflects the success rate of intra-AN hard handoffs.

Explanation The factors that cause intra-AN hard handoff failures are as follows:

Radio resources unavailable Requested terrestrial resources unavailable MS Not detected by destination side

Solution Optimize the soft handoff parameters, adjust the network structure to reduce pilot

pollution, and improve the neighboring cell configuration. If soft handoff failures occur because of insufficiency of resources, expand the relevant

resources.

3.2 Traffic 3.2.1 TCH, CE , and MacIndex Traffic

Formula Carrier level item:

DO 0 /DO A Traffic Channel Connection Total time(DO 0) [Second] = Measurement Duration/Total Number of Legs

DO 0/DO A Traffic Channel CE Total time(DO 0) [Second] = Measurement Duration/Total Number of Softer Legs

DO 0/DO A Traffic Channel MacIndex Total time(DO 0/DO A) [Second] = Measurement Duration

DO 0/DO A Traffic Channel Connection Total time(DO 0) [Second] = Measurement Duration



DO 0/DO A Traffic Channel CE Total time(DO 0) [Second] = Measurement Duration x Number of SHO legs

DO 0/DO A Traffic Channel MacIndex Total time(DO 0) [Second] = Measurement Duration x Total Number of Legs

Meaning This item measures the traffic on the TCH, excluding handoff traffic, MacIndex (soft handoffs only) traffic, and Walsh (soft and softer handoffs) traffic. In this way, the actual subscriber traffic is measured.

Explanation According to the traffic, figure out network optimization goals and strategies. When analyzing the measurement items, only the measurement data under heavy traffic has statistical sense. This is especially true of overall performance measurement items. Pay attention to sectors that bear heavy traffic and solve problems of such sectors with priority.

When the traffic drops, decrease in the connection setup performance, and call drop rate may all be the cause. Make efforts to optimize them. The charging policies may also affect traffic.

Solution When the traffic is so heavy that the system the system cannot bear, expand the system

capacity. When the traffic is light, check whether the network quality–related measurement items

deteriorate. If they do, optimize them.

3.2.2 RLP Octets Sent on Forward Channels (Including those resent)[KB/S]

Formula RLP Octets Sent on Forward Channels (Including those resent)[KB/S] = RLP Octets Sent on Forward Channels (Including those resent)[KB/S] + RLP Octets Resent on Forward Channels[Byte]/1024

Meaning Every second (a current unit) the RAC measures this item for each call. If a call seizes TCHs, the RAC increments this item by 1.

Explanation This item reflects the actual throughput of the RLP. According to the throughput analysis, figure out network optimization goals and strategies.

Solution Expand the capacity if the data flows is constantly low.





3.3 Resource Usage 3.3.1 DO CCH Synchronization Control Channel Usage [%]

Formula DO CCH Sync Msg Using Ratio [%] = Total bits on the synchronous CCH of a carrier/(Packets on the synchronous CCH of a carrier x Bits per packet) x 100%

Meaning Total bits on the synchronous CCH of a carrier refer to bits of packets at the MAC layer

(excluding CC channel headers, padding, and reserved bits). Packets on the synchronous CCH of a carrier refer to packets at the MAC layer.

Explanation This item reflects the percentage of the useful bits in the timeslots actually used by the synchronization control channel. This item helps us know the load on the CCH.

Solution When the DO CCH Synchronization Control Channel Usage is low, expand the capacity or check whether the network quality–related measurement items deteriorate. If they do, optimize them.

Airbridge Radio Access Subsystem Performance Management Guide 4 Performance Data for Initial Analysis of CDMA2000 1X Problems


4 Performance Data for Initial Analysis of CDMA2000 1X Problems

About This Chapter


Section Describes

4.1 Service Quality The performance data for the CDMA2000 1X service quality measurement.

4.2 Traffic The performance data for the CDMA2000 1X traffic measurement.

4.3 Resource Usage The performance data for the CDMA2000 1X resource usage measurement.





4.1 Service Quality 4.1.1 Call Setup Success Ratio

The cBSS provides specific performance measurement items for the initial analysis of the call setup success ratio. These performance measurement items distinguish CS services from PS services, IS95 from IS2000, and calling parties from called parties. Also, the causes of call setup failures are put into specific categories.

CS Call Setup Performance Stat Item name: CS Call Setup Success Ratio[%] Meaning: call setup success ratio in the CS domain Item type: RAC performance measurement, RAC/carrier-level Measurement method: by calculation Formula: CS Call Setup Success Ratio[%] = (([Successful CS IS-2000 Orig/Term Call

Setups]+[Successful CS IS-95 Orig/Term Call Setups])/([CS IS-2000 Orig/Term Attempts]+[CS IS-95 Orig/Term Attempts]))%100%

Analysis: The RAC performance measurement items distinguish IS95 from IS2000 and calling parties from called parties. Also, the causes of call setup failures are put into specific categories. Table 4-1 lists the measurement items about CS Call Setup Success Ratio.

Table 4-1 Measurement items about CS Call Setup Success Ratio

Item Name Meaning Solution Formula

CS A1 Interface Failures[Times]

Number of call setup failures resulting from a cause that the RAC fails to receive Assignment Requests during CS service call access. See C in Figure 4-1 and Figure 4-3.

Check the A interface and the VCN for faults and check the capacity of the VCN gateway exchange and the configuration of the assignment request timer.

(CS IS-95 Orig Attempts + CS IS-95 Term Attempts + CS IS-2000 Orig Attempts + CS IS-2000 Term Attempts) – (CS IS-95 Orig Assignment Attempts + CS IS-95 Term Assignment Attempts + CS IS-2000 Orig Assignment Attempts + CS IS-2000 Term Assignment Attempts)

CS Call Resource Allocation Failures[Times]

Number of call setup failures resulting from failures of RAC call resources allocation during CS service call access

Check whether the call resources are used up by excessively heavy carrier traffic. Incorrect configuration or abnormal resource status may result in the deficiency of available resources.

(CS IS-95 Orig Assignment Attempts + CS IS-95 Term Assignment Attempts + CS IS-2000 Orig Assignment Attempts + CS IS-2000 Term Assignment Attempts) – (CS IS-95 Orig TCH Ready + CS IS-95 Term TCH Ready + CS IS-2000 Orig TCH Ready + CS IS-2000 Term TCH Ready)




CS Reverse TCH Preamble Acquisition Failures[Times]

Number of reverse TCH Preamble messages that the RAC fails to receive after sending a Channel Assignment Message during CS service call access. See E in Figure 4-1 and Figure 4-3.

Check the quality of the forward and reverse links, the configuration of the reverse preamble timer, and the configuration of power control parameters.

(CS IS-95 Orig TCH Ready + CS IS-95 Term TCH Ready + CS IS-2000 Orig TCH Ready + CS IS-2000 Term TCH Ready) – (CS IS-95 Orig Successful Acquisitions of Reverse TCH Preambles + CS IS-95 Term Successful Acquisitions of Reverse TCH Preambles + CS IS-2000 Orig Successful Acquisitions of Reverse TCH Preambles + CS IS-2000 Term Successful Acquisitions of Reverse TCH Preambles)

CS Radio Link Setup Failures[Times]

Number of reverse MS Ack Orders that the BSS fails to receive after acquiring a TCH Preamble message and sending a BS Ack Order to the MS during CS service call access. See F in Figure 4-1 and Figure 4-3.

Check whether the order messages cannot be received because of the poort quality of the forward and reverse links.

(CS IS-95 Orig Successful Acquisitions of Reverse TCH Preambles + CS IS-95 Term Successful Acquisitions of Reverse TCH Preambles + CS IS-2000 Orig Successful Acquisitions of Reverse TCH Preambles + CS IS-2000 Term Successful Acquisitions of Reverse TCH Preambles) – (CS IS-95 Orig Successful Setup of Radio Link + CS IS-95 Term Successful Setup of Radio Link + CS IS-2000 Orig Successful Setup of Radio Link + CS IS-2000 Term Successful Setup of Radio Link)

CS Service Connect Failures[Times]

Number of Service Connect Complete messages that the RAC fails to receive after sending a Service Connect message during CS service call access. See H in Figure 4-1 and Figure 4-3.

Check the quality of the air interface and of the forware and reverse links.

(CS IS-95 Orig Reaching Service Connect + CS IS-95 Term Reaching Service Connect + CS IS-2000 Orig Reaching Service Connect + CS IS-2000 Term Reaching Service Connect) – (Completion Times of CS IS-95 Orig Service Connection + Completion Times of CS IS-95 Term Service Connection + Completion Times of CS IS-2000 Orig Service Connection + Completion Times of CS IS-2000 Term Service Connection)

CS TCH Signaling Exchange Failures[Times]

Number of call setup failures that occur between the RAC receiving a reverse TCH Preamble message and sending the VCN an Assignment Complete message during CS service call access.


(CS IS-95 Orig Successful Acquisitions of Reverse TCH Preambles + CS IS-95 Term Successful Acquisitions of Reverse TCH Preambles + CS IS-2000 Orig Successful Acquisitions of Reverse TCH Preambles + CS IS-2000 Term Successful Acquisitions of Reverse TCH Preambles) – (Successful CS IS-95 Orig Call Setups + Successful CS IS-95 Term Call Setups + Successful CS IS-2000 Orig Call Setups + Successful CS IS-2000 Term Call Setups)





CS Radio Link Setup Failures[Times] + CS Service Connect Failures[Times] = CS Successful Acquisitions of Reverse TCH Preambles[Times] – Successful CS Call Setups[Times]

Calling Procedure in the CS Domain Figure 4-1 shows the CS Call Setup Performance Stat (calling procedure).

Figure 4-1 CS Call Setup Performance Stat (calling procedure)

MS VCNBS

Origination Message

BS Ack Order

Complete L3 Info:CM Service Request

Assignment Request

Channel Assignment Message

Tch Preamble

BS Ack Order

MS Ack Order

Service Connect Message

Service Connect Completion

Assignment Complete

Ringback Tone

AOrigination Message

B

C

D

E

F

G

H

I

A: CS Silent Re-origination[Times] B: CS Orig Attempts[Times] C: CS Orig Assignment Attempts[Times] D: CS Orig TCH Ready[Times] E: CS Orig Successful Acquisitions of Reverse TCH Preambles[Times] F: CS Orig Successful Setup of Radio Link[Times] G: CS Orig Reaching Service Connect[Times] H: Completion Times of CS Orig Service Connection[Times] I: CS Successful Orig Call Setups[Times]



The measurement items CS IS-95 Orig Calls Early Released[Times] and CS IS-2000 Orig Calls Early Released are measured when the RAC receives any of the following messages and then releases a call before sending an Assignment Complete message during CS service origination access:

A Release Order from the MS A Clear Command from the VCN An N_DISCONNECT_IND from the signaling connection and control part (SCCP) of

the VCN

The measurement item CS Calls Released by MS in Connection State[Times]is measured when the RAC receives a Release Order from the MS after sending an Assignment Complete message during the call, as shown in Figure 4-2.

Figure 4-2 CS Call Setup Performance Stat (calling procedure_call early released and call released by MS in connection state)

C

A

B

Release Order

Clear Command

Release Order

or

MS VCNBS

Origination Message

Assignment Complete

……

……

……

……

……

……

……

……

During the entire process, at any time before receiving the Assignment Completemessage, if the BSC receives:

During the entire process, at any time after receiving the Assignment Completemessage, if the BSC receives:

A,B: CS Orig Calls Early Released[Times] C: CS Calls Released by MS in Connection State[Times]





Called Procedure in the CS Domain Figure 4-3 shows CS Call Setup Performance Stat (called procedure).

Figure 4-3 CS Call Setup Performance Stat (called procedure)

MS VCNBSS

1. ALLOCATION

3. ESTABLISH

2. ALLOCATION COMPLETE

4. ESTABLISH ACK

LE

5. Paging Request

9. Complete L3 Info:Paging Response

7. ReceiveCalling Number

(FSK/DTMF)6. Page Message

14. BS Ack Order

13. Tch Preamble

10. Base StationAck Order

17. Service ConnectCompletion

16. Service Connect Message

15. MS Ack Order

24. SIGNAL (off hook)

18. AssignmentComplete

8. Page Response Message

11. Assignment Request12. Channel Assignment

Message

19. Alert with Info

20. MS Ack Order

21. Connect

22. BS Ack Order23. Connect

A

B

C

D

E

F

G

H

I

A: CS Term Attempts[Times] B: CS Term Assignment Attempts[Times] C: CS Term TCH Ready[Times] D: CS Term Successful Acquisitions of Reverse TCH Preambles[Times] E: CS Term Successful Setup of Radio Link[Times] F: CS Term Reaching Service Connect[Times] G: Completion Times of CS Term Service Connection[Times] H: CS Successful Term Call Setups[Times] I: CS Term Answered[Times]



The measurement item Term Calls Early Released[Times] is measured when the RAC receives any of the following messages and then releases a call before sending an Assignment Complete message during CS service called access:


the VCN

The measurement item CS Orig Calls Released by MS in Connection State[Times] is measured when the RAC receives a Release Order from the MS after sending an Assignment Complete message during CS service call, as shown in Figure 4-4.

Figure 4-4 CS Call Setup Performance Stat (called procedure_call early released and call released by MS in connection state)

C

A

B

Release Order

Clear Command

Release Order

or

MS VCNBS

Assignment Complete

……

……

……

……

……

……

……

……




A,B: CS Term Calls Early Released[Times] C: CS Calls Released by MS in Connection State[Times]





PS Call Setup Performance Stat Item name: PS Call Setup Success Ratio[%] Meaning: call setup success ratio in the PS domain Item type: RAC performance measurement, RAC/carrier-level Item type: compound item Measurement method: by calculation Formula: PS Call Setup Success Ratio[%] = (([Successful PS IS-95/2000 Orig/Term Call

Setups]+[Successful PS IS-95/2000 Orig/Term Call Setups])/([PS IS-95/2000 Orig/Term Attempts]+[PS IS-95/2000 Orig/Term Attempts]))%100%

Analysis: The RAC performance measurement items distinguish calling parties from called parties. Also, the causes of call setup failures are put into specific categories. Table 4-2 lists the measurement items about PS Call Setup Success Ratio.

Table 4-2 Measurement items about PS Call Setup Success Ratio.


PS Call Resource Allocation Failures[Times]

Number of call setup failures resulting from failures of RAC call resources allocation during PS service call access

Check whether the call resources are used up by excessively heavy carrier traffic. Incorrect configuration or abnormal resource status may result in the deficiency of available resources.

(PS IS-95 Orig Assignment Attempts + PS IS-95 Term Assignment Attempts + PS IS-2000 Orig Assignment Attempts + PS IS-2000 Term Assignment Attempts) – (PS IS-95 Orig TCH Ready + PS IS-95 Term TCH Ready + PS IS-2000 Orig TCH Ready + PS IS-2000 Term TCH Ready)

PS Reverse TCH Preamble Acquisition Failures[Times]

Number of reverse TCH Preamble messages that the RAC fails to receive after sending a Channel Assignment Message during PS service call access. See E in Figure 4-5 $and Figure 4-7.

Check the quality of the forward and reverse links, the configuration of the reverse preamble timer, and the configuration of power control parameters.

(PS IS-95 Orig TCH Ready + PS IS-95 Term TCH Ready + PS IS-2000 Orig TCH Ready + PS IS-2000 Term TCH Ready) – (PS IS-95 Orig Successful Acquisitions of Reverse TCH Preambles + PS IS-95 Term Successful Acquisitions of Reverse TCH Preambles + PS IS-2000 Orig Successful Acquisitions of Reverse TCH Preambles + PS IS-2000 Term Successful Acquisitions of Reverse TCH Preambles)




PS Radio Link Setup Failures [Times]

Number of reverse MS Ack Orders that the BSS fails to receive after acquiring a TCH Preamble message and sending a BS Ack Order to the MS during PS service call access. See F in Figure 4-5 and Figure 4-7.

Check whether the order messages cannot be received because of the poort quality of the forward and reverse links.

(PS IS-95 Orig Successful Acquisitions of Reverse TCH Preambles + PS IS-95 Term Successful Acquisitions of Reverse TCH Preambles + PS IS-2000 Orig Successful Acquisitions of Reverse TCH Preambles + PS IS-2000 Term Successful Acquisitions of Reverse TCH Preambles) – (PS IS-95 Orig Successful Setup of Radio Link + PS IS-95 Term Successful Setup of Radio Link + PS IS-2000 Orig Successful Setup of Radio Link + PS IS-2000 Term Successful Setup of Radio Link)

PS Service Connect Failures [Times]

Number of Service Connect Complete messages that the RAC fails to receive after sending a Service Connect message during PS service call access. See H in Figure 4-5 and Figure 4-7.


(PS IS-95 Orig Reaching Service Connect + PS IS-95 Term Reaching Service Connect + PS IS-2000 Orig Reaching Service Connect + PS IS-2000 Term Reaching Service Connect) – (Completion Times of PS IS-95 Orig Service Connection + Completion Times of PS IS-95 Term Service Connection + Completion Times of PS IS-2000 Orig Service Connection + Completion Times of PS IS-2000 Term Service Connection)

PS TCH Signaling Exchange Failures [Times]

Number of call setup failures that occur between the RAC receiving a reverse TCH Preamble message and sending the VCN an Assignment Complete message during PS service call access.


(PS IS-95 Orig Successful Acquisitions of Reverse TCH Preambles + PS IS-95 Term Successful Acquisitions of Reverse TCH Preambles + PS IS-2000 Orig Successful Acquisitions of Reverse TCH Preambles + PS IS-2000 Term Successful Acquisitions of Reverse TCH Preambles) – (Successful PS IS-95 Orig Call Setups + Successful PS IS-95 Term Call Setups + Successful PS IS-2000 Orig Call Setups + Successful PS IS-2000 Term Call Setups)





CS Radio Link Setup Failures[Times] + CS Service Connect Failures[Times] = CS Successful Acquisitions of Reverse TCH Preambles[Times] – Successful CS Call Setups[Times]

Calling Procedure in the PS Domain The calling procedure in the PS domain involves MS-originated calls and MS-originated call activations.

The MS-originated call activation procedure is similar to the MS-originated calling procedure in the PS domain, but the A10/A11 connection, the PPP connection, and the Mobile IP connection (if used) do not need to be re-established in the MS-originated call activation procedure. The measurement items of the MS-originated call activation procedure are consistent with the MS-originated call activation procedure.



Figure 4-5 shows PS Call Setup Performance Stat (calling procedure).

Figure 4-5 PS Call Setup Performance Stat (calling procedure)

PDSNBSMS PCF

A11 Registration Request(Life time)

MSC

Origination

BS ACK Order CM Service Request

Assignment Request

Assignment Complete

Transmitting packet data

Establishing PPP connection, Mobile IP Registration

A11-Registration Reply (Life time, Accept)

ECAM

BSAck Order

MS Ack Order

Service Connect Msg

Service Connect Cmp Msg

Tch Preamble

A9-Setup-A8

A9-Connect-A8

B

C

D

E

F

G

H

I

Origination A

A: PS Silent Re-origination[Times] B: PS Orig Attempts[Times] C: PS Orig Assignment Attempts[Times] D: PS Orig TCH Ready[Times] E: PS Orig Successful Acquisitions of Reverse TCH Preambles[Times] F: PS Orig Successful Setup of Radio Link[Times] G: PS Orig Reaching Service Connect[Times] H: Completion Times of PS Orig Service Connection[Times] I: PS Successfull Orig Call Setups[Times]





The measurement item PS Orig Calls Early Released[Times] is measured when the RAC receives any of the following messages and then releases a call before sending an Assignment Complete message during PS service origination access:


the VCN

The measurement item PS Orig Calls Released by MS in Connection State[Times] is measured when the RAC receives a Release Order from the MS after sending an Assignment Complete message during PS service call, as shown in Figure 4-6. The measurement items of the MS-originated call activation procedure are consistent with the MS-originated calling procedure in the PS domain.

Figure 4-6 PS Call Setup Performance Stat (calling procedure_call early released and call released by MS in connection state)

PDSNBSMS PCFVCN

Origination

Assignment Complete

CRelease Order

……

A

B

Release Order

Clear Commandor

……

……

……

……

……

……

……

……

……

……

……

……

……

……

……



A,B: PS Orig Calls Early Released[Times] C: PS Orig Calls Released by MS in Connection State[Times]



Called Procedure in the PS Domain In the PS called procedure, the network side originates call activation. Figure 4-7 shows the PS Call Setup Performance Stat (called procedure).

Figure 4-7 PS Call Setup Performance Stat (called procedure)

Assignment Complete

Complete L3 info: Paging Response

Page Response Message

Assignment Request

A9-Setup-A8

A9-Connect-A8

BS Ack Order

IS-2000 TchSetup

Active Packet Data Session

Packet Data Traffic

A9-BS Service Request

BS Service Request

BS Service Response

A9-BS Service Response

Paging Request

General Page Message

Dormant,PPP connection is maintained

MS BS MSC PCF PDSN

A

B

C

D

A: PS Term Attempts[Times] B: PS Term Assignment Attempts[Times] C: PS Term TCH Ready[Times] PS Term Successful Acquisitions of Reverse TCH Preambles[Times] PS Term Successful Setup of Radio Link[Times] PS Term Reaching Service Connect[Times] Completion Times of PS Term Service Connection[Times] D: pS Successfull Term Call Setups[Times]





The measurement item PS Term Calls Early Released[Times] is measured when the RAC receives any of the following messages and then releases a call before sending an Assignment Complete message during PS service called access:


the VCN

The measurement item PS Orig Calls Released by MS in Connection State[Times] is measured when the RAC receives a Release Order from the MS after sending an Assignment Complete message during PS service call, as shown in Figure 4-8.

Figure 4-8 PS Call Setup Performance Stat (called procedure_call early released and call released by MS in connection state)

Assignment Complete



Assignment Request

A9-Setup-A8

A9-Connect-A8

BS Ack Order

IS-2000 TchSetup


Packet Data Traffic


BS Service Request

BS Service Response


Paging Request



MS BS VCN PCF PDSN

A

B

C

D

A,B: PS Term Calls Early Released[Times] C: PS Term Calls Released by MS in Connection State[Times]



4.1.2 Paging Success Ratio Paging Success Ratio in the CS/PS Domain

Item name: Paging Success Ratio[%] Meaning: ratio of the number of paging responses that the RAC sends to the RAC to the

number of paging requests that the RAC receives from the VCN. Item type: RAC performance measurement, RAC/carrier-level Measurement method: by calculation Formula: Paging Success Ratio [%] = (Successful pagings/Paging requests) x 100% Measurement point:

− Responses on the first/second/third paging attempts[Times]: measured when each module of the RAC receives a response message after the module sends the first/second/third paging request. Measurement starts once the conditions are met without distinguishing service types. A and B in Figure 4-9 indicate the measurement points in the process of paging MSs originated by the CS domain. A and B in Figure 4-10 indicate the measurement points in the process of call activation originated by the PS domain.

− Paging Responses[Times]: measured when the RAC sends the Paging Response message to the VCN. Measurement starts once the conditions are met without distinguishing service types. C in Figure 4-9 indicates the measurement point in the process of paging MSs originated by the CS domain. C in Figure 4-10 indicates the measurement point in the process of call activation originated by the PS domain.





Figure 4-9 shows the process of paging MSs originated by the CS domain.

Figure 4-9 process of paging MSs originated by the CS domain

MS MSC

Page message

Complete L3 Info:Paging Response

BS Ack Order


BS Ack Order

MS Ack Order



Assignment Complete

Paging Request


Assignment Request

TCH Preamble

Alert with Info

MS Ack Order

Connet Order

BS Ack Order

Connect

BSS

A

B

C

Paging Request

A, B: Paging requests C: Paging Responses[Times]:



Process of Call Activation Originated by the PS Domain Figure 4-10 shows the process of call activation originated by the PS domain.

Figure 4-10 process of call activation originated by the PS domain

Assignment Complete



Assignment Request

A9-Setup-A8

A9-Connect-A8

BS Ack Order

IS-2000 TchSetup


Packet Data Traffic


BS Service Request

BS Service Response


Paging Request



MS BS MSC PCF PDSN

A

B

C

Paging Request

A, B: Paging requests C: Paging Responses[Times]





4.1.3 Call Drop Ratio The cBSS provides specific performance measurement items for the initial analysis of the call drop ratio. These performance measurement items distinguish CS services from PS services. Also, the causes of call drops are put into specific categories.

CS Call Drop Performance Stat In the CDMA system, the call drop performance in the CS domain is measured with the compound item CS Call Drop Ratio[%].

Item name: CS Call Drop Ratio[%] Meaning: call drop ratio in the CS domain Item type: RAC performance measurement, RAC/carrier-level CS Call Drop Ratio[%] = ([CS Call Drops (Too many Erasure frames)[Times]]+[CS Call

Drops (No reverse frame received)[Times]]+[CS Call Drops (Abis interface abnormal)[Times]]+[CS Call Drops (A interface abnormal)[Times]]+[CS Call Drops (Other causes)[Times]]) / ([Successful CS Orig Call Setups[Times]]+ [Successful CS Term Call Setups[Times]] + [Successful CS Incoming Hard HOs[Times]]) x 100

Analysis: The RAC performance measurement items distinguish IS95 from IS2000 and calling parties from called parties. Also, the causes of call drops are put into specific categories. Table 4-3 lists the measurement items about CS Call Drop Ratio.

Table 4-3 Measurement items about CS Call Drop Ratio


CS Call Drops (Too many Erasure frames)[Times]

The RAC measures every time a call drop arises from a cause that the BSS receives too many idle or erasure frames after successful call setup of CS services and diversity combination, as indicated by A of Figure 4-11.

Check the forward and reverse coverage, the forward and reverse link interference, and BTS hardware faults (such as faults in the transceiver module and the power amplification module) and check the configuration of parameters, including power control parametera and handoff parameters.

CS IS-95 Call Drops (Too many Erasure frames) + CS IS-2000 Call Drops (Too many Erasure frames)

CS Call Drops (No reverse frame received)[Times]

The RAC measures every time a call drop arises from a cause that the BSS fails to receive any reverse frames of a call within a period after the successful call setup of CS services, as indicated by A of Figure 4-11.

Check the Abis link for faults.

CS IS-95 Call Drops (No reverse frame received) + CS IS-2000 Call Drops (No reverse frame received)




CS Call Drops (Abis interface abnormal)[Times]

The RAC measures every time a call drop arises from Abis interface failures after successful call setup of CS services. This measurement item does not include CS Call Drops (Too many Erasure frames) and CS Call Drops (No reverse frame received). See A in Figure 4-11.

Check the Abis interface boards of the BTS and the RAC and check other relevant RAC equipment.

CS IS-95 Call Drops (Abis interface abnormal) + CS IS-2000 Call Drops (Abis interface abnormal)

CS Call Drops (A interface abnormal)[Times]

The RAC measures every time a call drop arises from A interface failures after successful call setup of CS services, as indicated by A of Figure 4-11.

Check the A2 interface circuitand A3/A7 interface resources and check other relevant RAC equipment.

CS IS-95 Call Drops (A interface abnormal) + CS IS-2000 Call Drops (A interface abnormal)

CS Call Drops (HHO fail)[Times]

The RAC measures every time a call release arises from a cause that the source RAC waits overtime for an MS Ack Order from the MS after CS service call is set up successfully but the HHO fails, as indicated by Figure 4-11.

Chek the configuration of hard handoff parameters and of the handoff areas.

CS IS-95 Call Drops (HHO fail) + CS IS-2000 Call Drops (HHO fail)

CS Call Drops (Other causes)[Times]

The RAC measures every time a call release arises from some other causes after successful call setup of CS services, as indicated by Figure 4-11.

Check for interior errors and OAM intervention.

CS IS-95 Call Drops (Other causes) + CS IS-2000 Call Drops (Other causes)





CS Call Drop Procedure During CS calls, when the RAC detects call drop information, the original measurement items of the measurement subset CS Call Drop Performance Stat are measured on the basis of the call drop causes. Figure 4-11 shows the CS call drop procedure.

Figure 4-11 CS call drop procedure

MS VCNBS

Assignment Complete

......

......Call setup

Call in progress

A

The BSCdetects call

dropinformation

Call release

A: CS Call Drops (Too many Erasure frames)[Times] CS Call Drops (No reverse frame received)[Times] CS Call Drops (Abis interface abnormal)[Times] CS Call Drops (A interface abnormal)[Times] CS Call Drops (Other causes)[Times]

PS Call Drop Performance Measurement The call drop performance in the PS domain is measured with the compound item PS Call Drop Ratio[%].

Item name: PS Call Drop Ratio[%] Meaning: call drop ratio in the PS domain Item type: RAC performance measurement, RAC/carrier-level PS Call Drop Ratio[%] = (PS Call Drops (To many Erasure frames) + PS Call Drops (No

reverse frame received) + PS call Drops (Abis interface abnormal) + PS call Drops (A1 interface abnormal) + PS Call Drops (PCF failure) + PS Call Drops (HHO failure) + PS Call Drops (Other causes)) / (Successful PS Orig Call Setups + Successful PS Term Call Setups + PS Successful Incoming Hard HOs) x 100%

Analysis: In the RAC performance measurement items, the causes of call drops are put into specific categories. Table 4-4 lists the measurement items about PS Call Drop Ratio.



Table 4-4 Measurement items about PS Call Drop Ratio


PS Call Drops (Too many Erasure frames) [Times]

The RAC measures every time a call drop arises from a cause that the BSS receives too many idle or erasure frames after successful call setup of PS services and diversity combination, as indicated by A of Figure 4-12.

Check the forward and reverse coverage, the forward and reverse link interference, and BTS hardware faults (such as faults in RLDU, CDDU, CDFU, and the power amplification module) and check the configuration of parameters, including power control parametera and handoff parameters.

None

PS Call Drops (No reverse frame received) [Times]

The RAC measures every time a call drop arises from a cause that the BSS fails to receive any reverse frames of a call within a period after the successful call setup of PS services, as indicated by A of Figure 4-12.

Check the Abis link for faults. None

PS Call Drops (Abis interface abnormal) [Times]

The RAC measures every time a call drop arises from Abis interface failures after successful call setup of PS services. This measurement item does not include CS Call Drops (Too many Erasure frames) and CS Call Drops (No reverse frame received). See A in Figure 4-12.

Check the Abis interface boards of the BTS and the RAC and check other relevant equipment.

None

PS Call Drops (A1 interface abnormal) [Times]

The RAC measures every time a call drop arises from A interface failures after successful call setup in the PS, as indicated by A of Figure 4-12.

Check the A1 interface circuitand A3/A7 interface resources and check other relevant RAC equipment.

None

PS Call Drops (PCF failure) [Times]

The RAC measures every time a call is released because of faults in the transmission link between the RAC and the PCF after successful call setup of PS services, as indicated by A of Figure 4-12.

Check the A8 interface resources, the messages about abnormal releases by the PDSN, and other relevant resource faults.

None.

PS Call Drops (HHO fail)[Times]

The RAC measures every time a call release arises from a cause that the source RAC waits overtime for an MS Ack Order from the MS after PS service call is set up successfully but the HHO fails, as indicated by Figure 4-12.

Chek the configuration of hard handoff parameters and of the handoff areas.

None

PS Call Drops (Other causes) [Times]

The RAC measures every time a call release arises from some other causes after successful call setup of PS services, as indicated by A of Figure 4-12.

Check for interior errors and OAM intervention.

None





PS Call Drop Procedure During PS calls, when the RAC detects call drop information, the original measurement items of the measurement subset PS Call Drop Performance Stat are measured on the basis of the call drop causes.

Figure 4-12 shows the PS call drop procedure.

Figure 4-12 PS call drop procedure

PDSNBSMS PCFMSC

Assignment Complete

A

Call setup

Call in progress

Call release

BSC detectscall drop

information

......

......

......

......

A: PS Call Drops (Too many Erasure frames)[Times] PS Call Drops (No reverse frame received)[Times] PS Call Drops (Abis interface abnormal)[Times] PS Call Drops (A1 interface abnormal)[Times] PS Call Drops (PCF failure)[Times] PS Call Drops (HHO fail)[Times] PS Call Drops (Other causes)[Times]

4.1.4 Congestion Ratio The cBSS provides specific performance measurement items for the initial analysis of the congestion ratio. These performance measurement items distinguish CS services from PS services. Different congestion cases that occur in call setup, soft handoffs, and hard handoffs are measured in detail.

TCH Congestion Performance Stat-CS Item name: CS TCH Congestion Ratio[%] Item meaning: congestion in the allocation of TCH resources The TCH Congestion Ratio

is different from call resource allocation in that the TCH Congestion Ratio reflects the allocation of TCH resources when calls are set up.

Item type: AN performance measurement, AN/carrier-level Measurement method: by calculation Formula: CS TCH Congestion Ratio = ((TCH Assignment Requests[Times]–Successful

TCH Assignments[Times])/TCH Assignment Requests[Times]) % 100%



Analysis: The RAC performance measurement items distinguish calling parties from called parties. Also, the causes of call drops are put into specific categories. Table 4-5 lists the measurement items about CS TCH Congestion Ratio.

Table 4-5 Measurement items about CS TCH Congestion Ratio

Item Name Meaning Solution

TCH Assignment Failures (WALSH shortage)-CS Orig/Term/Soft HO/Hard HO [Times]

For failures occurring during the CS Orig/Term process, the RAC measures when it fails to assign TCH resources such as FCHs and DCCHs resulting from Walsh shortage, upon receiving an Assignment Request message from the VCN during CS origination/termination access. See C in Figure 4-13 and C in Figure 4-14.

For the inter-/intra-RAC hard hanoff process, the RAC measures when it fails to assign TCH resources because its request for target cell resources after it receives Handoff Command messages from the VCN fails and Walsh codes are not enough. See C in Figure 4-17 and C in Figure 4-18.

For the inter-/intra-RAC soft hanoff process, the RAC at the target side measures when it fails to assign TCH resources because its request for target cell resources after it receives s from the RAC at the source side fails and Walsh codes are not enough. See C in Figure 4-19 and C in Figure 4-20.

Check the number of accessing subscribers and the ratio of soft handoffs to hard handoffs. If these two values are excessively high, Walsh codes may be not enough.

TCH Assignment Failures (Low forward power)-CS Orig/Term/Soft HO/Hard HO [Times]

For failures occurring during CS Orig/Term process, the RAC measures when it fails to assign TCH resources such as FCHs and DCCHs resulting from low forward power, upon receiving an Assignment Request message from the VCN during CS origination/termination access.

For the inter-/intra-RAC hard hanoff process, the RAC measures when it fails to assign TCH resources because its request for target cell resources after it receives Handoff Command messages from the VCN fails and the forward power is low. See C in Figure 4-17 and C in Figure 4-18.

For the inter-/intra-RAC soft hanoff process, the RAC at the target side measures when it fails to assign TCH resources because its request for target cell resources after it receives s from the RAC at the source side fails and the forward power is low. See C in Figure 4-19 and C in Figure 4-20.

Check power control parameters, forward and reverse load parameters, and carrier coverage parameters






TCH Assignment Failures (Low reverse power)-CS Orig/Term/Soft HO/Hard HO [Times]

For failures occurring during CS Orig/Term process, the RAC measures when it fails to assign TCH resources such as FCHs and DCCHs resulting from low reverse power, upon receiving an Assignment Request message from the VCN during CS origination/termination access. See C in Figure 4-13 and C in Figure 4-14.

For the inter-/intra-RAC hard hanoff process, the RAC measures when it fails to assign TCH resources because its request for target cell resources after it receives Handoff Command messages from the VCN fails and the reverse power is low. See C in Figure 4-17 and C in Figure 4-18.

For the inter-/intra-RAC soft hanoff process, the RAC at the target side measures when it fails to assign TCH resources because its request for target cell resources after it receives s from the RAC at the source side fails and the reverse power is low. See C in Figure 4-19 and C in Figure 4-20.


TCH Assignment Failures (Channel shortage)-CS Orig/Term/Soft HO/Hard HO [Times]

For failures occurring during CS Orig/Term process, the RAC measures when it fails to assign TCH resources such as FCHs and DCCHs resulting from CE resource shortage, upon receiving an Assignment Request message from the VCN during CS origination/termination access. See C in Figure 4-13 and C in Figure 4-14. Number of radio TCH assignment failures resulting from CE shortage in CS hard HOs.

For the inter-/intra-RAC hard hanoff process, the RAC measures when it fails to assign TCH resources because its request for target cell resources after it receives Handoff Command messages from the VCN fails and the CE resources are not enough. See C in Figure 4-17 and C in Figure 4-18.

For the inter-/intra-RAC soft hanoff process, the RAC at the target side measures when it fails to assign TCH resources because its request for target cell resources after it receives s from the RAC at the source side fails and the CE resources are not enough. See C in Figure 4-19 and C in Figure 4-20.

Check the CE resources currently configured for the carrier.




TCH Assignment Failures (Other causes)-CS Orig/Term/Soft HO/Hard HO [Times]

For failures occurring during CS Orig/Term process, the RAC measures when it fails to assign TCH resources such as FCHs and DCCHs resulting from causes other than those described above, upon receiving an Assignment Request message from the VCN during CS origination/termination access. See C in Figure 4-13 and C in Figure 4-14.

For the inter-/intra-RAC hard hanoff process, the RAC measures when its request for target cell resources after it receives Handoff Command messages from the VCN fails and the RAC fails to assign TCH resources for causes other the those described above. See C in Figure 4-17 and C in Figure 4-18.

For the inter-/intra-RAC soft hanoff process, the RAC at the target side measures when it fails to assign TCH resources because its request for target cell resources after it receives A7 Handoff Requests from the RAC at the source side fails and the RAC fails to assign TCH resources for causes other the those described above. See C in Figure 4-19 and C in Figure 4-20.

Check factors related to causes other than those described above, for example, the equipment.





Calling Procedure in the CS Domain Figure 4-13 shows TCH Congestion Performance Stat-CS Orig.

Figure 4-13 TCH Congestion Performance Stat-CS Orig

MS VCNBS

Origination Message

BS Ack Order

Complete L3 Info:CM Service Request

Assignment Request


Tch Preamble

BS Ack Order

MS Ack Order



Assignment Complete

Ringback Tone

TCHassignment

Success:

Failure:

TCH assignment requestA

B

C

A: TCH Assignment Requests-CS Orig[Times] B: Successful TCH Assignments-CS Orig C: TCH Assignment Failures (WALSH shortage)-CS Orig[Times]

TCH Assignment Failures (Low forward power)-CS Orig[Times] TCH Assignment Failures (Low reverse power)-CS Orig[Times] TCH Assignment Failures (Channel shortage)-CS Orig[Times] TCH Assignment Failures (Other causes)-CS Orig



Called Procedure in the CS Domain Figure 4-14 shows TCH Congestion Performance Stat-CS Term.

Figure 4-14 TCH Congestion Performance Stat-CS Term

MS VCNBS

Page message

Complete L3 Info:Paging Response

BS Ack Order


BS Ack Order

MS Ack Order



Assignment Complete

Paging Request


Assignment Request

TCH Preamble

Alert with Info

MS Ack Order

Connet Order

BS Ack Order

Connect

A

TCHassignmentC

BSuccess:

Failure:

TCH assignmet request

A: TCH Assignment Requests-CS Term[Times] B: Successful TCH Assignments-CS Term C: TCH Assignment Failures (WALSH shortage)-CS Term[Times]

TCH Assignment Failures (Low forward power)-CS Term[Times] TCH Assignment Failures (Low reverse power)-CS Term[Times] TCH Assignment Failures (Channel shortage)-CS Term[Times] TCH Assignment Failures (Other causes)-CS Term





TCH Congestion Performance Stat-PS Item name: PS TCH Congestion Ratio[%] Item meaning: congestion in the allocation of TCH resources The TCH Congestion Ratio

is different from call resource allocation in that the TCH Congestion Ratio reflects the allocation of TCH resources when calls are set up.

Item type: RAC performance measurement, RAC/carrier level Measurement method: by calculation Formula: PS TCH Congestion Ratio = ((TCH Assignment Requests[Times]–Successful

TCH Assignments[Times])/TCH Assignment Requests[Times]) % 100% Analysis: The RAC performance measurement items distinguish calling parties from

called parties. Also, the causes of congestion are put into specific categories. Table 4-6 lists the measurement items about PS TCH Congestion Ratio.

Table 4-6 Measurement items about PS TCH Congestion Ratio


TCH Assignment Failures (WALSH shortage)-PS Orig/Term/Soft HO/Hard HO [Times]

For failures occurring during PS Orig/Term process, the RAC measures when it fails to assign TCH resources such as FCHs and DCCHs resulting from Walsh shortage, upon receiving an Assignment Request message from the VCN during PS origination/termination access. See C in Figure 4-15 and C in Figure 4-16.

For the inter-/intra-RAC hard hanoff process, the RAC measures when it fails to assign TCH resources because its request for target cell resources after it receives Handoff Command messages from the VCN fails and Walsh codes are not enough. See C in Figure 4-17 and C in Figure 4-18.

For the inter-/intra-RAC soft hanoff process, the RAC at the target side measures when it fails to assign TCH resources because its request for target cell resources after it receives s from the RAC at the source side fails and Walsh codes are not enough. See C in Figure 4-19 and C in Figure 4-20.

Check the number of accessing subscribers and the ratio of soft handoffs to hard handoffs. If these two values are excessively high, Walsh codes may be not enough.

TCH Assignment Failures (Low forward power)-PS Orig/Term/Soft HO/Hard HO [Times]

For failures occurring during PS Orig/Term process, the RAC measures when it fails to assign TCH resources such as FCHs and DCCHs resulting from low forward power, upon receiving an Assignment Request message from the VCN during PS origination/termination access. See C in Figure 4-15 and C in Figure 4-16.

For the inter-/intra-RAC hard hanoff process, the RAC measures when it fails to assign TCH resources because its request for target cell resources after it receives Handoff Command messages from the VCN fails and the forward power is low. See C in Figure 4-19.

For the inter-/intra-RAC soft hanoff process, the RAC at the target side measures when it fails to assign TCH resources because its request for target cell resources after it receives s from the RAC at the source side fails and the forward power is low. See C in Figure 4-19 and C in Figure 4-20.





TCH Assignment Failures (Low reverse power)-PS Orig/Term/Soft HO/Hard HO [Times]

For failures occurring during PS Orig/Term process, the RAC measures when it fails to assign TCH resources such as FCHs and DCCHs resulting from low reverse power, upon receiving an Assignment Request message from the VCN during PS origination/termination access. See C in Figure 4-15 and C in Figure 4-16.

The total number of failures in CS hard handoffs due to inadequate CE resources. For the inter-/intra-RAC hard hanoff process, the RAC measures when its request for target cell resources after it receives Handoff Command messages from the VCN fails and the reverse power is low. See C in Figure 4-17 and C in Figure 4-18.

For the inter-/intra-RAC soft hanoff process, the RAC at the target side measures when it fails to assign TCH resources because its request for target cell resources after it receives s from the RAC at the source side fails and the reverse power is low. See C in Figure 4-19 and C in Figure 4-20.


TCH Assignment Failures (Channel shortage)-PS Orig/Term/Soft HO/Hard HO [Times]

For failures occurring during PS Orig/Term process, the RAC measures when it fails to assign TCH resources such as FCHs and DCCHs resulting from CE shortage, upon receiving an Assignment Request message from the VCN during PS origination/termination access. See C in Figure 4-15 and C in Figure 4-16.

Number of radio TCH assignment failures resulting from CE shortage in CS hard HOs. For the inter-/intra-RAC hard hanoff process, the RAC measures when it fails to assign TCH resources because its request for target cell resources after it receives Handoff Command messages from the VCN fails and the CE resources are not enough. See C in Figure 4-17 and C in Figure 4-18.

For the inter-/intra-RAC soft hanoff process, the RAC at the target side measures when it fails to assign TCH resources because its request for target cell resources after it receives s from the RAC at the source side fails and the CE resources are not enough. See C in Figure 4-19 and C in Figure 4-20.

Check the CE resources currently configured for the carrier.






TCH Assignment Failures (Other causes)-PS Orig/Term/Soft HO/Hard HO [Times]

For failures occurring during PS Orig/Term process, the RAC measures when it fails to assign TCH resources such as FCHs and DCCHs resulting from causes other than those described above, upon receiving an Assignment Request message from the VCN during PS origination/termination access. See C in Figure 4-15 and C in Figure 4-16.

For the inter-/intra-RAC hard hanoff process, the RAC measures when its request for target cell resources after it receives Handoff Command messages from the VCN fails and the RAC fails to assign TCH resources for causes other the those described above. See C in Figure 4-17 and C in Figure 4-18.

For the inter-/intra-RAC soft hanoff process, the RAC at the target side measures when its request for target cell resources after it receives A7 Handoff Requests from the RAC at the source side fails and the RAC fails to assign TCH resources for causes other the those described above. See C in Figure 4-19 and C in Figure 4-20.

Check factors related to causes other than those described above, for example, the equipment.



Calling Procedure in the PS Domain Figure 4-15 shows TCH Congestion Performance Stat-PS Orig.

Figure 4-15 TCH Congestion Performance Stat-PS Orig

PDSNBSMS PCF

A11 Registration Request(Life time)

VCN

Origination

BS ACK Order

CM Service Request

Assignment Request

Assignment Complete



A11-Registration Reply (Life time, Accept)

ECAM

BSAck Order

MS Ack Order

Service Connect Msg

Service Connect Cmp Msg

Tch Preamble

A9-Setup-A8

A9-Connect-A8

TCHassignment

Success:

Failure:

TCHassignment

requestA

B

C

A: TCH Assignment Requests-PS Orig[Times] B: Successful TCH Assignments-PS Orig[Times] C: TCH Assignment Failures (WALSH shortage)-PS Orig[Times]

TCH Assignment Failures (Low forward power)-PS Orig[Times] TCH Assignment Failures (Low reverse power)-PS Orig[Times] TCH Assignment Failures (Channel shortage)-PS Orig[Times] TCH Assignment Failures (Other causes)-PS Orig





Called Procedure in the PS Domain Figure 4-16 shows TCH Congestion Performance Stat-PS Term.

Figure 4-16 TCH Congestion Performance Stat-PS Term

Assignment Complete



Assignment Request

A9-Setup-A8

A9-Connect-A8

BS Ack Order

IS-2000 TchSetup


Packet Data Traffic


BS Service Request

BS Service Response


Paging Request



MS BS VCN PCF PDSN

TCHassignment

Success:

Failure:

TCHassignment

requestA

B

C

A: TCH Assignment Requests-PS Term[Times] B: Successful TCH Assignments-PS Term C: TCH Assignment Failures (WALSH shortage)-PS Term[Times]

TCH Assignment Failures (Low forward power)-PS Term[Times] TCH Assignment Failures (Low reverse power)-PS Term[Times] TCH Assignment Failures (Channel shortage)-PS Term[Times] TCH Assignment Failures (Other causes)-PS Term



Inter-RAC Hard Handoff Procedure Figure 4-17 shows TCH Congestion Performance Stat --Inter-RAC Hard HO.

Figure 4-17 TCH Congestion Performance Stat--Inter-RAC Hard HO

MS

Handoff Required

Handoff Request

Handoff Request Ack

Handoff Command

Handoff Complete

Clear Command

Clear Complete

MS Ack Order

Handoff Commenced

Reverse Traffic Channel Frames or Traffic Channel Preamble

Handoff Completion Message

BS Ack Order

Handoff Direction Message

TargetBS

SourceBS

TCHassignment

Success:

Failure:

TCHassignment

requestA

B

C

TargetVCN

Handoff Request

SourceVCN

Handoff Request Ack

Clear Command

A: TCH Assignment Requests-CS Hard HO[Times] TCH Assignment Requests-PS Hard HO[Times]

B: Successful TCH Assignments-CS Hard HO[Times] Successful TCH Assignments-PS Hard HO[Times]

C: TCH Assignment Failures (WALSH shortage)-CS Hard HO[Times] TCH Assignment Failures (Low forward power)-CS Hard HO[Times]





TCH Assignment Failures (Low reverse power)-CS Hard HO[Times] TCH Assignment Failures (Channel shortage)-CS Hard HO[Times] TCH Assignment Failures (Other causes)-CS Hard HO[Times] TCH Assignment Failures (WALSH shortage)-PS Hard HO[Times] TCH Assignment Failures (Low forward power)-PS Hard HO[Times] TCH Assignment Failures (Low reverse power)-PS Hard HO[Times] TCH Assignment Failures (Channel shortage)-PS Hard HO[Times] TCH Assignment Failures (Other causes)-PS Hard HO[Times]

Intra-RAC Hard Handoff Procedure Figure 4-18 shows TCH Congestion Performance Stat (Intra-RAC HHO).

Figure 4-18 TCH Congestion Performance Stat-Intra-RAC HHO

Handoff Complete

MS Ack Order



BS Ack Order


Null forward traffic channel frames

BS VCNMS

Hard handofftriggered

TCHassignment

Success:

Failure:

TCHassignment

requestA

B

C

A: TCH Assignment Requests-CS Hard HO[Times] B: Successful TCH Assignments-CS Hard HO[Times] C: TCH Assignment Failures (WALSH shortage)-CS Hard HO[Times]

TCH Assignment Failures (Low forward power)-CS Hard HO[Times] TCH Assignment Failures (Low reverse power)-CS Hard HO[Times] TCH Assignment Failures (Channel shortage)-CS Hard HO[Times] TCH Assignment Failures (Other causes)-CS Hard HO[Times] TCH Assignment Failures (WALSH shortage)-PS Hard HO[Times] TCH Assignment Failures (Low forward power)-PS Hard HO[Times] TCH Assignment Failures (Low reverse power)-PS Hard HO[Times] TCH Assignment Failures (Channel shortage)-PS Hard HO[Times] TCH Assignment Failures (Other causes)-PS Hard HO[Times]



Inter-RAC Soft Handoff Procedure Figure 4-19 shows TCH Congestion Performance Stat (Inter-RAC SHO).

Figure 4-19 TCH Congestion Performance Stat--Inter-RAC SHO

A3-CEData Forward (Forward Frames)

A7- Handoff Request

A3-Connect

A3-Connect Ack

A7- Handoff Request Ack

A3-Traffic Channel Status

Extended Handoff direction message

Handoff Performed

MS Ack Order


BS Ack Order

Forward Frames

A3-CEData Reverse (Idle Frames)

SourceBS

MS VCN TargetBS

TCHassignment C

Success:

Failure:

A

B

TCHassignment

request

A: TCH Assignment Requests-CS Soft HO[Times] B: Successful TCH Assignments-CS Soft HO[Times] C: TCH Assignment Failures (WALSH shortage)-CS Soft HO[Times]

TCH Assignment Failures (Low forward power)-CS Soft HO[Times] TCH Assignment Failures (Low reverse power)-CS Soft HO[Times] TCH Assignment Failures (Channel shortage)-CS Soft HO[Times] TCH Assignment Failures (Other causes)-CS Soft HO[Times]





Intra-RAC Soft Handoff Procedure Figure 4-20 shows TCH Congestion Performance Stat (Intra-RAC Soft HO).

Figure 4-20 TCH Congestion Performance Stat-Intra-RAC Soft HO

Handoff Performed

MS Ack Order



BS Ack Order



BS VCNMS

Soft handofftriggered

TCHassignment

In case of success:

In case of failure:

TCHassignment

requestA

B

C

A: TCH Assignment Requests-CS Soft HO[Times] B: Successful TCH Assignments-CS Soft HO[Times] C: TCH Assignment Failures (WALSH shortage)-CS Soft HO[Times]

TCH Assignment Failures (Low forward power)-CS Soft HO[Times] TCH Assignment Failures (Low reverse power)-CS Soft HO[Times] TCH Assignment Failures (Channel shortage)-CS Soft HO[Times] TCH Assignment Failures (Other causes)-CS Soft HO[Times]

4.1.5 Performance Stat of Packet Call Activation

MS/AT Reactivation Success Ratio[%] Item name: MS/AT Reactivation Success Ratio[%] Item name: success ratio of reactivation attempts originated by the MS/AT side Item type: RAC performance measurement, RAC/carrier level Measurement method: by calculation Formula: MS/AT Reactivation Success Ratio[%] = (Successful MS/AT

Reactivations[Times]/MS/AT Reactivate Attempts[Times]) % 100% Item analysis:

Meanings of calculated items:



− Successful MS/AT Reactivations[Times]: Times of successful call activation originated by the MS/AT in the dormant state. After the MS/AT in the dormant state originates an activation request, the PCF processes the A9-Setup-A8 message sent by the BS/AN. The RAC measures every time the PCF returns an A9-Connect-A8 message to the BS/AN after successfully processing the A9-Setup-A8 message, as indicated by B of Figure 4-21.

− MS/AT Reactivate Attempts[Times]: Number of call activation requests originated by the MS/AT in the dormant state. The RAC measures every time the PCF receives an A9-Setup-A8 message from a BS/AN after the MS/AT in the dormant state originates an activation request, as indicated by A of Figure 4-21.

PCF Reactivation Success Ratio[%] Item name: PCF Reactivation Success Ratio[%] Item name: success ratio of reactivation attempts originated by the PCF side Item type: RAC performance measurement, RAC/carrier level Measurement method: by calculation Formula: PCF Reactivation Success Ratio[%] = (Successful PCF

Reactivations[Times]/PCF Reactivate Attempts[Times]) % 100% Item analysis:

Meanings of calculated items: − Successful PCF Reactivations[Times]: Times of successful call activation originated

by the PCF when the MS/AT is in the dormant state. After receiving data from the network side when the MS/AT is in the dormant state, the PCF sends the BS/AN an A9-BS-Service-Request message. The RAC measures every time the PCF returns an A9-Connect-A8 message to the BS/AN after processing the A9-Setup-A8 message from the BS/AN, as indicated by B of Figure 4-22.

− PCF Reactivate Attempts[Times]: number of call activation requests originated by the PCF when the MS/AT is in the dormant state. The RAC measures every time the PCF sends the BS/AN an A9-BS-Service-Request upon receiving data from the network side with the MS/AT in the dormant state, as indicated by A of Figure 4-22.

Access Success Ratio of Packet Service Subscribers[%] Item name: Access Success Ratio of Packet Service Subscribers[%] Item meaning: the success ratio of accesses by PS subscribers Item type: RAC performance measurement, RAC/carrier level Measurement method: by calculation Formula : Access Success Ratio of Packet Service Subscribers[%] = (Successful

Accesses of Packet Service Subscribers[Times]/Access Requests by Packet Service Subscribers[Times]) % 100%

Item analysis: Meanings of calculated items: − Successful Accesses of Packet Service Subscribers[Times]: Number of successful call

setups at the setup requests for data service calls that the PCF receives when the MS/AT is in the null state. The RAC measures every time the PCF returns an A9-Connect-A8 message to the BS/AN after it receives an A9-Setup-A8 message from the BS/AN and the call is successfully set up with the MS/AT in the null state, as indicated by B of Figure 4-23.





− Access Requests by Packet Service Subscribers[Times]: Number of setup requests for data service calls that the PCF receives when the MS/AT is in the null state. The RAC measures every time the PCF receives an A9-Setup-A8 message from the BS/AN with the MS/AT in the null state, as indicated by A of Figure 4-23.

In both the CDMA2000 1X and CDMA2000 1xEV-DO networks, the BS/AN is connected to the PCF through the A8/A9 interface. Therefore, the A8/A9 interface conceals from the PCF the differences between the CDMA2000 1X network and the CDMA2000 1xEV-DO network. The performance measurement items do not distinguish the CDMA2000 1X network from the the CDMA2000 1xEV-DO network.

Activation Procedure Originated by the MS/AT Figure 4-21 shows Performance Stat of Packet Call Activation-MS/AT Originated Activation (the data exchanges between the MS and the BS, between the BS and the VCN, and between the AT and the AN are omitted).

Figure 4-21 Performance Stat of Packet Call Activation-MS/AT Originated Activation

PDSN

A9-Setup-A8

MS/AT

A9-Connect-A8

PCF



A…

… B

BS/AN

A: MS/AT Reactivate Attempts[Times] B: Successful MS/AT Reactivations[Times]



Activation Procedure Originated by the Network Side Figure 4-22 shows Performance Stat of Packet Call Activation-Network Originated Activation.

Figure 4-22 Performance Stat of Packet Call Activation-Network Originated Activation

PDSN

A9-Setup-A8

MS/AT

A9-Connect-A8

BS/AN PCF



Packet Data Traffic



A

B…

…

A: PCF Reactivate Attempts[Times] B: Successful PCF Reactivations[Times]





Calling Procedure Originated by the MS/AT Figure 4-23 shows Performance Stat of Packet Call Activation-MS/AT Originated Call (the data exchanges between the MS and the BS, between the BS and the VCN, and between the AT and the AN are omitted).

Figure 4-23 Performance Stat of Packet Call Activation-MS/AT Originated Call

PDSN

A9-Setup-A8

MS/AT

A11-Registration-Request (Life Time)

A11-Registration-Reply (Life Time, Accept)

A9-Connect-A8

PCFBS/AN



……

A

B

A9-Disconnect-A8 C

Success

Failure

Access Requests by Packet Service Subscribers[Times] B: Successful Accesses of Packet Service Subscribers[Times] C: Times of Congestion on PCF[Times]



4.1.6 Short Message Success Ratio

Measurement Items About Short Message Success Ratio Short Message Success Ratio is measured on the basis of several measurement items, as listed in Table 4-7.

Table 4-7 Measurement items about Short Message Success Ratio

Item Name Type Meaning Measurement Point

MT/PP Short Messages on PCHs[Times]

Original Number of short messages that are sent to the MS on the common channel and are received by the RAC from the VCN.

The RAC measures when the module receives the ADDS Page messages from the VCN and the module determines that the messages are not broadcast messages. See A of Figure 4-24.

Broadcast Short Messages[Times]

Original Number of broadcast short messages that the RAC receives from the VCN.

The RAC measures every time it receives an ADDS Page message from the VCN and determines the message is a broadcast short message. See A of Figure 4-25.

MO/PP Short Messages on ACHs[Times]

Original Number of short messages that are sent from the MS to the VCN and are received by the RAC on the common channel.

The RAC measures when the module sends an ADDS Transfer message to the VCN. This item measures all the messages carried on the ADDS Transfer message, including Short Message, Position Location Data, Short Data Burst, and Over the Air Service Provisioning. See A of Figure 4-26.

TCH Downlink Short Messages[Times]

Original Number of short messages that the RAC receives from the VCN. The short messages are directed to the MS on traffic channels (TCHs).

The RAC measures when the RAC receives an ADDS Deliver message from the VCN. This item measures all the messages carried on the ADDS Deliver message, including Short Message, Position Location Data, Short Data Burst, and Over the Air Service Provisioning. See A of Figure 4-27.

TCH Uplink Short Messages[Times]

Original Number of short messages that are sent from the MS to the VCN and are received by the RAC on the traffic channel.

The RAC measures when the RAC sends an ADDS Deliver message to the VCN. This item measures all the messages carried on the ADDS Deliver message, including Short Message, Position Location Data, Short Data Burst, and Over the Air Service Provisioning. See A of Figure 4-28.





Procedure for MT/PP Short Messages on PCHs[Times] Figure 4-24 shows MT/PP Short Messages on PCHs[Times].

Figure 4-24 MT/PP Short Messages on PCHs[Times]

ADDS Page

ADDS Page Ack

Data Burst Message(Paging Channel)

A

MS BS MSC

Procedure for Broadcast Short Messages[Times] Figure 4-25 shows Broadcast Short Messages[Times].

Figure 4-25 Broadcast Short Messages[Times]

Data Burst Message(Traffic Channel)

Layer 2 Ack

ADDS Delivery

ADDS Delivery Ack

A

MS BS VCN



Procedure for MO/PP Short Messages on ACHs[Times] Figure 4-26 shows MO/PP Short Messages on ACHs[Times].

Figure 4-26 MO/PP Short Messages on ACHs[Times]


Layer 2 Ack

ADDS Delivery

ADDS Delivery Ack

A

MS BS VCN

Procedure for TCH Downlink Short Messages[Times] Figure 4-27 shows TCH Downlink Short Messages[Times].

Figure 4-27 TCH Downlink Short Messages[Times]


Layer 2 Ack

ADDS Delivery

ADDS Delivery Ack

A

MS BS VCN





Procedure for TCH Uplink Short Messages[Times] Figure 4-28 shows TCH Uplink Short Messages[Times].

Figure 4-28 TCH Uplink Short Messages[Times]


ADDS Transfer

Layer 2 Ack

A

MS BS VCN

4.1.7 Soft HO Success Ratio The cBSS provides specific performance measurement items for the initial analysis of the soft handoff success ratio. The intra-RAC soft handoff success ratio and the inter-RAC soft handoff success handoff ratio are measured separately. Also, the causes of soft handoff failures are measured in detail.

Inter-RAC Soft HO Performance Stat The inter-RAC soft handoff performance is measured with three compound items, namely, Inter-BS Soft HO Success Ratio[%], Inter-BS Soft HO Requests[Times], and Successful Inter-BS Soft Hos[Times].

Inter-BS Soft HO Success Ratio Item name: Inter-BS Soft HO Success Ratio[%] Item meaning: success ratio of inter-BS soft HOs for adding legs and deleting legs Item type: RAC performance measurement, RAC/carrier-level Inter-BS Soft HO Success Ratio[%] = (Successful Inter-BS Soft Hos-Add Leg[Times] +

Successful Inter-BS Soft Hos-Del Leg[Times]) / (Inter-BS Soft HO Requests-Add Leg[Times] + Inter-BS Soft HO Requests-Del Leg[Times]) x 100%

Analysis: The RAC performance measurement items measure the factors about Inter-RAC Soft HO Success Ratio in detail. Table 4-8 lists the measurement items about Inter-BS Soft HO Success Ratio.



Table 4-8 Measurement items about Inter-BS Soft HO Success Ratio


Inter-BS Soft HO Failures (Radio resources unavailable)[Times]

The RAC measures when the following conditions are satisfied:

The source BS sends an A7-Handoff Request message to the target RAC.

The CCM in the target BS requests for resources but fails.

The returned cause value is radio resources unavailable, as indicated by B of Figure 4-29 Inter-RAC Soft HO Performance Stat.

Check the radio resource configuration and the usage of Walsh codes and CE pool in the target cell.

Inter-BS Soft HO Failures (Requested terrestrial resources unavailable)[Times]


The source BS sends an A7-Handoff Request message to the target RAC.

The CCM in the target BS requests for resources but fails.

The returned cause value is requested terrestrial resources unavailable, as indicated by B of Figure 4-29 Inter-RAC Soft HO Performance Stat.

Check the Abis resource configuration and system equipment at the target side.

Inter-BS Soft HO Failures (Radio interface abnormal)[Times]

The RAC measures when it sends an Extended Handoff Direction Message to the MS upon successful resources acquisition and waiting for MS Ack Order messages times out, as indicated by D of Figure 4-29.

Check the usage of the radio interface and of Walsh codes and CE pools.

Inter-BS Soft HO Failures (MS rejected)[Times]

The RAC measures when it sends an Extended Handoff Direction Message to the MS upon successful resources acquisition and the MS returns an MS Reject Order message, as indicated by C of Figure 4-29.

Check the quality of the forward and reverse links.

Inter-BS Soft HO Failures (A3 link setup failed)[Times]

The RAC measures when an inter-BS soft HO fails owing to failures to request A3 resources, as indicated by B of Figure 4-29.

Check the A3/A7 interface link.

Inter-BS Soft HO Failures (Other causes)[Times]

The RAC measures when an inter-BS HO fails resulting from the causes such as:

Insufficient DSP resources on the FMR Insufficient DSP resources on the EVC

Check factors related to causes other than those described above, for example, the system equipment and MS parameter configuration.





Inter-BS Soft HO Requests Item name: Inter-BS Soft HO Requests[Times] Item meaning: Number of inter-BS soft HO requests for adding legs and deleting legs Formula: Inter-BS Soft HO Requests[Times] = Inter-BS Soft HO Requests-Add Leg +

Inter-BS Soft HO Requests-Del Leg Item analysis:

Meanings of calculated items: − Inter-BS Soft HO Requests-Add Leg[Times]: The RAC measures when it receives a

PSMM message and the source RRM module determines to trigger inter-BS soft HOs for adding legs. See A of Figure 4-29.

− Inter-BS Soft HO Requests-Del Leg[Times]: The RAC measures when it receives a PSMM message and the source RRM module determines to trigger inter-BS soft HOs for deleting legs. See A of Figure 4-29.

Successful Inter-BS Soft Hos Item name: Successful Inter-BS Soft Hos[Times] Item meaning: Number of successful inter-BS soft HOs for adding legs and deleting legs Formula: Successful Inter-BS Soft Hos[Times] = Successful Inter-BS Soft Hos-Add

Leg[Times] + Successful Inter-BS Soft Hos-Del Leg[Times] Item analysis:

Meanings of calculated items: − Successful Inter-BS Soft HOs -Add Leg[Times]: The RAC measures when it receives

a Handoff Completion Message, as indicated by E of Figure 4-29. − Successful Inter-BS Soft HOs -Del Leg[Times]: The RAC measures when it receives

a Handoff Completion Message, as indicated by E of Figure 4-29.



Inter-RAC Soft Handoff Procedure Figure 4-29 shows Inter-RAC Soft HO Performance Stat.

Figure 4-29 Inter-RAC Soft HO Performance Stat

A3-CEData Forward (Forward Frames)

SourceBS

TargetBS

A7- Handoff Request

A3-Connect

A3-Connect Ack

A7- Handoff Request Ack

A3-Traffic Channel Status

Extended Handoff direction message

Handoff Performed

MS Ack Order


BS Ack Order

Forward Frames

A3-CEData Reverse (Idle Frames)

MS VCN

ASoft handofftriggered

Apply fortarget BSresourcesB

MS Reject OrderMS rejects

MS accepts

CTimeout occurs when the

BSC waits for the MSAck Order message D

E

Success

Failure

A: Inter-BS Soft HO Requests-Add Leg[Times] Inter-BS Soft HO Requests-Del Leg[Times]

B: Inter-BS Soft HO Failures (Radio resources unavailable)[Times] Inter-BS Soft HO Failures (Requested Abis resources unavailable)[Times] Inter-BS Soft HO Failures (Radio interface abnormal)[Times] Inter-BS Soft HO Failures (A3 link setup failed)[Times]

C: Inter-BS Soft HO Failures (MS rejected)[Times] D: Inter-BS Soft HO Failures (Radio interface abnormal)[Times] E: Successful Inter-BS Soft HOs-Add Leg[Times]

Successful Inter-BS Soft HOs-Del Leg[Times]





Intra-RAC Soft HO Performance Stat Intra-RAC Soft HO Performance State reflects intra-RAC soft handoff (HO) performance from different perspectives by measuring soft HO requests, soft HO failure causes, successful soft HOs, and so on. The following describes associated measurement items briefly:

Intra-BS Soft HO Requests-Add Leg and Intra-BS Soft HO Requests-Del Leg: The RAC measures when it receives a PSMM message from the MS, and the radio resource management (RRM) module decides to trigger soft HOs for adding or deleting legs.

Intra-BS Soft HO Failures (Radio resources unavailable) and Intra-BS Soft HO Failures (Requested Abis resources unavailable): The RAC measures when soft HOs fail resulting from a cause that the call control module (CCM) fails to allocate resources such as radio resources, A interface resources, and Abis resources.

Intra-BS Soft HO Failures (MS rejected) and Intra-BS Soft HO Failures (Radio interface abnormal): The RAC sends Extended Handoff Direction Messages to direct the MS to perform handoffs upon successful resources allocation. − If the MS accepts to hand off, it returns an MS Ack Order message. − If the MS rejects to hand off, it returns an MS Reject Order message. In this case, the

RAC records one intra-BS soft HO failure (MS rejected). − If the RAC receives no messages from the MS, it regards it as radio interface

abnormality. In this case, the RAC records one Intra-BS Soft HO Failures (Radio interface abnormal).

Successful Intra-BS Soft Hos-Add Leg and Successful Intra-BS Soft Hos-Del Leg: The RAC measures when it receives a Handoff Completion Message from the MS after the handoff for adding legs or deleting legs ends.

Intra-BS Soft HO Failures (Other causes): The RAC measures when an intra-BS soft HO fails resulting from the cause other than the following: − Intra-BS Soft HO Failures (Radio resources unavailable) − Intra-BS Soft HO Failures (Requested Abis resources unavailable) − Intra-BS Soft HO Failures (Radio interface abnormal) − Intra-BS Soft HO Failures (MS rejected)

Intra-BS Soft HO Success Ratio, Intra-BS Soft HO Requests, and Successful Intra-BS Soft Hos are calculated based on associated original items.

Intra-BS Soft HO Success Ratio Item name: Intra-BS Soft HO Success Ratio [%] Item meaning: success ratio of intra-BS soft HOs for adding legs and deleting legs Item type: RAC performance measurement, RAC/carrier-level Intra-BS Soft HO Success Ratio[%] = (Successful Intra-BS Soft Hos-Add Leg +

Successful Intra-BS Soft Hos-Del Leg) / (Intra-BS Soft HO Requests-Add Leg + Intra-BS Soft HO Requests-Del Leg) x 100%



Analysis: The RAC performance measurement items measure the factors about Intra-RAC Soft HO Success Ratio in detail. Table 4-9 lists the measurement items about Intra-RAC Soft HO Success Ratio.

Table 4-9 Measurement items about Intra-RAC Soft HO Success Ratio


Intra-BS Soft HO Failures (Radio resources unavailable)[Times]

The RAC fails to request soft HO resources such as radio resources and Abis resources owing to radio resources unavailable in the target cell. As a result, the associated soft handoff fails, as indicated by B of Figure 4-30. At this point, the RAC records one intra-BS soft HO failure (Radio resources unavailable). In this case, the RAC does not send an Extended Handoff Direction Message.


Intra-BS Soft HO Failures (Requested Abis resources unavailable)[Times]

The RAC fails to request soft HO resources such as radio resources and Abis resources owing to Abis resources unavailable in the target cell. As a result, the associated soft handoff fails, as indicated by B of Figure 4-30. At this point, the RAC records one intra-BS soft HO failure (Requested Abis resources unavailable). In this case, the RAC does not send an Extended Handoff Direction Message.


Intra-BS Soft HO Failures (Radio interface abnormal)[Times]

The RAC sends an Extended Handoff Direction Message to the MS upon a successful request for soft HO resources. The associated timer expires owing to radio interface abnormal when the RAC waits for an MS Ack Order message, as indicated by D of Figure 4-30. At this point, the RAC records one intra-BS soft HO failure (Radio interface abnormal).


Intra-BS Soft HO Failures (MS rejected)[Times]

The RAC receives the PSMN message, and the RRM module triggers soft HO and requests resources such as radio resources, Abis resources, and A interface resources. The RAC sends an Extended Handoff Direction Message to the MS upon a successful resources request. The MS returns an MS Reject Order message instead of an MS Ack Order message, as indicated by C of Figure 4-30. At this point, the RAC records one intra-BS soft HO failure (MS rejected).


Intra-BS Soft HO Failures (A3 link setup failed)[Times]

The RAC measures when an inter-BS soft HO fails owing to failures to request A3 resources, as indicated by B of Figure 4-30.

Check the A3/A7 interface link.






Intra-BS Soft HO Failures (Other causes)[Times]

The RAC measures when an intra-BS soft HO fails resulting from the causes such as insufficient BTS CE resources and insufficient DSP resources on the FMR.


Intra-BS Soft HO Requests Item name: Intra-BS Soft HO Requests[Times] Item meaning: Number of intra-BS soft HO requests for adding legs and deleting legs Formula: Intra-BS Soft HO Requests[Times] = Intra-BS Soft HO Requests-Add Leg +

Intra-BS Soft HO Requests-Del Leg Item analysis:

Meanings of calculated items: − Intra-BS Soft HO Requests-Add Leg[Times]: The RAC measures when it receives a

PSMM message from the MS, and the RRM module triggers soft HOs. See A of Figure 4-30.

− Intra-BS Soft HO Requests-Del Leg[Times]: The RAC measures when it receives a PSMM message from the MS, and the RRM module triggers soft HOs. See A of Figure 4-30.

Successful Intra-BS Soft Hos Item name: Successful Intra-BS Soft Hos[Times] Item meaning: number of successful intra-BS soft HOs for adding legs and deleting legs Formula: Successful Intra-BS Soft Hos[Times] = Successful Intra-BS Soft Hos-Add

Leg[Times] + Successful Intra-BS Soft Hos-Del Leg[Times] Item analysis:

Meanings of calculated items: − Successful Intra-BS Soft HOs -Add Leg[Times]: The RAC measures when it receives

a Handoff Completion Message, as indicated by E of Figure 4-30. − Successful Intra-BS Soft HOs -Del Leg[Times]: The RAC measures when it receives

a Handoff Completion Message, as indicated by E of Figure 4-30.



Intra-RAC Soft Handoff Procedure Figure 4-30 shows Intra-RAC Soft HO Performance Stat.

Figure 4-30 Intra-RAC Soft HO Performance Stat

A

Handoff Performed

MS Ack Order



BS Ack Order

Extended Handoff Direction Message


BS VCNMS

E

MS Reject Order

Apply forresources

B

D

C


Success

Failure

MS rejects

MS accepts

Timeout occurs when theBSC waits for the MSAck Order message

A: Intra-BS Soft HO Requests-Add Leg[Times] Intra-BS Soft HO Requests-Del Leg[Times]

B: Intra-BS Soft HO Failures (Radio resources unavailable)[Times] Intra-BS Soft HO Failures (Requested Abis resources unavailable)[Times] Intra-BS Soft HO Failures (Radio interface abnormal)[Times]

C: Intra-BS Soft HO Failures (MS rejected)[Times] D: Intra-BS Soft HO Failures (Radio interface abnormal)[Times] E: Successful Intra-BS Soft HOs-Add Leg[Times]

Successful Intra-BS Soft HOs-Del Leg[Times]





4.1.8 Hard HO Success Ratio The cBSS provides specific performance measurement items for the initial analysis of the hard handoff success ratio. The hard handoff performance is measured in different situations, such as inter-RAC incoming/outgoing hard hanoffs. The causes of hard handoff failures are measured in detail.

Also, the times of each hard handoff algorithm are counted. Such data can be be used to find out the algorithm that leads to hard handoff failures.

Performance Stat of Inter-RAC Outgoing Hard HO the inter-RAC outgoing hard handoff performance is measured with the compound item Inter-BS Outgoing Hard HO Success Ratio[%].

Item name: Inter-BS Outgoing Hard HO Success Ratio[%] Item meaning: success ratio of inter-BS outgoing hard HOs Item type: RAC performance measurement, RAC/carrier-level Formula: Inter-BS Outgoing Hard HO Success Ratio[%] = Successful Inter-BS Outgoing

Hard HOs / Inter-BS Outgoing Hard HO Requests x 100% Analysis: The RAC performance measurement items measure the factors that lead to

inter-RAC outgoing hard handoff failures. Table 4-10 lists the measurement items about Inter-BS Outgoing Hard HO Success Ratio.

Table 4-10 Measurement items about Inter-BS Outgoing Hard HO Success Ratio


Inter-BS Outgoing Hard HO Failures (Radio resources unavailable)[Times]

The source RRM module triggers hard HOs, and then the target CCM starts to request for resources in the sequence of A interface resources, radio resources, and Abis resources. The RAC measures when a hard HO fails resulting from radio resources unavailable, as indicated by B of Figure 4-31.


Inter-BS Outgoing Hard HO Failures (Requested terrestrial resources unavailable)[Times]

The source RRM module triggers hard HOs, and then the target CCM starts to request for resources in the sequence of A interface resources, radio resources, and Abis resources. The RAC measures when a hard HO fails resulting from requested terrestrial resources unavailable, as indicated by B of Figure 4-31.

Check the A interface configuration, Abis link configuration and system equipment.

Inter-BS Outgoing Hard HO Failures (MS rejected)[Times]

The RAC measures when the source BS sends an Extended Handoff Direction Message to the MS, and the MS rejects to hand off by returning a MS Reject Order message, as indicated by C of Figure 4-31.

Check the quality of the forward and reverse links and the configuration of power control parameters.




Inter-BS Outgoing Hard HO Failures (MS Not detected by destination pilot)[Times]


The target BS fails to detect the MS, that is, the target BS waiting for preambles times out.

The target BS returns a Handoff Failure message to the source BS through the VCN.

The source BS sends probes and detects that the MS does not stay in the domain of the source BS, as indicated by D of Figure 4-31.


Inter-BS Outgoing Hard HO Failures (Other causes)[Times]

The RAC measures when an outgoing hard HO fails resulting from the causes such as:

AAL2 disconnection Insufficient DSP resources on the FMR Insufficient DSP resources on the EVC


Inter-RAC Outgoing Hard Handoff Procedure Figure 4-31 shows Performance Stat of Inter-RAC Outgoing Hard HO.





Figure 4-31 Performance Stat of Inter-RAC Outgoing Hard HO

MS VCN

Handoff Required

Handoff Request

Handoff Request Ack

Handoff Command

Handoff Complete Clear Command

Clear Complete

Handoff Commenced



BS Ack Order



TargetBS

SourceBS

A

B

MS Ack Order

MS Reject Order C

Handoff Fail

Handoff Reject

Timeout occurs when the TargetRAC wait for thePreamble

Target RAC detects thePreamble ：

D

E


Apply fortarget RACresources

Success

Failure

MS rejects

MS accepts

A: Inter-BS Outgoing Hard HO Requests[Times] B: Inter-BS Outgoing Hard HO Failures (Radio resources unavailable)[Times]

Inter-BS Outgoing Hard HO Failures (Requested terrestrial resources unavailable)[Times] C: Inter-BS Outgoing Hard HO Failures (MS rejected)[Times] D: Inter-BS Outgoing Hard HO Failures (Returned to original channel)[Times]

Inter-BS Outgoing Hard HO Failures (MS Not detected by destination pilot)[Times] E: Successful Inter-BS Outgoing Hard HOs[Times]



Performance Stat of Inter-RAC Incoming Hard HO The inter-RAC incoming hard handoff performance is measured with the compound item Inter-BS Incoming Hard HO Success Ratio[%].

Item name: Inter-BS Incoming Hard HO Success Ratio[%] Item meaning: success ratio of inter-BS incoming hard HOs Item type: RAC performance measurement, RAC/carrier-level Formula: Inter-BS Incoming Hard HO Success Ratio[%] = Successful Inter-BS

Incoming Hard HOs / Inter-BS Incoming Hard HO Requests x 100% Analysis: The RAC performance measurement items measure the factors that lead to

inter-RAC incoming hard handoff failures. Table 4-11 lists the measurement items about Inter-BS Incoming Hard HO Success Ratio.

Table 4-11 Measurement items about Inter-RAC Incoming Hard HO Success Ratio


Inter-BS Incoming Hard HOs Failures (Resource Allocation Failed)[Times]

The RAC measures when the target BS sends a Handoff Failure message to the VCN upon receiving a Handoff Request message. See B of Figure 4-32. The target BS allocates terrestrial circuit resources and radio resources for this handoff after receiving a Handoff Request message.

If resource allocation succeeds, the target BS sends a Handoff Request Ack message.

If resource allocation fails, the target BS sends a Handoff Failure message. This item measures the number of resource allocation failures.

Check the radio resource configuration, the usage of Walsh codes and CE pool, the A interface resource configuration, and the Abis link configuration in the target cell.

Inter-BS Incoming Hard HOs Failures (HO Execution Failed)[Times]

The target BS sends a Handoff Request Ack message to the VCN upon receiving a Handoff Request message. The RAC measures when the target BS sends a Handoff Failure message to the VCN in case of handoff failure, as indicated by C of Figure 4-32. The RAC measures this item when the associated timer expires as the target BS waits for a Handoff Complete message from the MS or an A9-AL Connected Ack message.

Check the timer parameter configuration and the quality of the forward and reverse links.






Inter-BS Incoming Hard HOs Failures (HO Interrupted by VCN)[Times]

The target BS sends a Handoff Request Ack message to the VCN upon receiving a Handoff Request message. The RAC measures when the target BS sends a Handoff Failure message to the VCN in case of handoff failure, as indicated by C of Figure 4-32. The RAC measures this item when the associated timer expires as the target BS waits for a Handoff Complete message from the MS or an A9-AL Connected Ack message.

Check the timer parameter configuration, the quality of the forward and reverse links, and the VCN resource configuration.

Inter-RAC Incoming Hard Handoff Procedure Figure 4-32 shows Performance Stat of Inter-RAC Incoming Hard HO.



Figure 4-32 Performance Stat of Inter-RAC Incoming Hard HO

MS VCN

Handoff Required

Handoff Request

Handoff Command

Handoff Complete Clear Command

Clear Complete

Handoff Commenced



BS Ack Order



TargetBS

SourceBS

MS Ack Order

D

A

Handoff Request Ack

B Handoff Fail

C Handoff Fail

Soft handoff succeeds：

Soft handoff fails


Apply for target BS resources

Success

Failure

A: Inter-BS Incoming Hard HO Requests[Times] B: Inter-BS Incoming Hard HOs Failures (Resource Allocation Failed)[Times] C: Inter-BS Incoming Hard HOs Failures (HO Execution Failed)[Times] C: Inter-BS Incoming Hard HOs Failures (HO Interrupted by VCN)[Times] D: Successful Inter-BS Incoming Hard HOs[Times]





Performance Stat of Hard HO Decision Algorithm Table 4-12 lists the measurement items about Performance Stat of Hard HO Decision Algorithm.

Table 4-12 Measurement items about Performance Stat of Hard HO Decision Algorithm

Item Name Item Type Measurement Method

Unit Item Analysis:

Pilot-beacon Hard HO Decisions[Times]

Original item

By accumulation

Time The RAC measures when it receives a PSMM or CFSRPM message and the source RRM module determines to trigger hard HOs.

Mobile assisted Hard HO Decisions[Times]

Original item

By accumulation


Same-frequency Hard HO Decisions[Times]

Original item

By accumulation


Handdown Hard HO Decisions[Times]

Original item

By accumulation


Direct Hard HO Decisions[Times]

Original item

By accumulation


Voice to Fax HHO Decisions[Times]

Original item

By accumulation

Time The RAC measures when a hard handoff is originated because of the transition from voice call to fax.



4.1.9 PCF HO Success Ratio

Inter-PCF Handoff Performance Stat The inter-PCF handoff performance is measured with the compound item HO Success Ratio of Packet Service Subscribers[%].

Item name: HO Success Ratio of Packet Service Subscribers[%] Item meaning: the success ratio of HOs by PS subscribers Item Type: RAC Formula: HO Success Ratio of Packet Service Subscribers[%] = Successful HOs of

Packet Service Subscribers[Times]/HO Requests by Packet Service Subscribers[Times] x 100%

Table 4-13 lists the measurement items about Inter-PCF Handoff Performance Stat.

Table 4-13 Measurement items about Inter-PCF Handoff Performance Stat

Item Name Item Type Item Analysis

Incoming HOs to this PCF with MS/AT Active[Times]

Original item Number of handoffs to the target PCF when the MS/AT is in the active state. The RAC measures every time the target PCF receives an A9-Setup-A8 message with the data ready indicator DRI and handoff indicator HO set to "1" when the MS is in the active state, as indicated by A of Figure 4-33.

Outgoing HOs from this PCF with MS/AT Active[Times]

Original item Number of handoffs from the source PCF when the MS is in the active state. The RAC measures every time the source PCF receives an A9-AL-Disconnected message with the MS in the active state, as indicated by B of Figure 4-33.

Incoming HOs to this PCF with MS/AT Dormant[Times]

Original item Number of handoffs to the target PCF when the MS/AT is in the dormant state. The RAC measures every time the target PCF receives an A9-Setup-A8 message with the data ready indicator DRI and handoff indicator HO set to "0" when the MS/AT is in the dormant state, as indicated by A of Figure 4-33.

HO Requests by Packet Service Subscribers[Times]

Original item Number of A9-Setup-A8 messages that the target PCF receives when the MS/AT is in the dormant or active state. The RAC measures every time the target PCF receives an A9-Setup-A8 message when the MS/AT is in the dormant or active state. The data ready indicator DRI and the handoff indicator HO are set to "0" or "1", as indicated by A of Figure 4-33, Figure 4-34, and Figure 4-35.





Item Name Item Type Item Analysis

Successful HOs of Packet Service Subscribers[Times]

Original item Number of successful handoffs to the target PCF when the MS/AT is in the dormant or active state. The RAC measures every time the target PCF receives an A9-Setup-A8 message with the data ready indicator DRI and handoff indicator HO set to "0" or "1" when the MS/AT is in the dormant or active state, and the handoff message is successfully processed, as indicated by C of Figure 4-33, Figure 4-34, and Figure 4-35.

Inter-PCF Handoff (Within the Same PDSN) Procedure With MS/AT Active Figure 4-33 shows Inter-PCF Handoff Performance Stat (within the same PDSN and with MS/AT active).



Figure 4-33 Inter-PCF Handoff Performance Stat (within the same PDSN and with MS/AT active)

SourceBS

GHDM/UHDM

Handoff Required

Handoff Request

MS

A9-Setup-A8

A11-Registration-Request

A11-Registration-Reply

Clear Command

A9-AL Disconnected

A9-Connect-A8

Handoff Request Ack

Handoff Command

A9-AL Connected Ack

MS Ack Order

Handoff Commenced

Handoff Completation

BS Ack Order

A9-ALConnected

Handoff Complete

A9-Release-A8

A11-Registration-Request(Lifetime=0)


A9-Release-A8 Complete

Clear Complete

A9-AL Disconnected Ack

SourcePCF PDSNVCN

TargetBS

TargetPCF

A

B

C

A: Incoming HOs to this PCF with MS/AT Active[Times] HO Requests by Packet Service Subscribers[Times]

B: Outgoing HOs from this PCF with MS/AT Active[Times] C: Successful HOs of Packet Service Subscribers[Times]





Inter-AN Handoff Procedure With MS/AT Dormant Figure 4-34 shows Inter-PCF Handoff Performance Stat (inter-AN handoff with MS/AT dormant).

Figure 4-34 Inter-PCF Handoff Performance Stat (inter-AN handoff with MS/AT dormant)

PDSN

A9-Setup-A8

AT TargetPCF

SourceAN

TargetAN

SourcePCF

UATIRequest

HardwareIDRequest

HardwareIDResponse

UATIAssignment

UATIComplete

A13-Session Information Request

A13-Session Information Response

A13-Session Information Confirm

A11-Registration-Update

A11-Registration-Ack





A9-Release-A8-Complete

LocationNotification

LocationAssignment

LocationComplete

A

B

A: Incoming HOs to this PCF with MS/AT Dormant[Times] HO Requests by Packet Service Subscribers[Times]

B: Successful HOs of Packet Service Subscribers[Times]



Inter-PCF Handoff (Within the Same RAC) Procedure With MS/AT Dormant Figure 4-35 shows Inter-PCF Handoff Performance Stat (within the same PDSN and with MS/AT dormant).

Figure 4-35 Inter-PCF Handoff Performance Stat (within the same PDSN and with MS/AT dormant)


Assignment Failure


Clear Command


Clear Complete

CM Service Request

Origination Message

BS Ack Order

Assignment Request

A9-Setup-A8






Dormant Packet Data Session

MS SourceBS

TargetBS VCN Source

PCFTargetPCF PDSN

A

B

A: Incoming HOs to this PCF with MS/AT Dormant[Times] HO Requests by Packet Service Subscribers[Times]

B: Successful HOs of Packet Service Subscribers[Times]





4.1.10 Data Rate Assignment When the data service rate is low, check the SCH rate assignment to find out the cause of the low rate and check the SCH request performance to find out the cause of SCH assignment failures so that necessary adjustments can be made.

Performance Stat of SCH Rate Assignment This performance measurement item is used mainly for network optimization. Table 4-14 lists the measurement items about Performance Stat of SCH Rate Assignment.

Table 4-14 Measurement items about Performance Stat of SCH Rate Assignment

Item Name Formula Measurement Point

Forward SCH Rate Reduction Rate Due To Weak Pilot Strength [1X*Times] is the total number of SCH rates when the SCH rate is limited due to weak pilot strength during forward SCH assignment. The RAC measures when the forward SCH rate is limited due to weak pilot strength during SCH radio resources assignment after receiving the assignment request.

Forward SCH Average Rate Due to Weak Pilot Strength Rate Reduction[Times of Basic Rate]

Forward SCH Rate Reduction Rate Due To Weak Pilot Strength [1X*Times]/Forward SCH Rate Reduction Due To Weak Pilot Strength [Times]

Forward SCH Rate Reduction Due To Weak Pilot Strength [Times] is the times that the forward SCH rate is limited due to weak pilot strength. The RAC measures when the forward SCH rate is limited due to weak pilot strength during SCH radio resources assignment after receiving the assignment request.

Forward SCH Rate Reduction Rate Due To Walsh Code Limit [1X*Times] is the total number of SCH rates when the SCH rate is limited due to Walsh code limit during forward SCH assignment. The RAC measures when the forward SCH rate is limited due to Walsh code limit during SCH radio resources assignment after receiving the assignment request.

Forward SCH Average Rate Due to Walsh Code Limit Rate Reduction[Times of Basic Rate]

Forward SCH Rate Reduction Rate Due To Walsh Code Limit [1X*Times]/Forward SCH Rate Reduction Due To Walsh Code Limit [Times]

Forward SCH Rate Reduction Due To Walsh Code Limit [Times] is the times that the forward SCH rate is limited due to Walsh code limit. The RAC measures when the forward SCH rate is limited due to Walsh code limit during SCH radio resources assignment after receiving the assignment request.




Forward SCH Rate Reduction Rate Due To Power Limit [1X*Times] is the total number of SCH rates when the SCH rate is limited due to power limit during forward SCH assignment. The RAC measures when the forward SCH rate is limited due to power limit during SCH radio resources assignment after receiving the assignment request.

Forward SCH Average Rate Due to Power Limit Rate Reduction[Times of Basic Rate]

Forward SCH Rate Reduction Rate Due To Power Limit [1X*Times]/Forward SCH Rate Reduction Due To Power Limit [Times]

Forward SCH Rate Reduction Due To Power Limit [Times] is the times that the forward SCH rate is limited due to power limit. The RAC measures when the forward SCH rate is limited due to power limit during SCH radio resources assignment after receiving the assignment request.

Forward SCH Rate Reduction Rate Due To CE Limit [1X*Times] is the total number of SCH rates when the SCH rate is limited due to CE limit during forward SCH assignment. The RAC measures when the forward SCH rate is limited due to CE limit during SCH radio resources assignment after receiving the assignment request.

Forward SCH Average Rate Due to CE Limit Rate Reduction[Times of Basic Rate]

Forward SCH Rate Reduction Rate Due To CE Limit [1X*Times]/Forward SCH Rate Reduction Due To CE Limit [Times]

Forward SCH Rate Reduction Due To CE Limit [Times] is the times that the forward SCH rate is limited due to CE limit. The RAC measures when the forward SCH rate is limited due to CE limit during SCH radio resources assignment after receiving the assignment request.

Forward SCH Rate Reduction Rate Due To Schedule [1X*Times] is the total number of SCH rates when the SCH rate is limited due to schedule during forward SCH assignment. The RAC measures when the forward SCH rate is limited due to schedule during SCH radio resources assignment after receiving the assignment request.

Forward SCH Average Rate Due to Schedule Rate Reduction[Times of Basic Rate]

Forward SCH Rate Reduction Rate Due To Schedule [1X*Times]/Forward SCH Rate Reduction Due To Schedule [Times]

Forward SCH Rate Reduction Due To Schedule [Times] is the times that the forward SCH rate is limited due to schedule. The RAC measures when the forward SCH rate is limited due to schedule during SCH radio resources assignment after receiving the assignment request.






Forward SCH Rate Reduction Rate Due To Others [1X*Times] is the total number of SCH rates when the SCH rate is limited due to other causes during forward SCH assignment. The RAC measures when the forward SCH rate is limited due to other causes during SCH radio resources assignment after receiving the assignment request.

Forward SCH Average Rate Due to Others Rate Reduction[Times of Basic Rate]

Forward SCH Rate Reduction Rate Due To Others [1X*Times]/Forward SCH Rate Reduction Due To Others [Times]

Forward SCH Rate Reduction Due To Others [Times] is times that the forward SCH rate is limited during forward SCH assignment due to causes other than the following:

Weak pilot strength Walsh code limit Power limit CE limit Schedule

The RAC measures when the forward SCH rate is limited due to other causes during SCH radio resources assignment after receiving the assignment request.

Reverse SCH Rate Reduction Rate Due To Weak Pilot Strength [1X*Times] is the total number of SCH rates when the SCH rate is limited due to weak pilot strength during reverse SCH assignment. During reverse SCH assignment, the rate is limited by the total rate when the pilot strength is weak.

Reverse SCH Average Rate Due to Weak Pilot Strength Rate Reduction[Times of Basic Rate]

Reverse SCH Rate Reduction Rate Due To Weak Pilot Strength [1X*Times]/Reverse SCH Rate Reduction Due To Weak Pilot Strength [Times]

Reverse SCH Rate Reduction Due To Weak Pilot Strength [Times] is the times that the reverse SCH rate is limited due to weak pilot strength. The RAC measures when the reverse SCH rate is limited due to weak pilot strength during SCH radio resources assignment after receiving the assignment request.

Reverse SCH Rate Reduction Rate Due To Capacity Limit [1X*Times] is the total number of SCH rates when the SCH rate is limited due to power limit during reverse SCH assignment. The RAC measures when the reverse SCH rate is limited due to Capacity limit during SCH radio resources assignment after receiving the assignment request.

Reverse SCH Average Rate Due to Capacity Limit Rate Reduction[Times of Basic Rate]

Reverse SCH Rate Reduction Rate Due To Capacity Limit [1X*Times]/Reverse SCH Rate Reduction Due To Capacity Limit [Times]

Reverse SCH Rate Reduction Due To Capacity Limit [Times] is the times that the reverse SCH rate is limited due to capacity limit. The RAC measures when the reverse SCH rate is limited due to Capacity limit during SCH radio resources assignment after receiving the assignment request.




Reverse SCH Rate Reduction Rate Due To CE Limit [1X*Times] is the total number of SCH rates when the SCH rate is limited due to CE limit during reverse SCH assignment. The RAC measures when the reverse SCH rate is limited due to CE limit during SCH radio resources assignment after receiving the assignment request.

Reverse SCH Average Rate Due to CE Limit Rate Reduction[Times of Basic Rate]

Reverse SCH Rate Reduction Rate Due To CE Limit [1X*Times]/Reverse SCH Rate Reduction Due To CE Limit [Times]

Reverse SCH Rate Reduction Due To CE Limit [Times] is the times that the reverse SCH rate is limited due to CE limit. The RAC measures when the reverse SCH rate is limited due to CE limit during SCH radio resources assignment after receiving the assignment request.

Reverse SCH Rate Reduction Rate Due To Others [1X*Times] is the total number of SCH rates when the SCH rate is limited due to others during reverse SCH assignment. The RAC measures when the reverse SCH rate is limited due to others during SCH radio resources assignment after receiving the assignment request.

Reverse SCH Average Rate Due to Others Rate Reduction[Times of Basic Rate]

Reverse SCH Rate Reduction Rate Due To Others [1X*Times]/Reverse SCH Rate Reduction Due To Others [Times]

Reverse SCH Rate Reduction Due To Others [Times] is times that the reverse SCH rate is limited during reverse SCH assignment due to causes other than the following:

Weak pilot strength Walsh code limit Power limit CE limit Schedule

The RAC measures when the reverse SCH rate is limited due to others during SCH radio resources assignment after receiving the assignment request.

Performance Stat of SCH Request In the CDMA system, the SCH request performance is measured with the compound items Successful Forward SCH requests Ratio[%] and Successful Reverse SCH requests Ratio[%].

Item name: Successful Forward SCH requests Ratio[%] Meaning: success ratio of F-SCH requests Item type: RAC performance measurement, RAC/carrier-level Successful Forward SCH requests Ratio[%] = (Successful Forward SCH Leg-Add

Leg[Times]+Successful Forward SCH Leg-Del Leg[Times])/(Forward SCH Leg Requests-Add Leg[Times]+Forward SCH Leg Requests-Del Leg[Times])%100%





Analysis: The RAC performance measurement items measure the factors that lead to forward SCH request failures. Table 4-15 lists the measurement items about Successful Forward SCH requests Ratio.

Table 4-15 Measurement items about Successful Forward SCH requests Ratio


Forward SCH Leg Failures (Radio resources unavailable)

The RAC measures when it fails to apply for the forward SCH resources due to unavailable radio resources. Then, the RAC does not send Extended Supplemental Channel Assignment Message.


Forward SCH Leg Failures (Requested terrestrial resources unavailable)

The RAC measures when it fails to apply for the forward SCH resources due to unavailable terrestrial resources. Then, the RAC does not send Extended Supplemental Channel Assignment Message.


Forward SCH Leg Failures (Act SDU Failure)

The RAC measures when it fails to apply for the forward SCH resources due to SDU activation failure. Then, the RAC does not send Extended Supplemental Channel Assignment Message.

Check the RAC hardware and query alarms.

Forward SCH Leg Failures (Other causes)

The RAC measures when it fails to apply for the forward SCH resources due to other causes. Then, the RAC does not send Extended Supplemental Channel Assignment Message.

Check possible causes other than those mentioned above.

Table 4-16 lists measurement subsets related to Successful Forward SCH requests Ratio.

Table 4-16 Measurement subsets related to Successful Forward SCH requests Ratio

Measurement Subset

Item Type

Measurement Method

Unit Measurement Point

Successful Forward SCH Leg-Add Leg [Times]

Original item

By accumulation

Time The RAC measures when it sets up a forward SCH, and the RRM module triggers forward SCH assignment. See A of Figure 4-36.

Successful Forward SCH Leg-Del Leg [Times]

Original item

By accumulation

Time The RAC measures when it sets up a forward SCH, and the RRM module triggers forward SCH assignment. See A of Figure 4-36.



Measurement Subset

Item Type

Measurement Method


Forward SCH Leg Requests-Add Leg [Times]

Original item

By accumulation

Time The RAC measures when it delivers an Extended Supplemental Channel Assignment Message, as indicated by B of Figure 4-36.

Forward SCH Leg Requests-Del Leg [Times]

Original item

By accumulation


Forward SCH Setup Procedure Figure 4-36 shows Performance Stat of Forward SCH Request.

Figure 4-36 Performance Stat of Forward SCH Request.

MS BSCBTS

Abis-BTS Setup

Abis Connect

Abis Connect Ack

Abis-BTS Setup Ack

Abis Burst Request

Abis Burst Response

Abis Burst Commit

Extended Supplemental Channel Assignment MessageB

ASCH setuptriggered

A: Forward SCH Leg Requests [Times] B: Successful Forward SCH Leg [Times]

Item name: Successful Reverse SCH requests Ratio Meaning: success ratio of R-SCH requests Item type: RAC performance measurement, RAC/carrier-level





Successful Reverse SCH requests Ratio[%] = (Successful Reverse SCH Leg-Add Leg[Times]+Successful Reverse SCH Leg-Del Leg[Times])/(Reverse SCH Leg Requests-Add Leg[Times]+Reverse SCH Leg Requests-Del Leg[Times])%100%

Analysis: The RAC performance measurement items measure the factors that lead to reverse SCH request failures. Table 4-17 lists the measurement items about Successful Reverse SCH requests Ratio.

Table 4-17 Measurement items about Successful Reverse SCH requests Ratio


Reverse SCH Leg Failures (Radio resources unavailable)

The RAC measures when it fails to apply for the reverse SCH resources due to unavailable radio resources. Then, the RAC does not send Extended Supplemental Channel Assignment Message.


Reverse SCH Leg Failures (Requested terrestrial resources unavailable)

The RAC measures when it fails to apply for the reverse SCH resources due to unavailable terrestrial resources. Then, the RAC does not send Extended Supplemental Channel Assignment Message.


Reverse SCH Leg Failures (Act SDU Failure)

The RAC measures when it fails to apply for the reverse SCH resources due to SDU activation failure. Then, the RAC does not send Extended Supplemental Channel Assignment Message.

Check the RAC hardware and query alarms.

Reverse SCH Leg Failures (Other causes)

The RAC measures when it fails to apply for the reverse SCH resources due to other causes. Then, the RAC does not send Extended Supplemental Channel Assignment Message.

Check possible causes other than those mentioned above.

Table 4-18 lists measurement items about Successful Reverse SCH requests Ratio.

Table 4-18 Measurement items related to Successful Reverse SCH requests Ratio

Measurement Subset

Item Type

Measurement Method


Successful Reverse SCH Leg-Add Leg [Times]

Original item

By accumulation




Measurement Subset

Item Type

Measurement Method


Successful Reverse SCH Leg-Del Leg [Times]

Original item

By accumulation


Reverse SCH Leg Requests-Add Leg [Times]

Original item

By accumulation

Time The RAC measures when it receives a Supplemental Channel Request Message, and the RRM module triggers reverse SCH assignment. See A of Figure 4-37.

Reverse SCH Leg Requests-Del Leg [Times]

Original item

By accumulation

Time The RAC measures when it receives a Supplemental Channel Request Message, and the RRM module triggers reverse SCH assignment. See A of Figure 4-37.





Reverse SCH Setup Procedure Figure 4-37 shows Performance Stat of Reverse SCH Request.

Figure 4-37 Performance Stat of Reverse SCH Request.

MS RACBTS

Abis-BTS Setup

Abis Connect

Abis Connect Ack

Abis-BTS Setup Ack

Supplemental Channel Request Message

Abis Burst Request

Abis Burst Response

Abis Burst Commit

Extended Supplemental Channel Assignment MessageB

A

A: Reverse SCH Leg Requests [Times] B: Successful Reverse SCH Leg [Times]

4.1.11 Location Update Success Ratio If the location update success ratio is low, measurement items such as Paging Success Ratio[%] is greatly affected. In such cases, check the location update measurement items.

Location Update Performance Stat Item name: Registration Success Ratio[%] Meaning: ratio of the number of Location Updating Accept messages that the RAC

receives from the VCN to the number of Location Updating Requests that the RAC sends to the VCN

Item type: RAC performance measurement, RAC/carrier-level Measurement method: by calculation Formula: Registration Success Ratio[%] = Successful Registration/Registration Requests

x 100% Item analysis:

Meanings of calculated items:



− Successful Registrations[Times]: Number of Location Updating Accept messages that the RAC receives from the VCN. The RAC measures every time it receives a Location Updating Accept message from the VCN, as indicated by B of Figure 4-38.

− Registration Requests[Times]: The RAC measures when the it sends a Location Updating Request message to the VCN. See A of Figure 4-38.

− Location Updates within Unit Time[Times/Minute]: Number of Location updates in a unit of time. Formula: Registration Requests/granularity period

MS Registration Acceptance Procedure Figure 4-38 shows Location Update Performance Stat.

Figure 4-38 Location Update Performance Stat

MS BS VCN

1

2

3

4

Registration Message

Location Updating Request

Location Updating Accept

Registration Accepted Order

A

B

A: Registration Requests[Times] B: Successful Registrations[Times]

4.1.12 FCH FER Performance Stat The FCH FER is measured by the BTS. The measurement items of average FER, maximum/minimum FER, average Eb/Nt, and maximum/minimum Eb/Nt are available. Table 4-19 lists measurement items about FCH FER Performance Stat.

Table 4-19 Measurement items about FCH FER Performance Stat


FCH Total Average PER [0. 10%]

In 30 minutes: the BTS measures: FCH Single Branch Average FER[0. 10%] FCH Soft Handoff Branch Average FER [0. 10%] FCH Softer Handoff Branch Average FER [0. 10%] FCH Soft-Softer Handoff Branch Average FER [0. 10%]

The BTS measures the average FER of the FCHs under each carrier and then measures the reverse convergence. If the FER is greater than the target value, adjust the power control parameter. In normal cases, the FER decreases because of poor coverage, pilot pollution, and interference.






FCH Max/Min FER

In 30 minutes, the BTS measures: FCH Single Branch Max FER[0. 10%] FCH Single Branch Min FER[0. 10%] FCH Soft Handoff Branch Max FER [0. 10%] FCH Soft Handoff Branch Min FER [0. 10%] FCH Softer Handoff Branch Max FER [0. 10%] FCH Softer Handoff Branch Min FER [0. 10%] FCH Soft-Softer Handoff Branch Max FER [0. 10%] FCH Soft-Softer Handoff Branch Min FER [0. 10%]

Max/Min FER shows the FER value range. If the FER value exceeds the value range, adjust the power control parameters or expand the system capacity.

FCH Average Eb/Nt

In 30 minutes, the BTS measures: FCH Single Branch Max FER[0. 10%] FCH Single Branch Min FER[0. 10%] FCH Soft Handoff Branch Max FER [0. 10%] FCH Soft Handoff Branch Min FER [0. 10%] FCH Softer Handoff Branch Max FER [0. 10%] FCH Softer Handoff Branch Min FER [0. 10%] FCH Soft-Softer Handoff Branch Average FER [0. 10%]

Average Eb/Nt is the intermediate variable of the power control. You can compare it with the specified maximum value and minimum value to decide whether the maximum value and minimum value are proper.

FCH Max/Min Eb/Nt

In 30 minutes: the BTS measures: FCH Single Branch Max Eb/Nt [0. 125dB] FCH Single Branch Min Eb/Nt [0. 125dB] FCH Soft Handoff Branch Max Eb/Nt [0. 125dB] FCH Soft Handoff Branch Min Eb/Nt [0. 125dB] FCH Softer Handoff Branch Max Eb/Nt [0. 125dB] FCH Softer Handoff Branch Min Eb/Nt [0. 125dB] FCH Soft-Softer Handoff Branch Max Eb/Nt [0. 125dB]

FCH Soft-Softer Handoff Branch Min Eb/Nt [0. 125dB]

Max/Min Eb/Nt indicates the value range of the Eb/Nt.



The carrier-level FER and Eb/Nt are measured by the RAC. Table 4-20 shows measurement items about Carrier FER and Eb/Nt Performance Stat.

Table 4-20 Measurement items about Carrier FER and Eb/Nt Performance Stat


FER of Carrier

FER of different services in the forward and reverse links in the CS/PS domain.

The RAC measures the average PER of each carrier and then measures the reverse convergence. If the PER is greater than the target value, adjust the power control parameter. In normal cases, the PER decreases because of poor coverage, pilot pollution, and interference.

Eb/Nt of Carrier

Average of all the Eb/Nt values in reverse link open circuit power control on the carrier.

This item reflects the maximum value of the PER, and the PER cannot exceed this value. Interference and faults in the MS/AT are among the factors that cause exceptions in the reverse power control. If the PER goes beyond this scope, adjust the power control parameters or expand the capacity.

4.1.13 SCH FER Measurement Stat SCH FER Measurement Stat measures the average FER and maximum FER on the RSCH. Table 4-21 lists measurement items of SCH FER Measurement Stat.

Table 4-21 Measurement items about SCH FER Performance Measurement


RSCH Average FER [0. 10%]

The BTS measures this item for each rate (1X, 2X, 4X, 8X, 16X) separately.

This is the average FER of the RSCH within 30 minutes.

The BTS measures the average PER of the MS/AT under each carrier and then measures the reverse convergence. If the PER is greater than the target value, adjust the power control parameter.

RSCH Max FER [0. 10%]

The BTS measures this item for each rate (1X, 2X, 4X, 8X, 16X) separately.

This is the maximum FER of the RSCH within 30 minutes.

This item relects the maximum value of the FER, and the value of the FER cannot exceed this value. If the PER goes beyond this scope, adjust the power control parameters or expand the capacity.





4.2 Traffic 4.2.1 Traffic Performance Stat(FCH)

Density of Traffic Carried on TCH (Excluding HO)[Erl] Item name: Density of Traffic Carried on TCH (Excluding HO)[Erl] Item meaning: density of traffic carried on the TCH, excluding HOs. Unit: Erl Item type: RAC performance measurement, RAC/carrier-level Formula: TCH Seizure Duration (Excluding HO) (DCCH-PS) [Second]/(Measurement

period x 60) Analysis: This item reflects the net FCH traffic. This item distinguishes the CS domain

from the PS domain. Table 4-22 lists measurement items about Density of Traffic Carried on TCH (Excluding HO).

Table 4-22 Measurement items about Density of Traffic Carried on TCH (Excluding HO)

Item Name Meaning Formula

Density of Traffic Carried on TCH (Excluding HO) (CS-FCH)[Erl]

Density of CS traffic carried on FCHs, excluding HOs.

TCH Seizure Duration (Excluding HO) (FCH-CS)/(measurement period x 60)

Density of Traffic Carried on TCH (Excluding HO) (PS-FCH)[Erl]

Density of PS traffic carried on FCHs, excluding HOs.

TCH Seizure Duration (Excluding HO) (FCH-PS)/(measurement period x 60)

Carrier-level performance measurement items are calculated as follows: all the original

items under this carrier are divided by the total number of legs of this item, and the quotients thus obtained are then added.

RAC-level performance measurement items are the sum of all the original items of this RAC.

CE Traffic Density Item name: CE Traffic Density Item meaning: density of CE traffic carried on the TCH. Unit: Erl Item type: RAC performance measurement, RAC/carrier level Formula: CE Seizure Duration [Second]/(measurement period x 60)



Analysis: This item reflects the occupation of CE resources, and it distinguishes the CD domain from the PS domain. Table 4-23 lists measurement items about CE Traffic Density.

Table 4-23 Measurement items about CE Traffic Density


CE Traffic Density - Speech Service FCH

Density of CE traffic carried on CS FCHs, excluding HOs

CE Seizure Duration (CS-FCH) / (measurement period x 60)

CE Traffic Density - Packet Service FCH[Erl]

Density of CE traffic carried on PS FCHs, excluding HOs

CE Seizure Duration (PS-FCH) / (measurement period x 60)

Carrier-level performance measurement items are calculated as follows: all the original

items under this carrier that involve sums are divided by the total number of softer handoff legs of this item, and the quotients thus obtained are then added.

RAC-level performance measurement items are the sum of all the original items of this RAC multiplied by the number of soft handoff legs of this item.

Walsh Traffic Density Item name: Walsh Traffic Density Item meaning: density of Walsh traffic carried on the TCH. Unit: Erl Item type: RAC performance measurement, RAC/carrier-level Formula: Walsh Seizure Duration [Second]/(measurement period x 60) Analysis: This item reflects the CE traffic density. This item distinguishes the CS domain

from the PS domain. Table 4-24 lists measurement items about Walsh Traffic Density.

Table 4-24 Measurement items about Walsh Traffic Density


Walsh Traffic Density - Speech Service FCH

Density of Walsh traffic carried on CS FCHs.

Walsh Seizure Duration (FCH-CS)/ measurement period x 60)

Walsh Traffic Density-Packet Service FCH[Erl]

Density of Walsh traffic carried on PS FCHs.

Walsh Seizure Duration (FCH-PS)/ measurement period x 60)





Carrier-level performance measurement items are the sum of all the original items of this carrier. RAC-level performance measurement items are the sum of all the original items of this RAC multiplied by the number of legs of this item.

Soft HO Ratio - FCH[%] Item name: Soft HO Ratio - FCH Item meaning: ratio of the soft HO (excluding softer HOs) traffic density on FCHs to the

traffic density excluding HOs Unit: % Item type: RAC performance measurement, RAC/carrier-level Formula: CE traffic density – Density of Traffic Carried on TCH (Excluding HO)

(FCH)/Density of Traffic Carried on TCH (Excluding HO) (FCH) x 100% Analysis: This item is related to Density of Traffic Carried on TCH.

4.2.2 SCH Traffic Performance Measurement

SCH Traffic Performance Measurement Items SCH Traffic Performance Measurement considers only situations in which the total number of soft handoff legs and softer handoff legs is not more than three. Table 4-25 lists measurement items about SCH Traffic Performance Measurement.

Table 4-25 Measurement items about SCH Traffic Performance Measurement


CE Traffic Density-SCH

Density of CE traffic carried on SCHs. The RAC measures RAC-level CE traffic carried on forward and reverse SCHs, and carrier-level CE traffic carried on forward and reverse SCHs.

CE Seizure Duration (SCH)/(measurement period x 60)

Walsh Traffic Density-SCH

Walsh Traffic Density carried on SCHs

Walsh Seizure Duration /(measurement period x 60)

Measurement items for the reverse SCH do not distinguish the RC3 from the RC4, and

reverse SCH original items measure 1X, 2X, 4X, 8X, 16X, and 32X. Carrier-level performance measurement items are the sum of all the original items of this

carrier. RAC-level performance measurement items are the sum of all the original items of this RAC multiplied by the number of legs of this item.



Table 4-26 lists the original items of CE seizure duration.

Table 4-26 Original items of CE seizure duration

Item Name Item Analysis

Single-Leg Seizure Duration (1X, 2X, 4X, 8X, 16X SCH-RC3/1X, 2X, 4X, 8X, 16X, 32X SCH-RC4)

During the current measurement time unit (one second), the RAC judges the handoff situation of the carrier in the forward SCH active set. The item that maps to the situation increases by 1.

Single-Leg Soft HO and Two-Leg Softer HO Seizure Duration (1X, 2X, 4X, 8X, 16X SCH-RC3/1X, 2X, 4X, 8X, 16X, 32X SCH-RC4)


Single-Leg Soft HO and Three-Leg Softer HO Seizure Duration (1X, 2X, 4X, 8X, 16X SCH-RC3/1X, 2X, 4X, 8X, 16X, 32X SCH-RC4)


Two-Leg Soft HO Seizure Duration (1X, 2X, 4X, 8X, 16X SCH-RC3/1X, 2X, 4X, 8X, 16X, 32X SCH-RC4)


Two-Leg Soft HO and Two-Leg Softer HO Seizure Duration (1X, 2X, 4X, 8X, 16X SCH-RC3/1X, 2X, 4X, 8X, 16X, 32X SCH-RC4)


Three-Leg Soft HO Seizure Duration (1X, 2X, 4X, 8X, 16X SCH-RC3/1X, 2X, 4X, 8X, 16X, 32X SCH-RC4)


The original items that affect Walsh seizure duration are the same as those that affect CE seizure duration.

Soft HO Ratio - SCH[%] Item name: Soft HO Ratio - SCH Item meaning: ratio of the soft HO (excluding softer HOs) traffic density on SCHs to the

traffic density excluding HOs Unit: % Item type: RAC performance measurement, RAC-level forward and reverse SCHs,

carrier-level forward and reverse SCHs. Formula:

− RC3: (([CE Seizure Duration-(Forward iXSCH-RC3)[Second]]/i-[TCH Seizure Duration (Excluding HO) (Forward iXSCH-RC3)[Second]])/[TCH Seizure Duration (Excluding HO) (Forward iXSCH-RC3)[Second]]) % 100%





− RC4: (([CE Seizure Duration-(Forward iXSCH-RC4)[Second]]/i/2-[TCH Seizure Duration (Excluding HO) (Forward iXSCH-RC4)[Second]])/[TCH Seizure Duration (Excluding HO) (Forward iXSCH-RC4)[Second]]) % 100%

Analysis: This item afftects measurement items (such as CE seizure duration) that are related to the proportion of soft handoffs. For details, refer to CE Traffic Density. The original items are the same. See Table 4-28.

The measurement for reverse SCHs does not distinguish the RC3 from the RC4, and the calculation methods for 1X, 2X, 4X, 8X, 16X, and 32X are the same as the RC4 methods.

4.2.3 1X Traffic Performance Measurement

1X Max Ach One Way Delay[km] Item name: 1X Max Ach One Way Delay[km] Item meaning: maximum ONEWAYDELAY of the ACH within 30 minutes. Unit: km Item type: BTS measurement Analysis: One way delay refers to the delay from the MS to the channels processing chip

set on the CCPM, excluding the transmission delay from the antenna feeder system to the channels processing chip set. The maximum one way delay within 30 minutes indicates the longest distance from an MS to the BTS. The BTSC measures the one way delay in the call count reported by the CCPM and calculates the maximum. This item is measured in every carrier.

1X Region (n km to n+1 km) Call Count[piece] Item name: 1X ACH Region (n km to n+1 km) Call Count[piece] Item meaning: successful call count in 1X ACH region (n km to n+1 km) Unit: Piece Item type: BTS measurement Analysist: The BTSC measures the one way delay reported by the CECM and calculates

separately the call count of 30 minutes in the region from n km to n+1 km (0≤n≤60) and that in the region beyond 60 km. The measurement object is a specific carrier.

4.2.4 Data Flow

Average Flow of PCF Data Item name: Average Flow of PCF Data Item meaning: Average data flow that the PCF receives from the PDSN (downlink) and

the BS/AN (uplink). Unit: kbit/s Item type: uplink and downlink Measurement method: by calculation



Formula: (8 % [Total of PCF uplink and downlink data])/(60 % Measurement period)

PCF Total Bytes Item name: PCF Total Bytes [KB] Item meaning: Total data that the PCF receives from the PDSN (downlink) and the

BS/AN (uplink). Unit: KB Item type: uplink and downlink Measurement method: By accumulation Analysis: The PCF measures every time it receives a message from the PDSN (downlink)

and the BS/AN (uplink).

PCF Total Packets Item name: PCF Total Packets [KB] Item meaning: Total packets that the PCF receives from the PDSN (downlink) and the

BS/AN (uplink). Unit: Packet Item type: uplink and downlink Measurement method: By accumulation Analysis: The PCF measures every time it receives a message from the PDSN (downlink)

and the BS/AN (uplink).

Average Size of PCF Packets Item name: Average Size of PCF Downlink Data Packets[Bytes/Packet] Item meaning: Average size of packets that the PCF receives from the PDSN (downlink)

and the BS/AN (uplink). Unit: Bytes/Packet Item type: uplink and downlink Measurement method: by calculation Analysis: ([Uplink/Downlink Bytes Received by PCF[KB]] % 1024)/[Uplink/Downlink

Packets Received by PCF[Packet]]

PCF discard packet number because packet is too long[Packet] Item name: PCF discard packet number because packet is too long[Packet] Item meaning: number of packets that the PCF receives from the PDSN but discards

because of over-long data packets Unit: Packet Item type: Downlink Measurement method: By accumulation Analysis: The RAC measures every downlink packet that the PCF receives from the

PDSN but discards because of over-long data packets.





Packets Discarded due to Buffer Area Overflow[Packet] Item nam: Packets Discarded due to Buffer Area Overflow[Packet] Item meaning: number of packets that the PCF receives from the PDSN but discards

because of buffer area overflow Unit: Packet Item type: Downlink Measurement method: By accumulation Analysis: The RAC measures every downlink packet that the PCF receives from the

PDSN but discards because of buffer area overflow.

Packets Discarded due to Sequencing Error[Packet] Item name: Packets Discarded due to Sequencing Error[Packet] Item meaning: number of packets that the PCF receives from the PDSN but discards

because of sequencing errors Unit: Packet Item type: Downlink Measurement method: By accumulation Analysis: The RAC measures every downlink packet that the PCF receives from the

PDSN but discards because of sequencing errors.

Forward Octets Between PCF and RAC[KB] Item name: Forward Octets Between PCF and RAC[KB] Item meaning: Downlink data that the RAC receives from the PCF. Unit: KB Item type: RAC measurement, forward Measurement method: By accumulation Analysis: The RAC measures the payload when it receives downlink data from the PCF.

Octets Received but Not Sent on Forward Channels[KB] Item name: Octets Received but Not Sent on Forward Channels[KB] Item meaning: Data that the CFMR receives but not yet sends. Unit: KB Item type: RAC measurement, forward Measurement method: by calculation Analysis: Forward Octets Between PCF and RAC [kB] – RLP Octets Sent on Forward

Channels (Excluding those resent)[KB] – Forward Lost RLP Octets [KB]/1024

RLP Octets Sent on Forward Channels(Excluding those resent)[KB] Item name: RLP Octets Sent on Forward Channels(Excluding those resent)[KB] Definition: data that the RAC sends on forward channels of the RLP sub-layer

(excluding re-sent data) Unit: KB Item type: RAC measurement, forward



Measurement method: By accumulation Measurement point: The RAC measures when it sends frames (not re-sent) on forward

channels of the RLP sub-layer.

RLP Octets Resent on Forward Channels[Byte] Item name: RLP Octets Resent on Forward Channels[Byte] Item meaning: data that the RAC re-sends on forward channels of the RLP sub-layer Unit: Byte Item type: RAC measurement, forward Measurement method: By accumulation Measurement point: The RAC measures when it re-sends frames on forward channels of

the RLP sub-layer.

Forward Lost RLP Octets[Byte] Item name: Forward Lost RLP Octets[Byte] Item meaning: forward data that the RAC discards due to the wrong PPP packet number Unit: Byte Item type: RAC measurement, forward Measurement method: By accumulation Analysis: The RAC measures when it discards the downlink data sent by the PCF due to

the wrong PPP packet number.

RLP Octets Received on Reverse Channels[KB] Item name: RLP Octets Received on Reverse Channels[KB] Item meaning: data that the RAC receives on reverse channels of the RLP sub-layer Unit: KB Item type: RAC measurement, reverse Measurement method: By accumulation Measurement point: The RAC measures when it receives access flow data on reverse


Total Frames Sent (Excluding those resent)[Entries] Item name: Total Frames Sent (Excluding those resent)[Entries] Item meaning: Number of RLP frames that the RAC sends to the MS on the RLP

sub-layer. Unit: Entry Item type: RAC measurement, forward and reverse Measurement method: By accumulation Analysis: The RAC measures when it receives RLP frames from the MS on the RLP

sub-layer, excluding those resent.





Total Frames Resent[Entries] Item name: Total Frames Resent[Entries] Item meaning: Number of RLP frames that the RAC re-sends to the MS on the RLP

sub-layer. Unit: Entry Item type: RAC measurement, forward and reverse Measurement method: By accumulation Analysis: The RAC measures when it re-sends RLP frames to the MS on the RLP

sub-layer.

Packet Discarded for Insufficient Buffer[Byte] Item name: Packet Discarded for Insufficient Buffer[Byte] Item meaning: forward packets that the RAC discards on the RLP sub-layer due to

insufficient buffer Unit: Byte Item type: RAC measurement, forward Measurement method: By accumulation Analysis: The RAC measures when it discards downlink packets sent by the PCF on the

RLP layer due to insufficient buffer.

Forward Link Frame Count at FCH[Entries] Item name: Forward Link Frame Count at FCH[Entries] Item meaning: Number of frames that the RAC sends on the FCH Unit: Entry Item type: RAC measurement, forward and reverse Measurement method: By accumulation Analysis: The RAC measures when it sends frames on the FCH.

Reverse Link Error Frame Count[Entries] Item name: Reverse Link Error Frame Count[Entries] Item meaning: total number of error frames that the RAC receives on reverse channels Unit: Entry Item type: RAC measurement, reverse Measurement method: By accumulation Analysis: The RAC measures when it receives error frames on reverse channels.

Total Frames Sent(rate 1/2/4/8/16/32)[Entries] Item name: Total Frames Sent(rate 1/2/4/8/16/32)[Entries] Item meaning: total frames sent by the RAC on the 1X/2X/4X/8X/16X/32X SCH Unit: Entry Item type: RAC measurement, forward and reverse Measurement method: By accumulation



Analysis: The RAC measures when it sends data frames on the 1X/2X/4X/8X/16X/32X SCH.

Packet Discarded for No A8[Byte] Item name: Packet Discarded for No A8[Byte] Item meaning: uplink data that the RAC receives on reverse channels without the A8

connection Unit: Byte Item type: RAC measurement, reverse Measurement method: By accumulation Analysis: The RAC measures when it receives uplink data on reverse channels without

the A8 connection.

4.3 Resource Usage 4.3.1 System Load Items

CSPU CPU Performance Stat Item name: CSPU CPU Load[%] Item meaning: CPU load of the CSPU Type: Original item (RAC level) Analysis: This item helps monitor the system load. Generally, the normal value of this

item is less below 70%. The value of this item may be excessively in the following situations: − Sudden increase in traffic, as on festivals or at ceremonies − Exceptions in the signaling board software

TCH Performance Stat Item name: Available TCHs[Entries] Item meaning: number of available TCHs on carriers Type: Original item (RAC level) Analysis: When the RRM module receives the blocking/unblocking indication of a

carrier or radio resource state indication, that is, carrier states (management state and operation state) change, the number of available TCHs is updated. This item reflects the situation of carriers and can be used to analyze the causes of congestion.

Forward Load of Carrier Item name: Forward Load of Carrier[%] Item meaning: forward load of current carriers. It is the ratio of the current transmit

power of carriers to the maximum transmit power Type: Original item (carrier level) Analysis: This item helps analyze whether the forward power of carriers has reached its

maximum and the traffic situations in the coverage. Generally, the forward load of carriers rises when the traffic grows. During network optimization and maintenance, pay





attention to the variation of the forward load of carriers and take timely methods, such as load sharing, shrinking the coverage, and resource optimization, to reduce the forward load of carriers.

Reverse Load of Carrier Item name: Reverse Load of Carrier[%] Item meaning: number of reverse equivalent subscribers on current carriers Type: Original item (carrier level) Analysis: This item helps analyze whether the number of reverse equivalent subscribers

on current carriers has reached its maximum. Also, this item reflects the traffic situations in the coverage. Generally, the reverse load of carriers rises when the traffic grows. During network optimization and maintenance, pay attention to the variation of the reverse load of carriers and take timely methods, such as load sharing, shrinking the coverage, and resource optimization, to reduce the reverse load of carriers.

License Performance Stat Item name: license-Restricted Call Rejection - 1X Forward/Reverse CE Resource

Overuse Item meaning: total times that the RAC fails to set up traffic channels for 1X calls due to

insufficient forward/reverse CE resources Type: Original item (RAC level) Analysis: The CSPU controls service through License. License Performance Stat shows

the system load. In the case of insufficient CE resources, − Adjust the CE resource allocation of the modules if a module frequently fails to set

up traffic channels because of insufficient License. − Expand the capacity if the RAC fails to set up traffic channels for a long period

because of insufficient License.

RSSI Performance Measurement Item name: Main and Diversity Average/Max/Min RSSI Item meaning: Maximum, minimum, and average of the main and diversity reverse RSSI

strength of each carrier board at the top of the cabinet within the measurement period. Type: Original item (carrier level) Analysis: The performance of the reverse channel in the WLL system is affected mainly

by the RSSI. If the RSSI is excessively high, KPI items, such as the call setup success ratio, call drop ratio, and paging success ratio, are affected. Therefore, in daily optimization and maintenance, pay close attention to the variation of the RSSI. Generally, the RSSI rises because of external interference and intra-system interference.



BTS STRM Transmitter Power Performance Measurement Table 4-27 lists the measurement items about BTS STRM Transmitter Power Performance Measurement.

Table 4-27 Measurement items about BTS STRM Transmitter Power Performance Measurement.

Item Name Explanation Solution

STRM Average Transmit Power [0.1 dBm]

This item measures the average digital transmit power of each TRM of the BTS within the measurement period.

STRM Max Transmit Power [0.1 dBm]

This item measures the maximum digital transmit power of each TRM of the BTS within the measurement period.

STRM Min Transmit Power [0.1 dBm]

This item measures the minimum digital transmit power of each TRM of the BTS within the measurement period.

These items clearly reflect the forward power usage of carriers so that you can notice in time carriers whose forward power is too low or too high. If the forward power is too low, take the traffic into consideration to judge whether the low forward power is normal. If it is abnormal, check whether there are alarms about the forward link.

If the forward power is too high, take the traffic into consideration to judge whether the high forward power is normal. If it is abnormal, capacity expansion is the best solution, or you can adjust the power control parameters to reduce the load.

BTS Channel Element Performance Measurement Item meaning: Number of the CEs of the carrier in different statuses (idle, traffic usage,

common channel usage, available or unavailable) in a period Type: Original item (carrier level) Analysis: The number of CEs shows the BTS load and shows whether the resource

allocation is reasonable. If the BTS congestion rate has exception, check the CE usage of the BTS.

Table 4-28 lists the measurement items about BTS Channel Element Performance Measurement.

Table 4-28 Measurement items about BTS Channel Element Performance Measurement

Item Name Explanation

1X Max Available Forward CEs[entries]

1X Max Available Reverse CEs[entries]

1X Min Available Forward CEs[entries]

The BTS measures the maximum and minimum forward and reverse CEs available in a measurement period. In normal cases, the number of the forward maximum CEs is equal






1X Min Available Reverse CEs[entries] to the number of forward CEs configured in the carrier or to the number of forward CEs of the obtained License. The number of the reverse maximum CEs is equal to the number of reverse CEs configured in the carrier minus 1 or the number of the obtained License minus 1. One reverse CE is reserved for I0 check.

1X Max Forward CEs Occupied By Service Channels[entries]

1X Max Reverse CEs Occupied By Service Channels[entries]

1X Min Forward CEs Occupied By Service Channels[entries]

1X Min Reverse CEs Occupied By Service Channels[entries]

The BTS measures the maximum and minimum CEs occupied by the forward and reverse traffic channels. The number of CEs occupied by the forward and reverse traffic channels indicates the number of legs set up in the BTS.

1X Max Forward CEs Occupied By Common Channels[entries]

1X Max Reverse CEs Occupied By Common Channels[entries]

1X Min Forward CEs Occupied By Common Channels[entries]

1X Min Reverse CEs Occupied By Common Channels[entries]

The BTS measures the maximum and minimum CEs occupied by the forward and reverse common channels in the measurement period. When you configure a forward or reverse common channel, the BTS must allocate a CE resource to the channel for decoding. Therefore, the maximum number of CEs occupied by the forward and reverse common channels is equal to the total number of forward and reverses common channels. In normal cases, the maximum value is equal to the minimum value.

1X Max Idle Forward CEs[entries]

1X Max Idle Reverse CEs[entries]

1X Min Idle Forward CEs[entries]

1X Min Idle Reverse CEs[entries]

The BTS measures the maximum and minimum forward and reverse idle CEs in a measurement period. After the BTS configuration, in the case of load or in the case of no service, the number of idle CEs = the number of CEs configured (available CEs) – the number of CEs occupied by the common channel –the number of CEs occupied by the traffic channel



License Performance Stat Table 4-29 lists measurement items about License Performance Stat.

Table 4-29 Measurement items about License Performance Stat.

Item Name Meaning Explanation

license-Restricted Call Rejection - 1X Forward CE Resource Overuse[Times]

Total times that the RAC fails to set up traffic channels for 1X calls due to insufficient forward CE resources

The RAC measures when it fails to assign radio resources on traffic channels due to insufficient forward CE resources.

license-Restricted Call Rejection - 1X Reverse CE Resource Overuse[Times]

Total times that the RAC fails to set up traffic channels for 1X calls due to insufficient reverse CE resources

The RAC measures when it fails to assign radio resources on traffic channels due to insufficient reverse CE resources.

license-Restricted Call Rejection – DO Reverse CE Resource Overuse[Times]

Total times that the RAC fails to set up traffic channels for DO calls due to insufficient reverse CE resources

The RAC measures when it fails to assign radio resources on traffic channels due to insufficient reverse CE resources.

4.3.2 PCH Performance Measurement

PCH Average Using Ratio [%] Item name: PCH Average Using Ratio [%] Item name: PCH average using ratio of a carrier within 30 minutes Item type: BTS measurement Formula: PCH Average Using Ratio [%] = Total length of paging messages sent from air

interface (bit)/Bandwidth of air interface (bit) x 100% Bandwidth of air interface = Paging rate x Measurement period

PCH Max/Min Using Ratio [%] Item name: PCH Max/Min Using Ratio [%] Item meaning: PCH maximum/minimum using ratio of a carrier within 30 minutes Item type: BTS measurement Analysis: The CCPM/CECM measures the PCH average using ratio every five minutes

and reports the result to the BTSC. The BTSC measures the PCH maximum using ratio of 30 minutes and reports the result to the OMC.





PCH OverHead Msg Using Ratio [%] Item name: PCH OverHead Msg Using Ratio [%] Item meaning: using ratio of overhead messages sent on PCHs of carriers within 30

minutes Item type: BTS measurement Formula: PCH Average Using Ratio [%] = PCH overhead message using ratio [%] =

Total length of overhead messages sent from air interface (bit)/Bandwidth of air interface (bit) x 100%, Bandwidth of air interface = Paging rate x Measurement period The total length of overhead messages sent from air interface does not include the length of those acting as fill messages. The CCPM/CECM measures the PCH overhead message using ratio every five minutes and reports the result to the BTSC. The BTSC averages the PCH overhead message using ratio of 30 minutes and reports the result to the OMC.

PCH Call/Noncall Msg Using Ratio [%] Item name: PCH Call/Noncall Msg Using Ratio [%] Item meaning: using ratio of overhead messages sent on PCHs of carriers within 30

minutes Item type: BTS measurement Analysis: A call message refers to a message related to the voice service, including

channels assignment message, GPM message, and ACK Order message. Analysis: A noncall message refers to a message not related to the voice service, for example, the short message. Formula: PCH call message using ratio [%] = Total length of call messages sent from air interface (bit)/Bandwidth of air interface (bit) x 100%, Bandwidth of air interface = Paging rate x Measurement period The CCPM/CECM measures the PCH call message using ratio every five minutes and reports the result to the BTSC. The BTSC averages the PCH call message using ratio of 30 minutes and reports the result to the OMC.

PCH Discarded Call/Noncall Msg Using Ratio [%] Item name: PCH Discarded Call/Noncall Msg Using Ratio [%] Item meaning: ratio of discarded call/noncall messages sent on PCHs within 30 minutes Item type: BTS measurement Formula: PCH discarded call/noncall msg using ratio [%] = Discarded call/noncall

messages owing to insufficient buffer/(Call/Noncall messages entering into the buffer + Discarded call/noncall messages owing to insufficient buffer) x 100%

PCH Delay Call/Noncall Slotted Msg Count [Piece] Item name: PCH Delay Call/Noncall Slotted Msg Count [Piece] Item name: PCH Delay Call/Noncall Slotted Msg Count [Piece] Item type: BTS measurement Unit: Piece Analysis: This item measures the call/noncall slotted messages sent on PCHs with

specific delay (1, 2, 3 or more) within 30 minutes. The CCPM/CECM measures this item every five minutes and reports the result to the BTSC. The BTSC calculates the total number of 30 minutes and reports the result to the OMC.



PCH Call/Noncall GPM Combine Num Count [Piece] Item name: PCH Call/Noncall GPM Combine Num Count [Piece] Item meaning: call/noncall slotted messages combined into a certain number of GPMs (0,

1, 2, 3 or more) within 30 minutes after sent on PCHs Item type: BTS measurement Unit: Piece Formula: PCH call/noncall GPM combine number count = PCH call/noncall GPM 0

combine number count + PCH call/noncall GPM 1 combine number count + PCH call/noncall GPM 2 combine number count + PCH call/noncall GPM 3 or more combine number count. The CCPM/CECM measures this item every five minutes and reports the result to the BTSC. The BTSC calculates the total number of 30 minutes and reports the result to the OMC.

4.3.3 ACH/EACH Performance Measurement Item name: ACH/EACH Max/Min/Average Using Ratio [%] Item name: ACH/EACH maximum/minimum/average using ratio of a carrier within 30

minutes Item type: BTS measurement Analysis:

− ACH/EACH Max/Min/Average Using Ratio [%] = MAX/MIN/ AVERAGE (Collision ratio + Valid access message using ratio). The measurement period is 2 seconds. ACH/EACH Max/Min/Average Using Ratio [%] is the maximum/minimum/average measurement results in the measurement period.

− Valid access message using ratio in a time unit = Valid access timeslots in a time unit/Total access timeslots in a time unit According to the ACH/EACH maximum/minimum/average using ratios reported by the CCPM/CECM, the BTSC calculates the ACH/EACH maximum/minimum/average using ratio of 30 minutes and reports it to the OMC.

Airbridge Radio Access Subsystem Performance Management Guide

5 Performance Data for Initial Measurement Point of CDMA2000 1xProblems



About This Chapter


Section Describes

5.1 Service Quality The performance data for the CDMA2000 1xEV-DO service quality measurement.

5.2 Traffic The performance data for the CDMA2000 1xEV-DO traffic measurement.

5.3 Resource Usage The performance data for the CDMA2000 1xEV-DO resource usage measurement.





5.1 Service Quality 5.1.1 Connection Performance

EV-DO Connection Performance Measurement-RAC The following three items are used to measure EV-DO connection performance measurement-RAC:

Connection Success Ratio[%] Quick Connection Success Ratio[%] Call Drop Ratio[%]

The item Connection Success Ratio[%] is described as follows:

Item name: Connection Success Ratio[%] Definition: Success ratio of all connections Item type: RAC performance measurement, RAC/carrier-level Formula: Connection Success Ratio[%]=([Connection Times]/[Connection

Requests]X100% = (([Successful AT-initiated Connection Times]+[Successful AN-initiated Connection Times])/([AT-Initiated Connection Requests]+[AN-Initiated Connection Requests]))X100%

Measurement point: The RAC performance measurement items measure the causes of RAC connection failure.

Table 5-1 lists the measurement items about RAC connection failure.

Table 5-1 Description of Connection Success Ratio



AT-initiated connection request fails. The AN measures when the AN fails to allocate the resource to the AT after receiving ConnectionRequest message. In this case, the AT does not send TrafficChannelAssignment message, as indicated by A in Figure 5-1.

AN-initiated connection request fails. The AN measures when the AN fails to allocate the resource to the AT after the AN sends the connection (including fast connection) request. In this case, the AT does not send TrafficChannelAssignment message, as indicated by C in Figure 5-2.

Check the radio resource configuration and the usage of Walsh codes and CE pool.





No R-TCH Detected

AT-initiated connection request fails. The AN measures when the access fails because the AN does not acquire AT R-TCH frames when the AN waits for TrafficChannelComplete message after sending the TrafficChannelAssignment message during the AT-initiated connection request, as indicated in C in Figure 5-1.

AN-initiated connection request fails. The AN measures when the access fails because the AN does not acquire AT R-TCH frames when waiting for the TrafficChannelComplete message after sending the TrafficChannelAssignment message during the AN-initiated connection request (including fast connection), as indicated by C in Figure 5-2.

Check the quality of the forward reverse link.

No Traffic Channel Complete received

AT-initiated connection request fails. The AN measures every time the AN receives no TrafficChannelComplete messages after sending a TrafficChannelAssignment message and acquiring AT R-TCH frames during the AN-initiated connection, as indicated by D in Figure 5-1.

AN-initiated connection request fails. The AN measures every time the AN receives no TrafficChannelComplete messages after sending a TrafficChannelAssignment message and acquiring AT R-TCH frames during the AN-initiated connection or fast connection, as indicated by H in Figure 5-1.

Check whether the radio environment is normal and the timer expires.

Table 5-2 lists the measurement items about fast connection failure.

Table 5-2 Measurement items about fast connection failure



The failure is caused by resource allocation during AN initiated fast connection. The AN measures when the AN fails to allocate resource to the AT after initiating fast connection request. In this case, the AT does not send the TrafficChannelAssignment message, as indicated by B in Figure 5-5.







No R-TCH Detected The fast connection fails because of no R-TCH detected. The AN measures every time the access fails because the AN does not acquire the AT R-TCH frames when the AN waits for the TrafficChannelComplete message after sending the TrafficChannelAssignment message during the fast connection request, as indicated by C in Figure 5-5.

Check the quality of the reverse link

No Traffic Channel Complete received

The AN does not receive the TrafficChannelComplete message during AN-initiated fast connection. The AN measures every time the AN receives no TrafficChannelComplete messages after sending a TrafficChannelAssignment message and acquiring AT R-TCH frames during the AN-initiated fast connection, as indicated by D in Figure 5-5.

Check whether the radio environment is normal and the timer expires.

Other causes Other causes (except the previous three causes) that cause the connection failure during the AN-initiated fast connection.

Check other items except the previous ones.

HRPD Session Performance Measurement-RAC The following items are used to measure HRPD session performance measurement-RAC:

HRPD Session Setup Success Ratio[%] Access Authentication Success Ratio[%] A13 Session Information Query Success Ratio[%] EV-DO Paging Success Ratio[%]

The item HRPD Session Setup Success Ratio is described as follows:

Item name: HRPD Session Setup Success Ratio[%] Definition: The successful ratio of setting up HRPD session between the AT and the AN Item type: RAC performance measurement, RAC/carrier-level Formula: HRPD Session Setup Success Ratio[%] = ([Successful HRPD Session

setup]/[HRPD Session setup Requests]) X 100% Measurement point: The RAC measurement items measure the causes of HRPD session

setup failure.




Table 5-3 lists the measurement items about HRPD Session Success Ratio.

Table 5-3 HRPD Session Setup Success RatioItem Name Meaning Solution

No HardwareID Request Sent

If the AN does not send the HardwareIDRequest message, the HRPD session setup fails. The AN measures every time it fails to process UATIRequest messages, as indicated by the B of Figure 5-1.

Check the interior system and the alarm information.

No HardwareID Response Received

If the AN does not receive the HardwareIDResponse message from the AT after sending the HardwareIDRequest message, the HRPD session setup fails. The AN measures every time:

The associated timer expires when the AN waits for HardwareIDResponse messages, as indicated by the D of Figure 5-1.

The AN receives a request to release HRPD sessions when waiting for the HardwareIDResponse messages, as indicated by the C of Figure 5-1.

Check the quality of the radio environment and forward/reverse links.

No UATIAssignment Sent

If the AN does not send the UATIAssignment message, the HRPD session setup fails. The AN measures every time:

The target AN fails to process the A13-Session Information Response messages during inter-AN handoffs.

The target AN receives an A13-Session Information Response message during inter-AN handoffs, as indicated by C in Figure 5-5.

The target AN receives a request to release the HRPD session request when waiting for the A13-Session Information Response/Reject message during inter-AN handoffs,, as indicated by D in Figure 5-5.

The associated timer expires when the A13-Session Information Response/Reject message times out during inter-AN handoffs, as indicated by E in Figure 5-5.

The AN fails to process the HardwareIDResponse message, as indicated by E in Figure 5-1.

Check the interior system and the alarm information.






No UATIComplete Received

If the AN does not receive the UATIComplete message from the AT after sending the UATIAssignment message, the HRPD session setup fails. The AN measures every time:

The associated timer expires when the AN waits for UATIComplete messages, as indicated by the H of Figure 5-1.

The AN receives a request to release HRPD sessions when waiting for UATIComplete messages, as indicated by the F of Figure 5-1.

Check whether the radio environment is normal.

Table 5-4 lists the measurement items about the causes of HRPD session release.

Table 5-4 Measurement items about the causes of HRPD session release


HRPD Session Released from AT

Normal closed. The AN measures every time the AT sends a SessionClose message with the release cause of Normal Close, as indicated by the A of Figure 5-3.

Protocol error. The AN measures every time the AT sends a SessionClose message with the release cause of Protocol Error, as indicated by the A of Figure 5-3.

Protocol configuration failure. The AN measures every time the AT sends a SessionClose message with the release cause of Protocol Configuration Failure, as indicated by the A of Figure 5-3.

Protocol negotiation error. The AN measures every time the AT sends a SessionClose message with the release cause of Protocol Negotiation Error, as indicated by the A of Figure 5-3.

Session configuration failure The AN measures every time the AT sends a SessionClose message with the release cause of Session Configuration Failure, as indicated by the A of Figure 5-3.

Others

Check the protocol configuration, Protocol negotiation, session configuration





…………….0……………………….

Configuration negotiation failure The AN measures every time it releases a session owing to configuration negotiation failures, as indicated by the A of Figure 5-4.

Keep alive timer expired The AN measures every time it releases a session owing to keep alive timer expired, as indicated by A in Figure 5-4.

MML operated The AN measures every time it releases a session owing to OAM intervention, as indicated by the A of Figure 5-4.

Authority failure The AN measures every time it releases a session upon receiving an A12 Access-Reject message from the AN-AAA, as indicated by the A of Figure 5-4.

Source AN release in inter AN handoff The AN measures every time the source AN releases a session upon receiving an A13-Session Information Confirm message, as indicated by the A of Figure 5-4.

The AN releases the session previously set up by the AT in the AN. The AN measures every time it releases an HRPD session previously set up by the AT in this AN, as indicated by A in Figure 5-4.

Others. If DO CFMRs are not configured, call releases may occur. Check the configuration.

Check the configuration negotiation and activate the timer.

Access Authentication Success Ratio

Item name: Access Authentication Success Ratio[%] Definition: The success ratio of access authentication from the AN to the AT. Item type: RAC performance measurement, RAC/carrier-level Formula: Access Authentication Success Ratio[%] = ([Successful Access

Authentications]/[Access Authentication Attempts]) x 100%

A13 Session Information Query Success Ratio

Item name: A13 Session Information Query Success Ratio[%] Definition: Success ratio of the target AN retrieving session information from the source

AN over the A13 interface during inter-AN handoffs Item type: RAC performance measurement, RAC/carrier-level Formula: A13 Session Information Query Success Ratio = Successful A13 Session

Information Queries / A13 Session Information Query Attempts x 100%





Measurement point: The RAC performance measurement items measure the causes of session information query failure. Table 5-5 lists the measurement items about Session Information Query Success Ratio.

Table 5-5 Measurement items about Session Information Query Success Ratio


A13 Session Information Query Failures (Rejected)

The target AN retrieves the session information over the A13 interface but are rejected by the source AN during inter-AN dormant handoffs. The AN measures every time the target AN receives an A13-Session Information Reject message, as indicated by the C of Figure 5-5.

Check whether the source AN has the session information.

A13 Session Information Query Failures (Other Causes)

Number of A13 session information query failures resulting from other causes except source AN rejection. The AN measures when the associated timer expires when the target AN waits for A13-Session Information Response/Reject messages, as indicated by the E of Figure 5-5. The target AN measures when receiving a request for releasing the HRPD session during waiting for Response/Reject messages, as indicated by the D of Figure 5-5.

Check whether the source AN has the session information.

EV-DO Paging Success Ratio

Item name: EV-DO Paging Success Ratio[%] Definition: Success ratio of AN EV-DO paging. Item type: RAC performance measurement, RAC/carrier-level Formula: Successful EV-DO Paging Times / EV-DO Paging Attempts x 100%




UATI Assignment Figure 5-1 shows the UATI assignment.

Figure 5-1 HRPD session performance measurement (UATI assignment)

UATIRequest

AN

HardwareIDRequest

HardwareIDResponse

AT

UATIAssignment

UATIComplete

A

G

B

D

E

H

In case of UATIRequest processing failure by the AN:

In case of successful UATIRequest processing by the AN:

In normal cases:

In case of waiting for HardwareIDResponse overtime:

Session CloseIn case of session release:

C

In normal cases:

In case of waiting for UATIComplete overtime:

In case of session release:

FSession Close

In normal cases:

UATIAssignment：

A: HRPD Session setup Requests G: Successful HRPD Session setup B: HRPD Session attempt Failures (No HardwareID Request Sent) C, D: HRPD Session attempt Failures (No HardwareID Response Received) E: HRPD Session attempt Failures (No UATIAssignment Sent) F, H: HRPD Session attempt Failures (No UATIComplete Received)





Access Authentication Figure 5-2 shows the access authentication.

Figure 5-2 HRPD session performance measurement (access authentication)

AN AAAAN

A12 Access-Request

A12 Access-Accept

A

B

A12 Access-Reject C

In case of access authentication success:

In case of access authentication reject:

A: Access Authentication Attempts B: Successful Access Authentications C: Access Authentication Rejections

HRPD Session Release Initiated by the AT Figure 5-3 shows the HRPD session release initiated by the AT that has the A8 connection.

Figure 5-3 HRPD session performance measurement (HRPD session release initiated by the AT)

SessionCose

PDSN

A9-Release-A8

AT AN PCF


A11-Registration Request

A11-Registration Reply

A

A: HRPD Session Released from AT (Normal closed) HRPD Session Released from AT (Protocol error) HRPD Session Released from AT (Protocol configuration failure)HRPD Session Released from AT (Protocol negotiation error)HRPD Session Released from AT (Session configuration failure)HRPD Session Released from AT (Others)

The measurement points of session release initiated by the AT that has the A8 connection are the same as those initiated by the AT that has not the A8 connection. In the session release initiated by the AT that has not the A8 connection, the A9-Release-A8 is replaced by the A9-Update-A8 message and the A9-Release-A8 Complete message is replaced by the A9-Update-A8 Ack message.




HRPD Session Release Initiated by the AN Figure 5-4 shows the HRPD session release initiated by the AN that has the A8 connection.

Figure 5-4 HRPD session performance measurement (HRPD session release initiated by the AN)

SessionClose

PDSN

A9-Release-A8

AT AN PCF


A11-Registration Request

A11-Registration Reply

SessionClose

A

HRPD Session Released from AN (Configure failed)HRPD Session Released from AN (Keep alive timer expired) HRPD Session Released from AN (MML operated) HRPD Session Released from AN (Authority failed)HRPD Session Released from AN (Source AN release in inter AN handoff) HRPD Session Released from AN (Release previously set up session in the AN) HRPD Session Released from AN (Others)

The measurement points of session release initiated by the AN that has the A8 connection are the same as those initiated by the AN that has not the A8 connection. In the session release initiated by the AN that has not the A8 connection, the A9-Release-A8 is replaced by the A9-Update-A8 message and the A9-Release-A8 Complete message is replaced by the A9-Update-A8 Ack message.





Inter-AN Dormant Handoff Figure 5-5 shows the inter-AN dormant handoff.

Figure 5-5 HRPD session performance measurement (inter-AN dormant handoff)

PDSN

A9-Setup-A8

AT TargetPCF

SourceAN

TargetAN

SourcePCF

UATIRequest

HardwareIDRequest

HardwareIDResponse

UATIAssignment

UATIComplete

A13-Session Information Request

A13-Session Information Response

A13-Session Information Confirm







A9-Release-A8-Complete

LocationNotification

LocationAssignment

LocationComplete

A

B

In case of Successful Retrieval of HRPD Session Information:

A13-Session Information RejectC

D Session Close

E

In case of HRPD session information transfer failure

In case of receiving HRPS session releaserequest when waiting for response:

In case of waiting for response overtime:

A: A13 Session Information Query Attempts B: Successful A13 Session Information Queries




C: A13 Session Information Query Failures (Rejected) HRPD Session attempt Failures (No UATIAssignment Sent)D, E: A13 Session Information Query Failures (Others) HRPD Session attempt Failures (No UATIAssignment Sent)

EV-DO Connection Performance Measurement-Carrier The measurement items of EV-DO Connection Performance Measurement-Carrier are used to measure a specified carrier. The measurement items of EV-DO Connection Performance Measurement-RAC are used to measure the RAC.

Besides the measurement items that are the same as those of EV-DO Connection Performance Measurement-RAC, EV-DO Connection Performance Measurement-Carrier has some specific items as listed in Table 5-6.

Table 5-6 Measurement items of EV-DO Connection Performance Measurement-Carrier

Item Name Measurement Point

Max Active Connectors of Carrier[Entries]

Number of maximum active connectors of the carrier. The radio resource management module measures the number of legs of the carrier on the following conditions:

Adding one leg. Removing one leg. Minute timer expires.

Min Active Connectors of Carrier[Entries]

Number of minimum active connectors of the carrier. The radio resource management module measures the number of legs of the carrier on the following conditions:

Adding one leg. Removing one leg. Minute timer expires.

HRPD Session Performance Measurement-Carrier The measurement items of HRPD Session Performance Measurement-Carrier are used to measure a specified carrier. The measurement items of HRPD Session Performance Measurement-RAC are used to measure the RAC. HRPD

Besides the measurement items that are the same as those of HRPD Session Performance Measurement-RAC, HRPD Session Performance Measurement-Carrier has a specific item as listed in Table 5-7.





Table 5-7 Measurement item of HRPD Session Performance Measurement-Carrier


EV-DO Access Channel Messages[Entries]

Number of messages that the AN receives on the access channels The AN measures every time it receives a message on the access channels.

5.1.2 IP Flow Performance

IP Flow Performance Measurement-RAC The following three compound items are used to measure IP flow performance measurement-RAC:

IP Flow Setup Success Ratio[%] IP Flow Drop Ratio[%] IP Flow Configuration Success Ratio[%]

IP Flow Setup Success Ratio

Item name: IP Flow Setup Success Ratio[%] Definition: Success ratio of all IP flows Item type: RAC performance measurement, RAC/carrier-level Formula: IP Flow Setup Success Ratio[%] = IP Flow Success[Times]/IP Flow Setup

Request[Times] x 100% = (AT Originate IP Flow Success[Times] + AN Originate IP Flow Success[Times])/(AT Originate IP Flow[Times] + AN Originate IP Flow[Times]) x 100%

Analysis: The causes of IP flow setup failures are put into specific categories. Table 4-6 lists the measurement items about IP Flow Setup Success Ratio with the real-time voice service as an example.

Table 5-8 Measurement items about IP Flow Setup Success Ratio with the real-time voice service as an example


AT Originate IP Flow (VOICE SERVICE)[Times]

The RAC measures when the AN receives ReservationOnRequest messages from the AT and the IP Flow in the messages is configured as real-time voice services. See A in Figure 5-6.

AT Originate IP Flow Fail (VOICE SERVICE)(Air interface resource apply fail) [Times]

The AN receives ReservationOnRequest messages from the AT, and the IP Flow in the messages is configured as real-time voice services. The RAC measures when the requests fail owing to the failure of air interface resource application. See B in Figure 5-6.





AT Originate IP Flow Fail (VOICE SERVICE)(Abis resource apply fail) [Times]

The AN receives ReservationOnRequest messages from the AT, and the IP Flow in the messages is configured as real-time voice services. The RAC measures when the requests fail owing to the failure of Abis interface resource application. See B in Figure 5-6.

AT Originate IP Flow Fail (VOICE SERVICE)(the rest of above) [Times]

The AN receives ReservationOnRequest messages from the AT, and the IP Flow in the messages to be released is configured as real-time voice services. The RAC measures when the requests fail for reasons other than the failure of the air interface application and Abis resource application. See B in Figure 5-6.

AN Originate IP Flow (VOICE SERVICE) [Times]

The RAC measures when the AN receives A9-BS Service Request messages from the PCF, and the IP Flow in the messages is configured as real-time voice services. See A in Figure 5-6.

AN Originate IP Flow Fail (VOICE SERVICE)(Air interface resource apply fail) [Times]

The AN receives A9-BS Service Request messages from the PCF, and the IP Flow in the messages is configured as real-time voice services. The RAC measures when the requests fail owing to the failure of air interface resource application. See B in Figure 5-6.

AN Originate IP Flow Fail (VOICE SERVICE)(Abis resource apply fail) [Times]

The AN receives A9-BS Service Request messages from the PCF, and the IP Flow in the messages is configured as real-time voice services. The RAC measures when the requests fail owing to the failure of Abis interface resource application. See A in Figure 5-6.

AN Originate IP Flow Fail (VOICE SERVICE)(the rest of above) [Times]

The AN receives A9-BS Service Request messages from the PCF, and the IP Flow in the messages is configured as real-time voice services. The RAC measures when the requests fail for reasons other than the failure of the air interface application and Abis resource application. See B in Figure 5-6.

AT Originate IP Flow Setup Success Ratio(VOICE SERVICE)[%]

N.A.

IP Flow Drop Ratio [%]

Item name: IP Flow Drop Ratio[%] Definition: drop ratio of all IP flows Item type: RAC performance measurement, RAC/carrier-level Formula: IP Flow Drop Ratio[%] = (IP Flow Release for Dormant Timer timeout [Times]

+ IP Flow Release for other reasons [Times])/(IP Flow Normal Release [Times] + IP Flow Release for Dormant Timer timeout [Times] + IP Flow Release for other reasons [Times]) x 100





Analysis: The causes of IP flow release are put into specific categories. Table 4-6 lists the measurement items about IP Flow Drop Ratio with the real-time voice service as an example.

Table 5-9 Measurement items about IP Flow Drop Ratio with the real-time voice service as an example


IP Flow Normal Release (VOICE SERVICE) [Times]

The RAC measures when the AN receives ReservationOffRequest messages from the AT, and the IP Flow in the messages is configured as real-time voice services. See A in Figure 5-6.

IP Flow Release for Dormant Timer timeout (VOICE SERVICE) [Times]

The RAC measures when the RLP dormant timer expires. See A in Figure 5-6.

IP Flow Release for other reasons (VOICE SERVICE) [Times]

The RAC measures when successfully set-up IP Flow for real-time voice services is released for reasons other than normal releases and dormant timer expiry.

IP Flow Configuration Success Ratio

Item name: IP Flow Configuration Success Ratio [%] Definition: Ratio of successful IP Flow configurations Item type: RAC performance measurement, RAC/carrier-level Formula: IP Flow Configuration Success Ratio[%] = (IP Flow Configuration Applied

[Times] – IP Flow Configuration Failed (the Configuration applied by AT is not rational) [Times] – IP Flow Configuration Failed (GAUP Configuration Fail) [Times] – IP Flow Configuration Failed (the rest of above) [Times])/IP Flow Configuration Applied [Times]×100

Analysis: The causes of RAC-level connection performance failures are put into specific categories. Table 5-10 lists the measurement items about IP Flow Configuration Success Ratio.

Table 5-10 Measurement items about IP Flow Configuration Success Ratio


IP Flow Configuration Applied [Times]

The RAC measures when the AN receives AttributeUpdateRequest messages from the AT and configures the IP Flow as requested by subscribers. See A in Figure 5-10.

IP Flow Configuration Failed (the Configuration applied by AT is not rational) [Times]

The AN receives AttributeUpdateRequest messages from the AT and configures the IP Flow as requested by subscribers. The RAC measures when IP Flow configuration fails owing to irrational configuration requests from the AT. See B in Figure 5-10.





IP Flow Configuration Failed (GAUP Configuration Fail) [Times]

The AN receives AttributeUpdateRequest messages from the AT and configures the IP Flow as requested by subscribers. The RAC measures when IP Flow configuration fails owing to the failures of GAUP configuration. See C in Figure 5-10.

IP Flow Configuration Failed (the rest of above) [Times]

The AN receives AttributeUpdateRequest messages from the AT and configures the IP Flow as requested by subscribers. The RAC measures when IP Flow configuration fails for reasons other than irrational configuration requests and the failures of GAUP configuration.

AT-Originated IP Flow Setup Figure 5-6 shows the Performance Stat of RAC IP Flow Setup (AT-originated).

Figure 5-6 Performance Stat of RAC IP Flow Setup (AT-originated)

PDSN

A9-Setup-A8

AT



ReservationOnRequest

A9-Connect-A8

AN AAA PCFAN

ReservationAccept

A

Apply forresources

B

Success:

Failures:

A9-Update-A8

A9-Update-A8 AckC

A: AT originate IP Flow Setup Requests [Times] B: AT Originate IP Flow Fail (Air/Abis interface resource apply fail) [Times] C: AT Originate IP Flow Success [Times]





AN-Originated IP Flow Setup Figure 5-7 shows the Performance Stat of RAC IP Flow Setup (AN-originated).

Figure 5-7 Performance Stat of RAC IP Flow Setup (AN-originated)

PDSN

A9-Setup-A8

AT




A9-Connect-A8

AN AAA PCFAN

ReservationAcceptFwdReservationAck

A

Apply forresources

B

Success:

Failure:

A9-Update-A8

A9-Update-A8 AckC

FwdReservationOnRevReservationOn

A: AN originate IP Flow Setup Requests [Times] B: AN Originate IP Flow Fail (Air/Abis interface resource apply fail) [Times] C: AN Originate IP Flow Success [Times]




AT-Originated IP Flow Release Figure 5-8 shows the Performance Stat of RAC IP Flow Release (AT-originated).

Figure 5-8 Performance Stat of RAC IP Flow Release (AT-originated)

ReservationOffRequest

PDSN

A9-Release-A8

AT AN PCF




A

ReservationAccept

Internal resourcesrelease

A: IP Flow Normal Release [Times]

AN-Originated IP Flow Release Figure 5-9 shows the Performance Stat of RAC IP Flow Release (AN-originated).

Figure 5-9 Performance Stat of RAC IP Flow Release (AN-originated)

FwdReservationOffRevReservationOff

PDSN

A9-Release-A8

AT AN PCF




A

ReservationAcceptFwdReservationAck

Dormancy timer expiry

Internal resourcesrelease

A: IP Flow Release for Dormant Timer timeout [Times]





IP Flow Configuration Figure 5-10 shows the Performance Stat of RAC IP Flow Configuration.

Figure 5-10 Performance Stat of RAC IP Flow Configuration

AttributeUpdateRequest

AT AN

A

GAUP process

B

C

A: IP Flow Configuration Applied [Times] B: IP Flow Configuration Failed (the Configuration applied by AT is not rational) [Times] C: IP Flow Configuration Failed (GAUP Configuration Fail) [Times]

5.1.3 Congestion Ratio

Successful Different Frequency Assignments Item name: Successful Different Frequency Assignments Definition: Times of successful different-frequency assignments for the MS. Item type: compound item Measurement method: by calculation Measurement point: The RAC measures when it receives a connection request.

Successful Different Frequency Assignments-Assigned CarrierItem name: Successful Different Frequency Assignments-Assigned Carrier

Definition: If the access carrier is not the assigned carrier, the RAC increments this item of the assigned carrier by 1.

Item type: Original item Measurement method: By accumulation Measurement point: The RAC measures when it receives a connection request, as

indicated by the A in Figure 5-11.




Successful Different Frequency Assignments-Access CarrierItem name: Successful Different Frequency Assignments-Access Carrier

Definition: If the access carrier is not the assigned carrier, the RAC increments this item of the assigned carrier by 1.

Item type: Original item Measurement method: By calculation Measurement point: The RAC measures when it receives a connection request, as

indicated by the A in Figure 5-11.





AT Calling Process Figure 5-11 shows the flowchart of the AT calling process.

Figure 5-11 Flowchart of the AT calling process

A: Successful Different Frequency Assignments-Assigned Carrier Successful Different Frequency Assignments-Access Carrier




5.1.4 Soft Handoff Performance

EV-DO Reverse Channel Soft-Handoff Performance Measurement-RAC The measurement items of EV-DO Reverse Channel Soft-Handoff Performance Measurement-Carrier are used to measure a specified carrier. The measurement items of EV-DO Reverse Channel Soft-Handoff Performance Measurement-RAC are used to measure the RAC.

Intra-BS Soft HO Success Ratio can show the intra-RAC soft handoff (HO) performance by measuring:

Soft HO requests Soft HO failure causes Successful soft HOs

The description of this item is as follows:

Item name: Intra-BS Soft HO Success Ratio Definition: success ratio of intra-BS soft HOs for adding legs and deleting legs Item type: RAC performance measurement, RAC/carrier-level Formula: Intra-BS Soft HO Success Ratio = ([Successful Intra-BS Soft HO

EV-DO]/[Intra-BS Soft HO Requests-EV-DO]) x 100% Measurement point: The cBSS performance measurement items measure the causes of

Intra-RAC soft HO failure.

Table 5-11 lists the measurement items about Intra-BS Soft HO Success Ratio.

Table 5-11 Measurement items about Intra-BS Soft HO Success Ratio


Intra-BS Soft HO Failures(Radio resources unavailable)

The RAC triggers soft HOs after receiving a TrafficChannelComplete messages, checks the number of soft HO leg failures, and analyzes failure causes, as indicated by C in Figure 5-12. Carriers for HO legs are unavailable.

The number of logical channels on carriers exceeds the specified number.

There is no remaining physical reverse channel element.


Intra-BS Soft HO Failures(Requested Abis resources unavailable)

The RAC triggers soft HOs after receiving a TrafficChannelComplete messages, checks the number of soft HO leg failures, and analyzes failure causes. The terrestrial resource includes the BTS, CBIE, CFMR, and TIE.







Intra-BS Soft HO Failures (Radio interface abnormal)[Times]

If the RAC receives no TrafficChannelComplete messages after triggering soft HO, the following two cases may occur: The MS receives no

TrafficChannelAssignment messages. The BTS receives no TrafficChannelComplete messages.


Intra-BS Soft HO Failures (Other causes)[Times]

The RAC measures when an inter-BS HO fails resulting from the other causes, as indicated by C in Figure 5-12.


Soft Handoff/Softer Handoff Figure 5-12 shows the flowchart of soft handoff/softer handoff.

Figure 5-12 Flowchart of soft handoff/softer handoff

RouteUpdate

ANAT

TrafficChannelAssignment

TrafficChannelComplete

A

DTimeout occurs when the BSC wait for the

TrafficChannelComplete message

B

CHandoff analysis based on theTrafficChannelComplete message

Normal condition


A: Intra-BS Soft HO requests EV-DO B: Times of Sending TCA for Intra-BS Soft HO C: Successful Intra-BS Soft HO EV-DO Intra-BS Soft HO Failures (Radio resources unavailable) EV-DO Intra-BS Soft HO Failures (Requested Abis resources unavailable) EV-DOIntra-BS Soft HO Failures (Other causes) D: D: Intra-BS Soft HO Failures (Radio interface abnormal)




5.1.5 Intra-AN Hard Handoff Performance

EV-DO Intra-AN Hard Handoff Performance Measurement-RAC EV-DO Intra-AN Hard Handoff Performance Measurement-RAC can show the intra-AN hard handoff performance by measuring Hard HO requests,Hard HO failure causes and Successful Hard Hos.

Item name: Intra-AN Hard HO Success Ratio [%] Item meaning: success ratio of inter-AN hard HOs Item type: RAC performance measurement, RAC/carrier-level Formula: Intra-AN Soft HO Success Ratio = ([Successful Intra-AN Hard HO]/[Intra-AN

Hard HO Requests]) x 100% Measurement point: The RAC performance measurement items measure the causes of

Intra-AN hard HO failure. Table 5-12 lists the measurement items about Intra-AN Hard HO Success Ratio.

Table 5-12 Measurement items about Intra-AN Hard HO Success Ratio


Intra-AN Hard HO Requests The AN measures when the radio resource management module determines to trigger hard handoffs. See A of Figure 5-13.

Successful Intra-AN Hard HOs The AN measures when the it receives the TrafficChannelComplete message, as indicated by D in Figure 5-13.

Intra-AN Hard HO Failures (Radio resources unavailable)[Times]

The radio resource management module determines to trigger hard handoffs. The target call management module measures when hard handoffs fail due to unavailability of radio resources. See B of Figure 5-13.

Intra-AN Hard HO Failures (Requested terrestrial resources unavailable) [Times]

The radio resource management module determines to trigger hard handoffs. The target call management module measures when hard handoffs fail due to unavailability of requested terrestrial resources. See B of Figure 5-13.

Intra-AN Hard HO Failures (MS Not detected by destination pilot) [Times]

The radio resource management module determines to trigger hard handoffs. The target call management module measures when hard handoffs fail due to the failures of the destination pilot to detect the MS. See C of Figure 5-13.

Intra-AN Hard HO Failures (Other causes) [Times]

The radio resource management module determines to trigger hard handoffs. The target call management module measures when hard handoffs fail due to causes other than:

Unavailability of radio resources Unavailability of requested terrestrial resources Failures of the destination pilot to detect the MS





Flowchart of EV-DO Intra-AN Hard Handoff Performance Measurement-RAC Figure 5-13 shows the EV-DO Intra-AN Hard Handoff Performance Measurement-RAC.

Figure 5-13 EV-DO Intra-AN Hard Handoff Performance Measurement-RAC

AT AN

HardHandoffTriggered

ResourceRequest

SucceedFail

TrafficChannelAssignment

MS Detection byDestinationPilot

TrafficChannelComplete

A

B

C

D

Succeed

Fail

A: Intra-AN Hard HO Requests B: Intra-AN Hard HO Failures (Radio resources unavailable)[Times]

Intra-AN Hard HO Failures (Requested terrestrial resources unavailable) [Times] C: Intra-AN Hard HO Failures (MS Not detected by destination pilot) [Times] D: Successful Intra-AN Hard HOs

5.2 Traffic 5.2.1 TCH Traffic Performance Measurement

DO 0 Traffic Channel Connection Total time(DO 0/DO A) [Second]Item name: DO 0 Traffic Channel Connection Total time(DO 0/DO A) [Second]

Definition: Duration that all the DO 0 or DO A calls seize TCHs. Unit: Second Item type: RAC performance measurement, RAC/carrier-level Measurement: By accumulation Measurement point: Every second (a current unit) the RAC measures this item for each

call. If a call seizes TCHs, the RAC increments this item by 1. TCH Seizure Duration-RAC does not involve handoff. TCH Seizure Duration-Carrier measures each carrier.




The CDMA2000 1Xev-Do Rev.A system provides different types of services. In performance measurement of the V200R003 version, the seizure duration of the TCH can be measured by service type with the following items:

Traffic Channel Connection Total time(VOIP)[Second] Traffic Channel Connection Total time(VT)[Second] Traffic Channel Connection Total time(GAME)[Second] Traffic Channel Connection Total time(SIP)[Second] Traffic Channel Connection Total time(STREAM)[Second] Traffic Channel Connection Total time(BE)[Second]

5.2.2 CE Traffic Performance Measurement

DO 0/DO A Traffic Channel CE Total time(DO 0/DO A) [Second] Item name: DO 0/DO A Traffic Channel CE Total time(DO 0/DO A) [Second] Definition: Duration that TCHs used for DO 0 or DO A calls occupy CEs. Unit: Second Item type: RAC performance measurement, RAC/carrier-level Measurement method: By accumulation Measurement point: Every second (a current unit) the RACC measures this item for each

call. If a call seizes TCHs, the RACC increments this item by 1. This item is measured for each carrier.

TCH CE seizure duration has performance measurement items that are measured independently by service type, similar to the measurement of TCH connection seizure duration.

5.2.3 MAC Index Traffic Performance Measurement

DO 0/DO A Traffic Channel MAC Index Total time(DO 0/DO A) [Second] Item name: DO 0/DO A Traffic Channel MAC Index Total time(DO 0/DO A) [Second] Definition: Duration that TCHs used for DO 0 or DO A calls occupy MAC Indexes. Unit: Second Item type: RAC performance measurement, RAC/carrier-level Measurement method: By accumulation Measurement point: Every second (a current unit) the RACC measures this item for each

call. If a call seizes TCHs, the RACC increments this item by 1. This item is measured for each carrier.





TCH MAC Index seizure duration has performance measurement items that are measured independently by service type, similar to the measurement of TCH connection seizure duration.

5.2.4 DO Traffic Performance Measurement

DO Max Ach One Way Delay[km] Item name: DO Max Ach One Way Delay[km] Definition: The maximum one way delay of DO ACH within 30 minutes Unit: km Item Type: BTC measurement Measurement point: One way delay refers to the delay from the MS to the channels

processing chip set on the CECM, excluding the transmission delay from the antenna feeder system to the channels processing chip set. The BTSC measures the one way delay reported by the CECM and calculates the maximum one way delay of 30 minutes, which indicates the longest distance from an MS to the BTS. The measurement object is a specific carrier

DO ACH Region (n km to n+1 km) Call Count[piece] Item name: DO ACH Region (n km to n+1 km) Call Count[piece] Definition: The successful call count in DO ACH region (n km to n+1 km) Unit: Piece Item type: BTS measurement Measurement point: The MC module measures the one way delay reported by the CECM

and calculates separately the call count of 30 minutes in the region from n km to n+1 km (0≤n≤60) and that in the region beyond 60 km. The measurement object is a specific carrier.

DO FTCH 38. 4k 16Slot Sent Packet Count [Packet] Item name: DO FTCH 38. 4k 16Slot Sent Packet Count [Packet] Definition: Total packets sent at a 38. 4 kbit/s on 16 timeslots on DO FTCHs within 30

minutes Unit: Packet Item type: BTS measurement Measurement point:

− The CECM measures this item for each QoS level (1–7) separately. − The CECM measures the number of packets sent at a 38. 4 kbit/s rate on 16 timeslots

on DO FTCHs every minute. The MC module calculates the total number within 30 minutes and reports it to the OMC




RTCH 9. 6k Received Packet Count [Packet] Item name: RTCH 9. 6k Received Packet Count [Packet] Definition: Total packets received at a 9. 6 kbit/s rate on DO FTCHs within 30 minutes Unit: Packet Item type: BTS measurement Measurement point: DO RTCH 9. 6k Received Packet Count [packet] = DO RTCH 1X

Single Branch Received Packet Count [packet] + DO RTCH 1X Soft Handoff Branch Received Packet Count [packet] + DO RTCH 1X Softer Handoff Branch Received Packet Count [packet] + DO RTCH 1X Soft-Softer Handoff Branch Received Packet Count [packet]

Table 5-13 lists the other items of the same kinds.

Table 5-13 Other items of the same kinds

Item Name Item Type Measurement Method Unit

DO FTCH 76.8 k 8 Slot Sent Packet Count [Packet]

Original item By accumulation Packet





















DO FTCH 1536 k 2 Slot Sent Packet Count [Packet]


DO FTCH 3072 k 1 Slot Sent Packet Count [Packet]






DO FTCH 1536 k 2 Slot Sent Packet Count [Packet] and DO FTCH 3072 k 1 Slot Sent Packet Count [Packet] are two newly added items for the forward EV-DO Rev.A TCH.

RTCH Rel.0 9.6k Received Packet Count [Packet] Item name: RTCH 9.6k Received Packet Count [Packet] Definition: Total packets received at a 9.6 kbit/s rate on DO FTCHs within 30 minutes Unit: Packet Item type: BTS measurement Measurement point: DO RTCH 9.6k Received Packet Count [packet] = DO RTCH 1X

Single Branch Received Packet Count [packet] + DO RTCH 1X Soft Handoff Branch Received Packet Count [packet] + DO RTCH 1X Softer Handoff Branch Received Packet Count [packet] + DO RTCH 1X Soft-Softer Handoff Branch Received Packet Count [packet]

Table 5-14 lists the other items of the same kind.

Table 5-14 Other items of the same kinds

Item Name Item Type Measurement Method

Unit

DO RTCH 19.2.6k Received Packet Count [Packet]






DO RTCH 153.6k Received Packet Count [Packet]


RTCH Rev.A 128-bit Received Packet Count [Packet] Item name: RTCH Rev.A 128-bit Received Packet Count [Packet] Definition: Total 128-bit packets received on DO Rev.A RTCHs within 30 minutes Unit: Packet Item type: BTS measurement Measurement point: RTCH Rev.A 128-bit Received Packet Count [Packet] = DO RTCH

Single Branch Received 128-bit Packet Count [packet] + DO RTCH Soft Handoff Branch Received 128-bit Packet Count [packet] + DO RTCH Softer Handoff Branch Received 128-bit Packet Count [packet] + DO RTCH Soft-Softer Handoff Branch Received 128-bit Packet Count [packet]





Table 5-15 Other items of the same kind


DO RTCH Single Branch Received 128-bit Packet Count [packet]


DO RTCH Soft Handoff Branch Received 128-bit Packet Count [packet]


DO RTCH Softer Handoff Branch Received 128-bit Packet Count [packet]


DO RTCH Soft and Softer Handoff Branch Received 128-bit Packet Count [packet]
























































DO RTCH PER Performance Stat Table 5-16 lists the items about DO RTCH PER Performance Stat.

Table 5-16 Items about DO RTCH PER Performance Stat


DO RTCH Total Average PER [0. 10%]

In 30 minutes, the BTS measures: DO RTCH Single Branch Average PER [0. 10%] DO RTCH Soft Handoff Branch Average PER [0. 10%]

DO RTCH Softer Handoff Branch Average FER [0. 10%]

DO RTCH Soft-Softer Handoff Branch Average PER [0. 10%]

The BTS measures the average PER and then measures the reverse convergence. If the PER is greater than the target value, adjust the power control parameter. In normal cases, the PER increases because of poor coverage, pilot pollution, and interference.






Received Packet Count[packet]

In 30 minutes: the BTS measures: DO RTCH Single Branch Received Packet Count [Packet]

DO RTCH Soft Handoff Branch Received Packet Count [Packet]

DO RTCH Softer Handoff Branch Received Packet Count [Packet]

DO RTCH Soft-Softer Handoff Branch Received Packet Count [Packet]

DO RTCH 1X Soft-Softer Handoff Branch Received Packet Count[packet]

DO RTCH 1X Single Branch Received Packet Count[packet]






The BTS measures the number of packets received.

Max/Min FER In 30 minutes, the BTS measures: FCH Single Branch Max FER[0. 10%] FCH Single Branch Min FER[0. 10%] FCH Soft Handoff Branch Max FER [0. 10%] FCH Soft Handoff Branch Min FER [0. 10%] FCH Softer Handoff Branch Max FER [0. 10%] FCH Softer Handoff Branch Min FER [0. 10%] FCH Soft-Softer Handoff Branch Max FER [0. 10%] FCH Soft-Softer Handoff Branch Min FER [0. 10%]

Max/Min PER indicates the PER value range. If the PER value exceeds the value range, adjust the power control parameters or expand the system capacity.

Average Eb/Nt In 30 minutes, the BTS measures: DO RTCH Single Branch Average Eb/Nt [0. 125 dB]

DO RTCH Soft Handoff Branch Average Eb/Nt [0. 125 dB]

DO RTCH Softer Handoff Branch Average Eb/Nt [0. 125 dB]

DO RTCH Soft-Softer Handoff Branch Average Eb/Nt [0. 125 dB]

Average Eb/Nt is the intermediate variable of the power control. You can compare it with the specified maximum value and minimum value to decide whether the maximum value and minimum value are proper.





Max/Min Eb/Nt In 30 minutes, the BTS measures: DO RTCH Single Branch Max Eb/Nt [0. 125 dB] 10. 24 DO RTCH Single Branch Min Eb/Nt [0. 125 dB]

DO RTCH Softer Handoff Branch Max Eb/Nt [0. 125 dB]

DO RTCH Softer Handoff Branch Min Eb/Nt [0. 125 dB]

DO RTCH Soft-Softer Handoff Branch Max Eb/Nt [0. 125 dB]

DO RTCH Soft-Softer Handoff Branch Min Eb/Nt [0. 125 dB]

Max/Min Eb/Nt indicates the value range of the Eb/Nt.

5.2.5 Throughput

Forward Octets Between PCF and RAC[KB] Item name: Forward Octets Between PCF and RAC[KB] Definition: Downlink data that the RAC receives from the PCF. Unit: KB Item type: RAC level and FRAME level Measurement method: By accumulation Measurement point: The RAC measures the payload when it receives downlink data

from the PCF.

Reverse Octets Between PCF and RAC[KB] Item name: Reverse Octets Between PCF and RAC[KB]Definition: Octets that the RAC

sends to the PCF. Unit: KB Item type: FRAME level Measurement method: By accumulation Measurement point: The RAC measures when it sends data to the PCF on the RLP

sub-layer.

Forward Broadcast-Multicast Service Lost Count Between PCF and RAC[Times] Item name: Forward Broadcast-Multicast Service Lost Count Between PCF and

RAC[Times] Definition: Times that the RAC discards PPP packets due to the wrong frame number. Unit: Time Item type: FRAME level Measurement method: By accumulation





Measurement point: The RAC measures when it discards PPP packets due to the wrong frame number.

Forward Broadcast-Multicast Service Octets Between PCF and RAC[Byte] Item name: Forward Broadcast-Multicast Service Octets Between PCF and RAC[Byte] Definition: Forward BCMCS data that the RAC receives from the PCF. Unit: Byte Item type: FRAME level Measurement method: By accumulation Measurement point: The RAC measures when it receives forward BCMCS data from the

PCF.

Adjusting Packets Count Between RAC and PCF[Times] Item name: Adjusting Packets Count Between RAC and PCF[Times] Definition: Times that the RAC sends adjusting packets to the PCF. Unit: Time Item type: FRAME level Measurement method: By accumulation Measurement point: The RAC measures when it sends adjusting packets to the PCF.

Discarded PPP Packet Count RAC Item name: Discarded PPP Packet Count Definition: Times that the RAC discards PPP packets due to its own reasons. Unit: Time Item type: FRAME level Measurement method: By accumulation Measurement point: The RAC measures when it receives forward PPP packets from the

PCF but discards the PPP packets due to its own reasons.

Discarded Octets by RAC Item name: Discarded Octets by RAC Definition: PPP packets that the RAC discards due to its own reasons. Unit: Byte Item type: FRAME level Measurement method: By accumulation Measurement point: The RAC measures when it receives forward PPP packets from the

PCF but discards the PPP packets due to its own reasons.

Discarded PPP Packet Count For Error PID By RAC[Times] Item name: Discarded PPP Packet Count For Error PID By RAC[Times] Definition: Times that the RAC discards PPP Packets due to error PID. Unit: Time Item type: FRAME level Measurement method: By accumulation




Measurement point: The RAC measures when it receives forward PPP packets from the PCF but discards due to error PID.

Discarded Octets For Error PID By RAC[Byte] Item name: Discarded Octets For Error PID By RAC[Byte] Definition: PPP Packets that the RAC discards due to error PID. Unit: Byte Item type: FRAME level Measurement method: By accumulation Measurement point: The RAC measures when it receives forward PPP packets from the

PCF but discards due to error PID.

Forward Broadcast-Multicast Service Octets By RAC[Byte] Item name: Forward Broadcast-Multicast Service Octets By RAC[Byte] Definition: Forward BCMCS data that the RAC receives from the PCF. Unit: Byte Item type: FRAME level Measurement method: By accumulation Measurement point: The RAC measures when it receives forward BCMCS data from the

PCF.

Octets Received but Not Sent on Forward Channels[KB] Item name: Octets Received but Not Sent on Forward Channels[KB] Definition: Data that the CFMR receives but not yet sends. Unit: KB Item type: RAC level and FRAME level Measurement method: By calculation Formula: Forward Octets Between PCF and RAC [kB] – RLP Octets Sent on Forward

Channels [kB] - Forward Lost RLP Octets [Byte]/1024

RLP Octets Sent on Forward Channels(Excluding those resent)[KB] Item name: RLP Octets Sent on Forward Channels(Excluding those resent)[KB] Definition: Octets that the RAC sends to the AT on the RLP sub-layer Unit: KB Item type: RAC level and FRAME level Measurement method: By accumulation Measurement point: The RAC measures every time it sends the forward data to the AT

on the RLP sub-layer, excluding the data resent.

RLP Octets Resent on Forward Channels[Byte] Item name: RLP Octets Resent on Forward Channels[Byte] Definition: Octets that the RAC resends on forward channels of the RLP sub-layer Unit: Byte





Item type: RAC level and FRAME level Measurement method: By accumulation Measurement point: The RAC measures every time it sends octets on forward channels

of the RLP sub-layer.

RLP Access Octets Sent on Forward Channels[Byte] Item name: RLP Access Octets Sent on Forward Channels[Byte] Definition: Access flow data that the RAC sends on forward channels of the RLP

sub-layer Unit: Byte Item type: RAC level and FRAME level Measurement method: By accumulation Measurement point: The RAC measures when it sends access flow data on forward


Forward Lost RLP Octets[Byte] Item name: Forward Lost RLP Octets[Byte] Definition: Upper layer data that the RAC receives on the RLP sub-layer but discards

due to buffer failure Unit: Byte Item type: RAC level and FRAME level Measurement method: By accumulation Measurement point: The RAC measures when it discards data due to buffer failure upon

receiving upper layer data on the RLP sub-layer.

RLP Octets Received on Reverse Channels[KB] Item name: RLP Octets Received on Reverse Channels[KB] Definition: Data that the RAC receives on reverse channels of the RLP sub-layer. Unit: KB Item type: RAC level and FRAME level Measurement method: By accumulation Measurement point: The RAC measures when it receives octets on the reverse channel of

the RLP sub-layer, including those resent. RLP Access Octets Received on Reverse Channels[Byte]

Item name: RLP Access Octets Received on Reverse Channels[Byte] Definition: Access flow data that the RAC receives on reverse channels of the RLP

sub-layer. Unit: Byte Item type: RAC level and FRAME level Measurement method: By accumulation Measurement point: The RAC measures when it receives access flow data on reverse





Reverse Lost RLP Octets[Byte] Item name: Reverse Lost RLP Octets[Byte]Definition: Uplink data that the RAC

discards due to data error after receiving the reverse data on the RLP sub-layer Unit: Byte Item type: FRAME level Measurement method: By accumulation Measurement point: The RAC measures every time it cannot distinguish the data frame

(excluding those resent) when processing the reverse data on the RLP sub-layer.

Packet Discarded for Insufficient Buffer[Byte] Item name: Packet Discarded for Insufficient Buffer[Byte] Definition: Amount of upper data discarded because of forward buffer insufficiency. The

RAC assigns a permanent buffer on the RLP sub-layer to each suRACriber to buffer data from the PCF.

Unit: Byte Item type: RAC Measurement method: By accumulation Measurement point: The RAC measures when it discards the PCF data (received on the

RLP sub-layer) because of forward buffer insufficiency.

Packet Discarded for Unknown AT[Byte] Item name: Packet Discarded for Unknown AT[Byte] Definition: Amount of reverse RLP data that the RAC receives on the RLP sub-layer but

discards because it fails to identify ATs Unit: Byte Item type: RAC Measurement method: By accumulation Measurement point: The RAC measures when it fails to identify an AT after receiving

reverse service data packets from the AT on the RLP sub-layer

Octets Resent on Request of AT[Byte] Item name: Octets Resent on Request of AT[Byte] Definition: Octets that the AT send a NAK messages to request the AN to resend. Unit: Byte Item type: FRAME level Measurement method: By accumulation Measurement point: The RAC measures when it receives a NAK message from an AT

from the RLP sub-layer.

Octets Resent on request of AN[Byte] Item name: Octets Resent on Request of AN[Byte] Definition: Octets that the AN send a NAK messages to request the AT to resend. Unit: Byte Item type: FRAME level





Measurement method: By accumulation Measurement point: The AN sends NAK messages on the RLP sub-layer through the

RAC to the AT. The NAK messages carry the octets that the AN requests the AT to resend. The RAC measures when the AN sends the NAK messages to the AT.

Reverse Link Frame Count(rate 1/2/3/4/5/6)[Entries] Item name: Reverse Link Frame Count(rate 1/2/3/4/5/6)[Entries] Definition: Number of frames on R-TCHs at the rate of 1 (9. 6 kbit/s)/2 (19. 2 kbit/s)/3

(38. 4 kbit/s)/4 (76. 8 kbit/s)/5 (153. 6 kbit/s) that the selection/distribution unit (SDU) receives.

Unit: Frame Item type: RAC Measurement method: By accumulation Measurement point: The RAC measures when the SDU receives the R-TCH frames at

the rate of 9. 6 kbit/s, 19. 2 kbit/s, 38. 4 kbit/s, 76. 8 kbit/s, 153. 6 kbit/s. The frames of different rates that the SDU receives on the reverse link are all frames on the physical layer.

5.2.6 EVDO Rev.A QoS Performance Measurement

Best Effort Service Forward Error Bytes Item name: Best Effort Service Forward Error Bytes[Byte] Definition: at the RLP sublayer of the RAC, best effort service bytes that the AT request

to be retransmitted Unit: Byte Item type: RAC level Measurement method: By accumulation Measurement point: The RAC measures when the RLP sublayer receives NAK requests

from the AT.

Best Effort Service Forward Bytes Item name: Best Effort Service Forward Bytes Definition: forward best effort service bytes that the RLP sublayer of the RAC transmits

(including retransmitted bytes) Unit: Byte Item type: RAC level Measurement method: By accumulation Measurement point: The RAC measures when the RLP sublayer transmits forward best

effort service bytes.

Best Effort Service Reverse Error Bytes Item name: Best Effort Service Reverse Error Bytes[Byte] Definition: all the reverse best effort service bytes that the RLP sublayer of the RAC

receives Unit: Byte




Item type: RAC level Measurement method: By accumulation Measurement point: The RAC measures when the RLP sublayer sends the NAK message

to request the reverse best effort service bytes to be retransmitted.

Best Effort Service Reverse Bytes Item name: Best Effort Service Reverse Bytes[Byte] Definition: at the RLP sublayer of the RAC, best effort service bytes that the AN request

to be retransmitted Unit: Byte Item type: RAC level Measurement method: By accumulation Measurement point: The RAC measures when the RLP sublayer receives reverse best

effort service bytes.


Table 5-17 Other items of the same kind


Media Stream Forward Error Bytes[Byte]


Media Stream Forward Bytes[Byte]


Media Stream Reverse Error Bytes[Byte]


Media Stream Reverse Bytes[Byte]


Signal Forward Error Bytes[Byte]


Signal Forward Bytes[Byte] Original item By accumulation Packet

Signal Reverse Error Bytes[Byte]


Signal Reverse Bytes[Byte] Original item By accumulation Packet

Interactive Game Forward Error Bytes[Byte]


Interactive Game Forward Bytes[Byte]


Interactive Game Reverse Error Bytes[Byte]


Interactive Game Reverse Bytes[Byte]







Realtime Video Reverse Error Bytes[Byte]


Realtime Video Reverse Bytes[Byte]


Realtime Voice Reverse Error Bytes[Byte]


Realtime Voice Reverse Bytes[Byte]


5.3 Resource Usage 5.3.1 Items About System Load

License Performance Stat Item name: license-Restricted Call Rejection - DO Reverse CE Resource

Overuse[Times] Definition: Total times that the RAC fails to set up traffic channels for DO calls due to

insufficient reverse CE resources. Type: Original item (RAC level) Measurement point:

The CSPU controls service through License. License Performance Stat shows the system load. In the case of insufficient CE resources, − Adjust the CE resource allocation of the modules if a module fails to set up traffic

channels for a long period because of License restricted. − Expand the capacity if the RAC fails to set up traffic channels for a long period

because of License restricted.

BTS Channel Element Performance Measurement Item name: CEs of BTSs in different statuses Definition: Number of the CEs of the carrier in different statuses (idle, traffic usage,

common channel usage, available or unavailable) in a period Type: Original item (Carrier level) Measurement point: The number of CEs shows the BTS load and shows whether the

resource allocation is reasonable. If the BTS congestion rate has exception, check the CE usage of the BTS.




Table 5-18 lists the items of BTS Channel Element Performance Measurement.

Table 5-18 Items of BTS Channel Element Performance Measurement


DO Max Available Forward CEs[entries]

DO Max Available Reverse CEs[entries]

DO Min Available Forward CEs[entries]

DO Min Available Reverse CEs[entries]

The BTS measures the maximum and minimum forward and reverse CEs available in a measurement period. In normal cases, the number of the forward maximum CEs is equal to the number of forward CEs configured in the carrier or to the number of forward CEs of the obtained License. The number of the reverse maximum CEs is equal to the number of reverse CEs configured in the carrier minus 1 or the number of the obtained License minus 1. One reverse CE is reserved for I0 check.

DO Max Forward CEs Occupied By Service Channels[entries]

DO Max Reverse CEs Occupied By Service Channels[entries]

DO Min Forward CEs Occupied By Service Channels[entries]

DO Min Reverse CEs Occupied By Service Channels[entries]

The BTS measures the maximum and minimum CEs occupied by the forward and reverse traffic channels in the measurement period. The number of CEs occupied by the forward and reverse traffic channels indicates the number of legs set up in the BTS.

DO Max Forward CEs Occupied By Common Channels[entries]

DO Max Reverse CEs Occupied By Common Channels[entries]

DO Min Forward CEs Occupied By Common Channels[entries]

DO Min Reverse CEs Occupied By Common Channels[entries]

The BTS measures the maximum and minimum CEs occupied by the forward and reverse common channels in the measurement period. When you configure a forward or reverse common channel, the BTS must allocate a CE resource to the channel for decoding. Therefore, the maximum or minimum number of CEs occupied by the forward and reverse common channels is equal to the total number of forward and reverses common channels. In normal cases, the maximum value is equal to the minimum value.

DO Max Idle Forward CEs[entries]

DO Max Idle Reverse CEs[entries]

DO Min Idle Forward CEs[entries]

DO Min Idle Reverse CEs[entries]

The BTS measures the maximum and minimum forward and reverse idle CEs in a measurement period. After the BTS configuration, in the case of load or in the case of no service, the number of idle CEs = the number of CEs configured (available CEs) – the number of CEs occupied by the common channel – the number of CEs occupied by the traffic channel





5.3.2 System Link Measurement Items

DO CCH Performance Measurement Item name: listed in Table 5-19 Definition: These items are used to measure the performance of DO synchronous CCH

and DO asynchronous CCH. Table 5-19 lists the measurement formula. Item type: compound item Measurement point: The DO CCH consists of synchronous slots, asynchronous slots, and

sub-synchronous slots. The messages sent on the CCH are sent in synchronous capsule (SC) or asynchronous capsule (AC) mode. The analysis of DO CCH usage shows the system load. You can improve the system performance by sharing the load, adjusting the antenna, and adding resource based on the analysis.

Table 5-19 Items of DO CCH Performance Measurement

Item Name Formula

DO CCH Sync Message Average Using Ratio[%]

DO CCH Sync Msg Using Ratio [%] = Total bits on the synchronous CCH of a carrier/(Packets on the synchronous CCH of a carrier x Bits per packet) x 100%

DO CCH Sync Overhead Message Max Using Ratio[%]

DO CCH Sync OverHead Msg Using Ratio [%] = Total bits of the overhead messages on the synchronous CCH of a carrier/(Packets on the synchronous CCH of a carrier x Bits per packet) x 100%

DO CCH Sync Other Message Average Using Ratio[%]

DO CCH Sync Other Msg Using Ratio [%] = Total bits of other messages on the synchronous CCH of a carrier/(Packets on the synchronous CCH of a carrier x Bits per packet) x 100%

DO CCH Discarded Sync Message Ratio[%]

DO CCH Discarded Sync Msg Count Due To Buffer Full [piece]/(DO CCH Sync Msg In Buffer Msg Count [piece] + DO CCH Discarded Sync Msg Count Due To Buffer Full [piece])

DO CCH Asynchronous Message Average Using Ratio[%]

DO CCH Async Msg Using Ratio [%] = Total bits of the paging messages and overhead messages on the asynchronous CCH of a carrier/(Packets on the asynchronous CCH of a carrier x Bits per packet) x 100%

DO CCH Discarded Asynchronous Message Ratio[%]

DO CCH Discarded Asynchronous Message Ratio[%] = Asynchronous messages discarded owing to insufficient buffer/Total asynchronous messages x 100%




Table 5-20 lists the items about DO CCH Performance Measurement.

Table 5-20 Items of DO CCH Performance Measurement


DO CCH Sync Message Using Packet Count[packet]

Total packets transmitted on DO synchronous CCHs

DO CCH Sync Message In Buffer Message Count[piece]

Synchronous messages in the buffer on DO CCHs

DO CCH Sync No Delay Send Message Count[piece]

Synchronous messages sent on DO CCHs without delay

DO CCH Sync One Delay Send Message Count[piece]

Synchronous messages sent with one timeslot period delay on DO CCHs

DO CCH Sync Two Delay Send Message Count[piece]

Synchronous messages sent with two timeslot periods delay on DO CCHs

DO CCH Sync More Delay Send Message Count[piece]

Synchronous messages sent with three or more timeslot periods delay on DO CCHs

DO CCH Discarded Sync Message Count Due To Buffer Full[piece]

Synchronous messages discarded owing to insufficient buffer

DO CCH Discarded Sub-Sync Message Count Due To Buffer Full[piece]

Sub-synchronous messages discarded owing to insufficient buffer

DO CCH Asynchronous Message Using Packet Count[packet

Packets transmitted on the DO asynchronous CCH

DO CCH Asynchronous Message In Buffer Message Count[piece]

Asynchronous messages in buffer on DO CCHs

DO CCH Asynchronous Message No Delay Send Message Count[piece]

Asynchronous messages sent without delay on DO CCHs

DO CCH Discarded Asynchronous Message Count Due To Buffer Full[piece]

Asynchronous messages discarded owing to insufficient buffer

DO CCH Discarded Asynchronous Message Count Due To Living Time[piece]

Asynchronous messages discarded owing to lifecycle expiration

Airbridge Radio Access Subsystem Performance Management Guide 6 Performance Data for Deeply Locating Problems


6 Performance Data for Deeply Locating Problems

About This Chapter


Section Describes

6.1 Subscriber Interface Tracing Subscriber interface tracing.

6.2 RFMT The RFMT.

6.3 CDR The CDR.

6.4 PSMM Data Collection PSMM data collection.

6.5 BTS Reverse RSSI Exceptional Check The BTS reverse RSSI exceptional check.

6.6 IMSI Tracing of the BTS The IMSI tracing of the BTS.

6.7 Walsh Channel Monitoring The Walsh channel monitoring.





6.1 Subscriber Interface Tracing 6.1.1 Introduction to Subscriber Interface Tracing

Through subscriber interface tracing,

The signaling of a specified call is traced on the LMT service maintenance system. The traced result is displayed in the window of the maintenance console.

For the CDMA2000 1X and CDMA2000 1xEV-DO systems, the following interfaces can be traced:

Um interface Abis interface A1 interface A3 interface A7 interface A9 interface A11 interface A12 interface A13 interface ACT interface A+ interface

6.1.2 Functions of Subscriber Interface Tracing Through subscriber interface tracing, you can:

Trace the signaling messages over multiple interfaces based on the IMSI that the subscriber uses.

Trace different interfaces. Display the traced data online, save the traced data, and review the traced data offline.

6.1.3 Operation To start the subscriber interface tracing, perform the following steps:

Step 1 Click the Maintenance tab.

Step 2 Click the Tracing node under the WLL RAC Navigation Tree.

Step 3 Double click Trace.



The Subscriber Interface Tracing Setting dialog box is displayed, as shown in Figure 6-1.

Figure 6-1 Subscriber Interface Tracing Setting dialog box

Step 4 Select the interface to be traced in the Interface List.

Step 5 Input the IMSI of the subscriber to be traced.

----End

The traced information is displayed in the right pane of the Service Maintenance System window. To view the detailed information about a record, double click the record.

To stop the subscriber interface tracing, close the right pane in the Service Maintenance System window or right click the mouse and select Stop Tracing Task.

You can:

Start the subscriber interface tracing multiple times to trace the signaling information of different subscribers.

Trace the signaling information about different interfaces for one subscriber.

6.1.4 Saving the Data and Processing the Data

Saving the Data By default, the data file is saved in ..\RAC\OutputFile\trace\user. The name of the data file is date_time_user. dat.

date indicates the date at which the interface tracing is started. time indicates the time at which the interface tracing is started. user indicates the user to be traced.

You can modify the name of the data file as required rather than change the directory in which the data file is saved. If you change the directory, the data cannot be reviewed.





Processing the Data On the LMT service maintenance system, you can offline review the data file of the subscriber interface tracing.

6.1.5 Application Scenario Subscriber interface tracing applies to:

Monitor the signaling information of a specified subscriber. Check whether the signaling interaction has exception from the signaling information.

6.2 RFMT 6.2.1 Introduction to RFMT

The RFMT is used to record:

The forward and reverse radio environment information, such as carrier transmit power and reverse RSSI.

Call feature information, including: − Branch status − Forward and reverse FER − Forward and reverse Eb/Nt − Forward code channel power of the branch − Receiving power of the MS − Forward Ec/Io − SCH application − Rate transmission over the SCH

6.2.2 Functions of the RFMT The RFMT implements the following functions:

Tracing call information about the sector carrier. The RFMT traces the power of a specified carrier and the call information about the specified carrier in all the active sets. The maximum tracing time lasts for six hours.

Collecting the information about the adjacent cell for optimization. The RFMT traces the power of the specified carriers and all the PSMM/PPSMM messages (neighbor information) of the specified carriers. The maximum tracing time lasts for six hours.

Tracing the call information of the specified IMSIs. The RFMT traces the call information of 10 specified IMSIs at most. The maximum tracing time lasts for 24 hours.

Tracing the call information about the random IMSI. The RFMT traces the information about 10 random calls for the specified modules.



The host can set the number of the traced subscribers. The maximum traced subscribers is 10. The maximum tracing time lasts for 24 hours. For RFMT DO data tracing, you can only use the method of specifying the IMSI.

6.2.3 Operation The related command is SET RFMT1x SET RFMTDO.

For the detailed operations, refer to the Help of the MML command in the service maintenance system.

6.2.4 Saving the Data and Processing the Data The data traced by the RFMT is saved in the BAM as a database, and is displayed and analyzed by the Nastar.

For the usage of the Nastar, refer to the related guide.

6.2.5 Application Scenario The RFMT is used to:

Analyze the process of all the calls in a partial cell. Record the call information about all the carriers that are specified based on the carrier

performance. This record is used to compare the quality of the reverse and forward carriers and to analyze the balance between the reverse and forward carriers.

Analyze the call of a specified IMSI. All the related information is recorded and used to locate the fault.

6.3 CDR 6.3.1 Introduction to the CDR

The CDR is used to record all the important events that occur after a call or flow is set up and before the call is released.

A CDR record is generated after the call is terminated. The system sends the records that meet the specified requirements to the BAM, which then analyzes the data.

6.3.2 Functions of the CDR To collect only the valuable information and reduce the amount of collection, set a certain filter condition in the related command.

Thus, only the valuable information is collected according to call release causes. For details, refer to the related instructions.





6.3.3 Operation To check whether the filter is enabled, run the LST CDRFILTER command.

To set the filter function, run the MOD CDRFILTER command.


After the CDR filter is enabled, the load of the RAC and the BAM increase. Do not enable all the CDR filters at one time and do not enable the CDR that is in normal release state.

6.3.4 Saving the Data and Processing the Data The data is stored in the BAM as a database.

The data traced by the CDR is displayed and analyzed by the Nastar.

For the usage of the Nastar, refer to the related instructions.

6.3.5 Application Scenario The CDR used along with the Nastar implements the following functions:

Performing health check for the system. Providing data to locate the faults, such as connection delay, call drop, and interference. Analyzing the data such as coverage, capacity, and voice quality.

6.4 PSMM Data Collection 6.4.1 Introduction to PSMM Data Collection

PSMM data collection helps you obtain the information about the radio environment and the features of the terminal after the system collects the PSMM/PPSMM/EPSMM messages or air interface messages, such as CFSRPT.

Then the system provides these information to the Nastar tool for the optimization of the neighbor cells and analysis of network coverage quality.



6.4.2 Functions of the PSMM The PSMM implements the following functions:

Reporting the following information about collection through Periodic Pilot Strength Measurement Message: − MS receiving power − EcIo of the pilot of the forward active set and candidate set − Pilot phase − Current Eb/Nt of the FCH

Reporting a PSMM message If the pilot strength is greater than the specified T_ADD threshold or is weaker than the specified T_DROP threshold for a certain time T_TDROP, a PSMM message is reported.

For the filed information collected by the PSMM and the radio environment information (for example, number and strength of the legs) about the terminal during collection, refer to the terminal feature information about the PSMM data collection field list during collection.

The feature information includes transmit power and receiving power.

6.4.3 Operation To collect the PSMM data, run the SET PSMMTRACE command.


6.4.4 Saving the Data and Processing the Data The data is stored as ..\RAC\TRACE\PSMM\PSMMTRACE********.dat.

Use the Nastar to process the data. For the usage of the Nastar, refer to the related instructions.

6.4.5 Application Scenario The PSMM applies to:

Optimization of the neighboring cells through the Nastar − Check the neighboring cells that are not configured and check the extra neighboring

cells. − List the priority of the neighboring cells. − Provide reference for adjusting the neighboring cells.

Coverage analysis and forecasting − Analyze and measure the network coverage through the information reported by the

MS. − Forecast the changes in coverage through the previous data analysis.

For the PSMM data application, refer to the Nastar instruction.





6.5 BTS Reverse RSSI Exceptional Check 6.5.1 Introduction to BTS Reverse RSSI Exceptional Check

The BTS reverse RSSI exceptional check is used to collect the data of the reverse main and diversity receiving signal strength.

6.5.2 Functions of BTS Reverse RSSI Exceptional Check You can collect the data through either of the following methods:

2s threshold data If the FER is within the specified range or the interference value exceeds the specified range, a record is generated.

Reporting data every 30s The BTS reports the current RSSI data every 30s. The RSSI data records: − Reverse receiving signal strength (main and diversity) − BTS current transmit power − Number of legs

6.5.3 Operation To check the BTS reverse RSSI exceptions, run the STR CBTSITFLOGTHD command.


6.5.4 Saving the Data and Processing the Data The data is stored in …\RAC\Services\BTSITFLOG. The BTSXXX_ITF_LOG. LOG and BTSXXX_ITF_LOG. LOG are used to distinguish the BTS records.


6.5.5 Application Scenario Through the Nastar, the BTS reverse RSSI exceptional check implements the following functions:

Checking the installation of partial BTS equipment through the reverse receiving signal. Monitoring the reverse interference and reverse link quality



6.6 IMSI Tracing of the BTS 6.6.1 Introduction to IMSI Tracing of the BTS

Record the following information about an IMSI user who makes a call in a specified BTS:

Forward and reverse wireless environment Call features

6.6.2 Functions of IMSI Tracing of the BTS IMSI tracing of the BTS implements the following functions:

Reporting the collected data every 2s Collecting the following information:

− Forward transmit power − Reverse RSSI − Leg handoff state − Reverse FER of the BTS − Reverse acquisition

6.6.3 Operation The related command is STR CBTSCHBITFINFOTRC.


6.6.4 Saving the Data and Processing the Data The data is stored in …\RAC\Services\BTSITFLOG. The BTSXXX_ITF_LOG. LOG and are used to distinguish the BTS records.

The traced data and the BTS reverse RSSI exceptional check data are saved in the same file. During importing the data, the Nastar can analyze and classify each traced data.


6.6.5 Application Scenario To analyze the exceptions of a call in several specified BTSs, start the IMSI trace.





6.7 Walsh Channel Monitoring 6.7.1 Introduction to Walsh Channel Monitoring

Monitor the Walsh channel power to check the integrity of the Walsh tree and the assignment ability of the SCH.

6.7.2 Functions of Walsh Channel Monitoring Walsh channel monitoring implements the following functions:

Collecting the quantity of the assigned and remained Walsh Collecting the allocated and remained Walsh space Supporting the display of 64 order Walsh codes and 128 order Walsh codes Supporting Qof 0-3 visible display. Displaying the specified Walsh codes in histogram. Displaying the channel measurement information in form. Providing the color scheme of all channels.

6.7.3 Operation To monitor the Walsh channel, perform the following steps:

Step 1 In the Service Maintenenace System window, click Maintenance tab and click Trace under WLL RAC Maintenance Tree.

Step 2 In the displayed Parameters of Radio Resource Monitoring dialog box, set the related information and click OK.



Step 3 Click Walsh Visualization.

In the tabbed page, the usage of Walsh codes is displayed in a table or a figure, as shown in Figure 6-2 and Figure 6-3.

Figure 6-2 CDMA2000 1x Radio Resource Monitoring





Figure 6-3 CDMA2000 1X Radio Resource Monitoring

----End

6.7.4 Saving the Data and Processing the Data For 1X carrier, the data is saved in \RAC\OutputFile\RMON\RADIO_RESOURCE. For the DO carrier, the data is saved in \RAC\OutputFile\RMON\\EV-DORADIO_RESOURCE.

The data can be saved both in the form of *. bin and *. txt. The *. bin files can be opened at the RAC maintenance console and the *. txt files can be opened by the edible tools.


6.7.5 Application Scenario Monitoring the Walsh channel power to check the integrity of the Walsh codes tree and the assignment ability of the SCH.

Airbridge Radio Access Subsystem Performance Management Guide 7 Common Test Calls and Loading Simulation


7 Common Test Calls and Loading Simulation

About This Chapter


Section Describes

7.1 Markov Test Call The related information about Markov test call.

7.2 Loopback Test Call The related information about loopback test call.

7.3 TDSO Test Call The related information about TDSO test call.

7.4 OCNS The related information about OCNS.

7.5 OUNS The related information about OUNS.





7.1 Markov Test Call 7.1.1 Introduction to Markov Test Call

Markov test call is used to test the quality of the FCH air interface for CDMA 1X services. It is an effective method of checking the quality of the traffic channels.

During a Markov test call, pseudo-random data are sent between the MS and the BSS to simulate human voice. Thus, you can measure the frame error rate (FER) of the forward and reverse traffic services.

A Markov test call can be initiated by an MS or VCN. By setting the field Service Option, you can distinguish a Markov test call and a common call.

If a Markov test call is initiated by an MS, Service Option in the Origination Message that is sent from the MS to the VCN is set to 0x801E(8K Markov) or 0x801F (13K Markov).

If a Markov test call is initiated by the VCN, Service Option in the General Page Message is set to 0x801E or 0x801F. After the MS receives the page response, Service Option in the Page Response Message is set to 0x801E or 0x801F.

For the detailed description about Markov test call, refer to the C. S0025_Markov_Service_Option,Markov Service Option (MSO) for cdma2000 Spread Spectrum Systems.

7.1.2 Scenario for Markov Test Call Markov test call is used to:

Check the quality of the traffic channels Measure the FER of the forward and reverse channels Measure the quality of radio environment

Markov test call applies to:

Network performance optimization To perform a test call, use the tools of a drive test to make a Markov test call. The signal distribution of the radio environment in the current network is obtained. You can make a Markov test call instead of a common call to measure access success rate, call drop rate, and voice capacity.

The check of configuration about the system synchronization clock Markov test call requires high system synchronization. Therefore, Markov test call can be used to check whether the configuration of the system synchronization clock is good. If the system GPS clock is faulty, the FER is high after you make a Markov test call.



7.1.3 Making a Markov Test Call If a Markov test call is initiated by an MS, the call process is the same as that of a making a common call.

If a Markov test call is initiated by the access side, the call process is the same as that when the MS is the called party. Only Service Option is set to different value.

Markov Test Call Initiated By an MS After the MS is in Test Call status of the Debug mode, you can select the related service to initiate a Markov test call. Alternatively, you can select the related service through the Call Monitor function that is enabled by the Cait software.

Markov Test Call Initiated By the VCN To initiate a Markov test call by the VCN, in the VCN of the core network, run the STR MKV command at the OMC of the CSOFTX 3000.

For the detailed operation about this command, refer to Guide to the CSOFTX3000 V100R001 Markov Call Operation.

7.1.4 Measuring Forward and Reverse FERs of a Markov Test Call During making a Markov test call, you can measure the FER of the forward and reverse channels. The MS measures the forward FER and sends the Power Measurement Report Message to the RAC. The CFMR of the RAC measures the reverse FER.

Measuring Forward FER You can measure the forward FER through either of the following methods:

View the forward FER through the window of the terminal, for example, HUAWEI C218.

Start the RFMT trace to record the F-FER. Enable the Cait software to measure the F-FER of a Markov test call. Analyze the log file of the Cait software through the BAM software to measure the

F-FER of a Markov test call.

Measuring Reverse FER You can measure the reverse FER:

Through the test call trace of the RAC maintenance console or By starting the RFMT trace to record the F-FER

For details, refer to the online help of the service maintenance system.





7.2 Loopback Test Call 7.2.1 Introduction to Loopback Test Call

Loopback test call is used to test the quality of the FCH air interface.

During a loopback test call, the BS sends a specified data stream to the MS through the forward TCH. Then, the MS sends the data steam to the BS through the reverse TCH.

The BS and MS measure the F-FER and R-FER of the TCH according the data block received and sent. Through a Loopback test call, you can measure the FERs of the forward and reverse FCH and the FERs of the forward SCH and reverse FCH.

A loopback test call can be initiated by the MS or by the VCN. By setting the field Service Option, you can distinguish a common call and a loopback test call. Service Option of a loopback test call is set to 0x0009 (13K Loopback) and 0037H (IS2000 Loopback).

For the detailed description about loopback test call, refer to the C. S0013-A_Loopback_Service_Option,Loopback Service Options (LSO) for cdma2000 Spread Spectrum Systems.

7.2.2 Scenario for Loopback Test Call Loopback test call is used to measure the FER of the TCH.

For the detailed measurement method, refer to the Recommended Minimum Performance Standards for Dual-Mode Spread Spectrum Mobile Stations, TIA/EIA-98-C.

7.2.3 Making a Loopback Test Call

Loopback Test Call Initiated by an MS After the MS is in Test Call status of the Debug mode, you can select the related service to initiate a loopback test call. Alternatively, you can select the related service through the Call Monitor function that is enabled by the Cait software.

Loopback Test Call Initiated by the Access Side To initiate a loopback test call by the access side, run the relevant command through the OMC console of the CSOFTX 3000 at the VCN of the core network.

For the detailed operation, refer to the Guide to the CSOFTX3000 V100R001 Markov Call.

7.2.4 Observing the Results of Making a Loopback Test Call During a loopback test call, you can measure the FER of the call.

Measuring Forward FER You can measure the forward FER through either of the following methods:

View the forward FER through the window of the terminal, for example, HUAWEI C218. Start the RFMT trace to record the F-FER.



Use IS2000 FER Information function that is enabled by the Cait software to measure the forward FER. Analyze the log file of the Cait through the BAM software to measure the forward FER.

Measuring Reverse FER You can measure the reverse FER:

Through the test call trace of the RAC maintenance console or By starting the RFMT trace to record the F-FER

For the detailed operation, refer to the online help of the service maintenance system, the Cait user guide, and the Guide to Data Analysis of CDMA 1X Drive Test.

7.3 TDSO Test Call 7.3.1 Introduction to TDSO Test Call

Test data service option (TDSO) test call is used to test the CDMA 1X data service.

The preset or random data packets are sent on the forward and reverse channels between the MS and the BSS. The data packet mechanism compares the data packets sent from the peer end and the data packets generated at the local end. In this way, FER and PDU error rate (PER) are obtained.

Thus, the transmission rate of the data service over the air interface is obtained according to the data transmission of the analog data service.

There are two types of TDSO:

Simple TDSO Full TDSO

TDSO described in this manual refers to Simple TDSO.

For the detailed description about TDSO test call, refer to the C. S0026_Test_Data_Service_Option, Test Data Service Option (TDSO) for cdma2000 Spread Spectrum Systems.

7.3.2 Scenario for TDSO Test Call TDSO test call is used to:

Locate the data service. TDSO test call transmits the data of air interface. Therefore, the impacts of RLP, TCP/IP protocol on the data service are avoided.

Check whether the clock is synchronized.





7.3.3 Making a TDSO Test Call TDSO test call is initiated by an MS.

After the MS is in Test Call status of the Debug mode, you can select the related service to initiate a TDSO test call. Alternatively, you can select the related service through the Call Monitor function that is enabled by the Cait software.

7.3.4 Observing the Results of Making a TDSO Test Call TDSO test call can be used to trace the forward and reverse FERs of the TDSO and the rate at the RAC maintenance console.

Use the STDSO measurement function of the Cait software to observe the frame measurement of the TDSO test call.

For details, refer to the online help of the service maintenance system and the Cait User Guide.

7.4 OCNS 7.4.1 Introduction to OCNS

Other channel noise simulator (OCNS) is used to simulate the forward load.

The forward load of the current cell and the neighbor cell must be measured during test. Forward OCNS is used to simulate the forward load of the system. By simulating the loading of the forward power, the effects of other forward TCH on the system is implemented.

7.4.2 Scenario for OCNS OCNS is used to simulate the forward loading in the tests.

7.4.3 Methods of OCNS Simulation To simulate the forward loading,

Run the SET OCNSTARTUP command to start the OCNS loading at the maintenance console.

Run the SET OCNSTOP command to stop the OCNS loading at the maintenance console.

The OCNSTARTUP and SET OCNSTOP are interior system commands and are BTS level commands. These commands are BTS level commands. They vary according with different BTS types.

For the OCNS detailed principle, operation procedure, and precautions, refer to the Operation Guide to CDMA2000 RAC OCNS.



7.5 OUNS 7.5.1 Introduction to OUNS

Other user noise simulator (OUNS) is used to simulate the effects from the reverse channels on the BTS capacity. Eb/Nt of each reverse TCH is the same. After the signal to noise ratio is changed, the system can simulate the user interference.

7.5.2 Scenario for OUNS OUNS is used for the capacity test and coverage test, in which a small number of MSs are used to simulate a great number of MSs. OUNS can test the reverse capacity and coverage.

7.5.3 Methods of OUNS Loading To start or stop the OUNS loading, run the SET CBTSOUNSPARA command by selecting different parameters. The command is BTS level commands. It varies according with different BTS types.

For the OUNS detailed principle, operation procedure, and precautions, refer to the Operation Guide to CDMA2000 BTS36XX RF New Functions.

performance management guide

Documents

data performance data

performance data system

performance measurement

performance alarm

performance management

daily performance monitoring

data kpi

kpi specification threshold