counter resource access

BSC Counters: Resource AccessMeasurement

DN9813745 © Nokia Corporation 1 (62)Issue 7-0 en Nokia Proprietary and Confidential

BSC Counters: Resource Access Measurement

The information in this documentation is subject to change without notice and describes onlythe product defined in the introduction of this documentation. This documentation is intendedfor the use of Nokia's customers only for the purposes of the agreement under which thedocumentation is submitted, and no part of it may be reproduced or transmitted in any form ormeans without the prior written permission of Nokia. The documentation has been prepared tobe used by professional and properly trained personnel, and the customer assumes fullresponsibility when using it. Nokia welcomes customer comments as part of the process ofcontinuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity,or performance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia and the customer. However, Nokiahas made all reasonable efforts to ensure that the instructions contained in the documentationare adequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the documentation.

Nokia's liability for any errors in the documentation is limited to the documentary correction oferrors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation orthe information in it.

This documentation and the product it describes are considered protected by copyrightaccording to the applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this documentation may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright © Nokia Corporation 2002. All rights reserved.

2 (62) © Nokia Corporation DN9813745Nokia Proprietary and Confidential Issue 7-0en

Contents

Contents 3

List of figures 4

Summary of changes 5

1 BSC Counters: Resource Access Measurement 7

2 Counters of Resource Access Measurement 11

3 Signalling charts of Resource Access Measurement 37



List of figures

Figure 1. Basic call without counters. 38

Figure 2. Basic call without counters (cont.). 39

Figure 3. Basic call with counters. 40

Figure 4. FACCH call setup due to SDCCH congestion. 41

Figure 5. Ghost reservation. 42

Figure 6. Busy AGCH-channel. 43

Figure 7. Unsuccessful channel request. 44

Figure 8. SMS broadcast. 44

Figure 9. Mobile originating SMS on a TCH. 45

Figure 10. Mobile terminating SMS on a TCH. 46

Figure 11. Mobile originating SMS on FACCH. 47

Figure 12. Mobile terminating SMS on FACCH. 48

Figure 13. Mobile originating SMS on an SDCCH. 49

Figure 14. Mobile terminating SMS on an SDCCH. 50

Figure 15. Mobile originating unsuccessful SMS on a TCH. 51

Figure 16. Mobile terminating unsuccessful SMS on a TCH. 52

Figure 17. Mobile originating unsuccessful SMS on FACCH. 53

Figure 18. Mobile terminating unsuccessful SMS on FACCH. 54

Figure 19. Mobile originating unsuccessful SMS on an SDCCH. 55

Figure 20. Mobile terminating unsuccessful SMS on an SDCCH. 56

Figure 21. CCCH load indication. 57

Figure 22. CCCH Load Indication if GPRS is activated in BTS and other condititionsare valid. 59

Figure 23. Unsuccessful channel requests due to BCSU overload. 60

Figure 24. PS Paging in GPRS 60

Figure 25. CS Paging in GPRS. 61


Summary of changes

Changes between document issues are cumulative. Therefore, the latest documentissue contains all changes made to previous issues.

Changes made between issues 7 and 6

1. Introduction

The following new counters added: 003059-003063

2. Counters

The following new counters added: 003059-003063


2. Counters

The following counters updated: 003002, 003004, 003010, 003013-003014,003016, 003020, 003025, 003030, 003039-003041, 003046, 003051, 003057


1. Counters

Information about figures added in counters 003046-003058

2. Signalling Charts

The following new signalling charts added: 10, 11, 16, 17, 21, 23 and 24

The following signalling chart updated: 20



1 BSC Counters: Resource AccessMeasurement

Resource Access Measurement registers information on all common controlchannels (CCCH) of the base station controller. The recorded items of datacomprise the number of messages sent to the Abis interface. The messages aresorted according to message type, average load on control channels, and thenumber of traffic channel seizures for mobile originating (MOC) and terminatingcalls (MTC). Signalling charts are drawn with the accuracy of message interface.

For more information on the documentation of the counters, with an exampletable and an explanation of the table fields, see BSC Counters: GeneralInformation on Measurements and Observations.

Counters

Paging messages sent to BTS 003000

Immediate assignment messages sent to BTS 003001

Immediate assignment reject messages sent to BTS 003002

SMS CB request messages sent to BTS 003003

Channel request messages received from BTS 003004

Delete indication messages received from BTS 003005

Average RACH slot counter 003006

Resource access denominator 1 003007

Average PCH load on CCCH 003008


Peak RACH load on CCCH 003010

Peak PCH load on CCCH 003011

Success seizure for MTC 003012

Success seizure for MOC 003013

Average RACH busy counter 003014




Average RACH access counter 003016


Minimum paging buffer 003018

SDCCH location update 003019

SDCCH call re-establishment 003020

SDCCH emergency call 003021

TCH emergency call 003022

TCH MTC 003023

TCH MOC 003024

TCH call re-establishment 003025

Success TCH SMS establishment 003026

Unsuccessful TCH SMS establishment 003027

Success SDCCH SMS establishment 003028

Unsuccessful SDCCH SMS establishment 003029

Ghost CCCH reservation 003030

Rejected seizure attempt due to distance 003031

TRX in extended area 003032

IMSI detach SDCCH 003033

IMSI detach TCH 003034

Maximum paging buffer capacity 003035

Average paging buffer capacity 003036


Delete paging command 003038

BCSU overload lower limit 003039

BCSU overload upper limit 003040

BCSU overload deleted RACH 003041

TRX diagnostics 003042

TRX diagnostics fault 003043

Successful seizures of SDCCHs 003044



Related topics

Counters of Resource Access Measurement

Signalling charts of Resource Access Measurement

Successful seizures of TCHs 003045

Paging load paging buffer space on Gb-interference 003046


Average buffer occupancy percentage 003048


Maximum buffer occupancy percentage 003050

Average CCCH load radio block occupancy paging 003051


Average DRX AGCH 003053


Average NON-DRX AGCH 003055


PS paging command 003057

CS paging command 003058

Call assign after SMS 003059

Spare 003060

Spare 003061

Spare 003062

Spare 003063



2 Counters of Resource AccessMeasurement

No

COUNTER NAME

RELEASE/CHANGED

003000

PAGING MESSAGES SENT TO BTS

S1

TRIGGER POINT(S) See figure Basic call with counters

EXPLANATION Number of PAGING_COMMAND messages sent to the BTS.

UPDATED When a PAGING_COMMAND message is sent to the BTS.

No

COUNTER NAME

RELEASE/CHANGED

003001

IMMEDIATE ASSIGNMENT MESSAGES SENT TO BTS

S1

TRIGGER POINT(S) See figures:

• Basic call with counters

• Busy AGCH Channel

EXPLANATION Number of IMMEDIATE_ASSIGN_COMMAND messages sent to theBTS.

UPDATED When an IMMEDIATE_ASSIGN_COMMAND message is sent to theBTS.



No

COUNTER NAME

RELEASE/CHANGED

003002

IMMEDIATE ASSIGNMENT REJECT MESSAGES SENT TOBTS

S1/S6

TRIGGER POINT(S) See figure Unsuccessful channel request

EXPLANATION Number of IMMEDIATE_ASSIGNMENT_REJECT messages sent tothe BTS.

UPDATED This counter is updated when anIMMEDIATE_ASSIGNMENT_REJECT message is packed and sentto the BTS. The message can include one to four immediateassignment rejects.

The IMMEDIATE_ASSIGNMENT_REJECT message is sent to MSin the following cases:

• No free SDCCH.

• Abis interface process has no internal resources to handle therequest.

No

COUNTER NAME

RELEASE/CHANGED

003003

SMS BC REQUEST MESSAGES SENT TO BTS

S1

TRIGGER POINT(S) See figure SMS broadcast

EXPLANATION Number of SMS_BROADCAST_ REQUEST messages sent to theBTS.

UPDATED When all 4 SMS_BROADCAST_REQUEST messages are sent tothe BTS.



No

COUNTER NAME

RELEASE/CHANGED

003004

CHANNEL REQUEST MESSAGES RECEIVED FROM BTS

S1


• Basic call with counters

• Ghost reservation

• Busy AGCH channel

• Unsuccesful channel request

• Unsuccesful channel requests due to BCSU overload

EXPLANATION Number of CHANNEL_REQUIRED messages received from theBTS.

UPDATED When a CHANNEL_REQUIRED message is received from the BTS.These requests are related to CSW channels. PSW channelrequests have their own counter 072082.

No

COUNTER NAME

RELEASE/CHANGED

003005

DELETE IND MESSAGES RECEIVED FROM BTS

S1

TRIGGER POINT(S) See figure Busy AGCH Channel

EXPLANATION Number of DELETE_INDICATION messages received from the BTS.

UPDATED When a DELETE_INDICATION message is received from the BTS.

No

COUNTER NAME

RELEASE/CHANGED

003006

AVE RACH SLOT COUNT

S1

TRIGGER POINT(S) See figure CCCH load indication

EXPLANATION Average number of the RACH slots on a CCCH.

UPDATED When the value of the RACH load is received in aCCCH_LOAD_INDICATION message from the BTS during ameasurement period. The new value of the RACH load is added tothe previous value, and the number of events is increased by one.

DEPENDENCIES Counter 003007 is updated along with this counter.

COUNTER TYPE Average



No

COUNTER NAME

RELEASE/CHANGED

003007

RES ACC DENOMINATOR 1

S1


EXPLANATION Denominator of the average RACH slot number (always > 0).


No

COUNTER NAME

RELEASE/CHANGED

003008

AVE PCH LOAD ON CCCH

S1


EXPLANATION When divided by the value of counter 3009, this counter tells theAverage PCH load on a CCCH. It indicates the remaining space forPaging Commands associated with this CCCH timeslot, given as thenumber of additional Paging Commands that it is possible to store.The smaller the value, the greater the load on the PCH

UPDATED Cumulatively during the measurement period every time when thelatest value of the PCH load is received in aCCCH_LOAD_INDICATION message from the BTS.

DEPENDENCIES This counter is updated along with counter 003009.


No

COUNTER NAME

RELEASE/CHANGED

003009


S1


EXPLANATION Denominator of the average PCH load on CCCH (always > 0).




No

COUNTER NAME

RELEASE/CHANGED

003010

PEAK RACH LOAD ON CCCH

S1


EXPLANATION Peak value of the number of busy RACHs on a CCCH.

UPDATED When the value of the RACH load received in aCCCH_LOAD_INDICATION message exceeds the previous value ofthe RACH load during the measurement period.

NOTE! This RACH counter is triggered when the RX Level is above -100dBm. Other detection methods (like CRC or S/N) are not applied.This means that high load on RACH may occure even without asignificant number of CHANNEL_REQUIRED messages. Forexample, RACHs from different MSs can clash and cause a highsignal level, but the decoding does not find any detectable RACH.The interference causes lots of bursts that trigger the counter, butthese bursts are then filtered out in the detection.

No

COUNTER NAME

RELEASE/CHANGED

003011

PEAK PCH LOAD ON CCCH

S1

EXPLANATION This counter is NOT relevant.

DEPENDENCIES This counter has been replaced by counter 003018 MIN PAGINGBUF.

No

COUNTER NAME

RELEASE/CHANGED

003012

SUCCESS SEIZURE FOR MOBILE TERM CALL

S1


EXPLANATION Number of successful seizures of SDCCHs for an MTC.

UPDATED When an ESTABLISH_INDICATION message with paging responseis received on SDCCH from the BTS.



No

COUNTER NAME

RELEASE/CHANGED

003013

SUCCESS SEIZURE FOR MOBILE ORIG CALL

S1


EXPLANATION Number of successful seizures for SDCCH for an MOC.

UPDATED When an ESTABLISH_INDICATION message with CM servicerequest is received on SDCCH from the BTS.

NOTE! This counter is updated also in case of a SMS orSupplementary Service Requests.

No

COUNTER NAME

RELEASE/CHANGED

003014

AVE RACH BUSY COUNT

S1


EXPLANATION Average number of busy RACHs on a CCCH.

UPDATED When the value of the RACH load is received in aCCCH_LOAD_INDICATION message from the BTS during ameasurement period. The number of busy RACHs is added to theprevious value and the number of the events is increased by one.

NOTE! This RACH counter is triggered when the RX Level is above -100dBm. Other detection methods (like CRC or S/N) are not applied.This means that high load on RACH may occure even without asignificant number of CHANNEL_REQUIRED messages. Forexample, RACHs from different MSs can clash and cause a highsignal level, but the decoding does not find any detectable RACH.The interference causes lots of bursts that trigger the counter, butthese bursts are then filtered out in the detection.





No

COUNTER NAME

RELEASE/CHANGED

003015


S1


EXPLANATION Denominator of the average number of busy RACHs (always > 0).


No

COUNTER NAME

RELEASE/CHANGED

003016

AVE RACH ACCESS COUNT

S1


EXPLANATION Number of average RACH accesses on a CCCH.

UPDATED When the value of the RACH load is received in aCCCH_LOAD_INDICATION message from the BTS during ameasurement period. The number of RACH accesses is added tothe previous value and the number of events is increased by one.

NOTE! This counter is updated by RACH bursts above the -100 dBmlevel that have passed the detection (CRC, S/N) in the BTS.



No

COUNTER NAME

RELEASE/CHANGED

003017


S1


EXPLANATION Denominator of the average number of RACH accesses (always >0).




No

COUNTER NAME

RELEASE/CHANGED

003018

MIN PAGING BUF

S2 PHASE 1


EXPLANATION Minimum size of the paging buffer on a CCCH (Peak value of theaverage PCH load: the smaller the value, the greater the load on thePCH).

UPDATED When the value of the PCH load with the size of the paging bufferreceived in a CCCH_LOAD_ INDICATION message from the BTS issmaller than the previous value during a measurement period.0xFFFFFFFF means 'unknown'.

No

COUNTER NAME

RELEASE/CHANGED

003019

SDCCH LOC UPD

S2 PHASE 1


EXPLANATION Number of successful seizures of SDCCHs for location update.

UPDATED When an ESTABLISH_INDICATION message with request for alocation update is received on SDCCH from the BTS.

No

COUNTER NAME

RELEASE/CHANGED

003020

SDCCH CALL RE EST

S3


EXPLANATION Number of successful SDCCH seizures for call re-establishmentattempts.

UPDATED When an ESTABLISHMENT_INDICATION message for a call re-establishment is received on SDCCH from the BTS. Note that thiscounter counts only the number of re-establisment attempts onSDCCH. Counter 057022 gives the number of SDCCH re-establishment assignments.



No

COUNTER NAME

RELEASE/CHANGED

003021

SDCCH EMERG CALL

S3


EXPLANATION Number of successful seizures of SDCCHs for an emergency call.

UPDATED When an ESTABLISH_INDICATION message for an emergency callis received on SDCCH from the BTS.

No

COUNTER NAME

RELEASE/CHANGED

003022

TCH EMERG CALL

S3/S5

TRIGGER POINT(S) See figure FACCH call setup due to SDCCH congestion

EXPLANATION Number of successful seizures of TCHs for an emergency call inFACCH call setup due to SDCCH congestion. If the FACCH callsetup is turned off, the counter value is zero.

UPDATED When an ESTABLISH_INDICATION message for an emergency callis received on TCH from the BTS.

RELATED TO A FEATURE BSS5290 : FACCH call setup due to SDCCH congestion

No

COUNTER NAME

RELEASE/CHANGED

003023

TCH MTC

S3/S5


EXPLANATION Number of successful seizures of TCHs for MTC in FACCH callsetup due to SDCCH congestion. If the FACCH call setup is turnedoff, the counter value is zero.

UPDATED When an ESTABLISH_INDICATION message with a pagingresponse is received on TCH from the BTS.

RELATED TO A FEATURE BSS5290 FACCH Call Setup due to SDCCH Congestion



No

COUNTER NAME

RELEASE/CHANGED

003024

TCH MOC

S3/S5


EXPLANATION Number of successful seizures of TCHs for MOC in FACCH callsetup due to SDCCH congestion. If the FACCH call setup is turnedoff, the counter value is zero.

UPDATED When an ESTABLISH_INDICATION message with a request for CMservice is received on TCH from the BTS.


No

COUNTER NAME

RELEASE/CHANGED

003025

TCH CALL RE EST

S3/S5


EXPLANATION Number of successful TCH seizures for call re-establishmentattempts in FACCH call setup due to SDCCH congestion. If theFACCH call setup is turned off, the counter value is zero.

UPDATED When an ESTABLISH_INDICATION message for a call re-establishment is receiced on TCH from the BTS. Note that thiscounter counts only the number of re-establisment attempts onTCH. Counter 057032 gives the number of TCH re-establishmentassignments.




No

COUNTER NAME

RELEASE/CHANGED

003026

SUCC TCH SMS EST

S3


• Mobile originating SMS on a TCH

• Mobile terminating SMS on a TCH

• Mobile originating SMS on FACCH

• Mobile terminating SMS on FACCH

EXPLANATION Number of SMSs successfully established on a TCH.

UPDATED When an ESTABLISH_INDICATION message (mobile originatingSMS) or an ESTABLISH_CONFIRM message (mobile terminatingSMS) is received on TCH from the BTS.

No

COUNTER NAME

RELEASE/CHANGED

003027

UNSUCC TCH SMS EST

S3


• Mobile originating unsuccessful SMS on a TCH

• Mobile terminating unsuccessful SMS on a TCH

• Mobile originating unsuccessful SMS on FACCH

• Mobile terminating unsuccessful SMS on FACCH

EXPLANATION Number of unsuccessful establishments of SMSs on a TCH.

UPDATED When establishment of SMS fails on TCH.



No

COUNTER NAME

RELEASE/CHANGED

003028

SUCC SDCCH SMS EST

S3


• Mobile originating SMS on an SDCCH

• Mobile terminating SMS on an SDCCH

EXPLANATION Number of SMSs successfully established on an SDCCH.

UPDATED When an ESTABLISH_INDICATION message (mobile originatingSMS) or an ESTABLISH_CONFIRM message (mobile terminatingSMS) is received on SDCCH from the BTS.

No

COUNTER NAME

RELEASE/CHANGED

003029

UNSUCC SDCCH SMS EST

S3


• Mobile originating unsuccessful SMS on an SDCCH

• Mobile terminating unsuccessful SMS on an SDCCH

EXPLANATION Number of unsuccessful establishments of SMSs on an SDCCH.

UPDATED When the establishment of an SMS fails on SDCCH.

No

COUNTER NAME

RELEASE/CHANGED

003030

GHOST CCCH RES

S3

TRIGGER POINT(S) See figure Ghost reservation

EXPLANATION Number of ghost reservations on a CCCH.

UPDATED When a ghost reservation is detected on a CCCH. This kind ofrandom access can be caused, for example, by white noise or co-channel interference. Note that the ghosts triggering this counterhave illegal establishment cause. Ghost accessess with legalestablishment cause get on SDCCH and later fail typically causingthe triggering of counter 0010075.

DEPENDENCIES See also counter 003031.



No

COUNTER NAME

RELEASE/CHANGED

003031

REJ SEIZ ATT DUE DIST

S5

TRIGGER POINT(S) See figure Ghost reservation

EXPLANATION Number of seizure attempts rejected due to distance.

UPDATED When random access is rejected by the BSC because of a too longdistance between the MS and BTS. This kind of random access canbe caused, for example, by white noise or co-channel interference.


RELATED TO A FEATURE BSS5280 Distance Checking in Resource Allocation

No

COUNTER NAME

RELEASE/CHANGED

003032

TRX IN EXT AREA

S6

EXPLANATION Normal TRX / extended TRX

0 = normal area

1= extended area

RELATED TO A FEATURE BSS6037 Improved Solution for Extended Cell

COUNTER TYPE Variable

No

COUNTER NAME

RELEASE/CHANGED

003033

IMSI DETACH SDCCH

S7


EXPLANATION Number of successful seizures of SDCCHs for IMSI detach.

UPDATED When an ESTABLISH_INDICATION message for an IMSI detach isreceived on SDCCH from the BTS.

RELATED TO A FEATURE BSS7043 Measurement Improvements



No

COUNTER NAME

RELEASE/CHANGED

003034

IMSI DETACH TCH

S7


EXPLANATION Number of successful seizures of TCHs for IMSI detach in FACCHcall setup due to SDCCH congestion. If the FACCH call setup isturned off, then the counter value is zero.

UPDATED When an ESTABLISH_INDICATION message for an IMSI detach isreceived on TCH from the BTS.

RELATED TO A FEATURE BSS7043 Measurement Improvements

No

COUNTER NAME

RELEASE/CHANGED

003035

MAX PAGING BUFFER CAPA

S7


EXPLANATION Maximum percent of paging buffer capacity. This counter indicatesmaximum paging buffer occupancy percentage during the reportingperiod. The range of this counter is 0-100% with 1% intervals.

UPDATED When the value of the maximum paging buffer received in aCCCH_LOAD_INDICATION message exceeds the previous valueof the paging buffer during a measurement period.

RELATED TO A FEATURE BSS7048 CCCH Improvements



No

COUNTER NAME

RELEASE/CHANGED

003036

AVE PAGING BUFFER CAPA

S7


EXPLANATION Average percent of the paging buffer capacity. This counter indicatesaverage paging buffer occupancy percentage during the reportingperiod. The range of this counter is 0-100 % with 1% intervals. Eachtime a paging multiframe cycle ends, the occupancy percentage(occupied buffer space versus maximum space) of each pagingqueue is calculated, which is (100*N)/N(max)%.

The sum and number of all average buffer occupancy values duringthe reporting period are stored. When it is time to send aCCCH_LOAD_INDICATION message, an average is calculated andreported in the message as average buffer occupancy percentageduring the reporting period.

UPDATED When a CCCH_LOAD_INDICATION message is received from theBTS. The average paging buffer value is added to the previous valueand the number of events is increased by one.




No

COUNTER NAME

RELEASE/CHANGED

003037


S7


EXPLANATION Denominator of the average number of paging buffers (always > 0).





No

COUNTER NAME

RELEASE/CHANGED

003038

DELETE PAGING COMMAND

S7


EXPLANATION Number of the delete paging commands. This counter indicates ifsome group-specific paging queue becomes so full that an additionalpaging command cannot be stored to the buffer. In such a case thepaging command is deleted.

The message reports the total amount of such deleted pagingcommands during the reporting period.

UPDATED When a CCCH_LOAD_INDICATION message is received from theBTS and the paging command is deleted.


No

COUNTER NAME

RELEASE/CHANGED

003039

BCSU OVERLOAD LOWER LIMIT

S7

TRIGGER POINT(S) See figure Unsuccessful channel requests due to BCSU overload

EXPLANATION Number of refused calls, when BCSU overload lower limit occurs.When the overload lower limit occurs, all calls except emergency,MOC and MTC calls are refused.

UPDATED When the call is refused due to BCSU overload lower limit. Eachtime a new CHANNEL_REQUIRED message comes from the BTSthrough the Abis interface, a software application in the BCSUchecks the number of free message buffers in the unit. When thelower limit (more than 34 unhandled messages) is exceeded, thecauses moc_data, location_update, other_cases andre_establishment will be omitted.



No

COUNTER NAME

RELEASE/CHANGED

003040

BCSU OVERLOAD UPPER LIMIT

S7


EXPLANATION Number of refused calls, when BCSU overload upper limit occurs.When the overload upper limit occurs, all calls are refused.

UPDATED When the call is refused due to BCSU overload upper limit. Eachtime a new CHANNEL_REQUIRED message comes from the BTSthrough the Abis interface, a software application in the BCSUchecks the number of free message buffers in the unit. When theupper limit (more than 53 unhandled messages) is exceeded, nocauses will trigger channel reservation in the BSC.

No

COUNTER NAME

RELEASE/CHANGED

003041

BCSU OVERLOAD DELETED RACH

S7


EXPLANATION Number of deleted RACHs on a CCCH when the RACH load is toohigh and MCMU is protected against overload.

UPDATED When new RACH commands come to the CCCH but there is no freespace on it and the commands are deleted. There can be amaximum of 20 simultaneous requests per CCCH to MCMU. If thereare more requests, the RACHs are deleted and this counter istriggered.

No

COUNTER NAME

RELEASE/CHANGED

003042

TRX DIAGNOSTICS

S8

EXPLANATION Number of the running times of TRX internal diagnostics.

UPDATED When TRX internal diagnostics is started. The base station hasrequested the blocking of the TRX for diagnostics.

RELATED TO A FEATURE BSS8143 Runtime diagnostics and BTS alarms



No

COUNTER NAME

RELEASE/CHANGED

003043

TRX DIAGNOSTICS FAULT

S8

EXPLANATION Number of times that the TRX internal diagnostics has detected afault.

UPDATED When diagnostics is stopped after fault detection. The BTS has senta message informing that the diagnostics has been stopped and thata fault has been detected.

RELATED TO A FEATURE BSS8143 Runtime diagnostics and BTS alarms

No

COUNTER NAME

RELEASE/CHANGED

003044

SUCC SEIZ SUPPLEM SERV

S9

EXPLANATION Number of successful seizures of SDCCHs for supplementaryservice.

UPDATED When an ESTABLISH_INDICATION message with CM servicerequest and service type supplementary service is received onSDCCH from the BTS.

No

COUNTER NAME

RELEASE/CHANGED

003045

TCH SUPPLEM SERV

S9

EXPLANATION Number of successful seizures of TCHs for supplementary servicein FACCH call setup due to SDCCH congestion. If FACCH call setupis turned off, the counter value is zero.

UPDATED When an ESTABLISH_INDICATION message with CM servicerequest and service type supplementary service is received on TCHfrom the BTS.



No

COUNTER NAME

RELEASE/CHANGED

003046

AVE PCH GB LOAD ON CCCH

S9

TRIGGER POINT(S) When CCCH_LOAD_IND message is received by BSC and GPRSsupport is configured on CCCH. See figure CCCH load indication ifGPRS is activated in BTS and other conditions are valid

EXPLANATION Average paging buffer space on Gb-interface. The counter indicatesthe remaining space for paging commands (CS, PS) and DRXAccess Grant. Smaller value means greater load on the PCH.

UPDATED When the value of the PCH Gb load is received in aCCCH_LOAD_IND message from the BTS during the measurementperiod. The new value of the PCH Gb load is added to the previousvalue, and the number of events is increased by one.


RELATED TO A FEATURE BSS9006 GPRS telecom in BCSU and MCMU


No

COUNTER NAME

RELEASE/CHANGED

003047


S9

TRIGGER POINT(S) See figure CCCH load indication if GPRS is activated in BTS andother conditions are valid

EXPLANATION Denominator of average PCH Gb load on CCCH.





No

COUNTER NAME

RELEASE/CHANGED

003048

AVE PAGING GB BUF

S9


EXPLANATION Average buffer occupancy percentage.

It is used to carry information on the load of the PCH associated withthis CCCH timeslot. This information reports the paging bufferoccupancy percentages within the buffer area of approximately 15seconds, in case the GPRS support is configured onto CCCH. Therange of this parameter is 0...100% with 1% intervals. Theoccupancy percentage (occupied buffer space vs. maximum space)of paging buffer is calculated every fourth 51-multiframe. An averageis calculated from these values and reported in CCCH_LOAD_INDmessage.

UPDATED When the value of the average paging Gb buffer load is received in aCCCH_LOAD_IND message from the BTS during measurementperiod. The new value of the average paging Gb buffer load is addedto the previous value, and the number of events is increased by one.




UNIT Percentage

LIMITS 0 - 100

No

COUNTER NAME

RELEASE/CHANGED

003049


S9


EXPLANATION Denominator of average buffer occupancy percentage.





No

COUNTER NAME

RELEASE/CHANGED

003050

MAX PAGING GB BUF

S9


EXPLANATION Maximum buffer occupancy percentage.

It is used to carry information on the load of the PCH associated withthis CCCH timeslot. It is the peak value of all values which arecalculated every fourth 51-multiframe during the concernedCCCH_LOAD_IND reporting period. The range of this parameter is0...100% with 1% intervals.

UPDATED When the value of the maximum paging buffer received in aCCCH_LOAD_INDICATION message exceeds the previous value ofthe paging buffer during the measurement period.


COUNTER TYPE Peak

UNIT Percentage

LIMITS 0 - 100

No

COUNTER NAME

RELEASE/CHANGED

003051

AVE PAGING LOAD AIR

S9

TRIGGER POINT(S) When CCCH_LOAD_IND message is received by BSC and phase 2BTS or newer is supported. See figure CCCH load indication ifGPRS is activated in BTS and other conditions are valid

EXPLANATION Average paging load on CCCH indicated by radio block occupancyfor paging messages.

Radio Block Occupancy carries information on the Radio interfaceload in percents of the associated CCCH timeslot. The radio blockoccupancy percentage for AGCH messages requiring DRX(occupied radio blocks vs. all radio blocks during reporting period) iscalculated and reported in CCCH_LOAD_ IND message.

UPDATED When a CCCH_LOAD_INDICATION message is received from theBTS. The average paging load value is added to the previous valueand the number of events is increased by one.






UNIT Percentage

LIMITS 0 - 100

No

COUNTER NAME

RELEASE/CHANGED

003051

AVE PAGING LOAD AIR

S9

No

COUNTER NAME

RELEASE/CHANGED

003052


S9


EXPLANATION Denominator of average radio interference CCCH load radio blockoccupancy paging.



No

COUNTER NAME

RELEASE/CHANGED

003053

AVE DRX AGCH LOAD AIR

S9

TRIGGER POINT(S) When CCCH_LOAD_IND message is received by BSC and phase 2BTS or newer is supported. See figure CCCH load indication ifGPRS is activated in BTS and other conditions are valid

EXPLANATION Average radio interference CCCH load radio block occupancy DRXAGCH.

It is used to carry information on the Radio interface load of theassociated CCCH timeslot. The range of this parameter is 0...100%with 1% intervals. The radio block occupancy percentage for AGCHmessages requiring DRX (occupied radio blocks vs. all radio blocksduring reporting period) is calculated and reported in CCCH_LOAD_IND message.

UPDATED When a CCCH_LOAD_INDICATION message is received from theBTS. The average DRX AGCH LOAD AIR value is added to theprevious value and the number of events is increased by one.






UNIT Percentage

LIMITS 0 - 100

No

COUNTER NAME

RELEASE/CHANGED

003053

AVE DRX AGCH LOAD AIR

S9

No

COUNTER NAME

RELEASE/CHANGED

003054


S9


EXPLANATION Denominator of average radio interference CCCH load radio blockoccupancy DRX AGCH.


No

COUNTER NAME

RELEASE/CHANGED

003055

AVE NON DRX AGCH LOAD AIR

S9

TRIGGER POINT(S) When CCCH_LOAD_IND message is received by BSC and phase 2BTS or the newer is supported. See figure CCCH load indication ifGPRS is activated in BTS and other conditions are valid

EXPLANATION Average radio interference CCCH load radio block occupancy NON-DRX AGCH.

It is used to carry information on the Radio interface load of theassociated CCCH timeslot. The range of this parameter is 0...100%with 1% intervals. The radio block occupancy percentage for AGCHmessages not requiring DRX (occupied radio blocks vs. all radioblocks during reporting period) is calculated and reported inCCCH_LOAD_ IND message.

UPDATED When a CCCH_LOAD_INDICATION message is received from theBTS. The average NON DRX AGCH LOAD AIR value is added to theprevious value and the number of events is increased by one.






UNIT Percentage

LIMITS 0 - 100

No

COUNTER NAME

RELEASE/CHANGED

003055

AVE NON DRX AGCH LOAD AIR

S9

No

COUNTER NAME

RELEASE/CHANGED

003056


S9


EXPLANATION Denominator of average radio interference CCCH load radio blockoccupancy NON-DRX AGCH.



No

COUNTER NAME

RELEASE/CHANGED

003057

PS PAGING MSG SENT

S9

TRIGGER POINT(S) When a PS-PAGING COMMAND message is sent from the BSC tothe BTS. See figure PS paging in GPRS

EXPLANATION This message is sent from the BSC/PCU to the BTS to request PSpaging of a GPRS MS.

UPDATED When a PS-PAGING COMMAND message is sent to the BTS. TheMS needs to be paged only when it is in MM-idle state. A GPRSpaging message is sent only to cells that support GPRS services.




No

COUNTER NAME

RELEASE/CHANGED

003058

CS PAGING MSG SENT

S9

TRIGGER POINT(S) When a CS-PAGING COMMAND message is sent from BSC to theBTS. See figure CS Paging in GPRS

EXPLANATION This message is sent from BSC/PCU to BTS to request CS paging ofa GPRS MS.

UPDATED When a CS-PAGING COMMAND is sent to the BTS.


No

COUNTER NAME

RELEASE/CHANGED

003059

CALL ASSIGN AFTER SMS

S10.5

EXPLANATION Number of calls started directly after an SMS on the alreadyreserved SDCCH.

UPDATED When an ASSIGNMENT REQUEST message is received directlyafter a successful SMS on SDCCH from the MSC.

No

COUNTER NAME

RELEASE/CHANGED

003060

SPARE003060

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

003061

SPARE003061

EXPLANATION Spare



Related topics



No

COUNTER NAME

RELEASE/CHANGED

003062

SPARE003062

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

003063

SPARE003063

EXPLANATION Spare



3 Signalling charts of Resource AccessMeasurement

The following figures show the signalling charts of Resource AccessMeasurement:



Figure 1. Basic call without counters.

BSC:MS: BTS: MSC:

PagingPaging commandPaging request

Channel requestChannel required

Channel activation

Immediate assign

SetupSetup

Call proceeding Call proceeding

Assignment requestPhysical context request

Physical context confirm

Channel activation

Channel activation ack

Assignment command

Ua

Sabm Establish indication

Ua

Assignment complete Assignment complete

Rf channel release

Rf channel release ack

Identification requestIdentification request

Identification response Identification response

Encryption command

Paging part

Radio access part on CCCH


Immediate assign command

Sabm Establish indication Paging response

Authentication requestAuthentification request

Authentification response

SDCCH signalling part

DDCH establishment part

TCH seized, FACCH signalling part

Ciphering mode command

Ciphering mode complete

Authentication response

Ciphering mode command

Ciphering mode complete



Figure 2. Basic call without counters (cont.).

Alert Alert

Connect Connect

Connect ackConnect ack

Release complete

Clear command

Clear complete

Channel release

Deactivate SACCH

Ua

Release indication

Rf channel release

Rf channel release ack

Disconnect Disconnect

ReleaseRelease

Release complete

BSC:MS: BTS: MSC:

Disc

Conversation phase

Release by MS



Figure 3. Basic call with counters.

BTS: MSC:MS: BSC:

PagingPaging command

Paging request

Channel requestChannel required

Channel activationChannel activation ack

Immediate assign

SabmEstablish indication

Paging responseUa

Paging part

Paging messages sent to BTS003000


Channel request messagesreceived from BTS

003004


Immediate assignment messagesent to BTS

003001


SDCCH signalling part

TCH seized, FACCH signalling part

Conversation phase

Release by MS

Success seizure for MTC003012

or Success seizure for MOC003013

or SDCCH location update003019

or SDCCH call re-establishment003020

or SDCCH emergency call003021

or IMSI detach SDCCH003033



Figure 4. FACCH call setup due to SDCCH congestion.

BTS:MS: BSC: MSC:

Sabm

Establish indication

Paging response

Ua


Paging part


TCH signalling part

Conversation phase

Release by MS

TCH emergency call003022

orTCH MTC

003023or

TCH MOC003024

orTCH call re-establishm.

003025or

IMSI detach TCH003034



Figure 5. Ghost reservation.

Counter 003031 is updated if distance verifying is activated in the resourceallocation feature and the channel request is rejected due to the distance betweenthe MS and BTS.

Ghost

Channel required

BSC:MS: MSC:BTS:


Paging part

Rej seiz att due dist003031

GHOST CCCH reservation003030


003004



Figure 6. Busy AGCH-channel.

Channel required

Channel activation

Channel request

Delete indication

MS: BSC: MSC:BTS:


Paging part



Immediate assignmentmessages sent to BTS

003001

Delete indication messagesreceived from BTS

003005


003004



Figure 7. Unsuccessful channel request.

Figure 8. SMS broadcast.

Channel required

Channel request

BSC: MS: MSC:BTS:


Paging part

Immediate assignment reject


003004

Immediate assignment rejectmessages sent to BTS

003002

BSC: MS: MSC:BTS:

SMS broadcast request




SMS CB request messagessent to the BTS

003003



Figure 9. Mobile originating SMS on a TCH.

Cp data

Cm serv req

Ua (SAPI = 3)

Sabm (SAPI = 3)


Cp data

Cp ack Cp ack

Cp data Cp data

Cp ackCp ack

Cm serv req

Cm serv ackCm serv ack

BSC: MS: MSC:BTS:

Active call

Successful TCH SMS003026

Active call continuous



Figure 10. Mobile terminating SMS on a TCH.

Cp data

Establish request

Sabm (SAPI = 3)

Ua (SAPI = 3)

Establish confirm

Cp data

Cp ack Cp ack

Cp data Cp data

Cp ackCp ack

BTS: MSC: MS: BSC:

Active call





Figure 11. Mobile originating SMS on FACCH.

MS starts SMS by sending SABM with SAPI = 3

SMS release

Cp ack

Cp ack

Cp data

Cp data

Cp ack

Cp ack

Cp data


Sabm (SAPI = 3)

FACCH call setup

Ua (SAPI = 3)

Instead of sending SETUP -message,

Cp data

BSC:MS: MSC:BTS:




Figure 12. Mobile terminating SMS on FACCH.

Establish request

MSC starts SMS by sending CP DATA -message

SMS release

Cp ack

Cp ack

Cp data

Cp data

Cp ack

Cp ack

Cp data

Establish confirm

Ua (SAPI = 3)

FACCH call setup

Sabm (SAPI = 3)


Cp data

BTS: MSC:MS: BSC:




Figure 13. Mobile originating SMS on an SDCCH.

Cp data

Ua (SAPI = 3)

Sabm (SAPI = 3)


Cp data

Cp ack Cp ack

Cp data Cp data

Cp ackCp ack

BTS: MSC: MS: BSC:


Connection is set up as in normal MOC

SMS release


Successful SDCCH SMS003028



Figure 14. Mobile terminating SMS on an SDCCH.

Cp data

Sabm (SAPI = 3)

Ua (SAPI = 3)

Establish confirm

Cp data

Cp ack Cp ack

Cp data Cp data

Cp ackCp ack

Establish request

BSC: MS: MSC:BTS:


Connection is set up as in normal MTC

SMS release


Successful SDCCH SMS003028



Figure 15. Mobile originating unsuccessful SMS on a TCH.

In the figure a failure can occur between the first and last position, causingcounter 3027 to be updated immediately. Signalling between the first and lastposition can be partly missing depending on where the failure takes place.Possible situations are: ERROR_INDICATION, RELEASE_INDICATION orCONNECTION_ FAILURE message during an SMS, and corruptedESTABLISH_ INDICATION message.

Cm serv ack Cm serv ack

Cm serv req

Cp ack

Cp ack

Cp data

Cp data

Cp ack

Cp ack

Cp data


Sabm (SAPI = 3)

Ua (SAPI = 3)

Cm serv req

Cp data

BTS: MSC:MS: BSC:

Active call

First position

Last position




Figure 16. Mobile terminating unsuccessful SMS on a TCH.


Cp data

Establish request

Sabm (SAPI = 3)

Ua (SAPI = 3)

Establish confirm

Cp data

Cp ack Cp ack

Cp data Cp data

Cp ackCp ack

BTS: MSC: MS: BSC:

Last position

First position

Active call




Figure 17. Mobile originating unsuccessful SMS on FACCH.


Cp data

Ua (SAPI = 3)

Sabm (SAPI = 3)


Cp data

Cp ack Cp ack

Cp data Cp data

Cp ackCp ack

BTS: MSC: MS: BSC:

SMS release


FACCH call setup


Unsuccessful TCH SMS003027



Figure 18. Mobile terminating unsuccessful SMS on FACCH.

In the figure a failure can occur between the first and last position, causingcounter 3027 to be updated immediately. Signalling between the first and lastposition can be partly missing depending on where the failure happens. Possiblesituations are: ERROR_INDICATION, RELEASE_INDICATION orCONNECTION_ FAILURE message during an SMS, and corruptedESTABLISH_ INDICATION message.

MS: BTS: BSC: MSC:

FACCH call setup



Cp data

Establish request

First position

Sabm (SAPI = 3)

Ua (SAPI = 3)

Establish confirm

Last position

SMS release



Figure 19. Mobile originating unsuccessful SMS on an SDCCH.

Message data corrupted in the ESTABLISH_INDICATION message.

Cp data

Ua (SAPI = 3)

Sabm (SAPI = 3)


Cp data

Cp ack

Cp ack

Cp data

Cp data

Cp ack

Cp ack

BTS: MSC: MS: BSC:

SMS release


Connection is set up as in normal MOC


Unsuccessful SDCCH SMS003029



Figure 20. Mobile terminating unsuccessful SMS on an SDCCH.

In the figure a failure can occur between the first and last position, causingcounter 3029 to be updated immediately. Signalling between the first and lastposition can be partly missing depending on where the failure takes place. Suchsituations can be caused by timer expiries while waiting forESTABLISH_CONFIRM message, an ERROR_INDICATION orRELEASE_INDICATION message that is received instead of anESTABLISH_CONFIRM message, or a corrupted ESTABLISH_CONFIRMmessage.

Cp data

Establish request

Sabm (SAPI = 3)

Ua (SAPI = 3)

Establish confirm

MS: BTS: BSC: MSC:

Connection is set up as in normal MTC



SMS release

First position

Last position



Figure 21. CCCH load indication.

CCCH load indication

MS: BTS: BSC: MSC:

Paging part


Ave nbr of RACH slots on CCCH003006

Denom of ave RACH slot number003007

Average PCH load on a CCCH003008

Denom of ave PCH load on CCCH003009

Peak value of number of busyRACHs on CCCH

003010

Ave nbr of busy RACHs on CCCH003014

Denom of ave nbr of busy RACHs003015

Nbr of ave RACH acc on CCCH003016

Denom of count of ave RACH acc003017

Min size of paging buffer on CCCH003018

Number of max paging buffer capa003035

Average paging buffer capacity003036

Denom of count of ave paging buffer003037

Number of deleted paging command003038



Counters 003035, 003036, 003037 and 003038 can be updated only with phase 2BTS or newer versions. Counters 003051-003056 can be updated if the BTSversion is of phase 2. Note: Counter 003008 contains paging load informationwhen paging comes through the Gb-interface and the GPRS is disabled in BTS,even if the BTS level is GPRS PH 1.



Figure 22. CCCH Load Indication if GPRS is activated in BTS and othercondititions are valid.

Counters 003006-003010, 003014-003018 and 003035-003038 can also beupdated.

MS: BTS: BSC: MSC:

Paging part


CCCH load indication

Ave PCH Gb load on CCCH003046

Denom of ave DRX AGCHload air003054

Ave non DRX AGCH load air003055

Denom of ave non DRXAGCH load air

003056

Denom of ave PCH Gb loadon CCCH003047

Ave DRX AGCH load air003053

Ave paging Gb buffer003048

Denom of ave paging Gbbuffer

003049

Maximum paging Gb buffer003050

Ave paging load air003051

Denom of ave paging load air003052



Figure 23. Unsuccessful channel requests due to BCSU overload.

Figure 24. PS Paging in GPRS

Channel request

Channel required

MS: BTS: BSC: MSC:

Paging part


Channel req msg received from BTS003004

BCSU overload lower limit003039

orBCSU overload upper limit

003040

BCSU overload deleted RACH003041

Paging command PS Paging

MS: BTS: BSC: SGSN:

Paging part

Ps paging msg sent003057



Figure 25. CS Paging in GPRS.

Note: If the GPRS level is GPRS PH1 but the GPRS is disabled in BTS, a normalpaging command message is sent to the BTS.

Related topics



MS: BTS: BSC: SGSN: MSC:

Paging part

CS PagingCS PagingPaging command

Cs paging msg sent003058


counter resource access

Documents

partly missing

bss7043 measurement

resource access

mobile originating

mobile terminating

occupied radio

bss8143 runtime

ms starts