0% found this document useful (0 votes)
302 views77 pages

RN3158 RANKPI Training: Radio Access Bearer

Uploaded by

AliNSN
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
302 views77 pages

RN3158 RANKPI Training: Radio Access Bearer

Uploaded by

AliNSN
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 77

RN3158 RANKPI Training

Radio Access Bearer


1 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
Agenda
• CS Radio Access Bearer (RAB)
– Signaling Flow and Trigger Points
– Radio Access Bearer setup
– CS Voice Radio Access Bearer
– CS RAB – related KPIs
– Additional measurements and KPIs (M1005, M1006, M1001/M1002)
• PS Radio Access Bearer
– Signaling Flow and Trigger Points of M1001 counters for PS
– RAB Bit Rate Counters
– PS RAB KPIs
– Additional measurements and KPIs (M1002, M1004, M1022)
• Radio Link failure and RRCC re-establishment
• Inter Circle Roaming Operator Statistics

2 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Radio Access Bearer setup

3 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAB and RRC connection

Radio Access Bearer


Signalling Connection

RRC Connection Iu Connection

RRC

Radio Bearer Iu Bearer

UE UTRAN CN
Uu (RNC) Iu

4 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


CS Voice Radio Access Bearer

5 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


AMR Voice Call
• Every call starts with RRC connection establishment
• UE indicates in Initial Direct Transfer service type
• Security functions triggered from CN follow

• CN sends RABAssignmentRequest to RNC to set-up resources


• RNC checks and allocates available resources

• In parallel there is ISDN signalling for call setup

6 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


AMR Voice Call L3 Signalling (1/2)

RRC Connection setup

UTRAN resource allocation for AMR voice call

7 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


AMR Voice Call L3 Signalling (2/2)

8 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAB Performance – example case: AMR call
positive
UE BS RNC CN

CM service request
AC RAB_STP_ATTEMPTS
RAB ass. req.
RL rec. prepare M1001C66 RAB STP ATT
Digit Analysis, RNC
RL rec. ready Iub internal
AAL2 sig. ERQ resources, AAL2 RAB SET UP PHASE
Digit Analysis, Iu CS CAC.
RNC internal AAL2 sig. ECF
resources, AAL2 CAC. AAL2 sig. ERQ M1001C73 RAB STP CPL
RL rec. commit
AAL2 sig. ECF RAB_STP_COMPLETE
Radio Bearer Setup
Exception: release of the RAB during the SET RAB ACCESS PHASE
UP or ACCESSE phase RAB ass. resp. (failure cause)
M1001C115 RAB ACC CPL
Radio Bearer Setup Complete RAB_ACC_COMPLETE
RAB ass. resp.

RAB Rel Req. RAB ACTIVE


Exception: release of
the RAB during the RAB ass. req. (release) PHASE
ACTIVE phase
RAB ass. resp. (release)
RAB_ACT_COMPLETE
Iu rel. req. M1001C136 RAB ACT CPL
Iu rel. conf.
9 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
RAB Performance – example case: AMR call
negative
failures in access phase
UE BS RNC CN failures in setup phase

CM service request
AC RAB_STP_ATTEMPTS
RAB ass. req. (setup)
RL rec. prepare M1001C80-84 due to AC, BTS,
Digit Analysis, RNC Transport, RNC, Frozen BTS
RL rec. ready
Iub internal M1001C531 due to AAL2 iuB
AAL2 sig. ERQ resources, AAL2
Digit Analysis, Iu CS M1001C619 due to License
RNC internal AAL2 sig. ECF
CAC. M800 M1001C621 due to AAL2 Iur
resources, AAL2 CAC. AAL2 sig. ERQ
RL rec. commit M550 M1001C625 due AAL2 IuCS
AAL2 sig. ECF RAB_STP_COMPLETE
Radio Bearer Setup
M1001C122 due to UE
Exception: release of the RAB during the SET
UP or ACCESSE phase RAB ass. resp. (failure cause) M1001C123 due to RNC

Radio Bearer Setup Complete RAB_ACC_COMPLETE


RAB ass. resp. (setup)
M1001C145 due to Iu
M1001C146 due to Radio
RAB Rel Req.
Exception: release of M1001C147 due to BTS
the RAB during the RAB ass. req. (release) M1001C148 due to IuR
ACTIVE phase M1001C150 due to RNC
RAB ass. resp. (release)
M1001C392 due to UE
Iu rel. req.
RAB_ACT_COMPLETE
Iu rel. conf.
failures in active phase
10 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
RAB active phase
• RU10 also contains counters to follow up events in RAB active
phase, broken down to CS voice, CS data and PS calls
• M1001C136-138 for normal completion
• Further counters for releases and failures, see next slide

11 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


CS voice RAB active phase counters

RAB releases RAB failures


M1001C143,C144, C422, C620 triggered by: M1001C145 ff triggered by:
Relocation Iu Interface failure
Pre-Emption Radio Interface failure
CN unspecified error BTS
License Iur Interface failure
RNC internal failure
UE

12 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


CS RAB – related KPIs

13 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Call Setup Success Rate – CSSR
CSSR for a specific service is calculated the following way:

CSSR any service = RRC connection setup & access X RAB setup & access any service

RRC part RAB part

14 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Success rate KPI
Call Setup Success Rate VOICE
CSSR Voice call (RNC_565f – counter names): CSSR Voice call (RNC_565f – counter numbers):

100 * 100 *
( (
sum( MOC_CONV_CALL_ATTS sum( M1001C22
- MOC_CONV_CALL_FAILS - M1001C23
+ MTC_CONV_CALL_ATTS + M1001C32
- MTC_CONV_CALL_FAILS - M1001C33
+ EMERGENCY_CALL_ATTS + M1001C40
- EMERGENCY_CALL_FAILS - M1001C41
- RRC_ACC_REL_EMERGENCY - M1001C562
- RRC_ACC_REL_MO_CONV - M1001C553
- RRC_ACC_REL_MT_CONV ) - M1001C558 )
------------------------------------------------- ------------------------------------------------- RRC part
sum( MOC_CONV_CALL_ATTS sum( M1001C22
+ MTC_CONV_CALL_ATTS + M1001C32
+ EMERGENCY_CALL_ATTS + M1001C40
- RRC_ATT_REP_MO_CONV - M1001C573
- RRC_ATT_REP_MT_CONV - M1001C578
- RRC_ATT_REP_EMERGENCY - M1001C582
- RRC_ACC_REL_EMERGENCY - M1001C562
- RRC_ACC_REL_MO_CONV - M1001C553
- RRC_ACC_REL_MT_CONV - M1001C558
- RRC_CONN_STP_REJ_EMERG_CALL ) - M1001C617 )
) )
* *
( (
sum( RAB_ACC_COMP_CS_VOICE) sum( M1001C115)
------------------------------------------------------ ------------------------------------------------------
sum( RAB_STP_ATT_CS_VOICE ) sum( M1001C66 ) RAB part
) ))

15 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Success rate KPI
Call Setup Success Rate UDI CALL (CS 64k video call)

CSSR Video call (RNC_566e – counter names): CSSR Video call (RNC_566e – counter numbers):

100 *
( 100 *
sum( MOC_CONV_CALL_ATTS (
- MOC_CONV_CALL_FAILS sum( M1001C22
+ MTC_CONV_CALL_ATTS - M1001C23
- MTC_CONV_CALL_FAILS + M1001C32
- RRC_ACC_REL_MO_CONV - M1001C33
- RRC_ACC_REL_MT_CONV ) - M1001C553
--------------------------------------------------- - M1001C558 )
sum( MOC_CONV_CALL_ATTS ---------------------------------------------------
+ MTC_CONV_CALL_ATTS sum( M1001C22
+ M1001C32
- RRC_ATT_REP_MO_CONV
- M1001C573
RRC part
- RRC_ATT_REP_MT_CONV
- RRC_ACC_REL_MO_CONV - M1001C578
- RRC_ACC_REL_MT_CONV ) - M1001C553
) - M1001C558 )
* )
( *
sum( RAB_ACC_COMP_CS_CONV ) (
---------------------------------------------------- sum( M1001C116 )
----------------------------------------------------
sum( RAB_STP_ATT_CS_CONV )
sum( M1001C67 ) RAB part
)
)

16 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Call Completion Success Rate - CCSR

CCSR for a specific service is calculated based on RAB Counters:

CCSR any service = RAB success rate any service

In Nokia RAN there are negative counters used to get success ratio:

sum ( RAB failure counters)


CCSR = 100 % - 100 % *
sum ( RAB failure counters + RAB active Complete)

17 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Success rate KPI – Voice Call
Call Completion Success Rate VOICE

CCSR Voice call (RNC_231c – counter names): CCSR Voice call (RNC_231c – counter numbers):

100 - 100*
100 - 100*
sum( RAB_ACT_REL_CS_VOICE_P_EMP
sum( M1001C144
+ RAB_ACT_FAIL_CS_VOICE_IU
+ M1001C145
+ RAB_ACT_FAIL_CS_VOICE_RADIO
+ M1001C146
+ RAB_ACT_FAIL_CS_VOICE_BTS
+ M1001C147
+ RAB_ACT_FAIL_CS_VOICE_IUR
+ M1001C148
+ RAB_ACT_FAIL_CS_VOICE_RNC
+ M1001C150
+ RAB_ACT_FAIL_CS_VOICE_UE)
+ M1001C392)
---------------------------------------------------------------
-----------------------------------------------------------------
--
sum(M1001C136
sum( RAB_ACT_COMP_CS_VOICE
+ M1001C143
+ RAB_ACT_REL_CS_VOICE_SRNC
+ M1001C144
+ RAB_ACT_REL_CS_VOICE_P_EMP
+ M1001C145
+ RAB_ACT_FAIL_CS_VOICE_IU
+ M1001C146
+ RAB_ACT_FAIL_CS_VOICE_RADIO
+ M1001C147
+ RAB_ACT_FAIL_CS_VOICE_BTS
+ M1001C148
+ RAB_ACT_FAIL_CS_VOICE_IUR
+ M1001C150
+ RAB_ACT_FAIL_CS_VOICE_RNC
+ M1001C392)
+ RAB_ACT_FAIL_CS_VOICE_UE)

18 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Success rate KPI – Voice Call – new in RU40 1/2
RNC_5434a RAB Success Ratio, Voice (CSR) (re-establishment included)

• RAB Success Ratio for AMR Voice [%] including RRC Call re-establishment into the formula
• Successful re-establishments are considered in the same way as abnormal releases (failures) from
end user point of view.
• it is calculated similarly as RNC_231d "RAB Success Ratio, Voice (CSR)" additionally taking into
account RRC Call Re-establishments as "failures“ from end user point of view
• it is taking into notice just calls which have successfully reestablished or have ended in this cell, but
might have been started in other cells

• Measurement 1001: Service Level & 1006: RRC signalling

• KPI class: Retainability


• Unit: %

• Object summary levels Network, City, Area, RNC, Cluster of cells, Cell
• Time summary levels Week, Day, Hour

19 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Success rate KPI – Voice Call – new in RU40 2/2
RNC_5434a RAB Success Ratio, Voice (CSR) (re-establishment included)
KPI formula: KPI formula with short names
100-100* 100-100*
sum([M1001C144] + sum([RAB_ACT_REL_CS_VOICE_P_EMP] +
[M1001C145] + [M1001C146] + [RAB_ACT_FAIL_CS_VOICE_IU] + [RAB_ACT_FAIL_CS_VOICE_RADIO] +
[M1001C147] + [M1001C148] + [RAB_ACT_FAIL_CS_VOICE_BTS] + [RAB_ACT_FAIL_CS_VOICE_IUR] +
[M1001C150] + [M1001C392] + [RAB_ACT_FAIL_CS_VOICE_RNC] + [RAB_ACT_FAIL_CS_VOICE_UE] +
[M1001C690] + [M1006C186]) [RAB_ACT_FAIL_CS_VOICE_TRANS] + [RRC_RE_EST_SUCC_RT])
/ /
sum([M1001C136] + [M1001C143] sum([RAB_ACT_COMP_CS_VOICE] + [RAB_ACT_REL_CS_VOICE_SRNC] +
+ [M1001C144] + [M1001C644] + [RAB_ACT_REL_CS_VOICE_P_EMP] + [RAB_ACT_REL_CS_VOICE_HHO] +
[M1001C647] + [M1001C650] + [RAB_ACT_REL_CS_VOICE_ISHO] + [RAB_ACT_REL_CS_VOICE_GANHO] +
[M1001C145] + [M1001C146] + [RAB_ACT_FAIL_CS_VOICE_IU] + [RAB_ACT_FAIL_CS_VOICE_RADIO] +
[M1001C147] + [M1001C148] + [RAB_ACT_FAIL_CS_VOICE_BTS] + [RAB_ACT_FAIL_CS_VOICE_IUR] +
[M1001C150] + [M1001C392] + [RAB_ACT_FAIL_CS_VOICE_RNC] + [RAB_ACT_FAIL_CS_VOICE_UE] +
[M1001C690] + [M1006C186]) [RAB_ACT_FAIL_CS_VOICE_TRANS] + [RRC_RE_EST_SUCC_RT])

20 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Success rate KPI – UDI Call
Call Completion Success Rate UDI CALL (CS 64k Video Call)

CCSR Voice call (RNC_selfmade – counter names): CCSR Voice call (RNC_selfmade – counter numbers):

100-100 * SUM (RAB_ACT_REL_CS_CONV_P_EMP 100 - 100*


+ RAB_ACT_FAIL_CS_CONV_IU sum( M1001C144
+ RAB_ACT_FAIL_CS_CONV_RADIO + M1001C145
+ RAB_ACT_FAIL_CS_CONV_BTS + M1001C146
+ RAB_ACT_FAIL_CS_CONV_IUR + M1001C147
+ RAB_ACT_FAIL_CS_CONV_RNC + M1001C148
+ RAB_ACT_FAIL_CS_CONV_UE + M1001C150
---------------------------------------- + M1001C392)
SUM (RAB_ACT_COMP_CS_CONV -----------------------------------------------------------------
+ RAB_ACT_REL_CS_CONV_SRNC sum(M1001C136
+ RAB_ACT_REL_CS_CONV_P_EMP + M1001C143
+ RAB_ACT_FAIL_CS_CONV_IU + M1001C144
+ RAB_ACT_FAIL_CS_CONV_RADIO + M1001C145
+ RAB_ACT_FAIL_CS_CONV_BTS + M1001C146
+ RAB_ACT_FAIL_CS_CONV_IUR + M1001C147
+ RAB_ACT_FAIL_CS_CONV_RNC + M1001C148
+ RAB_ACT_FAIL_CS_CONV_UE + M1001C150
+ M1001C392)

This KPI is based on RNC_160d – other services than UDI were excluded

21 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Additional measurements and KPIs for further
investigation

22 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


M1005: Radio Link related counters
UE BS RNC CN

CM service request
RAB ass. req. (setup)
RL rec. prepare
RL rec. ready/failure
AAL2 sig. ERQ
AAL2 sig. ECF
AAL2 sig. ERQ
RL rec. commit/cancel

AAL2 sig. ECF

•M1005 provides counters for all messages:


• Separated by SRNC and DRNC
• Separated by ADD, MOD, DEL
• Including 5 failure reasons
• RL Deletions and reconfiguration cancellations by RNC are also counted
• Straightforward to define PIs for each phase
23 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
RL Reconfiguration Counters: PREPARE message
(Add/Mod/Del)
Counters incremented when RNC sends RADIO
LINK RECONFIGURATION PREPARE
message:
M1005C132 REC_PREP_SRNC
1 for each PREPARE message

M1005C 78 RECONF_PREP_DCH_ADD_SRNC
1 for each DCH addition requested in the message

M1005C79 RECONF_PREP_DCH_MOD_SRNC
1 for each DCH modification requested in the message

M105C80 RECONF_PREP_DCH_DEL_SRNC

1 for each DCH deletion requested in the message

24 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RL Reconfiguration Counters:
READY (Add/Mod/Del) and COMMIT message
Counters incremented when RNC sends RADIO
LINK RECONFIGURATION READY message:

M1005C135 REC_PREP_SRNC_READY
1 for each READY message

M1005C84 RECONF_DCH_ADD_SRNC_RDY
1 for each DCH addition in the message

M1005C85 RECONF_DCH_MOD_SRNC_RDY
1 for each DCH modification in the message

M1005C86 RECONF_DCH_DEL_SRNC_RDY
1 for each DCH deletion in the message

M1005C126 REC_COMM_SYNCH_SRNC

1 for each COMMIT message

25 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Related failure counters in M1005

In SRNC
M1005C212 RECONF_ADD_FAIL_SRNC_RNL
M1005C213 RECONF_ADD_FAIL_SRNC_TRL
M1005C214 RECONF_ADD_FAIL_SRNC_PROT Same for PS!
M1005C215 RECONF_ADD_FAIL_SRNC_MISC
And in DRNC
M1005C216 RECONF_ADD_FAIL_DRNC_RNL
M1005C217 RECONF_ADD_FAIL_DRNC_TRL
M1005C218 RECONF_ADD_FAIL_DRNC_PROT
M1005C219 RECONF_ADD_FAIL_DRNC_MISC

M1005C94 RECONF_ADD_FAIL_SRNC_BTS_NR and


M1005C112 RECONF_ADD_FAIL_DRNC_BTS_NR
are incremented in case BTS does not respond in time and
response supervision timer expires in RNC

26 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RL Reconfiguration: CANCEL message from RNC

After READY message from BTS(s), RNC's RM may cancel the reconfiguration
request (e.g. due to AAL2 setup failure or if all BTSs are not ready for the new
configuration) by commanding the RNC's L3 Dedicated NBAP signalling entity to
send an NBAP:RADIO LINK RECONFIGURATION CANCEL message to the
BTS's L3 Dedicated NBAP signaling entity (instead of COMMIT message):

M1005C128 CANC_SRNC_TRAN_STP_FAIL AAL2 setup failure

M1005C129 CANC_SRNC_BTS_NOT_READY other BTS(s) do not support new configuration

27 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


M1006: Radio Bearer related counters
UE BS RNC CN

CM service request
AC
RAB ass. req. (setup)
RL rec. prepare
RL rec. ready Same for PS!
AAL2 sig. ERQ
AAL2 sig. ECF
AAL2 sig. ERQ
RL rec. commit
AAL2 sig. ECF
Radio Bearer Setup M1006C28 RB_SETUP

Radio Bearer Setup Complete/Failure


M1006C135 REC_PREP_SRNC_READY

M1006C76 RB_SETUP_FAIL

M1006C77 RB_SETUP_FAIL_UNS_CONF

•M1006 provides counters for all messages:


•RB Setup Failures due to unsupported configuration are counted separately

28 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


M1001/M1002: DCH related counters and KPIs, voice
call example
M1001C714 CS VOICE CALL DROP AFTER MISSING ADJ – introduced in RU30
Description: The number of CS Voice call RAB active failures after the UE has reported detected set
cell in 1A or 1C event, and handover could not be initiated because the reported cell is not included in
ADJS or ADJD list. Also one of RAB Active Failure counters is updated along with this counter.
Updated: When CS voice call RAB active failure happens within 10 seconds after receiving 1A/1C
event from the UE asking to add non-identified detected set cell to the active set. Here 10 seconds is
the time between the latest unidentified cell event, and the moment when all radio links are deleted.
Possible T314 expiry time is not anymore part of the time criteria.

• Same structure can be build from M1002 counters for any type of DCH service
(SRB, Video call, PS …) and Compressed Mode events
• Note that PS allocations are done via RB reconfiguration after
– allocation of DCH0/0
– reception of a capacity request

29 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


CS Voice DCH allocation signalling

Admission Control
decision

Request and Successful


AC for a CS Voice DCH

NOTE:
Failure can happen
later in the setup phase
(e.g. radio link
reconfiguration, or
AAL2 connection
setup)

30 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


CS Voice DCH allocation for SHO

UE BTS RNC
Admission Control
RRC: Measurement Report (e1a / e1c)
decision to setup new
radio link
NBAP: Radio Link Setup Request

Request and Successful


NBAP: Radio Link Setup Response AC for a CS Voice DCH
ALCAP:ERQ
for SHO trigger
ALCAP:ECF

RRC: Active Set Update NOTE:


Failure can happen later in
the setup phase (e.g.
RRC: Active Set Update Complete radio link setup, or AAL2
connection setup)

31 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Traffic Table: DCH request for RAB AMR Voice xx.yy

M1002C13 REQ_CS_VOICE_REJ_UL_SRNC

M1002C12REQ_CS_VOICE_IN_SRNC M1002C14 REQ_CS_VOICE_REJ_DL_SRNC


DCH request for RAB Voice Setup, SHO and HHO

M1002Cxx ALLO_FOR_AMR_xx_yy_UL_IN_SRNC
=

M1002C15 RT_DCH_INIT_VOICE_SRNC M1002Cxx ALLO_FOR_AMR_xx_yy_DL_IN_SRNC


DCH request only for RAB Voice Setup

+
M1002C16 REQ_CS_VOICE_SRNC M1002C17 REQ_CS_VOICE_REJ_SRNC
DCH request only for RAB Voice SHO

+
M1002C341REQ_CS_VOICE_HHO_SRNC
DCH request only for M1002C342REQ_CS_VOICE_HHO_REJ_SRNC
RAB Voice HHO

Supported AMR bitrates 4.75 / 5.90 / 7.95 / 12.2


32 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
UL/DL DCH blocking RAB CS Voice KPIs

This set of KPI is useful to understand if blocking at RAB level for CS


Voice is due to UL AC or DL AC.

In case of cell availability problem, these counters are not incremented


at all because AC does not even receive the DCH request.

UL DCH Reject Rate


CS Voice KPI 
100%
REQ_CS_VOI CE_REJ_UL_SRNC
UL DCH Reject Rate Voice 
REQ_CS_VOI CE_IN_SRNC
DL DCH Reject Rate
CS Voice KPI  M1002C13/M1002C12

100%
REQ_CS_VOI CE_REJ_DL_SRNC
DL DCH Reject Rate Voice 
REQ_CS_VOI CE_IN_SRNC

M1002C14/M1002C12
33 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
DCH allocation duration CS Voice KPI
DCH Duration CS Voice KPI

DCH Duration Voice 


DUR_FOR_AMR_12_2_UL_IN_SRNC
s
100

M1002C41/100
Counter unit 10ms.

The duration KPI gives an indication of the number of Erlang for voice in the
cell during the monitored hours.

34 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAB Holding Time

For each traffic class there are counters for RAB Holding time.
They are incremented (denominator also):
▪ when the RAB is released
▪ in the cell that was the reference when the RAB is released
▪ and in the hour in which it was released

RAB duration for CS voice class (measuring the time from RAB Assignment
Response to RAB Assignment Response for release (or Iu Release
command)) is defined as:
AVG _ RAB _ HLD _ TM _ CS _ VOICE
/ 100( s)
DENOM _ RAB _ HLD _ TM _ CS _ VOICE M1001C199/M1001C200

Due to mobility these KPIs are only accurate on network level.


For investigation on cell level use M1001C489-C502 relating to reference cell
M1001C714 CS VOICE CALL DROP AFTER MISSING ADJ – RU30

35 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAB Setup Time KPI (average)

The result represents the average time to successfully establish a CS voice RAB. A successful RAB
is defined as one for which the RNC sends a positive RANAP: RAB ASSIGNMENT RESPONSE
message.
UE RNC CORE
RAB Assignment Request
AVE _ RAB _ SETUP _ TM _ CS _ VOICE
Radio Bearer Setup / 100( s)
DENOM _ RAB _ SETUP _ TM _ CS _ VOICE
Radio Bearer Setup Complete
RAB Assignment Response
Triggering Point X

The AVG_RAB_SETUP_TM_CS_VOICE counter records the time between the RNC receiving a
RANAP: RAB ASSIGNMENT REQUEST and sending a positive RANAP: RAB ASSIGNMENT
RESPONSE. The counter sums the times for all successful RAB assignments.
The DENOM_ RAB_SETUP_TM_CS_VOICE is incremented by 1 after every successful RAB
assignment.
The factor of 100 appearing within the KPI calculation is a result of NSN internal representation of the
counter value. NSN uses a 10 ms unit for the AVG_RAB_SETUP_TM counter.
Same counters and formula is possible for any RAB (CS_VOICE, CS_CONV, PS_INTER,
PS_BACKG)
The KPI is meaningful for cell level and on hour basis

36 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAB Setup Time KPI (maximum)
• maximum setup time for RAB can be measured
• it is absolute maximum setup time per measurement period:

M1001C603 RRC SETUP TIME MAX


M1001C604 RAB SETUP TIME MAX CS VOICE
M1001C605 RAB SETUP TIME MAX CD DATA
M1001C608 RAB SETUP TIME MAX PS INTERACTIVE
M1001C609 RAB SETUP TIME MAX PS BACKGROUND

37 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Erlang for CS services

AVG _ RAB _ HLD _ TM _ CS _ VOICE M1001C199


( Erl )
100  60  60

The KPI should be generated on a daily and cluster basis (due to the
triggering rules of the RAB holding time).
Same KPI for each CS traffic class:
• CS_CONV
• CS_STREA

38 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Average Time between drop
The KPI represents the average time between abnormal RAB releases during CS
voice RAB active phase:

AVG _ RAB _ HLD _ TM _ CS _ VOICE


100  60 (min)
 RAB _ ACT
all _ failures
_ FAIL _ CS _ VOICE _ xxx
M1001C237 ff

The KPI should be generated on a daily and cluster basis (due to the triggering
rules of the RAB holding time).
Same KPI for each traffic class:
• CS_CONV
• CS_STREA
• PS_INTER
• PS BACKG

39 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Drop KPIs – Minutes Per Drop (RT)

RAB drop now also includes failure due to transport:

MPD Voice

MPD UDI
(video call)

40 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Traffic Mix KPIs
The KPI provides an indication of the percentage of CS voice, CD data, PS data RAB
establishment attempts relative to the total number of RAB establishment attempts.
The KPI is meaningful for cluster/cell level and on day/hour basis
These KPI are intended to provide a high level indication of the traffic profile loading the
network:
• CS_VOICE, CS_CONV, CS_STREA
• PS_STREA, PS_INTER, PS_BACKG, (PS_CONV)

Example for CS_VOICE:


_C S_VO IC E  R A B _ST P _A T T _C S_C O N V  R A B _ST P _A T T _C S_ST R EA  R A B _ST P _A T T _P S_C O N V  R A B _ST P _A T T _P S_ST R EA  R A B _ST P _A T

RAB _ STP _ ATT _ CS _ VOICE


 RAB _ STP _ ATT _ xyz
xyz

M1001C66/(M1001C66+ M1001C67+ M1001C68 +M1001C70 +M1001C71+ M1001C72)

41 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Packet Switched Radio Access Bearers

42 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Packet Call
• Every call starts with RRC connection establishment
• UE indicates in Initial Direct Transfer service type
• Security functions triggered from CN follow

• CN sends RABAssignmentRequest to RNC to set-up resources


• RNC allocates DCH0/0 without resource checks and responds
with RABAssignmentResponse => easy to have high CSSR
• In parallel there is GPRS Mobility Management signalling for
packet call setup
• After receiving UL or DL CR, RNC checks and allocates available
resources

43 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


PS terminology
• A packet call is a data transfer session that uses DCH, HS-
DSCH, or E-DCH channels, starting from a successful capacity
allocation (AC, BTS, transmission, RNC-internal) and ending to a
dedicated resource release (for example, transfer to FACH/PCH,
DCH 0/0, RAB release, outgoing relocation, HHO, ISHO)
• Packet calls start from DCH0/0
• One RAB can contain multiple packet calls
• Packet call sessions are active data transfer periods
• Packet call session start from the respective Capacity Request,
i.e. establishment of RLC protocol entity

44 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Layer 3 signaling for HSPA call setup (1/2)
Uu interface IuB interface Iu interface timing

RRC Connection setup

45 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Layer 3 signaling for HSPA call setup (2/2)
Uu interface IuB interface Iu interface timing

46 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAB PS set up procedure
positive M1001C70-C72
This triggers the RAB Setup Success Rate KPI! RAB STP ATT tc
RAB_STP_ATTEMPTS
UE BS RNC SGSN

RAB SETUP PHASE


Act. PDP context request
no AC M1001C77-C79
RAB ass. req. (setup)
RAB STP CPL tc
GTP tunnel
RAB_STP_COMPLETE
Radio Bearer Setup creation

Radio Bearer Setup Complete


RAB ACCESS PHASE
RAB ass. resp. (setup)
DCH 0/0 RAB_ACC_COMPLETE
Measurement Ctrl Digit Analysis, RNC Iub
Measurement Report internal resources, AAL2 M1001C119-C121
CAC.
RL rec. prepare RAB ACC ATT tc
RL rec. ready
AAL2 sig. ERQ RAB ACTIVE PHASE
DCH 0/0--->DCH X/Y
AAL2 sig. ECF
RL rec. commit
Measurement Report M1001C140-C142
RL rec. prepare AC RAB ACT CPL tc
RL rec. ready RAB_ACT_COMPLETE
RAB ass. req. (release)
47 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009 RAB ass. resp. (release)
RAB PS set up procedure
negative (same counters exist for PS STREAMING) failures in setup phase

failures in access phase M1001C105/110 due to Adm. Ctrl


SGSN M1001C107/112 due to RNC
UE BS RNC
M1001C108/113 due to ANCH
Act. PDP context request M1001C109/114 due to Frozen BTS
no AC M1001C257 due to not supp Param
on Uu RAB ass. req. (setup)
M1001C258 due to UE capabilities
GTP tunnel
RAB_STP_COMPLETE
Radio Bearer Setup creation
M1001C132/134 due to UE
Radio Bearer Setup Complete M1001C133/135 due to RNC
RAB ass. resp. (setup)
DCH 0/0 RAB_ACC_COMPLETE
Measurement Ctrl Digit Analysis, RNC Iub
Measurement Report internal resources, AAL2
CAC.
RL rec. prepare M1001C185/191 due to Iu
RL rec. ready M1001C186/192 due to Radio
AAL2 sig. ERQ M1001C187/193 due to BTS
DCH 0/0--->DCH X/Y M1001C188/194 due to IuR
AAL2 sig. ECF
M1001C190/196 due to RNC
RL rec. commit
M1001C397/298 due to UE
Measurement Report
RL rec. prepare AC failures in active phase

RL rec. ready RAB_ACT_COMPLETE


RAB ass. req. (release)
48 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009 RAB ass. resp. (release)
RAB Establishment – PS; PIs on Cell Level

RAB Setups Success Rate


RAB_STP_CO MP_PS_BACK G
RNC_29a  PS Background RAB setup success rate  % M1001C79/M1001C72
RAB_STP_AT T_PS_BACKG

RAB_STP_CO MP_PS_INTER
RNC_28a  PS Interactiv e RAB setup success rate  % M1001C78/M1001C71
RAB_STP_AT T_PS_INTER

RAB Setup & Access Success Rate


RAB_ACC_CO MP_PS_BACK G
RNC_36a  PS Background RAB setup and access success rate  %
RAB_STP_AT T_PS_BACKG

M1001C121/M1001C72

RAB_ACC_CO MP_PS_INTER
RNC_35a  PS Interactiv e RAB setup and access success rate  %
RAB_STP_AT T_PS_INTER

M1001C120/M1001C71

49 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAB Bit rate Counters

50 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAB Bit rate Counters
New RAB Bit Rate distribution counters introduced for measuring the number of
NRT RAB setup requests received from the core network, classified by the uplink
and downlink maximum bit rate.

• RAN 1509
• ASW Controlled with RNC license

• RAB Bitrate Counters show the requested NRT Bit rates from Core Network
• The Request depends on user specific subscription
• Maximum Uplink Bitrate
• Maximum Downlink Bitrate
• Performance Experts can compare avg. Bit rate from CN and avg. allocated
Bearer Bitrate in a cell
• If there is mismatch, most probably capacity constraints
• Note: Counters show attempts for RAB Bit rate, not Radio Bearer Bit rate

51 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAB Bitrate Counters
Signalling

• RNC triggers the counters based on request received from Core Network
• RANAP: RABAssignmentRequest lists user specific QoS parameters

Assume bit rates &


Max. bit rate availability
for customer

52 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAB Bit rate Counters
Counters Compare with throughput
(setup/establishment)
Statistic of customer
M1001 Measurement for downlink maximum RAB Bitrates: Service profile

Counter Counter Name Bitrate Class (kbps)


M1001C659 RAB_STP_ATT_BR_CLASS_1_DL 0 < Bitrate < 384

M1001C660 RAB_STP_ATT_BR_CLASS_2_DL 384 < Bitrate < 1800


M1001C661 RAB_STP_ATT_BR_CLASS_3_DL 1800 < Bitrate < 3600
M1001C662 RAB_STP_ATT_BR_CLASS_4_DL 3600 < Bitrate < 7200
M1001C663 RAB_STP_ATT_BR_CLASS_5_DL 7200 < Bitrate < 10000
M1001C664 RAB_STP_ATT_BR_CLASS_6_DL 10000 < Bitrate < 14400
M1001C665 RAB_STP_ATT_BR_CLASS_7_DL Bitrate > 14400

In these counters kbps means 1000 bits/s

53 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAB Bit rate Counters
Counters

M1001 Measurement for uplink maximum RAB Bitrates:

Counter Counter Name Bitrate Class (kbps)

M1001C666 RAB_STP_ATT_BR_CLASS_1_UL 0 < Bitrate < 128

M1001C667 RAB_STP_ATT_BR_CLASS_1_UL 128 < Bitrate < 384

M1001C668 RAB_STP_ATT_BR_CLASS_2_UL 384 < Bitrate < 1000

M1001C669 RAB_STP_ATT_BR_CLASS_3_UL 1000 < Bitrate < 2000

M1001C670 RAB_STP_ATT_BR_CLASS_4_UL Bitrate > 2000

In these counters kbps means 1000 bits/s

54 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


PS RAB active phase counters

RAB releases RAB failures

M1001C169 ff, C431ff triggered by: M1001C179 ff, C396ff triggered by:
Relocation Iu Interface failure
Pre-Emption Radio Interface failure
CN unspecified error BTS
Iur Interface failure
RNC internal failure
UE

55 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


DCH Holding Time

Most KPIs from CS section can also be used for PS.


For PS NRT traffic classes (interactive and background) there are
also counters for DCH Holding time .
They are incremented:

▪ when the RAB is released


▪ only on the cell that was the reference when the RAB is released (i.e
the cell that provided FMCS parameters)
▪ and in the hour in which it was released

AVG _ DCH _ HLD _ TM _ PS _ INTER


/ 100( s)
DENOM _ DCH _ HLD _ TM _ PS _ INTER

M1001C213/M1001C214

56 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Drop KPIs – Iu-PS service volume before drop
RAB drop now also includes failure due to transport:
ATM based IP based

57 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Additional measurements and KPIs for further
investigation

58 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Related counters in M1002: Setup and reconfiguration

M1002C553 REJ_DCH_DUE_CODES_INT_DL or
M1002C554 REJ_DCH_DUE_CODES_BGR_DL In case of successful capacity allocation :
M1002C142-C157
M1002C557 REJ_DCH_REC_DUE_CODES_INT_DL or ALLO_PS_INTERA_xx_yL_IN_SRNC or
M1002C558 REJ_DCH_REC_DUE_CODES_BGR_DL M1002C158-C173
M1002C555 REJ_DCH_DUE_POWER_INT_DL or ALLO_PS_BACKG_xx_yL_IN_SRNC
M1002C556 REJ_DCH_DUE_POWER_BGR_DL are incremented.
For different bit rates and separately for UL
M1002C559 REJ_DCH_REC_DUE_PWR_INT_DL or
M1002C560 REJ_DCH_REC_DUE_PWR_BGR_DL
and DL, includes SHO as well
(NOTE counters incremented only
M1002C626REJ_DCH_DUE_POWER_INT_UL or in case BTS setup and AAL2 reservation
M1002C627REJ_DCH_DUE_POWER_BGR_UL are ok)
M1002C628 REJ_DCH_REC_DUE_PWR_INT_UL or
M1002C629 REJ_DCH_REC_DUE_PWR_BGR_UL

Allocation duration counters :


M1002C206-M1002C221 DUR_PS_INTERA_xx_yL_IN_SRNC or
M1002C222-M1002C237 DUR_PS_BACKG_xx_yL_IN_SRNC
are started (sampled continuously with 1s interval RN2.0 GCD3 onwards)
For different bit rates and separately for UL and DL, includes SHO as
well
(NOTE counters started only in case BTS setup and AAL2 reservation
are ok)

59 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Related counters in M1004: Setup and reconfiguration

M1004C165 FAIL_NRT_DCH_SETUP_IUR

M1004C166 FAIL_NRT_DCH_UL_RECONF_IUR
M1004C167 FAIL_NRT_DCH_DL_RECONF_IUR

• Triggered by RNSAP: Radio Link Reconfiguration Failure

60 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Related counters in M1022: DCH Packet Call Setup
Statistics

Requests Successful Setups

M1022C0 PS_SESSION_REQ_UL: M1022C31 D_D_REQ_D_D_ALLO_INT - DCH/DCH is


successfully aIlocated after DCH/DCH was initially
triggered by UL CR
requested for INTERACTIVE traffic class
M1022C1 PS_SESSION_REQ_DL: M1022C32 D_D_REQ_D_D_ALLO_BGR - DCH/DCH is
triggered by DL CR successfully aIlocated after DCH/DCH was initially
CR M1022C2 PS_SESSION_REQ_OTHER: requested for BACKGROUND traffic class
triggered by Inter-RNC HHO or SRNS reloc.
M1022C7 PS_ATT_DCH_DCH_INT : DCH/DCH
was requested by AC for Interactive class Failures
M1022C8 PS_ATT_DCH_DCH_BGR : DCH/DCH
was requested by AC for Background class M1022C9-M1022C20 see next slide

61 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


UE Node B RNC SGSN
RANAP: RAB Assignment Request
PS Setup Failures
AC to check to accept
or reject RAB
Assignment Request

[DCH] RRC: Radio Bearer Setup

[DCH] RRC: Radio Bearer Setup Complete


RANAP: RAB Assignment Response:
Success
[DCH] RRC: Measurement Control
[DCH] RRC: Measurement Control
M1022C9 PS_SETUP_FAIL_AC_INT
Direct Transfer : Activate PDP Context Accept M1022C10 PS_SETUP_FAIL_AC_BGR
[DCH] RRC: Measurement Report
M1022C11 PS_SETUP_FAIL_BTS_INT
AC to check to accept M1022C12 PS_SETUP_FAIL_BTS_BGR
or reject Capacity
request M1022C13 PS_SETUP_FAIL_DMCU_INT
M1022C14 PS_SETUP_FAIL_DMCU_BGR
NBAP: RL Reconfiguration Prepare
M1022C15 PS_SETUP_FAIL_TRANS_INT
NBAP: RL Reconfiguration Ready M1022C16 PS_SETUP_FAIL_TRANS_BGR

ALCAP:ERQ M1022C17 PS_SETUP_FAIL_UE_INT


M1022C18 PS_SETUP_FAIL_UE_BGR
ALCAP:ECF
M1022C19 PS_SETUP_FAIL_OTHER_INT
NBAP: Radio Link Reconfiguration Commit M1022C20 PS_SETUP_FAIL_OTHER_BGR
[DCH] RRC: Radio Bearer Reconfiguration
[DCH] RRC: Radio Bearer Reconfiguration Complete

62 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


NRT Packet Call Setup KPIs

RNC_916 Packet Session Setup Success Ratio [%] 


Any PS
M1022C21 HS_E_REQ_HS_E_ALLO_I NT + M1022C22 HS_E_REQ_HS_E_ALLO_B GR 
Request
+ M1022C23 HS_E_REQ_HS_D_ALLO_I NT + M1022C24 HS_E_REQ_HS_D_ALLO_B GR  Can be


+ M1022C25 HS_D_REQ_HS_D_ALLO_I NT + M1022C26 HS_D_REQ_HS_D_ALLO_B GR  Setup?
+ M1022C27 HS_E_REQ_D_D_ALLO_INT  M1022C28 HS_E_REQ_D_D_ALLO_BG R 
+ M1022C29 HS_D_REQ_D_D_ALLO_INT + M1022C30 HS_D_REQ_D_D_ALLO_BG R 
+ M1022C31 D_D_REQ_D_D_ALLO_INT + M1022C32 D_D_REQ_D_D_ALLO_BGR
100 
M1022C3 PS_ATT_HSD SCH_EDCH_INT + M1022C4 PS_ATT_HSD SCH_EDCH_BGR 
+ M1022C7 PS_ATT_DCH _DCH_INT + M1022C8 PS_ATT_DCH _DCH_BGR
+ M1022C5 PS_ATT_HSD SCH_DCH_INT  M1022C6 PS_ATT_HSD SCH_DCH_BGR 

RNC_943a R99 Setup Success Ratio From User Perspective [%] 


 M1022C31D_D_REQ_D_D_ALLO_INT M1022C32 D_D_REQ_D_D_ALLO_BGR
Requested R99
can be setup or
 M1022C7 PS_ATT_DCH_DCH_INT  M1022C8 PS_ATT_DCH_DCH_BGR not?

63 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Radio Link failure and RRCC re-establishment

64 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAB Active phase

Time
UE side Network side
WBTS starts to receive “out of sync”
N313 L1 “out of sync” indicators.
indicators received in DL

After receiving N_OUTYNC_IND=8 indicators


Timer T313 started
on L1 T_RLFAILURE is started

T_RLFAILURE=2s expires, RL is moved to out-


Timer T312 expires, of-sync state
RL failure

RNC receives NBAP RL failure message

T_L1_Sync_ReEstab_Wait –timer started in RNC,


waiting for L1 synchronisation to be reestablished

T_L1_Sync_ReEstab_Wait –timer expired,


RNC sends NBAP:RADIO LINK
DELETION –message to the BTS if
T314/T315 are 0

T_L1_sync_ReEstab_Wait [s] =
max { 0, T313 - (T_RLFailure + NOutSynchInd * 0,010) } + L1SyncReEstabTmrOffset

65 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


L1SyncReEstabTmrOffset (def. 1s, not modifiable)
RRCC reestablishment, non-zero T314 or T315

Time
UE side Network side
WBTS starts to receive “out of sync”
N313 L1 “out of sync” indicators.
indicators received in DL

After receiving N_OUTYNC_IND=8 indicators


Timer T313 started
on L1 T_RLFAILURE is started

T_RLFAILURE=2s expires, RL is moved to out-


Timer T313 expires, of-sync state
T314/T315 started

RNC receives NBAP RL failure message

T_L1_Sync_ReEstab_Wait –timer started in RNC,


Cell re-selection is attempted waiting for L1 synch to be reestablished
during T314/T315
T_L1_Sync_ReEstab_Wait –timer expires, RCN waits
for re-establishment until T314 or RRC_ConnRe-
estabTmr= T315 + (T302*N302)
expire

RRC:CELL UPDATE is sent, if


successful RRC: CELL UPDATE
received, SRB is re- Timer expired without
established CELL UPDATE message
received: Iu release and
66 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
RL Deletion are sent
RB re-establishment, NRT example

UE RNC

CELL_DCH
NRT data transfer
Radio link failure
CELL UPDATE

CELL UPDATE CONFIRM


(RRC connection re-establishment)
CELL_FACH

UTRAN MOBILITY INFORMATION


CONFIRM
MEASUREMENT CONTROL

MEASUREMENT REPORT

RRM packet scheduling

RB RECONFIGURATION
CELL_DCH

RB RECONFIGURATION COMPLETE

NRT data transfer

67 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RRCC re-establishment counters from M1006

M1006 provides success and failure counters for RT, NRT and Multi-RAB

Successes Failures

M1006C186 RRC_RE_EST_SUCC_RT M1006C119 RRC_RE_EST_FAIL_UE_NRT

M1006C118 RRC_RE_EST_SUCC_NRT M1006C120 RRC_RE_EST_FAIL_NOREPLY_NRT

M1006C189 RRC_RE_EST_SUCC_MR M1006C187 RRC_RE_EST_FAIL_UE_RT

M1006C188 RRC_RE_EST_FAIL_NOREPLY_NRT

M1006C119 RRC_RE_EST_FAIL_UE_MR

M1006C119 RRC_RE_EST_FAIL_NOREPLY_NRT

68 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Radio Link Failure counters

When a dedicated NBAP signaling entity


receives an NBAP:RADIO LINK FAILURE
Typical Cause values are:
message from a BTS one of the counters
below are incremented: • Radio Network Layer Causes:
– Synchronisation Failure
M1005C204 RL_FAIL_SRNC_RNL – Invalid CM settings
M1005C205 RL_FAIL_SRNC_TRL • Transport Layer Causes:
M1005C206 RL_FAIL_SRNC_PROT – Transport Resources Unavailable
M1005C207 RL_FAIL_SRNC_MISC
• Miscellaneous Causes:
M1005C208 RL_FAIL_DRNC_RNL – Control Processing Overload
M1005C209 RL_FAIL_DRNC_TRL – HW Failure
M1005C210 RL_FAIL_DRNC_PROT – O&M Intervention
M1005C211 RL_FAIL_DRNC_MISC

69 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Inter Circle Roaming Operator Statistics

70 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAN2412: Inter Circle Roaming 1/6
For the situation that:
1. the operator has own 2G coverage in the area, but wants to direct its 3G subscriber to
another 3G operator to enable 3G services
2. operators agree on a certain type of resource split in the 3G network so that, for
example, the proportional network resources are consumed by the owning operator
(Provider) subscribers and the ICR operator (Seeker) subscribers

- ICR allows capacity sharing according to certain weights and enables ISHOs to home
2G networks
- allows the operator to offer 3G services in an area with no proprietary 3G spectrum.
- the feature allows the 3G operator to share network capacity with operators who do not
have 3G coverage in the area
- this feature is not the MORAN because only one operator has a spectrum in the area
- operator-specific quota split is a BTS-level parameter
- RNC enforces the quota split separately in each cell
- Utilization counters related to the capacity utilization for voice (in Erls) and data (Mbps)
are available per operator ID level (up to five operators)

71 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAN2412: Inter Circle Roaming 2/6
ICR

Load > Threshold Load < Threshold

R99 data calls are all calls are established


voice calls are handed over to the downgraded to normally
correct operator's 2G network the lower bit rates

1. the operator who exceeds his quota the most is the target operator for the load decrease activities

2. the quota is checked against the DL spreading code usage: when the first operator’s spreading code usage had
been reduced to the agreed quota, then if the load is still over the threshold, the next operator exceeding his quota is
targeted

3. while the cell is in load state and a new incoming call faces congestion, the candidates for the release or
downgrade are selected based on the code use of each operator

72 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAN2412: Inter Circle Roaming 3/6
M1034C0 INTER SYSTEM HHO RT ATTEMPTS PER OPER PER OPER: Per Operator
M1034C1 INTER SYSTEM HHO RT SUCCESS PER OPER
M1034C2 INTER SYSTEM HHO NRT ATTEMPTS PER OPER
M1034C3 INTER SYSTEM HHO NRT SUCCESS PER OPER
M1034C4 TRANSFERRED DATA FOR CS CALL DCH DL PER OPER
M1034C5 TRANSFERRED DATA FOR CS CALL DCH UL PER OPER
M1034C6 TRANSFERRED DATA FOR PS REL99 DCH DL PER OPER
M1034C7 TRANSFERRED DATA FOR PS REL99 DCH UL PER OPER
M1034C8 MAX SF256 CODE OCCUPANCY PER OPER
M1034C9 SUM SF256 CODE OCCUPANCY PER OPER
M1034C10 DENOM SF256 CODE OCCUPANCY PER OPER
M1034C11 RAB SETUP ATTEMPTS FOR CS VOICE PER OPER
M1034C12 RAB ACCESS COMPLETIONS FOR CS VOICE PER OPER
M1034C13 RAB SETUP ATTEMPTS FOR CS DATA CONV PER OPER
M1034C14 RAB ACCESS COMPLETIONS FOR CS DATA CONV PER OPER
M1034C15 RAB SETUP ATTEMPTS FOR PS STREAM PER OPER
M1034C16 RAB ACCESS COMPLETIONS FOR PS STREAM PER OPER
M1034C17 RAB SETUP ATTEMPTS FOR PS NRT PER OPER
M1034C18 RAB ACCESS COMPLETIONS FOR PS NRT PER OPER
M1034C19 RAB ACTIVE COMPLETIONS FOR CS VOICE PER OPER
M1034C20 RAB ACTIVE FAILURES FOR CS VOICE PER OPER

73 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAN2412: Inter Circle Roaming 4/6

M1034C21 RAB ACTIVE COMPLETIONS FOR CS DATA CONV PER OPER PER OPER: Per Operator
M1034C22 RAB ACTIVE FAILURES FOR CS DATA CONV PER OPER
M1034C23 RAB ACTIVE COMPLETIONS FOR PS DATA STREAM PER OPER
M1034C24 RAB ACTIVE FAILURES FOR PS STREAM PER OPER
M1034C25 RAB ACTIVE COMPLETIONS FOR PS NRT PER OPER
M1034C26 RAB ACTIVE FAILURES FOR PS NRT PER OPER
M1034C27 SUM RAB HOLDING TIME FOR CS VOICE PER OPER
M1034C28 SUM RAB HOLDING TIME FOR CS DATA CONV PER OPER
M1034C29 SUM RAB HOLDING TIME FOR PS STREAM PER OPER
M1034C30 SUM RAB HOLDING TIME FOR PS NRT PER OPER
M1034C31 MAX NUMBER OF HSDPA USERS IN CELL PER OPER
M1034C32 MAX NUMBER OF HSUPA USERS IN CELL PER OPER
M1034C33 SUM OF HSDPA USERS IN CELL PER OPER
M1034C34 SUM OF HSUPA USERS IN CELL PER OPER
M1034C35 DENOM HSPA USERS IN CELL PER OPER

74 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAN2412: Inter Circle Roaming 5/6

M1034C36 HS-DSCH MAC-D FLOW ALLOCATIONS PER OPER PER OPER: Per Operator
M1034C37 E-DCH ALLOCATIONS PER OPER
M1034C38 HS-DSCH ALLO REJECT MAX USERS PER OPER
M1034C39 HS-DSCH ALLO REJECT UL POWER PER OPER
M1034C40 HS-DSCH SETUP FAILURE PER OPER
M1034C41 HS-DSCH ALLO REJECT DL POWER PER OPER
M1034C42 E-DCH ALLO CANCEL DUE TO NON ACCEPTABLE AS PER OPER
M1034C43 E-DCH ALLO REJECT MAX USERS PER OPER
M1034C44 E-DCH ALLO REJECT BTS HW PER OPER
M1034C45 E-DCH SETUP FAILURE PER OPER
M1034C46 E-DCH SETUP REJECT DUE TO AC PER OPER
M1034C47 OPERATOR SHARE FOR REL99
M1034C48 OPERATOR SHARE FOR HSDPA

75 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


RAN2412: Inter Circle Roaming 6/6
Measurement M5009 Operator specific statistics (WBTS)

M5009C0 HSDPA MAC-HS DATA VOLUME PER OPERATOR


Description: Amount of transferred HSDPA MAC-hs/ehs data (including retransmissions) per OperID over the
measurement period.
Updated: The counter is updated over the measurement period. Unit: kilobytes

M5009C1 HSUPA MAC-E DATA VOLUME PER OPERATOR


Description: Amount of received HSUPA MAC-e/i data combining 10ms TTI and 2 ms TTI users (including
retransmissions) per OperID over the measurement period.
Updated: The counter is updated over the measurement period. Unit: kilobytes

76 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009


Thank You !

77 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

You might also like