Design

RNC 2600 NPGEP expansion (NSN)

Version: 1.5

Content
1

GENERAL INFORMATION................................................................................................................... 4

1.1
Formal Data..................................................................................................................................... 4
1.1.1 Documenthistory........................................................................................................................... 4
1.1.2 Agreed with................................................................................................................................... 4
1.1.3 Original Depository....................................................................................................................... 4
1.1.4 Communication............................................................................................................................. 4
1.1.5 Previous Versions......................................................................................................................... 4
1.1.6 Document History & Contact Details............................................................................................. 4
1.2
General Information concerning the Content...............................................................................5
1.2.1 Goal.............................................................................................................................................. 5
1.2.2 Scope............................................................................................................................................ 5
1.2.3 Responsibility................................................................................................................................ 5
1.2.4 Abbreviations................................................................................................................................ 5
1.2.5 Concerning Documents................................................................................................................ 5
2

INTRODUCTION................................................................................................................................... 6

DEFINITIONS........................................................................................................................................ 7

SERVICE & PARAMETER DESIGN..................................................................................................... 8

4.1
Software & Hardware Requirements.............................................................................................8
4.1.1 Software Requirements................................................................................................................ 8
4.1.2 Licence Requirements.................................................................................................................. 8
4.1.3 Hardware Requirements............................................................................................................... 8
4.2
RNC Hardware Layout.................................................................................................................... 9
4.2.1 NSN RNC Type 2600.................................................................................................................... 9
4.3
Iub IP Design.................................................................................................................................. 11
4.3.1 Protocol Control Plane................................................................................................................ 11
341.
Physical Conection (Layer-1).........................................................................................11
342.1
VLAN Configuration (Layer-2)........................................................................................ 11
34.1
IP Adresses (Layer-3)..................................................................................................... 11
34.1
ICSU allocation of the Iub-CP........................................................................................ 13
4.3.2 Protocol User Plane.................................................................................................................... 13
341.2
Physical Conection (Layer-1)......................................................................................... 13
342.
VLAN Configuration (Layer-2)........................................................................................ 13
34.2
IP Adresses (Layer-3).................................................................................................... 13
34.2
Iub UP Protocols............................................................................................................ 13
4.3.3 RACE Interface Design for Iub extension...................................................................................14
4.4
IuPS IP Design............................................................................................................................... 16
4.4.1 Protocol Control Plane................................................................................................................ 16
41.
Physical Conection (Layer-1)......................................................................................... 16
42.1
VLAN Configuration (Layer-2)........................................................................................ 17
43.1
IP Adresses (Layer-3).................................................................................................... 17
4.1
ICSU allocation of the IuPS-CP......................................................................................19
4.4.2 Protocol User Plane.................................................................................................................... 19
41.2
Physical Connection (Layer-1).......................................................................................19

42.
43.2
4.2
4.4.3

VLAN Configuration (Layer-2)........................................................................................ 19

IP Adresses (Layer-3).................................................................................................... 19
IuPS UP Protocols......................................................................................................... 19
RACE Interface Design for IUPS extension................................................................................19

4.5
QoS on the Iub & IuPS Interface.................................................................................................. 21
4.5.1 General QoS Requirements........................................................................................................ 21
4.6
Parameters..................................................................................................................................... 21
4.6.1 Iub related Parameters............................................................................................................... 21
4.6.2 IuPS related Parameters............................................................................................................. 21
4.7
Planing Tool x:akta........................................................................................................................ 21
4.7.1 x:akta Iub changes...................................................................................................................... 21
4.7.2 x:akta IuPS changes................................................................................................................... 21
4.8
5

Capacity dimensioning................................................................................................................. 22
REFERENCES.................................................................................................................................... 23

List of Figures
Figure 1: Front pannel of the NPGEP plug-in unit.......................................................................................... 8
Figure 2: RNC Type-2600 cabinet layout....................................................................................................... 9
Figure 3: RNC 2600 Iub design.................................................................................................................... 12
Figure 4: ICSU subnet allocation.................................................................................................................. 13
Figure 5: Race-Router design...................................................................................................................... 15
Figure 6: RNC 2600 IuPS design................................................................................................................. 18
Figure 7: ICSU subnet allocation.................................................................................................................. 19

List of Tables
Table 1: NPGEP limitations............................................................................................................................ 9
Table 2: NPGEP Service allocation RNC Type 2600....................................................................................10
Table 3: Iub VLAN allocation table................................................................................................................ 11
Table 4: Iub IP-Adress Scheme.................................................................................................................... 11
Table 5: Transfer network as IP destination table......................................................................................... 14
Table 7: Race-Router template.................................................................................................................... 16
Table 8: IuPS VLAN allocation table for additional Interfaces......................................................................17
Table 9: IuPS CP/UP IP address allocation scheme....................................................................................17
Table 10: IuPS CP/UP IP address allocation scheme..................................................................................20

1 Service & Parameter Design

1.1 Software & Hardware Requirements

1.1.1 Software Requirements

The implementation of the additional NPGEP cards for the IuB and IuPS interfces are designed on the NSN
UTRAN software RU40.

1.1.2 Licence Requirements

There are no new Licences needed for the expansion of the NPGEP cards for Iub and IuPS. The already
introduced Features fullfill the requirements.

RAN 74: IP based Iub for flexi WCDMA BTS

RAN750: IP based Iu-PS

1.1.3 Hardware Requirements

There are no new Hardware requirements for the expansion of the NPGEP cards for IuB and IuPS
necessary. The already introduced NPGEP card will fulfil the Hardware requirement. In the following, you
will find the specification of the NPGEP card.
Port 0 GE electrical (not used)
Port 1 GE electrical (not used)
Port 2 GE optical
Port 3 GE optical

Figure 1: Front pannel of the NPGEP plug-in unit

The card has the following limitations.

NPGE Card Limitations
# GE Ports (Electrical/Optical)
2/2
Port/Card Throughput (Gbps)
1/1,65
Max Ethernet MTU size (bytes)
4000
# IP Based Routes
3000
# VLANs
600
# BFD Sessions
600
# UDP Ports
64509
# IP Connection Setups/s
1800
# GTP Tunnels Active/Total
30000/300000
# GTP Tunnel Creations/s
800
Table 1: NPGEP limitations

1.2 RNC Hardware Layout

1.2.1 NSN RNC Type 2600

Since the project PILAR was finisched, only NSN RNC-2600 are remaining in the live-network. In the
following picture, you will see the racklayout and also the allocation of the Iub and IuPS interfaces to the
additional NPGEP cards.

Figure 2: RNC Type-2600 cabinet layout

The following table contains the allocation of the Iub and IuPS interface to the different NPGEP cards.
RNC
Rack
RNAC
RNAC
RNAC
RNAC
RNAC

Shelf

Slot

Port

1
1

17
17

2
3

Lan1 IuPS-1 (UP&CP)

Lan2 IuPS-1 (UP&CP)

17

Lan1 IuPS-1 (UP&CP) protection

Lan2 IuPS-1 (UP&CP) protection
Iub#1_1

2
1

17
18

3
2

RNAC
RNAC

1
2

18
18

3
2

RNAC
RNBC

2
1

18
17

3
2

RNBC

17

RNBC

17

RNBC

17

RNBC

15

1 only valide for NOKIA RNC

Service

RR Port
RNC1
RR1-2/9
RR12/10
RR2-2/9

VLANID
RNC1
255/257
256/258

RR Port
RNC2
2/13
2/14

VLANID
RNC2
260/262

RR Port
RNC3
2/4
2/5

265
266

261/263
2/4

2/13
RR22/10
RR12/11

Iub#1_1 - protection

RR22/11

Lan1 IuCS-1 (UP&CP) +

Lan1 Iur (UP&CP)
Lan2 IuCS-1 (UP&CP) +
Lan2 Iur (CP)
Lan1 IuCS-1 (UP&CP) +
Lan1 Iur (UP&CP)
protection
Lan2 IuCS-1 (UP&CP) +
Lan2 Iur (CP) protection
Iub#1_2

RR12/17
RR12/18
RR22/17
RR22/18
RR12/12

2/5
2/14
2/6
259

2/15

2/6

2/15
270/272
274/275
271/273
276

2/19
2/20

269

264

280/282
284/285
281/283
286

2/211
2/221

290
294
291
296

2/211
2/19
259
225

2/20
2/16

2/221
264
230(Huawe

not
defined

269
235

(Huawei)
RNBC
RNBC

1
2

15
15

3
2

Iub#1_2 - protection

RR22/12

RNBC
RNBC

2
3

15
15

3
2

Iub#1_3

RR1-2/7

RNBC
RNBC

3
4

15
15

3
2

Iub#1_3 - protection

RR2-2/7

RNBC
RNBC

4
3

15
17

3
2

Lan1 IuPS-2 (UP&CP)

RR12/23

RNBC
RNBC
RNBC

3
4
4

17
17
17

3
2
3

Lan2 IuPS-2 (UP&CP)

RR12/24

Lan1 IuPS-2 (UP&CP) protection

RR22/23

Lan2 IuPS-2 (UP&CP) protection

RR22/24

i)
2/16

259
226(Huawe
i)

2/44

not
defined
264
231(Huawe
i)

2/44
255
205
(Huawei)
256
206(Huawe
i)
257
207(Huawe
i)
258
208(Huawe
i)

Table 2: NPGEP Service allocation RNC Type 2600

2/38
2/39
2/38
2/39

not
defined

269
236

not
defined
210(Huawe
i)
211(Huawe
i)
212(Huawe
i)
213(Huawe
i)

not
defined

215

not
defined

216
not
defined

217

not
defined

218

1.3 Iub IP Design

1.3.1 Protocol Control Plane

2
Physical Conection (Layer-1)
There are no changes concerning the layer-1.

3
VLAN Configuration (Layer-2)
One target was, to keep the modifications as simple as it is possible. Therefor we decided to configure for
all Iub-interfaces the same VLAN.
VLAN ID
259

Usage
VLAN IDs for connection of RACE-Router to
RNC for Iub
Table 3: Iub VLAN allocation table

4
IP Adresses (Layer-3)
For each RNC an /29 subnet is reserved. This subnet contains six hosts IP addresses and will be
allocated like described in the following table.
IP-Adresse
Subnet + 0
Subnet + 1
Subent + 2
Subnet + 3
Subnet + 4
Subnet + 5
Subent + 6
Subnet + 7

Verwendung
Netzwerk-Adresse
Race-Router physical i/f
n/c
n/c
RNC (NPGEP Port i/f) Iub1
RNC (NPGEP Port i/f) Iub1b
RNC (NPGEP Port i/f) Iub1c
Broadcast-Adresse

Table 4: Iub IP-Adress Scheme

The following picture shows the testbed configuration scheme like described.

Figure 3: RNC 2600 Iub design

5
ICSU allocation of the Iub-CP
The maximum amount of ICSU card in an RNC Type 2600 config step-3 are 38 ICSU cards. The target
was, to reach from each NodeB all ICSU cards. This aim makes it necessary to reserve an /26 subnet
(62 hosts) fr the ICSU cards. Details are shown in the following picture.

Figure 4: ICSU subnet allocation

From NodeB side, no modifications concerning the IP addressing scheme is necessarry, because we keep
the /26 subnet for the iubSubnet for all NodeBs, independently of the NPGEP interface cards.

5.1.1 Protocol User Plane

6
Physical Conection (Layer-1)
There are no changes concerning the layer-1.

7
VLAN Configuration (Layer-2)
The VLAN allocation for the user-plane ist the same as described in the chapter 4..3.1.2 in the Iub VLAN
allocation table.

8
IP Adresses (Layer-3)
The IP adressing scheme will be the same as described in the chapter 4.3.1.3 in the table Iub IP-Adress
Scheme.

9
Iub UP Protocols
There are no changes concerning the Iub user-plane protocolls.

9.1.1 RACE Interface Design for Iub extension

As described before the expansion will be done by adding addition ports in the existing VLAN and in the
existing IP-Range. The RACE Router has to provide additional Interfaces these Interfaces will be assigned
to the existing Iub VLANID. So no new VLAN-interface is needed.
The distribution on the interfaces is static and part of the NodeB routing planning. NodeBs get different IP
Adresses from the RACE-RNC transfer network as IP destination, as shown in the table below.
IP-Adresse
Subnet + 0
Subnet + 1
Subent + 2
Subnet + 3
Subnet + 4
Subnet + 5
Subent + 6
Subnet + 7

Verwendung
Netzwerk-Adresse
Race-Router physical i/f
n/c
n/c
RNC (NPGEP Port i/f) Iub1
RNC (NPGEP Port i/f) Iub1b
RNC (NPGEP Port i/f) Iub1c
Broadcast-Adresse

Table 5: Transfer network as IP destination table

The table below shows the definition for VLAN and RACE Interfaces, please note that the interface
numbers are planning rules these definition must not be fixed in the xakta implementation and in the
template rules. The VLANID to usage assigment is fix. The 3.RNC is not a normal configuration
nevertheless there was the need for this configuration in the past as an exception; also this exception shall
be defined in this design. Deatiled information see Table 2: NPGEP Service allocation RNC Type 2600
Note: for the Huawei system it is supposed not to be possible to use the existing VLAN and IP Subnet for
the additional physical interfaces. Also the expansion for NSN in this way is limited to 3 because of the IP
network size (/29 = 6 Hosts). So for additional Interfaces in these cases new VLAN and new IPSubnetworks has to be configured, this will be described and implemented in a second step. => tbd.
The CP traffic from the NodeB to the RNC uses static routes on the RACE to be forwarded to the ICSU
network inside the RNC behind the NPGEP Interfaces. This traffic has to be distributed over all Interfaces
to the RNC, for this a static route to the same ICSU Network has to be added for every new Iub Port. The
traffic distribution is done by the rules of equal cost multi path routing (ECMP). To avoid black-holing in
case of failure on one of the Iub Interface pairs the static route shall be controlled by object tracking. The
tracked object must be the physical interface to the RNC (the gateway of the static route). The
configuration line is shown below, has to be done symmetrical on both routers.
Object definition
track <TRACK_ID> interface <RACE_INTERFACE> line-protocol
TRACK_ID : 3<physical port number, 2-digit with leading 0>
Static route
ip
route
vrf
IUB
<RNC_ICSU_IUB>
255.255.255.192
<RNC_ID>_Iub_<RACE_INTERFACE> track <TRACK_ID>

<RNC_IUB_IP>

name

The lines and the picture below shows the Testlab implementation and tries to explain the
function of the object tracking for the ICSU static route
track 304 interface GigabitEthernet2/4 line-protocol
!
track 309 interface GigabitEthernet2/9 line-protocol

RACELAB3-1#sh run | incl ip route vrf IUB

ip route vrf IUB 10.80.216.192 255.255.255.192 10.80.216.133 name RNC912_Iub_Gi2/4 track 304
ip route vrf IUB 10.80.216.192 255.255.255.192 10.80.216.132 name RNC912_Iub_Gi2/9 track 309

Note that the backup procedure changes by introduction of the object tracking
control for the static route, when the connection between active NPGEP board and
RACE#1 fails the static route will be deleted in the IUB vrf on RACE#1 and the
route to ICSU network will be learned over the iBGP from RACE#2. So the traffic
will be forwarded via the MPLS path to RACE#2 to reach the active NPGEP port at
RACE#2 instead of VLAN Switching.
When an RNC with an existing Iub has to be extended by additional Iub Interfaces the existing static route
has to be deleted and configured again with the object tracking extension. Otherwise there are two static
routes in the configuration one with object tracking the other one without.
Figure 5: Race-Router design
The table below shows the configuration templates, reports and templates has to be adjusted during further
implementation in xakta.
Naming in Templates has to be adapted to final report definition
RACE#1
INTERFACE_TYPE = RNC
interface <INTERFACE_ID>
description locally connected to RNC
<NEIGHBOR_BASEKEY> for
<INTERFACE_TYPE>
switchport
no switchport access vlan 999
switchport trunk encapsulation dot1q
switchport trunk allowed vlan
<INTERFACE_VLAN_STRING>
switchport mode trunk
spanning-tree portfast trunk

RACE#2
INTERFACE_TYPE = RNC
interface <INTERFACE_ID>
description locally connected to
<NEIGHBOR_BASEKEY> for <INTERFACE_TYPE>
switchport
no switchport access vlan 999
switchport trunk encapsulation dot1q
switchport trunk allowed vlan
<INTERFACE_VLAN_STRING>
switchport mode trunk
spanning-tree portfast trunk

Interface
Template as
used already
for IUB and LTE
in usymetrical
configuration

mtu 9216
load-interval 30
carrier-delay msec 0
wrr-queue bandwidth 60 35 5
wrr-queue cos-map 1 1 0
wrr-queue cos-map 1 2 1
wrr-queue cos-map 2 1 2 3
wrr-queue cos-map 2 2 4
wrr-queue cos-map 3 2 6 7
mls qos trust dscp
flowcontrol send of
no cdp enable
service-policy output PM-VOICE-out
arp timeout 240
no shut

mtu 9216
load-interval 30
carrier-delay msec 0
wrr-queue bandwidth 60 35 5
wrr-queue cos-map 1 1 0
wrr-queue cos-map 1 2 1
wrr-queue cos-map 2 1 2 3
wrr-queue cos-map 2 2 4
wrr-queue cos-map 3 2 6 7
mls qos trust dscp
flowcontrol send of
no cdp enable
service-policy output PM-VOICE-out
arp timeout 240
no shut

interface Vlan<VLAN_ID>
description RNC <RNC_ID> Iub lan
mtu 2000
ip vrf forwarding IUB
ip address <RNC_IUB_RACE1_IP>
255.255.255.248
no ip redirects
no ip unreachables
no ip proxy-arp
standby delay minimum 120 reload 120
standby version 2
standby <VLAN_ID> ip <RNC_IUB_HSRP_IP>
standby <VLAN_ID> timers msec 100 msec 600
standby <VLAN_ID> priority 170
standby <VLAN_ID> preempt delay minimum 120
standby <VLAN_ID> authentication
HSRP<VLAN_ID>
service-policy output PM-VOICE-out
no shut

interface Vlan<VLAN_ID>
description RNC <RNC_ID> Iub lan
mtu 2000
ip vrf forwarding IUB

standby <VLAN_ID> authentication HSRP<VLAN_ID>

service-policy output PM-VOICE-out
no shut

track <TRACK_ID> interface

<RACE_INTERFACE> line-protocol

track <TRACK_ID> interface <RACE_INTERFACE>

line-protocol

ip route vrf IUB <RNC_ICSU_IUB>

255.255.255.192 <RNC_IUB_IP> name
<RNC_ID>_Iub_<RACE_INTERFACE> track
<TRACK_ID>

ip address <RNC1_IUB_RACE2_IP> 255.255.255.248

no ip redirects
no ip unreachables
no ip proxy-arp
standby delay minimum 120 reload 120
standby version 2
standby <VLAN_ID> ip <RNC_IUB_HSRP_IP>
standby <VLAN_ID> timers msec 100 msec 600
standby <VLAN_ID> priority 120
standby <VLAN_ID> preempt delay minimum 120

ip route vrf IUB <RNC_ICSU_IUB> 255.255.255.192

<RNC_IUB_IP> name
<RNC_ID>_Iub_<RACE_INTERFACE> track
<TRACK_ID>

Table 6: Race-Router template

Configuration
of VLAN
Interface

Configuration
of ICSU static
routes

9.2 IuPS IP Design

9.2.1 Protocol Control Plane

10 Physical Conection (Layer-1)

There are no changes concerning the layer-1.

11 VLAN Configuration (Layer-2)

The desission for the VLAN configuration is the same as we dicided for Iub. The same VLANs which were
already used for the user-plane one and two and also for the control-plane one and two will be used for the
user-plane three and four and for the control-plane three and four. Details can be found in the following
table.
Node

VLAN name

RNC
RNC
RNC
RNC

Iu-PS UP LAN1
Iu-PS UP LAN2
Iu-PS CP LAN1
Iu-PS CP LAN2

VLAN
number
255
256
257
258

Description
Lan1 UP3 traffic for NP2GE-NPGE14-0
Lan2 UP4 traffic for NP2GE-NPGE14-1
Lan1 CP3 traffic for NP2GE-NPGE14-0
Lan2 CP4 traffic for NP2GE-NPGE14-1

Table 7: IuPS VLAN allocation table for additional Interfaces

12 IP Adresses (Layer-3)
The IP adress scheme will be similar to that scheme we implement for Iub. For each RNC a /29 subnet will
be reserved for the control-plane one and two. This subnet will contain six host IP addresses and will be
allocated like described in the following table.
Iu-PS UP/CP range
RNC
(NP2GE/GOU)
to
RACE-Router /29 IP
subnet
Subnet ID+0
Subnet ID+1
Subnet ID+2
Subnet ID+3
Subnet ID+4
Subnet ID+5
Subnet ID+6
Subnet ID+7

Use

Network Address
Logical
IP
address
RACE-Router
(HSRP/VRRP)
Physical IP address RACE-Router-1
Physical IP address RACE-Router-2
RNC (GOU/NP2GE-0 interface address)
RNC (GOU/NP2GE-14 interface address)
free
Broadcast

Table 8: IuPS CP/UP IP address allocation scheme

The following picture shows the testbed configuration scheme like described.

Figure 6: RNC 2600 IuPS design

13 ICSU allocation of the IuPS-CP

For the ICSU card which are allocated for the IuPS control-plane, a /28 subnet is reserved. From this
subnet, four IP addresses will be used for the ICSU AA0/AA1 virtual interfaces. Details will be shown in the
following picture.

Figure 7: ICSU subnet allocation

13.1.1 Protocol User Plane

14 Physical Connection (Layer-1)

There are no changes concerning the layer-1.

15 VLAN Configuration (Layer-2)

The VLAN allocation for the user-plane ist the same as described in the chapter 4.4.1.2 in the IuPS VLAN
allocation table for additional UP/CP.

16 IP Adresses (Layer-3)
The IP adressing scheme will be the same as described in the chapter 4.4.1.3 in the table IuPS CP/UP IP
address allocation scheme.

17 IuPS UP Protocols
There are no changes concerning the IuPS user-plane protocolls.

17.1.1 RACE Interface Design for IUPS extension

As described before the expansion will be done by adding addition ports in the existing VLAN and in the
existing IP-Range. The RACE Router has to provide additional Interfaces these Interfaces will be assigned
to the existing IUPS_UP/CP 1&2 VLANID. So no new VLAN-interface is needed.
The distribution on the interfaces will be done dynamicly by the RNC.
The table below shows the definition inside the existing RNC-RACE IP network.

Iu-PS UP/CP range - RNC

(NP2GE/GOU) to RACE-Router /
29 IP subnet
Subnet ID+0
Subnet ID+1
Subnet ID+2
Subnet ID+3
Subnet ID+4
Subnet ID+5
Subnet ID+6
Subnet ID+7

Use

Network Address
Logical IP address RACE-Router
(HSRP/VRRP)
Physical IP address RACE-Router-1
Physical IP address RACE-Router-2
RNC IUPS_UP/CP
RNC IUPS_UP/CP b
free
Broadcast

Table 9: IuPS CP/UP IP address allocation scheme

The table below shows the definition for VLAN and RACE Interfaces, please note that the interface
numbers are planning rules these definition must not be fixed in the xakta implementation and in the
template rules. The VLANID to usage assigment is fix. The 3.RNC is not a normal configuration
nevertheless there was the need for this configuration in the past as an exception; also this exception shall
be defined in this design. Detailed information see Table 2: NPGEP Service allocation RNC Type 2600
Note: For the Huawei system it is supposed to be not possible to use the existing VLAN and IP Subnet for
the additional physical interfaces. So for Huawei new VLAN and new IP-Subnetworks has to be configured,
this will be described and implemented in a second step. => tbd.
The CP traffic from the SGSN to the RNC uses static routes on the RACE to be forwarded to the ICSU
network inside the RNC behind the NPGEP Interfaces. This traffic has to be distributed over all Interfaces
to the RNC, for this a static route to the same ICSU Network has to be added for the new interface. The
traffic distribution is done by the rules of equal cost multi path routing (ECMP). To avoid black-holing in
case of failure on one of the IU Interface pairs the static route shall be controlled by object tracking. The
tracked object must be the physical interface to the RNC (the gateway of the static route). The
configuration line is shown below, has to be done on both routers.
Object definition
track <TRACK_ID> interface <RACE_INTERFACE> line-protocol
TRACK_ID : 2<physical port number, 2-digit with leading 0>
Static route
RACE#1:

ip route vrf IUPS_CP1 <RNC1_ICSU_AA00> 255.255.255.240 <RNC1_IUPSCP1b_IP>

name ICSU0-RNC<RNC1_ID> track <TRACK_ID>

RACE#2
ip route vrf IUPS_CP2 <RNC1_ICSU_AA01> 255.255.255.240 <RNC1_IUPSCP2b_IP>
name ICSU1-RNC<RNC1_ID> track <TRACK_ID>
Note: When adding the 2. static route the xisting route has to be deleted and
reconfigured with object tracking.

17.2 QoS on the Iub & IuPS Interface

17.2.1 General QoS Requirements

There are no changes concerning the Iub and IuPS quality of service design.

17.3 Parameters

17.3.1 Iub related Parameters

All parameters which have to be modivied are described and highlighted in red in the following EXCEL
table (RU40 Transport Parameter DESIGN).

NSN_3G_Transport_
Parameters_RU40_Itf_xakta_CCM_V2.16.xlsx

17.3.2 IuPS related Parameters

All parameters which have to be modivied are described and highlighted in red in the following EXCEL
table.

Nokia_XAKTA_IuPS_I
P_Parameters_v2 5_20140512.xlsx

17.4 Planing Tool x:akta

17.4.1 x:akta Iub changes

For the transport planning tool x:akta, the following x:akta reports have to be adapted for Iub.

01_RNC_IP_Report
03_FTM_IP_TRANS_Report
New RACE IUB report (incl. DCN ?)
(remove IUB/DCN data from 04_RNC1 and 05_RNC2_Report ????)

17.4.2 x:akta IuPS changes

For the transport planning tool x:akta, the following x:akta report have to be adapted for IuPS.

12_NOKIA_IUPS
04_RNC1_Report
05_RNC2_Report
(remove IUB/DCN data from 04_RNC1 and 05_RNC2_Report ????)

17.5 Capacity dimensioning

18 References

End of document