3g psr checkpoints

7
S No. Step/Description 1 Paging Timers Check 2 3 BTDM to be changed from 120 to 60 4 T3212 to be changed from 20 to 10 5 MP Load 6 Signaling Link Utilisation 7 8 EOS Check 9 SAE Check 10 11 UTRAN Rejections 12 13 14 3G PCH Capacity / Paging Congestion 15 CCSP Load 16 17 Software Correction Check in MSC-S 18 RRC connection Establishment Success Rate 19 Admission control feature 20 SCCP Establishment Success Rate 21 URA_PCH Mode (Active/Not) 22 23 Paging Intensity - No. of pages per second 24 RAB Assignment Success Rate 25 NBAP Failures 26 RANAP 27 t305 (periodic URA update) timer Paging Strategy to be changed from repeated Global to Local with IMSI LAC Duplicacy - Definition of LAC 33013 to be removed from HPRSM01 LAC Boundry - LAC-33012 is serving two disconnected areas in HP. Analysis of Paging Attempt Counters at RNC level 2) Number of preconfigured subsequent transmissions of the same Paging Record inactivityTimerPch & inactivityTimer, • hsdschInactivityTimer

Upload: violetchuwa

Post on 06-Nov-2015

261 views

Category:

Documents


9 download

DESCRIPTION

psr check points for 3g

TRANSCRIPT

3G PSRS No.Step/DescriptionCommands/CountersComments1Paging Timers Check2Paging Strategy to be changed from repeated Global to Local with IMSI3BTDM to be changed from 120 to 604T3212 to be changed from 20 to 10Closed5MP LoadPending6Signaling Link UtilisationOngoing7LAC Duplicacy - Definition of LAC 33013 to be removed from HPRSM018EOS Check9SAE Check10LAC Boundry - LAC-33012 is serving two disconnected areas in HP.11UTRAN RejectionspmNoPagingAttemptUtranRejected12Analysis of Paging Attempt Counters at RNC level13Paging without paging area ID (Paging Type 2)143G PCH Capacity / Paging Congestionpcong = {pmNoPagingAttemptUtranRejected/(npag*ncell)}npag = pmCnInitPagingToIdleUeLa + pmCnInitPagingToIdleUe ++ pmCnInitPagingToIdleUeRa + pmCnInitPagingToUraUe ++ pmUtranInitPagingToUraUe15CCSP Load16Number of preconfigured subsequent transmissions of the same Paging Recordget . NoOfPagingRecordTransm17Software Correction Check in MSC-S18RRC connection Establishment Success Rate:pmTotNoTermRrcConnectReq, pmTotNoTermRrcConnectReqSucc, pmTotNoTermRrcConnectReqCs, pmTotNoTermRrcConnectReqCsSucc19Admission control feature20SCCP Establishment Success Rate21URA_PCH Mode (Active/Not)get RncFeature=RabCombination021, get uerc label uraAlso check the following counters : pmCnInitPagingToUraUe, pmSamplesRabUra, pmSumRabUra, pmUtranInitPagingToUraUe, pmNoUraUpdSuccess, pmNoUraUpdAttempt, pmNoSystemRabReleasePacketUra, pmNoNormalRabR22inactivityTimerPch & inactivityTimer, hsdschInactivityTimerget . inactivityTimerPch, get . Inactivitytimer, get ChannelSwitchingValid only when URA_PCH mode is active and working23Paging Intensity - No. of pages per secondPaging Intensity [pages/sec] = the number of paging records /t Npag = (pmCnInitPagingToIdleUeLa + pmCnInitPagingToIdleUe+ pmCnInitPagingToIdleUeRa)*noOfPagingRecordTransm24RAB Assignment Success RatepmNoFailedRabEstAttemptLackDlChnlCode, pmNoFailedRabEstAttemptLackDlPwr, pmNoFailedRabEstAttemptLackDlAse, pmNoFailedRabEstAttemptLackUlAse, pmNoFailedRabEstAttemptExceedConnLimit, pmSumCompMode / pmSamplesCompMode (Number of CM Users per Cell), pmNoOfNon25NBAP FailurespmNoOfDiscardedNbapcMessages26RANAPCounters for monitoring abnormal RANAP release : pmNoSystemNasSignReleaseCs, pmNoSystemNasSignReleasePs, pmNoSystemRabReleaseSpeech, pmNoSystemRabReleaseAmrNb, pmNoSystemRabReleaseCs64, pmNoSystemRabReleaseCsStream, pmNoSystemRabReleasePacket, pmNoSystem27t305 (periodic URA update) timerget . T305Valid only when URA_PCH mode is active and working28utranDrxCycleLength (For UTRAN initiated paging)get . utranDrxCycleLengthValid only when URA_PCH mode is active and working29Paging Area Dimensioning30Inappropriate CN paging retransmission31Inappropriate time interval setting32Inappropriate Utran paging retransmission and time interval setting33DRX Circle Value unreasonable settingcnDrxCycleLengthCs (for CS) and cnDrxCycleLengthPs (for PS).34NP Value reasonable35CN use whole-network paging36CN pages with the wrong UE identifier37PCH/PICH channel power is set too low38Coverage Hole39UE Performance40Implied Shutdown Timer(Related to Paging Success Rate)41UE Location Area Updating Timer42Physical Paging Channel Power Setting(PICH and S-CCPCH)pich power and pch power43UE Accessibility Parameter: Maximum Access Attempts, Preamble Power, etc

MBD000EDDB8.doc

RNC Paging analysis

During last months we had increased number of subscribes which are unreachable, although they were under network coverage and they were not moving at that moment.

Paging statistics were the same as before, which means that results were between 94% to 98% which represents good KPI for paging. By that time paging statistics were recorded only on MSC nodes, so we got idea to activate paging statistics on RNC also in order to get more detailed picture regarding paging messages in the radio network.

Paging::pmNoPageDiscardCmpLoadC

Number of paging messages that are rejected because of MP overload

LocationArea::pmCnInitPagingToIdleUeLa

Number of CS paging messages received from CN

RoutingArea::pmCnInitPagingToIdleUeRa

Number of PS paging messages received from CN

Paging::pmCnInitPagingToIdleUe

Number of paging messages without paging area ID

Utrancell::pmNoPagingAttemptCnInitDcch

Number of paging messages sent via DCCH for active UE

Utrancell::pmNoPagingAttemptUtranRejected

Number of unsuccessful pagings due to congestion on radio part

Utrancell::pmNoPagingType1Attempt

Number of paging attempts for idle UE

Utrancell::pmTotNoTermRrcConnectReq

Number of terminating requests for RRC connections

Utrancell::pmTotNoTermRrcConnectReqSucc

Number of successful terminating requests for RRC connections

Utrancell::pmTotNoTermRrcConnectReqCs

Number of terminating RRC requests for Cs

Utrancell::pmTotNoTermRrcConnectReqCsSucc

Number of successful terminating requests for RRC connections for Cs

Utrancell::pmTotNoTermRrcConnectReqPs

Number of terminating RRC requests for Ps

Utrancell::pmTotNoTermRrcConnectReqPsSucc

Number of successful terminating requests for RRC connections for Ps

In order to make valid analysis we compared statistics derived from protocol analyzer measurements on IuCS interface and statistics derived from RNC. In embedded files you can see results of this measurements.

Comparing results from both ways of statistics measurement weve come to following:

Total number of paging requests from CN to RNC measured on PA and RNC are matching with error less then 0.3%

Total number of paging requests for Cs calls is matching with error of 5%

From the total number of paging requests 80% are for terminating SMS which belongs to class low priority signaling

The rest of 20% belongs to the Cs calls and here success rate for paging is over 99% which can be seen in the report ( paging_report_19052010.pdf ) in column RRC success for terminating calls. Similar values are for Ps calls.

Column Total Page Answer from Business Objects report doesnt show proper values because counter pmToNoTermRrcConnectReq doesnt increment correctly which is described in TR HJ67532

Formulas that are used for BO reports are:

1.Global RNC RRC Connection sucess rate

RrcSucc = RrcSuc

2.Terminating traffic RRC Connection sucess rate

RrcSuccTerm = 100 * sum_time_pmTotNoTermRrcConnectReqSucc / sum_time_pmTotNoTermRrcConnectReq

3.Total number of UE access for Paging Response

TotalPageAnswer = sum_time_pmTotNoTermRrcConnectReq

4.Total number of UE access for Paging Response, sent to Core after succesfull RRC connection

TotalPageAnswerToCore = sum_time_pmTotNoTermRrcConnectReqSucc

5.Paging Requests discarded for Central MP load

TotalPageDiscardCentralMpPLoad = pmNoPageDiscardCmpLoadC

6.Paging Requests discarded for Paging Channel queue congestion

TotalPageRejectUtrancell = sum_time_pmNoPagingAttemptUtranRejected

7.Total number of Paging Requests for idle UE

TotalPageType1 = pmCnInitPagingToIdleUeLa + pmCnInitPagingToIdleUeRa + pmCnInitPagingToIdleUe

8.Total number of Paging Requests for active UE

TotalPageType2 = sum_time_pmNoPagingAttemptCnInitDcch

9.Total number of Paging Requests received from CORE

TotalPageReqFromCore = TotalPageDiscardCentralMpPLoad + TotalPageType1 + TotalPageType2

10.Rate of Paging Response received from UE per Paging Request received from COREs

PagingSuccessRate = 100 * TotalPageAnswer / (TotalPageDiscardCentralMpPLoad + TotalPageType1)

11. Rate of Paging Response returned by the RNC to CORE per Paging Request received from COREs

PagingSuccessRatePostRrc = 100 * TotalPageAnswerToCore / (TotalPageDiscardCentralMpPLoad + TotalPageType1)

According to this results we can see that total paging response rate is between 92% and 94%, and for Cs and Ps calls is 99%. Since contribution of SMSs in total number of pagings is over 80% it means that SMSs are the most responsible for bad results in total paging response statistics.

_1361278718.xls

doc_0

Time_LA(Paging Statistics and Location Updating, LA)LA(Paging Statistics and Location Updating, LA)TotalFirstPageAttemptsPaging Success(%)SuccessfulFirst PageofTotalFirst Page Attempts(%)RepeatedPagesof TotalFirstPage Attempts(%)SuccessfulRepeatedPage(%)Location Update Success(%)TotalLocationUpdates

2010-05-1907:00 PM220032010126,28897.5194.185.5859.7898.6962,947

2010-05-1908:00 PM220032010125,07596.9393.446.3454.9398.5957,545

2010-05-1909:00 PM220032010122,74397.2994.075.7256.2298.4651,294

2010-05-1910:00 PM220032010120,88497.794.295.5161.7798.7145,159

2010-05-1911:00 PM220032010117,58897.8894.395.4364.1998.4833,617

2010-05-1907:00 PM220032010225,58296.8193.666.3449.7897.8161,191

2010-05-1908:00 PM220032010224,75797.3993.98656.9797.5653,517

2010-05-1909:00 PM220032010223,13097.2794.595.3749.9297.3143,744

2010-05-1910:00 PM220032010220,09597.5994.515.556.0297.4738,635

2010-05-1911:00 PM220032010215,31797.9394.994.9958.8296.5330,725

2010-05-1907:00 PM220034030110,29596.4792.77.2652.0799.1722,443

2010-05-1908:00 PM22003403019,83697.392.937.0561.999.1519,899

2010-05-1909:00 PM22003403019,41497.3392.937.1361.8599.0917,321

2010-05-1910:00 PM22003403017,69297.2392.127.8565.0799.0713,925

2010-05-1911:00 PM22003403016,19397.3892.837.2263.0998.8210,688

2010-05-1907:00 PM22003403031,13392.8587.211.5648.85999,456

2010-05-1908:00 PM22003403031,20793.2185.513.7556.0299.368,803

2010-05-1909:00 PM22003403031,29396.3787.713.0766.2799.537,427

2010-05-1910:00 PM22003403031,00295.2190.129.3854.2699.595,380

2010-05-1911:00 PM220034030366893.4186.8312.2853.6699.254,526

2010-05-1907:00 PM220034030412,08796.2592.27.6852.899.0617,326

2010-05-1908:00 PM220034030412,32596.3192.847.0848.9198.9615,552

2010-05-1909:00 PM220034030411,25996.9492.877.0158.0599.4513,314

2010-05-1910:00 PM220034030410,25597.2493.166.8659.4699.0410,409

2010-05-1911:00 PM22003403047,15997.0892.97.0359.4497.668,034

2010-05-1907:00 PM220034030618,44897.0292.597.2161.4698.935,252

2010-05-1908:00 PM220034030617,89197.3693.046.9262.5298.5332,530

2010-05-1909:00 PM220034030617,46696.792.467.1659.2398.7929,750

2010-05-1910:00 PM220034030615,15497.1492.147.7164.998.6124,131

2010-05-1911:00 PM220034030611,55197.9893.526.3270.6897.619,614

2010-05-1907:00 PM220035801286,61196.6193.356.5449.8396.55168,660

2010-05-1908:00 PM220035801283,93196.4593.136.7549.1796.32153,264

2010-05-1909:00 PM220035801280,91396.5793.16.795196.18135,120

2010-05-1910:00 PM220035801269,69296.8793.366.5253.8496.4118,537

2010-05-1911:00 PM220035801256,05897.4494.15.7757.9595.9194,146

2010-05-1907:00 PM220035801753,44897.0293.836.1252.1597.3991,749

2010-05-1908:00 PM220035801751,33796.9894.115.8449.1797.5283,850

2010-05-1909:00 PM220035801748,74397.193.786.2253.4597.5175,614

2010-05-1910:00 PM220035801743,46397.3993.866.1257.7697.5468,494

2010-05-1911:00 PM220035801734,60997.9994.755.2162.1597.4254,915

2010-05-1907:00 PM220036101370,53295.7992.587.3143.8993.5978,656

2010-05-1908:00 PM220036101372,93596.0692.857.0245.6993.575,147

2010-05-1909:00 PM220036101370,01796.1692.697.1648.4893.6771,452

2010-05-1910:00 PM220036101360,89596.1892.926.9446.8993.7262,561

2010-05-1911:00 PM220036101343,36196.6192.986.9452.2694.0555,750

2010-05-1907:00 PM2200361026110,08394.5691.128.6939.5695.36142,239

2010-05-1908:00 PM2200361026112,02595.491.888.0243.9395.41129,372

2010-05-1909:00 PM2200361026107,98795.691.947.9745.9395.67116,507

2010-05-1910:00 PM220036102695,32695.8592.247.6946.9495.6298,197

2010-05-1911:00 PM220036102669,36896.1892.357.5650.6195.5483,654

2010-05-1907:00 PM220036102740,30392.0988.6711.2230.4689.546,990

2010-05-1908:00 PM220036102740,83192.7689.3310.532.690.443,664

2010-05-1909:00 PM220036102739,20092.9689.410.5133.8790.4739,668

2010-05-1910:00 PM220036102733,27593.1789.6310.2234.6591.5635,421

2010-05-1911:00 PM220036102723,50894.4990.779.1740.691.5231,821

_1361278725/Paging_report_19052010.pdf

3G_Paging

RNC Time Pmcninitpagingtoidleuela PmcninitpagingtoidleueraRNCBZ01 19/05/2010 19:00 53322 3138RNCBZ01 19/05/2010 20:00 51312 3285RNCBZ01 19/05/2010 21:00 47118 3490RNCBZ01 19/05/2010 22:00 41880 3295

Measurement period: 5/19/2010 7:00:00 PM - 5/19/2010 11:00:00 PM21/05/2010 10:00Last refresh:

1

Pmcninitpagingtoidleuera Pmcninitpagingtoidleue TotalPageType1 TotalPageAnswer TotalPageAnswerToCore PagingSuccessRatePostRrc3138 0 56460 70913 52540 93.06 %3285 0 54597 69464 50633 92.74 %3490 0 50608 65043 46796 92.47 %3295 0 45175 59731 42059 93.10 %

2

PagingSuccessRatePostRrcPmtotnotermrrcconnectreqcsPmtotnotermrrcconnectreqcssuccRRC success for terminating Cs calls93.06 % 13257 13210 99.65 %92.74 % 11742 11682 99.49 %92.47 % 9477 9418 99.38 %93.10 % 6490 6443 99.28 %

3

RRC success for terminating Cs callsPmtotnotermrrcconnectreqpssuccPmtotnotermrrcconnectreqpsRRC success for terminating Ps calls99.65 % 1633 1641 99.51 %99.49 % 1690 1696 99.65 %99.38 % 1620 1632 99.26 %99.28 % 1461 1467 99.59 %

4

3G_paging