Flowgraphs Counters RRC Setup CS
1
Performance Statistics - Flowcharts for Counters C 00 01114M End RRC Connection Setup YES pmTotNoRrcConnectReqSucc + pmTotNoTermRrcConnectReqSucc + pmTotNoRrcConnectReqCsSucc + pmTotNoTermRrcConnectReqCsSucc + Release of already allocated resources RRC CONNECTION SETUP SRNC UE RRC CONNECTION SETUP COMPLETE SRNC UE RADIO LINK RESTORE INDICATION SRNC RBS Increment only once even if repeated RRC Connection Requests RRC CONNECTION REJECT SRNC UE pmTotNoUtranRejRrcConnReq + If timer does not expire: NO YES YES NO Send RRC Connection Setup and start timer RRC CONNECTION RELEASE SRNC UE RRC CONNECTION RELEASE COMPLETE SRNC UE Send RRC connection Release, start timer, receive RRC Connection Release Complete/timer expires Successful Admission Control? NO YES pmNoRrcCsReqDeniedAdm+ pmNoRrcReqDeniedAdm+ pmNoReqDeniedAdm+ Failed due to TN block? NO YES Step the relevant counter(s): pmNoRrcConnReqBlockTnCs + pmNoRrcConnReqBlockNodeCs + YES Admission reject due to Unisaal/Sctp congestion? NO NO YES RRC Connection Setup is triggered by RRC Connection Request message YES pmTotNoRrcConnectReq + pmTotNoTermRrcConnectReq + pmTotNoRrcConnectReqCs + pmTotNoTermRrcConnectReqCs + pmTotNoRrcConnectReqSubTr + RRC CONNECTION REQUEST SRNC UE 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’. pmNoRejRrcConnMpLoadC + NO Release of already allocated resources Successful Load Control? Release of already allocated resources pmNoLoadSharingRrcConn + pmNoLoadSharingRrcConnCs + Check with Load Control Admission reject as a result of load sharing? Radio Link Setup pmNoFailedRrcConnectReqHw + pmNoFailedRrcConnectReqCsHw + or pmNoRrcReqDeniedAdmDlPwr + or pmNoRrcReqDeniedAdmDlChnlCode+ or pmNoRrcReqDeniedAdmDlHw + or pmNoRrcReqDeniedAdmUlHw + Successful setup? Admission reject due to other reason? pmTotNoRrcConnectSetup + pmTotNoUtranRejRrcConnReq + pmTotNoRrcReq + NO RRC Connection Setup Complete and NBAP Radio Link Restore Indication are received before timer expires? *) Stepped for Establishement Cause = Originating or Terminating Conversational Call, Emergency, Subscribed, Originating or Terminating Interactive/Background Call. pmTotNoRrcConnectUeCapability + * pmTotNoRrcConnectUeCapability + * Figure 3 RRC Connection Setup - CS Scenario 10 103/1551-AXD 105 03/1 Uen E | 2010-03-08
Transcript of Flowgraphs Counters RRC Setup CS
Performance Statistics - Flowcharts for Counters
C 00 01114M
End RRC Connection Setup
YES
pmTotNoRrcConnectReqSucc +pmTotNoTermRrcConnectReqSucc +pmTotNoRrcConnectReqCsSucc +
pmTotNoTermRrcConnectReqCsSucc +
Release of alreadyallocated resources
RRC CONNECTIONSETUP
SRNCUE
RRC CONNECTIONSETUP COMPLETE
SRNCUE
RADIO LINKRESTOREINDICATION
SRNCRBS
Increment only onceeven if repeated RRCConnection Requests
RRC CONNECTIONREJECT
SRNCUEpmTotNoUtranRejRrcConnReq +
If timer does not expire:
NO
YES
YES
NO
Send RRC ConnectionSetup and start timer
RRC CONNECTIONRELEASE
SRNCUE
RRC CONNECTIONRELEASE COMPLETE
SRNCUE
Send RRC connection Release,start timer, receive RRC
Connection ReleaseComplete/timer expires
SuccessfulAdmission Control?
NO
YES
pmNoRrcCsReqDeniedAdm+pmNoRrcReqDeniedAdm+
pmNoReqDeniedAdm+
Failed dueto TN block?
NO
YES
Step the relevant counter(s):pmNoRrcConnReqBlockTnCs +
pmNoRrcConnReqBlockNodeCs +
YES
Admission reject
due to Unisaal/Sctp
congestion?
NO
NO
YES
RRC Connection Setup is triggeredby RRC Connection Request message
YES
pmTotNoRrcConnectReq +pmTotNoTermRrcConnectReq +pmTotNoRrcConnectReqCs +
pmTotNoTermRrcConnectReqCs +pmTotNoRrcConnectReqSubTr +
RRC CONNECTIONREQUEST
SRNCUE
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 = ‘TerminatingConversational Call’.For pmTotNoRrcConnectReqSubTr, step for couse = ‘Originating Subscribed Traffic Call’.
pmNoRejRrcConnMpLoadC +NO
Release of alreadyallocated resources
SuccessfulLoad Control?
Release of alreadyallocated resources
pmNoLoadSharingRrcConn +pmNoLoadSharingRrcConnCs +
Check with Load Control
Admissionreject as a result of
load sharing?
Radio Link Setup
pmNoFailedRrcConnectReqHw +pmNoFailedRrcConnectReqCsHw +
or pmNoRrcReqDeniedAdmDlPwr +
or pmNoRrcReqDeniedAdmDlChnlCode+
or pmNoRrcReqDeniedAdmDlHw +
or pmNoRrcReqDeniedAdmUlHw +
Successful setup?
Admissionreject due to other
reason?
pmTotNoRrcConnectSetup +
pmTotNoUtranRejRrcConnReq +
pmTotNoRrcReq +
NORRC Connection
Setup Complete and NBAP RadioLink Restore Indication are
received before timerexpires?
*) Stepped for Establishement Cause = Originating orTerminating Conversational Call, Emergency, Subscribed,
Originating or Terminating Interactive/Background Call.
pmTotNoRrcConnectUeCapability + *
pmTotNoRrcConnectUeCapability + *
Figure 3 RRC Connection Setup - CS Scenario
10 103/1551-AXD 105 03/1 Uen E | 2010-03-08
