Vous êtes sur la page 1sur 1

Performance Statistics - Flowcharts for Counters

RRC Connection Setup is triggered by RRC Connection Request message pmTotNoRrcReq + pmTotNoRrcConnectReq + pmTotNoTermRrcConnectReq + pmTotNoRrcConnectReqCs + pmTotNoTermRrcConnectReqCs + pmTotNoRrcConnectReqSubTr + Check with Load Control

UE

RRC CONNECTION REQUEST

SRNC

Increment only once, even if repeated RRC Connection Requests. For pmTotNoRrcConnectReq, step for all Establishment Causes. For pmTotNoRrcConnectReqCs, step for Establishment Cause = Emergency Call or Originating or Terminating Conversational Call. For pmTotNoTermRrcConnectReq, step for cause = Terminating Conversational Call, Terminating Streaming Call, Terminating Interactive Call, Terminating Background Call, Terminating High Priority Signalling, Terminating Low Priority Signalling or Terminating - cause unknown. For pmTotNoTermRrcConnectReqCs, step for cause = Terminating Conversational Call. For pmTotNoRrcConnectReqSubTr, step for couse = Originating Subscribed Traffic Call. pmNoRrcCsReqDeniedAdm+ pmNoRrcReqDeniedAdm+ pmNoReqDeniedAdm+

pmNoRejRrcConnMpLoadC +

NO

Successful Load Control? YES Successful Admission Control? YES Radio Link Setup NO

Release of already allocated resources

Admission reject as a result of load sharing? NO

YES

pmNoLoadSharingRrcConn + pmNoLoadSharingRrcConnCs +

Release of already allocated resources Admission reject due to Unisaal/Sctp congestion? YES NO Admission reject due to other reason? NO YES

pmTotNoUtranRejRrcConnReq +

Step the relevant counter(s): pmNoRrcConnReqBlockTnCs + pmNoRrcConnReqBlockNodeCs + YES Successful setup? YES Send RRC Connection SRNC Setup and start timer pmTotNoRrcConnectSetup + NO Failed due to TN block? NO

UE

RRC CONNECTION SETUP

pmNoFailedRrcConnectReqHw + pmNoFailedRrcConnectReqCsHw + or pmNoRrcReqDeniedAdmDlPwr + or pmNoRrcReqDeniedAdmDlChnlCode+ or pmNoRrcReqDeniedAdmDlHw + or pmNoRrcReqDeniedAdmUlHw +

RBS

RADIO LINK RESTORE INDICATION

SRNC
RRC Connection Setup Complete and NBAP Radio Link Restore Indication are received before timer SRNC expires? YES NO pmTotNoRrcConnectUeCapability + *

UE

RRC CONNECTION SETUP COMPLETE

pmTotNoRrcConnectUeCapability + *

Send RRC connection Release, UE start timer, receive RRC Connection Release UE Complete/timer expires

RRC CONNECTION RELEASE

SRNC

RRC CONNECTION SRNC RELEASE COMPLETE

Increment only once even if repeated RRC Connection Requests

pmTotNoRrcConnectReqSucc + pmTotNoTermRrcConnectReqSucc + pmTotNoRrcConnectReqCsSucc + pmTotNoTermRrcConnectReqCsSucc +

Release of already allocated resources

UE

RRC CONNECTION REJECT

SRNC

If timer does not expire: pmTotNoUtranRejRrcConnReq +

End RRC Connection Setup

*) Stepped for Establishement Cause = Originating or Terminating Conversational Call, Emergency, Subscribed, Originating or Terminating Interactive/Background Call.
C 00 01114M

Figure 3 10

RRC Connection Setup - CS Scenario


103/1551-AXD 105 03/1 Uen E | 2010-03-08

Vous aimerez peut-être aussi