3G 1X Performance Management Indexes and Their Calculation

7/31/2019 3G 1X Performance Management Indexes and Their Calculation

1/189

3G RLSA Performance Management Indexes and Their Calculation

Technical Document

Document Name: 3G RLSA Performance Management Indexes and their Calculation

Document No.:

Version:

Document Quality:

Total 185 pages (including the cover)

Compiled by:

Reviewed by:

Signed by:

Standardized by:

Approved by:

ZTE CORPORATION


2/189


1.

ZTE Confidential Proprietary Page 1

Revision HistoryVersion Date Reviser Description

1.0 2005-11-20 GUO Zhongcheng First draft

Note:

All information contained herein the document is confidential. Any reproduction, distribution, storage or incorporated into

any database is strictly prohibited without ZTE Corporation's prior written permission.


3/189


4/189


5/189


6/189


7/189


8/189


9/189


10/189


11/189


12/189


13/189


14/189


15/189


16/189


1.


2 Registration

2.1 Function Description

The performance data statistic in registration involves the global carrier and the cell carrier (sector). According to related 3G protocols, there are 9

types of registration, for which the times of success/failure should be counted respectively.

1. Power-up registration: The mobile station registers with the network on power-up to remind the network of its activation.

2. Power-down registration: The mobile station registers on power-down. This type of registration may occur on the control channel as an

independent process, or occur on the control channel in the release operation of a conversation.

3. Timer-based registration: The mobile station registers whenever its timer counter reaches a predetermined value. It allows the mobile station

to register periodically and allows the network to deregister the inactive mobile stations.

4. Distance-based registration: The mobile station registers whenever it enters a cell whose distance from the cell in which the mobile station

last registered exceeds a given threshold calculated with control channels.

5. Zone-based registration: A mobile service range can be divided into several smaller zones and the zone is a set of one or more cells. Themobile station identifies the current cell with the forward control channel parameter and registers whenever it enters a zone that is not in its

zone list. This type of registration allows the network to limit the paging to operate in the cell the MS registers with.

6. Parameter-change registration: The mobile station registers when certain of its stored parameters change.

7. Ordered registration: The mobile station registers with the order from the base station.

8. User zone registration: The mobile station registers when it selects an active user zone while in the Idle State.

9. Implicit registration: The base station learns the location of the mobile from the origination or page response message, and the registration

attached is called implicit registration.

2.2 Protocol Flow

For details, please refer to 3GPP2 A.S0001-A version 2.0 4.1.2.2.2.

The flow below is a registration due to location change.


17/189


1.



18/189


1.


2.3 Counter Table Detail

2.3.1 GbcReg (Global Carrier Registration)

Statistical item Description DT Trigger C/

S

LC Res

PowerUpReqNum Power Up Request Num FL

Every time when BS (base station) receives a registration

message from MS (mobile station), it will determine the type

of registration is Powerup and add 1 to the counter of that

type of registration accordingly.

C GC

PowerUpSuccNum Power Up Success Num FLAdd 1 to the counter every time when MSC returns a

Registration Accepted Order within specified time.C

GC

PowerDownReqNum Power Down Request Num FL



of registration is PowerDown and add 1 to the counter of thattype of registration accordingly.

C

GC

PowerDownSuccNum Power Down Success Num FLAdd 1 to the counter every time when MSC returns a


GC

TimerBasedReqNum Timer Based Request Num FL



of registration is TimerBased and add 1 to the counter of that


C

GC

TimerBasedSuccNum Timer Based Success Num FLAdd 1 to the counter every time when MSC returns a


GC


19/189


1.


DistanceBasedReqNum Distance Based Request Num FL


message from MS (mobile station), it will determine the typeof registration is DistanceBased and add 1 to the counter of

that type of registration accordingly.

C

GC

DistanceBasedSuccNum Distance Based Success Num FLAdd 1 to the counter every time when MSC returns a


GC

ZoneBasedReqNum Zone Based Request Num FL



of registration is ZoneBased and add 1 to the counter of thattype of registration accordingly.

C

GC

ZoneBasedSuccNum Zone Based Success Num FLAdd 1 to the counter every time when MSC returns a


GC

ParameterChangeReqNu

m

Parameter Change Request

NumFL



of registration is Parameter Change and add 1 to the counter

of that type of registration accordingly.

C

GC

ParameterChangeSuccN

um

Parameter Change Success

NumFL

Add 1 to the counter every time when MSC returns a


GC

OrderedReqNum Ordered Request Num FL



of registration is Ordered by BS, and add 1 to the counter of


C

GC

OrderedSuccNum Ordered Success Num FLAdd 1 to the counter every time when MSC returns a


GC

UserZoneReqNum User Zone Request Num FL



of registration is User Zone and add 1 to the counter of that


C

GC


20/189


1.


UserZoneSuccNum User Zone Success Num FLAdd 1 to the counter every time when MSC returns a

Registration Accepted Order within specified time.

CGC

2.3.2 ClcReg (Cell Carrier Registration)


S

LC Res

PowerUpReqNum Power Up Request Num

IN Every time when BS (base station) receives a registration


of registration is Powerup and add 1 to the counter of that


C CC

PowerUpSuccNum Power Up Success NumIN Add 1 to the counter every time when MSC returns a

Registration Accepted Order within specified time.C CC

PowerDownReqNum Power Down Request Num


message from MS (mobile station), it will determine the typeof registration is PowerDown and add 1 to the counter of that


C CC

PowerDownSuccNum Power Down Success NumIN Add 1 to the counter every time when MSC returns a


TimerBasedReqNum Timer Based Request Num



of registration is TimerBased and add 1 to the counter of that


C CC

TimerBasedSuccNum Timer Based Success NumIN Add 1 to the counter every time when MSC returns a



21/189


1.


DistanceBasedReqNum Distance Based Request Num


message from MS (mobile station), it will determine the typeof registration is DistanceBased and add 1 to the counter of


C CC

DistanceBasedSuccNum Distance Based Success NumIN Add 1 to the counter every time when MSC returns a


ZoneBasedReqNum Zone Based Request Num



of registration is ZoneBased and add 1 to the counter of thattype of registration accordingly.

C CC

ZoneBasedSuccNum Zone Based Success NumIN Add 1 to the counter every time when MSC returns a


ParameterChangeReqNu

m

Parameter Change Request

Num



of registration is Parameter Change and add 1 to the counter

of that type of registration accordingly.

C CC

ParameterChangeSuccN

um

Parameter Change Success

Num

IN Add 1 to the counter every time when MSC returns a


OrderedReqNum Ordered Request Num



of registration is Ordered by BS, and add 1 to the counter of


C CC

OrderedSuccNum Ordered Success NumIN Add 1 to the counter every time when MSC returns a


UserZoneReqNum User Zone Request Num



of registration is User Zone and add 1 to the counter of that


C CC


22/189


1.


UserZoneSuccNum User Zone Success NumIN Add 1 to the counter every time when MSC returns a


2.4 Calculation Method

Overall Registration Success Rate = 00%1

RequestNum

SuccessNum

Type

Type

Registration Success Rate of each type = 00%1RequestNum

SuccessNum

3 Voice Services

3.1 Call Services (Voice)

3.1.1 Call Origination (Voice)

3.1.1.1 Function Description

The performance data in call origination (voice) involves the global carrier and the cell carrier (sector). After the base station (BS) receives an

origination message from the mobile station (MS), it will first determine if it is a voice call based on the parameters. If yes, it will go on the call flow for

voice services and collect related data accordingly.


23/189


1.


3.1.1.2 Protocol Flow

For details, please refer to 3GPP2 A.S0001-A version 2.0 2.2.2.1.


24/189


1.


3.1.1.3 Counter Table Detail

3.1.1.3.1 GbcVocOrigCall (Global Carrier Voice Originating Call)


S

LC Res

MSOriginateNum MS Originating Num FLAdd 1 to the counter every time when BS receives an

origination message from MS.C GC

CallSuccessNum Voice Originating RequestNum

FL Add 1 to the counter every time when BS sends theAssignment Complete message to MSC.

C GC

ExtInterruptNum Outer Interrupt Num FL

Add 1 to the counter every time when BS fails to set up a

traffic channel due to insufficient resources (including SE, VE,

CIC, CE, Walsh Code and Power).

C

GC

BlockFailureNum Block Success Num FLAdd 1 to the counter every time when BS receives a release

request from MS or MSC in the process of call setup.C

GC

OtherFailureNum Other Reason Success Num FLAdd 1 to the counter every time when the call origination fails

for reasons other than the above.C

GC

3.1.1.3.2 ClcVocOrgCall (Cell Carrier Voice Originating Call)


S

LC Res

MSOriginateNum MS Originating Num INAdd 1 to the counter every time when BS receives an

origination message from MS.C CC

CallSuccessNumVoice Originating Request

Num

IN Add 1 to the counter every time when BS sends the

Assignment Complete message to MSC.C CC


25/189


1.


ExtInterruptNum Outer Interrupt Num

IN Add 1 to the counter every time when BS fails to set up a



C CC

BlockFailureNum Block Success NumIN Add 1 to the counter every time when BS receives a release

request from MS or MSC in the process of call setup.C CC

OtherFailureNum Other Reason Success NumIN Add 1 to the counter every time when the call origination fails

for reasons other than the above.C CC

3.1.1.4 Calculation Method

Call Origination Success Rate = 100%

umOriginateN

SuccessNum

Call Origination Block Rate = 100%

umOriginateN

BlockNum

Call Origination External Interrupt Rate = 100%

umOriginateN

mterrruptNuExternalIn

Note: The user may decide whether the external interrupt number is added to the success number.


26/189


1.


3.1.2 Paging (Voice)


The performance data in paging (voice) involves the global carrier and the cell carrier (sector). After the base station (BS) receives a paging request

from the mobile switching center (MSC), it will broadcast the message. And when BS receives the page response from a mobile station (MS), it will go

on the paging flow for voice services and collect related data accordingly.




27/189


1.



28/189


1.



3.1.2.3.1 GbcVocPagCall (Global Carrier Voice Paging Call)


S

LC Res

PagingMsNum MS Paging Num FLAdd 1 to the counter every time when BS receives a paging

request from MSC.C

GC

PageResponceNum MS Paging Response Num FL Add 1 to the counter every time when BS receives a pageresponse message from MS.

C GC

CallSuccessNum Voice Paging Request Num FLAdd 1 to the counter every time when BS sends the

Assignment Complete message to MSC.C

GC





C

GC



GC

OtherFailureNum Other Reason Success Num FLAdd 1 to the counter every time when the paging fails for

reasons other than the above.C

GC

3.1.2.3.2 ClcVocPagCall (Cell Carrier Voice Paging Call)


S

LC Res

PagingMsNum MS Paging NumIN Add 1 to the counter every time when BS receives a paging

request from MSC.C CC


29/189


1.


PageResponceNum MS Paging Response NumIN Add 1 to the counter every time when BS receives a page

response message from MS.C CC

CallSuccessNum Voice Paging Request NumIN Add 1 to the counter every time when BS sends the






C CC


request from MS or MSC in the process of call setup.

C CC

OtherFailureNum Other Reason Success NumIN Add 1 to the counter every time when the paging fails for

reasons other than the above.C CC


Paging Response Rate= 100%

PagingNum

onseNumPagingResp

Paging Success Rate = 100%

onseNumPagingResp

SuccessNum

Paging Block Rate = 100%

onseNumPagingResp

BlockNum


30/189


1.


Paging External Interrupt Rate = 100%

onseNumPagingResp



3.1.3 Calls (Voice)


As the call process of voice services includes call origination (voice) and paging (voice), its data comes from the data of the two.


Call Success Rate (Voice) = 100%+

+

MTMO

MTMO

onseNumPagingRespumOriginateN

SuccessNumSuccessNum

Call Block Rate (Voice) = 0%10onseNumPagingRespumOriginateN

BlocksNumBlockNum

MTMO

MTMO +

+

Call External Interrupt Rate (Voice)

= 100%+

+

MTMO

MTMO


terruptNumExternalInterruptNumExternalIn



31/189


1.


3.2 Handoff (Voice)

3.2.1 Intra-BSS Handoff


The intra-BSS handoff is the handoff that takes place in the same BSS as that of call setup. Its performance management data involves the global and

cell carriers. Based on the traffic channels it occupies, it can be further divided into the following types:

1. Soft handoff: The handoff whose traffic channels are in different CEs.2. Softer handoff: The handoff whose traffic channels are in the same CE but with different Walsh codes.

3. Semi-soft handoff: According to related 3G protocols, all the change carrier handoffs, caused by frame-offset handoffs and change RC handoffs

are hard handoff. To distinguish these kinds of hard handoff from that occurs between the original BS and one of other manufacturers BSs, we

call them semi-soft handoff.

4. Cross-BSS handoff out: The handoff where the traffic channel for call setup is in a BSS, but as the mobile station moves, its air interface traffic

channel is handed off out to another BSS.

5. Other intra-BSS handoff: Those handoffs that cannot be classified into the above types.


For details, please refer to 3GPP2 C.S0005-A v6.0 ANNEX B CDMA CALL FLOW EXAMPLES.


32/189


1.



33/189


1.



3.2.1.3.1 GbcVocHoSrcBss (Global Carrier Voice Handoff as Source BSS)


S

LC Res

SrcBscSoftAdd_HoRNum

Soft Handoff Add Request

Num as Source BSC FL

Every time when BS receives a handoff request from MS, it

will determine the type of handoff is Soft and add 1 to thecounter of that type accordingly.

C

GC

SrcBscSoftAdd_HoSNumSoft Handoff Add Success

Num as Source BSCFL

Every time when BS receives a Handoff Completion message

from MS, it will determine the type of handoff and add 1 to the

counter of that type accordingly.

C

GC

SrcBscSofterAdd_HoRNu

m

Softer Handoff Add Request

Num as Source BSC

FL


will determine the type of handoff is Softer and add 1 to the


C

GC

SrcBscSofterAdd_HoSNu

m

Softer Handoff Add Success

Num as Source BSCFL




C

GC

SrcBscFREQ_HoRNum

Inter-Frequency Semi handoff

Add Request Num as Source

BSC

FL


will determine the type of handoff is change Frequency and

add 1 to the counter of that type accordingly.

C

GC

SrcBscFREQ_HoSNum


Add Success Num as Source

BSC

FL




C

GC

SrcBscFO_HoRNumInter-Frame Semi handoff Add

Request Num as Source BSCFL


will determine the type of handoff is change Frame Offset and


C

GC


34/189


1.


SrcBscFO_HoSNumInter-Frame Semi handoff Add

Success Num as Source BSC

FL




C

GC

SrcBscRC_HoRNumInter-RC Semi handoff Add

Request Num as Source BSCFL


will determine the type of handoff is change Radio

Configuration and add 1 to the counter of that type

accordingly.

C

GC

SrcBscRC_HoSNum

Inter-RC Semi handoff Add

Success Num as Source BSC FL


from MS, it will determine the type of handoff and add 1 to thecounter of that type accordingly.

C

GC

InterBscHo_HoRNum

Handoff-Out Handoff Request

Num Between BSC as Source

BSC

FL


will determine the type of handoff is out to other BS and add 1

to the counter of that type accordingly.

C

GC

InterBscHo_HoSNum

Handoff-Out Handoff Success


BSC

FL




C

GC

SrcBscOther_HoRNumOther Handoff Request Num

Between BSC as Source BSCFL


will determine the type of handoff is not recognized and add 1


C

GC

SrcBscOther_HoSNumOther Handoff Success Num

Between BSC as Source BSCFL




C

GC

3.2.1.3.2 ClcVocHoSrcBss (Cell Carrier Voice Handoff as Source BSS)


S

LC Res


35/189


1.


SrcBscSoftAdd_HoRNumSoft Handoff Add Request

Num as Source BSC

IN Every time when BS receives a handoff request from MS, it

will determine the type of handoff is Soft and add 1 to the


C CC

SrcBscSoftAdd_HoSNumSoft Handoff Add Success

Num as Source BSC

IN Every time when BS receives a Handoff Completion message



C CC

SrcBscSofterAdd_HoRNu

m


Num as Source BSC




C CC

SrcBscSofterAdd_HoSNu

m


Num as Source BSC




C CC

SrcBscFREQ_HoRNum


Add Request Num as Source

BSC




C CC

SrcBscFREQ_HoSNumInter-Frequency Semi handoff

Add Success Num as Source

BSC




C CC

SrcBscFO_HoRNumInter-Frame Semi handoff Add

Request Num as Source BSC




C CC

SrcBscFO_HoSNum Inter-Frame Semi handoff AddSuccess Num as Source BSC




C CC

SrcBscRC_HoRNumInter-RC Semi handoff Add

Request Num as Source BSC




accordingly.

C CC


36/189


1.


SrcBscRC_HoSNumInter-RC Semi handoff Add

Success Num as Source BSC




C CC

InterBscHo_HoRNum



BSC


will determine the type of handoff is out to other BS and add 1


C CC

InterBscHo_HoSNum



BSC




C CC

SrcBscOther_HoRNumOther Handoff Request Num

Between BSC as Source BSC




C CC

SrcBscOther_HoSNumOther Handoff Success Num

Between BSC as Source BSC




C CC


Overall Handoff Success Rate = 00%

Type

1RequestNum

SuccessNumType

Handoff Success Rate of each type = 00%1RequestNum

SuccessNum

Note: According to related protocols, the semi-soft handoff is often classified into the hard handoff. Therefore, calculate the handoff success rate of

semi-soft handoff separately.


37/189


1.


3.2.2 Inter-BSS Handoff


The inter-BSS handoff is the handoff that takes place in the BSS (the target one) different from that of call setup due to the move of the mobile station.

Its performance management data involves the global and cell carriers. Based on the traffic channels it occupies, it can be further divided into the

following types:

1. Soft handoff: The handoff whose traffic channels are in different CEs.

2. Softer handoff: The handoff whose traffic channels are in the same CE but with different Walsh codes.

3. Semi-soft handoff: According to related 3G protocols, all the change carrier handoffs, caused by frame-offset handoffs and change RC handoffs

are hard handoff. To distinguish these kinds of hard handoff from that occurs between the original BS and one of other manufacturers BSs, we

call them semi-soft handoff.

4. Cross-BSS handoff in: The handoff where the traffic channel for call setup is in other BSS, but as the mobile station moves, its air interface traffic

channel is handed off into the BSS.

5. Other intra-BSS handoff: Those handoffs that cannot be classified into the above types.


For details, please refer to 3GPP2 A.S0001-A version 2.0 3.5.2.3.1.


38/189


1.



39/189


1.



3.2.2.3.1 GbcVocHoTgtBss (Global Carrier Voice Handoff as Target BSS)


S

LC Res

TgtBscSoftAdd_HoRNumSoft Handoff Add Request

Num as Target BSCFL




C

GC

TgtBscSoftAdd_HoSNumSoft Handoff Add Success

Num as Target BSCFL




C

GC

TgtBscSofterAdd_HoRNu

m


Num as Target BSCFL




C

GC

TgtBscSofterAdd_HoSNu

m


Num as Target BSCFL

Every time when BS receives a Handoff Completion messagefrom MS, it will determine the type of handoff and add 1 to the


CGC

TgtBscFREQ_HoRNum


Add Request Num as Target

BSC

FL




C

GC

TgtBscFREQ_HoSNum


Add Success Num as Target

BSC

FL




C

GC

TgtBscFO_HoRNumInter-Frame Semi handoff Add

Request Num as Target BSCFL




C

GC


40/189


1.


TgtBscFO_HoSNumInter-Frame Semi handoff Add

Success Num as Target BSC

FL




C

GC

TgtBscRC_HoRNumInter-RC Semi handoff Add

Request Num as Target BSCFL




accordingly.

C

GC

TgtBscRC_HoSNum

Inter-RC Semi handoff Add

Success Num as Target BSC FL


from MS, it will determine the type of handoff and add 1 to thecounter of that type accordingly.

C

GC

InterBscHo_HoRNum


Num Between BSC as Target

BSC

FL


will determine the type of handoff is handoff into self and add

1 to the counter of that type accordingly.

C

GC

InterBscHo_HoSNum



BSC

FL




C

GC

TgtBscOther_HoRNumOther Handoff Request Num

Between BSC as Target BSCFL




C

GC

TgtBscOther_HoSNumOther Handoff Success Num

Between BSC as Target BSCFL




C

GC

3.2.2.3.2 ClcVocHoTgtBss (Cell Carrier Voice Handoff as Target BSS)


S

LC Res

3G RLSA P f M t I d d Th i C l l ti


41/189


1.


TgtBscSoftAdd_HoRNumSoft Handoff Add Request

Num as Target BSC




C CC

TgtBscSoftAdd_HoSNumSoft Handoff Add Success

Num as Target BSC




C CC

TgtBscSofterAdd_HoRNu

m


Num as Target BSC




C CC

TgtBscSofterAdd_HoSNu

m


Num as Target BSC




C CC

TgtBscFREQ_HoRNum


Add Request Num as Target

BSC




C CC

TgtBscFREQ_HoSNumInter-Frequency Semi handoffAdd Success Num as Target

BSC

IN Every time when BS receives a Handoff Completion messagefrom MS, it will determine the type of handoff and add 1 to the


C CC

TgtBscFO_HoRNumInter-Frame Semi handoff Add

Request Num as Target BSC




C CC

TgtBscFO_HoSNum Inter-Frame Semi handoff AddSuccess Num as Target BSC




C CC

TgtBscRC_HoRNumInter-RC Semi handoff Add

Request Num as Target BSC




accordingly.

C CC



42/189


1.


TgtBscRC_HoSNumInter-RC Semi handoff Add

Success Num as Target BSC




C CC

InterBscHo_HoRNum



BSC


will determine the type of handoff is handoff into self and add

1 to the counter of that type accordingly.

C CC

InterBscHo_HoSNum



BSC




C CC

TgtBscOther_HoRNumOther Handoff Request Num

Between BSC as Target BSC




C CC

TgtBscOther_HoSNumOther Handoff Success Num

Between BSC as Target BSC




C CC


Overall Handoff Success Rate = 00%

Type

1RequestNum

SuccessNumType

Handoff Success Rate of each type = 00%1RequestNum

SuccessNum

Note: According to related protocols, the semi-soft handoff is often classified into the hard handoff. Therefore, calculate the handoff success rate of

semi-soft handoff separately.



43/189


1.


3.3 Release (Voice)

3.3.1 Function Description

The releases in voice services are divided into two types: normal releases (hang up) from the mobile station (MS), base station (BS) and mobile

switching center (MSC), and abnormal release (call drop) from the MS, BS and MSC. Therefore, count the numbers of normal and abnormal releases

respectively.

3.3.2 Protocol Flow



44/189


1.




45/189

g

1.


3.3.3 Counter Table Detail

3.3.3.1 GbcVocRls (Global Carrier Voice Release)


S

LC Res

CM_NorRlsSNum Normal Release Num FLAdd 1 to the counter every time when BS receives a normal

release message from MS or MSC.C

GC

CM_SysDorpNum System Drop Num FLAdd 1 to the counter every time when a call exception

message from BS or MSC is received. CGC

CM_RadioDropNum Radio Drop Num FLAdd 1 to the counter every time when a call exception

radio message from BS or MSC is received.C

GC

3.3.3.2 ClcVocRls (Cell Carrier Voice Release)

Statistical item Description DT Trigger C/ S

LC Res

CM_NorRlsSNum Normal Release NumIN Add 1 to the counter every time when BS receives a normal

release message from MS or MSC.C CC

CM_SysDorpNum System Drop NumIN Add 1 to the counter every time when a call exception

message from BS or MSC is received.C CC

CM_RadioDropNum Radio Drop Num

IN Add 1 to the counter every time when a call exception

radio message from BS or MSC is received. C CC



46/189

1.


3.3.4 Calculation Method

Call Drop Rate = 100%+

DropNumaseNumNormalRele

DropNum

3.4 Traffic (Voice)

3.4.1 Intra-BSS Traffic


The intra-BSS traffic refers to the traffic of calls and handoffs which both occur in the same BSS.

Based on the call flow, the system divides the entire call process into 5 time periods.

T1: from the time when BS receives a call request from MS to the time when BS receives an assignment request from MSCT2: from the time when BS receives the assignment request from MSC to the time when BS sends channel assignment message to MS

T3: from the time when BS sends channel assignment message to MS to the time when BS sends an assignment complete message to MSC

T4: from the time when BS sends the assignment complete message to MSC to the time when BS sends to MSC a clear request (this time period is

the conversation process)

T5: from the time when BS sends to MSC a clear request to the time of Clear Complete

As there may be soft handoff in the time periods T3 and T4, the traffic in these two periods includes both that of calls and that of handoffs.

Please follow the calculation method below to calculate the traffic of call and handoff.The traffic of call is the duration of the conversation, while the traffic of handoff can be calculated as follows:

In the process of handoff, the traffic of handoff is the duration of that handoff deducting the part used for the call.

Suppose the duration of a handoff is T and 3 CEs are occupied in this handoff process. 1 CE is enough for the call, so the rest 2 CEs must be allocated

to the handoff. Provided that 3 CEs are evenly used, then for each CE, its traffic of call is T/3, while its traffic of handoff is 2T/3.

If softer handoff occurs between cells of a BTS in this duration, the traffic on the traffic channel of each CE should be further broken down.



47/189

1.


Suppose there are two traffic channels in the second one of the above 3 CEs, the total traffic on the two channels are the same as that of the CE. Then

the traffic of call on each traffic channel is T/3/2 and the traffic of handoff is 2T/3/2. The rest traffic on this channel, T (T/3/2) (2T/3/2), is the traffic of

softer handoff.

From the above, we can summarize the following points:

1. The traffic of call for each CE can be obtained by dividing the call duration by the number of CEs.

2. The traffic of handoff for each CE can be got by deducting the traffic of call from the total traffic.

3. The traffic of call on the traffic channel (TCH) of a CE can be calculated by dividing the traffic of call of that CE by the number of TCHs.

4. The traffic of handoff on each TCH of a CE can be calculated by dividing the traffic of handoff of that CE by the number of TCHs.

5. The traffic of softer handoff on each TCH of a CE can be got by deducting the part for call and handoffs of that CE from the total traffic of that CE.

With the traffic of each CE and TCH, we can apportion the traffic among the cells/carriers of each BTS to calculate the traffic of each BTS.

Apportionment of Traffic:

Call Soft Handoff Softer HandoffCE TCH CE TCH CE TCH

T/3/2 T-T/3 /2 - T-T/3/2- T-T/3 /2T/3

T/3/2T-T/3

T-T/3 /2 - T-T/3/2- T-T/3 /2

T/3 T/3 T-T/3 T-T/3 - -

T/3 T/3 T-T/3 T-T/3 - -

CE3 BTS3

CE2 BTS2

CE1 BTS1

B

S

C

TCH at Air Interface

TCH1

TCH2

TCH3

TCH4



48/189

1.




1


49/189

1.



1


50/189

1.



3.4.1.3.1 GbcVocErl (Global Carrier Voice Erlang as Source BSS)


S

LC Res

UmaOrg_A1fAssReq_Du

ration

Request Call Duration From

Originating To Assign(Second)FL

Duration from the time when BS receives an origination

message from MS to the time when BS receives an

assignment request from MSC

C

GC

AvfAssReq_AvfSvcAss_

Duration

Call Duration From Assign

Requesting To Traffic

Assign(Second)

FL

Duration from the time when BS receives the assignment

request from MSC to the time when BS sends channel

assignment message to MS

C

GC

AvfSvcAss_AvfAssCmp_

Dur

Call Duration From Originating

To Assign(Second)FL

Duration from the time when BS sends channel assignment

message to MS to the time when BS sends an assignment

complete message to MSC

C

GC

AvrAssCmp_AvfRlsReq_

Dur

Call Duration From Finishing

Assign To Requesting

Release(Second)

FL

Duration from the time when BS sends the assignment

complete message to MSC to the time when BS sends to

MSC a clear request (this time period is the conversation

process)

C

GC

AvfRlsReq_EndPrc_Dur

Call Duration From

Requesting Release To

resource release(Second)

FLDuration from the time when BS sends to MSC a clear

request to the time of Clear Complete

C

GC


1


51/189

1.


3.4.1.3.2 ClcVocErl (Cell Carrier Voice Erlang as Source BSS)


LC Res

UmaOrg_A1fAssReq_Du

ration



Duration from the time when BS receives an origination

message from MS to the time when BS receives an


C CC


Duration



Assign(Second)

FL




C CC


CallDur

Call Duration From Traffic

Assign To Assign

Finished(Second)

FL

Call Duration from the time when BS sends channel

assignment message to MS to the time when BS sends an

assignment complete message to MSC

C CC


SHoDur

Soft Handoff Duration From

Traffic Assign To Assign

Finished(Second)

FL

Soft Handoff Duration from the time when BS sends channel

assignment message to MS to the time when BS sends an

assignment complete message to MSC

C CC


SSHoDur

Softer Handoff Duration From

Traffic Assign To Assign

Finished(Second)

FL

Softer Handoff Duration from the time when BS sends

channel assignment message to MS to the time when BS

sends an assignment complete message to MSC

C CC


CallDur


Finished To Requesting

Release(Second)

FL

Call Duration from the time when BS sends the assignment


MSC a clear request

C CC


ShoDur


Assign Finished To

Requesting Release(Second)

FL

Soft Handoff Duration from the time when BS sends the

assignment complete message to MSC to the time when BS

sends to MSC a clear request

C CC


SSHoDur


Assign Finished To

Requesting Release(Second)

FL

Softer Handoff Duration from the time when BS sends the

assignment complete message to MSC to the time when BS

sends to MSC a clear request

C CC


1.


52/189

1.


AvfRlsReq_EndPrc_Call

Dur

Call Duration From



FLCall Duration from the time when BS sends to MSC a clear

request to the time of Clear CompleteC CC

AvfRlsReq_EndPrc_Sho

Dur




FLSoft Handoff Duration from the time when BS sends to MSC

a clear request to the time of Clear CompleteC CC

AvfRlsReq_EndPrc_SSH

oDur




FLSofter Handoff Duration from the time when BS sends to

MSC a clear request to the time of Clear CompleteC CC


As the entire process from the call setup to the release is divided into 5 time periods as per the standard protocol, the users can define the call duration

by themselves to meet their specific requirements. It is recommended to define the call duration as the follows:

Call duration: CallDur = AvfSvcAss_AvfAssCmp (T3)

+ AvrAssCmp_AvfRlsReq (T4)+ AvfRlsReq_EndPrc (T5)

Traffic (Erl) in unit timeT

CallDurT

where the numerator is the total call duration within the time T

As in the time period T3, T4 and T5, handoff may occur. So the traffic during these periods includes not only the traffic of calls, but also the traffic of softhandoff and/or softer handoff.

From the above description and analysis, we can calculate the following:

Call Duration:

CallDur = AvfSvcAss_AvfAssCmp_CallDur

+ AvrAssCmp_AvfRlsReq_CallDur


1.


53/189


+ AvfRlsReq_EndPrc_CallDur

Soft Handoff Duration:

SHODur = AvfSvcAss_AvfAssCmp_SHODur+ AvrAssCmp_AvfRlsReq_SHODur

+ AvfRlsReq_EndPrc_SHODur

Softer Handoff Duration

SSHODur = AvfSvcAss_AvfAssCmp_SSHODur

+ AvrAssCmp_AvfRlsReq_SSHODur

+ AvfRlsReq_EndPrc_SSHODur

And the traffics in unit time are calculated as follows:

Traffic of call:T

CallDurT

Traffic of soft handoff:T

SHODurT

Traffic of softer handoff:T

SSHODurT

As the above traffic is calculated based on the usage of CEs and TCHs, the traffic of the BTS or Cell where these CEs and TCHs are can be calculated.

And the traffic of call, soft handoff and softer handoff can be calculated separately for the BTS or Cell.

For example, for a cell:

Its traffic of calls is the sum of the traffic of calls on all of its TCHs. Its traffic of soft handoffs is the sum of the traffic of softer handoffs on all of its TCHs.

Its traffic of softer handoffs is the sum of the traffic of softer handoffs on all of its TCHs.


1.


54/189


3.4.2 Inter-BSS Traffic


The inter-BSS traffic is the traffic of calls that are handed off from other BSSs to this BSS and occupy the system resources of this BSS. As only

handoff is involved in this process, this type of traffic is actually the traffic of handoffs.


The same as that for intra-BSS traffic

3.4.2.2.1 GbcVocErlTgtBss (Global Carrier Voice Erlang as Target BSS)


S

LC Res

HODurationVoice Handoff TCH

Duration(Second)FL The traffic of handoff in the time period T4 C GC

3.4.2.2.2 ClcVocErlTgtBss (Cell Carrier Voice Erlang as Target BSS)


S

LC Res

SHoDuration Soft Handoff TCHDuration(Second)

FL The traffic of soft handoff in the time period T4 C CC

SSHoDurationSofter Handoff TCH

Duration(Second)FL The traffic of softer handoff in the time period T4 C CC


1.


55/189



The duration and traffic of inter-BSS handoff are calculated as follows:Soft Handoff Duration: SHODur = SHoDuration

Softer Handoff Duration: SSHODur = SSHoDuration

Traffic of Soft Handoff:T

SHODurT

Traffic of Softer Handoff:T

SSHODurT

4 SMS

4.1 SMS on Control Channels


Generally, short messages occur on the control channel, and they are divided into two types: short messages originated by the mobile station (MS)

and those terminated by the mobile switching center (MSC). Therefore, count the numbers of successful and failed short messages of the two types

respectively.

4.1.2 Protocol Flow

SMS originated by MS


1.


56/189


SMS terminated by MSC


1.


57/189



4.1.3.1 GbcSmsCallCch (Global Carrier SMS Call on Control Channel)


S

LC Res

CCHOriginTotalNumCCH Originating SM Total

NumFL

In the SMS originated by MS, add 1 to the counter every time

when BS receives a SMS Delivery message from MS.C

GC

CCHOriginReqNum

CCH Originating SM Request

Num FL

In the SMS originated by MS, add 1 to the counter every time

when BS sends a ADDS Deliver Ack message to MSC. C

GC

CCHPagingTotalNum CCH Paging SM Total Num FLIn the SMS terminated by MSC, add 1 to the counter every

time when BS receives a ADDS Deliver message from MSC.C

GC

CCHPagingReqNumCCH Paging SM Request

NumFL

In the SMS terminated by MSC, add 1 to the counter every

time when BS sends a ADDS Deliver Ack message to MSC.C

GC


Call Origination Success Rate of SMS on control channel = 00%1equestNumOriginateR

uccessNumOriginateS

Paging Success Rate of SMS on control channel = 00%1estNumPagingRequ

essNumPagingSucc

Overall Success Rate of SMS on control channel


1.


58/189


= 00%1estNumPagingRequequestNumOriginateR

essNumPagingSuccuccessNumOriginateS

+

+

4.2 SMS on Traffic Channels

4.2.1 Call Origination (SMS)


The performance data in call origination (SMS) involves the global carrier and the cell carrier (sector). After the base station (BS) receives an

origination message from the mobile station (MS), it will first determine if it is a call of short message on the traffic channel based on its service option.

If yes, it will go on the call flow for SMS, which is similar to that for voice services, and collect related data accordingly.




1.


59/189



4.2.1.3.1 GbcSmsOrgCall (Global Carrier SMS Originating Call)


S

LC Res


1.

Add 1 to the counter every time when BS receives an


60/189




CallSuccessNum Voice Originating RequestNum

FL Add 1 to the counter every time when BS sends theAssignment Complete message to MSC.

C GC





C

GC



GC

OtherFailureNum Other Reason Success Num FLAdd 1 to the counter every time when the call origination fails

for reasons other than the above.C

GC

4.2.1.3.2 ClcSmsOrgCall (Cell Carrier SMS Originating Call)


S

LC Res

MSOriginateNum MS Originating NumIN Add 1 to the counter every time when BS receives an

origination message from MS.C CC


Num







C CC






1.


61/189




umOriginateN

SuccessNum


umOriginateN

BlockNum


umOriginateN



4.2.2 Paging (SMS)


The performance data in paging (SMS) involves the global carrier and the cell carrier (sector). After the base station (BS) receives a paging request

from the mobile switching center (MSC), it will broadcast the message. And when BS receives the page response from a mobile station (MS), it will goon the paging flow for SMS services and collect related data accordingly.




1.


62/189



1.

4 2 2 3 Counter Table Detail


63/189



4.2.2.3.1 GbcSmsPagCall (Global Carrier SMS Paging Call)


S

LC Res

PagingMsNum MS Paging Num FLAdd 1 to the counter every time when BS receives a paging

request from MSC.C

GC

PageResponceNum MS Paging Response Num FL

Add 1 to the counter every time when BS receives a page

response message from MS. C

GC

CallSuccessNum Voice Paging Request Num FLAdd 1 to the counter every time when BS sends the

Assignment Complete message to MSC.C

GC





C

GC



GC

OtherFailureNum Other Reason Success Num FLAdd 1 to the counter every time when the paging fails for

reasons other than the above.C

GC

4.2.2.3.2 ClcSmsPagCall (Cell Carrier SMS Paging Call)


S

LC Res

PagingMsNum MS Paging NumIN Add 1 to the counter every time when BS receives a paging

request from MSC.C CC


1.

P R N MS P i R NIN Add 1 to the counter every time when BS receives a page

C CC


64/189


PageResponceNum MS Paging Response Numy p g

response message from MS.C CC

CallSuccessNum Voice Paging Request Num IN Add 1 to the counter every time when BS sends theAssignment Complete message to MSC.

C CC





C CC



OtherFailureNum Other Reason Success NumIN Add 1 to the counter every time when the paging fails for

reasons other than the above.C CC


Paging Response Rate= 100%

PagingNum

onseNumPagingResp

Paging Success Rate = 100%

onseNumPagingResp

SuccessNum

Paging Block Rate = 100%

onseNumPagingResp

BlockNum


1.



65/189


Paging External Interrupt Rate = 100%

onseNumPagingResp



4.2.3 SMS Calls


As the call process of SMS includes call origination (SMS) and paging (SMS), its data comes from the data of the two.


Call Success Rate (SMS) = 100%+

+

MTMO

MTMO


SuccessNumSuccessNum

Call Block Rate (SMS) = 0%10onseNumPagingRespumOriginateN

BlocksNumBlockNum

MTMO

MTMO +

+

Call External Interrupt Rate (SMS)

= 100%+

+

MTMO

MTMO


terruptNumExternalInterruptNumExternalIn



1.

4 2 4 SMS Handoff


66/189


4.2.4 SMS Handoff

As the duration of SMS on the traffic channel is very short, its duration of handoff will not be counted.

4.2.5 SMS Release


The releases on the traffic channel in SMS are divided into two types: normal releases (hang up) from the mobile station (MS), base station (BS) and

mobile switching center (MSC), and abnormal release (call drop) from the MS, BS and MSC. Therefore, count the numbers of normal and abnormal

releases respectively.



1.


67/189



1.



68/189


4.2.5.3.1 GbcSmsRls (Global Carrier SMS Release)


S

LC Res

CM_NorRlsSNum Normal Release Num FLAdd 1 to the counter every time when BS receives a normal

release message from MS or MSC.C

GC

CM_SysDorpNum System Drop Num FLAdd 1 to the counter every time when a call exception

message from BS or MSC is received.C

GC

CM_RadioDropNum Radio Drop Num FLAdd 1 to the counter every time when a call exception

radio message from BS or MSC is received.C

GC

4.2.5.3.2 ClcVocRls (Cell Carrier Voice Release)


LC Res

CM_NorRlsSNum Normal Release NumIN Add 1 to the counter every time when BS receives a normal

release message from MS or MSC.C CC

CM_SysDorpNum System Drop NumIN Add 1 to the counter every time when a call exception

message from BS or MSC is received.C CC

CM_RadioDropNum Radio Drop Num

IN Add 1 to the counter every time when a call exception

radio message from BS or MSC is received. C CC


1.



69/189


Call Drop Rate = 100%+

DropNumaseNumNormalRele

DropNum

4.2.6 SMS Traffic


In SMS, the traffic on the traffic channel is similar to that on the traffic channel in voice services. But as no handoff occurs in SMS, its traffic is

completely the traffic of calls.


Please refer to the traffic model and flow for voice services.


4.2.6.3.1 GbcSmsErl (Global Carrier SMS Erlang as Source BSS)


S

LC Res

UmaOrg_A1fAssReq_Du

ration



Duration from the time when BS receives an originationmessage from MS to the time when BS receives an


CGC


Duration



Assign(Second)

FL




C

GC


1.

AvfSvcAss_AvfAssCmp_ Call Duration From OriginatingFL


message to MS to the time when BS sends an assignment C

GC


70/189


Dur To Assign(Second)FL message to MS to the time when BS sends an assignment


C


Dur

Call Duration From Finishing

Assign To Requesting

Release(Second)

FL



MSC a clear request (this time period is the conversation

process)

C

GC

AvfRlsReq_EndPrc_Dur

Call Duration From




request to the time of Clear Complete

C

GC

4.2.6.3.2 ClcSmsErl (Cell Carrier SMS Erlang as Source BSS)


S

LC Res

UmaOrg_A1fAssReq_Du

ration



Duration from the time when BS receives an originationmessage from MS to the time when BS receives an


C CC


Duration



Assign(Second)

FL




C CC

AvfSvcAss_AvfAssCmp_CallDur

Call Duration From Traffic

Assign To Assign

Finished(Second)

FL


message to MS to the time when BS sends an assignment


C CC


1.

AvrAssCmp AvfRlsReqCall Duration From Assign




71/189



CallDur

Finished To Requesting

Release(Second)

FLcomplete message to MSC to the time when BS sends to

MSC a clear request (this time period is the conversationprocess)

C CC

AvfRlsReq_EndPrc_Call

Dur

Call Duration From




request to the time of Clear CompleteC CC

4.2.6.4 Calculation MethodAs the entire process from the call setup to the release is divided into 5 time periods as per the standard protocol, the users can define the call duration

by themselves to meet their specific requirements. It is recommended to define the call duration as the follows:

Call duration: CallDur = AvfSvcAss_AvfAssCmp (T3)

+ AvrAssCmp_AvfRlsReq (T4)

+ AvfRlsReq_EndPrc (T5)

Traffic (Erl) in unit timeT

CallDurT

where the numerator is the total call duration within the time T

5 Data Services

5.1 Data Burst


It records the short data on the control channel from PDSN, originated by PDSN and by MS.


1.

5.1.2 Protocol Flow


72/189



1.


73/189



1.


74/189



1.



75/189


5.1.3.1 GlbDatBrst Global Data Burst


S

LC Res

TCHOriginTotalNumTCH Originating SM Total

NumFL

Request number of data bursts originated by MS on the traffic

channelC

GC

TCHOriginReqNumTCH Originating SM Request

NumFL

Success number of data bursts originated by MS on the traffic

channelC

GC

TCHPagingTotalNum TCH Paging SM Total Num FLRequest number of data bursts originated by PDSN on the

traffic channelC

GC

TCHPagingReqNum TCH Paging SM Request Num FLSuccess number of data bursts originated by PDSN on the

traffic channelC

GC

CCHOriginTotalNumCCH Originating SM Total

NumFL

Request number of data bursts originated by MS on the

control channelC

GC

CCHOriginReqNumCCH Originating SM Request

NumFL

Success number of data bursts originated by MS on the

control channelC

GC

CCHPagingTotalNum CCH Paging SM Total Num FLRequest number of data bursts originated by PDSN on the

control channelC

GC

CCHPagingReqNumCCH Paging SM Request

NumFL

Success number of data bursts originated by PDSN on the

control channelC

GC


1.



76/189


Call Origination Success Rate of Data Burst on traffic channel = 00%

TCH

TCH 1lNumOriginTota

NumOriginSucc

Paging Success Rate of Data Burst on traffic channel = 00%

TCH

TCH 1lNumPagingTota

NumPagingSucc

Call Origination Success Rate of Data Burst on control channel = 00%1lNumOriginTota

NumOriginSucc

CCH

CCH

Paging Success Rate of Data Burst on control channel = 00%1lNumPagingTota

NumPagingSucc

CCH

CCH

Overall Success Rate of Data Burst = 00%1lNumPagingTotalNumOriginTota

NumPagingSuccNumOriginSucc

+

+

5.2 RLP Data Flow


It records the forward and reverse data flow as well as the data retransmission quality in RLP link layer.


1.

5.2.2 Protocol Flow


77/189


None


5.2.3.1 GlbRLPFlux Global Radio Link Protocol Flux


S

LC Res

TxTotalFrame Forward Transmit Total Frame FLRecord the size of the forward data packet every time when it

is transmitted.C

GC

TxRexmitFrameForward Resending Total

FrameFL

Record the size of the forward data packet every time when it

is retransmitted.C

GC

RxTotalFrame Reverse Transmit Total Frame FLRecord the size of the reverse data packet every time when it

is transmitted.C

GC

RxRexmitFrame Reverse Resending TotalFrame

FL Record the size of the reverse data packet every time when itis retransmitted.

C GC


Forward Flow Rate = )/( sBYTET

meTxTotalFra

Forward Retransmission Rate = )/( sBYTET

ameTxRexmitFr


1.

Reverse Flow Rate = )/( sBYTET

meRxTotalFra


78/189


T

Reverse Retransmission Rate = )/( sBYTET

ameRxRexmitFr

5.3 Call Service (Data)

5.3.1 Call Origination (Data)


The performance data in call origination (data) involves the global carrier and the cell carrier. After the base station (BS) receives an origination

message from the mobile station (MS), it will first determine if it is a call of data services based on the parameters. If yes, it will go on the call flow for

data services and collect related data accordingly.




1.


79/189



1.



80/189


5.3.1.3.1 GbcDatOrigCall (Global Carrier Data Originating Call)


S

LC Res




Num

FLAdd 1 to the counter every time when BS sends the

Assignment Complete message to MSC.

CGC





C

GC



GC

OtherFailureNum Other Reason Success Num FL

Add 1 to the counter every time when the call origination fails

for reasons other than the above. C

GC

5.3.1.3.2 ClcDatOrgCall (Cell Carrier Data Originating Call)


S

LC Res

MSOriginateNum MS Originating Num IN Add 1 to the counter every time when BS receives anorigination message from MS.

C CC


Num




1.




CIC CE Walsh Code and Power)

C CC


81/189









umOriginateN

SuccessNum


umOriginateN

BlockNum


umOriginateN



5.3.2 Paging (Data)


The performance data in paging (data services) involves the global carrier and the cell carrier. After the base station (BS) receives a paging request


1.

from the mobile switching center (MSC), it will broadcast the message. And when BS receives the page response from a mobile station (MS), it will go

on the paging flow for data services and collect related data accordingly.


82/189





1.


83/189


3G RLSA P

3G 1X Performance Management Indexes and Their Calculation

Documents

Transcript of 3G 1X Performance Management Indexes and Their Calculation