Signalling Traffic Dimensioning IHSPA Rel 3 IUS v01

1/37 COO RA RD SA NE Dimensioning Guideline
Meriem Zitouni For internal use only
Dimensioning Guideline
Document type subline, COO RA MRD SA NE Access&E2E
For internal use only, 08.03.2010
Signalling Traffic Dimensioning

Dimensioning Guideline – I-HSPA Rel.3
Revision History
Version Date Change Notes
01/AFI 23.12.2009 First version – update of rel.2 (adapted for I-HSPA rel.3)
02/AFI 23.02.2010 Update after the review of a first version, ready for the second
review round
01/IUS 08.03.2010 Updated regarding the review comments.
Authors
In addition to the author named on the cover page the following persons have
collaborated on this document:
Name Department
Jacek Kotwinski COO RA RD SA NE

Table of contents
1. Introduction .......................................................................... 6
2. Concept................................................................................ 7
3. Signalling events.................................................................. 8
3.1 Mobile Originated Call.................................................................................... 8
3.2 Mobile Terminated Call .................................................................................. 8
3.3 Location Update Procedure ........................................................................... 8
3.4 PS/CS Short Message Service ...................................................................... 8
3.5 IMSI Detach ................................................................................................... 8
3.6 Serving Radio Network Subsystem Relocation.............................................. 9
3.7 Mobile Initiated and Network Initiated Session .............................................. 9
3.8 Routing Area Update...................................................................................... 9
3.9 Soft and Softer Handover............................................................................... 9
3.10 Channel Type Switching .............................................................................. 10
3.11 NRT Bit Rate Adaptation.............................................................................. 10
3.12 Inward Mobility ............................................................................................. 10
3.13 Outward Mobility .......................................................................................... 10
3.14 Multimedia Messaging Services................................................................... 11
3.15 Role Switch .................................................................................................. 11
3.16 Paging Optimization ..................................................................................... 11
4. Impact of I-HSPA Rel.3 features........................................ 12
5. Iur/Iur* signalling dimensioning .......................................... 13

5.1 Protocol stacks............................................................................................ 13
5.2 Signalling protocols ...................................................................................... 13
5.3 Iur/Iur* scenarios .......................................................................................... 14
5.4 Total Iur/Iur* signalling ................................................................................. 20
5.5 Exemplary calculation .................................................................................. 21
6. Iu signalling dimensioning.................................................. 23
6.1 Protocol stacks............................................................................................ 23
6.2 Signalling protocols ...................................................................................... 24
6.3 Iu-CS scenarios............................................................................................ 24
6.4 Total Iu-CS signalling ................................................................................... 28
6.5 Iu-PS scenarios............................................................................................ 29
6.6 Total Iu-PS signalling ................................................................................... 34
6.7 Exemplary calculation .................................................................................. 35
7. Signalling parameters ........................................................ 37

List of Figures and Tables
Figure 1. General concept of signalling dimensioning ....................................7

Figure 2: Iur/Iur* C-Plane protocol stack .........................................................13
Figure 3: Iu C-Plane protocol stack.................................................................23
Table 1: Parameters used for signalling dimensioning ...................................37

References
[1] I-HSPA Rel.3 System Architecture Description

https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/400055308
[2] E2E Network Field Performance for Offer and Field Acceptance - I-HSPA
Definitions Rel.3.
[3] Access Network Dimensioning Guideline for I-HSPA Rel.3
[4] Traffic Modelling Guideline for I-HSPA Rel.3
[5] Dimensioning Guideline I-HSPA Rel.2 Signaling Traffic Dimensioning
[6] Dimensioning Guideline RU20 Signaling Traffic Dimensioning
[7] PMN0 UTRAN Signalling Traffic Dimensioning UMR7.0
[8] PMN0 UTRAN Signalling Traffic Dimensioning RU10
1. Introduction
This document deals with the signalling part of the UTRAN interfaces Iur, Iur*, Iu-CS
and Iu-PS (Iub interface is not part of the document since it is internal I-BTS interface).
It is an addendum to [3], which describes U-Plane related dimensioning on mentioned
interfaces. The goal of this document and related Excel based Signalling Calculator is
to present general aspects of the signalling dimensioning. Detailed information about
message flows and the corresponding message lengths for different kind of scenarios /
UE behaviour can be seen in [4] and [2]. Message flow charts are intended to help to
understand which messages are sent and which NE is involved into the transaction.
Presented message flow procedures are based on general 3GPP related signalling.
Depending on the specific implementation there can appear small differences. However
this is not critical from the dimensioning point of view. Generic background for the
analysis is an experience taken out of UMR releases, further extended with analysis of
RAS0X, RU10, RU20 and, in particular, I-HSPA specific features and characteristics of
signalling protocols.
The document is inherited from RU 20 [6] and adapted to I-HSPA Rel.3. The
adaptations are small and mainly related to the renaming.
Main focuses of the analysis are the following protocols, considered on top of ATM and
IP transport options:
• Iu-CS: RANAP
• Iu-PS: RANAP
• Iur/Iur*: RNSAP
UE-adapter related signalling (RRC protocol) is considered as out of scope.

2. Concept
General concept of the dimensioning is shown on the figure below:
Figure 1. General concept of signalling dimensioning
The following points summarize the main parts of the dimensioning chain:
• Each interface has a set of signalling events (scenarios) defined,

• Event basically might be described by the following:
- name (e.g. CS Mobile Originated Call),
- set of required Traffic Model / system parameters (e.g. BHCA CS),
- detailed message flow related to the signalling transaction, containing
message lengths and summarized event’s length for ATM and IP transport
option,
- formula used to calculate signalling load, which binds the data mentioned
above.
• Signalling load resulting from the events is summed up and multiplied by additional
safety margin, to constitute overall signalling load (no QoS algorithms are
deployed, resulting bandwdith reflects the average load).
Please note, that the message flows are not available within the document. Instead,
Reader is asked to refer to the Signalling Calculator, in which all the message flows are
available in hidden sheets.
3. Signalling events
The following subchapters describe all the events which are considered in further
signalling dimensioning.
3.1 Mobile Originated Call

The Mobile Originated Call (MOC) is the procedure when the UE initiates a connection
to the network. At the beginning of MOC the authentication procedure must take place.
Call clearing can be initiated either by UE or network. In this document all connections
will be cleared by UE.
3.2 Mobile Terminated Call

The Mobile Terminated Call (MTC) is the procedure when the network site initiates a
connection to the UE. The MTC is initiated by a paging procedure. Paging procedure is
used to determine the radio cell in which the UMTS mobile subscriber is currently
located.
3.3 Location Update Procedure

The Location Update (LU) procedure is initiated exclusively by UE. It provides the VLR
and HLR with the information about the current location area of UMTS mobile
subscriber.
3.4 PS/CS Short Message Service

The purpose of the Short Message Service (SMS) is to provide the means to transfer
messages between a GSM/UMTS PLMN Mobile Station (MS) and a Short Message
Entity (SME) via a Service Centre (SC). The SC acts as a store and forward centre for
short messages.
The SMS comprises two basic services:
• SMS MO (Short Message Mobile Originated)
• SMS MT (Short Message Mobile Terminated)
Text messages to be transferred contain up to 140 octets (CS SMS).

An active MS shall be able to receive/submit a short message at any time,
independently of whether or not there is a speech or data call in progress. A report shall
always be returned to the SC/MS.
In the document it is assumed, that SMS is always originated/received by the UE being
in Idle RRC state before the transaction.
3.5 IMSI Detach

Detach procedure may be running on both Iu-CS and Iu-PS interface, either individually
or as a combined IMSI/GPRS Detach, e.g. if UE is completely switched off by the user.
IMSI Detach procedure may be invoked by a mobile station if the mobile station is
deactivated or if the USIM is detached from the mobile station.
The procedure causes mobile station to be indicated as inactive in the network.

GPRS Detach procedure may be initiated either by network or by a mobile station and
is used to detach IMSI in the network for GPRS services and/or non-GPRS services.
3.6 Serving Radio Network Subsystem Relocation

Serving Radio Network Subsystem (SRNS) Relocation procedure is performed on Iu-
CS, Iu-PS, Iur* and Iur interface. The purpose of this procedure is relocation of the Iu
interface termination and serving functionality (SRNC – adapter that controls
connections toward the CN) from one adapter to another. Advantage is reduction of the
Iur/Iur* traffic.
The procedure is related to HO procedures:
On Iu-PS interface the procedure is related to Inter Adapter HHO, ISHO to/from 2G and
ISHO to/from 3G.
On Iur interface the procedure is related to ISHO to/from 3G.
On Iur* interface the procedure is related to inter-adapter HO.
On Iu-CS interface it is related to ISHO to/from 2G.
3.7 Mobile Initiated and Network Initiated Session

Mobile Initiated Session (MIS) is the procedure when the UE initiates a packet switched
(PS) connection to the network. Whereas Network Initiated Session (NIS) is the
procedure when the network initiates a packet switched connection to the UE (e.g. used
by PUSH services). This procedure is relevant for PS Rel. 99 as well as for HSxPA
calls.
3.8 Routing Area Update

Routing Area Update (RAU) procedure is initiated exclusively by UE. It provides the
SGSN and HLR with the information about the current routing area of UMTS mobile
subscriber.
3.9 Soft and Softer Handover

Handover deals with the mobility of the end users in a mobile network: it guarantees the
continuity of the wireless services when the mobile user moves across the cellular
boundaries.
Soft handover means that the UE is connected to more than one WCDMA BTS at the
same time (also called as ‘macro diversity’). It uses more resources for a single
connection not only on the radio interface, but also in the UTRAN Iub and Iur/Iur*. The
advantage is increased probability of performing error-free data transaction.
Softer handover is a special case of soft handover where the UE is connected to more
than one sectors of a Node B. It uses more radio resources with an advantage of
getting stronger RX signal. It does not affect Iub and Iur/Iur* U-Plane traffic, but should
be considered in signalling dimensioning.
Please note, that Soft/Softer Handover is also applicable for Rel. 5 and Rel. 6 UEs,
however it is related only to UL DCH or E-DCH return channel (no Soft/Softer
handover for DL HS-DSCH possible).
3.10 Channel Type Switching

Packet switched traffic in general may result in burst utilization of the available
resources on the air interface. Therefore an efficient mechanism to re-allocate
resources from "silent" PS mobiles towards "active" ones is foreseen. This mechanism
is called channel type switching as it involves the shift of users that do not transfer data
for a given period of time from dedicated to common channels (and vice versa for active
users).
Normally the CTS were performed between two states: FACH to DCH and DCH to
FACH state. Because of HSxPA introduction there are also other possibilities:
• FACH to HS-DSCH
• HS-DSCH to FACH
• FACH to E-DCH+HS-DSCH
• E-DCH+HS-DSCH to FACH
Because of the joint HSDPA/HSUPA assumption and similarities between pure HSDPA
and HSxPA Channel Type Switching, only two latter combinations can be accounted. In
case of CTS FACH to E-DCH+HS-DSCH first radio link typically will not be created over
Iur/Iur* but in its own cell and this combination will also not be considered.
Inward and Outward Mobility are also examples of CTS but they will be presented
separately as Inward/Outward mobility.
3.11 NRT Bit Rate Adaptation

Bit Rate Adaptation is introduced for all NRT related services. It takes into account the
needs of service. The feature improves the dedicated radio resource usage and user
QoS by adapting the dedicated rate to the throughput requirements.
3.12 Inward Mobility

Inward Mobility is associated with the CTS from DCH/DCH to E-DCH/HS-DSCH state.
The procedure is connected with the mobility of the HSUPA/HSDPA capable UE.
Generally it means that the UE enters the area where the HSUPA/HSDPA is supported
and the quality of the the cell is much better then the non-HS one..
Please note that because of the joint HSDPA/HSUPA assumption, the document does
not consider the other Inward Mobility possibilities:
• HSDPA Inward Mobility (DCH/DCH to DCH/HS-DSCH)
• HSUPA Inward Mobility (DCH/HS-DSCH to E-DCH/HS-DSCH)
3.13 Outward Mobility

Outward Mobility is associated with the CTS from E-DCH/HS-DSCH to DCH state. It
occurs when UE leaves the area where the HSUPA/HSDPA is supported.
Please note that because of the joint HSDPA/HSUPA assumption, the document does
not consider the other Outward Mobility possibilities:
• HSDPA Outward Mobility (DCH/HS-DSCH to DCH/DCH)

• HSUPA Outward Mobility (E-DCH/HS-DSCH to DCH/HS-DSCH)
3.14 Multimedia Messaging Services

MM content is distributed on top of an IP bearer after PDP context is established. The
MMS comprises of two basic services:
• MMS MO (Multimedia Messaging Originated)
• MMS MT (Multimedia Messaging Mobile Terminated)
3.15 Role Switch

I-HSPA system supports a different intra-system handover procedure or the HSPA
bearers from 3GPP standardized SRNS relocation procedure. The main difference is
that radio links between UE and initial Source Adapter are not released after SRNS
relocation is completed but those are actually kept after relocation for UL DCH and
DCCH processing. Idea of this solution is to keep UE in UL synchronization on those
radio links to facilitate fast backward relocation if it will be required. This means that
while there is a hard handover switching of user DL traffic on HS-DSCH, soft handover
state for UL DCH and DCCH is still maintained after completion of Serving Adapter
change (SRNS relocation).
This functionality means that both adapters will switch (swap) roles of Drift ADA and
Serving ADA in respect to those radio links as well as Target adapter will be a new
Controlling RNC for these radio links. Such functionality is referred further as
SRNC/DRNC role switch.
This feature is not standardized in 3GPP and requires proprietary extensions in RNSAP
to support this [1]
3.16 Paging Optimization

Paging optimization is a feature which reduces the RANAP paging in the CN
(MSC/SGSN) for flat RAN architecture. Each Location Area is divided into paging
groups by grouping several I-BTSs in each paging group. Each paging group has one I-
BTS configured as paging Master and another (different) I-BTS configured as Paging
Standby from MSC/SGSN perspective. The Paging Master and Paging Standby I-BTSs
are connected to all the other I-BTSs part of the Paging Group through the Iur*
interface.
When MSC/SGSN has to invoke RANAP Paging in the LA/RA, it pages only the PM/PS
I-BTSs in the paging groups. On receiving the RANAP Paging, the PM/PS I-BTS
distributes the paging message further to all the other I-BTSs part of the paging group.
Maximum number of I-BTSs in one paging group is 32 in case of IP/Ethernet and 20 in
case of IP/ATM.
4. Impact of I-HSPA Rel.3 features

The following I-HSPA Rel.3 features are identified as impacting C-Plane dimensioning
methodology described by this document:
1. RAN 2051 Paging Optimization
In the flat RAN architecture paging load in CN is significantly increased. The

reduction of the Paging load in the CN is achieved by introducing the concept of the
Paging group under one LA/RA.
2. RAN1201 Fractional DPCH
Modification of existing HSPA related events in order to consider SRBs over HSPA
set up, basically requiring additional CID/UDP_port establishment/release and
consideration of additional IEs in NBAP, RNSAP messages.
Impact to HSPA NRT calls to be analyzed when more information is available

(in particular: Iur/Iur* traces).
5. Iur/Iur* signalling dimensioning

The following chapter describes steps needed in signalling dimensioning of the Iur/Iur*
interface.
5.1 Protocol stacks

Iur/Iur* C-Plane protocol stack is presented on the figure below:
Figure 2: Iur/Iur* C-Plane protocol stack
The control plane's protocol stack consists of RNSAP located on top of the broadband
SS7 protocols.
Please note, that IP over ATM case is currently not considered in the document.
5.2 Signalling protocols

From Control Plane point of view the following protocols appear on the Iur/Iur* interface:
RNSAP
The main RNSAP functions are:
• Radio Link Management (SRNC manages radio links using dedicated resources
in a DRNS)
• Physical Channel Reconfiguration (DRNC reallocates the physical channel

resources for a Radio Link)
• Radio Link Supervision
• Compressed Mode Control
• Measurements on Dedicated Resources
• DCH Rate Control
• Relocation Execution
• Reporting of General Error Situations
• Information Exchange
ALCAP is not used in case of AAL5 and in case of IP transport option.
5.3 Iur/Iur* scenarios

The following subchapters explain a set of signalling events used to calculate Iur/Iur*
signalling load.
The overall signalling traffic calculation based on the traffic model and the calculation of
the number of subscriber in Iur/Iur* drift handover area.
In case of homogenous distribution of subscribers, the number of subscribers in drift
handover area can be calculated on base of the following formula.
# subscribertotal ⋅ Drift _ HO _ Area
# subscriberdrift _ area =
RNC _ Area
As it is known, the Iur* interface is the interface between two adapters and Iur is
interface between adapter and RNC. So for signalling traffic dimensioning it has to be
taken into account that for some connections one adapter has SRNC functionality and
for others the second adapter has SRNC functionality.
Case 1: Adapter1 has SRNC functionality

Case 2: Adapter2 has SRNC functionality
This is the reason for which the following formulas have to be applied twice, and the
results are summed up in appropriate directions.
However, it can happen that the input (traffic model, number of subscribers) is similar
for both cases. Then there is no need to apply doubled calculations and the first
outcome can be used to estimate the total traffic.
5.3.1 Soft Handover

Formula
length⋅# subs Drift _ HO ⋅ BHCA ⋅ 0.5 ⋅ HO per _ call ⋅ SHORate ⋅ 8

data _ rate Iur ,SHO =
3600 ⋅ 1000
Length
ATM [bytes] IP [bytes]

DL UL DL UL
RNSAP 689 742 1404 1580
Message flow
Signalling Calculator -> Iur SoftHO sheet
Note: It is assumed that in case of active users in drift handover area, 50% of total
number of handovers are performed on Iur/Iur*.
5.3.2 Softer Handover

Formula
length⋅# subs Drift _ HO ⋅ BHCA ⋅ 0.5 ⋅ HO per _ call ⋅ (1 − SHORate ) ⋅ 8

data _ rateIur ,SofterHO =
3600 ⋅1000
Length

DL UL DL UL
RNSAP 212 583 576 1050
Message flow
Signalling Calculator -> Iur SofterHO sheet
Note: It is assumed that in case of active users in drift handover area, 50% of total
number of handovers are performed on Iur/Iur*.
5.3.3 Channel Type Switching (DCH to FACH)

Formulas
length ⋅ BHCA _ PS⋅# subsDrift _ HO ⋅ CTS per _ call ⋅ dch _ fach _ rate ⋅ 8
data _ rateIur,DCH _ FACH =
3600 ⋅ 1000
Length

DL UL DL UL
DCH -
> CCH RNSAP 106 212 356 538
Message flow
Signalling Calculator -> Iur CTS DCH-FACH sheet
5.3.4 NRT Bit Rate Adaptation

Formulas
length⋅# subs Drift _ HO ⋅ BRAper _ subs ⋅ 8

data _ rateIur ,BRA =
3600 ⋅ 1000
Length

DL UL DL UL
RNSAP 212 212 478 422
Message flow
Signalling Calculator -> Iur BRA sheet
Note: : Iur and Iur* procedure. The AAL5 protocol for Iur and Iur* interface is not 3GPP
compliant because AAL2 protocol is the one standardized.
5.3.5 SRNS Relocation procedure

Formulas
length⋅# subs ADA ⋅ BHCA ⋅ SRNS per _ call ⋅ 8

data _ rateIur , BRA =
3600 ⋅ 1000
Length

DL UL DL UL
RNSAP 106 53 354 168
Message flow
Signalling Calculator -> Iur SRNS Rel sheet
Note: Iur/Iur* related signalling is exchanged only in ‘UE not involved’ SRNS Relocation.
Mentioned message flow shows only Iur/Iur* related part of the transaction (it is
assumed that SCCP connection already exists). For Iu related messages please refer to
Chapter 6.
5.3.6 Inward Mobility at a DRNC controlled cell

The following subchapters described HSPA related events which might occur on
Iur/Iur*. Radio link reconfiguration is done over the interface.
Please note that in the current version of the document an average message lengths
have been taken into account for pure RNSAP messages linked with HSDPA mobility
events on Iur/Iur*. Detailed consideration will follow as soon as more information is
available.
Formulas
length⋅# subs Drift _ HO ⋅ BHCA _ HS ⋅ Inward _ Outward per _ call ⋅ inward _ rate ⋅ 8
data _ rate Iur , Inward =
3600 ⋅ 1000
Length

DL UL DL UL
RNSAP 262 137 450 239
Message flow
Signalling Calculator -> Iur HSPA Events sheet

5.3.7 Outward Mobility at a DRNC controlled cell

The following subchapters described HSPA related events which might occur on
Iur/Iur*. Radio link reconfiguration is done over the interface.
Please note that in the current version of the document an average message lengths
have been taken into account for pure RNSAP messages linked with HSDPA mobility
events on Iur/Iur*. Detailed consideration will follow as soon as more information is
available.
Formulas
length⋅# subs Drift _ HO ⋅ BHCA _ HS ⋅ Inward _ Outward per _ call ⋅ (1 - inward _ rate) ⋅ 8
data _ rate Iur ,Outward =
3600 ⋅ 1000
Length

DL UL DL UL
RNSAP 262 137 450 239
Message flow
5.3.8 HS Channel Type Switching Procedure
Formula
length ⋅ BHCA _ HS ⋅ CTS per _ call ⋅ # subs Drift _ HO ⋅ hs _ fach _ rate ⋅ 8

data _ rateIur , FACH_HS =
3600 ⋅ 1000
Length

DL UL DL UL
DCH ->
CCH RNSAP 184 190 397 407
Message flow
5.3.9 Role switch

Formulas
length⋅# subs Drift _ HO ⋅ BHCA ⋅ Re location per _ call ⋅ 8

data _ rate Iur ∗, RoleSwitch =
3600 ⋅ 1000
Length

DL UL DL UL
RNSAP 901 265 818 246
For message flow refer to [2].
Note: Only Iur* procedure;
5.3.10 Paging Optimization
Formula
1. Paging Master ADA
length ⋅ paging _ frequency ⋅# ADAinPG ⋅ 8

data _ rate Iur *UL , Paging =
1000
+ PagingLoad ForURA _ PCHstate
data _ rate Iur *DL , Paging = PagingLoad ForURA _ PCHstate
2. Non Paging Master ADA
length ⋅ paging _ frequency ⋅ 1 ⋅ 8

data _ rate Iur *DL , Paging =
1000
+ PagingLoad ForURA _ PCHstate
data _ rate Iur *UL , Paging = PagingLoad ForURA _ PCHstate

PagingLoad ForURA _ PCHstate = (# subscriber s ADA * retra _ factor * length *

∑ ( BHCA * MT
PS .CS , SMS , MMS
ratio )) * 8 / 1000
Length

DL UL DL UL
RNSAP 172 172 200 200
Message flow
Signalling Calculator -> Iur Paging sheet
Note: Only Iur* procedure
5.4 Total Iur/Iur* signalling

To estimate total Iur/Iur* signalling per appropriate protocol (RNSAP) and direction
(UL/DL), subresults of all the scenarios described above shall be summed up, taking
into account related procedure’s length. Please note that the calculation shall be
performed for both involved ADAs.
Total required signalling bandwidth per SS7 link is then calculated as follows (taking
into account number of SS7 signalling links n which is in case of I-HSP always 1):
∑ data _ rate Iur / Iur ∗, procedure
B Iur / Iur ∗, adapter1− > adapter 2 = procedures

⋅ (1 + M )
link _ load ⋅ n
Similar calculation applies for ADA2-> ADA1 relations.
An additional margin M has been introduced since the calculated data rates do not
include all possible procedures. For example the Signalling Transport Activities (i.e.
SSCOP-POLL mechanism, SCTP Heartbeat, RNSAP Dedicated Measurements, MTP
Signalling Link Test Messages) is not considered in the signalling traffic calculation.
As a first assumption M=10% is regarded as a reasonable value. Exact value will be
estimated as soon as measurement data is available.
The factor link_load denotes average load of the signalling link. It is recommended to
use 80% .
5.5 Exemplary calculation

Goal
Calculate Iur/Iur* Ethernet signalling link bandwidth for the following case:
a. 5183 subscribers per ADA (8% in drift handover area),

b. Default Traffic Model, as provided in Signalling Calculator,
c. 1 links,
Resolution (only some events shown)
a) RNSAP DL1 (ADA1 -> ADA2) signalling bandwidth consumed by Soft Handover:
length⋅# subs Drift _ HO ⋅ BHCA ⋅ 0.5 ⋅ HO per _ call ⋅ SHORate ⋅ 8

data _ rate RNSAP _ DL1, SHO = =
3600 ⋅1000
1404 ⋅ 414 ⋅ 2,25 ⋅ 0,5 ⋅ 4,3 ⋅ 0,67 ⋅ 8
= = 4,19kbps
3600 ⋅1000
b) RNSAP DL1 (ADA1 -> ADA2) signalling bandwidth consumed by Softer Handover:
length⋅# subs Drift _ HO ⋅ BHCA ⋅ 0.5 ⋅ HO per _ call ⋅ (1 − SHORate) ⋅ 8

data _ rate RNSAP _ DL1, SofterHO = =
3600 ⋅1000
576 ⋅ 414 ⋅ 2,25 ⋅ 0.5 ⋅ 4,3 ⋅ 0.33 ⋅ 8
= = 0,85kbps
3600 ⋅1000
c) RNSAP DL1 (ADA1 -> ADA2) signalling bandwidth consumed by HSPA Inward
Mobility:
length⋅# subs Drift _ HO ⋅ BHCA _ HS ⋅ Inward _ Outward per _ call ⋅ inward _ rate ⋅ 8
data _ rateRNSAP _ DL1, Inward = =
3600 ⋅ 1000
450 ⋅ 414 ⋅ 0.596 ⋅ 0.8 ⋅ 0.5 ⋅ 8
= = 0.09kbps
3600 ⋅ 1000
d) all the remaining events shall be calculated in a similar way,

e) In case of Paging Optimization, number of I-BTSs in paging group is relevant. In
case of IP/Ethernet maximum number of I-BTSs is 32 (in case of IP/ATM max
number is 20).
f) UL1 RNSAP bandwidth shall be calculated in a similar way, however taking into
account different lengths,
g) because of the fact, that from ADA 2 point of view, Traffic Model and number of
subscribers in DHO area is similar, it might be assumed that DL1 = DL2 and UL1 =
UL2,
h) total ADA1 egress signalling bandwidth per SS7 link (assuming 1 links):
∑ (data _ rate
procedures
RNSAP _ DL1, procedure )+
∑ (data _ rate
procedures
RNSAP _ UL1, procedure )
B Iur , ADA1 _ egress = ⋅ (1 + M ) =
link _ load ⋅ n
5787,09
= ⋅ (1 + 0.1) = 7957,26kbps
0.8 ⋅ 1
Because of the equation in point e), bandwidth in ingress direction will be similar (links
are loaded symmetrically).
For the calculation of remaining events’ signalling bandwidth please refer to Signalling
Calculator with a default input.
6. Iu signalling dimensioning
The following chapter describes steps needed in signalling dimensioning of the Iu-CS
and Iu-PS interface.
6.1 Protocol stacks

Iu C-Plane protocol stack is presented on the figure below:
Figure 3: Iu C-Plane protocol stack
The control plane's protocol stack consists of RANAP located on top of the broadband
SS7 protocols.
A control plane in the Iu-CS can be terminated in an MSC server and a user plane in
the Iu-CS can be terminated in an MGW. In such a case, separate Iu-CS interfaces can
be configured from the ADA to the MSC server and to the MGW.
Both interfaces (Iu-PS and Iu-CS) are mapped as IP over Ethernet or as IP over
AAL5/ATM. In I-HSPA Rel.3 only AAL5 is used. The AAL5, defined in ITU-T I.363.5, is
on top of the ATM layer and it maps higher layer protocols to ATM layer. An association
must be made between the peer nodes IP address and the encapsulating PVC.
Please note, that IP over ATM case is currently not considered in the document.
6.2 Signalling protocols

From Control Plane point of view the following protocols appear on the Iu interface:
RANAP
The main RANAP functions are:
a. relocating serving ADA

b. overall RAB management (setting up, modifying and releasing RABs)
c. requesting RAB release
d. paging the user
e. transport of NAS information between UE and CN
f. controlling the security mode in the UTRAN (sending the security keys to the
UTRAN, and setting the operation mode for security functions)
g. location reporting (transferring the actual location information from ADA to the
CN)
h. data volume reporting
i. reporting general error situations
j. information Transfer
ALCAP is not used in case of AAL5 and in case of IP transport option
6.3 Iu-CS scenarios

The following subchapters explain a set of signalling events used to calculate Iu-CS
signalling load. Description follows the same format as in the previous interfaces.
6.3.1 Mobile Originated Call

Formula
length ⋅ BHCA _ CS ⋅# subs RNC ⋅ moc _ rate ⋅ 8

data _ rate IuCS , CS _ MOC =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 848 742 2014 1926
Message flow
Signalling Calculator -> Iu MOC sheet

Note:
- for CS data calls the same message flow is accounted

- in this message flow the call clearing is initiated by the UE since it represents the
worst case regarding the signalling load
6.3.2 Mobile Terminated Call

Formula
length ⋅ BHCA _ CS ⋅# subs RNC ⋅ (1 − moc _ rate) ⋅ 8

data _ rate IuCS , CS _ MTC =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 901 742 2040 2096
Message flow
Signalling Calculator -> Iu MTC sheet
Note:
- for CS data calls the same message flow is accounted

- in this message flow the call clearing is initiated by the UE since it represents the
worst case regarding the signalling load
6.3.3 Location Update

Formula
length ⋅ ( LocationUpdates + IMSI _ Att _ Det BH )⋅# subs RNC ⋅ 8

data _ rate IuCS , LU =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 530 477 1356 1154
Message flow
Signalling Calculator -> Iu LU sheet
Note: IMSI_Att_DetBH is a common value for both Attach and Detach

(#Attach = #Detach = IMSI_Att_DetBH)
6.3.4 SMS Mobile Originated

Formula
length ⋅ SMS BH ⋅# subs RNC ⋅ sms _ mo _ rate ⋅ 8

data _ rate IuCS , MO _ SMS =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 530 636 1370 1413
Message flow
Signalling Calculator -> Iu CS SMS MO sheet
6.3.5 SMS Mobile Terminated

Formula
length ⋅ SMS BH ⋅# subs RNC ⋅ (1 − sms _ mo _ rate ) ⋅ 8

data _ rate IuCS , MT _ SMS =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 689 530 1657 1334
Message flow
Signalling Calculator -> Iu CS SMS MT sheet

6.3.6 IMSI Detach

Formula
length ⋅ IMSI _ Att _ Det BH ⋅# subs RNC ⋅ 8

data _ rate IuCS , IMSI _ Detach =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 53 159 164 244
Message flow
Signalling Calculator -> Iu IMSI Detach sheet
Note: In the message flow two types of event is shown – with and without switching off.
However, final calculations take into account with switching off case.
6.3.7 SRNS Relocation

Formula
length ⋅ BHCA _ CS ⋅ SRNS per _ call ⋅# subs RNC ⋅ 8

data _ rateIuCS ,SRNS _ Re location =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 318 530 906 1314
Message flow
Signalling Calculator -> Iu SRNS CS sheet
Note: In the message flow and length calculation signalling load is accumulated from
both:
• Source RNC (DL1 and UL1)

• Target `RNC (DL2 and UL2)
Formula
1. Paging Master ADA
length ⋅ paging _ frequency ⋅ 8

data _ rate IuCS *DL , Paging =
1000
2. Non Paging Master ADA
data _ rate IuCS *DL , Paging = 0
Length

DL UL DL UL
RNSAP 172 172 202 202
Message flow
Signalling Calculator -> Iu-CS Paging sheet
Note: Non Paging Master ADA can receive the RANAP Paging messages when both
Master and Standby are down. But since this is a rare scenario, it need not be
accounted.
6.4 Total Iu-CS signalling

To estimate total Iu-CS signalling per appropriate signalling protocol (RANAP) and
appropriate direction (UL/DL), subresults of all the scenarios described above shall be
summed up, taking into account related procedure’s length.
into account number of SS7 signalling links n which is in case of I-HSP always 1):
∑ data _ rate
procedures
IuCS , procedure
B IuCS = ⋅ (1 + M )
link _ load ⋅ n
SSCOP-POLL mechanism, SCTP Heartbeat, USSD, Inter-system handovers, MTP
Signalling Link Test Messages) is not considered in the signalling traffic calculation.
Margin M=25% is assumed as a reasonable default value. It results from the
comparison of dimensioned bandwidth against PM counter results from the real
networks, performed for eRNC. For details please refer to Chapter 5.7 in [8].
Factor link_load denotes average load of the signalling link. It is recommended to use
80%.
6.5 Iu-PS scenarios

The following subchapters explain a set of signalling events used to calculate Iu-PS
signalling load. Description follows the same format as in the previous interfaces
6.5.1 PS Mobile Originated Call

Formula
length ⋅ BHCA _ PS ⋅# subs RNC ⋅ mis _ rate ⋅ 8

data _ rate IuPS , PS _ MOC =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 901 1007 2204 2160
Message flow
Signalling Calculator -> Iu MIS sheet
Note: BHCA_PS account all PS calls, including HSxPA.
6.5.2 PS Mobile Terminating Call

Formula
length ⋅ BHCA _ PS ⋅# subs RNC ⋅ (1 − mis _ rate ) ⋅ 8

data _ rate IuPS , PS _ MOC =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 1007 1007 2408 2152
Message flow
Signalling Calculator -> Iu NRS sheet
Note: BHCA_PS account all PS calls, including HSxPA.
6.5.3 Routing Area Update

Formula
length ⋅ RoutingUpdates⋅# subs RNC ⋅ 8

data _ rate IuPS , RAU =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 530 530 1364 1218
Message flow
Signalling Calculator -> Iu RAU sheet
6.5.4 GPRS Attach

Attach procedure on Iu-PS is quite similar to the Location Update on Iu-CS. Only NAS
messages and the SGSN as core network element are different.
Formula
length ⋅ GPRS BH ⋅# subs RNC ⋅ 8

data _ rate IuPS , Attach =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 424 318 998 806
Message flow
Signalling Calculator -> Iu GPRS Attach sheet
Note: It is assumed that subscriber performs the same number of GPRS Attach and
Detach events.
6.5.5 GPRS Detach

The GPRS Detach procedure is started by sending the Detach Request message. The
detach type information element in this message may indicate one of the following:
• GPRS Detach with switching off
• GPRS Detach without switching off
• IMSI Detach
• GPRS / IMSI Detach with switching off
• GPRS / IMSI Detach without switching off
If the mobile station is not switched off, then the network sends a Detach Accept
message. Combined GPRS/IMSI Detach is performed in parallel on Iu-CS and Iu-PS.
Formula
length ⋅ GPRS BH ⋅# subs RNC ⋅ 8

data _ rate IuPS , Detach =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 53 159 172 238
Message flow
Signalling Calculator -> Iu GPRS Detach sheet
Note:
- in the message flow two types of event is shown – with and without switching off.
However, final calculations take into account with switching off case. Network
initiated case is neglected
- it is assumed that subscriber performs the same number of GPRS Attach and
Detach events
6.5.6 SRNS Relocation

Formula
length ⋅ BHCA _ PS ⋅ SRNS per _ call ⋅# subs RNC ⋅ 8

data _ rate IuPS ,SRNS _ Re location =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 318 530 906 1314
Message flow
Signalling Calculator -> Iu SRNS PS sheet
Note: In the message flow and length calculation signalling load is accumulated from
both:
• Source RNC (DL1 and UL1)

• Target RNC (DL2 and UL2)
6.5.7 SMS Mobile Originated

Formula
length ⋅ SMS BH ⋅# subs ADA ⋅ sms _ mo _ rate ⋅ 8

data _ rate IuPS , MO _ SMS =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 530 636 1370 1413
Message flow
Signalling Calculator -> Iu PS SMS MO sheet
6.5.8 SMS Mobile Terminated

Formula
length ⋅ SMS BH ⋅# subs ADA ⋅ (1 − sms _ mo _ rate ) ⋅ 8

data _ rate IuPS , MT _ SMS =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 689 530 1657 1334
Message flow
Signalling Calculator -> Iu PS SMS MT sheet
6.5.9 MMS Mobile Originated

Formula
length ⋅ MMS BH ⋅# subs ADA ⋅ mms _ mo _ rate ⋅ 8

data _ rate IuPS , MO _ MMS =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 636 742 1468 1532
Message flow
Signalling Calculator -> Iu PS MMS MO sheet
6.5.10 MMS Mobile Terminated

Formula
length ⋅ MMS BH ⋅# subs ADA ⋅ (1 − mms _ mo _ rate ) ⋅ 8

data _ rate IuPS , MT _ MMS =
3600 ⋅ 1000
Length

DL UL DL UL
RANAP 742 742 1676 1532
Message flow
Signalling Calculator -> Iu PS SMS MT sheet
Formula
1. Paging Optimization is off (not available in I-HSPA Rel.3)
length ⋅ paging _ frequency ⋅ 8

data _ rate IuPS *DL , Paging =
1000
Length

DL UL DL UL
RNSAP 172 172 202 202
Message flow
Signalling Calculator -> Iu-PS Paging sheet
6.6 Total Iu-PS signalling

To estimate total Iu-PS RANAP signalling per appropriate direction (UL/DL), subresults
of all the scenarios described above shall be summed up, taking into account related
procedure’s length.
into account number of SS7 signalling links n which is in case of I-HSP always):
∑ data _ rate
procedures
IuPS , procedure
B IuPS = ⋅ (1 + M )
link _ load ⋅ n
SSCOP-POLL mechanism, SCTP heartbeat, Inter-system handovers, MTP Signalling

Link Test Messages), Short Message Service (SMS) over Iu-PS are not considered in
the signalling traffic calculation.
Margin M=17% is assumed as a reasonable default value. It results from the
comparison of dimensioned bandwidth against PM counter results from the real
networks, performed for eRNC. For details please refer to Chapter 5.7 in [8].
Factor link_load denotes average load of the signalling link. It is recommended to use
80%.
6.7 Exemplary calculation

Goal
Calculate Iu-PS Ethernet signalling link bandwidth for the following case:
a. 5183 subscribers per ADA,

b. Default Traffic Model, as provided in Signalling Calculator,
c. 1 links,
Resolution (only some events shown)
a) RANAP DL signalling bandwidth consumed by PS MOC:
length ⋅ BHCA _ PS ⋅# subs RNC ⋅ mis _ rate ⋅ 8

data _ rate RANAP _ DL , PS _ MOC = =
3600 ⋅ 1000
2204 ⋅ 1,49 ⋅ 5183 ⋅ 0,8 ⋅ 8
= = 30,26kbps
3600 ⋅ 1000
b) RANAP DL signalling bandwidth consumed by Routing Area Update:
length ⋅ RoutingUpdates⋅# subs RNC ⋅ 8

data _ rate RANAP _ DL , RAU =
3600 ⋅ 1000
1364 ⋅ 1.8 ⋅ 5183 ⋅ 8
= = 28,28kbps
3600 ⋅ 1000
c) all the remaining events shall be calculated in a similar way,

d) total DL required signalling bandwidth per SS7 link (assuming 1 links):
∑ data _ rate
procedures
IuPS , procedure
306,43
B RANAP _ DL , IuPS = ⋅ (1 + M ) = ⋅ (1 + 0.17) = 448,15kbps
link _ load ⋅ n 0.8 ⋅ 1
e) similar calculation shall be performed for UL:
B RANAP _ UL , IuPS = 124,01kbps
f) link bandwidth might be chosen taking into account maximum of DL and UL:
SS 7 _ LinkBW = 449kbps
For the calculation of remaining events’ signalling bandwidth please refer to Signalling
Calculator with a default input.
7. Signalling parameters
The following table explains all the signalling parameters described in the document.
Acronym Description
BHCA Busy hour call attempts per subscriber (total)
Busy Hour CS Call Attempts per subscriber (DCH voice +
BHCA_CS
data)
BHCA_CS_HSPA Busy Hour CS over HSPA Call Attempts per subscriber
BHCA_PS’99 Busy Hour PS Rel. 99 Call Attempts per subscriber
BHCA_HS Busy Hour PS HSxPA Call Attempts per subscriber
moc_rate Mobile Originated ratio of all CS calls (0…1)
mis_rate Mobile Initiaded Session ratio of all PS calls (0…1)
SMSBH Busy Hour SMSes per subscriber
mo_sms_rate Mobile Originated ratio of all SMS (0…1)
HOper_call Number of handover (soft and softer) per call
SHORate Soft handover ratio (0…1)
LocationUpdates Number of location updates per subscriber per busy hour
RoutingUpdates Number of routing area updates per subscriber per busy hour
CTSper call Average number of channel type switching events per PS call
dch_fach_rate Ratio of CTS from DCH to FACH (0…1)
hs_fach_rate Ratio of CTS from E-DCH+HS-DSCH to FACH (0…1)

Average number of Bit Rate Adaptation events per subscriber
BRAper subs
in the busy hour
Average number of Inward and Outward Mobility events per
Inward_Outwardper call
HSxPA call
inward_rate Ratio of Inward Mobility (0…1)
Average number of E-DCH/HS-DSCH Cell change events per
CellChangeper call
HSxPA call
IMSI_Att_DetBH Busy Hour IMSI Attach/Detach per subscriber
SRNSBH SRNS Relocations per call

Busy Hour GPRS Attach/Detach procedures per subscriber
GPRSBH (assumption: subscriber performs the same number of GPRS
Attach and Detach events)
#subsNodeB Number of subscribers per NodeB
#subsDrift_HO Number of subscribers in drift handover area
#subsADA Number of subscribers per ADA

Table 1: Parameters used for signalling dimensioning

Signalling Traffic Dimensioning IHSPA Rel 3 IUS v01

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Signalling Traffic Dimensioning IHSPA Rel 3 IUS v01

Uploaded by

Copyright:

Available Formats

1/37 COO RA RD SA NE Dimensioning Guideline

Meriem Zitouni For internal use only

Signalling Traffic Dimensioning

Version Date Change Notes

01/IUS 08.03.2010 Updated regarding the review comments.

Jacek Kotwinski COO RA RD SA NE

4. Impact of I-HSPA Rel.3 features........................................ 12

5. Iur/Iur* signalling dimensioning .......................................... 13

7. Signalling parameters ........................................................ 37

List of Figures and Tables

Figure 1. General concept of signalling dimensioning ....................................7

Table 1: Parameters used for signalling dimensioning ...................................37

[1] I-HSPA Rel.3 System Architecture Description

UE-adapter related signalling (RRC protocol) is considered as out of scope.

Figure 1. General concept of signalling dimensioning

• Each interface has a set of signalling events (scenarios) defined,

3.1 Mobile Originated Call

3.2 Mobile Terminated Call

3.3 Location Update Procedure

3.4 PS/CS Short Message Service

Text messages to be transferred contain up to 140 octets (CS SMS).

3.5 IMSI Detach

The procedure causes mobile station to be indicated as inactive in the network.

3.6 Serving Radio Network Subsystem Relocation

3.7 Mobile Initiated and Network Initiated Session

3.8 Routing Area Update

3.9 Soft and Softer Handover

3.10 Channel Type Switching

3.11 NRT Bit Rate Adaptation

3.12 Inward Mobility

3.13 Outward Mobility

• HSDPA Outward Mobility (DCH/HS-DSCH to DCH/DCH)

3.14 Multimedia Messaging Services

3.15 Role Switch

3.16 Paging Optimization

4. Impact of I-HSPA Rel.3 features

1. RAN 2051 Paging Optimization

In the flat RAN architecture paging load in CN is significantly increased. The

2. RAN1201 Fractional DPCH

Impact to HSPA NRT calls to be analyzed when more information is available

5. Iur/Iur* signalling dimensioning

5.1 Protocol stacks

Figure 2: Iur/Iur* C-Plane protocol stack

5.2 Signalling protocols

The main RNSAP functions are:

• Physical Channel Reconfiguration (DRNC reallocates the physical channel

ALCAP is not used in case of AAL5 and in case of IP transport option.

5.3 Iur/Iur* scenarios

Case 1: Adapter1 has SRNC functionality

5.3.1 Soft Handover

length⋅# subs Drift _ HO ⋅ BHCA ⋅ 0.5 ⋅ HO per _ call ⋅ SHORate ⋅ 8

ATM [bytes] IP [bytes]

Signalling Calculator -> Iur SoftHO sheet

5.3.2 Softer Handover

length⋅# subs Drift _ HO ⋅ BHCA ⋅ 0.5 ⋅ HO per _ call ⋅ (1 − SHORate ) ⋅ 8

ATM [bytes] IP [bytes]

Signalling Calculator -> Iur SofterHO sheet

5.3.3 Channel Type Switching (DCH to FACH)

ATM [bytes] IP [bytes]

Signalling Calculator -> Iur CTS DCH-FACH sheet

5.3.4 NRT Bit Rate Adaptation

length⋅# subs Drift _ HO ⋅ BRAper _ subs ⋅ 8

ATM [bytes] IP [bytes]

Signalling Calculator -> Iur BRA sheet