03-Traffic Statistic Items

Traffic Statistic ManualM900/M1800 Base Station Controller

Error: Reference source not foundError:Reference source not found

Chapter 3 Traffic Statistic Items

3.1 BSC measurement function

3.1.1 General

The statistic items in BSC Measurement Function are used to measure the traffic statistic of all cells in the BSC. These items are listed in Table 3-1

The statistic items in BSC Measurement Function can be divided into following classifications:

Statistics of times that MSC rejects MS’s service request, including the statistics according to different rejection causes.

The status of circuit service and packet service paging being transmitted and implemented, including the measurement at A (Pb) interface and Abis interface.

Measurement of circuit service and packet service CCCH overload. The status of circuit service and packet service immediate assignment request

and the implementation. Number of TCH seizure requests, the successful TCH seizures, TCH call

drops, TCH seizure requests for very early assignment, successful TCH seizures for very early assignment, TCH call drops for very early assignment, SDCCH seizure requests, successful SDCCH seizures, and SDCCH call drops.

Dedicated measurement for assignment procedure, including the number of unsuccessful assignments due to various causes.

Measurement of TCH MR (measurement report), and independent measurement of very early TCH assignment MR.

Intra-BSC handover request and the implementation of the request, the measurement of incoming BSC handover request and the implementation (including the measurement of the unsuccessful incoming BSC handovers due to various causes), outgoing BSC handover request and the implementation, and the measurement of the handover due to various causes.

The measurement of analytical items such as BSC handover success rate, call drop rate, and traffic volume.

1



Table 3-1 Statistic items in BSC Measurement Function

No. Item name

1 Sum of CM service rejections

2 CM service rejections due to congestion

3 CM service rejections due to network failure

4 CM service rejections due to illegal MS

5 CM service rejections due to other causes

6 Average interval of random accesses

7 Average interval of random accesses for packet call

8 Received circuit paging messages from MSC

9 Circuit paging commands to BTS

10 Successful circuit pagings of Abis interface

11 Circuit paging PCH overloads of Abis interface

12 Circuit paging RACH overloads of Abis interface

13 Packet paging commands to BTS

14 Packet paging PCH overloads of Abis interface

15 Immediate assignment requests

16 Packet immediate assignment request

17 Immediate assignment transmissions

18 Successful packet immediate assignment

19 Successful connections

20 TCH call drop connected

21 Attempted TCH seizures (all)

22 Successful TCH seizures

23 TCH call drop

24 Successful TCH seizures for very early assignment

25 TCH drop for very early assignment

26 Attempted SDCCH seizures (all)

27 Successful SDCCH seizures

28 Attempted SDCCH seizures meeting SDCCH overflow

29 SDCCH call drop

30 Assignment requests

31 Unsuccessful assignments

32 Unsuccessful assignments (equipment failure)

33 Unsuccessful assignments (requested terrestrial resource unavailable)

34 Unsuccessful assignments (terrestrial circuit already allocated)

35 Unsuccessful assignments (invalid message contents)

36 Unsuccessful assignments (radio interface failure, reversion to previous channel)

37 Unsuccessful assignments (no radio resource available)

2



38 Unsuccessful assignments (other causes)

39 Unsuccessful channel activation during assignment (NACK)

40 Channel activation timeout during assignment

41 Sum of TCH measurement reports (excluding very early assignment)

42 Sum of 1800 cell TCH measurement reports(excluding very early assignment)

43 Sum of configured TRX in the BSC

44 Sum of available TRX in the BSC

45 Attempted intracell handovers

46 Successful intracell handovers

47 Unsuccessful intracell handovers

48 Attempted intercell handovers

49 Intercell handovers

50 Attempted intercell handovers (9001800)

51 Attempted intercell handovers (1800→900)

52 Successful intercell handovers

53 Successful intercell handovers (9001800)

54 Successful intercell handovers (1800900)

55 Intra BSC handovers

56 Attempted incoming BSC handovers

57 Attempted incoming BSC handovers (9001800)

58 Attempted incoming BSC handovers (1800900)

59 Attempted incoming BSC handovers (to 900)

60 Attempted incoming BSC handovers (to 1800)

61 Successful incoming BSC handovers

62 Successful incoming BSC handovers (9001800)

63 Successful incoming BSC handovers (1800900)

64 Successful incoming BSC handovers (to 900)

65 Successful incoming BSC handovers (to 1800)

66 Unsuccessful incoming BSC handovers

67 Unsuccessful incoming BSC handovers (equipment failure

68 Unsuccessful incoming BSC handovers (requested terrestrial resource unavailable)

69 Unsuccessful incoming BSC handovers (Terrestrial Circuit Already Allocated)

70 Unsuccessful incoming BSC handovers (Invalid Message Contents)

71 Unsuccessful incoming BSC handovers (no radio resource available)

72 Unsuccessful incoming BSC handovers (other causes)

73 Unsuccessful channel activation in incoming BSC handovers (NACK)

74 Channel activation timeout in incoming BSC handovers

75 Incoming BSC handovers

76 Attempted outgoing BSC handovers

77 Attempted outgoing BSC handovers (from 900)

3



78 Attempted outgoing BSC handovers (from 1800)

79 Attempted outgoing BSC handovers (9001800)

80 Attempted outgoing BSC handovers (1800900)

81 Successful outgoing BSC handovers

82 Successful outgoing BSC handovers (from 900)

83 Successful outgoing BSC handovers (from 1800)

84 Successful outgoing BSC handovers (9001800)

85 Successful outgoing BSC handovers (1800900)

86 Outgoing BSC handovers

87 Unsuccessful outgoing BSC handovers with successful reversion

88 Unsuccessful outgoing BSC handovers with unsuccessful reversion

89 Attempted handovers for uplink quality

90 Attempted handovers for downlink quality

91 Attempted handovers for uplink strength

92 Attempted handovers for downlink strength

93 Attempted handovers for timing advance

94 Attempted handovers for better cell

95 Attempted handovers for traffic load

96 Attempted handovers for rapid rxlevel drop

97 Attempted handovers for response to MSC invocation

98 Attempted handovers for O&M intervention

99 Attempted handovers from underlaid subcell to overlaid subcell

100 Attempted handovers from overlaid subcell to underlaid subcell

101 Attempted handovers for directed retry

102 Attempted handovers for other causes

103 Extended cell attempted handovers for minimum timing advance

104 Successful handovers for uplink quality

105 Successful handovers for downlink quality

106 Successful handovers for uplink strength

107 Successful handovers for downlink strength

108 Successful handovers for timing advance

109 Successful handovers for better cell

110 Successful handovers for traffic load

111 Successful handovers for rapid rxlevel drop

112 Successful handovers for response to MSC invocation

113 Successful handovers for O&M intervention

114 Successful handovers from underlaid subcell to overlaid subcell

115 Successful handovers from overlaid subcell to underlaid subcell

116 Successful handovers for directed retry

117 Successful handovers for other causes

4



118 Extended cell successful handovers (minimum timing advance

119 Successful BSC inter-layer handovers (upper to lower)

120 Successful BSC inter-layer handovers (lower to upper)

121 Unsuccessful BSC internal handovers with successful reversion

122 Unsuccessful BSC internal handovers with unsuccessful reversion

123Sum of Full rate TCH measurement reports (excluding very early assignment)

124Sum of Half rate TCH measurement reports (excluding very early assignment)

125Sum of 1800 cell Full rate TCH measurement reports (excluding very early assignment)

126Sum of 1800 cell Half rate TCH measurement reports (excluding very early assignment)

127Assignment requests with signalling channel

128Successful assignments with signalling channel

129 Circuit paging (A-interface) success rate

130 Ratio of paging channel overloads (%)

131 Rate of sending immediate assignment command

132 Intracell handover success rate

133 Intercell handover success rate

134 Incoming BSC handover success rate

135 Outgoing BSC handover success rate

136 Ratio of intraBSC interband handover to total intraBSC handover

137 Ratio of interBSC interband handover to total interBSC handover

138 Dual-band handover success rate

139 TCH call drop rate (%)

140 Traffic volume (excluding very early assignment) (Erl)

141 Traffic volume of 1800 cell (excluding very early assignment) (Erl)

142 Intra BSC radio handover success rate

143 Incoming BSC radio handover success rate

144 Outgoing BSC radio handover success rate

145 Percentage of TRX in good condition (%)

146 SDCCH call drop rate (%)

147 SDCCH congestion rate (SDCCH overflow) (%)

148Full rate traffic volume (excluding very early assignment) (ERL)

149Half rate traffic volume (excluding very early assignment) (ERL)

150Full rate traffic volume of 1800 cell (excluding very early assignment) (ERL)

151Half rate traffic volume of 1800 cell (excluding very early assignment) (ERL)

Many statistic items in BSC Measurement Function have the corresponding items of cell level in Cell Measurement Function.

For the traffic status of the specified cell, you can register the related items in Cell Measurement Function.

5



It is recommended that all statistic items in BSC Measurement Function should be registered through 3 tasks after the BSC kickoff because these items are important items for measuring network performance. It is recommended that the templates should be used to register and the traffic statistic cycle should be 60 minutes.

Note:

1) A statistic task can contains at most 60 items. Therefore, 3 tasks are needed to register all items of

BSC Measurement Function.

2) Three default templates for BSC Measurement Function are provided.

The statistic object of BSC Measurement Function is the whole BSC. So there is no object option on the object definition interface in OMC traffic statistics console.

3.1.2 Statistic Items

I. Sum of CM service rejections

Description: in the MS originating immediate assignment procedure, first MS and BSS establish RR connection. Then MS sends the detailed MM service request on MM layer through CM SERVICE REQUEST to network side. This message can carry the following MM service types: Mobile originating call establishment, packet mode connection establishment, emergency call establishment, short message service and supplementary service activation. BSS transparently transmits this message to NSS. If NSS does not support or does not respond to this service request for some reason, MSC sends CM SERVICE REJECT message to the MS. BSC transparently transmits this message. See GSM 0408 protocol.

Measurement point: as shown in Chapter 3 Figure 3-2 A1, when BSC receives the DTAP message of CM SERVICE REJECT from MSC, this item is measured regardless the rejection cause carried in the message.

Formula: none

6



MS BTS BSC MSC/VLR

1.L2-SABM2.ESTABLISH INDICATION

A1 B1

C1

3.CM SERVICE REQUEST

4.CM SERVICE REJECT

D1 E1

A1: Sum of CM service rejections

B1: Sum of CM service rejections (congestion)

C1: Sum of CM service rejections (network failure)

D1: Sum of CM service rejections (illegal MS)

E1: Sum of CM service rejections (other reasons)

Figure 3-2 CM SERVICE REQUEST rejection process

II. CM service rejections due to congestion

Description: if NSS cannot normally respond to a CM SERVICE REQUEST message due to the congestion after receiving this message from MS MM layer, NSS responds MS a CM SERVICE REJECT message in which the rejection cause is congestion. See GSM 0408 protocol.

Measurement point: as shown in the B1 in Chapter 3 Figure 3-2 , this item is measured when BSC receives the DTAP message of CM SERVICE REJECT from MSC and the rejection cause carried in this message is congestion.

Formula: none

III. CM service rejections due to network failure

Description: if NSS cannot normally respond to a CM SERVICE REQUEST due to network failure after receiving this message from MS MM layer, NSS responds MS a CM SERVICE REJECT message in which the rejection cause is network failure. See GSM 0408 protocol.

Measurement point: as shown in the C1 in Chapter 3 Figure 3-2 , BSC measures this item when BSC receives the DTAP message of CM SERVICE REJECT from MSC, the rejection cause carried in this message is network failure.

Formula: none

7



IV. CM service rejections due to illegal MS

Description: if NSS cannot normally respond to a CM SERVICE REQUEST due to being unable to identify the MS after receiving this message from MS MM layer, NSS responds MS a CM SERVICE REJECT message in which the rejection cause is illegal MS. See GSM 0408 protocol.

Measurement point: as shown in the D1 in Chapter 3 Figure 3-2 , This item is measured when BSC receives the DTAP message of CM SERVICE REJECT from MSC with the rejection cause carried in this message being illegal MS.

Formula: none

V. CM service rejections due to other causes

Description: if NSS cannot normally respond to a CM SERVICE REQUEST due to the reasons other than above mentioned ones after receiving this message from MS MM layer, NSS responds MS a CM SERVICE REJECT message. See GSM 0408 protocol.

Measurement point: as shown in the E1 in Chapter 3 Figure 3-2 , This item is measured when BSC receives the DTAP message of CM SERVICE REJECT from MSC with the rejection cause carried in this message being other than the above mentioned ones.

Formula: none

VI. Average interval of random accesses

Description: This item describes the access frequency of calling MS. The RR entity of the mobile station initiates the immediate assignment procedure by scheduling the sending of CHANNEL REQUEST on the RACH to BTS, then BTS sends CHANNEL REQUIRED to BSC. See GSM 0408.

Measurement point: BSC countes 1 to the number of channel accesses every time it receives CHANNEL REQUIRED message from BTS, and average inter arrival time = measurement period (second)/sum of channel access times within the measurement period.

Formula: Measurement period (second)/sum of channel access times within the measurement period

Unit: Second

VII. Average interval of random accesses for packet call

Description: This item describes the frequency of PS access frequency with the access cause being packet call. The RR entity of the mobile station initiates the immediate channel assignment procedure by periodically sending of CHANNEL REQUEST on the RACH to BTS, then BTS sends CHANNEL REQUIRED to BSC. See GSM 0408 protocol.

8



Measurement point: BSC countes 1 to the number of channel accesses every time BSC receives CHANNEL REQUIRED message from BTS containing access cause "packet call", and average inter of packet arrival time = measurement period (second)/sum of channel packet access times in the measurement period.

Formula: measurement period (second)/sum of channel packet access times within the measurement period

Unit: Second

VIII. Received circuit paging messages from MSC

Description: when an MS under the BSC is called for circuit service, MSC sends the circuit service PAGING message to page the called MS from A interface (or from Gb interface through SGSN). This item is used to measure the sum of the received PAGING messages in the statistic cycle. The repeated PAGING message is measured repeatedly. See GSM 0808 protocol.

Measurement point: as shown in Figure 3-3 A1 and A2, this item is measured every time BSC receives the circuit PAGING messages from A interface or Pb interface (Huawei BSC-PCU interface).

Formula: none

3. PAGING REQUEST 2. PAGING COMMAND

MS BTS BSC PCU SGSN MSC/VLR

11'. PAGING 12'. PAGING REQUEST 13'. PAGING

REQUEST

A2

4.CHANNEL REQUEST 5.CHANNEL REQUIRED

6.CHANNEL ACTIVATION

7. CHANNEL ACKTIVATION ACKNOWLEDGE

8.IMMEDIATE ASSIGN CMMAND 9. IMMEDIATE

ASSIGNMENT 10. PAGING RESPONSE

11. EST IND(PAGING RESPONSE)

C1

A1

B1

1. PAGING

A1: Received circuit paging messages from MSC

A2: Received circuit paging messages from MSC through GS interface

B1: Circuit paging commands to BTS

C1: Successful circuit paging of Abis interface

Figure 3-3 Circuit paging process

9



IX. Circuit paging commands to BTS

Description: in the case an MS under the BSC is called for circuit service, BSC sends PAGING COMMAND to the corresponding cell according to the cell identification discriminator after receiving the circuit PAGING message from MSC or PCU. This item is used to measure the paging delivery times at Abis. See GSM 0858 and 0408 protocol.

Measurement point: as shown in the Figure 3-3 B1, this item is measured in every cell every time BSC sends PAGING COMMAND message to the corresponding cell.

Formula: none

X. Successful circuit pagings of Abis interface

Description: after a called MS receives PAGING REQUEST message from network side, the paging response process is implemented. This MS reports ESTABLISH INDICATION, with the cause value PAGING RESPONSE, to MSC if it successfully seizes signaling channel. See GSM 0408 protocol.

Measurement point: as shown in Figure 3-3 C1, this item is measured every time BSC receives PAGING RESPONSE message from MS.

Formula: none

XI. Circuit paging PCH overloads of Abis interface

Description: BTS reports CCCH LOAD INDICATION message to BSC when detecting the overload of PCH, then BSC measures this item and sends OVERLOAD message to MSC simultaneously. See GSM 0858 protocol.

Measurement point: as shown in Figure 3-4 A1, this item is measured when BSC receives CCCH LOAD INDICATION message from BTS with the cause value carried in the message being PCH overload.

Formula: none

BTS BSC MSC/VLR

CCCH LOAD INDICATION

A1 OVERLOADB1

A1:Circuit paging PCH overloads of Abis interface

B1: Circuit paging RACH overloads of Abis interface

Figure 3-4 CCCH overload process

10



XII. Circuit paging RACH overloads of Abis interface

Description: When detecting RACH overload, BTS reports CCCH LOAD INDICATION to BSC, then BSC measures this item and implements the internal flow control.

Measurement point: as shown in Figure 3-4 B1, this item is measured when BSC receives CCCH LOAD INDICATION message from BTS with the cause value carried in the message being RACH overload.

Formula: none

XIII. Packet paging commands to BTS

Description: in the case an MS under the BSC is called for packet service, SGSN sends PAGING REQUEST message to PCU to page this MS. PCU processes this message and then sends PACKET PAGING message to BSC. According to the cell identification discriminator carried in the PACKET PAGING message, BSC sends PACKET PAGING REQUEST message to the corresponding cell. See GSM 0408, 0460, 0360 protocols.

Measurement point: as shown in Figure 3-5 A1, this item is measured in every cell when BSC sends a PACKET PAGING REQUEST message to the corresponding cell.

Formula: none

PACKET PAGING REQUEST

MS BSC+BTS PCU SGSN

PAGING REQUEST

PACKET PAGING

A1

A1: Packet paging commands to BTS

Figure 3-5 Packet paging process

XIV. Packet paging PCH overloads of Abis interface

Description: when detecting the overload of PCH seized by packet service (See GPRS Related Measurement Function for packet combined channel relation), BTS reports Packet CCCH Load Indication message to BSC. BSC forwards this message to PCU and PCU initiates packet paging process.

Measurement point: BSC measures this item upon reception of Packet CCCH Load Indication message from BTS.

Formula: none

11



XV. Immediate assignment requests

Description: when an MS wants to obtain network service due to some reason, this MS sends CHANNEL REQUEST message to BTS on RACH to request Dedicated Control Channel, then BTS sends CHANNEL REQUIRED to BSC. This item measures all the access cause value of CHANNEL REQUIRED.

Measurement point: As shown in Figure 3-6 A1, this item is measured when BSC receives CHANNEL REQUIRED message from BTS.

Formula: none

MS BTS BSC

1.CHANNEL REQUEST

2.CHANNEL REQUIRED

3.CHANNEL ACTIVATION

4. CHANNEL ACKTIVATION ACKNOWLEDGE

5.IMMEDIATE ASSIGN CMMAND

A1

B1

A1: Packet immediate assignment request

B1: Immediate assignment transmissions

Figure 3-6 immediate assignment transmission process

XVI. Packet immediate assignment request

Description: to request channel for packet service, MS sends CHANNEL REQUEST message to BTS on RACH and the access cause carried in the message is Packet Call, then BTS sends CHANNEL REQUIRED to BSC. Upon reception of this message, BSC forwards the request to PCU. See GSM 0408 and 0406 protocol.

Measurement point: as shown in Figure 3-7 A1, BSC measures this item when BSC receives CHANNEL REQUIRED message from BTS and if the access cause carried in the message is Packet Call.

Formula: none

12



MS BTS BSC

CHANNEL REQUEST(PACKET CALL)

CHANNEL REQUIRED

IMMEDIATE ASSIGN CMMAND

A1

HUAWEI PCU

Packet Channel Request

Packet Immediate Assign Command

B1

A1: Packet immediate assignment request

B1: Successful packet immediate assignment

Figure 3-7 Packet immediate channel assignment procedure

XVII. Immediate assignment transmissions

Description: in immediate assignment procedure, upon reception of the CHANNEL REQUIRED message reported from BTS, BSC allocates and activates a signaling channel for the MS. If BSC receives the CHANNEL ACTIVATION ACKNOWLEDGE message from BTS indicating that the channel is ready, BSC sends an IMMEDIATE ASSIGNMENT COMMAND message informing the MS to access the dedicated signaling channel, which can be either SDCCH or TCH. This item includes all access cause value of CHANNEL REQUIRED.

Measurement point: As shown in Figure 3-6 B1, this item is measured when BSC sends the IMMEDIATE ASSIGN COMMAND message to MS.

Formula: none

XVIII. Successful packet immediate assignment

Description: if the cause value carried in the CHANNEL REQUEST message sent by MS on RACH is packet call, BSC forwards this message to PCU after receiving the message. PCU initiates PDCH assignment procedure after receiving the forwarded message and sends a Packet Immediate Assign Command message (Huawei Pb interface) to BSC, then BSC converts this message into IMMEDIATE ASSIGN COMMAND of Abis interface to BTS and BTS sends this message to MS. This process is described in Figure 3-7 . The measurement point of this item is indicated in B1. See GSM 0408, 0460 protocol.

Measurement point: upon reception of the Packet Immediate Assign Command message from PCU, BSC measures this item and sends IMMEDIATE ASSIGN COMMAND to BTS.

Formula: none

13



XIX. Successful connections

Description: the successful circuit service connection time in immediate assignment procedure, if CC connection is to be established after MM connection establishment of MOC, MOC sends a SETUP message to the network to request the call setting up; then MSC responds a CALL PROCESSING message to MOC and pages MTC simultaneously. After the MM connection establishment between MSC and MTC, MSC sends a SETUP message to MTC to request the establishment of CC connection. If permitting the call establishment, MTC responds a CALL CONFIRM message to MSC and MSC forwards this message to MOC. Having seized the traffic channel, MTC sends an ALERTING message to MSC and MSC forwards this message to MOC. After that, MTC sends a CONNECT message to MOC after its off-hook, MOC responds the CONNECT ACKNOWLEDGE message. The call is set up and the MOC and MTC enter the conversation state. See GSM 0408, 0858, 0808 protocols for detailed full process of call connection establishment between the calling MS and the called MS.

Note:

This statistic item includes the "directed retry" in the channel assignment procedure. If the directed

retry takes place in the channel assignment procedure, this item is measured in the cell that actually

allocates channel, that is destination cell of directed retry.

Measurement point: As shown in Chapter 3 Figure 3-8 A’, A’’, this item is measured when BSC receives the DTAP type of CC message CONNECT or CONNECT ACKNOWLEDGE. If MOC and MTC share the same BSC, both MOC and MTC are measured.

Formula: none

14



Ori-MS BSS1 MSC

A1"

1.CM SERVICE REQUEST

BSS2 Termi-MS

3.CALL CONFIRMED

2.SETUP

4.ALARTING

4.CONNECT

5.CONNECT ACKNOWLEDGE A1'

Note:A1' count in BSS1A1" count in BSS2

A’, A’’: Successful connections

Figure 3-8 CC connection establishment process

XX. TCH call drop connected

Description: this item measures the number of call drop when MS is normally during the conversation on radio channel. In the assignment procedure and handover procedure, the establishment of a conversation is indicated by: in assignment procedure BSC receives the CONNECT message and the CONNECT ACKNOWLEDGE message from CC layer; in the incoming BSC handover procedure the target cell sends HANOVER COMPLETE message to MSC; successful intra BSC handover: the target cell sends HANDOVER PERFORMED message to MSC when it detects the access of the MS. If the call drop occurs after the above stages, it will be regarded as call drop connected.

Measurement point:1) Upon BSC’s reception of ERROR INDICATION message from BTS due to

an abnormal connection in a radio link layer. See GSM 0508 protocol.2) During MS conversation, BTS detects a fault in radio link layer or

hardware; it sends a CONNECTION FAILURE INDICATION message to BSC informing the BSC this failure. See GSM 0508 protocol.

3) The timer expires when BSC waiting for the CLEAR COMMAND message from MSC during outgoing BSC handover.

4) In Intra-BSC handover procedure, the target cell sends Inter Clear Request to the source cell when the timer for the target cell to wait for HANDOVER COMPLETE from MS expires, in this case, this item is measured in the source cell.

15



5) In Intra-BSC handover procedure, the source cell, excluding the source cell for directed retry, measures the item when the timer for the source cell to wait for Inter Clear Request with cause value HANDOVER COMPLETE from the target cell expires.

6) In Intra-BSC handover procedure, when the target cell AM/CM net-drive fails (due to timeout or negative acknowledgement), the target cell sends Inter Clear Request to source cell, in this case, this item is measured in the source cell.

7) In the case that MS reverses to the original channel after intra BSC handover fails, the source cell first releases the terrestrial connection but the AM/CM re-net-drive fails (due to timeout or negative acknowledgement). In this case this item is measured in the source cell.

8) The resource of the lower_priority call will be preempted by the higher_priority call if MSC and BSC both supports preemption, which will cause call drop.

9) This item is measured when the RSL link of the TRX that the call is using disconnects, which will cause call drop.

Note:

AM/CM net-drive: In assignment procedure or handover procedure, BSC establishes the terrestrial

connection in A-interface for a MS after it has successfully allocated radio channel.

Formula: none

XXI. Attempted TCH seizures (all)

Description: in the following procedures, if the requested channel type is SDCCH, this item shall be measured after BSC receives a relevant request.1) In immediate assignment procedure, MS sends CHANNEL REQUEST

to BTS to request radio channel.2) In assignment procedure and incoming BSC handover procedure, MSC

requests radio resource by sending ASSIGNMENT REQUEST or HANDOVER REQUEST to BSC.

3) In intra BSC handover, BSC itself requests a new channel for call.

Note:

SDCCH handover:

Handover happens on SDCCH.

16



Channel reallocation:

In the immediate assignment procedure, Huawei BSC supports channel reallocation. BSC initiates

radio channel allocation when it receives CHANNEL REQUIRED message from BTS. BSC allocates a

TCH if the access cause value of CHANNEL REQUIRED is "emergency call "or "call re-

establishment" and BSC supports very early assignment TCH. Otherwise, BSC allocates a SDCCH.

BSC reallocates radio channel automatically based on "GSM 0408" if BSC supports very early

assignment of TCH and channel allocation fails due to no radio resource available. In other words

BSC allocates a TCH automatically if SDCCH allocation fails and the access cause is not "location

update", and similarly, BSC allocates a SDCCH automatically if TCH allocation fails. So, to one

CHANNEL REQUEST message, BSC measures both SDCCH and TCH seizure times.

Very early assignment TCH:

If BSC allocates a TCH as a signaling channel in immediate assignment procedure, instead of the

traffic channel allocation procedure, the Mode Modify procedure can be implemented in the

assignment procedure.

Assignment SDCCH:

In the assignment procedure, MSC sends ASSIGNMENT REQUEST message to BSC to request for

a radio channel. BSC responses ASSIGNMENT COMPLETE message to MSC directly if the channel

type in the ASSIGNMENT REQUEST is SDCCH. In this case, BSC implements signaling or short

message transmission on the channel already allocated. BSC does not measure either "attempted

SDCCH seizures" or "successful SDCCH seizures" for it does not allocate a new channel. Instead, it

measures the times of "assignment requests" and "assignment success" after successfully sending

ASSIGNMENT COMPLETE message.

Discard CHANNLE REQUIRED in internal flow:

In the immediate assignment procedure, BSC receives CHANNEL REQUIRED messages from BTS.

BSC discards these messages if the system is too busy to respond. In this case, "attempted TCH" or

"SDCCH seizures" will be measured but "successful or unsuccessful channel seizures" will not be

measured.

Measurement point: the measurement point of this item is described in Figure3-9 , Figure 3-10 , Figure 3-11 and Figure 3-12 TCH-ATT-BSC1--TCH-ATT-BSC4.1) In immediate assignment procedure, this item is measured when BSC

receives CHANNEL REQUIRED message from BTS and the requested channel type is TCH.

2) In assignment procedure, this item is measured when BSC receives ASSIGNMENT REQUEST message from MSC and the requested channel type is TCH.

3) In intra BSC handover, the source cell sends Intercell Handover Request message (Huawei defined message) to the target cell; if the handover is taken place on TCH, this item is measured when the target

17



cell receives this message. The intra BSC handover includes the case that handover is taken place in the same cell with the originating and the target cell being the same one.

4) This item is measured when Huawei BSC receives the HANDOVER REQUEST message from other BSC and the handover is taken place on TCH.

Formula: none

MS BTS BSC

CHANNEL REQUEST CHANNEL REQUIRED

CHANNEL ACTIVATION

CHANNEL ACKTIVATION ACKNOWLEDGE

TCH-ATT-BSC1

TCH -ATT-BSC1: Attempted TCH seizures (all)

Figure 3-9 Immediate assignment procedure-channel seizure procedure

18



MS BTS BSC

.ASSIGN CMMAND

MSC

ASSIGNMENT REQUEST

SABM

UAESTABLISH INDICATION

ASSIGNMENT COMPLETE

(directly retry)HANDOVER REQIRED

(directly retry)HANDOVER REQUEST ACK

CHANNEL ACTICATION

CHANNEL ACTIVATION ACK

QUEUEING INDICATIONTCH-ATT-BSC 2


Figure 3-10 Assignment procedure-channel seizure procedure

MS BTS' BSC Ori-Cell

HANDOVER ACCESS

UA

Intercell Handover Request

BSC Des-Cell BTS''MR

Handover algorithm

HANDOVER COMMAND

Intercell Handover Response

HANDOVER DETECT

CH ACTCH ACT ACK

HANDOVER COMPLETE

Inter Clear Request (Handover Success)

TCH-ATT-BSC3

SABM


Figure 3-11 Intra-BSC handover channel seizure procedure

19



MS Other BSC

HANDOVER ACCESS

UA

HANDOVER REQUIRED

HUAWEI BSC HUAWEI BTS

HANDOVER COMMAND

HANDOVER REQUEST ACK

HANDOVER DETECT

CH ACTCH ACT ACK

HANDOVER COMPLETE

TCH-ATT-BSC4

MSC

QUEUEING INDICATION

HANDOVER REQUEST

SABM


Figure 3-12 Incoming BSC handover channel seizure procedure

XXII. Successful TCH seizures

Description: in very early assignment procedure, assignment procedure, and handover procedure, BSC measures this item when MS successfully seizes the allocated TCH. The successful directed retry is also measured as successful TCH seizure: If there is no available channel after ASSIGNMENT REQUEST message from MSC is sent to the cell of the BSC and the system supports directed retry, then BSC initiates outgoing cell handover according to the information about adjacent cell in MS’s MR.

Measurement point: this item is measured if TCH is successfully seized by the following processes: 1) Upon BSC’s reception of CHANNEL ACTIVATION ACKNOWLEDGE

message from BTS in very early assignment TCH process.2) In the case the target cell of directed retry is located in other BSC and

directed retry succeeds, MSC sends CLEAR COMMAND message to the originating BSC to release the original connection. This item is measured when the originating BSC receives this message.

3) In the case the directed retry target cell is located in the same BSC and the directed retry succeeds, target cell sends Inter Clear Request message to the source cell to request to release the resource and the original connection. This item is measured when the source cell receives this message.

4) This item is measured when BSC sends ASSIGNMENT COMPLETE message to MSC after the assignment procedure is successfully implemented.

20



5) In incoming BSC handover procedure, MS sends HANDOVER ACCESS message to the BSC. This item is measured when BSC receives HANDOVER DETECT message from BTS.

6) In the process of incoming internal inter cell handover and intracell handover in BSC, MS sends HANDOVER ACCESS message to BSC. BSC measures this item in the target cell when receiving HANDOVER DETECTION message from BTS.

Formula: none

XXIII. TCH call drop

Description: in assignment procedure and traffic channel handover procedure, BSC measures TCH call drop when the process implementation fails due to some reason after MS has accessed the TCH assigned by BSC. Or this item is measured when call drop takes place due to some reason when MS is in normal seizure of TCH. After the above cases occur, BSC sends CLEAR REQUEST message to MSC to request to clear the call.

Measurement point: this item is measured if call drop occurs on TCH in the following processes. Chapter 3 Figure 3-13 , Chapter 3 Figure 3-14 , Chapter 3 Figure 3-15 A1 and A2 indicate the main measurement points.1) In the case TCH serves as traffic channel, this item is measured when

BSC receives ERROR INDICATION message from BTS due to an abnormal case for a radio link layer connection. See GSM 0858 protocol.

2) In the case TCH is seized as traffic channel, this item is measured when BSC receives the CONNECT FAILURE INDICATION message from BTS due to an active connection has been broken for some reason such as TCH link failure or hardware failure etc. See GSM 0508 for details.

3) In assignment procedure and handover procedure, this item is measured in the case of the failure of decoding HANDOVER DETECTION and HANDOVER COMPLETE message.

4) In the case TCH serves as traffic channel, this item is measured when incoming BSC handover is initiated and the timer for the target cell to wait for HANDOVER COMPLETE message expires.

5) In the case TCH serves as traffic channel, this item is measured when outgoing BSC handover is initiated and the timer for the source cell to wait for CLEAR COMMAND message from MSC expires (T8 expires).

6) In Intra-BSC handover procedure, the target cell sends Inter Clear Request to the source cell when the timer for the target cell to wait for HANDOVER COMPLETE from MS expires, in this case, this item is measured in the source cell.

7) In Intra-BSC handover procedure, the source cell, excluding the source cell for directed retry, measures the item when the timer for the source cell

21



to wait for Inter Clear Request with cause value HANDOVER COMPLETE from the target cell expires.

8) In Intra-BSC handover procedure, when the target cell AM/CM net-drive fails (due to timeout or negative acknowledgement), the target cell sends Inter Clear Request to source cell, in this case, this item is measured in the source cell.

9) In the case that MS reverses to the original channel after intra BSC handover fails, the source cell first releases the terrestrial connection but the AM/CM re-net-drive fails (due to timeout or negative acknowledgement). In this case this item is measured in the source cell.

10) The resource of the lower_priority call will be preempted by the higher_priority call if MSC and BSC both supports preemption, which will cause call drop.

11) This item is measured when the RSL link of the TRX that the call is using disconnects, which will cause call drop.

Formula: none

MS BTS BSC

ASSIGN CMMAND

MSC

ASSIGNMENT REQUEST

SABM


CHANNEL ACTICATION


A1

ERROR INDICATION

CONNECTION FAILURE INDICATION

A2

A1, A2: TCH call drop (BSC)

Figure 3-13 TCH drop for assignment

22



MS BSC' BSC Ori-Cell

HANDOVER ACCESS

UA


BSC Des-Cell BSC''

HANDOVER COMMAND


HANDOVER DETECT

CH ACTCH ACT ACK

A1

ERROR INDICATION


A2

SABM

A1, A2: TCH drop for very early assignment (BSC), TCH call drop (BSC)

Figure 3-14 Drop for Intra BSC handover

MS Other BSC

HANDOVER ACCESS

UA

HANDOVER REQUIRED


HANDOVER COMMAND


HANDOVER DETECT

CH ACTCH ACT ACK

MSC

A1

ERROR INDICATION


A2

SABM

HANDOVER REQUEST

A1, A2: TCH drop for very early assignment (BSC), TCH call drop (BSC)

Figure 3-15 Incoming BSC TCH handover procedure

XXIV. Successful TCH seizures for very early assignment

Description: BSC measures this item when MS successfully seizes the TCH assigned by the network in very early assignment procedure (including the MS access for various reasons).

23



Measurement point: the measurement points of this item are indicated in Chapter 3 Figure 3-16 A1. This item is measured when BSC receives CHANNEL ACTIVATION ACKNOWLEDGE message from BTS in very early assignment TCH process.

Formula: none

A1:Successful TCH seizures for very early assignment

Figure 3-16 Successful TCH seizures for very early assignment procedure

XXV. TCH drop for very early assignment

Description: In intraBSC or interBSC handover procedure, if a handover occurs on TCH and the speech data indication is signaling, this handover is regarded as a signaling channel handover. BSC measures this item if MS has accessed the TCH assigned by BSC but the implementation of the signaling channel handover fails due to some reason. BSC also measures this item when call drop occurs due to some reason after MS has established the normal connection on TCH and the speech data indication is signaling. When the above cases occur, BSC sends a CLEAR REQUEST message to MSC to clear the current connection.

Measurement point: this item is measured if the channel type in the following cases is TCH. The A1 and A2 in Chapter 3 Figure 3-17 , Chapter 3 Figure 3-14 , and Chapter 3 Figure 3-15 indicate the main measurement points of this item.1) In the case TCH is seized as signaling channel, this item is measured

when BSC receives ERROR INDICATION message from BTS due to an abnormal case for a radio link layer connection. See GSM 0858 protocol.

2) In the case TCH is seized as signaling channel, this item is measured when BSC receives CONNECTION FAILURE INDICATION message from BTS due to an active connection has been broken for some reason such

24



as TCH link failure or hardware failure etc. See GSM 0858 protocol for details.

3) In the case TCH is seized as signaling channel, in incoming BSC handover procedure, this item is measured in the target cell in the case of the failure of decoding HANDOVER DETECTION and HANDOVER COMPLETE message.

4) In the case TCH serves as signaling channel, this item is measured when incoming BSC handover is initiated and the timer for the target cell to wait for HANDOVER COMPLETE message expires.

5) In the case TCH serves as signaling channel, this item is measured when outgoing BSC handover is initiated and the timer for the source cell to wait for CLEAR COMMAND message from MSC expires (T8 expires).

6) In the case TCH is seized as signaling channel, in Intra-BSC handover procedure, this item is measured in the source cell when the timer for the target cell or the source cell to wait for HANDOVER COMPLETE expires.

7) In the case TCH is seized as signaling channel, The resource of the lower_priority call will be preempted by the higher_priority call if MSC and BSC both supports preemption, which will cause call drop.

8) In the case TCH is seized as signaling channel, this item is measured when the RSL link of the TRX that the call is using disconnects, which will cause call drop.

Formula: none

MS BTS BSC

CHANNEL REQUEST CHANNEL REQUIRED

CHANNEL ACTIVATION



EST_IND

A1

SABM

UA

ERROR INDICATION


A2

A1, A2: TCH drop for very early assignment (BSC)

Figure 3-17 TCH drop for very early assignment

XXVI. Attempted SDCCH seizures (all)

Description: in immediate assignment procedure, MS sends CHANNEL REQUEST to BTS to request radio channel. In incoming BSC handover

25



procedure, MSC requests radio resource by sending HANDOVER REQUEST to BSC. In intra BSC handover, BSC itself requests a new channel for call. In those cases, this item is measured when BSC receives SDCCH allocation request.

Measurement point: the measurement point of this item is described in Figure3-18, Figure 3-20 and Figure 3-20 SD-ATT-BSC1--SD-ATT- BSC3.1) In immediate assignment procedure, BSC measure this item when it

receives CHANNEL REQUIRED message from MS and if the requested channel type is SDCCH.

2) For intra BSC handover on SDCCH, this item is measured when the target cell receives Intercell Handover Request message (Huawei defined message) from the source cell.

3) This item is measured if when Huawei BSC receives HANDVER REQUEST message from other BSC and the handover is taken place on SDCCH.

Formula: none

MS BTS BSC

CHANNEL REQUEST

CHANNEL REQUIRED

CHANNEL ACTIVATION



SD-ATT-BSC1

EST_IND

SD -ATT-BSC1: Attempted SDCCH seizures (all)


26



MS BTS' BSC Ori-Cell

HANDOVER ACCESS

UA


BSC Des-Cell BTS''MR

Handover algorithm

HANDOVER COMMAND


HANDOVER DETECT

CH ACTCH ACT ACK

HANDOVER COMPLETE

Inter Clear Request(Handover Success)

SD-ATT-BSC2

SABM

SD-ATT-BSC2: Attempted SDCCH seizures (all)


MS Other BSC

HANDOVER ACCESS

UA

HANDOVER REQUIRED


HANDOVER COMMAND


HANDOVER DETECT

CH ACTCH ACT ACK

HANDOVER COMPLETE

SD-ATT-BSC3

MSC

QUEUEING INDICATION

SABM

HANDOVER REQUEST

SD -ATT-BSC3: Attempted TCH seizures (all)


27



XXVII. Successful SDCCH seizures

Description: in immediate assignment procedure, assignment procedure, and handover procedure, this item is measured when BSC receives the notification from MS that MS has successfully seized the assigned SDCCH.

Measurement point:1) In immediate SDCCH assignment procedure, this item is measured when

BSC receives CHANNEL ACTIVATION ACKNOWLEDGE message from BTS.

2) In the process of incoming BSC handover on SDCCH, BTS sends HANDOVER DETECTION message to BSC. This item is measured when BSC receives HANDOVER DETECTION.

3) In the process of incoming internal inter cell handover and intracell handover in BSC, BTS sends HANDOVER DETECTION message to BSC. BSC measures this item in the target cell when receiving this message.

Formula: none

XXVIII. Attempted SDCCH seizures meeting SDCCH overflow

Description: in immediate assignment procedure and handover procedure, this item is measured if there is no available SDCCH for assignment when MS or MSC requests BSS to assign SDCCH.

Measurement point: this item is measured if there is no available SDCCH when SDCCH is requested in the following cases:1) BSC receives CHANNEL REQUIRED message from BTS.2) BSC receives Intercell Handover Request message from other cell in the

same BSC.3) BSC receives HANDOVER REQUEST message from other BSC.

Formula: none

XXIX. SDCCH call drop

Description: in immediate assignment procedure and handover procedure, BSC measures SDCCH call drop when the process implementation fails due to some reason after MS has accessed the SDCCH assigned by BSC. Or this item is measured when call drop takes place due to some reason when MS is in normal seizure of SDCCH. After the above cases occur, BSC sends CLEAR REQUEST message to MSC.

Measurement point: 1) This item is measured when BSC receives ERROR INDICATION

message from BTS due to an abnormal case for a radio link layer connection.

28



2) This item is measured when BSC receives CONNECTION FAILURE INDICATION message from BTS because an active connection has been broken for some reason such as SDCCH link failure or hardware failure (see GSM 0508 for details).

3) In incoming BSC handover procedure on SDCCH, this item is measured in the target cell in the case of the failure of decoding HANDOVER DETECTION and HANDOVER COMPLETE message.

4) In the process of incoming BSC handover on SDCCH, this item is measured in the target cell when the timer for the target cell to wait for the HANDOVER COMPLETE message expires.

5) In the process outgoing BSC handover on SDCCH, this item is measured when the timer for the source cell to wait for CLEAR COMMAND message from MSC expires (T8 expires).

6) In the process of intra BSC handover on SDCCH, this item is measured in the source cell when the timer for the source cell or the target cell to wait for HANDOVER COMPLETE message expires.

7) This item is measured when the RSL link of the TRX that the call is running on disconnect, which will cause call drop, this item measures call drop on SDCCH for RSL disconnection.

Formula: none

XXX. Assignment requests

Description: the initial random access by the MS and "Immediate Assignment" to a DCCH is handled autonomously by the BSS without reference to the MSC. After the RR connection is established between MS and BSS, MS establishes the MM and CC connection with MSC on this channel. MSC allocates or reallocates to the MS a radio (and possibly terrestrial) resource in ASSIGNMENT REQUEST message according to MS’s CC connection request.

Measurement point: as shown in Figure 3-21 A1, this item is measured when BSC receives ASSIGNMENT REQUEST message from MSC.

Formula: none

29



MS BTS BSC

ASSIGN CMMAND

A1

MSC

ASSIGNMENT REQUEST

SABM


ASSIGNMENT COMPLETE


MODE (MODIFY)

MODE (MODIFY) ACKNOLEDGE(NEGATIVE ACKNOWLEDGE,REJECT)

(directly retry)HANDOVER FAILURE(REQUEST ACKNOWLEDGE)

CHANNEL ACKTIVATION

CHANNEL ACKTIVATION ACKNOWLEDGE (NACK)

ASSIGNMENT COMPLETE

In Immediate Assignment or IntraBSC Handover

ASS FAILURE

H 4

B 2

B 3 B 4 B 5

C1

C 2

D1 E1

F1

F1

F2

F3

F3

F3

G1

G 2 G 3

G4

G6

G5

G5

B6

H 2

H 3

H 3

ASS FAILURE

ASS FAILURE

A1: Assignment requests B2-B6: Unsuccessful assignments (equipment failure)

C1-C2: Unsuccessful assignments (requested

terrestrial resource unavailable)

D1: Unsuccessful assignments (terrestrial circuit already

allocated)

E1:Unsuccessful assignments (invalid

message contents))

F1-F3: Unsuccessful assignments (radio interface failure,

reversion to previous channel))

G1-G6: Unsuccessful assignments (no radio

resource available))H2-H4: Unsuccessful assignments (other causes))

Figure 3-21 Assignment implementation process

XXXI. Unsuccessful assignments

Description: BSS might fail to implement the assignment procedure due to some reason after receiving ASSIGNMENT REQUEST message from MSC.

30



Note:

The relation between queue, directed retry and mode modify in assignment procedure.

In assignment procedure, upon reception of ASSIGNMENT REQUEST message, BSC first checks

CIC resource, then analyzes the CHANNEL TYPE in the message (See GSM 0808), at last compares

the analyzed CHANNEL TYPE with the currently seized one. The comparison result leads to three

types of options: mode modify, directed retry, or requesting a new channel.

CHANNEL TYPE contains channel rate and type and traffic type (speech/data indicator), speech

encoding algorithm and transparency indicator.

The channel re-allocation is initiated if the channel rate or type is different.

The mode modify is initiated if the traffic type (speech/data indicator), or speech encoding

algorithm/transparency indicator is different.

If all are consistent, the system uses the existing radio channel and allocates CIC for BSC net-drive.

So there are 5 subsequent processes after the reception of ASSIGNMENT REQUEST.

1. Mode modify.

2. Queue (if there is no available channel during re-allocation and the system supports queue).

3. Directed retry (if there is no available channel during re-allocation and the system supports directed

retry).

4. No available channel after the queue timeout; directed retry again if the system supports directed

retry.

5. Normal assignment: new channel is assigned, activated, and then is normally seized by the MS.

Measurement point: as shown in Figure 3-21 , if BSS fails to respond to ASSIGNMENT COMPLETE message to MSC due to some reason after receiving ASSIGNMENT REQUEST message, this item is measured and BSS responds ASSIGNMENT FAILURE message to MSC simultaneously. Figure 3-21 shows the reasons for unsuccessful assignment. This item is measured for the unsuccessful assignment caused by any of these reasons.

Formula: none

XXXII. Unsuccessful assignments (equipment failure)

Description: the sum of unsuccessful assignments due to equipment failure. See Unsuccessful assignments for the process.

Measurement point: as shown in Figure 3-21 B2~B6, this item is measured in the following case.1) In assignment procedure, BSC assigns terrestrial circuit according to the

CIC specified by MSC but the assignment fails. In this case, this item is measured and BSC requests MSC to clear the connection simultaneously.

2) In assignment procedure, this item is measured if BSC’s AM/CM net-drive fails (AM/CM returns net-drive failure or responds timeout) after the mode

31



modify is implemented and the radio channel has been successfully modified according to the CHANNEL TYPE required by MSC.

3) If mode modify is initiated in assignment procedure, this item is measured when BSC receives MODE MODIFY NEGATIVE ACKNOWLEDGE message from BTS indicating the failure of mode modify after the MODE MODIFY message is sent to BTS.

4) If mode modify is initiated in assignment procedure, this item is measured when the timer for BSC to wait for the response expires after the MODE MODIFY message has been sent to BTS.

5) In assignment procedure, this item is measured when BSC receives Channel Activation NACK or the timer for BSC to wait for Channel Activation ACK expires.

Formula: none

XXXIII. Unsuccessful assignments (requested terrestrial resource unavailable)

Description: Unsuccessful assignments due to the requested terrestrial resource unavailable. See Unsuccessful assignments for the process.

Measurement point: as shown in Figure 3-21 C1~C2:1) This item is measured when BSC detects the state of CIC requested in the

ASSIGNMENT REQUEST message received from MSC is unavailable.2) This item is measured when AM/CM net-drive fails (AM/CM returns net-

drive rejection or timer for waiting for AM/CM expires) in assignment procedure,.

Formula: none

XXXIV. Unsuccessful assignments (terrestrial circuit already allocated)

Description: unsuccessful assignments due to terrestrial circuit already allocated. See Unsuccessful assignments for the process.

Measurement point: as shown in Figure 3-21 D1, in assignment procedure, this item is measured when BSC detects the CIC requested in the ASSIGNMENT REQUEST message received from MSC has already been allocated.

Formula: none

XXXV. Unsuccessful assignments (invalid message contents)

Description: unsuccessful assignments due to invalid message contents. See Unsuccessful assignments for the process.

Measurement point: as shown in Figure 3-21 E1, this item is measured when BSC detects the ASSIGNMENT REQUEST message contains invalid contents

32



during the message decoding, Which includes CHANNEL TYPE, CIC, Layer 3 header information.

Formula: none

XXXVI. Unsuccessful assignments (radio interface failure, reversion to previous channel)

Description: unsuccessful assignments due to radio interface failure with reversion to previous channel

Measurement point: as shown in Figure 3-21 F1-F3:1) BSC measures this item when MS fails to access the new channel and

reverses to the old signaling channel due to Um interface failures after it receives the ASSIGNMENT COMMAND message.

2) in assignment procedure, after sending the ASSIGNMENT COMMAND message, if the timer for BSC to wait for ASSIGNMENT COMPLETE message from MS expires, BSC measures this item and informs MSC to clear the connection simultaneously.

Formula: none

XXXVII. Unsuccessful assignments (no radio resource available)

Description: unsuccessful assignments due to no radio resource available. See Unsuccessful assignments for the process.

Measurement point: as shown in Figure 3-21 G1-G6, 1) This item is measured when BSC does not support the assigned channel.2) This item is measured if there is no available channel when BSC assigns

the channel after receiving ASSIGNMENT REQUEST message and BSC does not support queue and directed retry.

3) If mode modify is initiated in assignment procedure, the CHANNEL MODE MODIFY message is sent to the MS, then the MS implement mode modify and response CHANNEL MODE MODIFY ACKNOWLEDGE to BSC. This item is measured when BSC receives this message from MS but meets error when decode channel mode IE.

4) If there is no available channel when BSC receives ASSINGMENT REQUEST message and the system supports queue, the assignment procedure waits for channel resource; if idle channel is available before the timer expires, the system allocates the channel successfully and the assignment procedure goes normally; if there still no available channel resource after the timer expires and the call doesn’t support directed retry, BSC measures the unsuccessful assignment due to channel unavailable.

5) If directed retry fails, this item is measured and ASSIGNMENT FAILURE message is sent to MSC to request to clear the connection if the source cell of directed retry is in one of the following cases.

33



a) There is no available target cell in the MR reported from MS, for directed retry selects the target cell of handover according to the MR.

b) This item is measured in the source cell if the source cell receives Intercell Handover Reject message from the target cell when directed retry is trying to select other cell in the BSC.

c) This item is measured in the source cell if the MS reverses to the original signaling channel when directed retry is trying to select other cell in the BSC.

d) This item is measured in the source cell when the timer for source cell to wait for response from target cell expires when directed retry is trying to select other cell in the BSC.

e) When directed retry is trying to select other cell in the BSC, the source cell receives Inter Clear Request message (Huawei defined message) from the target cell. However this message is not the one to inform the handover completion but to inform the source cell of the directed retry failure and to request to clear the connection. In this case, this item is measured in the source cell.

f) When directed retry is trying to select other cell in the BSC, the source cell sends HANDOVER COMMAND to MS to request the MS to access the new channel. This item is measured if the source cell has not received Inter Clear Request message (Huawei defined message) from the target cell after the timer expires.

Note:

If directed retry is trying to select the target cell in other BSC and the directed retry process fails, the

source cell does not return assignment failure and the failure is not measured as an assignment

failure item. The failure is processed according to handover procedure.

Formula: none

XXXVIII. Unsuccessful assignments (other causes)

Description: unsuccessful assignments due to the following causes. See Unsuccessful assignments for the process.

Measurement point: as shown in Figure 3-21 H2-H4,1) When BSC detects IEs, such as, channel rate and type, speed encoding

algorithm, is incorrectly described in ASSIGNMENT REQUEST message.

34



2) In assignment procedure, BSC measures the item if the timer for BSC to wait for ESTABLISH INDICATION expires when the ASSIGNMENT COMMAND message has been sent to MS In this case BSC sends clear request to MSC to clear the connection simultaneously.

3) If mode modify is initiated in assignment procedure, BSC does not receive the acknowledge message from MS after sending mode modify message, which leads to the timeout of BSC.

Formula: none

XXXIX. Unsuccessful channel activation during assignment (NACK)

Description: See Unsuccessful assignments . Measurement point: this item is measured when BSC receives CHANNEL

ACTIVATION NEGATIVE ACKNOWLEDGE message from BTS after sending CHANNEL ACTIVATION message to BTS to activate the newly- allocated channel.

Formula: none

XL. Channel activation timeout during assignment

Description: See Unsuccessful assignments . Measurement point: this item is measured when the timer for BSC to wait for

CHANNEL ACTIVATION ACKNOWLEDGE from BTS expires after sending CHANNEL ACTIVATION message to BTS to activate the newly- allocated channel.

Formula: none

XLI. Sum of TCH measurement reports (excluding very early assignment)

Description: MS shall report a MR to the network every 480ms after the successful seizure of TCH. See GSM 0408 protocol. This item is a parameter for traffic calculation.

Measurement point: this item is measured when BSC receives the MR of TCH from BTS. This item excludes the MR of the TCH with speech/data indicator being signaling. Both M900 and M1800 cells are included.

Formula: none

XLII. Sum of 1800 cell TCH measurement reports(excluding very early assignment)

Description: MS shall report a MR to the network every 480ms after the successful seizure of TCH. See GSM 0408 protocol. This item is a parameter for traffic calculation.

35



Measurement point: this item is measured when BSC receives the MR of TCH from BTS. This item excludes the MR of the TCH with speech/data indicator being signaling. Only M1800 cells are included.

Formula: none

XLIII. Sum of configured TRX in the BSC

Description: the sum of actually configured TRXs in the BSC. Measurement point: the configured TRXs that are shown in statistic database

as "install" are measured every time at the end of a statistic cycle. Formula: none

XLIV. Sum of available TRX in the BSC

Description: sum of TRXs that managed by BSC and are in normal use state. Measurement point: this item is measured at the end of a statistic cycle. Formula: none

XLV. Attempted intracell handovers

Description: Intracell handover is normally triggered by receiving strength, receiving quality, O&M intervention, IUO, and its source cell and the target cell are the same one. This item measures the times of handover attempts which are initiated by a source cell in intracell handover. The measurement result can be used to observe the frequency of the intracell handover initiated by BSC. Together with Successful intracell handovers and Unsuccessful intracellhandovers , this item reflects the performance of intracell handover in the BSC. Related items: Attempted intercell handovers , Attempted incoming BSChandovers , Attempted outgoing BSC handovers .

Note:

In intraBSC handover procedure, an idle adjacent cell (if the adjacent and the source cell are in

different BMs of the same BSC, the adjacent cell will be treated as an idle cell, because system can't

get the using situation of channels in other BM’s cell) has a higher priority to be selected as the target

cell. If all adjacent cells of the source cell are congested, system will still select the default adjacent

cell which is the first one of the adjacent cell candidates, even if it is congested. If the selected

adjacent cell and the source cell are the same one, this item will be measured. But the IUO handover

(a special handover that still belongs to intracell handover and occurs between the overlaid and

underlaid subcell of an IUO cell) is an exception. If the target subcell is congested, the handover

cannot be initiated, and the measurement cannot be carried out.

36



Measurement point: After handover algorithm decision, the source cell sends an Intercell Handover Request message to the target cell, and this item is measured if the source cell is the same as the target cell.

Formula: none.

XLVI. Successful intracell handovers

Description: Intracell handover is normally triggered by receiving strength, receiving quality, O&M intervention, IUO handover. If BSC receives a HANDOVER COMPLETE message which shows an MS has been successfully handed over to the target cell, then the BSC sends a HANDOVER PERFORMED message to MSC to notify the success of this handover. This item measures the times of successful internal intracell handovers. This item, together with Attempted intracell handovers and Unsuccessful intracellhandovers helps the user know the performance of intracell handover in the BSC. Related items: Successful intercell handovers , Successful incomingBSC handovers and Successful outgoing BSC handovers .

Measurement: Measured when BSC sends a HANDOVER PERFORMED message to MSC after the MS has been successfully handed over to target cell during the procedure of intracell handover, as shown in Figure 3-22 A1.

Formula: none.

MS BTS BSC MSC/VLR

HANDOVER COMPLETE

.HANDOVER COMMAND

A1

(Intracell handover)

HANDOVER PERFORMED

A1: Successful intracell handover

Figure 3-22 Successful intracell handover

XLVII. Unsuccessful intracell handovers

Description: After an intracell handover has been initiated, the source cell enters the status of waiting for the Intercell Handover Response message. After BSC has allocated channel, activated new channel, and sent a HANDOVER COMMAND message to MS, the source cell enters the status of waiting for Inter Handover Complete. After the MS has successfully accessed the new channel, the previous channel will be released. During this period, any abnormality will cause failure of the handover. This item measures the times of

37



the unsuccessful intracell handovers. This item, together with Attemptedintracell handovers and Successful intracell handovers helps the user know the performance of intracell handover in the BSC. Related items: Unsuccessfulincoming BSC handovers .

38



Note:

The following occasions might cause the failure of internal intracell handover:

1) Previous channel becomes invalid or the connection is terminated due to abnormality of radio

resource or terrestrial resource;

2) MS fails to access the destination channel due to poor radio environment or incorrect handover

parameter;

3) Handover is interrupted and original call is cleared because errors have been detected during BSS

internal processing;

4) BSS is informed to clear the call when MSC detects error.

Measurement point:1) Measured when the source cell receives the CONNECTION FAILURE

INDICATION message from BTS during the procedure of intracell handover, as shown in Figure 3-23 A1 and A2.

2) During the procedure of intracell handover, after the source cell sends the HANDOVER COMMAND message, if MS fails to access the destination channel, the MS will return to the previous channel and send a HANDOVER FAILURE message to the source cell. This item is measured when the source cell receives this message, as shown in Figure 3-23 A3.

3) During the procedure of intracell handover, after the target cell receives HANDOVER DETECTION, it will send an Inter Clear Request message to source cell for AM/CM net-drive fails or the timer waiting for HANDOVER COMPLETE times out. This item is measured when the source cell receives this message and then the source cell sends a CLEAR REQUEST message to MSC simultaneously.

4) During the procedure of intracell handover, the source cell receives CLEAR COMMAND from MSC. This item is measured in this case, as shown in Figure 3-23 A4 and A5.

5) During the procedure of intracell handover, the target cell sends Intercell Handover Reject to the source cell when it fails to prepare or activate the channels (e.g. channel allocation failure, CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE received, expiry of timer waiting for CHANNEL ACTIVATION ACKNOWLEDGE). This item is measured when the target cell receives this message.

6) During the procedure of intracell handover, the source cell receives ERROR INDICATION from BTS. This item is measured in this case, as shown in Figure 3-23 A6 and A7.

7) During the procedure of intracell handover, this item measured at the expiry of the timer waiting for Intercell Handover Response in source cell.

39



8) During the procedure of intracell handover, this item measured at the expiry of the timer waiting for Inter Clear Request in source cell.

Formula: none.

MS BTS BSC MSC/VLR

HANDOVER COMPLETE

.HANDOVER COMMAND

A2

(Intracell handover)

HANDOVER PERFORMED

CONN FAIL IND

Old Channel

CONN FAIL INDHANDOVER FAILURE

A3

A1

Old Channel

New Channel

A5

CLEAR COMMAND

CLEAR COMMAND

A4

ERROR IND

A6

ERROR INDA7

A1~A7: Unsuccessful intracell handover

Figure 3-23 Unsuccessful intracell handover

XLVIII. Attempted intercell handovers

Description: Internal intercell handover is normally triggered by receiving strength, receiving quality, TA, traffic load, Response to MSC invocation, DIRECTED RETRY, rapid rxlevel drop, better cell, O&M intervention. The source cell and target cells are different ones in the same BSC. This item measures the times of handover attempts which are initiated by a source cell in internal intercell handover procedure. This item reflects the frequency of BSC initiating internal intercell handovers. This item, together with Successfulintercell handovers helps the user know the performance of the Internal intercell handover. Related item: Attempted intracell handovers , Attemptedincoming BSC handovers and Attempted outgoing BSC handovers .

40



Note:

In intra BSC handover procedure, an idle adjacent cell (if the adjacent and the source cell are in




cell which is the first one of the adjacent cell candidates, even if it is congested so as to carry out the

measurement of this item.

Measurement point: After handover algorithm decision, the source cell sends an Intercell Handover Request message to the target cell, and this item is measured if the source cell and the target cell are not the same cell.

Formula: none.

XLIX. Intercell handovers

Description: During the procedure of internal intercell handover, after successfully activating the new channel, the target cell will inform the source cell that the channel is ready. After receiving the information from the target cell, the source cell will send HANDOVER COMMAND to the MS. This item measures the times of this message being sent. This item, together with Attempted intercell handovers helps the user observe the situation of handover failure due to abnormality during the procedure of preparing new channel in the target cell, or together with Successful intercell handovers know the situation of handover failure due to Um interface abnormality. Related items: Intra BSC handovers, Incoming BSC handovers and OutgoingBSC handovers.

Measurement point: During the procedure of internal intercell handover, the source cell sends the HANDOVER COMMAND message. This item is measured in this case, as shown in Figure 3-24 A1.

Formula: none.

MS BTS BSC MSC/VLR

HANDOVER COMPLETE

HANDOVER COMMAND

A1

(Intercell handover)

HANDOVER PERFORMED

CHANNEL ACT

CHAN ACT ACK

A1: internal intercell handover

41



Figure 3-24 internal intercell handover

L. Attempted intercell handovers (9001800)

Description: Internal intercell handover is normally triggered by receiving strength, receiving quality, TA, traffic load, Response to MSC invocation, DIRECTED RETRY, rapid rxlevel drop, better cell, O&M intervention. The source cell and target cells are different ones controlled by the same BSC. This item measures the times of handover attempts from the source cell (GSM900) to the target cell (GSM1800) in internal intercell handover. This item, together with Attempted intercell handovers (1800→900) , helps the user know the frequency of interband handovers, or together with Successfulintercell handovers (9001800), know the performance of interband handover in the BSC. Related items: Attempted intercell handovers .

Note:

1) In intraBSC handover procedure, an idle adjacent cell (if the adjacent and the source cell are in




cell that is the first one of the adjacent cell candidates, even if it is congested so as to carry out the


2) Cell system type: GSM900 cell and GSM1800 cell.

GSM 900 cell: The frequency value of this cell is in GSM900 band, and the corresponding ARFCN is

from 1 to 124.

GSM 1800 cell: The frequency value of this cell is in GSM1800 band, and the corresponding ARFCN

is from 512 to 885.

Measurement point: Measured when the source cell (GSM900 cell) sends Intercell Handover Request to the target cell (GSM1800 cell) after handover algorithm decision.

Formula: none.

LI. Attempted intercell handovers (1800→900)

Description: Internal intercell handover is normally triggered by receiving strength, receiving quality, TA, traffic load, Response to MSC invocation, DIRECTED RETRY, rapid rxlevel drop, better cell, O&M intervention. The source cell and target cells are different ones controlled by the same BSC. This item measures the times of handover attempts from the source cell

42



(GSM1800) to the target cell (GSM900) in internal intercell handover. This item, together with Attempted intercell handovers (9001800) , helps the user know the frequency of interband handovers, or together with Successfulintercell handovers (1800900) to know the performance of interband handover in the BSC. Related items: Attempted intercell handovers .

Note:

1) In intraBSC handover, an idle adjacent cell will be selected as the target cell. If all adjacent cells of

the source cell are congested, system will still select the default adjacent cell even if it is congested so

as to carry out the measurement of this item.



from 1 to 124.


is from 512 to 885.

Measurement point: Measured when the source cell (GSM1800 cell) sends Intercell Handover Request to the target cell (GSM900 cell) after handover algorithm decision.

Formula: none.

LII. Successful intercell handovers

Description: Internal intercell handovers can be classified into two types by the handover cause: DIRECTED RETRY, non-DIRECTED RETRY (e.g. signal quality, signal strength, TA, traffic load, rapid rxlevel drop, better cell, Response to MSC invocation, and O&M intervention). This item measures the times of successful internal intercell handovers. This item, together with Attempted intercell handovers , helps the user know the performance of internal intercell handover. Related items: Successful intracell handovers , Successful incoming BSC handovers and Successful outgoing BSChandovers .

Measurement point: 1) Measured when BSC sends ASSIGNMENT COMPLETE to MSC after the

MS has successfully accessed in the target cell in internal intercell handover procedure (handover cause: DIRECTED RETRY), as shown in Figure 3-25 A1.

2) Measured when BSC sends HANDOVER PERFORMED to MSC after the MS has successfully accessed in the target cell in the internal intercell handover procedure (handover cause: non-DIRECTED RETRY, e.g.

43



signal quality, signal strength, TA, traffic load, rapid rxlevel drop, better cell, Response to MSC invocation, and O&M intervention), as shown in Figure 3-26 A1.

Formula: none.

MS BTS BSC MSC/VLR

HANDOVER COMPLETE

HANDOVER COMMAND

A1

ASSIGNMENT REQUEST

ASSIGNMENT COMPLETE

C1 B1

A1: Successful internal intercell handover

B1: Successful internal intercell handover (900-1800)

C1: Successful internal intercell handover (1800-900)

Figure 3-25 Successful internal intercell handover (DIRECTED RETRY)

MS BTS BSC MSC/VLR

HANDOVER COMPLETE

.HANDOVER COMMAND

A1

(Intercell Handover)

HANDOVER PERFORMED

C1 B1

A1: Successful Internal intercell handover

B1: Successful Internal intercell handover (900-1800)

C1: Successful Internal intercell handover (1800-900)

Figure 3-26 Successful Internal intercell handover (not DIRECTED RETRY)

LIII. Successful intercell handovers (9001800)

Description: Internal intercell handovers can be classified into two types by the handover cause: DIRECTED RETRY, non-DIRECTED RETRY (e.g. signal quality, signal strength, TA, traffic load, rapid rxlevel drop, better cell, Response to MSC invocation, and O&M intervention). This item measures the

44



times of successful internal intercell handovers from GSM900 cell to GSM1800 cell. This item, together with Attempted intercell handovers (9001800) helps the user know the performance of interband handover in the BSC. Related items: Successful intercell handovers .

45



Note:

Cell system type: GSM900 cell and GSM1800 cell.


from 1 to 124.


is from 512 to 885.

Measurement point:1) In internal intercell handover (handover cause: DIRECTED RETRY), the

source cell is a GSM900 cell and the target cell is a GSM1800 one. After MS successfully accessed the target cell, BSC sends ASSIGNMENT COMPLETE to MSC. This item is measured in this case, as shown in Figure 3-25 B1.

2) In internal intercell handover (handover cause: non-DIRECTED RETRY, e.g. signal quality, signal strength, TA, traffic load, rapid rxlevel drop, better cell, Response to MSC invocation, and O&M intervention), the source cell is a GSM900 cell and the target cell is a GSM1800 one. After MS successfully handed over to the target cell, BSC sends a HANDOVER PERFORMED message to MSC. This item is measured in this case, as shown in Figure 3-26 B1.

Formula: none.

LIV. Successful intercell handovers (1800900)

Description: Internal intercell handovers can be classified into two types by the handover cause: DIRECTED RETRY, non-DIRECTED RETRY (e.g. signal quality, signal strength, TA, traffic load, rapid rxlevel drop, better cell, Response to MSC invocation, and O&M intervention). This item measures the times of successful internal intercell handovers from GSM1800 cell to GSM900 cell. This item, together with Attempted intercell handovers (1800→900) to know the performance of inter-frequency handover in the BSC. Related items: Successful intercell handovers .

Note:



from 1 to 124.

46




is from 512 to 885.

Measurement point:1) In an internal intercell handover (handover cause: DIRECTED RETRY),

the source cell is a GSM1800 cell and the target cell is a GSM900 one. After MS successfully handed over to the target cell, BSC sends an ASSIGNMENT COMPLETE message to MSC. This item is measured in this case, as shown in Figure 3-25 C1.

2) In a Internal intercell handover (handover cause: non-DIRECTED RETRY, e.g. signal quality, signal strength, TA, traffic load, rapid rxlevel drop, better cell, Response to MSC invocation, and O&M intervention), the source cell is a GSM1800 cell and the target cell is a GSM900 one. After successfully handed over to the target cell, BSC sends HANDOVER PERFORMED to MSC. This item is measured in this case, as shown in Figure 3-26 C1.

Formula: none.

LV. Intra BSC handovers

Description: There are two types of intraBSC handovers: internal intracell handover and internal intercell handover. After successfully activating the new channel, the target cell informs the source cell that the channel is ready. After receiving this information, the source cell sends a HANDOVER COMMAND message to MS. This item measures the total times of sending this message in the BSC, both in the cases of intercell handover and intracell handover. This item, together with Intercell handovers , helps the user know the times of internal intracell handovers. Related items: Intercell handovers , Incoming BSChandovers .

Measurement point: During the procedure of intraBSC handover, the source cell sends the HANDOVER COMMAND message. This item is measured in this case, as shown in Figure 3-27 A1.

Formula: none.

47



MS BTS BSC MSC/VLR

HANDOVER COMPLETE

.HANDOVER COMMAND

A1

HANDOVER PERFORMED

CHANNEL ACT

CHAN ACT ACK

A1: Intra BSC handover

Figure 3-27 Intra BSC handover

LVI. Attempted incoming BSC handovers

Description: During the procedure of interBSC handover, source BSC initiates a handover by sending a HANDOVER REQUIRED message to MSC. After receiving this message, MSC sends a HANDOVER REQUEST message to target BSC. The target BSC receives this message, and starts the preparation of new channel. This item measures the times of target BSC receiving handover requests. This item reflects the frequency of the handover from other BSCs to local BSC. Together with Successful incoming BSC handovers , this item helps the user know the performance of this type of handover in the local BSC. Related items: Attempted intracell handovers , Attempted intercellhandovers and Attempted outgoing BSC handovers .

Measurement point: During the procedure of interBSC handover, the target BSC receives HANDOVER REQUEST from MSC. This item is measured in this case, as shown in Figure 3-28 F1.

Formula: none.

48



MS BTS BSC MSC/VLR

HANDOVER COMPLETE

HANDOVER DETECTION

A1 ,B1 ,C1 , D1, E1

CHANNEL ACT

CHAN ACT ACK

HANDOVER COMPLETE

HANDOVER REQ ACK

HANDOVER REQUEST

F1

A1: Successful incoming BSC handover

B1: Successful incoming BSC handover (900-1800)

C1: Successful incoming BSC handover (1800-900)

D1: Successful incoming BSC handover (to 900)

E1: Successful incoming BSC handover (to 1800)

F1: Successful incoming BSC handover

Figure 3-28 Successful incoming BSC handover

LVII. Attempted incoming BSC handovers (9001800)

Description: During the procedure of interBSC handover, the target BSC receives HANDOVER REQUEST from MSC, and then packs this message into IntoBSC Handover Request, which will be sent to the BM which the target cell belongs to. This item measures the times of the target BSC receiving IntoBSC Handover Request when the source cell is a GSM900 one, and the target cell is a GSM1800 one. This item reflects the frequency of the handover from GSM900 cells of other BSCs to GSM1800 cells of the local BSC. Together with Successful incoming BSC handovers (9001800), this item helps the user know the performance of this type of handover. Related items: Attemptedincoming BSC handovers .

Note:



from 1 to 124.


is from 512 to 885.

49



Measurement point: During the procedure of interBSC handover, the BM which the target cell belongs to receives IntoBSC Handover Request, and the source cell is a GSM900 one, the target cell is a GSM1800 one. This item is measured in this case.

Formula: none.

LVIII. Attempted incoming BSC handovers (1800900)

Description: During the procedure of interBSC handover, the target BSC receives HANDOVER REQUEST from MSC, and then packs this message into IntoBSC Handover Request, which will be sent to the BM which the target cell belongs to. This item measures the times of the target BSC receiving IntoBSC Handover Request when the source cell is a GSM1800 one, and the target cell is a GSM900 one. This item reflects the frequency of the handover from GSM1800 cells of other BSCs to GSM900 cells of the local BSC. Together with Successful incoming BSC handovers (1800900), this item helps the user know the performance of this type of handover. Related items: Attemptedincoming BSC handovers .

Note:



from 1 to 124.


is from 512 to 885.

Measurement point: During the procedure of interBSC handover, the BM which the target cell belongs to receives Inter IntoBSC Handover Request, and the source cell is a GSM1800 one, while the target cell is a GSM900 one. This item is measured in this case.

Formula: none.

LIX. Attempted incoming BSC handovers (to 900)

Description: During the procedure of interBSC handover, the target BSC receives HANDOVER REQUEST from MSC, and then packs this message into IntoBSC Handover Request, which will be sent to the BM which the target cell belongs to. This item measures the times of the target BSC receiving the Inter IntoBSC Handover Request message when the target cell is a GSM900 one. This item reflects of the handover to GSM900 cells of the local BSC. Together

50



with Successful incoming BSC handovers (to 900) , this item helps the user know the performance of this type of handover. Related items: Attemptedincoming BSC handovers .

Measurement point: During the procedure of interBSC handover, the BM which the target cell belongs to receives Inter IntoBSC Handover Request, and the target cell is a GSM900 one. This item is measured in this case.

Formula: none.

LX. Attempted incoming BSC handovers (to 1800)

Description: During the procedure of interBSC handover, the target BSC receives the HANDOVER REQUEST message from MSC, and then packs this message into the Inter IntoBSC Handover Request message, which will be then sent to the BM which the target cell belongs to. This item measures the times of the target BSC receiving the Inter IntoBSC Handover Request message when the target cell is a GSM1800 one. This item reflects of the handover to GSM1800 cells of the local BSC. Together with Successfulincoming BSC handovers (to 1800) , this item helps the user know the performance of this type of handover. Related items: Attempted incoming BSChandovers .

Note:



from 1 to 124.


is from 512 to 885.

Measurement point: During the procedure of interBSC handover, the BM which the target cell belongs to receives Inter IntoBSC Handover Request, and the target cell is a GSM1800 one. This item is measured in this case.

Formula: none.

LXI. Successful incoming BSC handovers

Description: During the procedure of interBSC handover, the target BSC receives the HANDOVER REQUEST message from MSC, and starts the preparation of new channel. After the channel preparation has been done, and the MS has accessed the target cell, the target BSC sends a HANDOVER COMPLETE message to MSC to indicate that the handover has finished. This item, together with Attempted incoming BSC handovers , helps the user know

51



the performance of this type of handover. Related items: Successful outgoingBSC handovers, Successful intercell handovers , Successful intracellhandovers .

Measurement point: During the procedure of interBSC handover, the target BSC receives HANDOVER COMPLETE, and forward it to MSC, as shown in Figure 3-28 A1.

Formula: none.

LXII. Successful incoming BSC handovers (9001800)

Description: During the procedure of interBSC handover, the target BSC receives the HANDOVER REQUEST message from MSC, and starts the preparation of new channel. After the channel preparation has been done, and the MS has accessed the target cell, the target BSC sends a HANDOVER COMPLETE message to MSC to indicate that the handover has finished. This item measures the successful handovers from other BSCs (GSM900 cells) to local BSC (GSM1800 cell). This item, together with Attempted incoming BSChandovers (9001800) , helps the user know the performance of the handover of this type. Related parameters: Successful incoming BSChandovers .

Note:



from 1 to 124.


is from 512 to 885.

Measurement point: During the procedure of interBSC handover from GSM900 cell to GSM1800 cell, the target BSC receives the HANDOVER COMPLETE message, and forwards it to MSC, as shown in Figure 3-28 B1.

Formula: none.

LXIII. Successful incoming BSC handovers (1800900)

Description: During the procedure of interBSC handover, the target BSC receives the HANDOVER REQUEST message from MSC, and starts the preparation of new channel. After the channel preparation has been done, and the MS has accessed the target cell, the target BSC sends a HANDOVER COMPLETE message to MSC to indicate that the handover has finished. This item measures the successful handovers from other BSCs (GSM1800 cells) to

52



local BSC (GSM900 cell). This item, together with Attempted incoming BSChandovers (1800900) , helps the user know the performance of the handover of this type. Related parameters: Successful incoming BSChandovers .

Measurement point: During the procedure of interBSC handover from GSM1800 cell to GSM900 cell, the target BSC receives the HANDOVER COMPLETE message, and forwards it to MSC, as shown in Figure 3-28 C1.

Formula: none.

LXIV. Successful incoming BSC handovers (to 900)

Description: During the procedure of interBSC handover, the target BSC receives the HANDOVER REQUEST message from MSC, and starts the preparation of new channel. After the channel preparation has been done, and the MS has accessed the target cell, the target BSC sends a HANDOVER COMPLETE message to MSC to indicate that the handover has finished. This item measures the successful handovers from other BSCs to local BSC (GSM900 cell). This item, together with Attempted incoming BSC handovers(to 900) , helps the user know the performance of the handover of this type. Related parameters: Successful incoming BSC handovers .

Measurement point: During the procedure of interBSC handover to GSM900 cell, the target BSC receives the HANDOVER COMPLETE message, and forwards it to MSC, as shown in Figure 3-28 D1.

Formula: none.

LXV. Successful incoming BSC handovers (to 1800)

Description: During the procedure of interBSC handover, the target BSC receives the HANDOVER REQUEST message from MSC, and starts the preparation of new channel. After the channel preparation has been done, and the MS has accessed the target cell, the target BSC sends a HANDOVER COMPLETE message to MSC to indicate that the handover has finished. This item measures the successful handovers from other BSCs to local BSC (GSM1800 cell). This item, together with Attempted incoming BSC handovers(to 1800), helps the user know the performance of the handover of this type. Related parameters: Successful incoming BSC handovers .

Measurement point: During the procedure of interBSC handover to GSM900 cell, the target BSC receives the HANDOVER COMPLETE message, and forwards it to MSC, as shown in Figure 3-28 E1.

Formula: none.

53



LXVI. Unsuccessful incoming BSC handovers

Description: During the procedure of interBSC handover, the target BSC receives HANDOVER REQUEST from MSC, and then packs this message into IntoBSC Handover Request, and sends the packed message to the BM which the target cell belongs to request internal resource. And then the BSC checks the conditions of incoming BSC handover. If the conditions can be satisfied, the BSC applies for channel resource and generates HANDOVER COMMAND. And then the BSC activates the new channel and waits for the access of an MS on the new channel. On receiving HANDOVER COMPLETE from the MS, the target BSC sends a HANDOVER COMPLETE message to MSC, and this handover is finished here. If abnormality takes place during this period, BSC will send CLEAR REQUEST or HANDOVER FAILURE to MSC to indicate that the BSC wishes to release the associated dedicated resource(s). This means this incoming BSC handover fails. This item, together with Attempted incoming BSC handovers helps the user know the performance of this type of handover. The unsuccessful incoming BSC handovers with all kinds of specified cause can help know the details that cause the failure of BSC incoming handover. Related items: Unsuccessful outgoing BSChandovers with successful reversion and Unsuccessful outgoing BSChandovers with unsuccessful reversion .

Note:

The causes of unsuccessful incoming BSC handover can be:

1) Equipment failure;

2) Resource congestion or resource unavailable;

3) Message content invalid;

4) Timers time out;

5) Error detected during BSS internal processing, e.g. storing a message in buffer failed, No. of target

cell invalid, message decoding failed;

6) MSC informs BSC to clear resources.

Measurement point:1) During the procedure of interBSC handover, the target BSC processes the

HANDOVER REQUEST message. This item is measured if the following abnormalities occur, and in this case, BSC will send a HANDOVER FAILURE message to MSC: message decoding failed, service type is speech or data but no CIC contained or the contained CIC does not belong to the target BSC.

2) During the procedure of interBSC handover, the target BSC obtains the specified CIC which is presented in the HANDOVER REQUEST message.

54



This item is measured when the following abnormalities occur, and in this case, BSC will send a HANDOVER FAILURE message to MSC: the state of the specified CIC is busy or abnormal, dismatching between circuit pool and channel rate type or speech version.

3) During the procedure of interBSC handover, the target BSC sends a HANDOVER FAILURE message to MSC for AM/CM net-drive fails. This item is measured in this case send a HANDOVER FAILURE message to.

4) During the procedure of interBSC handover, the target BSC will check the incoming BSC handover conditions. This item is measured when abnormalities are detected, and BSC will at the same time send a HANDOVER FAILURE message to MSC. The abnormalities include: Service type is data but the channel rate type is unknown, fail to request channel, ciphering algorithm is not supported.

5) During the procedure of interBSC handover, the target BSC fails to send a CHANNEL ACTIVATION message. This item is measured in this case, and at the same time, BSC sends a HANDOVER FAILURE message to MSC.

6) During the procedure of interBSC handover, the target BSC receives the CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGEmessage. This item is measured in this case, and at the same time, BSC will send a HANDOVER FAILURE message to MSC, as shown in Figure 3-29 A1.

7) During the procedure of interBSC handover, the target BSC receives CONNECTION FAILURE INDICATION from BTS after receiving HANDOVER DETECTION. . This item is measured in this case, and at the same time, BSC will send a HANDOVER FAILURE message to MSC, as shown in Figure 3-29 A2.

8) During the procedure of interBSC handover, the target BSC receives the HANDOVER DETECTION message or HANDOVER COMPLETE. This item is measured when the decoding of these messages failed, and in this case, BSC will send a CLEAR REQUEST message to MSC.

9) During the procedure of interBSC handover, the target BSC sends a HANDOVER COMPLETE message to MSC. This item is measured when BSC fails to send this message, and in this case, BSC will send a CLEAR REQUEST message to MSC.

10) During the procedure of interBSC handover, the target BSC starts timer waiting for the CHANNEL ACTIVATION ACKNOWLEDGEmessage. This item is measured when this timer times out, and in this case, BSC will send a HANDOVER FAILURE message to MSC.

11) During the procedure of interBSC handover, the target BSC starts timer Tqho (maximum allowed queuing time for handover). This item is measured when the timer times out, and in this case, BSC will send a HANDOVER FAILURE message to MSC.

55



12) During the procedure of interBSC handover, the target BSC starts timer waiting for HANDOVER DETECTION or timer waiting for HANDOVER COMPLETE. This item is measured when these timers time out, and in this case, BSC will send a CLEAR REQUEST message to MSC.

13) During the procedure of interBSC handover, the target BSC receives the CLEAR COMMAND message from MSC. This item is measured in this case, as shown in Figure 3-29 A3~A5.

Formula: none.

MS BTS New BSC MSC/VLR

HANDOVER COMPLETE

HANDOVER COMMAND

HANDOVER COMPLETE

CONN FAIL IND

CONN FAIL IND

HANDOVER DETECTION

A1

New Channel

HANDOVER REQUEST

Old BSC

HANDOVER REQUIRED

CHAN ACT

CHAN ACT ACK

CHAN ACT NACK

New Channel

A2

CLEAR COMMAND

CLEAR COMMAND

CLEAR COMMAND

A3

A4

A5

B1

B2

A3 C1

C2

C3

D1

A1~A5 : Unsuccessful incoming BSC handover

B1~B2: Unsuccessful incoming BSC handover (equipment failure)

C1~C3: Unsuccessful incoming BSC handover (other causes)

D1 : Unsuccessful incoming BSC handover (NACK)

Figure 3-29 Unsuccessful incoming BSC handover

LXVII. Unsuccessful incoming BSC handovers (equipment failure)

Description: This item measures the times of unsuccessful incoming BSC handovers due to equipment failure during the procedure of interBSC handover. Related items: Unsuccessful incoming BSC handovers .

Measurement point: 1) During the procedure of interBSC handover, the target BSC processes the

HANDOVER REQUEST message. This item is measured when service type is speech or data but the contained CIC does not belong to the target BSC, and in this case, BSC will send a HANDOVER FAILURE message to MSC.

56



2) During the procedure of interBSC handover, the target BSC sends a HANDOVER FAILURE message to MSC for AM/CM net-drive fails. This item is measured in this case, and at the same time, BSC will send a HANDOVER FAILURE message to MSC.

3) During the procedure of interBSC handover, the target BSC will check the incoming BSC handover conditions. This item is measured when abnormalities of equipment failure are detected, and BSC will at the same time send a HANDOVER FAILURE message to MSC.

4) During the procedure of interBSC handover, the target BSC fails to send a CHANNEL ACTIVATION message. This item is measured in this case, and at the same time, BSC sends a HANDOVER FAILURE message to MSC.

5) During the procedure of interBSC handover, when the target BSC receives the CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE message, this item is measured in this case, and at the same time, BSC will send a HANDOVER FAILURE message to MSC, as shown in Figure3-29 B1.

6) During the procedure of interBSC handover, the target BSC receives the HANDOVER DETECTION message, and then receives the CONNECTION FAILURE INDICATION message. This item is measured in this case, and at the same time, THE BSC will send a HANDOVER FAILURE message to MSC, as shown in Figure 3-29 B2.

7) During the procedure of interBSC handover, the target BSC starts the timer waiting for the CHANNEL ACTIVATION ACKNOWLEDGE message. This item is measured when this timer times out, and in this case, BSC will send a HANDOVER FAILURE message to MSC.

Formula: none.

LXVIII. Unsuccessful incoming BSC handovers (requested terrestrial resource unavailable)

Description: This item measures the times of unsuccessful incoming BSC handovers due to requested terrestrial resource unavailable during the procedure of interBSC handover. Related items: Unsuccessful incoming BSChandovers .

Measurement point: During the procedure of interBSC handover, the target BSC obtains the specified CIC in the handover request. This item is measured when the specified CIC is abnormal, and in this case, BSC will send a HANDOVER FAILURE message to MSC.

Formula: none.

57



LXIX. Unsuccessful incoming BSC handovers (Terrestrial Circuit Already Allocated)

Description: This item measures the times of unsuccessful incoming BSC handovers due to terrestrial circuit already allocated during the procedure of interBSC handover. Related items: Unsuccessful incoming BSC handovers .

Measurement point: During the procedure of interBSC handover, the target BSC obtains the specified CIC in the handover request. This item is measured when the specified CIC is busy, and in this case, BSC will send a HANDOVER FAILURE message to MSC.

Formula: none.

LXX. Unsuccessful incoming BSC handovers (Invalid Message Contents)

Description: This item measures the times of unsuccessful incoming BSC handovers due to invalid message contents during the procedure of interBSC handover. Related items: Unsuccessful incoming BSC handovers .

Measurement point: During the procedure of interBSC handover, the target BSC will check the incoming BSC handover conditions. This item is measured when service type is data but the channel rate type is unknown, and BSC will at the same time send a HANDOVER FAILURE message to MSC.

Formula: none.

LXXI. Unsuccessful incoming BSC handovers (no radio resource available)

Description: This item measures the times of unsuccessful incoming BSC handovers due to no radio resource available during the procedure of interBSC handover. Related items: Unsuccessful incoming BSC handovers .

Measurement point: 1) During the procedure of interBSC handover, the target BSC will check the

incoming BSC handover conditions. This item is measured when there is no channel available, and BSC will at the same time send a HANDOVER FAILURE message to MSC. For example, requesting for channel failed.

2) During the procedure of interBSC handover, the target BSC starts the timer Tqho (maximum allowed queuing time for handover). This item is measured when this timer times out, and in this case, BSC will send a HANDOVER FAILURE message to MSC.

Formula: none.

LXXII. Unsuccessful incoming BSC handovers (other causes)

Description: This item measures the times of unsuccessful incoming BSC handovers due to other causes rather than equipment failure, requested terrestrial resource unavailable, terrestrial circuit already allocated, invalid message contents and no radio resource available during the procedure of

58



interBSC handover. These causes include sending message failed, timeout of timer waiting for HANDOVER DETECTION or timer waiting for the HANDOVER COMPLETE message. Related items: Unsuccessful incomingBSC handovers.

Measurement point:1) During the procedure of interBSC handover, the target BSC processes the

HANDOVER REQUEST message. This item is measured if the following abnormalities occur, and in this case, BSC will send a HANDOVER FAILURE message to MSC: message decoding failed, service type is speech or data but no CIC contained.

2) During the procedure of interBSC handover, the target BSC obtains the specified CIC in the handover request. This item is measured when the following abnormalities occur, and in this case, BSC will send a HANDOVER FAILURE message to MSC: dismatching between circuit pool and channel rate type or voice version.

3) During the procedure of interBSC handover, the target BSC will check the incoming BSC handover conditions. This item is measured when abnormalities are detected, and BSC will at the same time send a HANDOVER FAILURE message to MSC. The abnormalities include ciphering algorithm not supported.

4) During the procedure of interBSC handover, the target BSC receives the HANDOVER DETECTION message or the HANDOVER COMPLETE message. This item is measured when the decoding of this message failed, and in this case, BSC will send a CLEAR REQUEST message to MSC.

5) During the procedure of interBSC handover, the target BSC sends a HANDOVER COMPLETE message to MSC. This item is measured when BSC fails to send this message, and in this case, BSC will send a CLEAR REQUEST message to MSC.

6) During the procedure of interBSC handover, the target BSC starts the timer waiting for HANDOVER DETECTION or HANDOVER COMPLETE. This item is measured when this timer times out, and in this case, BSC will send a CLEAR REQUEST message to MSC.

7) During the procedure of interBSC handover, the target BSC receives CLEAR COMMAND from MSC. This item is measured in this case, as shown in Figure 3-29 C1-C3.

Formula: none.

59



LXXIII. Unsuccessful channel activation in incoming BSC handovers (NACK)

Description: This item measures the times of unsuccessful incoming handovers due to unsuccessful channel activation in incoming BSC handovers (CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE received) which is a kind of equipment failure. Related items: Unsuccessful incoming BSChandovers and Unsuccessful incoming BSC handovers (equipment failure ).

Measurement point: This item is measured when the target BSC that is waiting for the CHANNEL ACTIVATION ACKNOWLEDGE message receives the CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE message during the procedure of interBSC handover. In this case, BSC will send a HANDOVER FAILURE message to MSC, as shown in Figure 3-29 D1.

Formula: none.

LXXIV. Channel activation timeout in incoming BSC handovers

Description: This item measures the times of unsuccessful incoming handovers due to timeout of timer for waiting for the CHANNEL ACTIVATION ACKNOWLEDGE message which is a kind of equipment failure. Related items: Unsuccessful incoming BSC handovers and Unsuccessful incomingBSC handovers (equipment failure) .

Measurement point: This item is measured when timer waiting for the CHANNEL ACTIVATION ACKNOWLEDGE message times out in the target BSC, and the BSC will at the same time send a HANDOVER FAILURE message to MSC.

Formula: none.

LXXV. Incoming BSC handovers

Description: After the target BSC receives the HANDOVER REQUEST message from MSC, it checks the conditions of incoming handover. If the check passes, the target BSC will request channel resource, generate and store the HANDOVER COMMAND message in buffer, and at the same time, it will send CHANNEL ACTIVATION to BTS. After receiving CHANNEL ACTIVATION ACKNOWLEDGE, the BSC packs the HANDOVER COMMAND message into HANDOVER REQUEST ACKNOWLEDGE, which will then be sent to MSC. MSC transfers this message to the source BSC, and the source BSC sends the HANDOVER COMMAND message to MS. This item measures the times of target BSC sending HANDOVER REQUEST ACKNOWLEDGE to MSC. This item, togerther with Attempted incoming BSC handovers , helps the user know the unsuccessful handovers due to abnormalities during the preparation of new channel in target cell, together with Successful incoming

60



BSC handovers, know unsuccessful handovers due to radio interface abnormal. Related items: Intercell handovers and Intra BSC handovers .

Measurement point: During the procedure of interBSC handover, the target BSC receives the CHANNEL ACTIVATION ACKNOWLEDGE message, and then sends to MSC the HANDOVER REQUEST ACKNOWLEDGE message which contains the HANDOVER COMMAND message, a message to be sent to MS. This item is measured in this case, as shown in Figure 3-30 A1.

Formula: none.

MS BTS BSC MSC/VLR

HANDOVER COMPLETE

HANDOVER DETECTION

CHANNEL ACT

CHAN ACT ACK

HANDOVER COMPLETE

HANDOVER REQ ACK

A1

A1: Incoming BSC handover

Figure 3-30 Incoming BSC handover

LXXVI. Attempted outgoing BSC handovers

Description: InterBSC handover is normally triggered by receiving strength, receiving quality, TA, traffic load, Response to MSC invocation, DIRECTED RETRY, rapid rxlevel drop, better cell or O&M intervention. The source cell and target cell are from different BSCs. The source BSC sends HANDOVER REQUIRED to MSC to initiate a handover. This message contains a list of candidate cells for handover. At this stage, the source BSC does not know the target cell which is selected by MSC or whether the selected cell is congested. It only records the first cell in the candidate list as the default target cell. This item measures the times of source BSC notifying MSC to initiate handover attempts. This item reflects the frequece of local BSC initiating interBSC handover. Together with Successful outgoing BSC handovers , this item shows the performance of the local BSC initiating interBSC handover. Related items: Attempted intracell handovers , Attempted intercell handovers and Attempted incoming BSC handovers .

Measurement point: After handover algorithm decision, the source BSC sends HANDOVER REQUIRED to MSC. This item is measured in this case, as shown in Figure 3-31 A1.

Formula: none.

61



MS BSC2BSC1 MSC/VLR

HANDOVER REQUIRED

HANDOVER REQUEST

HANDOVER REQ ACK

HANDOVER COMMAND

HANDOVER COMMANDHANDOVER DETECT

HANDOVER COMPLETE

CLEAR COMPLETE

A1, B1, C1

CLEAR COMMAND

D1, E1, F1

A1: Attempted outgoing BSC handovers

B1: Attempted outgoing BSC handovers (from 900)

C1: Attempted outgoing BSC handovers (from 1800))

D1: Outgoing BSC handovers

E1: Attempted outgoing BSC handovers (900-1800)

F1: Attempted outgoing BSC handovers (1800-900)

Figure 3-31 Attempted outgoing BSC handover

LXXVII. Attempted outgoing BSC handovers (from 900)

Description: InterBSC handover is normally triggered by receiving strength, receiving quality, TA, traffic load, Response to MSC invocation, DIRECTED RETRY, rapid rxlevel drop, better cell or O&M intervention. The source cell and target cell are from different BSCs. The source BSC sends HANDOVER REQUIRED to MSC to initiate a handover. This message contains a list of candidate cells for handover. At this stage, the source BSC does not know the target cell which is selected by MSC or whether the selected cell is congested. It only knows the source cell (GSM900) that initiates this handover. This item measures the times of source BSC (the source cell is GSM900 cell) notifying MSC to initiate handover attempts. This item reflects the frequece of GSM900 cells of objective BSC initiating interBSC handover. Together with Successfuloutgoing BSC handovers (from 900) , this item shows the performance of this type handover. Related items: Attempted outgoing BSC handovers .

62



Note:



from 1 to 124.


is from 512 to 885.

Measurement point: After handover algorithm decision, the source BSC (the source cell is GSM900 cell) sends HANDOVER REQUIRED to MSC. This item is measured in this case, as shown in Figure 3-31 B1.

Formula: none.

LXXVIII. Attempted outgoing BSC handovers (from 1800)

Description: InterBSC handover is normally triggered by receiving strength, receiving quality, TA, traffic load, Response to MSC invocation, DIRECTED RETRY, rapid rxlevel drop, better cell or O&M intervention. The source cell and target cell are from different BSCs. The source BSC sends HANDOVER REQUIRED to MSC to initiate a handover. This message contains a list of candidate cells for handover. At this stage, the source BSC does not know the target cell which is selected by MSC or whether the selected cell is congested. It only knows the source cell (GSM1800) that initiates this handover. This item measures the times of source BSC (the source cell is GSM1800 cell) notifying MSC to initiate handover attempts. This item reflects the frequece of GSM1800 cells of local BSC initiating interBSC handover. Together with Successfuloutgoing BSC handovers (from 1800) , this item shows the performance of this type handover. Related items: Attempted outgoing BSC handovers .

Note:



from 1 to 124.


is from 512 to 885.

Measurement point: After handover algorithm decision, the source BSC (the source cell is GSM900 cell) sends HANDOVER REQUIRED to MSC. This item is measured in this case, as shown in Figure 3-31 C1.

63



Formula: none.

LXXIX. Attempted outgoing BSC handovers (9001800)

Description: InterBSC handover is normally triggered by receiving strength, receiving quality, TA, traffic load, Response to MSC invocation, DIRECTED RETRY, rapid rxlevel drop, better cell or O&M intervention. The source cell and target cell are from different BSCs. This item reflects the frequece of local BSC initiating interBSC handover from GSM900 cell to GSM1800 cell. Together with Successful outgoing BSC handovers (9001800) , this item shows the performance of this type handover. Related items: Attempted outgoing BSChandovers and Outgoing BSC handovers .

Note:

1) The source BSC sends HANDOVER REQUIRED to MSC to initiate handover. This message

contains a list of candidate cells for handover. At this stage, the source BSC does not know the target

cell which is selected by MSC or whether the selected cell is congested. It only knows the source cell

(GSM900) that initiates this handover. If the item is measured at this moment, the result is not

precise. The target cell and its system type can only be known after receiving the first response

message HANDOVER COMMAND from MSC.



from 1 to 124.


is from 512 to 885.

Measurement point: During the procedure of interBSC handover from GSM900 cell to GSM1800 cell, the source BSC receives the HANDOVER COMMAND message from MSC. This item is measured in this case, as shown in Figure 3-31 E1.

Formula: none.

LXXX. Attempted outgoing BSC handovers (1800900)

Description: InterBSC handover is normally triggered by receiving strength, receiving quality, TA, traffic load, Response to MSC invocation, DIRECTED RETRY, rapid rxlevel drop, better cell or O&M intervention. The source cell and target cell are in different BSCs. This item reflects the frequece of local BSC initiating interBSC handover from GSM1800 cell to GSM900 cell. Together with Successful outgoing BSC handovers (1800900) , this item shows the

64



performance of this type handover. Related items: Attempted outgoing BSChandovers and Outgoing BSC handovers .

Note:

1) The source BSC sends HANDOVER REQUIRED to MSC to initiate handover. This message

contains a list of candidate cells for handover. At this stage, the source BSC does not know the target

cell which is selected by MSC or whether the selected cell is congested. It only knows the source cell

(GSM1800) that initiates this handover. If the item is measured at this moment, the result is not

precise. The target cell and its system type can only be known after receiving the first response

message HANDOVER COMMAND from MSC.



from 1 to 124.


is from 512 to 885.

Measurement point: During the procedure of interBSC handover from GSM1800 cell to GSM900 cell, the source BSC receives the HANDOVER COMMAND message from MSC. This item is measured in this case, as shown in Figure 3-31 F1.

Formula: none.

LXXXI. Successful outgoing BSC handovers

Description: During the procedure of interBSC handover, the source BSC sends a HANDOVER COMMAND message to MS. After successfully accessed the target cell, MSC sends CLEAR COMMAND (cause: handover success) to source BSC to clear the previous resources. This handover successfully ends here. Together with Attempted outgoing BSC handovers, this item shows the performance of this type handover. Related items: Successful intracell handovers , Successful intercell handovers and Successful incoming BSC handovers .

Measurement point: During the procedure of interBSC handover, the source BSC receives CLEAR COMMAND (cause: handover success) from MSC. This item is measured in this case, as shown in Figure 3-32 A1.

Formula: none.

65



MS BSC2BSC1 MSC/VLR

HANDOVER REQUIRED

HANDOVER REQUEST

HANDOVER REQ ACK

HANDOVER COMMAND


HANDOVER COMPLETE

CLEAR COMPLETEA1, B1, C1 , D1, E1

CLEAR COMMAND

A1: Successful outgoing BSC handover

B1: Successful outgoing BSC handover (from 900)

C1: Successful outgoing BSC handover (from 1800))

D1: Successful outgoing BSC handover (900-1800)

E1: Successful outgoing BSC handover (1800-900)

Figure 3-32 Successful outgoing BSC handover

LXXXII. Successful outgoing BSC handovers (from 900)

Description: During the procedure of interBSC handover, the source BSC sends a HANDOVER COMMAND message to MS. After successfully accessed the target cell, MS sends CLEAR COMMAND (cause: handover success) to source BSC to clear the previous resources. This handover successfully ends here. This item measures the times of successful outgoing handover originated from GSM900 cell. Together with Attempted outgoingBSC handovers (from 900) , this item shows the performance of this type handover. Related items: Successful outgoing BSC handovers .

Note:



from 1 to 124.


is from 512 to 885.

66



Measurement point: During the procedure of interBSC handover, the source BSC (source cell is GSM900 cell) receives CLEAR COMMAND (cause: handover success) from MSC. This item is measured in this case, as shown in Figure 3-32 B1.

Formula: none.

LXXXIII. Successful outgoing BSC handovers (from 1800)

Description: During the procedure of interBSC handover, the source BSC sends a HANDOVER COMMAND message to MS. After successfully accessed the target cell, MS sends CLEAR COMMAND (cause: handover success) to source BSC to clear the previous resources. This handover successfully ends here. This item measures the times of successful outgoing handover originated from GSM1800 cell. Together with Attempted outgoingBSC handovers (from 1800) , this item shows the performance of this type handover. Related items: Successful outgoing BSC handovers .

Measurement point: During the procedure of interBSC handover, the source BSC (source cell is GSM1800 cell) receives CLEAR COMMAND (cause: handover success) from MSC. This item is measured in this case, as shown in Figure 3-32 C1.

Formula: none.

LXXXIV. Successful outgoing BSC handovers (9001800)

Description: During the procedure of interBSC handover, the source BSC sends a HANDOVER COMMAND message to MS. After successfully accessed the target cell, MS sends CLEAR COMMAND (cause: handover success) to source BSC to clear the previous resources. This handover successfully ends here. This item measures the times of successful outgoing handover from GSM900 cell to GSM1800 cell. Together with Attemptedoutgoing BSC handovers (9001800) , this item shows the performance of this type handover. Related items: Successful outgoing BSC handovers .

Note:



from 1 to 124.


is from 512 to 885.

67



Measurement point: During the procedure of interBSC handover from GSM900 cell to GSM1800 cell, the source BSC receives CLEAR COMMAND (cause: handover success) from MSC. This item is measured in this case, as shown in Figure 3-32 D1.

Formula: none.

LXXXV. Successful outgoing BSC handovers (1800900)

Description: During the procedure of interBSC handover, the source BSC sends a HANDOVER COMMAND message to MS. After successfully accessed the target cell, MS sends CLEAR COMMAND (cause: handover success) to source BSC to clear the previous resources. This handover successfully ends here. This item measures the times of successful outgoing handover from GSM1800 cell to GSM900 cell. Together with Attemptedoutgoing BSC handovers (1800900) , this item shows the performance of this type handover. Related items: Successful outgoing BSC handovers .

Note:



from 1 to 124.


is from 512 to 885.

Measurement point: During the procedure of interBSC handover from GSM1800 cell to GAM900 cell, the source BSC receives CLEAR COMMAND (cause: handover success) from MSC. This item is measured in this case, as shown in Figure 3-32 E1.

Formula: none.

LXXXVI. Outgoing BSC handovers

Description: During the procedure of interBSC handover, the target BSC finishes allocating the new channel and generates the message HANDOVER COMMAND, which is forwarded by MSC to the source BSC. After receiving this message, the source BSC sends it to MS. This item measures the times of the source BSC sending HANDOVER COMMAND. Together with Attemptedoutgoing BSC handovers , this item shows the situation of unsuccessful handovers due to abnormalities in the procedure of new channel preparation, and with Successful outgoing BSC handovers , it shows the situation of

68



unsuccessful handovers due to radio interface abnormal. Related items: Incoming BSC handovers , Intra BSC handovers and Intercell handovers .

Measurement point: This item is measured when the source BSC receives HANDOVER COMMAND from MSC, as shown in Figure 3-31 D1.

Formula: none.

LXXXVII. Unsuccessful outgoing BSC handovers with successful reversion

Description: During the procedure of interBSC handover, the source BSC sends a HANDOVER COMMAND message to MS. If the MS cannot access the target cell due to poor radio environment or handover parameter incorrect, it will send HANDOVER FAILURE (cause: Radio interface failure, reversion to old channel) to the source BSC via the previous channel. BSC then forwards this message to MSC. MSC requests the target BSC to clear the involved resources. The connecting between the source BSC and MS remains the same. This item measures the times of unsuccessful handover with successful reversion. Related items: Unsuccessful incoming BSC handovers , Unsuccessful outgoing BSC handovers with unsuccessful reversion and Unsuccessful BSC internal handovers with successful reversion .

Measurement point: This item is measured when the source BSC receives HANDOVER FAILURE (cause: Radio interface failure, reversion to old channel) from MS during the procedure of interBSC handover, as shown in Figure 3-33 A1.

Formula: none.

BTS BSC1 MSC/VLR

HANDOVER REQUIRED

HANDOVER COMMAND

CLEAR COMMANDCLEAR COMPLETE

A1 HANDOVER FAILURE

HANDOVER FAILURE

CLEAR COMMAND

CONN FAIL IND

ERROR INDICATION

HANDOVER COMMAND

B1 B2

B3

A1: Unsuccessful outgoing BSC handovers with successful reversion

B1~B3: Unsuccessful outgoing BSC handovers with unsuccessful reversion

Figure 3-33 Unsuccessful outgoing BSC handovers

69



LXXXVIII. Unsuccessful outgoing BSC handovers with unsuccessful reversion

Description: During the procedure of interBSC handover, after the source BSC sends the HANDOVER COMMAND message to MS, the connection between MS and the source BSC is terminated before the connection established between MS and the target BSC due to poor radio environment or equipment failure. When BSC detects this situation, it will send a CLEAR REQUEST message to MSC to request release the previous resources and the involved resources during handover. This handover failed and the original service cannot be restored in the source BSC. This item measures the times of unsuccessful handover with unsuccessful reversion. Related items: Unsuccessful incoming BSC handovers , Unsuccessful outgoing BSChandovers with successful reversion and Unsuccessful BSC internalhandovers with unsuccessful reversion .

Measurement point:1) This item is measured when the source BSC receives CONNECTION

FAILURE INDICATION from BTS during the procedure of interBSC handover, as shown in Figure 3-33 B1.

2) This item is measured when the source BSC receives ERROR INDICATION from BTS during the procedure of interBSC handover, as shown in Figure 3-33 B2.

3) This item is measured when the source BSC receives CLEAR COMMAND (cause: not handover success) from MSC during the procedure of interBSC handover, as shown in Figure 3-33 B3.

4) This item is measured when the source BSC waiting for CLEAR COMMAND (cause: handover success) from MSC times out during the procedure of interBSC handover.

Formula: none.

LXXXIX. Attempted handovers for uplink quality

Description: At the beginning of a handover, BSC will receive Handover Indication from LAPD module. This message contains the cause value of the handover, according to which the BSC measures all kinds of handover attempts with specific handover cause. This item measures the times of handovers (including internal intracell handover, internal intercell handover and outgoing interBSC handover) caused by uplink signal quality. This item shows the frequency of handover caused by uplink signal quality in the BSC. Together with Successful handovers for uplink quality , this item shows the performance of handovers of this type. Related items: Attempted intracellhandovers , Attempted intercell handovers and Attempted outgoing BSChandovers .

70



Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (including internal intracell handover and internal intercell handover) or HANDOVER REQUIRED (outgoing interBSC handover) due to uplink signal quality. This item is measured in this case.

Formula: none.

XC. Attempted handovers for downlink quality

Description: At the beginning of a handover, BSC will receive Handover Indication from LAPD module. This message contains the cause value of the handover, according to which the BSC measures all kinds of handover attempts with specific handover cause. This item measures the times of handovers (including Internal intracell handover, Internal intercell handover and outgoing interBSC handover) caused by downlink signal quality. This item shows the frequency of handover caused by downlink signal quality. Together with Successful handovers for downlink quality , this item shows the performance of handovers of this type. Related items: Attempted intracellhandovers , Attempted intercell handovers and Attempted outgoing BSChandovers .

Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (Internal intracell handover and internal intercell handover) or HANDOVER REQUIRED (interBSC handover) due to downlink signal quality. This item is measured in this case.

Formula: none.

XCI. Attempted handovers for uplink strength

Description: At the beginning of a handover, BSC will receive Handover Indication from LAPD module. This message contains the cause value of the handover, according to which the BSC measures all kinds of handover attempts with specific handover cause. This item measures the times of handovers (including Internal intracell handover, Internal intercell handover and outgoing interBSC handovers) caused by uplink signal strength. This item shows the frequency of handover caused by uplink signal strength. Together with Successful handovers for uplink strength , this item shows the performance of handovers of this type. Related items: Attempted intracellhandovers , Attempted intercell handovers and Attempted outgoing BSChandovers .

Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (Internal intracell handover and internal intercell handover) or HANDOVER REQUIRED (interBSC handover) due to uplink signal strength. This item is measured in this case.

Formula: none.

71



XCII. Attempted handovers for downlink strength

Description: At the beginning of a handover, BSC will receive Handover Indication from LAPD module. This message contains the cause value of the handover, according to which the BSC measures all kinds of handover attempts with specific handover cause. This item measures the times of handovers (including Internal intracell handover, Internal intercell handover and outgoing interBSC handover) caused by downlink signal strength. This item shows the frequency of handover caused by downlink signal strength. Together with Successful handovers for downlink strength , this item shows the performance of handovers of this type. Related items: Attempted intracellhandovers , Attempted intercell handovers and Attempted outgoing BSChandovers .

Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (Internal intracell handover and internal intercell handover) or HANDOVER REQUIRED (interBSC handover) due to downlink signal strength. This item is measured in this case.

Formula: none.

XCIII. Attempted handovers for timing advance

Description: At the beginning of a handover, BSC will receive Handover Indication from LAPD module. This message contains the cause value of the handover, according to which the BSC measures all kinds of handover attempts with specific handover cause. This item measures the times of handovers (including Internal intercell handover and outgoing interBSC handover) caused by TA (because a subscriber moves far away from the serving cell but close to the target cell while talking, so the signal strength and the signal quality in serving cell drops and a handover will be triggered.). This item shows the frequency of handover caused by TA. Together with Successful handovers for timing advance , this item shows the performance of handovers of this type. Related items: Attempted intracell handovers , Attempted intercell handovers and Attempted outgoing BSC handovers .

Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (internal intercell handover) or HANDOVER REQUIRED (interBSC handover) due to TA. This item is measured in this case.

Formula: none.

XCIV. Attempted handovers for better cell

Description: At the beginning of a handover, BSC will receive Handover Indication from LAPD module. This message contains the cause value of the handover, according to which the BSC measures all kinds of handover attempts with specific handover cause. This item measures the times of

72



handovers (including Internal intercell handover and outgoing interBSC handover) caused by "better cell" (adjacent cell with lower path loss (PBGT) or higher priority). This item shows the frequency of handover caused by "better cell". Together with Successful handovers for better cell , this item shows the performance of handovers of this type. Related items: Attempted intracellhandovers , Attempted intercell handovers and Attempted outgoing BSChandovers .

Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (internal intercell handover) or HANDOVER REQUIRED (interBSC handover) due to "better cell". This item is measured in this case.

Formula: none.

XCV. Attempted handovers for traffic load

Description: At the beginning of a handover, BSC will receive Handover Indication from LAPD module. This message contains the cause value of the handover, according to which the BSC measures all kinds of handover attempts with specific handover cause. This item measures the times of handovers (including Internal intercell handover and outgoing interBSC handover) caused by traffic load. This item shows the frequency of handover caused by traffic load. Together with Successful handovers for traffic load , this item shows the performance of handovers of this type. Related items: Attempted intracell handovers , Attempted intercell handovers and Attemptedoutgoing BSC handovers .

Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (internal intercell handover) or HANDOVER REQUIRED (interBSC handover) due to traffic load. This item is measured in this case.

Formula: none.

XCVI. Attempted handovers for rapid rxlevel drop

Description: At the beginning of a handover, BSC will receive Handover Indication from LAPD module. This message contains the cause value of the handover, according to which the BSC measures all kinds of handover attempts with specific handover cause. This item measures the times of handovers (including Internal intercell handover and outgoing interBSC handover) caused by rapid rxlevel drop. This item shows the frequency of handover caused by rapid rxlevel drop. Together with Successful handoversfor rapid rxlevel drop , this item shows the performance of handovers of this type. Related items: Attempted intracell handovers , Attempted intercellhandovers , Attempted outgoing BSC handovers .

73



Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (internal intercell handover) or HANDOVER REQUIRED (interBSC handover) due to traffic load. This item is measured in this case.

Formula: none.

XCVII. Attempted handovers for response to MSC invocation

Description: At the beginning of a handover, BSC will receive Handover Indication from LAPD module. This message contains the cause value of the handover, according to which the BSC measures all kinds of handover attempts with specific handover cause. This item measures the times of handovers (including Internal intercell handover and outgoing interBSC handover) caused by Response to MSC invocation (MSC sending HANDOVER CANDIDATE ENQUIRY to BSC which causes handovers of multiple MSs in a cell). This item shows the frequency of handover caused by Response to MSC invocation. Together with Successful handovers forresponse to MSC invocation , this item shows the performance of handovers of this type. Related items: Attempted intracell handovers , Attempted intercellhandovers and Attempted outgoing BSC handovers .

Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (internal intercell handover) or HANDOVER REQUIRED (interBSC handover) due to Response to MSC invocation. This item is measured in this case.

Formula: none.

XCVIII. Attempted handovers for O&M intervention

Description: At the beginning of a handover, BSC will receive Handover Indication from LAPD module. This message contains the cause value of the handover, according to which the BSC measures all kinds of handover attempts with specific handover cause. This item measures the times of handovers (including Internal intracell handover, Internal intercell handover and outgoing interBSC handover) caused by O&M intervention (operation on O&M console which causes handovers, such as forced handover, no call drop blocking (blocking channels, TRXs and cells), BCCH mutual aid or TRX mutual aid). This item shows the frequency of handover caused by O&M intervention. Together with Successful handovers for O&M intervention , This item shows the performance of handovers of this type. Related items: Attempted intracellhandovers , Attempted intercell handovers and Attempted outgoing BSChandovers .

Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (Internal intracell handover and internal intercell handovers)

74



or HANDOVER REQUIRED (interBSC handover) due to O&M intervention. This item is measured in this case.

Formula: none.

XCIX. Attempted handovers from underlaid subcell to overlaid subcell

Description: Before originating handover, BSC will receive Handover Indication from LAPD module. This message contains the cause value of handover. The times of handover attempts of various can be measured according to this message. This item measures the times of handovers from underlaid subcell to overlaid subcell. This type of handover takes place only in IUO cells, and is regarded as a specific intracell handover. This item shows the frequency of handover from underlaid subcell to overlaid subcell. Together with Successfulhandovers from underlaid subcell to overlaid subcell , this item shows the performance of handovers of this type. Related items: Attempted intracellhandovers and Attempted handovers from overlaid subcell to underlaidsubcell .

Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (Internal intracell handover) due to handover from underlaid subcell to overlaid subcell. This item is measured in this case.

Formula: none.

C. Attempted handovers from overlaid subcell to underlaid subcell

Description: At the beginning of a handover, BSC will receive Handover Indication from LAPD module. This message contains the cause value of the handover, according to which the BSC measures all kinds of handover attempts with specific handover cause. This item measures the times of handovers from overlaid subcell to underlaid subcell. This type of handover takes place only in IUO cells, and is regarded as intracell handover. This item shows the frequency of handover from overlaid subcell to underlaid subcell. Together with Successful handovers from overlaid subcell to underlaidsubcell , this item shows the performance of handovers of this type. Related items: Attempted intracell handovers and Attempted handovers fromunderlaid subcell to overlaid subcell .

Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (Internal intracell handover) due to handover from overlaid subcell to underlaid subcell. This item is measured in this case.

Formula: none.

CI. Attempted handovers for directed retry

Description: At the beginning of a handover, BSC will receive Handover Indication from LAPD module. This message contains the cause value of the

75



handover, according to which the BSC measures all kinds of handover attempts with specific handover cause. This item measures the times of handovers (including Internal intercell handover and outgoing interBSC handover) caused by directed retry (a handover triggered because the current cell is congested during the procedure of assignment). This item shows the frequency of handover caused by directed retry. Together with Successfulhandovers for directed retry , this item shows the performance of handovers of this type. Related items: Attempted intercell handovers and Attemptedoutgoing BSC handovers .

Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (internal intercell handovers) or HANDOVER REQUIRED (interBSC handover) due to DIRECTED RETRY. This item is measured in this case.

Formula: none.

CII. Attempted handovers for other causes

Description: At the beginning of a handover, BSC will receive Handover Indication from LAPD module. This message contains the cause value of the handover, according to which the BSC measures all kinds of handover attempts with specific handover cause. This item measures the times of handovers (including Internal intracell handover, Internal intercell handover and outgoing interBSC handover) caused by other causes (such as fast moving, handover cause being abnormal value). This item shows the frequency of handover caused by other causes. Together with Successfulhandovers for other causes , this item shows the performance of handovers of this type. Related items: Attempted intracell handovers , Attempted intercellhandovers and Attempted outgoing BSC handovers .

Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (Internal intracell handover and internal intercell handovers) or HANDOVER REQUIRED (interBSC handover) due to other causes. This item is measured in this case.

Formula: none.

CIII. Extended cell attempted handovers for minimum timing advance

Description: Before originating handover, BSC will receive Handover Indication from LAPD module. This message contains the cause value of handover. The times of handover attempts of various can be measured according to this message. This item measures the times of handovers (interBSC handovers) caused by minimum timing advance (occurs only in single timeslot extended cells). This item shows the frequency of handover caused by minimum timing advance. Together with Extended cell successful handovers (minimum timing

76



advance) , this item shows the performance of handovers of this type. Related items: Attempted intracell handovers .

Measurement point: In single timeslot extended cells, handovers can be triggered by TA being smaller than minimum timing advance. After handover algorithm decision, BSC sends Intercell Handover Request (internal intercell handovers). This item is measured in this case.

Formula: none.

CIV. Successful handovers for uplink quality

Description: This item measures all successful handovers caused by uplink signal quality, including internal intracell handover, internal intercell handover and outgoing BSC handover. For intraBSC handovers, the message HANDOVER PERFORMED to MSC contains the handover cause. For interBSC handovers, the message HANDOVER REQUIRED corresponding to this handover contains the handover cause. Together with Attemptedhandovers for uplink quality , this item shows the performance of handovers of this type. Related items: Successful intracell handovers , Successfulintercell handovers and Successful outgoing BSC handovers .

Measurement point:1) This item is measured when the source BSC receives CLEAR COMMAND

(cause: handover success) from MSC during the procedure of interBSC handover caused by uplink signal quality.

2) During the procedure of Internal intracell handover/intercell handover caused by uplink signal quality, after MS accessed the target cell, BSC will send HANDOVER PERFORMED to MSC. This item is measured in this case.

Formula: none.

CV. Successful handovers for downlink quality

Description: This item measures all successful handovers caused by downlink signal quality, including Internal intracell handover, Internal intercell handover and outgoing handover. For intraBSC handovers, the message HANDOVER PERFORMED to MSC contains the handover cause. For interBSC handovers, the message HANDOVER REQUIRED corresponding to this handover contains the handover cause. Together with Attempted handovers for downlinkquality , this item shows the performance of handovers of this type. Related items: Successful intracell handovers , Successful intercell handovers and Successful outgoing BSC handovers .

Measurement point:

77



1) This item is measured when the source BSC receives CLEAR COMMAND (cause: handover success) from MSC during the procedure of interBSC handover caused by downlink signal quality.

2) During the procedure of Internal intracell handover/intercell handover caused by downlink signal quality, after MS accessed the target cell, BSC will send HANDOVER PERFORMED to MSC. This item is measured in this case.

Formula: none.

CVI. Successful handovers for uplink strength

Description: This item measures all successful handovers caused by uplink signal strength, including Internal intracell handover, Internal intercell handover and outgoing handover. For intraBSC handovers, the message HANDOVER PERFORMED to MSC contains the handover cause. For interBSC handovers, the message HANDOVER REQUIRED corresponding to this handover contains the handover cause. Together with Attempted handovers for uplinkstrength , this item shows the performance of handovers of this type. Related items: Successful intracell handovers , Successful intercell handovers and Successful outgoing BSC handovers .


(cause: handover success) from MSC during the procedure of interBSC handover caused by uplink signal strength.

2) During the procedure of Internal intracell handover/intercell handover caused by uplink signal strength, after MS accessed the target cell, BSC will send HANDOVER PERFORMED to MSC. This item is measured in this case.

Formula: none.

CVII. Successful handovers for downlink strength

Description: This item measures all successful handovers caused by downlink signal strength, including Internal intracell handover, Internal intercell handover and outgoing handover. For intraBSC handovers, the message HANDOVER PERFORMED to MSC contains the handover cause. For interBSC handovers, the message HANDOVER REQUIRED corresponding to this handover contains the handover cause. Together with Attempted handovers for downlinkstrength , this item shows the performance of handovers of this type. Related items: Successful intracell handovers , Successful intercell handovers and Successful outgoing BSC handovers .

Measurement point:

78



1) This item is measured when the source BSC receives CLEAR COMMAND (cause: handover success) from MSC during the procedure of interBSC handover caused by downlink signal strength.

2) During the procedure of Internal intracell handover/intercell handover caused by downlink signal strength, after MS accessed the target cell, BSC will send HANDOVER PERFORMED to MSC. This item is measured in this case.

Formula: none.

CVIII. Successful handovers for timing advance

Description: This item measures all successful handovers caused by TA (because a subscriber moves far away from the serving cell but close to the target cell while talking, so the signal strength and the signal quality in serving cell drops and a handover will be triggered.), including Internal intercell handover and outgoing handover. For intraBSC handovers, the message HANDOVER PERFORMED to MSC contains the handover cause. For interBSC handovers, the message HANDOVER REQUIRED corresponding to this handover contains the handover cause. Together with Attemptedhandovers for timing advance , this item shows the performance of handovers of this type. Related items: Successful intercell handovers and Successful outgoing BSC handovers .


(cause: handover success) from MSC during the procedure of interBSC handover caused by TA.

2) During the procedure of BSC intercell handover caused by TA, after MS accessed the target cell, BSC will send HANDOVER PERFORMED to MSC. This item is measured in this case.

Formula: none.

CIX. Successful handovers for better cell

Description: This item measures all successful handovers caused by "better cell" (adjacent cell with lower path loss (PBGT) or higher priority), including Internal intercell handover and outgoing handover. For intraBSC handovers, the message HANDOVER PERFORMED to MSC contains the handover cause. For interBSC handovers, the message HANDOVER REQUIRED corresponding to this handover contains the handover cause. Together with Attempted handovers for better cell , this item shows the performance of handovers of this type. Related items: Successful intercell handovers and Successful outgoing BSC handovers .

Measurement point:

79



1) This item is measured when the source BSC receives CLEAR COMMAND (cause: handover success) from MSC during the procedure of interBSC handover caused by "better cell".

2) During the procedure of BSC intercell handover caused by "better cell", after MS accessed the target cell, BSC will send HANDOVER PERFORMED to MSC. This item is measured in this case.

Formula: none.

CX. Successful handovers for traffic load

Description: This item measures all successful handovers caused by traffic load, including Internal intercell handover and outgoing handover. For intraBSC handovers, the message HANDOVER PERFORMED to MSC contains the handover cause. For interBSC handovers, the message HANDOVER REQUIRED corresponding to this handover contains the handover cause. Together with Attempted handovers for traffic load , this item shows the performance of handovers of this type. Related items: Successfulintercell handovers and Successful outgoing BSC handovers .


(cause: handover success) from MSC during the procedure of interBSC handover caused by traffic load.

2) During the procedure of BSC intercell handover caused by traffic load, after MS accessed the target cell, BSC will send HANDOVER PERFORMED to MSC. This item is measured in this case.

Formula: none.

CXI. Successful handovers for rapid rxlevel drop

Description: This item measures all successful handovers caused by rapid rxlevel drop, including Internal intercell handover and outgoing handover. For intraBSC handovers, the message HANDOVER PERFORMED to MSC contains the handover cause. For interBSC handovers, the message HANDOVER REQUIRED corresponding to this handover contains the handover cause. Together with Attempted handovers for rapid rxlevel drop , this item shows the performance of handovers of this type. Related items: Successful intercell handovers and Successful outgoing BSC handovers .


(cause: handover success) from MSC during the procedure of interBSC handover caused by rapid rxlevel drop.

80



2) During the procedure of BSC intercell handover caused by rapid rxlevel drop, after MS accessed the target cell, BSC will send HANDOVER PERFORMED to MSC. This item is measured in this case.

Formula: none.

CXII. Successful handovers for response to MSC invocation

Description: This item measures all successful handovers caused by Response to MSC invocation (MSC sending HANDOVER CANDIDATE ENQUIRY to BSC which causes handovers of multiple MSs in a cell), including Internal intercell handover and outgoing handover. For intraBSC handovers, the message HANDOVER PERFORMED to MSC contains the handover cause. For interBSC handovers, the message HANDOVER REQUIRED corresponding to this handover contains the handover cause. Together with Attempted handovers for response to MSC invocation , this item shows the performance of handovers of this type. Related items: Successful intercellhandovers and Successful outgoing BSC handovers .


(cause: handover success) from MSC during the procedure of interBSC handover caused by Response to MSC invocation.

2) During the procedure of BSC intercell handover caused by Response to MSC invocation, after MS accessed the target cell, BSC will send HANDOVER PERFORMED to MSC. This item is measured in this case.

Formula: none.

CXIII. Successful handovers for O&M intervention

Description: This item measures all successful handovers caused by O&M intervention (operation on O&M console which causes handovers, such as forced handover, no call drop blocking (blocking channels, TRXs and cells), BCCH mutual aid or TRX mutual aid), including Internal intracell handover, Internal intercell handover and outgoing handover. For intraBSC handovers, the message HANDOVER PERFORMED to MSC contains the handover cause. For interBSC handovers, the message HANDOVER REQUIRED corresponding to this handover contains the handover cause. Together with Attempted handovers for O&M intervention, this item shows the performance of handovers of this type. Related items: Successful intracell handovers , Successful intercell handovers and Successful outgoing BSC handovers .


(cause: handover success) from MSC during the procedure of interBSC handover caused by O&M intervention.

81



2) During the procedure of BSC intracell/intercell handover caused by O&M intervention, after MS accessed the target cell, BSC will send HANDOVER PERFORMED to MSC. This item is measured in this case.

Formula: none.

CXIV. Successful handovers from underlaid subcell to overlaid subcell

Description: This item measures all successful handovers from underlaid subcell to overlaid subcell. This type of handover takes place only in IUO cells, which is a specific type of internal intracell handover. For intraBSC handovers, the message HANDOVER PERFORMED to MSC contains the handover cause. Together with Attempted handovers from underlaid subcell to overlaidsubcell , this item shows the performance of handovers of this type. Related items: Successful intracell handovers and Successful handovers fromoverlaid subcell to underlaid subcell .

Measurement point: During the procedure of handover from underlaid subcell to overlaid subcell, after MS accessed the overlaid subcell, BSC will send HANDOVER PERFORMED to MSC. This item is measured in this case.

Formula: none.

CXV. Successful handovers from overlaid subcell to underlaid subcell

Description: This item measures all successful handovers from overlaid subcell to underlaid subcell. This type of handover takes place only in IUO cells, which is a specific type of internal intracell handover. For intraBSC handovers, the message HANDOVER PERFORMED to MSC contains the handover cause. Together with Attempted handovers from overlaid subcell to underlaidsubcell , this item shows the performance of handovers of this type. Related items: Successful intracell handovers and Successful handovers fromunderlaid subcell to overlaid subcell .

Measurement point: During the procedure of handover from overlaid subcell to underlaid subcell, after MS accessed the underlaid subcell, BSC will send HANDOVER PERFORMED to MSC. This item is measured in this case.

Formula: none.

CXVI. Successful handovers for directed retry

Description: This item measures all successful handovers caused by directed retry (triggered the current cell is congested during the procedure of assignment), including Internal intercell handover and outgoing handover. For intraBSC handovers, the message HANDOVER PERFORMED to MSC contains the handover cause. For interBSC handovers, the message HANDOVER REQUIRED corresponding to this handover contains the handover cause. Together with Attempted handovers for directed retry , this

82



item shows the performance of handovers of this type. Related items: Successful intercell handovers and Successful outgoing BSC handovers .


(cause: handover success) from MSC during the procedure of interBSC handover caused by directed retry.

2) During the procedure of BSC intercell handover caused by directed retry, after MS accessed the target cell, BSC will send HANDOVER PERFORMED to MSC. This item is measured in this case.

Formula: none.

CXVII. Successful handovers for other causes

Description: This item measures all successful handovers caused by other causes (fast moving, handover cause being abnormal value), including Internal intracell handover, Internal intercell handover and outgoing handover. For intraBSC handovers, the message HANDOVER PERFORMED to MSC contains the handover cause. For interBSC handovers, the message HANDOVER REQUIRED corresponding to this handover contains the handover cause. Together with Attempted handovers for other causes, this item shows the performance of handovers of this type. Related items: Successful intracell handovers , Successful intercell handovers and Successful outgoing BSC handovers .


(cause: handover success) from MSC during the procedure of interBSC handover caused by other causes (such as fast moving, handover cause being filled with abnormal value).

2) During the procedure of BSC intercell handover caused by other causes (such as fast moving, handover cause being filled with abnormal value), after MS accessed the target cell, BSC will send HANDOVER PERFORMED to MSC. This item is measured in this case.

Formula: none.

CXVIII. Extended cell successful handovers (minimum timing advance)

Description: This item measures all successful handovers in a single timeslot extended cell caused by minimum timing advance (occurs only in single timeslot extended cells). It is a specific type of internal intracell handover. The message HANDOVER PERFORMED sent to MSC contains the handover cause. Together with Extended cell attempted handovers for minimum timingadvance , this item shows the performance of handovers of this type. Related items: Successful intracell handovers .

83



Measurement point: After MS accessed the underlaid subcell, BSC will send HANDOVER PERFORMED to MSC. This item is measured in this case.

Formula: none.

CXIX. Successful BSC inter-layer handovers (upper to lower)

Description: This item measures the times of successful internal intercell handovers in which the layer of the source cell is higher than the layer of the target cell. Related items: Successful BSC inter-layer handovers (lower toupper) and Successful intercell handovers .

Note:

The layers of cells are divided into four types, labelled with layer 1~4: 1. Pico, 2. Micro, 3. Macro, 4.

Umbrella. The higher layer has the lower priority. The upper layer normally refer to the one with the

lower priority between two layers, and the lower layer refers to the one with higher priority. This item

aims at the priority among the different type of layers, not at the different priority in the same type of

layer.

Measurement point: In internal intercell handover, after MS has been successfully handed over to the target cell, the target cell sends Inter Clear Request to the source cell to instruct the source cell to clear the involved resources. This item is measured when the source cell receives this message, and the layer of the source cell is higher than that of the target cell.

Formula: none.

CXX. Successful BSC inter-layer handovers (lower to upper)

Description: This item measures the times of successful BSC internal intercell handovers in which the layer of the source cell is lower than the layer of the target cell. Related items: Successful BSC inter-layer handovers (upper tolower) and Successful intercell handovers .

Note:

The layers of cells are divided into four types, labelled with layer 1~4: 1. Pico, 2. Micro, 3. Macro, 4.

Umbrella. The higher layer has the lower priority. The upper layer normally refers to the one with the

lower priority between two layers, and the lower layer refers to the one with higher priority. This item

aims at the priority among the different type of layers, not at the different priority in the same type of

layer.

84



Measurement point: In the internal intercell handover, after MS is successfully handed over to the target cell, the target cell sends Inter Clear Request to the source cell to intruct the source cell to clear the involved resources. This item is measured when the source receives this message, and the layer of the source cell is lower than that of the target cell.

Formula: none.

CXXI. Unsuccessful BSC internal handovers with successful reversion

Description: During the procedure of intraBSC handover, the source cell sends a HANDOVER COMMAND message to MS. If the MS cannot be handed over to the target cell due to poor radio environment or handover parameter incorrect, it will send HANDOVER FAILURE (cause: Radio interface failure, reversion to old channel) to the BSC via the previous channel. On receipt of this message the BSC will release the involved resources associated with the target cell, and the connecting between the BSC and MS remains the same. This item measures the times of unsuccessful handover with successful reversion. Related items: Unsuccessful intracell handovers, Unsuccessfuloutgoing BSC handovers with successful reversion and Unsuccessful BSCinternal handovers with unsuccessful reversion .

Measurement point: This item is measured when the source cell receives HANDOVER FAILURE (cause: Radio interface failure, reversion to old channel) from MS during the procedure of internal intracell handover or internal intercell handover, as shown in Figure 3-34 A1.

Formula: none.

MS BTS BSC MSC/VLR

HANDOVER COMPLETE

.HANDOVER COMMAND

B1

HANDOVER PERFORMED

Old Channel

CONN FAIL IND

HANDOVER FAILURE

A1

Old Channel

New Channel

ERROR INDB2

A1: Unsuccessful BSC internal handovers with successful reversion

B1~B2: Unsuccessful BSC internal handovers with unsuccessful reversion

Figure 3-34 Unsuccessful BSC internal handovers

85



CXXII. Unsuccessful BSC internal handovers with unsuccessful reversion

Description: During the procedure of intraBSC handover, after the source BSC sends the HANDOVER COMMAND message to MS, the connection between MS and the source cell is terminated before the connection between MS and the target cell set up due to poor radio environment or equipment failure. When BSC detects this situation, it will send a CLEAR REQUEST message to MSC to clear the previous resources and the involved resources during handover. This handover failed and the original service cannot be restored. This item measures the times of unsuccessful handover with unsuccessful reversion. Related items: Unsuccessful intracell handovers , Unsuccessful BSC internalhandovers with successful reversion and Unsuccessful outgoing BSChandovers with unsuccessful reversion .

Measurement point:1) This item is measured when the source cell receives CONNECTION

FAILURE INDICATION from BTS after sending the HANDOVER COMMAND message to MS during the procedure of intraBSC handover, as shown in Figure 3-34 B1.

2) During the procedure of intraBSC handover, after the target cell receives HANDOVER DETECTION, it will send an Inter Clear Request message to the source cell if the timer waiting HANDOVER COMPLETE times out or AM/CM net-drive fails. This item is measured when the source cell receives this message, which will then send a CLEAR REQUEST message to MSC.

3) During the procedure of intraBSC handover, after sending HANDOVER COMMAND to MS, the source cell receives ERROR INDICATION from BTS. This item is measured in this case, as shown in Figure 3-34 B2.

4) During the procedure of intraBSC handover, the source cell starts the timer waiting for Inter Clear Request after sending HANDOVER COMMAND to MS, this item is measured when the timer times out.

Formula: none.

CXXIII. Sum of Full rate TCH measurement reports (excluding very early assignment)

Meaning: After seizing a TCH, MS sends a MR every 480ms to the network (GSM 0408). This item provides the number of MRs reported by MS after seizing a full rate TCH. It is a traffic measurement parameter. This item does not include the MR of full rate TCH whose service type is signaling. It is applicable to both 900 and 1800 cells.

Measurement point: This item is measured when BSC receives the MR of full rate TCH from BTS.

Formula: None.

86



CXXIV. Sum of Half rate TCH measurement reports (excluding very early assignment)

Meaning: After seizing a TCH, MS sends a MR every 480ms to the network (GSM 0408). This item provides the number of MRs reported by MS after seizing a half rate TCH. It is a traffic measurement parameter. This item does not include the MR of half rate TCH whose service type is signaling. It is applicable to both 900 and 1800 cells.

Measurement point: This item is measured when BSC receives the MR of half rate TCH from BTS.

Formula: None.

CXXV. Sum of 1800 cell Full rate TCH measurement reports (excluding very early assignment)

Meaning: After seizing a TCH, MS sends a MR every 480ms to the network (GSM 0408). This item provides the number of MRs reported by MS after seizing a full rate TCH. It is a traffic measurement parameter. This item does not include the MR of full rate TCH whose service type is signaling. It is applicable to 1800 cells only.

Measurement point: This item is measured when BSC receives the MR of full rate TCH from BTS.

Formula: None.

CXXVI. Sum of 1800 cell Half rate TCH measurement reports (excluding very early assignment)

Meaning: After seizing a TCH, MS sends a MR every 480ms to the network (GSM 0408). This item provides the number of MRs reported by MS after seizing a half rate TCH. It is a traffic measurement parameter. This item does not include the MR of half rate TCH whose service type is signaling. It is applicable to 1800 cells only.

Measurement point: This item is measured when BSC receives the MR of half rate TCH from BTS.

Formula: None.

CXXVII. Assignment requests with signalling channel

Meaning: When there is a short message sent to a MS which is engaged in a conversation (seizing a TCH), MSC may issue ASSIGNMENT REQUEST to assign a signaling channel for short message transmission. Since MS has already seized voice channel after channel assignment, and this voice channel can be used to send short message, BSC only needs to return ASSIGNMENT COMPLETE to MSC indicating that channel assignment is completed. After conversation and short message is complete, MSC issues CLEAR COMMAND

87



to initiate release procedure. This item provides the times of ASSIGNMENT REQUEST from MSC to BSC being used to establish signaling connections.

Measurement point: As shown in Figure 3-35A, this item is measured when BSC receives ASSIGNMENT REQUEST from MSC which is used to assign resource for signaling connection establishment.

Formula: None.

A: Times of signaling channel assignment request

B: Times of successful signaling channel assignment

Figure 3-35 Signaling channel request procedure

CXXVIII. Successful assignments with signalling channel

Meaning: When there is a short message sent to a MS which is engaged in a conversation (seizing a TCH), MSC may issue ASSIGNMENT REQUEST to assign a signaling channel for short message transmission. Since MS has already seized voice channel after channel assignment, and this voice channel can be used to send short message, BSC only needs to return ASSIGNMENT COMPLETE to MSC indicating that channel assignment is completed. After conversation and short message is complete, MSC issues CLEAR COMMAND to initiate release procedure. This item provides the times of ASSIGNMENT REQUEST from MSC to BSC being used to establish signaling connections, and after which BSC returns ASSIGNMENT COMPLETE to MSC.

Measurement point: As shown in Figure 3-35 B, this item is measured when BSC returns ASSIGNMENT COMPLETE to MSC after BSC receives ASSIGNMENT REQUEST from MSC which is used to assign resource for signaling connection establishment.

Formula: None.

CXXIX. Circuit paging (A-interface) success rate

Description: See Successful circuit pagings of Abis interface and Receivedcircuit paging messages from MSC .

88



Measurement point: none. Formula: Successful circuit pagings of Abis interface / Received circuit paging

messages from MSC

CXXX. Ratio of paging channel overloads (%)

Description: This item measures the percentage of PCH overloads in the paging commands to BTS. See Circuit paging PCH overloads of Abisinterface , Packet paging PCH overloads of Abis interface , Circuit pagingcommands to BTS and Packet paging commands to BTS .

Measurement point: none. Formula: (Circuit paging PCH overloads of Abis interface + Packet paging PCH

overloads of Abis interface) / (Circuit paging commands to BTS + Packet paging commands to BTS)

CXXXI. Rate of sending immediate assignment command

Description: See Immediate assignment transmissions and Immediateassignment requests .

Measurement point: none. Formula: Immediate assignment transmissions / Immediate assignment

requests

CXXXII. Intracell handover success rate

Description: See Successful intracell handovers , Attempted intracellhandovers .

Measurement point: none. Formula: Successful intracell handovers / Attempted intracell handovers

CXXXIII. Intercell handover success rate

Description: See Successful intercell handovers , Attempted intercellhandovers .

Measurement point: none. Formula: Successful intercell handovers / Attempted intercell handovers

CXXXIV. Incoming BSC handover success rate

Description: See Successful incoming BSC handovers , Attempted incomingBSC handovers.

Measurement point: none. Formula: Successful incoming BSC handovers / Attempted incoming BSC

handovers

89



CXXXV. Outgoing BSC handover success rate

Description: See Successful outgoing BSC handovers , Attempted outgoingBSC handovers.

Measurement point: none. Formula: Successful outgoing BSC handovers / Attempted outgoing BSC

handovers

CXXXVI. Ratio of intraBSC interband handover to total intraBSC handover

Description: This item measures the percentage of the intraBSC interband handovers in total internal intercell handovers. See Attempted intercellhandovers , Attempted intercell handovers (9001800) , Attempted intercellhandovers (1800→900) .

Measurement point: none. Formula: (Attempted intercell handovers (9001800) + Attempted intercell

handovers (1800900)) / Attempted intercell handovers

CXXXVII. Ratio of interBSC interband handover to total interBSC handover

Description: This item measures the percentage of the interBSC interband handovers in total interBSC handovers. See Attempted incoming BSChandovers , Attempted incoming BSC handovers (9001800) , Attemptedincoming BSC handovers (1800900) , Attempted outgoing BSC handovers , Attempted outgoing BSC handovers (9001800) , Attempted outgoing BSChandovers (1800900) .

Measurement point: none. Formula: (Attempted incoming BSC handovers (9001800) + Attempted

incoming BSC handovers (1800900) + Attempted outgoing BSC handovers (9001800) + Attempted outgoing BSC handovers (1800900)) / (Attempted incoming BSC handovers + Attempted outgoing BSC handovers)

CXXXVIII. Dual-band handover success rate

Description:The dual-band handover success rate in a BSC, including intraBSC dual-band handovers and interBSC dual-band handovers. See Successful intercell handovers (9001800) , Successful intercell handovers(1800900) , Attempted intercell handovers (9001800) , Attempted intercellhandovers (1800→900) , Successful incoming BSC handovers (9001800) , Successful incoming BSC handovers (1800900), Attempted incoming BSChandovers (9001800) , Attempted incoming BSC handovers (1800900) , Successful outgoing BSC handovers (9001800) , Successful outgoing BSChandovers (1800900) , Attempted outgoing BSC handovers (9001800) , Attempted outgoing BSC handovers (1800900) .

Measurement point: none.

90



Formula: (Successful intercell handovers (9001800) + Successful intercell handovers (1800900) + Successful incoming BSC handovers (9001800) + Successful incoming BSC handovers (1800900) + Successful outgoing BSC handovers (9001800)+ Successful outgoing BSC handovers (1800900)) / (Attempted intercell handovers (9001800) + Attempted intercell handovers (1800900) + Attempted incoming BSC handovers (9001800) + Attempted incoming BSC handovers (1800900) + Attempted outgoing BSC handovers (9001800) + Attempted outgoing BSC handovers (1800900))

CXXXIX. TCH call drop rate (%)

Description: This item measures the percentage of TCH call drops in successful TCH seizures. See TCH call drop and Successful TCH seizures .

Measurement point: none. Formula: TCH call drop / Successful TCH seizures

CXL. Traffic volume (excluding very early assignment) (Erl)

Description: This item measures the total traffic volume of all cells in a BSC, excluding the traffic volume during very early assignment. See Sum of TCHmeasurement reports (excluding very early assignment) .

Measurement point: none. Formula: Sum of TCH measurement reports (excluding very early assignment)

0.48 / Statistic Cycle (second)

CXLI. Traffic volume of 1800 cell (excluding very early assignment) (Erl)

Description: This item measures the total traffic volume of all GSM 1800 cells in a BSC, excluding the traffic volume during very early assignment. See Sumof 1800 cell TCH measurement reports(excluding very early assignment) .

Measurement point: none. Formula: Sum of 1800 cell TCH measurement reports(excluding very early

assignment) 0.48 / (Statistic Cycle (second))

CXLII. Intra BSC radio handover success rate

Description: See Successful intracell handovers , Successful intercellhandovers , Intra BSC handovers .

Measurement point: none. Formula: (Successful intracell handovers + Successful intercell handovers) /

Intra BSC handovers

CXLIII. Incoming BSC radio handover success rate

Description: See Successful incoming BSC handovers , Incoming BSChandovers .

91



Measurement point: none. Formula: Successful incoming BSC handovers / Incoming BSC handovers

CXLIV. Outgoing BSC radio handover success rate

Description: See Successful outgoing BSC handovers , Outgoing BSChandovers .

Measurement point: none. Formula: Successful outgoing BSC handovers / Outgoing BSC handovers

CXLV. Percentage of TRX in good condition (%)

Description: This item measures the percentage of good TRXs in total configured TRXs. See Sum of available TRX in the BSC and Sum ofconfigured TRX in the BSC.

Measurement point: none. Formula: Sum of available TRX in the BSC / Sum of configured TRX in the

BSC

CXLVI. SDCCH call drop rate (%)

Description: This item measures the percentage of SDCCH call drops in successful SDCCH seizures. See SDCCH call drop and Successful SDCCHseizures .

Measurement point: none. Formula: SDCCH call drop / Successful SDCCH seizures

CXLVII. SDCCH congestion rate (SDCCH overflow) (%)

Description: This item measures the percentage of the attempted SDCCH seizures meeting congestion in total attempted SDCCH seizures. See Attempted SDCCH seizures meeting SDCCH overflow and AttemptedSDCCH seizures (all) .

Measurement point: none. Formula: Attempted SDCCH seizures meeting an SDCCH blocked state /

Attempted SDCCH seizures (all)

CXLVIII. Full rate traffic volume (excluding very early assignment) (ERL)

Meaning: This item provides the traffic volume on full rate TCHs of all cells (including 900and 1800) of the measured BSC, excluding the traffic on full rate TCH of very early assignment. See Sum of Full rate TCH measurement reports(excluding very early assignment) .

Measurement point: None. Formula: [Total number of Full rate TCH MRs (excluding very early

assignment)] × 0.48 / [measurement period (sec)]

92



CXLIX. Half rate traffic volume (excluding very early assignment) (ERL)

Meaning: This item provides the traffic volume on half rate TCHs of all cells (including 900and 1800) of the measured BSC, excluding the traffic on half rate TCH of very early assignment. See Sum of Half rate TCH measurementreports (excluding very early assignment) .

Measurement point: None. Formula: [Total number of half rate TCH MRs (excluding very early

assignment)] × 0.48 / [measurement period (sec)]

CL. Full rate traffic volume of 1800 cell (excluding very early assignment) (ERL)

Meaning: This item provides the traffic volume on full rate TCHs of all 1800 cells of the measured BSC, excluding the traffic on full rate TCH of very early assignment. See Sum of 1800 cell Full rate TCH measurement reports(excluding very early assignment) .

Measurement point: None. Formula: [Total number of Full rate TCH MRs on 1800 cells (excluding very

early assignment)] × 0.48 / [measurement period (sec)]

CLI. Half rate traffic volume of 1800 cell (excluding very early assignment) (ERL)

Meaning: This item provides the traffic volume on half rate TCHs of all 1800 cells of the measured BSC, excluding the traffic on half rate TCH of very early assignment. See Sum of 1800 cell Half rate TCH measurement reports(excluding very early assignment) .

Measurement point: None. Formula: [Total number of half rate TCH MRs on 1800 cells (excluding very

early assignment)] × 0.48 / [measurement period (sec)]

3.2 SCCP Measurement Function

3.2.1 General

In SS7 protocol system, SCCP (Signaling Connection Control Part) and MTP (Message Transfer Part) provide a comprehensive network function for the data of application part. SCCP provides two types of services: connectionless service and connection-oriented service.

Connectionless service transmits signaling in the signaling network directly using the routing function of SCCP and MTP without establishing signaling connection

93



before transmitting the signaling data. It is flexible and simple, and applicable for transmission of small amount data.

Connection-oriented service needs to establish a signaling connection (virtual connection) between calling SCCP and called SCCP in request-response mode before transmitting signaling data. This connection is used to transmit signaling. When transmission is completed, the relative message will be sent to request for releasing the signaling connection. This type of service is applicable for transmission of large amount data.

SCCP Measurement Function shows the flow of important messages under two types of SCCP services at A interface. It can be used to analyze the operation of SCCP system, and locate the faults at A interface signaling link layer.

All the statistic items are listed in Table 3-1 .

Table 3-1 Statistic items in SCCP Measurement Function

No. Item name

1 UDT messages (O)

2 UDT messages (I)

3 XUDT messages (O)

4 XUDT messages (I)

5 CR messages (O)

6 CR messages (I)

7 CC messages (O)

8 CC messages (I)

9 CREF messages (O)

10 CREF messages (I)

11 DT1 messages (O)

12 DT1 messages (I)

13 RLSD messages (O)

14 RLSD messages (I)

15 RLC messages (O)

16 RLC messages (I)

3.2.2 Statistic items

I. UDT messages (O)

Description: The connectionless service provided by SCCP uses the messages UNITDATA (UDT) and EXTENDED UNITDATA (XUDT) to transmit

94



user data. UNITDATA does not have the capability of data segmenting/reassembling. The maximum length of user data it can transmit is 128 octets. EXTENDED UNITDATA is capable of segmenting/reassembling data. The maximum length of user data it can transmit is 2048 octets.

Measurement point: When SCCP service module of BSC sends UNITDATA, the number of UDT messages (O) is increased by 1.

Formula: none.

II. UDT messages (I)

Description: The connectionless service provided by SCCP uses the messages UNITDATA (UDT) and EXTENDED UNITDATA (XUDT) to transmit user data. UNITDATA does not have the capability of data segmenting/reassembling. The maximum length of user data it can transmit is 128 octets. EXTENDED UNITDATA is capable of segmenting/reassembling data. The maximum length of user data it can transmit is 2048 octets.

Measurement point: When SCCP service module of BSC receives UNITDATA from the peer SCCP service module, the number of UDT messages (I) is increased by 1.

Formula: none.

III. XUDT messages (O)


Measurement point: When SCCP service module of BSC sends EXTENDED UNITDATA, the number of XUDT messages (O) is increased by 1.

Formula: none.

IV. XUDT messages (I)


Measurement point: When SCCP service module of BSC receives EXTENDED UNITDATA from the peer SCCP service module, the number of XUDT messages (I) is increased by 1.

95



Formula: none.

V. CR messages (O)

Description: Connection-oriented service needs to establish a signaling connection (virtual connection) between calling SCCP and called SCCP in request-response mode before transmitting signaling data. Figure 3-1 illustrates the process of creating a successful signaling connection. The calling SCCP sends CONNECTION REQUEST (CR) to the called SCCP to request the setup of a signaling connection between the two entities. On reception of a CONNECTION REQUEST, the called SCCP initiates the setup of the signaling connection, and then sends CONNECTION CONFIRM (CC) to the calling SCCP. On reception of CONNECTION CONFIRM, the calling SCCP completes the setup of the signaling connection.

Measurement point: When SCCP service module of BSC sends CONNECTION REQUEST, the number of CR messages (O) is increased by 1.

Formula: none.

SCCP-A SCCP-B

CONNECTION REQUEST

A B

C D

CONNECTION CONFIRM

A: CR messages (O)

B: CR messages (I)

C: CC messages (I)

D: CC messages (O)

Figure 3-1 Establishment of SCCP signaling connection (successful)

VI. CR messages (I)

Description: Connection-oriented service needs to establish a signaling connection (virtual connection) between calling SCCP and called SCCP in request-response mode before transmitting signaling. Figure 3-1 illustrates the process of creating a successful signaling connection. The calling SCCP sends CONNECTION REQUEST (CR) to the called SCCP to request the setup of a signaling connection between the two entities. On reception of a CONNECTION REQUEST message, the called SCCP initiates the setup of the

96



signaling connection, and then sends CONNECTION CONFIRM (CC) to the calling SCCP. On reception of CONNECTION CONFIRM, the calling SCCP completes the setup of the signaling connection.

Measurement point: When SCCP service module of BSC receives CONNECTION REQUEST from the peer SCCP service module, the number of CR messages (I) is increased by 1.

Formula: none.

VII. CC messages (O)

Description: Connection-oriented service needs to establish a signaling connection (virtual connection) between calling SCCP and called SCCP in request-response mode before transmitting signaling. Figure 3-1 illustrates the process of creating a successful signaling connection. The calling SCCP sends CONNECTION REQUEST (CR) to the called SCCP to request the setup of a signaling connection between the two entities. On reception of a CONNECTION REQUEST, the called SCCP initiates the setup of the signaling connection, and then sends CONNECTION CONFIRM (CC) to the calling SCCP. On reception of CONNECTION CONFIRM, the calling SCCP completes the setup of the signaling connection.

Measurement point: When SCCP service module of BSC sends CONNECTION CONFIRM, the number of CC messages (O) is increased by 1.

Formula: none.

VIII. CC messages (I)

Description: Connection-oriented service needs to establish a signaling connection (virtual connection) between calling SCCP and called SCCP in request-response mode before transmitting signaling. Figure 3-1 illustrates the process of creating a successful signaling connection. The calling SCCP sends CONNECTION REQUEST (CR) to the called SCCP to request the setup of a signaling connection between the two entities. On reception of a CONNECTION REQUEST, the called SCCP initiates the setup of the signaling connection, and then sends CONNECTION CONFIRM (CC) to the calling SCCP. On reception of CONNECTION CONFIRM, the calling SCCP completes the setup of the signaling connection.

Measurement point: When SCCP service module of BSC receives CONNECTION CONFIRM from the peer SCCP service module, the number of CC messages (I) is increased by 1.

Formula: none.

97



IX. CREF messages (O)

Description: Connection-oriented service needs to establish a signaling connection (virtual connection) between calling SCCP and called SCCP in request-response mode before transmitting signaling. After calling SCCP initiates CONNECTION REQUEST, the called SCCP or an intermediate node SCCP may refuse the connection for some reason. In this case, they will initiates CONNECTION REFUSED (CREF). See Figure 3-36 .

Measurement point: When SCCP service module of BSC sends CONNECTION REFUSED, the number of CREF messages (O) is increased by 1.

Formula: none.

SCCP-A

CONNECTION REQUEST

A

CONNECTION REFUSED

SCCP-B

B

A: CREF messages (I)

B: CREF messages (O)

Figure 3-36 Establishment of SCCP signaling connection (failure)

X. CREF messages (I)

Description: Connection-oriented service needs to establish a signaling connection (virtual connection) between calling SCCP and called SCCP in request-response mode before transmitting signaling. After calling SCCP initiates CONNECTION REQUEST, the called SCCP or an intermediate node SCCP may refuse the connection for some reason. In this case, they will initiates CONNECTION REFUSED (CREF). See Figure 3-36 .

Measurement point: When SCCP service module of BSC receives CONNECTION REFUSED from the peer SCCP service module, the number of CREF messages (I) is increased by 1.

Formula: none.

98



XI. DT1 messages (O)

Description: Connection-oriented service needs to establish a signaling connection (virtual connection) between calling SCCP and called SCCP in request-response mode before transmitting signaling data. DATA FORM 1 (DT1) is used in transmitting signaling between SCCP signaling points. When a SCCP needs to transmit signaling, it will send DT1 containing the signaling to the peer SCCP. On reception of this DT1, the peer SCCP will also respond with a DT1 containing signaling. See Figure 3-37 .

Measurement point: When SCCP service module of BSC sends DATA FORM 1, the number of DT1 messages (O) is increased by 1.

Formula: none.

SCCP-A

CONNECTION REQUEST

A

CONNECTION CONFIRM

SCCP-B

B

DATA FORM 1

DATA FORM 1

A: DT1 messages (I)

B: DT1 messages (O)

Figure 3-37 Establishment of SCCP signaling connection and data transmission

XII. DT1 messages (I)

Description: Connection-oriented service needs to establish a signaling connection (virtual connection) between calling SCCP and called SCCP in request-response mode before transmitting signaling data. DATA FORM 1 (DT1) is used in transmitting signaling between SCCP signaling points. When a SCCP needs to transmit signaling, it will send DT1 containing the signaling to the peer SCCP. On reception of this DT1, the peer SCCP will also respond with a DT1 containing signaling. See Figure 3-37 .

Measurement point: When SCCP service module of BSC receives DATA FORM 1 from the peer SCCP service module, the number of DT1 messages (I) is increased by 1.

Formula: none.

99



XIII. RLSD messages (O)

Destination: RELEASED (RLSD) is sent, in the forward or backward direction, to indicate that the sending SCCP wants to release a signaling connection and the associated resources. On reception of this message, the receiving SCCP should release the connection and any other associated resources as well. A RELEASE COMPLETE (RLC) message is sent in response to the RELEASED message indicating that the RELEASED message has been received, and the appropriate procedures have been completed. See Figure 3-38.

Measurement point: When SCCP service module of BSC sends RELEASED, the number of RLSD messages (O) is increased by 1.

Formula: none.

SCCP-A

CONNECTION REQUEST

C

CONNECTION CONFIRM

SCCP-B

D

DATA FORM 1

DATA FORM 1

RELEASED

RELEASE COMPLETE

A B

A: RLSD messages (O)

B: RLSD messages (I)

C: RLC messages (I)

D: RLC messages (O)

Figure 3-38 Transmission of SCCP signaling

XIV. RLSD messages (I)


100



Measurement point: When SCCP service module of BSC receives RELEASED from the peer SCCP service module, the number of RLSD messages (I) is increased by 1.

Formula: none.

XV. RLC messages (O)


Measurement point: When SCCP service module of BSC sends RELEASE COMPLETE, the number of RLC messages (O) is increased by 1.

Formula: none.

XVI. RLC messages (I)


Measurement point: When SCCP service module of BSC receives RELEASE COMPLETE from the peer SCCP service module, the number of RLC messages (I) is increased by 1.

Formula: none.

3.3 A-interface Operation and Management Statistic

3.3.1 General

"A-interface Operation and Management Statistic" reflect the O&M and running status of BSC equipment, as well as concern the interworking between BSC and MSC, including reset of MSC, reset of BSC, reset, fault and recovery of a single module in BSC, the overall running status of A interface signaling, BSC's handling procedure after MSC overload, etc. See Table 3-1 for the list of all the relevant statistic items.

101



Table 3-1 Statistic items in A-interface Operation and Management Statistic

No. Item name

1 BSC initiated reset

2 MSC initiated reset

3 Single module (BSC) initiated reset

4 Internal notifications of BSC reset

5 Internal notifications of MSC reset

6 Internal notifications of BM reset

7 BSC BM suspend

8 BSC BM resume

9 BSC overload

10 SS7 link connections

11 SS7 link breakdowns


I. BSC initiated reset

Description: After the user initiates reset of BSC in BSC Maintenance System, BSC Maintenance System sends an MT_RESET_RESOURCE message to BSC. Upon receipt of the message, BSC shall execute the command. When BSC is reset, all the calls within it shall be cleared (In the subsequent 128 seconds, the establishment of new calls shall be prohibited). In the meantime, BSC shall send a RESET message to MSC and await the response message (RESET_ACK). The timer value for awaiting the RESET_ACK message is 150 second. BSC shall resend the RESET message, if it cannot receive the RESET_ACK message before the timer expires. Such repeat operations can be performed for max. 3 times. This statistic item is used calculate the number of RESET message sent from BSC to MSC.

Measurement point: Statistics will be made when BSC sends a RESET message to MSC.

Formula: none

II. MSC initiated reset

Description: MSC sends a RESET message to BSC when it is reset. Upon receipt of the RESET message, BSC returns a RESET_ACK message, and at the same time, it clears all the CS calls (GPRS calls no impact) within BSC and prohibits the establishment of new calls in the subsequent 128s. This item is

102



used calculate the number of times BSC receives RESET messages from MSC.

Measurement point: Statistics will be made when BSC receives a RESET message from MSC.

Formula: none

III. Single module (BSC) initiated reset

Description: When a single BM is reset, the calls in all the cells under this module shall be cleared (The establishment of new calls shall be prohibited in the subsequent 128s). At the same time, this BM shall notify other BMs to clear the calls that occupy its A interface circuit resources. This item is used calculate the number of times a single BM is reset. In the following cases, a single module shall be reset.1) The user resets a BM in BSC Maintenance System.2) The communication between BM and AM/CM is resumed after

interruption.3) When the communication between BM and AM/CM is resumed after

interruption, the communication on A interface of BSC is in interruption state (The SS7 links of the whole BSC are disconnected), but afterwards, BM detects that the communication on A interface is resumed.

4) The first time BM detects that the communication on A interface is normal after kickoff (At least 1 SS7 link is normal).

Measurement point: Statistics will be made when a single BM is reset and calls are cleared.

Formula: none

IV. Internal notifications of BSC reset

Description: This item is correlated with "BSC initiated reset". After user initiates reset of BSC in BSC Maintenance System, the BM with the smallest module No. among the BMs of BSC that work normally shall serve as the main control BM, sends an INTER_BSC_RESET_IND message to the other BMs notifying them to clear calls, and await the response messages. The timer value for awaiting the response messages is 2 second. The BM shall resend the message if it has not received the response messages before expiry of the timer. This statistic item is to calculate the times of the main control BM notifying the other BMs to clear calls during BSC reset.

Measurement point: Statistics will be made when the other BMs receive an INTER_BSC_RESET_IND message from the main control BM during BSC reset.

Formula: none.

103



V. Internal notifications of MSC reset

Description: This item is correlated with "MSC initiated reset". MSC sends a RESET message to BSC when MSC is reset. After BSC receives the message, the BM with the smallest module No. among the BMs of BSC that work normally shall serve as the main control BM, return an RESET_ACK message to MSC, clear all the CS calls (GPRS services are free from the impact) of itself, send an INTER_MSC_RESET_IND message to the other BMs notifying them to clear CS calls, and await the response messages. The timer value for awaiting the response message is 2 second. The BM shall resend the message if it has not received the response messages before expiry of the timer. This statistic item is to calculate the times of the main control BM in BSC notifying other BMs to clear CS calls after BSC receives a RESET message from MSC.

Measurement point: After BSC receives a RESET message from MSC, the main control BM sends an INTER_MSC_RESET_IND message to other BMs. When the other BMs receive INTER_MSC_RESET_IND and clear CS calls, statistics will be made.

Formula: none.

VI. Internal notifications of BM reset

Description: This item is correlated with "Single module (BSC) initiated reset". When a single BM is reset, the BM shall send an INTER_BSC_BM_RESET_IND message to other BMs notifying them to clear the calls that occupy its A interface circuit resources, and await the response messages. The timer value for awaiting the response message is 2 second. The BM shall resend the message if it has not received the response message before expiry of the timer. This statistic item is to calculate the times of a BM notifying other BMs to clear the calls that occupy its A interface circuit resources when it is reset.

Measurement point: Upon reset, a BM sends an INTER_BSC_BM_RESET_IND message to other BMs. When the other BMs receive INTER_BSC_BM_RESET_IND and clear the calls that occupy the A interface circuit resources of that BM, statistics will be made.

Formula: none.

VII. BSC BM suspend

Description: "BM suspend" means that after the communication between AM/CM and a BM in BSC is interrupted, the BM shall clear all the calls as well as prohibit establishment of new calls in it, and disconnect its SS7 link. This statistic item is used to calculate the number of times the communication

104



between BM and AM/CM is interrupted. The BM whose communication is interrupted is to make statistics.

Measurement point: Statistics will be made when BM detects that the communication between AM/CM and itself is interrupted.

Formula: none.

VIII. BSC BM resume

Description: This statistic item is correlated with "BSC BM suspend". "BM resume" means that the communication between BM and AM/CM is resumed after interruption. This item is to calculate the times of that the communication between BM and Am/CM is resumed after interruption. The BM whose communication is interrupted is to make the statistics. BM will be automatically reset after its communication with AM/CM is resumed. For relevant description, please refer to "Single module (BSC) initiated reset".

Measurement point: Statistics will be made when BM detects that its communication with AM/CM is resumed after interruption.

Formula: none.

IX. BSC overload

Description: After overload occurs to MSC, MSC sends an OVERLOAD message to BSC. Upon receipt of the OVERLOAD message, BSC starts the corresponding flow control algorithm or raise the flow control level. According to the algorithm, BSC shall discard a proportion of calls that are being established so as to lessen the severity of MSC overload. According to the algorithm, if BSC no longer receives any OVERLOAD messages from MSC within a period of time, the flow control level will be automatically lowered, and the proportion of discarded calls will be reduced until no flow control is required. This item is to calculate the times of overload occur to MSC.

Measurement point: Statistics will be made when BSC receives an OVERLOAD message from MSC.

Formula: none.

X. SS7 link connections

Description: "SS7 link connection" refers to the normal connection of SCCP layer between MSC and BSC on A interface. When the SCCP layer satisfies the following conditions at the same time, the connection will be regarded as "normal". Otherwise, it will be regarded as "breakdown".1) Permitted by DPC2) No congestion3) SCCP available

105



This statistic item is to calculate the times of SCCP connection are resumed. Measurement point:

1) The first time BM detects that the SCCP connection on A interface is normal after kickoff.

2) When BM detects that the state of SCCP connection on A interface has changed from "breakdown" into "normal".

Formula: none.

XI. SS7 link breakdowns

Description: This statistic item is correlated with "SS7 link connections". When the SCCP layer of BSC on A interface satisfies the following conditions at the same time, the connection will be regarded as "normal". Otherwise, it will be regarded as "breakdown".1) Permitted by DPC2) No congestion3) SCCP available This statistic item is to calculate the times of SCCP connection state changes from "normal" into "breakdown".

Measurement point: Statistics will be made when BM detects that the SCCP connection on A interface is broken down.

Formula: none.

3.4 A-interface Equipment Maintenance Statistic

3.4.1 General

"A-interface Equipment Maintenance Statistic" reflects the operations performed by users to A interface trunk circuits and board equipment, including user-initiated block, unblock, setting, reset, etc. See Table 3-2 for the list of all the relevant statistic items.

Table 3-2 Statistic items in A-interface Equipment Maintenance Statistic

No. Item name

1 Act of setting trunk circuit table dynamically

2 Act of unblocking circuits

3 Act of blocking circuits

4 Act of resetting circuits

5 Act of resetting FTC boards

6 Act of resetting SM boards

106




I. Act of setting trunk circuit table dynamically

Description: The user implements dynamic data configuration to send the trunk circuit table to one or more BMs. According to the data received, BM refreshes the A interface circuit management table in memory. This statistic item is to calculate the number of A interface trunk circuits in this BM after the A interface circuit management table is updated(including the A interface trunk circuits that are not installed)

Measurement point: Statistics will be made when BM receives a trunk circuit table from Data Management System.

Formula: none.

II. Act of unblocking circuits

Description: When the user performs an unblocking operation for A interface circuits via BSC Maintenance System, BSC Maintenance System sends an MT_OPEN_CIRCUIT message to the corresponding BM of BSC, which contains the range of the to-be-unblocked circuits. Upon receipt of the message, BM modifies the states of the circuits in the specified range, notifies MSC about the state modifications through the GROUP_UNBLOCK_CIRCUIT and UNBLOCK_CIRCUIT messages, and awaits the response message. BM will resend the messages to MSC if it cannot receive a response message within 150 second. The max. number of resending is 2. This statistic item is to calculate the times of the user performs unblocking operations in BSC Maintenance System.

Measurement point: When BM modifies the states of circuits upon receipt of the MT_OPEN_CIRCUIT message from BSC Maintenance System, statistics will be made.

Formula: none.

III. Act of blocking circuits

Description: When the user performs a blocking operation for A interface circuits via BSC Maintenance System, BSC Maintenance System sends an MT_BLOCK_CIRCUIT message to the corresponding BM of BSC, which contains the range of the to-be-blocked circuits. Upon receipt of the message, BM modifies the states of the circuits in the specified range, notifies MSC about the state modifications through the GROUP_BLOCK_CIRCUIT and BLOCK_CIRCUIT messages, and awaits the response message. BM will resend the messages to MSC if it cannot receive a response message within

107



150 second. The max. number of resending is 2. If a circuit within the range is being occupied by a call, the circuit state will be changed into "blocked" after the call is terminated. This statistic item is to calculate the times of the user performs blocking operations in BSC Maintenance System.

Measurement point: When BM modifies the states of circuits upon receipt of the MT_BLOCK_CIRCUIT message from BSC Maintenance System, statistics will be made.

Formula: none.

IV. Act of resetting circuits

Description: When the user performs a reset operation for A interface circuits via BSC Maintenance System, BSC Maintenance System sends an MT_RESET_CIRCUIT message to the corresponding BM of BSC, which contains the range of the to-be-reset circuits. Upon receipt of the message, BM changes the states of the blocked circuits in the specified range into "idle", sends RESET_CIRCUIT messages one by one to MSC, and awaits the response messages. BM will resend the message to MSC if it cannot receive a response message within 150 second. The max. number of resending is 2. Upon receipt of the RESET_CIRCUIT message, MSC first judges whether the circuit is being occupied by a call, clears the call if it occupies the circuit, and then returns RESET_CIRCUIT_ACK message to BSC. This statistic item is to calculate the number of times the user performs reset operations in BSC Maintenance System.

Measurement point: When BM receives an MT_RESET_CIRCUIT message from BSC Maintenance System, statistics will be made.

Formula: none.

V. Act of resetting FTC boards

Description: When the user resets FTC via BSC Maintenance System, BSC Maintenance System sends a RESET_FTC message to the corresponding BM of BSC. Upon receipt of the message, the BM implements reset operation for FTC. This statistic item is to calculate the times of the user performs FTC reset operations in BSC Maintenance System.

Measurement point: When BM resets FTC after it receives a RESET_FTC message from BSC Maintenance System, statistics will be made.

Formula: none.

VI. Act of resetting SM boards

Description: When the user resets an SM board via BSC Maintenance System, BSC Maintenance System sends a RESET_SM message to the corresponding BM in BSC. Upon receipt of the message, the BM implements reset operation

108



for the SM board. This statistic item is to calculate the times of the user performs SM reset operations in BSC Maintenance System.

Measurement point: When BM resets SM board after it receives a RESET_SM message from BSC Maintenance System, statistics will be made.

Formula: none.

3.5 A-interface Trunk Board Message Statistic

3.5.1 General

"A-interface Trunk Board Message Statistic" reflects the operational state of A interface hardware equipment, including board reset, E1 trunk reset, fault and recovery. See Table 3-3 for the list of all the relevant statistic items.


No. Item name

1 FTC board reset messages

2 FTC board errors

3 SM board reset messages

4 SM board errors

5 E3M board errors

6 E1 errors

7 E1 recovery

8 E1 warnings


I. FTC board reset messages

Description: After FTC is successfully reset, a report is sent to BM, notifying it about the success of FTC reset. Upon receipt of the message, BM sets the state of the FTC as "normal", and sends configuration information (such as supporting of TFO) to the FTC. This statistic item is to calculate the times of FTC reports success of FTC reset to BM.

Measurement point: When BM receives a message from FTC, indicating that the FTC is successfully reset, statistics will be made.

Formula: none.

109



II. FTC board errors

Description: When an FTC fault is detected, BM will set the state of the FTC as "faulty". This statistic item is to calculate the times of BM detects FTC faults.

Measurement point: When BM detects that FTC becomes faulty, statistics will be made.

Formula: none.

III. SM board reset messages

Description: After an SM board is successfully reset, a report is sent to BM, notifying it about the success of SM reset. Upon receipt of the message, BM sets the state of the SM board as "normal". This statistic item is to calculate the times of the SM board reports success of SM reset to BM.

Measurement point: When BM receives a message from a SM board, indicating that the SM board is successfully reset, statistics will be made.

Formula: none.

IV. SM board errors

Description: When an SM board fault is detected, BM will set the state of the SM board as "faulty". This statistic item is to calculate the times of BM detects SM board faults.

Measurement point: When BM detects that an SM board becomes faulty, statistics will be made.

Formula: none.

V. E3M board errors

Description: When an E3M board fault is detected, BM will set the state of the E3M board as "faulty". This statistic item is to calculate the number of times BM detects E3M board faults.

Measurement point: When BM detects that an E3M board becomes faulty, statistics will be made.

Formula: none.

VI. E1 errors

Description: When an E1 trunk on A interface becomes faulty, FTC/SM reports the E1 trunk fault to BM. BM will also consider that a fault has occurred to the relevant A interface E1 trunk when it detects FTC/SM/E3M becomes faulty. BM will refresh E1 state and relevant A interface circuit state. This statistic item is to calculate the times of faults occur to the A interface trunk.

Measurement point:1) When BM receives a report from SM, notifying that a fault has occurred to

an E1 trunk.

110



2) When BM detects an FTC/SM/E3M fault. Formula: none.

VII. E1 recovery

Description: FTC/SM reports E1 trunk recovery to BM when it detects that an E1 trunk on A interface has recovered from fault. BM will refresh the E1 state and relevant A interface circuit state. This statistic item is to calculate the times of A interface trunk recovers from fault.

Measurement point: When BM receives an E1 trunk recovery report, statistics will be made.

Formula: none.

VIII. E1 warnings

Description: When the state of an A interface E1 trunk changes (from "normal" to "faulty", or from "faulty" to "normal"), BM will report an alarm to the alarm system (Alarm No.: 317. Alarm name: A interface E1 state reporting). This statistic item is to calculate the times of alarm 317 is reported.

Measurement point: When BM reports alarm 317 to the alarm system, statistics will be made.

Formula: none.

3.6 CPU Measurement Function

3.6.1 General

CPU measurement function includes two statistic items: Percentage of CPU occupation (%) and Peak percentage of CPU occupation (%), see Table 3-4 .

The former one is the percentage of CPU in busy status during the measurement cycle. This item indicates the load of BSC. The latter one is the maximum CPU occupation within measurement cycle.

CPU occupation rate indicates the load of system. But 100% CPU occupation does not mean that the processing capacity of CPU has been fully exerted, and no more tasks can be accepted. Since BSC has some buffering capability, newly arrived tasks can be stored in the buffer. Theoretically, as long as enough internal buffering space of BSC still exists, BSC is able to accept new service requests, and the service will not be interrupted. In other words, high CPU occupation does not always indicate BSC failure. In practice, sometime, CPU occupation may go higher than 80%.

However, the internal buffering space of BSC is limited. If CPU occupation hooks on high values for a long time, the BSC internal buffering space may be exhausted

111



at a certain instant because the arrival model of service requests has a high unexpectability. In this case, the new service requests might be discarded.

Try to avoid the following operations in the case of high CPU occupation:

1) Setting large amount of data on-line;2) Resetting BTS or board, or loading software to board;3) Implementing interface signaling tracing.

It is recommended to register this task on any occasion.

In practice, if CPU occupation is higher than 80%, the network is likely in abnormal status. The following can be the causes of high CPU occupation: long period of large scope link disconnection between BTS and BSC (the duration of link disconnection is longer than the period of MS periodical location update), large number of MSs simultaneously implementing location update after recovery of transmission link, short message broadcasting to entire network at NSS.

Measurement object: BM.

Recommended period: 30 minutes.

Table 3-4 Statistic items in CPU Measurement Function

No. Item name

1 Percentage of CPU occupation (%)

2 Peak percentage of CPU occupation (%)


I. Percentage of CPU occupation (%)

Description: This item measures the percentage of CPU in busy status during the measurement cycle. "CPU in busy status" can be that CPU is process system message or timing task. It is opponent to "CPU in idle status", which means that the ready message queue of operation system is empty, no clock interruption occurs and CPU is waiting for clock interruption.

Note:

The internal sampling period of CPU occupation in BSC is 10 seconds. The occupation is obtained by

calculating idle rate. This means whenever CPU is idle, the duration of its idle time is summed up.

After 10 seconds, the percentage of idle time is calculated, and then the CPU occupation is obtained

by subtracting this percentage from 1.

112



Measurement point: Whenever CPU is idle, the duration of its idle time is summed up every 10 seconds.

Formula: none.

II. Peak percentage of CPU occupation (%)

Description: Maximum CPU occupation within the measurement cycle. Measurement point: Whenever a higher CPU occupation is found within the

period, its value is recorded. Formula: none.

3.7 BSC Cell Broadcast Measurement

3.7.1 General

BSC Cell Broadcast Measurement provides statistic items for the measurement of operations of Cell Broadcast short message service (CBS) in the entire BSC. It contains three measurement types: BSC Cell Broadcast Measurement Function(Total), BSC Cell Broadcast Measurement Function(Period), BSC Cell Broadcast Measurement Function(Others). Because of the correlation of items in the first two measurement types, it is required that all the items of one measurement type be registered in the same task.

Note: The items of BSC Cell Broadcast Measurement Function(Total) are the accumulated values during the operation of BSC cell broadcast module. The items of BSC Cell Broadcast Measurement Function(Period) and BSC Cell Broadcast Measurement Function(Others) are the accumulated values during the statistic period.

To know the operation of the cell broadcast of a specified cell, it is necessary to register the relative items in Cell Broadcast Statistic.

The object of BSC cell broadcast measurement is the entire BSC. The Object Info window of task registration should display "The task needn’t special parameter". The recommended statistic cycle is 60 minutes.

Below are the details of each item, including the description, measurement point and formula. "Description" briefly introduces the trigger process and trigger cause, and the focus here is message interaction between Cell Broadcast Center (CBC) and BSC. "Measurement point" lists the causes that trigger the measurement of this item. None of the items here has measurement formula.

113



3.7.2 BSC Cell Broadcast Measurement Function(Total)

Table 3-5 lists all statistic items of BSC Cell Broadcast Measurement Function(Total).

Table 3-5 Statistic items in BSC Cell Broadcast Measurement Function(Total)

No. Item name

1 Received "write-replace" messages

2 Received "kill request" messages

3 Received "status-CBCH-query" messages

4 Received "status-message-query" messages

5 Received "set-DRX" messages

6 Received "reset request" messages

7 Reports to "write-replace" message

8 Rejections to "write-replace" message

9 Reports to "kill request" message

10 Rejections to "kill request" message

11 Reports to "status-CBCH-query" message

12 Rejections to "status-CBCH-query" message

13 Reports to "status-message-query" message

14 Rejections to "status-message-query" message

15 Reports to "set-DRX" message

16 Rejections to "set-DRX" message

17 Sent "restart-indication" messages

18 Rejections to "reset request" messages

19 Sent "failure-indication" messages

20 CBCH overload (overflow)

21 CBCH overload (underflow)

22 Received "write" messages

23Reports to "write" messages

24 Rejections to "write" messages

25Received "replace" messages

26 Reports to "replace" messages

27Rejections to "replace" messages

28Capacity of message library

29Disconnected times of BM 1


31 Disconnected times of BM 3

32 Disconnected times of BM 4

114







37Disconnected times of CBC

I. Received "write-replace" messages

Description: CBC sends a WRITE-REPLACE message to the BSC when a new message is created or a message already broadcast is modified. After receiving this message and confirming its correctness, BSC will judge whether it is a new message or a substitute. If it is a new message, it will store it in the message library. If it is a substitute message, it will delete the corresponding old message, and then store the new one in the message library. Next, BSC sends REPORT Response to CBC. If the WRITE-REPLACE message BSC receives is incorrect (not conforming to ETSI GSM 03.41), BSC will return REJECT Response. Related items: Reports to "write-replace" message and Rejections to "write-replace" message .

Measurement point: As shown in Figure 3-39 A, this item is measured when BSC receives WRITE-REPLACE from CBC regardless of the correctness of this message.

Formula: None.

CBC BSC

WRITE-REPLACE Request

REPORT Response

A

REJECT Response C

B

A: Received "write-replace" messages

B: Reports to "write-replace" message

C: Rejections to "write-replace" message

Figure 3-39 Send broadcast short message

II. Received "kill request" messages

Description: CBC sends a KILL Request message to the BSC when a Cell Broadcast(CB) message sent to the specified(one or multiple) cells is deleted. After receiving this message and confirming its correctness, BSC will delete it

115



from the message library. Next, BSC sends REPORT Response to CBC. If the KILL Request BSC receives is incorrect, BSC will return REJECT Response. Related items: Reports to "kill request" message and Rejections to "killrequest" message .

Measurement point: As shown in Figure 3-40 A, this item is measured when BSC receives KILL Request from CBC regardless of the correctness of this message.

Formula: None.

CBC

KILL Request

REPORT Response

REJECT Response

BSC

A

C

B

A: Received "kill request" messages

B: Reports to "kill request" message

C: Rejections to "kill request" message

Figure 3-40 Delete short message

III. Received "status-CBCH-query" messages

Description: CBC sends STATUS CBCH QUERY Request to the BSC in order to obtain the current loading of the CBCH of particular cells. After receiving this message and confirming its correctness, BSC will query the relative data in cell broadcast data library, and sends STATUS-CBCH-QUERY Response to CBC. If the received STATUS-CBCH-QUERY Request is incorrect, BSC will return REJECT Response. Related items: Rejections to "status-CBCH-query"message and Reports to "status-CBCH-query" message .

Measurement point: As shown in Figure 3-41 A, this item is measured when BSC receives STATUS-CBCH-QUERY request from CBC regardless of the correctness of this message.

Formula: None.

116



CBC STATUS-CBCH-QUERY Request

STATUS-CBCH-QUERY Response

REJECT Response

BSC A

C

B

A: Received "status-CBCH-query" messages

B: Reports to "status-CBCH-query" message

C: Rejections to "status-CBCH-query" message

Figure 3-41 Query broadcast channel

IV. Received "status-message-query" messages

Description: CBC sends a STATUS-MESSAGE-QUERY Request to the BSC in order to obtain the current status of CB message for the cells referenced. After receiving this message and confirming its correctness, BSC will query the relative data in cell broadcast data library, and sends STATUS-MESSAGE-QUERY Response to CBC. If the received STATUS-MESSAGE-QUERY Request is incorrect, BSC will return REJECT Response. Related items: Reports to "status-message-query" message and Rejections to "status-message-query" message .

Measurement point: As shown in Figure 3-42 A, this item is measured when BSC receives STATUS- MESSAGE-QUERY Request from CBC regardless of the correctness of this message.

Formula: None.

CBC STATUS-MESSAGE-QUERY Request

STATUS-MESSAGE-QUERY Response

REJECT Response

BSC A

C

B

A: Received "status-message-query" messages

B: Reports to "status-message-query" message

C: Rejections to "status-message-query" message

Figure 3-42 Query the transmission of broadcast short message

117



V. Received "set-DRX" messages

Description: DRX (Discontinuous Reception) mode can be configured in CBC so that the MS can receive the CB message in DRX mode. In this mode, CBC sends SET-DRX Request to BSC. After receiving this message and confirming its correctness, BSC will set the next schedule message according to the parameter in the message, and send SET-DRX Response to CBC. If the received SET-DRX Request is incorrect, BSC will return REJECT Response. Related items: Reports to "set-DRX" message and Rejections to "set-DRX"message .

Measurement point: As shown in Figure 3-43 A, this item is measured when BSC receives SET-DRX Request from CBC regardless of the correctness of this message.

Formula: None.

CBC SET-DRX Request

SET-DRX Response

REJECT Response

BSC A

C

B

A: Received "set-DRX" messages

B: Reports to "set-DRX" message

C: Rejections to "set-DRX" message

Figure 3-43 Set DRX mode

VI. Received "reset request" messages

Description: When CBC resetting the specified cell, it will send RESET Request to BSC. After receiving this message and confirming its correctness, BSC will stop sending any message to the related cell, and clear the relative information in message library and cell broadcast table. If the status of Cell Broadcast Channel (CBCH) of the specified cell is normal before resetting, BSC will return RESTART-INDICATION Request. If the status of CBCH is abnormal (e.g. cell failure or not installed, CBCH blocked), BSC will return FAILURE-INDICATION Request. If the received RESET Request is incorrect, BSC will return REJECT Response. Related items: Sent "restart-indication"messages , Rejections to "reset request" messages and Sent "failure-indication" messages .

118



Measurement point: As shown in Figure 3-44 A, this item is measured when BSC receives RESET Request from CBC regardless of the status of cell CBCH.

Formula: None.

CBC BSC RESET Request

RESTART-INDICATION Request

FAILURE-INDICATION Request

REJECT Response

A

B C D

A: Received "reset request" messages

B: Successful reset

C: Received "failure-indication" messages

D: Unsuccessful reset

Figure 3-44 Reset cells

VII. Reports to "write-replace" message

Description: CBC sends a WRITE-REPLACE message to the BSC when a new message is created or a message already broadcast is modified. After receiving this message and confirming its correctness, BSC will judge whether it is a new message or a substitute. If it is a new message, it will store it in the message library. If it is a substitute message, it will delete the corresponding old message, and then store the new one in the message library. Next, BSC sends REPORT Response to CBC. Related items: Received "write-replace"messages and Rejections to "write-replace" message .

Measurement point: As shown in Figure 3-39 B, when BSC receives WRITE-REPLACE from CBC and the message is correct, it will send REPORT Response to CBC. This item is measured in this case.

Formula: None.

VIII. Rejections to "write-replace" message

Description: CBC sends a WRITE-REPLACE message to the BSC when a new message is created or a message already broadcast is modified. After receiving this message and it is incorrect, BSC will return REJECT Response. Related items: Received "write-replace" messages and Reports to "write-replace" message.

119



Measurement point: As shown in Figure 3-39 C, when BSC receives WRITE-REPLACE from CBC and the message is incorrect, it will send REJECT Response to CBC. This item is measured in this case.

Formula: None.

IX. Reports to "kill request" message

Description: CBC sends a KILL Request message to the BSC when a CB message sent to the specified(one or multiple) cells is deleted. After receiving this message and confirming its correctness, BSC will delete it from the message library. Next, BSC sends REPORT Response to CBC. Related items: Received "kill request" messages and Rejections to "kill request" message .

Measurement point: As shown in Figure 3-40 B, when BSC receives KILL Request from CBC and the message is correct, it will send REPORT Response to CBC. This item is measured in this case.

Formula: None.

X. Rejections to "kill request" message

Description: CBC sends a KILL Request message to the BSC when a CB message sent to the specified(one or multiple) cells is deleted. After receiving this message and it is incorrect, BSC will return REJECT Response. Related items: Received "kill request" messages and Reports to "kill request"message .

Measurement point: As shown in Figure 3-40 C, when BSC receives KILL Request from CBC and the message is incorrect, it will send REJECT Response to CBC. This item is measured in this case.

Formula: None.

XI. Reports to "status-CBCH-query" message

Description: CBC sends STATUS CBCH QUERY Request to the BSC in order to obtain the current loading of the CBCH of particular cells. After receiving this message and confirming its correctness, BSC will query the relative data in cell broadcast data table, and sends STATUS-CBCH-QUERY Response to CBC. Related items: Received "status-CBCH-query" messages and Reports to"status-message-query" message.

Measurement point: As shown in Figure 3-41 B, when BSC receives STATUS-CBCH-QUERY Request from CBC and the message is correct, it will send REPORT Response to CBC. This item is measured in this case.

Formula: None.

120



XII. Rejections to "status-CBCH-query" message

Description: CBC sends STATUS CBCH QUERY Request message to the BSC in order to obtain the current loading of the CBCH of particular cells. If the received STATUS-CBCH-QUERY Request is incorrect, BSC will return REJECT Response. Related items: Received "status-CBCH-query" messages and Rejections to "status-CBCH-query" message .

Measurement point: As shown in Figure 3-41 C, when BSC receives STATUS-CBCH-QUERY Request from CBC and the message is incorrect, it will send REJECT Response to CBC. This item is measured in this case.

Formula: None.

XIII. Reports to "status-message-query" message

Description: CBC sends a STATUS-MESSAGE-QUERY Request to the BSC in order to obtain the current status of CB message for the cells referenced. After receiving this message and confirming its correctness, BSC will query the relative data in cell broadcast data table, and sends STATUS-MESSAGE-QUERY Response to CBC. Related items: Received "status-message-query"messages and Rejections to "status-message-query" message .

Measurement point: As shown in Figure 3-42 B, when BSC receives STATUS- MESSAGE -QUERY Request from CBC and the message is correct, it will send REPORT Response to CBC. This item is measured in this case.

Formula: None.

XIV. Rejections to "status-message-query" message

Description: CBC sends a STATUS-MESSAGE-QUERY Request message to the BSC in order to obtain the current status of CB message for the cells referenced. If the received STATUS-MESSAGE-QUERY Request is incorrect, BSC will return REJECT Response. Related items: Reports to "status-message-query" message and Reports to "status-message-query"message .

Measurement point: As shown in Figure 3-42 C, when BSC receives STATUS- MESSAGE -QUERY Request from CBC and the message is incorrect, it will send REJECT Response to CBC. This item is measured in this case.

Formula: None.

XV. Reports to "set-DRX" message

Description: DRX (Discontinuous Reception) mode can be configured in CBC so that the MS can receive the CB message in DRX mode. In this mode, CBC sends SET-DRX Request to BSC. After receiving this message and confirming its correctness, BSC will set the scheduling message of next transmission according to the parameter in the message, and send SET-DRX Response to

121



CBC. If the received SET-DRX Request is incorrect, BSC will return REJECT Response. Related items: Received "set-DRX" messages and Rejections to"set-DRX" message .

Measurement point: As shown in Figure 3-43 B, when BSC receives SET-DRX Request from CBC and the message is correct, it will send SET-DRX Response to CBC. This item is measured in this case.

Formula: None.

XVI. Rejections to "set-DRX" message

Description: DRX (Discontinuous Reception) mode can be configured in CBC so that the MS can receive the CB message in DRX mode. In this mode, CBC sends SET-DRX Request to BSC. If the received SET-DRX Request is incorrect, BSC will return REJECT Response. Related items: Received "set-DRX" messages and Rejections to "set-DRX" message .

Measurement point: As shown in Figure 3-43 C, when BSC receives SET-DRX Request from CBC and the message is incorrect, it will send REJECT Response to CBC. This item is measured in this case.

Formula: None.

XVII. Sent "restart-indication" messages

Description: When CBC resetting the specified cell, it will send RESET Request to BSC. After receiving this message and confirming its correctness, BSC will stop sending any message to the related cell, and clear the relative information in message library and cell broadcast table. If the status of Cell Broadcast Channel (CBCH) of the specified cell is normal before resetting, BSC will return RESTART-INDICATION Request. Related items: Received"reset request" messages , Rejections to "reset request" messages and Sent"failure-indication" messages .

Measurement point: Figure 3-44 B, when BSC receives RESET Request from CBC and the status of the cell CBCH is normal, it will send RESTART-INDICATION Request to CBC. This item is measured in this case.

Formula: None.

XVIII. Rejections to "reset request" messages

Description: When CBC resetting the specified cell, it will send RESET Request to BSC. If the received RESET Request is incorrect, BSC will return REJECT Response. Related items: Received "reset request" messages , Sent"restart-indication" messages and Sent "failure-indication" messages .

Measurement point: Figure 3-44 D, when BSC receives RESET Request from CBC and the message is incorrect, it will send REJECT Response to CBC. This item is measured in this case.

122



Formula: None.

XIX. Sent "failure-indication" messages

Description: When resetting the specified cell, CBC will send RESET Request to BSC. After receiving this message and confirming its correctness, BSC will stop sending any message to the related cell, and clear the relative information in message library and cell broadcast table. If the status of Cell Broadcast Channel (CBCH) of the specified cell is abnormal, BSC will return FAILURE-INDICATION Request. Related items: Received "reset request" messages , Sent "restart-indication" messages and Rejections to "reset request"messages .

Measurement point:1) As shown in Figure 3-44 C, when BSC receives RESET Request from

CBC and the message is correct while the status of CBCH is incorrect, it will send FAILURE-INDICATION Request to CBC. This item is measured in this case.

2) This item is also measured when the links between BSC and Cell Broadcast DataBase (CDB) are all disconnected.

Formula: None.

XX. CBCH overload (overflow)

Description: BTS reports the information about load of CBCH to BSC with the message CBCH Loading Indication, and requests BSC to implement corresponding flow control. According to the reported load type ("overflow" and "underflow"), BSC measures the times of overflow/underflow.

Measurement point: As shown in Figure 3-45 A, this item is measured when BSC receives CBCH Loading Indication from BTS, and load type is overflow.

Formula: None.

BTS

CBCH Loading Indication

BSC

A(B)

A: CBCH overload (overflow)

B: CBCH overload (underflow)

Figure 3-45 BTS reports CBCH overflow

XXI. CBCH overload (underflow)

Description: BTS reports the information about load of CBCH to BSC with the message CBCH Loading Indication, and requests BSC to implement

123



corresponding flow control. According to the reported load type ("overflow" and "underflow"), BSC measures the times of overflow/underflow.

Measurement point: As shown in Figure 3-45 B, this item is measured when BSC receives CBCH Loading Indication from BTS, and load type is underflow.

Formula: None.

XXII. Received "write" messages

Description: CBC sends a WRITE-REPLACE message to the BSC when a new message is created or a message already broadcast is modified. After receiving this message and confirming its correctness, BSC will judge whether it is a new message or a substitute. If it is a new message, it will store it in the message library. If it is a substitute message, it will delete the corresponding old message, and then store the new one in the message library. Next, BSC sends REPORT Response to CBC. If the WRITE-REPLACE message BSC receives is incorrect (not conforming to ETSI GSM 03.41), BSC will return REJECT Response. Related items: Reports to "write" messages and Rejections to "write" messages .

Measurement point: As shown in Figure 3-46 A, this item is measured when BSC receives WRITE-REPLACE from CBC which contains WRITE within it and it is correct.

Formula: None.

A: Received "write" messages

B: Reports to "write" messages

C: Rejections to "write" messages

Figure 3-46 Received "write" messages

XXIII. Reports to "write" messages

Description: CBC sends a WRITE-REPLACE message to the BSC when a new message is created or a message already broadcast is modified. After receiving this message and confirming its correctness, BSC will judge whether

124



it is a new message or a substitute. If it is a new message, it will store it in the message library. If it is a substitute message, it will delete the corresponding old message, and then store the new one in the message library. Next, BSC sends REPORT Response to CBC. Related items: Received "write" messages and Rejections to "write" messages .

Measurement point: As shown in Figure 3-46 B, when BSC receives WRITE-REPLACE from CBC which contains WRITE within it and it is correct, then BSC sends REPORT Response to CBC. In this case, the item is measured.

Formula: None.

XXIV. Rejections to "write" messages

Description: CBC sends a WRITE-REPLACE message to the BSC when a new message is created or a message already broadcast is modified. After receiving this message and it is incorrect, BSC will return REJECT Response. Related items: Received "write" messages and Reports to "write" messages .

Measurement point: As shown in Figure 3-46 C, when BSC receives WRITE-REPLACE from CBC which contains WRITE within it and it is incorrect, BSC will return REJECT Response to CBC. In this case, the item is measured.

Formula: None.

XXV. Received "replace" messages

Description: CBC sends a WRITE-REPLACE message to the BSC when a new message is created or a message already broadcast is modified. After receiving this message and confirming its correctness, BSC will judge whether it is a new message or a substitute. If it is a new message, it will store it in the message library. If it is a substitute message, it will delete the corresponding old message, and then store the new one in the message library. Next, BSC sends REPORT Response to CBC. If the WRITE-REPLACE message BSC receives is incorrect (not conforming to ETSI GSM 03.41), BSC will return REJECT Response. Related items: Reports to "replace" messages and Rejections to "replace" messages .

Measurement point: As shown in Figure 3-46 A, this item is measured when BSC receives WRITE-REPLACE from CBC which contains REPLACE within it and it is correct.

Formula: None.

XXVI. Reports to "replace" messages

Description: CBC sends a WRITE-REPLACE message to the BSC when a new message is created or a message already broadcast is modified. After receiving this message and confirming its correctness, BSC will judge whether it is a new message or a substitute. If it is a new message, it will store it in the

125



message library. If it is a substitute message, it will delete the corresponding old message, and then store the new one in the message library. Next, BSC sends REPORT Response to CBC. Related items: Received "replace"messages and Rejections to "replace" messages .

Measurement point: As shown in Figure 3-46 B, when BSC receives WRITE-REPLACE from CBC which contains REPLACE within it and it is correct, then BSC sends REPORT Response to CBC. In this case, the item is measured.

Formula: None.

XXVII. Rejections to "replace" messages

Description: CBC sends a WRITE-REPLACE message to the BSC when a new message is created or a message already broadcast is modified. After receiving this message and it is incorrect, BSC will return REJECT Response. Related items: Received "replace" messages and Reports to "replace"messages .

Measurement point: As shown in Figure 3-46 C, when BSC receives WRITE-REPLACE from CBC which contains REPLACE within it and it is incorrect, BSC will return REJECT Response to CBC. In this case, the item is measured.

Formula: None.

XXVIII. Capacity of message library

Description: After receiving a broadcast message from CBC, BSC will store the message into message library. This item gives the percentage of number of storded messages in the library to the capacity of the library.

Measurement point: BSC gets the number of messages in message library every five minutes.

Formula: None.

XXIX. Disconnected times of BM 1

Description: The cell broadcast function is completed by CDB and each BM module. CDB is the bridge of communication between CBC and BSC’s BM module, board GMEM responses for communication between BMs and CDB. During running, cases such as board broken will make the communication stop, then the messages can not be broadcast. This item gives the times of communication broken.

Measurement point: When the communication between CDB and BSC’s BM1 broken, this item is measured.

Formula: None.

126



XXX. Disconnected times of BM 2



Formula: None.

XXXI. Disconnected times of BM 3



Formula: None.

XXXII. Disconnected times of BM 4



Formula: None.

XXXIII. Disconnected times of BM 5


127




Formula: None.

XXXIV. Disconnected times of BM 6



Formula: None.

XXXV. Disconnected times of BM 7



Formula: None.

XXXVI. Disconnected times of BM 8



Formula: None.

XXXVII. Disconnected times of CBC

Description: The cell broadcast function is completed by CDB and each BM module. CDB is the bridge of communication between CBC and BSC’s BM

128



module, board GMEM responses for communication between BMs and CDB. During running, cases such as board broken will make the communication stop, then the messages can not be broadcast. This item gives the times of communication broken.

Measurement point: When the communication between CDB and CBC broken, this item is measured.

Formula: None.

3.7.3 BSC Cell Broadcast Measurement Function(Period)

Table 3-1 lists all statistic items of BSC Cell Broadcast Measurement Function(Period). For detailed information of each items, please refter to 3.7.2 .

Table 3-1 Statistic items in BSC Cell Broadcast Measurement Function(Period)

No. Item name

1 Received"write-replace"messagesintheperiod

2 Received "kill request" messages in the period

3 Received "status-CBCH-query" messages in the period

4 Received "status-message-query" messages in the period

5 Received "set-DRX" messages in the period

6 Received "reset request" messages in the period

7 Reports to "write-replace" message in the period

8 Rejections to "write-replace" message in the period

9 Reports to "kill request" message in the period

10 Rejections to "kill request" message in the period

11 Reports to "status-CBCH-query" message in the period

12 Rejections to "status-CBCH-query" message in the period

13 Reports to "status-message-query" message in the period

14 Rejections to "status-message-query" message in the period

15 Reports to "set-DRX" message in the period

16 Rejections to "set-DRX" message in the period

17 Sent "restart-indication" messages in the period

18 Rejections to "reset request" messages in the period

19 Sent "failure-indication" messages in the period

20 CBCH overload (overflow) in the period

21 CBCH overload (underflow) in the period

22 Received "write" messages in the period

23 Reports to "write" messages in the period

24 Rejections to "write" messages in the period

129



25 Received "replace" messages in the period

26 Reports to "replace" messages in the period

27 Rejections to "replace" messages in the period

28 Disconnected times of BM 1 in the period








36 Disconnected times of CBC in the period

37 Received"write-replace"messagesintheperiod

3.7.4 BSC Cell Broadcast Measurement Function(Others)

Table 3-2 lists all statistic items of BSC Cell Broadcast Measurement Function(Others).

Table 3-2 Statistic items in BSC Cell Broadcast Measurement Function(Others)

I. Configer Cell Number in the period

Description: BSC receives broadcast messages from CBC through CDB, then BSC broadcast to the cells in it according to CBC’s broadcast schedure and the cell configured in BSC. This item gives the number of cells configured in BSC.

Measurement point: At the end of statistic period, the number of installed cells in BSC will be measured in this item.

Formula: None.

II. Broadcasting Cell Number in the period

Description: BSC receives broadcast messages from CBC through CDB, then BSC broadcast to the cells in it according to CBC’s broadcast schedure and the cell configured in BSC. This item gives the number of cells broadcasted in BSC in the period.

130

No. Item name1 Configer Cell Number in the period2 Broadcasting Cell Number in the period3 Broadcasting Cell Rate in the period



Measurement point: When BSC broadcasts a message to a cell in it, this item is measured

Formula: None.

III. Broadcasting Cell Rate in the period

Description: This item is the ratio of the number of cells broadcasted in BSC in the period to the number of all the installed cells in BSC.

Measurement point: None. Formula: Broadcasting Cell Number in the period / Configer Cell Number in the

period

3.8 MTP Measurement Function

3.8.1 General

In SS7 protocol system, SCCP (Signaling Connection Control Part) and MTP (Message Transfer Part) provide comprehensive network function for the application layer.


The measurement object of MTP Measurement Function is the signaling link managed by MTP service module of BSC. User can observe the operation of MTP processing part of A interface and analyze the operation of SS7 system so as to implement effective management over signaling network resources and evaluate the resource performance and effectiveness of resource utilization.

Table 3-3 Statistic items in MTP Measurement Function

No. Item name

1 Signaling link in service duration

2 Signaling link unavailable duration

3 Signaling link failure

4 Signaling link failure duration

5 Inhibitted local links

6 Local link inhibit duration

7 Inhibitted remote links

8 Remote link inhibit duration

9 Remote processor failure

10 Remote processor failure duration

11 Signaling link local auto rotate

131



12 Message signaling units (O)

13 Signaling octets (O)

14 Signaling link sending rate (%)

15 Message signaling units (I)

16 Signaling octets (I)

17 Signaling link receiving rate (%)

18 Signaling link in congestion

19 Signaling link congestion time

20 Lost message signaling units due to congestion

21 Transfer-prohibited signals (TFP) (I)


I. Signaling link in service duration

Description: This item measures the duration of SS7 link in normal service. Measurement point: MTP service module of BSC checks the status of SS7 link

once per second. This item is measured when the status of the SS7 link is normal.

Formula: none.

II. Signaling link unavailable duration

Description: This item measures the duration of SS7 link unavailable for various causes including but not limited to local management inhibited, remote management inhibited and signaling link failure.

Measurement point: MTP service module of BSC checks the status of SS7 link once per second. This item is measured when the link is unavailable.

Formula: none.

III. Signaling link failure

Description: This item measures the times of SS7 link out of service for various causes. When a signaling link is out of service, its status is unavailable. But when a signaling link is unavailable, it is not necessarily out of service. For example, a signaling link can be unavailable due to remote management inhibited, but this link is not faulty.

Measurement point: This item is measured when SS7 is out of service. Formula: none.

132



IV. Signaling link failure duration

Description: This item measures the duration of signaling link out of service due to link failure. If the MTP service module of BSC receives the message indicating the failure of a remote processor via an SS7 link, and then this link is out of service due to failure, the measurement of the remote processor failure duration will be terminated, and only the signaling link failure duration will be measured.

Measurement point: MTP service module of BSC checks the status of SS7 link once per second. This item is measured when the link is out of service.

Formula: none.

V. Inhibitted local links

Description: This item measures the times of maintenance system successfully inhibiting the SS7 link. In this occasion, the status of the SS7 link is unavailable.

Measurement point: This item is measured when the SS7 link is successfully inhibited by the maintenance system.

Formula: none.

VI. Local link inhibit duration

Description: This item measures the duration of signaling link in the status of local management inhibited after the SS7 link is successfully inhibited by maintenance system.

Measurement point: MTP service module of BSC checks the status of SS7 link once per second. This item is measured when the link is in the status of local management inhibited.

Formula: none.

VII. Inhibitted remote links

Description: This item measures the times of remote signaling point successfully inhibiting SS7 link. In this case, the status of SS7 link is unavailable.

Measurement point: This item is measured when the SS7 link is successfully inhibited by a remote signaling point.

Formula: none.

VIII. Remote link inhibit duration

Description: This item measures the duration of signaling link in the status of remote management inhibited after the SS7 link is successfully inhibited by remote signaling point.

133



Measurement point: MTP service module of BSC checks the status of SS7 link once per second. This item is measured when the link is in the status of remote management inhibited.

Formula: none.

IX. Remote processor failure

Description: This item measures the times of MTP service module of BSC receiving the message indicating remote processor failure via an SS7 link. In this occasion, the status of SS7 is unavailable.

Measurement point: This item is measured when MTP service module of BSC receives the message indicating remote processor failure.

Formula: none.

X. Remote processor failure duration

Description: This item measures the duration of signaling link in the status of unavailable due to remote processor failure after MTP service module of BSC receives the message indicating remote processor failure.

Measurement point: MTP service module of BSC checks the status of SS7 link once per second. This item is measured when the link unavailable due to remote processor failure.

Formula: none.

XI. Signaling link local auto rotate

Description: This item measures the times of MTP service module of BSC switching the service from one SS7 link to another SS7 link when the status of the SS7 link changes from available to unavailable.

Measurement point: This item is measured when MTP service module of BSC initiates service switching on SS7 links.

Formula: none.

XII. Message signaling units (O)

Description: This item measures the number of message signal units transmitted by MTP service module of BSC via an SS7 link.

Measurement point: This item is measured when MTP service module of BSC sends message signal unit via an SS7 link.

Formula: none.

XIII. Signaling octets (O)

Description: This item measures the number of bytes occupied by Signaling Information Field (SIF) and Service Information Octet (SIO) in the message signal unit transmitted by MTP service module of BSC via an SS7 link.

134



Measurement point: This item is measured when MTP service module of BSC transmits message signal unit via an SS7 link.

Formula: none.

XIV. Signaling link sending rate (%)

Description: This item measures the percentage of message signal units sent by MTP service module of BSC via an SS7 link to the bearing capability (bandwidth) of a signaling link. The bearing capability of a signaling link is 8k Byte/s, i.e. 8 1024 = 8192 (Byte/s). Each message signal unit contains message contents (SIF + SIO) of several bytes and other information of 6 bytes. Therefore the bytes of message signal units transmitted via a signaling link can be calculated with the formula: "Signaling octets (O) + Message signaling units (O) 6".

Measurement point: none. Formula: (Signaling octets (O) + Message signaling units (O) 6) / (8192

measurement cycle(second))

XV. Message signaling units (I)

Description: This item measures the number of message signal units received by MTP service module of BSC via an SS7 link.

Measurement point: This item is measured when MTP service module of BSC receives message signal unit via an SS7 link.

Formula: none.

XVI. Signaling octets (I)

Description: This item measures the number of bytes occupied by Signaling Information Field (SIF) and Service Information Octet (SIO) in the message signal unit received by MTP service module of BSC via an SS7 link.

Measurement point: This item is measured when MTP service module of BSC receives message signal unit via an SS7 link.

Formula: none.

XVII. Signaling link receiving rate (%)

Description: This item measures the percentage of message signal units received by MTP service module of BSC via an SS7 link to the bearing capability (bandwidth) of signaling link. The bearing capability of signaling link is 8k Byte/s, i.e. 8 1024 = 8192 (Byte/s). Each message signal unit contains message contents (SIF + SIO) of several bytes and other information of 6 bytes. Therefore the bytes of message signal units received via a signaling link can be calculated with the formula: "Signaling octets (I) + Message signaling units (I) 6".

135



Measurement point: none. Formula: (Signaling octets (I) + Message signaling units (I) 6) / (8192

measurement cycle(second))

XVIII. Signaling link in congestion

Description: This item measures the times of the number of messages in the sending buffer to be sent from L3 of MTP service module of BSC exceeding congestion threshold.

Measurement point: This item is measured when the number of messages in the sending buffer to be sent from L3 of MTP service module of BSC exceeds congestion threshold.

Formula: none.

XIX. Signaling link congestion time

Description: This item measures the duration of the number of messages in the sending buffer sent from L3 of MTP service module of BSC exceeding congestion threshold.

Measurement point: MTP service module of BSC checks the status of SS7 link once per second. This item is measured when the number of messages in the buffer to be sent from L3 of MTP service module of BSC exceeds congestion threshold.

Formula: none.

XX. Lost message signaling units due to congestion

Description: This item measures the number of message signal units discarded when the number of messages in the sending buffer to be sent from L3 of MTP service module of BSC exceeding congestion threshold.

Measurement point: This item is measured when the number of messages in the sending buffer to be sent from L3 of MTP service module of BSC exceeds congestion threshold and the message signal units is to be discarded.

Formula: none.

XXI. Transfer-prohibited signals (TFP) (I)

Description: This item measures the times of MTP service module of BSC receiving TransFer-Prohibited (TFP) message via an SS7 link.

Measurement point: This item is measured when MTP service module of BSC receives TFP message via an SS7 link.

Formula: none.

136



3.9 Cell Measurement Function

The traffic statistic items in "Cell Measurement Function" are used to measure the traffic operation of a cell in BSC. The items can be classified into 5 types, SDCCH seizure type, TCH seizure type, paging & random access type, handover type and radio resource configuration type.

SDCCH seizure type: From the angles of channel seizure request, failure/success of seizure, congestion, traffic volume, etc., items of this type reflect the operational state of the SDCCH seizure procedure (including immediate assignment and handover), and further reflect the usage status of SDCCH resources from the aspects of number of channels in various states (blocked, idle and OOS), duration of seizure, etc.

TCH seizure type: From the angles of channel seizure request, failure/success of seizure, congestion, traffic volume, etc., items of this type reflect the operational state of the TCH seizure procedure (including very early assignment, assignment and handover), and further reflect the usage status of TCH resources from the aspects of number of channels in various states (blocked, idle and OOS), duration of seizure, etc.

Paging & random access type: From the aspects of page delivery, paging channel overload and success of paging, items of this type reflect the operational state of the paging procedure. From the aspects of immediate assignment request, immediate assignment delivery and successful immediate assignment, the items reflect the operational state of the immediate assignment procedure.

Handover type: From the angles of request, success, failure, handover failure, success of re-establishment, etc., items of this type reflect the operational states of intra-cell handover, intra-BSC intra-cell handover, and inter-BSC handover procedures. In addition, This type also comprises the items related to dual-band handover.

Radio resource configuration type: From the angles of TRX configuration, the actual configuration of various channels, initial configuration of various channels, etc., items of this type reflect the radio resources configuration status in the current system.

3.9.1 SDCCH Measurement Function


137



Table 3-4 Statistic items in SDCCH Statistic Items

No. Item name

1 Attempted SDCCH seizures (all)

2 Successful SDCCH seizures (all)

3 Successful SDCCH seizures for handover

4 Successful SDCCH seizures for immediate assignment

5 Successful SDCCH seizures for location update

6 Successful SDCCH seizures for MOC

7 Successful SDCCH seizures for MTC

8 Successful SDCCH seizures for emergency call

9 Successful SDCCH seizures for call re-establishment

10 Successful SDCCH seizures for IMSI detach

11 Attempted SDCCH seizures meeting SDCCH overflow

12 Unsuccessful SDCCH channel activation (NACK)

13 SDCCH channel activation timeout (timeout)

14 SDCCH lost radio connections (connection failure)

15 SDCCH lost radio connections (error indication)

16 Unsuccessful SDCCH seizures due to terrestrial link failures

17 Unsuccessful SDCCH seizures due to A-interface failure

18 SDCCH call drop

19 SDCCH uplink point to point short messages

20 SDCCH downlink point to point short messages

21 Configured SDCCHs

22 Available SDCCHs

23 Average SDCCH busy time (second)

24 All SDCCH busy time (second)

25 Average num. of busy SDCCHs

26 Maximum num. of busy SDCCHs

27 Average num. of blocked SDCCHs

28 Average num. of idle SDCCHs

29 Average num. of OOS SDCCHs

30 Configured CBCHs

31 SDCCH usability (%)

32 SDCCH blocking rate (%)

33 SDCCH traffic volume (excluding very early assignment) (ERL)

34 SDCCH call drop rate (%)

35 Traffic density at average SDCCH call drop

36 SDCCH RF lost rate (%)

37 SDCCH channel activation NACK rate

138



38 SDCCH channel activation timeout rate

39 SDCCH seizure failures

40 SDCCH traffic volume (including very early assignment) (ERL)

I. Attempted SDCCH seizures (all)

Description: In the immediate assignment procedure, MS directly requests BSS to allocate channels. In the incoming BSC handover procedures, MSC requests BSS to allocate channels to MS. In the intra-BSC handover procedure, BSC itself requests BSS to reallocate radio channels. In the above procedures, if the requested channel type is SDCCH, this item shall be measured after BSC receives a relevant request.

Note:

SDCCH handover:

Handover happens on SDCCH.

Channel reallocation:

In the immediate assignment procedure, Huawei BSC supports channel reallocation. BSC initiates

radio channel allocation when it receives CHANNEL REQUIRED message from BTS. BSC allocates a

TCH if the access cause value of CHANNEL REQUIRED is "emergency call" or "call re-

establishment" and BSC supports very early assignment TCH. Otherwise, BSC allocates a SDCCH.

BSC reallocates radio channel automatically based on "GSM 0408" if BSC supports very early

assignment of TCH and channel allocation fails due to no radio resource available. In other words

BSC allocates a TCH automatically if SDCCH allocation fails and the access cause is not "location

update", and similarly, BSC allocates a SDCCH automatically if TCH allocation fails. So, to one

CHANNEL REQUEST message, BSC measures both SDCCH and TCH seizure times.

Very early assignment TCH:

If BSC allocates a TCH as a signaling channel in immediate assignment procedure, instead of the

traffic channel allocation procedure, the Mode Modify procedure can be implemented in the

assignment procedure.

Assignment SDCCH:

In the assignment procedure, MSC sends ASSIGNMENT REQUEST message to BSC to request for

a radio channel. BSC responses ASSIGNMENT COMPLETE message to MSC directly if the channel

type in the ASSIGNMENT REQUEST is SDCCH. In this case, BSC implements signaling or short

message transmission on the channel already allocated. BSC does not measure either "attempted

SDCCH seizures" or "successful SDCCH seizures" for it does not allocate a new channel. Instead, it

measures the times of "assignment requests" and "assignment success" after successfully sending

ASSIGNMENT COMPLETE message.

Discard CHANNLE REQUIRED in internal flow:

139



In the immediate assignment procedure, BSC receives CHANNEL REQUIRED messages from BTS.

BSC discards these messages if the system is too busy to respond. In this case, "attempted TCH" or

"SDCCH seizures" will be measured but "successful or unsuccessful channel seizures" will not be

measured.

Measurement point: "SD-ATT-C1" in Figure 3-47 , "SD-ATT-C2" in Figure 3-49 and "SD-ATT-C3" in Figure 3-50 indicate the measurement points of this statistic item in the calling procedure.1) In the immediate assignment procedure, this item is measured when BSC

receives a CHANNEL REQUIRED message from BTS and the requested

channel type is SDCCH (requested by MS, or by the system during the

second allocation procedure).

2) In the intra-BSC SDCCH handover procedure (the originating cell and target cell belong to the same BSC), this item is measured when the target cell receives an Intercell Handover Request message (internal message in Huawei BSC) from the originating cell. This item is also measured on intra-cell handover occasions. The mere difference is that the target cell and originating cell are the same.

3) In the inter-BSC handover procedure, this item is measured when BSC receives a HANDOVER REQUEST message from other BSC, and the handover takes place on SDCCH.

Formula: none.

SD-ATT-C1: Attempted SDCCH seizures (all)

TCH -ATT-C1: Attempted TCH seizures (all)

TCH -ATT-C6: Attempted TCH seizures for very early assignment

TCH -ATT-C7: Attempted TCH seizures for SDCCH busy

140



SD-SUCC-C1: Successful SDCCH seizures (all)

SD-SUCC-C4: Successful SDCCH seizures for immediate assignment

TCH -SUCC-C6: Successful TCH seizures for very early assignment

TCH -SUCC-C1: Successful TCH seizures (all)

TCH -SUCC-C61: Successful TCH allocation for very early assignment

TCH -SUCC-C62: Successful TCH seizures for SDCCH busy


MS BTS BSC

.ASSIGN CMMAND

MSC

ASSIGNMENT REQUEST

SABM


ASSIGNMENT COMPLETE


(directly retry)HANDOVER REQUEST ACK

CHANNEL ACTIVATION


TCH-ATT-C 2TCH-ATT-C 8TCH-ATT-C 9TCH-ATT-C 10TCH-ATT-C 5

TCH-ATT-C13

TCH-ATT-C14QUEUEING INDICATION

TCH-ATT-C16

TCH-ATT-BSC 2

TCH-SUCC-C23

TCH-SUCC-C21,22

TCH-SUCC-C51,54,55,56

TCH-SUCC-C52,53,54,55,56TCH-SUCC-C82,83

TCH-SUCC-C81TCH-SUCC-C91TCH-SUCC-C101

TCH-SUCC-C92,93TCH-SUCC-C102,103

TCH-SUCC-C13


TCH -ATT-C5: Attempted TCH seizures for call

TCH -ATT-C8: Attempted TCH seizures for MOC

TCH -ATT-C9: Attempted TCH seizures for MTC

TCH -ATT-C10: Attempted TCH seizures for call re-establishment

TCH -ATT-C13: Attempted TCH seizures for directed retry

TCH -ATT-C14: TCH queue requests

TCH -ATT-C16: TCH preemption requests

TCH -SUCC-C21--23: Successful TCH seizures (all)

TCH -SUCC-C51--53: Successful TCH seizures for call

TCH -SUCC-C81--83: Successful TCH seizures for MOC

TCH -SUCC-C91--93: Successful TCH seizures for MTC

TCH -SUCC-C101--103: Successful TCH seizures for call re-establishment

TCH -SUCC-C13: Successful TCH seizures for directed retry

TCH -SUCC-C54: Successful assignments of speech version 1 TCH

141





Figure 3-48 Assignment procedure-channel seizure procedure



TCH -ATT-C11: Attempted TCH seizures for intraBSC incoming cell handover

TCH -ATT-C17: Attempted TCH seizures for intracell handover

TCH -SUCC-C17: Successful TCH seizures for intracell handover


TCH -SUCC-C11: Successful TCH seizures for intraBSC incoming cell handover

SD-SUCC-C2: Successful SDCCH seizures for handover, Successful SDCCH seizures (all)


142




TCH -ATT-C4:Attempted TCH seizures (all)

TCH -ATT-C12: Attempted TCH seizures for interBSC incoming cell handover


TCH -SUCC-C12: Successful TCH seizures for interBSC incoming cell handover

SD -SUCC-C3: Successful SDCCH seizures for handover, Successful SDCCH seizures (all)

Figure 3-50 Incoming BSC handover channel seizure procedure

I. Successful SDCCH seizures (all)

Description: In the immediate assignment and handover procedures, MS notifies BSS after it successfully seizes the SDCCH allocated by the network. This item is measured when BSC receives the notification. For related contents, please refer to Attempted SDCCH seizures (all) ".

Measurement point: "SD-SUCC-C1" in Figure 3-47 , "SD-SUCC-C2" in Figure3-49 and "SD-SUCC-C3" in Figure 3-50 indicate the measurement points of this statistic item in the calling procedure. 1) In the immediate procedure, this item is measured when BSC receives an

CHANNEL ACTIVATION ACKNOWLEDGE message for SDCCH from BTS.

2) In the incoming BSC handover on SDCCH procedure, BTS sends a HANDOVER DETECTION message to the target BSC. Upon reception of this message. This item is measured in the target BSC.

3) In the intra-BSC incoming cell handover procedure (including intracell handover) on SDCCH, BTS sends a HANDOVER DETECTION message to the target cell. This item is measured in the target cell when the target cell receiving this message.

Formula: none.

143



Note:

The message ESTABLISH INDICATION describes in this manual are all refer to that the value of

SAPI is zero, all other values are excluded.

II. Successful SDCCH seizures for handover

Description: In the SDCCH handover procedure, BTS sends a HANDOVER DETECTION message to the target cell. This item is measured when BSC receives the HANDOVER DETECTION message. For related contents, please refer to Attempted SDCCH seizures (all) ".

Measurement point: "SD-SUCC-C2" in Figure 3-49 and "SD-SUCC-C3" in Figure 3-50 indicate the measurement points of this statistic item in the calling procedure. 1) In the incoming BSC handover (incoming BSC handover on SDCCH)

procedure, BTS sends a HANDOVER DETECTION message to the target cell. BSC measures the item when receives the HANDOVER DETECTION message.

2) In the intra-BSC incoming cell handover procedure (intra-BSC incoming cell handover on SDCCH), BTS sends a HANDOVER DETECTION message to the target cell. This item is measured in the target cell when the target cell receives the HANDOVER DETECTION message.

Formula: none.

III. Successful SDCCH seizures for immediate assignment

Description: In the immediate assignment procedure for SDCCH, after successfully seizing the SDCCH allocated by BSC, MS reports a SABM frame on the SDCCH to BTS, indicating the establishment of a radio link layer connection in the multi-frame mode. BTS returns a UA frame to MS, and sends an ESTABLISH INDICATION message to BSC, notifying it to establish a normal Um interface connection. This statistic item is measured on all the occasions allowed in the service request message of ESTABLISH INDICATION. For related contents, please refer to Attempted SDCCH seizures(all) ".

Measurement point: "SD-SUCC-C4" in Figure 3-47 indicates the measurement point of this item in the calling procedure. In the immediate assignment procedure, BTS reports an ESTABLISH INDICATION message to BSC, indicating the establishment of SDCCH connection in the multi-frame mode. This item is measured when BSC receives the ESTABLISH INDICATION message.

144



Formula: none.

IV. Successful SDCCH seizures for location update

Description: This statistic item specially measures the number of times SDCCH is successfully seized for MS location update.

Measurement point: "SD-SUCC-C4" in Figure 3-47 indicates the measurement point of this item in the calling procedure. In the immediate assignment procedure, BTS reports an ESTABLISH INDICATION message to BSC, indicating the establishment of SDCCH connection in the multi-frame mode. The type of the service request message in ESTABLISH INDICATION is "LOCATION UPDATE REQUEST".

Formula: none.

V. Successful SDCCH seizures for MOC

Description: This statistic item specially measures the number of times SDCCH is successfully seized for MOC (Mobile Originated Call).

Measurement point: "SD-SUCC-C4" in Figure 3-47 indicates the measurement point of this item in the calling procedure. In the immediate assignment procedure, BTS reports an ESTABLISH INDICATION message to BSC, indicating the establishment of SDCCH connection in the multi-frame mode. The type of the service request message in ESTABLISH INDICATION is "CM SERVICE REQUEST", and the CM service type is "MOC".

Formula: none.

VI. Successful SDCCH seizures for MTC

Description: This statistic item specially measures the number of times SDCCH is successfully seized for MTC (Mobile Terminated Call).

Measurement point: "SD-SUCC-C4" in Figure 3-47 indicates the measurement point of this item in the calling procedure. In the immediate assignment procedure, BTS reports an ESTABLISH INDICATION message to BSC, indicating the establishment of SDCCH connection in the multi-frame mode. The type of the service request message in ESTABLISH INDICATION is "PAGING RESPONSE".

Formula: none.

VII. Successful SDCCH seizures for emergency call

Description: This statistic item specially measures the number of times SDCCH is successfully seized for emergency calls.

Measurement point: "SD-SUCC-C4" in Figure 3-47 indicates the measurement point of this item in the calling procedure. In the immediate assignment procedure, BTS reports an ESTABLISH INDICATION message to

145



BSC, indicating the establishment of SDCCH connection in the multi-frame mode. The type of the service request message in ESTABLISH INDICATION is "CM SERVICE REQUEST", and the CM service type is "Emergency call establishment".

Formula: none.

VIII. Successful SDCCH seizures for call re-establishment

Description: This statistic item specially measures the number of times SDCCH is successfully seized for MS call re-establishment.

Measurement point: "SD-SUCC-C4" in Figure 3-47 indicates the measurement point of this item in the calling procedure. In the immediate assignment procedure, BTS reports an ESTABLISH INDICATION message to BSC, indicating the establishment of SDCCH connection in the multi-frame mode. The type of the service request message in ESTABLISH INDICATION is "CM REESTABLISHMENT REQUEST".

Formula: none.

IX. Successful SDCCH seizures for IMSI detach

Description: This statistic item specially measures the number of times SDCCH is successfully seized for IMSI detach.

Measurement point: "SD-SUCC-C4" in Figure 3-47 indicates the measurement point of this item in the calling procedure. In the immediate assignment procedure, BTS reports an ESTABLISH INDICATION message to BSC, indicating the establishment of SDCCH connection in the multi-frame mode. The type of the service request message in ESTABLISH INDICATION is "IMSI DETACH".

Formula: none.

X. Attempted SDCCH seizures meeting SDCCH overflow

Description: in immediate assignment and handover procedure, this item is measured in the case that the MS or MSC requests BSC to allocate SDCCH but BSS has no available SDCCH.

Measurement point: if the requested channel is SDCCH but the cell has no available SDCCH, this item is measured on the following occasions: 4) BSC receives the CHANNEL REQUIRED message from the BTS.

5) The target cell receives the Intercell Handover Request message from other cells of the BSC.

6) The BSC receives the HANDOVER REQUEST message from other BSC. Formula: none

146



XI. Unsuccessful SDCCH channel activation (NACK)

Description: in immediate assignment procedure, having allocated SDCCH for the MS, BSC sends the CHANNEL ACTIVATION message to the BTS. If the BTS returns a CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE message to the BSC, this indicates that the channel activation fails.

Measurement point: this item is measured when BSC receives the CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE message from the BTS where the cell is located.

Formula: none

XII. SDCCH channel activation timeout (timeout)

Description: in immediate assignment procedure, having allocated SDCCH for the MS, BSC sends a CHANNEL ACTIVATION message to the BTS and starts the timer (internal timer, 5 seconds) to wait for the CHANNEL ACTIVATION ACKNOWLEDGE message. This item is measured if the BTS has not responded to this message when the timer expires.

Measurement point: BSC sends the CHANNEL ACTIVATION message to the BTS where the cell to be measured is located to activate the specified SDCCH. Then, this item is measured if there is no response from the BTS when the timer for the BSC to wait for the response from the BTS expires.

Formula: none

XIII. SDCCH lost radio connections (connection failure)

Description: If BTS detects that an active connection has been broken for some reason, it sends a CONNECTION FAILURE INDICATION message to the BSC informing the BSC that the call drop occurs at Um interface due to radio link connection failure.

Measurement point: BSC measures this item upon reception of the CONNECTION FAILURE INDICATION message (cause: any cause except 0X20-equipment failure and 0X22-terrestrial channel failure) from the BTS and if the failure occurs on SDCCH.

Formula: none

XIV. SDCCH lost radio connections (error indication)

Description: If BTS detects an abnormal case for a radio link layer connection, it sends a ERROR INDICATION message to BSC informing the BSC that the call drop occurs at Um interface due to radio link error. See GSM 0858 protocol.

Measurement point: BSC measures this item upon reception of the ERROR INDICATION message from the BTS and if the failure occurs on SDCCH.

Formula: none

147



XV. Unsuccessful SDCCH seizures due to terrestrial link failures

Description: If BTS detects that an active connection has been broken for some reason, it sends a CONNECTION FAILURE INDICATION message to the BSC informing the BSC that terrestrial link disconnect in ABIS interface.

Measurement point: 1) BSC measures this item upon reception of CONNECTION FAILURE

INDICATION message (cause: 0X20-equipment failure and 0X22-terrestrial channel failure) from the BTS and if the failure occurs on SDCCH.

2) This item is measured when the RSL link of the TRX that the call is running on disconnect, which will cause call drop, this item measures call drop on SDCCH for RSL disconnection.

Formula: none

XVI. Unsuccessful SDCCH seizures due to A-interface failure

Description: after the call established on SDCCH reports the ESTABLISH INDICATION message, the established SDCCH and the related link will be released if A interface connection failure occurs due to A interface connection failures.

Note:

This item is also measured if the duration of A interface trunk circuit failure exceeds 15 seconds, the

resource check of internal RR-AIR software detects exception, the inconsistency between the SCCP

code and BSSMAP code is found, SCCP connection disconnect, BSC receives RESET CIRCUIT

message from MSC.

Measurement point: This item is measured if the duration of A interface trunk circuit failure exceeds 15 seconds, SCCP connection disconnect, BSC receives RESET CIRCUIT message from MSC.

Formula: none

XVII. SDCCH call drop

Description: the description of this item is the same as that of SDCCH call drop of "BSC Measurement Function" except the measurement object is the specified cell.

Measurement point: See SDCCH call drop in "BSC Measurement Function" Formula: none

148



XVIII. SDCCH uplink point to point short messages

Description: SDCCH can be used to send the uplink/downlink short messages. This item is used to measure the number of the uplink short messages sent on SDCCH.

Measurement point: this item is measured when BSC receives the uplink short message sent on SDCCH.

Formula: none

XIX. SDCCH downlink point to point short messages

Description: SDCCH can be used to send the uplink/downlink short messages. This item is used to measure the number of the downlink short messages sent on SDCCH.

Measurement point: this item is measured when BSC receives the downlink short message sent on SDCCH.

Formula: none

XX. Configured SDCCHs

Description: This item indicates the number of SDCCHs currently configured for a certain cell on real-time basis. It includes the SDCCH dynamically adjusted from TCH. It is an average number of SDCCHs at various sampling points within the measurement cycle.

Measurement point: System checks the number of configured SDCCHs every five seconds. The accumulated value from the data got at the sampling points is divided with the times of sampling to get the average number of configure SDCCHs within the measurement cycle.

Formula: none.

XXI. Available SDCCHs

Description: This item indicates the number of available (idle or busy) SDCCHs in a certain cell on real-time basis. It includes the SDCCH dynamically adjusted from TCH. It is an average number of available SDCCHs at various sampling points within the measurement cycle.

Measurement point: System checks the number of available SDCCHs every five seconds. The accumulated value from the data got at the sampling points is divided with the times of sampling to get the average number of available SDCCHs within the measurement cycle.

Formula: none.

XXII. Average SDCCH busy time (second)

Description: This item indicates the average duration of the SDCCHs configured for a cell being busy. It shows the situation of random access

149



frequency in the objective cell from the angle of channel seizure duration. See Configured SDCCHs

Measurement point: Average duration of SDCCHs busy in a cell. Formula: Sum of the durations of SDCCHs busy in a cell / Number of

configured SDCCHs

XXIII. All SDCCH busy time (second)

Description: This item indicates the duration of no SDCCH can be allocated. It shows the situation of all SDCCHs have been allocated or blocked so that no SDCCH can be allocated any more.

Measurement point: Total duration of no SDCCH in a cell can be allocated. Formula: none.

XXIV. Average num. of busy SDCCHs

Description: This item indicates the average number of the busy SDCCHs configured for a cell. It is an average number of busy SDCCHs at various sampling points within the measurement cycle. It shows the situation of random access frequency in the objective cell from the angle of number of channel seized.

Measurement point: System checks the number of busy SDCCHs every five seconds. The accumulated value from the data got at the sampling points is divided with the times of sampling to get the average number of busy SDCCHs within the measurement cycle.

Formula: none.

XXV. Maximum num. of busy SDCCHs

Description: This item indicates the maximum number of the SDCCHs configured for a cell being busy. It is a peak value of the number of busy SDCCHs at various sampling points within the measurement cycle. It shows the highest random access frequency in the objective cell from the angle of number of channel seized.

Measurement point: System checks the number of busy SDCCHs every five seconds. The highest value by the end of the period is recorded.

Formula: none.

XXVI. Average num. of blocked SDCCHs

Description: This item indicates the average number of the blocked SDCCHs configured for a cell. It is an average number of blocked SDCCHs at various sampling points within the measurement cycle. The block of SDCCH can be caused by O&M, or by RSL link disconnection. It shows the situation of SDCCH blocked.

150



Measurement point: System checks the number of blocked SDCCHs every five seconds. The accumulated value from the data got at the sampling points is divided with the times of sampling to get the average number of blocked SDCCHs within the measurement cycle.

Formula: none.

XXVII. Average num. of idle SDCCHs

Description: This item indicates the average number of the idle SDCCHs configured for a cell. It is an average number of idle SDCCHs at various sampling points within the measurement cycle. The status of an idle SDCCH is normal and not seized. It shows the situation of SDCCH seizure in a cell within the period.

Measurement point: System checks the number of idle SDCCHs every five seconds. The accumulated value from the data got at the sampling points is divided with the times of sampling to get the average number of idle SDCCHs within the measurement cycle.

Formula: none.

XXVIII. Average num. of OOS SDCCHs

Description: This item indicates the average number of the OOS SDCCHs configured for a cell. It is an average number of OOS SDCCHs at various sampling points within the measurement cycle. The status of OOS means a channel is unavailable, it may be caused by the following reasons, channel blocked due to O&M, cell’s status changed from installed to not installed and BTS or TRX failure. It shows the situation of unavailable SDCCHs in a cell within the period.

Measurement point: System checks the number of OSS SDCCHs every five seconds. The accumulated value from the data got at the sampling points is divided with the times of sampling to get the average number of OSS SDCCHs within the measurement cycle.

Formula: none.

XXIX. Configured CBCHs

Description: CELL BROADCAST CHANNEL (CBCH) is used to transfer the cell broadcast information from CBC to MS. For the areas where cell broadcast is available, it is possible to configure CBCH with the combination of BCCH + CBCH or SDCCH + CBCH in Radio Channel Configuration Table. This item indicates the number of configured CBCHs for a cell. It is an average number of configured CBCHs at various sampling points within the measurement cycle.

Measurement point: System checks the number of configured CBCHs every five seconds. The accumulated value from the data got at the sampling points

151



is divided with the times of sampling to get the average number of configured CBCHs within the measurement cycle.

Formula: none.

XXX. SDCCH usability (%)

Description: This item indicates the percentage of usable SDCCHs accounting the configured SDCCHs. See Available SDCCHs and Configured SDCCHs .

Measurement point: none. Formula: number of usable SDCCHs / number of configured SDCCHs

XXXI. SDCCH blocking rate (%)

Description: This item indicates the percentage of times of attempted seizures meeting an SDCCH blocked state accounting the total number of SDCCH requests. See Attempted SDCCH seizures meeting SDCCH overflow and Attempted SDCCH seizures (all) .

Measurement point: none. Formula: times of attempted seizures meeting an SDCCH blocked state /

attempted SDCCH seizures (all)

XXXII. SDCCH traffic volume (excluding very early assignment) (ERL)

Description: This item indicates the traffic volume on SDCCH, i.e. the ratio of duration of MS seizing SDCCH to measurement cycle. The duration of MS seizing SDCCH is calculated by multiplying the number of MR reported by MS via SDCCH with the report period (0.47 seconds). See Sum of SDCCHmeasurement reports in the cell .

Measurement point: none. Formula: Total number of SDCCH measurement reports 0.47 / measurement

cycle (second)

XXXIII. SDCCH call drop rate (%)

Description: This item indicates the percentage of SDCCH call drops accounting all successful SDCCH seizures. See SDCCH call drop and Successful SDCCH seizures (all) .

Measurement point: none. Formula: SDCCH call drops / all successful SDCCH seizures

XXXIV. Traffic density at average SDCCH call drop

Description: This item indicates average duration of MS seizing SDCCH after which a SDCCH call drop occurs. The duration of MS seizing SDCCH is calculated by multiplying the number of MR reported by MS via SDCCH with

152



the report period (0.47 seconds). See Sum of SDCCH measurement reports inthe cell and SDCCH call drop .

Measurement point: none. Formula: Total number of SDCCH measurement reports 0.47 / SDCCH call

drops

XXXV. SDCCH RF lost rate (%)

Description: This item indicates the percentage of SDCCH call drops due to radio link disconnection when seized by MS caused by air interface causes accounting all successful SDCCH seizures. See SDCCH lost radioconnections (connection failure) , SDCCH lost radio connections (errorindication) and Successful SDCCH seizures (all) .

Measurement point: none. Formula: (times of radio link disconnection when SDCCH seized (connection

failure) + times of radio link disconnection when SDCCH seized (error indication)) / successful SDCCH seizures (all)

XXXVI. SDCCH channel activation NACK rate

Description: This item indicates the percentage of times of BTS returning CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE after receiving CHANNEL ACTIVATION aiming at SDCCH from BSC accounting times of CHANNEL ACTIVATION sent. See Unsuccessful SDCCH channel activation(NACK) , Attempted SDCCH seizures (all) and Attempted SDCCH seizuresmeeting SDCCH overflow .

Measurement point: none. Formula: Unsuccessful channel activation (NACK) / (Attempted SDCCH

seizures (all) – Attempted SDCCH seizures meeting an SDCCH blocked state)

XXXVII. SDCCH channel activation timeout rate

Description: This item indicates the percentage of times of no response from BTS within the time limit set in the timer of waiting for channel activation response after BTS receiving CHANNEL ACTIVATION aiming at SDCCH from BSC accounting times of CHANNEL ACTIVATION sent. The times of BSC sending CHANNEL ACTIVATION aiming at SDCCH can be calculated by subtracting Attempted SDCCH seizures (all) with Attempted SDCCH seizures meeting an SDCCH blocked state. See SDCCH channel activation timeout(timeout), Attempted SDCCH seizures (all) and Attempted SDCCH seizuresmeeting SDCCH overflow .

Measurement point: none. Formula: Channel activation timeout (timeout) / (Attempted SDCCH seizures

(all) - Attempted SDCCH seizures meeting an SDCCH blocked state)

153



XXXVIII. SDCCH seizure failures

Description: After MS initiates the request to seize SDCCH of a cell, there may be no available SDCCH in the cell, or after BSC initiates CHANNEL ACTIVATION, BTS may return CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE or BTS does not respond within the duration set in the timer. In these cases, MS is unable to seize SDCCH. This item measures times of MS failing to seize SDCCH in the objective cell. See Attempted SDCCHseizures meeting SDCCH overflow , Unsuccessful SDCCH channel activation(NACK) and SDCCH channel activation timeout (timeout) .

Measurement point: none. Formula: Attempted SDCCH seizures meeting an SDCCH blocked state +

Unsuccessful channel activation (NACK) + Channel activation timeout (timeout)

XXXIX. SDCCH traffic volume (including very early assignment) (ERL)

Description: This item indicates the traffic volume on signaling channels, i.e. the ratio of duration of MS seizing signaling channels to measurement cycle. The signaling channels here include SDCCH and TCH acting as signaling channel. The duration of MS seizing SDCCH channels is calculated by multiplying the number of MR reported by MS via SDCCH channels with the report period 0.47 second, the duration of MS seizing TCH channels is calculated by multiplying the number of MR reported by MS via TCH channels with the report period 0.48 second. See Sum of TCH measurement reportsduring very early assignment procedure in the cell and Sum of SDCCHmeasurement reports in the cell .

Measurement point: none. Formula: (Very early TCH measurement reports 0.48 + Total number of

SDCCH measurement reports 0.47 )/ measurement cycle (second)

3.9.2 TCH Measurement Function


Table 3-1 Statistic items in TCH statistic items

No. Item name

1Attempted TCH seizures (all)

2Attempted TCH seizures for call

3Attempted TCH seizures for very early assignment

4Attempted TCH seizures for SDCCH overflow

5Attempted TCH seizures for MOC

154



6Attempted TCH seizures for MTC

7Attempted TCH seizures for call re-establishment

8Attempted TCH seizures for intraBSC incoming cell handover

9Attempted TCH seizures for interBSC incoming cell handover

10Attempted TCH seizures for directed retry

11TCH queue requests

12TCH preemption requests

13Attempted TCH seizures for intracell handover

14Successful TCH seizures for intracell handover

15Successful TCH seizures for very early assignment

16Successful TCH seizures (all)

17Successful TCH seizures for call

18Successful TCH allocation for very early assignment

19Successful TCH allocation for SDCCH overflow

20Successful TCH seizures for MOC

21Successful TCH seizures for MTC

22Successful TCH seizures for call re-establish

23Successful TCH seizures for intraBSC incoming cell handover

24Successful TCH seizures for interBSC incoming cell handover

25Successful TCH seizures for directed retry

26Successful TCH queue operation

27Successful TCH preemption

28Successful assignments of speech version 1 TCH (excluding directed retry)



31TCH seizure failures for call(no radio resource)

32TCH seizure failures for interBSC incoming cell handover

33TCH seizure failures for intraBSC incoming cell handover

34TCH Seizure failures (all)

35Attempted TCH seizures meeting TCH overflow

36TCH seizure failures for call

37TCH seizure failures for very early assignment

38TCH seizure failures for MOC

39TCH seizure failures for MTC

40TCH seizure failures for call re-establishment

41TCH seizure failures for intraBSC incoming cell handover(no radio resource)

42TCH seizure failures for interBSC incoming cell handover(no radio resource)

43TCH seizure failures for directed retry

44TCH Queue failures for queue full

45TCH queue failures for timeout

155



46Directed retry after queue failure

47TCH seizure failures (equipment failure)

48TCH seizure failures (requested terrestrial resource unavailable)

49TCH seizure failures (terrestrial circuit already allocated)

50TCH seizure failures (invalid message contents)

51TCH call drop

52TCH drop for very early assignment

53TCH lost radio connections (connection failure)

54TCH lost radio connections (error indication)

55TCH channel activation NACKs (call)

56TCH channel activation timeout (call)

57TCH channel activation NACKs (handover)

58TCH channel activation timeout (handover)

59 TCH mode modification (NACK)

60TCH mode modification timeout

61TCH seizure failures due to terrestrial link failures

62TCH seizure failures due to A-interface failures

63Average TCH queue length

64Maximum TCH queue length

65Average TCH queue time

66TCH uplink point to point short messages

67TCH downlink point to point short messages

68TCH seizure failures for intracell handover

69TCH seizure failures for intracell handover (no radio resource)

70Configured TCHs of 1800 cell

71Configured TCHs of 900 cell

72Available TCHs

73Average num. of busy TCHs

74Maximum num. of busy TCHs

75All TCH busy time (second)

76Average TCH busy time (second)

77Average num. of idle TCHs in Interf. band 1





82Average num. of blocked TCHs

83Average num. of idle TCHs

84Average num. of OOS TCHs

85TCH usability (%)

156



86Attempted TCH seizures (excluding handover)

87Attempted TCH seizures (including handover)

88TCH seizure failures (excluding handover)

89TCH seizure failures (including handover)

90TCH congestion rate (excluding handover)(%)

91TCH congestion rate (including handover)(%)

92TCH traffic volume (excluding very early assignment) (ERL)

93Traffic density at average TCH call drop

94TCH RF lost rate (%)

95TCH call drop rate (%)

96TCH traffic volume of 1800 cell (excluding very early assignment) (ERL))

97TCH congestion rate (TCH overflow) (%)

I. Attempted TCH seizures (all)

Description: In the immediate assignment procedure, assignment procedure and inter-BSC handover procedure, MS or MSC requests BSS to allocate radio channels. In the intra-BSC handover procedure, BSC itself reallocates radio channels. In the above procedures, if the requested channel type is TCH, this item shall be measured after BSC receives a relevant request.

Measurement point: "TCH-ATT-C1"~"TCH-ATT-C4" in Figure 3-47 , Figure 3-48 , Figure 3-49 and Figure 3-50 indicate the measurement points of this statistic item in the calling procedure. In the procedures below, if the requested channel type is TCH, this item shall be measured.1) In the very early assignment procedure for TCH (The TCH allocated in the

immediate assignment procedure serves as a signaling channel), this item is measured when BSC receives a CHANNEL REQUIRED message from BTS.

2) In the assignment procedure, this item is measured when BSC receives an ASSIGNMENT REQUEST message from MSC and the requested channel type is TCH.

3) In the intra-BSC handover procedure (the originating cell and target cell belong to the same BSC), this item is measured when the target cell receives an Intercell Handover Request message (internal message in Huawei BSC) from the originating cell. This item is also measured on Intra-cell handover occasions. The mere difference is that the target cell and originating cell is the same.

4) This item is measured when BSC receives a HANDOVER REQUEST message from other BSC.

Formula: none.

157



II. Attempted TCH seizures for call

Description: This statistic item measures the number of times BSC receives ASSIGNMENT REQUEST messages from MSC requesting to seize TCH. For related information, please refer to Attempted TCH seizures (all) .

Measurement point: "TCH-ATT-C5" in Figure 3-48 indicates the measurement point of this statistic item in the calling procedure. In the assignment procedure, this item is measured when BSC receives an ASSIGNMENT REQUEST message from MSC, requesting allocation of TCH.

Formula: none.

III. Attempted TCH seizures for very early assignment

Description: This statistic item measures the number of times BSC receives CHANNEL REQUEST messages from MS requesting to seize TCH, either TCH first allocation or reallocation is included. For related information, please refer to Attempted SDCCH seizures (all) .

Measurement point: "TCH-ATT-C6" in Figure 3-47 indicates the measurement point of this statistic item in the calling procedure. In the very early assignment procedure, this item is measured when BSC receives CHANNEL REQUIRED message from BTS and the requested channel type is TCH.

Formula: none.

IV. Attempted TCH seizures for SDCCH overflow

Description: In the immediate assignment procedure, BSC receives a Channel Quest message from MS requesting to seize SDCCH, but SDCCH allocation fails due to no SDCCH available. BSS shall automatically attempt to allocate TCH at once if it supports that. This statistic item measures the number of times the system attempts to allocate TCH after SDCCH allocation fails. BSC will not implement second channel allocation if the access cause in the CHANNEL REQUEST is location update because CHANNEL REQUEST with "location update" as the access cause does not support TCH as signalling channel, For related information, please refer to Attempted TCH seizures(all) .

Measurement point: "TCH-ATT-C7" in Figure 3-47 indicates the measurement point of this item in the calling procedure. In the immediate assignment procedure, BSC receives a CHANNEL REQUEST message from MS requesting to seize SDCCH, but SDCCH allocation fails. This item is measured when the system automatically attempts to allocate TCH.

Formula: none.

158



V. Attempted TCH seizures for MOC

Description: This statistic item specially measures the number of TCH allocation requests received by BSC from MSC in the assignment procedure, requesting BSS to allocate TCH for MOC in BSC. For related contents, please refer to Attempted TCH seizures (all) .

Measurement point: "TCH-ATT-C8" in Figure 3-48 indicates the measurement point of this item. In the assignment procedure, this item is measured when BSC receives an ASSIGNMENT REQUEST message from MSC, requesting BSS to allocate TCH for MOC.

Formula: none.

VI. Attempted TCH seizures for MTC

Description: This statistic item specially measures the number of TCH allocation requests received by BSC from MSC in the assignment procedure, requesting BSS to allocate TCH for MTC in BSC. For related contents, please refer to Attempted TCH seizures (all) .

Measurement point: "TCH-ATT-C9" in Figure 3-48 indicates the measurement point of this item in the calling procedure. In the assignment procedure, this item is measured when BSC receives an ASSIGNMENT REQUEST message from MSC, requesting BSS to allocate TCH for MTC.

Formula: none.

VII. Attempted TCH seizures for call re-establishment

Description: This statistic item specially measures the number of TCH allocation requests received by BSC from MSC in the assignment procedure, requesting BSS to allocate TCH for MS call re-establishment. For related contents, please refer to Attempted TCH seizures (all) .

Measurement point: "TCH-ATT-C10" in Figure 3-48 indicates the measurement point of this item. In the assignment procedure, this item is measured when BSC receives an ASSIGNMENT REQUEST message from MSC, requesting BSS to allocate TCH for MS call re-establishment.

Formula: none.

VIII. Attempted TCH seizures for intraBSC incoming cell handover

Description: In the intra-BSC handover procedure, this statistic item measures the number of times the target cell receives Intercell Handover Request messages from the originating cell, requesting allocation of TCH.

Measurement point: "TCH-ATT-C11" in Figure 3-49 indicates the measurement point of this item in the calling procedure. In the intra-BSC handover procedure, the originating cell sends an Intercell Handover Request message to the target cell, requesting allocation of TCH. This item is measured

159



when the target cell receives this message. It is not measured on intra-cell handover occasions. For relevant contents of intra-cell handover, please refer to Attempted TCH seizures for intracell handover .

Formula: none.

IX. Attempted TCH seizures for interBSC incoming cell handover

Description: In the inter-BSC handover procedure, this statistic item measures the number of times the cell in Huawei BSC receives HANDOVER REQUEST messages from other BSC (transferred via MSC), requesting allocation of TCH.

Measurement point: "TCH-ATT-C12" in Figure 3-50 indicates the measurement point of this item in the calling procedure. This item is measured when BSC receives an incoming BSC handover request (HANDOVER REQUEST), requesting allocation of TCH.

Formula: none.

X. Attempted TCH seizures for directed retry

Description: BSC performs message content check and status check after it receives an ASSIGNMENT REQUEST message from MSC.If it finds no available channel for allocation, and it supports directed retry, BSC can automatically initiate directed retry to another cell in the current BSC or to a cell in other BSC. For the originating cell, the directed retry procedure is an outgoing cell handover procedure with the cause value "Directed retry", whereas, for the target cell, it is an incoming cell handover procedure with the cause value "Directed retry".

Measurement point: "TCH-ATT-C13" in Figure 3-48 indicates the measurement point of this item in the calling procedure. After the above-mentioned conditions are satisfied, the originating cell initiates directed retry, by sending a HANDOVER REQUIRED message to MSC or sending a Intercell Handover Request message to another cell in the current BSC, this item is measured.

Formula: none.

XI. TCH queue requests

Description: BSC performs message content check and status check after it receives an ASSIGNMENT REQUEST message from MSC. If it finds no available channel for allocation, and either of the following two conditions is satisfied, BSC can automatically initiate the queue procedure.1) If BSC and the priority IE contained in the ASSIGNMENT REQUEST

message both support preemption, BSC shall implement preemption. If preemption is successfully implemented, and queue is supported by BSC

160



and the queue IE in the ASSIGNMENT REQUEST message, BSC shall initiate the queue procedure.

2) Even if priority IE in ASSIGNMENT REQUEST or BSS does not support preemption, BSC can also initiate the queue procedure, so long as queue IE in ASSIGNMENT REQUEST and BSS support queue.

In assignment procedure, after the queue conditions are satisfied, BSC returns a QUEUEING INDICATION message to MSC and starts timer T11. Before expiry of timer T11, if there are released channels in BSS and the queuing calls successfully seize the idle channels; the assignment procedure shall go on.

Likewise, for incoming BSC handover, if there is no channel available in BSC and queue is supported, the system can also perform queue for TCH seizures. This procedure is similar to the assignment procedure. The only difference is that the timer started in the incoming BSC handover procedure is timer Tqho. Preemption and queue are not supported in the immediate assignment and intra-BSC handover procedures.

Measurement point: "TCH-ATT-C14" in Figure 3-48 indicates the measurement point of this item in the calling procedure. In the assignment or incoming BSC handover procedure, when BSC initiates the queue procedure by returning a QUEUEING INDICATION message to MSC, this item is measured.

Formula: none.

XII. TCH preemption requests

Description: In the assignment or incoming BSC handover procedure, BSC performs message content check and status check after it receives an ASSIGNMENT REQUEST or HANDOVER REQUEST message from MSC. If it finds no available channel for allocation, and it supports preemption, which is also supported by ASSIGNMENT REQUEST or HANDOVER REQUEST, BSC shall implement preemption. If preemption is successfully implemented, and queue is supported by the system, BSC shall initiate the queue procedure.

Measurement point: "TCH-ATT-C16" in Figure 3-48 indicates the measurement point of this item in the calling procedure. In the assignment or incoming BSC handover procedure, preemption shall be implemented when there is no available channel in BSC and the system supports resource preemption. At the same time, this item shall be measured.

Formula: none.

161



XIII. Attempted TCH seizures for intracell handover

Description: This item measures the number of times the serving cell receives Intracell Handover Request messages in the intra-cell handover (handover between different channels in the serving cell) procedure.

Note:

BSC performs handover decision according to the MR reported by MS; the target cell can be either

other cell or the serving cell itself. Handover between different channels in the same cell is called

intra-cell handover.

Measurement point: "TCH-ATT-C17" in Figure 3-49 indicates the measurement point of this item in the calling procedure. This item is measured when the serving cell receives an Intercell Handover Request message from itself.

Formula: none.

XIV. Successful TCH seizures for intracell handover

Description: In the intra-cell handover procedure, upon reception of a HANDOVER COMMAND message from the serving cell, MS accesses the new channel, and sends a HANDOVER ACCESS on this channel

Measurement point: "TCH-SUCC-C17" in Figure 3-49 indicates the measurement point of this item in the calling procedure. In the intra-cell handover procedure, MS reports a HANDOVER ACCESS message on the new channel after it accesses a new channel in the serving cell. BTS sends HANDOVER DETECTION message to BSC. This item is measured in the serving cell when BSC receives the HANDOVER DETECTION message.

Formula: none.

XV. Successful TCH seizures for very early assignment

Description: In the very early assignment procedure, after a TCH is allocated, BSC activates the TCH. BTS shall return a CHANNEL ACTIVATION ACKNOWLEDGE message to BSC if it considers that the channel is successfully activated. Then BSC sends IMMEDIATE ASSIGNMENT COMMAND to MS, upon reception of this message, MS sends a SABM frame to BTS to establish the radio interface connection, BTS sends ESTABLISH INDICATION to BSC and response a UA frame to MS to acknowledge the connection. Whether Abis interface adopts a terrestrial link or satellite for transmission, the measurement point is the same (If satellite transmission is

162



adopted, the CHANNEL ACTIVATION and IMMEDIATE ASSIGNMENT COMMAND messages are delivered together to MS).

Measurement point: "TCH-SUCC-C6" in Figure 3-47 indicates the measurement point of this item in the calling procedure. In the very early assignment procedure, this item is measured when BSC receives an CHANNEL ACTIVATION ACKNOWLEDGE message from BTS.

Formula: none.

XVI. Successful TCH seizures (all)

Description: In the very early assignment procedure, assignment procedure and handover procedure, BSC measures this item when MS successfully seizes the TCH allocated by the network.

163



Note:

In the assignment procedure, successful directed retry is regarded as successful TCH seizure. More

specifically, after the ASSIGNMENT REQUEST message from MSC is delivered to a cell in BSC, if

there is no available channel in that cell and the system supports directed retry, BSC shall initiate

outgoing cell handover according to the adjacent cell information in the MR (Measurement Report) of

MS. If directed retry is performed in BSC, the target cell shall send an ASSIGNMENT CONFIRMED

message to MSC after it has successfully implemented directed retry. In the meantime, this item shall

be measured in the originating cell. Directed retry only takes place in the TCH assignment procedure.

Measurement point: "TCH-SUCC-C1" in Figure 3-47 , "TCH-SUCC-C21~23" in Figure 3-48 , "TCH-SUCC-C3" in Figure 3-49 and "TCH-SUCC-C4" in Figure 3-50 indicate the measurement points of this statistic item in the calling procedure.1) In the very early assignment procedure for TCH, this item is measured

when BSC receives an CHANNEL ACTIVATION ACKNOWLEDGE message from BTS.

2) In the assignment procedure, if directed retry is successfully implemented and the target cell for direct retry belongs to other BSC, MSC shall send a CLEAR COMMAND to the originating cell to clear the previous connections. This item shall be measured when the originating cell receives the CLEAR COMMAND message.

3) In the assignment procedure, if directed retry is successfully implemented and the target cell for direct retry belongs to the current BSC, the target cell shall send an Inter Clear Request message to the originating cell, notifying it to clear resources and connections. This item shall be measured when the originating cell receives the Inter Clear Request message.

4) This item is measured when the assignment procedure is successfully completed, and BSC sends an ASSIGNMENT COMPLETE message to MSC. The case that the target cell of directed retry sends ASSIGNMENT COMPLETE message to MSC after successfully completes directed retry is excluded.

5) In the incoming BSC handover procedure, this item is measured in the target BSC when the target BSC receives a HANDOVER DETECTIONmessage from BTS.

6) In the intra-BSC incoming cell handover procedure and intracell handover procedure, this item measured when BSC receives HANDOVER DETECTIONfrom BTS.

Formula: none.

164



XVII. Successful TCH seizures for call

Description: In the assignment procedure, upon reception of an ASSIGNMENT REQUEST message from MSC, BSC allocates TCH (for voice data transmission) to MS. After channel allocation is successfully completed, BSC requests BTS to activate this channel. BTS shall return a CHANNEL ACTIVATION ACKNOWLEDGE message to BSC if it allows channel activation operations. Upon reception of the CHANNEL ACTIVATION ACKNOWLEDGE message, BSC sends ASSIGNMENT COMMAND to MS, which sends ASSIGNMENT COMPLETE to BSC after it successfully accesses the new channel.

Measurement point: "TCH-SUCC-C51~53" in Figure 3-48 indicates the measurement point of this item in the calling procedure.1) In the assignment procedure, this item is measured when BSC sends an

ASSIGNMENT COMPLETE message to MSC. The case that the target cell of directed retry sends ASSIGNMENT COMPLETE message to MSC after successfully completes directed retry is excluded.

2) In the assignment procedure, if directed retry is successfully implemented and the target cell for direct retry belongs to other BSC, MSC shall send a CLEAR COMMAND to the originating cell to clear the previous connections. This item is measured when the originating cell receives the CLEAR COMMAND message.

3) In the assignment procedure, if directed retry is successfully implemented and the target cell for direct retry belongs to the current BSC, the target cell shall send an Inter Clear Request message to the originating cell, notifying it to clear resources and connections. This item is measured when the originating cell receives the Inter Clear Request message.

Formula: none.

XVIII. Successful TCH allocation for very early assignment

Description: In the very early assignment procedure, whether TCH is allocated in the first allocation or second allocation procedure, so long as BSC has successfully allocated TCH, this item shall be measured. For second allocation strategies, please refer to Attempted SDCCH seizures (all) .

Measurement point: "TCH-SUCC-C61" in Figure 3-47 indicates the measurement point of this item in the calling procedure. In the very early assignment procedure, this item is measured when BSC successfully allocates TCH for calls.

Formula: none.

165



XIX. Successful TCH allocation for SDCCH overflow

Description: In the very early assignment procedure, if BSC successfully allocates TCH in the second channel allocation procedure (For the requested SDCCH, because there is no SDCCH available, BSC allocates TCH in the second allocation procedure), this item shall be measured. For second allocation strategies, please refer to Attempted SDCCH seizures (all) .

Measurement point: "TCH-SUCC-C62" in Figure 3-47 indicates the measurement point of this item in the calling procedure. In the very early assignment procedure, this item is measured when BSC successfully allocates TCH in the channel second allocation procedure.

Formula: none.

XX. Successful TCH seizures for MOC

Description: This item is related to Successful TCH seizures for call . It measures the number of times BSC successfully allocates TCH for MOC. For the directed retry in assignment procedure, please refer to Attempted TCHseizures for directed retry .

Measurement point: "TCH-SUCC-C81~C83" in Figure 3-48 indicates the measurement point of this item in the calling procedure.1) In the assignment procedure, this item is measured when BSC sends an




Formula: none.

XXI. Successful TCH seizures for MTC

Description: This item is related to Successful TCH seizures for call . It measures the number of times BSC successfully allocates TCH for MTC. For the directed retry in assignment procedure, please refer to Attempted TCHseizures for directed retry .

166







Formula: none.

XXII. Successful TCH seizures for call re-establish

Description: This item is related to Successful TCH seizures for call . It measures the number of times BSC successfully allocates TCH for call re-establishment. For the directed retry in assignment procedure, please refer to Attempted TCH seizures for directed retry .





Formula: none.

167



XXIII. Successful TCH seizures for intraBSC incoming cell handover

Description: In the intra-BSC incoming cell handover procedure, BTS shall report a HANDOVER DETECTION message to the target cell after it accesses the TCH of the target cell. This item measures the number of times the target cell receives the HANDOVER DETECTION messages.

Measurement point: "TCH-SUCC-C11" in Figure 3-49 indicates the measurement point of this item in the calling procedure. In the intra-BSC incoming cell handover procedure, this item is measured when the target cell receives a HANDOVER DETECTION message. This item is not measured on intra-cell handover occasions. For the statistic item related to intra-cell handover, please refer to Successful TCH seizures for intracell handover .

Formula: none.

XXIV. Successful TCH seizures for interBSC incoming cell handover

Description: In the inter-BSC incoming cell handover procedure, BTS reports a HANDOVER DETECTION message to the target cell in Huawei BSC after MS seizes the TCH of the cell. This item measures the number of times the target cell receives the HANDOVER DETECTION messages.

Measurement point: "TCH-SUCC-C12" in Figure 3-50 indicates the measurement point of this item in the calling procedure. This item is measured when BSC receives a HANDOVER DETECTION message from MS which came from other BSC and the handover takes place on TCH.

Formula: none.

XXV. Successful TCH seizures for directed retry

Description: In the directed retry procedure, when directed retry is successfully implemented, i.e. MS successfully accesses the target cell in the current BSC or other BSC, this item shall be measured in the originating cell. For description of the directed retry procedure; please refer to Attempted TCHseizures for directed retry . 1) If the target cell for directed retry is another cell in the current BSC, from

the angle of the target cell, the directed retry procedure is an incoming cell handover procedure, whereas, from the angle of originating cell, the directed retry procedure is outgoing cell handover in assignment procedure. Therefore, for the originating cell, successful inter-cell directed retry in BSC means successful outgoing cell handover.

2) If the target cell for directed retry belongs to other BSC, from the angle of the target cell, the directed retry procedure is an incoming BSC handover procedure, whereas, from the angle of originating cell, the directed retry procedure is outgoing BSC handover procedure.

168



Therefore, for the originating cell, successful inter-BSC directed retry means successful outgoing BSC handover.

Measurement point: "TCH-SUCC-C13" in Figure 3-48 indicates the measurement point of this item in the calling procedure. When there is no available channel, BSC initiates directed retry. Directed retry shall be implemented in the target cell of the current BSC or other BSC.1) If the target cell belongs to the current BSC, the target cell shall send an

Inter Clear Request message (internal message in Huawei BSC) with the cause value "Handover Success" to the originating cell after it successfully implements incoming cell handover. This item is measured when the originating cell receives the Inter Clear Request message.

3) If the target cell belongs to other BSC, the target cell shall send a HANDOVER COMPLETE message to MSC after it successfully implements incoming BSC handover. Upon reception of the message, MSC sends a CLEAR COMMAND message to the originating cell. This item is measured when the originating cell receives the CLEAR COMMAND message.

Formula: none.

XXVI. Successful TCH queue operation

Description: For description of queue in the assignment and incoming BSC handover procedures, please refer to TCH queue requests . In the queue of assignment procedure, BSC returns a QUEUEING INDICATION message to MSC and starts timer T11. Before expiry of timer T11, if there are released TCHs in BSS and the queuing calls successfully seize the idle channels, the assignment procedure shall go on, and this item shall be measured once. Likewise, for incoming BSC handover, if there is no available TCH in BSC and queue is supported, the system can perform queue for TCH seizures. This procedure is similar to the assignment procedure. The only difference is that the timer started in the incoming BSC handover procedure is timer Tqho.

Measurement point: In the assignment procedure or in the incoming BSC handover procedure, BSC returns a QUEUEING INDICATION message to MSC. Before expiry of specified timer, if the system has successfully allocated TCH to a queuing call, this item shall be measured.

Formula: none.

XXVII. Successful TCH preemption

Description: For description of the TCH seizure preemption in the assignment and incoming BSC handover procedures, please refer to TCH preemptionrequests . Based on the priorities of the channel type requested in the ASSIGNMENT REQUEST messages from MSC, BSC preempts a channel

169



which is seized by a lower-priority call. This item is measured when the channel is successfully preempted.

Measurement point: In the assignment or in incoming BSC handover procedure, if the current call successfully preempts the channel seized by a lower-prior call, this item shall be measured in the cell where the assignment or handover takes place.

Formula: none.

XXVIII. Successful assignments of speech version 1 TCH (excluding directed retry)

Description: The measurement point of this item is similar to that of Successful TCHseizures for call. This item is specially used to measure the number of times the speech version indicated in ASSIGNMENT COMPLETE is "GSM speech algorithm version 1".

Measurement point: "TCH-SUCC-C54" in Figure 3-48 indicates the measurement point of this item in the calling procedure.

When assignment is successfully implemented, BSC sends an ASSIGNMENT COMPLETE message to MSC, in which, the indicated speech version is "GSM speech algorithm version 1".

Formula: none.

XXIX. Successful assignments of speech version 2 TCH (excluding directed retry)

Description: The measurement point of this item is similar to that of SuccessfulTCH seizures for call . This item is specially used to measure the number of times the speech version indicated in ASSIGNMENT COMPLETE is "GSM speech algorithm version 2".

Measurement point: "TCH-SUCC-C55" in Figure 3-48 indicates the measurement point of this item in the calling procedure. When assignment is successfully implemented, BSC sends an ASSIGNMENT COMPLETE message to MSC, in which, the indicated speech version is "GSM speech algorithm version 2".

Formula: none.

XXX. Successful assignments of speech version 3 TCH (excluding directed retry)

Description: The measurement point of this item is similar to that of "Successful TCH seizures for call ". This item is specially used to measure the number of times the speech version indicated in ASSIGNMENT COMPLETE is "GSM speech algorithm version 3".

170



Measurement point: "TCH-SUCC-C56" in Figure 3-48 indicates the measurement point of this item in the calling procedure. When the assignment is successfully implemented, BSC sends an ASSIGNMENT COMPLETE message to MSC, in which, the indicated speech version is "GSM speech algorithm version 3".

Formula: none.

XXXI. TCH seizure failures for call(no radio resource)

Description: See Unsuccessful assignments of BSC Measurement Function. This item is used to measure the unsuccessful assignments due to no available TCH in assignment procedure.

Measurement point: See Unsuccessful assignments (no radio resourceavailable) of BSC Measurement Function. the measurement object of this item is the cell.

Formula: none

XXXII. TCH seizure failures for interBSC incoming cell handover

Description: in the case inter BSC handover occurs when the MS is seizing TCH, this item is measured if the target BSC receives the CLEAR COMMAND message from MSC or receives the clear message of RR-AIR inside the BSC. In this case the HANDOVER FAILURE message is not sent. Otherwise, If the incoming BSC handover fails due to some other reason, the target BSC should send a HANDOVER FAILURE message to MSC and it measures this item at the same time.

Measurement point: 1) In the case inter BSC handover occurs when MS is seizing TCH. This

item is measured if the target BSC meets A interface connection failure in the target BSC. In this case the target will not send HANDOVER FAILURE to MSC

2) The target BSC under the following states receives the CLEAR COMMAND message from MSC. The target BSC has no available channel and is queuing for the channel. Or the target BSC is waiting for the HANDOVER DETECTION or HANDOVER COMPLETE message from the MS. In this case this item is measured and the target BSC does not send the HANDOVER FAILURE message to MSC.

3) In the case inter BSC handover occurs when MS is seizing TCH. This item is measured when the target BSC sends the HANDOVER FAILURE message to MSC because the BSC fails to implement the handover procedure due to some reason (excluding the above mentioned causes).

Formula: none

171



XXXIII. TCH seizure failures for intraBSC incoming cell handover

Description: in the case intra BSC incoming cell handover occurs when MS is seizing TCH; the handover implementation fails due to some reason during the period after the target cell receives the Intercell Handover Request message from the source cell and before the target cell sends the Intercell Handover Response message to the source cell, then the target cell sends the Intercell Handover Failure message to the source cell. This item is not used to measure the intra cell handover.

Measurement point: if intra BSC incoming cell handover occurs when the MS is seizing TCH, this item is measured when the following occasions occur.1) The target cell receives the CHANNEL ACTICATION NEGATIVE

ACKNOWLEDGE message from the BTS when activating the newly allocated TCH.

2) The implementation of the incoming cell handover procedure fails because the target cell does not support the encryption algorithm in the Intercell Handover Request message.

3) No response after the timer (internal timer, 5 seconds) expires when the target cell activates the newly allocated TCH.

4) The target cell has no available TCH. Formula: none

XXXIV. TCH Seizure failures (all)

Description: TCH seizure failures that occur in all calling procedure due to all reasons. The measurement point includes the measurement of the following statistic items: TCH seizure failures for call , TCH seizure failures for interBSCincoming cell handover , TCH seizure failures for very early assignment , TCH seizure failures for intraBSC incoming cell handover , and TCH seizurefailures for intracell handover . However, this item is an initial statistic item.

Formula: See the TCH seizure failures in various occasions mentioned in the above description.

XXXV. Attempted TCH seizures meeting TCH overflow

Description: this item is measured if there is no available TCH in immediate TCH assignment, TCH assignment, incoming BSC handover on TCH, or intra BSC incoming cell handover procedure. Though no TCH available, the call might initiate forced seizure, queue, and directed retry procedure etc., according to the actual situation. So this item does not means that the implementation of calling procedure fails.

Measurement point: this item is measured if there is no available TCH when requesting TCH in the calling procedure.

Formula: none

172



XXXVI. TCH seizure failures for call

Description: SeeUnsuccessful assignments of "BSC Measurement Function". In Huawei BSC traffic statistic system, unsuccessful assignments occur in the cell are measured as TCH seizure failures.

Measurement point: the same as that of Unsuccessful assignments of "BSC Measurement Function". But the statistic object of this item is cell.

Formula: none

XXXVII. TCH seizure failures for very early assignment

Description: this item is measured when TCH allocation failure, TCH activation failure, or TCH activation NACK occurs in BSC in very early TCH assignment procedure.

Measurement point: 1) This item is measured if there is no available TCH when the MS requests

channel from BSC in very early TCH assignment procedure.2) In very early TCH assignment procedure, after BSC allocates a TCH, it

sends a CHANNEL ACTIVATION message to the BTS to activate this channel. If BTS returns the CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE message. Then this item is measured when BSC receives this message.

3) In very early TCH assignment procedure, after BSC allocates a TCH, sends a CHANNEL ACTIVATION message to the BTS to activate this channel. At the same time, BSC starts the timer. Then this item is measured if the response from the BTS has not been received when the timer expires.

Formula: none

XXXVIII. TCH seizure failures for MOC

Description: the same as that of TCH seizure failures for call except this item is used to measure only the occasion that the MS serves as MOC.

Measurement point: this item is measured when assignment procedure in which the MS serves as MOC fails due to some reason. The measurement point is similar to that of TCH seizure failures for call .

Formula: none

XXXIX. TCH seizure failures for MTC

Description: the same as that of TCH seizure failures for call except this item is used to measure only the occasion that the MS serves as MTC.

Measurement point: this item is measured when assignment procedure in which the MS serves as MTC fails due to some reason. The measurement point is similar to that of TCH seizure failures for call .

173



Formula: none

XL. TCH seizure failures for call re-establishment

Description: the same as that of TCH seizure failures for call except this item is used to measure only the occasion of call re-establishment.

Measurement point: this item is measured when the implementation of the call re-establishment procedure fails due to some reason. The measurement point is similar to that of TCH seizure failures for call .

Formula: none

XLI. TCH seizure failures for intraBSC incoming cell handover(no radio resource)

Description: in intra BSC incoming cell handover procedure, this item is measured if the target cell has no available TCH when allocating TCH upon reception of the Intercell Handover Request message requesting TCH from other cell in the same BSC.

Measurement point: in intra BSC incoming cell handover, this item is measured if it is TCH that is requested and the handover fails due to no available TCH.

Formula: none

XLII. TCH seizure failures for interBSC incoming cell handover(no radio resource)

Description: this item measures the handover failure in inter-BSC handover due to no available radio channel or timer for queue expires in target cell in the target BSC.

Measurement point: In incoming BSC handover procedure occurs when the MS is seizing TCH, if there is no available TCH after the target cell receives the HANDOVER REQUEST message and queue isn’t supported, this item is measured. If there is no available TCH but both BSC and this handover support the queue, then the system starts the timer to wait for TCH release. This item is measured if there is still no TCH available when the timer expires.

Formula: none

XLIII. TCH seizure failures for directed retry

Description: in assignment procedure, if it is TCH that MSC requests for and the cell supports directed retry, then BSC judges to select an adjacent cell for outgoing cell handover according to the MR from the MS. As this handover is caused by directed retry, this procedure is called directed retry. This item is used to measure the TCH seizure failures for directed retry if the source cell implements the directed retry.

Measurement point:

174



1) In the case directed retry occurs in TCH assignment procedure, this item is measured in the source cell in the following case: if the target cell is in the same BSC and the source cell receives the Inter Clear Request message from the target cell in the directed retry procedure; however this message is not the one to inform the handover completion but to inform the source cell of the directed retry failure and to request to clear the connection.

2) In the case directed retry occurs in TCH assignment procedure, this item is measured if the target cell is in the same BSC and the source cell receives the Intercell Handover Reject message from the target cell in the directed retry procedure.

3) In the case directed retry occurs in TCH assignment procedure and the target cell is in the same BSC, this item is measured in the source cell if the timer for the source cell to wait for Inter Clear Request message upon the completion of the handover from the target cell expires after the source cell sends the MS the HANDOVER COMMAND message to request the MS to access the new channel.

4) In the case directed retry occurs in TCH assignment procedure, this item is measured if the target cell is in the same BSC and the target cell fails to respond to the Intercell Handover Request message sent by the source cell after the timer expires.

Formula: none

XLIV. TCH Queue failures for queue full

Description: in assignment procedure and incoming BSC handover procedure, if it is TCH that MSC requests for, there is no available TCH in the cell when BSC allocates the channel, and the system supports queue, then the call queue is initiated. Each Huawei BSC BM supports only 100 queuing calls. This item is measured if the call queue fails because the queue is full.

Measurement point: in assignment procedure and incoming BSC handover procedure, this item is measured if the call queue fails because the queue is full.

Formula: none

XLV. TCH queue failures for timeout

Description: in assignment procedure and incoming BSC handover procedure, if it is TCH that MSC requests for, there is no available TCH in the cell when BSC allocates the channel, and the system supports queue, then the call queue is initiated and the related timer is started to wait for the resource release.

175



Measurement point: in assignment procedure and incoming BSC handover procedure, if BSC starts the queue timer due to no available TCH, then this item is measured if there is no TCH released when the timer expires and the system doesn't support the queue in assignment procedure.

Formula: none

XLVI. Directed retry after queue failure

Description: in assignment procedure, if it is TCH that MSC requests for, there is no available TCH in the cell when BSC allocates the channel, and if the system supports queue, then the call queue is initiated and the related timer (T11) is started. If the system supports the directed retry, the directed retry is initiated and this item is measured in the case there is still no TCH available when the timer (T11) expires.

Measurement point: If the queue is initiated in TCH assignment procedure and there is still no TCH available after the queue timer expires, the system initiates the directed retry if possible and this item is measured at the same time.

Formula: none

XLVII. TCH seizure failures (equipment failure)

Description: in assignment procedure, if it is TCH that MSC requests for, this item is measured when the implementation of the assignment procedure fails due to equipment failure. See the following measurement points for the definition of equipment failure.

Measurement point: 1) In channel assignment procedure, BSC allocates the terrestrial circuit

according to the CIC specified by MSC but the allocation fails. Then this item is measured and BSC requests MSC to clear the connection simultaneously.

2) If mode modify is initiated in assignment procedure, after the radio channel is successfully modified according to the CHANNEL TYPE requested by MSC, this item is measured if the AM/CM net-drive of BSC fails. (AM/CM returns net-drive rejection or response timeout).

3) If mode modify is initiated in assignment procedure, this item is measured when BSC receives the MODE MODIFY NEGATIVE ACKNOWLEDGE message from BTS indicating the failure of mode modify after the MODE MODIFY message is sent to BTS.

4) If mode modify is initiated in assignment procedure, this item is measured when the timer for BSC to wait for the response expires after the MODE MODIFY message has been sent to the BTS.

176



5) In assignment procedure, this item is measured when BSC receives Channel Activation NACK or the timer for BSC to wait for Channel Activation ACK expires.

Formula: none

XLVIII. TCH seizure failures (requested terrestrial resource unavailable)

Description: in assignment procedure, if it is TCH that MSC requests for, this item is measured if the implementation of assignment procedure fails because the requested terrestrial resource on BSS side is unavailable. See the following measurement points for the definition of "requested terrestrial resource unavailable".

Measurement point: 1) This item is measured when BSC detects the state of CIC requested in

ASSIGNMENT REQUEST message received from MSC is unavailable.2) In assignment procedure, this item is measured when AM/CM net-drive

fails (AM/CM returns net-drive rejection or AM/CM response timeout). Formula: none

XLIX. TCH seizure failures (terrestrial circuit already allocated)

Description: in assignment procedure, if it is TCH that MSC requests for, this item is measured if the BSC detects the requested CIC has already been seized. At the same time BSC informs MSC of the assignment failure.

Measurement point: in assignment procedure, this item is measured when BSC detects the CIC requested in ASSIGNMENT REQUEST message received from MSC has already been seized.

Formula: none

L. TCH seizure failures (invalid message contents)

Description: in assignment procedure, if it is TCH that MSC requests for, this item is measured when BSC detects the ASSIGNMENT REQUEST message contains invalid contents during the message decoding. At the same time BSC informs MSC of the assignment failure.

Measurement point: this item is measured when BSC detects the ASSIGNMENT REQUEST message contains invalid contents during the message decoding, Which includes CHANNEL TYPE, CIC, Layer 3 header information.

Formula: none

LI. TCH call drop

Description: the same as that of TCH call drop of "BSC Measurement Function". But the statistic object of this item is cell.

177



Description: the same as that of TCH call drop of "BSC Measurement Function". But the statistic object of this item is cell.

Formula: none

LII. TCH drop for very early assignment

Description: the same as that of TCH drop for very early assignment of "BSC Measurement Function". But the statistic object of this item is cell.

Measurement point: the same as that of TCH drop for very early assignment of "BSC Measurement Function". But the statistic object of this item is cell.

Formula: none

LIII. TCH lost radio connections (connection failure)

Description: in the case that the TCH is seized as the traffic channel, if BTS detects that an active connection has been broken for some reason, it sends CONNECTION FAILURE INDICATION message to BSC informing the BSC that the call drop occurs at Um interface due to radio link connection failure.

Measurement point: BSC measures this item upon reception of CONNECTION FAILURE INDICATION message (cause: any cause except 0X20-equipment failure and 0X22-terrestrial channel failure) from the BTS and if the failure occurs on TCH.

Formula: none

LIV. TCH lost radio connections (error indication)

Description: in the case that the TCH is seized as the traffic channel, if BTS detects an abnormal case for a radio link layer connection, it sends ERROR INDICATION message to BSC informing the BSC that the call drop occurs at Um interface due to radio link error. See GSM 0858 protocol

Measurement point: BSC measures this item upon reception of ERROR INDICATION message from the BTS and if the failure occurs on TCH.

Formula: none

LV. TCH channel activation NACKs (call)

Description: after receiving ASSIGNMENT REQUEST message from MSC, BSC initiates assignment procedure, then allocates channel. After the successful channel allocation, BSC sends CHANNEL ACTIVATION message to the BTS to activate the allocated channel. BTS checks the state of this channel and responses to the BSC.

Measurement point: in assignment procedure, BSC measures this item upon reception of CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE message from the BTS after having sent CHANNEL ACTIVATION message to the BTS.

Formula: none

178



LVI. TCH channel activation timeout (call)

Description: after receiving ASSIGNMENT REQUEST message from MSC, BSC initiates assignment procedure, then allocates channel. After the successful channel allocation, BSC sends the CHANNEL ACTIVATION message to the BTS to activate the allocated channel. BTS checks the state of this channel and responses to the BSC.

Measurement point: in assignment procedure, BSC sends the CHANNEL ACTIVATION message to the BTS and the timer is started to wait for the response. This item is measured if no response is received when the timer expires.

Formula: none

LVII. TCH channel activation NACKs (handover)

Description: the measurement result of this item includes intra BSC handover (including intra cell handover and inter cell handover) and inter BSC handover. After the BSC receives the HANDOVER REQUEST message from MSC, the incoming BSC handover procedure is initiated. The cell of the BSC (target cell) receives the Intercell Handover Request message from the other channel of this cell or from the other cell in this BSC (source cell), the intra BSC handover procedure is initiated. In these two procedures BSC first allocates channel for the request. After the successful allocation, BSC sends a CHANNEL ACTIVATION message to the BTS to activate the allocated channel. BTS checks the state of this channel and responses to the BSC.

Measurement point: in intra BSC handover or inter BSC handover procedure, BSC measures this item upon reception of the CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE message from the BTS where the target cell is located after having sent the CHANNEL ACTIVATION message to this BTS.

Formula: none

LVIII. TCH channel activation timeout (handover)

Description: the measurement result of this item includes intra BSC handover (including intra cell handover and inter cell handover) and inter BSC handover. After the BSC receives the HANDOVER REQUEST message from MSC, the incoming BSC handover procedure is initiated. The cell of the BSC (target cell) receives the HANDOVER REQUEST message from the other channel of this cell or from the other cell in this BSC (source cell), the intra BSC handover procedure is initiated. In these two procedures BSC first allocates channel for the request. After the successful allocation, BSC sends a CHANNEL ACTIVATION message to the BTS to activate the allocated channel. BTS checks the state of this channel and responses to the BSC.

179



Measurement point: in intra BSC handover or inter BSC handover procedure, BSC sends a CHANNEL ACTIVATION message to the TCH of the BTS where the target cell is located and the timer is started to wait for the response. This item is measured if there is no response from the BTS when the timer expires.

Formula: none

LIX. TCH mode modification (NACK)

Description: after receiving the ASSIGNMENT REQUEST message from MSC, BSC judges the CHANNEL TYPE contained in the message. The mode modify procedure is initiated if BSC finds that the relation between the requested TCH and the radio channel allocated in the immediate assignment phase is as follows: "channel rate and type" are consistent, "speech encoding algorithm/transparency indicator" are not consistent or speech encoding algorithm/transparency indicator are not consistent.

Measurement point: in the case mode modify procedure is initiated in TCH assignment procedure, after the MODE MODIFY message is sent to the BTS, BSC measures this item upon reception of the MODE MODIFY NEGATIVE ACKNOWLEDGE message responded from the BTS indicating the implementation of mode modify procedure fails.

Formula: none

LX. TCH mode modification timeout

Description: after receiving the ASSIGNMENT REQUEST message from MSC, BSC judges the CHANNEL TYPE contained in the message. The mode modify procedure is initiated if BSC finds that the relation between the requested TCH and the radio channel allocated in the immediate assignment phase is as follows: "channel rate and type" consistent, and "speech encoding algorithm/transparency indicator" are not consistent or speech encoding algorithm/transparency indicator are not consistent.

Measurement point:1) In TCH assignment procedure, if the mode modify procedure is initiated,

after the MODE MODFIY message has been sent to the BTS, a timer is started. This item is measured if there is no response when the timer expires, indicating the implementation of the mode modify procedure fails.

2) In the assignment procedure, if the mode modify procedure is initiated, after the CHANNEL MODE MODFIY message has been sent to the MS, a timer is started. This item is measured if there is no response from MS when the timer expires, indicating the implementation of the mode modify procedure fails.

Formula: none

180



LXI. TCH seizure failures due to terrestrial link failures

Description: in the case that the TCH is seized as the traffic channel, if BTS detects that an active connection has been broken for some reason, it sends a CONNECTION FAILURE INDICATION message to BSC informing the BSC that the terrestrial link in ABIS interface fails.

Measurement point: 1) BSC measures this item upon reception of the CONNECTION FAILURE

INDICATION message (cause: 0X20-equipment failure and 0X22-terrestrial channel failure) from the BTS and if the failure occurs on TCH.

2) This item is measured when the RSL link of the TRX that the call is running on disconnect, which will cause call drop.

Formula: none

LXII. TCH seizure failures due to A-interface failures

Description: after the call established on TCH reports the ESTABLISH INDICATION message, the established TCH and the related link will be released if A interface connection failure occurs due to A interface connection failures.

181

Traffic Statistic ManualM900/M1800 Base Station Controller Error: Reference source not found

Measurement point: This item is measured if the duration of A interface trunk circuit failure exceeds 15 seconds, SCCP connection disconnect, BSC receives RESET CIRCUIT message from MSC.

Formula: none

LXIII. Average TCH queue length

Description: indicates the average number of the calls that participate in the queuing in the specified cell.

Measurement point: at the end of a statistic cycle, the average number of the calls that participate in the queuing in this cycle is sent to the BAM.

Formula: none

LXIV. Maximum TCH queue length

Description: indicates the maximum number of the calls that participate in the queuing in the specified cell.

Measurement point: at the end of a statistic cycle, the maximum number of the calls that participate in the queuing in this cycle is sent to the BAM.

Formula: none

LXV. Average TCH queue time

Description: in assignment and incoming BSC handover procedure, BSC implement queue procedure due to no available radio channel and the system support that. This item indicates the average waiting duration of the calls that participate in the queuing in the statistic cycle in the specified cell.

Measurement point: at the end of a statistic cycle, the sum of waiting duration of the calls that participate in the queuing in this cycle is sent to the BAM. Together with TCH queue requests and TCH Queue failures for queue full , the average TCH queue time will be calculated.

Formula: the sum of TCH queue time / (TCH queue requests - TCH Queue failures for queue full )

LXVI. TCH uplink point to point short messages

Description: TCH can be used to send uplink/downlink short message. This item is used to measure the number of the uplink short messages sent on the TCH of the cell.

Measurement point: this item is measured upon BSC’s reception of the uplink short message sent on TCH.

Formula: none

182


LXVII. TCH downlink point to point short messages

Description: TCH can be used to send uplink/downlink short messages. This item is used to measure the number of the downlink short messages sent on the TCH of the cell.

Measurement point: this item is measured upon BSC’s reception of the downlink short message sent on TCH.

Formula: none

LXVIII. TCH seizure failures for intracell handover

Description: In the view of calling procedure, intra cell handover in the BSC is the same as intra BSC handover procedure except the source cell and the serving cell are the same If the source cell and target cell are the same cell, then this cell is called the serving cell. In intra cell handover procedure, before the serving cell sends the Intercell Handover Response message to indicate the new channel is ready, if the new channel preparation fails due to some reason, the serving cell sends a Intercell Handover Failure message internally indicating the intra cell handover failure.

Measurement point: 1) In the new TCH activation procedure, this item is measured when the

serving cell receives the CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE message from the BTS.

2) This item is measured if the implementation of intra cell handover procedure fails because the encryption algorithm in Intercell Handover Request message does not support.

3) No response after the timer (internal timer, 5 seconds) expires when the serving cell activates the new TCH.

4) in intra cell handover procedure, if it is TCH that is requested in the handover but there is no available TCH in the serving cell, and this leads to the handover failure. In this case, this item is measured.

Formula: none

LXIX. TCH seizure failures for intracell handover (no radio resource)

Description: in intra cell handover procedure, the serving cell sends the Intercell Handover Request message internally to request a new TCH. Then this item is measured if the serving cell detects that there is no available TCH during the TCH allocation.

Measurement point: in intra cell handover procedure, if it is TCH that is requested in the handover but there is no available TCH in the serving cell, and this leads to the handover failure. In this case, this item is measured.

Formula: none

183


LXX. Configured TCHs of 1800 cell

Description: This item indicates the number of TCH currently configured for a certain 1800 cell on real-time basis. It excludes the TCH dynamically adjusted to SDCCH, and includes the TCH adjusted from dynamic PDCH. It is an average number of configured TCHs got at all sampling points within the statistic cycle.

Measurement point: System gets the number of configured TCHs every five seconds. The accumulated value of the data got at all sampling points is divided with the times of sampling times to get the average number of configured TCHs of 1800 cell within the statistic cycle.

Formula: none

LXXI. Configured TCHs of 900 cell

Description: This item indicates the number of TCH currently configured for a certain 900 cell on real-time basis. It excludes the TCH dynamically adjusted to SDCCH, and includes the TCH adjusted from dynamic PDCH. It is an average number of configured TCHs got at all sampling points within the statistic cycle.

Measurement point: System gets the number of configured TCHs every five seconds. The accumulated value of the data got at all sampling points is divided with the times of sampling to get the average number of configured TCHs of 900 cell within the statistic cycle.

Formula: none

LXXII. Available TCHs

Description: This item indicates the number of available (idle or busy) TCHs in a certain cell on real-time basis. It excludes the TCH dynamically adjusted to SDCCH, and includes the TCH adjusted from dynamic PDCH. It is an average number of available TCHs got at all sampling points within the statistic cycle.

Measurement point: System gets the number of available TCHs every five seconds. The accumulated value of the data got at all sampling points is divided with the times of sampling to get the average number of available TCHs within a statistic cycle.

Formula: none

LXXIII. Average num. of busy TCHs

Description: This item indicates the average number of the busy TCHs in a cell within the statistic cycle. It is an average number of busy TCHs got at all sampling points within the statistic cycle. In the view of the number of channel seizures, it shows the average level of the MSs of this cell seizing the traffic channel resources.

184


Measurement point: System gets the number of busy TCHs every five seconds. The accumulated value of the data got at all sampling points is divided with the times of sampling to get the average number of busy TCHs within a statistic cycle.

Formula: none

LXXIV. Maximum num. of busy TCHs

Description: This item indicates the maximum number of the busy TCHs in a cell. It is a peak value of busy TCHs got at all sampling points within a statistic cycle. In the view of channel seizures, it shows the maximum traffic channel resource that is seized by the MSs of the cell.

Measurement point: System gets the number of busy TCHs every five seconds. The maximum value can be known by the end of the statistic cycle.

Formula: none

LXXV. All TCH busy time (second)

Description: This item indicates the duration of no TCH can be allocated. It shows the situation that all the traffic channel resources of the cell have been allocated or blocked so that no TCH can be allocated any more.

Measurement point: Total duration that no TCH in a cell can be allocated. Formula: none

LXXVI. Average TCH busy time (second)

Description: This item indicates the average duration that the TCHs in a cell are busy, i.e., the average duration for each TCH being busy. In the view of channel seizure duration, it shows the average level that the MSs of this cell seizes the traffic channel resource. See Configured TCHs of 1800 cell and Configured TCHs of 900 cell .

Measurement point: Total duration of each TCH in a cell being busy. Formula: Sum of the duration of each TCH in a cell being busy / (number of

configured TCHs in 1800 cell + number of configured TCHs in 900 cell)

LXXVII. Average num. of idle TCHs in Interf. band 1

Description: The interference band is the uplink interference level rank of TCH and this level is reported to BSC by BTS at idle TCH via the RF RESOURCE INDICATION message. There are six ranks of interference band. The level range for each band can be set through the data configuration console. Generally they are set as follows:

Interfere band 0 -110~-105dBm



185





The higher the level, the severer the interference. Generally, it is regarded that the interference exists if the idle channel falls into the interference band 4 or interference band 5. This item indicates the average number of idle TCHs in the interference band 1.

Measurement point: System gets the number of idle TCHs in the interference band 1 every five seconds. The accumulated value of the data got at all sampling points is divided with the times of sampling to get the average number of idle TCHs in interference band 1 within the statistic cycle.

Formula: none

LXXVIII. Average num. of idle TCHs in Interf. band 2


Interference band 0 -110~-105dBm








Formula: none

186


LXXIX. Average num. of idle TCHs in Interf. band 3










Formula: none

LXXX. Average num. of idle TCHs in Interf. band 4









187



Formula: none

LXXXI. Average num. of idle TCHs in Interf. band 5










Formula: none

LXXXII. Average num. of blocked TCHs

Description: This item indicates the average number of the TCHs being blocked. It is the average of blocked TCHs got at all sampling points within the statistic cycle. The TCH blocking can be caused by the channel blocking during the O&M or caused by RSL link disconnection. It shows the situation of TCHs in a cell being unavailable within the statistic cycle.

Measurement point: System checks the number of blocked TCHs every five seconds. The accumulated value from the data got at the sampling points is divided with the times of sampling to get the average number of blocked TCHs within the measurement cycle.

Formula: none

188


LXXXIII. Average num. of idle TCHs

Description: This item indicates the average number of the TCHs in a cell being idle. It is the average of idle TCHs got at all sampling points within the statistic cycle. An idle TCH refers to a TCH that is in normal state and has not been seized. It shows the situation of TCH seizure in a cell within the period.

Measurement point: System checks the number of idle TCHs every five seconds. The accumulated value from the data got at the sampling points is divided with the times of sampling to get the average number of idle TCHs within the measurement cycle.

Formula: none

LXXXIV. Average num. of OOS TCHs

Description: This item indicates the average number of the TCHs in a cell being in OOS state. It is the average of OOS TCHs got at all sampling points within the statistic cycle. The status of OOS means the channel is unavailable, including channel blocked due to O&M, site status changed from installed to not installed and BTS or TRX failure. It shows the situation of unavailable TCHs in a cell within the statistic cycle.

Measurement point: System checks the number of OOS TCHs every five seconds. The accumulated value from the data got at the sampling points is divided with the times of sampling to get the average number of OOS TCHs within the measurement cycle.

Formula: none

LXXXV. TCH usability (%)

Description: This item indicates the percentage of available TCHs in totally configured TCHs. See Available TCHs , Configured TCHs of 900 cell and Configured TCHs of 1800 cell .

Measurement point: none Formula: number of available TCHs / (number of configured TCHs in 1800 cell

+ number of configured TCHs in 900 cell)

LXXXVI. Attempted TCH seizures (excluding handover)

Description: This item indicates the attempted TCH seizures, excluding the ones for handover and including the ones for calls and for very early TCH assignment. See Attempted TCH seizures for call and Attempted TCHseizures for very early assignment .

Measurement point: none Formula: Attempted TCH seizures for call + Attempted TCH seizures for very

early assignment

189


LXXXVII. Attempted TCH seizures (including handover)

Description: This item indicates all attempted TCH seizures, excluding the ones for intracell handover. See Attempted TCH seizures for call , AttemptedTCH seizures for very early assignment , Attempted TCH seizures forintraBSC incoming cell handover and Attempted TCH seizures for interBSCincoming cell handover .

Measurement point: none Formula: Attempted TCH seizures for call + Attempted TCH seizures for very

early assignment + Attempted TCH seizures for intraBSC incoming cell handover + Attempted TCH seizures for interBSC incoming cell handover

LXXXVIII. TCH seizure failures (excluding handover)

Description: This item indicates the TCH seizure failures for calls and for very early TCH assignment, excluding the ones for handover. See TCH seizurefailures for call and TCH seizure failures for very early assignment .

Measurement point: none Formula: TCH seizures failures for call + TCH seizures failures for very early

assignment

LXXXIX. TCH seizure failures (including handover)

Description: This item indicates all TCH seizure failures, excluding the ones for intracell handover. See TCH seizure failures for call , TCH seizure failures forvery early assignment , TCH seizure failures for intraBSC incoming cellhandover(no radio resource) and TCH seizure failures for interBSC incomingcell handover(no radio resource) .

Measurement point: none Formula: TCH seizure failures for call + TCH seizure failures for very early

assignment + TCH seizure failures for intra BSC incoming cell handover (no radio resource) + TCH seizure failures for inter BSC incoming cell handover (no radio resource)

XC. TCH congestion rate (excluding handover)(%)

Description: This item indicates the percentage of attempted TCH seizure failures (excluding the ones for handover) in total TCH requests. See TCHseizure failures for call, TCH seizure failures for very early assignment , Attempted TCH seizures for call and Attempted TCH seizures for very earlyassignment .

Measurement point: none Formula: (TCH seizure failures for call + TCH seizure failures for very early

assignment) / (attempted TCH seizures + attempted TCH seizures for very early assignment)

190


XCI. TCH congestion rate (including handover)(%)

Description: This item indicates the percentage of attempted TCH seizure failures (including the ones for handover, excluding the ones for intracell handover) in total TCH requests. See TCH seizure failures for call , TCHseizure failures for very early assignment , TCH seizure failures for intraBSCincoming cell handover(no radio resource) , TCH seizure failures for interBSCincoming cell handover(no radio resource) , Attempted TCH seizures for call , Attempted TCH seizures for very early assignment , Attempted TCH seizuresfor intraBSC incoming cell handover and Attempted TCH seizures for interBSCincoming cell handover .

Measurement point: none Formula: (TCH seizure failures for call + TCH seizure failures for very early

assignment + TCH seizure failures for intra BSC incoming cell handover (no radio resource) + TCH seizure failures for inter BSC incoming cell handover (no radio resource) ) / (attempted TCH seizures (all) + attempted TCH seizures for very early assignment + attempted TCH seizures for intraBSC incoming cell handover + attempted TCH seizures for interBSC incoming cell handover)

XCII. TCH traffic volume (excluding very early assignment) (ERL)

Description: This item indicates the ratio of duration of MS seizing TCH to statistic cycle. The duration of MS seizing TCH is calculated by multiplying the number of MR reported by MS via TCH with the report period (0.48 seconds). See Sum of TCH measurement reports in the cell (excluding very earlyassignment) .

Measurement point: none Formula: Sum of TCH measurement reports in the cell (excluding very early

assignment) 0.48 / statistic cycle (second)

XCIII. Traffic density at average TCH call drop

Description: This item indicates average duration of MS seizing TCH after which a TCH call drop occurs. The duration of MS seizing TCH is calculated by multiplying the number of MR reported by MS via TCH with the report period (0.48 seconds). See Sum of TCH measurement reports in the cell (excludingvery early assignment) and TCH call drop .

Measurement point: none Formula: Total number of TCH measurement reports (excluding very early

assignment) 0.48 / TCH call drops

XCIV. TCH RF lost rate (%)

Description: This item indicates the percentage of call drops due to radio link disconnection when seized by MS caused by air interface causes accounting

191


all successful TCH seizures. See TCH lost radio connections (connectionfailure) , TCH lost radio connections (error indication) and Successful TCHseizures (all) .

Measurement point: none Formula: (times of radio link disconnection when TCH seized (connection

failure) + times of radio link disconnection when TCH seized (error indication)) / successful TCH seizures (all)

XCV. TCH call drop rate (%)

Description: This item indicates the percentage of TCH call drops accounting all successful TCH seizures. See TCH call drop , Successful TCH seizures(all) .

Measurement point: none Formula: TCH call drops / successful TCH seizures (all)

XCVI. TCH traffic volume of 1800 cell (excluding very early assignment) (ERL))

Description: This item indicates the ratio of duration of MS (in 1800 cell) seizing TCH to statistic cycle. The duration of MS seizing TCH is calculated by multiplying the number of MR reported by MS via TCH with the report period (0.48 seconds). See Sum of TCH measurement reports in 1800 cell (excludingvery early assignment) .

Measurement point: none Formula: Total number of TCH measurement reports in 1800 cell (excluding

very early assignment) 0.48 / statistic cycle (second)

XCVII. TCH congestion rate (TCH overflow) (%)

Description: This item indicates the percentage of meeting a TCH blocked state on attempted TCH seizures in attempted TCH seizures (all). See Attempted TCH seizures meeting TCH overflow and Attempted TCHseizures (all) .

Measurement point: none Formula: Attempted TCH seizures meeting a TCH blocked state / Attempted

TCH seizures (all)

3.9.3 Random Access Measurement Function


192


Table 3-2 Random access measurement items

No. Item name

1Packet paging commands to BTS

2Packet paging PCH overloads of ABIS interface

3Circuit paging commands to BTS

4Successful circuit pagings of ABIS interface

5Circuit paging PCH overloads of ABIS interface

6Immediate assignment requests

7Successful immediate assignments

8Successful immediate assignments for location update

9Successful immediate assignments for location update (dual-band MS)

10Successful immediate assignments for MOC

11Successful immediate assignments for MOC (dual-band MS)

12Successful immediate assignments for MTC

13Successful immediate assignments for MTC (dual-band MS)

14Successful immediate assignments for emergency calls

15Successful immediate assignments for call re-establishment

16Successful immediate assignments for other procedures

17Circuit paging RACH overloads of ABIS interface

18Immediate assignment rejections

19Immediate assignment transmissions

20Ratio of paging channel overloads(%)

21Immediate assignment success rate (%)

I. Packet paging commands to BTS

Description: in the case an MS under the BSC is called for packet service, SGSN sends a PAGING REQUEST message to PCU to page this MS. PCU processes this message and then sends the PACKET PAGING message to the BSC. According to the cell identification discriminator carried in the PACKET PAGING message, BSC sends a PACKET PAGING REQUEST message to the corresponding cell. See GSM 0408, 0460, and 0360 protocols.

Measurement point: this item is measured when BSC sends the PACKET PAGING REQUEST message to the corresponding cell.

Formula: none

I. Packet paging PCH overloads of ABIS interface

Description: when detecting the overload of PCH seized by packet service (See GPRS Related Measurement Function for packet logical channel

193


combination relation), BTS reports the Packet CCCH Load Indication message to the BSC. The BSC forwards this message to PCU and PCU initiates packet paging flow control procedure.

Measurement point: BSC measures this item upon reception of the Packet CCCH Load Indication message from BTS.

Formula: none

II. Circuit paging commands to BTS

Description: in the case an MS under the BSC is called for circuit service, the BSC sends the PAGING COMMAND message to the corresponding cell according to the cell identification discriminator after receiving the circuit PAGING message from MSC or PCU. This item is used to measure the paging times at Abis. See GSM 0858 and 0408 protocol.

Measurement point: this item is measured when the BSC sends the PAGING REQUEST message to the corresponding cell.

Formula: none

III. Successful circuit pagings of ABIS interface

Description: after a called MS receives PAGING REQUEST message from network side, the paging response procedure is initiated. This MS reports an ESTABLISH INDICATION (the type of the service request message is PAGING RESPONSE) to MSC if it successfully seizes the signaling channel. See GSM 0408 protocol.

Measurement point: this item is measured when BSC receives the ESTABLISH INDICATION message from MS and the type of the service request message in ESTABLISH INDICATION is "PAGING RESPONSE".

Formula: none

IV. Circuit paging PCH overloads of ABIS interface

Description: BTS reports a CCCH LOAD INDICATION message to the BSC when detecting the overload of CCCH type of PCH, then BSC measures this item and sends a OVERLOAD message to MSC simultaneously. See GSM 0858 protocol.

Measurement point: this item is measured when BSC receives the CCCH LOAD INDICATION message from the BTS with the cause value carried in the message being PCH overload.

Formula: none

V. Immediate assignment requests

Description: When network service is required, MS reports a CHANNEL REQUEST message on RACH, requesting a dedicated control channel. Upon

194


reception of this message, BSC starts channel allocation and measures this item.

Note:

For a channel request, if second allocation takes places, this item shall only be measured once.

Measurement point: "SD-ATT-C1" in Figure 3-47 indicates the measurement point. This item is measured when BSC receives a CHANNEL REQUEST message from MS.

Formula: none.

VI. Successful immediate assignments

Description: In the immediate assignment procedure, after successfully seizing a channel (SDCCH or TCH) allocated by BSC for transferring signaling, MS reports a SABM frame on this channel to BTS, indicating the establishment of a radio link layer connection in the multi-frame mode. BTS returns a UA frame to MS, and sends an ESTABLISH INDICATION message to BSC, notifying it to establish a normal Um interface connection.

Note:

This statistic item is measured on all the occasions allowed in the service request message of

ESTABLISH INDICATION. The following items are measured as per the requested service type in the

service request message. All the measurement points are the same.

Measurement point: "SD-SUCC-C4" in Figure 3-47 indicates the measurement point in the calling procedure. This item is measured when BSC receives an ESTABLISH INDICATION message from BTS in the immediate assignment procedure.

Formula: none.

VII. Successful immediate assignments for location update

Description: This item measures the number of successful immediate assignments for location update.

Measurement point: In the immediate assignment procedure, this item is measured when BSC receives an ESTABLISH INDICATION from MS, in

195


which, the type of the service request message is "LOCATION UPDATE REQUEST".

Formula: none.

VIII. Successful immediate assignments for location update (dual-band MS)

Description: In the immediate assignment procedure, after MS sends a SABM frame, A UA frame is returned, indicating the establishment of a radio link layer connection in the multi-frame mode. If SYSTEM INFORMATION TYPE 3 is set as "ECSC (Early ClassMark Sending Control) allowed", MS (such as dual-band MS and vehicle mounted large power MS) can automatically initiate the classmark change procedure, by sending a CLASSMARK CHANGE message on the dedicated channel. The message contains the new MS classmark 2 information element. It may also contain a classmark 3 information element. In addition, after the MM connection between MS and MSC is established, MSC can also initiate the classmark change procedure, by sending a CLASSMARK CHANGE message to MS. Likewise, MS shall acknowledge the message and implement the class change procedure. For further description, please refer to GSM 0408.

Measurement point: A1 and A2 in Figure 3-51 , indicate the measurement point. This item is measured when BSC receives a CLASSMARK CHANGE message from MS and finds that the initial access cause is "LOCATION UPDATE".

Formula: none.

MS BSS MSC

COMPLETE LAYER 3 INFORMATION

A1

SABM

CLASSMARK CHANGE

SYSTEM INFORMATION TYPE 3ECSC

CLASSMARK REQUESTCLASSMARK ENQUIRY

CLASSMARK CHANGE

CLASSMARK UPDATE

CLASSMARK UPDATEA2

B1C1

B2C2

A1,A2: Successful immediate assignments for location update (dual-band MS)

B1,B2: Successful immediate assignments for MOC (dual-band MS)

C1,C2: Successful immediate assignments for MTC (dual-band MS

196


Figure 3-51 Classmark change procedure

IX. Successful immediate assignments for MOC

Description: This item measures the number of successful immediate assignments for MOC.

Measurement point: In the immediate assignment procedure, this item is measured when BSC receives an ESTABLISH INDICATION from MS, in which, the type of service request message is "CM SERVICE REQUEST" and CM service type is "MOC".

Formula: none.

X. Successful immediate assignments for MOC (dual-band MS)

Description: This item measures the number of successful immediate assignments for MOC (dual-band MS). For description of the classmark change procedure, please refer to Successful immediate assignments for location update (dual-bandMS) ".

Measurement point: B1 and B2 in Figure 3-51 indicate the measurement point. This item is measured when BSC receives a CLASSMARK CHANGE message from MS and finds that the initial access cause is "MOC".

Formula: none.

XI. Successful immediate assignments for MTC

Description: This item measures the number of successful immediate assignments for MTC.

Measurement point: In the immediate assignment procedure, this item is measured when BSC receives an ESTABLISH INDICATION from MS, in which, the type of service request message is "PAGING RESPONSE".

Formula: none.

XII. Successful immediate assignments for MTC (dual-band MS)

Description: For description of the classmark change procedure, please refer to Successful immediate assignments for location update (dual-band MS) ".

Measurement point: A1 and A2 in Figure 3-51 indicate the measurement point. This item is measured when BSC receives a CLASSMARK CHANGE message from MS and finds that the initial access cause is "MTC".

Formula: none.

XIII. Successful immediate assignments for emergency calls

Description: This item measures the number of successful immediate assignments for emergency calls

197


Measurement point: In the immediate assignment procedure, this item is measured when BSC receives an ESTABLISH INDICATION from MS, in which, the type of service request message is "CM SERVICE REQUEST" and CM service type is "Emergency call establishment".

Formula: none.

XIV. Successful immediate assignments for call re-establishment

Description: This item measures successful immediate assignments for call re-establishment.

Measurement point: In the immediate assignment procedure, this item is measured when BTS reports an ESTABLISH INDICATION message to BSC, indicating the establishment of SDCCH connection in the multi-frame mode, and the type of service request message contained in ESTABLISH INDICATION is " CM REESTABLISHMENT REQUEST".

Formula: none.

XV. Successful immediate assignments for other procedures

Description: This item measures the number of successful immediate assignments, and the type of the service request message in ESTABLISH INDICATION is a value other than the above-mentioned values. For related information, please refer to Successful immediate assignments .

Measurement point: In the immediate assignment procedure, this item is measured when BTS reports an ESTABLISH INDICATION message to BSC, which indicates the establishment of SDCCH connection in the multi-frame mode and contains the following information. Type of the service request message is "IMSI DETACH" or "CM SERVICE REQUEST". CM service type is "Packet mode connection establishment", "Short message service", or "Supplementary service activation".

Formula: none.

XVI. Circuit paging RACH overloads of ABIS interface

Description: when detecting CCCH type of RACH overload, BTS reports to BSC, then BSC measures this item and implements the internal flow control if BSC support that.

Measurement point: this item is measured when BSC receives the CCCH LOAD INDICATION message from the BTS with the cause value carried in the message being RACH overload.

Formula: none

198


XVII. Immediate assignment rejections

Description: upon reception of the CHANNEL REQUEST message from the MS, if there is no available channel, the BSC sends the IMMEDIATE ASSIGNMENT REJECT message to the MS indicating the immediate assignment procedure fails.

Measurement point: upon reception of the CHANNEL REQUEST message from the MS, if there is no available channel, the BSC sends the IMMEDIATE ASSIGNMENT REJECT message to the MS. In this case, this item is measured.

Formula: none

XVIII. Immediate assignment transmissions

Description: upon reception of the CHANNEL REPORT message reported from MS, BSC allocates and then activates a signaling channel for the MS. Upon reception of CHANNEL ACTIVATION ACKNOWLEDGE message from BTS indicating that the channel is ready, BSC sends a IMMEDIATE ASSIGN COMMAND to inform the MS to access the dedicated signaling channel, which can be SDCCH or TCH.

Measurement point: this item is measured when the BSC sends the IMMEDIATE ASSIGN COMMAND message.

Formula: none

XIX. Ratio of paging channel overloads(%)

This is an analytic item that describes the relation between PCH overloads and paging at Abis interface. Both circuit service and packet service are included in this item.

Measurement point: Analytic item. See Circuit paging PCH overloads of ABISinterface , Packet paging PCH overloads of ABIS interface , Circuit pagingcommands to BTS , and Packet paging commands to BTS .

Formula: (Circuit paging PCH overloads of ABIS interface + Packet paging PCH overloads of ABIS interface ) / (Circuit paging commands to BTS + Packet paging commands to BTS)

XX. Immediate assignment success rate (%)

Description: This is an analytic item. In immediate assignment procedure, for one request, MS might send several the CHANNEL REQUEST messages but the ESTABLISH INDICATION message can be sent only one time. So this item cannot directly reflect the situation of unsuccessful immediate assignments.

Measurement point: Analytic item. See Successful immediate assignments and Immediate assignment requests

199


Formula: Successful immediate assignments/ Immediate assignment requests

3.9.4 Inter-cell Handover Measurement Function


Table 3-1 Statistic items in Inter-cell Handover Measurement Function

No. Item name

1 Attempted incoming internal inter cell handovers

2Incoming internal inter cell handovers

3Attempted incoming interBSC inter cell handovers

4Attempted incoming internal inter cell handovers (from 900 cell)

5Attempted incoming internal inter cell handovers (from 1800 cell)

6Attempted outgoing internal inter cell handovers

7Outgoing internal inter cell handovers

8Attempted outgoing interBSC inter cell handovers

9Attempted outgoing internal inter cell handovers (to 900 cell)

10Attempted outgoing internal inter cell handovers (to 1800 cell)

11Outgoing interBSC inter cell handovers (to 900 cell)

12Outgoing interBSC inter cell handovers (to 1800 cell)

13Attempted handovers for uplink quality

14Attempted handovers for downlink quality

15Attempted handovers for uplink strength

16Attempted handovers for downlink strength

17Attempted handovers for timing advance

18Attempted handovers for better cell

19Attempted handovers for traffic load

20Attempted handovers for rapid level drop

21Attempted handovers for response to MSC invocation

22Attempted handovers for O&M intervention

23Attempted handovers for directed retry

24Attempted handovers for other causes

25Attempted handovers with uplink receiving level rank 0






31Attempted handovers with uplink receiving quality rank 0


200








39Average uplink receiving level at handover request

40Average uplink receiving quality at handover request

41Successful incoming internal inter cell handovers

42Successful incoming interBSC inter cell handovers

43Successful incoming internal inter cell handovers (from 900 cell)

44Successful incoming internal inter cell handovers (from 1800 cell)

45Successful outgoing internal inter cell handovers

46Successful outgoing interBSC inter cell handovers

47Successful outgoing internal inter cell handovers (to 900 cell)

48Successful outgoing internal inter cell handovers (to 1800 cell)

49Successful outgoing interBSC inter cell handovers (to 900 cell)

50Successful outgoing interBSC inter cell handovers (to 1800 cell)

51Unsuccessful incoming internal inter cell handovers

52Unsuccessful incoming internal inter cell handovers (no radio resource available)

53Unsuccessful incoming internal inter cell handovers (other causes)

54Unsuccessful outgoing internal inter cell handovers

55Unsuccessful incoming interBSC inter cell handovers

56Unsuccessful outgoing interBSC inter cell handovers

57Unsuccessful internal inter cell handovers (channel mode unacceptable)

58Unsuccessful internal inter cell handovers (timing advance out of range)

59Unsuccessful internal inter cell handovers (frequency not implemented)

60Unsuccessful internal inter cell handovers (timer expired)

61Unsuccessful internal inter cell handovers (other causes)

62Unsuccessful internal inter cell handovers with successful reversions

63Unsuccessful internal inter cell handovers with unsuccessful reversions

64Attempted inter cell handovers

65Successful inter cell handovers

66Inter cell handover success rate (%)

67Inter cell radio handover success rate(%)

68Dual-band inter cell handover success rate (%)

201


I. Attempted incoming internal inter cell handovers

Description: During the procedure of internal intercell handover, the source cell sends an Intercell Handover Request message to the target cell after handover algorithm decision. This item measures the times of the current cell, as the target cell of internal intercell handover, receiving the Intercell Handover Request message. It indicates the frequency of the intraBSC handover from other cells to the current cell. Together with Successful incoming internal intercell handovers and Unsuccessful incoming internal inter cell handovers, this item shows the performance of this type of handover. Related items: Attempted incoming interBSC inter cell handovers and Attempted outgoinginternal inter cell handovers .

Measurement point: During the procedure of internal intercell handover, the target cell (current cell) receives an Intercell Handover Request message from the source cell. This item is measured in this case.

Formula: none.

I. Incoming internal inter cell handovers

Description: During the procedure of internal intercell handover, the target cell sends Intercell Handover Response to the source cell after channel activation to indicate that the channel preparation is complete. This message contains the HANDOVER COMMAND message to be sent to MS. This item measures the times of the current cell, as the target cell of internal intercell handover, sending Intercell Handover Response. Together with Attempted incominginternal inter cell handovers , this item shows the situation of handover failure due to abnormality during the procedure of channel preparation in the target cell. Together with Successful incoming internal inter cell handovers , this item shows the situation of handover failure due to radio interface abnormal. Related items: Outgoing internal inter cell handovers and Inter BSC incomingcell handovers .

Measurement point: During the procedure of internal intercell handover, the target cell (current cell) sends Intercell Handover Response to the source cell. This item is measured in this case.

Formula: none.

II. Attempted incoming interBSC inter cell handovers

Description: During the procedure of interBSC handover, on reception of HANDOVER REQUEST from MSC, the target BSC will pack this message into IntoBSC Handover Request to be transferred to the BM of the target cell. This item measures the times of the current cell receiving IntoBSC Handover Request. It indicates the frequency of the handovers from cells in other BSC to the current cell. Together with Successful incoming interBSC inter cell

202


handovers and Unsuccessful incoming interBSC inter cell handovers , this items shows the performance of this type of handover. Related items: Attempted incoming internal inter cell handovers and Attempted outgoinginterBSC inter cell handovers.

Measurement point: During the procedure of interBSC handover, the target cell (current cell) receives IntoBSC Handover Request. This item is measured in this case.

Formula: none.

III. Attempted incoming internal inter cell handovers (from 900 cell)

Description: During the procedure of internal intercell handover, the source cell sends an Intercell Handover Request message to the target cell after handover algorithm decision. This item measures the times of current cell, as the target cell of internal intercell handover, receiving Intercell Handover Request from the source cell (GSM900). It indicates the frequency of the intraBSC handover from other cells (GSM900) to the current cell. Together with Successfulincoming internal inter cell handovers (from 900 cell) , this item shows the performance of this type of handover. Related items: Attempted incominginternal inter cell handovers .

Note:

Cell system type: GSM 900 cell and GSM 1800 cell.


from 1 to 124.


is from 512 to 885.

Measurement point: During the procedure of internal intercell handover, the target cell (current cell) receives the Intercell Handover Request message from the source cell (GSM900). This item is measured in this case.

Formula: none.

IV. Attempted incoming internal inter cell handovers (from 1800 cell)

Description: During the procedure of internal intercell handover, the source cell sends an Intercell Handover Request message to the target cell after handover algorithm decision. This item measures the times of current cell, as the target cell of internal intercell handover, receiving Intercell Handover Request from the source cell (GSM1800). It indicates the frequency of the intraBSC handover from other cells (GSM1800) to the current cell. Together with

203


Successful incoming internal inter cell handovers (from 1800 cell) , this item shows the performance of this type of handover. Related items: Attemptedincoming internal inter cell handovers .

Note:



from 1 to 124.


is from 512 to 885.

Measurement point: During the procedure of internal intercell handover, the target cell (current cell) receives the Intercell Handover Request message from the source cell (GSM1800). This item is measured in this case.

Formula: none.

V. Attempted outgoing internal inter cell handovers

Description: Internal intercell handover is normally triggered by receiving strength, receiving quality, TA, traffic load, Response to MSC invocation, directed retry, rapid rxlevel drop, better cell, O&M intervention. The source cell and the target cell are different ones in the same BSC. This item measures the times of internal intercell handover attempts initiated by the current cell. This item reflects the frequency of the current cell initiating internal intercell handovers. This item, together with Successful outgoing internal inter cellhandovers and Unsuccessful outgoing internal inter cell handovers , shows the performance of this type of handover. Related items: Attempted outgoinginterBSC inter cell handovers and Attempted incoming internal inter cellhandovers .

Note:

In intraBSC handover, an idle adjacent cell (if the adjacent and the source cell are in different BMs of

the same BSC, the adjacent cell will be treated as an idle cell because system can’t get the using

situation of channels in other BM’s cell) has higher priority to be selected as the target cell. If all

adjacent cells of the source cell are congested, system will still select the default adjacent cell which

is the first one in the handover candidate list, even if it is congested so as to carry out the


204


Measurement point: After handover algorithm decision, the source cell sends an Intercell Handover Request message to the target cell. This item is measured if the source cell and the target cell are different in this case.

Formula: none.

VI. Outgoing internal inter cell handovers

Description: During the procedure of internal intercell handover, after successfully activating the new channel, the target cell will inform the source cell that the channel is ready. After receiving the information, the source cell will send a HANDOVER COMMAND message to the MS. This item measures the times of the HANDOVER COMMAND message being sent from the current cell. This item, together with Attempted outgoing internal inter cell handovers , this item shows the situation of handover failure due to abnormality during the procedure of channel preparation in the target cell. Together with Successfuloutgoing internal inter cell handovers , this item shows the situation of handover failure due to radio interface abnormal. Related items: Incominginternal inter cell handovers and Inter BSC outgoing cell handovers .

Measurement point: During the procedure of internal intercell handover, the source cell sends a HANDOVER COMMAND message to a MS. This item is measured in this case, as shown in Figure 3-52 A1.

Formula: none.

MS BTS BSC MSC/VLR

HANDOVER COMPLETE

HANDOVER COMMAND

A1

(Intercell handover)

HANDOVER PERFORMED

CHANNEL ACT

CHAN ACT ACK

A1: Outgoing internal inter cell handovers

Figure 3-52 Outgoing internal inter cell handovers

VII. Attempted outgoing interBSC inter cell handovers

Description: InterBSC handover is normally triggered by receiving strength, receiving quality, TA, traffic load, Response to MSC invocation, directed retry, rapid rxlevel drop, better cell, O&M intervention. The source cell and target cell are in different BSCs. The source cell sends a HANDOVER REQUIRED

205


message to MSC to initiate a handover. This message contains a list of candidate cells for handover. At this stage, the source cell does not know the target cell which is selected by MSC or whether the selected cell is congested. It only records the first cell in the candidate list as the default target cell. This item measures the times of source cell notifying MSC to initiate handover attempts. This item reflects the frequece of current cell initiating interBSC handover. Together with Successful outgoing interBSC inter cellhandovers and Unsuccessful outgoing interBSC inter cell handovers , this item shows the performance of this type of handover. Related items: Attempted outgoing internal inter cell handovers and Attempted incominginterBSC inter cell handovers.

Measurement point: After handover algorithm decision, the source cell (current cell) sends a HANDOVER REQUIRED message to MSC. This item is measured in this case, as shown in Figure 3-53 A1.

Formula: none.

MS BSC2BSC1 MSC/VLR

HANDOVER REQUIRED

HANDOVER REQUEST

HANDOVER REQ ACK

HANDOVER COMMAND

HANDOVER COMMAND

MS

HANDOVER ACCESSHANDOVER DETECT

HANDOVER COMPLETEHANDOVER COMPLETE

CLEAR COMMAND

CLEAR COMPLETE

A1

B1 , C1, D1, E1, F1

A1: Attempted outgoing interBSC inter cell handovers

B1: Inter BSC outgoing cell handovers

C1: Outgoing interbsc inter cell handovers (to 900)

D1: Outgoing interbsc inter cell handovers (to 1800)

E1: Attempted dual-band intercell handovers

F1: Attempted outgoing inter cell handovers (including various handover causes)

Figure 3-53 Attempted outgoing interBSC inter cell handovers

206


VIII. Attempted outgoing internal inter cell handovers (to 900 cell)

Description: Internal intercell handover is normally triggered by receiving strength, receiving quality, TA, traffic load, Response to MSC invocation, directed retry, rapid rxlevel drop, better cell, O&M intervention. The source cell and target cell are different ones in the same BSC. This item measures the times of handover attempts from the current cell to the target cell (GSM900). It shows the frequency of the handovers from the current cell to other GSM900 cells in the same BSC. This item, together with Successful outgoinginternal inter cell handovers (to 900 cell) , shows the performance of this type of handover. Related items: Attempted outgoing internal inter cellhandovers .

207


Note:

1) In intraBSC handover, an idle adjacent cell (if the adjacent and the source cell are in different BMs

of the same BSC, the adjacent cell will be treated as an idle cell because system can’t get the using





2) Cell system type: GSM 900 cell and GSM 1800 cell.


from 1 to 124.


is from 512 to 885.

Measurement point: After handover algorithm decision, the source cell (current cell) sends Intercell Handover Request to the target cell (GSM900 cell). This item is measured if the source cell and the target cell are different ones in this case.

Formula: none.

IX. Attempted outgoing internal inter cell handovers (to 1800 cell)

Description: Internal intercell handover is normally triggered by receiving strength, receiving quality, TA, traffic load, Response to MSC invocation, directed retry, rapid rxlevel drop, better cell, O&M intervention. The source cell and target cell are different ones in the same BSC. This item measures the times of handover attempts from the current cell to the target cell (GSM1800). It shows the frequency of the handovers from the current cell to other GSM1800 cells in the same BSC. This item, together with Successful outgoinginternal inter cell handovers (to 1800 cell) , shows the performance of this type of handover. Related items: Attempted outgoing internal inter cellhandovers .

Note:

1). In intraBSC handover, an idle adjacent cell (if the adjacent and the source cell are in different BMs

of the same BSC, the adjacent cell will be treated as an idle cell because system can’t get the using





2). Cell system type: GSM 900 cell and GSM 1800 cell.

208



from 1 to 124.


is from 512 to 885.

Measurement point: After handover algorithm decision, the source cell (current cell) sends an Intercell Handover Request message to the target cell (GSM1800 cell). This item is measured if the source cell and the target cell are different.

Formula: none.

X. Outgoing interBSC inter cell handovers (to 900 cell)

Description: During the procedure of interBSC handover, the target BSC finishes allocating the new channel and generates the message HANDOVER COMMAND, which is sent by MSC to the source BSC. After receiving this message, the source BSC sends it to MS. This item measures the times of the current cell sending the HANDOVER COMMAND message in the handovers from the current cell to the GSM900 cells. Together with Successful outgoinginterBSC inter cell handovers (to 900 cell) , this item shows the situation of handover failure due to radio interface abnormal. Related items: Inter BSCoutgoing cell handovers .

Note:



from 1 to 124.


is from 512 to 885.

Measurement point: During the procedure of InterBSC handover, this item is measured when the source cell (current cell) receives the HANDOVER COMMAND message from MSC and the target cell is a GSM900 one, as shown in Figure 3-53 C1.

Formula: none.

XI. Outgoing interBSC inter cell handovers (to 1800 cell)

Description: During the procedure of interBSC handover, the target BSC finishes allocating the new channel and generates the message HANDOVER COMMAND, which is sent by MSC to the source BSC. After receiving this

209


message, the source BSC sends it to MS. This item measures the times of the current cell sending the HANDOVER COMMAND message in the handovers from the current cell to the GSM1800 cells. Together with Successful outgoinginterBSC inter cell handovers (to 1800 cell) , this item shows the situation of handover failure due to radio interface abnormal. Related items: Attemptedoutgoing interBSC inter cell handovers .

Note:



from 1 to 124.


is from 512 to 885.

Measurement point: During the procedure of InterBSC handover, this item is measured when the source cell (current cell) receives the HANDOVER COMMAND message from MSC and the target cell is a GSM1800 one, as shown in Figure 3-53 D1.

Formula: none.

XII. Attempted handovers for uplink quality

Description: When BSC initiates a handover, it will receive a Handover Indication message from LAPD module. This message contains the cause value of handover. The times of handover attempts for all kinds of causes can be measured according to the causes in this message. This item measures the times of handover attempts (including internal intracell handover, internal intercell handover and interBSC handovers) caused by uplink signal quality in the current cell. This item shows the frequency of handover caused by uplink signal quality in the current cell. Related items: Attempted intracellhandovers , Attempted outgoing internal inter cell handovers , Attemptedoutgoing interBSC inter cell handovers and Attempted intracell handovers foruplink quality .

Measurement point: After handover algorithm decision, the source cell (current cell) sends the Intercell Handover Request message (internal intracell handover and internal intercell handover) or the HANDOVER REQUIRED message (interBSC handover) due to uplink signal quality. This item is measured in this case.

Formula: none.

210


XIII. Attempted handovers for downlink quality

Description: When BSC initiates a handover, it will receive a Handover Indication message from LAPD module. This message contains the cause value of handover. The times of handover attempts for all kinds of causes can be measured according to the causes in this message. This item measures the times of handover attempts (including BSC internal intracell handover, internal intercell handover BSC internal intercell and inter BSC handovers) caused by downlink signal quality in the current cell. This item shows the frequency of handover caused by downlink signal quality in the current cell. Related items: Attempted intracell handovers , Attempted outgoing internal inter cellhandovers , Attempted outgoing interBSC inter cell handovers and Attemptedintracell handovers for downlink quality .

Measurement point: After handover algorithm decision, the source cell (current cell) sends the Intercell Handover Request message (internal intracell handover and internal intercell handover) or the HANDOVER REQUIRED message (interBSC handover) due to downlink signal quality. This item is measured in this case.

Formula: none.

XIV. Attempted handovers for uplink strength

Description: When BSC initiates a handover, it will receive a Handover Indication message from LAPD module. This message contains the cause value of handover. The times of handover attempts for all kinds of causes can be measured according to the causes in this message. This item measures the times of handover attempts (including BSC internal intracell handover, internal intercell handover BSC internal intercell and inter BSC handovers) caused by uplink signal strength in the current cell. This item shows the frequency of handover caused by uplink signal strength in the current cell. Related items: Attempted intracell handovers , Attempted outgoing internal inter cellhandovers , Attempted outgoing interBSC inter cell handovers and Attemptedintracell handovers for other causes .

Measurement point: After handover algorithm decision, the source cell (current cell) sends the Intercell Handover Request message (internal intracell handover and internal intercell handover) or the HANDOVER REQUIRED message (interBSC handover) due to uplink signal strength. This item is measured in this case.

Formula: none.

XV. Attempted handovers for downlink strength

Description: When BSC initiates a handover, it will receive a Handover Indication message from LAPD module. This message contains the cause

211


value of handover. The times of handover attempts for all kinds of causes can be measured according to the causes in this message. This item measures the times of handover attempts (including BSC internal intracell handover, internal intercell handover BSC internal intercell and inter BSC handovers) caused by downlink signal strength in the current cell. This item shows the frequency of handover caused by downlink signal strength in the current cell. Related items: Attempted intracell handovers , Attempted outgoing internal inter cellhandovers , Attempted outgoing interBSC inter cell handovers and Attemptedintracell handovers for other causes .

Measurement point: After handover algorithm decision, the source cell (current cell) sends the Intercell Handover Request message (internal intracell handover and internal intercell handover) or the HANDOVER REQUIRED message (interBSC handover) due to downlink signal strength. This item is measured in this case.

Formula: none.

XVI. Attempted handovers for timing advance

Description: When BSC initiates a handover, it will receive a Handover Indication message from LAPD module. This message contains the cause value of handover. The times of handover attempts for all kinds of causes can be measured according to the causes in this message. This item measures the times of handovers (including internal intercell handover and interBSC handover) caused by TA in the current cell (a subscriber moves far away from the serving cell but it is close to the target cell while talking, which causes the signal strength and the signal quality in serving cell drop thus a handover is triggered). This item shows the frequency of handover caused by TA in the current cell. Related items: Attempted outgoing internal inter cell handovers and Attempted outgoing interBSC inter cell handovers .

Measurement point: After handover algorithm decision, the source cell sends the Intercell Handover Request message (internal intercell handover) or the HANDOVER REQUIRED message (interBSC handover) due to TA. This item is measured in this case.

Formula: none.

XVII. Attempted handovers for better cell

Description: When BSC initiates a handover, it will receive a Handover Indication message from LAPD module. This message contains the cause value of handover. The times of handover attempts for all kinds of causes can be measured according to the causes in this message. This item measures the times of handovers (including internal intercell handover and interBSC handover) caused by "better cell" (adjacent cell with lower path loss (PBGT) or

212


higher priority) in the current cell. This item shows the frequency of handover caused by "better cell" in the current cell. Related items: Attempted outgoinginternal inter cell handovers and Attempted outgoing interBSC inter cellhandovers .

Measurement point: After handover algorithm decision, the source cell sends the Intercell Handover Request message (internal intercell handover) or the HANDOVER REQUIRED message (interBSC handover) due to "better cell". This item is measured in this case.

Formula: none.

XVIII. Attempted handovers for traffic load

Description: When BSC initiates a handover, it will receive a Handover Indication message from LAPD module. This message contains the cause value of handover. The times of handover attempts for all kinds of causes can be measured according to the causes in this message. This item measures the times of handovers (including internal intercell handover and interBSC handover) caused by traffic load in the current cell. This item shows the frequency of handover caused by traffic load in the current cell. Related items: Attempted outgoing internal inter cell handovers and Attempted outgoinginterBSC inter cell handovers.

Measurement point: After handover algorithm decision, the source cell sends the Intercell Handover Request message (internal intercell handover) or the HANDOVER REQUIRED message (interBSC handover) due to traffic load. This item is measured in this case.

Formula: none.

XIX. Attempted handovers for rapid level drop

Description: When BSC initiates a handover, it will receive a Handover Indication message from LAPD module. This message contains the cause value of handover. The times of handover attempts for all kinds of causes can be measured according to the causes in this message. This item measures the times of handovers (including internal intercell handover and interBSC handover) caused by rapid rxlevel drop in the current cell. This item shows the frequency of handover caused by rapid rxlevel drop in the current cell. Related items: Attempted outgoing internal inter cell handovers and Attemptedoutgoing interBSC inter cell handovers .

Measurement point: After handover algorithm decision, the source cell sends the Intercell Handover Request message (internal intercell handover) or the HANDOVER REQUIRED message (interBSC handover) due to rapid rxlevel drop. This item is measured in this case.

Formula: none.

213


XX. Attempted handovers for response to MSC invocation

Description: When BSC initiates a handover, it will receive a Handover Indication message from LAPD module. This message contains the cause value of handover. The times of handover attempts for all kinds of causes can be measured according to the causes in this message. This item measures the times of handovers (including internal intercell handover and interBSC handover) caused by Response to MSC invocation (MSC sending HANDOVER CANDIDATE ENQUIRY to BSC which causes handovers of multiple MSs in a cell) in the current cell. This item shows the frequency of handover caused by Response to MSC invocation in the current cell. Related items: Attempted outgoing internal inter cell handovers and Attemptedoutgoing interBSC inter cell handovers .

Measurement point: After handover algorithm decision, the source cell sends the Intercell Handover Request message (internal intercell handover) or the HANDOVER REQUIRED message (interBSC handover) due to Response to MSC invocation. This item is measured in this case.

Formula: none.

XXI. Attempted handovers for O&M intervention

Description: When BSC initiates a handover, it will receive a Handover Indication message from LAPD module. This message contains the cause value of handover. The times of handover attempts for all kinds of causes can be measured according to the causes in this message. This item measures the times of handover attempts (including BSC internal intracell handover, internal intercell handover BSC internal intercell and inter BSC handovers) caused by O&M intervention (operation on O&M console which causes handovers, such as forced handover, blocking without call dropped (blocking channels, TRXs and cells), BCCH mutual aid or TRX mutual aid) in the current cell. This item shows the frequency of handover caused by O&M intervention. Related items: Attempted intracell handovers , Attempted outgoing internal inter cellhandovers , Attempted outgoing interBSC inter cell handovers and Attemptedintracell handovers for other causes .

Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (BSC internal intracell and BSC internal intercell handovers) or the HANDOVER REQUIRED message (interBSC handover) due to O&M intervention. This item is measured in this case.

Formula: none.

XXII. Attempted handovers for directed retry

Description: When BSC initiates a handover, it will receive a Handover Indication message from LAPD module. This message contains the cause

214


value of handover. The times of handover attempts for all kinds of causes can be measured according to the causes in this message. This item measures the times of handovers (including internal intercell handover and interBSC handover) caused by directed retry (a handover triggered for the current cell is congested during the procedure of assignment) in the current cell. This item shows the frequency of handover caused by directed retry. Related items: Attempted outgoing internal inter cell handovers and Attempted outgoinginterBSC inter cell handovers.

Measurement point: After handover algorithm decision, the source cell sends the Intercell Handover Request message (internal intercell handover) or the HANDOVER REQUIRED message (interBSC handover) due to directed retry. This item is measured in this case.

Formula: none.

XXIII. Attempted handovers for other causes

Description: When BSC initiates a handover, it will receive a Handover Indication message from LAPD module. This message contains the cause value of handover. The times of handover attempts for all kinds of handover causes can be measured according to the cause in this message. This item measures the times of handover attempts (including BSC internal intracell handover, internal intercell handover BSC internal intercell and inter BSC handovers) caused by other causes (such as fast moving, handover cause being abnormal value) in the current cell. This item shows the frequency of handover caused by other causes. Related items: Attempted intracellhandovers , Attempted outgoing internal inter cell handovers , Attemptedoutgoing interBSC inter cell handovers and Attempted intracell handovers forother causes .

Measurement point: After handover algorithm decision, BSC sends Intercell Handover Request (BSC internal intracell and BSC internal intercell handovers) or the HANDOVER REQUIRED message (interBSC handover) due to other causes. This item is measured in this case.

Formula: none.

XXIV. Attempted handovers with uplink receiving level rank 0

Description: When BSC initiates handover, it will receive Handover Indication from LAPD module. The times of various ranks can be measured according to the receiving strength rank and receiving quality rank (obtained from the last MR that triggered the handover) contained in this message. This item measures the times of uplink receiving strength rank being 0 (rxlevel -100 dBm) when the current cell initiates a handover (including internal intracell handover, internal intercell handover and interBSC handover). Together with

215


times of other receiving strength ranks and receiving quality ranks, this item shows the handover environment of the current cell.

Measurement point: After handover algorithm decision, the source cell (current cell) sends an Intercell Handover Request message (internal intracell handover, internal intercell handover) or the HANDOVER REQUIRED message (interBSC handover) and the uplink receiving strength rank is 0 (rxlevel -100 dBm).

Formula: none.

XXV. Attempted handovers with uplink receiving level rank 1

Description: When BSC initiates handover, it will receive Handover Indication from LAPD module. The times of various ranks can be measured according to the receiving strength rank and receiving quality rank (obtained from the last MR that triggered the handover) contained in this message. This item measures the times of uplink receiving strength rank being 1 (-99 ~ -95 dBm) when the current cell initiates a handover (including internal intracell handover, internal intercell handover and interBSC handover). Together with times of other receiving strength ranks and receiving quality ranks, this item shows the handover environment of the current cell.

Measurement point: After handover algorithm decision, the source cell (current cell) sends an Intercell Handover Request message (internal intracell handover, internal intercell handover) or the HANDOVER REQUIRED message (interBSC handover) and the uplink receiving strength rank is 1 (-99 ~ -95 dBm).

Formula: none.

XXVI. Attempted handovers with uplink receiving level rank 2



216


Formula: none.

XXVII. Attempted handovers with uplink receiving level rank 3



Formula: none.

XXVIII. Attempted handovers with uplink receiving level rank 4



Formula: none.

XXIX. Attempted handovers with uplink receiving level rank 5

Description: When BSC initiates handover, it will receive Handover Indication from LAPD module. The times of various ranks can be measured according to the receiving strength rank and receiving quality rank (obtained from the last MR that triggered the handover) contained in this message. This item

217


measures the times of uplink receiving strength rank being 5 ( -69 dBm) when the current cell initiates a handover (including internal intracell handover, internal intercell handover and interBSC handover). Together with times of other receiving strength ranks and receiving quality ranks, this item shows the handover environment of the current cell.

Measurement point: After handover algorithm decision, the source cell (current cell) sends an Intercell Handover Request message (internal intracell handover, internal intercell handover) or the HANDOVER REQUIRED message (interBSC handover) and the uplink receiving strength rank is 5 ( -69 dBm).

Formula: none.

XXX. Attempted handovers with uplink receiving quality rank 0

Description: When BSC initiates handover, it will receive Handover Indication from LAPD module. The times of various ranks can be measured according to the receiving strength rank and receiving quality rank (obtained from the last MR that triggered the handover) contained in this message. This item measures the times of uplink receiving quality rank being 0 (BER < 0.2%) when the current cell initiates handover (including BSC internal intra cell, BSC internal inter cell and interBSC handovers). Together with times of other receiving strength ranks and receiving quality ranks, this item shows the handover environment of the current cell.

Measurement point: After handover algorithm decision, the source cell sends an Intercell Handover Request message (BSC internal intra cell, BSC internal inter cell handovers) or the HANDOVER REQUIRED message (interBSC handovers) and the uplink receiving quality rank is 0 (BER < 0.2%).

Formula: none.

XXXI. Attempted handovers with uplink receiving quality rank 1

Description: When BSC initiates handover, it will receive Handover Indication from LAPD module. The times of various ranks can be measured according to the receiving strength rank and receiving quality rank (obtained from the last MR that triggered the handover) contained in this message. This item measures the times of uplink receiving quality rank being 1 (BER: 0.2 ~ 0.4%) when the current cell initiates handover (including BSC internal intra cell, BSC internal inter cell and interBSC handovers). Together with times of other receiving strength ranks and receiving quality ranks, this item shows the handover environment of the current cell.

Measurement point: After handover algorithm decision, the source cell sends an Intercell Handover Request message (BSC internal intra cell, BSC internal

218


inter cell handovers) or the HANDOVER REQUIRED message (interBSC handovers) and the uplink receiving quality rank is 1 (BER: 0.2 ~ 0.4%).

Formula: none.

XXXII. Attempted handovers with uplink receiving quality rank 2


Measurement point: After handover algorithm decision, the source cell sends an Intercell Handover Request message (BSC internal intra cell, BSC internal inter cell handovers) or the HANDOVER REQUIRED message (interBSC handovers) and the uplink receiving quality rank is 2 (BER: 0.4 ~ 0.8%).

Formula: none.

XXXIII. Attempted handovers with uplink receiving quality rank 3



Formula: none.

XXXIV. Attempted handovers with uplink receiving quality rank 4

Description: When BSC initiates handover, it will receive Handover Indication from LAPD module. The times of various ranks can be measured according to the receiving strength rank and receiving quality rank (obtained from the last MR that triggered the handover) contained in this message. This item

219


measures the times of uplink receiving quality rank being 4 (BER: 1.6 ~ 3.2%) when the current cell initiates handover (including BSC internal intra cell, BSC internal inter cell and interBSC handovers). Together with times of other receiving strength ranks and receiving quality ranks, this item shows the handover environment of the current cell.


Formula: none.

XXXV. Attempted handovers with uplink receiving quality rank 5



Formula: none.

XXXVI. Attempted handovers with uplink receiving quality rank 6



220


Formula: none.

XXXVII. Attempted handovers with uplink receiving quality rank 7

Description: When BSC initiates handover, it will receive Handover Indication from LAPD module. The times of various ranks can be measured according to the receiving strength rank and receiving quality rank (obtained from the last MR that triggered the handover) contained in this message. This item measures the times of uplink receiving quality rank being 7 (BER > 12.8%) when the current cell initiates handover (including BSC internal intra cell, BSC internal inter cell and interBSC handovers). Together with times of other receiving strength ranks and receiving quality ranks, this item shows the handover environment of the current cell.

Measurement point: After handover algorithm decision, the source cell sends an Intercell Handover Request message (BSC internal intra cell, BSC internal inter cell handovers) or the HANDOVER REQUIRED message (interBSC handovers) and the uplink receiving quality rank is 7 (BER > 12.8%).

Formula: none.

XXXVIII. Average uplink receiving level at handover request

Description: When BSC initiates handover, it will receive Handover Indication from LAPD module. This message contains uplink receiving strength (obtained from the last MR that triggered the handover). Whenever the current cell initiates a handover (including internal intracell handover, internal intercell handover and interBSC handover), the uplink receiving strength will be added to the value of this item which is the sum of the receiving strength at handover in BSC. The sum of the receiving strengths at handover and the times of initiating three types of attempted handovers can be used to calculate the average receiving strength when the current cell initiates handovers. This item shows the handover environment of the current cell.

Measurement point: After handover algorithm decision, the source cell sends an Intercell Handover Request message (internal intracell handover, internal intercell handover) or the HANDOVER REQUIRED message (interBSC handover). The uplink receiving strength reported by LAPD module is measured at this moment for this item.

Formula: Sum of receiving strengths at handovers / (Attempted outgoinginternal inter cell handovers + Attempted outgoing interBSC inter cellhandovers + Attempted intracell handovers )

221


Note:

The sum of receiving strengths at handovers is the BSC internal statistic meaning of average

receiving strength item at initiating handover. The average value is obtained after the calculation

following the formula.

XXXIX. Average uplink receiving quality at handover request

Description: When BSC initiates handover, it will receive Handover Indication from LAPD module. This message contains uplink receiving quality (obtained from the last MR that triggered the handover). Whenever the current cell initiates a handover (including internal intracell handover, internal intercell handover and interBSC handover), the uplink receiving quality will be added to the value of this item which is the sum of the receiving strength at handover in BSC. The sum of the receiving strengths at handover and the times of initiating three types of attempted handovers can be used to calculate the average receiving quality when the current cell initiates handovers. This item shows the handover environment of the current cell.

Measurement point: After handover algorithm decision, the source cell sends an Intercell Handover Request message (internal intracell handover, internal intercell handover) or the HANDOVER REQUIRED message (interBSC handover). The uplink receiving quality reported by LAPD module is measured at this moment for this item.

Formula: Sum of receiving quality at handovers / (Attempted outgoing internalinter cell handovers + Attempted outgoing interBSC inter cell handovers + Attempted intracell handovers )

222


Note:

The sum of receiving quality at handovers is the BSC internal statistic meaning of average receiving

quality item at initiating handover. The average value is obtained after the calculation following the

formula.

XL. Successful incoming internal inter cell handovers

Description: Internal intercell handovers can be classified into two types by the handover cause: directed retry, non-directed retry (e.g. signal quality, signal strength, TA, traffic load, rapid rxlevel drop, better cell, Response to MSC invocation, and O&M intervention). This item measures the times of successful handovers. This item, together with Attempted incoming internal inter cellhandovers , helps the user know the performance of internal intercell handovers. Related items: Successful incoming interBSC inter cellhandovers , Successful outgoing internal inter cell handovers , Successfuloutgoing interBSC inter cell handovers . Successful intracell handovers .

Measurement point: 1) Measured when the target cell (current cell) sends ASSIGNMENT

COMPLETE to MSC after the MS has been successfully handed over to the target cell in the internal intercell handover (handover cause: directed retry), as shown in Figure 3-54 A1.

2) Measured when the target cell (current cell) sends a HANDOVER PERFORMED message to MSC after the MS has been successfully handed over to the target cell in the internal intercell handover (handover cause: non-directed retry, e.g. signal quality, signal strength, TA, traffic load, rapid rxlevel drop, better cell, Response to MSC invocation, and O&M intervention), as shown in Figure 3-55 B1.

Formula: none.

MS BTS BSC MSC/VLR

HANDOVER COMPLETE

HANDOVER COMMAND

A1, B1, C1, D1, E1

ASSIGNMENT REQUEST

ASSIGNMENT COMPLETE

A1: Successful incoming internal inter cell handovers

B1: Successful incoming internal inter cell handovers (from 900)

C1: Successful incoming internal inter cell handovers (from 1800)

D1: Successful dual-band intercell handovers

223


E1: Successful incoming inter cell handovers

Figure 3-54 Successful incoming internal inter cell handovers (directed retry)

MS BTS BSC MSC/VLR

HANDOVER COMPLETE

.HANDOVER COMMAND

HANDOVER PERFORMED

A1, B1 , C1, D1, E1, F1

A1: Successful intracell handovers

B1: Successful incoming internal inter cell handovers


D1: Successful incoming internal inter cell handovers (from 1800)

E1: Successful dual-band intercell handovers

F1: Successful incoming inter cell handovers

Figure 3-55 Successful intraBSC handovers (not directed retry)

XLI. Successful incoming interBSC inter cell handovers

Description: During the procedure of interBSC handover, the target BSC receives the HANDOVER REQUEST message from MSC, and starts the preparation of new channel. After the channel preparation has been done, and the MS has accessed the target cell, the target BSC fv MSC, and this handover is finished successfully. This item, together with Attempted incominginterBSC inter cell handovers, helps the user know the performance of interBSC handovers. Related items: Successful incoming internal inter cellhandovers , Successful outgoing internal inter cell handovers , Successfuloutgoing interBSC inter cell handovers .

Measurement point: During the procedure of interBSC handover, the target (current) cell receives HANDOVER COMPLETE, and sends it to MSC. This item is measured in this case, as shown in Figure 3-56 A1.

Formula: none.

224


MS BTS BSC MSC/VLR

HANDOVER COMPLETE

.HANDOVER DETECTION

A1, B1, C1

CHANNEL ACT

CHAN ACT ACK

HANDOVER COMPLETE

HANDOVER REQ ACK

HANDOVER REQUESTT

A1: Successful incoming inter BSC inter cell handovers

B1: Successful dual-band intercell handovers

C1: Successful incoming inter cell handovers

Figure 3-56 Successful incoming inter BSC internal inter cell handovers

XLII. Successful incoming internal inter cell handovers (from 900 cell)

Description: Internal intercell handovers can be classified into two types by the handover cause: directed retry, non-directed retry (e.g. signal quality, signal strength, TA, traffic load, rapid rxlevel drop, better cell, Response to MSC invocation, and O&M intervention). This item measures the times of MS being handed over successfully from other GSM 900 cell to the current cell in the same BSC. This item, together with Attempted incoming internal inter cellhandovers (from 900 cell) , helps the user know the performance of internal intercell handover. Related items: Successful incoming internal inter cellhandovers .

Note:



from 1 to 124.


is from 512 to 885.

Measurement point:1) Measured when the target cell (current cell) sends ASSIGNMENT

COMPLETE to MSC after the MS has been successfully handed over

225


from the GSM900 cell to the target cell in the internal intercell handover (handover cause: directed retry), as shown in Figure 3-54 B1.

2) Measured when the target cell (current cell) sends a HANDOVER PERFORMED message to MSC after the MS has been successfully handed over from the GSM900 cell to the target cell in the internal intercell handover (handover cause: non-directed retry, e.g. signal quality, signal strength, TA, traffic load, rapid rxlevel drop, better cell, Response to MSC invocation, and O&M intervention), as shown in Figure 3-55 C1.

Formula: none.

XLIII. Successful incoming internal inter cell handovers (from 1800 cell)

Description: Internal intercell handovers can be classified into two types by the handover cause: directed retry, non-directed retry (e.g. signal quality, signal strength, TA, traffic load, rapid rxlevel drop, better cell, Response to MSC invocation, and O&M intervention). This item measures the times of MS being handed over successfully from other GSM 1800 cell to the current cell in the same BSC. This item, together with Attempted incoming internal inter cellhandovers (from 1800 cell) , helps the user know the performance of internal intercell handover. Related items: Successful incoming internal inter cellhandovers .

Note:



from 1 to 124.


is from 512 to 885.

Measurement point:1) Measured when the target cell (current cell) sends ASSIGNMENT

COMPLETE to MSC after the MS has been successfully handed over from the GSM1800 cell to the target cell in the internal intercell handover (handover cause: directed retry), as shown in Figure 3-54 C1.

2) Measured when the target cell (current cell) sends a HANDOVER PERFORMED message to MSC after the MS has been successfully handed over from the GSM1800 cell to the target cell in the internal intercell handover (handover cause: non-directed retry, e.g. signal quality, signal strength, TA, traffic load, rapid rxlevel drop, better cell, Response to MSC invocation, and O&M intervention), as shown in Figure 3-55 D1.

226


Formula: none.

XLIV. Successful outgoing internal inter cell handovers

Description: During the procedure of internal intercell handover, the source cell sends a HANDOVER COMMAND message to MS. After MS is handed over to the target cell, the target cell sends Inter Clear Request to the source cell to indicate that the handover succeeded. On reception of this message, the source cell clears the original resources. This item measures the times of the current cell, as the source cell, receiving Inter Clear Request from the target cell. Together with Attempted outgoing internal inter cell handovers , this item shows the performance of internal intercell handover. Related items: Successful incoming internal inter cell handovers , Successful outgoinginterBSC inter cell handovers.

Measurement point: During the procedure of internal intercell handover, the source cell (current cell) receives Inter Clear Request (cause: internal intercell handover succeeded) from the target cell. This item is measured in this case.

Formula: none.

XLV. Successful outgoing interBSC inter cell handovers

Description: During the procedure of interBSC handover, the source cell sends a HANDOVER COMMAND message to MS. After MS successfully accessed the target cell, the source cell receives the CLEAR COMMAND message (cause: handover success) from MSC and begins to clear the previous resources. This handover successfully ends here. Together with Attemptedoutgoing interBSC inter cell handovers , Unsuccessful outgoing interBSCinter cell handovers , this item shows the performance of interBSC handover. Related items: Successful intracell handovers , Successful incoming interBSCinter cell handovers , Successful outgoing internal inter cell handovers .

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives the CLEAR COMMAND message (cause: handover success) from MSC. This item is measured in this case, as shown in Figure 3-57 A1.

Formula: none.

227


MS BSC2BSC1 MSC/VLR

HANDOVER REQUIRED

HANDOVER REQUEST

HANDOVER REQ ACK

HANDOVER COMMAND


HANDOVER COMPLETE

CLEAR COMPLETEA1, B1, C1, D1, E1

CLEAR COMMAND

A14: Successful outgoing interbsc inter cell handovers

B1: Successful outgoing interbsc inter cell handovers (to 900)

C1: Successful outgoing interbsc inter cell handovers (to 1800)


E1: Successful outgoing inter cell handovers (including various causes)

Figure 3-57 Successful outgoing interBSC inter cell handovers

XLVI. Successful outgoing internal inter cell handovers (to 900 cell)

Description: During the procedure of internal intercell handover, the source cell (current cell) sends a HANDOVER COMMAND message to MS. After MS is handed over to the target cell, the target cell sends Inter Clear Request to the source cell to clear the previous resources. This item measures the times of the current cell, as the source cell, receiving Inter Clear Request from the target GSM900 cell. Together with Attempted outgoing internal inter cellhandovers (to 900 cell) , this item shows the performance of internal intercell handover. Related items: Successful outgoing internal inter cell handovers .

Note:



from 1 to 124.


is from 512 to 885.

228


Measurement point: During the procedure of internal intercell handover, the source cell (current cell) receives Inter Clear Request (cause: internal intercell handover succeeded) from the target GSM900 cell.

Formula: none.

XLVII. Successful outgoing internal inter cell handovers (to 1800 cell)

Description: During the procedure of internal intercell handover, the source cell (current cell) sends a HANDOVER COMMAND message to MS. After MS is handed over to the target cell, the target cell sends Inter Clear Request to the source cell to clear the previous resources. This item measures the times of the current cell, as the source cell, receiving Inter Clear Request from the target GSM1800 cell. Together with Attempted outgoing internal inter cellhandovers (to 1800 cell) , this item shows the performance of internal intercell handover. Related items: Successful outgoing internal inter cell handovers .

Note:



from 1 to 124.


is from 512 to 885.

Measurement point: During the procedure of internal intercell handover, the source cell (current cell) receives Inter Clear Request (cause: internal intercell handover succeeded) from the target GSM1800 cell.

Formula: none.

XLVIII. Successful outgoing interBSC inter cell handovers (to 900 cell)

Description: During the procedure of interBSC handover, the source cell sends a HANDOVER COMMAND message to MS. After successfully accessed the target cell, MSC sends CLEAR COMMAND (cause: handover success) to source cell to clear the previous resources. This handover successfully ends here. This item measures the times of successful interBSC handovers from the current cell to other GSM900 cells in other BSC. Related items: Successfuloutgoing interBSC inter cell handovers .

229


Note:



from 1 to 124.


is from 512 to 885.

Measurement point: During the procedure of interBSC handover from the source cell (current cell) to a GSM900 cell, the source cell receives the CLEAR COMMAND message (cause: handover success) from MSC. This item is measured in this case, as shown in Figure 3-57 B1.

Formula: none.

XLIX. Successful outgoing interBSC inter cell handovers (to 1800 cell)

Description: During the procedure of interBSC handover, the source cell (current cell) sends a HANDOVER COMMAND message to MS. After successfully accessed the target cell, MSC sends CLEAR COMMAND (cause: handover success) to source cell to clear the previous resources. This handover successfully ends here. This item measures the times of successful interBSC handovers from the current cell to other GSM1800 cells in other BSC. Related items: Successful outgoing interBSC inter cell handovers .

Note:



from 1 to 124.


is from 512 to 885.

Measurement point: During the procedure of interBSC handover from the source cell (current cell) to a GSM1800 cell, the source cell receives the CLEAR COMMAND message (cause: handover success) from MSC. This item is measured in this case, as shown in Figure 3-57 C1.

Formula: none.

230


L. Unsuccessful incoming internal inter cell handovers

Description: After internal intercell handover is initiated, the target cell receives the Intercell Handover Request message from the source cell. And then, it allocates and activates channels and waits for the access of MS to the target channel. If the access of MS is successful, the target cell will send a HANDOVER PERFORMED message to MSC to indicate that this handover is successful. If abnormality occurs during this process, then this handover is a failure. This item measures the times of unsuccessful incoming internal inter cell handovers to the current cell. Together withAttempted incoming internalinter cell handovers , Successful incoming internal inter cell handovers , this item shows the performance of incoming internal inter cell handover. Related items: Unsuccessful intracell handovers , Unsuccessful outgoing internal intercell handovers , Unsuccessful incoming interBSC inter cell handovers .

Note:

The following are the causes of unsuccessful incoming internal inter cell handover:

1) The original channel becomes invalid or connection disconnects due to abnormality of radio

resource and terrestrial resource;


parameters;

3) Handover is interrupted and the original call is cleared when error has been detected during BSS



Measurement point:1) During the procedure of internal intercell handover, the target cell (current

cell) receives Inter Clear Request from the source cell. This item is measured in this case. The source cell sends Inter Clear Request to the target cell on reception of the CONNECTION FAILURE INDICATION message, the ERROR INDICATION message, the CLEAR COMMAND message or at the expiry of the timer waiting for Inter Clear Request.

2) During the procedure of internal intercell handover, the target cell (current cell) receives CONNECTION FAILURE INDICATION from BTS. This item is measured in this case, as shown in Figure 3-58 A1, A2 and A3.

3) During the procedure of internal intercell handover, the target cell (current cell) receives the ERROR INDICATION message (cause: timer T200 expired (N200 + 1) times (0x01) or unsolicited DM response, multiple

231


frame established state (0x05) or sequence error (0x07)). This item is measured in this case, as shown in Figure 3-58 A5, A6 and A7.

4) During the procedure of internal intercell handover, abnormality (no available channel) occurs when the target cell (current cell) is allocating new channels. This item is measured in this case, and at the same time, Intercell Handover Reject is sent to the source cell.

5) During the procedure of internal intercell handover, the target cell (current cell) fails to send the CHANNEL ACTIVATION message. This item is measured in this case, and at the same time, Intercell Handover Reject is sent to the source cell.

6) During the procedure of internal intercell handover, the target (current) cell receives the CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE message. This item is measured in this case, and at the same time, Intercell Handover Reject is sent to the source cell, as shown in Figure 3-58 A4.

7) During the procedure of internal intercell handover, the target (current) cell receives Clear For Handover Failure from the source cell after successful channel activation. This happens when MS fails to access the target cell and returns to the source cell, and then the source cell notifies the target cell to clear the related resources after receiving the HANDOVER FAILURE message from MS.

8) During the procedure of internal intercell handover, the target (current) cell waiting for CHANNEL ACTIVATION ACKNOWLEDGE times out. This item is measured in this case, and at the same time, Intercell Handover Reject is sent to the source cell.

9) During the procedure of internal intercell handover, the target (current) cell waiting for HANDOVER DETECTION times out again after resending Intercell Handover Response on timeout. This item is measured in this case, and then the related resources are released.

10) During the procedure of internal intercell handover, the target (current) cell waiting for HANDOVER COMPLETE times out. This item is measured in this case, and at the same time, Inter Clear Request is sent to the source cell.

Formula: none.

232


MS BTS BSC MSC/VLR

HANDOVER COMPLETE

.HANDOVER COMMAND

HANDOVER PERFORMED

CONN FAIL IND

A1 , B1

New Channel

ERROR IND

Old Channel

CHANNEL ACT

CHAN ACT ACK

HANDOVER DETECTIOIN

CHAN ACT NACK

A4

CONN FAIL IND

A2, B2

CONN FAIL IND

A3 , B3

A5, B4

ERROR INDA6 , B5

ERROR IND

A7 , B6

New Channel

A1~A7: Unsuccessful incoming internal inter cell handovers

B1~B6: Unsuccessful incoming internal inter cell handovers (other causes)

Figure 3-58 Unsuccessful incoming internal inter cell handovers

LI. Unsuccessful incoming internal inter cell handovers (no radio resource available)

Description: After internal intercell handover is initiated, the target cell receives the Intercell Handover Request message from the source cell. And then, it starts to allocate channels. If the channel allocation fails here, this handover will fail due to no channel available in the target cell. This item measures the times of unsuccessful internal intercell handovers to the current cell due to no radio resource available. Together with Unsuccessful incoming internal intercell handovers , this item shows the situation of unsuccessful handover due to channel allocation.

Measurement point: During the procedure of internal intercell handover, abnormality (no available channel) occurs when the target cell (current cell) is allocating new channels. This item is measured in this case, and at the same time, Intercell Handover Reject is sent to the source cell.

Formula: none.

233


LII. Unsuccessful incoming internal inter cell handovers (other causes)

Description: After internal intercell handover is initiated, the target cell receives the Intercell Handover Request message from the source cell. And then, it allocates and activates channels and waits for the access of MS to the target channel. If the access of MS is successful, the target cell will send a HANDOVER PERFORMED message to MSC to indicate that this handover is successful. If abnormality occurs during this process, then this handover is a failure. This item measures the times of unsuccessful incoming internal inter cell handovers to the current cell due to other causes (e.g. timer timeout, radio interface abnormal). Together with Unsuccessful incoming internal inter cellhandovers , this item shows the situation of unsuccessful handover due to other causes.

Measurement point:1) During the procedure of internal intercell handover, the target cell (current

cell) receives Inter Clear Request from the source cell. This item is measured in this case. The source cell sends Inter Clear Request to the target cell on reception of the CONNECTION FAILURE INDICATION message, the ERROR INDICATION message, the CLEAR COMMAND message or at the expiry of the timer waiting for the Inter Clear Request message.

2) Measured when the source cell (current cell) receives CONNECTION FAILURE INDICATION from BTS during the procedure of internal intercell handover, as shown in Figure 3-58 B1, B2 and B3.

3) During the procedure of internal intercell handover, the target cell (current cell) receives the ERROR INDICATION message (cause: timer T200 expired (N200 + 1) times (0x01) or unsolicited DM response, multiple frame established state (0x05) or sequence error (0x07)). This item is measured in this case, as shown in Figure 3-58 B4, B5 and B6.

4) During the procedure of internal intercell handover, the target cell (current cell) fails to send the CHANNEL ACTIVATION message. This item is measured in this case, and at the same time, Intercell Handover Reject is sent to the source cell.

5) During the procedure of internal intercell handover, the target cell (current cell) receives Clear For Handover Failure from the source cell after successful channel activation. This happens when MS fails to access the target cell and returns to the source cell, and then the source cell notifies the target cell to clear the related resources after receiving the HANDOVER FAILURE message from MS.

6) During the procedure of internal intercell handover, the target (current) cell receives the CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE

234


message. This item is measured in this case, and at the same time, Intercell Handover Reject is sent to the source cell.

7) During the procedure of internal intercell handover, the target (current) cell waiting for CHANNEL ACTIVATION ACKNOWLEDGE times out. This item is measured in this case, and at the same time, Intercell Handover Reject is sent to the source cell.

8) During the procedure of internal intercell handover, the target (current) cell waiting for HANDOVER DETECTION times out again after resending Intercell Handover Response on timeout. This item is measured in this case, and then the related resources are released.

9) During the procedure of internal intercell handover, the target (current) cell waiting for HANDOVER COMPLETE times out. This item is measured in this case, and at the same time, the Inter Clear Request message is sent to the source cell.

Formula: none.

LIII. Unsuccessful outgoing internal inter cell handovers

Description: After internal intercell handover is initiated, the source cell enters the state of waiting for Intercell Handover Response. The target cell allocates and activates channels, and then sends Intercell Handover Response to notify the source cell. The source cell sends a HANDOVER COMMAND message to MS, and then enters the states of waiting for the Inter Clear Request message. After MS has successfully access the new channel, the target cell sends Inter Clear Request to notify the source cell to clear the original resource. This handover is a successful one. The abnormalities occur during this period will result in the failure of outgoing internal inter cell handovers. This item measures the times of unsuccessful outgoing internal inter cell handovers to the current cell. Together with Attempted outgoing internal inter cellhandovers , Successful outgoing internal inter cell handovers , this item shows the performance of internal intercell handover. Related items: Unsuccessful intracell handovers , Unsuccessful incoming internal inter cellhandovers , Unsuccessful outgoing interBSC inter cell handovers .

Note:

The following are the causes of unsuccessful outgoing internal inter cell handover:

1) The original channel becomes invalid or connection disconnects due to abnormality of radio

resource and terrestrial resource;


parameters;

235


3) Handover is interrupted and the original call is cleared when error has been detected during BSS



Measurement point:1) During the procedure of internal intercell handover, the source cell (current

cell) receives CONNECTION FAILURE INDICATION from BTS. This item is measured in this case, as shown in Figure 3-59 A1 and A2.

2) During the procedure of internal intercell handover, MS fails to access the target cell and returns to the source cell (current cell), and the source cell receives the HANDOVER FAILURE message from MS. This item is measured in this case, and at the same time, Clear For Handover Failure is sent to the target cell, as shown in Figure 3-59 A3.

3) During the procedure of internal intercell handover, the source cell (current cell) receives the ERROR INDICATIONmessage (cause: timer T200 expired (N200 + 1) times (0x01) or unsolicated DM response, multiple frame established state (0x05) or sequence error" (0x07)) from BTS. This item is measured in this case, as shown in Figure 3-59 A4 and A5.

4) During the procedure of internal intercell handover, the source cell (current cell) receives the CLEAR COMMAND message from MSC. This item is measured in this case, as shown in Figure 3-59 A6 and A7.

5) During the procedure of internal intercell handover, when AM/CM net-drive fails or the timer waiting for HANDOVER COMPLETE times out, the target cell sends Inter Clear Request to the source cell. This item is measured when the source cell (current cell) receives this message.

6) During the procedure of internal intercell handover, the target cell sends Intercell Handover Reject to the source cell when it fails to prepare or activate the channels (e.g. channel allocation failure, CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE received, expiry of the timer waiting for CHANNEL ACTIVATION ACKNOWLEDGE). This item is measured when the source cell (current cell) receives this message.

7) During the procedure of internal intercell handover, when the source cell (current cell) waiting for Inter Clear Request times out, it sends Inter Clear Request to the target cell. This item is measured in this case.

8) During the procedure of internal intercell handover, the source cell waiting for Intercell Handover Response times out again after resending Intercell Handover Request. This item is measured in this case, and then the related resources will be released.

Formula: none.

236


MS BTS BSC MSC/VLR

HANDOVER COMPLETE

.HANDOVER COMMAND

HANDOVER PERFORMED

CONN FAIL IND

New Channel

ERROR IND

Old Channel

CHANNEL ACT

A1 , F2

CONN FAIL INDA2, F3, H1,J1

A4, F4

ERROR INDA5, F5, H2, J2

.HANDOVER FAILURE

A3, B1, C1, D1, E1, F1, G1, I1

CLEAR COMMAND

A6, F6

CLEAR COMMANDA7, F7Old Channel

A1~A7: Unsuccessful outgoing internal inter cell handovers

B1: Unsuccessful outgoing internal inter cell handovers (channel invalid)

C1: Unsuccessful outgoing internal inter cell handovers (TA invalid)

D1: Unsuccessful outgoing internal inter cell handovers (frequency invalid)

E1: Unsuccessful outgoing internal inter cell handovers (timer expired)

F1~F7: Unsuccessful outgoing internal inter cell handovers (other causes)

G1: Unsuccessful internal inter cell handovers with successful reversions

H1~H2: Unsuccessful internal inter cell handovers with unsuccessful reversions

I1: Unsuccessful outgoing intercell handovers with successful reversions

J1~J2: Unsuccessful outgoing intercell handovers with unsuccessful reversions

Figure 3-59 Unsuccessful outgoing internal inter cell handovers

LIV. Unsuccessful incoming interBSC inter cell handovers

Description: During the procedure of interBSC handover, the target BSC receives the HANDOVER REQUEST message from MSC, and then packs this message into IntoBSC Handover Request, which is then sent to the BM of the target cell to request for internal resource. And then BSC checks the conditions of incoming BSC handovers. If the conditions can be satisfied, BSC requests for channel resource and generates a HANDOVER COMMAND message. And then BSC activates the channel and waits for the access of MS to the new channel. On receiving the HANDOVER COMPLETE message from MS, the target BSC sends a HANDOVER COMPLETE message to MSC, and this handover is finished here. If abnormality takes place during this period, BSC will send a CLEAR REQUEST message or a HANDOVER FAILURE message to MSC to release the resource. This means this incoming BSC handover fails.

237


This item measures the times of interBSC handovers when the current cell is the target cell. Together with Attempted incoming interBSC inter cellhandovers , this item shows the performance of interBSC handover. Related items: Unsuccessful incoming internal inter cell handovers , Unsuccessfuloutgoing interBSC inter cell handovers .

Note:

The causes of incoming BSC handover can be:

1) Equipment failure;

2) Resource congestion or resource unavailable;

3) Message content invalid;

4) Timers time out;

5) Error have been detected during BSS internal processing, e.g. storing a message in buffer failed,

decoding failed;

6) MSC notifies BSC to clear resources.

Measurement point:1) During the procedure of interBSC handover, the target cell (current cell)

processes HANDOVER REQUEST. This item is measured if the following abnormalities occur, and in this case, the target cell will send a HANDOVER FAILURE message to MSC: service type is speech or data but no CIC contained or the contained CIC does not belong to the target BSC.

2) During the procedure of interBSC handover, the target cell (current cell) obtains the specified CIC contained in the HANDOVER REQUEST message. This item is measured when the following abnormalities occur, and in this case, the target cell will send a HANDOVER FAILURE message to MSC: the state of the specified CIC is busy or abnormal, dismatching between circuit pool and channel rate type or speech version.

3) During the procedure of interBSC handover, the target cell (current cell) sends a HANDOVER FAILURE message to MSC for AM/CM net-drive fails. This item is measured in this case.

4) During the procedure of interBSC handover, the target cell (current cell) will check the incoming BSC handover conditions. This item is measured when abnormalities are detected, and the target cell will at the same time send HANDOVER FAILURE to MSC. The abnormalities include: Service type is data but the channel rate type is unknown, requesting for channel failed, ciphering algorithm is not supported.

238


5) During the procedure of interBSC handover, the target cell (current cell) fails to send the CHANNEL ACTIVATION message. This item is measured in this case, and at the same time, the target cell sends a HANDOVER FAILURE message to MSC.

6) During the procedure of interBSC handover, the target cell (current cell) receives the CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE message. This item is measured in this case, and at the same time, the target cell will send a HANDOVER FAILURE message to MSC, as shown in Figure 3-60 A1.

7) During the procedure of interBSC handover, the target cell (current cell) receives CONNECTION FAILURE INDICATION from BTS after receiving HANDOVER DETECTION. This item is measured in this case, and at the same time, the target cell will send a HANDOVER FAILURE message to MSC, as shown in Figure 3-60 A2.

8) During the procedure of interBSC handover, the target cell (current cell) receives HANDOVER DETECTION or HANDOVER COMPLETE. This item is measured when the decoding of these messages failed, and in this case, the target cell will send a CLEAR REQUEST message to MSC.

9) During the procedure of interBSC handover, the target cell (current cell) sends a HANDOVER COMPLETE message to MSC. This item is measured when the target cell fails to send this message, and in this case, it will send a CLEAR REQUEST message to MSC.

10) During the procedure of interBSC handover, the target cell (current cell) starts timer waiting for CHANNEL ACTIVATION ACKNOWLEDGE. This item is measured when this timer times out, and in this case, the target cell will send a HANDOVER FAILURE message to MSC.

11) During the procedure of interBSC handover, the target cell (current cell) starts timer Tqho (maximum allowed queuing time for handover). This item is measured when the timer times out, and in this case, the target cell will send a HANDOVER FAILURE message to MSC.

12) During the procedure of interBSC handover, the target cell (current cell) starts timer waiting for the HANDOVER DETECTION message or timer waiting for the HANDOVER COMPLETE message. This item is measured when these timers time out, and in this case, the target cell will send a CLEAR REQUEST message to MSC.

13) During the procedure of interBSC handover, the target cell (current cell) receives the CLEAR COMMAND message from MSC. This item is measured in this case, as shown in Figure 3-60 A3~A5.

Formula: none.

239


MS BTS New BSC MSC/VLR

HANDOVER COMPLETE

HANDOVER COMMAND

HANDOVER COMPLETE

Old Channel

CONN FAIL IND

HANDOVER DETECTION

A1

New Channel

HANDOVER REQUEST

Old BSC

HANDOVER REQUIRED

CHAN ACT

CHAN ACT ACK

CHAN ACT NACK

New Channel

A2

CLEAR COMMAND

CLEAR COMMAND

CLEAR COMMANDA4

A5

A3

HANDOVER REQ ACK HANDOVER COMMAND

A1~A5 : Unsuccessful incoming interbsc inter cell handovers

Figure 3-60 Unsuccessful incoming interBSC inter cell handovers

LV. Unsuccessful outgoing interBSC inter cell handovers

Description: During the procedure of interBSC handover, the source cell sends a HANDOVER REQUIRED message to MSC to initiate a handover. After MS has been successfully handed over to the target cell, the source cell which receives the CLEAR COMMAND message from MSC, which means the handover has been successfully completed. If abnormality occurs during this period, the interBSC handover will be an unsuccessful one. This item measures the times of interBSC handover failures when the current cell is the source cell, i.e. interBSC outgoing handover failures. Together with, Attemptedoutgoing interBSC inter cell handovers , Successful outgoing interBSC intercell handovers , this item shows the performance of interBSC handover. Related items: Unsuccessful outgoing internal inter cell handovers , Unsuccessful incoming interBSC inter cell handovers , Unsuccessful outgoingBSC handovers with successful reversion , Unsuccessful outgoing BSChandovers with unsuccessful reversion .

Measurement point:1) During the procedure of interBSC handover, MS fails to access the target

cell and returns to the source cell (current cell). The source cell receives the HANDOVER FAILURE message (cause: Radio interface failure, reversion to old channel) from MS. This item is measured in this case, as shown in Figure 3-61 A1.

240


2) During the procedure of interBSC handover, the source cell (current cell) receives CONNECTION FAILURE INDICATION from BTS. This item is measured in this case, as shown in Figure 3-61 A2 and A3.

3) During the procedure of interBSC handover, the source cell (current cell) receives the ERROR INDICATION message (cause: timer T200 expired (N200+1) times" (0x01) or unsolicited DM response, multiple frame established state (0x05) or sequence error" (0x07)) from BTS. This item is measured in this case, as shown in Figure 3-61 A4 and A5.

4) During the procedure of interBSC handover, the source cell (current cell) receives the CLEAR COMMAND message (cause: not handover success) from MSC. This item is measured in this case, as shown in Figure 3-61 A6 and A7.

5) During the procedure of interBSC handover, the source cell (current cell) receives HANDOVER REQUIRED REJECT from MSC. This item is measured in this case, as shown in Figure 3-61 A8.

6) During the procedure of interBSC handover, the timer T7 (waiting for HANDOVER COMMAND) expired after the source cell (current cell) had resent HANDOVER REQUIRED for twice due to this timer expiry. This item is measured in this case.

7) During the procedure of interBSC handover, the timer T8 (waiting for the CLEAR COMMAND message (cause: handover success) from MSC) expired. This item is measured in this case.

241


BTS BSC1 MSC/VLR

HANDOVER REQUIRED

HANDOVER COMMAND

CLEAR COMMAND

CLEAR COMPLETE

HANDOVER FAILURE

CLEAR COMMAND

CONN FAIL IND

ERROR INDICATION

HANDOVER COMMAND

CLEAR COMMAND

CONN FAIL IND

ERROR INDICATION

A2 A6

A4 HANDOVER REQ REJ

A8

A1

A7

A3

A5

A1~A8: Unsuccessful incoming interBSC inter cell handovers


LVI. Unsuccessful internal inter cell handovers (channel mode unacceptable)

Description: After internal intercell handover is initiated, the source cell sends a HANDOVER COMMAND message to MS, and then enters the states of waiting for the Inter Clear Request message. After the access of MS to the new channel, the target cell sends Inter Clear Request to notify the source cell to clear the previous resources. This marks a successful internal intercell handover. If MS fails to access the target cell due to channel invalid (the mode or the type of the allocated channel not in line with what MS requests for), then this outgoing internal inter cell handover is a failure in the current cell. This item measures the times of unsuccessful outgoing internal inter cell handovers due to channel invalid when the current cell is the source cell. Together with Unsuccessful outgoing internal inter cell handovers , this item shows the situation of unsuccessful outgoing internal inter cell handovers due to channel invalid when the current cell is the source cell.

Measurement point: During the procedure of internal intercell handover, MS fails to access the target cell and returns to the source cell (current cell), and the source cell receives the HANDOVER FAILURE message (cause:

242


Abnormal release, channel unacceptable (0x02) or Channel mode unacceptable (0x09)) from MS. This item is measured in this case, as shown in Figure 3-59 B1.

Formula: none.

LVII. Unsuccessful internal inter cell handovers (timing advance out of range)

Description: After internal intercell handover is initiated, the source cell sends a HANDOVER COMMAND message to MS, and then enters the state of waiting for the Inter Clear Request message. After the access of MS to the new channel, the target cell sends Inter Clear Request to notify the source cell to clear the previous resources. This marks a successful internal intercell handover. If MS fails to access the target cell due to TA invalid (the value of TA out of normal range), then this outgoing internal inter cell handover is a failure. This item measures the times of unsuccessful outgoing internal inter cell handovers due to timing advance out of range when the current cell is the source cell. Together with Unsuccessful outgoing internal inter cellhandovers , this item shows the situation of unsuccessful outgoing internal inter cell handovers due to timing advance out of range when the current cell is the source cell.

Measurement point: During the procedure of internal intercell handover, MS fails to access the target cell and returns to the source cell (current cell), and the source cell receives the HANDOVER FAILURE message (cause: Handover impossible, timing advance out of range (0x08)) from MS. This item is measured in this case, as shown in Figure 3-59 C1.

Formula: none.

LVIII. Unsuccessful internal inter cell handovers (frequency not implemented)

Description: After internal intercell handover is initiated, the source cell sends a HANDOVER COMMAND message to MS, and then enters the state of waiting for the Inter Clear Request message. After the access of MS to the new channel, the target cell sends Inter Clear Request to notify the source cell to clear the previous resources. This marks a successful internal intercell handover. If MS fails to access the target cell due to frequency not implemented (the allocated ARFCN of frequency not supported by MS), then this outgoing internal inter cell handover is a failure. This item measures the times of unsuccessful outgoing internal inter cell handovers due to frequency not implemented when the current cell is the source cell. Together with Unsuccessful outgoing internal inter cell handovers , this item shows the

243


situation of unsuccessful outgoing internal inter cell handovers due to frequency not implemented when the current cell is the source cell.

Measurement point: During the procedure of internal intercell handover, MS fails to access the target cell and returns to the source cell (current cell), and the source cell receives the HANDOVER FAILURE message (cause: Frequency not implemented (0x0a)) from MS. This item is measured in this case, as shown in Figure 3-59 D1.

Formula: none.

LIX. Unsuccessful internal inter cell handovers (timer expired)

Description: After internal intercell handover is initiated, the source cell sends a HANDOVER COMMAND message to MS, and then enters the state of waiting for the Inter Clear Request message. After the access of MS to the new channel, the target cell sends Inter Clear Request to notify the source cell to clear the previous resources. This marks a successful internal intercell handover. If various timers expired during the process, then this outgoing internal inter cell handover is a failure. This item measures the times of unsuccessful outgoing internal inter cell handovers due to timer expired when the current cell is the source cell. Together with Unsuccessful outgoing internalinter cell handovers , this item shows the situation of unsuccessful outgoing internal inter cell handovers due to timer expired when the current cell is the source cell.

Measurement point:1) During the procedure of internal intercell handover, MS fails to access the

target cell and returns to the source cell (current cell), and the source cell receives the HANDOVER FAILURE message (cause: Abnormal release, timer expired (0x03)) from MS. This item is measured in this case, as shown in Figure 3-59 E1.

2) During the procedure of internal intercell handover, when the timer waiting for HANDOVER COMPLETE times out, the target cell sends Inter Clear Request to the source cell. This item is measured when the source cell (current cell) receives this message.

3) During the procedure of internal intercell handover, the source cell (current cell) waiting for Inter Clear Request times out. This item is measured in this case.

4) During the procedure of internal intercell handover, the source cell waiting for Intercell Handover Response times out again after resending Intercell Handover Request due to timeout. This item is measured in this case.

Formula: none.

244


LX. Unsuccessful internal inter cell handovers (other causes)

Description: After internal intercell handover is initiated, the source cell sends a HANDOVER COMMAND message to MS, and then enters the state of waiting for the Inter Clear Request message. After the access of MS to the new channel, the target cell sends Inter Clear Request to notify the source cell to clear the previous resources. This marks a successful internal intercell handover. There are many abnormalities during the process, such as abnormal channel preparation in the target cell, abnormal at radio link and internal processing abnormal, which caused this handover failure. As far as, the causes except for channel invalid, TA out of range, frequency not implemented and timer expired are all considered as other causes. This item measures the times of unsuccessful outgoing internal inter cell handovers due to other causes when the current cell is the source cell. Together with Unsuccessfuloutgoing internal inter cell handovers , this item shows the situation of unsuccessful outgoing internal inter cell handovers due to other causes when the current cell is the source cell.

Measurement point:1) During the procedure of internal intercell handover, MS fails to access the

target cell and returns to the source cell (current cell), and the source cell receives the HANDOVER FAILURE message (cause: other causes, including Abnormal release, unspecified (0x01), Preemptive release (0x05), Call already cleared (0x41), Semantically incorrect message (0x5f), Invalid mandatory information (0x60), Message type non - existent or not implemented (0x61), Message type not compatible with protocol state (0x62), Conditional IE error (0x64), No cell allocation available (0x65), Protocol error unspecified (0x6f), etc.) from MS. This item is measured in this case, as shown in Figure 3-59 F1.

2) During the procedure of internal intercell handover, the source cell (current cell) receives CONNECTION FAILURE INDICATION from BTS. This item is measured in this case, as shown in Figure 3-59 F2 and F3.

3) During the procedure of internal intercell handover, the source cell (current cell) receives the ERROR INDICATION message (cause: timer T200 expired (N200 + 1) times (0x01) or unsolicited DM response, multiple frame established state (0x05) or sequence error (0x07)) from BTS. This item is measured in this case, as shown in Figure 3-59 F4 and F5.

4) During the procedure of internal intercell handover, the source cell (current cell) receives the CLEAR COMMAND message from MSC. This item is measured in this case, as shown in Figure 3-59 F6 and F7.

5) During the procedure of internal intercell handover, the target cell sends Intercell Handover Reject to the source cell when it fails to prepare or activate the channels (e.g. channel allocation failure, CHANNEL

245


ACTIVATION NEGATIVE ACKNOWLEDGE received, expiry of timer waiting for CHANNEL ACTIVATION ACKNOWLEDGE). This item is measured when the source cell (current cell) receives this message.

6) During the procedure of internal intercell handover, when AM/CM net-drive fails, the target cell sends Inter Clear Request to the source cell. This item is measured when the source cell (current cell) receives this message.

Formula: none.

LXI. Unsuccessful internal inter cell handovers with successful reversions

Description: During the procedure of internal intercell handover, the source cell sends a HANDOVER COMMAND message to MS. If the MS cannot access the target cell due to poor radio environment or handover parameter incorrect, it will send a HANDOVER FAILURE message (cause: Radio interface failure, reversion to old channel) to the source cell via the previous channel. The source cell then informs the target cell to clear the resources related to this handover. The connecting between the source cell and MS remains the same. This item measures the times of unsuccessful handover with successful reversion when the current cell is the source cell in a handover. Related items: Unsuccessful outgoing internal inter cell handovers , Unsuccessful internalinter cell handovers with unsuccessful reversions , Unsuccessful intracellhandovers with successful reversions , Unsuccessful outgoing BSC handoverswith successful reversion .

Measurement point: This item is measured when the source cell (current cell), receives the HANDOVER FAILURE message (cause: Radio interface failure, reversion to old channel) from MS during the procedure of internal intercell handover, as shown in Figure 3-59 G1.

Formula: none.

LXII. Unsuccessful internal inter cell handovers with unsuccessful reversions

Description: During the procedure of internal intercell handover, after the source cell sends a HANDOVER COMMAND message to MS, the connection between MS and the source cell is terminated before the connection between MS and the target cell set up due to poor radio environment or equipment failure. When BSC detects this situation, it will send a CLEAR REQUEST message to MSC to clear the previous resources and the involved resources during handover. This handover failed and the original service cannot be restored. This item measures the times of unsuccessful handover with unsuccessful reversion when the current cell is the source cell in a handover. Related items: Unsuccessful outgoing internal inter cell handovers , Unsuccessful internal inter cell handovers with successful reversions ,

246


Unsuccessful intracell handovers with unsuccessful reversions , Unsuccessfuloutgoing BSC handovers with unsuccessful reversion .

Measurement:1) This item is measured when the source cell (current cell) receives

CONNECTION FAILURE INDICATION during the procedure of internal intercell handover, as shown in Figure 3-59 H1.

2) During the procedure of internal intercell handover, the source cell (current cell) receives the ERROR INDICATION message (cause: timer T200 expired (N200 + 1) times (0x01) or unsolicited DM response, multiple frame established state (0x05) or sequence error (0x07)) from BTS. This item is measured in this case, as shown in Figure 3-59 H2.

3) During the procedure of internal intercell handover, when AM/CM net-drive fails, the target cell sends Inter Clear Request to the source cell. This item is measured when the source cell (current cell) receives this message.

4) This item is measured when the source cell (current cell) waiting for Inter Clear Request times out after sending the HANDOVER COMMAND message to MS during the procedure of internal intercell handover.

Formula: none.

LXIII. Attempted inter cell handovers

Description: This item measures the times of attempted inter cell handovers in the current cell, including incoming internal inter cell handover, incoming interBSC inter cell handover, outgoing internal inter cell handover and outgoing interBSC inter cell handover. Related items:Attempted incoming internal intercell handovers , Attempted incoming interBSC inter cell handovers , Attempted outgoing internal inter cell handovers , Attempted outgoinginterBSC inter cell handovers.

Measurement point: none. Formula: Attempted incoming internal inter cell handovers+ Attempted

incoming interBSC inter cell handovers + Attempted outgoing internal inter cell handovers + Attempted outgoing interBSC inter cell handovers

LXIV. Successful inter cell handovers

Description: This item measures the times of successful inter cell handovers in the current cell, including incoming internal inter cell handover, incoming interBSC inter cell handover, outgoing internal inter cell handover, outgoing interBSC inter cell handover. Related items: Successful incoming internal intercell handovers , Successful incoming interBSC inter cell handovers , Successful outgoing internal inter cell handovers , Successful outgoinginterBSC inter cell handovers.

Measurement point: none.

247


Formula: Successful incoming internal inter cell handovers + Successful incoming interBSC inter cell handovers + Successful outgoing internal inter cell handovers + Successful outgoing interBSC inter cell handovers

LXV. Inter cell handover success rate (%)

Description: This item measures the success rate of the inter cell handovers in the current cell, including incoming internal inter cell handover, incoming interBSC inter cell handover, outgoing interBSC inter cell handover and outgoing interBSC inter cell handover. Related items: Successful incominginternal inter cell handovers , Successful incoming interBSC inter cellhandovers , Successful outgoing internal inter cell handovers , Successfuloutgoing interBSC inter cell handovers , Attempted incoming internal inter cellhandovers , Attempted incoming interBSC inter cell handovers , Attemptedoutgoing internal inter cell handovers , Attempted outgoing interBSC inter cellhandovers .

Measurement point: none. Formula: (Successful incoming internal inter cell handovers + Successful

incoming interBSC inter cell handovers + Successful outgoing internal inter cell handovers + Successful outgoing interBSC inter cell handovers) / (Attempted incoming internal inter cell handovers+ Attempted incoming interBSC inter cell handovers + Attempted outgoing internal inter cell handovers + Attempted outgoing interBSC inter cell handovers)

LXVI. Inter cell radio handover success rate(%)

Description: This item measures the success rate of inter cell radio handover in the current cell, including incoming internal inter cell handover, incoming interBSC inter cell handover, outgoing interBSC inter cell handover and outgoing interBSC inter cell handover. Related items: Successful incominginternal inter cell handovers , Successful incoming interBSC inter cellhandovers , Successful outgoing internal inter cell handovers , Successfuloutgoing interBSC inter cell handovers , Incoming internal inter cellhandovers , Inter BSC incoming cell handovers , Outgoing internal inter cellhandovers , Inter BSC outgoing cell handovers .

Measurement point: none. Formula: (Successful incoming internal inter cell handovers + Successful

incoming interBSC inter cell handovers + Successful outgoing internal inter cell handovers + Successful outgoing interBSC inter cell handovers) / (Incoming internal inter cell handovers + Inter BSC incoming cell handovers + Outgoing internal inter cell handovers + Inter BSC outgoing cell handovers).

248


LXVII. Dual-band inter cell handover success rate (%)

Description: This item measures the success rate of dual-band inter cell handover in the current cell, including incoming internal inter cell handover, incoming interBSC inter cell handover, outgoing interBSC inter cell handover and outgoing interBSC inter cell handover. Related items: Successful dual-band intercell handovers , Attempted dual-band intercell handovers .

Measurement point: none. Formula: Successful dual-band intercell handovers / Attempted dual-band

intercell handovers

3.9.5 Intra-cell Handover Measurement Function

The items of intra-cell handover measurement function are shown in Table 3-1 .

Table 3-1 Statistic items in intra-cell handover measurement function

No. Item name

1Attempted intracell handovers

2Successful intracell handovers

3Attempted intracell handovers for uplink quality

4Attempted intracell handovers for downlink quality

5Attempted intracell handovers for other causes

6Unsuccessful intracell handovers

7Unsuccessful intracell handovers (channel mode unacceptable)

8Unsuccessful intracell handovers (frequency not implemented)

9Unsuccessful intracell handovers (timer expired)

10Unsuccessful intracell handovers (other causes)

11Unsuccessful intracell handovers with successful reversions

12Unsuccessful intracell handovers with unsuccessful reversions

13Intracell handover success rate (%)

I. Attempted intracell handovers

Description: Intracell handover is normally triggered by receiving strength, receiving quality, O&M intervention, and IUO handover. Its source cell and target cell are the same one. This item measures the number of intracell handover attempts initiated by the current cell. The measurement result of this item can be used to observe the frequency of the intracell handover initiated by the current cell. Together with Successful intracell handovers, Unsuccessfulintracell handovers , this item reflects the performance of intracell handover of

249


the current cell. Related items: Attempted outgoing internal inter cellhandovers , Attempted outgoing interBSC inter cell handovers .

250


Note:

In intraBSC handover, an idle adjacent cell (if the adjacent and the source cell are in different BMs of

the same BSC, the adjacent cell will be treated as an idle cell because system can’t get the using



is the first one in the handover candidate list, even if it is congested. If the selected adjacent cell and

the source cell are the same one, this item will be measured. But IUO handover (a special type of

intracell handover from underlaid to overlaid subscell or from overlaid to underlaid subcell of an IUO

cell) is an exception. When the target subcell is congested, handover cannot be initiated, and the

measurement will not be carried out.

Measurement point: After handover algorithm decision, the source cell (current cell) sends an Intercell Handover Request message to the target cell. This item is measured if the source cell is the same as the target cell in this case.

Formula: none.

II. Successful intracell handovers

Description: Intracell handover is normally triggered by receiving strength, receiving quality, O&M intervention, and IUO handover. If BSC receives Handover Complete, which indicates the MS has been successfully handed over to the target cell. BSC then sends Handover Performed to MSC to notify the success of this handover. This item measures the times of successful intracell handovers in the current cell. This item, together with Attemptedintracell handovers and Unsuccessful intracell handovers helps the user know the performance of intracell handover in the current cell. Related items: Successful incoming internal inter cell handovers , Successful incominginterBSC inter cell handovers, Successful outgoing internal inter cellhandovers , Successful outgoing interBSC inter cell handovers .

Measurement: Measured when the target cell (current cell) sends Handover Performed to MSC after the MS has been successfully handed over to target cell in the intracell handover, as shown in Figure 3-55 A1.

Formula: none.

III. Attempted intracell handovers for uplink quality

Description: When BSC initiates a handover, it will receive Handover Indication from LAPD module. This message contains the cause value of the handover. The times of handover attempts for all kinds of handover causes can be measured according to the cause in this message. This item measures the times of attempted intracell handovers caused by uplink signal quality in the

251


current cell. This item shows the frequency of intracell handover caused by uplink signal quality in the current cell. Related items: Attempted intracellhandovers , Attempted handovers for uplink quality .

Measurement point: After handover algorithm decision, the source cell (current cell) sends an Intercell Handover Request message (internal intracell handover) due to uplink signal quality. This item is measured if the source and target cells are the same one in this case.

Formula: none.

IV. Attempted intracell handovers for downlink quality

Description: When BSC initiates a handover, it will receive Handover Indication from LAPD module. This message contains the cause value of the handover. The times of handover attempts for all kinds of handover causes can be measured according to the cause in this message. This item measures the times of attempted intracell handovers caused by downlink signal quality in the current cell. This item shows the frequency of intracell handover caused by downlink signal quality in the current cell. Related items: Attempted intracellhandovers , Attempted handovers for downlink quality .

Measurement point: After handover algorithm decision, the source cell (current cell) sends an Intercell Handover Request message (internal intracell handover) due to downlink signal quality. This item is measured if the source and target cells are the same one in this case.

Formula: none.

V. Attempted intracell handovers for other causes

Description: When BSC initiates a handover, it will receive Handover Indication from LAPD module. This message contains the cause value of the handover. The times of handover attempts for all kinds of handover causes can be measured according to the cause in this message. This item measures the times of attempted intracell handovers caused by other causes (e.g. signal strength, O&M intervention) in the current cell. This item shows the frequency of intracell handover caused by other causes in the current cell. Related items: Attempted intracell handovers , Attempted handovers for other causes .

Measurement point: After handover algorithm decision, the source cell (current cell) sends an Intercell Handover Request message (internal intracell handover) due to other causes (e.g. signal strength, O&M intervention). This item is measured if the source and target cells are the same one in this case.

Formula: none.

252


VI. Unsuccessful intracell handovers

Description: After an intracell handover has been initiated, the source cell enters the state of waiting for Intercell Handover Response. After the target cell has allocated channel, activated new channel, and sent Intercell Handover Response to inform the source cell about it. After the source cell sends Handover Command to MS, it enters the state of waiting for the Inter Clear Request message. After the MS has been successfully accessed the new channel, the target cell will send Inter Clear Request to inform the source cell to release the previous channel and this intracell handover is finished successfully. During this period, any abnormality will cause failure of handover. This item measures the times of the unsuccessful intracell handovers in the current cell. This item, together with Attempted intracell handovers , Successful intracell handovers helps the user know the performance of intracell handover in the current cell. Related items: Unsuccessful outgoinginternal inter cell handovers , Unsuccessful incoming internal inter cellhandovers , Unsuccessful outgoing interBSC inter cell handovers .

Note:

Below are the causes of unsuccessful intracell handover:

1) Previous channel becomes invalid or connection is terminated due to abnormality of radio resource

or terrestrial resource;

2) MS fails to access the target channel due to poor radio environment or incorrect handover

parameter;

3) Handover is interrupted and original call is cleared because errors have been detected during BSS



Measurement point:1) Measured when the source cell (current cell) receives CONNECTION

FAILURE INDICATION during the procedure of intracell handover, as shown in Figure 3-1 A1 and A2.

2) During the procedure of intracell handover, MS fails to access the target cell, then returns to the source cell (current cell) and sends HANDOVER FAILURE to source cell. This item is measured when the source cell receives this message, and at the same time, a Clear For Handover Failure message is sent to the target cell, as shown in Figure 3-1 A3.

3) During the procedure of intracell handover, the source cell (current cell) receives the ERROR INDICATION message (cause: timer T200 expired

253


(N200 + 1) times (0x01) or unsolicited DM response, multiple frame established state (0x05) or sequence error (0x07)) from BTS. This item is measured in this case, as shown in Figure 3-1 A4 and A5.

4) During the procedure of intracell handover, the source cell (current cell) receives the CLEAR COMMAND message from MSC. This item is measured in this case, as shown in Figure 3-1 A6 and A7.

5) During the procedure of intracell handover, after the target cell receives HANDOVER DETECTION, it will send Inter Clear Request to the source cell for AM/CM net-drive fails or the timer waiting for HANDOVER COMPLETE times out. This item is measured when the source cell receives (current cell) this message.

6) During the procedure of intracell handover, the target cell sends Intercell Handover Reject to the source cell when it fails to prepare or activate the channels (e.g. channel allocation failure, CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE received, expiry of timer waiting for CHANNEL ACTIVATION ACKNOWLEDGE). This item is measured when the source cell (current cell) receives this message.

7) During the procedure of intracell handover, when the source cell (current cell) waiting for Inter Clear Request times out, it sends Inter Clear Request to the target cell. This item is measured in this case.

8) During the procedure of intracell handover, the source cell (current cell) waiting for Intercell Handover Response times out again after resending Intercell Handover Request due to timeout. This item is measured in this case, and the related resources will be released at the same time.

Formula: none.

MS BTS BSC MSC/VLR

HANDOVER COMPLETE

HANDOVER COMMAND

HANDOVER PERFORMED

CONN FAIL IND

New Channel

ERROR IND

Old Channel

CHANNEL ACT

A1

CONN FAIL INDA2, G1

A4

ERROR INDA5, G2

HANDOVER FAILURE

A3, B1, C1, D1, E1, F1

CLEAR COMMAND

A6, E6

CLEAR COMMANDA7Old Channel

A1~A7: Unsuccessful intracell handovers

254


B1: Unsuccessful intracell handovers (channel invalid)

C1: Unsuccessful intracell handovers (TA invalid)

D1: Unsuccessful intracell handovers (timer expired)

E1: Unsuccessful intracell handovers (other causes)

F1: Unsuccessful intracell handovers with successful reversions

G1~G2: Unsuccessful intracell handovers with unsuccessful reversions

Figure 3-1 Unsuccessful intracell handovers

VII. Unsuccessful intracell handovers (channel mode unacceptable)

Description: After intracell handover is initiated, the source cell sends a HANDOVER COMMAND message to MS, and then enters the state of waiting for the Inter Clear Request message. After the access of MS to the new channel, the target cell sends Inter Clear Request to notify the source cell to clear the previous resources. This marks a successful internal intracell handover. If MS fails to access the target cell due to channel invalid (the mode or the type of the allocated channel not in line with what MS requests for), then this intracell handover is a failure. This item measures the times of unsuccessful intracell handovers due to channel invalid in the current cell. Together with Unsuccessful intracell handovers, this item shows the situation of unsuccessful intracell handover caused by channel invalid in the current cell.

Measurement point: During the procedure of internal intracell handover, MS fails to access the target cell and returns to the source cell (current cell), and the source cell receives the HANDOVER FAILURE message (cause: Abnormal release, channel unacceptable (0x02) or Channel mode unacceptable (0x09)) from MS. This item is measured in this case, as shown in Figure 3-1 B1.

Formula: none.

VIII. Unsuccessful intracell handovers (frequency not implemented)

Description: After intracell handover is initiated, the source cell sends a HANDOVER COMMAND message to MS, and then enters the state of waiting for the Inter Clear Request message. After the access of MS to the new channel, the target cell sends Inter Clear Request to notify the source cell to clear the previous resources. This marks a successful internal intracell handover. If MS fails to access the target cell due to frequency not implemented, then this intracell handover is a failure. This item measures the times of unsuccessful intracell handovers due to frequency not implemented in the current cell. Together with Unsuccessful intracell handovers , this item shows the situation of unsuccessful intracell handover caused by frequency not implemented in the current cell.

255


Measurement point: During the procedure of internal intracell handover, MS fails to access the target cell and returns to the source cell (current cell), and the source cell receives the HANDOVER FAILURE message (cause: Frequency not implemented (0x0a)) from MS. This item is measured in this case, as shown in Figure 3-1 C1.

Formula: none.

IX. Unsuccessful intracell handovers (timer expired)

Description: After intracell handover is initiated, the source cell sends a HANDOVER COMMAND message to MS, and then enters the state of waiting for the Inter Clear Request message. After the access of MS to the new channel, the target cell sends Inter Clear Request to notify the source cell to clear the previous resources. This marks a successful internal intracell handover. If various timers expired during the process, then this intracell handover is a failure. This item measures the times of unsuccessful intracell handovers due to timer expired in the current cell. Together with Unsuccessfulintracell handovers , this item shows the situation of unsuccessful intracell handover caused by timer expired.

Measurement point:1) During the procedure of intracell handover, MS fails to access the target

cell and returns to the source cell (current cell), and the source cell receives the HANDOVER FAILURE message (cause: Abnormal release, timer expired (0x03)) from MS. This item is measured in this case, as shown in Figure 3-1 D1.

2) During the procedure of intracell handover, after the target cell receives HANDOVER DETECTION, it will send Inter Clear Request to the source cell for the timer waiting for HANDOVER COMPLETE times out. This item is measured when the source cell (current cell) receives this message.

3) During the procedure of intracell handover, the source cell (current cell) waiting for Inter Clear Request times out. This item is measured in this case.

4) During the procedure of intracell handover, the source cell waiting for Intercell Handover Response times out again after resending Intercell Handover Request due to timeout. This item is measured in this case.

Formula: none.

X. Unsuccessful intracell handovers (other causes)

Description: After intracell handover is initiated, the source cell sends a HANDOVER COMMAND message to MS, and then enters the state of waiting for the Inter Clear Request message. After the access of MS to the new channel, the target cell sends Inter Clear Request to notify the source cell to

256


clear the previous resources. This marks a successful internal intracell handover. There are many abnormalities during the process, such as abnormal channel preparation in the target cell, abnormal at radio link, which caused this handover failure, are considered as other causes. This item measures the times of unsuccessful intracell handovers due to other causes in the current cell. Together with Unsuccessful intracell handovers , this item shows the situation of unsuccessful intracell handover caused by other causes.

Measurement point:1) During the procedure of intracell handover, MS fails to access the target

cell and returns to the source cell (current cell), and the source cell receives the HANDOVER FAILURE message (cause: other causes, including Abnormal release, unspecified (0x01), Preemptive release (0x05), Call already cleared (0x41), Semantically incorrect message (0x5f), Invalid mandatory information (0x60), Message type non-existent or not implemented (0x61), Message type not compatible with protocol state (0x62), Conditional IE error (0x64), No cell allocation available (0x65), Protocol error unspecified (0x6f), etc.) from MS. This item is measured in this case, as shown in Figure 3-1 E1.

2) During the procedure of intracell handover, the target cell sends Intercell Handover Reject to the source cell when it fails to prepare or activate the channels (e.g. channel allocation failure, CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE received, expiry of timer waiting for CHANNEL ACTIVATION ACKNOWLEDGE). This item is measured when the source cell (current cell) receives this message.

3) Measured when the source cell (current cell) receives CONNECTION FAILURE INDICATION during the procedure of intracell handover.

4) During the procedure of intracell handover, the source cell (current cell) receives the ERROR INDICATION message (cause: timer T200 expired (N200 + 1) times (0x01) or unsolicited DM response, multiple frame established state (0x05) or sequence error (0x07)) from BTS. This item is measured in this case.

5) During the procedure of intracell handover, the source cell (current cell) receives the CLEAR COMMAND message from MSC. This item is measured in this case.

6) During the procedure of intracell handover, when AM/CM net-drive fails after the target cell receives HANDOVER DETECTION, the target cell sends Inter Clear Request to the source cell. This item is measured when the source cell (current cell) receives this message

Formula: none.

257


XI. Unsuccessful intracell handovers with successful reversions

Description: During the procedure of intracell handover, the source cell sends a HANDOVER COMMAND message to MS. If the MS cannot access the target cell due to poor radio environment or handover parameter incorrect, it will send a HANDOVER FAILURE message (cause: Radio interface failure, reversion to old channel) to the source cell via the previous channel. On reception of this message, the source cell notifies the target cell to clear the resources related to this handover. The connecting between the source cell and MS remains the same. This item measures the times of unsuccessful intracell handover with successful reversion in the current cell. Related items: Unsuccessful intracell handovers , Unsuccessful intracell handovers withunsuccessful reversions , Unsuccessful internal inter cell handovers withsuccessful reversions , Unsuccessful outgoing BSC handovers with successfulreversion .

Measurement point: This item is measured when the source cell (current cell) receives the HANDOVER FAILURE message (cause: Radio interface failure, reversion to old channel) from MS during the procedure of intracell handover, as shown in Figure 3-1 F1.

Formula: none.

XII. Unsuccessful intracell handovers with unsuccessful reversions

Description: During the procedure of intracell handover, after the source BSC sends a HANDOVER COMMAND message to MS, the connection between MS and the source cell is terminated before the connection between MS and the target cell due to poor radio environment or equipment failure. When BSC detects this situation, it will send a CLEAR REQUEST message to MSC to request for clearing the previous resources and the resources during handover. This handover is failed and the original service cannot be restored. This item measures the times of unsuccessful handover with unsuccessful reversion in the current cell. Related items: Unsuccessful intracell handovers , Unsuccessful intracell handovers with successful reversions , Unsuccessfulinternal inter cell handovers with unsuccessful reversions , Unsuccessfuloutgoing BSC handovers with unsuccessful reversion .

Measurement point:1) This item is measured when the source cell (current cell) receives

CONNECTION FAILURE INDICATION from BTS after sending the HANDOVER COMMAND message to MS during the procedure of intracell handover, as shown in Figure 3-1 G1.

2) During the procedure of intracell handover, the source cell (current cell) receives the ERROR INDICATION message (cause: timer T200 expired (N200 + 1) times (0x01) or unsolicited DM response, multiple frame

258


established state (0x05) or sequence error (0x07)) from BTS. This item is measured in this case, as shown in Figure 3-1 G 2.

3) During the procedure of intracell handover, after the target cell receives HANDOVER DETECTION, it will send Inter Clear Request to the source cell for AM/CM net-drive fails or the timer waiting for HANDOVER COMPLETE times out. This item is measured when the source cell (current cell) receives this message.

4) This item is measured when the source cell (current cell) waiting for the Inter Clear Request message (cause: handover success) times out after sending the HANDOVER COMMAND message to MS during the procedure of intracell handover.

Formula: none.

XIII. Intracell handover success rate (%)

Description: See Successful intracell handovers , Attempted intracellhandovers .

Measurement point: none. Formula: Successful intracell handovers / Attempted intracell handovers

3.1.2 Other Measurement Function


Table 3-1 Statistic items in other measurement function

No. Item name

1Sum of TCH measurement reports in 1800 cell (excluding very early assignment)

2 Sum of TCH measurement reports in the cell (excluding very early assignment)

3Sum of SDCCH measurement reports in the cell

4Sum of configured TRX in the cell

5Sum of available TRX in the cell

6Sum of TCH measurement reports during very early assignment procedure in the cell

7Sum of TCH measurement reports during very early assignment procedure in the 1800 cell

8 Unusable time of the cell (second)

9Initially configured static PDCHs of 900 cell

10Initially configured static PDCHs of 1800 cell

11Average available PDCHs

12 Attempted handovers in the extended cell (minimum timing advance)

13 Attempted dual-band intercell handovers

14Successful dual-band intercell handovers

15Inter BSC incoming cell handovers

16Inter BSC outgoing cell handovers

259


17SDCCHs initially configured

18Initially configured TCHs of 900 cell

19Initially configured TCHs of 1800 cell

20Initially configured dynamic PDCHs of 900 cell

21Initially configured dynamic PDCHs of 1800 cell

22Unsuccessful outgoing BSC handovers with successful reversion

23Unsuccessful outgoing BSC handovers with unsuccessful reversion

24 Average available TCHs from Dyn-PDTCH

25 Average available PDCHs from Dyn-PDTCH

26Percentage of TRX in good condition (%)

27Ratio of cell usability (%)

I. Sum of TCH measurement reports in 1800 cell (excluding very early assignment)

Description: MS shall report a MR to the network every 480ms after it seizes TCH. This item reflects the number of original MRs received from MS on all the TCHs (speech/data) of a 1800 cell in BSC, and is irrelated to the state of the MR pre-processing switch. This item is used to calculate the traffic volume on TCH which serves as a speech/data channel.

Measurement point: This item shall be measured when BSC receives a MR which is reported by BTS on TCH, and the TCH serves as a speech/data channel instead of signaling channel.

Formula: none.

II. Sum of TCH measurement reports in the cell (excluding very early assignment)

Description: MS shall report a MR to the network every 480ms after it seizes TCH. This item reflects the number of original MRs received from MS on all the TCHs (speech/data) of a cell (900 cell or 1800 cell) in BSC, and is irrelated to the state of the MR pre-processing switch. This item is used to calculate the traffic volume on TCH which serves as a speech/data channel.

Measurement point: This item shall be measured when BSC receives a MR which is reported by BTS on TCH, and the TCH serves as a speech/data channel instead of signaling channel.

Formula: none.

III. Sum of SDCCH measurement reports in the cell

Description: MS shall report a MR to the network every 470ms after it seizes SDCCH. This item reflects the number of original MRs received from MS on all

260


the SDCCHs of a cell in BSC, and is irrelated to the state of the MR pre-processing switch. This item is used to calculate the traffic volume on SDCCH.

Measurement point: This item is measured when BSC receives a MR which is reported by BTS on SDCCH.

Formula: none.

IV. Sum of configured TRX in the cell

Description: This item reflects the number of TRXs installed in a cell in BSC. If the state of a cell is "Not installed", the measurement result of this item is "0".

Measurement point: This item is measured at the end of a statistic cycle. Formula: none.

V. Sum of available TRX in the cell

Description: This item reflects the number of available TRXs in a cell in BSC. Here, "available" means that the state of TRX is "Enabled" and RSL state is "Normal".

Measurement point: This item is measured at the end of a statistic cycle. Formula: none.

VI. Sum of TCH measurement reports during very early assignment procedure in the cell

Description: MS shall report a MR to the network every 480ms after it seizes TCH. This item reflects the number of original MRs received from MS on all the TCHs (signaling) of a cell (900 cell or 1800 cell) in BSC, and is irrelated to the state of the MR pre-processing switch. This item is used to calculate the traffic volume on TCH which serves as a signaling channel.

Measurement point: This item shall be measured when BSC receives a MR which is reported by BTS on TCH, and the TCH serves as a signaling channel, instead of speech/data channel.

Formula: none.

VII. Sum of TCH measurement reports during very early assignment procedure in the 1800 cell

Description: MS shall report a MR to the network every 480ms after it seizes TCH. This item reflects the number of original MRs received from MS on all the TCHs (signaling) of a 1800 cell in BSC, and is irrelated to the state of the MR pre-processing switch. This item is used to calculate the traffic volume on TCH which serves as a signaling channel.

Measurement point: This item shall be measured when BSC receives a MR which is reported by BTS on TCH, and the TCH serves as a signaling channel instead of speech/data channel.

261


Formula: none.

VIII. Unusable time of the cell (second)

Description: Here, "unusable" means that the operational state of the current primary BCCH of a cell is "Disabled", or the RSL of the TRX where the current primary BCCH of a cell is located is broken down. So long as either of the two conditions is satisfied, the cell shall be regarded as "unusable". This item reflects the out-of-service duration of a cell resulted from various causes.

Measurement point: The system checks cell state every 5s. This item is measured when the system detects that a cell has exited "Service" state. There may exist a +5s/-5s deviation.

Formula: none.

IX. Initially configured static PDCHs of 900 cell

Description: This item provides the number of static PDCHs of a 900 cell in BSC at the start time of a measurement period according to the data configuration table

Measurement point: This item is measured at the start time of a measurement period.

Formula: None.

X. Initially configured static PDCHs of 1800 cell

Description: This item provides the number of static PDCHs of a 1800 cell in BSC at the start time of a measurement period according to the data configuration table

Measurement point: This item is measured at the start time of a measurement period.

Formula: None.

XI. Average available PDCHs

Description: This item provides the average number of available PDCHs in a cell within a measurement period. The cells here include those whose configuration status is "static PDCH" or "dynamic PDCH" and operation status is "PDCH" (i.e. the related channels are currently seized by packet service). The channel status can be either idle or seized, but it should be an available channel. This item is measured under sampling mechanism. BSC checks the number of dynamic PDCHs recorded in the database every five senconds. This number is accumulated within measurement period. At the end of measurement period, this accumulated number is divided with the times of accumulating (times of sampling) to get the value of this item. Therefore, this item may not be an integer.

262


Measurement point: At the end of each measurement period, the average available PDCHs will be calculated and sent to BAM.

Formula: None.

XII. Attempted handovers in the extended cell (minimum timing advance)

Description: When BSC initiates a handover, it will receive Handover Indication from LAPD module. This message contains the cause value of handover. The times of handover attempts for all kinds of handover causes can be measured according to the cause in this message. This item measures the times of handovers (intracell handovers) caused by minimum timing advance (occurs only in single timeslot extended cells) in the current cell. This item shows the frequency of handover caused by minimum timing advance in the current cell. Relate items: Attempted intracell handovers .

Measurement point: In single timeslot extended cells (current cell), handovers can be triggered by TA being smaller than minimum timing advance. After handover algorithm decision, the current cell sends Intercell Handover Request (internal intracell handover). This item is measured in this case.

Formula: none.

XIII. Attempted dual-band intercell handovers

Description: Dual-band handover refers to the handover from GSM900 cell to GSM1800 cell or from GSM 1800 cell to GSM 900 cell. The cell system type of the source cell and the target cell should be the different. This type of handovers includes intraBSC handover and interBSC handover. This item measures the times of the current cell taking place dual-band intercell handovers. If the current cell is a GSM 900 cell, the item measures the handovers which are from other GSM 1800 cells to the current cell or from the current cell to other GSM1800 cells. If the current cell is a GSM 1800 cell, the item measures the handovers which are from other GSM900 cells to the current cell or from the current cell to other GSM900 cells. This item shows the frequency of the dual-band intercell handovers taking place in the current cell. Together with Successful dual-band intercell handovers , this item shows the performance of this type of handover. Related items:Attempted incominginternal inter cell handovers , Attempted incoming interBSC inter cellhandovers , Attempted outgoing internal inter cell handovers , Attemptedoutgoing interBSC inter cell handovers .

263


Note:

1) For outgoing interBSC inter cell handover, after initiating a handover by sending a HANDOVER

REQUIRED message to MSC, the source cell does not know the target cell until the reception of a

HANDOVER COMMAND message from MSC.



from 1 to 124.


is from 512 to 885.


cell) sends an Intercell Handover Request message, and the cell system type of the target cell and the source cell are different. This item is measured in this case.

2) During the procedure of internal intercell handover, the target cell (current cell) receives Intercell Handover Request, and the cell system type of the target cell and the source cell are different. This item is measured in this case.

3) During the procedure of interBSC handover, the source cell (current cell) receives the HANDOVER COMMAND message from MSC, and the cell system type of the target cell and the source cell are different. This item is measured in this case, as shown in Figure 3-53 E1.

4) During the procedure of interBSC handover, the target cell (current cell) receives IntoBSC Handover Request, and the cell system type of the target cell and the source cell are different. This item is measured in this case.

Formula: none.

XIV. Successful dual-band intercell handovers

Description: Dual-band handover refers to the handover from GSM900 cell to GSM1800 cell or from GSM 1800 cell to GSM 900 cell. The cell system type of the source cell and the target cell should be different. This type of handovers includes intraBSC handover and interBSC handover. This item shows the times of successful dual-band intercell handovers taking place in the current cell. Together with Attempted dual-band intercell handovers , this item shows the performance of this type of handover. Related items: Successful incominginternal inter cell handovers , Successful incoming interBSC inter cellhandovers , Successful outgoing internal inter cell handovers , Successfuloutgoing interBSC inter cell handovers .

264


Note:

1) For outgoing interBSC inter cell handover, after initiating a handover by sending a HANDOVER


HANDOVER COMMAND message from MSC.



from 1 to 124.


is from 512 to 885.


cell) receives Inter Clear Request (cause: internal intercell handover succeeded) from the target cell. This item is measured in this case.

2) During the procedure of internal intercell handover (cause: directed retry), after MS is successfully handed over to the target cell (current cell), the target cell will send ASSIGNMENT COMPLETE to MSC. This item is measured when the current cell sends this message, as shown in Figure3-54 D1.

3) During the procedure of internal intercell handover (cause: not directed retry, such as receiving strength, receiving quality, TA, traffic load, Response to MSC invocation, directed retry, rapid rxlevel drop, better cell or O&M intervention), after MS is successfully handed over to the target cell (current cell), the target cell sends a HANDOVER PERFORMED message to MSC. This item is measured in this case Figure 3-55 E1.

4) During the procedure of interBSC handover, the source cell (current cell) receives the CLEAR COMMAND message (cause: handover success) from MSC. This item is measured in this case, as shown in Figure 3-57 D1.

5) During the procedure of interBSC handover, the target cell (current cell) receives HANDOVER COMPLETE from MS and sends it to MSC at the same time. This item is measured in this case, as shown in Figure 3-56 B1.

Formula: none.

XV. Inter BSC incoming cell handovers

Description: After the target BSC receives the HANDOVER REQUEST message from MSC, it checks the conditions of incoming handover. If the

265


check passed, the target BSC will request for channel resource, generate and store the HANDOVER COMMAND message in buffer, and at the same time, it will send a CHANNEL ACTIVATION to BTS message. After receiving the CHANNEL ACTIVATION ACKNOWLEDGE message, BSC packs the HANDOVER COMMAND message into the HANDOVER REQUEST ACKNOWLEDGE message, which will then be sent to MSC. MSC transfers this message to the source BSC, and the source BSC sends a HANDOVER COMMAND message to MS. This item measures the times of the current cell as the target cell sending HANDOVER REQUEST ACKNOWLEDGE to MSC. This item, together with Attempted incoming interBSC inter cell handovers , helps the user know the situation of the unsuccessful handovers due to abnormalities during the preparation of new channel in the current cell, or with Successful incoming interBSC inter cell handovers to know the situation of unsuccessful handovers due to radio interface abnormal in the current cell. Related items: Inter BSC outgoing cell handovers , Incoming internal inter cellhandovers .

Measurement point: During the procedure of interBSC handover, after the target cell (current cell) receives the CHANNEL ACTIVATION ACKNOWLEDGE message, it sends HANDOVER REQUEST ACKNOWLEDGE to MSC which contains the HANDOVER COMMAND message to be sent to MS. This item is measured in this case, as shown in Figure 3-1 A1.

Formula: none.

MS BTS BSC MSC/VLR

HANDOVER COMPLETE

HANDOVER DETECTION

CHANNEL ACT

CHAN ACT ACK

HANDOVER COMPLETE

HANDOVER REQ ACK

A1

A1: Inter BSC incoming cell handovers

Figure 3-1 Inter BSC incoming cell handovers

XVI. Inter BSC outgoing cell handovers

Description: During the procedure of interBSC handover, the target BSC finishes allocating the new channel and generates the HANDOVER COMMAND message, which is sent by MSC to the source BSC. After

266


receiving this message, the source BSC sends it to MS. This item measures the times of the current cell as the source cell sending the HANDOVER COMMAND message to MS. Together with Attempted outgoing interBSC intercell handovers , this item helps the user know the situation of unsuccessful handovers due to abnormalities during the preparation of new channel in the target cell, or with Successful outgoing interBSC inter cell handovers to know the situation of unsuccessful handovers due to radio interface abnormal in the target cell. Related items: Outgoing internal inter cell handovers , Inter BSCincoming cell handovers .

Measurement point:This item is measured when the source cell (current cell) receives the HANDOVER COMMAND message from MSC, as shown in Figure3-53 B1.

Formula: none.

XVII. SDCCHs initially configured

Description: This item reflects the number of SDCCHs of a cell in BSC at the start time of a statistic cycle which are configured in the data configuration table. The SDCCHs obtained by dynamic adjustment of TCHs are excluded.

Measurement point: This item is measured at the start time of a statistic cycle. Formula: none.

XVIII. Initially configured TCHs of 900 cell

Description: This items reflects the number of TCHs of a 900 cell in BSC at the start time of a statistic cycle which are configured in the data configuration table, including the TCHs which are dynamically converted into SDCCHs.


XIX. Initially configured TCHs of 1800 cell

Description: This items reflects the number of TCHs of a 1800 cell in BSC at the start time of a statistic cycle which are configured in the data configuration table, including the TCHs which are dynamically converted into SDCCHs.


XX. Initially configured dynamic PDCHs of 900 cell

Description: This items reflects the number of dynamic PDCHs of a 900 cell in BSC at the start time of a statistic cycle which are configured in the data configuration table


267


XXI. Initially configured dynamic PDCHs of 1800 cell

Description: This items reflects the number of dynamic PDCHs of a 1800 cell in BSC at the start time of a statistic cycle which are configured in the data configuration table


XXII. Unsuccessful outgoing BSC handovers with successful reversion

Description: During the procedure of interBSC handover, after the source cell sends a HANDOVER COMMAND message to MS, if the MS cannot accessed the target cell due to poor radio environment or handover parameter incorrect, it will send a HANDOVER FAILURE message (cause: Radio interface failure, reversion to old channel) to the source BSC via the previous channel. The source BSC then sends this message to MSC. MSC notifies the target BSC to clear the resources related to this handover. The connecting between the source cell and MS remains the same. This item measures the times of unsuccessful handover with successful reversion when the current cell is the source cell. Related items: Unsuccessful outgoing BSC handovers withunsuccessful reversion , Unsuccessful internal inter cell handovers withsuccessful reversions , Unsuccessful intracell handovers with successfulreversions .

Measurement point: This item is measured when the source cell (current cell) receives the HANDOVER FAILURE message (cause: Radio interface failure, reversion to old channel) from MS during the procedure of interBSC handover, as shown in Figure 3-1 A1.

Formula: none.

BTS BSC1 MSC/VLR

HANDOVER REQUIRED

HANDOVER COMMAND


A1, C1 HANDOVER FAILURE

HANDOVER FAILURE

CLEAR COMMAND

CONN FAIL IND

ERROR INDICATION

HANDOVER COMMAND

B1 , D1B2 , D2

B3 , D3



268


C1: Unsuccessful outgoing inter cell handovers with successful reversion

D1~D3: Unsuccessful outgoing inter cell handovers with unsuccessful reversion


XXIII. Unsuccessful outgoing BSC handovers with unsuccessful reversion

Description: During the procedure of interBSC handover, after the source cell sends a HANDOVER COMMAND message to MS, the connection between MS and the source BSC is terminated before the connection between MS and the target BSC set up due to poor radio environment or equipment failure. When BSC detects this situation, it will send a CLEAR REQUEST message to MSC to request for clearing the previous resources and the resources during handover. This handover is failed and the original service cannot be restored. This item measures the times of unsuccessful handover with unsuccessful reversion when the current cell is the source cell. Related items: Unsuccessfuloutgoing BSC handovers with successful reversion , Unsuccessful outgoinginterBSC inter cell handovers, Unsuccessful internal inter cell handovers withunsuccessful reversions , Unsuccessful intracell handovers with unsuccessfulreversions .

Measurement point:1) This item is measured when the source cell (current cell) receives

CONNECTION FAILURE INDICATION from BTS during the procedure of interBSC handover, as shown in Figure 3-1 B1.

2) This item is measured when the source cell (current cell) receives the ERROR INDICATION message (cause: timer T200 expired (N200 + 1) times (0x01) or unsolicited DM response, multiple frame established state (0x05) or sequence error (0x07)) from BTS during the procedure of interBSC handover, as shown in Figure 3-1 B2.

3) This item is measured when the source cell (current cell) receives the CLEAR COMMAND message (cause: not handover success) from MSC during the procedure of interBSC handover, as shown in Figure 3-1 B3.

4) This item is measured when the source cell (current cell) waiting for the CLEAR COMMAND message (cause: handover success) from MSC times out during the procedure of interBSC handover.

Formula: none.

XXIV. Average available TCHs from Dyn-PDTCH

Description: This item provides the average number of available TCHs converted from dynamic PDCHs in a cell within the measurement period. The channel status can be either idle or seized, but it should be an available channel. This item is measured under sampling mechanism. BSC checks the

269


number of available TCHs converted from dynamic PDCHs in a cell recorded in the database every five senconds. This number is accumulated within measurement period. At the end of measurement cycle, this accumulated number is divided by the times of accumulating (times of sampling) to get the value of this item. Therefore, this item may not be an integer.

Measurement point: At the end of each measurement period, the average available TCHs converted from dynamic PDCHs will be calculated and sent to BAM.

Formula: None.

XXV. Average available PDCHs from Dyn-PDTCH

Description: This item provides the average number of available PDCHs converted from dynamic PDCHs within the measurement period. The channel status can be either idle or seized, but it should be an available channel. This item is measured under sampling mechanism. BSC checks the number of available PDCHs converted from dynamic PDCHs in a cell recorded in the database every five senconds. This number is accumulated within measurement period. At the end of measurement period, this accumulated number is divided by the times of accumulating (times of sampling) to get the value of this item. Therefore, this item may not be an integer.

Measurement point: At the end of each measurement period, the average available PDCHs converted from dynamic PDCHs will be calculated and sent to BAM.

Formula: None.

XXVI. Percentage of TRX in good condition (%)

Description: This item reflects the percentage of available TRXs to configured TRXs. See Sum of available TRX in the cell and Sum of configured TRX inthe cell .

Measurement point: Omitted. Formula: Sum of available TRX in the BSC / Sum of configured TRX in the

BSC

XXVII. Ratio of cell usability (%)

Description: This item reflects the percentage of unusable time of the cell to the statistic cycle. See Unusable time of the cell (second) .

Measurement point: Omitted. Formula: 1-unusable time of the cell (s) / Statistic cycle (s).

270


3.2 Power Control Measurement

3.2.1 General

Power control is the process of changing the transmission power of BTS and MS during a conversation. The purpose of power control is to improve conversation quality, and at the same time keep the signal level to remain at a certain range. The elements that trigger power control are the receiving level and receiving strength in MR.

Power control measurement is for the statistics of parameters related to the transmitting power and receiving level, including times of BSC sending power control commands to BTS and MS, the average transmitting power level of BTS and MS.

When power control is registered, it is possible to analyze "Average downlink strength" to know the coverage quality and power control effect, or to analyze "Power control messages to MS for power increasing" to get the information of the frequency of power control implementation in a cell.

The object of power control measurement is the cell. The module No. and cell No. (or all cells in a module) can be configured in the interface of Object Definition. This measurement indices in this part is listed in Table 3-1 .

Table 3-1 Power control measurement items

No. Item name

1Power control messages to MS for power increasing

2Power control messages to MS for power decreasing

3Power control messages to BTS for power increasing

4Power control messages to BTS for power decreasing

5Average MS power level

6Average BTS power level

7Average downlink strength

8Average uplink strength

9Average downlink quality

10Average uplink quality

11Maximum downlink power duration percentage

12Maximum uplink power duration percentage

13Average distance between MS and BTS

14Maximum distance between MS and BTS

15Sum of measurement reports in a cell

271



I. Power control messages to MS for power increasing

Description: After receiving MR, BSC compares the uplink receiving level and uplink receiving strength in MR with the configured uplink receiving level threshold and uplink receiving strength threshold according to the power control algorithm. If the result suggests that the MS needs to increase transmitting power, the corresponding message will be sent to MS. Whenever this happens, this index will increase by 1.

Measurement point: Measured when BSC sends the power increasing message to MS.

Formula: none.

II. Power control messages to MS for power decreasing

Description: After receiving MR, BSC compares the uplink receiving level and uplink receiving strength in MR with the configured uplink receiving level threshold and uplink receiving strength threshold according to the power control algorithm. If the result suggests that the MS needs to lower transmitting power, the corresponding message will be sent to MS. Whenever this happens, this index will increase by 1.

Measurement point: Measured when BSC sends the power decreasing message to MS.

Formula: none.

III. Power control messages to BTS for power increasing

Description: After receiving MR, BSC compares the downlink receiving level and downlink receiving strength in MR with the configured downlink receiving level threshold and downlink receiving strength threshold according to the power control algorithm. If the result suggests that the BTS needs to increase transmitting power, the corresponding message will be sent to BTS. Whenever this happens, this index will increase by 1.

Measurement point: Measured when BSC sends the power increasing message to BTS.

Formula: none.

IV. Power control messages to BTS for power decreasing

Description: After receiving MR, BSC compares the uplink receiving level and uplink receiving strength in MR with the configured uplink receiving level threshold and uplink receiving strength threshold according to the power

272


control algorithm. If the result suggests that the BTS needs to lower transmitting power, the corresponding message will be sent to BTS. Whenever this happens, this index will increase by 1.

Measurement point: Measured when BSC sends the power decreasing message to BTS.

Formula: none.

V. Average MS power level

Description: This index reflects the average transmitting power of the MSs in the cell. After receiving MR, BSC will add the transmitting power level value of MS in MR to the sum. The value of this index is generated by dividing the sum with the total times of receiving MR. The lower MS average power level suggests the higher MS transmitting power.

Measurement point: Measured when BSC receives MR. Formula: none.

VI. Average BTS power level

Description: This index reflects the average transmitting power of the BTSs in the cell. After receiving MR, BSC will add the transmitting power level value of BTS in MR to the sum. The value of this index is generated by dividing the sum within the measurement cycle with the total times of receiving MR. The lower BTS average power level suggests the higher BTS transmitting power.


VII. Average downlink strength

Description: This index reflects the average downlink receiving level in this cell. After receiving MR, BSC will add the downlink receiving level values to the sum. The value of this index is generated by dividing the sum within the measurement cycle with the total times of receiving MR.


VIII. Average uplink strength

Description: This index reflects the average uplink receiving level in this cell. After receiving MR, BSC will add the downlink receiving level values to the sum. The value of this index is generated by dividing the sum within the measurement cycle with the total times of receiving MR.


273


IX. Average downlink quality

Description: This index reflects the average downlink receiving quality in the cell. After receiving MR, BSC will add the downlink receiving quality level values to the sum. The value of this index is generated by dividing the sum within the measurement cycle with the total times of receiving MR. There are 8 quality levels: 0~7. The lower average downlink signal quality suggests the better quality.


X. Average uplink quality

Description: This index reflects the average uplink receiving quality in the cell. After receiving MR, BSC will add the uplink receiving quality level values to the sum. The value of this index is generated by dividing the sum within the measurement cycle with the total times of receiving MR. There are 8 quality levels: 0~7. The lower average uplink signal quality suggests the better quality.


XI. Maximum downlink power duration percentage

Description: This index reflects the percentage of time BTS spent in maximum power transmission in the cell. After BSC receiving MR, the times of downlink power being the maximum value will increase by 1 if the downlink transmitting power level value is 0 in MR. The value of this index is generated by dividing the times of the downlink power being the maximum value with the total times of receiving MR, and then multiplying quotient with 100. If the time for downlink power being the maximum value is too long, then there may be areas with poor coverage or unreasonably configured power control parameter.

Measurement point: Measured when BSC receives the MR in which the downlink transmitting power level value is 0.

Formula: none.

XII. Maximum uplink power duration percentage

Description: This index reflects the percentage of time MS spent in maximum power transmission in the cell. After BSC receiving MR, the times of uplink power being the maximum value will increase by 1 if the uplink transmitting power level value is smaller than "MS Max Radio Power Control Level" in system information in MR. Normally the lower power level value suggests the higher MS transmitting power. The value of this index is generated by dividing the times of the uplink power being the maximum value with the total times of receiving MR, and then multiplying quotient with 100. If the time for uplink

274


power being the maximum value is too long, then there may be too low receiving level or unreasonably configured power control parameter.

Measurement point: Measured when BSC receives the MR in which the uplink transmitting power level value is smaller or equal to "MS Max Radio Power Control Level" in system message.

Formula: none.

XIII. Average distance between MS and BTS

Description: This index reflects the average distance between MSs and BTS in the cell. The average distance between MSs and BTS is indicated with TA (a unit of TA value equal to about 550 meters). After receiving MR, BSC will add the TA value in MR to the sum. The value of this index is generated by dividing the sum within the measurement cycle with the total times of receiving MR. Normally, the larger distance between MS and BTS will cause larger TA value.


XIV. Maximum distance between MS and BTS

Description: This index reflects the maximum distance between MSs and BTS in the cell. The maximum distance between MSs and BTS is indicated with TA (a unit of TA value equal to about 550 meters). After receiving MR, BSC will compare the current TA value in MR with the previous one. The larger one is recorded. The value of this index is largest TA within the measurement cycle with the total times of receiving MR. Normally, the larger distance between MS and BTS will cause larger TA value.

Measurement point: Measured when BSC receives MR in which the TA is larger than the previous one.

Formula: none.

XV. Sum of measurement reports in a cell

Description: This index reflects the total times of sending cell measurement reports. When BSC receives MR, this index increases by 1.


3.3 Call Drop Measurement

3.3.1 General

"Call drop measurement" is used to measure the average level, quality and TA when call drop occurs.

275


When "call drop measurement" is registered, it is possible to find out the cause of call drop with the help of measurement results. For example, when "Average timing advance at Full Rate TCH call drop" is registered, the TA will be measured when call drop occurs after full rate TCH is seized. If the value of the result is too high, it can be concluded that the cause of call drop is TA too high which is further caused by subscriber too far away from BTS or adjacent cell configuration improper. In another example, the value in the result of "Average uplink level at Full Rate TCH call drop" is too high, and so is "Average uplink quality at Full Rate TCH call drop", i.e. the uplink receiving level is high enough but the TCH quality is poor. It indicates that the call drop is possibly caused by uplink interference.

The object of "Call drop measurement" is cell. In the object definition interface, user can select some cells by inputting module No. and cell No. or select all cells within a module to measure.

User can register the items related to full rate, half rate or SDCCH call drop. Among them, items related to full rate call drop and SDCCH call drop belong to "full rate call drop measurement", and those related to half rate call drop belong to "half rate call drop measurement".

Note that valid MR is the complete MR whose uplink MR and downlink MR are both valid.

3.9.6 Full Rate Call Drop Measurement

The items of full rate call drop measurement are listed in Table 3-2 .

Table 3-2 Full rate call drop measurement indices

No. Item name

1Average uplink level at SDCCH call drop

2Average downlink level at SDCCH call drop

3Average uplink quality at SDCCH call drop

4Average downlink quality at SDCCH call drop

5Average timing advance at SDCCH call drop

6Average uplink level at full rate TCH call drop

7Average downlink level at full rate TCH call drop

8Average uplink quality at full rate TCH call drop

9Average downlink quality at full rate TCH call drop

10Average timing advance at full rate TCH call drop

276


I. Average uplink level at SDCCH call drop

Meaning: When seizing a SDCCH, MS reports a MR to the network every 470ms. This item provides the average uplink level in MRs when call drops occur on SDCCH. Whenever a call drop occurs on SDCCH, the value of uplink level in the last valid MR is accumulated. Within the measurement period, the sum of the this values accumulated is divided by the total times of call drop on SDCCH of the measured cell to get the value of this item.

Measurement point: This item is measured when call drop occurs on SDCCH. Formula: None.

II. Average downlink level at SDCCH call drop

Meaning: When seizing a SDCCH, MS reports a MR to the network every 470ms. This item provides the average downlink level in MRs whenever call drop occurs on SDCCH. Whenever call drop occurs on SDCCH, the value of downlink level in the last valid MR is accumulated. Within the measurement period, the sum of the this values accumulated is divided by the total times of call drop on SDCCH of the measured cell to get the value of this item.


III. Average uplink quality at SDCCH call drop

Meaning: When seizing a SDCCH, MS reports a MR to the network every 470ms. This item provides the average uplink quality in MRs whenever call drop occurs on SDCCH. Whenever call drop occurs on SDCCH, the value of uplink quality in the last valid MR is accumulated. Within the measurement period, the sum of the this values accumulated is divided by the total times of call drop on SDCCH of the measured cell to get the value of this item.


IV. Average downlink quality at SDCCH call drop

Meaning: When seizing a SDCCH, MS reports a MR to the network every 470ms. This item provides the average downlink quality in MRs whenever call drop occurs on SDCCH. Whenever call drop occurs on SDCCH, the value of downlink quality in the last valid MR is accumulated. Within the measurement period, the sum of the this values accumulated is divided by the total times of call drop on SDCCH of the measured cell to get the value of this item.


277


V. Average timing advance at SDCCH call drop

Meaning: When seizing a SDCCH, MS reports a MR to the network every 470ms. This item provides the average timing advance in MRs whenever call drop occurs on SDCCH. Whenever call drop occurs on SDCCH, the value of timing advance in the last valid MR is accumulated. Within the measurement period, the sum of the this values accumulated is divided by the total times of call drop on SDCCH of the measured cell to get the value of this item.


VI. Average uplink level at full rate TCH call drop

Meaning: When seizing a full rate TCH, MS reports a MR to the network every 470ms. This item provides the average uplink level in MRs whenever call drop occurs on full rate TCH. Whenever call drop occurs on full rate TCH, the value of uplink level in the last valid MR is accumulated. Within the measurement period, the sum of the this values accumulated is divided by the total times of call drop on full rate TCH of the measured cell to get the value of this item.

Measurement point: This item is measured when call drop occurs on full rate TCH.

Formula: None.

VII. Average downlink level at full rate TCH call drop

Meaning: When seizing a full rate TCH, MS reports a MR to the network every 470ms. This item provides the average downlink level in MRs whenever call drop occurs on full rate TCH. Whenever call drop occurs on full rate TCH, the value of downlink level in the last valid MR is accumulated. Within the measurement period, the sum of the this values accumulated is divided by the total times of call drop on full rate TCH of the measured cell to get the value of this item.


Formula: None.

VIII. Average uplink quality at full rate TCH call drop

Meaning: When seizing a full rate TCH, MS reports a MR to the network every 470ms. This item provides the average uplink quality in MRs whenever call drop occurs on full rate TCH. Whenever call drop occurs on full rate TCH, the value of uplink quality in the last valid MR is accumulated. Within the measurement period, the sum of the this values accumulated is divided by the total times of call drop on full rate TCH of the measured cell to get the value of this item.

278



Formula: None.

IX. Average downlink quality at full rate TCH call drop

Meaning: When seizing a full rate TCH, MS reports a MR to the network every 470ms. This item provides the average downlink quality in MRs whenever call drop occurs on full rate TCH. Whenever call drop occurs on full rate TCH, the value of downlink quality in the last valid MR is accumulated. Within the measurement period, the sum of the this values accumulated is divided by the total times of call drop on full rate TCH of the measured cell to get the value of this item.


Formula: None.

X. Average timing advance at full rate TCH call drop

Meaning: When seizing a full rate TCH, MS reports a MR to the network every 470ms. This item provides the average timing advance in MRs whenever call drop occurs on full rate TCH. Whenever call drop occurs on full rate TCH, the value of timing advance in the last valid MR is accumulated. Within the measurement period, the sum of the this values accumulated is divided by the total times of call drop on full rate TCH of the measured cell to get the value of this item.


Formula: None.

3.9.7 Half Rate Call Drop Measurement

The items of half rate call drop measurement are listed in Table 3-3 .

Table 3-3 Half rate call drop measurement

1Average uplink level at half rate TCH call drop

2Average downlink level at half rate TCH call drop

3Average uplink quality at half rate TCH call drop

4Average downlink quality at half rate TCH call drop

5Average timing advance at half rate TCH call drop

279


I. Average uplink level at half rate TCH call drop

Meaning: When seizing a half rate TCH, MS reports a MR to the network every 470ms. This item provides the average uplink level in MRs whenever call drop occurs on half rate TCH. Whenever call drop occurs on half rate TCH, the value of uplink level in the last valid MR is accumulated. Within the measurement period, the sum of the this values accumulated is divided by the total times of call drop on half rate TCH of the measured cell to get the value of this item.

Measurement point: This item is measured when call drop occurs on half rate TCH.

Formula: None.

II. Average downlink level at half rate TCH call drop

Meaning: When seizing a half rate TCH, MS reports a MR to the network every 470ms. This item provides the average downlink level in MRs whenever call drop occurs on half rate TCH. Whenever call drop occurs on half rate TCH, the value of downlink level in the last valid MR is accumulated. Within the measurement period, the sum of the this values accumulated is divided by the total times of call drop on half rate TCH of the measured cell to get the value of this item.


Formula: None.

III. Average uplink quality at half rate TCH call drop

Meaning: When seizing a half rate TCH, MS reports a MR to the network every 470ms. This item provides the average uplink quality in MRs whenever call drop occurs on half rate TCH. Whenever call drop occurs on half rate TCH, the value of uplink quality in the last valid MR is accumulated. Within the measurement period, the sum of the this values accumulated is divided by the total times of call drop on half rate TCH of the measured cell to get the value of this item.


Formula: None.

IV. Average downlink quality at half rate TCH call drop

Meaning: When seizing a half rate TCH, MS reports a MR to the network every 470ms. This item provides the average downlink quality in MRs whenever call drop occurs on half rate TCH. Whenever call drop occurs on half rate TCH, the value of downlink quality in the last valid MR is accumulated. Within the measurement period, the sum of the this values accumulated is divided by the

280


total times of call drop on half rate TCH of the measured cell to get the value of this item.


Formula: None.

V. Average timing advance at half rate TCH call drop

Meaning: When seizing a half rate TCH, MS reports a MR to the network every 470ms. This item provides the average timing advance in MRs whenever call drop occurs on half rate TCH. Whenever call drop occurs on half rate TCH, the value of timing advance in the last valid MR is accumulated. Within the measurement period, the sum of the this values accumulated is divided by the total times of call drop on half rate TCH of the measured cell to get the value of this item.


Formula: None.

3.4 SITE Initial Measurement Function

3.4.1 General

The traffic statistic items in "SITE Initial Measurement Function" are used to measure the initialization status of a BTS. See Table 3-1 for the list of all the relevant statistic items.


No. Item name

1 Sum of site initializations

2 Successful site initializations(kickoff)

3 Successful site initializations(reset)

4 Unsuccessful site initializations(kickoff)

5 Unsuccessful site initializations(reset)

The measurement object of each traffic statistic item in "SITE Initial Measurement Function" is BTS, and the statistic result is number of BTS initializations, number of successful initializations, number of unsuccessful initializations, etc. respectively. Because the statistics are made without distinguishing the causes for BTS initialization, initialization success or failure, the statistic results can only reflect the site initialization status in a statistic period on the whole, and are of no significance

281


for analyzing the success or failure of a specific initialization. When analyzing the specific causes, the user can make use of the alarm progress interface and BTS reset progress interface. For example, by viewing the [Site Initialization] interface in Figure 3-2 , the user can learn that the site initialization failure is caused by erroneous data configuration.

Figure 3-2 Site initialization


I. Sum of site initializations

Description: This item is used to calculate the number of initializations of a BTS within a statistic period. It does not differentiate initialization causes. So long as a BTS is initialized, the number of site initializations will be incremented by 1. The causes that can lead to BTS initialization include level-3 or level-4 reset initiated by BTS Maintenance System, BTS reset initiated by BSC after BTS reports an erroneous state change report, scheduled initialization performed after BTS initialization fails, initialization caused by dynamic data configuration (including dynamic addition of BTS, modification of channel type in a BTS of chain connection, TRX addition, cell addition, modification of the relevant property of a 2-TS extended cell, etc.), initialization requested by BTS.

Measurement point: The number of successful site initializations will be incremented by 1 when a site is successfully initialized.

Formula: none.

282


II. Successful site initializations(kickoff)

Description: Site kickoff initialization refers to BTS initialization that is led to by causes other than level-3 or level-4 reset initiated by BTS Maintenance System, and BTS reset initiated by BSC after BTS reports an erroneous state change report. For example, scheduled initialization performed after BTS initialization fails, initialization caused by dynamic data configuration (including dynamic addition of BTS, modification of channel type in a BTS of chain connection, TRX addition, cell addition, modification of the relevant property of a 2-TS extended cell, etc.), initialization requested by BTS. This statistic item is used to calculate the number of successful BTS kickoff initializations within a statistic period.

Measurement point: The number of successful site kickoff initializations will be incremented by 1 when a BTS kickoff initialization is successfully completed and BSC receives a state change report from BTS.

Formula: none.

III. Successful site initializations(reset)

Description: This item is used to calculate the number of all successful site initializations except successful site kickoff initializations. The causes for site non-kickoff initialization include level-3 and level-4 reset initiated by BTS Maintenance System, and BTS reset initiated by BSC after BTS reports an erroneous state report.

Measurement point: The number of successful site initializations will be incremented by 1 when a site non-kickoff initialization is successfully completed and BSC receives a state change report from BTS.

Formula: none.

IV. Unsuccessful site initializations(kickoff)

Description: This item is used to calculate the number of unsuccessful site kickoff initializations. The following causes can lead to site kickoff initialization failure.1) BSC cannot receive a response within the specified time after it sends an

initialization message to BTS.2) During the course of initialization, BSC detects an error such as data

configuration error.3) After BSC sends initialization messages to BTS for three successive

times, BTS still returns an erroneous response. Measurement point:

1) When site kickoff initialization fails.4) When site kickoff initialization is initiated again after the previous site

kickoff initialization fails.

283


5) When flow control is performed during the course of site kickoff initialization.

Formula: none.

V. Unsuccessful site initializations(reset)

Description: This item is used to calculate the number of unsuccessful site initializations except unsuccessful site kickoff initializations. The following causes can lead to site initialization failure.1) BSC cannot receive a response within the specified time after it sends an

initialization message to BTS.2) During the course of initialization, BSC detects an error such as data

configuration error.3) After BSC sends initialization messages to BTS for three successive


7) When site initialization fails.

When site initialization is initiated again after the previous site initialization

fails.

When flow control is performed during the course of site initialization.

Formula: none.

3.5 BTS Initial Measurement Function

3.5.1 General

The traffic statistic items in "BTS Initial Measurement Function" are used to measure the initialization status of a cell. See Table 3-1 for the list of all the relevant statistic items.

Table 3-1 Statistic items in BTS Initial Measurement Function

No. Item name

1 Sum of cell initializations

2 Successful cell initializations(kickoff)

3 Successful cell initializations(reset)

4 Unsuccessful cell initializations(kickoff)

5 Unsuccessful cell initializations(reset)

The measurement object of each traffic statistic item in "BTS Initial Measurement Function" is cell, and the statistic result is number of cell initializations, number of

284


successful initializations, number of unsuccessful initializations, etc. respectively. Because the statistics are made without distinguishing the causes for cell initialization, initialization success or failure, the statistic results can only reflect the cell initialization status in a statistic period on the whole, and are of no significance for analyzing the success or failure of a specific initialization. When analyzing the specific causes, the user can make use of the alarm progress interface and initialization progress interface. For example, by viewing the [Site Initialization] interface in Figure 3-2 , the user can learn that the cell initialization failure is caused by erroneous cell extended property configuration.

Figure 3-2 Cell initialization failure


I. Sum of cell initializations

Description: This item is used to calculate the number of initializations of a cell within a statistic period. It does not differentiate initialization causes. So long as a cell configuration message is delivered to BTS, the number of cell initializations will be incremented by 1. The causes that can lead to cell initialization include BTS initialization, cell initialization caused by dynamic data configuration (including dynamic addition of a cell, dynamic addition/deletion of TRX in a baseband FH cell, dynamic modification of the frequencies of the TRX where BCCH is located, modification of the frequencies of the TRX that participates in baseband FH, modification of cell FH data, etc.), TRX mutual aid or TRX switchback occurred in a baseband FH cell, and scheduled cell initialization initiated again after the previous cell initialization fails.

285


Measurement point: The number of cell initializations will be incremented by 1 when a cell configuration message is delivered to BTS.

Formula: none.

II. Successful cell initializations(kickoff)

Description: Cell kickoff initialization refers to the cell initialization that is led to by causes other than level-3 or level-4 reset of BTS initiated by BTS Maintenance System, and BTS reset initiated by BSC after BTS reports an erroneous state change report, For example, cell initialization caused by dynamic data configuration (including dynamic addition of a cell, dynamic addition/deletion of TRX in a baseband FH cell, dynamic modification of the frequencies of the TRX where BCCH is located, modification of the frequencies of the TRX that participates in baseband FH, modification of cell FH data, etc.), TRX mutual aid or TRX switchback occurred in a baseband FH cell, scheduled cell initialization initiated again after the previous cell initialization fails, etc. This item is used to calculate the number of successful cell kickoff initializations within a statistic period.

Measurement point: The number of successful cell kickoff initializations will be incremented by 1 when a cell kickoff initialization is completed, and a report is received indicating that the management state of the cell has changed.

Formula: none.

III. Successful cell initializations(reset)

Description: This item is used to calculate the number of successful cell initializations (reset), The causes that can lead to this kind of cell initialization include level-3 or level-4 reset of BTS initiated by BTS Maintenance System, and BTS reset initiated by BSC after BTS reports an erroneous state change report.

Measurement point: The number of successful cell initializations (reset) will be incremented by 1 when a cell initialization is completed, and a report is received indicating that the management state of the cell has changed.

Formula: none.

IV. Unsuccessful cell initializations(kickoff)

Description: This item is used to calculate the number of unsuccessful cell kickoff initializations. The following causes can lead to cell initialization failure.1) BSC cannot receive a response within the specified time after it sends a

cell initialization message to BTS.2) During the course of initialization, BSC detects an error such as data

configuration error.

286


3) After BSC sends cell initialization messages to BTS for three successive times, BTS still returns an erroneous response.

Measurement point:4) When cell kickoff initialization fails.5) When cell kickoff initialization is initiated again after the previous cell

kickoff initialization fails.6) When flow control is performed during the course of cell initialization.

Formula: none.

V. Unsuccessful cell initializations(reset)

Description: This item is used to calculate the number of unsuccessful cell initializations except unsuccessful cell kickoff initializations. The following causes can lead to cell initialization failure.1) BSC cannot receive a response within the specified time after it sends a

cell initialization message to BTS.2) During the course of initialization, BSC detects an error such as data

configuration error.3) After BSC sends cell initialization messages to BTS for three successive


1) When cell initialization fails.2) When cell initialization is initiated again after the previous cell

initialization fails.3) When flow control is performed during the course of cell initialization.

Formula: none.

3.6 Cell Broadcast Statistic

3.6.1 General

The items of Cell Broadcast Statistic are used to measure the times of CB messages and the load of CBCH in one or multiple cells under a specified module. Table 3-1 lists all items in Cell Broadcast Statistic.

Table 3-1 Statistic items in Cell broadcast statistic

No. Item name

1 CBS messages (O)

2 Load of CBCH msg queue(%)

287


To know the operation of the cell broadcast of the entire BSC, it is necessary to register the relative items in BSC Cell Broadcast Measurement Function.

The object of Cell Broadcast Statistic is cell which can be one or multiple cells under the specified BM. The recommended measurement cycle is 60 minutes.


I. CBS messages (O)

Description: BSC transfers CBS information to each appropriate BTS via the SMS BROADCAST COMMAND message, indicating the channel which shall be used. In DRX mode, the broadcast short messages also include the schedule messages and null messages.

Measurement point: As shown in Figure 3-1 A, this item is measured when BSC sends SMS BROADCAST COMMAND

Formula: none.

BSC BTS

SMS BROADCAST COMMAND A

A: CBS messages (O)

Figure 3-1 Times of sending SMS broadcast

II. Load of CBCH msg queue(%)

Description: The percentage of the current length of queue for CB message transmission accounting the total capacity of the buffer for cell transmission.

Measurement point: Length of the CB message transmission queue of BSC sampling cell every five minutes.

Formula: Length of the CB message transmission queue / total capacity of the buffer for cell transmission

288


3.7 Outgoing Inter Cell Handover Measurement Function

3.7.1 General

The statistic items in Outgoing Inter Cell Handover Measurement Function are used to know the performance of the handover between the specified cell and its adjacent cells. They are mainly divided into attempted handover, successful handovers, and unsuccessful handovers, where attempted handover and successful handovers are measured according to different handover causes respectively, reflecting the handover performance from the specified cell to its adjacent cells in detail. All statistic items of Outgoing Inter Cell Handover Measurement Function are listed in Table 3-1 .

To know the incoming inter cell handover performance of the specified cell, the related statistic items of Incoming Inter Cell Handover Measurement Function should be registered.

For the statistic items of Outgoing Inter Cell Handover Measurement Function, it is recommended that they should be registered at the early stage of BSC running, or be registered when the handover performance of the specified cell is to be known so that the network optimization can be performed. At the stable running stage of BSC, the task of these statistic items can be deleted. These items together with the statistic items of Incoming Inter Cell Handover Measurement Function can be used to know the handover situation between two specified cells. The statistic cycle is recommended to be 60 minutes.

The statistic object of the statistic items of Outgoing Inter Cell Handover Measurement Function is two cells: the source cell and its adjacent cell. While registering, the way of setting the adjacent cell can either be set to all adjacent cells of the source cell, or can be specified by CGI. All statistic items of Outgoing Inter Cell Handover Measurement Function will be selected together for registration.

The description, measurement point, and measurement formula for each statistic item are described as follows:

The description is to brief the procedure to trigger the statistic item, the cause to trigger the statistic item, the feature of the traffic indicated by the statistic item, and the handling of the abnormal situations.

Measurement point gives all causes to trigger the statistic item.

289


Table 3-1 Statistic items in Outgoing Inter Cell Handover Measurement Function

No. Item name

1 Attempted outgoing inter cell handovers

2 Attempted outgoing inter cell handovers for uplink quality

3 Attempted outgoing inter cell handovers for downlink quality

4 Attempted outgoing inter cell handovers for uplink strength

5 Attempted outgoing inter cell handovers for downlink strength

6 Attempted outgoing inter cell handovers for timing advance

7 Attempted outgoing inter cell handovers for traffic load

8 Attempted outgoing inter cell handovers for response to MSC

9 Attempted outgoing inter cell handovers for O&M intervention

10 Attempted outgoing inter cell handovers for better cell

11 Attempted outgoing inter cell handovers for rapid level drop

12 Attempted outgoing inter cell handovers for directed retry

13 Attempted outgoing inter cell handovers for other causes

14 Attempted extended inter cell outgoing cell handovers for minimum timing advance

15 Successful outgoing inter cell handovers

16 Successful outgoing inter cell handovers for uplink quality

17 Successful outgoing inter cell handovers for downlink quality

18 Successful outgoing inter cell handovers for uplink strength

19 Successful outgoing inter cell handovers for downlink strength

20 Successful outgoing inter cell handovers for timing advance

21 Successful outgoing inter cell handovers for traffic load

22 Successful outgoing inter cell handovers for response to MSC

23 Successful outgoing inter cell handovers for O&M intervention

24 Successful outgoing inter cell handovers for better cell

25 Successful outgoing inter cell handovers for rapid level drop

26 Successful outgoing inter cell handovers for directed retry

27 Successful outgoing inter cell handovers for other causes

28 Successful outgoing inter cell handovers in the extended cell (minimum timing advance)

29 Unsuccessful outgoing cell handover with successful reversion

30 Unsuccessful outgoing cell handover with unsuccessful reversion

31 Outgoing inter cell handover success rate (%)

290



I. Attempted outgoing inter cell handovers

Description: the attempted handovers that the current cell (source cell) initiates to the specified target cell. If the target cell and the current cell are in different BSCs, the handover is interBSC handover; otherwise the handover is internal intercell handover. This item is used to indicate the frequency of the handover from the current cell to the specified target cell. This item together with Successful outgoing inter cell handovers can be used to know the performance of such handover from the current cell to the specified target cell. See Attempted outgoing internal inter cell handovers and Attempted outgoinginterBSC inter cell handovers.

Note:

For outgoing interBSC inter cell handover, after initiating a handover by sending a HANDOVER


HANDOVER COMMAND message from MSC. Therefore, the source cell measures the number of

attempted handovers by measuring the number of outgoing interBSC inter cell handover, i.e.,

accumulates the number of attempted handovers on reception of a HANDOVER COMMAND

message.

Measurement point: 1) In internal intercell handover procedure, the target cell is the registered

adjacent cell. This item is measured when the source cell (the current cell) sends an Intercell Handover Request message to the specified target cell after the handover algorithm decision.

2) In interBSC handover procedure, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the HANDOVER COMMAND message from MSC, as shown in Figure 3-1 F1.

Formula: none

291


MS BSC2BSC1 MSC/VLR

HANDOVER REQUIRED

HANDOVER REQUEST

HANDOVER REQ ACK

HANDOVER COMMAND

HANDOVER COMMAND

MS

HANDOVER ACCESSHANDOVER DETECT

HANDOVER COMPLETE

CLEAR COMMAND

CLEAR COMPLETE

A1

B1 , C1, D1, E1, F1

HANDOVER REQUIRED

HANDOVER COMPLETE

A1: Attempted outgoing interBSC inter cell handovers

B1: Inter BSC outgoing cell handovers

C1: Outgoing interbsc inter cell handovers (to 900)

D1: Outgoing interbsc inter cell handovers (to 1800)

E1: Attempted dual-band intercell handovers

F1: Attempted outgoing inter cell handovers (including various handover causes)

Figure 3-1 Attempted outgoing interBSC inter cell handovers

II. Attempted outgoing inter cell handovers for uplink quality

Description: when BSC initiates a handover, it will receive Handover Indication message containing "handover cause" from LAPD module. The attempted handovers are measured according to the different handover causes in this message. This item measures the attempted handovers (internal intercell handover or interBSC handover, determined by the source cell and the target cell) that the current cell initiates to the specified target cell due to uplink quality. This item is used to indicate the frequency that the current cell initiates the handovers to the specified target cell due to uplink quality. This item together with Successful outgoing inter cell handovers for uplink quality can be used to know the performance of such handover from the current cell to the specified target cell. See Attempted outgoing inter cell handovers .

Note:




attempted handovers by measuring the number of outgoing interBSC inter cell handover, i.e,

292



message.

Measurement point:1) In internal intercell handover procedure, the target cell is the registered

adjacent cell. This item is measured when the source cell (the current cell) sends an Intercell Handover Request message to the specified target cell due to the uplink quality after the handover algorithm decision.

2) In inter BSC handover procedure, the target cell is the registered adjacent cell. In the case the source cell initiates handover due to the uplink quality, this item is measured when the source cell (the current cell) receives the HANDOVER COMMAND message from MSC, as shown in Figure 3-1 F1.

Formula: none

III. Attempted outgoing inter cell handovers for downlink quality

Description: when BSC initiates a handover, it will receive Handover Indication message containing "handover cause" from LAPD module. The attempted handovers are measured according to the different handover causes in this message. This item is used to measure the attempted handovers (internal intercell handover or inter BSC handover, determined by the source cell and target cell) that the current cell initiates to the specified target cell due to down quality. This item is used to indicate the frequency that the current cell initiates the handovers to the specified target cell due to downlink quality. This item together with Successful outgoing inter cell handovers for downlink quality can be used to know the performance of such handover from the current cell to the specified target cell can be known. See Attempted outgoing inter cellhandovers .

Note:






message.

Measurement point:

293


1) In internal intercell handover procedure, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) sends an Intercell Handover Request message to the specified target cell due to downlink quality after the handover algorithm decision.

2) In inter BSC handover procedure, the target cell is the registered adjacent cell. In the case the source cell initiates handover due to downlink quality, This item is measured when the source cell (the current cell) receives the HANDOVER COMMAND message from MSC, as shown in Figure 3-1 F1.

Formula: none

IV. Attempted outgoing inter cell handovers for uplink strength

Description: when BSC initiates a handover, it will receive Handover Indication message containing "handover cause" from LAPD module. The attempted handovers are measured according to the different handover causes in this message. This item is used to measure the attempted handovers (internal intercell handover or inter BSC handover, determined by the source cell and target cell) that the current cell initiates to the specified target cell due to uplink strength. This item is used to indicate the frequency that the current cell initiates the handovers to the specified target cell due to uplink strength. This item together with Successful outgoing inter cell handovers for uplink strength can be used to know the performance of such handover from the current cell to the specified target cell can be known. SeeAttempted outgoing inter cellhandovers .

Note:






message.


adjacent cell. This item is measured when the source cell (the current cell) sends an Intercell Handover Request message to the specified target cell due to the uplink strength after the handover algorithm decision.

2) In inter BSC handover procedure, the target cell is the registered adjacent cell. In the case the source cell initiates handover due to the uplink

294


strength, This item is measured when the source cell (the current cell) receives the HANDOVER COMMAND message from MSC, as shown in Figure 3-1 F1.

Formula: none

V. Attempted outgoing inter cell handovers for downlink strength

Description: when BSC initiates a handover, it will receive Handover Indication message containing "handover cause" from LAPD module. The attempted handovers are measured according to the different handover causes in this message. This item is used to measure the attempted handovers (internal intercell handover or inter BSC handover, determined by the source cell and target cell) that the current cell initiates to the specified target cell due to downlink strength. This item is used to indicate the frequency that the current cell initiates the handovers to the specified target cell due to downlink strength. This item together with Successful outgoing inter cell handovers for downlinkstrength can be used to know the performance of such handover from the current cell to the specified target cell can be known. See Attempted outgoinginter cell handovers .

Note:






message.


adjacent cell. This item is measured when the source cell (the current cell) sends an Intercell Handover Request message to the specified target cell due to the downlink strength after the handover algorithm decision.

2) In inter BSC handover procedure, the target cell is the registered adjacent cell. In the case the source cell initiates handover due to the downlink strength, This item is measured when the source cell (the current cell) receives the HANDOVER COMMAND message from MSC, as shown in Figure 3-1 F1.

Formula: none

295


VI. Attempted outgoing inter cell handovers for timing advance

Description: when BSC initiates a handover, it will receive Handover Indication message containing "handover cause" from LAPD module. The attempted handovers are measured according to the different handover causes in this message. This item is used to measure the attempted handovers (internal intercell handover or inter BSC handover, determined by the source cell and target cell) that the current cell initiates to the specified target cell due to TA (during the conversation, the subscriber is far from the serving cell but near to the target cell. This leads to the drop of signal strength and signal quality in serving cell, and a handover will be triggered.). This item is used to indicate the frequency that the current cell initiates the handovers to the specified target cell due to TA. This item together with Successful outgoing inter cell handoversfor timing advance can be used to know the performance of such handover from the current cell to the specified target cell can be known. See Attemptedoutgoing inter cell handovers .

296


Note:






message.


adjacent cell. This item is measured when the source cell (the current cell) sends an Intercell Handover Request message to the specified target cell due to TA after the handover algorithm decision.

2) In inter BSC handover procedure, the target cell is the registered adjacent cell. In the case the source cell initiates handover due to TA, This item is measured when the source cell (the current cell) receives the HANDOVER COMMAND message from MSC, as shown in Figure 3-1 F1.

Formula: none

VII. Attempted outgoing inter cell handovers for traffic load

Description: when BSC initiates a handover, it will receive Handover Indication message containing "handover cause" from LAPD module. The attempted handovers are measured according to the different handover causes in this message. This item is used to measure the attempted handovers (internal intercell handover or inter BSC handover, determined by the source cell and target cell) that the current cell initiates to the specified target cell due to traffic load. This item is used to indicate the frequency that the current cell initiates the handovers to the specified target cell due to traffic load. This item together with Successful outgoing inter cell handovers for traffic load can be used to know the performance of such handover from the current cell to the specified target cell can be known. See Attempted outgoing inter cell handovers .

Note:





297



message.


adjacent cell. This item is measured when the source cell (the current cell) sends an Intercell Handover Request message to the specified target cell due to traffic load after the handover algorithm decision.

2) In inter BSC handover procedure, the target cell is the registered adjacent cell. In the case the source cell initiates handover due to traffic load, This item is measured when the source cell (the current cell) receives the HANDOVER COMMAND message from MSC, as shown in Figure 3-1 F1.

Formula: none

VIII. Attempted outgoing inter cell handovers for response to MSC

Description: when BSC initiates a handover, it will receive Handover Indication message containing "handover cause" from LAPD module. The attempted handovers are measured according to the different handover causes in this message. This item is used to measure the attempted handovers (internal intercell handover or inter BSC handover, determined by the source cell and target cell) that the source cell initiates to the target cell for Response to MSC invocation (MSC sends a HANDOVER CANDIDATE EQUIRY message to BSC which causes handovers of multiple MSs in a cell.). This item is used to indicate the frequency that the current cell initiates the handovers to the specified target cell for response to MSC. This item together with Successfuloutgoing inter cell handovers for response to MSC can be used to know the performance of such handover from the current cell to the specified target cell can be known. See Attempted outgoing inter cell handovers .

Note:






message.

Measurement point:

298


1) In internal intercell handover procedure, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) sends an Intercell Handover Request message to the target cell for response to MSC after the handover algorithm decision.

2) In inter BSC handover procedure, the target cell is the registered adjacent cell. In the case the source cell initiates handover for response to MSC, This item is measured when the source cell (the current cell) receives the HANDOVER COMMAND message from MSC, as shown in Figure 3-1 F1.

Formula: none

IX. Attempted outgoing inter cell handovers for O&M intervention

Description: when BSC initiates a handover, it will receive Handover Indication message containing "handover cause" from LAPD module. The attempted handovers are measured according to the different handover causes in this message. This item is used to measure the attempted handovers (internal intercell handover or inter BSC handover, determined by the source cell and target cell) that the current cell initiates to the specified target cell due to O&M intervention (the handover is due to the operation on O&M console, such as forced handover, blocking without call drop (blocking channels, TRXs, and cells, etc.; or BCCH/TRX mutual assistance). This item is used to indicate the frequency that the current cell initiates the handovers to the specified target cell due to O&M intervention. This item together with Successful outgoing intercell handovers for O&M intervention can be used to know the performance of such handover from the current cell to the specified target cell can be known. See Attempted outgoing inter cell handovers .

Note:






message.


adjacent cell. This item is measured when the source cell (the current cell) sends an Intercell Handover Request message to the specified target cell due to O&M intervention after the handover algorithm decision.

299


2) In inter BSC handover procedure, the target cell is the registered adjacent cell. In the case the source cell initiates handover due to O&M intervention, This item is measured when the source cell (the current cell) receives the HANDOVER COMMAND message from MSC, as shown in Figure 3-1 F1.

Formula: none

X. Attempted outgoing inter cell handovers for better cell

Description: when BSC initiates a handover, it will receive Handover Indication message containing "handover cause" from LAPD module. The attempted handovers are measured according to the different handover causes in this message. This item is used to measure the attempted handovers (internal intercell handover or inter BSC handover, determined by the source cell and target cell) that the current cell initiates to the specified target cell due to "better cell" (the adjacent cell with lower path loss (PBGT) or higher priority). This item is used to indicate the frequency that the current cell initiates the handovers to the specified target cell due to "better cell". This item together with Successfuloutgoing inter cell handovers for better cell can be used to know the performance of such handover from the current cell to the specified target cell can be known. See Attempted outgoing inter cell handovers .

Note:






message.


adjacent cell. This item is measured when the source cell (the current cell) sends an Intercell Handover Request message to the specified target cell due to "better cell" after the handover algorithm decision.

2) In inter BSC handover procedure, the target cell is the registered adjacent cell. In the case the source cell initiates handover due to "better cell", This item is measured when the source cell (the current cell) receives the HANDOVER COMMAND message from MSC, as shown in Figure 3-1 F1.

Formula: none

300


XI. Attempted outgoing inter cell handovers for rapid level drop

Description: when BSC initiates a handover, it will receive Handover Indication message containing "handover cause" from LAPD module. The attempted handovers are measured according to the different handover causes in this message. This item is used to measure the attempted handovers (internal intercell handover or inter BSC handover, determined by the source cell and target cell) that the current cell initiates to the specified target cell due to rapid level drop. This item is used to indicate the frequency that the current cell initiates the handovers to the specified target cell due to rapid level drop. This item together with Successful outgoing inter cell handovers for rapid level drop can be used to know the performance of such handover from the current cell to the specified target cell can be known. See Attempted outgoing inter cellhandovers .

Note:






message.


adjacent cell. This item is measured when the source cell (the current cell) sends an Intercell Handover Request message to the specified target cell due to rapid level drop after the handover algorithm decision.

2) In inter BSC handover procedure, the target cell is the registered adjacent cell. In the case the source cell initiates handover due to rapid level drop, This item is measured when the source cell (the current cell) receives the HANDOVER COMMAND message from MSC, as shown in Figure 3-1 F1.

Formula: none

XII. Attempted outgoing inter cell handovers for directed retry

Description: when BSC initiates a handover, it will receive Handover Indication message containing " handover cause" from LAPD module. The attempted handovers are measured according to the different handover causes in this message. This item is used to measure the attempted handovers (internal

301


intercell handover or inter BSC handover, determined by the source cell and target cell) that the current cell initiates to the specified target cell due to directed retry (a handover is triggered for the current cell is congested during

the process of assignment ）. This item is used to indicate the frequency that the current cell initiates the handovers to the specified target cell due to directed retry. This item together with Successful outgoing inter cell handoversfor directed retry can be used to know the performance of such handover from the current cell to the specified target cell can be known. See Attemptedoutgoing inter cell handovers .

302


Note:






message.


adjacent cell. This item is measured when the source cell (the current cell) sends an Intercell Handover Request message to the specified target cell due to directed retry after the handover algorithm decision.

2) In inter BSC handover procedure, the target cell is the registered adjacent cell. In the handover initiated by the source cell (the current cell) due to directed retry, This item is measured when the source cell (the current cell) receives the HANDOVER COMMAND message from MSC, as shown in Figure 3-1 F1.

Formula: none

XIII. Attempted outgoing inter cell handovers for other causes

Description: when BSC initiates a handover, it will receive Handover Indication message containing " handover cause" from LAPD module. The attempted handovers are measured according to the different handover causes in this message. This item is used to measure the attempted handovers (internal intercell handover or inter BSC handover, determined by the source cell and target cell) that the current cell initiates to the specified target cell due to other causes (such as fast moving and handover cause being abnormal value). This item is used to indicate the frequency that the current cell initiates the handovers to the specified target cell due to other causes. This item together with Successful outgoing inter cell handovers for other causes can be used to know the performance of such handover from the current cell to the specified target cell can be known. See Attempted outgoing inter cell handovers .

303


Note:






message.


adjacent cell. This item is measured when the source cell (the current cell) sends an Intercell Handover Request message to the specified target cell due to other causes (such as fast moving and handover cause unknown) after the handover algorithm decision.

2) In inter BSC handover procedure, the target cell is the registered adjacent cell. In the case the source cell initiates handover due to other causes (such as fast moving and handover cause unknown), This item is measured when the source cell (the current cell) receives the HANDOVER COMMAND message from MSC, as shown in Figure 3-1 F1.

Formula: none

XIV. Attempted extended inter cell outgoing cell handovers for minimum timing advance

Description: when BSC initiates a handover, it will receive Handover Indication message containing " handover cause" from LAPD module. The attempted handovers are measured according to the different handover causes in this message. This item is used to measure the attempted handovers (internal intercell handover or inter BSC handover, determined by the source cell and target cell) that the current cell (single timeslot extended cell) initiates to the specified target cell due to the minimum timing advance. This item is used to indicate the frequency that the current cell (single timeslot extended cell) initiates the handover due to the minimum timing advance. This item together with Successful outgoing inter cell handovers in the extended cell (minimumtiming advance) can be used to know the performance of such handover from the current cell to the specified target cell. See Attempted outgoing intercell handovers .

Measurement point: In single timeslot extended cell (the current cell), this item is measured when the current cell sends an Intercell Handover Request

304


message (for internal intercell handover) due to the minimum timing advance after the handover algorithm decision.

Formula: none

XV. Successful outgoing inter cell handovers

Description: the successful handovers for the MS initiates from the current cell to the specified target cell. If the target cell and the current cell are in different BSCs, the handover is interBSC handover; otherwise the handover is internal intercell handover. This item together with Attempted outgoing inter cellhandovers can be used to know the performance of such handover from the current cell to the target cell. See Successful outgoing internal inter cellhandovers , Successful outgoing interBSC inter cell handovers .

Note:






message.


adjacent cell. This item is measured when the source cell (the current cell) receives the Inter Clear Request message (cause: internal intercell handover success) from the target cell.

2) In interBSC handover procedure, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the CLEAR COMMAND message (cause: handover success) from MSC, as shown in Figure 3-1 E1.

Formula: none

305


MS BSC2BSC1 MSC/VLR

HANDOVER REQUIRED

HANDOVER REQUEST

HANDOVER REQ ACK

HANDOVER COMMAND


HANDOVER COMPLETE

CLEAR COMPLETEA1, B1, C1, D1, E1

CLEAR COMMAND

A1: Successful outgoing interbsc inter cell handovers

B1: Successful outgoing interbsc inter cell handovers (to 900)

C1: Successful outgoing interbsc inter cell handovers (to 1800)


E1: Successful outgoing inter cell handovers (including various causes)

Figure 3-1 Successful outgoing interBSC inter cell handovers

XVI. Successful outgoing inter cell handovers for uplink quality

Description: the successful handovers that the MS initiates from the current cell to the specified target cell due to uplink quality. If the target cell and the current cell are in different BSCs, the handover is interBSC handover; otherwise the handover is internal intercell handover. For internal intercell handover, the handover cause is carried in the HANDOVER PERFORMED message sent to MSC, for interBSC handover, it is carried in the corresponding HANDOVER REQUIRED message. This item together with Attempted outgoing inter cell handovers for uplink quality can be used to know the performance of such handover. See Successful outgoing inter cellhandovers .

Note:





306



message.

Measurement point: 1) In internal intercell handover procedure due to uplink quality, the target

cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the Intercell Handover Request message (cause: internal intercell handover success) from the target cell.

2) In inter BSC handover due to uplink quality, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the CLEAR COMMAND message (cause: handover success) from MSC, as shown in Figure 3-1 E1.

Formula: none

XVII. Successful outgoing inter cell handovers for downlink quality

Description: the successful handovers that the MS initiates from the current cell to the specified target cell due to downlink quality. If the target cell and the current cell are in different BSCs, the handover is inter BSC handover, otherwise the handover is internal intercell handover. For internal intercell handover, the handover cause is carried in HANDOVER PERFORMED message sent to MSC, while the cause for inter BSC handover is carried in the corresponding HANDOVER REQUIRED message. This item together with Attempted outgoing inter cell handovers for downlink quality can be used to know the performance of such handover. See Successful outgoing inter cellhandovers .

Note:






message.

Measurement point: 1) In internal intercell handover procedure due to downlink quality, the target

cell is the registered adjacent cell. This item is measured when the source

307


cell (the current cell) receives the Intercell Handover Request message (cause: internal intercell handover success) from the target cell.

2) In inter BSC handover due to downlink quality, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the CLEAR COMMAND message (cause: handover success) from MSC, as shown in Figure 3-1 E1.

Formula: none

XVIII. Successful outgoing inter cell handovers for uplink strength

Description: the successful handovers that the MS initiates from the current cell to the specified target cell due to uplink strength. If the target cell and the current cell are in different BSCs, the handover is inter BSC handover, otherwise the handover is internal intercell handover. For internal intercell handover, the handover cause is carried in HANDOVER PERFORMED message sent to MSC, while the cause for inter BSC handover is carried in the corresponding HANDOVER REQUIRED message. This item together with Attempted outgoing inter cell handovers for uplink strength can be used to know the performance of such handover. See Successful outgoing inter cellhandovers .

Note:






message.

Measurement point: 1) In internal intercell handover procedure due to uplink strength, the target


2) In inter BSC handover due to uplink strength, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the CLEAR COMMAND message (cause: handover success) from MSC, as shown in Figure 3-1 E1.

Formula: none

308


XIX. Successful outgoing inter cell handovers for downlink strength

Description: the successful handovers that the MS initiates from the current cell to the specified target cell due to downlink strength. If the target cell and the current cell are in different BSCs, the handover is inter BSC handover, otherwise the handover is internal intercell handover. For internal intercell handover, the handover cause is carried in HANDOVER PERFORMED message sent to MSC, while the cause for inter BSC handover is carried in the corresponding HANDOVER REQUIRED message. This item together with Attempted outgoing inter cell handovers for downlink strength can be used to know the performance of such handover. See Successful outgoing inter cellhandovers .

Note:






message.

Measurement point: 1) In internal intercell handover procedure due to downlink strength, the

target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the Intercell Handover Request message (cause: internal intercell handover success) from the target cell.

2) In inter BSC handover due to downlink strength, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the CLEAR COMMAND message (cause: handover success) from MSC, as shown in Figure 3-1 E1.

Formula: none

XX. Successful outgoing inter cell handovers for timing advance

Description: the successful handovers that the MS initiates from the current cell to the specified target cell due to timing advance. If the target cell and the current cell are in different BSCs, the handover is inter BSC handover, otherwise the handover is internal intercell handover. For internal intercell handover, the handover cause is carried in HANDOVER PERFORMED message sent to MSC, while the cause for inter BSC handover is carried in the corresponding HANDOVER REQUIRED message. This item together with Attempted outgoing inter cell handovers for timing advance can be used to

309


know the performance of such handover. See Successful outgoing inter cellhandovers .

Note:






message.

Measurement point: 1) In internal intercell handover procedure due to timing advance, the target


2) In inter BSC handover due to timing advance, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the CLEAR COMMAND message (cause: handover success) from MSC, as shown in Figure 3-1 E1.

Formula: none

XXI. Successful outgoing inter cell handovers for traffic load

Description: the successful handovers that the MS initiates from the current cell to the specified target cell due to traffic load. If the target cell and the current cell are in different BSCs, the handover is inter BSC handover, otherwise the handover is internal intercell handover. For internal intercell handover, the handover cause is carried in HANDOVER PERFORMED message sent to MSC, while the cause for inter BSC handover is carried in the corresponding HANDOVER REQUIRED message. This item together with Attempted outgoing inter cell handovers for traffic load can be used to know the performance of such handover. See Successful outgoing inter cellhandovers .

Note:



310





message.

Measurement point: 1) In internal intercell handover procedure due to traffic load, the target cell is

the registered adjacent cell. This item is measured when the source cell (the current cell) receives the Intercell Handover Request message (cause: internal intercell handover success) from the target cell.

2) In inter BSC handover due to traffic load, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the CLEAR COMMAND message (cause: handover success) from MSC, as shown in Figure 3-1 E1.

Formula: none

XXII. Successful outgoing inter cell handovers for response to MSC

Description: the successful handovers that the MS initiates from the current cell to the specified target cell for response to MSC. If the target cell and the current cell are in different BSCs, the handover is inter BSC handover, otherwise the handover is internal intercell handover. For internal intercell handover, the handover cause is carried in HANDOVER PERFORMED message sent to MSC, while the cause for inter BSC handover is carried in the corresponding HANDOVER REQUIRED message. This item together with Attempted outgoing inter cell handovers for response to MSC can be used to know the performance of such handover. See Successful outgoing inter cellhandovers .

Note:






message.

Measurement point:

311


1) In internal intercell handover for response to MSC, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the Intercell Handover Request message (cause: internal intercell handover success) from the target cell.

2) In inter BSC handover for response to MSC, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the CLEAR COMMAND message (cause: handover success) from MSC, as shown in Figure 3-1 E1.

Formula: none

XXIII. Successful outgoing inter cell handovers for O&M intervention

Description: the successful handovers that the MS initiates from the current cell to the specified target cell due to the operation on O&M console, such as forced switchover, blocking without call drop (blocking channel, TRX, and cell, etc.; or main BCCH/TRX mutual assistance. If the target cell and the current cell are in different BSCs, the handover is inter BSC handover, otherwise the handover is internal intercell handover. For internal intercell handover, the handover cause is carried in HANDOVER PERFORMED message sent to MSC, while the cause for inter BSC handover is carried in the corresponding HANDOVER REQUIRED message. This item together with Attemptedoutgoing inter cell handovers for O&M intervention can be used to know the performance of such handover. See Successful outgoing inter cellhandovers .

Note:






message.

Measurement point: 1) In internal intercell handover for O&M intervention, the target cell is the

registered adjacent cell. This item is measured when the source cell (the current cell) receives the Intercell Handover Request message (cause: internal intercell handover success) from the target cell.

2) In inter BSC handover for O&M intervention, the target cell is the registered adjacent cell. This item is measured when the source cell (the

312


current cell) receives the CLEAR COMMAND message (cause: handover success) from MSC, as shown in Figure 3-1 E1.

Formula: none

XXIV. Successful outgoing inter cell handovers for better cell

Description: the successful handovers that the MS initiates from the current cell to the specified target cell due to " better cell". If the target cell and the current cell are in different BSCs, the handover is inter BSC handover, otherwise the handover is internal intercell handover. For internal intercell handover, the handover cause is carried in HANDOVER PERFORMED message sent to MSC, while the cause for inter BSC handover is carried in the corresponding HANDOVER REQUIRED message. This item together with Attempted outgoing inter cell handovers for better cell can be used to know the performance of such handover. See Successful outgoing inter cellhandovers .

Note:






message.

Measurement point: 1) In internal intercell handover procedure due to "better cell", the target cell

is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the Intercell Handover Request message (cause: internal intercell handover success) from the target cell.

2) In inter BSC handover due to "better cell", the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the CLEAR COMMAND message (cause: handover success) from MSC, as shown in Figure 3-1 E1.

Formula: none

XXV. Successful outgoing inter cell handovers for rapid level drop

Description: the successful handovers that the MS initiates from the current cell to the specified target cell due to rapid level drop. If the target cell and the current cell are in different BSCs, the handover is inter BSC handover, otherwise the handover is internal intercell handover. For internal intercell

313


handover, the handover cause is carried in HANDOVER PERFORMED message sent to MSC, while the cause for inter BSC handover is carried in the corresponding HANDOVER REQUIRED message. This item together with Attempted outgoing inter cell handovers for rapid level drop can be used to know the performance of such handover. See Successful outgoing inter cellhandovers .

Note:






message.

Measurement point:1) In internal intercell handover procedure due to rapid level drop, the target


2) In inter BSC handover due to rapid level drop, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the CLEAR COMMAND message (cause: handover success) from MSC, as shown in Figure 3-1 E1.

Formula: none

XXVI. Successful outgoing inter cell handovers for directed retry

Description: the successful handovers that the MS initiates from the current cell to the specified target cell due to directed retry. If the target cell and the current cell are in different BSCs, the handover is inter BSC handover, otherwise the handover is internal intercell handover. For internal intercell handover, the handover cause is carried in HANDOVER PERFORMED message sent to MSC, while the cause for inter BSC handover is carried in the corresponding HANDOVER REQUIRED message. This item together with Attempted outgoing inter cell handovers for directed retry can be used to know the performance of such handover. See Successful outgoing inter cellhandovers .

314


Note:






message.

Measurement point: 1) In internal intercell handover procedure due to directed retry, the target


2) In inter BSC handover due to directed retry, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the CLEAR COMMAND message (cause: handover success) from MSC, as shown in Figure 3-1 E1.

Formula: none

XXVII. Successful outgoing inter cell handovers for other causes

Description: the successful handovers that the MS initiates from the current cell to the specified target cell due to other causes (such as fast moving and handover cause unknown). If the target cell and the current cell are in different BSCs, the handover is inter BSC handover, otherwise the handover is internal intercell handover. For internal intercell handover, the handover cause is carried in HANDOVER PERFORMED message sent to MSC, while the cause for inter BSC handover is carried in the corresponding HANDOVER REQUIRED message. This item together with Attempted outgoing inter cellhandovers for other causes can be used to know the performance of such handover. See Successful outgoing inter cell handovers .

Note:






message.

315


Measurement point: 1) In internal intercell handover procedure due to other causes (such as fast

moving and handover cause unknown), the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the Intercell Handover Request message (cause: internal intercell handover success) from the target cell.

2) In inter BSC handover due to other causes (such as fast moving and handover cause unknown), the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the CLEAR COMMAND message (cause: handover success) from MSC, as shown in Figure 3-1 E1.

Formula: none

XXVIII. Successful outgoing inter cell handovers in the extended cell (minimum timing advance)

Description: The successful handovers due to minimum timing advance in single timeslot extended cell. The handover is internal intracell handover. The handover cause is carried in HANDOVER PERFROMED message sent to MSC. This item together with Attempted extended inter cell outgoing cellhandovers for minimum timing advance can be used to know the performance of such handover. See Successful outgoing inter cellhandovers .

Measurement point: In single timeslot extended cell (the current cell), after the MS successfully accesses the target channel during the internal intracell handover due to the minimum timing advance, the current cell sends a HANDOVER PERFORMED message to MSC. This item is measured when the current cell sends this message.

Formula: none

XXIX. Unsuccessful outgoing cell handover with successful reversion

Description: after the source cell sends a HANDOVER COMMAND message to the MS, if the MS cannot access the specified target cell due to the causes, such as poor radio environment or handover parameter error, the MS sends a HANDOVER FAILURE message (cause: Radio interface failure, reversion to old channel) to the source cell on the original channel. Upon reception of this message, the source cell informs the target cell to clear the related handover resource and MS restores the connection in the source cell. In the handover with the current cell serving as the source cell (the target cell is the specified cell), this item is used to measure the number of the above mentioned occasions, i.e., successful reversions after the handover failure. If the target

316


cell and the current cell are in different BSCs, the handover is interBSC handover; otherwise the handover is internal intercell handover. See Unsuccessful outgoing cell handover with unsuccessful reversion , Unsuccessful internal inter cell handovers with successful reversions , and Unsuccessful outgoing BSC handovers with successful reversion .

Measurement point: 1) In internal intercell handover, the target cell is the registered adjacent cell.

This item is measured when the source cell (the current cell) receives the HANDOVER FAILURE message (cause: Radio interface failure, reversion to old channel) from the MS, as shown in Figure 3-1 I1.

1) In interBSC handover, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the HANDOVER FAILURE message (cause: Radio interface failure, reversion to old channel) from the MS, as shown in Figure 3-2 C1.

317


Formula: none

MS BTS BSC MSC/VLR

HANDOVER COMPLETE

HANDOVER COMMAND

HANDOVER PERFORMED

CONN FAIL IND

New Channel

ERROR IND

Old Channel

CHANNEL ACT

A1 , F2

CONN FAIL IND

A2, F3, H1,J1

A4, F4

ERROR INDA5, F5, H2, J2

.HANDOVER FAILURE

A3, B1, C1, D1, E1, F1, G1, I1

CLEAR COMMAND

A6, F6

CLEAR COMMAND

A7, F7Old Channel

A1~A7: Unsuccessful outgoing internal inter cell handovers

B1: Unsuccessful outgoing internal inter cell handovers (channel invalid)

C1: Unsuccessful outgoing internal inter cell handovers (TA invalid)

D1: Unsuccessful outgoing internal inter cell handovers (frequency invalid)

E1: Unsuccessful outgoing internal inter cell handovers (timer expired)

F1~F7: Unsuccessful outgoing internal inter cell handovers (other causes)

G1: Unsuccessful internal inter cell handovers with successful reversions

H1~H2: Unsuccessful internal inter cell handovers with unsuccessful reversions

I1: Unsuccessful outgoing intercell handovers with successful reversions

J1~J2: Unsuccessful outgoing intercell handovers with unsuccessful reversions

Figure 3-1 Unsuccessful outgoing internal inter cell handovers

318


BTS BSC1 MSC/VLR

HANDOVER REQUIRED

HANDOVER COMMAND


A1, C1 HANDOVER FAILURE

HANDOVER FAILURE

CLEAR COMMAND

CONN FAIL IND

ERROR INDICATION

HANDOVER COMMAND

B1 , D1B2 , D2

B3 , D3



C1: Unsuccessful outgoing inter cell handovers with successful reversion

D1~D3: Unsuccessful outgoing inter cell handovers with unsuccessful reversion


XXX. Unsuccessful outgoing cell handover with unsuccessful reversion

Description: after the source cell sends a HANDOVER COMMAND message to the MS, if the connection between the MS and the target cell has not been established yet but the connection between the MS and the source cell has been disconnected due to the causes, such as poor radio environment or equipment failure, then BSC sends a CLEAR REQUEST message to MSC to request clearing the old resource and the resource involved in the handover. So this handover is unsuccessful and the original service cannot be restored. In the handover with the current cell serving as the source cell (the target cell is the specified cell), this item is used to measure the number of the above mentioned occasions, i.e., unsuccessful handover with unsuccessful reversion. If the target cell and the current cell are in different BSCs, the handover is inter BSC handover, otherwise the handover is internal intercell handover. See Unsuccessful outgoing cell handover with successful reversion , Unsuccessfulinternal inter cell handovers with successful reversions , and Unsuccessfuloutgoing BSC handovers with successful reversion .

Measurement point: 1) In internal intercell handover, the target cell is the registered adjacent cell.

This item is measured when the source cell (the current cell) receives the CONNECTION FAILURE INDICATION message from the BTS after

319


sending a HANDOVER COMMAND message to MS, as shown in Figure3-1 J1.

2) In internal intercell handover, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the ERROR INDICATION message (cause: "timer T200 expired (N200+1) times" (0x01), or "unsolicited DM response, multiple frame established state"(0x05), or "sequence error"(0x07)) from the BTS, as shown in Figure3-1 J2.

3) In internal intercell handover, after the target cell receives the HANDOVER DETECTION message, when AM/CM net-drive fails or the timer waiting for HANDOVER COMPLETE times out, it sends an Inter Clear Request message to the source cell . This item is measured when the source cell (the current cell) receives this message.

4) In internal intercell handover, the target cell is the registered adjacent cell. This item is measured when the timer for the source cell (the current cell) to wait for Inter Clear Request message after sending HANDOVER COMMAND message expires.

5) In inter BSC handover, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the CONNECTION FAILURE INDICATION message from BTS, as shown in Figure 3-2 D1.

6) In inter BSC handover, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the ERROR INDICATION message (cause: "timer T200 expired (N200+1) times" (0x01), or "unsolicited DM response, multiple frame established state" (0x05), or "sequence error"(0x07)), as shown in Figure 3-2 D2.

7) In inter BSC handover, the target cell is the registered adjacent cell. This item is measured when the source cell (the current cell) receives the CLEAR COMMAND message (cause: not handover success), as shown in Figure 3-2 D3.

8) In inter BSC handover, the target cell is the registered adjacent cell. This item is measured when the timer for the source cell to wait for the CLEAR COMMAND message (cause: handover success) from MSC expires.

Formula: none

XXXI. Outgoing inter cell handover success rate (%)

Description: The success rate of the outgoing inter cell handovers from the current cell to the specified target cell, including outgoing internal intercell handover and outgoing interBSC inter cell handover. See Attempted outgoinginter cell handovers and Successful outgoing inter cell handovers .

Measurement point: none

320


Formula: Successful outgoing inter cell handovers / Attempted outgoing inter cell handovers

3.8 Incoming Inter Cell Handover Measurement Function

3.8.1 General

The statistic items of Incoming Inter Cell Handover Measurement Function are used to know the incoming inter cell handover performance of the specified cell, such as attempted incoming inter cell handovers and successful incoming inter cell handovers. All statistic items of Incoming Inter Cell Handover Measurement Function are listed in Table 3-1 .

To know the outgoing inter cell handover performance of the specified cell, the related statistic items of Outgoing Inter Cell Handover Measurement Function should be registered.

For the statistic items of Incoming Inter Cell Handover Measurement Function, it is recommended that they should be registered at the early stage of BSC running, or be registered when the handover performance of the specified cell is to be known so that the network optimization can be performed. At the stable running stage of BSC, the task of these statistic items can be deleted. These items together with the statistic items of Outgoing Inter Cell Handover Measurement Function can be used to know the handover situation between two specified cells. The statistic cycle is recommended to be 60 minutes.

The statistic object of the statistic items of Incoming Inter Cell Handover Measurement Function is the target adjacent cell that MSs hand over to, the specified cell must be nominated as the target cell in a handover, and the statistic results about this cell will list the situations all other adjacent cell (maxnum 32 cells) handed over to the cell. All statistic items of Incoming Inter Cell Handover Measurement Function will be selected together for registration.

Table 3-1 Statistic items in Incoming Inter Cell Handover Measurement Function

No. Item name

1 Attempted incoming inter cell handovers

2 Successful incoming inter cell handovers

3 Unsuccessful incoming cell handovers (congestion)

4 Incoming inter cell handover success rate (%)

321



I. Attempted incoming inter cell handovers

Description: the incoming inter cell handover requests (including inter BSC handover and internal intercell handover) that the current cell (the target cell) receives from other cells (source cell). If source cells are different, the results and the measured objects are different and they are determined by some source cell and some target cell. This item can be used to know the frequency of the handovers that some source cell initiates to the current cell. This item together with Successful incoming inter cell handovers can be used to know the performance of the handover from this cell to the current cell. See Attempted incoming interBSC inter cell handovers , and Attempted incominginternal inter cell handovers .

Measurement point: 1) In internal intercell, a source cell will send a Intercell Handover Request

message to a target cell after the handover algorithm decision. The target cell is the registered adjacent cell. This item is measured when the target cell (the current cell) receives this message.

2) In interBSC handover, the target BSC packs the HANDOVER REQUEST message received from MSC into the IntoBSC Handover Request message, and then forwards the message to the BM where the target cell configured. This item is measured when the target cell (the current cell) receives this message.

Formula: none

II. Successful incoming inter cell handovers

Description: the successful incoming inter cell handovers (including inter BSC handover and internal intercell handover) that MS is hander over from some other cells (source cell) to the current cell (the target cell). If source cells are different, the results and the measured objects are different and they are determined by some source cell and some target cell This item together with Attempted incoming inter cell handovers can be used to know the performance of the handover from some cell to the current cell. See Attemptedincoming interBSC inter cell handovers and Attempted incoming internal intercell handovers .

Measurement point:1) In internal intercell handover (cause: directed retry), after the MS successfully

accesses the target cell (the current cell), the target cell will finally send an ASSIGNMENT COMPLETE message to MSC,this item is measured in this case, as shown in Figure 3-2 E1.

322


2) In internal intercell handover (cause: non-directed retry, such as signal quality, signal strength, TA, traffic load, rapid level drop, better cell, MSC invocation, and O&M intervention, after the MS successfully accesses the target cell (the current cell), this item is measured when the target cell will finally send a HANDOVER PERFORMED message to MSC, as shown in Figure 3-1 F1.

3) In interBSC handover, this item is measured when the target cell (the current cell) forwards HANDOVER COMPLETE message to MSC after the target cell has received this message, as shown in Figure 3-2 C1.

Formula: none

MS BTS BSC MSC/VLR

HANDOVER COMPLETE

HANDOVER COMMAND

A1, B1, C1, D1, E1

ASSIGNMENT REQUEST

ASSIGNMENT COMPLETE

A1: Successful incoming internal inter cell handovers

B1: Successful incoming internal inter cell handovers (from 900)



E1: Successful incoming inter cell handovers

Figure 3-1 Successful incoming internal inter cell handovers(directed retry)

MS BTS BSC MSC/VLR

HANDOVER COMPLETE

.HANDOVER COMMAND

HANDOVER PERFORMED

A1, B1 , C1, D1, E1, F1

A1: Successful intracell handover

B1: Successful incoming internal inter cell handovers


D1: Successful incoming internal inter cell handovers (from 1800)

E1: Successful dual-band intercell handovers

F1: Successful incoming inter cell handovers

Figure 3-2 Successful intraBSC handover (not DIRECTED RETRY)

323


MS BTS BSC MSC/VLR

HANDOVER COMPLETE

.HANDOVER DETECTION

A1, B1, C1

CHANNEL ACT

CHAN ACT ACK

HANDOVER COMPLETE

HANDOVER REQ ACK

HANDOVER REQUESTT

A1: Successful incoming inter BSC inter cell handovers

B1: Successful dual-band intercell handovers

C1: Successful incoming inter cell handovers

Figure 3-3 Successful incoming inter BSC internal inter cell handovers

III. Unsuccessful incoming cell handovers (congestion)

Description: after the current cell (target cell) has received handover request (including interBSC handover or internal intercell handover) from other cells (source cell), the current cell initiates the channel preparation procedure. If exception occurs during the channel preparation procedure, the handover will be measured as an unsuccessful handover due to channel congestion. If source cells are different, the results and the measured objects are different and they are determined by some source cell and some target cell. See Unsuccessful incoming internal inter cell handovers (no radio resourceavailable) and Unsuccessful incoming BSC handovers (no radio resourceavailable.

Measurement point: 1) In internal intercell handover, this item is measured when the exception,

such as no available channel, occurs during the target cell (the current cell) is allocating a new channel. And the target cell sends an Intercell Handover Reject message to the source cell simultaneously.

2) In interBSC handover, during the target cell (the current cell) checking the conditions for incoming BSC handover, if the check result is that there is no available channel, for example, channel request fails, This item is measured and the target cell sends a HANDOVER FAILURE message to MSC in this case.

3) In interBSC handover, the target cell (the current cell) measures this item when the timer Tqho (maximum allowed queuing time for handover) in the

324


target cell expires. And the target cell sends a HANDOVER FAILURE message to MSC simultaneously.

Formula: none

IV. Incoming inter cell handover success rate (%)

Description: the success rate of the incoming inter cell handovers (including internal intercell handover and interBSC handover) that some cell initiates to the current cell. See Attempted incoming inter cell handovers and Successfulincoming inter cell handovers.

Measurement point: none Formula: Successful incoming inter cell handovers / Attempted incoming inter

cell handovers

3.9 Undefined Adjacent Cell Measurement Function

3.9.1 General

An undefined adjacent cell is a cell which is not configured as adjacent cell in Cell Adjacent Relationship table but whose BCCH frequency is configured in BA table in BSC data configuration. Undefined Adjacent Cell Measurement Function is used to measure the information of undefined adjacent cells reported by MS. This is an effective measure to check the adjacent cells missed in configuration. It is recommended to register this measurement task at equipment deployment, and delete it after the operation of system is stable.

If the measurement results of this task indicate during the initial stage of the newly deployed equipment that the signals from some cells are strong while these cells are not configured as adjacent cells, then these cells can be configured as adjacent cells during network optimization.

The object of undefined adjacent cell measurement task is cell. User can set the module and cell of the task in the interface of Object Definition, as well as Rate limit and Level limit. In the information of undefined adjacent cell reported by MS, a unique cell is defined by BSIC and BCCH. The measurement results of an undefined adjacent cell will be displayed at the background if the ratio of number of MRs containing this undefined adjacent cell to total number of MRs containing all undefined adjacent cells equals to Rate limit, and the Average signal intensity of undefined adjacent cells is larger than or equal to Level limit. For example, in the measurement task of Cell A, Cell A has three undefined adjacent cells: N1, N2 and N3. Among the MRs reported by MS, there is one MR containing N1, one MR containing N2, eight containing N3. The Average signal intensity of N1, N2 and N3 is 25. If the Rate limit is 15, and Level limit is 20, then the MRs of N1 and N2 are 1 /

325


(1 + 1 + 8) = 10%, and MR of N3 is 8 / (1 + 1 + 8) = 80%. Therefore, only the measurement results of N3 will be displayed at background. The items of this measurement are listed in Table 3-1 .

Table 3-1 Statistic items in Undefined Adjacent Cell Measurement Function

No. Item name

1BSIC of undefined adjacent cell

2BCCH of undefined adjacent cell

3Average signal intensity of undefined adjacent cell

4Undefined adjacent cell measurement reports


I. BSIC of undefined adjacent cell

Description: MS reports to the network one MR per 480ms. If the signal of a frequency received by MS is configured in BA table of BSC, it will be reported as an adjacent cell in MR. If this cell is not configured as adjacent cell in Cell Adjacent Relationship table, its BSIC will be recorded as an undefined adjacent one. The frequencies of BSIC and BCCH can be used to identify an adjacent cell.

Measurement point: On reception of MR, BSC judges whether the record of the undefined adjacent cell in this MR already exists according to the frequencies of BSIC and BCCH. If the record already exists, the receiving level of this cell is accumulated, and Undefined adjacent cell measurement reports increases by 1. Otherwise, a new record will be created to measure BSIC; BCCH, receiving level and number of measurement reports of this undefined adjacent cell.

Formula: none.

II. BCCH of undefined adjacent cell

Description: MS reports to the network one MR per 480ms. If the signal of a frequency received by MS is configured in BA table of BSC, it will be reported as an adjacent cell in MR. If this cell is not configured as adjacent cell in Cell Adjacent Relationship table, its BCCH will be recorded as an undefined adjacent one. The frequencies of BSIC and BCCH can be used together to identify an adjacent cell.

Measurement point: On reception of MR, BSC judges whether the record of the undefined adjacent cell in this MR already exists according to the frequencies of BSIC and BCCH. If the record already exists, the receiving level

326


of this cell is accumulated, and Undefined adjacent cell measurement reports increases by 1. Otherwise, a new record will be created to measure BSIC, BCCH, receiving level and number of measurement reports of this undefined adjacent cell.

Formula: none.

III. Average signal intensity of undefined adjacent cell

Description: MS reports to the network one MR per 480ms. If the signal of a frequency received by MS is configured in BA table of BSC, it will be reported as an adjacent cell in MR. If this cell is not configured as adjacent cell in Cell Adjacent Relationship table, its signal intensity will be recorded as an undefined adjacent one. If the average signal intensity is large, it may be necessary to adjust the coverage or adjacent cells.

Measurement point: On reception of MR, BSC judges whether the record of the undefined adjacent cell in this MR already exists according to the frequencies of BSIC and BCCH. If the record already exists, the receiving level of this cell is accumulated, and Undefined adjacent cell measurement reports increases by 1. The value of this item is got by dividing the sum of the accumulated receiving level with Undefined adjacent cell measurement reports. Otherwise, a new record will be created to measure BSIC, BCCH, receiving level and number of measurement reports of this undefined adjacent cell.

Formula: none.

IV. Undefined adjacent cell measurement reports

Description: MS reports to the network one MR per 480ms. If the signal of a frequency received by MS is configured in BA table of BSC, it will be reported as an adjacent cell in MR. If this cell is not configured as adjacent cell in Cell Adjacent Relationship table, the number of MRs containing this cell will be measured.

Measurement point: On reception of MR, BSC judges whether the record of the undefined adjacent cell in this MR already exists according to the frequencies of BSIC and BCCH. If the record already exists, the receiving level of this cell is accumulated, and the value of this item increases by 1. Otherwise, a new record will be created to measure BSIC, BCCH, receiving level and number of measurement reports of this undefined adjacent cell.

Formula: none.

327


3.10 Defined Adjacent Cell Measurement Function

3.10.1 General

A defined adjacent cell is a cell which is configured as adjacent cell in Cell Adjacent Relationship table and whose BCCH frequency is configured in BA table in BSC data configuration. Defined Adjacent Cell Measurement Function is used to measure the information of defined adjacent cells reported by MS. This is an effective measure to check the redundant adjacent cells. It is recommended to register this measurement task at equipment deployment, and delete it after the operation of system is stable.

The measurement results of this measurement function can be the basis of the network optimization.

The object of defined adjacent cell measurement task is cell. User can set the module and cell of the task in the interface of Object Definition, as well as Rate limit and Level limit. In the information of defined adjacent cell reported by MS, a unique cell is defined by BSIC and BCCH. The measurement results of an defined adjacent cell will be displayed at the background if the ratio of number of MRs containing this defined adjacent cell to total number of MRs containing all defined adjacent cells equals to Rate limit, and the Average signal intensity of defined adjacent cells is larger than or equal to Level limit. For example, in the measurement task of Cell A, Cell A has three defined adjacent cells: N1, N2 and N3. Among the MRs reported by MS, there is one MR containing N1, one MR containing N2, eight containing N3. The Average signal intensity of N1, N2 and N3 is 25. If the Rate limit is 15, and Level limit is 20, then the MRs of N1 and N2 are 1 / (1 + 1 + 8) = 10%, and MR of N3 is 8 / (1 + 1 + 8) = 80%. Therefore, only the measurement results of N3 will be displayed at background. The items of this measurement are listed in Table 3-1 .

Table 3-1 Statistic items in Defined Adjacent Cell Measurement Function

No. Item name

1BSIC of defined adjacent cell

2BCCH of defined adjacent cell

3Average signal intensity of defined adjacent cell

4Defined adjacent cell measurement reports

328



I. BSIC of defined adjacent cell

Description: MS reports to the network one MR per 480ms. If the signal of a frequency received by MS is configured in BA table of BSC, it will be reported as an adjacent cell in MR. If this cell is configured as adjacent cell in Cell Adjacent Relationship table, its BSIC will be recorded as an undefined adjacent one. The frequencies of BSIC and BCCH can be used to identify an adjacent cell.

Measurement point: On reception of MR, BSC judges whether the record of the defined adjacent cell in this MR already exists according to the frequencies of BSIC and BCCH. If the record already exists, the receiving level of this cell is accumulated, and Defined adjacent cell measurement reports increases by 1. Otherwise, a new record will be created to measure BSIC, BCCH, receiving level and number of measurement reports of this defined adjacent cell.

Formula: none.

II. BCCH of defined adjacent cell

Description: MS reports to the network one MR per 480ms. If the signal of a frequency received by MS is configured in BA table of BSC, it will be reported as an adjacent cell in MR. If this cell is configured as adjacent cell in Cell Adjacent Relationship table, its BCCH will be recorded as a defined adjacent one. The frequencies of BSIC and BCCH can be used together to identify an adjacent cell.

Measurement point: On reception of MR, BSC judges whether the record of the defined adjacent cell in this MR already exists according to the frequencies of BSIC and BCCH. If the record already exists, the receiving level of this cell is accumulated, and defined adjacent cell measurement reports increases by 1. Otherwise, a new record will be created to measure BSIC, BCCH, receiving level and number of measurement reports of this defined adjacent cell.

Formula: none.

III. Average signal intensity of defined adjacent cell

Description: MS reports to the network one MR per 480ms. If the signal of a frequency received by MS is configured in BA table of BSC, it will be reported as an adjacent cell in MR. If this cell is configured as adjacent cell in Cell Adjacent Relationship table, its signal intensity will be recorded as a defined adjacent one. If the average signal intensity is large, it may be necessary to adjust the coverage or adjacent cells.

Measurement point: On reception of MR, BSC judges whether the record of the defined adjacent cell in this MR already exists according to the frequencies

329


of BSIC and BCCH. If the record already exists, the receiving level of this cell is accumulated, and Defined adjacent cell measurement reports increases by 1. The value of this item is got by dividing the sum of the accumulated receiving level with Defined adjacent cell measurement reports. Otherwise, a new record will be created to measure BSIC, BCCH, receiving level and number of measurement reports of this defined adjacent cell.

Formula: none.

IV. Defined adjacent cell measurement reports

Description: MS reports to the network one MR per 480ms. If the signal of a frequency received by MS is configured in BA table of BSC, it will be reported as an adjacent cell in MR. If this cell is configured as adjacent cell in Cell Adjacent Relationship table, the number of MRs containing this cell will be measured.

Measurement point: On reception of MR, BSC judges whether the record of the defined adjacent cell in this MR already exists according to the frequencies of BSIC and BCCH. If the record already exists, the receiving level of this cell is accumulated, and the value of this item increases by 1. Otherwise, a new record will be created to measure BSIC, BCCH, receiving level and number of measurement reports of this defined adjacent cell.

Formula: none.

3.10 Receiving Quality Measurement

3.10.1 General

The valid MRs received by BSC contains the values of uplink and downlink receiving quality rank. The receiving quality can be indicated with eight ranks: 0~7. Each rank corresponds to a BER range, as shown in Table 3-4 . Rank 0 has the lowest BER, i.e. the best receiving quality, while Rank 7 has the highest BER, i.e. the lowest receiving quality.

Table 3-4 Receiving quality level and BER correspondence

Receiving quality level BER

0 < 0.2%

1 0.2 ~ 0.4%

2 0.4 ~ 0.8%

3 0.8 ~ 1.6%

4 1.6 ~ 3.2%

5 3.2 ~ 6.4%

330


6 6.4 ~ 12.8%

7 > 12.8%

"Receiving quality measurement", on the basis of the valid MRs or pre-processed MRs received within the measurement period, measures the times of the receiving quality being in various ranks, and indicates the measured cell's uplink and downlink receiving quality rank distribution. These items indicate absolute times, so when a valid pre-processing MR is received, it is necessary to provide the actual times of the receiving signal being in various receiving quality ranks according to the frequency of reporting valid pre-processing MRs. The results of "Receiving quality measurement", adding with the results of "receiving level measurement", can be used to analyze the cell's radio signal coverage and interference.

The object of "Receiving quality measurement" is TRX. In the object definition interface, user can specify TRXs by giving the module No., cell No. and TRX No. in a task, or just register all TRXs within the cell.

This measurement can be divided into "full rate receiving quality measurement" and "half rate receiving quality measurement".

3.10.2 Full Rate Receiving Quality Measurement

The measurement items of full rate receiving quality measurement are listed in Table 3-5 .

Table 3-5 Full rate receiving quality measurement items

No. Item name

1Average uplink receiving quality 0 in Full Rate TCH








9Average downlink receiving quality 0 in Full Rate TCH






331




I. Average uplink receiving quality 0 in Full Rate TCH

Meaning: If BSC receives a valid MR on full rate TCH in which the uplink receiving quality is 0, this item increases by 1. If BSC receives a valid pre-processing MR on full rate TCH in which the uplink quality receiving is 0, then the frequency in the report is added to this item.

Measurement point: This item is measured when BSC receives a valid MR or a valid pre-processing MR in which the uplink receiving quality is 0.

Formula: None.

II. Average uplink receiving quality 1 in Full Rate TCH



Formula: None.

III. Average uplink receiving quality 2 in Full Rate TCH



Formula: None.

IV. Average uplink receiving quality 3 in Full Rate TCH



Formula: None.

332


V. Average uplink receiving quality 4 in Full Rate TCH



Formula: None.

VI. Average uplink receiving quality 5 in Full Rate TCH



Formula: None.

VII. Average uplink receiving quality 6 in Full Rate TCH



Formula: None.

VIII. Average uplink receiving quality 7 in Full Rate TCH



Formula: None.

IX. Average downlink receiving quality 0 in Full Rate TCH

Meaning: If BSC receives a valid MR on full rate TCH in which the downlink receiving quality is 0, this item increases by 1. If BSC receives a valid pre-processing MR on full rate TCH in which the downlink quality receiving is 0, then the frequency in the report is added to this item.

333


Measurement point: This item is measured when BSC receives a valid MR or a valid pre-processing MR in which the downlink receiving quality is 0.

Formula: None.

X. Average downlink receiving quality 1 in Full Rate TCH



Formula: None.

XI. Average downlink receiving quality 2 in Full Rate TCH



Formula: None.

XII. Average downlink receiving quality 3 in Full Rate TCH



Formula: None.

XIII. Average downlink receiving quality 4 in Full Rate TCH



Formula: None.

334


XIV. Average downlink receiving quality 5 in Full Rate TCH



Formula: None.

XV. Average downlink receiving quality 6 in Full Rate TCH



Formula: None.

XVI. Average downlink receiving quality 7 in Full Rate TCH



Formula: None.

3.10.3 Half Rate Receiving Quality Measurement


Table 3-6 Half rate receiving quality measurement

No. Item name

1Average uplink receiving quality 0 in Half Rate TCH






335




9Average downlink receiving quality 0 in Half Rate TCH








I. Average uplink receiving quality 0 in Half Rate TCH

Meaning: If BSC receives a valid MR on half rate TCH in which the uplink receiving quality is 0, this item increases by 1. If BSC receives a valid pre-processing MR on half rate TCH in which the uplink quality receiving is 0, then the frequency in the report is added to this item.


Formula: None.

II. Average uplink receiving quality 1 in Half Rate TCH



Formula: None.

III. Average uplink receiving quality 2 in Half Rate TCH



Formula: None.

336


IV. Average uplink receiving quality 3 in Half Rate TCH



Formula: None.

V. Average uplink receiving quality 4 in Half Rate TCH



Formula: None.

VI. Average uplink receiving quality 5 in Half Rate TCH



Formula: None.

VII. Average uplink receiving quality 6 in Half Rate TCH



Formula: None.

VIII. Average uplink receiving quality 7 in Half Rate TCH


337



Formula: None.

IX. Average downlink receiving quality 0 in Half Rate TCH

Meaning: If BSC receives a valid MR on half rate TCH in which the downlink receiving quality is 0, this item increases by 1. If BSC receives a valid pre-processing MR on half rate TCH in which the downlink quality receiving is 0, then the frequency in the report is added to this item.


Formula: None.

X. Average downlink receiving quality 1 in Half Rate TCH



Formula: None.

XI. Average downlink receiving quality 2 in Half Rate TCH



Formula: None.

XII. Average downlink receiving quality 3 in Half Rate TCH



Formula: None.

338


XIII. Average downlink receiving quality 4 in Half Rate TCH



Formula: None.

XIV. Average downlink receiving quality 5 in Half Rate TCH



Formula: None.

XV. Average downlink receiving quality 6 in Half Rate TCH



Formula: None.

XVI. Average downlink receiving quality 7 in Half Rate TCH



Formula: None.

339


3.11 Receiving Level Measurement Function

3.11.1 General

The valid MRs BSC receives contain the rank information of uplink receiving level, downlink receiving level, uplink receiving quality and downlink receiving quality.

Receiving level can be divided into 6 ranks: 0~5. Each rank corresponds to a range of receiving level. As shown in Table 3-7 , higher rank suggests higher receiving level.

Table 3-7 Correspondence between receiving levels and their ranks

Receiving level ranks Receiving level (dBm)

0 ≤-100

1 -99 ~ -95

2 -94 ~ -90

3 -89 ~ -80

4 -79 ~ -70

5 ≥-69

The receiving quality can be indicated with eight ranks: 0~7. Each rank corresponds to a BER range, as shown in Table 3-8 . Rank 0 has the lowest BER, i.e. the best receiving quality, while Rank 7 has the highest BER, i.e. the lowest receiving quality.

Table 3-8 Correspondence between receiving quality ranks and BER

Receiving quality rank BER

0 < 0.2%

1 0.2 ~ 0.4%

2 0.4 ~ 0.8%

3 0.8 ~ 1.6%

4 1.6 ~ 3.2%

5 3.2 ~ 6.4%

6 6.4 ~ 12.8%

7 > 12.8%

"Receiving level measurement", on the basis of the valid MRs or pre-processed MRs received within the measurement period, measures the times of the receiving

340


level and receiving quality being in various ranks, and indicates the measured cell's uplink and downlink receiving level and receiving quality rank distribution. These items indicate absolute times, so when a valid pre-processing MR is received, it is necessary to provide the actual times of the receiving signal being in various receiving level and receiving quality ranks according to the frequency of reporting valid pre-processing MRs.

The results of "receiving level measurement" and "receiving quality measurement" can be used together to analyze radio signal coverage and interference of a cell. For example, if there are too many times of high level and low quality, it can be concluded that interference exists; if there are too many times of low level and low quality, it can be concluded that coverage problem exists. These results are useful in locating the faults in the transceving channels in TRX, antenna feeder.

The object of "Receiving level measurement" is TRX. In the object definition interface, user can specify TRXs by giving the module No., cell No. and TRX No. in a task, or just register all TRXs within the cell.

This measurement can be divided into "full rate receiving level measurement" and "half rate receiving level measurement".

3.11.2 Full Rate Receiving Level Measurement


Table 3-9 Items of full rate receiving level measurement

No. Item name

1Uplink receiving level rank 0 and receiving quality rank 0 in Full Rate TCH














341




































49Downlink receiving level rank 0 and receiving quality rank 0 in Full Rate TCH






342










































343




I. Uplink receiving level rank 0 and receiving quality rank 0 in Full Rate TCH

Meaning: If BSC receives a valid MR on full rate TCH in which the uplink receiving level is 0 and uplink receiving quality is 0, this item increases by 1. If BSC receives a valid pre-processing MR on full rate TCH in which the uplink receiving level is 0 and uplink receiving quality is 0, then the frequency in the report is added to this item.

Measurement point: This item is measured when BSC receives a valid MR or a valid pre-processing MR in which the uplink receiving level is 0 and uplink receiving quality is 0.

Formula: None.

II. Uplink receiving level rank 0 and receiving quality rank 1 in Full Rate TCH



Formula: None.

III. Uplink receiving level rank 0 and receiving quality rank 2 in Full Rate TCH



Formula: None.

344


IV. Uplink receiving level rank 0 and receiving quality rank 3 in Full Rate TCH



Formula: None.

V. Uplink receiving level rank 0 and receiving quality rank 4 in Full Rate TCH



VI. Uplink receiving level rank 0 and receiving quality rank 5 in Full Rate TCH



Formula: None.

VII. Uplink receiving level rank 0 and receiving quality rank 6 in Full Rate TCH

Meaning: If BSC receives a valid MR on full rate TCH in which the uplink receiving level is 0 and uplink receiving quality is 6, this item increases by 1. If BSC receives a valid pre-processing MR on full rate TCH in which the uplink

345


receiving level is 0 and uplink receiving quality is 6, then the frequency in the report is added to this item.


Formula: None.

VIII. Uplink receiving level rank 0 and receiving quality rank 7 in Full Rate TCH



Formula: None.

IX. Uplink receiving level rank 1 and receiving quality rank 0 in Full Rate TCH



Formula: None.

X. Uplink receiving level rank 1 and receiving quality rank 1 in Full Rate TCH



346


Formula: None.

XI. Uplink receiving level rank 1 and receiving quality rank 2 in Full Rate TCH



Formula: None.

XII. Uplink receiving level rank 1 and receiving quality rank 3 in Full Rate TCH



Formula: None.

XIII. Uplink receiving level rank 1 and receiving quality rank 4 in Full Rate TCH



Formula: None.

347


XIV. Uplink receiving level rank 1 and receiving quality rank 5 in Full Rate TCH



Formula: None.

XV. Uplink receiving level rank 1 and receiving quality rank 6 in Full Rate TCH



Formula: None.

XVI. Uplink receiving level rank 1 and receiving quality rank 7 in Full Rate TCH



Formula: None.

XVII. Uplink receiving level rank 2 and receiving quality rank 0 in Full Rate TCH


348




Formula: None.

XVIII. Uplink receiving level rank 2 and receiving quality rank 1 in Full Rate TCH



Formula: None.

XIX. Uplink receiving level rank 2 and receiving quality rank 2 in Full Rate TCH



Formula: None.

XX. Uplink receiving level rank 2 and receiving quality rank 3 in Full Rate TCH



349


Formula: None.

XXI. Uplink receiving level rank 2 and receiving quality rank 4 in Full Rate TCH



Formula: None.

XXII. Uplink receiving level rank 2 and receiving quality rank 5 in Full Rate TCH



Formula: None.

XXIII. Uplink receiving level rank 2 and receiving quality rank 6 in Full Rate TCH



Formula: None.

350


XXIV. Uplink receiving level rank 2 and receiving quality rank 7 in Full Rate TCH



Formula: None.

XXV. Uplink receiving level rank 3 and receiving quality rank 0 in Full Rate TCH



Formula: None.

XXVI. Uplink receiving level rank 3 and receiving quality rank 1 in Full Rate TCH



Formula: None.

XXVII. Uplink receiving level rank 3 and receiving quality rank 2 in Full Rate TCH


351




Formula: None.

XXVIII. Uplink receiving level rank 3 and receiving quality rank 3 in Full Rate TCH



Formula: None.

XXIX. Uplink receiving level rank 3 and receiving quality rank 4 in Full Rate TCH



Formula: None.

XXX. Uplink receiving level rank 3 and receiving quality rank 5 in Full Rate TCH



352


Formula: None.

XXXI. Uplink receiving level rank 3 and receiving quality rank 6 in Full Rate TCH



Formula: None.

XXXII. Uplink receiving level rank 3 and receiving quality rank 7 in Full Rate TCH



Formula: None.

XXXIII. Uplink receiving level rank 4 and receiving quality rank 0 in Full Rate TCH



Formula: None.

353


XXXIV. Uplink receiving level rank 4 and receiving quality rank 1 in Full Rate TCH



Formula: None.

XXXV. Uplink receiving level rank 4 and receiving quality rank 2 in Full Rate TCH



Formula: None.

XXXVI. Uplink receiving level rank 4 and receiving quality rank 3 in Full Rate TCH



Formula: None.

XXXVII. Uplink receiving level rank 4 and receiving quality rank 4 in Full Rate TCH


354




Formula: None.

XXXVIII. Uplink receiving level rank 4 and receiving quality rank 5 in Full Rate TCH



Formula: None.

XXXIX. Uplink receiving level rank 4 and receiving quality rank 6 in Full Rate TCH



Formula: None.

XL. Uplink receiving level rank 4 and receiving quality rank 7 in Full Rate TCH



355


Formula: None.

XLI. Uplink receiving level rank 5 and receiving quality rank 0 in Full Rate TCH



Formula: None.

XLII. Uplink receiving level rank 5 and receiving quality rank 1 in Full Rate TCH



Formula: None.

XLIII. Uplink receiving level rank 5 and receiving quality rank 2 in Full Rate TCH



Formula: None.

356


XLIV. Uplink receiving level rank 5 and receiving quality rank 3 in Full Rate TCH



Formula: None.

XLV. Uplink receiving level rank 5 and receiving quality rank 4 in Full Rate TCH



Formula: None.

XLVI. Uplink receiving level rank 5 and receiving quality rank 5 in Full Rate TCH



Formula: None.

XLVII. Uplink receiving level rank 5 and receiving quality rank 6 in Full Rate TCH


357




Formula: None.

XLVIII. Uplink receiving level rank 5 and receiving quality rank 7 in Full Rate TCH



Formula: None.

XLIX. Downlink receiving level rank 0 and receiving quality rank 0 in Full Rate TCH

Meaning: If BSC receives a valid MR on full rate TCH in which the downlink receiving level is 0 and downlink receiving quality is 0, this item increases by 1. If BSC receives a valid pre-processing MR on full rate TCH in which the downlink receiving level is 0 and downlink receiving quality is 0, then the frequency in the report is added to this item.

Measurement point: This item is measured when BSC receives a valid MR or a valid pre-processing MR in which the downlink receiving level is 0 and downlink receiving quality is 0.

Formula: None.

L. Downlink receiving level rank 0 and receiving quality rank 1 in Full Rate TCH



358


Formula: None.

LI. Downlink receiving level rank 0 and receiving quality rank 2 in Full Rate TCH



Formula: None.

LII. Downlink receiving level rank 0 and receiving quality rank 3 in Full Rate TCH



Formula: None.

LIII. Downlink receiving level rank 0 and receiving quality rank 4 in Full Rate TCH



LIV. Downlink receiving level rank 0 and receiving quality rank 5 in Full Rate TCH

Meaning: If BSC receives a valid MR on full rate TCH in which the downlink receiving level is 0 and downlink receiving quality is 5, this item increases by 1.

359


If BSC receives a valid pre-processing MR on full rate TCH in which the downlink receiving level is 0 and downlink receiving quality is 5, then the frequency in the report is added to this item.


Formula: None.

LV. Downlink receiving level rank 0 and receiving quality rank 6 in Full Rate TCH



Formula: None.

LVI. Downlink receiving level rank 0 and receiving quality rank 7 in Full Rate TCH



Formula: None.

LVII. Downlink receiving level rank 1 and receiving quality rank 0 in Full Rate TCH


360



Formula: None.

LVIII. Downlink receiving level rank 1 and receiving quality rank 1 in Full Rate TCH



Formula: None.

LIX. Downlink receiving level rank 1 and receiving quality rank 2 in Full Rate TCH



Formula: None.

LX. Downlink receiving level rank 1 and receiving quality rank 3 in Full Rate TCH



Formula: None.

361


LXI. Downlink receiving level rank 1 and receiving quality rank 4 in Full Rate TCH



Formula: None.

LXII. Downlink receiving level rank 1 and receiving quality rank 5 in Full Rate TCH



Formula: None.

LXIII. Downlink receiving level rank 1 and receiving quality rank 6 in Full Rate TCH



Formula: None.

LXIV. Downlink receiving level rank 1 and receiving quality rank 7 in Full Rate TCH

Meaning: If BSC receives a valid MR on full rate TCH in which the downlink receiving level is 1 and downlink receiving quality is 7, this item increases by 1. If BSC receives a valid pre-processing MR on full rate TCH in which the

362


downlink receiving level is 1 and downlink receiving quality is 7, then the frequency in the report is added to this item.


Formula: None.

LXV. Downlink receiving level rank 2 and receiving quality rank 0 in Full Rate TCH



Formula: None.

LXVI. Downlink receiving level rank 2 and receiving quality rank 1 in Full Rate TCH



Formula: None.

LXVII. Downlink receiving level rank 2 and receiving quality rank 2 in Full Rate TCH



363


Formula: None.

LXVIII. Downlink receiving level rank 2 and receiving quality rank 3 in Full Rate TCH



Formula: None.

LXIX. Downlink receiving level rank 2 and receiving quality rank 4 in Full Rate TCH



Formula: None.

LXX. Downlink receiving level rank 2 and receiving quality rank 5 in Full Rate TCH



Formula: None.

364


LXXI. Downlink receiving level rank 2 and receiving quality rank 6 in Full Rate TCH



Formula: None.

LXXII. Downlink receiving level rank 2 and receiving quality rank 7 in Full Rate TCH



Formula: None.

LXXIII. Downlink receiving level rank 3 and receiving quality rank 0 in Full Rate TCH



Formula: None.

LXXIV. Downlink receiving level rank 3 and receiving quality rank 1 in Full Rate TCH


365




Formula: None.

LXXV. Downlink receiving level rank 3 and receiving quality rank 2 in Full Rate TCH



Formula: None.

LXXVI. Downlink receiving level rank 3 and receiving quality rank 3 in Full Rate TCH



Formula: None.

LXXVII. Downlink receiving level rank 3 and receiving quality rank 4 in Full Rate TCH



366


Formula: None.

LXXVIII. Downlink receiving level rank 3 and receiving quality rank 5 in Full Rate TCH



Formula: None.

LXXIX. Downlink receiving level rank 3 and receiving quality rank 6 in Full Rate TCH



Formula: None.

LXXX. Downlink receiving level rank 3 and receiving quality rank 7 in Full Rate TCH



Formula: None.

367


LXXXI. Downlink receiving level rank 4 and receiving quality rank 0 in Full Rate TCH



Formula: None.

LXXXII. Downlink receiving level rank 4 and receiving quality rank 1 in Full Rate TCH



Formula: None.

LXXXIII. Downlink receiving level rank 4 and receiving quality rank 2 in Full Rate TCH



Formula: None.

LXXXIV. Downlink receiving level rank 4 and receiving quality rank 3 in Full Rate TCH


368




Formula: None.

LXXXV. Downlink receiving level rank 4 and receiving quality rank 4 in Full Rate TCH



Formula: None.

LXXXVI. Downlink receiving level rank 4 and receiving quality rank 5 in Full Rate TCH



Formula: None.

LXXXVII. Downlink receiving level rank 4 and receiving quality rank 6 in Full Rate TCH



369


Formula: None.

LXXXVIII. Downlink receiving level rank 4 and receiving quality rank 7 in Full Rate TCH



Formula: None.

LXXXIX. Downlink receiving level rank 5 and receiving quality rank 0 in Full Rate TCH



Formula: None.

XC. Downlink receiving level rank 5 and receiving quality rank 1 in Full Rate TCH



Formula: None.

370


XCI. Downlink receiving level rank 5 and receiving quality rank 2 in Full Rate TCH



Formula: None.

XCII. Downlink receiving level rank 5 and receiving quality rank 3 in Full Rate TCH



Formula: None.

XCIII. Downlink receiving level rank 5 and receiving quality rank 4 in Full Rate TCH



Formula: None.

XCIV. Downlink receiving level rank 5 and receiving quality rank 5 in Full Rate TCH


371




Formula: None.

XCV. Downlink receiving level rank 5 and receiving quality rank 6 in Full Rate TCH



Formula: None.

XCVI. Downlink receiving level rank 5 and receiving quality rank 7 in Full Rate TCH



Formula: None.

3.11.3 Half Rate Receiving Level Measurement

The items of half rate receiving level measurement are listed in Table 3-10 .

Table 3-10 Items of half rate receiving level measurement

No. Item name

1Uplink receiving level rank 0 and receiving quality rank 0 in Half Rate TCH




372










































373






49Downlink receiving level rank 0 and receiving quality rank 0 in Half Rate TCH




































374














I. Uplink receiving level rank 0 and receiving quality rank 0 in Half Rate TCH

Meaning: If BSC receives a valid MR on half rate TCH in which the uplink receiving level is 0 and uplink receiving quality is 0, this item increases by 1. If BSC receives a valid pre-processing MR on half rate TCH in which the uplink receiving level is 0 and uplink receiving quality is 0, then the frequency in the report is added to this item.


Formula: None.

II. Uplink receiving level rank 0 and receiving quality rank 1 in Half Rate TCH



Formula: None.

375


III. Uplink receiving level rank 0 and receiving quality rank 2 in Half Rate TCH



Formula: None.

IV. Uplink receiving level rank 0 and receiving quality rank 3 in Half Rate TCH



Formula: None.

V. Uplink receiving level rank 0 and receiving quality rank 4 in Half Rate TCH



VI. Uplink receiving level rank 0 and receiving quality rank 5 in Half Rate TCH

Meaning: If BSC receives a valid MR on half rate TCH in which the uplink receiving level is 0 and uplink receiving quality is 5, this item increases by 1. If BSC receives a valid pre-processing MR on half rate TCH in which the uplink

376




Formula: None.

VII. Uplink receiving level rank 0 and receiving quality rank 6 in Half Rate TCH



Formula: None.

VIII. Uplink receiving level rank 0 and receiving quality rank 7 in Half Rate TCH



Formula: None.

IX. Uplink receiving level rank 1 and receiving quality rank 0 in Half Rate TCH



377


Formula: None.

X. Uplink receiving level rank 1 and receiving quality rank 1 in Half Rate TCH



Formula: None.

XI. Uplink receiving level rank 1 and receiving quality rank 2 in Half Rate TCH



Formula: None.

XII. Uplink receiving level rank 1 and receiving quality rank 3 in Half Rate TCH



Formula: None.

378


XIII. Uplink receiving level rank 1 and receiving quality rank 4 in Half Rate TCH



Formula: None.

XIV. Uplink receiving level rank 1 and receiving quality rank 5 in Half Rate TCH



Formula: None.

XV. Uplink receiving level rank 1 and receiving quality rank 6 in Half Rate TCH



Formula: None.

XVI. Uplink receiving level rank 1 and receiving quality rank 7 in Half Rate TCH


379




Formula: None.

XVII. Uplink receiving level rank 2 and receiving quality rank 0 in Half Rate TCH



Formula: None.

XVIII. Uplink receiving level rank 2 and receiving quality rank 1 in Half Rate TCH



Formula: None.

XIX. Uplink receiving level rank 2 and receiving quality rank 2 in Half Rate TCH



380


Formula: None.

XX. Uplink receiving level rank 2 and receiving quality rank 3 in Half Rate TCH



Formula: None.

XXI. Uplink receiving level rank 2 and receiving quality rank 4 in Half Rate TCH



Formula: None.

XXII. Uplink receiving level rank 2 and receiving quality rank 5 in Half Rate TCH



Formula: None.

381


XXIII. Uplink receiving level rank 2 and receiving quality rank 6 in Half Rate TCH



Formula: None.

XXIV. Uplink receiving level rank 2 and receiving quality rank 7 in Half Rate TCH



Formula: None.

XXV. Uplink receiving level rank 3 and receiving quality rank 0 in Half Rate TCH



Formula: None.

XXVI. Uplink receiving level rank 3 and receiving quality rank 1 in Half Rate TCH


382




Formula: None.

XXVII. Uplink receiving level rank 3 and receiving quality rank 2 in Half Rate TCH



Formula: None.

XXVIII. Uplink receiving level rank 3 and receiving quality rank 3 in Half Rate TCH



Formula: None.

XXIX. Uplink receiving level rank 3 and receiving quality rank 4 in Half Rate TCH



383


Formula: None.

XXX. Uplink receiving level rank 3 and receiving quality rank 5 in Half Rate TCH



Formula: None.

XXXI. Uplink receiving level rank 3 and receiving quality rank 6 in Half Rate TCH



Formula: None.

XXXII. Uplink receiving level rank 3 and receiving quality rank 7 in Half Rate TCH



Formula: None.

384


XXXIII. Uplink receiving level rank 4 and receiving quality rank 0 in Half Rate TCH



Formula: None.

XXXIV. Uplink receiving level rank 4 and receiving quality rank 1 in Half Rate TCH



Formula: None.

XXXV. Uplink receiving level rank 4 and receiving quality rank 2 in Half Rate TCH



Formula: None.

XXXVI. Uplink receiving level rank 4 and receiving quality rank 3 in Half Rate TCH


385




Formula: None.

XXXVII. Uplink receiving level rank 4 and receiving quality rank 4 in Half Rate TCH



Formula: None.

XXXVIII. Uplink receiving level rank 4 and receiving quality rank 5 in Half Rate TCH



Formula: None.

XXXIX. Uplink receiving level rank 4 and receiving quality rank 6 in Half Rate TCH



386


Formula: None.

XL. Uplink receiving level rank 4 and receiving quality rank 7 in Half Rate TCH



Formula: None.

XLI. Uplink receiving level rank 5 and receiving quality rank 0 in Half Rate TCH



Formula: None.

XLII. Uplink receiving level rank 5 and receiving quality rank 1 in Half Rate TCH



Formula: None.

387


XLIII. Uplink receiving level rank 5 and receiving quality rank 2 in Half Rate TCH



Formula: None.

XLIV. Uplink receiving level rank 5 and receiving quality rank 3 in Half Rate TCH



Formula: None.

XLV. Uplink receiving level rank 5 and receiving quality rank 4 in Half Rate TCH



Formula: None.

XLVI. Uplink receiving level rank 5 and receiving quality rank 5 in Half Rate TCH


388




Formula: None.

XLVII. Uplink receiving level rank 5 and receiving quality rank 6 in Half Rate TCH



Formula: None.

XLVIII. Uplink receiving level rank 5 and receiving quality rank 7 in Half Rate TCH



Formula: None.

XLIX. Downlink receiving level rank 0 and receiving quality rank 0 in Half Rate TCH

Meaning: If BSC receives a valid MR on half rate TCH in which the downlink receiving level is 0 and downlink receiving quality is 0, this item increases by 1. If BSC receives a valid pre-processing MR on half rate TCH in which the downlink receiving level is 0 and downlink receiving quality is 0, then the frequency in the report is added to this item.


389


Formula: None.

L. Downlink receiving level rank 0 and receiving quality rank 1 in Half Rate TCH



Formula: None.

LI. Downlink receiving level rank 0 and receiving quality rank 2 in Half Rate TCH



Formula: None.

LII. Downlink receiving level rank 0 and receiving quality rank 3 in Half Rate TCH



Formula: None.

390


LIII. Downlink receiving level rank 0 and receiving quality rank 4 in Half Rate TCH



LIV. Downlink receiving level rank 0 and receiving quality rank 5 in Half Rate TCH



Formula: None.

LV. Downlink receiving level rank 0 and receiving quality rank 6 in Half Rate TCH



Formula: None.

LVI. Downlink receiving level rank 0 and receiving quality rank 7 in Half Rate TCH

Meaning: If BSC receives a valid MR on half rate TCH in which the downlink receiving level is 0 and downlink receiving quality is 7, this item increases by 1. If BSC receives a valid pre-processing MR on half rate TCH in which the

391




Formula: None.

LVII. Downlink receiving level rank 1 and receiving quality rank 0 in Half Rate TCH



Formula: None.

LVIII. Downlink receiving level rank 1 and receiving quality rank 1 in Half Rate TCH



Formula: None.

LIX. Downlink receiving level rank 1 and receiving quality rank 2 in Half Rate TCH



392


Formula: None.

LX. Downlink receiving level rank 1 and receiving quality rank 3 in Half Rate TCH



Formula: None.

LXI. Downlink receiving level rank 1 and receiving quality rank 4 in Half Rate TCH



Formula: None.

LXII. Downlink receiving level rank 1 and receiving quality rank 5 in Half Rate TCH



Formula: None.

393


LXIII. Downlink receiving level rank 1 and receiving quality rank 6 in Half Rate TCH



Formula: None.

LXIV. Downlink receiving level rank 1 and receiving quality rank 7 in Half Rate TCH



Formula: None.

LXV. Downlink receiving level rank 2 and receiving quality rank 0 in Half Rate TCH



Formula: None.

LXVI. Downlink receiving level rank 2 and receiving quality rank 1 in Half Rate TCH


394




Formula: None.

LXVII. Downlink receiving level rank 2 and receiving quality rank 2 in Half Rate TCH



Formula: None.

LXVIII. Downlink receiving level rank 2 and receiving quality rank 3 in Half Rate TCH



Formula: None.

LXIX. Downlink receiving level rank 2 and receiving quality rank 4 in Half Rate TCH



395


Formula: None.

LXX. Downlink receiving level rank 2 and receiving quality rank 5 in Half Rate TCH



Formula: None.

LXXI. Downlink receiving level rank 2 and receiving quality rank 6 in Half Rate TCH



Formula: None.

LXXII. Downlink receiving level rank 2 and receiving quality rank 7 in Half Rate TCH



Formula: None.

396


LXXIII. Downlink receiving level rank 3 and receiving quality rank 0 in Half Rate TCH



Formula: None.

LXXIV. Downlink receiving level rank 3 and receiving quality rank 1 in Half Rate TCH



Formula: None.

LXXV. Downlink receiving level rank 3 and receiving quality rank 2 in Half Rate TCH



Formula: None.

LXXVI. Downlink receiving level rank 3 and receiving quality rank 3 in Half Rate TCH


397




Formula: None.

LXXVII. Downlink receiving level rank 3 and receiving quality rank 4 in Half Rate TCH



Formula: None.

LXXVIII. Downlink receiving level rank 3 and receiving quality rank 5 in Half Rate TCH



Formula: None.

LXXIX. Downlink receiving level rank 3 and receiving quality rank 6 in Half Rate TCH



398


Formula: None.

LXXX. Downlink receiving level rank 3 and receiving quality rank 7 in Half Rate TCH



Formula: None.

LXXXI. Downlink receiving level rank 4 and receiving quality rank 0 in Half Rate TCH



Formula: None.

LXXXII. Downlink receiving level rank 4 and receiving quality rank 1 in Half Rate TCH



Formula: None.

399


LXXXIII. Downlink receiving level rank 4 and receiving quality rank 2 in Half Rate TCH



Formula: None.

LXXXIV. Downlink receiving level rank 4 and receiving quality rank 3 in Half Rate TCH



Formula: None.

LXXXV. Downlink receiving level rank 4 and receiving quality rank 4 in Half Rate TCH



Formula: None.

LXXXVI. Downlink receiving level rank 4 and receiving quality rank 5 in Half Rate TCH


400




Formula: None.

LXXXVII. Downlink receiving level rank 4 and receiving quality rank 6 in Half Rate TCH



Formula: None.

LXXXVIII. Downlink receiving level rank 4 and receiving quality rank 7 in Half Rate TCH



Formula: None.

LXXXIX. Downlink receiving level rank 5 and receiving quality rank 0 in Half Rate TCH



401


Formula: None.

XC. Downlink receiving level rank 5 and receiving quality rank 1 in Half Rate TCH



Formula: None.

XCI. Downlink receiving level rank 5 and receiving quality rank 2 in Half Rate TCH



Formula: None.

XCII. Downlink receiving level rank 5 and receiving quality rank 3 in Half Rate TCH



Formula: None.

402


XCIII. Downlink receiving level rank 5 and receiving quality rank 4 in Half Rate TCH



Formula: None.

XCIV. Downlink receiving level rank 5 and receiving quality rank 5 in Half Rate TCH



Formula: None.

XCV. Downlink receiving level rank 5 and receiving quality rank 6 in Half Rate TCH



Formula: None.

XCVI. Downlink receiving level rank 5 and receiving quality rank 7 in Half Rate TCH


403




Formula: None.

3.11 Up-Down Link Balance Measurement Function

3.11.1 General

To achieve an excellent system, it is necessary to have a power estimation during planning so as to maintain the balance between the uplink and downlink signals within the covered area. If the uplink signal coverage is larger than that of downlink signal, the signal at the edge of the cell will be weak and easily "submerged" by the stronger signals from other cells. If the downlink signal coverage is larger than that of uplink signal, MS will be forced to station at this signal, but since the unlink signal is too weak, the voice quality will be affected. The balance here does not mean absolute equal. With the MR on Abis interface, it is easy to judge whether the uplink and downlink signal is in balance.

The MR BSC receives contains uplink receiving level and downlink receiving level. Here is a calculation method for Up-Down Link Balance Measurement: (downlink receiving level – uplink receiving level) – (MS sensitivity – BTS sensitivity). The current value for BSC is 6. This difference calculated from the above formula can be classified into 11 ranks according the to dB value of the result: Rank 1~11. The number of MR in each rank is measured in this measurement. The correspondence is listed in Table 3-1 .

Table 3-1 Relation between uplink/downlink balance rank and receiving level

Uplink and downlink balance

level

Downlink receiving level – uplink receiving level – 6 (dB)

1 -15

2 -14 ~ -10

3 -9 ~ -6

4 -5 ~ -3

5 -2 ~ 0

6 0

7 1 ~ 2

8 3 ~ 5

9 6 ~ 9

404


10 10 ~ 14

11 15

If the measurement result shows that the uplink/downlink are frequently in the balance level 1, then the downlink loss is too large or the downlink transmitting power is to weak. If the measurement result shows that the uplink/downlink are frequently in the balance level 11, then the uplink loss is too large or the uplink transmitting power is to weak. These data can be used as a reference to locate the faults in transceiving channels such as TRX and antenna feeder.

The object of Up-down link balance measurement is TRX. The module No., cell No. and TRX No. (or all TRXs in the configured range of cells in the configured range) of the task can be configured in Object Definition. All measurement items are listed in Table 3-2 .

Table 3-2 Up-down link balance measurement items

No. Item name

1Rank 1

2Rank 2

3Rank 3

4Rank 4

5Rank 5

6Rank 6

7Rank 7

8Rank 8

9Rank 9

10Rank 10

11Rank 11


I. Rank 1

Description: After BSC receives MR, this index increases by 1 if the result from the calculation method in 3.11.1 is in up-down link balance rank 1.

Measurement point: Measured when BSC receives MR, and the result from the calculation method in 3.11.1 is in the up-down link balance rank 1.

Formula: none.

405


II. Rank 2



Formula: none.

III. Rank 3



Formula: none.

IV. Rank 4



Formula: none.

V. Rank 5



Formula: none.

VI. Rank 6



Formula: none.

VII. Rank 7



Formula: none.

406


VIII. Rank 8



Formula: none.

IX. Rank 9



Formula: none.

X. Rank 10



Formula: none.

XI. Rank 11



Formula: none.

3.12 LAPD Link Measurement Function

3.12.1 General

The Layer 3 (L3) information interaction between BSC and BTS is conducted on the basis of normal functioning of Layer 2 (L2) link. The management and maintenance of L2 link conforms to the specification of ISDN data link layer. In BSC, the management of L2 is carried out by LAPD board.

"LAPD Link Measurement Function" measures the times of sending and receiving link setup or refuse messages between LAPD and L2 entity in BTS. These items can be used to judge whether L2 link is in normal condition.

407


The object of "LAPD Link Measurement Function" is the link. In the interface of Object Definition, it is possible to register the module No., link No. or the links within the configured range in the module. All items are listed in Table 3-1 .

Table 3-1 LAPD link measurement items

No. Item name

1 BSC num. of sending link setups

2 BSC num. of receiving link setups

3 BSC num. of sending rejections

4 BSC num. of receiving rejections

5 BSC num. of sending RNRs

6 BSC num. of receiving RNRs

7 BSC num. of retransmissions

8 BSC num. of received serial number errors

9 BSC num. of receiving layer 3 data requests

10 BSC num. of sending messages

11 BSC num. of receiving messages

12 BSC num. of sending message queue overflows

13 BSC num. of receiving long frame errors

14 BSC num. of receiving octets errors

15 BSC num. of receiving give-up serials

16 BSC num. of receiving CRC errors

17 BSC num. of L1L2 queue overflows

18 BSC num. of received frames by physical layer

19 BTS num. of receiving long frame errors


21 BTS num. of sending long frame errors


23 BTS num. of sending RNRs

24 BTS num. of receiving RNRs

25 BTS num. of retransmissions

26 BTS num. of received serial number errors

27 BTS num. of receiving layer 3 data requests

28 BTS num. of sending messages

29 BTS num. of receiving messages

30 BTS num. of sending message queue overflows


32 BTS num. of receiving octets errors

33 BTS num. of receiving give-up serials

34 BTS num. of receiving CRC errors

408


35 BTS num. of L1L2 queue overflows

36 BTS num. of received frames by physical layer


I. BSC num. of sending link setups

Description: This item measures the times of LAPD, the L2 entity in BSC, sending SABME frames. Normally, SABME frame is sent to request for link setup. After the startup of BSC, the link status is converted to multi-frame (Multi_I) setup through the frame interaction between the L2 entities of BSC and BTS. During this procedure, LAPD sends SABME from to BTS L2 entity. In the normal operation of BSC, if link status becomes abnormal or physical link between BSC and BTS is broken, BSC will also send SABME frame to request for link reestablishment.

Measurement point: This item is measured when LAPD sends SABME frame. Formula: none.

II. BSC num. of receiving link setups

Description: This item measures the times of LAPD, the L2 entity in BSC, receiving SABME frames. According to the specification of L2, SABME frame is sent to request for link setup. During the startup and normal operation of BSC, link setup is not initiated by BTS, so BTS will not send SABME frame to BSC, and that means this item should be 0. If the link status is abnormal (other than Multi_I), BTS may send SABME frame to BSC. Note that if the uplink physical link is broken, then even BTS have sent SABME frame, BSC will have no chance to receive it, so this item will not increase.

Measurement point: This item is measured when LAPD receives SABME frame.

Formula: none.

III. BSC num. of sending rejections

Description: This item measures the times of BSC L2 entity, i.e. LAPD, sending REJ frame. In L2 specification, REJ frame is a monitoring frame which means the received Frame I (information frame) is refused, and at the same time the Serial No. of Frame I is expected from the peer end. Frame I is an information frame numbered in sequence. LAPD has records for the received and sent Frame Is. Normally this item should be 0. If the LAPD receives a Frame I whose No. is not expected, it sends a REJ frame to BTS, and this item increases by 1. For example, the serial No. of Frame I expected by BSC is A,

409


while the No. of the received one is B, BSC sends a REJ frame to request for Frame I whose serial No. is A.

Measurement point: This item is measured when LAPD sends REJ frame. Formula: none.

IV. BSC num. of receiving rejections

Description: This item measures the times of BSC L2 entity, i.e. LAPD, receiving REJ frame. In L2 specification, REJ frame is a monitoring frame which means the received Frame I (information frame) is refused, and at the same time the Serial No. of Frame I is expected from the peer end. Frame I is an information frame numbered in sequence. LAPD has records for the received and sent Frame Is. Normally this item should be 0. If the BTS receives a Frame I whose No. is not expected, it sends a REJ frame to BSC, and this item increases by 1. For example, the serial No. of Frame I expected by BTS is A, while the No. of the received one is B, BTS sends a REJ frame to request for Frame I whose serial No. is A.

Measurement point: This item is measured when LAPD receives a REJ frame. Formula: none.

V. BSC num. of sending RNRs

Description: This item measures the times of BSC L2 entity, i.e. LAPD, sending RNR frame. In L2 specification, REJ frame is a monitoring frame which means the home end is busy and is not ready to receive the next Frame I and at the same time the Serial No. of Frame I is expected from the peer end. When the peer end receives, it stops sending Frame I. if the receiver of BSC is busy, it sends RNR frame to BTS. BTS stops sending Frame I on reception of RNR.

Measurement point: This item is measured when LAPD sends RNR frame. Formula: none.

VI. BSC num. of receiving RNRs

Description: This item measures the times of BSC L2 entity, i.e. LAPD, receiving RNR frame. In L2 specification, REJ frame is a monitoring frame which means the home end is busy and is not ready to receive the next Frame I and at the same time the Serial No. of Frame I is expected from the peer end. When the peer end receives, it stops sending Frame I. if the receiver of BTS is busy, it sends RNR frame to BSC. BSC stops sending Frame I on reception of RNR.

Measurement point: This item is measured when LAPD receives RNR frame. Formula: none.

410


VII. BSC num. of retransmissions

Description: This item measures the times of BSC L2 entity, i.e. LAPD, resending Frame I (information frame). BSC receiving REJ frame from BTS means that error occurs when BTS receives Frame I. BSC resends the Frame I of the No. in REJ frame and all Frame Is after this No. BSC receiving REJ frame from BTS means that BTS L2 receiver is busy and cannot receive Frame I. BSC resends the Frame I of the No. in REJ frame and all Frame Is after this No. after the peer end is not busy. This item increases by 1 when BSC resends a Frame 1.

Measurement point: This item is measured when LAPD resends Frame I. Formula: none.

VIII. BSC num. of received serial number errors

Description: This item measures the times of inconsistency between expected serial No. of information frame and the one to be sent after BSC L2 entity, i.e. LAPD, receives the frame containing expected serial No. of information frame. The frames of RR, RNR, REJ and I sent from BTS all contain the expected serial No. of Frame I to be sent from BSC. And BSC records the range of serial No of the Frame Is. If the received Frame I is not in that range, then this serial No. is considered to be an incorrect one, and this item increases by 1.

Measurement point: This item is measured when LAPD receives frames containing the serial No of expected information frames and the No. is incorrect.

Formula: none.

IX. BSC num. of receiving layer 3 data requests

Description: This item measures the times of BSC L2 entity, i.e. LAPD, receiving the to-be-confirmed information L3 transfer requests. L3 transfer requests can be divided into two types: one needs to be confirmed and the other needs no confirming. The former type is transferred with L2 Frame I and the latter one is transferred with L2 Frame UI. All L3 messages sent by BSC are to be confirmed. This item increases by 1 if LAPD receives a to-be-confirmed information L3 transfer requests.

Measurement point: This item is measured when LAPD receives to-be-confirmed information L3 transfer requests.

Formula: none.

X. BSC num. of sending messages

Description: This item measures the times of BSC L2 entity, i.e. LAPD, sending Frame I. Frame I is a numbered information frame. L3 transfer requests can be divided into two types: one needs to be confirmed and the other needs no

411


confirming. The former type is transferred with L2 Frame I and the latter one is transferred with L2 Frame UI. All L3 messages sent by BSC are to be confirmed. This item increases by 1 if LAPD sends a to-be-confirmed information L3 transfer requests.

Measurement point: This item is measured when LAPD sends a Frame I. Formula: none.

XI. BSC num. of receiving messages

Description: This item measures the times of BSC L2 entity, i.e. LAPD, receiving Frame I. Frame I is a numbered information frame. L3 transfer requests can be divided into two types: one needs to be confirmed and the other needs no confirming. The former type is transferred with L2 Frame I and the latter one is transferred with L2 Frame UI. All L3 messages received by BSC are to be confirmed. This item increases by 1 if LAPD receives a to-be-confirmed information L3 transfer requests.

Measurement point: This item is measured when LAPD receives a Frame I. Formula: none.

XII. BSC num. of sending message queue overflows

Description: L3 transfer requests can be divided into two types: one needs to be confirmed and the other needs no confirming. The former type is transferred with L2 Frame I and the latter one is transferred with L2 Frame UI. When sending the information to be confirmed, BSC L2 entity, i.e. LAPD, put the Frame I in a message queue to be sent in sequence. If large amount of information is to be sent within a short period of time by L3, the message queue will overflows, and message will be lost. This item increases by 1 whenever the message queue overflows. This situation seldom appears because the processing capacity of LAPD is powerful and the message queue is long.

Measurement point: This item is measured when the message queue of Frame Is sent by LAPD overflows.

Formula: none.

XIII. BSC num. of receiving long frame errors

Description: L3 message is sent via L2 to L1. L1 is the physical for sending the information in the form of physical frame. If error takes place when L1 receives long frame, then this frame will be discarded, and this item increases by 1.

Measurement point: This item is measured when L1 of BSC receives incorrect long frame.

Formula: none.

412


XIV. BSC num. of receiving octets errors

Description: L3 message is sent via L2 to L1. L1 is the physical for sending the information in the form of physical frame. If L1 receives frames containing byte errors, then this frame will be discarded; this item increases by 1.

Measurement point: This item is measured when L1 of BSC receives frame containing byte errors.

Formula: none.

XV. BSC num. of receiving give-up serials

Description: L3 message is sent via L2 to L1. L1 is the physical for sending the information in the form of physical frame. If L1 receives frames containing give-up serials, then this frame will be discarded; this item increases by 1.

Measurement point: This item is measured when L1 of BSC receives frame containing give-up serials.

Formula: none.

XVI. BSC num. of receiving CRC errors

Description: L3 message is sent via L2 to L1. L1 is the physical for sending the information in the form of physical frame. If L1 receives frames containing CRC errors, then this frame will be discarded; this item increases by 1.

Measurement point: This item is measured when L1 of BSC receives frame containing CRC errors.

Formula: none.

XVII. BSC num. of L1L2 queue overflows

Description: When receiving message, BSC first receives physical frame via L1, and then put it in the queue leading from L1 to L2. If large amount of information is received within a short period of time by L1, the message queue will overflows, and message will be lost. This item increases by 1 whenever the message queue overflows.

Measurement point: This item is measured when the message queue leading from L1 to L2 overflows.

Formula: none.

XVIII. BSC num. of received frames by physical layer

Description: When receiving message, BSC first receives physical frame via L1, and then put it in the queue leading from L1 to L2. This item increases by 1 whenever L1 receives a physical frame.

Measurement point: This item is measured when L1 receives a physical frame. Formula: none.

413


XIX. BTS num. of receiving long frame errors

Description: This item measures the times of L2 entity in BTS sending SABME frames. According to the specification of L2, SABME frame is sent to request for link setup. During the startup and normal operation of BSC, link setup is not initiated by BTS; so BTS will not send SABME frame to BSC, and that means this item should be 0. If the link status is abnormal (other than Multi_I), BTS may send SABME frame to BSC. Note that if the uplink physical link is broken, then even BTS have sent SABME frame, BSC will have no chance to receive it, so this item will not increase.

Measurement point: This item is measured when BTS L2 entity sends a SABME frame.

Formula: none.

XX. BTS num. of receiving long frame errors

Description: This item measures the times of L2 entity in BTS receiving SABME frames. Normally, SABME frame is sent to request for link setup. After the startup of BSC, the link status is converted to multi-frame (Multi_I) setup through the frame interaction between the L2 entities of BSC and BTS. During this procedure, LAPD sends SABME from to BTS L2 entity. In the normal operation of BSC, if link status becomes abnormal or physical link between BSC and BTS is broken, BSC will also send SABME frame to request for link reestablishment.

Measurement point: This item is measured when BTS L2 entity receives a SABME frame.

Formula: none.

XXI. BTS num. of sending long frame errors

Description: This item measures the times of BTS L2 entity sending REJ frame. In L2 specification, REJ frame is a monitoring frame which means the received Frame I (information frame) is refused, and at the same time the Serial No. of Frame I is expected from the peer end. Frame I is an information frame numbered in sequence. LAPD has records for the received and sent Frame Is. Normally this item should be 0. If the BTS receives a Frame I whose No. is not expected, it sends a REJ frame to BSC, and this item increases by 1. For example, the serial No. of Frame I expected by BTS is A, while the No. of the received one is B, BTS sends a REJ frame to request for Frame I whose serial No. is A. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

Measurement point: This item is measured when BTS L2 entity sends a REJ frame.

Formula: none.

414


XXII. BTS num. of receiving long frame errors

Description: This item measures the times of BTS L2 entity receiving REJ frame. In L2 specification, REJ frame is a monitoring frame which means the received Frame I (information frame) is refused, and at the same time the Serial No. of Frame I is expected from the peer end. Frame I is an information frame numbered in sequence. LAPD has records for the received and sent Frame Is. Normally this item should be 0. If the LAPD receives a Frame I whose No. is not expected, it sends a REJ frame to BTS, and this item increases by 1. For example, the serial No. of Frame I expected by BSC is A, while the No. of the received one is B, BSC sends a REJ frame to request for Frame I whose serial No. is A. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

Measurement point: This item is measured when BTS L2 entity receives a REJ frame.

Formula: none.

XXIII. BTS num. of sending RNRs

Description: This item measures the times of BTS L2 entity receiving RNR frame. In L2 specification, REJ frame is a monitoring frame which means the home end is busy and is not ready to receive the next Frame I and at the same time the Serial No. of Frame I is expected from the peer end. When the peer end receives, it stops sending Frame I. if the receiver of BTS is busy, it sends RNR frame to BSC. BSC stops sending Frame I on reception of RNR. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

Measurement point: This item is measured when BTS L2 entity sends a RNR frame.

Formula: none.

XXIV. BTS num. of receiving RNRs

Description: This item measures the times of BTS L2 entity receiving RNR frame. In L2 specification, REJ frame is a monitoring frame which means the home end is busy and is not ready to receive the next Frame I and at the same time the Serial No. of Frame I is expected from the peer end. When the peer end receives, it stops sending Frame I. if the receiver of BSC is busy, it sends RNR frame to BTS. BTS stops sending Frame I on reception of RNR. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

Measurement point: This item is measured when BTS L2 entity receives a RNR frame.

Formula: none.

415


XXV. BTS num. of retransmissions

Description: This item measures the times of BTS L2 entity resending Frame I (information frame). BTS receiving REJ frame from BSC means that error occurs when BSC receives Frame I. BTS resends the Frame I of the No. in REJ frame and all Frame Is after this No. BTS receiving REJ frame from BSC means that BSC L2 receiver is busy and cannot receive Frame I. BTS resends the Frame I of the No. in REJ frame and all Frame Is after this No. after the peer end is not busy. This item increases by 1 when BTS resends a Frame 1. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

Measurement point: This item is measured when BTS L2 entity resends Frame I.

Formula: none.

XXVI. BTS num. of received serial number errors

Description: This item measures the times of inconsistency between expected serial No. of information frame and the one to be sent after BTS L2 entity receives the frame containing expected serial No. of information frame. The frames of RR, RNR, REJ and I sent from BSC all contain the expected serial No. of Frame I to be sent from BTS. And BTS records the range of serial No of the Frame Is. If the received Frame I is not in that range, then this serial No. is considered to be an incorrect one, and this item increases by 1. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

Measurement point: This item is measured when BTS L2 entity receives frames containing the serial Nos of expected information frames and the No. is incorrect.

Formula: none.

XXVII. BTS num. of receiving layer 3 data requests

Description: This item measures the times of BTS L2 entity receiving the to-be-confirmed information L3 transfer requests. L3 transfer requests can be divided into two types: one needs to be confirmed and the other needs no confirming. The former type is transferred with L2 Frame I and the latter one is transferred with L2 Frame UI. Only MR message in the L3 messages sent from BTS needs no confirming. This item increases by 1 if BTS L2 entity receives a to-be-confirmed information L3 transfer requests. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

Measurement point: This item is measured when BTS L2 entity receives to-be-confirmed information L3 transfer requests.

416


Formula: none.

XXVIII. BTS num. of sending messages

Description: This item measures the times of BTS L2 entity sending Frame I. Frame I is a numbered information frame. L3 transfer requests can be divided into two types: one needs to be confirmed and the other needs no confirming. The former type is transferred with L2 Frame I and the latter one is transferred with L2 Frame UI. Only MR message in the L3 messages sent from BTS needs no confirming. This item increases by 1 if BTS L2 entity sends a to-be-confirmed information L3 transfer requests. This item increases by 1 if BTS L2 entity receives a to-be-confirmed information L3 transfer requests. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

Measurement point: This item is measured when BTS L2 entity sends a Frame I.

Formula: none.

XXIX. BTS num. of receiving messages

Description: This item measures the times of BTS L2 entity receiving Frame I. Frame I is a numbered information frame. L3 transfer requests can be divided into two types: one needs to be confirmed and the other needs no confirming. The former type is transferred with L2 Frame I and the latter one is transferred with L2 Frame UI. Only MR message in the L3 messages sent from BTS needs no confirming. This item increases by 1 if BTS L2 entity receives a to-be-confirmed information L3 transfer requests. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

Measurement point: This item is measured when BTS L2 entity receives a Frame I.

Formula: none.

XXX. BTS num. of sending message queue overflows

Description: L3 transfer requests can be divided into two types: one needs to be confirmed and the other needs no confirming. The former type is transferred with L2 Frame I and the latter one is transferred with L2 Frame UI. When sending the information to be confirmed, BTS L2 entity put the Frame I in a message queue to be sent in sequence. If large amount of information is to be sent within a short period of time by L3, the message queue will overflows, and message will be lost. This item increases by 1 whenever the message queue overflows. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

417


Measurement point: This item is measured when the message queue of Frame Is sent by BTS L2 entity overflows.

Formula: none.

XXXI. BTS num. of receiving long frame errors

Description: L3 message is sent via L2 to L1. L1 is the physical for sending the information in the form of physical frame. If error takes place when L1 receives long frame, then this frame will be discarded, and this item increases by 1. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

Measurement point: This item is measured when L1 of BTS receives incorrect long frame.

Formula: none.

XXXII. BTS num. of receiving octets errors

Description: L3 message is sent via L2 to L1. L1 is the physical for sending the information in the form of physical frame. If L1 receives frames containing byte errors, then this frame will be discarded; this item increases by 1. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

Measurement point: This item is measured when L1 of BTS receives frame containing byte errors.

Formula: none.

XXXIII. BTS num. of receiving give-up serials

Description: L3 message is sent via L2 to L1. L1 is the physical for sending the information in the form of physical frame. If L1 receives frames containing give-up serials, then this frame will be discarded; this item increases by 1. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

Measurement point: This item is measured when L1 of BTS receives frame containing give-up serials.

Formula: none.

XXXIV. BTS num. of receiving CRC errors

Description: L3 message is sent via L2 to L1. L1 is the physical for sending the information in the form of physical frame. If L1 receives frames containing CRC errors, then this frame will be discarded; this item increases by 1. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

418


Measurement point: This item is measured when L1 of BTS receives frame containing CRC errors.

Formula: none.

XXXV. BTS num. of L1L2 queue overflows

Description: When receiving message, BTS first receives physical frame via L1, and then put it in the queue leading from L1 to L2. If large amount of information is received within a short period of time by L1, the message queue will overflows, and message will be lost. This item increases by 1 whenever the message queue overflows. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

Measurement point: This item is measured when the message queue leading from L1 to L2 overflows.

Formula: none.

XXXVI. BTS num. of received frames by physical layer

Description: When receiving message, BTS first receives physical frame via L1, and then put it in the queue leading from L1 to L2. This item increases by 1 whenever L1 receives a physical frame. If the uplink physical link is broken, the measurement result cannot be sent to BSC, and this item will not increase.

Measurement point: This item is measured when L1 of BTS receives a physical frame.

Formula: none.

3.13 Channel Allocation Measurement Function

Channel Allocation Measurement Function is the basis of evaluating the channel allocation algorithm, observing channel allocation during system operation, and locating problems related to channel allocation. To be specific, it provides the information of the channel distribution at various interference bands, the degree of the channel interference exceeding the threshold set by Channel II algorithm, times of various situations happened from channel allocation to seizure and then to call drop and times of call drops caused by connection failure and error indication. In addition, it also provides the items such as Successful SDCCH seizure rate after allocation, Unsuccessful SDCCH seizure rate after allocation and SDCCH call drop rate as the reference for network operation analysis.

The measurement object of Channel Allocation Measurement Function is the TRX. User can select the TRX in a cell as the object of statistic task.

Since the items in Channel Allocation Measurement Function are used to observe the performance of channel allocation algorithm, it should be registered in that case. The recommended statistic cycle is 60 minutes.

419


3.13.1 SDCCH Allocation Measurement Function

All the statistic items in this part are listed in Table 3-1 .

Table 3-1 Statistic items in Channel Allocation Measurement Function

No. Item name

1 Average num. of idle SDCCHs in Interf. band 1





6 Num. of the uplink Interf. indication message in seized SDCCH

7 Num. of the downlink Interf. indication message in seized SDCCH

8 SDCCH allocations

9 Successful SDCCH seizures

10 SDCCH seizure failures (caused by channel

11 SDCCH call drops (caused by channel)

12 SDCCH lost radio connections (connection failure)

13 SDCCH lost radio connections (error indication)

14 Successful SDCCH seizure rate after allocation

15 SDCCH seizure failure rate (caused by channel)

16 SDCCH call drop rate (caused by channel)

I. Average num. of idle SDCCHs in Interf. band 1

Description: Interference band is the level rank contained in RF RESOURCE INDICATION to be reported to BSC by BTS when the channel is idle. There are six ranks. The level range can be decided with data configuration. Below is the normal setting:

Interf. 0 -110~-105 dBm

Interf. 1 -105~-98 dBm





The higher rank suggests higher interference level. Normally, an idle channel at Interf. 4 or 5 suggests the existence of interference. This item measures the average times of the uplink interference level rank of an idle SDCCH of a TRX at Interf. 1 within the measurement cycle.

420


Measurement point: System gets the number of idle SDCCHs at Interf. 1 every five seconds. At the end of the measurement cycle, the total number from all sampling points is divided with the times of sampling to get the average number of idle SDCCHs at Interf. 1.

Formula: none.

II. Average num. of idle SDCCHs in Interf. band 2


Interf. 0 -110~-105 dBm








Formula: none.

III. Average num. of idle SDCCHs in Interf. band 3


Interf. 0 -110~-105 dBm






421




Formula: none.

IV. Average num. of idle SDCCHs in Interf. band 4


Interf. 0 -110~-105 dBm







Measurement point: System get the number of idle SDCCHs at Interf. 4 every five seconds. At the end of the measurement cycle, the total number from all sampling points is divided with the times of sampling to get the average number of idle SDCCHs at Interf. 4.

Formula: none.

V. Average num. of idle SDCCHs in Interf. band 5


Interf. 0 -110~-105 dBm



422







Formula: none.

VI. Num. of the uplink Interf. indication message in seized SDCCH

Description: In the application of Huawei II channel allocation algorithm, BSC calculates the priority rank of channel interference indication according to the channel interference indication message reported by LAPD module. The priority rank is the basis for the subsequent channel allocation. LAPD compares the level and quality in the measurement report reported by MS via this channel with the threshold configured to decide whether to send interference indication message to BSC. If both level and quality exceeds the threshold, LAPD sends interference indication message to BSC. This item measures the number of uplink interference indication messages of a SDCCH within the measurement cycle received by BSC.

Measurement point: This item is measured when BSC receives an uplink interference indication message of a SDCCH reported by LAPD module.

Formula: none.

VII. Num. of the downlink Interf. indication message in seized SDCCH

Description: In the application of Huawei II channel allocation algorithm, BSC calculates the priority rank of channel interference indication according to the channel interference indication message reported by LAPD module. The priority rank is the basis for the subsequent channel allocation. LAPD compares the level and quality in the measurement report reported by MS via this channel with the threshold configured to decide whether to send interference indication message to BSC. If both level and quality exceeds the threshold, LAPD sends interference message to BSC. This item measures the number of downlink interference indication messages of a SDCCH within the measurement cycle received by BSC.

423


Measurement point: This item is measured when BSC receives a downlink interference indication message of a SDCCH reported by LAPD module.

Formula: none.

VIII. SDCCH allocations

Description: This item measures the times of BSC radio resource management module successfully finding idle SDCCH after receiving SDCCH requests, including the times of successfully preempting SDCCH. BSC sends a CHANNEL ACTIVATION message to BTS afterwards to activate this SDCCH.

Measurement point: This item is measured when BSC radio resource management module finds or preempts an idle SDCCH from the channel resource table.

Formula: none.

IX. Successful SDCCH seizures

Description: This item measures the times of BSC receiving the notification indicating successful SDCCH seizures after MS successfully seizes the SDCCH during the procedure of immediate assignment and handover.

Measurement point:1) This item is measured when BTS sends CHANNEL ACTIVATION ACKNOWLEDGE message to BSC in the immediate assignment procedure.2) During the procedure of Incoming BSC handover, when the destination

cell receives HANDOVER DETECTION from BTS, this item is measured.3) During the procedure of Intra-BSC incoming cell handover, when the

destination cell receives HANDOVER DETECTION from BTS, this item is measured.

Formula: none.

X. SDCCH seizure failures (caused by channel)

Description: This item measures the times of SDCCH seizure failures caused by unsuccessful channel activation.

Measurement point: In the immediate assignment procedure, after BSC sends CHANNEL ACTIVATION to BTS, BTS dose not respond or returns CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE. This item is measured in this case.

Formula: none.

XI. SDCCH call drops (caused by channel)

Description: This item measures the times of SDCCH call drops caused by unsuccessful message decoding at air interface or radio interface link broken.

Measurement point:

424


1) BTS detects SDCCH radio link failure or hardware link failure, and sends CONNECTION FAILURE INDICATION to BSC to indicate that call drop happens at the air interface due to radio link connection failure. This item is measured when BSC receives this message.

2) BTS sends ERROR INDICATION to BSC due to SDCCH radio link layer connection abnormal so as to notify BSC the call drop at air interface due to radio link failure. This item is measured when BSC receives ERROR INDICATION (cause: timer T200 expired (N200 + 1) times (0x01), unsolicited DM response, multiple frame established state (0x05), sequence error (0x07)).

3) In the process of BSC internal outgoing inter cell handover (SDCCH handover), this item is measured when waiting for the Internal Handover Complete message times out.

4) In the process of outgoing inter BSC handover (SDCCH handover), this item is measured when waiting for the CLEAR COMMAND message with cause of handover success times out.

Formula: none.

XII. SDCCH lost radio connections (connection failure)

Description: BTS detects SDCCH radio link failure, and sends CONNECTION FAILURE INDICATION to BSC to indicate that call drop happens at the air interface due to radio link connection failure. This item measures the times of receiving CONNECTION FAILURE INDICATION (cause: all causes described in "GSM 0858" except for equipment failure (0X20) and terrestrial channel failure (0X22)).

Measurement point: This item is measured when BSC receives CONNECTION FAILURE INDICATION (cause: all causes described in GSM 0858 except for equipment failure (0X20) and terrestrial channel failure (0X22)) from the SDCCH of objective cell.

Formula: none.

XIII. SDCCH lost radio connections (error indication)

Description: BTS sends ERROR INDICATION to BSC due to SDCCH radio link layer connection abnormal so as to notify BSC the call drop at air interface due to radio link failure. This item is measured when BSC receives ERROR INDICATION (cause: timer T200 expired (N200 + 1) times (0x01), unsolicited DM response, multiple frame established state (0x05), sequence error (0x07)). See "GSM 0858".

Measurement point: This item is measured when BSC receives ERROR INDICATION (cause: timer T200 expired (N200 + 1) times (0x01), unsolicited

425


DM response, multiple frame established state (0x05), sequence error (0x07)) from the SDCCH of the objective cell.

Formula: none.

XIV. Successful SDCCH seizure rate after allocation

Description: This item measures the percentage of times of MS successfully seizing channels accounting times of BSC successfully allocating channels. See Successful SDCCH seizures and SDCCH allocations .

Measurement point: none. Formula: successful SDCCH seizures / SDCCH allocations

XV. SDCCH seizure failure rate (caused by channel)

Description: This item measures the percentage of times of unsuccessful MS seizing channels due to channel related causes accounting times of BSC successfully allocating channels. See SDCCH seizure failures (caused bychannel) and SDCCH allocations .

Measurement point: none. Formula: SDCCH seizure failures (caused by channel) / times of SDCCH

allocations

XVI. SDCCH call drop rate (caused by channel)

Description: This item measures the percentage of SDCCH call drops (caused by channel) accounting for successful SDCCH seizures. See SDCCH calldrops (caused by channel) and Successful SDCCH seizures .

Measurement point: none. Formula: SDCCH call drops (caused by channel) / successful SDCCH seizures

3.13.2 TCH Allocation Measurement Function


Table 3-1 Statistic items in TCH Allocation Measurement Function

No. Item name

1 Average num. of idle TCHs in Interf. band 1





6 Num. of the uplink Interf. indication message in seized TCH

7 Num. of the downlink Interf. indication message in seized TCH

8 TCH allocations

426


9 Successful TCH seizures

10 TCH seizure failures (caused by channel)

11 TCH call drops (caused by channel)

12 TCH lost radio connections (connection failure)

13 TCH lost radio connections (error indication)

14 Successful TCH seizure rate after allocation

15 TCH seizure failure rate (caused by channel)

16 TCH call drop rate (caused by channel)

I. Average num. of idle TCHs in Interf. band 1


Interf. 0 -110~-105 dBm






The higher rank suggests higher interference level. Normally, an idle channel at Interf. 4 or 5 suggests the existence of interference. This item measures the average times of the uplink interference level rank of an idle TCH of a TRX at Interf. 1 within the measurement cycle.

Measurement point: System gets the number of idle TCHs at Interf. 1 every five seconds. At the end of the measurement cycle, the total number from all sampling points is divided with the times of sampling to get the average number of idle TCHs at Interf. 1.

Formula: none.

II. Average num. of idle TCHs in Interf. band 2


Interf. 0 -110~-105 dBm


427








Formula: none.

III. Average num. of idle TCHs in Interf. band 3


Interf. 0 -110~-105 dBm








Formula: none.

428


IV. Average num. of idle TCHs in Interf. band 4


Interf. 0 -110~-105 dBm








Formula: none.

V. Average num. of idle TCHs in Interf. band 5


Interf. 0 -110~-105 dBm







429



Formula: none.

VI. Num. of the uplink Interf. indication message in seized TCH

Description: In the application of Huawei II channel allocation algorithm, BSC calculates the priority rank of channel interference indication according to the channel interference indication message reported by LAPD module. The priority rank is the basis for the subsequent channel allocation. LAPD compares the level and quality in the measurement report reported by MS via this channel with the threshold configured to decide whether to send interference indication message to BSC. If both level and quality exceeds the threshold, LAPD sends interference indication message to BSC. This item measures the number of uplink interference indication messages of a TCH within the measurement cycle received by BSC.

Measurement point: This item is measured when BSC receives an uplink interference indication message of a TCH reported by LAPD module.

Formula: none.

VII. Num. of the downlink Interf. indication message in seized TCH

Description: In the application of Huawei II channel allocation algorithm, BSC calculates the priority rank of channel interference indication according to the channel interference indication message reported by LAPD module. The priority rank is the basis for the subsequent channel allocation. LAPD compares the level and quality in the measurement report reported by MS via this channel with the threshold configured to decide whether to send interference indication message to BSC. If both level and quality exceeds the threshold, LAPD sends interference indication message to BSC. This item measures the number of downlink interference indication messages of a TCH within the measurement cycle received by BSC.

Measurement point: This item is measured when BSC receives a downlink interference indication message of a TCH reported by LAPD module.

Formula: none.

VIII. TCH allocations

Description: This item measures the times of BSC radio resource management module successfully finding idle TCH after receiving TCH requests, including the times of successfully preempting TCH. BSC sends CHANNEL ACTIVATION to BTS afterwards to activate this TCH.

430


Measurement point: This item is measured when BSC radio resource management module successfully finding or successfully preempting an idle TCH after receiving TCH requests.

Formula: none.

IX. Successful TCH seizures

Description: This item measures the times of MS successfully seizing the TCHs allocated by the network during the procedure of very early assignment, assignment and handover. Successful directed retries during assignment are also regarded as successful TCH seizures. After the ASSIGNMENT REQUEST from MSC is sent to a certain cell of BSC, if this cell has no channel available and system supports directed retry, BSC will initiate outgoing inter cell handover according to the adjacent cell information in MS measurement report (MR). In the case of BSC internal directed retry, the destination cell sends ASSIGNMENT COMPLETE to MSC, but it is the originating cell that measures this item. Directed retry takes place only in the procedure of TCH assignment.

Measurement:1) In the procedure of very early assignment, this item is measured when

BTS sends CHANNEL ACTIVATION ACKNOWLEDGE message to BSC.2) If the destination cell of directed retry is from other BSC, after directed

retry is successfully implemented, MSC sends CLEAR COMMAND to originating cell to clear the original connection. This item is measured when the originating cell of the local BSC receives CLEAR COMMAND.

3) If the destination cell of directed retry is from local BSC, after directed retry is successfully implemented, the destination cell notifies the originating cell to clear the original resource and connection. This item is measured when the originating cell of the local BSC receives this Internal Clear Request.

4) After successful implementation of TCH assignment, BSC sends ASSIGNMENT COMPLETE to MSC. This item is measured in this case.

5) During the procedure of Incoming BSC handover (TCH handover), when the destination cell receives HANDOVER DETECTION from BTS, this item is measured.

6) During the procedure of Incoming inter cell handover (TCH handover), when the destination cell receives HANDOVER DETECTION from BTS, this item is measured.

Formula: none.

431


X. TCH seizure failures (caused by channel)

Description: This item measures the times of TCH seizure failures due to BTS channel activation failures or unsuccessful MS access the assigned channels during the procedure of very early assignment, assignment and handover.

Measurement point:1) In the procedure of very early assignment, after BSC sends CHANNEL

ACTIVATION to BTS, BTS does not respond or returns CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE. This item is measured in this case.

2) In the procedure of assignment, after BSC sends CHANNEL ACTIVATION to BTS, BTS does not respond or returns CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE. This item is measured in this case. This item can also be measured when MS fails to access the assigned channel and returns to the original channel and reports this assignment failure via original channel. In this case, the cause value reported by BSC to MSC is reverting to old channel (0x0a). If MS can neither access the assigned channel nor return to the original channel, the cause value reported is radio interface message failure (0x00). This item is also measured in this case.

3) In the procedure of BSC internal incoming cell handover (TCH handover), after BSC sends CHANNEL ACTIVATION to BTS, BTS does not respond or returns CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE. This item is measured in this case. When the destination cell waiting for HANDOVER DETECTION from BTS times out, is also measured. And when the originating cell receives HANDOVER FAILURE from MS or CONNECTION FAILURE INDICATION or ERROR INDICATION from BTS, this item is also measured.

4) In the procedure of incoming inter BSC handover (TCH handover), BSC sends CHANNEL ACTIVATION to BTS, BTS does not respond or returns CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE. This item is measured in this case.

5) Formula: none.

XI. TCH call drops (caused by channel)

Description: This item measures the times of call drops after TCH seizures due to message decoding failure at air interface or radio link broken

Measurement point:1) BTS detects TCH radio link failure or hardware link failure, and sends

CONNECTION FAILURE INDICATION to BSC to indicate that call drop happens at the air interface due to radio link connection failure. This item is measured when BSC receives this message.

432


2) BTS sends ERROR INDICATION to BSC due to TCH radio link layer connection abnormal so as to notify BSC the call drop at air interface due to radio link failure. This item is measured when BSC receives ERROR INDICATION (cause: timer T200 expired (N200 + 1) times (0x01), unsolicited DM response, multiple frame established state (0x05), sequence error (0x07)).

3) In the procedure of BSC internal outgoing inter cell handover, this item is measured when waiting for the Internal Handover Complete message times out.

4) In the procedure of outgoing inter BSC handover, this item is measured when waiting for CLEAR COMMAND with cause of handover success times out.

Formula: none.

XII. TCH lost radio connections (connection failure)

Description: BTS detects TCH radio link failure, and sends CONNECTION FAILURE INDICATION to BSC to indicate that call drop happens at the air interface due to radio link connection failure. This item measures the times of receiving CONNECTION FAILURE INDICATION (cause: all causes described in "GSM 0858" except for equipment failure (0X20) and terrestrial channel failure (0X22)).

Measurement point: This item is measured when BSC receives CONNECTION FAILURE INDICATION (cause: all causes described in GSM 0858 except for equipment failure (0X20) and terrestrial channel failure (0X22)) from the TCH of objective cell.

Formula: none.

XIII. TCH lost radio connections (error indication)

Description: BTS sends ERROR INDICATION to BSC due to TCH radio link layer connection abnormal so as to notify BSC the call drop at air interface due to radio link failure. This item is measured when BSC receives ERROR INDICATION (cause: timer T200 expired (N200 + 1) times (0x01), unsolicited DM response, multiple frame established state (0x05), sequence error (0x07)). See "GSM 0858".

Measurement point: This item is measured when BSC receives ERROR INDICATION (cause: timer T200 expired (N200 + 1) times (0x01), unsolicited DM response, multiple frame established state (0x05), sequence error (0x07)) from the TCH of the objective cell.

Formula: none.

433


XIV. Successful TCH seizure rate after allocation

Description: This item measures the percentage of times of MS successfully seizing TCHs accounting times of BSC successfully allocating TCHs. See Successful TCH seizures and TCH allocations .

Measurement point: none. Formula: successful TCH seizures / TCH allocations

XV. TCH seizure failure rate (caused by channel)

Description: This item measures the percentage of times of unsuccessful MS seizing TCHs due to channel related causes accounting times of BSC successfully allocating channels. See TCH seizure failures (caused bychannel) and TCH allocations

Measurement point: none. Formula: TCH seizure failures (caused by channel) / times of TCH allocations

XVI. TCH call drop rate (caused by channel)

Description: This item measures the percentage of TCH call drops (caused by channel) accounting for successful TCH seizures. See TCH call drops (causedby channel) and Successful TCH seizures .

Measurement point: none. Formula: TCH call drops (caused by channel) / successful TCH seizures

3.11.4 TRX Level Measurement Function


Table 3-11 Statistic items in TRX Level Measurement Function

No. Item name

1Handover Times

2Completed Handovers

3Immediate Assignment Commands

4Successful Immediate Assignment Commands

5Assignment Command Times

6Assignment Complete Times

7Channel Mode Modifies

8Channel Mode Modify Acknowledges

I. Handover Times

Description: This item provides the times of target cell’s successful response of handovers from source cell to target cell's specified TRX. The handover type

434


may be internal inter cell handover or interBSC inter cell handover. The handover can be either between SDCCHs or bewteen TCHs. This item indicates the frequency of handovers to target cell's specified TRX. Together with HANDOVER COMPLETE message , this item helps provide the radio handover success rate of specified TRX.

Measurement point: 1) In the case of internal inter-cell handover, after handover algorithm

decision, the source cell sends an Intercell Handover Request message to target cell. After successfully activating new channel on a TRX, the target cell will send Intercell Handover Response message to inform the source cell that the channel is ready.This item measures the times of this message sent by the target cell for the specified TRX.

2) In the case of incoming BSC handover, after the target BSC receives the HANDOVER REQUEST message from MSC, it checks the conditions of incoming handover. If the check passed, the target BSC will request channel resource, generate and store the HANDOVER COMMAND message in buffer, and at the same time, it will send CHANNAL ACTIVATION to BTS. After receiving CHANNAL ACTIVATION ACKNOWLEDGE, the BSC packs the HANDOVER COMMAND message into HANDOVER REQUEST ACKNOWLEDGE, which will then be sent to MSC. MSC transfers this message to the source BSC, and the source BSC sends the HANDOVER COMMAND message to MS. This item measures the times of target BSC sending HANDOVER REQUEST ACKNOWLEDGE to MSC for the specified TRX.

Formula: None.

II. Completed Handovers

Description: This item provides the times of completed handovers to target cell's specified TRX. The handover type may be internal inter cell handover or interBSC inter cell handover. The handover can be either between SDCCHs or bewteen TCHs. This item indicates the times of completed handovers to target cell's specified TRX. Together with the handover times, this item shows the radio handover success rate of specified TRX.

Measurement point: After the source cell sending HANDOVER COMMAND to MS, the target cell receives the HANDOVER COMPLETE message. This item measures the times of this message received at the target cell for the specified TRX.

Formula: None.

435


III. Immediate Assignment Commands

Description: This item measures the times of IMMADIATE ASSIGNMENT COMMAND message sent at specified cell's specified TRX. Upon reception of the CHANNEL REQUEST message reported from MS, BSC allocates and activates a signaling channel for the MS. If BSC receives the CHANNEL ACTIVATION ACKNOWLEDGE message from BTS indicating that the channel is ready, BSC sends an IMMEDIATE ASSIGNMENT COMMAND message informing the MS to access to the dedicated signaling channel, which can be either SDCCH or TCH.This item indicates the times of sending IMMEDIATE ASSIGNMENT COMMAND message. Together with the times of ESTABLISH INDICATION message, this item shows the radio immediate assignmet success rate.

Measurement point: This item is measured when BSC sends the IMMEDIATE ASSIGN COMMAND message to MS. BSC measures this item at the TRX from which the MS access the network.

Formula: None.

IV. Successful Immediate Assignment Commands

Description: This item measures the times of ESTABLISH INDICATION message received at specified cell's specified TRX. Upon reception of the CHANNEL REQUEST message reported from MS, BSC allocates and activates a signaling channel for the MS, and sends an IMMEDIATE ASSIGNMENT COMMAND message informing the MS to access to the dedicated signaling channel. Upon reception of a SABM frame on a link on the actived channel, the BTS sends an ESTABLISH INDICATION message to BSC. Together with the times of IMMEDIATE ASSIGNMENT COMMAND message this item shows the radio immediate assignmet success rate.

Measurement point: This item is measured when BSC receives the ESTABLISH INDICATION message from BTS. BSC measures this item at the TRX from which the MS access the network.

Formula: None.

V. Assignment Command Times

Description: This item measures the times of ASSIGNMENT COMMAND to MS sent at specified cell's specified TRX. The initial random access by the MS and "Immediate Assignment" to a DCCH is handled autonomously by the BSS without reference to the MSC. After the RR connection is established between MS and BSS, MS establishes the MM and CC connection with MSC on this channel. MSC allocates or reallocates to the MS a radio (and possibly terrestrial) resource in ASSIGNMENT REQUEST message according to MS's CC connection request.When the BSC receives the ASSIGNMENT REQUEST

436


message from MSC, it initiates the channel assignment procedure by sending an ASSIGNMENT COMMAND message to the mobile station on the main signalling link. This item indicates the times of ASSIGNMENT COMMAND message at the specified TRX. Together with the times of ASSIGNMENT COMPLETE message, this item shows the radio assignmet success rate.

Measurement point: This item is measured when BSC receives the ASSIGNMENT REQUEST message from MSC, and sends the ASSIGNMENT COMMAND to MS.

Formula: None.

VI. Assignment Complete Times

Description: This item measures the times of ASSIGNMENT COMPLETE message from MS at specified cell's specified TRX. When the BSC receives the ASSIGNMENT REQUEST message from MSC, it initiates the channel assignment procedure by sending an ASSIGNMENT COMMAND message to the mobile station on the main signalling link. After the main signalling link is successfully established, the mobile station returns an ASSIGNMENT COMPLETE message to BSC, then BSC transfer the message to MSC. This item indicates the times of ASSIGNMENT COMMAND message at the specified TRX. Together with the times of ASSIGNMENT COMMAND message, this item shows the radio assignmet success rate.

Measurement point: When the BSC receives the ASSIGNMENT REQUEST message from MSC, it initiates the channel assignment procedure by sending an ASSIGNMENT COMMAND message to the mobile station on the main signalling link. After the main signalling link is successfully established, the mobile station returns an ASSIGNMENT COMPLETE message to BSC, this item is measured.

Formula: None.

VII. Channel Mode Modifies

Description: This item measures the times of CHANNEL MODE MODIFY message to MS at specified cell's specified TRX. This procedure is used by BSC to request a change of the channel mode of an active channel. The BSC initiates this procedure by sending a MODE MODIFY message to the BTS and after receives the MODE MODIFY ACKNOWLEDGE message from the BTS, it then sends CHANNEL MODE MODIFY message to the MS.This item indicates the times that BSC sending CHANNEL MODE MODIFY message to MS at the specified TRX. Together with the times of CHANNEL MODE MODIFY ACKNOWLEDGE message, this item shows the radio channel mode modify success rate.

437


Measurement point: When BSC receives the MODE MODIFY ACKNOWLEDGE message from the BTS, and sends CHANNEL MODE MODIFY message to the MS, this item is measured.

Formula: None.

VIII. Channel Mode Modify Acknowledges

Description: This item measures the times of CHANNEL MODE MODIFY ACKNOWLEDGE message from MS at spcified cell's spcified TRX. This procedure is used by BSC to request a change of the channel mode of an active channel. The BSC initiates this procedure by sending a MODE MODIFY message to the BTS and after receives the MODE MODIFY ACKNOWLEDGE message from the BTS, it then sends CHANNEL MODE MODIFY message to the MS. When the MS has received the CHANNEL MODE MODIFY message, it sets the mode for the indicated channel, and then replies by a CHANNEL MODE MODIFY ACKNOWLEDGE message indicating the ordered channel mode. If the mobile station does not support the indicated mode, it will remain in the old mode and return the current associated channel mode information within the CHANNEL MODE MODIFY ACKNOWLEDGE message, and when the BSC receives this message, it compares the channel mode received from MS and requested to MS. If they are uniform, the BSC will consider this procedure as a success, otherwise, as a failure. This item indicates the times that BSC receivs CHANNEL MODE MODIFY ACKNOWLEDGE message from MS at the given TRX and the mode modify procedure is successful. Together with the times of CHANNEL MODE MODIFY message, this item shows the radio channel mode modify success rate.

Measurement point: This item is measured when BSC receives the CHANNEL MODE MODIFY ACKNOWLEDGE message from the MS at the given TRX and the mode modify procedure is successful.

Formula: None.

3.14 Cell Flow Control Measurement Function

3.14.1 General

"Cell Flow Control Measurement Function" shows the resources utilization of the cell and BTS that the cell belongs to. All the statistic items in this part are listed in Table 3-1 .

The statistic items of this measurement type can be registered selectively according to necessity.

Recommended period: 60 minutes

438


Measurement object cell

Table 3-1 Statistic items in Cell Flow Control Measurement Function

No. Item name

1Delete indications

2CCCH load indications (Circuit RACH overload)

3CCCH load indications (Circuit PCH overload)

4TRX overloads (CCCH overload)

5TRX overloads (TRX processor overload)

6TCH overloads

7Load indications to MSC

8Times of TCH convert to SDCCH

9Times of SDCCH convert to TCH


I. Delete indications

Description: When an IMMEDIATE ASSIGN COMMAND message is deleted due to downlink CCCH overload, BTS reports the DELETE INDICATION message. This item measures the number of times BSC receives the DELETE INDICATION message from the current cell within the measurement cycle.

Measurement point: This item is measured when BSC receives the DELETE INDICATION message reported by BTS.

Formula: none.

II. CCCH load indications (Circuit RACH overload)

Description: When the uplink CCCH (RACH) is overload, BTS sends CCCH LOAD INDICATION (RACH overload) BSC. Currently Huawei BSS does not support the RACH overload of packet service; therefore packet call caused RACH overload is also regarded as circuit service RACH overload. Besides, when the downlink CCCH is overload, BTS not only reports overload to BSC, but also distinguishes between overload caused by packet service and overload caused by circuit service. In the former case, CCCH LOAD INDICATION is sent to BSC, and in the latter case, PACKET CCCH LOAD INDICATIN is sent to PCU.

Measurement point: This item is measured when BSC receives the CCCH LOAD INDICATION (cause: uplink CCCH (RACH) overload) message from BTS.

Formula: none.

439


III. CCCH load indications (Circuit PCH overload)

Description: BTS stores the downlink CCCH (PCH) messages from BSC and PCU in different receiving buffer queues. Downlink CCCH overload takes place when the length of a receiving buffer queue exceeds the threshold. Whether CCCH LOAD INDICATION is reported to PCU or BSC depends on the overloaded queue.

Measurement point: This item is measured when BSC receives the CCCH LOAD INDICATION (cause: circuit service downlink CCCH (PCH) overload) message.

Formula: none.

IV. TRX overloads (CCCH overload)

Description: This item measures the number of times BSC receives the OVERLOAD (cause: CCCH overload) message from the objective cell within the measurement cycle. That means, when BTS detects CCCH overload, it reports OVERLOAD (cause: CCCH overload) to BSC, and at the same time, it also reports CCCH LOAD INDICATION to BSC.

440


Note:

TRX overload reports (CCCH overload) = CCCH load reports (RACH overload) + CCCH load reports

(PCH overload) (including circuit service and packet service). However, in practice, BER may cause

difference of this equation.

Measurement point: This item is measured when BSC receives the OVERLOAD (cause: CCCH overload) message from BTS.

Formula: none.

V. TRX overloads (TRX processor overload)

Description: This item measures the number of times BSC receives the OVERLOAD (cause: TRX processor overload) message from the objective cell within the measurement cycle. TRX processor overload means the CPU occupation of the TRX processor under the measured cell exceeds the threshold. This item has no direct relation with CCCH overload.

Measurement point: This item is measured when BSC receives the OVERLOAD (cause: TRX processor overload) message from BTS.

Formula: none.

VI. TCH overloads

Description: On the occasion of TCH flow control, this item is measured when the number of idle service channels is smaller than the number threshold of service channels. Whenever this happens, BSC will adjust cell flow ranks, which affects the minimum access level in the system message issued by BSC. The higher cell flow rank suggests higher minimum access level, and it is more difficult for MS to access or camp on the current cell. But in practice, the function of TCH flow control is prohibited, so the result of this index is 0.

Measurement point: On the occasion of TCH flow control, this item is measured when the number of idle service channels is smaller than the number threshold of service channels.

Formula: none.

VII. Load indications to MSC

Description: BSC finds that a cell has no service channel available, but this cell has been configured with external adjacent cell, to prevent the handovers from adjacent cell to the current cell, BSC sends LOAD INDICATION to MSC, which forwards this message to the BSS where the adjacent cell is located. The external adjacent cell will leave the congested cells out of candidate list. BSC checks the number of idle service channels every five seconds.

441


Measurement point: BSC finds that a cell has no service channel available, but this cell has been configured with external adjacent cell. to prevent the handovers from adjacent cell to the current cell, BSC sends LOAD INDICATION to MSC. This item is measured when BSC sends this message to MSC.

Formula: none.

VIII. Times of TCH convert to SDCCH

Description: On the occasion that SDCCH dynamic convert is allowed, if BSC finds that the number of idle SDCCHs in the current cell is smaller than the number threshold when allocating SDCCH, it starts to convert a TCH to SDCCH. If the coverted TCH is idle, TCH is dynamically converted to SDCCH immediately. Otherwise, the call seizing the current TCH will be handed over to other channel, and then dynamic convert is initiated. This item is measured when dynamic convert is implemented.

Measurement point: This item is measured when BSC initiates TCH dynamic convert (TCH to SDCCH).

Formula: none.

IX. Times of SDCCH convert to TCH

Description: On the occasion that SDCCH dynamic convert is allowed, BSC first initiates dynamic convert algorithm (leaky bucket algorithm). When necessary, the TCH dynamically converted to SDCCH will be converted back to TCH. This item measures the times of SDCCH converted to TCH.

Measurement point: This item is measured when a SDCCH is converted back to TCH.

Formula: none.

3.15 GPRS Related Measurement Function

3.15.1 General

Huawei BSS consists of BSC, BTS and PCU. The packet data is transferred to the core network of GPRS via BTS, BSC and PCU. The signaling transmission path is MS – BTS – BSC (BSC performs partial management) – PCU – SGSN.

Huawei BSS system supports the following combined channels:

1) PBCCH + PCCCH + PDTCH + PACCH + PTCCH

PCCCH + PDTCH + PACCH + PTCCHPDTCH + PACCH + PTCCH

Note that: PCCCH = PPCH + PRACH + PAGCH + PNCH.

442


Currently, most MSs does not support the first two types of combined channels, so CCCH is usually used to realize the function of PCCCH, BCCH realizes the function of PBCCH. This means that normally only the combination of PDTCH + PACCH + PTCCH (called PDCH) is applied.

The packet call procedure at BTS-BSC side only consists of immediate assignment procedure. The immediate assignment process is as follows: MS is accessed the network via RACH, and It sends CHANNEL REQUEST (contained cause value: Packet Call (0 x 03)) to request for PDCH. When BSC decides that this request is a packet call request, it will forward this message to PCU, which will implement channel assignment. After assigning PDCH, PCU will initiate PACKET IMMEDIATE ASSIGNMENT COMMAND, which will be transparently transferred by BSC to MS. MS is then notified to access the assigned PDCH. After access PDCH, MS implements the corresponding signaling transmission and data transmission. PCU implements packet channel assignment according to the actual needs of the connection. The signaling concerning assignment is transmitted on PACCH. The packet service supports cell reselection, not handover process. When providing packet service, if it is necessary to set up circuit connection, BSC will notify PCU (then PCU notifies MS) to suspend the packet service, and give the priority to circuit service. After the circuit service is complete and the related link is released, BSC will resume the packet service.

All statistic items related to packet call and PDCH resources in BSS traffic statistic system are contained in this measurement function, and see Table 3-1 for details. For cells supporting GPRS, it is recommended to use a task to register these items, both during the initial operation and normal operation of the network so as to obtain the information about the implementation of packet call process and utilization of PDCH resources.

If there are many MSs supporting GPRS in a cell or some MS attach failed, there will be many Packet immediate assignment requests. It is possible to obtain the information of packet immediate assignment by comparing "Successful packet immediate assignments" and "Packet immediate assignment requests". The interface information tracing function provided by BSC and PCU can be used to trace the information at Pb interface.

Recommended cycle: 60 minutes

The measurement object of GPRS Related Measurement Function is cell.

Table 3-1 GPRS performance measurement

No. Item name

1 Packet immediate assignment requests

443


2 Successful packet immediate assignments

3 TCH requires to PCU by BSC

4 Successful TCH requires to PCU by BSC

5 Configured static PDCHs

6 Configured dynamic PDCHs

7 Average availabled PDCHs

8 Max num. of availabled PDCH

9 Min num. of availabled PDCH


I. Packet immediate assignment requests

Description: The packet call procedure at BSC-PCU side only consists of immediate assignment procedure, i.e. MS accesses the network via RACH. It sends CHANNEL REQUEST (contained cause value: Packet Call (0 x 03)) to request for PDCH. When BSC decides that this request is a packet call request, it will forward this message to PCU, which will implement channel assignment.

Measurement point: This item is measured when BSS receives CHANNEL REQUEST from MS.

Formula: none.

I. Successful packet immediate assignments

Description: On reception of CHANNEL REQUEST forwarded by BSS, PCU assigns channels, and then initiates PACKET IMMEDIATE ASSIGNMENT COMMAND.

Measurement: This item is measured when BSC receives PACKET IMMEDIATE ASSIGNMENT COMMAND from PCU.

Formula: none.

II. TCH requires to PCU by BSC

Description: Huawei BSS supports both static PDCH and dynamic PDCH. On the occasion of the former one, after GPRS cells start to function, PCU obtains the right to assign these channels, while BSC only has the right of basic maintenance, and will not implement the management and allocation of these channels. On the occasion of dynamic channel, the circuit service and packet service request for channels to each other when necessary, but the circuit service has the right to forcedly seize the channel.

444


Measurement point: When the circuit service needs to seize or plans to seize the dynamic PDCH currently seized by packet service, it will send BSC_PCU_TCH_REQ (Huawei Pb interface message) to PCU. This item is measured in this case.

Formula: none.

III. Successful TCH requires to PCU by BSC

Description: After BSC requires to get back dynamic PDCH from PCU, if PCU responds and agrees to this requirement, this item is measured.

Measurement point: This item is measured when BSC receives PCU_BSC_TCH_ACK (Huawei Pb interface message) from PCU.

Formula: none.

IV. Configured static PDCHs

Description: This item measures the average number of static PDCHs configured in a cell in each measurement cycle. This item is measured in sampling mechanism. BSC check the number of static PDCHs recorded in the database every five minutes. This number is accumulated within measurement cycle. At the end of measurement cycle, this accumulated number is divided with the times of accumulating (times of sampling) to get the value of this item. Therefore, this item may not be an integer.

Measurement point: At the end of each measurement cycle, the average number of static PDCH configured will be calculated and sent to BAM.

Formula: none.

V. Configured dynamic PDCHs

Description: This item measures the average number of dynamic PDCHs configured in a cell in each measurement cycle. This item is measured in sampling mechanism. BSC check the number of dynamic PDCHs recorded in the database every five minutes. Note that what concerned here is the configuration in the database. Even if the dynamic PDCH is currently used as TCH by BSC, this item will still be measured. This number is then accumulated within measurement cycle. At the end of measurement cycle, this accumulated number is divided with the times of accumulating (times of sampling) to get the value of this item. Therefore, this item may not be an integer.

Measurement point: At the end of each measurement cycle, the average number of dynamic PDCH configured will be calculated and sent to BAM.

Formula: none.

445


VI. Average availabled PDCHs

Description: This item measures the average number of available PDCHs in a cell within the measurement cycle, including the cells whose configuration status are "static PDCH" or "dynamic PDCH" and operation status are "PDCH" (i.e. the related channels are currently seized by packet service). The channel status can be either idle or using, but it should be an available channel. This item is measured in sampling mechanism. BSC check the number of dynamic PDCHs recorded in the database every five seconds. This number is accumulated within measurement cycle. At the end of measurement cycle, this accumulated number is divided with the times of accumulating (times of sampling) to get the value of this item. Therefore, this item may not be an integer.

Measurement point: At the end of each measurement cycle, the average available PDCHs will be calculated and sent to BAM.

Formula: none.

VII. Max num. of availabled PDCH

Description: This item measures the maximum number of available PDCHs in a cell within the measurement cycle, including the PDCHs whose configuration status are "static PDCH" or "dynamic PDCH" whose operation status are "PDCH". The channel status can be either idle or using.

Measurement point: At the end of each measurement cycle, the maximum number of available PDCH will be calculated and sent to BAM.

Formula: none.

VIII. Min num. of availabled PDCH

Description: This item measures the minimum number of available PDCHs in a cell within the measurement cycle, including the PDCHs whose configuration status are "static PDCH" or "dynamic PDCH" whose operation status are "PDCH". The channel status can be either idle or using.

Measurement point: At the end of each measurement cycle, the minimum number of available PDCH will be calculated and sent to BAM.

Formula: none.

3.16 Overlaid/Underlaid Subcell Measurement

3.16.1 General

When using the function of IUO cell, it is important to reasonably configure the TRXs of the overlaid subcell and underlaid subcell so that in the wide covered area the underlaid subcell can be used to provide remote coverage and the overlaid

446


subcell to bear the traffic; in the dense multiplexing area the less multiplexed TRX frequency (e.g. BCCH) can be used. With scientific configuration of the parameters related to overlaid and underlaid power, the system interference can be lowered to the greatest extent.

Overlaid/Underlaid Subcell Measurement Function is used to measure the IUO cell related indices such as times of overflow and handover success rate. These data can be used to decide whether the IUO channel allocation and IUO HO parameter configuration is reasonable.

The task of overlaid/underlaid subcell measurement is the cell. The module No., cell No. and TRX No. (or all cells in the module) of the task can be configured in Object Definition. All measurement items are listed in Table 3-1 .

Table 3-1 Statistic items in Overlaid/underlaid subcell measurement items

No. Item name

1Attempted TCH seizures in UnderLaid subcell meeting TCH overflow

2Attempted TCH seizures in OverLaid subcell meeting TCH overflow

3Number of TCH measurement reports in UnderLaid subcell

4Number of TCH measurement reports in OverLaid subcell

5Attempted handovers from UnderLaid subcell to OverLaid subcell

6Attempted handovers from OverLaid subcell to UnderLaid subcell

7Successful handovers from UnderLaid subcell to OverLaid subcell

8Successful handovers from OverLaid subcell to UnderLaid subcell

9Failed handovers from UnderLaid subcell to OverLaid subcell due to congestion

10Failed handovers from OverLaid subcell to UnderLaid subcell due to congestion

11Average uplink level of handovers from OverLaid subcell to UnderLaid subcell

12Average downlink level of handovers from OverLaid subcell to UnderLaid subcell

13Average timing advance(TA) of handovers from OverLaid subcell to UnderLaid subcell

14Average uplink level of handovers from UnderLaid subcell to OverLaid subcell

15Average downlink level of handovers from UnderLaid subcell to OverLaid subcell

16Average timing advance(TA) of handovers from UnderLaid subcell to OverLaid subcell)

17Attempted SDCCH seizures in UnderLaid subcell meeting SDCCH overflow

18Attempted SDCCH seizures in OverLaid subcell meeting SDCCH overflow

19Number of SDCCH measurement reports in UnderLaid subcell

20Number of SDCCH measurement reports in OverLaid subcell

21Attempted channel seizures in UnderLaid subcell only

22Attempted channel seizures in OverLaid subcell only

23Attempted channel seizures in UnderLaid subcell preferred

24Attempted channel seizures in OverLaid subcell preferred

25Attempted TCHF seizures in UnderLaid subcell meeting TCHF overflow

447


26Attempted TCHH seizures in UnderLaid subcell meeting TCHH overflow

27Attempted TCHF seizures in OverLaid subcell meeting TCHF overflow

28Attempted TCHH seizures in OverLaid subcell meeting TCHF overflow

29Failed handover preparings from Underlaid Subcell to Overlaid Subcell due to congestion

30Failed handover preparings from Overlaid Subcell to Underlaid Subcell due to congestion

31Handover requests incoming intra-BSC (Underlaid Subcell in prefrence)

32Handover requests incoming intra-BSC (Overlaid Subcell in prefrence)

33Overflows for incoming intra-BSC handover (Underlaid Subcell in prefrence)

34Overflows for incoming intra-BSC handover (Overlaid Subcell in prefrence)

35Handover requests incoming inter-BSC (Underlaid Subcell in prefrence)

36Handover requests incoming inter-BSC (Overlaid Subcell in prefrence)

37Overflows for incoming inter-BSC handover (Underlaid Subcell in prefrence)

38Overflows for incoming inter-BSC handover (Overlaid Subcell in prefrence)

39Assignment requests (Underlaid Subcell in prefrence)

40Assignment requests (Overlaid Subcell in prefrence)

41Assignment overflows (Underlaid Subcell in prefrence)

42Assignment overflows (Overlaid Subcell in prefrence)

43TCH traffic volume in UnderLaid subcell (ERL)

44TCH traffic volume in OverLaid subcell (ERL)

45Successful handover rate from underlaid subcell to overlaid subcell (%)

46Successful handover rate from overlaid subcell to underlaid subcell(%)


I. Attempted TCH seizures in UnderLaid subcell meeting TCH overflow

Description: When BSC needs to allocate TCH to MS for some reasons (e.g. assignment, immediate assignment, intra-BSC handover, inter-BSC handover), it will first fill the IUO property in the channel request according to the configured data, and then initiate the channel allocation process. If the requested IUO is underlaid subcell, but there is no idle TCH in underlaid subcell, this index will increase by 1. The information of times of IUO TCH overflow can be used to optimize the IUO channel allocation parameters and IUO handover parameter.

Measurement point: Measured when the TCH allocated by BSC for MS is in underlaid subcell, while the underlaid subcell has no idle TCH.

Formula: none.

448


II. Attempted TCH seizures in OverLaid subcell meeting TCH overflow

Description: When BSC needs to allocate TCH to MS for some reasons (e.g. assignment, immediate assignment, intra-BSC handover, inter-BSC handover), it will first fill the IUO property in the channel request according to the configured data, and then initiate the channel allocation process. If the requested IUO is overlaid subcell, but there is no idle TCH in overlaid subcell, this index will increase by 1. The information of times of IUO TCH overflow can be used to optimize the IUO channel allocation parameters and IUO handover parameter.

Measurement point: Measured when the TCH allocated by BSC for MS is in overlaid subcell, while the overlaid subcell has no idle TCH.

Formula: none.

III. Number of TCH measurement reports in UnderLaid subcell

Description: The total number of MRs received from the TCH of underlaid subcell. When BSS receives the MR from MS, if the serving cell is the underlaid subcell and currently seizes TCH, this index increases by 1.

Measurement point: Measured when BSS receives the MR from MS and the serving cell is underlaid subcell, and currently seizes TCH.

Formula: none.

IV. Number of TCH measurement reports in OverLaid subcell

Description: The total number of MRs received from the TCH of overlaid subcell. When BSS receives the MR from MS, if the serving cell is the overlaid subcell and currently seizes TCH, this index increases by 1.

Measurement point: Measured when BSS receives the MR from MS and the serving cell is overlaid subcell, and currently seizes TCH.

Formula: none.

V. Attempted handovers from UnderLaid subcell to OverLaid subcell

Description: Attempts of handover from underlaid to overlaid subcell. The index will increase by 1 when the serving cell is the underlaid subcell, and after the BSC handover decision algorithm process, system initiates the handover from underlaid to overlaid subcell. If the value of this index is too large, the configuration of IUO HO Data may be not reasonable.

Measurement point: Measured BSC initiates the handover from underlaid to overlaid subcell within a cell.

Formula: none.

449


VI. Attempted handovers from OverLaid subcell to UnderLaid subcell

Description: Attempts of handover from overlaid to underlaid subcell. The index will increase by 1 when the serving cell is the overlaid subcell, and after the BSC handover decision algorithm process, system initiates the handover from overlaid to underlaid subcell. If the value of this index is too large, the configuration of IUO HO Data may be not reasonable.

Measurement point: Measured BSC initiates the handover from overlaid to underlaid subcell within a cell.

Formula: none.

VII. Successful handovers from UnderLaid subcell to OverLaid subcell

Description: Times of successful handover from underlaid to overlaid subcell. The index will increase by 1 when the serving cell is the underlaid subcell, and after the BSC handover decision algorithm process, system initiates a successful handover from underlaid to overlaid subcell.

Measurement point: Measured BSC initiates a successful handover from underlaid to overlaid subcell within a cell.

Formula: none.

VIII. Successful handovers from OverLaid subcell to UnderLaid subcell

Description: Times of successful handover from overlaid to underlaid subcell. The index will increase by 1 when the serving cell is the overlaid subcell, and after the BSC handover decision algorithm process, system initiates a successful handover from overlaid to underlaid subcell.

Measurement point: Measured BSC initiates a successful handover from overlaid to underlaid subcell within a cell.

Formula: none.

IX. Failed handovers from UnderLaid subcell to OverLaid subcell due to congestion

Description: When the serving cell is the underlaid subcell, after the BSC handover decision algorithm process, system initiates a handover from underlaid to overlaid subcell. This index will increase by 1 if the handover failed due to overlaid subcell congestion. It is possible to judge whether the TCH configuration of overlaid subcell is reasonable with this index and "Attemptedhandovers from UnderLaid subcell to OverLaid subcell " as the reference.

Measurement point: Measured when the handover within a cell from underlaid to overlaid subcell failed due to overlaid subcell congestion.

Formula: none.

450


X. Failed handovers from OverLaid subcell to UnderLaid subcell due to congestion

Description: When the serving cell is the overlaid subcell, after the BSC handover decision algorithm process, system initiates a handover from overlaid to underlaid subcell. This index will increase by 1 if the handover failed due to underlaid subcell congestion. It is possible to judge whether the TCH configuration of underlaid subcell is reasonable with this index and "Attemptedhandovers from OverLaid subcell to UnderLaid subcell ".

Measurement point: Measured when the handover within a cell from ovderlaid to underlaid subcell failed due to underlaid subcell congestion.

Formula: none.

XI. Average uplink level of handovers from OverLaid subcell to UnderLaid subcell

Description: Average uplink level during the IUO handover from overlaid to underlaid subcell. When the serving cell is the overlaid subcell, after the BSC handover decision algorithm process, system initiates a handover from overlaid to underlaid subcell. The uplink level value in MR will be added to the sum in this case. The value of this index is generated by dividing the sum with the total times adding the level values within the measurement cycle. Note that, the measurement point is at the moment when the handover is initiated. No matter the handover afterwards is successful or not, the uplink level in MR that triggers the handover will be measured. This index can be used to judge whether the configuration of IUO HO Data is reasonable.

Measurement point: Measured when BSC initiates a handover from overlaid to underlaid subcell within a cell.

Formula: none.

XII. Average downlink level of handovers from OverLaid subcell to UnderLaid subcell

Description: Average downlink level during the IUO handover from overlaid to underlaid subcell. When the serving cell is the overlaid subcell, after the BSC handover decision algorithm process, system initiates a handover from overlaid to underlaid subcell. The downlink level value in MR will be added to the sum in this case. The value of this index is generated by dividing the sum with the total times adding the level values within the measurement cycle. Note that, the measurement point is at the moment when the handover is initiated. No matter the handover afterwards is successful or not, the downlink level in MR that triggers the handover will be measured. This index can be used to judge whether the configuration of IUO HO Data is reasonable.

451



Formula: none.

XIII. Average timing advance(TA) of handovers from OverLaid subcell to UnderLaid subcell

Description: Average TA during the IUO handover from overlaid to underlaid subcell. When the serving cell is the overlaid subcell, after the BSC handover decision algorithm process, system initiates a handover from overlaid to underlaid subcell. The TA value in MR will be added to the sum in this case. The value of this index is generated by dividing the sum with the total times adding the TA values within the measurement cycle. Note that, the measurement point is at the moment when the handover is initiated. No matter the handover afterwards is successful or not, the TA in MR that triggers the handover will be measured. This index can be used to judge whether the configuration of IUO HO Data is reasonable.


Formula: none.

XIV. Average uplink level of handovers from UnderLaid subcell to OverLaid subcell

Description: Average uplink level during the IUO handover from underlaid to overlaid subcell. When the serving cell is the underlaid subcell, after the BSC handover decision algorithm process, system initiates a handover from underlaid to ovderlaid subcell. The uplink level value in MR will be added to the sum in this case. The value of this index is generated by dividing the sum with the total times adding the level values within the measurement cycle. Note that, the measurement point is at the moment when the handover is initiated. No matter the handover afterwards is successful or not, the uplink level in MR that triggers the handover will be measured. This index can be used to judge whether the configuration of IUO HO Data is reasonable.

Measurement point: Measured when BSC initiates a handover from underlaid to overlaid subcell within a cell.

Formula: none.

XV. Average downlink level of handovers from UnderLaid subcell to OverLaid subcell

Description: Average downlink level during the IUO handover from underlaid to overlaid subcell. When the serving cell is the underlaid subcell, after the BSC handover decision algorithm process, system initiates a handover from

452


underlaid to ovderlaid subcell. The downlink level value in MR will be added to the sum in this case. The value of this index is generated by dividing the sum with the total times adding the level values within the measurement cycle. Note that, the measurement point is at the moment when the handover is initiated. No matter the handover afterwards is successful or not, the downlink level in MR that triggers the handover will be measured. This index can be used to judge whether the configuration of IUO HO Data is reasonable.


Formula: none.

XVI. Average timing advance(TA) of handovers from UnderLaid subcell to OverLaid subcell)

Description: Average TA during the IUO handover from underlaid to overlaid subcell. When the serving cell is the underlaid subcell, after the BSC handover decision algorithm process, system initiates a handover from underlaid to ovderlaid subcell. The TA value in MR will be added to the sum in this case. The value of this index is generated by dividing the sum with the total times adding the TA values within the measurement cycle. Note that, the measurement point is at the moment when the handover is initiated. No matter the handover afterwards is successful or not, the TA level in MR that triggers the handover will be measured. This index can be used to judge whether the configuration of IUO HO Data is reasonable.


Formula: none.

XVII. Attempted SDCCH seizures in UnderLaid subcell meeting SDCCH overflow

Description: After receiving an SDCCH request, BSC first fill the IUO property in the channel request according to the data configuration, and then initiates the channel allocation process. The value of this index will increase by 1 if the property of IUO that requests for channel is underlaid subcell while there is no idle SDCCH in this underlaid subcell. If the times of underlaid signaling channel overflow is large, the SDCCH configured for underlaid subcell is not enough, which often results in congestion.

Measurement point: Measured when the property of IUO that requests for channel is underlaid subcell while there is no idle SDCCH in this underlaid subcell.

Formula: none.

453


XVIII. Attempted SDCCH seizures in OverLaid subcell meeting SDCCH overflow

Description: After receiving an SDCCH request, BSC first fill the IUO property in the channel request according to the data configuration, and then initiates the channel allocation process. The value of this index will increase by 1 if the property of IUO that requests for channel is overlaid subcell while there is no idle SDCCH in this overlaid subcell. If the times of overlaid signaling channel overflow is large, the SDCCH configured for overlaid subcell is not enough, which often results in congestion.

Measurement point: Measured when the property of IUO that requests for channel is overlaid subcell while there is no idle SDCCH in this overlaid subcell.

Formula: none.

XIX. Number of SDCCH measurement reports in UnderLaid subcell

Description: Total number of MRs on the SDCCH of IUO underlaid subcell. The value of this index will increase by 1 if the serving cell is the underlaid subcell and SDCCH is currently seized when BSS receives the MR from MS.

Measurement point: Measured when BSS receives the MR from MS and the serving cell is the underlaid subcell and SDCCH is currently seized.

Formula: none.

XX. Number of SDCCH measurement reports in OverLaid subcell

Description: Total number of MRs on the SDCCH of IUO overlaid subcell. The value of this index will increase by 1 if the serving cell is the overlaid subcell and SDCCH is currently seized when BSS receives the MR from MS.

Measurement point: Measured when BSS receives the MR from MS and the serving cell is the overlaid subcell and SDCCH is currently seized.

Formula: none.

XXI. Attempted channel seizures in UnderLaid subcell only

Meaning: Times of different IUO properties in channel requests. When the IUO property is required to be underlaid subcell only in the channel request, this item increases by 1.

Measurement point: This item is measured when the IUO property is required to be underlaid subcell only in the channel request.

Formula: None.

454


XXII. Attempted channel seizures in OverLaid subcell only

Meaning: Times of different IUO properties in channel requests. When the IUO property is required to be overlaid subcell only in the channel request, this item increases by 1.

Measurement point: This item is measured when the IUO property is required to be overlaid subcell only in the channel request.

Formula: None.

XXIII. Attempted channel seizures in UnderLaid subcell preferred

Meaning: Times of different IUO properties in channel requests. When underlaid subcell is preferred for IUO property in the channel request, this item increases by 1.

Measurement point: This item is measured when underlaid subcell is preferred for IUO property in the channel request.

Formula: None.

XXIV. Attempted channel seizures in OverLaid subcell preferred

Meaning: Times of different IUO properties in channel requests. When overlaid subcell is preferred for IUO property in the channel request, this item increases by 1.

Measurement point: This item is measured when overlaid subcell is preferred for IUO property in the channel request.

Formula: None.

XXV. Attempted TCHF seizures in UnderLaid subcell meeting TCHF overflow

Meaning: Times of IUO channel assignment results deviating from channel allocation request. If the requested TCH is underlaid full rate while the allocated one is non-underlaid full rate or allocation fails, this item increases by 1. If the result of this item is too large, it suggests that the underlaid full rate TCH is not enough for channel allocation. This item can be used together with Attempted TCHH seizures in UnderLaid subcell meeting TCHH overflow , Attempted TCHF seizures in OverLaid subcell meeting TCHF overflow and Attempted TCHH seizures in OverLaid subcell meeting TCHF overflow as a reference for adjusting the ratio of full rate and half rate channels on IUO subcells.

Measurement point: This item is measured when the requested TCH is underlaid full rate while the allocated one is non-underlaid full rate or allocation fails.

Formula: None.

455


XXVI. Attempted TCHH seizures in UnderLaid subcell meeting TCHH overflow

Meaning: Times of IUO channel assignment results deviating from channel allocation request. If the requested TCH is underlaid full rate while the allocated one is non-underlaid full rate or allocation fails, this item increases by 1. If the result of this item is too large, it suggests that the underlaid full rate TCH is not enough for channel allocation. This item can be used together with Attempted TCHF seizures in UnderLaid subcell meeting TCHF overflow , Attempted TCHF seizures in OverLaid subcell meeting TCHF overflow and Attempted TCHH seizures in OverLaid subcell meeting TCHF overflow as a reference for adjusting the ratio of full rate and half rate channels on IUO subcells.

Measurement point: This item is measured when the requested TCH is underlaid half rate while the allocated one is non-underlaid half rate or allocation fails.

Formula: None.

XXVII. Attempted TCHF seizures in OverLaid subcell meeting TCHF overflow

Meaning: Times of IUO channel assignment results deviating from channel allocation request. If the requested TCH is overlaid full rate while the allocated one is non-overlaid full rate or allocation fails, this item increases by 1. If the result of this item is too large, it suggests that the overlaid full rate TCH is not enough for channel allocation. This item can be used together with AttemptedTCHF seizures in UnderLaid subcell meeting TCHF overflow , AttemptedTCHH seizures in UnderLaid subcell meeting TCHH overflow and AttemptedTCHH seizures in OverLaid subcell meeting TCHF overflow as a reference for adjusting the ratio of full rate and half rate channels on IUO subcells.

Measurement point: This item is measured when the requested TCH is overlaid full rate while the allocated one is non-overlaid full rate or allocation fails.

Formula: None.

XXVIII. Attempted TCHH seizures in OverLaid subcell meeting TCHF overflow

Meaning: Times of IUO channel assignment results deviating from channel allocation request. If the requested TCH is overlaid half rate while the allocated one is non-overlaid half rate or allocation fails, this item increases by 1. If the result of this item is too large, it suggests that the overlaid half rate TCH is not enough for channel allocation. This item can be used together with AttemptedTCHF seizures in UnderLaid subcell meeting TCHF overflow , Attempted

456


TCHH seizures in UnderLaid subcell meeting TCHH overflow and AttemptedTCHF seizures in OverLaid subcell meeting TCHF overflow as a reference for adjusting the ratio of half rate and half rate on IUO subcells.

Measurement point: This item is measured when the requested TCH is overlaid half rate while the allocated one is non-overlaid half rate or allocation fails.

Formula: None.

II. Failed handover preparings from Underlaid Subcell to Overlaid Subcell due to congestion

Description: During the handover from underlaid to overlaid subcell, BSC will check the overlaid channel seizure before sending Inter handover request. If overlaid subcell has no idle channel, this handover will not be initiated. This item provides the times of handovers not initiated due to no idle channel available in overlaid subcell. If the result of this item is large, it is necessary to adjust the traffic sharing ratio between overlaid and underlaid subcells.

Measurement point: During the handover from underlaid to overlaid subcell, BSC will check the overlaid channel seizure before sending Inter handover request. This item is measured if overlaid subcell has no idle channel.

Formula: None.

III. Failed handover preparings from Overlaid Subcell to Underlaid Subcell due to congestion

Description: During the handover from overlaid to underlaid subcell, BSC will check the underlaid channel seizure before sending Inter handover request. If underlaid subcell has no idle channel, this handover will not be initiated. This item provides the times of handovers not initiated due to no idle channel available in underlaid subcell. If the result of this item is large, it is necessary to adjust the traffic sharing ratio between overlaid and underlaid subcells.

Measurement point: During the handover from overlaid to underlaid subcell, BSC will check the underlaid channel seizure before sending Inter handover request. This item is measured if underlaid subcell has no idle channel.

Formula: None.

IV. Handover requests incoming intra-BSC (Underlaid Subcell in prefrence)

Description: This item provides the times of underlaid subcell in preference during intra BSC incoming cell handover. Overflows for incoming intra-BSChandover (Underlaid Subcell in prefrence) and this item together show the utilization of underlaid subcell. If the times of congestions accounts a large proportion of the total requests, it means that the underlaid subcell channels

457


are congested, and the traffic sharing ratio between underlaid and overlaid subcells needs to be adjusted.

Measurement point: This item is measured when the channel request is underlaid subcell in preference during intra BSC incoming cell handover procedure.

Formula: None.

V. Handover requests incoming intra-BSC (Overlaid Subcell in prefrence)

Description: This item provides the times of overlaid subcell in preference during intra BSC incoming cell handover. Overflows for incoming intra-BSChandover (Overlaid Subcell in prefrence) and this item together show the utilization of overlaid subcell. If the times of congestions accounts a large proportion of the total requests, it means that the overlaid subcell channels are congested, and the traffic sharing ratio between underlaid and overlaid subcells needs to be adjusted.

Measurement point: This item is measured when the channel request is overlaid subcell in preference during intra BSC incoming cell handover procedure.

Formula: None.

VI. Overflows for incoming intra-BSC handover (Underlaid Subcell in prefrence)

Description: This item provides the times of channel allocation failures or times of overlaid channel allocated due to underlaid channel congestion during intra BSC incoming cell handover in which the underlaid channel is in preference in the requests. Handover requests incoming intra-BSC (Underlaid Subcell inprefrence) and this item together show the utilization of underlaid subcell. If the times of congestions accounts a large proportion of the total requests, it means that the underlaid subcell channels are congested, and the traffic sharing ratio between underlaid and overlaid subcells needs to be adjusted.

Measurement point: This item is measured when the channel request is underlaid subcell in preference but the channel allocation failed or overlaid channel is allocated during intra BSC incoming cell handover.

Formula: None.

VII. Overflows for incoming intra-BSC handover (Overlaid Subcell in prefrence)

Description: This item provides the times of channel allocation failures or times of underlaid channel allocated due to overlaid channel congestion during intra BSC incoming cell handover in which the overlaid channel is in preference in the requests. Handover requests incoming intra-BSC (Overlaid Subcell in

458


prefrence) and this item together show the utilization of overlaid subcell. If the times of congestions accounts a large proportion of the total requests, it means that the overlaid subcell channels are congested, and the traffic sharing ratio between underlaid and overlaid subcells needs to be adjusted.

Measurement point: This item is measured when the channel request is overlaid subcell in preference but the channel allocation failed or underlaid channel is allocated during intra BSC incoming cell handover.

Formula: None.

VIII. Handover requests incoming inter-BSC (Underlaid Subcell in prefrence)

Description: This item provides the times of Underlaid Subcell in preference in the requests during inter BSC handover. Overflows for incoming inter-BSChandover (Underlaid Subcell in prefrence) and this item together show the utilization of underlaid subcell. If the times of congestions accounts a large proportion of the total requests, it means that the underlaid subcell channels are congested, and the traffic sharing ratio between underlaid and overlaid subcells needs to be adjusted.

Measurement point: This item is measured when the channel request is underlaid subcell in preference in an incoming inter BSC handover.

Formula: None.

IX. Handover requests incoming inter-BSC (Overlaid Subcell in prefrence)

Description: This item provides the times of Overlaid Subcell in preference in the requests during inter BSC handover. Overflows for incoming inter-BSChandover (Overlaid Subcell in prefrence) and this item together show the utilization of overlaid subcell. If the times of congestions accounts a large proportion of the total requests, it means that the overlaid subcell channels are congested, and the traffic sharing ratio between underlaid and overlaid subcells needs to be adjusted.

Measurement point: This item is measured when the channel request is overlaid subcell in preference in an incoming inter BSC handover.

Formula: None.

X. Overflows for incoming inter-BSC handover (Underlaid Subcell in prefrence)

Description: This item provides the times of channel allocation failures or times of overlaid channel allocated due to underlaid channel congestion during incoming inter BSC handover in which the underlaid channel is in preferrence in the requests. Handover requests incoming inter-BSC (Underlaid Subcell inprefrence) and this item together show the utilization of underlaid subcell. If

459


the times of congestions accounts a large proportion of the total requests, it means that the underlaid subcell channels are congested, and the traffic sharing ratio between underlaid and overlaid subcells needs to be adjusted.

Measurement point: This item is measured when the channel request is underlaid subcell in preference but the channel allocation failed or overlaid channel is allocated during incoming inter BSC handover.

Formula: None.

XI. Overflows for incoming inter-BSC handover (Overlaid Subcell in prefrence)

Description: This item provides the times of channel allocation failures or times of underlaid channel allocated due to overlaid channel congestion during incoming inter BSC handover in which the overlaid channel is in preference in the requests. Handover requests incoming inter-BSC (Overlaid Subcell inprefrence) and this item together show the utilization of overlaid subcell. If the times of congestions accounts a large proportion of the total requests, it means that the overlaid subcell channels are congested, and the traffic sharing ratio between underlaid and overlaid subcells needs to be adjusted.

Measurement point: This item is measured when the channel request is overlaid subcell in preference but the channel allocation failed or underlaid channel is allocated during incoming inter BSC handover.

Formula: None.

XII. Assignment requests (Underlaid Subcell in prefrence)

Description: This item provides the times of Underlaid Subcell in preference during assignment procedure. Assignment overflows (Underlaid Subcell inprefrence) and this item together show the utilization of underlaid subcell. If the times of congestions accounts a large proportion of the total requests, it means that the underlaid subcell channels are congested, and the traffic sharing ratio between underlaid and overlaid subcells needs to be adjusted.

Measurement point: This item is measured when the channel request is Underlaid Subcell in preference during assignment procedure.

Formula: None.

XIII. Assignment requests (Overlaid Subcell in prefrence)

Description: This item provides the times of overlaid Subcell in preference during assignment procedure. Assignment overflows (Overlaid Subcell inprefrence) and this item together show the utilization of overlaid subcell. If the times of congestions accounts a large proportion of the total requests, it means that the overlaid subcell channels are congested, and the traffic sharing ratio between underlaid and overlaid subcells needs to be adjusted.

460


Measurement point: This item is measured when the channel request is overlaid Subcell in preference during assignment procedure.

Formula: None.

XIV. Assignment overflows (Underlaid Subcell in prefrence)

Description: This item provides the times of channel allocation failures or times of overlaid channel allocated due to underlaid channel congestion during channel assignment in which the underlaid channel is in preference in the requests. Assignment requests (Underlaid Subcell in prefrence) and this item show the utilization of underlaid subcell. If the times of congestions accounts a large proportion of the total requests, it means that the underlaid subcell channels are congested, and the traffic sharing ratio between underlaid and overlaid subcells needs to be adjusted.

Measurement point: This item is measured when the channel request is underlaid subcell in preference but the channel allocation failed or overlaid channel is allocated during channel assignment.

Formula: None.

XV. Assignment overflows (Overlaid Subcell in prefrence)

Description: This item provides the times of channel allocation failures or times of underlaid channel allocated due to overlaid channel congestion during channel assignment in which the overlaid channel is in preference in the requests. Assignment requests (Overlaid Subcell in prefrence) and this item show the utilization of overlaid subcell. If the times of congestions accounts a large proportion of the total requests, it means that the overlaid subcell channels are congested, and the traffic sharing ratio between underlaid and overlaid subcells needs to be adjusted.

Measurement point: This item is measured when the channel request is overlaid subcell in preference but the channel allocation failed or underlaid channel is allocated during channel assignment.

Formula: None.

XXIX. TCH traffic volume in UnderLaid subcell (ERL)

Description: Underlaid TCH traffic. This is an analysis index. Unit: ERL. It is calculated from Number of TCH measurement reports in UnderLaid subcell .

Measurement point: none. Formula: Number of TCH measurement reports in UnderLaid subcell 0.48 /

Measurement cycle (second)

461


XXX. TCH traffic volume in OverLaid subcell (ERL)

Description: Overlaid TCH traffic. This is an analysis index. Unit: ERL. It is calculated from Number of TCH measurement reports in OverLaid subcell .

Measurement point: none. Formula: Number of TCH measurement reports in OverLaid subcell 0.48 /

Measurement cycle (second)

XXXI. Successful handover rate from underlaid subcell to overlaid subcell (%)

Description: Success rate of IUO handover from underlaid to overlaid subcell. This is an analysis index. Unit: %. It is calculated from Successful handoversfrom UnderLaid subcell to OverLaid subcell and Attempted handovers fromUnderLaid subcell to OverLaid subcell .

Measurement point: none. Formula: Successful handovers from UnderLaid subcell to OverLaid subcell /

Attempted handovers from UnderLaid subcell to OverLaid subcell

XXXII. Successful handover rate from overlaid subcell to underlaid subcell(%)

Description: Success rate of IUO handover from overlaid to underlaid subcell. This is an analysis index. Unit: %. It is calculated from Successful handoversfrom OverLaid subcell to UnderLaid subcell and Attempted handovers fromOverLaid subcell to UnderLaid subcell .

Measurement point: none. Formula: Successful handovers from OverLaid subcell to UnderLaid subcell /

Attempted handovers from OverLaid subcell to UnderLaid subcell

3.12 Cell Measurement Function (2)

3.12.1 General

The items in “Cell Measurement Function (2)" is for the measurement of a cell's Full rate TCH and Half rate TCH. They can be classified into six categories: attempted channel seizure items, successful channel seizure items, unsuccessful channel allocation and activation items, call drop items, traffic volume items and resource configuration items. Below are the details:

Channel seizure request items provide information about requests of various channels in various procedures such as very early assignment, assignment, incoming interBSC handover, intra BSC incoming cell handover, intra cell handover, outgoing inter BSC handover and intra BSC outgoing cell handover, etc.

462


Successful channel seizure items provide information about successfully realized requests of various channels in various procedures such as very early assignment, assignment, incoming interBSC handover, intra BSC incoming cell handover, intra cell handover, outgoing inter BSC handover and intra BSC outgoing cell handover, etc, as well as the information about the seized channel types.

Unsuccessful channel allocation and activation items provide information about times of negative response to channel activation request received or times of channel activation timeout in the procedures of very early assignment, assignment, handover and mode modification. Items like congestion for channel allocation request, channel transform and reverse shows the situation of system resource allocation.

Call drop items provide information about the times of call drop after channel seizure from the aspects of radio link disconnection, terrestrial link disconnection and A interface failure, etc.

Traffic volume items provide information about the utilization situation of radio resources by means of the items concerning number of MRs and traffic volume.

Resource configuration items provide information about the current radio resource configuration and utilization by means of items concerning number of channels actually configured, number of initial configuration, number of available ones, number of channels in various status.

The six categories of items provide information of channel allocation, channel utilization and resource configuration of Full rate and Half rate TCH. If Half rate function is provided, it is possible to know the operations on Full rate and Half rate TCH with the help of these items. If the Half rate function is provided, the TCH measurement in cell measurement can provide the information of TCH operation.

The object of Cell Measurement Function (2) is cell. In the object definition interface user can select some cells or all cells as the object.

It is recommended that all items of this measurement be registered in three tasks after BSC system startup. When registering, the related template is recommended and the best choice for measurement period is 60 minutes.

Note:

1) At most 60 items can be registered in a task. That is why Cell Measurement Function (2) needs

three tasks.

2) Three default item templates are available.

463


Table 3-12 Cell Measurement Function (2) items

No. Item name

1Attempted TCH seizures during very early assignment (TCHF)

2Attempted TCH seizures during very early assignment (TCHF preferred)

3Attempted TCH seizures during very early assignment (TCHH preferred)

4Attempted TCH seizures during assignment (TCHF)

5Attempted TCH seizures during assignment (TCHH)

6Attempted TCH seizures during assignment (TCHF preferred, change not allowed)

7Attempted TCH seizures during assignment (TCHH preferred, change not allowed)

8Attempted TCH seizures during assignment (TCHF preferred, change allowed)

9Attempted TCH seizures during assignment (TCHH preferred, change allowed)

10Attempted TCH seizures during assignment (TCHF or TCHH, change not allowed)

11Attempted TCH seizures during assignment (TCHF or TCHH, change allowed)

12Attempted TCH seizures during intraBSC incoming cell handover (TCHF)

13Attempted TCH seizures during intraBSC incoming cell handover (TCHH)

14Attempted TCH seizures during intraBSC incoming cell handover (TCHF preferred, change allowed)

15Attempted TCH seizures during intraBSC incoming cell handover (TCHH preferred, change allowed)

16Attempted TCH seizures during intracell handover (TCHF)

17Attempted TCH seizures during intracell handover (TCHH)

18Attempted TCH seizures during intracell handover (TCHF preferred, change allowed)

19Attempted TCH seizures during intracell handover (TCHH preferred, change allowed)

20Attempted TCH seizures during intraBSC incoming cell handover (TCHF preferred, change not allowed)

21Attempted TCH seizures during intraBSC incoming cell handover (TCHH preferred, change not allowed)

22Attempted TCH seizures during intraBSC incoming cell handover (TCHF or TCHH, change not allowed)

23Attempted TCH seizures during intraBSC incoming cell handover (TCHF or TCHH, change allowed)

24Attempted TCH seizures during interBSC incoming cell handover (TCHF)

25Attempted TCH seizures during interBSC incoming cell handover (TCHH)

26Attempted TCH seizures during interBSC incoming cell handover (TCHF preferred, change not allowed)

27Attempted TCH seizures during interBSC incoming cell handover (TCHH preferred, change not allowed)

28Attempted TCH seizures during interBSC incoming cell handover (TCHF preferred, change allowed)

29Attempted TCH seizures during interBSC incoming cell handover (TCHH preferred, change allowed)

30Attempted TCH seizures during interBSC incoming cell handover (TCHF or TCHH, change not allowed)

31Attempted TCH seizures during interBSC incoming cell handover (TCHF or TCHH, change allowed)

32Attempted outgoing internal inter cell handovers (using TCHF originally, excluding directed retry)

33Attempted outgoing internal inter cell handovers (using TCHH originally, excluding directed retry)

34Attempted intracell handovers (using TCHF originally)

35Attempted intracell handovers (using TCHH originally)

36Attempted outgoing interBSC inter cell handovers (using TCHF originally, excluding directed retry)

464


37Attempted outgoing interBSC inter cell handovers (using TCHH originally, excluding directed retry)

38Request of TCH allocation (TCHF)

39Request of TCH allocation (TCHH)

40Request of TCH allocation (TCHF preferred)

41Request of TCH allocation (TCHH preferred)

42Successful TCHF seizures during very early assignment

43Successful TCHH seizures during very early assignment

44Successful TCH seizures during very early assignment (TCHF)

45Successful TCH seizures during very early assignment (TCHF preferred)

46Successful TCH seizures during very early assignment (TCHH preferred)

47 Successful TCH seizures during assignment (TCHF)

48Successful TCH seizures during assignment (TCHH)

49Successful TCH seizures during assignment (TCHF preferred, change not allowed)

50Successful TCH seizures during assignment (TCHH preferred, change not allowed)

51Successful TCH seizures during assignment (TCHF preferred, change allowed)

52Successful TCH seizures during assignment (TCHH preferred, change allowed)

53Successful TCH seizures during assignment (TCHF or TCHH, change not allowed)

54Successful TCH seizures during assignment (TCHF or TCHH, change allowed)

55Successful TCHF seizures during assignment (excluding directed retry)

56Successful TCHH seizures during assignment (excluding directed retry)

57Successful TCH seizures during intraBSC incoming cell handover (TCHF preferred, change not allowed)

58Successful TCH seizures during intraBSC incoming cell handover (TCHH preferred, change not allowed)

59Successful TCH seizures during intraBSC incoming cell handover (TCHF or TCHH, change not allowed)

60Successful TCH seizures during intraBSC incoming cell handover (TCHF or TCHH, change allowed)

61Successful TCH seizures during intraBSC incoming cell handover (TCHF)

62Successful TCH seizures during intraBSC incoming cell handover (TCHH)

63Successful TCH seizures during intraBSC incoming cell handover (TCHF preferred, change allowed)

64Successful TCH seizures during intraBSC incoming cell handover (TCHH preferred, change allowed)

65Successful TCH seizures during intracell handover (TCHF)

66Successful TCH seizures during intracell handover (TCHH)

67Successful TCH seizures during intracell handover (TCHF preferred, change allowed)

68Successful TCH seizures during intracell handover (TCHH preferred, change allowed)

69Successful TCHF seizures during intraBSC incoming cell handover

70Successful TCHH seizures during intraBSC incoming cell handover

71Successful TCHF seizures during intracell handover

72Successful TCHH seizures during intracell handover

73Successful TCH seizures during interBSC incoming cell handover (TCHF)

74Successful TCH seizures during interBSC incoming cell handover (TCHH)

75Successful TCH seizures during interBSC incoming cell handover (TCHF preferred, change not allowed)

76Successful TCH seizures during interBSC incoming cell handover (TCHH preferred,

465


77Successful TCH seizures during interBSC incoming cell handover (TCHF preferred, change allowed)

78Successful TCH seizures during interBSC incoming cell handover (TCHH preferred, change allowed)

79Successful TCH seizures during interBSC incoming cell handover (TCHF or TCHH, change not allowed)

80Successful TCH seizures during interBSC incoming cell handover (TCHF or TCHH, change allowed)

81Successful TCHF seizures during interBSC incoming cell handover

82Successful TCHH seizures during interBSC incoming cell handover

83Successful outgoing internal inter cell handovers (using TCHF originally, excluding directed retry)

84Successful outgoing internal inter cell handovers (using TCHH originally, excluding directed retry)

85Successful outgoing interBSC inter cell handovers (using TCHF originally, excluding directed retry)

86Successful outgoing interBSC inter cell handovers (using TCHH originally, excluding directed retry)

87TCHF channel activation failures during very early assignment (NACK)

88TCHH channel activation failures during very early assignment (NACK)

89TCHF channel activation failures during very early assignment (TIMEOUT)

90TCHH channel activation failures during very early assignment (TIMEOUT)

91TCHF channel activation failures during assignment (NACK)

92TCHH channel activation failures during assignment (NACK)

93TCHF channel activation failures during assignment (TIMEOUT)

94TCHH channel activation failures during assignment (TIMEOUT)

95TCHF channel activation failures during handover (NACK)

96TCHH channel activation failures during handover (NACK)

97TCHF channel activation failures during handover (TIMEOUT)

98TCHH channel activation failures during handover (TIMEOUT)

99TCHF channel activation failures during mode modification (NACK)

100TCHH channel activation failures during mode modification (NACK)

101TCHF channel activation failures during mode modification (TIMEOUT)

102TCHH channel activation failures during mode modification (TIMEOUT)

103Attempted TCHF seizures meeting TCHF overflow

104Attempted TCHH seizures meeting TCHH overflow

105TCHF call drop during very early assignment

106TCHH call drop during very early assignment

107TCHF call drop

108TCHH call drop

109TCHF lost radio connections (connection failure)

110TCHH lost radio connections (connection failure)

111TCHF lost radio connections (error indication)

112TCHH lost radio connections (error indication)

113TCHF call drops due to terrestrial link failures (ABIS)

114TCHH call drops due to terrestrial link failures (ABIS)

115TCHF call drops due to A-interface failures

466


116TCHH call drops due to A-interface failures

117Sum of TCHF measurement reports during very early assignment procedure in the cell

118Sum of TCHH measurement reports during very early assignment procedure in the cell

119Sum of TCHF measurement reports during very early assignment procedure in the 1800cell

120Sum of TCHH measurement reports during very early assignment procedure in the 1800 cell

121Sum of TCHF measurement reports in the cell (excluding very early assignment)

122Sum of TCHH measurement reports in the cell (excluding very early assignment)

123Sum of TCHF measurement reports in 1800 cell (excluding very early assignment)

124Sum of TCHH measurement reports in 1800 cell (excluding very early assignment)

125Initially configured TCHF of 900 cell

126Initially configured TCHH of 900 cell

127Initially configured TCHF of 1800 cell

128Initially configured TCHH of 1800 cell

129Configured TCHF of 900 cell

130Configured TCHH of 900 cell

131Configured TCHF of 1800 cell

132Configured TCHH of 1800 cell

133Available TCHF

134Available TCHH

135Average num. of busy TCHF

136Average num. of busy TCHH

137Maximum num. of busy TCHF

138Maximum num. of busy TCHH

139All TCHF busy time (second)

140All TCHH busy time (second)

141Average TCHF busy time(second)

142Average TCHH busy time(second)

143Average num. of idle TCHF in Interf. band 1





148Average num. of idle TCHH in Interf. band 1





153Average num. of blocked TCHF

154Average num. of blocked TCHH

155Average num. of idle TCHF

467


156Average num. of idle TCHH

157Average num. of OOS TCHF

158Average num. of OOS TCHH

159Attempted transform from TCHF to TCHH

160Successful transform from TCHF to TCHH

161Attempted reverse from TCHH to TCHF

162Successful reverse from TCHH to TCHF

163TCHF usability (%)

164TCHH usability (%)

165TCHF traffic volume (excluding very early assignment) (ERL)

166TCHH traffic volume (excluding very early assignment) (ERL)

167TCHF traffic volume of 1800 cell (excluding very early assignment) (ERL)

168TCHH traffic volume of 1800 cell (excluding very early assignment) (ERL)

169Traffic density at average TCHF call drop

170Traffic density at average TCHH call drop

171TCHF RF lost rate (%)

172TCHH RF lost rate (%)

173TCHF call drop rate (%)

174TCHH call drop rate (%)


I. Attempted TCH seizures during very early assignment (TCHF)

Description: In the immediate assignment procedure, BSC decides the channel type of first allocation request and the channel type of second allocation request according to the MS capability and the service type MS requests for in the channel request message, as well as the settings on data management console including "Immediate assignment TCH" switch in "Cell call control table", "Immediate assignment" switch and "Capacity and quality" switch in "Software parameter table". If there is no channel available during first channel allocation, system will initiate the second allocation. Whenever the channel type of "Full rate TCH" is requested for, this item increases by 1. For details of second channel allocation, see Attempted SDCCH seizures (all) in Cell Measurement Function.

Note:

1. "Immediate assignment" switch in "Software parameter table":

468


In data management console, open: Configuration/Software parameter/Software parameter – call

parameter (5)'s BIT0~1. BIT0 controls immediate assignment in mobile originated call, and BIT1

controls immediate assignment in mobile terminating call.

The functions software parameter realizes and its setting methods are listed below:

1) TCH immediate assignment not allowed (FFFF). (Default)

2) immediate assignment TCH in mobile originated call allowed (FFFE).

3) immediate assignment TCH in mobile terminating call allowed (FFFD).

4) immediate assignment TCH in both mobile originated call and mobile terminating call allowed

(FFFC).

According to the "Immediate assignment TCH" in "Cell call control table", the channel types allocated

by BSC are liseted below:

Immediate

assignement

TCH switch

Access cause Call parameter (5)

(Immediate assignment

not allowed)

Call parameter (5)

(Immediate assignment

allowed)

Off Call

establisheme

nt

SDCCH SDCCH

Response to

paging

SDCCH SDCCH

Emergency

call

SDCCH SDCCH

Call re-

establisheme

nt

SDCCH SDCCH

Location

update

SDCCH SDCCH

On Call

establisheme

nt

First SDCCH, second

TCH

First TCH second SDCCH

Response to

paging

First SDCCH, second

TCH


Emergency

call

First TCH, second

SDCCH


Call re-

establisheme

nt

First TCH second

SDCCH


Location

update

SDCCH SDCCH

In the table above, "First" stands for the first channel allocation, and "second" stands for second

channel allocation.

469


2. "Capacity and quality" switch in "Software parameter table":

In data management console, open: Configuration/Software parameter/Software parameter – call

parameter (5)'s BIT4.

Software parameter realization and setting methods are listed below:

1) Voice quality oriented (FFFF). If the MS supports dual rates, the requested channel type should be

"Full rate or Half rate TCH, Full rate preferred, and channel type change not allowed", so as to

guarantee voice quality.

2) Channel capacity oriented (FFEF). If the MS supports dual rates, the requested channel type

should be "Full rate or Half rate TCH, Half rate preferred, and channel type change not allowed", so

as to guarantee channel capacity.

If the MS does not support dual rates or the MS type unknown, then only Full rate TCH will be

allocated regardless of parameter settings.

Therefore, there are three types of channel can be requested for in the immediate assignment

procedure: "Full rate TCH", "Full rate or Half rate TCH, Full rate preferred, and channel type change

not allowed" and "Full rate or Half rate TCH, Half rate preferred, and channel type change not

allowed".

3. Information "GSM0808" in related to channel type:

When "speech/data indicator" is speech, the definition of "Channel rate and type" is:

0000 1000 TCH (Full rate TCH channel Bm).

0000 1001 TCH (Half rate TCH channel Lm)

0000 1010 Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half

rate allowed also after first channel allocation as a result of the request.

0000 1011 Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half

rate allowed also after first channel allocation as a result of the request.

0001 1010 Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half

rate not allowed after first channel allocation as a result of the request.

0001 1011 Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half

rate not allowed after first channel allocation as a result of the request.

0000 1111 Full or Half rate TCH channel, changes between full and Half rate allowed also after first

channel allocation as a result of the request.

0001 1111 Full or Half rate TCH channel., changes between full and Half rate not allowed after first

channel allocation as a result of the request.

Measurement point: On reception of the channel request in immediate assignment procedure, BSC decides the type of channel to be allocated according to channel type requested for and BSC software parameter settings, and then starts to allocate channel. This item is measured when the allocated channel type is Full rate TCH.

Formula: None.

470


II. Attempted TCH seizures during very early assignment (TCHF preferred)

Description: In the immediate assignment procedure, BSC decides the channel type of first allocation request and the channel type of second allocation request according to the MS capability and the service type MS requests for in the channel request message, as well as the settings on data management console including "Immediate assignment TCH" switch in "Cell call control table", "Immediate assignment" switch and "Capacity and quality" switch in "Software parameter table". If there is no channel available during first channel allocation, system will initiate the second allocation. Whenever the channel type of "Full or Half rate TCH channel, Full rate preferred, changes between full rate and half rate not allowed after first channel allocation as a result of the request" is requested for, this item increases by 1. For details of second channel allocation, see Attempted SDCCH seizures (all) in Cell Measurement Function. For other information, please refer to Attempted TCH seizures duringvery early assignment (TCHF) in Cell Measurement Function (2).

Measurement point: On reception of the channel request in immediate assignment procedure, BSC decides the type of channel to be allocated according to channel type requested for and BSC software parameter settings, and then starts to allocate channel. This item is measured when the allocated channel type is Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate not allowed also after first channel allocation as a result of the request.

Formula: None.

III. Attempted TCH seizures during very early assignment (TCHH preferred)

Description: In the immediate assignment procedure, BSC decides the channel type of first allocation request and the channel type of second allocation request according to the MS capability and the service type MS requests for in the channel request message, as well as the settings on data management console including "Immediate assignment TCH" switch in "Cell call control table", "Immediate assignment" switch and "Capacity and quality" switch in "Software parameter table". If there is no channel available during first channel allocation, system will initiate the second allocation. Whenever the channel type of "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate not allowed also after first channel allocation as a result of the request" is requested for, this item increases by 1. For details of second channel allocation, see Attempted SDCCH seizures (all) in Cell Measurement Function. For other information, please refer to Attempted TCH seizures duringvery early assignment (TCHF) in Cell Measurement Function (2).

Measurement point: On reception of the channel request in immediate assignment procedure, BSC decides the type of channel to be allocated

471


according to channel type requested for and BSC software parameter settings, and then starts to allocate channel. This item is measured when the allocated channel type is Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate not allowed also after first channel allocation as a result of the request.

Formula: None.

IV. Attempted TCH seizures during assignment (TCHF)

Description: In the procedure of immediate assignment, BSS allocates the radio channel to MS for signaling transmission. After RR connection between MS and BSS has been set up, the MM and CC connection to MSC is set up through this radio channel. MSC allocates terrestrial resource for MS in the message ASSIGNMENT REQUEST according to the CC connection request from MS, and specifies the channel type in the channel assignment procedure. This item is measured when BSC receives ASSIGNMENT REQUEST in which MSC specifies the channel type as "Full rate TCH". For the processing after BSC receives ASSIGNMENT REQUEST, see Assignment requests and Unsuccessful assignments in BSC Measurement Function.

Note:MSC specifies channel type in the assignment request. Different service types (voice or data)

correspond to different channel types.

The channel types for voice service include:

1) Full rate TCH channel Bm.

2) Half rate TCH channel Lm.

3) Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate allowed

also after first channel allocation as a result of the request.

4) Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate allowed


5) Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate not

allowed after first channel allocation as a result of the request.

6) Full or Half rate TCH channel. Half rate preferred, changes between Full rate and Half rate not


7) Full or Half rate TCH channel, changes between full and Half rate allowed also after first channel

allocation as a result of the request.

8) Full or Half rate TCH channel, changes between full and Half rate not allowed after first channel

allocation as a result of the request.

Huawei BSC supports all of the above channel types.

The channel types for data service include:

472


1) Full rate TCH channel Bm.

2) Half rate TCH channel Lm.

3) Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate allowed


4) Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate allowed


5) Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate not


6) Full or Half rate TCH channel. Half rate preferred, changes between Full rate and Half rate not


7) Full rate TCH channels in a multislot configuration, changes by the BSS of the the number of TCHs

and if applicable the used radio interface rate per channel allowed after first channel allocation as a

result of the request.

8) Full rate TCH channels in a multislot configuration, changes by the BSS of the number of TCHs or

the used radio interface rate per channel not allowed after first channel allocation as a result of the

request.

Huawei BSC supports 1)~6) of the above channel types.

Measurement point: This item is measured when BSC receives ASSIGNMENT REQUEST from MSC, in which the channel type is "Full rate TCH".

Formula: None.

V. Attempted TCH seizures during assignment (TCHH)

Description: In the procedure of immediate assignment, BSS allocates the radio channel to MS for signaling transmission. After RR connection between MS and BSS has been set up, the MM and CC connection to MSC is set up through this radio channel. MSC allocates terrestrial resource for MS in the message ASSIGNMENT REQUEST according to the CC connection request from MS, and specifies the channel type in the channel assignment procedure. This item is measured when BSC receives ASSIGNMENT REQUEST in which MSC specifies the channel type as "Half rate TCH". For the processing after BSC receives ASSIGNMENT REQUEST, see Assignment requests and Unsuccessful assignments in BSC Measurement Function. For other information, see Attempted TCH seizures during assignment (TCHF) .

Measurement point: This item is measured when BSC receives ASSIGNMENT REQUEST from MSC, in which the channel type is "Half rate TCH".

Formula: None.

VI. Attempted TCH seizures during assignment (TCHF preferred, change not allowed)

Description: In the procedure of immediate assignment, BSS allocates the radio channel to MS for signaling transmission. After RR connection between

473


MS and BSS has been set up, the MM and CC connection to MSC is set up through this radio channel. MSC allocates terrestrial resource for MS in the message ASSIGNMENT REQUEST according to the CC connection request from MS, and specifies the channel type in the channel assignment procedure. This item is measured when BSC receives ASSIGNMENT REQUEST in which MSC specifies the channel type as "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request". For the processing after BSC receives ASSIGNMENT REQUEST, see Assignment requests and Unsuccessful assignments in BSC Measurement Function. For other information, see Attempted TCH seizures during assignment (TCHF) .

Measurement point: This item is measured when BSC receives ASSIGNMENT REQUEST from MSC, in which the channel type is "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request".

Formula: None.

VII. Attempted TCH seizures during assignment (TCHH preferred, change not allowed)

Description: In the procedure of immediate assignment, BSS allocates the radio channel to MS for signaling transmission. After RR connection between MS and BSS has been set up, the MM and CC connection to MSC is set up through this radio channel. MSC allocates terrestrial resource for MS in the message ASSIGNMENT REQUEST according to the CC connection request from MS, and specifies the channel type in the channel assignment procedure. This item is measured when BSC receives ASSIGNMENT REQUEST in which MSC specifies the channel type as "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request". For the processing after BSC receives ASSIGNMENT REQUEST, see Assignment requests and Unsuccessful assignments in BSC Measurement Function. For other information, see Attempted TCH seizures during assignment (TCHF) .

Measurement point: This item is measured when BSC receives ASSIGNMENT REQUEST from MSC, in which the channel type is "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request".

Formula: None.

474


VIII. Attempted TCH seizures during assignment (TCHF preferred, change allowed)

Description: In the procedure of immediate assignment, BSS allocates the radio channel to MS for signaling transmission. After RR connection between MS and BSS has been set up, the MM and CC connection to MSC is set up through this radio channel. MSC allocates terrestrial resource for MS in the message ASSIGNMENT REQUEST according to the CC connection request from MS, and specifies the channel type in the channel assignment procedure. This item is measured when BSC receives ASSIGNMENT REQUEST in which MSC specifies the channel type as "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request". For the processing after BSC receives ASSIGNMENT REQUEST, see Assignment requests and Unsuccessful assignments in BSC Measurement Function. For other information, see Attempted TCH seizures during assignment (TCHF) .

Measurement point: This item is measured when BSC receives ASSIGNMENT REQUEST from MSC, in which the channel type is "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request".

Formula: None.

IX. Attempted TCH seizures during assignment (TCHH preferred, change allowed)

Description: In the procedure of immediate assignment, BSS allocates the radio channel to MS for signaling transmission. After RR connection between MS and BSS has been set up, the MM and CC connection to MSC is set up through this radio channel. MSC allocates terrestrial resource for MS in the message ASSIGNMENT REQUEST according to the CC connection request from MS, and specifies the channel type in the channel assignment procedure. This item is measured when BSC receives ASSIGNMENT REQUEST in which MSC specifies the channel type as "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request". For the processing after BSC receives ASSIGNMENT REQUEST, see Assignment requests and Unsuccessful assignments in BSC Measurement Function. For other information, see Attempted TCH seizures during assignment (TCHF) .

Measurement point: This item is measured when BSC receives ASSIGNMENT REQUEST from MSC, in which the channel type is "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request".

Formula: None.

475


X. Attempted TCH seizures during assignment (TCHF or TCHH, change not allowed)

Description: In the procedure of immediate assignment, BSS allocates the radio channel to MS for signaling transmission. After RR connection between MS and BSS has been set up, the MM and CC connection to MSC is set up through this radio channel. MSC allocates terrestrial resource for MS in the message ASSIGNMENT REQUEST according to the CC connection request from MS, and specifies the channel type in the channel assignment procedure. This item is measured when BSC receives ASSIGNMENT REQUEST in which MSC specifies the channel type as "Full or Half rate TCH channel, changes between full and Half rate not allowed after first channel allocation as a result of the request". For the processing after BSC receives ASSIGNMENT REQUEST, see Assignment requests and Unsuccessful assignments in BSC Measurement Function. For other information, see Attempted TCHseizures during assignment (TCHF) .

Measurement point: This item is measured when BSC receives ASSIGNMENT REQUEST from MSC, in which the channel type is "Full or Half rate TCH channel, changes between full and Half rate not allowed after first channel allocation as a result of the request".

Formula: None.

XI. Attempted TCH seizures during assignment (TCHF or TCHH, change allowed)

Description: In the procedure of immediate assignment, BSS allocates the radio channel to MS for signaling transmission. After RR connection between MS and BSS has been set up, the MM and CC connection to MSC is set up through this radio channel. MSC allocates terrestrial resource for MS in the message ASSIGNMENT REQUEST according to the CC connection request from MS, and specifies the channel type in the channel assignment procedure. This item is measured when BSC receives ASSIGNMENT REQUEST in which MSC specifies the channel type as "Full or Half rate TCH channel, changes between full and Half rate allowed also after first channel allocation as a result of the request". For the processing after BSC receives ASSIGNMENT REQUEST, see Assignment requests and Unsuccessful assignments in BSC Measurement Function. For other information, see Attempted TCHseizures during assignment (TCHF) .

Measurement point: This item is measured when BSC receives ASSIGNMENT REQUEST from MSC, in which the channel type is "Full or Half rate TCH channel, changes between full and Half rate allowed also after first channel allocation as a result of the request".

Formula: None.

476


XII. Attempted TCH seizures during intraBSC incoming cell handover (TCHF)

Description: In intra BSC handover procedure, the source cell sends Intercell Handover Request to target cell containing the channel mode of the current call. On reception of this message, the target cell decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. For information about intra BSC incoming cell handover procedure, see Attempted TCHseizures for intraBSC incoming cell handover in Cell Measurement Function.

Note:In intra BSC intercell handover procedure, the source cell sends Intercell Handover Request to target

cell containing the channel mode of the current call. On reception of this message, the target cell

decides the channel type to be allocated for this handover according to handover type, the capability

of the circuit pool of the A interface, channel type of the current call and the channel rate and channel

type requested by MSC during call setup. There can be the following several cases:

1. If the handover cause is direct retry, it means that the source cell has not allocated TCH for this

call. Therefore, the target cell will decide the channel type to be allocated for this handover according

to handover type, the capability of the circuit pool of the A interface, channel type of the current call

and the channel rate and channel type requested by MSC (ASSIGNMENT REQUEST or HANDOVER

REQUEST) during call setup.

1) If the circuit pool can support Full rate or Half rate only, the target cell can allocate Full rate or Half

rate only.

2) If the circuit pool supports both Full rate and Half rate, the target cell will allocate the TCH of the

same channel type as the one requested by MSC.

2. If the cause of non direct retry, it means that the source cell has allocate TCH for this call.

Therefore, the target cell will decide the channel type to be allocated for this handover according to

handover type, the capability of the circuit pool of the A interface, channel type of the current call and

the channel rate and channel type requested by MSC (ASSIGNMENT REQUEST or HANDOVER

REQUEST) during call setup.

1) When this handover is a signaling channel handover, system does not allow change of channel

type. Therefore, the target cell will allocate the TCH of the same channel type as the TCH currently

seized.

2) If the circuit pool can support Full rate or Half rate only, the target cell can allocate Full rate or Half

rate only.

3) If the circuit pool supports both Full rate and Half rate, the target cell will allocate the TCH of the

same channel type as the one requested by MSC. If the channel rate and channel type is not allowed

to change, the target cell will allocate a TCH with the same channel type as the current seized TCH. If

477


the channel rate and channel type is allowed to change, the target cell will allocate a TCH with the

same channel type as the one requested by MSC.

Measurement point: In intra BSC handover procedure, on reception of the Intercell Handover Request from the source cell, the target cell will decide that the channel type to be allocated for this handover is "Full rate TCH" according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item is measured in this case.

Formula: None.

XIII. Attempted TCH seizures during intraBSC incoming cell handover (TCHH)

Description: In intra BSC handover procedure, the source cell sends Intercell Handover Request to target cell containing the channel mode of the current call. On reception of this message, the target cell decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. For information about intra BSC incoming cell handover procedure, see Attempted TCHseizures for intraBSC incoming cell handover in Cell Measurement Function. For other information, see Attempted TCH seizures during intraBSC incomingcell handover (TCHF) in Cell Measurement Function (2).

Measurement point: In intra BSC handover procedure, on reception of the Intercell Handover Request for the source cell, the target cell will decide that the channel type to be allocated for this handover is "Half rate TCH" according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item is measured in this case.

Formula: None.

XIV. Attempted TCH seizures during intraBSC incoming cell handover (TCHF preferred, change allowed)

Description: In intra BSC handover procedure, the source cell sends Intercell Handover Request to target cell containing the channel mode of the current call. On reception of this message, the target cell decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. For information about intra BSC incoming cell handover procedure, see Attempted TCHseizures for intraBSC incoming cell handover in Cell Measurement Function.

478


For other information, see Attempted TCH seizures during intraBSC incomingcell handover (TCHF) in Cell Measurement Function (2).

Measurement point: In intra BSC handover procedure, on reception of the Intercell Handover Request for the source cell, the target cell will decide that the channel type to be allocated for this handover is "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request" according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item is measured in this case.

Formula: None.

XV. Attempted TCH seizures during intraBSC incoming cell handover (TCHH preferred, change allowed)

Description: In intra BSC handover procedure, the source cell sends Intercell Handover Request to target cell containing the channel mode of the current call. On reception of this message, the target cell decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. For information about intra BSC incoming cell handover procedure, see Attempted TCHseizures for intraBSC incoming cell handover in Cell Measurement Function. For other information, see Attempted TCH seizures during intraBSC incomingcell handover (TCHF) in Cell Measurement Function (2).

Measurement point: In intra BSC handover procedure, on reception of the Intercell Handover Request for the source cell, the target cell will decide that the channel type to be allocated for this handover is "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request" according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item is measured in this case.

Formula: None.

XVI. Attempted TCH seizures during intracell handover (TCHF)

Description: In intra cell handover (i.e. handover between different channels of the serving cell) procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, BSC decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type

479


requested by MSC during call setup. This item provides the frequency of channel types being requested for among intra cell handover. For information about intra cell handover procedure, see Attempted TCH seizures for intracellhandover in Cell Measurement Function.

Note:In intra cell handover procedure, the serving cell receives Intercell Handover Request containing the

channel mode of the current call. On reception of this message, BSC decides the channel type to be

allocated for this handover according to handover type, the capability of the circuit pool of the A

interface, channel type of the current call and the channel rate and channel type requested by MSC

during call setup. There can be the following several cases:

1. If the handover is a signaling channel handover, system will not allow change of channel types.

Therefore the serving cell will allocate the channel of the same type as the currently seized channel.

2. If the circuit pool can support Full rate or Half rate only, the serving cell can allocate Full rate or Half

rate only.

3. If the circuit pool supports both Full rate and Half rate, the serving cell will allocate the TCH of the

same channel type as the one requested by MSC during call setup.

1) If the channel rate and channel type requested by MSC during call setup are not allowed to be

changed, then the serving cell will allocate a channel of same type as the currently seized one.

2) If the channel rate and channel type requested by MSC during call setup are allowed to be

changed, the serving cell will allocate the channel of the same channel type as the one requested by

MSC during call setup.

Please note that in 2), BSC will treate the "Full or Half rate TCH channel, changes between full and

Half rate allowed also after first channel allocation as a result of the request" as "Full or Half rate TCH

channel, Full rate preferred, changes between Full rate and Half rate allowed also after first channel

allocation as a result of the request". Therefore, for intra cell handover, there are only four channel

types: "Full rate TCH", "Half rate TCH", "Full or Half rate TCH channel, Full rate preferred, changes

between Full rate and Half rate allowed also after first channel allocation as a result of the request"

and "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate

allowed also after first channel allocation as a result of the request".

Measurement point: In intra cell handover procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, BSC decides that the channel type to be allocated for this handover is "Full rate TCH" according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item is measured in this case.

Formula: None.

480


XVII. Attempted TCH seizures during intracell handover (TCHH)

Description: In intra cell handover (i.e. handover between different channels of the serving cell) procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, BSC decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item provides the frequency of channel types being requested for among intra cell handover. For information about intra cell handover procedure, see Attempted TCH seizures for intracellhandover in Cell Measurement Function. For other information, see Attempted TCH seizures during intracell handover (TCHF) in Cell Measurement Function (2).

Measurement point: In intra cell handover procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, BSC decides that the channel type to be allocated for this handover is "Half rate TCH" according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item is measured in this case.

Formula: None.

XVIII. Attempted TCH seizures during intracell handover (TCHF preferred, change allowed)


Measurement point: In intra cell handover procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, BSC decides that the channel type to be allocated for this handover is "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate allowed also after first

481


channel allocation as a result of the request" according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item is measured in this case.

Formula: None.

XIX. Attempted TCH seizures during intracell handover (TCHH preferred, change allowed)


Measurement point: In intra cell handover procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, BSC decides that the channel type to be allocated for this handover is "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request" according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item is measured in this case.

Formula: None.

XX. Attempted TCH seizures during intraBSC incoming cell handover (TCHF preferred, change not allowed)

Description: In intraBSC incoming cell handover procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, the target cell decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item provides the frequency of channel types being requested for among intraBSC incoming cell handover. For information about intraBSC incoming cell

482


handover procedure, see Attempted TCH seizures for intraBSC incoming cellhandover in Cell Measurement Function. For other information, see Attempted TCH seizures during intraBSC incoming cell handover (TCHF) in Cell Measurement Function (2).

Measurement point: In intraBSC incoming cell handover procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, the target cell decides that the channel type to be allocated for this handover is "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request" according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item is measured in this case.

Formula: None.

XXI. Attempted TCH seizures during intraBSC incoming cell handover (TCHH preferred, change not allowed)

Description: In intraBSC incoming cell handover procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, the target cell decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item provides the frequency of channel types being requested for among intraBSC incoming cell handover. For information about intraBSC incoming cell handover procedure, see Attempted TCH seizures for intraBSC incoming cellhandover in Cell Measurement Function. For other information, see Attempted TCH seizures during intraBSC incoming cell handover (TCHF) in Cell Measurement Function (2).

Measurement point: In intraBSC incoming cell handover procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, the target cell decides that the channel type to be allocated for this handover is "Full or Half rate TCH channel. Half rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request" according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item is measured in this case.

Formula: None.

483


XXII. Attempted TCH seizures during intraBSC incoming cell handover (TCHF or TCHH, change not allowed)

Description: In intraBSC incoming cell handover procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, the target cell decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item provides the frequency of channel types being requested for among intraBSC incoming cell handover. For information about intraBSC incoming cell handover procedure, see Attempted TCH seizures for intraBSC incoming cellhandover in Cell Measurement Function. For other information, see Attempted TCH seizures during intraBSC incoming cell handover (TCHF) in Cell Measurement Function (2).

Measurement point: intraBSC incoming cell handover procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, the target cell decides that the channel type to be allocated for this handover is "Full or Half rate TCH channel, changes between full and Half rate not allowed after first channel allocation as a result of the request" according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item is measured in this case.

Formula: None.

XXIII. Attempted TCH seizures during intraBSC incoming cell handover (TCHF or TCHH, change allowed)

Description: In intraBSC incoming cell handover procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, the target decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item provides the frequency of channel types being requested for among intraBSC incoming cell handover. For information about intraBSC incoming cell handover procedure, see Attempted TCH seizures for intraBSC incoming cellhandover in Cell Measurement Function. For other information, see Attempted TCH seizures during intraBSC incoming cell handover (TCHF) in Cell Measurement Function (2).

Measurement point: In intra cell handover procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call.

484


On reception of this message, BSC decides that the channel type to be allocated for this handover is "Full or Half rate TCH channel, changes between full and Half rate allowed also after first channel allocation as a result of the request" according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. This item is measured in this case.

Formula: None.

XXIV. Attempted TCH seizures during interBSC incoming cell handover (TCHF)

Description: In inter BSC handover procedure, the cell receives HANDOVER REQUEST from MSC via TCH. This message is sent by other BSC to request for a TCH. It contains the channel type for this handover specified by MSC, and BSC allocates channels according to this message. This item shows the frequency various channel types being specified by MSC among inter BSC handovers. For inter BSC handover procedure, see Attempted TCH seizuresfor interBSC incoming cell handover in Cell Measurement Function.

Note:The definitions of channel types in HANDOVER REQUEST are the same as those in assignment

procedure. See "Attempted TCH seizures during assignment (TCHF)".

Measurement point: In inter BSC handover procedure, the related cell receives HANDOVER REQUEST from MSC. This item is measured when MSC specifies "Full rate TCH" as the type of the channel to be allocated in this message.

Formula: None.

XXV. Attempted TCH seizures during interBSC incoming cell handover (TCHH)

Description: In inter BSC handover procedure, the cell receives HANDOVER REQUEST from MSC via TCH. This message is sent by other BSC to request for a TCH. It contains the channel type for this handover specified by MSC, and BSC allocates channels according to this message. This item shows the frequency various channel types being specified by MSC among inter BSC handovers. For inter BSC handover procedure, see Attempted TCH seizuresfor interBSC incoming cell handover in Cell Measurement Function. For other information, see Attempted TCH seizures during interBSC incoming cellhandover (TCHF) in Cell Measurement Function (2).

Measurement point: In inter BSC handover procedure, the related cell receives HANDOVER REQUEST from MSC. This item is measured when MSC

485


specifies "Half rate TCH" as the type of the channel to be allocated in this message.

Formula: None.

XXVI. Attempted TCH seizures during interBSC incoming cell handover (TCHF preferred, change not allowed)


Measurement point: In inter BSC handover procedure, the related cell receives HANDOVER REQUEST from MSC. This item is measured when MSC specifies "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request" as the type of the channel to be allocated in this message.

Formula: None.

XXVII. Attempted TCH seizures during interBSC incoming cell handover (TCHH preferred, change not allowed)


Measurement point: In inter BSC handover procedure, the related cell receives HANDOVER REQUEST from MSC. This item is measured when MSC specifies "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request" as the type of the channel to be allocated in this message.

Formula: None.

486


XXVIII. Attempted TCH seizures during interBSC incoming cell handover (TCHF preferred, change allowed)


Measurement point: In inter BSC handover procedure, the related cell receives HANDOVER REQUEST from MSC. This item is measured when MSC specifies "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request" as the type of the channel to be allocated in this message.

Formula: None.

XXIX. Attempted TCH seizures during interBSC incoming cell handover (TCHH preferred, change allowed)


Measurement point: In inter BSC handover procedure, the related cell receives HANDOVER REQUEST from MSC. This item is measured when MSC specifies "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request" as the type of the channel to be allocated in this message.

Formula: None.

XXX. Attempted TCH seizures during interBSC incoming cell handover (TCHF or TCHH, change not allowed)

Description: In inter BSC handover procedure, the cell receives HANDOVER REQUEST from MSC via TCH. This message is sent by other BSC to request for a TCH. It contains the channel type for this handover specified by MSC,

487


and BSC allocates channels according to this message. This item shows the frequency various channel types being specified by MSC among inter BSC handovers. For inter BSC handover procedure, see Attempted TCH seizuresfor interBSC incoming cell handover in Cell Measurement Function. For other information, see Attempted TCH seizures during interBSC incoming cellhandover (TCHF) in Cell Measurement Function (2).

Measurement point: In inter BSC handover procedure, the related cell receives HANDOVER REQUEST from MSC. This item is measured when MSC specifies "Full or Half rate TCH channel, changes between full and Half rate not allowed after first channel allocation as a result of the request" as the type of the channel to be allocated in this message.

Formula: None.

XXXI. Attempted TCH seizures during interBSC incoming cell handover (TCHF or TCHH, change allowed)


Measurement point: In inter BSC handover procedure, the related cell receives HANDOVER REQUEST from MSC. This item is measured when MSC specifies "Full or Half rate TCH channel, changes between full and Half rate allowed also after first channel allocation as a result of the request" as the type of the channel to be allocated in this message.

Formula: None.

XXXII. Attempted outgoing internal inter cell handovers (using TCHF originally, excluding directed retry)

Description: A cell will initiates the procedure of handover to another cell controlled by the same BSC due to receiving level, receiving quality, TA, load-sharing, MSC interference, DIRECTED RETRY, rapid level drop, better cell, O&M interference. This item suggests the relation between the frequency of the calls in the current cell being handed over to other cells controlled by the same BSC and the type of the channel currently seized. For information about intra BSC inter cell handover, see Attempted outgoing internal inter cellhandovers in Cell Measurement Function.

488


Measurement point: After handover algorithm decision, the source cell (i.e. the current cell of the call) sends Intercell Handover Request to the target cell (the source cell and target cell are different), and the original type of the TCH currently seized is "Full rate TCH".

Formula: None.

XXXIII. Attempted outgoing internal inter cell handovers (using TCHH originally, excluding directed retry)

Description: A cell will initiates the procedure of handover to another cell controlled by the same BSC due to receiving level, receiving quality, TA, load-sharing, MSC interference, DIRECTED RETRY, rapid level drop, better cell, O&M interference.This item suggests the relation between the frequency of the calls in the current cell being handed over to other cells controlled by the same BSC and the type of the channel currently seized. For information about intra BSC inter cell handover, see Attempted outgoing internal inter cell handovers in Cell Measurement Function.

Measurement point: After handover algorithm decision, the source cell (i.e. the current cell of the call) sends Intercell Handover Request to the target cell (the source cell and target cell are different), and the original type of the TCH currently seized is "Half rate TCH".

Formula: None.

XXXIV. Attempted intracell handovers (using TCHF originally)

Description: Intra cell handover is normally triggered by causes related to receiving level, receiving quality, O&M interference and IUO, etc. In this procedure, the source cell and target cell are the same. This item provides the relation between the frequency of intra cell handover and the types of channels currently seized by the calls. For information about intra cell handover see Attempted intracell handovers in Cell Measurement Function.

Measurement point: After handover algorithm decision, the source cell (the current cell of the call) sends Intercell Handover Request to the target cell (the source cell itself). This item is measured when the original type of the channel of this call is "Full rate TCH" in this procedure.

Formula: None.

XXXV. Attempted intracell handovers (using TCHH originally)

Description: Intra cell handover is normally triggered by causes related to receiving level, receiving quality, O&M interference and IUO, etc. In this procedure, the source cell and target cell are the same. This item provides the relation between the frequency of intra cell handover and the types of channels

489


currently seized by the calls. For information about intra cell handover see Attempted intracell handovers in Cell Measurement Function.

Measurement point: After handover algorithm decision, the source cell (the current cell of the call) sends Intercell Handover Request to the target cell (the source cell itself). This item is measured when the original type of the channel of this call is "Half rate TCH" in this procedure.

Formula: None.

XXXVI. Attempted outgoing interBSC inter cell handovers (using TCHF originally, excluding directed retry)

Description: Inter BSC handover is usually triggered by the causes related to receiving level, receiving performance, TA, load-sharing, MSC interference, DIRECTED RETRY, rapid level drop, better cell and O&M interference. In this procedure, the source cell and target cell are controlled by different BSCs. The source cell sends HANDOVER REQUIRED to MSC to initiate handover. This item provides the relation between the frequency of inter BSC handover and the types of channels currently seized by the calls. For information about inter BSC handover see Attempted outgoing interBSC inter cell handovers in Cell Measurement Function.

Measurement point: After handover algorithm decision, the source cell (i.e. the current cell of the call) sends HANDOVER REQUIRED to MSC. This item is measured when the original type of the channel of this call is "Full rate TCH" in this procedure.

Formula: None.

XXXVII. Attempted outgoing interBSC inter cell handovers (using TCHH originally, excluding directed retry)

Description: Inter BSC handover is usually triggered by the causes related to receiving level, receiving performance, TA, load-sharing, MSC interference, DIRECTED RETRY, rapid level drop, better cell and O&M interference. In this procedure, the source cell and target cell are controlled by different BSCs. The source cell sends HANDOVER REQUIRED to MSC to initiate handover. This item provides the relation between the frequency of inter BSC handover and the types of channels currently seized by the calls. For information about inter BSC handover see Attempted outgoing interBSC inter cell handovers in Cell Measurement Function.

Measurement point: After handover algorithm decision, the source cell (i.e. the current cell of the call) sends HANDOVER REQUIRED to MSC. This item is measured when the original type of the channel of this call is "Half rate TCH" in this procedure.

Formula: None.

490


XXXVIII. Request of TCH allocation (TCHF)

Description: In the procedures of very early assignment, assignment and handover, the channel management module of BSC decides the type of the channel to be allocated after BSC receives a channel request. Based on the channel allocation algorithms, the requested channels can be divided into four types: Full rate TCH, Half rate TCH, Full rate TCH preferred and Half rate TCH preferred. This item provides the respective times of these four types of channels being requested.

Measurement point: This item is measured when the channel management module of BSC decides the type of the channel to be allocated as "Full rate TCH" after BSC receives channel request.

Formula: None.

XXXIX. Request of TCH allocation (TCHH)

Description: In the procedures of very early assignment, assignment and handover, the channel management module of BSC decides the type of the channel to be allocated after BSC receives a channel request. Based on the channel allocation algorithms, the requested channels can be divided into four types: Full rate TCH, Half rate TCH, Full rate TCH preferred and half TCH rate preferred. This item provides the respective times of these four types of channels being requested.

Measurement point: This item is measured when the channel management module of BSC decides the type of the channel to be allocated as "Half rate TCH" after BSC receives channel request.

Formula: None.

XL. Request of TCH allocation (TCHF preferred)


Measurement point: This item is measured when the channel management module of BSC decides the type of the channel to be allocated as "Full rate TCH preferred" after BSC receives channel request.

Formula: None.

491


XLI. Request of TCH allocation (TCHH preferred)


Measurement point: This item is measured when the channel management module of BSC decides the type of the channel to be allocated as "Half rate TCH preferred" after BSC receives channel request.

Formula: None.

XLII. Successful TCHF seizures during very early assignment

Description: In the very early assignment procedure (including the MS access due to various causes), after MS has successfully seized the TCH allocated by the network, BSC regards this very early assignment a successful one. This item provides the respective times of various types of channels being seized during a successful very early assignment. Note that, the channel here refers to the one seized by MS rather than the one requested for. For details of very early assignment procedure, see Attempted TCH seizures during very earlyassignment (TCHF) in Cell Measurement Function (2).

Measurement point: This item is measured in very early assignment procedure when BSC receives CHANNEL ACTIVATION ACKNOWLEDGE from BTS, and in this message, the channel type is "Full rate TCH".

Formula: None.

XLIII. Successful TCHH seizures during very early assignment

Description: In the very early assignment procedure (including the MS access due to various causes), after MS has successfully seized the TCH allocated by the network, BSC regards this very early assignment a successful one. This item provides the respective times of various types of channels being seized during a successful very early assignment. Note that, the channel here refers to the one seized by MS rather than the one requested for. For details of very early assignment procedure, see Attempted TCH seizures during very earlyassignment (TCHF) in Cell Measurement Function (2).

Measurement point: This item is measured in very early assignment procedure when BSC receives CHANNEL ACTIVATION ACKNOWLEDGE from BTS, and in this message, the channel type is "Half rate TCH".

Formula: None.

492


XLIV. Successful TCH seizures during very early assignment (TCHF)

Description: In the very early assignment procedure (including the MS access due to various causes), after MS has successfully seized the TCH allocated by the network, BSC regards this very early assignment a successful one. This item provides the times of successful MS access after MS requesting for Full rate TCH. Please note that the channel here is the one MS requests for, but the one actually allocated may be either Full rate or Half rate TCH. For details about channel allocation in very early assignment, see Attempted TCHseizures during very early assignment (TCHF) in Cell Measurement Function (2).

Measurement point: This item is measured in very early assignment procedure when BSC receives CHANNEL ACTIVATION ACKNOWLEDGE from BTS, in which the type of the requested channel is "Full rate TCH".

Formula: None.

XLV. Successful TCH seizures during very early assignment (TCHF preferred)

Description: In the very early assignment procedure (including the MS access due to various causes), after MS has successfully seized the TCH allocated by the network, BSC regards this very early assignment a successful one. This item provides the times of successful MS access after MS requesting for Full rate TCH. Please note that the channel here is the one MS requests for, but the one actually allocated may be either Full rate or Half rate TCH. For details about channel allocation in very early assignment, see Attempted TCHseizures during very early assignment (TCHF) in Cell Measurement Function (2).

Measurement point: This item is measured in very early assignment procedure when BSC receives CHANNEL ACTIVATION ACKNOWLEDGE from BTS, in which the type of the requested channel is "Full or Half rate TCH channel, Full rate preferred, changes between full rate and half rate not allowed after first channel allocation as a result of the request".

Formula: None.

XLVI. Successful TCH seizures during very early assignment (TCHH preferred)

Description: In the very early assignment procedure (including the MS access due to various causes), after MS has successfully seized the TCH allocated by the network, BSC regards this very early assignment a successful one. This item provides the times of successful MS access after MS requesting for Full rate TCH. Please note that the channel here is the one MS requests for, but the one actually allocated may be either Full rate or Half rate TCH. For details

493


about channel allocation in very early assignment, see Attempted TCHseizures during very early assignment (TCHF) in Cell Measurement Function (2).

Measurement point: This item is measured in very early assignment procedure when BSC receives CHANNEL ACTIVATION ACKNOWLEDGE from BTS, in which the type of the requested channel is "Full or Half rate TCH channel. Half rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request".

Formula: None.

XLVII. Successful TCH seizures during assignment (TCHF)

Description: In assignment procedure, MSC sends ASSIGNMENT REQUEST to BSC. This message contains the type of the channel to be assigned. On reception of this message, BSC allocates a channel for MS. After MS has successfully seized the TCH, BSC considers the assigned TCH successfully seized. A successful Directed Retry in assignment procedure is also regarded as a successful TCH seizure. This item provides the distribution of successful assigned TCH seizures in the messages ASSIGNMENT REQUEST containing various types of channels.

Measurement point:1) If the target cell of Directed Retry is controlled by other BSC, then after

Directed Retry has been successfully implemented, MSC sends CLEAR COMMAND to the originating BSC to clear all the original connections. This item is measured when this message contains the assigned channel type of "Full rate TCH".

2) If the destinatin cell of Directed Retry is controlled by the local BSC, then after Directed Retry has been successfully implemented, the target cell will notify the source cell to clear all resources and connections. This item is also measured when the source cell receives this internal message and the message ASSIGNMENT REQUEST contains the assigned channel type of "Full rate TCH".

3) This item is also measured when BSC sends ASSIGNMENT COMPLETE to BSC after the assignment procedure is successfully implemented, and the message ASSIGNMENT REQUEST contains the assigned channel type of "Full rate TCH".

Formula: None.

XLVIII. Successful TCH seizures during assignment (TCHH)

Description: In assignment procedure, MSC sends ASSIGNMENT REQUEST to BSC. This message contains the type of the channel to be assigned. On reception of this message, BSC allocates a channel for MS. After MS has

494


successfully seized the TCH, BSC considers the assigned TCH successfully seized. A successful Directed Retry in assignment procedure is also regarded as a successful TCH seizure. This item provides the distribution of successful assigned TCH seizures in the messages ASSIGNMENT REQUEST containing various types of channels.


Directed Retry has been successfully implemented, MSC sends CLEAR COMMAND to the originating BSC to clear all the original connections. This item is measured when this message contains the assigned channel type of "Half rate TCH".

2) If the destinatin cell of Directed Retry is controlled by the local BSC, then after Directed Retry has been successfully implemented, the target cell will notify the source cell to clear all resources and connections. This item is also measured when the source cell receives this internal message and the message ASSIGNMENT REQUEST contains the assigned channel type of "Half rate TCH".

3) This item is also measured when BSC sends ASSIGNMENT COMPLETE to BSC after the assignment procedure is successfully implemented, and the message ASSIGNMENT REQUEST contains the assigned channel type of "Half rate TCH".

Formula: None.

XLIX. Successful TCH seizures during assignment (TCHF preferred, change not allowed)



Directed Retry has been successfully implemented, MSC sends CLEAR COMMAND to the originating BSC to clear all the original connections. This item is measured when ASSIGNMENT REQUEST contains the assigned channel type of "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request".

495


2) If the destinatin cell of Directed Retry is controlled by the local BSC, then after Directed Retry has been successfully implemented, the target cell will notify the source cell to clear all resources and connections. This item is also measured when the source cell receives this internal message and the message ASSIGNMENT REQUEST contains the assigned channel type of "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request".

3) This item is also measured when BSC sends ASSIGNMENT COMPLETE to BSC after the assignment procedure is successfully implemented, and the message ASSIGNMENT REQUEST contains the assigned channel type of "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request".

Formula: None.

L. Successful TCH seizures during assignment (TCHH preferred, change not allowed)



Directed Retry has been successfully implemented, MSC sends CLEAR COMMAND to the originating BSC to clear all the original connections. This item is measured when this message contains the assigned channel type of "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request".

2) If the destinatin cell of Directed Retry is controlled by the local BSC, then after Directed Retry has been successfully implemented, the target cell will notify the source cell to clear all resources and connections. This item is also measured when the source cell receives this internal message and the message ASSIGNMENT REQUEST contains the assigned channel type of "Full or Half rate TCH channel, Half rate preferred, changes between Full rate

496


and Half rate not allowed after first channel allocation as a result of the request".

3) This item is also measured when BSC sends ASSIGNMENT COMPLETE to BSC after the assignment procedure is successfully implemented, and the message ASSIGNMENT REQUEST contains the assigned channel type of "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request".

Formula: None.

LI. Successful TCH seizures during assignment (TCHF preferred, change allowed)



Directed Retry has been successfully implemented, MSC sends CLEAR COMMAND to the originating BSC to clear all the original connections. This item is measured when this message contains the assigned channel type of "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request".

2) If the destinatin cell of Directed Retry is controlled by the local BSC, then after Directed Retry has been successfully implemented, the target cell will notify the source cell to clear all resources and connections. This item is also measured when the source cell receives this internal message and the message ASSIGNMENT REQUEST contains the assigned channel type of "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request".

3) This item is also measured when BSC sends ASSIGNMENT COMPLETE to BSC after the assignment procedure is successfully implemented, and the message ASSIGNMENT REQUEST contains the assigned channel type of "Full or Half rate TCH channel, Full rate preferred, changes between Full rate

497


and Half rate allowed also after first channel allocation as a result of the request".

Formula: None.

LII. Successful TCH seizures during assignment (TCHH preferred, change allowed)

Description: In assignment procedure, MSC sends ASSIGNMENT REQUEST to BSC. This message contains the type of the channel to be assigned. On reception of this message, BSC allocates a channel for MS. After MS has successfully seized the TCH, BSC considers the assigned TCH successfully seized. A successful Directed Retry in assignment procedure is also regarded as a successful TCH seizure. This item provides the distribution of times of successful assigned TCH seizures in the messages ASSIGNMENT REQUEST containing various types of channels.


Directed Retry has been successfully implemented, MSC sends CLEAR COMMAND to the originating BSC to clear all the original connections. This item is measured when this message contains the assigned channel type of "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request".

2) If the destinatin cell of Directed Retry is controlled by the local BSC, then after Directed Retry has been successfully implemented, the target cell will notify the source cell to clear all resources and connections. This item is also measured when the source cell receives this internal message and the message ASSIGNMENT REQUEST contains the assigned channel type of "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request".

3) This item is also measured when BSC sends ASSIGNMENT COMPLETE to BSC after the assignment procedure is successfully implemented, and the message ASSIGNMENT REQUEST contains the assigned channel type of "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request".

Formula: None.

498


LIII. Successful TCH seizures during assignment (TCHF or TCHH, change not allowed)

Description: In assignment procedure, MSC sends ASSIGNMENT REQUEST to BSC. This message contains the type of the channel to be assigned. On reception of this message, BSC allocates a channel for MS. After MS has successfully seized the TCH, BSC considers the assigned TCH successfully seized. A successful Directed Retry in assignment procedure is also regarded as a successful TCH seizure. This item provides the distribution of the times of successful assigned TCH seizures in the messages ASSIGNMENT REQUEST containing various types of channels.


Directed Retry has been successfully implemented, MSC sends CLEAR COMMAND to the originating BSC to clear all the original connections. This item is measured when this message contains the assigned channel type of "Full or Half rate TCH channel, changes between full and Half rate not allowed after first channel allocation as a result of the request".

2) If the destinatin cell of Directed Retry is controlled by the local BSC, then after Directed Retry has been successfully implemented, the target cell will notify the source cell to clear all resources and connections. This item is also measured when the source cell receives this internal message and the message ASSIGNMENT REQUEST contains the assigned channel type of "Full or Half rate TCH channel, changes between full and Half rate not allowed after first channel allocation as a result of the request".

3) This item is also measured when BSC sends ASSIGNMENT COMPLETE to BSC after the assignment procedure is successfully implemented, and the message ASSIGNMENT REQUEST contains the assigned channel type of "Full or Half rate TCH channel, changes between full and Half rate not allowed after first channel allocation as a result of the request".

Formula: None.

LIV. Successful TCH seizures during assignment (TCHF or TCHH, change allowed)

Description: In assignment procedure, MSC sends ASSIGNMENT REQUEST to BSC. This message contains the type of the channel to be assigned. On reception of this message, BSC allocates a channel for MS. After MS has successfully seized the TCH, BSC considers the assigned TCH successfully seized. A successful Directed Retry in assignment procedure is also regarded as a successful TCH seizure. This item provides the distribution of times of successful assigned TCH seizures in the messages ASSIGNMENT REQUEST containing various types of channels.

499



Directed Retry has been successfully implemented, MSC sends CLEAR COMMAND to the originating BSC to clear all the original connections. This item is measured when this message contains the assigned channel type of "Full or Half rate TCH channel, changes between full and Half rate allowed also after first channel allocation as a result of the request".

2) If the destinatin cell of Directed Retry is controlled by the local BSC, then after Directed Retry has been successfully implemented, the target cell will notify the source cell to clear all resources and connections. This item is also measured when the source cell receives this internal message and the message ASSIGNMENT REQUEST contains the assigned channel type of "Full or Half rate TCH channel, changes between full and Half rate allowed also after first channel allocation as a result of the request".

3) This item is also measured when BSC sends ASSIGNMENT COMPLETE to BSC after the assignment procedure is successfully implemented, and the message ASSIGNMENT REQUEST contains the assigned channel type of "Full or Half rate TCH channel, changes between full and Half rate allowed also after first channel allocation as a result of the request".

Formula: None.

LV. Successful TCHF seizures during assignment (excluding directed retry)

Description: In assignment procedure, MSC sends ASSIGNMENT REQUEST to BSC. This message contains the type of the channel to be assigned. On reception of this message, BSC allocates a channel for MS. After MS has successfully seized the TCH, BSC considers the assigned TCH successfully seized. A successful Directed Retry in assignment procedure is also regarded as a successful TCH seizure. This item provides the times of MS seizing various channels in the successful assigned TCH seizures.


Directed Retry has been successfully implemented, MSC sends CLEAR COMMAND to the originating BSC to clear all the original connections. This item is measured when this message is received and the type of the seized TCH is "Full rate TCH".

2) If the destinatin cell of Directed Retry is controlled by the local BSC, then after Directed Retry has been successfully implemented, the target cell will notify the source cell to clear all resources and connections. This item is also measured when the source cell receives this internal message and the type of the seized TCH is "Full rate TCH".

500


3) This item is also measured when BSC sends ASSIGNMENT COMPLETE to MSC after the assignment procedure is successfully implemented, and the type of the seized TCH is "Full rate TCH".

Formula: None.

LVI. Successful TCHH seizures during assignment (excluding directed retry)

Description: In assignment procedure, MSC sends ASSIGNMENT REQUEST to BSC. This message contains the type of the channel to be assigned. On reception of this message, BSC allocates a channel for MS. After MS has successfully seized the TCH, BSC considers the assigned TCH successfully seized. A successful Directed Retry in assignment procedure is also regarded as a successful TCH seizure. This item provides the times of MS seizing various channels in the successful assigned TCH seizures.


Directed Retry has been successfully implemented, MSC sends CLEAR COMMAND to the originating BSC to clear all the original connections. This item is measured when this message is received and the type of the seized TCH is "Half rate TCH".

2) If the destinatin cell of Directed Retry is controlled by the local BSC, then after Directed Retry has been successfully implemented, the target cell will notify the source cell to clear all resources and connections. This item is also measured when the source cell receives this internal message and the type of the seized TCH is "Half rate TCH".

3) This item is also measured when BSC sends ASSIGNMENT COMPLETE to MSC after the assignment procedure is successfully implemented, and the type of the seized TCH is "Half rate TCH".

Formula: None.

LVII. Successful TCH seizures during intraBSC incoming cell handover (TCHF preferred, change not allowed)

Description: In intra BSC incoming cell handover procedure, the target cell receives Intercell Handover Request. On reception of this message, the target cell decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. BSC receives this message and considers that the MS

501


has successfully seized the TCH. This item provides the distribution of times of successful intra BSC incoming cell handovers in various handovers in which different channel types are requested for. For details, see Attempted TCHseizures during intraBSC incoming cell handover (TCHF) in Cell Measurement Function (2). For information about intra BSC incoming cell handover, see Attempted TCH seizures for intraBSC incoming cell handover in Cell Measurement Function.

Measurement point: This item is measured in intra BSC incoming cell handover procedure when the destinationcell receives HANDOVER DETECTION, and the requested channel type is "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request".

Formula: None.

LVIII. Successful TCH seizures during intraBSC incoming cell handover (TCHH preferred, change not allowed)

Description: In intra BSC incoming cell handover procedure, the target cell receives Intercell Handover Request. On reception of this message, the target cell decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. BSC receives this message and considers that the MS has successfully seized the TCH. This item provides the distribution of times of successful intra BSC incoming cell handovers in various handovers in which different channel types are requested for. For details, see Attempted TCHseizures during intraBSC incoming cell handover (TCHF) in Cell Measurement Function (2). For information about intra BSC incoming cell handover, see Attempted TCH seizures for intraBSC incoming cell handover in Cell Measurement Function.

Measurement point: This item is measured in intra BSC incoming cell handover procedure when the destinationcell receives HANDOVER DETECTION, and the requested channel type is "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request".

Formula: None.

502


LIX. Successful TCH seizures during intraBSC incoming cell handover (TCHF or TCHH, change not allowed)


Measurement point: This item is measured in intra BSC incoming cell handover procedure when the destinationcell receives HANDOVER DETECTION, and the requested channel type is "Full or Half rate TCH channel, changes between full and Half rate not allowed after first channel allocation as a result of the request".

Formula: None.

LX. Successful TCH seizures during intraBSC incoming cell handover (TCHF or TCHH, change allowed)

Description: In intra BSC incoming cell handover procedure, the target cell receives Intercell Handover Request. On reception of this message, the target cell decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. BSC receives this message and considers that the MS has successfully seized the TCH. This item provides the distribution of times of successful intra BSC incoming cell handovers in various handovers in which different channel types are requested for. For details, see Attempted TCHseizures during intraBSC incoming cell handover (TCHF) in Cell Measurement Function (2). For information about intra BSC incoming cell

503


handover, see Attempted TCH seizures for intraBSC incoming cell handover in Cell Measurement Function.

Measurement point: This item is measured in intra BSC incoming cell handover procedure when the destinationcell receives HANDOVER DETECTION, and the requested channel type is "Full or Half rate TCH channel, changes between full and Half rate allowed also after first channel allocation as a result of the request".

Formula: None.

LXI. Successful TCH seizures during intraBSC incoming cell handover (TCHF)


Measurement point: This item is measured in intra BSC incoming cell handover procedure when the destinationcell receives HANDOVER DETECTION, and the requested channel type is "Full rate TCH".

Formula: None.

LXII. Successful TCH seizures during intraBSC incoming cell handover (TCHH)

Description: In intra BSC incoming cell handover procedure, the target cell receives Intercell Handover Request. On reception of this message, the target cell decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER

504


ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. BSC receives this message and considers that the MS has successfully seized the TCH. This item provides the distribution of times of successful intra BSC incoming cell handovers in various handovers in which different channel types are requested for. For details, see Attempted TCHseizures during intraBSC incoming cell handover (TCHF) in Cell Measurement Function (2). For information about intra BSC incoming cell handover, see Attempted TCH seizures for intraBSC incoming cell handover in Cell Measurement Function.

Measurement point: This item is measured in intra BSC incoming cell handover procedure when the destinationcell receives HANDOVER DETECTION, and the requested channel type is "Half rate TCH".

Formula: None.

LXIII. Successful TCH seizures during intraBSC incoming cell handover (TCHF preferred, change allowed)


Measurement point: This item is measured in intra BSC incoming cell handover procedure when the destinationcell receives HANDOVER DETECTION, and the requested channel type is "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request".

Formula: None.

505


LXIV. Successful TCH seizures during intraBSC incoming cell handover (TCHH preferred, change allowed)


Measurement point: This item is measured in intra BSC incoming cell handover procedure when the destinationcell receives HANDOVER DETECTION, and the requested channel type is "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request".

Formula: None.

LXV. Successful TCH seizures during intracell handover (TCHF)

Description: In intra cell handover (i.e. handover between different channels of the serving cell) procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, BSC decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. BSC receives this message and considers that the MS has successfully seized the TCH. This item provides the distribution of times of successful intra BSC incoming cell handovers in various handovers in which different channel types are requested for. For details, see Attempted TCH seizures during intracell handover (TCHF) in Cell

506


Measurement Function (2). For information about intracell handover, see Attempted TCH seizures for intracell handover in Cell Measurement Function.

Measurement point: This item is measured in intra cell handover procedure when the target cell receives HANDOVER DETECTION, and the requested channel type is "Full rate TCH".

Formula: None.

LXVI. Successful TCH seizures during intracell handover (TCHH)

Description: In intra cell handover (i.e. handover between different channels of the serving cell) procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, BSC decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. BSC receives this message and considers that the MS has successfully seized the TCH. This item provides the distribution of times of successful intra BSC incoming cell handovers in various handovers in which different channel types are requested for. For details, see Attempted TCH seizures during intracell handover (TCHF) in Cell Measurement Function (2). For information about intracell handover, see Attempted TCH seizures for intracell handover in Cell Measurement Function.

Measurement point: This item is measured in intra cell handover procedure when the target cell receives HANDOVER DETECTION, and the requested channel type is "Half rate TCH".

Formula: None.

LXVII. Successful TCH seizures during intracell handover (TCHF preferred, change allowed)

Description: In intra cell handover (i.e. handover between different channels of the serving cell) procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, BSC decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. BSC receives this message and

507


considers that the MS has successfully seized the TCH. This item provides the distribution of times of successful intra BSC incoming cell handovers in various handovers in which different channel types are requested for. For details, see Attempted TCH seizures during intracell handover (TCHF) in Cell Measurement Function (2). For information about intracell handover, see Attempted TCH seizures for intracell handover in Cell Measurement Function.

Measurement point: This item is measured in intra cell handover procedure when the target cell receives HANDOVER DETECTION, and the requested channel type is "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request".

Formula: None.

LXVIII. Successful TCH seizures during intracell handover (TCHH preferred, change allowed)

Description: In intra cell handover (i.e. handover between different channels of the serving cell) procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, BSC decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. BSC receives this message and considers that the MS has successfully seized the TCH. This item provides the distribution of times of successful intra BSC incoming cell handovers in various handovers in which different channel types are requested for. For details, see Attempted TCH seizures during intracell handover (TCHF) in Cell Measurement Function (2). For information about intracell handover, see Attempted TCH seizures for intracell handover in Cell Measurement Function.

Measurement point: This item is measured in intra cell handover procedure when the target cell receives HANDOVER DETECTION, and the requested channel type is "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request".

Formula: None.

LXIX. Successful TCHF seizures during intraBSC incoming cell handover

Description: In intra BSC incoming cell handover procedure, the target cell receives Intercell Handover Request. On reception of this message, the target

508


cell decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. BSC receives this message and considers that the MS has successfully seized the TCH. This item provides the times of MS seizing various types of channels when the TCH is successfully seized in intra BSC incoming cell handover. For details, see Attempted TCH seizures duringintraBSC incoming cell handover (TCHF) in Cell Measurement Function (2). For information about intra BSC incoming cell handover, see Attempted TCHseizures for intraBSC incoming cell handover in Cell Measurement Function.

Measurement point: This item is measured in intra BSC incoming cell handover procedure when the target cell receives HANDOVER DETECTION, and the requested channel type is "Full rate TCH".

Formula: None.

LXX. Successful TCHH seizures during intraBSC incoming cell handover

Description: In intra BSC incoming cell handover procedure, the target cell receives Intercell Handover Request. On reception of this message, the target cell decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. BSC receives this message and considers that the MS has successfully seized the TCH. This item provides the times of MS seizing various types of channels when the TCH is successfully seized in intra BSC incoming cell handover. For details, see Attempted TCH seizures duringintraBSC incoming cell handover (TCHF) in Cell Measurement Function (2). For information about intra BSC incoming cell handover, see Attempted TCHseizures for intraBSC incoming cell handover in Cell Measurement Function.

Measurement point: This item is measured in intra BSC incoming cell handover procedure when the target cell receives HANDOVER DETECTION, and the requested channel type is "Half rate TCH".

Formula: None.

509


LXXI. Successful TCHF seizures during intracell handover

Description: In intra cell handover (i.e. handover between different channels of the serving cell) procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, BSC decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. BSC receives this message and considers that the MS has successfully seized the TCH. This item provides the times of MS seizing various types of channels when the TCH is successfully seized in intra cell handover. For details, see Attempted TCH seizures duringintracell handover (TCHF) in Cell Measurement Function (2). For information about intracell handover, see Attempted TCH seizures for intracell handover in Cell Measurement Function.

Measurement point: This item is measured in intra cell handover procedure when the target cell receives HANDOVER DETECTION, and the requested channel type is "Full rate TCH".

Formula: None.

LXXII. Successful TCHH seizures during intracell handover

Description: In intra cell handover (i.e. handover between different channels of the serving cell) procedure, the serving cell receives Intercell Handover Request containing the channel mode of the current call. On reception of this message, BSC decides the channel type to be allocated for this handover according to handover type, the capability of the circuit pool of the A interface, channel type of the current call and the channel rate and channel type requested by MSC during call setup. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. BSC receives this message and considers that the MS has successfully seized the TCH. This item provides the times of MS seizing various types of channels when the TCH is successfully seized in intra cell handover. For details, see Attempted TCH seizures duringintracell handover (TCHF) in Cell Measurement Function (2). For information about intracell handover, see Attempted TCH seizures for intracell handover in Cell Measurement Function.

510


Measurement point: This item is measured in intra cell handover procedure when the target cell receives HANDOVER DETECTION, and the requested channel type is "Half rate TCH".

Formula: None.

LXXIII. Successful TCH seizures during interBSC incoming cell handover (TCHF)

Description: In inter BSC handover procedure, the cell receives HANDOVER REQUEST from MSC. This message is sent by other BSC to request for a TCH. It contains the channel type for this handover specified by MSC, and BSC allocates channels according to this message. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. This item provides the distribution of times of successful inter BSC incoming cell handovers in various handovers in which different channel types are requested for. For inter BSC handover procedure, see Attempted TCH seizures for interBSC incomingcell handover in Cell Measurement Function.

Note:The definitions of channel types in HANDOVER REQUEST are the same as those in ASSIGNMENT

REQUEST. See Attempted TCH seizures during assignment (TCHF) in Cell Measurement Function

(2).

Measurement point: This item is measured in inter BSC handover procedure when the related cell receives HANDOVER REQUEST from MSC and the type of the channel requested for is "Full rate TCH".

Formula: None.

LXXIV. Successful TCH seizures during interBSC incoming cell handover (TCHH)

Description: In inter BSC handover procedure, the cell receives HANDOVER REQUEST from MSC. This message is sent by other BSC to request for a TCH. It contains the channel type for this handover specified by MSC, and BSC allocates channels according to this message. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. This item provides the distribution of times of successful inter BSC incoming cell handovers in various handovers in which different channel types are requested for. For inter BSC handover procedure, see Attempted TCH seizures for interBSC incomingcell handover in Cell Measurement Function. For other information, see

511


Successful TCH seizures during interBSC incoming cell handover (TCHF) in Cell Measurement Function (2).

Measurement point: This item is measured in inter BSC handover procedure when the target cell receives HANDOVER DETECTION and the type of the channel requested for is "Half rate TCH".

Formula: None.

LXXV. Successful TCH seizures during interBSC incoming cell handover (TCHF preferred, change not allowed)

Description: In inter BSC handover procedure, the cell receives HANDOVER REQUEST from MSC. This message is sent by other BSC to request for a TCH. It contains the channel type for this handover specified by MSC, and BSC allocates channels according to this message. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. This item provides the distribution of times of successful inter BSC incoming cell handovers in various handovers in which different channel types are requested for. For inter BSC handover procedure, see Attempted TCH seizures for interBSC incomingcell handover in Cell Measurement Function. For other information, see Successful TCH seizures during interBSC incoming cell handover (TCHF) in Cell Measurement Function (2).

Measurement point: This item is measured in inter BSC handover procedure when the target cell receives HANDOVER DETECTION and the type of the channel requested for is "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request".

Formula: None.

LXXVI. Successful TCH seizures during interBSC incoming cell handover (TCHH preferred, change not allowed)

Description: In inter BSC handover procedure, the cell receives HANDOVER REQUEST from MSC. This message is sent by other BSC to request for a TCH. It contains the channel type for this handover specified by MSC, and BSC allocates channels according to this message. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. This item provides the distribution of times of successful inter BSC incoming cell handovers in various handovers in which different channel types are requested for. For inter BSC handover procedure, see Attempted TCH seizures for interBSC incoming

512


cell handover in Cell Measurement Function. For other information, see Successful TCH seizures during interBSC incoming cell handover (TCHF) in Cell Measurement Function (2).

Measurement point: This item is measured in inter BSC handover procedure when the target cell receives HANDOVER DETECTION and the type of the channel requested for is "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate not allowed after first channel allocation as a result of the request".

Formula: None.

LXXVII. Successful TCH seizures during interBSC incoming cell handover (TCHF preferred, change allowed)


Measurement point: This item is measured in inter BSC handover procedure when the target cell receives HANDOVER DETECTION and the type of the channel requested for is "Full or Half rate TCH channel, Full rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request".

Formula: None.

LXXVIII. Successful TCH seizures during interBSC incoming cell handover (TCHH preferred, change allowed)

Description: In inter BSC handover procedure, the cell receives HANDOVER REQUEST from MSC. This message is sent by other BSC to request for a TCH. It contains the channel type for this handover specified by MSC, and BSC allocates channels according to this message. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. This item provides

513


the distribution of times of successful inter BSC incoming cell handovers in various handovers in which different channel types are requested for. For inter BSC handover procedure, see Attempted TCH seizures for interBSC incomingcell handover in Cell Measurement Function. For other information, see Successful TCH seizures during interBSC incoming cell handover (TCHF) in Cell Measurement Function (2).

Measurement point: This item is measured in inter BSC handover procedure when the target cell receives HANDOVER DETECTION and the type of the channel requested for is "Full or Half rate TCH channel, Half rate preferred, changes between Full rate and Half rate allowed also after first channel allocation as a result of the request".

Formula: None.

LXXIX. Successful TCH seizures during interBSC incoming cell handover (TCHF or TCHH, change not allowed)


Measurement point: This item is measured in inter BSC handover procedure when the target cell receives HANDOVER DETECTION and the type of the channel requested for is "Full or Half rate TCH channel, changes between full and Half rate not allowed after first channel allocation as a result of the request".

Formula: None.

LXXX. Successful TCH seizures during interBSC incoming cell handover (TCHF or TCHH, change allowed)

Description: In inter BSC handover procedure, the cell receives HANDOVER REQUEST from MSC. This message is sent by other BSC to request for a TCH. It contains the channel type for this handover specified by MSC, and BSC allocates channels according to this message. After successfully

514


allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. This item provides the distribution of times of successful inter BSC incoming cell handovers in various handovers in which different channel types are requested for. For inter BSC handover procedure, see Attempted TCH seizures for interBSC incomingcell handover in Cell Measurement Function. For other information, see Successful TCH seizures during interBSC incoming cell handover (TCHF) in Cell Measurement Function (2).

Measurement point: This item is measured in inter BSC handover procedure when the target cell receives HANDOVER DETECTION and the type of the channel requested for is "Full or Half rate TCH channel, changes between full and Half rate allowed also after first channel allocation as a result of the request".

Formula: None.

LXXXI. Successful TCHF seizures during interBSC incoming cell handover

Description: In inter BSC handover procedure, the cell receives HANDOVER REQUEST from MSC. This message is sent by other BSC to request for a TCH. It contains the channel type for this handover specified by MSC, and BSC allocates channels according to this message. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. This item provides the times of MS seizing various types of channels when the TCH is successfully seized in inter BSC incoming cell handover. For inter BSC handover procedure, see Attempted TCH seizures for interBSC incoming cellhandover in Cell Measurement Function.

Measurement point: This item is measured in inter BSC handover procedure when the target cell receives HANDOVER DETECTION and the type of the channel seized actually is "Full rate TCH".

Formula: None.

LXXXII. Successful TCHH seizures during interBSC incoming cell handover

Description: In inter BSC handover procedure, the cell receives HANDOVER REQUEST from MSC. This message is sent by other BSC to request for a TCH. It contains the channel type for this handover specified by MSC, and BSC allocates channels according to this message. After successfully allocating the channel, BSC notifies MS to access the network. After accessing the network, MS sends HANDOVER ACCESS to BTS. After processing this message, BTS sends HANDOVER DETECTION to BSC. This

515


item provides the times of MS seizing various types of channels when the TCH is successfully seized in inter BSC incoming cell handover. For inter BSC handover procedure, see Attempted TCH seizures for interBSC incoming cellhandover in Cell Measurement Function.

Measurement point: In inter BSC handover procedure, the target cell receives HANDOVER DETECTION and the type of the channel seized actually is "Half rate TCH".

Formula: None.

LXXXIII. Successful outgoing internal inter cell handovers (using TCHF originally, excluding directed retry)

Description: In intra BSC outgoing cell handover procedure, the source cell sends HANDOVER COMMAND to MS. After MS successfully accesses the network, the source cell sends Inter Clear Request to the target cell indicating that this handover is successfully completed. The source cell receives this message and then clears the old resources. When the old resources are cleared, BSC considers that this handover is successfully completed. This item provides the distribution of successful handovers from the current cell to cells controlled by same BSC in the handovers from the current cell to cells controlled by same BSC of various types of TCHs originally seized. For information about intra BSC outgoing cell handover, see Attempted outgoinginternal inter cell handovers in Cell Measurement Function.

Measurement point: This item is measured when the source cell (current cell) receives the message Inter Clear Request (cause: handover success) and the type of the TCH originally seized is "Full rate TCH".

Formula: None.

LXXXIV. Successful outgoing internal inter cell handovers (using TCHH originally, excluding directed retry)

Description: In intra BSC outgoing cell handover procedure, the source cell sends HANDOVER COMMAND to MS. After MS successfully accesses the network, the source cell sends Inter Clear Request to the target cell indicating that this handover is successfully completed. The source cell receives this message and then clears the old resources. When the old resources are cleared, BSC considers that this handover is successfully completed. This item provides the distribution of successful handovers from the current cell to cells controlled by same BSC in the handovers from the current cell to cells controlled by same BSC of various types of TCHs originally seized. For information about intra BSC outgoing cell handover, see Attempted outgoinginternal inter cell handovers in Cell Measurement Function.

516


Measurement point: This item is measured when the source cell (current cell) receives the message Inter Clear Request (cause: handover success) and the type of the TCH originally seized is "Half rate TCH".

Formula: None.

LXXXV. Successful outgoing interBSC inter cell handovers (using TCHF originally, excluding directed retry)

Description: In intra BSC outgoing cell handover procedure, the source cell sends HANDOVER COMMAND to MS. After successfully accessing the network, MS sends Inter Clear Request (cause: handover success) to the target cell indicating that this handover is successfully completed. The source cell receives this message and then clears the old resources. When the old resources are cleared, BSC considers that this handover is successfully completed. If the handover is terminated due to normal MS onhook, it is also considered as a successful one. This item provides the distribution of successful handovers from the current cell to cells controlled by same BSC in the handovers from the current cell to cells controlled by same BSC of various types of TCHs originally seized. For information about inter BSC inter cell handover, see Successful outgoing interBSC inter cell handovers in Cell Measurement Function.

Measurement point:1) This item is measured in inter BSC outgoing cell handover procedure when the

source cell (current cell) receives CLEAR COMMAND (cause: handover success) from MSC, and the type of the channel originally seized is "Full rate TCH".

2) This item is measured in inter BSC outgoing cell handover procedure when the source cell (current cell) receives CLEAR COMMAND (cause: call control) from MSC, and the type of the channel originally seized is "Full rate TCH".

3) This item is measured in inter BSC outgoing cell handover procedure when the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause:

handover success or call control ） from MSC, and the type of the channel originally seized is "Full rate TCH".

Formula: None.

LXXXVI. Successful outgoing interBSC inter cell handovers (using TCHH originally, excluding directed retry)

Description: In intra BSC outgoing cell handover procedure, the source cell sends HANDOVER COMMAND to MS. After successfully accessing the network, MS sends Inter Clear Request (cause: handover success) to the target cell indicating that this handover is successfully completed. The source cell receives this message and then clears the old resources. When the old

517


resources are cleared, BSC considers that this handover is successfully completed. If the handover is terminated due to normal MS onhook, it is also considered as a successful one. This item provides the distribution of successful handovers from the current cell to cells controlled by same BSC in the handovers from the current cell to cells controlled by same BSC of various types of TCHs originally seized. For information about inter BSC inter cell handover, see Successful outgoing interBSC inter cell handovers in Cell Measurement Function.

Measurement point:1) This item is measured in inter BSC outgoing cell handover procedure when the

source cell (current cell) receives CLEAR COMMAND (cause: handover success) from MSC, and the type of the channel originally seized is "Half rate TCH".

2) This item is measured in inter BSC outgoing cell handover procedure when the source cell (current cell) receives CLEAR COMMAND (cause: call control) from MSC, and the type of the channel originally seized is "Half rate TCH".

3) This item is measured in inter BSC outgoing cell handover procedure when the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause:

handover success or call control ） from MSC, and the type of the channel originally seized is "Half rate TCH".

Formula: None.

LXXXVII. TCHF channel activation failures during very early assignment (NACK)

Description: In very early assignment procedure, after allocating TCH, BSC sends CHANNEL ACTIVATION to BTS to activate this channel. On reception of this message, BTS checks the status of the channel and responds. If BTS responds with CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE, BSC considers that the channel activation failed. This item provides the distribution of channel activation failures due to negative responses from BTS in the very early assignment procedures of difference types of TCH to be activated.

Measurement point: In very early assignment procedure, BSC sends CHANNEL ACTIVATION to BTS to activate "Full rate TCH". This item is measured when BTS responds with CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE.

Formula: None.

LXXXVIII. TCHH channel activation failures during very early assignment (NACK)

Description: In very early assignment procedure, after allocating TCH, BSC sends CHANNEL ACTIVATION to BTS to activate this channel. On reception

518


of this message, BTS checks the status of the channel and responds. If BTS responds with CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE, BSC considers that the channel activation failed. This item provides the distribution of channel activation failures due to negative responses from BTS in the very early assignment procedures of difference types of TCH to be activated.

Measurement point: In very early assignment procedure, BSC sends CHANNEL ACTIVATION to BTS to activate "Half rate TCH". This item is measured when BTS responds with CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE.

Formula: None.

LXXXIX. TCHF channel activation failures during very early assignment (TIMEOUT)

Description: In very early assignment procedure, after allocating TCH, BSC sends CHANNEL ACTIVATION to BTS to activate this channel and starts the internal timer (five seconds). On reception of this message, BTS checks the status of the channel and responds. If BSC fails to receive the response from BTS after timer expiry, it considers that channel activation failed. This item provides the distribution of channel activation failures due to expiry of timer of responses from BTS in the very early assignment procedures of difference types of TCH to be activated.

Measurement point: In very early assignment procedure, BSC sends CHANNEL ACTIVATION to BTS to activate "Full rate TCH". This item is measured when BSC fails to receive the response from BTS after timer expiry (five seconds later).

Formula: None.

XC. TCHH channel activation failures during very early assignment (TIMEOUT)

Description: In very early assignment procedure, after allocating TCH, BSC sends CHANNEL ACTIVATION to BTS to activate this channel and starts the internal timer (five seconds). On reception of this message, BTS checks the status of the channel and responds. If BSC fails to receive the response from BTS after timer expiry, it considers that channel activation failed. This item provides the distribution of channel activation failures due to expiry of timer of responses from BTS in the very early assignment procedures of difference types of TCH to be activated.

Measurement point: In very early assignment procedure, BSC sends CHANNEL ACTIVATION to BTS to activate "Half rate TCH". This item is measured when BSC fails to receive the response from BTS after timer expiry (five seconds later).

519


Formula: None.

XCI. TCHF channel activation failures during assignment (NACK)

Description: In assignment procedure, on reception of ASSIGNMENT REQUEST from MSC, BSC allocates TCH, and then sends CHANNEL ACTIVATION to BTS to activate this channel. On reception of this message, BTS checks the status of the channel and responds. If BTS responds with CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE, BSC considers that the channel activation failed. This item provides the distribution of channel activation failures due to negative responses from BTS in the assignment procedures of difference types of TCH to be activated.

Measurement point: In assignment procedure, BSC sends CHANNEL ACTIVATION to BTS to activate "Full rate TCH". This item is measured when BTS responds with CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE.

Formula: None.

XCII. TCHH channel activation failures during assignment (NACK)

Description: In assignment procedure, on reception of ASSIGNMENT REQUEST from MSC, BSC allocates TCH, and then sends CHANNEL ACTIVATION to BTS to activate this channel. On reception of this message, BTS checks the status of the channel and responds. If BTS responds with CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE, BSC considers that the channel activation failed. This item provides the distribution of channel activation failures due to negative responses from BTS in the assignment procedures of difference types of TCH to be activated.

Measurement point: In assignment procedure, BSC sends CHANNEL ACTIVATION to BTS to activate "Half rate TCH". This item is measured when BTS responds with CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE.

Formula: None.

XCIII. TCHF channel activation failures during assignment (TIMEOUT)

Description: In assignment procedure, on reception of ASSIGNMENT REQUEST from MSC, BSC allocates TCH, and then sends CHANNEL ACTIVATION to BTS to activate this channel and starts the internal timer (five seconds). On reception of this message, BTS checks the status of the channel and responds. If BSC fails to receive the response from BTS after timer expiry, it considers that channel activation failed. This item provides the distribution of channel activation failures due to expiry of timer of responses from BTS in the assignment procedures of difference types of TCH to be activated.

Measurement point: In assignment procedure, BSC sends CHANNEL ACTIVATION to BTS to activate "Full rate TCH". This item is measured when

520


BSC fails to receive the response from BTS after timer expiry (five seconds later).

Formula: None.

XCIV. TCHH channel activation failures during assignment (TIMEOUT)

Description: In assignment procedure, on reception of ASSIGNMENT REQUEST from MSC, BSC allocates TCH, and then sends CHANNEL ACTIVATION to BTS to activate this channel and starts the internal timer (five seconds). On reception of this message, BTS checks the status of the channel and responds. If BSC fails to receive the response from BTS after timer expiry, it considers that channel activation failed. This item provides the distribution of channel activation failures due to expiry of timer of responses from BTS in the assignment procedures of difference types of TCH to be activated.

Measurement point: In assignment procedure, BSC sends CHANNEL ACTIVATION to BTS to activate "Half rate TCH". This item is measured when BSC fails to receive the response from BTS after timer expiry (five seconds later).

Formula: None.

XCV. TCHF channel activation failures during handover (NACK)

Description: This item covers the cases of intra BSC handover (including intra cell handover and intra BSC inter cell handover) and inter BSC handover. On reception of HANDOVER REQUEST from MSC, BSC is engaged in incoming BSC handover procedure. Or after receiving Intercell Handover Request from its other channel or from other cell controlled by the same BSC (source cell), the cell controlled by this BSC (target cell) is enaged in intra BSC handover procedure. In both procedures, BSC first allocates TCH, and then sends CHANNEL ACTIVATION to BTS to activate this channel. On reception of this message, BTS checks the status of the channel and responds. If BTS responds with CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE, BSC considers that the channel activation failed. This item provides the distribution of channel activation failures due to negative responses from BTS in the handover procedures of difference types of TCH to be activated.

Measurement point: In intra BSC or inter BSC procedure, BSC sends CHANNEL ACTIVATION to BTS to activate "Full rate TCH". This item is measured when BTS responds with CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE.

Formula: None.

521


XCVI. TCHH channel activation failures during handover (NACK)

Description: This item covers the cases of intra BSC handover (including intra cell handover and intra BSC inter cell handover) and inter BSC handover. On reception of HANDOVER REQUEST from MSC, BSC is engaged in incoming BSC handover procedure. Or after receiving Intercell Handover Request from its other channel or from other cell controlled by the same BSC (source cell), the cell controlled by this BSC (target cell) is enaged in intra BSC handover procedure. In both procedures, BSC first allocates TCH, and then sends CHANNEL ACTIVATION to BTS to activate this channel. On reception of this message, BTS checks the status of the channel and responds. If BTS responds with CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE, BSC considers that the channel activation failed. This item provides the distribution of channel activation failures due to negative responses from BTS in the handover procedures of difference types of TCH to be activated.

Measurement point: In intra BSC or inter BSC procedure, BSC sends CHANNEL ACTIVATION to BTS to activate "Half rate TCH". This item is measured when BTS responds with CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE.

Formula: None.

XCVII. TCHF channel activation failures during handover (TIMEOUT)

Description: This item covers the cases of intra BSC handover (including intra cell handover and intra BSC inter cell handover) and inter BSC handover. On reception of HANDOVER REQUEST from MSC, BSC is engaged in incoming BSC handover procedure. Or after receiving Intercell Handover Request from its other channel or from other cell controlled by the same BSC (source cell), the cell controlled by this BSC (target cell) is enaged in intra BSC handover procedure. In both procedures, BSC first allocates TCH, and then sends CHANNEL ACTIVATION to BTS to activate this channell and starts the internal timer (five seconds). On reception of this message, BTS checks the status of the channel and responds. If BSC fails to receive the response from BTS after timer expiry, it considers that channel activation failed. This item provides the distribution of channel activation failures due to expiry of timer of responses from BTS in the intra BSC or inter BSC handover procedures of difference types of TCH to be activated.

Measurement point: In intra BSC or inter BSC procedure, BSC sends CHANNEL ACTIVATION to BTS to activate "Full rate TCH". This item is measured when BSC fails to receive the response from BTS after timer expiry (five seconds later).

Formula: None.

522


XCVIII. TCHH channel activation failures during handover (TIMEOUT)

Description: This item covers the cases of intra BSC handover (including intra cell handover and intra BSC inter cell handover) and inter BSC handover. On reception of HANDOVER REQUEST from MSC, BSC is engaged in incoming BSC handover procedure. Or after receiving Intercell Handover Request from its other channel or from other cell controlled by the same BSC (source cell), the cell controlled by this BSC (target cell) is enaged in intra BSC handover procedure. In both procedures, BSC first allocates TCH, and then sends CHANNEL ACTIVATION to BTS to activate this channell and starts the internal timer (five seconds). On reception of this message, BTS checks the status of the channel and responds. If BSC fails to receive the response from BTS after timer expiry, it considers that channel activation failed. This item provides the distribution of channel activation failures due to expiry of timer of responses from BTS in the intra BSC or inter BSC handover procedures of difference types of TCH to be activated.

Measurement point: In intra BSC or inter BSC procedure, BSC sends CHANNEL ACTIVATION to BTS to activate "Half rate TCH". This item is measured when BSC fails to receive the response from BTS after timer expiry (five seconds later).

Formula: None.

XCIX. TCHF channel activation failures during mode modification (NACK)

Description: On reception of ASSIGNMENT REQUEST from MSC, BSC analyze the CHANNEL TYPE in this message. If it finds that the properties of CHANNEL TYPE and the radio channel at the phase of immediate assignment satisfy any of the following conditions, it will implement Mode Modify procedure: 1. Channel rates are the same, but voice data indications are different; 2. Channel rates and voice data indications are the same, but voice coding algorithm or data transparent transmission modes are different.

Measurement point: If Mode Modify is implemeted during the procedure of assigning "Full rate TCH", then when MODE MODIFY is received by BTS, it will respond to BSC with MODE MODIFY NEGATIVE ACKNOWLEDGE, indicating that implementation of Mode Modify failed. This item is measured when BSC receives this message.

Formula: None.

C. TCHH channel activation failures during mode modification (NACK)

Description: On reception of ASSIGNMENT REQUEST from MSC, BSC analyze the CHANNEL TYPE in this message. If it finds that the properties of CHANNEL TYPE and the radio channel at the phase of immediate assignment satisfy any of the following conditions, it will implement Mode Modify

523


procedure: 1. Channel rates are the same, but voice data indications are different; 2. Channel rates and voice data indications are the same, but voice coding algorithm or data transparent transmission modes are different.

Measurement point: If Mode Modify is implemeted during the procedure of assigning "Half rate TCH", then when MODE MODIFY is received by BTS, it will respond to BSC with MODE MODIFY NEGATIVE ACKNOWLEDGE, indicating that implementation of Mode Modify failed. This item is measured when BSC receives this message.

Formula: None.

CI. TCHF channel activation failures during mode modification (TIMEOUT)


Measurement point: If Mode Modify is implemeted during the procedure of assigning "Full rate TCH", then when MODE MODIFY is received by BTS, it is suppposed to respond to BSC. This item is measured when BSC receives no response from BTS before the timer expires (five secondes).

Formula: None.

CII. TCHH channel activation failures during mode modification (TIMEOUT)


Measurement point: If Mode Modify is implemeted during the procedure of assigning "Half rate TCH", then when MODE MODIFY is received by BTS, it is suppposed to respond to BSC. This item is measured when BSC receives no response from BTS before the timer expires (five secondes).

Formula: None.

524


CIII. Attempted TCHF seizures meeting TCHF overflow

Description: This item is measured when attemping to allocate Full rate TCH, BSC channel allocation module finds that there is no such TCH available for allocation.

Measurement point: This item is measured when BSC requests for Full rate TCH only but the channel allocation failed. This item can also be measured when BSC requests for Full rate or Half rate TCH and Full rate preferrer, but the channel allocation failed or Half rate TCH is allocated.

Formula: None. Formula: None.

CIV. Attempted TCHH seizures meeting TCHH overflow

Description: This item is measured when attemping to allocate Half rate TCH, BSC channel allocation module finds that there is no such TCH available for allocation.

Measurement point: This item is measured when BSC requests for Half rate TCH only but the channel allocation failed. This item can also be measured when BSC requests for Full rate or Half rate TCH and Half rate preferrer, but the channel allocation failed or Full rate TCH is allocated.

Formula: None.

CV. TCHF call drop during very early assignment

Description: BSC sends CLEAR REQUEST to MSC to clear the current connection when any of the following cases take place: 1) In very early assignment, the connection between MS and BSC fails due to various causes after MS has access the allocated TCH. 2) In intra BSC or inter BSC handover procedures, the TCH handover on TCH fails due to various causes. For details, see TCH drop for very early assignment in BSC Measurement Function.

Measurement point: This item is measured when the channel type in the following procedures is "Full rate TCH" and the service type is signaling.

1) After MS seizes the channel, BTS sends ERROR INDICATION to BSC due to connection of radio link layer abnormal, and the cause of abnormal is timer T200 expired (N200+1) times (0x01), unsolicited DM response, multiple frame established state (0x05) and sequence error (0x07). This item is measured when BSC receives this message. See "GSM 0858".

2) After MS seizes the channel, BTS sends CONNECTION FAILURE INDICATION to BSC due to radio link failure or hardware failure (see GSM 0858 for details). This item is also measured when BSC receives this message.

525


3) In the procedure of incoming BSC signaling channel handover, the target cell receives HANDOVER DETECTION and HANDOVER COMPLETE. This item is also measured when errors detected in the messages during decoding.

4) This item is also measured in incoming BSC signaling channel handover procedure when the target cell waiting for HANDOVER COMPLETE times out.

5) This item is also measured in outgoing BSC signaling channel handover procedure, when the source cell waiting for message of CLEAR COMMAND times out (T8 expiry).

6) This item is measured in intra BSC signaling channel handover procedure, when the source cell or target cell waiting for message of HANDOVER COMPLETE times out.

7) This item is also measured when call drop occurs caused by forcibly channel seizure.

8) This item is also measured when the disconnection of RSL of the TRX where the channel is borne.

Formula: None.

CVI. TCHH call drop during very early assignment

Description: BSC sends CLEAR REQUEST to MSC to clear the current connection when any of the following cases take place: 1) In very early assignment, the connection between MS and BSC fails due to various causes after MS has access the allocated TCH. 2) In intra BSC or inter BSC handover procedures, the TCH handover on TCH fails due to various causes. For details, see TCH drop for very early assignment in BSC Measurement Function.

Measurement point: This item is measured when the channel type in the following procedures is "Half rate TCH" and the service type is signaling.



3) In the procedure of incoming BSC signaling channel handover, the target cell receives HANDOVER DETECTION and HANDOVER COMPLETE. This item is also measured when errors detected in the messages during decoding.

4) This item is also measured in incoming BSC signaling channel handover procedure, when the target cell waiting for HANDOVER COMPLETE times out.

526


5) This item is also measured in outgoing BSC signaling channel handover procedure, when the source cell waiting for message of CLEAR COMMAND times out (T8 expiry).

6) This item is measured in intra BSC signaling channel handover procedure, when the source cell or target cell waiting for message of HANDOVER COMPLETE times out.

7) This item is also measured when call drop occurs caused by forcibly channel seizure.

8) This item is also measured when the disconnection of RSL of the TRX where the channel is borne.

Formula: None.

CVII. TCHF call drop

Description: BSC sends CLEAR REQUEST to MSC to clear the current connection when any of the following cases take place: 1) Handover procedure fails due to various causes after MS accesses the allocated Full rate TCH; 2) After the conversation has already set up on Full rate TCH, call drop occurs due to various causes.

Measurement point: This item is measured in the following procedures, when the channel type is "Full rate TCH", and the service type is voice or data.



3) In the procedure of incoming BSC traffic channel handover, the target cell receives HANDOVER DETECTION and HANDOVER COMPLETE. This item is also measured when errors detected in the messages during decoding.

4) This item is also measured in incoming BSC traffic channel handover procedure, when the target cell waiting for HANDOVER COMPLETE times out.

5) This item is also measured in outgoing BSC traffic channel handover procedure, when the source cell waiting for message of handover complete and resource clearance message CLEAR COMMAND times out (T8 expiry).

6) This item is also measured in intra BSC traffic channel handover procedure, when the target cell waiting for HANDOVER COMPLETE times out.

527


7) This item is also measured in intra BSC traffic channel handover (non Direct Retry handover) procedure, when the source cell waiting for HANDOVER COMPLETE times out.

8) If both BSC and MSC support forcible seizure, then the calls of low priority may be robbed off the radio resources by the calls with high priority, thus call drops occur.

9) This item is also measured when RSL of the TRX of the channel disconnected. Formula: None.

CVIII. TCHH call drop

Description: BSC sends CLEAR REQUEST to MSC to clear the current connection when any of the following cases take place: 1) Handover procedure fails due to various causes after MS accesses the allocated Full rate TCH; 2) After the conversation has already set up on Full rate TCH, call drop occurs due to various causes.

Measurement point: This item is measured in the following procedures, when the channel type is "Half rate TCH", and the service type is voice or data.



3) In the procedure of incoming BSC traffic channel handover, the target cell receives HANDOVER DETECTION and HANDOVER COMPLETE. This item is also measured when errors detected in the messages during decoding.

4) This item is also measured in incoming BSC traffic channel handover procedure, when the target cell waiting for HANDOVER COMPLETE times out.

5) This item is also measured in outgoing BSC traffic channel handover procedure, when the source cell waiting for message of handover complete and resource clearance message CLEAR COMMAND times out (T8 expiry).

6) This item is also measured in intra BSC traffic channel handover procedure, when the target cell waiting for HANDOVER COMPLETE times out.

7) This item is also measured in intra BSC traffic channel handover (non Direct Retry handover) procedure, when the source cell waiting for HANDOVER COMPLETE times out.

528


8) If both BSC and MSC support forcible seizure, then the calls of low priority may be robbed off the radio resources by the calls with high priority, thus call drops occur.

9) This item is also measured when RSL of the TRX of the channel disconnected. Formula: None.

CIX. TCHF lost radio connections (connection failure)

Description: When Full rate TCH is seized and the service type is voice or data, if BTS detects any radio link failure or hardware failure, it will send CONNECTION FAILURE INDICATION to BSC indicating that call drop occurs on air interface due to radio link connection failure.

Measurement point: BSC receives CONNECTION FAILURE INDICATION on the Full rate TCH of the object cell. This item is measured when the cause value in this message is any one other than "0X20-equipment failure" and "0X22-terrestrial channel failure".

Formula: None.

CX. TCHH lost radio connections (connection failure)

Description: When Half rate TCH is seized and the service type is voice or data, if BTS detects any radio link failure or hardware failure, it will send CONNECTION FAILURE INDICATION to BSC indicating that call drop occurs on air interface due to radio link connection failure.

Measurement point: BSC receives CONNECTION FAILURE INDICATION on the Half rate TCH of the object cell. This item is measured when the cause value in this message is any one other than "0X20-equipment failure" and "0X22-terrestrial channel failure".

Formula: None.

CXI. TCHF lost radio connections (error indication)

Description: When Full rate TCH is seized, if BTS detects an abnormal case for a radio link layer connection, it will send ERROR INDICATION to BSC indicating that call drop on air interface occurs. See GSM 0858.

Measurement point: BSC receives ERROR INDICATION on the Full rate TCH of the object cell. This item is measured when the cause value in this message is "timer T200 expired (N200+1) times (0x01)", "unsolicited DM response", "multiple frame established state (0x05)" and "sequence error (0x07)".

Formula: None.

529


CXII. TCHH lost radio connections (error indication)

Description: When Half rate TCH is seized, if BTS detects an abnormal case for a radio link layer connection, it will send ERROR INDICATION to BSC indicating that call drop on air interface occurs. See GSM 0858.

Measurement point: BSC receives ERROR INDICATION on the Half rate TCH of the object cell. This item is measured when the cause value in this message is "timer T200 expired (N200+1) times (0x01)", "unsolicited DM response", "multiple frame established state (0x05)" and "sequence error (0x07)".

Formula: None.

CXIII. TCHF call drops due to terrestrial link failures (ABIS)

Description: When Full rate TCH is seized, if BTS detects an abnormal case for a radio link layer connection or hardware failure, it will send CONNECTION FAILURE INDICATION to BSC indicating connection failure on Abis interface. This item is measured when BSC detects RSL disconnection.

Measurement point: 1) This item is measured when BSC receives CONNECTION FAILURE

INDICATION (cause value: "0X20-equipment failure or 0X22-terrestrial channel failure") and failure occurs to Full rate TCH from BTS.

2) This item is also measured when Full rate TCH is seized, but link failure occurs to the RSL of its TRX.

Formula: None.

CXIV. TCHH call drops due to terrestrial link failures (ABIS)

Description: When Half rate TCH is seized, if BTS detects an abnormal case for a radio link layer connection or hardware failure, it will send CONNECTION FAILURE INDICATION to BSC indicating connection failure on Abis interface. This item is measured when BSC detects RSL disconnection

Measurement point: 1) This item is measured when BSC receives CONNECTION FAILURE

INDICATION (cause value: "0X20-equipment failure or 0X22-terrestrial channel failure") and failure occurs to Half rate TCH from BTS.

2) This item is also measured when Half rate TCH is seized, but link failure occurs to the RSL of its TRX.

Formula: None.

CXV. TCHF call drops due to A-interface failures

Description: After ESTABLISH INDICATION for the call established on full rate TCH, if connection error occurs on A-interface, the established connection path and related link resources will be released.

530


Measurement point: After ESTABLISH INDICATION for the call established on full rate TCH, A-interface connection errors occur due to A-interface trunk circuit fault persisting for 15 seconds, SCCP connection failure or MSC circuit re-selection. As a result the established connection path and related link resources will be released. This item is measured in this case.

Formula: None.

CXVI. TCHH call drops due to A-interface failures

Description: After ESTABLISH INDICATION for the call established on half rate TCH, if connection error occurs on A-interface, the established connection path and related link resources will be released.

Measurement point: After ESTABLISH INDICATION for the call established on half rate TCH, A-interface connection errors occur due to A-interface trunk circuit fault persisting for 15 seconds, SCCP connection failure or MSC circuit re-selection. As a result the established connection path and related link resources will be released. This item is measured in this case.

Formula: None.

CXVII. Sum of TCHF measurement reports during very early assignment procedure in the cell

Description: After seizing TCH, MS will send a MR every 480ms to the network. This item provides the number of original MRs from MSs when all Full rate TCHs of a cell (regardless of 900 or 1800) are used as signaling channel. It has no relation with the preproccessing switch status of MRs. This item is used to measure the traffic volume when Full rate TCH is used as signaling channel.

Measurement point: This item is measured when BSC receives MR of Full rate TCH from BTS, and the current Full rate TCH is used as signaling channel instead of traffic channel.

Formula: None.

CXVIII. Sum of TCHH measurement reports during very early assignment procedure in the cell

Description: After seizing TCH, MS will send a MR every 480ms to the network. This item provides the number of original MRs from MSs when all Half rate TCHs of a cell (regardless of 900 or 1800) are used as signaling channel. It has no relation with the preproccessing switch status of MRs. This item is used to measure the traffic volume when Half rate TCH is used as signaling channel.

531


Measurement point: This item is measured when BSC receives MR of Half rate TCH from BTS, and the current Half rate TCH is used as signaling channel instead of traffic channel.

Formula: None.

CXIX. Sum of TCHF measurement reports during very early assignment procedure in the 1800 cell

Description: After seizing TCH, MS will send a MR every 480ms to the network. This item provides the number of original MRs from MSs when all Full rate TCHs of a 1800 cell are used as signaling channel. It has no relation with the preproccessing switch status of MRs. This item is used to measure the traffic volume when Full rate TCH is used as signaling channel.

Measurement point: This item is measured when BSC receives MR of Full rate TCH from BTS, and the current Full rate TCH is used as signaling channel instead of traffic channel.

Formula: None.

CXX. Sum of TCHH measurement reports during very early assignment procedure in the 1800 cell

Description: After seizing TCH, MS will send a MR every 480ms to the network. This item provides the number of original MRs from MSs when all Half rate TCHs of a 1800 cell are used as signaling channel. It has no relation with the preproccessing switch status of MRs. This item is used to measure the traffic volume when Half rate TCH is used as signaling channel.

Measurement point: This item is measured when BSC receives MR of Half rate TCH from BTS, and the current Half rate TCH is used as signaling channel instead of traffic channel.

Formula: None.

CXXI. Sum of TCHF measurement reports in the cell (excluding very early assignment)

Description: After seizing TCH, MS will send a MR every 480ms to the network. This item provides the number of original MRs from MSs when all Full rate TCHs of a cell (regardless of 900 or 1800) are used as traffic channel. It has no relation with the preproccessing switch status of MRs. This item is used to measure the traffic volume when Full rate TCH is used as traffic channel.

Measurement point: This item is measured when BSC receives MR of Full rate TCH from BTS, and the current Full rate TCH is used as traffic channel instead of signaling channel.

Formula: None.

532


CXXII. Sum of TCHH measurement reports in the cell (excluding very early assignment)

Description: After seizing TCH, MS will send a MR every 480ms to the network. This item provides the number of original MRs from MSs when all Half rate TCHs of a cell (regardless of 900 or 1800) are used as traffic channel. It has no relation with the preproccessing switch status of MRs. This item is used to measure the traffic volume when Half rate TCH is used as traffic channel.

Measurement point: This item is measured when BSC receives MR of Half rate TCH from BTS, and the current Half rate TCH is used as traffic channel instead of signaling channel.

Formula: None.

CXXIII. Sum of TCHF measurement reports in 1800 cell (excluding very early assignment)

Description: After seizing TCH, MS will send a MR every 480ms to the network. This item provides the number of original MRs from MSs when all Full rate TCHs of a 1800 cell are used as traffic channel. It has no relation with the preproccessing switch status of MRs. This item is used to measure the traffic volume when Full rate TCH is used as traffic channel.

Measurement point: This item is measured when BSC receives MR of Full rate TCH from BTS, and the current Full rate TCH is used as traffic channel instead of signaling channel.

Formula: None.

CXXIV. Sum of TCHH measurement reports in 1800 cell (excluding very early assignment)

Description: After seizing TCH, MS will send a MR every 480ms to the network. This item provides the number of original MRs from MSs when all Half rate TCHs of a 1800 cell are used as traffic channel. It has no relation with the preproccessing switch status of MRs. This item is used to measure the traffic volume when Half rate TCH is used as traffic channel.

Measurement point: This item is measured when BSC receives MR of Half rate TCH from BTS, and the current Half rate TCH is used as traffic channel instead of signaling channel.

Formula: None.

CXXV. Initially configured TCHF of 900 cell

Description: This item provides the number of the Full rate TCHs of a 900 cell configured in data configuration table at the start time of the measurement

533


period. It includes the Full rate TCHs dynamically converted as SDCCHs or Half rate TCHs

Measurement point: number of the Full rate TCHs of a 900 cell configured in data configuration table at the start time of the measurement period.

Formula: None.

CXXVI. Initially configured TCHH of 900 cell

Description: This item provides the number of the Full rate TCHs of a 900 cell configured in data configuration table at the start time of the measurement period. It includes the Full rate TCHs dynamically converted as SDCCHs but excludes the Full rate TCHs dynamically coverted to Half rate TCHs

Measurement point: number of the Half rate TCHs of a 900 cell configured in data configuration table at the start time of the measurement period.

Formula: None.

CXXVII. Initially configured TCHF of 1800 cell

Description: This item provides the number of the Full rate TCHs of a 1800 cell configured in data configuration table at the start time of the measurement period. It includes the Full rate TCHs dynamically converted to SDCCHs or Half rate TCHs

Measurement point: number of the Full rate TCHs of a 1800 cell configured in data configuration table at the start time of the measurement period.

Formula: None.

CXXVIII. Initially configured TCHH of 1800 cell

Description: This item provides the number of the Full rate TCHs of a 1800 cell configured in data configuration table at the start time of the measurement period. It includes the Half rate TCHs dynamically converted to SDCCHs but excludes the Half rate TCHs dynamically coverted from Full rate TCHs

Measurement point: number of the Half rate TCHs of a 1800 cell configured in data configuration table at the start time of the measurement period.

Formula: None.

CXXIX. Configured TCHF of 900 cell

Description: This item provides the number of Full rate TCHs currently configured in a 900 cell on real time basis. It does not include the Full rate TCHs dynamically converted to SDCCHs or Half rate TCHs, but includes the Full rate TCHs converted from PDCH. It is the average value of the sum from the sampling points within the measurement period.

534


Measurement point: System gets the number of configured Full rate TCHs once per five seconds. The average number of the configured Full rate TCHs is obtained by dividing the accumulated number with the times of sampling.

Formula: None.

CXXX. Configured TCHH of 900 cell

Description: This item provides the number of Half rate TCHs currently configured in a 900 cell on real time basis. It does not include the Half rate TCHs dynamically converted to SDCCHs, but includes the Half rate TCHs converted from PDCHs and Full rate TCHs. It is the average value of the sum from the sampling points within the measurement period.

Measurement point: System gets the number of configured Half rate TCHs once per five seconds. The average number of the configured Half rate TCHs is obtained by dividing the accumulated number with the times of sampling.

Formula: None.

CXXXI. Configured TCHF of 1800 cell

Description: This item provides the number of Full rate TCHs currently configured in a 1800 cell on real time basis. It does not include the Full rate TCHs dynamically converted to SDCCHs or Half rate TCHs, but includes the Full rate TCHs converted from PDCH. It is the average value of the sum from the sampling points within the measurement period.

Measurement point: System gets the number of configured Full rate TCHs once per five seconds. The average number of the configured Full rate TCHs is obtained by dividing the accumulated number with the times of sampling.

Formula: None.

CXXXII. Configured TCHH of 1800 cell

Description: This item provides the number of Half rate TCHs currently configured in a 1800 cell on real time basis. It does not include the Half rate TCHs dynamically converted to SDCCHs, but includes the Half rate TCHs converted from PDCHs and Full rate TCHs. It is the average value of the sum from the sampling points within the measurement period.

Measurement point: System gets the number of configured Half rate TCHs once per five seconds. The average number of the configured Half rate TCHs is obtained by dividing the accumulated number with the times of sampling.

Formula: None.

CXXXIII. Available TCHF

Description: This item provides the number of available (idle or busy) Full rate TCHs of a cell. It does not include the Full rate TCHs dynamically converted to

535


SDCCH and Half rate TCH, but includes those dynamically coverted from PDCH. It is an average value of total number of all sample points within the measurement period.

Measurement point: System gets the number of available Full rate TCHs once per five seconds. At the end of the measurement period the accumulated number is divided with the times of sampling to get the average number of available Full rate TCHs.

Formula: None.

CXXXIV. Available TCHH

Description: This item provides the number of available (idle or busy) Half rate TCHs of a cell. It does not include the Half rate TCHs dynamically converted to SDCCHs, but includes Half rate TCHs dynamically coverted from dynamic PDCHs and Full rate TCHs. It is an average value of total number of all sample points within the measurement period.

Measurement point: System gets the number of available Half rate TCHs once per five seconds. At the end of the measurement period the accumulated number is divided with the times of sampling to get the average number of available Half rate TCHs.

Formula: None.

CXXXV. Average num. of busy TCHF

Description: This item provides the average number of seized Full rate TCHs of a cell within the measurement period. It is an average value of total number of all sample points within the measurement period. This item indicates the average situation of Full rate TCH seizure of a cell within the measurement period.

Measurement point: System gets the number of seized Full rate TCHs once per five seconds. At the end of the measurement period the accumulated number is divided with the times of sampling to get the average number of available Full rate TCHs.

Formula: None.

CXXXVI. Average num. of busy TCHH

Description: This item provides the average number of seized Half rate TCHs of a cell within the measurement period. It is an average value of total number of all sample points within the measurement period. This item indicates the average situation of Half rate TCH seizure of a cell within the measurement period.

Measurement point: System gets the number of seized Half rate TCHs once per five seconds. At the end of the measurement period the accumulated

536


number is divided with the times of sampling to get the average number of available Half rate TCHs.

Formula: None.

CXXXVII. Maximum num. of busy TCHF

Description: This item provides the maximum number of seized Full rate TCH. It is the peak of number of seized Full rate TCH. It indicates the maximum Full rate TCH seizure of a cell within the measurement period from the angle of seized channel number.

Measurement point: System gets the number of seized Full rate TCHs once per five seconds. System picks up the maximum value at the end of the measurement period.

Formula: None.

CXXXVIII. Maximum num. of busy TCHH

Description: This item provides the maximum number of seized Half rate TCH. It is the peak of number of seized Half rate TCH. It indicates the maximum Half rate TCH seizure of a cell within the measurement period from the angle of seized channel number.

Measurement point: System gets the number of seized Half rate TCHs once per five seconds. System picks up the maximum value at the end of the measurement period.

Formula: None.

CXXXIX. All TCHF busy time (second)

Description: This item provides the duration in which a cell has no Full rate TCH for allocation. This item indicates the situation of no Full rate TCH for allocation for TCH resources seized or unavailable within the measurement period from the angle of duration.

Meausrement point: Accumulated duration in which there are no Full rate TCHs for allocation in the cell.

Formula: None.

CXL. All TCHH busy time (second)

Description: This item provides the duration in which a cell has no Half rate TCH for allocation. This item indicates the situation of no Half rate TCH for allocation for TCH resources seized or unavailable within the measurement period from the angle of duration.

Meausrement point: Accumulated duration in which there are no Half rate TCHs for allocation in the cell.

Formula: None.

537


CXLI. Average TCHF busy time(second)

Description: This item provides the average duration in which the Full rate TCHs of a cell are seized, i.e., the average duration of each Full rate TCH in busy status. This item indicates the average situation of Full rate TCH seizure within the measurement period.

Measurement point: Accumulated duration in which the Full rate TCHs in a cell are busy.

Formula: Accumulated duration in which the Full rate TCHs in a cell are busy/(number of configured Full rate TCH in 900 cells + number of configured Full rate TCH in 1800 cells)

CXLII. Average TCHH busy time(second)

Description: This item provides the average duration in which the Half rate TCHs of a cell are seized, i.e., the average duration of each Half rate TCH in busy status. This item indicates the average situation of Half rate TCH seizure within the measurement period.

Measurement point: Accumulated duration in which the Half rate TCHs in a cell are busy.

Formula: Accumulated duration in which the Half rate TCHs in a cell are busy/(number of configured Half rate TCH in 900 cells + number of configured Half rate TCH in 1800 cells)

CXLIII. Average num. of idle TCHF in Interf. band 1

Description: Interference band is a range of uplink interference level on TCH. This information is contained in RF RESOURCE INDICATION reported to BSC by BTS via idle TCH. There are six interference bands. The level range can be defined using data configuration console. Usually the definitions are:






Interference band 5 -85~-47dBm High rank indicates stronger interference. Normally, when the interference on

idle TCH is as strong as band 4 or 5, it is considered that interference exists. This item provides the average a cell's number of idle Full rate TCHs on which the interference belongs to band 1.

Measurement point: System gets the number of idle Full rate TCHs on which the interference belongs to band 1 once per five seconds, and gets the average number at the end of the measurement period by dividing the total number with the times of sampling.

538


Formula: None.

CXLIV. Average num. of idle TCHF in Interf. band 2










Formula: None.

CXLV. Average num. of idle TCHF in Interf. band 3









Measurement point: System gets the number of idle Full rate TCHs on which the interference belongs to band 3 once per five seconds, and gets the

539


average number at the end of the measurement period by dividing the total number with the times of sampling.

Formula: None.

CXLVI. Average num. of idle TCHF in Interf. band 4










Formula: None.

CXLVII. Average num. of idle TCHF in Interf. band 5









540



Formula: None.

CXLVIII. Average num. of idle TCHH in Interf. band 1








idle TCH is as strong as band 4 or 5, it is considered that interference exists. This item provides the average a cell's number of idle Half rate TCHs on which the interference belongs to band 1.

Measurement point: System gets the number of idle Half rate TCHs on which the interference belongs to band 1 once per five seconds, and gets the average number at the end of the measurement period by dividing the total number with the times of sampling.

Formula: None.

CXLIX. Average num. of idle TCHH in Interf. band 2








idle TCH is as strong as band 4 or 5, it is considered that interference exists.

541


This item provides the average a cell's number of idle Half rate TCHs on which the interference belongs to band 2.


Formula: None.

CL. Average num. of idle TCHH in Interf. band 3










Formula: None.

CLI. Average num. of idle TCHH in Interf. band 4








542


High rank indicates stronger interference. Normally, when the interference on idle TCH is as strong as band 4 or 5, it is considered that interference exists. This item provides the average a cell's number of idle Half rate TCHs on which the interference belongs to band 4.


Formula: None.

CLII. Average num. of idle TCHH in Interf. band 5










Formula: None.

CLIII. Average num. of blocked TCHF

Description: This item provides a cell's average number of blocked Full rate TCHs within the measurement period. It is the average value of number of blocked Full rate TCH from all sampling points within the measurement period. The block status can be caused by O&M or RSL disconnection. This item provides the situation of a cell's unavailable Full rate TCHs within the measurement period.

Measurement point: System gets the number of blocked Full rate TCHs, and gets the average number at the end of the measurement period by dividing the total number with the times of sampling.

543


Formula: None.

CLIV. Average num. of blocked TCHH

Description: This item provides a cell's average number of blocked Half rate TCHs within the measurement period. It is the average value of number of blocked Half rate TCH from all sampling points within the measurement period. The block status can be caused by O&M or RSL disconnection. This item provides the situation of a cell's unavailable Half rate TCHs within the measurement period.

Measurement point: System gets the number of blocked Half rate TCHs, and gets the average number at the end of the measurement period by dividing the total number with the times of sampling.

Formula: None.

CLV. Average num. of idle TCHF

Description: This item provides a cell's average number of idle Full rate TCHs within the measurement period. It is the average value of number of idle Full rate TCH from all sampling points within the measurement period. The idle channel refers to normal channel not seized by MS. This item provides the situation of a cell's Full rate TCH seizure within the measurement period.

Measurement point: System gets the number of idle Full rate TCHs, and gets the average number at the end of the measurement period by dividing the total number with the times of sampling.

Formula: None.

CLVI. Average num. of idle TCHH

Description: This item provides a cell's average number of idle Half rate TCHs within the measurement period. It is the average value of number of idle Half rate TCH from all sampling points within the measurement period. The idle channel refers to normal channel not seized by MS. This item provides the situation of a cell's Half rate TCH seizure within the measurement period.

Measurement point: System gets the number of idle Half rate TCHs, and gets the average number at the end of the measurement period by dividing the total number with the times of sampling.

Formula: None.

CLVII. Average num. of OOS TCHF

Description: This item provides a cell's average number of Full rate TCHs in OOS status within the measurement period. It is the average value of number of Full rate TCH in OOS status from all sampling points within the measurement period. The OOS status refers to unavailable status caused by

544


channel blocking from O&M, cell status changed from installed to not installed or BTS/TRX failure. This item provides the situation of a cell's unavailable Full rate TCH within the measurement period.

Measurement point: System gets the number of Full rate TCHs in OOS status, and gets the average number at the end of the measurement period by dividing the total number with the times of sampling.

Formula: None.

CLVIII. Average num. of OOS TCHH

Description: This item provides a cell's average number of Half rate TCHs in OOS status within the measurement period. It is the average value of number of Half rate TCH in OOS status from all sampling points within the measurement period. The channel in OOS status refers to refers to unavailable status caused by channel blocking from O&M, cell status changed from installed to not installed or BTS/TRX failure. This item provides the situation of a cell's unavailable Half rate TCH within the measurement period.

Measurement point: System gets the number of Half rate TCHs in OOS status, and gets the average number at the end of the measurement period by dividing the total number with the times of sampling.

Formula: None.

CLIX. Attempted transform from TCHF to TCHH

Description: The initial configuration of Full rate and Half rate TCH may not be able to satisfy actual needs, so BSC supports transformation from Full rate TCH to Half rate TCH under certain conditions. The rule of transformation: 1) The TCH channel initially configured as Full rate TCH and currently used as Full rate TCH can be transformed to Half rate TCH under certain conditions, and the corresponding Half rate TCH is reversed to Full rate TCH; 2) The initial Half rate TCH can be used as Half rate TCH only, and cannot be transformed; 3) The initial dynamic PDCH cannot be transformed to Half rate TCH. The conditions of transformation: before each channel allocation, if system allows dynamic data transformation (i.e. in [Channel\Radio channel management control table], the field [TCH rate transformation flag] is set as "Yes"), it will first check whether the current traffic volume (number of channels currently seized/total number of available channels of the cell) exceeds the threshold of TCH rate transformation on large traffic volume, and whether the total number of Full rate TCHs of the cell is larger than 1 so as to decide whether to implement transformation from Full rate TCH to Half rate TCH. If it is necessary to implement transformation and the cell has idle Full rate TCH, system first issues the transformation command, and then initiates channel allocation procedure. Otherwise, system will initiate channel allocation

545


procedure directly. The procedure of transformation: 1) A Full rate TCH available for transformation is selected. For an IUO cell, the idle channel on the underlaid subcell is preferred. If there is no channel available for transformation, then this transformation fails. 2) The channel type is transformed. In this step, the channel is blocked, and then the channel resource is updated, and the channel configuration is sent to the BTS. After BTS has transformed the channel type, it will send a status change report to BSC. On reception of this report, BSC unblocks the channel. The channel transformation is successfully completed after this step, and a Full rate TCH is transformed to two Half rate TCHs.

Measurement point: This item is measured when system initiates transformation form Full rate TCH to Half rate TCH.

Formula: None.

CLX. Successful transform from TCHF to TCHH

Description: The initial configuration of Full rate and Half rate TCH may not be able to satisfy actual needs, so BSC supports transformation from Full rate TCH to Half rate TCH under certain conditions. The rule of transformation: 1) The TCH channel initially configured as Full rate TCH and currently used as Full rate TCH can be transformed to Half rate TCH under certain conditions, and the corresponding Half rate TCH is reversed to Full rate TCH; 2) The initial Half rate TCH can be used as Half rate TCH only, and cannot be transformed; 3) The initial dynamic PDCH cannot be transformed to Half rate TCH. The conditions of transformation: before each channel allocation, if system allows dynamic data transformation (i.e. in [Channel\Radio channel management control table], the field [TCH rate transformation flag] is set as "Yes"), it will first check whether the current traffic volume (number of channels currently seized/total number of available channels of the cell) exceeds the threshold of TCH rate transformation on large traffic volume, and whether the total number of Full rate TCHs of the cell is larger than 1 so as to decide whether to implement transformation from Full rate TCH to Half rate TCH. If it is necessary to implement transformation and the cell has idle Full rate TCH, system first issues the transformation command, and then initiates channel allocation procedure. Otherwise, system will initiate channel allocation procedure directly. The procedure of transformation: 1) A Full rate TCH available for transformation is selected. For an IUO cell, the idle channel on the underlaid subcell is preferred. If there is no channel available for transformation, then this transformation fails. 2) The channel type is transformed. In this step, the channel is blocked, and then the channel resource is updated, and the channel configuration is sent to the BTS. After BTS has transformed the channel type, it will send a status change report to

546


BSC. On reception of this report, BSC unblocks the channel. The channel transformation is successfully completed after this step, and a Full rate TCH is transformed to two Half rate TCHs.

Measurement point: This item is measured when BSC unblocks the channel on reception of status change report from BTS after initiating transformation from Full rate TCH to Half rate TCH.

Formula: None.

CLXI. Attempted reverse from TCHH to TCHF

Description: When a Full rate TCH is transformed to two Half rate TCHs, BSC will start a timer (3 seconds) to implement the following operations once per three seconds: when the current traffic volume (number of channels currently seized/total number of available channels of the cell) is smaller that the threshold of TCH rate transformation on large traffic volume, system will tranverse the channel resource table. For ordinary cells, the two Half rate TCHs transformed from Full rate TCH are reversed to Full rate TCH; for IUO cells, the two Half rate TCHs on non underlaid TRX are reversed to Full rate TCH so as to ensure the traffic on the underlaid subcell. If there is conversation on Half rate TCH, system will initiate handover to hand it over to other TCH. If this handover fails, this reverse will be given up. In addition, If the field [TCH rate transformation flag] in [Channel\Radio channel management control table] is changed from "Yes" to "No", then BSC will immediately reverse the Half rate TCHs transformed from Full rate TCHs to Full rate TCHs. If there are calls on these channels, they will be dropped. The procedure of channel reverse: the channel is blocked, and then the channel resource is updated, and the channel configuration is sent to the BTS. After BTS has transformed the channel type, it will send a status change report to BSC. On reception of this report, BSC unblocks the channel. The channel reverse is successfully completed after this step, and two Half rate TCHs is reversed to a Full rate TCH.

Measurement point: This item is measured when system initiates channel reverse from Full rate TCH to Half rate TCH.

Formula: None.

CLXII. Successful reverse from TCHH to TCHF

Description: When a Full rate TCH is transformed to two Half rate TCHs, BSC will start a timer (3 seconds) to implement the following operations once per three seconds: when the current traffic volume (number of channels currently seized/total number of available channels of the cell) is smaller that the threshold of TCH rate transformation on large traffic volume, system will tranverse the channel resource table. For ordinary cells, the two Half rate

547


TCHs transformed from the first Full rate TCH are reversed to Full rate TCH; for IUO cells, the two Half rate TCHs on non underlaid TRX are reversed to Full rate TCH so as to ensure the traffic on the underlaid subcell. If there is conversation on Half rate TCH, system will initiate handover to hand it over to other TCH. If this handover fails, this reverse will be given up. In addition, If the field [TCH rate transformation flag] in [Channel\Radio channel management control table] is changed from "Yes" to "No", then BSC will immediately reverse the Half rate TCHs transformed from Full rate TCHs to Full rate TCHs. If there are calls on these channels, they will be dropped. The procedure of channel reverse: the channel is blocked, and then the channel resource is updated, and the channel configuration is sent to the BTS. After BTS has transformed the channel type, it will send a status change report to BSC. On reception of this report, BSC unblocks the channel. The channel reverse is successfully completed after this step, and two Half rate TCHs is reversed to a Full rate TCH.

Measurement point: This item is measured when system receives status change report from BTS after initiating channel reverse from Half rate TCH to Full rate TCH.

Formula: None.

CLXIII. TCHF usability (%)

Description: This item provides the percentage of number of available full TCHs among the total number of Full rate TCHs. See Available TCHF , Configured TCHF of 900 cell and Configured TCHF of 1800 cell .

Measurement point: None. Formula: Number of available Full rate TCHs/ (number of 900 cell Full rate

TCHs + 1800 cell Full rate TCHs)

CLXIV. TCHH usability (%)

Description: This item provides the percentage of number of available half TCHs among the total number of Half rate TCHs. See Available TCHH , Configured TCHH of 900 cell and Configured TCHH of 1800 cell .

Measurement point: None. Formula: Number of available Half rate TCHs/(number of 900 cell Half rate

TCHs + 1800 cell Half rate TCHs)

CLXV. TCHF traffic volume (excluding very early assignment) (ERL)

Description: This item provides the traffic volume on Full rate TCHs (excluding those seized in very early assignment procedure), i.e. the ratio of the duration of MS seizing Full rate TCH to measurement period. The duration of MS seizing Full rate TCH is obtained by multiplying the number of MRs reported by

548


MS on Full rate TCH with 0.48 seconds (period for reporting MRs). See Sum ofTCHF measurement reports in the cell (excluding very early assignment) .

Measurement point: None. Formula: Total number of MRs on Full rate TCH of the cell (excluding very

early assignment) 0.48/measurement period (second)

CLXVI. TCHH traffic volume (excluding very early assignment) (ERL)

Description: This item provides the traffic volume on Half rate TCHs (excluding those seized in very early assignment procedure), i.e. the ratio of the duration of MS seizing Half rate TCH to measurement period. The duration of MS seizing Half rate TCH is obtained by multiplying the number of MRs reported by MS on Half rate TCH with 0.48 seconds (period for reporting MRs). See Sum of TCHH measurement reports in the cell (excluding very earlyassignment) .

Measurement point: None. Formula: Total number of MRs on Half rate TCH of the cell (excluding very

early assignment) 0.48/measurement period (second)

CLXVII. TCHF traffic volume of 1800 cell (excluding very early assignment) (ERL)

Description: This item provides the traffic volume on Full rate TCHs (excluding those seized in very early assignment procedure) of 1800 cell, i.e. the ratio of the duration of MS seizing Full rate TCH to measurement period in a 1800 cell. The duration of MS seizing Full rate TCH is obtained by multiplying the number of MRs reported by MS on Full rate TCH with 0.48 seconds (period for reporting MRs). See Sum of TCHF measurement reports in 1800 cell(excluding very early assignment) .

Measurement point: None. Formula: Total number of MRs on Full rate TCH of 1800 cell (excluding very

early assignment) 0.48/meansurement period (second)

CLXVIII. TCHH traffic volume of 1800 cell (excluding very early assignment) (ERL)

Description: This item provides the traffic volume on Half rate TCHs (excluding those seized in very early assignment procedure) of 1800 cell, i.e. the ratio of the duration of MS seizing Half rate TCH to measurement period in a 1800 cell. The duration of MS seizing Half rate TCH is obtained by multiplying the number of MRs reported by MS on Half rate TCH with 0.48 seconds (period for reporting MRs). See Sum of TCHH measurement reports in 1800 cell(excluding very early assignment) .

Measurement point: None.

549


Formula: Total number of MRs on Half rate TCH of 1800 cell (excluding very early assignment) 0.48/measurement period (second)

CLXIX. Traffic density at average TCHF call drop

Description: This item provides the average duration between two consecutive call drops on Full rate TCHs when they are used for voice and data transmission. The duration of MS seizing Full rate TCH is obtained by multiplying the number of MRs reported by MS on Full rate TCH with 0.48 seconds (period for reporting MRs). See Sum of TCHF measurement reportsin the cell (excluding very early assignment) .

Measurement point: None. Formula: Total number of MRs on Full rate TCH (excluding very early

assignment) 0.48 (second)/times of call drop on Full rate TCHs

CLXX. Traffic density at average TCHH call drop

Description: This item provides the average duration between two consecutive call drops on Half rate TCHs when they are used for voice and data transmission. The duration of MS seizing Half rate TCH is obtained by multiplying the number of MRs reported by MS on Half rate TCH with 0.48 seconds (period for reporting MRs). See Sum of TCHH measurement reportsin the cell (excluding very early assignment) .

Measurement point: None. Formula: Total number of MRs on Half rate TCH (excluding very early

assignment) 0.48 (second)/times of call drop on Half rate TCHs

CLXXI. TCHF RF lost rate (%)

Description: This item provides the percentage of times of call drop caused by radio link disconnection after MS seizing Full rate TCH due to air interface problems among times of Full rate TCH successfully seized. See TCHF lostradio connections (connection failure) , TCHF lost radio connections (errorindication) , Successful TCHF seizures during assignment (excluding directedretry) , Successful TCHF seizures during intracell handover , SuccessfulTCHF seizures during intraBSC incoming cell handover and SuccessfulTCHF seizures during interBSC incoming cell handover .

Meausrement point: None. Formula: (Times of radio link disconnection when Full rate TCHs are seized

(connection failure) + times of radio link disconnection when Full rate TCHs are seized (error indication))/(times of successful Full rate TCH assignment + times of successful intra BSC incoming cell handover to Full rate TCH + times of successful intra cell handover to Full rate TCH + times of successful inter BSC incoming cell handover to Full rate TCH)

550


CLXXII. TCHH RF lost rate (%)

Description: This item provides the percentage of times of call drop caused by radio link disconnection after MS seizing Half rate TCH due to air interface problems among times of Half rate TCH successfully seized. See TCHH lostradio connections (connection failure) , TCHH lost radio connections (errorindication) , Successful TCHH seizures during assignment (excluding directedretry) , Successful TCHH seizures during intracell handover , SuccessfulTCHH seizures during intraBSC incoming cell handover and SuccessfulTCHH seizures during interBSC incoming cell handover .

Measurement point: None. Formula: (Times of radio link disconnection when Half rate TCHs are seized

(connection failure) + times of radio link disconnection when Half rate TCHs are seized (error indication))/(times of successful Half rate TCH assignment + times of successful intra BSC incoming cell handover to Half rate TCH + times of successful intra cell handover to Half rate TCH + times of successful inter BSC incoming cell handover to Half rate TCH)

CLXXIII. TCHF call drop rate (%)

Description: This item provides the percentage of number of call drop on Full rate TCH among total times of Full rate TCH seizures. See TCHF call drop , Successful TCHF seizures during assignment (excluding directed retry) , Successful TCHF seizures during intracell handover , Successful TCHFseizures during intraBSC incoming cell handover and Successful TCHFseizures during interBSC incoming cell handover .

Measurement point: None. Formula: Times of call drop on Full rate TCH/(times of successful Full rate

TCH assignment + times of successful intra BSC incoming cell handover to Full rate TCH + times of successful intra cell handover to Full rate TCH + times of successful inter BSC incoming cell handover to Full rate TCH)

CLXXIV. TCHH call drop rate (%)

Description: This item provides the percentage of number of call drop on Half rate TCH among total times of Half rate TCH seizures. See TCHH call drop , Successful TCHH seizures during assignment (excluding directed retry) , Successful TCHH seizures during intracell handover , Successful TCHHseizures during intraBSC incoming cell handover and Successful TCHHseizures during interBSC incoming cell handover .

Measurement point: None. Formula: Times of call drop on Half rate TCH/(times of successful Half rate

TCH assignment + times of successful intra BSC incoming cell handover to

551


Half rate TCH + times of successful intra cell handover to Half rate TCH + times of successful inter BSC incoming cell handover to Half rate TCH)

3.13 Cell Measurement Function (3)

3.13.1 General

The traffic statistic items of “Cell Measurement Function (3)" are related to non-triggered handovers due to target cell congestion and unsuccessful outgoing interBSC inter cell handovers.

“Non-triggered handovers due to target cell congestion”:

If all the target cells of a handover are in the same BM module as the source cell, and they are all congested, then this handover will not be triggered by the source cell, and the measurements of these items are triggered based on different handover reasons. If the target cells do not belong to the same BM module as the source cell, or the target cells belong to other BSC, then the handover to those cells will be triggered even if the target cells are congested.

“Unsuccessful outgoing interBSC inter cell handovers” is classified into four categories:

Unsuccessful outgoing interBSC inter cell handovers due to BSC abnormal (5 causes);

Unsuccessful handovers with successful reversions, and MS sends a HANDOVER FAILURE message containing failure cause to source BSC (17 causes);

Unsuccessful handovers, and source BSC receives a HANDOVER REQUIRED REJECT message containing failure cause from MSC (14 causes);

Unsuccessful handover, and source BSC receives a CLEAR COMMAND message containing failure cause from MSC (8 causes) ;


Table 3-13 Statistic items in Cell Measurement Function (3)

No. Item name

1Non-triggered handovers with target cell congestion (uplink quality)

2Non-triggered handovers with target cell congestion (downlink quality)

3Non-triggered handovers with target cell congestion (uplink strength)

4Non-triggered handovers with target cell congestion (downlink strength)

5Non-triggered handovers with target cell congestion (timing advance)

552


6Non-triggered handovers with target cell congestion (better cell)

7Non-triggered handovers with target cell congestion (traffic load)

8Non-triggered handovers with target cell congestion (rapid level drop)

9Non-triggered handovers with target cell congestion (response to MSC invocation)

10Non-triggered handovers with target cell congestion (O&M intervention)

11Non-triggered handovers with target cell congestion (directed retry)

12Non-triggered handovers with target cell congestion (minimum timing advance)

13Non-triggered handovers with target cell congestion (other causes)

14Unsuccessful outgoing interBSC inter cell handovers (connection failure)

15Unsuccessful outgoing interBSC inter cell handovers (error indication)

16Unsuccessful outgoing interBSC inter cell handovers (A-interface failure)

17Unsuccessful outgoing interBSC inter cell handovers (timer T7 expired)

18Unsuccessful outgoing interBSC inter cell handovers (timer T8 expired)

19Unsuccessful outgoing interBSC inter cell handovers (MS reported: Abnormal release,unspecified)

22Unsuccessful outgoing interBSC inter cell handovers (MS reported: Abnormal release,channel unacceptable)

21Unsuccessful outgoing interBSC inter cell handovers (MS reported: Abnormal release,timer expired)

22Unsuccessful outgoing interBSC inter cell handovers (MS reported: Abnormal release,no activity on the radio path)

23Unsuccessful outgoing interBSC inter cell handovers (MS reported: Preemptive release)

24Unsuccessful outgoing interBSC inter cell handovers (MS reported: Handover impossible, timing advance out of range)

25Unsuccessful outgoing interBSC inter cell handovers (MS reported: Channel mode unavailable)

26Unsuccessful outgoing interBSC inter cell handovers (MS reported: Frequency not implemented)

27Unsuccessful outgoing interBSC inter cell handovers (MS reported: Call already cleared)

28Unsuccessful outgoing interBSC inter cell handovers (MS reported: Semantically incorrect message)

29Unsuccessful outgoing interBSC inter cell handovers (MS reported: Invalid mandatory information)

30Unsuccessful outgoing interBSC inter cell handovers (MS reported: Message type non-existent or not implemented)

31Unsuccessful outgoing interBSC inter cell handovers (MS reported: Message type not compatible with protocol state)

32Unsuccessful outgoing interBSC inter cell handovers (MS reported: Conditional IE error)

33Unsuccessful outgoing interBSC inter cell handovers (MS reported :No cell allocation available)

34Unsuccessful outgoing interBSC inter cell handovers (MS reported: Protocol error unspecified)

35Unsuccessful outgoing interBSC inter cell handovers (MS reported: Other)

36Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause O & M intervention )

37Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Equipment failure)

38Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause No radio resource available)

39Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Requested terrestrial resource unavailable)

40Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause BSS not equipped)

41Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Invalid Cell)

42Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Requested transcoding/rate adaption unavailable)

43Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Circuit pool mismatch)

553


44Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Requested Speech version unavailable)

45Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Ciphering algorithm not supported)

46Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Terrestrial circuit already allocated)

47Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Invalid message)

48Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Protocol Error between BSS and MSC)

49Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Other)

50Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause Radio interface message failure)

51Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause Radio interface failure)

52Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause O & M intervention)

53Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause Equipment failure)

54Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause Preemption)

55Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause Invalid message)

56Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause Protocol Error between BSS and MSC)

57Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause Other)


I. Non-triggered handovers with target cell congestion (uplink quality)

Description: During the procedure of inter cell handover within a BM of BSC, if all the target cells of the handover are in the same BM module as the source cell, and they are all congested, then this handover would not be triggered by the source cell, and the measurements of these items are triggered based on different handover reasons. If the target cells do not belong to the same BM module as the source cell, or the target cells belong to other BSC, then the handover to those cells will be triggered even if the target cells are congested.

Measurement point: During the procedure of inter cell handover within a BM of BSC, after system receiving the handover request message from LAPD, if all the target cells are in the same BM module as the source cell and they are all congested, then this handover would not be triggered by the source cell. This item is measured when the handover reason is uplink quality,.

Formula: None.

II. Non-triggered handovers with target cell congestion (downlink quality)

Description: During the procedure of inter cell handover within a BM of BSC, if all the target cells of the handover are in the same BM module as the source cell, and they are all congested, then this handover would not be triggered by the source cell, and the measurements of these items are triggered based on different handover reasons. If the target cells do not belong to the same BM

554


module as the source cell, or the target cells belong to other BSC, then the handover to those cells will be triggered even if the target cells are congested.

Measurement point: During the procedure of inter cell handover within a BM of BSC, after system receiving the handover request message from LAPD, if all the target cells are in the same BM module as the source cell and they are all congested, then this handover would not be triggered by the source cell. This item is measured when the handover reason is downlink quality.

Formula: None

III. Non-triggered handovers with target cell congestion (uplink strength)


Measurement point: During the procedure of inter cell handover within a BM of BSC, after system receiving the handover request message from LAPD, if all the target cells are in the same BM module as the source cell and they are all congested, then this handover would not be triggered by the source cell. This item is measured when the handover reason is uplink strength.

Formula: None

IV. Non-triggered handovers with target cell congestion (downlink strength)


Measurement point: During the procedure of inter cell handover within a BM of BSC, after system receiving the handover request message from LAPD, if all the target cells are in the same BM module as the source cell and they are all congested, then this handover would not be triggered by the source cell. This item is measured when the handover reason is downlink strength.

Formula: None

555


V. Non-triggered handovers with target cell congestion (timing advance)


Measurement point: During the procedure of inter cell handover within a BM of BSC, after system receiving the handover request message from LAPD, if all the target cells are in the same BM module as the source cell and they are all congested, then this handover would not be triggered by the source cell. This item is measured when the handover reason is timing advance.

Formula: None

VI. Non-triggered handovers with target cell congestion (better cell)


Measurement point: During the procedure of inter cell handover within a BM of BSC, after system receiving the handover request message from LAPD, if all the target cells are in the same BM module as the source cell and they are all congested, then this handover would not be triggered by the source cell. This item is measured when the handover reason is better cell.

Formula: None

VII. Non-triggered handovers with target cell congestion (traffic load)


Measurement point: During the procedure of inter cell handover within a BM of BSC, after system receiving the handover request message from LAPD, if all the target cells are in the same BM module as the source cell and they are all

556


congested, then this handover would not be triggered by the source cell. This item is measured when the handover reason is traffic load.

Formula: None

VIII. Non-triggered handovers with target cell congestion (rapid level drop)


Measurement point: During the procedure of inter cell handover within a BM of BSC, after system receiving the handover request message from LAPD, if all the target cells are in the same BM module as the source cell and they are all congested, then this handover would not be triggered by the source cell. This item is measured when the handover reason is rapid level drop.

Formula: None

IX. Non-triggered handovers with target cell congestion (response to MSC invocation)


Measurement point: During the procedure of inter cell handover within a BM of BSC, after system receiving the handover request message from LAPD, if all the target cells are in the same BM module as the source cell and they are all congested, then this handover would not be triggered by the source cell. This item is measured when the handover reason is response to MSC invocation.

Formula: None

X. Non-triggered handovers with target cell congestion (O&M intervention)

Description: During the procedure of inter cell handover within a BM of BSC, if all the target cells of the handover are in the same BM module as the source cell, and they are all congested, then this handover would not be triggered by the source cell, and the measurements of these items are triggered based on different handover reasons. If the target cells do not belong to the same BM

557


module as the source cell, or the target cells belong to other BSC, then the handover to those cells will be triggered even if the target cells are congested.

Measurement point: During the procedure of inter cell handover within a BM of BSC, after system receiving the handover request message from LAPD, if all the target cells are in the same BM module as the source cell and they are all congested, then this handover would not be triggered by the source cell. This item is measured when the handover reason is O&M intervention.

Formula: None

XI. Non-triggered handovers with target cell congestion (directed retry)


Measurement point: During the procedure of inter cell handover within a BM of BSC, after system receiving the handover request message from LAPD, if all the target cells are in the same BM module as the source cell and they are all congested, then this handover would not be triggered by the source cell. This item is measured when the handover reason is directed retry.

Formula: None

XII. Non-triggered handovers with target cell congestion (minimum timing advance)


Measurement point: During the procedure of inter cell handover within a BM of BSC, after system receiving the handover request message from LAPD, if all the target cells are in the same BM module as the source cell and they are all congested, then this handover would not be triggered by the source cell. This item is measured when the handover reason is minimum timing advance.

Formula: None

558


XIII. Non-triggered handovers with target cell congestion (other causes)


Measurement point: During the procedure of inter cell handover within a BM of BSC, after system receiving the handover request message from LAPD, if all the target cells are in the same BM module as the source cell and they are all congested, then this handover would not be triggered by the source cell. This item is measured when the handover reason is other causes except for the above.

Formula: None

XIV. Unsuccessful outgoing interBSC inter cell handovers (connection failure)

Description: During the procedure of outgoing interBSC inter cell handover, if BTS detects a fault on radio link layer or hardware in source cell, it will send a CONNECTION FAILURE INDICATION message to BSC informing this failure, this handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to connection failure. Related items: Unsuccessfuloutgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives CONNECTION FAILURE INDICATION from BTS. This item is measured at A1 and A2 shown in Figure 3-62 .

Formula: None.

559


A1-A2: Unsuccessful incoming interBSC inter cell handovers

(connection failure)

B1-B2: Unsuccessful incoming interBSC inter cell handovers(error

indication)

C1: Unsuccessful incoming interBSC inter cell handovers(MS

reported various causes)

D1: Unsuccessful incoming interBSC inter cell handovers

(HANDOVER REQUIRED REJECT with various causes)

E1-E2: Unsuccessful incoming interBSC inter cell

handovers(CLEAR COMMAND with various causes)


XV. Unsuccessful outgoing interBSC inter cell handovers (error indication)

Description: During the procedure of outgoing interBSC inter cell handover, if BTS detects an abnormal connection on radio link layer in source cell, it will send a ERROR INDICATION message to BSC informing this failure. And this handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to error indication. Related items: Unsuccessful outgoinginterBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives the ERROR INDICATION message (cause: timer T200 expired (N200+1) times” (0x01) or unsolicited DM response, multiple frame established state (0x05) or sequence error” (0x07)) from BTS. This item is measured at B1 and B2, as shown in Figure 3-62 .

Formula: None

560


XVI. Unsuccessful outgoing interBSC inter cell handovers (A-interface failure)

Description: During the procedure of outgoing interBSC inter cell handover, if error occurs on A interface module processing, A interface module sends Abort Request to the source cell (current cell). And this handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to A-interface failure. Related items: Unsuccessful outgoing interBSC inter cellhandovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, error occurs on A interface module processing, A interface module sends Abort Request to the source cell (current cell). This item is measured when the source cell receives this message.

Formula: None

XVII. Unsuccessful outgoing interBSC inter cell handovers (timer T7 expired)

Description: During the procedure of outgoing interBSC inter cell handover, after the source cell sends a HANDOVER REQUIRED message to MSC, it will start timer T7 (waiting for the HANDOVER COMMAND). When HANDOVER COMMAND is not received before T7 expiry, HANDOVER REQUIRED will be resent and T7 will be started again to wait for HANDOVER COMMAND. If HANDOVER COMMAND is not received after several times of T7 expiry, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to timer T7 expired. Related items: Unsuccessfuloutgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the timer T7 (waiting for HANDOVER COMMAND) expired after the source cell (current cell) had resent HANDOVER REQUIRED for twice on T7 expiry. This item is measured in this case.

Formula: None

XVIII. Unsuccessful outgoing interBSC inter cell handovers (timer T8 expired)

Description: During the procedure of outgoing interBSC inter cell handover, after the source cell sends a HANDOVER COMMAND message to MS, it will start timer T8 to wait for the CLEAR COMMAND message (cause: handover success) from MSC. If the timer T8 expired, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to timer T8 expired. Related items: Unsuccessful outgoing interBSC inter cellhandovers of Cell Measurement Function.

561


Measurement point: During the procedure of interBSC handover, the timer T8 (waiting for the CLEAR COMMAND message (cause: handover success) from MSC) expired. This item is measured in this case.

Formula: None

XIX. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Abnormal release, unspecified)

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER COMMAND message to MS, it receives a HANDOVER FAILURE message from MS with cause “Abnormal release, unspecified (0x01)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Abnormal release, unspecified (0x01)". Related items: Unsuccessful outgoing interBSCinter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Abnormal release, unspecified (0x01)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XX. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Abnormal release, channel unacceptable)

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER COMMAND message to MS, it receives a HANDOVER FAILURE message from MS with cause “Abnormal release, channel unacceptable (0x02)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Abnormal release, channel unacceptable (0x02)". Related items: Unsuccessfuloutgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Abnormal release, channel unacceptable (0x02)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXI. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Abnormal release, timer expired)

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER COMMAND message to MS, it

562


receives a HANDOVER FAILURE message from MS with cause “Abnormal release, timer expired (0x03)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Abnormal release, timer expired (0x03)". Related items: Unsuccessful outgoinginterBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Abnormal release, timer expired (0x03)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXII. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Abnormal release, no activity on the radio path)

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER COMMAND message to MS, it receives a HANDOVER FAILURE message from MS with cause “Abnormal release, no activity on the radio path (0x04)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Abnormal release, no activity on the radio path (0x04)". Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Abnormal release, no activity on the radio path (0x04)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXIII. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Preemptive release)

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER COMMAND message to MS, it receives a HANDOVER FAILURE message from MS with cause “Preemptive release (0x05)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Preemptive release (0x05)". Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Preemptive release

563


(0x05)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXIV. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Handover impossible, timing advance out of range)

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER COMMAND message to MS, it receives a HANDOVER FAILURE message from MS with cause “Handover impossible, timing advance out of range (0x08)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Handover impossible, timing advance out of range (0x08)". Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Handover impossible, timing advance out of range (0x08)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXV. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Channel mode unavailable)

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER COMMAND message to MS, it receives a HANDOVER FAILURE message from MS with cause “Channel mode unavailable (0x09)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Channel mode unavailable (0x09)". Related items: Unsuccessful outgoing interBSCinter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Channel mode unavailable (0x09)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXVI. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Frequency not implemented)


564


receives a HANDOVER FAILURE message from MS with cause “Frequency not implemented (0x0a)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Frequency not implemented (0x0a)". Related items: Unsuccessful outgoing interBSC intercell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Frequency not implemented (0x0a)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXVII. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Call already cleared)

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER COMMAND message to MS, it receives a HANDOVER FAILURE message from MS with cause “Call already cleared (0x41)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Call already cleared (0x41)". Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Call already cleared (0x41)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXVIII. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Semantically incorrect message)

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER COMMAND message to MS, it receives a HANDOVER FAILURE message from MS with cause “Semantically incorrect message (0x5f)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Semantically incorrect message (0x5f)". Related items: Unsuccessful outgoing interBSCinter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Semantically

565


incorrect message (0x5f)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXIX. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Invalid mandatory information)

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER COMMAND message to MS, it receives a HANDOVER FAILURE message from MS with cause “Invalid mandatory information (0x60)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Invalid mandatory information (0x60)". Related items: Unsuccessful outgoinginterBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Invalid mandatory information (0x60)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXX. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Message type non-existent or not implemented)

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER COMMAND message to MS, it receives a HANDOVER FAILURE message from MS with cause “Message type non-existent or not implemented (0x61)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Message type non-existent or not implemented (0x61)". Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Message type non-existent or not implemented (0x61)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXXI. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Message type not compatible with protocol state)


566


receives a HANDOVER FAILURE message from MS with cause “Message type not compatible with protocol state (0x62)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Message type not compatible with protocol state (0x62)". Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Message type not compatible with protocol state (0x62)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXXII. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Conditional IE error)

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER COMMAND message to MS, it receives a HANDOVER FAILURE message from MS with cause “Conditional IE error (0x64)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Conditional IE error (0x64)". Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Conditional IE error (0x64)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXXIII. Unsuccessful outgoing interBSC inter cell handovers (MS reported :No cell allocation available)

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER COMMAND message to MS, it receives a HANDOVER FAILURE message from MS with cause “No cell allocation available (0x65)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: No cell allocation available (0x65)". Related items: Unsuccessful outgoing interBSCinter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: No cell allocation

567


available (0x65)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXXIV. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Protocol error unspecified)

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER COMMAND message to MS, it receives a HANDOVER FAILURE message from MS with cause “Protocol error unspecified (0x6f)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Protocol error unspecified (0x6f)". Related items: Unsuccessful outgoing interBSC intercell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Protocol error unspecified (0x6f)) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXXV. Unsuccessful outgoing interBSC inter cell handovers (MS reported: Other)

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER COMMAND message to MS, it receives a HANDOVER FAILURE message from MS with cause “Other”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "MS reported: Other". Related items: Unsuccessfuloutgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, if MS fails to access the target cell and returns to the source cell (current cell), the source cell receives the HANDOVER FAILURE message (cause: Other, all specified causes in GSM0808 protocol have been listed above except for “Normal Event”, the “Other” cause here include the “Normal Event”(0x00) and other causes which are not defined in GSM0808 protocol) from MS. This item is measured in this case, as shown in Figure 3-62 C1.

Formula: None

XXXVI. Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause O & M intervention )

Description: During the procedure of outgoing interBSC inter cell handover, if after the source cell sends a HANDOVER REQUIRED message to MSC, it

568


receives a HANDOVER REQUIRED REJECT message from MSC with cause “O & M intervention (0x07)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to HANDOVER REQUIRED REJECT with cause “O & M intervention (0x07)”. Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause: O & M intervention (0x07)) from MSC. This item is measured in this case, as shown in Figure 3-62 D1.

Formula: None.

XXXVII. Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Equipment failure)

Description: During the procedure of outgoing interBSC inter cell handover, after the source cell sends a HANDOVER REQUIRED message to MSC, it receives a HANDOVER REQUIRED REJECT message from MSC with cause “Equipment failure (0x20)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to HANDOVER REQUIRED REJECT with cause “Equipment failure (0x20)”. Related items: Unsuccessfuloutgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause: Equipment failure (0x20)) from MSC. This item is measured in this case, as shown in Figure 3-62 D1.

Formula: None

XXXVIII. Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause No radio resource available)

Description: During the procedure of outgoing interBSC inter cell handover, after the source cell sends a HANDOVER REQUIRED message to MSC, it receives a HANDOVER REQUIRED REJECT message from MSC with cause “No radio resource available (0x21)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to HANDOVER REQUIRED REJECT with cause “No radio resource available (0x21)”. Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause: No radio resource available (0x21)) from MSC. This item is measured in this case, as shown in Figure 3-62 D1.

569


Formula: None

XXXIX. Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Requested terrestrial resource unavailable)

Description: During the procedure of outgoing interBSC inter cell handover, after the source cell sends a HANDOVER REQUIRED message to MSC, it receives a HANDOVER REQUIRED REJECT message from MSC with cause “Requested terrestrial resource unavailable (0x22)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to HANDOVER REQUIRED REJECT with cause “Requested terrestrial resource unavailable (0x22)”. Related items: Unsuccessful outgoing interBSC inter cellhandovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause: Requested terrestrial resource unavailable (0x22)) from MSC. This item is measured in this case, as shown in Figure 3-62 D1.

Formula: None

XL. Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause BSS not equipped)

Description: During the procedure of outgoing interBSC inter cell handover, after the source cell sends a HANDOVER REQUIRED message to MSC, it receives a HANDOVER REQUIRED REJECT message from MSC with cause “BSS not equipped (0x25)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to HANDOVER REQUIRED REJECT with cause “BSS not equipped (0x25)”. Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause: BSS not equipped (0x25)) from MSC. This item is measured in this case, as shown in Figure 3-62 D1.

Formula: None

XLI. Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Invalid Cell)

Description: During the procedure of outgoing interBSC inter cell handover, after the source cell sends a HANDOVER REQUIRED message to MSC, it receives a HANDOVER REQUIRED REJECT message from MSC with cause “Invalid Cell (0x27)”, the handover fails. This item measures the times of

570


outgoing interBSC inter cell handover failure due to HANDOVER REQUIRED REJECT with cause “Invalid Cell (0x27)”. Related items: Unsuccessfuloutgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause: Invalid Cell (0x27)) from MSC. This item is measured in this case, as shown in Figure3-62 D1.

Formula: None

XLII. Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Requested transcoding/rate adaption unavailable)

Description: During the procedure of outgoing interBSC inter cell handover, after the source cell sends a HANDOVER REQUIRED message to MSC, it receives a HANDOVER REQUIRED REJECT message from MSC with cause “Requested transcoding/rate adaption unavailable (0x30)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to HANDOVER REQUIRED REJECT with cause “Requested transcoding/rate adaption unavailable (0x30)”. Related items: Unsuccessfuloutgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause: Requested transcoding/rate adaption unavailable (0x30)) from MSC. This item is measured in this case, as shown in Figure 3-62 D1.

Formula: None

XLIII. Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Circuit pool mismatch)

Description: During the procedure of outgoing interBSC inter cell handover, after the source cell sends a HANDOVER REQUIRED message to MSC, it receives a HANDOVER REQUIRED REJECT message from MSC with cause “Circuit pool mismatch (0x31)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to HANDOVER REQUIRED REJECT with cause “Circuit pool mismatch (0x31)”. Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause: Circuit pool mismatch (0x31)) from MSC. This item is measured in this case, as shown in Figure 3-62 D1.

Formula: None

571


XLIV. Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Requested Speech version unavailable)

Description: During the procedure of outgoing interBSC inter cell handover, after the source cell sends a HANDOVER REQUIRED message to MSC, it receives a HANDOVER REQUIRED REJECT message from MSC with cause “Requested Speech version unavailable (0x33)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to HANDOVER REQUIRED REJECT with cause “Requested Speech version unavailable (0x33)”. Related items: Unsuccessful outgoing interBSC inter cellhandovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause: Requested Speech version unavailable (0x33)) from MSC. This item is measured in this case, as shown in Figure 3-62 D1..

Formula: None

XLV. Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Ciphering algorithm not supported)

Description: During the procedure of outgoing interBSC inter cell handover, after the source cell sends a HANDOVER REQUIRED message to MSC, it receives a HANDOVER REQUIRED REJECT message from MSC with cause “Ciphering algorithm not supported (0x40)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to HANDOVER REQUIRED REJECT with cause “Ciphering algorithm not supported (0x40)”. Related items: Unsuccessful outgoing interBSC inter cellhandovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause: Ciphering algorithm not supported (0x40)) from MSC. This item is measured in this case, as shown in Figure 3-62 D1.

Formula: None

XLVI. Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Terrestrial circuit already allocated)

Description: During the procedure of outgoing interBSC inter cell handover, after the source cell sends a HANDOVER REQUIRED message to MSC, it receives a HANDOVER REQUIRED REJECT message from MSC with cause “Terrestrial circuit already allocated (0x50)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to HANDOVER REQUIRED REJECT with cause “Terrestrial circuit already

572


allocated (0x50)”. Related items: Unsuccessful outgoing interBSC inter cellhandovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause: Terrestrial circuit already allocated (0x50)) from MSC. This item is measured in this case, as shown in Figure 3-62 D1.

Formula: None

XLVII. Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Invalid message)

Description: During the procedure of outgoing interBSC inter cell handover, after the source cell sends a HANDOVER REQUIRED message to MSC, it receives a HANDOVER REQUIRED REJECT message from MSC with cause “Invalid message” (“Invalid message contents” (0x51), “Information element or field missing” (0x52), ”Incorrect value”(0x53)), the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to HANDOVER REQUIRED REJECT with cause “Invalid message”. Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause: Invalid message (“Invalid message contents” (0x51), “Information element or field missing” (0x52), ”Incorrect value”(0x53)) from MSC. This item is measured in this case, as shown in Figure 3-62 D1.

Formula: None

XLVIII. Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Protocol Error between BSS and MSC)

Description: During the procedure of outgoing interBSC inter cell handover, after the source cell sends a HANDOVER REQUIRED message to MSC, it receives a HANDOVER REQUIRED REJECT message from MSC with cause “Protocol Error between BSS and MSC (0x60)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to HANDOVER REQUIRED REJECT with cause “Protocol Error between BSS and MSC (0x60)”. Related items: Unsuccessful outgoing interBSC inter cellhandovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause: Protocol Error between BSS and MSC (0x60)) from MSC. This item is measured in this case, as shown in Figure 3-62 D1.

Formula: None

573


XLIX. Unsuccessful outgoing interBSC inter cell handovers (HANDOVER REQUIRED REJECT with cause Other)

Description: During the procedure of outgoing interBSC inter cell handover, after the source cell sends a HANDOVER REQUIRED message to MSC, it receives a HANDOVER REQUIRED REJECT message from MSC with cause “Other” (mainly include the other causes in GSM0808 protocol except for the causes listed above and the causes that are not defined in protocol), the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to HANDOVER REQUIRED REJECT with cause “Other”. Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives HANDOVER REQUIRED REJECT (cause: Other, mainly include the other causes in GSM0808 protocol except for the causes listed above and the causes that are not defined in protocol) from MSC. This item is measured in this case, as shown in Figure 3-62 D1.

Formula: None

L. Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause Radio interface message failure)

Description: During the procedure of outgoing interBSC inter cell handover, if the source cell receives a CLEAR COMMAND message from MSC with cause “Radio interface message failure (0x00)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "CLEAR COMMAND with cause Radio interface message failure". Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives the CLEAR COMMAND message (cause: Radio interface message failure (0x00)) from MSC. This item is measured in this case, as shown in Figure 3-62 E1 and E2.

Formula: None.

LI. Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause Radio interface failure)

Description: During the procedure of outgoing interBSC inter cell handover, the source cell receives a CLEAR COMMAND message from MSC with cause “Radio interface failure (0x01)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "CLEAR COMMAND with cause Radio interface failure". Related items: Unsuccessfuloutgoing interBSC inter cell handovers of Cell Measurement Function.

574


Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives the CLEAR COMMAND message (cause: Radio interface failure (0x01)) from MSC. This item is measured in this case, as shown in Figure 3-62 E1 and E2.

Formula: None

LII. Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause O & M intervention)

Description: During the procedure of outgoing interBSC inter cell handover, the source cell receives a CLEAR COMMAND message from MSC with cause “O & M intervention (0x07)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "CLEAR COMMAND with cause O & M intervention". Related items: Unsuccessful outgoing interBSCinter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives the CLEAR COMMAND message (cause: O & M intervention (0x07)) from MSC. This item is measured in this case, as shown in Figure 3-62 E1 and E2.

Formula: None

LIII. Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause Equipment failure)

Description: During the procedure of outgoing interBSC inter cell handover, the source cell receives a CLEAR COMMAND message from MSC with cause “Equipment failure (0x20)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "CLEAR COMMAND with cause Equipment failure". Related items: Unsuccessful outgoing interBSC intercell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives the CLEAR COMMAND message (cause: Equipment failure (0x20)) from MSC. This item is measured in this case, as shown in Figure 3-62 E1 and E2.

Formula: None

LIV. Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause Preemption)

Description: During the procedure of outgoing interBSC inter cell handover, the source cell receives a CLEAR COMMAND message from MSC with cause “Preemption (0x29)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "CLEAR COMMAND with

575


cause Preemption". Related items: Unsuccessful outgoing interBSC inter cellhandovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives the CLEAR COMMAND message (cause: Preemption (0x29)) from MSC. This item is measured in this case, as shown in Figure 3-62 E1 and E2.

Formula: None

LV. Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause Invalid message)

Description: During the procedure of outgoing interBSC inter cell handover, the source cell receives a CLEAR COMMAND message from MSC with cause “Invalid message” (“Invalid message contents” (0x51), “Information element or field missing” (0x52), ”Incorrect value” (0x53)), the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "CLEAR COMMAND with cause Invalid message". Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives the CLEAR COMMAND message (cause: “Invalid message”, include “Invalid message contents” (0x51), “Information element or field missing” (0x52), ”Incorrect value” (0x53)) from MSC. This item is measured in this case, as shown in Figure 3-62 E1 and E2.

Formula: None

LVI. Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause Protocol Error between BSS and MSC)

Description: During the procedure of outgoing interBSC inter cell handover, the source cell receives a CLEAR COMMAND message from MSC with cause “Protocol Error between BSS and MSC (0x60)”, the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "CLEAR COMMAND with cause Protocol Error between BSS and MSC". Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives the CLEAR COMMAND message (cause: Protocol Error between BSS and MSC (0x60)) from MSC. This item is measured in this case, as shown in Figure 3-62 E1 and E2.

Formula: None

576


LVII. Unsuccessful outgoing interBSC inter cell handovers (CLEAR COMMAND with cause Other)

Description: During the procedure of outgoing interBSC inter cell handover, the source cell receives a CLEAR COMMAND message from MSC with cause “Other” (mainly include the other causes in GSM0808 protocol except for the causes listed above and the causes that are not defined in protocol), the handover fails. This item measures the times of outgoing interBSC inter cell handover failure due to "CLEAR COMMAND with cause Other ". Related items: Unsuccessful outgoing interBSC inter cell handovers of Cell Measurement Function.

Measurement point: During the procedure of interBSC handover, the source cell (current cell) receives the CLEAR COMMAND message (cause: other, mainly include the other causes in GSM0808 protocol except for the causes listed above and the causes that are not defined in protocol) from MSC. This item is measured in this case, as shown in Figure 3-62 E1 and E2.

Formula: None

3.14 Abis-interface BTS CRC Measurement Function

3.14.1 General

The traffic statistic items of "Abis-interface BTS CRC Measurement Function" are used to measure the probability of "CRC error" or "CRC severely error" of each Abis interface E1 port, which provide the information about communication situation of the E1 link connecting BSC and BTS.

The object of Abis-interface BTS CRC Measurement Function is site.


Table 3-1 Statistic items in Abis-interface BTS CRC Measurement Function

No. Item name

1 CRC errored seconds of port 0

2 CRC severely errored seconds of port 0








577







































Because the items of Abis-interface BTS CRC Measurement Function have the same description, measurement point and formula except for Port No., so the next section will provide detailed information of the first two items only.

578



I. CRC (severely) errored secondsof port 0

Description: In a BSS, the communication between BSC and BTS is provided by E1. BTS checks the E1 links of each E1 port. Whenever a “CRC error” or “CRC severely error” is detected, the corresponding counter counts 1. BTS reports the counter values to BSC every 5 minutes. BSC sums up the number of times counted to get the results of these items. These items provide the information of CRC errors occurs on Abis interface E1 transmission. The larger “CRC errored seconds” and “CRC severely errored seconds” suggests worse Abis E1 transmission.

Measurement point: BTS reports the counter value to BSC every 5 minutes. BSC sums up the number of times counted concerning to difference ports according to the port number in the messages to get results of these items.

Formula: None.

3.15 Call Allocation by TA Measurement Function

3.15.1 General

The traffic statistic items of “Call Allocation by TA Measurement Function" are used to measure the number of MRs reported by MS within specified range of TA. The results provide the information about traffic distribution on difference distances between BTS and MS. This measurement function is a helpful reference for network maintenance and optimization.

The statistic object of Call Allocation by TA Measurement Function is TRX. The module No., cell No. and TRX No. (or all TRXs in the configured range of cells in the configured range) of the task can be configured in Object Definition. Because of the correlation between these items, it is required that all these items be registered in the same task.


Table 3-2 Statistic items in Call Allocation by TA Measurement Function

No. Item name

1 Number of MR(TA = 0)





579



























31 Number of MR(30 <= TA <= 31)

32 Number of MR(32 <= TA <= 33)

33 Number of MR(34 <= TA <= 35)

34 Number of MR(36 <= TA <= 37)

35 Number of MR(38 <= TA <= 39)

36 Number of MR(40 <= TA <= 44)

37 Number of MR(45 <= TA <= 49)

38 Number of MR(50 <= TA <= 54)

39 Number of MR(55 <= TA <= 63)

40 Number of MR(63 < TA)

Because the items of Call Allocation by TA Measurement Function have the same description, measurement point and formula except for TA values, so the next section will provide detailed information of the first item only.

580



I. Number of MR (TA = 0)

Description: Timing Advance (TA) suggests the distance between MS and BTS. Larger TA suggests longer distance between MS and BTS. MS reports a MR to the network periodically after it seizes channel. The number of MRs suggests the traffic volume. Larger number suggests heavier traffic volume. Items in this measurement function provide the number of MRs reported by MS within specified range of TA. The results provide the information about traffic distribution on difference distances between BTS and MS. This measurement function is a helpful reference for network maintenance and optimization.

Measurement point: After BSC receives a MR, the item "Number of MR (TA = x)" or "Number of MR(x1 <= TA <=x2)" increases by 1.

Formula: None.

3.16 Call Drop on TRX Measurement Function

3.16.1 General

“Call Drop on TRX Measurement Function" includes three measurement types: Call Drop Measurement by TA Function, Call Drop Measurement by Receiving Level Function and Call Drop Measurement by Receiving Quality Function.

Call Drop Measurement by TA Function: Items in this measurement type provide call drop distribution in cases of different TAs. These items can be used for the network maintenance and optimization.

Call Drop Measurement by Receiving Level Function: Items in this measurement type provide call drop distribution in cases of different uplink receiving levels and downlink receiving levels. These items can be used for the network maintenance and optimization.

Call Drop Measurement by Receiving Quality Function: Items in this measurement type provide call drop times distribution in cases of different uplink receiving qualities and downlink receiving qualities. These items can be used for the network maintenance and optimization.

The statistic object of Call Drop on TRX Measurement Function is TRX. The module No., cell No. and TRX No. (or all TRXs in the configured range of cells in the configured range) of the task can be configured in Object Definition. Because of the correlation between items of the same measurement type, it is required that all

581


items of a measurement type of Call Drop on TRX Measurement Function be registered in the same task.

3.16.2 Call Drop Measurement by TA Function

All the statistic items of Call Drop Measurement by TA Function are listed in Table3-3 .

Table 3-3 Statistic items in Call Drop Measurement by TA Function

No. Item name

1 Call drops(TA=0)

2 Call drops(TA=1)

3 Call drops(TA=2)

4 Call drops(TA=3)

5 Call drops(TA=4)

6 Call drops(TA=5)

7 Call drops(TA=6)

8 Call drops(TA=7)

9 Call drops(TA=8)

10 Call drops(TA=9)

11 Call drops(TA=10)




















582


31 Call drops(30<=TA<=31)









40 Call drops(TA>63)

Because the items of Call Drop Measurement by TA Function have the same description, measurement point and formula except for TA value considered, so the next section will provide detailed information of the first item only.

I. Call drops (TA=0)

Description: Timing Advance (TA) suggests the distance between MS and BTS. Larger TA suggests longer distance between MS and BTS. After BSC receives ERROR INDICATION message or CONNECTION FAILURE message and the channel currently seized by MS is TCH, the index

corresponding to the last TA value of this call increases by 1. These items provide information about call drop distribution in cases of different TAs. These items can be used for the network maintenance and optimization.

Measurement point: After BSC receives ERROR INDICATION message or CONNECTION FAILURE message and the channel currently seized by MS is TCH, the index corresponding to the last TA value of this call increases by 1.

Formula: None.

3.16.3 Call Drop Measurement by Receiving Level Function

All the statistic items of Call Drop Measurement by Receiving Level Function are listed in Table 3-4 .

Table 3-4 Statistic items in Call Drop Measurement by Receiving Level Function

No. Item name

1 Call drops(0<=uplink receiving level<=5)






583






11 Call drops(0<=downlink receiving level<=5)










Because the items of Call Drop Measurement by Receiving Level Function have the same description, measurement point and formula except for uplink receiving level value or downlink receiving level value considered, so the next section will provide detailed information of two typical items only.

I. Call drops(0<=uplink receiving level<=5)

Description: After BSC receives ERROR INDICATION message or CONNECTION FAILURE message and the channel currently seized by MS is TCH, the index corresponding to the last uplink receiving level value of this call

increases by 1. These items provide information about call drop distribution in cases of different uplink receiving level values. These items can be used for the network maintenance and optimization.

Measurement point: After BSC receives ERROR INDICATION message or CONNECTION FAILURE message and the channel currently seized by MS is TCH, the index corresponding to the last uplink receiving level value of this call increases by 1.

Formula: None.

II. Call drops(0<=downlink receiving level<=5)

Description: After BSC receives ERROR INDICATION message or CONNECTION FAILURE message and the channel currently seized by MS is TCH, the index corresponding to the last downlink receiving level value of this

call increases by 1. These items provide information about call drop distribution in cases of different downlink receiving level values. These items can be used for the network maintenance and optimization.

584


Measurement point: After BSC receives ERROR INDICATION message or CONNECTION FAILURE message and the channel currently seized by MS is TCH, the index corresponding to the last downlink receiving level value of this call increases by 1.

Formula: None.

3.16.4 Call Drop Measurement by Receiving Quality Function

All the statistic items of Call Drop Measurement by Receiving Quality Function are listed in Table 3-5 .

Table 3-5 Statistic items in Call Drop Measurement by Receiving Quality Function

No. Item name

1 Call drops(uplink receiving quality=0)








9 Call drops(downlink receiving quality=0)








Because the items of Call Drop Measurement by Receiving Quality Function have the same description, measurement point and formula except for uplink receiving quality value or downlink receiving quality value considered, so the next section will provide detailed information of two typical items only.

I. Call drops(uplink receiving quality=0)

Description: After BSC receives ERROR INDICATION message or CONNECTION FAILURE message and the channel currently seized by MS is TCH, the index corresponding to the last uplink receiving quality value of this

call increases by 1. These items provide information about call drop

585


distribution in cases of different uplink receiving quality values. These items can be used for the network maintenance and optimization.

Measurement point: After BSC receives ERROR INDICATION message or CONNECTION FAILURE message and the channel currently seized by MS is TCH, the index corresponding to the last uplink receiving quality value of this call increases by 1.

Formula: None.

II. Call drops(downlink receiving quality=0)

Description: After BSC receives ERROR INDICATION message or CONNECTION FAILURE message and the channel currently seized by MS is TCH, the index corresponding to the last downlink receiving quality value of

this call increases by 1. These items provide information about call drop distribution in cases of different downlink receiving quality values. These items can be used for the network maintenance and optimization.

Measurement point: After BSC receives ERROR INDICATION message or CONNECTION FAILURE message and the channel currently seized by MS is TCH, the index corresponding to the last downlink receiving quality value of this call increases by 1.

Formula: None.

3.17 Cell Frequency Scan

3.17.1 General

Uplink frequency scan function is a Huawei-featured function. It can scan the uplink Rx level of all the frequencies in GSM900/1800 frequency band, i.e. it can scan the strength of interference signals in the frequency bands of “876~880M Hz”, “880~890M Hz”, "890~915M Hz" and "1805~1880M Hz". The uplink frequency scan function is to test interference. Because the uplink frequency scan is a test of uplink Rx level, the measurement result reflects the strength of the signals of the measurement frequency that can be received in the cell, and can serve as the reference for engineers to select appropriate working frequencies.

3.17.2 Principle

On the precondition that normal conversion is not affected, the uplink frequency scan function utilizes an idle frame on a TCH of the measurement cell to conduct a cyclic test (When BSC allocates this channel, the TCH on the TRX which BCCH belongs to is preferred), and scans the uplink Rx level of the designated frequency.

586


TCH is of 26-multiframe structure, and there is one idle frame in each multiframe. So the period of the idle frame on TCH is "26 multiframe structure*0.577 (burst length)*8 (TDMA frame) =120ms". In actual application, it takes about 1 minute to scan 50 frequencies. In a frequency scan task, max. 124 measurement frequencies can be registered. An ergodic scan approximately takes 3 minutes. Uplink frequency scan is triggered after a frequency scan traffic statistic task is registered. The measurement shall be stopped when the traffic statistic task is deleted or suspended.

The measurement result output in Traffic Statistic System is the average value of the uplink Rx level scanned from the start time of a frequency scan task till the measurement result is output, but clipping to measurement result is performed technically. Because an idle frame is adopted for uplink frequency scan, in actual application, the uplink Rx level of synchronous cells (including the frequencies of the other TRXs of this cell) cannot be scanned.

The uplink frequency scan function is used to measure the interference level that affects GSM900/1800 uplink Rx quality in the radio environment. It can measure the uplink interference of all GSM900/1800 frequency bands. To perform more accurate measurement for the interference band of idle TCH, please refer to the items in "Cell Measurement Function" and "Channel Allocation Measurement Function". Measurement of this interference band only aims at designated frequencies.

Because the main set and sub set levels are reported and processed separately, there are two statistic values for the uplink frequency scan result of a frequency. The values adopt "main setlevel/sub set level" form.

The registered task period can be set as per the actual requirement. The min. period is 15 minutes. The object type of a frequency scan traffic statistic task is "cell". For each cell we can only register one of the following measurement types: Band 900, Band 1800, Band EGSM, Band RGSM.

Note:

BTS20 does not support the frequency scan function. The principle of BTS3001C frequency scan

function is similar to that of BTS3X. BTS3001C uses all the timeslots of the 8 TCHs on the whole

TRX, so the precision is comparatively higher. However, normal conversion is interrupted. BTS3001C

frequency scan function is started and controlled by BTS Maintenance System.

587

Documents

03-Traffic Statistic Items