3G 1X Performance Management Indexes and Their Calculation

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
3G RLSA Performance Management Indexes and Their Calculation 1.
Revision History
Version 1.0 Date 2005-11-20 Reviser GUO Zhongcheng First draft Description
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.
ZTE Confidential Proprietary
Page 1
Contents
1 2 Abbreviation .................................................................................................................................................................................................................................... 14 Registration ..................................................................................................................................................................................................................................... 15 2.1 Function Description ............................................................................................................................................................................................................ 15 2.2 Protocol Flow ........................................................................................................................................................................................................................ 15 2.3 Counter Table Detail ............................................................................................................................................................................................................ 17 2.3.1 GbcReg (Global Carrier Registration) ................................................................................................................................................................. 17 2.3.2 ClcReg (Cell Carrier Registration) ....................................................................................................................................................................... 19 2.4 Calculation Method .............................................................................................................................................................................................................. 21 Voice Services ................................................................................................................................................................................................................................ 21 3.1 Call Services (Voice)............................................................................................................................................................................................................ 21 3.1.1 Call Origination (Voice) .......................................................................................................................................................................................... 21 3.1.1.1 Function Description................................................................................................................................................................................. 21 3.1.1.2 Protocol Flow............................................................................................................................................................................................. 22 3.1.1.3 Counter Table Detail ................................................................................................................................................................................. 23 3.1.1.3.1 GbcVocOrigCall (Global Carrier Voice Originating Call) ............................................................................................................. 23 3.1.1.3.2 ClcVocOrgCall (Cell Carrier Voice Originating Call) .................................................................................................................... 23 3.1.1.4 Calculation Method ................................................................................................................................................................................... 24 3.1.2 Paging (Voice)......................................................................................................................................................................................................... 25 3.1.2.1 Function Description................................................................................................................................................................................. 25 3.1.2.2 Protocol Flow............................................................................................................................................................................................. 25 3.1.2.3 Counter Table Detail ................................................................................................................................................................................. 27 3.1.2.3.1 GbcVocPagCall (Global Carrier Voice Paging Call) .................................................................................................................... 27 3.1.2.3.2 ClcVocPagCall (Cell Carrier Voice Paging Call)........................................................................................................................... 27 3.1.2.4 Calculation Method ................................................................................................................................................................................... 28 3.1.3 Calls (Voice) ............................................................................................................................................................................................................ 29 3.1.3.1 Function Description................................................................................................................................................................................. 29
Page 2
3.2
3.3
3.4
3.1.3.2 Calculation Method ................................................................................................................................................................................... 29 Handoff (Voice)..................................................................................................................................................................................................................... 30 3.2.1 Intra-BSS Handoff .................................................................................................................................................................................................. 30 3.2.1.1 Function Description................................................................................................................................................................................. 30 3.2.1.2 Protocol Flow............................................................................................................................................................................................. 30 3.2.1.3 Counter Table Detail ................................................................................................................................................................................. 32 3.2.1.3.1 GbcVocHoSrcBss (Global Carrier Voice Handoff as Source BSS) ........................................................................................... 32 3.2.1.3.2 ClcVocHoSrcBss (Cell Carrier Voice Handoff as Source BSS) ................................................................................................. 33 3.2.1.4 Calculation Method ................................................................................................................................................................................... 35 3.2.2 Inter-BSS Handoff .................................................................................................................................................................................................. 36 3.2.2.1 Function Description................................................................................................................................................................................. 36 3.2.2.2 Protocol Flow............................................................................................................................................................................................. 36 3.2.2.3 Counter Table Detail ................................................................................................................................................................................. 38 3.2.2.3.1 GbcVocHoTgtBss (Global Carrier Voice Handoff as Target BSS)............................................................................................. 38 3.2.2.3.2 ClcVocHoTgtBss (Cell Carrier Voice Handoff as Target BSS) ................................................................................................... 39 3.2.2.4 Calculation Method ................................................................................................................................................................................... 41 Release (Voice) .................................................................................................................................................................................................................... 42 3.3.1 Function Description .............................................................................................................................................................................................. 42 3.3.2 Protocol Flow........................................................................................................................................................................................................... 42 3.3.3 Counter Table Detail............................................................................................................................................................................................... 44 3.3.3.1 GbcVocRls (Global Carrier Voice Release) .......................................................................................................................................... 44 3.3.3.2 ClcVocRls (Cell Carrier Voice Release) ................................................................................................................................................ 44 3.3.4 Calculation Method................................................................................................................................................................................................. 45 Traffic (Voice) ........................................................................................................................................................................................................................ 45 3.4.1 Intra-BSS Traffic ..................................................................................................................................................................................................... 45 3.4.1.1 Function Description................................................................................................................................................................................. 45 3.4.1.2 Protocol Flow............................................................................................................................................................................................. 47 3.4.1.3 Counter Table Detail ................................................................................................................................................................................. 49
Page 3
3.4.1.3.1 GbcVocErl (Global Carrier Voice Erlang as Source BSS) .......................................................................................................... 49 3.4.1.3.2 ClcVocErl (Cell Carrier Voice Erlang as Source BSS) ................................................................................................................ 50 3.4.1.4 Calculation Method ................................................................................................................................................................................... 51 3.4.2 Inter-BSS Traffic ..................................................................................................................................................................................................... 53 3.4.2.1 Function Description................................................................................................................................................................................. 53 3.4.2.2 Protocol Flow............................................................................................................................................................................................. 53 3.4.2.2.1 GbcVocErlTgtBss (Global Carrier Voice Erlang as Target BSS) ............................................................................................... 53 3.4.2.2.2 ClcVocErlTgtBss (Cell Carrier Voice Erlang as Target BSS)...................................................................................................... 53 3.4.2.3 Calculation Method ................................................................................................................................................................................... 54 SMS.................................................................................................................................................................................................................................................. 54 4.1 SMS on Control Channels .................................................................................................................................................................................................. 54 4.1.1 Function Description .............................................................................................................................................................................................. 54 4.1.2 Protocol Flow........................................................................................................................................................................................................... 54 4.1.3 Counter Table Detail............................................................................................................................................................................................... 56 4.1.3.1 GbcSmsCallCch (Global Carrier SMS Call on Control Channel) ...................................................................................................... 56 4.1.4 Calculation Method................................................................................................................................................................................................. 56 4.2 SMS on Traffic Channels .................................................................................................................................................................................................... 57 4.2.1 Call Origination (SMS) ........................................................................................................................................................................................... 57 4.2.1.1 Function Description................................................................................................................................................................................. 57 4.2.1.2 Protocol Flow............................................................................................................................................................................................. 57 4.2.1.3 Counter Table Detail ................................................................................................................................................................................. 58 4.2.1.3.1 GbcSmsOrgCall (Global Carrier SMS Originating Call).............................................................................................................. 58 4.2.1.3.2 ClcSmsOrgCall (Cell Carrier SMS Originating Call) .................................................................................................................... 59 4.2.1.4 Calculation Method ................................................................................................................................................................................... 60 4.2.2 Paging (SMS).......................................................................................................................................................................................................... 60 4.2.2.1 Function Description................................................................................................................................................................................. 60 4.2.2.2 Protocol Flow............................................................................................................................................................................................. 60 4.2.2.3 Counter Table Detail ................................................................................................................................................................................. 62
Page 4
4.2.2.3.1 GbcSmsPagCall (Global Carrier SMS Paging Call) .................................................................................................................... 62 4.2.2.3.2 ClcSmsPagCall (Cell Carrier SMS Paging Call) .......................................................................................................................... 62 4.2.2.4 Calculation Method ................................................................................................................................................................................... 63 4.2.3 SMS Calls ................................................................................................................................................................................................................ 64 4.2.3.1 Function Description................................................................................................................................................................................. 64 4.2.3.2 Calculation Method ................................................................................................................................................................................... 64 4.2.4 SMS Handoff ........................................................................................................................................................................................................... 65 4.2.5 SMS Release .......................................................................................................................................................................................................... 65 4.2.5.1 Function Description................................................................................................................................................................................. 65 4.2.5.2 Protocol Flow............................................................................................................................................................................................. 65 4.2.5.3 Counter Table Detail ................................................................................................................................................................................. 67 4.2.5.3.1 GbcSmsRls (Global Carrier SMS Release) .................................................................................................................................. 67 4.2.5.3.2 ClcVocRls (Cell Carrier Voice Release)......................................................................................................................................... 67 4.2.5.4 Calculation Method ................................................................................................................................................................................... 68 4.2.6 SMS Traffic .............................................................................................................................................................................................................. 68 4.2.6.1 Function Description................................................................................................................................................................................. 68 4.2.6.2 Protocol Flow............................................................................................................................................................................................. 68 4.2.6.3 Counter Table Detail ................................................................................................................................................................................. 68 4.2.6.3.1 GbcSmsErl (Global Carrier SMS Erlang as Source BSS) .......................................................................................................... 68 4.2.6.3.2 ClcSmsErl (Cell Carrier SMS Erlang as Source BSS) ................................................................................................................ 69 4.2.6.4 Calculation Method ................................................................................................................................................................................... 70 Data Services.................................................................................................................................................................................................................................. 70 5.1 Data Burst.............................................................................................................................................................................................................................. 70 5.1.1 Function Description .............................................................................................................................................................................................. 70 5.1.2 Protocol Flow........................................................................................................................................................................................................... 71 5.1.3 Counter Table Detail............................................................................................................................................................................................... 74 5.1.3.1 GlbDatBrstGlobal Data Burst .......................................................................................................................................................... 74 5.1.4 Calculation Method................................................................................................................................................................................................. 75
Page 5
5.2
5.3
5.4
RLP Data Flow...................................................................................................................................................................................................................... 75 5.2.1 Function Description .............................................................................................................................................................................................. 75 5.2.2 Protocol Flow........................................................................................................................................................................................................... 76 5.2.3 Counter Table Detail............................................................................................................................................................................................... 76 5.2.3.1 GlbRLPFluxGlobal Radio Link Protocol Flux................................................................................................................................ 76 5.2.4 Calculation Method................................................................................................................................................................................................. 76 Call Service (Data) ............................................................................................................................................................................................................... 77 5.3.1 Call Origination (Data) ........................................................................................................................................................................................... 77 5.3.1.1 Function Description................................................................................................................................................................................. 77 5.3.1.2 Protocol Flow............................................................................................................................................................................................. 77 5.3.1.3 Counter Table Detail ................................................................................................................................................................................. 79 5.3.1.3.1 GbcDatOrigCall (Global Carrier Data Originating Call)............................................................................................................... 79 5.3.1.3.2 ClcDatOrgCall (Cell Carrier Data Originating Call) ...................................................................................................................... 79 5.3.1.4 Calculation Method ................................................................................................................................................................................... 80 5.3.2 Paging (Data) .......................................................................................................................................................................................................... 80 5.3.2.1 Function Description................................................................................................................................................................................. 80 5.3.2.2 Protocol Flow............................................................................................................................................................................................. 81 5.3.2.3 Counter Table Detail ................................................................................................................................................................................. 83 5.3.2.3.1 GbcDatPagCall (Global Carrier Data Paging Call) ...................................................................................................................... 83 5.3.2.3.2 ClcDatOrgCall (Cell Carrier Data Paging Call)............................................................................................................................. 83 5.3.2.4 Calculation Method ................................................................................................................................................................................... 84 5.3.3 Call Service (Data) ................................................................................................................................................................................................. 85 5.3.3.1 Function Description................................................................................................................................................................................. 85 5.3.3.2 Calculation Method ................................................................................................................................................................................... 85 Handoff (Data Services) ...................................................................................................................................................................................................... 86 5.4.1 Intra-BSS Handoff .................................................................................................................................................................................................. 86 5.4.1.1 Function Description................................................................................................................................................................................. 86 5.4.1.2 Protocol Flow............................................................................................................................................................................................. 86
Page 6
5.5
5.6
5.4.1.3 Counter Table Detail ................................................................................................................................................................................. 88 5.4.1.3.1 GbcDatHoSrcBss (Global Carrier Data Handoff as Source BSS)............................................................................................. 88 5.4.1.3.2 ClcDatHoSrcBss (Cell Carrier Data Handoff as Source BSS) ................................................................................................... 89 5.4.1.4 Calculation Method ................................................................................................................................................................................... 91 5.4.2 Inter-BSS Handoff .................................................................................................................................................................................................. 92 5.4.2.1 Function Description................................................................................................................................................................................. 92 5.4.2.2 Protocol Flow............................................................................................................................................................................................. 92 5.4.2.3 Counter Table Detail ................................................................................................................................................................................. 94 5.4.2.3.1 GbcDatHoTgtBss (Global Carrier Data Handoff as Target BSS)............................................................................................... 94 5.4.2.3.2 ClcDatHoTgtBss (Cell Carrier Data Handoff as Target BSS)..................................................................................................... 95 5.4.2.4 Calculation Method ................................................................................................................................................................................... 97 Release (Data Service) ....................................................................................................................................................................................................... 98 5.5.1 Function Description .............................................................................................................................................................................................. 98 5.5.2 Protocol Flow........................................................................................................................................................................................................... 98 5.5.3 Counter Table Detail............................................................................................................................................................................................. 104 5.5.3.1 GbcDatRls (Global Carrier Data Release) .......................................................................................................................................... 104 5.5.3.2 ClcDatRls (Cell Carrier Data Release) ................................................................................................................................................ 104 5.5.4 Calculation Method............................................................................................................................................................................................... 105 Traffic (Data Services) ....................................................................................................................................................................................................... 105 5.6.1 Intra-BSS Traffic ................................................................................................................................................................................................... 105 5.6.1.1 Function Description............................................................................................................................................................................... 105 5.6.1.2 Protocol Flow........................................................................................................................................................................................... 107 5.6.1.3 Counter Table Detail ............................................................................................................................................................................... 109 5.6.1.3.1 GbcDatErl (Global Carrier Data Erlang as Source BSS) .......................................................................................................... 109 5.6.1.3.2 ClcDatErl (Cell Carrier Data Erlang as Source BSS) ................................................................................................................ 110 5.6.1.4 Calculation Method ..................................................................................................................................................................................111 5.6.2 Inter-BSS Traffic ................................................................................................................................................................................................... 113 5.6.2.1 Function Description............................................................................................................................................................................... 113
Page 7
5.6.2.2 Protocol Flow........................................................................................................................................................................................... 113 5.6.2.3 Counter Table Detail ............................................................................................................................................................................... 113 5.6.2.3.1 GbcDatErlTgtBss (Global Carrier Data Erlang as Target BSS) ............................................................................................... 113 5.6.2.3.2 ClcDatErlTgtBss (Cell Carrier Data Erlang as Target BSS) ..................................................................................................... 113 5.6.2.4 Calculation Method ................................................................................................................................................................................. 114 SCH ................................................................................................................................................................................................................................................ 114 6.1 Function Description .......................................................................................................................................................................................................... 114 6.2 Protocol Flow ...................................................................................................................................................................................................................... 115 6.3 Counter Table Detail .......................................................................................................................................................................................................... 115 6.3.1 ClcFSCHInfo (Cell Carrier Forward SCH Information) ................................................................................................................................... 115 6.3.2 ClcRSCHInfo (Cell Carrier Reverse SCH Information)................................................................................................................................... 117 6.4 Calculation Method ............................................................................................................................................................................................................ 119 Concurrent Services .................................................................................................................................................................................................................... 121 7.1 Setup/Release Model ........................................................................................................................................................................................................ 121 7.2 Traffic Calculation Model................................................................................................................................................................................................... 124 7.3 Concurrent Voice Services ............................................................................................................................................................................................... 126 7.3.1 Call Origination (Concurrent Voice Services)................................................................................................................................................... 126 7.3.1.1 Function Description............................................................................................................................................................................... 126 7.3.1.2 Protocol Flow........................................................................................................................................................................................... 126 7.3.1.3 Counter Table Detail ............................................................................................................................................................................... 127 7.3.1.3.1 GbcConVocOrgCall (Global Carrier Concurrent Voice Originating Call)................................................................................ 127 7.3.1.3.2 ClcConVocOrgCall (Cell Carrier Concurrent Voice Originating Call) ...................................................................................... 128 7.3.1.4 Calculation Method ................................................................................................................................................................................. 129 7.3.2 Paging (Concurrent Voice Services).................................................................................................................................................................. 129 7.3.2.1 Function Description............................................................................................................................................................................... 129 7.3.2.2 Protocol Flow........................................................................................................................................................................................... 129 7.3.2.3 Counter Table Detail ............................................................................................................................................................................... 131 7.3.2.3.1 GbcConVocPagCall (Global Carrier Concurrent Voice Paging Call) ...................................................................................... 131
Page 8
7.4
7.5
7.6
7.3.2.3.2 ClcConVocPagCall (Cell Carrier Concurrent Voice Paging Call)............................................................................................. 131 7.3.2.4 Calculation Method ................................................................................................................................................................................. 132 Concurrent Data Services................................................................................................................................................................................................. 133 7.4.1 Call Origination (Concurrent Data Services) .................................................................................................................................................... 133 7.4.1.1 Function Description............................................................................................................................................................................... 133 7.4.1.2 Protocol Flow........................................................................................................................................................................................... 133 7.4.1.3 Counter Table Detail ............................................................................................................................................................................... 135 7.4.1.3.1 GbcConDatOrgCall (Global Carrier Concurrent Data Originating Call).................................................................................. 135 7.4.1.3.2 ClcConDatOrgCall (Cell Carrier Concurrent Data Originating Call)........................................................................................ 135 7.4.1.4 Calculation Method ................................................................................................................................................................................. 136 7.4.2 Paging (Concurrent Data Services) ................................................................................................................................................................... 137 7.4.2.1 Function Description............................................................................................................................................................................... 137 7.4.2.2 Protocol Flow........................................................................................................................................................................................... 137 7.4.2.3 Counter Table Detail ............................................................................................................................................................................... 139 7.4.2.3.1 GbcConDatPagCall (Global Carrier Concurrent Data Paging Call) ........................................................................................ 139 7.4.2.3.2 ClcConDatPagCall (Cell Carrier Concurrent Data Paging Call) .............................................................................................. 139 7.4.2.4 Calculation Method ................................................................................................................................................................................. 140 Concurrent Release........................................................................................................................................................................................................... 141 7.5.1 Function Description ............................................................................................................................................................................................ 141 7.5.2 Protocol Flow......................................................................................................................................................................................................... 141 7.5.3 Counter Table Detail............................................................................................................................................................................................. 143 7.5.3.1 GbcConRls (Global Carrier Concurrent Release).............................................................................................................................. 143 7.5.3.2 ClcConRls (Cell Carrier Concurrent Release).................................................................................................................................... 144 7.5.4 Calculation Method............................................................................................................................................................................................... 145 Concurrent Traffic............................................................................................................................................................................................................... 145 7.6.1 Function Description ............................................................................................................................................................................................ 145 7.6.2 Protocol Flow......................................................................................................................................................................................................... 146 7.6.3 Counter Table Detail............................................................................................................................................................................................. 146
Page 9
7.6.3.1 GbcConErl (Global Carrier Concurrent Erlang).................................................................................................................................. 146 7.6.3.2 ClcConErl (Cell Carrier Concurrent Erlang)........................................................................................................................................ 146 7.6.4 Calculation Method............................................................................................................................................................................................... 148 Hard Handoff................................................................................................................................................................................................................................. 148 8.1 Hard Handoff Add to a BSS.............................................................................................................................................................................................. 148 8.1.1 Function Description ............................................................................................................................................................................................ 148 8.1.2 Protocol Flow......................................................................................................................................................................................................... 148 8.1.3 Counter Table Detail............................................................................................................................................................................................. 150 8.1.3.1 GbcHdHoAdd (Global Carrier Hard Handoff Add) ............................................................................................................................. 150 8.1.3.2 ClcHdHoAddTgtBss (Cell Carrier Hard Handoff Add as Target BSS)............................................................................................. 151 8.1.4 Calculation Method............................................................................................................................................................................................... 153 8.2 Hard Handoff Off a BSS.................................................................................................................................................................................................... 153 8.2.1 Function Description ............................................................................................................................................................................................ 153 8.2.2 Protocol Flow......................................................................................................................................................................................................... 153 8.2.3 Counter Table Detail............................................................................................................................................................................................. 153 8.2.3.1 GbcHdHoDrpSrcBss (Global Carrier Hard Handoff Drop as Source BSS).................................................................................... 153 8.2.3.2 ClcHdHoDrp (Cell Carrier Hard Handoff Drop) .................................................................................................................................. 154 8.2.4 Calculation Method............................................................................................................................................................................................... 154 PCF................................................................................................................................................................................................................................................. 154 9.1 PCF Call .............................................................................................................................................................................................................................. 154 9.1.1 Function Description ............................................................................................................................................................................................ 154 9.1.2 Protocol Flow......................................................................................................................................................................................................... 155 9.1.3 Counter Table Detail............................................................................................................................................................................................. 157 9.1.3.1 GbcPcfCall (Global Carrier PCF Call).................................................................................................................................................. 157 9.1.4 Calculation Method............................................................................................................................................................................................... 158 9.2 PCF Handoff ....................................................................................................................................................................................................................... 158 9.2.1 Function Description ............................................................................................................................................................................................ 158 9.2.2 Protocol Flow......................................................................................................................................................................................................... 158
Page 10
9.3
9.4
9.5
9.6
9.2.3 Counter Table Detail............................................................................................................................................................................................. 160 9.2.3.1 GbcPcfHo (Global PCF Handoff).......................................................................................................................................................... 160 9.2.4 Calculation Method............................................................................................................................................................................................... 161 PCF Release....................................................................................................................................................................................................................... 161 9.3.1 Function Description ............................................................................................................................................................................................ 161 9.3.2 Protocol Flow......................................................................................................................................................................................................... 161 9.3.3 Counter Table Detail............................................................................................................................................................................................. 163 9.3.3.1 GbcPcfRls (Global PCF Release) ........................................................................................................................................................ 163 9.3.4 Calculation Method............................................................................................................................................................................................... 164 Transition between PCF States........................................................................................................................................................................................ 164 9.4.1 Function Description ............................................................................................................................................................................................ 164 9.4.2 Protocol Flow......................................................................................................................................................................................................... 164 9.4.3 Counter Table Detail............................................................................................................................................................................................. 164 9.4.3.1 GbcPcfSta (Global PCF Status)............................................................................................................................................................ 164 9.4.4 Calculation Method............................................................................................................................................................................................... 165 PCF Block ........................................................................................................................................................................................................................... 165 9.5.1 Function Description ............................................................................................................................................................................................ 165 9.5.2 Protocol Flow......................................................................................................................................................................................................... 165 9.5.3 Counter Table Detail............................................................................................................................................................................................. 165 9.5.3.1 GbcPcfBlk (Global Carrier PCF Block) ................................................................................................................................................ 165 9.5.4 Calculation Method............................................................................................................................................................................................... 166 PCF Traffic .......................................................................................................................................................................................................................... 166 9.6.1 Function Description ............................................................................................................................................................................................ 166 9.6.2 Protocol Flow......................................................................................................................................................................................................... 166 9.6.3 Counter Table Detail............................................................................................................................................................................................. 166 9.6.3.1 GbcPcfMacDatFlow (Global PCF Mac Data Flow) ............................................................................................................................ 166 9.6.3.2 GbcPcfMediaDatFlow (Global PCF Media Data Flow) ..................................................................................................................... 167 9.6.3.3 GbcPcfSignalDatFlow (Global PCF Signal Data Flow)..................................................................................................................... 168
Page 11
9.6.4 Calculation Method............................................................................................................................................................................................... 168 10 System Resources ....................................................................................................................................................................................................................... 168 10.1 Function Description .......................................................................................................................................................................................................... 168 10.2 Protocol Flow ...................................................................................................................................................................................................................... 168 10.3 Counter Table Detail .......................................................................................................................................................................................................... 169 10.3.1 Selector Element .................................................................................................................................................................................................. 169 10.3.2 PCF Entity.............................................................................................................................................................................................................. 169 10.3.3 Vocoder Element .................................................................................................................................................................................................. 169 10.3.4 CIC.......................................................................................................................................................................................................................... 170 10.3.5 Forward Channel Element .................................................................................................................................................................................. 170 10.3.6 Reverse Channel Element .................................................................................................................................................................................. 171 10.3.7 Traffic Channel...................................................................................................................................................................................................... 171 10.3.8 CPU ........................................................................................................................................................................................................................ 172 10.4 Calculation Method ............................................................................................................................................................................................................ 173 11 Block............................................................................................................................................................................................................................................... 173 11.1 Block (Voice Services)....................................................................................................................................................................................................... 173 11.1.1 Function Description ............................................................................................................................................................................................ 173 11.1.2 Protocol Flow......................................................................................................................................................................................................... 173 11.1.3 Counter Table Detail............................................................................................................................................................................................. 174 11.1.3.1 GbcVocBlkRsn (Global Carrier Voice Block Reason) ....................................................................................................................... 174 11.1.3.2 ClcVocBlkRsn (Cell Carrier Voice Block Reason).............................................................................................................................. 174 11.1.4 Calculation Method............................................................................................................................................................................................... 175 11.2 Block (SMS) ........................................................................................................................................................................................................................ 175 11.2.1 Function Description ............................................................................................................................................................................................ 175 11.2.2 Protocol Flow......................................................................................................................................................................................................... 176 11.2.3 Counter Table Detail............................................................................................................................................................................................. 176 11.2.3.1 GbcSmsBlkRsn (Global Carrier SMS Block Reason) ....................................................................................................................... 176 11.2.3.2 ClcSmsBlkRsn (Cell Carrier SMS Block Reason) ............................................................................................................................. 177
ZTE Confidential Proprietary Page 12
12
13
14
15
11.2.4 Calculation Method............................................................................................................................................................................................... 177 11.3 Block (Data Service) .......................................................................................................................................................................................................... 177 11.3.1 Function Description ............................................................................................................................................................................................ 177 11.3.2 Protocol Flow......................................................................................................................................................................................................... 178 11.3.3 Counter Table Detail............................................................................................................................................................................................. 178 11.3.3.1 GbcDatBlkRsn (Global Carrier Data Block Reason) ......................................................................................................................... 178 11.3.3.2 ClcDatBlkRsn (Cell Carrier Data Block Reason) ............................................................................................................................... 179 11.3.4 Calculation Method............................................................................................................................................................................................... 179 Power Overload ............................................................................................................................................................................................................................ 180 12.1 Function Description .......................................................................................................................................................................................................... 180 12.2 Protocol Flow ...................................................................................................................................................................................................................... 180 12.3 Counter Table Detail .......................................................................................................................................................................................................... 180 12.3.1 ClcPwOL(Cell Carrier Power Overload)............................................................................................................................................................ 180 12.4 Calculation Method ............................................................................................................................................................................................................ 181 CES Link Data .............................................................................................................................................................................................................................. 181 13.1 Function Description .......................................................................................................................................................................................................... 181 13.2 Protocol Flow ...................................................................................................................................................................................................................... 181 13.3 Counter Table Detail .......................................................................................................................................................................................................... 181 13.3.1 CesLnkDat (CES Link Data) ............................................................................................................................................................................... 181 13.4 Calculation Method ............................................................................................................................................................................................................ 182 RFS Data ....................................................................................................................................................................................................................................... 182 14.1 Function Description .......................................................................................................................................................................................................... 182 14.2 Protocol Flow ...................................................................................................................................................................................................................... 182 14.3 Counter Table Detail .......................................................................................................................................................................................................... 182 14.3.1 ClcRfsInfo(Cell Carrier Radio Frequency Information) ................................................................................................................................... 182 14.4 Calculation Method ............................................................................................................................................................................................................ 183 Failure Causes.............................................................................................................................................................................................................................. 183 15.1 Function Description .......................................................................................................................................................................................................... 183
Page 13
15.2 Protocol Flow ...................................................................................................................................................................................................................... 184 15.3 Table Detail.......................................................................................................................................................................................................................... 184 15.4 Calculation Method ............................................................................................................................................................................................................ 185 16 Adjacent Cells ............................................................................................................................................................................................................................... 185 16.1 Function Description .......................................................................................................................................................................................................... 185 16.2 Protocol Flow ...................................................................................................................................................................................................................... 185 16.3 Table Detail.......................................................................................................................................................................................................................... 186 16.4 Calculation Method ............................................................................................................................................................................................................ 187
1 Abbreviation
Abbreviation DT C/S LC Gbc(GBC) Clc(CLC) Voc(VOC) Dat(DAT) Con(CON) Full Item Data Type Cumulative/Straight Location Global Carrier Cell Carrier Voice service Data service Concurrent service Value FL: C: GC: Float(64 Bit) Cumulative Global Carrier IN: S: Int(32 Bit) Straight TI: SB: Subnet TinyInt(16 Bit)
CC: Cell Carrier
Page 14
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. The mobile 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.
Page 15
Page 16
2.3 Counter Table Detail

2.3.1 GbcReg (Global Carrier Registration)
Statistical item Description DT Trigger 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. Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time. Every time when BS (base station) receives a registration message from MS (mobile station), it will determine the type of registration is PowerDown and add 1 to the counter of that type of registration accordingly. Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time. Every time when BS (base station) receives a registration message from MS (mobile station), it will determine the type of registration is TimerBased and add 1 to the counter of that type of registration accordingly. Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time. C/ S LC Res
PowerUpReqNum
Power Up Request Num
FL
GC
PowerUpSuccNum
Power Up Success Num
FL
GC GC
PowerDownReqNum
Power Down Request Num
FL
PowerDownSuccNum
Power Down Success Num
FL
GC GC
TimerBasedReqNum
Timer Based Request Num
FL
TimerBasedSuccNum
Timer Based Success Num
FL
GC
Page 17
DistanceBasedReqNum
Distance Based 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 DistanceBased and add 1 to the counter of that type of registration accordingly. Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time. Every time when BS (base station) receives a registration message from MS (mobile station), it will determine the type of registration is ZoneBased and add 1 to the counter of that type of registration accordingly. Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time. Every time when BS (base station) receives a registration message from MS (mobile station), it will determine the type of registration is Parameter Change and add 1 to the counter of that type of registration accordingly. Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time. Every time when BS (base station) receives a registration message from MS (mobile station), it will determine the type of registration is Ordered by BS, and add 1 to the counter of that type of registration accordingly. Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time. Every time when BS (base station) receives a registration message from MS (mobile station), it will determine the type of registration is User Zone and add 1 to the counter of that type of registration accordingly.
GC C
DistanceBasedSuccNum
Distance Based Success Num
FL
GC GC
ZoneBasedReqNum
Zone Based Request Num
FL
ZoneBasedSuccNum
Zone Based Success Num
FL
GC GC
ParameterChangeReqNu m ParameterChangeSuccN um
Parameter Change Request Num Parameter Change Success Num
FL
FL
GC GC
OrderedReqNum
Ordered Request Num
FL
OrderedSuccNum
Ordered Success Num
FL
GC GC
UserZoneReqNum
User Zone Request Num
FL
Page 18
UserZoneSuccNum
User Zone Success Num
FL
Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time.
GC
2.3.2 ClcReg (Cell Carrier Registration)

Statistical item Description DT IN PowerUpReqNum Power Up Request Num Trigger 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. Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time. Every time when BS (base station) receives a registration message from MS (mobile station), it will determine the type of registration is PowerDown and add 1 to the counter of that type of registration accordingly. Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time. Every time when BS (base station) receives a registration message from MS (mobile station), it will determine the type of registration is TimerBased and add 1 to the counter of that type of registration accordingly. Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time. C/ S LC Res
CC
PowerUpSuccNum
Power Up Success Num
IN IN
CC
PowerDownReqNum
Power Down Request Num
CC
PowerDownSuccNum
Power Down Success Num
IN IN
CC
TimerBasedReqNum
Timer Based Request Num
CC
TimerBasedSuccNum
Timer Based Success Num
IN
CC
Page 19
IN DistanceBasedReqNum Distance Based Request Num
Every time when BS (base station) receives a registration message from MS (mobile station), it will determine the type of registration is DistanceBased and add 1 to the counter of that type of registration accordingly. Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time. Every time when BS (base station) receives a registration message from MS (mobile station), it will determine the type of registration is ZoneBased and add 1 to the counter of that type of registration accordingly. Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time. Every time when BS (base station) receives a registration message from MS (mobile station), it will determine the type of registration is Parameter Change and add 1 to the counter of that type of registration accordingly. Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time. Every time when BS (base station) receives a registration message from MS (mobile station), it will determine the type of registration is Ordered by BS, and add 1 to the counter of that type of registration accordingly. Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time. Every time when BS (base station) receives a registration message from MS (mobile station), it will determine the type of registration is User Zone and add 1 to the counter of that type of registration accordingly.
CC
DistanceBasedSuccNum
Distance Based Success Num
IN IN
CC
ZoneBasedReqNum
Zone Based Request Num
CC
ZoneBasedSuccNum
Zone Based Success Num
IN IN
CC
ParameterChangeReqNu m ParameterChangeSuccN um
Parameter Change Request Num Parameter Change Success Num IN IN
CC
CC
OrderedReqNum
Ordered Request Num
CC
OrderedSuccNum
Ordered Success Num
IN IN
CC
UserZoneReqNum
User Zone Request Num
CC
Page 20
UserZoneSuccNum
User Zone Success Num
IN
Add 1 to the counter every time when MSC returns a Registration Accepted Order within specified time.
CC
2.4 Calculation Method

Type
SuccessNum
Overall Registration Success Rate =
Type
RequestNum
100%
SuccessNum
Registration Success Rate of each type =
RequestNum
100%
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.
Page 21
3.1.1.2 Protocol Flow

For details, please refer to 3GPP2 A.S0001-A version 2.0 2.2.2.1.
Page 22
3.1.1.3 Counter Table Detail

3.1.1.3.1 GbcVocOrigCall (Global Carrier Voice Originating Call) Statistical item Description DT Trigger Add 1 to the counter every time when BS receives an origination message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of call setup. Add 1 to the counter every time when the call origination fails for reasons other than the above. C/ S C C LC Res
MSOriginateNum CallSuccessNum
MS Originating Num Voice Num Originating Request
FL FL
GC GC GC
ExtInterruptNum
Outer Interrupt Num
FL
C GC GC
BlockFailureNum OtherFailureNum
Block Success Num Other Reason Success Num
FL FL
C C
3.1.1.3.2 ClcVocOrgCall (Cell Carrier Voice Originating Call) Statistical item Description DT Trigger Add 1 to the counter every time when BS receives an origination message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. C/ S C C LC Res
IN IN
CC CC
Page 23
IN ExtInterruptNum Outer Interrupt Num IN IN
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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of call setup. Add 1 to the counter every time when the call origination fails for reasons other than the above.
CC
C C
CC CC
3.1.1.4 Calculation Method
SuccessNum
Call Origination Success Rate =
OriginateNum
100%
BlockNum
Call Origination Block Rate =
OriginateNum
100%
ExternalInterrruptNum
Call Origination External Interrupt Rate =
OriginateNum
100%
Note: The user may decide whether the external interrupt number is added to the success number.
Page 24
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.

Page 25
Page 26

3.1.2.3.1 GbcVocPagCall (Global Carrier Voice Paging Call) Statistical item Description DT Trigger Add 1 to the counter every time when BS receives a paging request from MSC. Add 1 to the counter every time when BS receives a page response message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of call setup. Add 1 to the counter every time when the paging fails for reasons other than the above. C/ S C C C LC GC GC GC GC C GC GC Res
PagingMsNum PageResponceNum CallSuccessNum
MS Paging Num MS Paging Response Num Voice Paging Request Num
FL FL FL
ExtInterruptNum
Outer Interrupt Num
FL
FL FL
C C
3.1.2.3.2 ClcVocPagCall (Cell Carrier Voice Paging Call) Statistical item Description DT IN Trigger Add 1 to the counter every time when BS receives a paging request from MSC. C/ S C LC Res
PagingMsNum
MS Paging Num
CC
Page 27
PageResponceNum CallSuccessNum
MS Paging Response Num Voice Paging Request Num
IN IN IN
Add 1 to the counter every time when BS receives a page response message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of call setup. Add 1 to the counter every time when the paging fails for reasons other than the above.
C C
CC CC
ExtInterruptNum
Outer Interrupt Num IN IN
CC
C C
CC CC
PagingResponseNum
Paging Response Rate=
PagingNum SuccessNum PagingResponseNum BlockNum
100%
Paging Success Rate =
100%
Paging Block Rate =
PagingResponseNum
100%
Page 28
Paging External Interrupt Rate =
PagingResponseNum
100%
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) =
SuccessNum + SuccessNum 100% OriginateNum + PagingResponseNum

MO MT MO MT MO MT
BlockNum + BlocksNum 100% Call Block Rate (Voice) = OriginateNum + PagingResponseNum

MO MT
Call External Interrupt Rate (Voice)
ExternalInterruptNum + ExternalInterruptNum 100% = OriginateNum + PagingResponseNum

MO MT MO MT
Page 29
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.
Page 30
Page 31

3.2.1.3.1 GbcVocHoSrcBss (Global Carrier Voice Handoff as Source BSS) Statistical item Description DT Trigger Every time when BS receives a handoff request from MS, it will determine the type of handoff is Soft and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is Softer and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is change Frequency and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is change Frame Offset and add 1 to the counter of that type accordingly. C/ S C GC C GC C GC C GC C GC C GC C LC GC Res
SrcBscSoftAdd_HoRNum
Soft Handoff Add Request Num as Source BSC Soft Handoff Add Success Num as Source BSC Softer Handoff Add Request Num as Source BSC Softer Handoff Add Success Num as Source BSC Inter-Frequency Semi handoff Add Request Num as Source BSC Inter-Frequency Semi handoff Add Success Num as Source BSC Inter-Frame Semi handoff Add Request Num as Source BSC
FL
SrcBscSoftAdd_HoSNum
FL
SrcBscSofterAdd_HoRNu m SrcBscSofterAdd_HoSNu m
FL
FL
SrcBscFREQ_HoRNum
FL
SrcBscFREQ_HoSNum
FL
SrcBscFO_HoRNum
FL
Page 32
SrcBscFO_HoSNum
Inter-Frame Semi handoff Add Success Num as Source BSC
FL
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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is change Radio Configuration and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is out to other BS and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is not recognized and add 1 to the counter of that type accordingly. 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.
GC C GC C
SrcBscRC_HoRNum
Inter-RC Semi handoff Add Request Num as Source BSC
FL
SrcBscRC_HoSNum
Inter-RC Semi handoff Add Success Num as Source BSC Handoff-Out Handoff Request Num Between BSC as Source BSC Handoff-Out Handoff Success Num Between BSC as Source BSC Other Handoff Request Num Between BSC as Source BSC Other Handoff Success Num Between BSC as Source BSC
GC C GC C GC C GC C GC C
FL
InterBscHo_HoRNum
FL
InterBscHo_HoSNum
FL
SrcBscOther_HoRNum
FL
SrcBscOther_HoSNum
FL
3.2.1.3.2 ClcVocHoSrcBss (Cell Carrier Voice Handoff as Source BSS) Statistical item Description DT Trigger C/ S LC Res
Page 33
Soft Handoff Add Request Num as Source BSC Soft Handoff Add Success Num as Source BSC Softer Handoff Add Request Num as Source BSC Softer Handoff Add Success Num as Source BSC Inter-Frequency Semi handoff Add Request Num as Source BSC Inter-Frequency Semi handoff Add Success Num as Source BSC Inter-Frame Semi handoff Add Request Num as Source BSC Inter-Frame Semi handoff Add Success 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 counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is Softer and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is change Frequency and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is change Frame Offset and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is change Radio Configuration and add 1 to the counter of that type accordingly.
CC
IN
CC
IN
CC
IN
CC
IN
SrcBscFREQ_HoRNum
CC
IN
SrcBscFREQ_HoSNum
CC
IN
SrcBscFO_HoRNum
CC
IN
SrcBscFO_HoSNum
CC
IN SrcBscRC_HoRNum Inter-RC Semi handoff Add Request Num as Source BSC
CC
Page 34
SrcBscRC_HoSNum
IN
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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is out to other BS and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is not recognized and add 1 to the counter of that type accordingly. 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.
CC
IN
InterBscHo_HoRNum
CC
IN
InterBscHo_HoSNum
CC
IN
SrcBscOther_HoRNum
CC
IN
SrcBscOther_HoSNum
CC
Overall Handoff Success Rate =
Type
SuccessNum
Type
RequestNum
100%
SuccessNum
Handoff Success Rate of each type =
RequestNum
100%
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.
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. 3.2.2.2 Protocol Flow For details, please refer to 3GPP2 A.S0001-A version 2.0 3.5.2.3.1.
Page 36
Page 37

3.2.2.3.1 GbcVocHoTgtBss (Global Carrier Voice Handoff as Target BSS) Statistical item Description DT Trigger Every time when BS receives a handoff request from MS, it will determine the type of handoff is Soft and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is Softer and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is change Frequency and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is change Frame Offset and add 1 to the counter of that type accordingly. C/ S C GC C GC C GC C GC C GC C GC C LC GC Res
TgtBscSoftAdd_HoRNum
Soft Handoff Add Request Num as Target BSC Soft Handoff Add Success Num as Target BSC Softer Handoff Add Request Num as Target BSC Softer Handoff Add Success Num as Target BSC Inter-Frequency Semi handoff Add Request Num as Target BSC Inter-Frequency Semi handoff Add Success Num as Target BSC Inter-Frame Semi handoff Add Request Num as Target BSC
FL
TgtBscSoftAdd_HoSNum
FL
TgtBscSofterAdd_HoRNu m TgtBscSofterAdd_HoSNu m
FL
FL
TgtBscFREQ_HoRNum
FL
TgtBscFREQ_HoSNum
FL
TgtBscFO_HoRNum
FL
Page 38
TgtBscFO_HoSNum
Inter-Frame Semi handoff Add Success Num as Target BSC
FL
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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is change Radio Configuration and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is handoff into self and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is not recognized and add 1 to the counter of that type accordingly. 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.
GC C GC C
TgtBscRC_HoRNum
Inter-RC Semi handoff Add Request Num as Target BSC
FL
TgtBscRC_HoSNum
Inter-RC Semi handoff Add Success Num as Target BSC Handoff-Out Handoff Request Num Between BSC as Target BSC Handoff-Out Handoff Success Num Between BSC as Target BSC Other Handoff Request Num Between BSC as Target BSC Other Handoff Success Num Between BSC as Target BSC
FL
InterBscHo_HoRNum
FL
InterBscHo_HoSNum
FL
TgtBscOther_HoRNum
FL
TgtBscOther_HoSNum
FL
3.2.2.3.2 ClcVocHoTgtBss (Cell Carrier Voice Handoff as Target BSS) Statistical item Description DT Trigger C/ S LC Res
Page 39
Soft Handoff Add Request Num as Target BSC Soft Handoff Add Success Num as Target BSC Softer Handoff Add Request Num as Target BSC Softer Handoff Add Success Num as Target BSC Inter-Frequency Semi handoff Add Request Num as Target BSC Inter-Frequency Semi handoff Add Success Num as Target BSC Inter-Frame Semi handoff Add Request Num as Target BSC Inter-Frame Semi handoff Add Success Num as Target BSC
IN
CC
IN
CC
IN
CC
IN
CC
IN
TgtBscFREQ_HoRNum
CC
IN
TgtBscFREQ_HoSNum
CC
IN
TgtBscFO_HoRNum
CC
IN
TgtBscFO_HoSNum
CC
IN TgtBscRC_HoRNum Inter-RC Semi handoff Add Request Num as Target BSC
CC
Page 40
TgtBscRC_HoSNum
IN
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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is handoff into self and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is not recognized and add 1 to the counter of that type accordingly. 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.
CC
IN
InterBscHo_HoRNum
CC
IN
InterBscHo_HoSNum
CC
IN
TgtBscOther_HoRNum
CC
IN
TgtBscOther_HoSNum
CC
Type
SuccessNum
Type
RequestNum
100%
SuccessNum
RequestNum
100%
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
Page 42
Page 43
3.3.3 Counter Table Detail

3.3.3.1 GbcVocRls (Global Carrier Voice Release)
Statistical item Description DT Trigger Add 1 to the counter every time when BS receives a normal release message from MS or MSC. Add 1 to the counter every time when a call exception message from BS or MSC is received. Add 1 to the counter every time when a call exception radio message from BS or MSC is received. C/ S C C C LC GC GC GC Res
CM_NorRlsSNum CM_SysDorpNum CM_RadioDropNum
Normal Release Num System Drop Num Radio Drop Num
FL FL FL
3.3.3.2 ClcVocRls (Cell Carrier Voice Release)

Statistical item Description DT IN IN IN Trigger Add 1 to the counter every time when BS receives a normal release message from MS or MSC. Add 1 to the counter every time when a call exception message from BS or MSC is received. Add 1 to the counter every time when a call exception radio message from BS or MSC is received. C/ S C C C LC Res
CC CC CC
Page 44
3.3.4 Calculation Method
DropNum
Call Drop Rate =
NormalReleaseNum + DropNum
100%
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 MSC T2: 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.
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. TCH at Air Interface CE1BTS1 TCH1 TCH2 TCH3 TCH4 CE3BTS3 Apportionment of Traffic: CE T/3 T/3 T/3 Call TCH T/3/2 T/3/2 T/3 T/3 CE T-T/3 T-T/3 T-T/3 Soft Handoff TCH T-T/3/2 T-T/3/2 T-T/3 T-T/3 CE Softer Handoff TCH T-T/3/2-T-T/3/2 T-T/3/2-T-T/3/2 Page 46
CE2BTS2
B S C
Page 47
Page 48

3.4.1.3.1 GbcVocErl (Global Carrier Voice Erlang as Source BSS) Statistical item Description DT Trigger Duration from the time when BS receives an origination message from MS to the time when BS receives an assignment request from MSC Duration from the time when BS receives the assignment request from MSC to the time when BS sends channel assignment message to MS Duration from the time when BS sends channel assignment message to MS to the time when BS sends an assignment complete message to MSC 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) Duration from the time when BS sends to MSC a clear request to the time of Clear Complete C/ S C GC C GC C GC C LC GC Res
UmaOrg_A1fAssReq_Du ration AvfAssReq_AvfSvcAss_ Duration AvfSvcAss_AvfAssCmp_ Dur
Request Call Duration From Originating To Assign(Second) Call Duration From Assign Requesting To Traffic Assign(Second) Call Duration From Originating To Assign(Second) Call Duration From Finishing Assign To Requesting Release(Second) Call Duration From Requesting Release To resource release(Second)
FL
FL
FL
AvrAssCmp_AvfRlsReq_ Dur
FL
GC C
AvfRlsReq_EndPrc_Dur
FL
Page 49
3.4.1.3.2 ClcVocErl (Cell Carrier Voice Erlang as Source BSS) Statistical item Description DT Trigger Duration from the time when BS receives an origination message from MS to the time when BS receives an assignment request from MSC Duration from the time when BS receives the assignment request from MSC to the time when BS sends channel assignment message to MS 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 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 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 Call Duration from the time when BS sends the assignment complete message to MSC to the time when BS sends to MSC a clear request 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 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/ S C LC Res
UmaOrg_A1fAssReq_Du ration AvfAssReq_AvfSvcAss_ Duration AvfSvcAss_AvfAssCmp_ CallDur AvfSvcAss_AvfAssCmp_ SHoDur AvfSvcAss_AvfAssCmp_ SSHoDur AvrAssCmp_AvfRlsReq_ CallDur AvrAssCmp_AvfRlsReq_ ShoDur AvrAssCmp_AvfRlsReq_ SSHoDur
Request Call Duration From Originating To Assign(Second) Call Duration From Assign Requesting To Traffic Assign(Second) Call Duration From Traffic Assign To Assign Finished(Second) Soft Handoff Duration From Traffic Assign To Assign Finished(Second) Softer Handoff Duration From Traffic Assign To Assign Finished(Second) Call Duration From Assign Finished To Requesting Release(Second) Soft Handoff Duration From Assign Finished To Requesting Release(Second) Softer Handoff Duration From Assign Finished To Requesting Release(Second)
FL
CC
FL
CC
FL
CC
FL
CC
FL
CC
FL
CC
FL
CC
FL
CC
Page 50
AvfRlsReq_EndPrc_Call Dur AvfRlsReq_EndPrc_Sho Dur AvfRlsReq_EndPrc_SSH oDur
Call Duration From Requesting Release To resource release(Second) Soft Handoff Duration From Requesting Release To resource release(Second) Softer Handoff Duration From Requesting Release To resource release(Second)
FL
Call Duration from the time when BS sends to MSC a clear request to the time of Clear Complete Soft Handoff Duration from the time when BS sends to MSC a clear request to the time of Clear Complete Softer Handoff Duration from the time when BS sends to MSC a clear request to the time of Clear Complete
CC
FL
CC
FL
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)
CallDur
Traffic (Erl) in unit time
T
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 soft handoff and/or softer handoff. From the above description and analysis, we can calculate the following: Call Duration: CallDur = AvfSvcAss_AvfAssCmp_CallDur + AvrAssCmp_AvfRlsReq_CallDur
+ 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:
CallDur
Traffic of call:
T
SHODur
Traffic of soft handoff:
T
SSHODur
Traffic of softer handoff:
T
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.
Page 52
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) Statistical item Description Voice Handoff Duration(Second) TCH DT Trigger C/ S C LC Res
HODuration
FL
The traffic of handoff in the time period T4
GC
3.4.2.2.2 ClcVocErlTgtBss (Cell Carrier Voice Erlang as Target BSS) Statistical item Description Soft Handoff Duration(Second) Softer Handoff Duration(Second) TCH TCH DT Trigger C/ S C C LC Res
SHoDuration SSHoDuration
FL FL
The traffic of soft handoff in the time period T4 The traffic of softer handoff in the time period T4
CC CC
Page 53

The duration and traffic of inter-BSS handoff are calculated as follows: Soft Handoff Duration: SHODur = SHoDuration Softer Handoff Duration: SSHODur = SSHoDuration
SHODur
Traffic of Soft Handoff:
T
SSHODur
Traffic of Softer Handoff:
T
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
Page 54
SMS terminated by MSC
Page 55

4.1.3.1 GbcSmsCallCch (Global Carrier SMS Call on Control Channel)
Statistical item Description CCH Originating SM Total Num CCH Originating SM Request Num CCH Paging SM Total Num CCH Num Paging SM Request DT Trigger In the SMS originated by MS, add 1 to the counter every time when BS receives a SMS Delivery message from MS. In the SMS originated by MS, add 1 to the counter every time when BS sends a ADDS Deliver Ack message to MSC. In the SMS terminated by MSC, add 1 to the counter every time when BS receives a ADDS Deliver message from MSC. In the SMS terminated by MSC, add 1 to the counter every time when BS sends a ADDS Deliver Ack message to MSC. C/ S C C C C LC GC GC GC GC Res
CCHOriginTotalNum CCHOriginReqNum CCHPagingTotalNum CCHPagingReqNum
FL FL FL FL
OriginateSuccessNum
Call Origination Success Rate of SMS on control channel =
OriginateRequestNum
100%
100%
PagingSuccessNum
Paging Success Rate of SMS on control channel =
PagingRequestNum
Overall Success Rate of SMS on control channel
Page 56
OriginateSuccessNum + PagingSuccessNum
=
OriginateRequestNum + PagingRequestNum
100%
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.

Page 57

4.2.1.3.1 GbcSmsOrgCall (Global Carrier SMS Originating Call) Statistical item Description DT Trigger C/ S LC Res
Page 58
FL FL
Add 1 to the counter every time when BS receives an origination message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of call setup. Add 1 to the counter every time when the call origination fails for reasons other than the above.
C C
GC GC GC
ExtInterruptNum
Outer Interrupt Num
FL
C GC GC
FL FL
C C
4.2.1.3.2 ClcSmsOrgCall (Cell Carrier SMS Originating Call) Statistical item Description DT IN Request IN IN ExtInterruptNum Outer Interrupt Num IN IN Trigger Add 1 to the counter every time when BS receives an origination message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of call setup. Add 1 to the counter every time when the call origination fails for reasons other than the above. C/ S C C LC Res
MS Originating Num Voice Num Originating
CC CC
CC
C C
CC CC
Page 59
SuccessNum
OriginateNum
100%
BlockNum
OriginateNum
100%
OriginateNum
100%
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 go on the paging flow for SMS services and collect related data accordingly.

Page 60
Page 61

4.2.2.3.1 GbcSmsPagCall (Global Carrier SMS Paging Call) Statistical item Description DT Trigger Add 1 to the counter every time when BS receives a paging request from MSC. Add 1 to the counter every time when BS receives a page response message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of call setup. Add 1 to the counter every time when the paging fails for reasons other than the above. C/ S C C C LC GC GC GC GC C GC GC Res
FL FL FL
ExtInterruptNum
Outer Interrupt Num
FL
FL FL
C C
4.2.2.3.2 ClcSmsPagCall (Cell Carrier SMS Paging Call) Statistical item Description DT IN Trigger Add 1 to the counter every time when BS receives a paging request from MSC. C/ S C LC Res
PagingMsNum
MS Paging Num
CC
Page 62
IN IN IN
C C
CC CC
ExtInterruptNum
CC
C C
CC CC
PagingResponseNum
100%
100%
Paging Block Rate =
PagingResponseNum
100%
Page 63
PagingResponseNum
100%
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) =

MO MT MO MT MO MT
BlockNum + BlocksNum 100% Call Block Rate (SMS) = OriginateNum + PagingResponseNum

MO MT
Call External Interrupt Rate (SMS)

MO MT MO MT
Page 64
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.
Page 65
Page 66

4.2.5.3.1 GbcSmsRls (Global Carrier SMS Release) Statistical item Description DT Trigger Add 1 to the counter every time when BS receives a normal release message from MS or MSC. Add 1 to the counter every time when a call exception message from BS or MSC is received. Add 1 to the counter every time when a call exception radio message from BS or MSC is received. C/ S C C C LC GC GC GC Res
FL FL FL
4.2.5.3.2 ClcVocRls (Cell Carrier Voice Release) Statistical item Description DT IN IN IN Trigger Add 1 to the counter every time when BS receives a normal release message from MS or MSC. Add 1 to the counter every time when a call exception message from BS or MSC is received. Add 1 to the counter every time when a call exception radio message from BS or MSC is received. C/ S C C C LC Res
CC CC CC
Page 67
DropNum
Call Drop Rate =
100%
4.2.6 SMS Traffic

4.2.6.1 Function Description 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) Statistical item Description DT Trigger Duration from the time when BS receives an origination message from MS to the time when BS receives an assignment request from MSC Duration from the time when BS receives the assignment request from MSC to the time when BS sends channel assignment message to MS C/ S C GC C LC GC Res
UmaOrg_A1fAssReq_Du ration AvfAssReq_AvfSvcAss_ Duration
Request Call Duration From Originating To Assign(Second) Call Duration From Assign Requesting To Traffic Assign(Second)
FL
FL
Page 68
AvfSvcAss_AvfAssCmp_ Dur
Call Duration From Originating To Assign(Second) Call Duration From Finishing Assign To Requesting Release(Second) Call Duration From Requesting Release To resource release(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 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) Duration from the time when BS sends to MSC a clear request to the time of Clear Complete
GC C GC C
FL
GC C
FL
4.2.6.3.2 ClcSmsErl (Cell Carrier SMS Erlang as Source BSS) Statistical item Description DT Trigger Duration from the time when BS receives an origination message from MS to the time when BS receives an assignment request from MSC Duration from the time when BS receives the assignment request from MSC to the time when BS sends channel assignment message to MS 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/ S C LC Res
UmaOrg_A1fAssReq_Du ration AvfAssReq_AvfSvcAss_ Duration AvfSvcAss_AvfAssCmp_ CallDur
Request Call Duration From Originating To Assign(Second) Call Duration From Assign Requesting To Traffic Assign(Second) Call Duration From Traffic Assign To Assign Finished(Second)
FL
CC
FL
CC
FL
CC
Page 69
AvrAssCmp_AvfRlsReq_ CallDur
Call Duration From Assign Finished To Requesting Release(Second) Call Duration From Requesting Release To resource 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) Duration from the time when BS sends to MSC a clear request to the time of Clear Complete
CC
AvfRlsReq_EndPrc_Call Dur
FL
CC

CallDur
T
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.
5.1.2 Protocol Flow
Page 71
Page 72
Page 73

5.1.3.1 GlbDatBrstGlobal Data Burst
Statistical item Description TCH Originating Num SM Total DT Trigger Request number of data bursts originated by MS on the traffic channel Success number of data bursts originated by MS on the traffic channel Request number of data bursts originated by PDSN on the traffic channel Success number of data bursts originated by PDSN on the traffic channel Request number of data bursts originated by MS on the control channel Success number of data bursts originated by MS on the control channel Request number of data bursts originated by PDSN on the control channel Success number of data bursts originated by PDSN on the control channel C/ S C C C C C C C C LC GC GC GC GC GC GC GC GC Res
TCHOriginTotalNum TCHOriginReqNum TCHPagingTotalNum TCHPagingReqNum CCHOriginTotalNum CCHOriginReqNum CCHPagingTotalNum CCHPagingReqNum
FL FL FL FL FL FL FL FL
TCH Originating SM Request Num TCH Paging SM Total Num TCH Paging SM Request Num CCH Originating SM Total Num CCH Originating SM Request Num CCH Paging SM Total Num CCH Num Paging SM Request
Page 74
Call Origination Success Rate of Data Burst on traffic channel =
TCH
OriginSuccNum 100% OriginTotalNum

TCH
Paging Success Rate of Data Burst on traffic channel =
TCH
PagingSuccNum 100% PagingTotalNum

TCH
Call Origination Success Rate of Data Burst on control channel =
CCH
OriginSuccNum 100% OriginTotalNum

CCH
Paging Success Rate of Data Burst on control channel =
CCH
PagingSuccNum 100% PagingTotalNum

CCH
OriginSuccNum + PagingSuccNum
Overall Success Rate of Data Burst =
OriginTotalNum + PagingTotalNum
100%
5.2 RLP Data Flow

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

None

5.2.3.1 GlbRLPFluxGlobal Radio Link Protocol Flux
Statistical item Description DT Trigger Record the size of the forward data packet every time when it is transmitted. Record the size of the forward data packet every time when it is retransmitted. Record the size of the reverse data packet every time when it is transmitted. Record the size of the reverse data packet every time when it is retransmitted. C/ S C C C C LC GC GC GC GC Res
TxTotalFrame TxRexmitFrame RxTotalFrame RxRexmitFrame
Forward Transmit Total Frame Forward Frame Resending Total
FL FL FL FL
Reverse Transmit Total Frame Reverse Frame Resending Total

Forward Flow Rate =
TxTotalFrame ( BYTE / s)
T
Forward Retransmission Rate =
TxRexmitFrame ( BYTE / s)
T
Page 76
Reverse Flow Rate =
RxTotalFrame ( BYTE / s)
T
Reverse Retransmission Rate =
RxRexmitFrame ( BYTE / s)
T
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.

Page 77
Page 78

5.3.1.3.1 GbcDatOrigCall (Global Carrier Data Originating Call) Statistical item Description DT Trigger Add 1 to the counter every time when BS receives an origination message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of call setup. Add 1 to the counter every time when the call origination fails for reasons other than the above. C/ S C C LC Res
FL FL
GC GC GC
ExtInterruptNum
Outer Interrupt Num
FL
C GC GC
FL FL
C C
5.3.1.3.2 ClcDatOrgCall (Cell Carrier Data Originating Call) Statistical item Description DT IN Request IN Trigger Add 1 to the counter every time when BS receives an origination message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. C/ S C C LC Res
MS Originating Num Voice Num Originating
CC CC
Page 79
CC
C C
CC CC
SuccessNum
OriginateNum
100%
BlockNum
OriginateNum
100%
OriginateNum
100%
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
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.

Page 81
Page 82

5.3.2.3.1 GbcDatPagCall (Global Carrier Data Paging Call) Statistical item Description DT Trigger Add 1 to the counter every time when BS receives a paging request from MSC. Add 1 to the counter every time when BS receives a page response message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of call setup. Add 1 to the counter every time when the paging fails for reasons other than the above. C/ S C C C LC GC GC GC GC C GC GC Res
FL FL FL
ExtInterruptNum
Outer Interrupt Num
FL
FL FL
C C
5.3.2.3.2 ClcDatOrgCall (Cell Carrier Data Paging Call) Statistical item Description DT IN Trigger Add 1 to the counter every time when BS receives a paging request from MSC. C/ S C LC Res
PagingMsNum
MS Paging Num
CC
Page 83
IN IN IN
C C
CC CC
ExtInterruptNum
CC
C C
CC CC
PagingResponseNum
100%
100%
Paging Block Rate =
PagingResponseNum
100%
Page 84
PagingResponseNum
100%
5.3.3 Call Service (Data)

As the call process of data services includes call origination (data) and paging (data), its data comes from the data of the two.
Call Success Rate (Data) =

MO MT MO MT MO MT
BlockNum + BlocksNum 100% Call Block Rate (Data) = OriginateNum + PagingResponseNum

MO MT
Call External Interrupt Rate (Data)

MO MT MO MT
Page 85
5.4 Handoff (Data Services)

5.4.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.
Page 86
Page 87

5.4.1.3.1 GbcDatHoSrcBss (Global Carrier Data Handoff as Source BSS) Statistical item Description DT Trigger Every time when BS receives a handoff request from MS, it will determine the type of handoff is Soft and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is Softer and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is change Frequency and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is change Frame Offset and add 1 to the counter of that type accordingly. C/ S C GC C GC C GC C GC C GC C GC C LC GC Res
Soft Handoff Add Request Num as Source BSC Soft Handoff Add Success Num as Source BSC Softer Handoff Add Request Num as Source BSC Softer Handoff Add Success Num as Source BSC Inter-Frequency Semi handoff Add Request Num as Source BSC Inter-Frequency Semi handoff Add Success Num as Source BSC Inter-Frame Semi handoff Add Request Num as Source BSC
FL
FL
FL
FL
SrcBscFREQ_HoRNum
FL
SrcBscFREQ_HoSNum
FL
SrcBscFO_HoRNum
FL
Page 88
SrcBscFO_HoSNum
Inter-Frame Semi handoff Add Success Num as Source BSC
FL
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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is change Radio Configuration and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is out to other BS and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is not recognized and add 1 to the counter of that type accordingly. 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.
GC C GC C
SrcBscRC_HoRNum
Inter-RC Semi handoff Add Request Num as Source BSC
FL
SrcBscRC_HoSNum
FL
InterBscHo_HoRNum
FL
InterBscHo_HoSNum
FL
SrcBscOther_HoRNum
FL
SrcBscOther_HoSNum
FL
5.4.1.3.2 ClcDatHoSrcBss (Cell Carrier Data Handoff as Source BSS) Statistical item Description DT Trigger C/ S LC Res
Page 89
Soft Handoff Add Request Num as Source BSC Soft Handoff Add Success Num as Source BSC Softer Handoff Add Request Num as Source BSC Softer Handoff Add Success Num as Source BSC Inter-Frequency Semi handoff Add Request Num as Source BSC Inter-Frequency Semi handoff Add Success Num as Source BSC Inter-Frame Semi handoff Add Request Num as Source BSC Inter-Frame Semi handoff Add Success Num as Source BSC
IN
CC
IN
CC
IN
CC
IN
CC
IN
SrcBscFREQ_HoRNum
CC
IN
SrcBscFREQ_HoSNum
CC
IN
SrcBscFO_HoRNum
CC
IN
SrcBscFO_HoSNum
CC
IN SrcBscRC_HoRNum Inter-RC Semi handoff Add Request Num as Source BSC
CC
Page 90
SrcBscRC_HoSNum
IN
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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is out to other BS and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is not recognized and add 1 to the counter of that type accordingly. 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.
CC
IN
InterBscHo_HoRNum
CC
IN
InterBscHo_HoSNum
CC
IN
SrcBscOther_HoRNum
CC
IN
SrcBscOther_HoSNum
CC
Type
SuccessNum
Type
RequestNum
100%
SuccessNum
RequestNum
100%
5.4.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.
Page 92
Page 93

5.4.2.3.1 GbcDatHoTgtBss (Global Carrier Data Handoff as Target BSS) Statistical item Description DT Trigger Every time when BS receives a handoff request from MS, it will determine the type of handoff is Soft and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is Softer and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is change Frequency and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is change Frame Offset and add 1 to the counter of that type accordingly. C/ S C GC C GC C GC C GC C GC C GC C LC GC Res
Soft Handoff Add Request Num as Target BSC Soft Handoff Add Success Num as Target BSC Softer Handoff Add Request Num as Target BSC Softer Handoff Add Success Num as Target BSC Inter-Frequency Semi handoff Add Request Num as Target BSC Inter-Frequency Semi handoff Add Success Num as Target BSC Inter-Frame Semi handoff Add Request Num as Target BSC
FL
FL
FL
FL
TgtBscFREQ_HoRNum
FL
TgtBscFREQ_HoSNum
FL
TgtBscFO_HoRNum
FL
Page 94
TgtBscFO_HoSNum
Inter-Frame Semi handoff Add Success Num as Target BSC
FL
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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is change Radio Configuration and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is handoff into self and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is not recognized and add 1 to the counter of that type accordingly. 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.
GC C GC C
TgtBscRC_HoRNum
Inter-RC Semi handoff Add Request Num as Target BSC
FL
TgtBscRC_HoSNum
FL
InterBscHo_HoRNum
FL
InterBscHo_HoSNum
FL
TgtBscOther_HoRNum
FL
TgtBscOther_HoSNum
FL
5.4.2.3.2 ClcDatHoTgtBss (Cell Carrier Data Handoff as Target BSS) Statistical item Description DT Trigger C/ S LC Res
Page 95
Soft Handoff Add Request Num as Target BSC Soft Handoff Add Success Num as Target BSC Softer Handoff Add Request Num as Target BSC Softer Handoff Add Success Num as Target BSC Inter-Frequency Semi handoff Add Request Num as Target BSC Inter-Frequency Semi handoff Add Success Num as Target BSC Inter-Frame Semi handoff Add Request Num as Target BSC Inter-Frame Semi handoff Add Success Num as Target BSC
IN
CC
IN
CC
IN
CC
IN
CC
IN
TgtBscFREQ_HoRNum
CC
IN
TgtBscFREQ_HoSNum
CC
IN
TgtBscFO_HoRNum
CC
IN
TgtBscFO_HoSNum
CC
IN TgtBscRC_HoRNum Inter-RC Semi handoff Add Request Num as Target BSC
CC
Page 96
TgtBscRC_HoSNum
IN
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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is handoff into self and add 1 to the counter of that type accordingly. 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. Every time when BS receives a handoff request from MS, it will determine the type of handoff is not recognized and add 1 to the counter of that type accordingly. 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.
CC
IN
InterBscHo_HoRNum
CC
IN
InterBscHo_HoSNum
CC
IN
TgtBscOther_HoRNum
CC
IN
TgtBscOther_HoSNum
CC
Type
SuccessNum
Type
RequestNum
100%
SuccessNum
RequestNum
100%
5.5 Release (Data Service)

The releases in data 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.
5.5.2 Protocol Flow

For details, please refer to 3GPP2 A.S0001-A version 2.0 2.14.7.2 and 2.14.7.3.
Page 98
Page 99
Page 100
Page 101
Page 102
Page 103

5.5.3.1 GbcDatRls (Global Carrier Data Release)
Statistical item Description DT Trigger Add 1 to the counter every time when BS receives a normal release message from MS or MSC. Add 1 to the counter every time when a call exception message from BS or MSC is received. Add 1 to the counter every time when a call exception radio message from BS or MSC is received. C/ S C C C LC GC GC GC Res
FL FL FL
5.5.3.2 ClcDatRls (Cell Carrier Data Release)

Statistical item Description DT IN IN IN Trigger Add 1 to the counter every time when BS receives a normal release message from MS or MSC. Add 1 to the counter every time when a call exception message from BS or MSC is received. Add 1 to the counter every time when a call exception radio message from BS or MSC is received. C/ S C C C LC Res
CC CC CC
Page 104
DropNum
Call Drop Rate =
100%
5.6 Traffic (Data Services)

5.6.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 MSC T2: 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.
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. TCH at Air Interface CE1BTS1 TCH1 TCH2 TCH3 TCH4 CE3BTS3 Apportionment of Traffic: CE T/3 T/3 T/3 Call TCH T/3/2 T/3/2 T/3 T/3 CE T-T/3 T-T/3 T-T/3 Soft Handoff TCH T-T/3/2 T-T/3/2 T-T/3 T-T/3 CE Softer Handoff TCH T-T/3/2-T-T/3/2 T-T/3/2-T-T/3/2 Page 106
CE2BTS2
B S C
Page 107
Page 108

5.6.1.3.1 GbcDatErl (Global Carrier Data Erlang as Source BSS) Statistical item Description DT Trigger Duration from the time when BS receives an origination message from MS to the time when BS receives an assignment request from MSC Duration from the time when BS receives the assignment request from MSC to the time when BS sends channel assignment message to MS Duration from the time when BS sends channel assignment message to MS to the time when BS sends an assignment complete message to MSC 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) Duration from the time when BS sends to MSC a clear request to the time of Clear Complete C/ S C GC C GC C GC C LC GC Res
UmaOrg_A1fAssReq_Du ration AvfAssReq_AvfSvcAss_ Duration AvfSvcAss_AvfAssCmp_ Dur
Request Call Duration From Originating To Assign(Second) Call Duration From Assign Requesting To Traffic Assign(Second) Call Duration From Originating To Assign(Second) Call Duration From Finishing Assign To Requesting Release(Second) Call Duration From Requesting Release To resource release(Second)
FL
FL
FL
FL
GC C
FL
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 soft handoff and/or softer handoff.
Page 109
5.6.1.3.2 ClcDatErl (Cell Carrier Data Erlang as Source BSS) Statistical item Description DT Trigger Duration from the time when BS receives an origination message from MS to the time when BS receives an assignment request from MSC Duration from the time when BS receives the assignment request from MSC to the time when BS sends channel assignment message to MS 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 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 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 Call Duration from the time when BS sends the assignment complete message to MSC to the time when BS sends to MSC a clear request 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 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/ S C LC Res
UmaOrg_A1fAssReq_Du ration AvfAssReq_AvfSvcAss_ Duration AvfSvcAss_AvfAssCmp_ CallDur AvfSvcAss_AvfAssCmp_ SHoDur AvfSvcAss_AvfAssCmp_ SSHoDur AvrAssCmp_AvfRlsReq_ CallDur AvrAssCmp_AvfRlsReq_ ShoDur AvrAssCmp_AvfRlsReq_ SSHoDur
Request Call Duration From Originating To Assign(Second) Call Duration From Assign Requesting To Traffic Assign(Second) Call Duration From Traffic Assign To Assign Finished(Second) Soft Handoff Duration From Traffic Assign To Assign Finished(Second) Softer Handoff Duration From Traffic Assign To Assign Finished(Second) Call Duration From Assign Finished To Requesting Release(Second) Soft Handoff Duration From Assign Finished To Requesting Release(Second) Softer Handoff Duration From Assign Finished To Requesting Release(Second)
FL
CC
FL
CC
FL
CC
FL
CC
FL
CC
FL
CC
FL
CC
FL
CC
Page 110
AvfRlsReq_EndPrc_Call Dur AvfRlsReq_EndPrc_Sho Dur AvfRlsReq_EndPrc_SSH oDur
Call Duration From Requesting Release To resource release(Second) Soft Handoff Duration From Requesting Release To resource release(Second) Softer Handoff Duration From Requesting Release To resource release(Second)
FL
Call Duration from the time when BS sends to MSC a clear request to the time of Clear Complete Soft Handoff Duration from the time when BS sends to MSC a clear request to the time of Clear Complete Softer Handoff Duration from the time when BS sends to MSC a clear request to the time of Clear Complete
CC
FL
CC
FL
CC

CallDur
T
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 soft handoff and/or softer handoff. From the above description and analysis, we can calculate the following: Call Duration: CallDur = AvfSvcAss_AvfAssCmp_CallDur + AvrAssCmp_AvfRlsReq_CallDur
+ 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:
CallDur
Traffic of call:
T
SHODur
Traffic of soft handoff:
T
SSHODur
Traffic of softer handoff:
T
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.
Page 112
5.6.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 of intra-BSS traffic

For the global inter-BSS handoffs occurring in the time period T4, where the BSS involved is the target one, only the traffic of handoff is calculated. 5.6.2.3.1 GbcDatErlTgtBss (Global Carrier Data Erlang as Target BSS) Statistical item Description Voice Handoff Duration(Second) TCH DT Trigger C/ S C LC Res
HODuration
FL
The traffic of handoff in the time period T4
GC
For the inter-BSS handoffs occurring between the cells, there may be traffic of soft handoff and traffic of softer handoff. 5.6.2.3.2 ClcDatErlTgtBss (Cell Carrier Data Erlang as Target BSS) Statistical item Description Soft Handoff Duration(Second) TCH DT Trigger C/ S C LC Res
SHoDuration
FL
The traffic of soft handoff in the time period T4
CC
Page 113
SSHoDuration
Softer Handoff Duration(Second)
TCH
FL
The traffic of softer handoff in the time period T4
CC

The duration and traffic of inter-BSS handoff are calculated as follows: Soft Handoff Duration: SHODur = SHoDuration Softer Handoff Duration: SSHODur = SSHoDuration
SHODur
Traffic of Soft Handoff:
T
SSHODur
Traffic of Softer Handoff:
T
SCH

It records the times the forward/reverse supplemental channels are successfully set up, the service level of these channels and the duration of transmission at different rates, which will be used to calculate the system resources used by the supplemental channels.
Page 114
6.2 Protocol Flow 6.3 Counter Table Detail

6.3.1 ClcFSCHInfo (Cell Carrier Forward SCH Information)
Statistical item Description DT IN w2XSuccessNum 2X Setup Success Num Trigger When PDSN has data to be transmitted, BS will request to assign supplemental channels at a certain rate. If when 2X Rate the assignment is successful, add 1 to the counter for that rate. If the resources available cannot meet the requirements, BS will continue to try at a lower rate until the lowest rate 2X. If the assignment is not successful even at 2X, add 1 to the counter. Therefore, all failed requests are at 2X. According to the systems scheduling algorithm, the supplemental channel will enquire the subscribers at an interval of 320 milliseconds. When PDSN has data to be transmitted, BS will request to assign supplemental channels at a certain rate. If when 4X Rate the assignment is successful, add 1 to the counter for that rate. If the resources available cannot meet the requirements, BS will continue to try at a lower rate until the lowest rate 4X. If the assignment is not successful even at 2X, add 1 to the counter. Therefore, all failed requests are at 2X. C/ S LC Res
CC
IN w2XFailureNum 2X Setup Failure Num
CC
IN w2X320MsNum 2X 320Ms Attempter Num IN w4XSuccessNum 4X Setup Success Num
CC
CC
CC
Page 115
According to the systems scheduling algorithm, the supplemental channel will enquire the subscribers at an interval of 320 milliseconds. When PDSN has data to be transmitted, BS will request to assign supplemental channels at a certain rate. If when 8X Rate the assignment is successful, add 1 to the counter for that rate. If the resources available cannot meet the requirements, BS will continue to try at a lower rate until the lowest rate 8X. If the assignment is not successful even at 2X, add 1 to the counter. Therefore, all failed requests are at 2X. According to the systems scheduling algorithm, the supplemental channel will enquire the subscribers at an interval of 320 milliseconds. When PDSN has data to be transmitted, BS will request to assign supplemental channels at a certain rate. If when 16X Rate the assignment is successful, add 1 to the counter for that rate. If the resources available cannot meet the requirements, BS will continue to try at a lower rate until the lowest rate 16X. If the assignment is not successful even at 2X, add 1 to the counter. Therefore, all failed requests are at 2X. According to the systems scheduling algorithm, the supplemental channel will enquire the subscribers at an interval of 320 milliseconds.
CC
CC
CC
CC
CC
CC
IN w16X320MsNum 16X 320Ms Attempter Num
CC
Page 116
IN w32XSuccessNum 32X Setup Success Num
When PDSN has data to be transmitted, BS will request to assign supplemental channels at a certain rate. If when 32X Rate the assignment is successful, add 1 to the counter for that rate. If the resources available cannot meet the requirements, BS will continue to try at a lower rate until the lowest rate 32X. If the assignment is not successful even at 2X, add 1 to the counter. Therefore, all failed requests are at 2X. According to the systems scheduling algorithm, the supplemental channel will enquire the subscribers at an interval of 320 milliseconds.
CC
CC
IN w32X320MsNum 32X 320Ms Attempter Num
CC
6.3.2 ClcRSCHInfo (Cell Carrier Reverse SCH Information)

Statistical item Description DT Trigger In the case of the reverse supplemental channel initiated by the MS, MS will request for a channel at 2X rate. Then BS will assign the channel at 2X rate. If the assignment is successful, add 1 to this counter. If BS cannot assign a reverse supplemental channel for MS at the requested 2X rate, it will try it at a lower rate again and again until the lowest rate. If the assignment is successful at a lower rate, add 1 to this counter. If the reverse supplemental channel cannot be assigned even at the lowest rate, add 1 to this counter. The duration of the reverse supplemental channel assigned to a single subscriber. C/ S LC Res
w2XSuiteRateSuccNum
2X Suite Rate Success Num
IN
CC
IN w2XDownRateSuccNum 2X Down Rate Success Num
CC
w2XAssignFailNum w2XDuration
2X Assign Failure Num 2X RSCH Duration
IN IN
C C
CC CC
Page 117
IN w4XSuiteRateSuccNum 4X Suite Rate Success Num
In the case of the reverse supplemental channel initiated by the MS, MS will request for a channel at 4X rate. Then BS will assign the channel at 4X rate. If the assignment is successful, add 1 to this counter. If BS cannot assign a reverse supplemental channel for MS at the requested 4X rate, it will try it at a lower rate again and again until the lowest rate. If the assignment is successful at a lower rate, add 1 to this counter. If the reverse supplemental channel cannot be assigned even at the lowest rate, add 1 to this counter. The duration of the reverse supplemental channel assigned to a single subscriber. In the case of the reverse supplemental channel initiated by the MS, MS will request for a channel at 8X rate. Then BS will assign the channel at 8X rate. If the assignment is successful, add 1 to this counter. If BS cannot assign a reverse supplemental channel for MS at the requested 8X rate, it will try it at a lower rate again and again until the lowest rate. If the assignment is successful at a lower rate, add 1 to this counter. If the reverse supplemental channel cannot be assigned even at the lowest rate, add 1 to this counter. The duration of the reverse supplemental channel assigned to a single subscriber. In the case of the reverse supplemental channel initiated by the MS, MS will request for a channel at 16X rate. Then BS will assign the channel at 16X rate. If the assignment is successful, add 1 to this counter.
CC
CC
IN IN IN
C C
CC CC
w8XSuiteRateSuccNum
CC
CC
IN IN IN
C C
CC CC
w16XSuiteRateSuccNum
CC
Page 118
IN w16XDownRateSuccNu m 16X Down Rate Success Num
If BS cannot assign a reverse supplemental channel for MS at the requested 16X rate, it will try it at a lower rate again and again until the lowest rate. If the assignment is successful at a lower rate, add 1 to this counter. If the reverse supplemental channel cannot be assigned even at the lowest rate, add 1 to this counter. The duration of the reverse supplemental channel assigned to a single subscriber. In the case of the reverse supplemental channel initiated by the MS, MS will request for a channel at 32X rate. Then BS will assign the channel at 32X rate. If the assignment is successful, add 1 to this counter. If BS cannot assign a reverse supplemental channel for MS at the requested 32X rate, it will try it at a lower rate again and again until the lowest rate. If the assignment is successful at a lower rate, add 1 to this counter. If the reverse supplemental channel cannot be assigned even at the lowest rate, add 1 to this counter. The duration of the reverse supplemental channel assigned to a single subscriber.
CC
IN IN IN
C C
CC CC
w32XSuiteRateSuccNum
CC
IN w32XDownRateSuccNu m 32X Down Rate Success Num
CC
IN IN
C C
CC CC

Vi represents the rates of corresponding physical layers (1X, 2X, 4X, 8X, 16X, 32X), which are 9.6Kbps, 19.2Kbps, 38.4Kbps, 76.8Kbps, 153.6Kbps and 307.2Kbps respectively.
Vi
Rate
Page 119
V2X V4X V8X V16X V32X

Average forward data burst rate =
19.2Kbps 38.4Kbps 76.8Kbps 153.6Kbps 307.2Kbps
SucNumX 19.2 + SucNumX 38.4 + SucNumX 76.8 + SucNum X 153.6 + SucNum X 307.2 2 4 8 16 32 SucNumX + SucNumX + SucNumX + SucNum X + SucNum X 2 4 8 16 32
Average reverse data burst rate =
(SucNum: SuccessNum)
(SN + DN) 2 X 19.2 + (SN + DN) 4 X 38.4 + (SN + DN)8X 76.8 + (SN + DN)16X 1536 + (SN + DN)32X 3072 . . (SN + DN) 2 X + (SN + DN) 4 X + (SN + DN)8X + (SN + DN)16X + (SN + DN)32X
DownRateNum) Match rate of each reverse rate =
(SN: SuiteRateNum, DN:
SuiteRateNum 100% SuiteRateNum + DownRateNum
Equivalent Forward Traffic (converted to 1X basic traffic) =
(320msNum) 320ms (2 + 4 + 8 + 16 + 32) T 1000ms

Equivalent Reverse traffic (converted to 1X basic traffic) =
(320msNum) 320ms (2 + 4 + 8 + 16 + 32) T 1000ms
Page 120
7 Concurrent Services
7.1 Setup/Release Model
In addition to voice services and packet data services, there are voice and packet data concurrent services, which complicate the call setup and release, as well as the calculation of traffic. For this reason, we divide the process from call setup to final release into three stages by connection and service instances: Connection service Connection service here means the connection process of the entire communication process (to distinguish it from the global and cell data in performance statistics). It mainly involves the setup and release operations in the connection between the mobile station and the base station, regardless of the service instances: voice or data. Single Service On current traffic channels, there is only one type of services, either voice or packet data. Concurrent Services On current traffic channels, there exist two types of services simultaneously: voice and packet data. Now, we will discuss the classification and counting of the data of the three service stages by analyzing the most common service procedure. We here take the example of Call Number of the three stages. Connection service with single service (either voice or data) Voice A B
Connection
A Set connections up
Single Service
Assign services voice
Concurrent Services
Page 121
Release connections
Release services
voice
Connection service with concurrent services release separately
Voice A B
Voice C Data D E F
Connection Single service

A B Set up connection Assign voice services only
Concurrent Services
Assign concurrent services
data
Release concurrent voice services Assign concurrent voice services Release concurrent voice services
Page 122
Release connection
Release services
data
Connection service with concurrent services release simultaneously
Voice A B
Voice C Data D
Connection Single Service

A B C D E Release connection Set up connection Assign services voice
Concurrent Services
Assign concurrent data services Release concurrent voice services Assign concurrent voice services Release voice & data concurrent services
The corresponding relation between the services assignment number and the services release number: The sum of voice services assignment numbers in single service and concurrent services is consistent with the sum of their release numbers. The sum of data services assignment numbers in single service and concurrent services is consistent with the sum of their release numbers. Where,
The services assignment number = voice services assignment number in single service + data services assignment number in single service The services release number = voice services assignment number in single service + data services assignment number in single service + concurrent voice & data service release number The service assignment/release number will be counted separately, but obtained from the above calculation. Special Attention: The services assignment in single service does not correspond to its services release one by one. The services assignment in concurrent services does not correspond to their services release one by one. Establishment of statistic models: Connection Service: Count only the number of connection setup and that of connection release. Voice Services: Count the numbers of voice services in single service and concurrent services Data Services: Count the numbers of data services in single service and concurrent services
7.2 Traffic Calculation Model

Here is an example of traffic calculation models for three stages:
Page 124
Uma_Origination Duration T1 Voice A1f_AssignmentRequest Duration T2 Voice Avf_ServiceAssignmen Duration T3 Voice
Avr_AssignmentComplete Duration T4 Voice
Duration T5
Avr_ReleaseRequest (Release of concurrent voice)
Data
ResourceRelease Duration T6
Duration T7
Avr_ReleaseRequest (release of concurrent data)
ResourceRelease
Page 125
Duration T8
Concurrent services occur after Avr_AssignmentComplete, whose traffic can be calculated as the duration in the above figure (i.e. the duration from the release starts to the release ends). T1, T2 and T3: No concurrent services occur, so report them as durations of single service (voice services). T4: There are only voice services, report it as the duration of voice services T5: There are both voice and data services, report it as the duration of concurrent services, regardless of concurrent voice services or concurrent data services T6: There are only data services, report it as the duration of voice services. T7: There are both voice and data services, report it as the duration of concurrent services. T8: There are only voice services, report it as the duration of voice services. Traffic Calculation Model: Traffic of Connection service: T1 + T2 + T3 + T4 + T5 + T6 + T7 + T8 Traffic of Voice Services: T1 + T2 + T3 + T4 + T5 + T7 + T8 Traffic of Data Services: T5 + T6 + T7 Traffic of Concurrent Services: T5 + T7 The traffic of connection service can be obtained from the above formula, and no counter is set for it separately.
7.3 Concurrent Voice Services

7.3.1 Call Origination (Concurrent Voice Services)
It means the call origination of voice services occurs during data services. The items to be counted, involving the global carrier and the cell, are the same as those in call origination process of voice services.

Page 126

7.3.1.3.1 GbcConVocOrgCall (Global Carrier Concurrent Voice Originating Call) Statistical item Description DT Trigger C/ S LC Res
Page 127
MS Originating Num Concurrent Voice Originating Request Num Outer Interrupt Num
FL FL
Add 1 to the counter every time when BS receives an enhanced origination message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of call setup. Add 1 to the counter every time when the call origination fails for reasons other than the above.
C C
GC GC GC
ExtInterruptNum
FL
C GC GC
FL FL
C C
7.3.1.3.2 ClcConVocOrgCall (Cell Carrier Concurrent Voice Originating Call) Statistical item Description DT Trigger Add 1 to the counter every time when BS receives an enhanced origination message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of call setup. Add 1 to the counter every time when the call origination fails for reasons other than the above. C/ S C C LC Res
MS Originating Num Concurrent Voice Originating Request Num Outer Interrupt Num
IN IN IN
CC CC
ExtInterruptNum
CC
IN IN
C C
CC CC
Page 128
SuccessNum
OriginateNum
100%
BlockNum
OriginateNum
100%
OriginateNum
100%
7.3.2 Paging (Concurrent Voice Services)

It means the paging of voice services occurs during data services. The items to be counted, involving the global carrier and the cell, are the same as those in paging process of voice services.

Page 129
Page 130

7.3.2.3.1 GbcConVocPagCall (Global Carrier Concurrent Voice Paging Call)
Statistical item
Description
DT
Trigger Add 1 to the counter every time when BS receives an additional service notification from MSC. Add 1 to the counter every time when BS receives a page response message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of call setup. Add 1 to the counter every time when the paging fails for reasons other than the above.
C/ S C C C
LC GC GC GC GC
Res
Paging MS Num Paging Response Num Paging Request Num
FL FL FL
ExtInterruptNum
Outer Interrupt Num
FL
C GC GC
FL FL
C C
7.3.2.3.2 ClcConVocPagCall (Cell Carrier Concurrent Voice Paging Call) Statistical item Description DT IN Trigger Add 1 to the counter every time when BS receives an additional service notification from MSC. C/ S C LC Res
PagingMsNum
Paging MS Num
CC
Page 131
Paging Response Num Paging Request Num
IN IN IN
C C
CC CC
ExtInterruptNum
CC
C C
CC CC
PagingResponseNum
100%
100%
Paging Block Rate =
PagingResponseNum
100%
Page 132
PagingResponseNum
100%
7.4 Concurrent Data Services

7.4.1 Call Origination (Concurrent Data Services)
It means the call origination of data services occurs during voice services. The items to be counted, involving the global carrier and the cell, are the same as those in call origination process of data services.

Page 133
Page 134

7.4.1.3.1 GbcConDatOrgCall (Global Carrier Concurrent Data Originating Call) Statistical item Description DT Trigger Add 1 to the counter every time when BS receives an enhanced origination message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of call setup. Add 1 to the counter every time when the call origination fails for reasons other than the above. C/ S C C LC GC GC GC C GC GC Res
MS Originating Num Concurrent Data Originating Request Num Outer Interrupt Num
FL FL
ExtInterruptNum
FL
FL FL
C C
7.4.1.3.2 ClcConDatOrgCall (Cell Carrier Concurrent Data Originating Call) Statistical item Description DT IN IN Trigger Add 1 to the counter every time when BS receives an enhanced origination message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. C/ S C C LC Res
MS Originating Num Concurrent Data Originating Request Num
CC CC
Page 135
CC
C C
CC CC
SuccessNum
OriginateNum
100%
BlockNum
OriginateNum
100%
OriginateNum
100%
Page 136
7.4.2 Paging (Concurrent Data Services)

It means during voice services, the PCF initiates the paging process of the mobile station from Dormant state to Active state. The items to be counted involve the global carriers and the cell carriers.

Page 137
Page 138

7.4.2.3.1 GbcConDatPagCall (Global Carrier Concurrent Data Paging Call) Statistical item Description DT Trigger Add 1 to the counter every time when BS receives a A9 BS Service request from PCF. Add 1 to the counter every time when BS receives a page response message from MS. Add 1 to the counter every time when BS sends the Assignment Complete message to MSC. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of call setup. Add 1 to the counter every time when the paging fails for reasons other than the above. C/ S C C C LC GC GC GC GC C GC GC Res
Paging MS Num Paging Response Num Paging Request Num
FL FL FL
ExtInterruptNum
Outer Interrupt Num
FL
FL FL
C C
7.4.2.3.2 ClcConDatPagCall (Cell Carrier Concurrent Data Paging Call) Statistical item Description DT IN Trigger Add 1 to the counter every time when BS receives a A9 BS Service request from PCF. C/ S C LC Res
PagingMsNum
Paging MS Num
CC
Page 139
Paging Response Num Paging Request Num
IN IN IN
C C
CC CC
ExtInterruptNum
CC
C C
CC CC
PagingResponseNum
100%
100%
Paging Block Rate =
PagingResponseNum
100%
Page 140
PagingResponseNum
100%
7.5 Concurrent Release

The concurrent releases are broken down into three cases: first release of voice services, first release of data services and simultaneous release of voice and data services. Therefore, count the numbers of normal and abnormal releases of the three cases respectively.
7.5.2 Protocol Flow

Page 141
Page 142

7.5.3.1 GbcConRls (Global Carrier Concurrent Release)
Statistical item Description DT Trigger When BS sends a Service Release message to MSC, it will determine whether it is a normal Voice release based on the message. If yes, it will add 1 to the counter. C/ S C LC GC Res
ConVoc_RlsSuccNum
Concurrent Voice Success Num
Release
FL
Page 143
ConVoc_RlsFailNum
Concurrent Voice Failure Num Concurrent Data Success Num Concurrent Data Failure Num
Release
FL
When BS sends a Service Release message to MSC, it will determine whether it is an abnormal Voice release based on the message. If yes, it will add 1 to the counter. When BS sends a Service Release message to MSC, it will determine whether it is a normal Data release based on the message. If yes, it will add 1 to the counter. When BS sends a Service Release message to MSC, it will determine whether it is an abnormal Data release based on the message. If yes, it will add 1 to the counter. When BS sends a Service Release message to MSC, it will determine whether it is a normal Voice and Data release based on the message. If yes, it will add 1 to the counter. When BS sends a Service Release message to MSC, it will determine whether it is an abnormal Voice and Data release based on the message. If yes, it will add 1 to the counter.
ConData_RlsSuccNum
Release
FL
ConData_RlsFailNum
Release
FL
ConVocData_RlsSuccNu m
Concurrent Voice and Data Release Success Num Concurrent Voice and Data Release Failure Num
FL
ConVocData_RlsFailNum
FL
7.5.3.2 ClcConRls (Cell Carrier Concurrent Release)

Statistical item Description DT IN Trigger When BS sends a Service Release message to MSC, it will determine whether it is a normal Voice release based on the message. If yes, it will add 1 to the counter. When BS sends a Service Release message to MSC, it will determine whether it is an abnormal Voice release based on the message. If yes, it will add 1 to the counter. C/ S C LC Res
ConVoc_RlsSuccNum
Concurrent Voice Success Num Concurrent Voice Failure Num
Release
CC
ConVoc_RlsFailNum
Release
IN
CC
Page 144
ConData_RlsSuccNum
Concurrent Data Success Num Concurrent Data Failure Num
Release
IN
When BS sends a Service Release message to MSC, it will determine whether it is a normal Data release based on the message. If yes, it will add 1 to the counter. When BS sends a Service Release message to MSC, it will determine whether it is an abnormal Data release based on the message. If yes, it will add 1 to the counter. When BS sends a Service Release message to MSC, it will determine whether it is a normal Voice and Data release based on the message. If yes, it will add 1 to the counter. When BS sends a Service Release message to MSC, it will determine whether it is an abnormal Voice and Data release based on the message. If yes, it will add 1 to the counter.
CC
ConData_RlsFailNum
Release
IN
CC
ConVocData_RlsSuccNu m
Concurrent Voice and Data Release Success Num Concurrent Voice and Data Release Failure Num
IN
CC
IN
ConVocData_RlsFailNum
CC
DropNum
Call drop rate =
100%
7.6 Concurrent Traffic

In calculating the traffic of concurrent services, the traffic of voices services and data services should be distinguished. The traffic of these services involves the global carriers and cell carriers.
Page 145
7.6.2 Protocol Flow

Please refer to related description in Section 6.1.

7.6.3.1 GbcConErl (Global Carrier Concurrent Erlang)
Statistical item Description Call Duration From Traffic Assign To Finishing Assign(Second) Call Duration From Finishing Assign To Requesting Release(Second) Call Duration From Requesting Release To resource release(Second) DT Trigger Duration from the time when BS sends channel assignment message to MS to the time when BS sends an assignment complete message to MSC 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) Duration from the time when BS sends to MSC a clear request to the time of Clear Complete C/ S C GC C LC GC Res
AvfSvcAss_AvfAssCmp_ Dur
FL
FL
GC C
FL
7.6.3.2 ClcConErl (Cell Carrier Concurrent Erlang)

Statistical item Description Call Duration From Traffic Assign To Assign Finished(Second) DT Trigger 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/ S C LC Res
AvfSvcAss_AvfAssCmp_ CallDur
FL
CC
Page 146
AvfSvcAss_AvfAssCmp_ SHoDur AvfSvcAss_AvfAssCmp_ SSHoDur AvrAssCmp_AvfRlsReq_ CallDur AvrAssCmp_AvfRlsReq_ ShoDur AvrAssCmp_AvfRlsReq_ SSHoDur AvfRlsReq_EndPrc_Call Dur AvfRlsReq_EndPrc_Sho Dur AvfRlsReq_EndPrc_SSH oDur
Soft Handoff Duration From Traffic Assign To Assign Finished(Second) Softer Handoff Duration From Traffic Assign To Assign Finished(Second) Call Duration From Assign Finished To Requesting Release(Second) Soft Handoff Duration From Assign Finished To Requesting Release(Second) Softer Handoff Duration From Assign Finished To Requesting Release(Second) Call Duration From Requesting Release To resource release(Second) Soft Handoff Duration From Requesting Release To resource release(Second) Softer Handoff Duration From Requesting Release To resource release(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 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 Call Duration from the time when BS sends the assignment complete message to MSC to the time when BS sends to MSC a clear request 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 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 Call Duration from the time when BS sends to MSC a clear request to the time of Clear Complete Soft Handoff Duration from the time when BS sends to MSC a clear request to the time of Clear Complete Softer Handoff Duration from the time when BS sends to MSC a clear request to the time of Clear Complete
CC
FL
CC
FL
CC
FL
CC
FL
CC
FL
CC
FL
CC
FL
CC
Page 147

Please refer to related description in Section 6.1.
8 Hard Handoff
8.1 Hard Handoff Add to a BSS
The hard handoff add to a BSS means the call is handed off into the source BSC, the process of which is similar to that of a call. Therefore, the items to be recorded here are the same as that for common calls. The statistics here involves the global carriers and cells.
8.1.2 Protocol Flow

Page 148
Page 149

8.1.3.1 GbcHdHoAdd (Global Carrier Hard Handoff Add)
Statistical item VOC_HoAddRequestNu m VOC_HoAddSuccessNu m VOC_HoExtInterruptNum VOC_HoBlockFailureNu m VOC_HoOtherFailureNu m DATA_HoAddRequestNu m DATA_HoAddSuccessNu m DATA_HoExtInterruptNu m DATA_HoBlockFailureNu m DATA_HoOtherFailureNu m
Description Voice Hard Handoff Request Num Voice Hard Handoff Request Num Add Add
DT
Trigger Add 1 to the counter every time when the target BSC receives the Voice Handoff request from MSC. Add 1 to the counter every time when the target BSC receives the Voice Handoff Complete message. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of handoff. Add 1 to the counter every time when the hard handoff fails for reasons other than the above. Add 1 to the counter every time when the target BSC receives the Handoff request from MSC. Add 1 to the counter every time when the target BSC receives the Data Handoff Complete message. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of handoff. Add 1 to the counter every time when the hard handoff fails for reasons other than the above.
C/ S C C
LC GC GC GC
Res
FL FL
Voice Hard Handoff Add Outer Interrupt Num Voice Hard Handoff Add Block Success Num Voice Hard Handoff Add Other Success Num Data Hard Handoff Request Num Data Hard Handoff Request Num Add Add
FL
C GC GC GC GC GC C GC GC
FL FL FL FL
C C C C
Data Hard Handoff Add Outer Interrupt Num Data Hard Handoff Add Block Success Num Data Hard Handoff Add Other Success Num
FL
FL FL
C C
Page 150
CON_HoAddRequestNu m CON_HoAddSuccessNu m CON_HoExtInterruptNum CON_HoBlockFailureNu m CON_HoOtherFailureNu m
Concurrent Hard Handoff Add Request Num Concurrent Hard Handoff Add Request Num Concurrent Hard Handoff Add Outer Interrupt Num Concurrent Hard Handoff Add Block Success Num Concurrent Hard Handoff Add Other Success Num
FL FL
Add 1 to the counter every time when the target BSC receives the Voice and Data Handoff request from MSC. Add 1 to the counter every time when the target BSC receives the Voice and Data Handoff Complete message. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of handoff. Add 1 to the counter every time when the hard handoff fails for reasons other than the above.
C C
GC GC GC
FL
C GC GC
FL FL
C C
8.1.3.2 ClcHdHoAddTgtBss (Cell Carrier Hard Handoff Add as Target BSS)

Statistical item VOC_HoAddRequestNu m VOC_HoAddSuccessNu m VOC_HoExtInterruptNum VOC_HoBlockFailureNu m VOC_HoOtherFailureNu m Description Voice Hard Handoff Request Num Voice Hard Handoff Request Num Add Add DT IN IN IN Trigger Add 1 to the counter every time when the target BSC receives the Voice Handoff request from MSC. Add 1 to the counter every time when the target BSC receives the Voice Handoff Complete message. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of handoff. Add 1 to the counter every time when the hard handoff fails for reasons other than the above. C/ S C C LC Res
CC CC
Voice Hard Handoff Add Outer Interrupt Num Voice Hard Handoff Add Block Success Num Voice Hard Handoff Add Other Success Num
CC
IN IN
C C
CC CC
Page 151
DATA_HoAddRequestNu m DATA_HoAddSuccessNu m DATA_HoExtInterruptNu m DATA_HoBlockFailureNu m DATA_HoOtherFailureNu m CON_HoAddRequestNu m CON_HoAddSuccessNu m CON_HoExtInterruptNum CON_HoBlockFailureNu m CON_HoOtherFailureNu m
Data Hard Handoff Request Num Data Hard Handoff Request Num
Add Add
IN IN IN
Add 1 to the counter every time when the target BSC receives the Handoff request from MSC. Add 1 to the counter every time when the target BSC receives the Data Handoff Complete message. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of handoff. Add 1 to the counter every time when the hard handoff fails for reasons other than the above. Add 1 to the counter every time when the target BSC receives the Voice and Data Handoff request from MSC. Add 1 to the counter every time when the target BSC receives the Voice and Data Handoff Complete message. 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). Add 1 to the counter every time when BS receives a release request from MS or MSC in the process of handoff. Add 1 to the counter every time when the hard handoff fails for reasons other than the above.
C C
CC CC
Data Hard Handoff Add Outer Interrupt Num Data Hard Handoff Add Block Success Num Data Hard Handoff Add Other Success Num Concurrent Hard Handoff Add Request Num Concurrent Hard Handoff Add Request Num Concurrent Hard Handoff Add Outer Interrupt Num Concurrent Hard Handoff Add Block Success Num Concurrent Hard Handoff Add Other Success Num
CC
IN IN IN IN IN
C C C C
CC CC CC CC
CC
IN IN
C C
CC CC
Page 152
HoAddSuccessNum
Success Rate of Hard Handoff Add =
HoAddRequestNum
100%
The success rates for voice, data and concurrent services can be calculated respectively.
8.2 Hard Handoff Off a BSS

As the resource(s) are released only one time in hard handoff off of a BSS, simply record the number of handoffs, which should include that in voice, data and concurrent services. This statistics involves in global carriers and cells.
8.2.2 Protocol Flow

Please refer to the flow in Section 7.1.2.

8.2.3.1 GbcHdHoDrpSrcBss (Global Carrier Hard Handoff Drop as Source BSS)
Statistical item Description Voice Hard Handoff Removed Num Data Hard Handoff Removed Num DT Trigger Add 1 to the counter every time when the source BSC sends a Voice Handoff Required message. Add 1 to the counter every time when the source BSC sends a Data Handoff Required message. C/ S C C LC GC GC Res
Voc_HoDropNum Data_HoDropNum
FL FL
Page 153
Con_HoDropNum
Concurrent Hard Removed Num
Handoff
FL
Add 1 to the counter every time when the source BSC sends a Voice and Data Handoff Required message.
GC
8.2.3.2 ClcHdHoDrp (Cell Carrier Hard Handoff Drop)

Statistical item Description Voice Hard Handoff Removed Num Data Hard Handoff Removed Num Concurrent Hard Removed Num Handoff DT IN IN IN Trigger Add 1 to the counter every time when the source BSC sends a Voice Handoff Required message. Add 1 to the counter every time when the source BSC sends a Data Handoff Required message. Add 1 to the counter every time when the source BSC sends a Voice and Data Handoff Required message. C/ S C C C LC CC CC CC Res
Voc_HoDropNum Data_HoDropNum Con_HoDropNum

None
PCF
9.1 PCF Call

PCF calls are divided into the following types: NULL and Dormant calls initiated by the MS and Dormant call initiated by PDSN, which are all global data.
Page 154
9.1.2 Protocol Flow

For details, please refer to 3GPP2 A.S0001-A version 2.0 2.14.7.1 and 2.14.7.7.
Page 155
Page 156

9.1.3.1 GbcPcfCall (Global Carrier PCF Call)
Statistical item Description DT Trigger Every time when PCF receive an A9-Setup-A8 request from BSC that MS is Null State, it will judge the state of the MS and add 1 to the counter accordingly. Every time when PCF sends an A9-Connect-A8 message to BSC that MS is Null State, it will judge the state of the MS and add 1 to the counter accordingly. Every time when PCF receive an A9-Setup-A8 request from BSC that MS is Dormant State, it will judge the state of the MS and add 1 to the counter accordingly. Every time when PCF sends an A9-Connect-A8 message to BSC that MS is Dormant State, it will judge the state of the MS and add 1 to the counter accordingly. Every time when PCF receive an A9-Setup-A8 request from BSC that PDSN paging, it will judge the state of the MS and add 1 to the counter accordingly. Every time when PCF sends an A9-Connect-A8 message to BSC that PDSN paging, it will judge the state of the MS and add 1 to the counter accordingly. C/ S C GC C GC C GC C GC C GC C LC GC Res
NC_CallSNum
NULL Call Request Num
FL
NC_CallFNum
NULL Call Success Num
FL
DC_CallSNum
Dormant Call Request Num
FL
DC_CallFNum
Dormant Call Success Num
FL
PC_CallSNum
PDSN Call Request Num
FL
PC_CallFNum
PDSN Call Success Num
FL
Page 157
SuccessNum
Call Success Rate =
RequestNum
100%
The success rates of NULL call, Dormant call and PDSN call can be calculated respectively.
9.2 PCF Handoff

9.2.1 Function Description 9.2.2 Protocol Flow
Page 158
Page 159

9.2.3.1 GbcPcfHo (Global PCF Handoff)
Statistical item Description DT Trigger Add 1 to the counter every time when the target PCF sends an A11-Registration request (Lifetime, MEI) to PDSN that MS is Dormant State. Add 1 to the counter every time when the target PCF receives an A11-Registration Reply (Lifetime, Accept) from PDSN that MS is Dormant State. Add 1 to the counter every time when the source PCF receives an A11-Registration Update from PDSN that MS is Dormant State. Add 1 to the counter every time when the source PCF receives an A11-Registration Reply (Lifetime=0, Accept) from PDSN that MS is Dormant State. Add 1 to the counter every time when the target PCF sends an A11-Registration request (Lifetime, MEI) to PDSN that MS is Active State. Add 1 to the counter every time when the target PCF receives an A11-Registration Reply (Lifetime, Accept) from PDSN that MS is Active State. Add 1 to the counter every time when the source PCF receives an A11-Registration Update from PDSN that MS is Active State. C/ S C GC C GC C GC C GC C GC C GC C LC GC Res
DA_HandoffSNum
Dormant Handoff In Success Num Dormant Handoff In Failure Num Dormant Handoff Out Success Num Dormant Handoff Out Failure Num Active Handoff In Success Num
FL
DA_HanfoffFNum
FL
DD_HandoffSNum
FL
DD_HanfoffFNum
FL
AA_HandoffSNum
FL
AA_HanfoffFNum
Active Handoff In Failure Num
FL
AD_HandoffSNum
Active Handoff Out Success Num
FL
Page 160
AD_HanfoffFNum
Active Handoff Out Failure Num
FL
Add 1 to the counter every time when the source PCF receives an A11-Registration Reply (Lifetime=0, Accept) from PDSN that MS is Active State.
GC C
SuccessNum
Handoff Success Rate =
RequestNum
100%
The success rate of handoff in and handoff out of sessions in Active/Dormant state can be calculated separately.
9.3 PCF Release

It records the session releases on the PCF, Active-Null release, Active-Dormant release and Dormant-Null release.
9.3.2 Protocol Flow

For details, please refer to 3GPP2 A.S0001-A version 2.0 2.14.7.2, 2.14.7.3, 2.14.7.4 and 2.14.7.5.
Page 161
Page 162

9.3.3.1 GbcPcfRls (Global PCF Release)
Statistical item Description DT Trigger Every time when PCF receive an A9-Release-A8 request from BSC, it will judge the state of the MS that from Active to Null, and add 1 to the counter accordingly. Every time when PCF sends an A9-Release-A8 Complete message to BSC, it will judge the state of the MS that from Active to Null, and add 1 to the counter accordingly. Every time when PCF receive an A9-Release-A8 request from BSC, it will judge the state of the MS that from Active to Dormant, and add 1 to the counter accordingly. Every time when PCF sends an A9-Release-A8 Complete message to BSC, it will judge the state of the MS that from Active to Dormant, and add 1 to the counter accordingly. Every time when PCF receive an A9-Release-A8 request from BSC, it will judge the state of the MS that from Dormant to Null, and add 1 to the counter accordingly. Every time when PCF sends an A9-Release-A8 Complete message to BSC, it will judge the state of the MS that from Dormant to Null, and add 1 to the counter accordingly. C/ S C GC C GC C GC C GC C GC C LC GC Res
A2N_RlsSNum
Active To Null Success Num
FL
A2N_RlsFNum
Active To Null Failure Num
FL
A2D_RlsSNum
Active To Dormant Success Num Active To Dormant Failure Num
FL
A2D_RlsFNum
FL
D2N_RlsSNum
Dormant To Null Success Num
FL
D2N_RlsFNum
Dormant To Null Failure Num
FL
Page 163
SuccessNum
Release Success Rate =
RequestNum
100%
The release success rate of Active-Null, Active-Dormant and Dormant-Null can be calculated separately.
9.4 Transition between PCF States

It records the transitions between the three states of MS sessions: Null, Dormant and Active. The transitions fall into 6 cases.
9.4.2 Protocol Flow

The transition between PCF states is actually the setup and release processes of connections between the mobile station and the base station. Therefore, you can refer to the call and release flows.

9.4.3.1 GbcPcfSta (Global PCF Status)
Statistical item Null2ActiveNum Active2NullNum Active2DormNum
Description Null To Active Status Num Active To Null Status Num Active To Dormant Status Num
DT FL FL FL
Trigger This is a call from Null state to Active State This is a release from Active state to Null State This is a release from Active state to Dormant State
C/ S C C C
LC GC GC GC
Res
Page 164
Dorm2ActiveNum Null2DormNum Dorm2NullNum
Dormant To Active Status Num Null To Dormant Status Num Dormant To Null Status Num
FL FL FL
This is a call from Dormant to Active State This is a call from Null state to Dormant State This is a release from Dormant state to Null State
C C C
GC GC GC

None
9.5 PCF Block

It records the blocks between PCF and BS/PDSN.
9.5.2 Protocol Flow

For details, please refer to PCF call flow.

9.5.3.1 GbcPcfBlk (Global Carrier PCF Block)
Statistical item PDSNBlock RPLinkBlock UPCFResourceBlock Description PDSN Capacity Block RP Link Block UPCF Resource Block DT FL FL FL Trigger A Data call fail due to the PDSN reason A Data call fail due to the RP link is not available A Data call fail due to the UPCF Resource is not available C/ S C C C LC GC GC GC Res
Page 165

None
9.6 PCF Traffic

It records the data flow by the PCF module, including the number and bytes of downloaded/uploaded data packets.
9.6.2 Protocol Flow

None

9.6.3.1 GbcPcfMacDatFlow (Global PCF Mac Data Flow)
Statistical item ArpRevMsg ArpSndMsg IcmpRevMsg IcmpSndMsg RevFrameNum RevFrameSize SndFrameNum Description Receive ARP Packet Num Send ARP Packet Num Receive ICMP Packet Num Send ICMP Packet Num Receive Ethernet Packet Num the Bytes of Receive Ethernet Packet Bytes Send Ethernet Packet Num DT FL FL FL FL FL FL FL Trigger The number of ARP that PCF Received The number of ARP that PCF Send The number of ICMP that PCF Received The number of ICMP that PCF Send The number of Frame that PCF Received in Ethernet Link The Bytes of Frame that PCF Received in Ethernet Link The number of Frame that PCF Send in Ethernet Link C/ S C C C C C C LC GC GC GC GC GC GC Res
Page 166
SndFrameSize RevErrFrameNum RevErrFrameSize
the Bytes of Send Ethernet Packet Bytes Receive Ethernet Error Packet Num the Bytes of Receive Error Ethernet Packet Bytes
FL FL FL
The Bytes of Frame that PCF Send in Ethernet Link The number of Error Frame that PCF Received in Ethernet Link The Bytes of Error Frame that PCF Received in Ethernet Link
9.6.3.2 GbcPcfMediaDatFlow (Global PCF Media Data Flow)

Statistical item PCF2MSNum PCF2MSByte PCF2PDSNNum PCF2PDSNByte PDSN2PCFNum PDSN2PCFByte MS2PCFNum MS2PCFByte DiscardNumforBufferLack DiscardNumforUnknown MS DiscardNumforOtherRsn Description PCF to MS Packet Num PCF to MS Packet Bytes PCF to PDSN Packet Num PCF to PDSN Packet Bytes PDSN to PCF Packet Num PDSN to PCF Packet Bytes MS to PCF Packet Num MS to PCF Packet Bytes Discard Num for Buffer Lack Discard Num for Unknown MS Discard Num Reasons for Other DT FL FL FL FL FL FL FL FL FL FL FL Trigger The media packet number that from PCF to MS The media packet bytes that from PCF to MS The media packet number that from PCF to PDSN The media packet bytes that from PCF to PDSN The media packet number that from PDSN to PCF The media packet bytes that from PDSN to PCF The media packet number that from MS to PCF The media packet bytes that from MS to PCF The media packet number that discard because of the buffer is lack The media packet number that discard because of unknown MS The media packet number that discard because of the other reason C/ S C C C C C C LC GC GC GC GC GC GC Res
Page 167
9.6.3.3 GbcPcfSignalDatFlow (Global PCF Signal Data Flow)

Statistical item PCF2PDSNNum PCF2PDSNByte PDSN2PCFNum PDSN2PCFByte Description PCF to PDSN Packet Num PCF to PDSN Packet Bytes PDSN to PCF Packet Num PDSN to PCF Packet Bytes DT FL FL FL FL Trigger The signal packet number that from PCF to PDSN The signal packet bytes that from PCF to PDSN The signal packet number that from PDSN to PCF The signal packet bytes that from PDSN to PCF C/ S C C C C LC GC GC GC GC Res

None
10 System Resources
It mainly records the total number, available number and maximum busy number of CDMA system resources so as to trace the usage of the resources within a certain period.
10.2 Protocol Flow

None
Page 168

10.3.1 Selector Element
Statistical item SETotalNum SEReliableNum MaxBusySENum Description SE Total Num SE Reliable Num SE Max Busy Num DT FL FL FL Trigger Total SE configured number Number of SE available The maximum SE number that can be used in a certain period C/ S S S C LC GC GC GC Res
10.3.2 PCF Entity

Statistical item Description The maximum Entity Busy PCF DT Trigger C/ S C C C C LC GC GC GC GC Res
MaxBusyPCFCENum MaxEntityActiveNum PCFCEAllocFailNum PCFCEAllocTotalNum
FL FL FL FL
The maximum number of Busy PCF Entity available The maximum number of Active PCF Entity available The number that allocated the PCF Entity is failure The total number that allocated the PCF Entity
The maximum Active PCF Entity PCF CE Allocate Failure Num PCF CE Allocate Total Num
10.3.3 Vocoder Element

Statistical item TotalVENum Description VE Total Num DT int Trigger Total VE configured number C/ S S LC GC Res
Page 169
ReliableVENum MaxBusyVENum
VE Reliable Num VE Max Busy Num
int int
Number of VE available The maximum SE number that can be used in a certain period
S C
GC GC
10.3.4 CIC
Statistical item TotalCICNum ReliableCICNum MaxBusyCICNum Description CIC Total Num CIC Reliable Num CIC Max Busy Num DT int int int Trigger Total CIC configured number Number of CIC available The maximum SE number that can be used in a certain period C/ S S S C LC GC GC GC Res
10.3.5 Forward Channel Element

Statistical item Description DT IN IN IN IN IN IN Trigger C/ S S S C C C C LC BT S BT S BT S BT S BT S BT S
Page 170
Res
TotalCENum ReliableCENum MaxBusyVoiceFCHUsed CENum MaxBusyDataFCHUsedC ENum MaxBusyCurFCHUsedC ENum MaxBusyDataSCHUsedC ENum
FTCE Total Num FTCE Reliable Num Voice FTCE Max Busy Num Data FTCE Max Busy Num Concurrent FTCE Max Busy Num Data FSCE Max Busy Num
Total CE configured number Number of CE available The maximum Voice FCHCE number that can be used in a certain period The maximum Data FCHCE number that can be used in a certain period The maximum Voice and Data FCHCE number that can be used in a certain period The maximum Data FSCHCE number that can be used in a certain period
MaxBusyDataDCCHUsed CENum
Data FDCCH Max Busy Num
IN
The maximum Data DCCHCE number that can be used in a certain period
BT S
10.3.6 Reverse Channel Element

Statistical item Description DT IN IN IN IN IN IN IN Trigger C/ S S S C C C C C LC BT S BT S BT S BT S BT S BT S BT S Res
TotalCENum ReliableCENum MaxBusyVoiceRCHUsed CENum MaxBusyDataRCHUsedC ENum MaxBusyCurRCHUsedC ENum MaxBusyDataSCHUsedC ENum MaxBusyDataDCCHUsed CENum
RTCE Total Num RTCE Reliable Num Voice RTCE Max Busy Num Data RTCE Max Busy Num Concurrent RTCE Max Busy Num Data RSCE Max Busy Num Data RDCCH Max Busy Num
Total CE configured number Number of CE available The maximum Voice RFCHCE number that can be used in a certain period The maximum Data RFCHCE number that can be used in a certain period The maximum Voice and Data RCHCE number that can be used in a certain period The maximum Data RSCHCE number that can be used in a certain period The maximum Data DCCHCE number that can be used in a certain period
10.3.7 Traffic Channel

Statistical item Description DT Trigger C/ S LC Res
Page 171
MaxBusyVoiceFCHNum MaxBusyDataFCHNum MaxBusyCurFCHNum MaxBusyDataFwdSCHNu m MaxBusyDataRevSCHNu m MaxBusyDataDCCHNum SCHUsedWalshCodeTim e
Voice FCH Max Busy Num Data FCH Max Busy Num Concurrent FCH Max Busy Num Data FSCH Max Busy Num Data RSCH Max Busy Num DCCH Max Busy Num SCH WalshCode Duration
IN IN IN IN IN IN
The maximum Voice FCH number that can be used in a certain period The maximum Data FCH number that can be used in a certain period The maximum Voice and Data FCH number that can be used in a certain period The maximum Data FSCH number that can be used in a certain period The maximum Data RSCH number that can be used in a certain period The maximum Data DCCH number that can be used in a certain period The time that RSCH
C C C C C C C
CC CC CC CC CC CC CC
FL
10.3.8 CPU
The Cpu Usage StatistiC/S Include all Main Control Boards. Statistical item MaxUseRate AvgUseRate Description Max Use Rate Average Use Rate DT IN IN Trigger The maximum of CPU about main control board The average of CPU about main control board C/ S S S LC GC GC Res
Page 172
ReliableNum
Availability =
TotalNum
100%
BusyNum
Maximum Usage =
ReliableNum
100%
11 Block
11.1 Block (Voice Services)
The block in voice services is an important factor resulting in failure of voice services setup. Therefore, the block data of the resources that may be used in the services should be recorded in detail. The block data involves in global and cell carriers.
11.1.2 Protocol Flow

Please refer to the flows in voice services, such as setup flow and handoff flow.
Page 173

11.1.3.1 GbcVocBlkRsn (Global Carrier Voice Block Reason)
Description DT Trigger The type will label that Voice Call, Voice Handoff Add and Voice hard handoff add. The service process is failure due to the VE not available. The service process is failure due to the SE not available. The service process is failure due to the DSMP not available. The service process is failure due to the CIC not available. The service process is failure due to the CE not available. The service process is failure due to the CH not available. The service process is failure due to the Forward Power not available. The service process is failure due to the Reverse power not available. The service process is failure due to the Frame Offset not available. The service process is failure due to the Carrier status error. C/ S C C C C C C C C C C C LC GC GC GC GC GC GC GC GC GC GC GC Res
Statistical item
ServiceType VEBlockNum SEBlockNum DSMPBlockNum CICBlockNum CEBlockNum CHBlockNum FPWBlockNum RPWBlockNum FOBlockNum CRErrBlockNum
Service Type VE Block Number SE Block Number DSMP Block Number CIC Block Number CE Block Number CH Block Number Forward Power Block Number Reverse Power Block Number Frame Offset Block Number Carrier Frequency Status Failure Oriented Block
TI FL FL FL FL FL FL FL FL FL FL
11.1.3.2
ClcVocBlkRsn (Cell Carrier Voice Block Reason)

Description DT Trigger C/ S LC Res
Statistical item
Page 174
ServiceType VEBlockNum SEBlockNum DSMPBlockNum CICBlockNum CEBlockNum CHBlockNum FPWBlockNum RPWBlockNum FOBlockNum CRErrBlockNum
Service Type VE Block Number SE Block Number DSMP Block Number CIC Block Number CE Block Number CH Block Number Forward Power Block Number Reverse Power Block Number Frame Offset Block Number Carrier Frequency Status Failure Oriented Block
TI IN IN IN IN IN IN IN IN IN IN
The type will label that Voice Call, Voice Handoff Add and Voice hard handoff add. The service process is failure due to the VE not available. The service process is failure due to the SE not available. The service process is failure due to the DSMP not available. The service process is failure due to the CIC not available. The service process is failure due to the CE not available. The service process is failure due to the CH not available. The service process is failure due to the Forward Power not available. The service process is failure due to the Reverse power not available. The service process is failure due to the Frame Offset not available. The service process is failure due to the Carrier status error.
C C C C C C C C C C C
CC CC CC CC CC CC CC CC CC CC CC

None
11.2 Block (SMS)

The block of traffic channels in SMS is an important factor resulting in failure of SMS setup. Therefore, the block data of the resources that may be
Page 175
used in the services should be recorded in detail. The block data involves in global and cell carriers.

Please refer to the setup flows in SMS.

11.2.3.1 GbcSmsBlkRsn (Global Carrier SMS Block Reason)
Description VE Block Number SE Block Number DSMP Block Number CIC Block Number CE Block Number CH Block Number Forward Power Block Number Reverse Power Block Number Frame Offset Block Number Carrier Frequency Status Failure Oriented Block DT FL FL FL FL FL FL FL FL FL FL Trigger The service process is failure due to the VE not available. The service process is failure due to the SE not available. The service process is failure due to the DSMP not available. The service process is failure due to the CIC not available. The service process is failure due to the CE not available. The service process is failure due to the CH not available. The service process is failure due to the Forward Power not available. The service process is failure due to the Reverse power not available. The service process is failure due to the Frame Offset not available. The service process is failure due to the Carrier status error. C/ S C C C C C C C C C C LC GC GC GC GC GC GC GC GC GC GC Res
Statistical item VEBlockNum SEBlockNum DSMPBlockNum CICBlockNum CEBlockNum CHBlockNum FPWBlockNum RPWBlockNum FOBlockNum CRErrBlockNum
Page 176
11.2.3.2
ClcSmsBlkRsn (Cell Carrier SMS Block Reason)

Description VE Block Number SE Block Number DSMP Block Number CIC Block Number CE Block Number CH Block Number Forward Power Block Number Reverse Power Block Number Frame Offset Block Number Carrier Frequency Status Failure Oriented Block DT IN IN IN IN IN IN IN IN IN IN Trigger The service process is failure due to the VE not available. The service process is failure due to the SE not available. The service process is failure due to the DSMP not available. The service process is failure due to the CIC not available. The service process is failure due to the CE not available. The service process is failure due to the CH not available. The service process is failure due to the Forward Power not available. The service process is failure due to the Reverse power not available. The service process is failure due to the Frame Offset not available. The service process is failure due to the Carrier status error. C/ S C C C C C C C C C C LC CC CC CC CC CC CC CC CC CC CC Res
Statistical item VEBlockNum SEBlockNum DSMPBlockNum CICBlockNum CEBlockNum CHBlockNum FPWBlockNum RPWBlockNum FOBlockNum CRErrBlockNum

None
11.3 Block (Data Service)

The block in data services is an important factor resulting in failure of data services setup. Therefore, the block data of the resources that may be used
in the services should be recorded in detail. The block data involves in global and cell carriers.

Please refer to the flows in data services, such as setup flow and handoff flow.

11.3.3.1 GbcDatBlkRsn (Global Carrier Data Block Reason)
Description DT Trigger The type will label that Data Call, Data Handoff Add and Data hard handoff add. The service process is failure due to the SE not available. The service process is failure due to the DSMP not available. The service process is failure due to the CIC not available. The service process is failure due to the CE not available. The service process is failure due to the CH not available. The service process is failure due to the Forward Power not available. The service process is failure due to the Reverse power not available. The service process is failure due to the Frame Offset not available. The service process is failure due to the Carrier status error. C/ S C C C C C C C C C C LC GC GC GC GC GC GC GC GC GC GC Res
Statistical item
ServiceType SEBlockNum DSMPBlockNum CICBlockNum CEBlockNum CHBlockNum FPWBlockNum RPWBlockNum FOBlockNum CRErrBlockNum
Service Type SE Block Number DSMP Block Number CIC Block Number CE Block Number CH Block Number Forward Power Block Number Reverse Power Block Number Frame Offset Block Number Carrier Frequency Status Failure Oriented Block
TI FL FL FL FL FL FL FL FL FL
Page 178
11.3.3.2
ClcDatBlkRsn (Cell Carrier Data Block Reason)

Description DT Trigger The type will label that Data Call, Data Handoff Add and Data hard Handoff Add. The service process is failure due to the SE not available. The service process is failure due to the DSMP not available. The service process is failure due to the CIC not available. The service process is failure due to the CE not available. The service process is failure due to the CH not available. The service process is failure due to the Forward Power not available. The service process is failure due to the Reverse power not available. The service process is failure due to the Frame Offset not available. The service process is failure due to the Carrier status error. C/ S C C C C C C C C C C LC Res
Statistical item
ServiceType SEBlockNum DSMPBlockNum CICBlockNum CEBlockNum CHBlockNum FPWBlockNum RPWBlockNum FOBlockNum CRErrBlockNum
Service Type SE Block Number DSMP Block Number CIC Block Number CE Block Number CH Block Number Forward Power Block Number Reverse Power Block Number Frame Offset Block Number Carrier Frequency Status Failure Oriented Block
TI IN IN IN IN IN IN IN IN IN
CC CC CC CC CC CC CC CC CC CC

None
Page 179
12 Power Overload
It records the changes of QOS due to power overload, including limiting new connections and releasing old connections. It involves the cell carrier.
12.2 Protocol Flow

None

12.3.1 ClcPwOL(Cell Carrier Power Overload)
Statistical item Description Power Over Release forward SCH Num Power Over Reject Connection Num New DT IN IN IN IN IN IN Trigger Add 1 to the counter every time when the forward SCH is released due to power overload. Add 1 to the counter every time when the new connection is rejected due to power overload. Add 1 to the counter every time when the Handoff Add operation is rejected due to power overload. Add 1 to the counter every time when the power increase operation is rejected due to power overload. Add 1 to the counter every time when the reverse SCH is released due to power overload. The total time of power overload C/ S C C C C C C LC Res
PowerOverRlsFSCHNum PowerOverRejectNewCo nNum PowerOverRejectHOAdd Num PowerOverRejectPowerI ncNum PowerOverRlsRSCHNum PowerOverTotalTime

CC CC CC CC CC CC
Page 180
Power Over Reject Handoff Add Num Power Over Reject Power Inc Num Power Over Release reverse SCH Num Power Over Total Time

None
13 CES Link Data

The statistics involved in CES link data focuses on the numbers for which the fingers of reception antennas are locked. By observing the finger lock status of antenna in a certain period, you can see if the antenna is balanced, which is very useful for network planning. Another content of CES link data statistics is the number of accesses, which reflects the demodulation of the information at air interface in an access environment.
13.2 Protocol Flow

None

13.3.1 CesLnkDat (CES Link Data)
Statistical item Description DT Trigger Add 1 to the counter every time when the finger of antenna 0 is locked. C/ S S LC Res
LockFingerA0
Antenna 0 Lock Finger Num
FL
CC
Page 181
LockFingerA1 AccSuccNum AccSuccNum
Antenna 1 Lock Finger Num Access Success Number Access Failure Number
FL FL FL
Add 1 to the counter every time when the finger of antenna 1 is locked. Add 1 to the counter every time when the information on the air interface is successfully demodulated. Add 1 to the counter every time when the information on the air interface fails to be demodulated.
S S S
CC CC CC

None
14 RFS Data
It records the transmitter power, the attenuation values of TX and RX, the instantaneous RSSI values of RX0 and RX1 links.
14.2
None
Protocol Flow

14.3.1 ClcRfsInfo(Cell Carrier Radio Frequency Information)
Statistical item Description DT Trigger C/ S LC Res
Page 182
MaxTransmitPower MinTransmitPower AvgTransmitPower RSSI_M RSSI_D
The Max value of Transmit Power The Max value of Transmit Power The Max value of Transmit Power Main RSSI Diversity RSSI
IN IN IN IN IN
The Maximum value of Transmit Power The Minimum value of Transmit Power The Average value of Transmit Power Main RSSI Diversity RSSI
S S S S S
CC CC CC CC CC
14.4
None
Calculation Method
15 Failure Causes
In current RLSA services, the system not only captures all the failures, but also records the failure information in detail, such as the location, PN and CI of the failed cell. The OMC sorts the failures by service type, and list them in the order of their numbers of failure The service failure types include: Registration failure Call failure (Voice) Call failure (SMS) Call failure (Data) Call drop (Voice) Call drop (SMS)
Call drop (Data) Handoff failure (Voice) Handoff failure (Data) Call failure (Concurrent Voice Services) Call failure (Concurrent Data Services) Concurrent release failure Hard Handoff failure Forward SCH assignment failure Reverse SCH assignment failure Forward SCH release failure Reverse SCH release failure
15.2 Protocol Flow

None
15.3 Table Detail

Statistical item ServiceType ServiceSubType Description Service Type Service Sub Type DT IN TI Trigger The Service type is on the list above 15.1 As for some Service, it can be divided with sub type, such as call service, is be divided with common call, assignment softer handoff call. Because the service process can be successful that will pass through some essential state, so we will distinguish with by the service state. When service fail had happened, we will record the MSC ID C/ S S S LC CC CC Res
ServiceState MSCID
Service State MSC ID
TI IN
S S
CC CC
Page 184
CI PN ErrorReason Number
CI PN Error Reason Number
IN IN IN IN
When service fail had happened, we will record the Cell CI When service fail had happened, we will record the Pilot PN When service fail had happened, we will record the Error Reason ID. When service fail had happened we will accumulative the numbers of this error reason that induce the process fail.
S S S S
CC CC CC CC

None
16 Adjacent Cells
It records the handoff of a source cell with target cells. The target cell may be one of the following three cases: It is an adjacent cell of the source cell It is a non-adjacent cell of the source cell (but it is an adjacent cell of the cells around the source one) It is an invalid target cell
16.2 Protocol Flow

Each time when a handoff finishes, the set of source cells before the handoff, the newly-added set of target cells, as well as whether the handoff is successful or not, will be reported. Based on the information, the OMC will reconfigure the neighbor list of the source cells.
Page 185
16.3 Table Detail

Statistical item Description DT IN TI IN TI TI IN TI IN TI TI IN Trigger When handoff had happened, we will record the source MSC ID. If not retain it, it will be fill with an invalid value When handoff had happened, we will record the source BSS ID. If not retain it, it will be fill with an invalid value When handoff had happened, we will record the source BTS ID. If not retain it, it will be fill with an invalid value C/ S S S S LC Res
SourceMscId SourceBssId SourceBtsId SourceCellId SourceCarrierId TargetMscId TargetBssId TargetBtsId TargetCellId TargetCarrierId TargetCI
Source MSC ID Source BSS ID Source BTS ID Source CELL ID Source Carrier ID Target MSC ID Target BSS ID Target BTS ID Target CELL ID Target Carrier ID Target CI
CC CC CC CC CC CC CC CC CC CC CC
When handoff had happened, we will record the source CELL S ID. If not retain it, it will be fill with an invalid value When handoff had happened, we will record the Target Carrier ID. If not retain it, it will be fill with a invalid value When handoff had happened, we will record the Target MSC ID. If not retain it, it will be fill with an invalid value When handoff had happened, we will record the Target BSS ID. If not retain it, it will be fill with a invalid value When handoff had happened, we will record the Target BTS ID. If not retain it, it will be fill with an invalid value S S S S
When handoff had happened, we will record the Target CELL S ID. If not retain it, it will be fill with an invalid value When handoff had happened, we will record the Target Carrier ID. If not retain it, it will be fill with a invalid value S
When handoff had happened, we will record the Target CELL S CI. If not retain it, it will be fill with an invalid value.
Page 186
TargetPN HandoffType ReportType HoSNum HoInvPNFNum HoBlockFNum HoOtherFNum
Target PN Handoff Type Report Type Handoff Success Number Handoff Number Invalid PN Fail
IN IN TI IN IN IN IN
When handoff had happened, we will record the Target Pilot PN. If not retain it, it will be fill with an invalid value. When handoff had happened, we will record the Handoff Type. If not retain it, it will be fill with an invalid value. When handoff had happened, we will record the information about which value is invalid above the fields. When handoff had happened, and the result is success, it will be increment. When handoff had happened, and the result is failure, the failure reason is invalid Pilot PN, then the value be increment. When handoff had happened, the result is failure; the failure reason is not available resource. then the value be increment. When handoff had happened, the result is failure, the failure due to the others reason. Then the value is increment.
S S S S S S S
CC CC CC CC CC CC CC
Handoff Block Fail Number Handoff Other Fail Number

Adjacent Cell: Search all the target cells configured for the source cell, and count or calculate the times of successful/failed handoffs and the handoff success rate of each target cell. 2. Non-adjacent Cell: Count or calculate the times of successful/failed handoffs and the handoff success rate of those target cells that are not the adjacent cells of the source cell. 3. Invalid Target Cell: Count the number of the target cells whose information is incomplete. Once a source cell is selected, the handoff between this cell and all of its target cells can be enquired. Comparing these target cells with the adjacent cells of all source cells, you can take further actions accordingly. For those target cells who are the adjacent cells of the source cell and with high handoff success rate, no optimization is required for them. For those target cells who are not adjacent cells of the source cell (but they are adjacent cells of other active cells during handoff), if their handoffs with the source cell are frequent and of high success rate, you need to configure them as the adjacent cells of the source cell.
1.
For those adjacent cells of the source one where no handoff occurs or the times of handoffs is few, it means the configuration of these adjacent cells is not reasonable and you need to remove them from the neighbor list of the source cell.
Page 188

3G 1X Performance Management Indexes and Their Calculation

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3G 1X Performance Management Indexes and Their Calculation

Uploaded by

Copyright:

Available Formats

3G RLSA Performance Management Indexes and Their Calculation

Standardized by: Approved by:

3G RLSA Performance Management Indexes and Their Calculation 1.

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

3G RLSA Performance Management Indexes and Their Calculation 1.

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

CC: Cell Carrier

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

2.2 Protocol Flow

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

2.3 Counter Table Detail

Power Up Request Num

Power Up Success Num

Power Down Request Num

Power Down Success Num

Timer Based Request Num

Timer Based Success Num

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

Distance Based Request Num

Distance Based Success Num

Zone Based Request Num

Zone Based Success Num

Parameter Change Request Num Parameter Change Success Num

Ordered Request Num

Ordered Success Num

User Zone Request Num

ZTE Confidential Proprietary

3G RLSA Performance Management Indexes and Their Calculation 1.

User Zone Success Num

2.3.2 ClcReg (Cell Carrier Registration)

Power Up Success Num

Power Down Request Num

Power Down Success Num

Timer Based Request Num

Timer Based Success Num

ZTE Confidential Proprietary