05 RN30035EN40GLA0 MCRNC Iu IuB Planning PDF

Module 5 – mcRNC Iu/IuB Planning
3GTPL RU40
RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

Nokia Solutions and Networks Academy
Legal notice
Intellectual Property Rights
All copyrights and intellectual property rights for Nokia Solutions and Networks training documentation, product
documentation and slide presentation material, all of which are forthwith known as Nokia Solutions and Networks
training material, are the exclusive property of Nokia Solutions and Networks. Nokia Solutions and Networks owns
the rights to copying, modification, translation, adaptation or derivatives including any improvements or
developments. Nokia Solutions and Networks has the sole right to copy, distribute, amend, modify, develop,
license, sublicense, sell, transfer and assign the Nokia Solutions and Networks training material. Individuals can
use the Nokia Solutions and Networks training material for their own personal self-development only, those same
individuals cannot subsequently pass on that same Intellectual Property to others without the prior written
agreement of Nokia Solutions and Networks. The Nokia Solutions and Networks training material cannot be used
outside of an agreed Nokia Solutions and Networks training session for development of groups without the prior
written agreement of Nokia Solutions and Networks.
2 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

Outline
• mcRNC Site solution Overview
• Scheduling
• Protection and resiliency
• Ethernet interface planning
• Iub/Iu user plane configuration
• Iub/Iu control plane configuration
• Iub/Iu IP addressing
• Routing

Overview of Site Solution
• mcRNC Evolved Site Solution
• Site solution based on Ethernet switchport configuration in the site routers
• One VLAN spans over the EIPUs and a single site router/switch (user plane)
• Redundancy is based on the static routes configuration (L3 type of a site solution)
• BFD Single-Hop with static routes applied for next-hop supervision
• Available at RU30/mcRNC2.0 release / Supports 1GE interfaces
• mcRNC OSPF Site Solution
• Site solution where dynamic routing is applied for IP redundancy (except Iu/Iur control plane)
• BFD Single-Hop is applied for OSPF neighbour monitoring
• Available at RU30/mcRNC2.0 for 1GE
• Available at RU40/mcRNC3.0 for both 1GE and 10GE
• mcRNC VRRP/HSRP Site Solution
• Site solution based on Ethernet switchport configuration in the site routers
• Site router redundancy is managed with VRRP or HSRP protocols (L2 type of a site solution)
• One VLAN spans over the EIPUs and site routers/switches (not further to network – no “L2 Iub”
support)
• Provides planning principles compatibility with the current IPA-RNC VRRP/HSRP site solution
• Available at RU40/mcRNC3.0 release / Supports 1GE and 10GE interfaces
mcRNC and RNC2600 Transport Comparison
RNC2600 (NPGEP) Multicontroller RNC
Active / standby interface protection All interfaces active, enabling comprehensive connectivity monitoring and load
sharing
Network, application, and unit protection are combined in single protection Application and unit protection by FlexiPlatform HA services, network protection
mechanism (NPGEP, 2N redundancy) based on site solution (L3 routing, VRRP)
End-to-end layer 2 network support mcRNC requires L3 site routers,
L2 end-to-end (L2 Iub) solution support can be considered in later releases based
on the customer demand. L3 site routers are preferred from the NSN view.
Logical interfaces (Iu/Iur/Iub) can be placed on separate physical interfaces (so Logical interfaces (Iu/Iur/Iub) can be placed on separate physical interfaces (So
called „Dedicated NPGE“ configuration) called „Dedicated EIPU“ configuration)
RNC2600 Site Solutions mcRNC Site Solutions

- HSRP/VRRP Site Solution - Static route + BFD Single-Hop (Evolved SiSo, RU30)
- OSPF supported - OSPF Site Solution (RU30)
- HSRP/VRRP Site Solution (RU40)
Routing instances separation only available with using separate dedicated VRF feature supported for separating the routing instances
NPGE(P) units - Can be used for simplified Static route setup
- Needed with OSPF based routing (Iu/Iur control plane and SCTP Multi-Homing
with static routes)
IP Based Route scheduling available for Iub (IFC, Internal Flow Control) IP Based Route scheduling available for all interfaces (Virtual or Real Queues,
Internal Flow Control or E-RED)
Spanning tree required for ESA protection No spanning tree needed

BCN-B Inter BCN Connection

BCN-A Inter BCN Connection

mcRNC Evolved Site Solution
• Supports only 1GE interfaces
• Ethernet Interface configuration
• L3 interfaces in RNC, VLAN interfaces (switchports) in site routers
• Ethernet link supervision
• L1 mechanisms (Loss-of-Signal/Carrier and remote fault indicator), and
• Single-hop BFD
• Route redundancy
• Redundant static routes (ECMP in RNC, primary/backup routes in routers)
• Feature requirement
• RAN2440: Fast IP Rerouting

mcRNC Evolved Site Solution Topology
mcRNC BCN #1 mcRNC BCN #2
U
U
P
E
P
E
P
E
P
E
-0
-2
-1
-3
I
I
IPU1 IPU2 IPU3 IPU4
VLAN_Iu1 /27
VLAN_Iub1 /27
VLAN_Iu2 /27
VLAN_Iub2 /27
VLAN_Iu1 /27
VLAN_Iub1 /27
VLAN_Iu2 /27
VLAN_Iub2 /27
VLAN_Iu1 /27
VLAN_Iub1 /27
VLAN_Iu2 /27
VLAN_Iub2 /27
VLAN_Iu1 /27
VLAN_Iub1 /27
VLAN_Iu2 /27
VLAN_Iub2 /27
P
S
P
S
P
S
P
S
P
S
P
S
P
S
P
S
F
F
7
5
1
6
1
5
1
6
1
BFD
VLAN_Iub1 VLAN_Iub2
VLAN_Iu1 VLAN_Iu2
+ -48V TO -60V + -48V TO -60V
34A MAX. 34A MAX.
REMOVE LABEL FOR REMOVE LABEL FOR

Cisco 7603-S SYSTEM GROUND Cisco 7603-S SYSTEM GROUND
PEM-DC PEM-DC
7600-ES+40G3CXL 7600-ES+40G3CXL
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
1
9
A/L
A/L
Cisco Cisco
EXT CLK EXT CLK
STATUS STATUS
A/L
A/L
ETHERNET SERVICES MODULE CLASS 1 ETHERNET SERVICES MODULE CLASS 1
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
2
8
LASER LASER
7600-ES+40G3CXL 7600-ES+40G3CXL
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
1
9
A/L
A/L
EXT CLK EXT CLK
STATUS STATUS
A/L
A/L
ETHERNET SERVICES MODULE CLASS 1 ETHERNET SERVICES MODULE CLASS 1
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
2
8
LASER LASER
7600-ES+20G3CXL 7600-ES+20G3CXL
7600 I 7600 II
10
12
14
16
18
10
12
14
16
18
0
8
A/L
A/L
EXT CLK EXT CLK
STATUS STATUS
A/L
A/L
ETHERNET SERVICES MODULE ETHERNET SERVICES MODULE
11
13
15
17
19
11
13
15
17
19
1
9
CLASS 1 LASER CLASS 1 LASER

P U
F
11
S P
I
VLAN_Iu1 /30 E
STATUS
STATUS
STATUS
PEM-DC
EXT
EXT
EXT
7600-ES+40G3CXL
7600-ES+40G3CXL
7600-ES+20G3CXL
Iu1 7
CLK
CLK
CLK
ETHERNET SERVICES MODULE

1 0 2 1 2 1
3 2 4 3 4 3
P VLAN_Iub1 /30
5 4 6 5 6 5
7 6 8 7 8 7
Iub1 F
34A MAX.
9 8 10 9 10 9
+ -48V TO -60V
IPU1
11 10 12 11 12 11
S -
13 12 14 13 14 13 0
15 14 16 15 16 15
VLAN_Iu2 /30
17 16 18 17 18 17
19 18 20 19 20 19
Iu3
A/L A/L A/L
LASER
LASER
A/L A/L A/L
CLASS 1
CLASS 1
8
CLASS 1 LASER
22 21 22 21
VLAN_Iub2 /30
24 23 24 23
26 25 26 25
Iub3 P
28 27 28 27
30 29 30 29 F
32 31 32 31
U
34 33 34 33
36 35 36 35
S P
38 37 38 37
Iu5 I
Cisco 7603-S
40 39 40 39
5 VLAN_Iu3 /30 E
SYSTEM GROUND
REMOVE LABEL FOR
mcRNC BCN #1
Iub5 1
P VLAN_Iub3 /30
F
S
IPU2
Iu7 -
6 VLAN_Iu4 /30 2
Iub7 1 VLAN_Iub4 /30
7600 I
Cisco
P U
F
S P
I
VLAN_Iu5 /30 E
Iu2 7
P VLAN_Iub5 /30
Iub2 F
Cisco
IPU3
7600 II
VLAN_Iu6 /30 -
1
Iu4
8 VLAN_Iub6 /30
STATUS
STATUS
STATUS
PEM-DC
EXT
EXT
EXT
7600-ES+40G3CXL
7600-ES+40G3CXL
7600-ES+20G3CXL
CLK
CLK
CLK

1 0 2 1 2 1
Iub4 P
3 2 4 3 4 3
5 4 6 5 6 5
7 6 8 7 8 7
34A MAX.
F U
9 8 10 9 10 9
+ -48V TO -60V
S
Ref: Basic SiSo (mcRNC 1.0)
11
13
10
12
12
14
11
13
12
14
11
13
Iu6 P
I
15 14 16 15 16 15
17 16 18 17 18 17
5 VLAN_Iu7 /30 E
19 18 20 19 20 19
A/L
LASER
A/L A/L
Iub6 1
LASER
CLASS 1
A/L
CLASS 1
A/L A/L
CLASS 1 LASER
22 21 22 21
RN30035EN40GLA0
24 23 24 23
P VLAN_Iub7 /30
26 25 26 25
28 27 28 27
F
30 29 30 29
S
IPU4
32 31 32 31
Iu8 -
34 33 34 33
36 35 36 35
38 37 38 37
6 VLAN_Iu8 /30 3
Cisco 7603-S
40 39 40 39
Iub8 1
SYSTEM GROUND
REMOVE LABEL FOR
VLAN_Iub8 /30
mcRNC BCN #2
©2014 Nokia Solutions and Networks. All rights reserved.

mcRNC OSPF Site Solution
BCN-B
• NSN preferred option
• EIPUs of one BCN are connected to one site
router; site routers are interconnected
• mcRNC is set up with dedicated EIPU
• two EIPUs in different BCNs form a pair
• VRFs are applied for separating the routing
processes
• L3 type of site solution with dynamic routing
• OSPF with BFD (Single Hop) or OSPF Fast Hello
applied for fast reaction to link failures
• Supports 1GE and 10GE interfaces

Iu/Iur user plane and Iub control and user plane
• OSPF dynamic routing is applied for

• Iu/Iur user plane
• Iub control/user plane
• The application IP addresses for the service termination

• Configured to the loopback interface
• Recovery Group (RG) as the owner of the address
• IP address is located at EIPU node where the active Recovery Unit of the Recovery Group
(QNUP/QNIUB) is located

• The interface or link failure is detected with the Link State Detector functionality (10GE)
• Link State Detector is configured with 10GE and LAG interface since one EIPU is connected to
one site switch
• Link State Detector is bound to RG and configured to monitor network interface(s) and OSPF
neighbour state. In case of link or interface failure the RG switchover will be triggered.
• Recovery Group (QNUP, QNIUB) protection switchover may be triggered due to the following
events:
• SW failure (mcRNC redundancy mechanisms)
• HW failure (EIPU, BCN)
• Link/Interface failure or Next hop failure monitored via BFD Single-Hop (Link State Detector)
(OSPF SiSo, 10GE)

Iu/Iur user plane and Iub control and user plane (1GE + 10GE, Dedicated EIPU)
OSPF areas: 10.0.1.0 (Iu/Iur UP)
mcRNC BCN #1 10.0.3.0 (Iub)
VRFs
EIPU-0 VLAN_Iu1
loopback VRF VLAN_Iu1
SFP+11
10GE 0/0/2
10.0.1.17/28 VRF • O&M (default)
10.0.1.18/28 Base
addresses Stations
0/0/11 VLAN_Iu
• Iu/Iur control plane
10.0.3.17/28
VLAN_Iub1
UP
UP
G
A 10.0.1.1/30 EX4500 #1
UP 0/0/12 L
0/0/13
1
VLAN_Iub
10.0.3.1/30
• Iu-PS user plane
4x1GE 0/0/14
EIPU-2
• Iu-CS user plane
loopback VRF G SFP13 0/0/0 0/0/1
10.0.3.18/28
VLAN_Iub1
addresses
A
L
SFP14 • Iub
UP 1
UP
UP
SFP15
Backhaul Network
SFP16 redundant
10GE
(LAG)
0/0/0 0/0/1 DCN

mcRNC BCN #2
EIPU-1 VLAN_Iu2 VLAN_Iu
SFP+11
0/0/2
10.0.1.33/28 VRF 10.0.1.2/30
addresses 10.0.1.34/28
0/0/11
10.0.3.33/28
VLAN_Iub2
UP G VLAN_Iub EX4500 #2
UP
UP 0/0/12
A
L 10.0.3.2/30 NetAct
1
0/0/13
0/0/14
4x1GE
EIPU-3 G SFP13
10.0.3.34/28
VLAN_Iub2
loopback VRF A
L
SFP14
addresses
1 SFP15
UP
UP
UP SFP16

Iu/Iur user plane and Iub control and user plane (10GE, Shared EIPU)
OSPF areas: 10.0.1.0 (Iu/Iur UP)
mcRNC BCN #1 10.0.3.0 (Iub)
EIPU-0
loopback VRF VLAN_Iu1 VRF
10.0.1.17/28
10.0.3.17/28
VLAN_Iub1
VLAN_Iu1
10.0.1.18/28 Base
addresses Stations
VLAN_Iu
0/0/2
UP
UP VLAN_Iub1 10GE 10.0.1.1/30 EX4500 #1
UP
10.0.3.18/28
SFP+11
VLAN_Iub
10.0.3.1/30
EIPU-2 loopback VRF VLAN_Iu1 0/0/0 0/0/1
UP
UP VLAN_Iub1
UP Backhaul Network
10.0.3.19/28 redundant
10GE
(LAG)
0/0/0 0/0/1 DCN

mcRNC BCN #2
EIPU-1 VLAN_Iu
VRF 10.0.1.2/30
10.0.1.33/28
10.0.3.33/28
VLAN_Iub2
VLAN_Iu2
VLAN_Iub
0/0/2
UP
UP VLAN_Iub2 10GE EX4500 #2
UP 10.0.3.34/28
10.0.3.2/30 NetAct
SFP+11
EIPU-3
VLAN_Iu2
loopback VRF 10.0.1.35/28
addresses
UP VLAN_Iub2
UP
UP 10.0.3.35/28

• Related features
• RAN2256 Ethernet Link Aggregation for mcRNC
• Requires RAN2256 license
• RAN2550 OSPF Enhancements in mcRNC (OSPF + BFD)
• Requires “RAN1510 OSPF for Redundancy” license
• RAN2257 Support of Virtual Routing and Forwarding in mcRNC
• RAN2696 mcRNC 10GE based network connectivity
• BCN-B / Octeon II HW
• Required for 10GE network interfaces
• RAN2240 mcRNC HW release2 support
• Required Site router functions

• OSPF with BFD Single-Hop
• 1GE and 10GE interfaces

mcRNC VRRP/HSRP Site Solution
BCN-B
• EIPUs of one BCN are connected to one site
router; site routers are interconnected
• mcRNC is set up with dedicated EIPU
• two EIPUs in different BCNs form a pair
• VRFs are applied for separating the routing
processes
• Site solution based on Ethernet switchport
configuration in the site routers
• Site router redundancy is managed with VRRP or
HSRP protocols
• One VLAN spans over the EIPUs and site
routers/switches (not further to network)
• Provides planning principles compatibility with the
current IPA-RNC VRRP/HSRP site solution

• Static routing and HSRP/VRRP is applied for

• Iu/Iur user plane
• Iub control/user plane
• The application IP addresses for the service termination

• Configured to the network interface (VLAN)
• Recovery Group (RG) as the owner of the address
• IP address is located at EIPU node where the active Recovery Unit of the Recovery Group
(QNUP/QNIUB) is located

• The interface or link failure is detected with the Link State Detector functionality (10GE)
• Link State Detector is configured with 10GE and LAG interface since one EIPU is connected to
one site switch
• Link State Detector is bound to RG and configured to monitor network interface state. In case of
link or interface failure the RG switchover will be triggered.
• Carrier state detection is fastest with the optical interfaces  optical recommended
• Failure detection time with optical interface is around 50ms and with electrical interface around
950ms
• Recovery Group (QNUP, QNIUB) protection switchover may be triggered due to the following
events:
• SW failure (mcRNC redundancy mechanisms)
• HW failure (EIPU, BCN)
• Link/Interface failure

Iu/Iur user plane (1GE + 10GE, Dedicated EIPU)
VRFs
• O&M (default)
• Iu/Iur control plane
• 2*Iu-PS user plane
• 2*Iu-CS user plane
• 2*Iur user plane
• 2*Iub

Iu/Iur user plane (10GE, Shared EIPU)
VLAN_Iu1
10.0.1.2/27
mcRNC BCN #1 VLAN_Iu2
EIPU-0 10.0.1.34/27
QNUP-0 VLAN_Iu1
10.0.1.4 role iuiurup 10.0.1.4/27 (*)
MSC
10GE VLAN_Iu1 Server /
VLAN_Iu2
VLAN_Iu1
VLAN_Iu2
0/0/2
MGW /
QNUP-1 standby
EX4500 #1 SGSN /
SFP+11
GGSN
VLAN_Iu2
EIPU-2 QNUP-2 VLAN_Iu1

10.0.1.5 role iuiurup 10.0.1.5/27 (*)
VRRP Iu1 0/0/0 0/0/1
VLAN_Iu2 10.0.1.1 (*)
QNUP-3 standby
Backbone Network
redundant
10GE
(LAG)
mcRNC BCN #2 VRRP Iu2
10.0.1.33 (*) 0/0/0 0/0/1
EIPU-1
QNUP-0 standby DCN
VLAN_Iu1
VLAN_Iu1
VLAN_Iu2
QNUP-1 VLAN_Iu2 VLAN_Iu1
0/0/2
10.0.1.36 role iuiurup 10.0.1.36/27 (*)
EX4500 #2
SFP+11
VLAN_Iu2 NetAct
EIPU-3 10GE
QNUP-2 standby VLAN_Iu1
VLAN_Iu1
QNUP-3 VLAN_Iu2 10.0.1.3/27
10.0.1.37 role iuiurup 10.0.1.37/27 (*)
VLAN_Iu2
10.0.1.35/27
Iub user and control plane (1GE + 10GE, Dedicated EIPU)

Iub user and control plane (10GE, Shared EIPU)
mcRNC BCN #1 VLAN_Iub1
10.0.3.2/27
EIPU-0 QNUP-0 VLAN_Iub1
-> 10.0.3.4 10.0.3.4/27 (*) VLAN_Iub2
10GE
QNUP-1 standby 10.0.3.16/27 (*) 10.0.3.34/27
QNIUB-0 VLAN_Iub2
-> 10.0.3.16
SFP+11
VLAN_Iub1
VLAN_Iub1
VLAN_Iub2
0/0/2
QNIUB-1 standby
EX4500 #1
EIPU-2 QNUP-2 VLAN_Iub2
VLAN_Iub1
-> 10.0.3.5 10.0.3.5/27 (*)
QNUP-3 standby 10.0.3.17/27 (*)
QNIUB-2 VLAN_Iub2 VRRP Iub1 Base
-> 10.0.3.17 10.0.3.1 (*) 0/0/0 0/0/1 Stations
QNIUB-3 standby Backbone Network
redundant
10GE
mcRNC BCN #2 (LAG)
EIPU-1 QNUP-0 standby VLAN_Iub1 VRRP Iub2 DCN

0/0/0 0/0/1
QNUP-1 VLAN_Iub2 10.0.3.33 (*)
10GE
-> 10.0.3.36 10.0.3.36/27 (*)
QNIUB-0 standby 10.0.3.48/27 (*)
VLAN_Iub1
VLAN_Iub2
SFP+11
QNIUB-1 VLAN_Iub1 NetAct
0/0/2
-> 10.0.3.48
EX4500 #2
VLAN_Iub2
EIPU-3 QNUP-2 standby VLAN_Iub1
QNUP-3 VLAN_Iub2
-> 10.0.3.37 10.0.3.37/27 (*)
10.0.3.49/27 (*) VLAN_Iub1
QNIUB-2 standby
10.0.3.3/28
QNIUB-3
VLAN_Iub2
-> 10.0.3.49
10.0.3.35/27
mcRNC Iu/Iur control plane
OSPF SiSo, VRRP/HSRP SiSo
• Static route configuration is applied for Iu / Iur control plane traffic

• Control plane resilience for Iu and Iur interfaces is provided by two different layers
• M3UA layer enables use of multiple SCTP associations for the same signalling connection
• SCTP layer provides multi-homing support for increased end-to-end redundancy
• The IP addresses of the multi-homed SCTP association are configured mcRNC backplane and
network interface interfaces reserved for the SCTP/SIGTRAN configuration (sctp interfaces).
• IP address of the SCTP link is configured into the same interface from where the related traffic is
sent out from the node

• SCTP associations configuration

• Signalling connections towards the core network elements (that is MSS and SGSN) should be
using at least four EIPU nodes for the M3UA layer resilience and EIPU load balancing
• Neighbour RNCs should be configured to at least to one or two EIPUs each, using different EIPUs
per neighbouring RNC
• The SCTP associations towards all CN elements and neighbor RNCs should be evenly distributed
over the EIPU nodes of the mcRNC
• Iu/Iur control plane is located to VRFs 1 – 4

• VRFs1-4 contain the backplane sctp interfaces pre-configured by the system


• Related features
• RAN2256 Ethernet Link Aggregation for mcRNC
• Requires RAN2256 license
• RAN2257 Support of Virtual Routing and Forwarding in mcRNC
• RAN2696 mcRNC 10GE based network connectivity
• BCN-B / Octeon II HW
• Required for 10GE network interfaces
• RAN2240 mcRNC HW release2 support
• Required Site router functions

• VRRP / HSRP
• Ethernet switching (VLAN) and L3 routing
• 1GE and 10GE interfaces

Outline
• Scheduling
• Routing

General mcRNC QoS Architecture
IP Based Route #n
IP Based Route
IP Based #3
IP Based RouteRoute
#1 #2 Traffic
Traffic
Traffic Marking
Traffic
Marking
Marking Classification
Marking
Classification
Classification
Queue 6 (WFQ)
Queue 5 (WFQ)
Queue 4 (WFQ)
Queue 3 (WFQ)
Queue 2 (WFQ)
Classification
Queue 1 (SP)
Queue
Queue 5 (WFQ)
Queue 4 (WFQ)
Queue 3 (WFQ)
Queue 2 (WFQ)
Queue 1 (SP)
Queue 6 (WFQ)
Queue 5 (WFQ)
Queue64(WFQ)
Queue
Queue
Queue
Queue 6 (WFQ)
Queue 5 (WFQ)
Queue 4 (WFQ)
Queue 3 (WFQ)
Queue 2 (WFQ)
Queue 1 (SP)
3
2
1
(WFQ)
(WFQ)
(WFQ)
(SP)
IP Based
IP Based Route
IP Based
IP Based Route Scheduler
Route Route
Scheduler
Scheduler
Scheduler
Network I/f
Scheduler
Queue 1 (SP)
Queue 2 (WRR)
Network I/f Internal Egress Queue 3 (WRR)
Ingress Classification Queue 4 (WRR)
Classification Processing Queue 5 (WRR)
Queue 6 (WRR)

mcRNC IP Based Route Scheduling
mcRNC IP Based Route Scheduling
• Per neighbour element user plane traffic scheduling (e.g. traffic to
BTS)
• Based on the Strict priority and 5*WFQ queues
• Queue allocation is based on the DSCP values IP Based Route scheduler
• Scheduling options:
• Virtual Queue EF Queue Strict Priority
• Internal Flow Control
AF4 Queue
• IFC is supported similarly as with the IPA-RNC
AF3 Queue WFQ
• Control messages from scheduling to User Plane
AF2 Queue
• Minimizes the RNC internal delays at transport queues
AF1 Queue
• Works for Iub only
• E-RED Default mapping (IDSP) BE Queue
- Configurable
• Packet drop events DSCP Egress queue
• Real Queue / PHB IPBR
• Real queues applied 48, 46 EF
• E-RED 34, 36, 38 AF4 IPBR
26, 28, 30 AF3
• Packet drop events 18, 20, 22 AF2 … Interface
10, 12, 14 AF1
0, other BE IPBR

mcRNC Physical Interface egress scheduling
mcRNC Physical Interface Scheduling
• Physical interface scheduling for all outgoing packets via the given interface (1GE, LAG, 10GE)
• Based on the Strict priority and 5*WRR queues
• Queue allocation is based on the DSCP values
System Default mapping Physical Network Interface Scheduler

- Modification not recommended (DSCP to PIP ACL rules)
DSCP Egress queue
EF Queue Strict Priority
/ PHB
48, 46 EF AF4 Queue
AF3 Queue
34, 36, 38 AF4 WRR
AF2 Queue
26, 28, 30 AF3
AF1 Queue
18, 20, 22 AF2
BE Queue
10, 12, 14 AF1
0, other BE

Virtual Queueing – based on E-RED
IP based route using E-RED Physical Network Interface Scheduler
Packet Packet
Packet User Plane
Counters EF Queue Strict Priority

Strict Priority
EF
Decrease
AF4
AF4 Queue
counters at Packet
97% route AF3 Packet
AF3 Queue
bitrate
WFQ AF2 WRR
AF1
BE
AF2 Queue
AF1 Queue
E-RED
Algorithm BE Queue
• Virtual Queueing counts bytes in virtual queues per IP based route

• No dedicated (physical) scheduling per IP based route
• Counters are decreased according to 1SP + 5WFQ scheme,
but only according to 97% of the configured route bandwidth
– Leading to low queueing delay at the bottleneck (assuming a static bandwidth limit)
• E-RED packet dropping mode
• When counter indicates (virtual) queue low threshold is exceeded, packets are dropped according to
E-RED algorithm per IP based route
• WFQ weights and E-RED parameters can be configured via PHB profile (IPHB)
• Supported for all logical interfaces (user plane)
Virtual Queueing – based on IFC
IP based route using IFC Physical Network Interface Scheduler
Packet Packet
Packet RLC/MAC
Packet
EF Queue
Counters Strict Priority
Strict Priority
EF
Decrease
AF4
AF4 Queue
counters at Packet
97% route AF3 Packet
AF3 Queue
bitrate
WFQ AF2 WRR
AF1
BE
AF2 Queue
AF1 Queue
E-RED
Algorithm BE Queue
• Internal Flow Control (IFC) mode

• IFC mode supported for IP based routes on Iub interface only (due to relation to RLC/MAC)
• When counter indicates (virtual) queue low threshold is exceeded, IFC message is sent based on an
E-RED algorithm to RLC/MAC scheduler
• Instead of dropping packets, RLC/MAC scheduler reduces transmission rate
• Reduces Iub packet delay, as packet drop (and thus retransmissions of end user packets) is avoided
• E-RED algorithm
• WFQ weights and E-RED parameters can be configured via PHB profile (IPHB)
• Although no real discard is performed, E-RED alike algorithm is used to determine the level of user
plane transmission rate reduction needed

Real Queueing
Physical Network Interface Scheduler
IP based route
EF Queue Strict Priority EF Queue Strict Priority

Packet AF4 Queue
AF3 Queue AF4 Queue
Packet AF2 Queue WFQ Packet
AF1 Queue AF3 Queue
BE Queue WRR
AF2 Queue
E-RED
Dropper Packet AF1 Queue
BE Queue
2nd Level 1st Level

Queues Queues
• Real Queueing provides dedicated physical queues (buffers) per IP based route
• Adds second level of scheduling
• Scheduler type: 1SP + 5WFQ
• Supported for all logical interfaces (user plane)
• No significant performance penalty compared to Virtual Queueing, yet higher precision achieved
• Queue management
• Excess packets are discarded by E-RED algorithm
• Queues can be configured via PHB profile (IPHB), e.g. queue length, weight, and thresholds

Outline
• Scheduling
• Routing

Protection Mechanisms
• Depending on the Functional Unit (FU) type, specific protection schemes are supported:
• FUs in CFPU: 2N protection mechanism in cold-stanby mode for OMU and CFCP.
• FUs in CSPU: N+M protection mechanism, then M protecting FUs for N working FUs with
M>=1. This is applied to CSCP.
• FUs in USPU: SN+ protection mechanism, then load sharing between USUP units.
• FUs in EIPU: 2N protection mechanism, then if an EIPU fails it is protected by another working
one.

User Plane Recovery Group
• The QNUP Recovery Group, User Plane

• Recovery Group is located to EIPU nodes
• Holds the IP addresses terminating the User Plane at IP layer
• Terminates the User Plane transport connections from any logical interface from several neighbor
nodes
• Hot active/standby redundancy scheme for end user connection resilience
• QNUP RGs are allocated with the following scheme in order to provide a good basic load distribution (2
QNUP instances per EIPU pair)
BCN-1 BCN-2
EIPU-0 EIPU-2 EIPU-1 EIPU-3
Active Standby QNUP-0
Standby Active QNUP-1
Active Standby QNUP-2
Standby Active QNUP-3

IuB Control Plane Recovery Group
• QNIUB Recovery Group, Iub control plane

• Recovery Group is located to EIPU nodes
• Terminates the Iub control plane at IP/SCTP layer
• Holds the IP addresses terminating the Iub Control Plane at IP layer
• Cold active/standby redundancy scheme for end user connection resilience
• Terminates connections from several BTSs
• QNIUB RGs are allocated with the following scheme in order to provide a good basic load distribution (2
QNIUB instances per EIPU pair)
BCN-1 BCN-2
Active Standby QNIUB-0
Standby Active QNIUB-1
Active Standby QNIUB-2
Standby Active QNIUB-3

Sigtran Recovery Group
• The Iu/Iur control plane traffic SIGTRAN stack processing is located to EIPU nodes
• The transport network redundancy is handled with the SCTP multihoming configuration. The
service level redundancy and load sharing is handled at M3UA / SCCP layer.
• The SCCP layer contains the Hot active/standby redundancy scheme in order to provide full
RANAP/RNSAP resilience (QNIU Recovery Group)
BCN-1 BCN-2
SCCP SCCP
SCCP SCCP
SCCP SCCP
SCCP SCCP
M3UA M3UA M3UA M3UA
SCTP SCTP SCTP SCTP
IP A1 IP A2 IP B1 IP B2 IP C1 IP C2 IP D1 IP D2
Multi-homed Multi-homed Multi-homed Multi-homed

SCTP SCTP SCTP SCTP
40 Association RN30035EN40GLA0
Association ©2014 Nokia
Association Solutions and Networks. All rights reserved.
Association
#1 #2 #3 #4
Other Recovery Groups
• QNOMU Recovery Group, O&M functions

• Located to CFPU nodes
• Recovery Group is bound to CFPU units
• Holds the IP address(es) for the O&M connections to BTS and OMS
• Hot active/standby scheme for resilient management
• SSH Recovery Group, Secure Shell
• Secure Linux shell account access, SCLI access
• QNCFCP Recovery Group, Service Area Broadcast, Centralized functions
• Located to CFPU nodes
• Holds the IP address(es) for the SAB traffic in between the mcRNC and Cell Broadcast Center (Iu-
BC)
• Hot active/standby scheme for resilient management
BCN-1 BCN-2
CFPU-0 CFPU-1
Active Standby QNOMU
Active Standby SSH
Active Standby QNCFCP

Outline
• Scheduling
• Routing

SiSo Network Reference
 Reference: WCDMA RAN, Rel. RU40, Operating Documentation, Issue 03:
Configuring IP Connection for Multicontroller RNC
Network reference topology:

 OSPF Site Solution:
1. mcRNC OSPF SiSo, VRF, 10GE and shared EIPU
2. mcRNC OSPF SiSo, VRF, 1GE with LAG and shared EIPU
3. mcRNC OSPF SiSo, VRF, 10GE, 1GE with LAG and dedicated EIPU
 VRRP/HSRP Site Solution:
1. mcRNC VRRP/HSRP SiSo, VRF, 10GE and shared EIPU
2. mcRNC VRRP/HSRP SiSo, VRF, 1GE with LAG and shared EIPU
3. mcRNC VRRP/HSRP SiSo, VRF, 10GE, 1GE with LAG and dedicated EIPU
 Evolved Site Solution:
1. Iu, Iur, and Iub interfaces with mcRNC Evolved Site Solution

mcRNC OSPF SiSo, VRF, 10GE and shared EIPU
Network Configuration
The main building blocks for the VRF are the following:
• VRFs are configured in EIPU nodes to logically separate the routing functions
and
IP addressing.
• Simplified static route configuration can be applied for the user plane
connections.
• One VLAN interface can belong to only one VRF.
The main building blocks for the OSPF site solution in general are the following:
• OSPF manages the user plane routing
• Iu/Iur control plane with SCTP Multi-Homing is managed with static routes
Restrictions
• O&M-related functions in the CFPU unit belong to the default VRF only. Iu/Iur
control plane IP addresses of a single SCTP multi-homed association can only
belong to one VRF. Incoming traffic towards the IP address within the VRF has to
come in via the VLAN interface tied to the same VRF.

IuB Configuration

Iu/Iur User Plane Configuration

Iu/Iur Control Plane Configuration
• Iu-PS control plane, SCTP associations
– SCTP association-1, 10.1.8.2/28, 10.1.8.145/28
• Iu-CS control plane, SCTP associations

• Iur control plane, SCTP associations


mcRNC OSPF SiSo, VRF, 1GE with LAG and shared EIPU
• VRFs are configured in EIPU nodes to logically separate the routing functions and
IP addressing
• Simplified static route configuration can be applied for the user-plane connections
• One VLAN interface can belong to only one VRF
Restrictions:
O&M-related functions in the CFPU unit belong to default VRF only. Iu/Iur control
plane IP addresses of a single SCTP multi-homed association can only belong to one
VRF. Incoming traffic towards the IP address within the VRF has to come in via the
VLAN interface tied to the same VRF.

IuB Configuration


• Iu-CS control plane, SCTP associations



mcRNC OSPF SiSo, VRF, 10GE, 1GE with LAG and dedicated EIPU
• VRFs are configured in EIPU nodes to logically separate the routing functions
and IP addressing
• Simplified static route configuration can be applied for the user-plane
connections
• One VLAN interface can belong to only one VRF
Restrictions:
O&M-related functions in the CFPU unit belong to default VRF only. Iu/Iur
control plane IP addresses of a single SCTP multi-homed association can only
belong to one VRF.
Incoming traffic towards the IP address within the VRF has to come in via the
VLAN interface tied to the same VRF.

IuB Configuration


• Iu-CS control plane, two SCTP associations



Thank you
RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

05 RN30035EN40GLA0 MCRNC Iu IuB Planning PDF

Uploaded by

Document Information

Original Title

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

05 RN30035EN40GLA0 MCRNC Iu IuB Planning PDF

Uploaded by

Copyright:

Available Formats

Module 5 – mcRNC Iu/IuB Planning

RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

2 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

4 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

RNC2600 Site Solutions mcRNC Site Solutions

6 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

7 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

8 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

9 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

REMOVE LABEL FOR REMOVE LABEL FOR

10 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

ETHERNET SERVICES MODULE

ETHERNET SERVICES MODULE

©2014 Nokia Solutions and Networks. All rights reserved.

12 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

• OSPF dynamic routing is applied for

• The application IP addresses for the service termination

13 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

14 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

0/0/0 0/0/1 DCN

15 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

EIPU-2 loopback VRF VLAN_Iu1 0/0/0 0/0/1

0/0/0 0/0/1 DCN

16 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

• Required Site router functions

17 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

18 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

• Static routing and HSRP/VRRP is applied for

• The application IP addresses for the service termination

19 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

20 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

21 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

EIPU-2 QNUP-2 VLAN_Iu1

23 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

EIPU-1 QNUP-0 standby VLAN_Iub1 VRRP Iub2 DCN

• Static route configuration is applied for Iu / Iur control plane traffic

25 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

• SCTP associations configuration

• Iu/Iur control plane is located to VRFs 1 – 4

26 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

27 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

• Required Site router functions

28 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

29 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

30 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

31 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

System Default mapping Physical Network Interface Scheduler

32 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

Counters EF Queue Strict Priority

• Virtual Queueing counts bytes in virtual queues per IP based route

• Internal Flow Control (IFC) mode

34 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

EF Queue Strict Priority EF Queue Strict Priority

2nd Level 1st Level

35 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

36 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

37 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

• The QNUP Recovery Group, User Plane

Standby Active QNUP-1

Active Standby QNUP-2

Standby Active QNUP-3

38 RN30035EN40GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.

• QNIUB Recovery Group, Iub control plane