McRNC

Product Introduction

mcRNC Transport Introduction

BCN-B HW (RU40 / mcRNC3.0)

2x USB
1x RJ-45

Software download
(BCN eSW, NSN personnel)

Hardware maintenance
Debugging
interfaces

1x SFP
- Trace port
(External port mirroring)
- SFP22
(Megamon/monitoring)

10x SFP

7x SFP+
Backplane

1GE external ports

SFP13 SFP22

4x RJ-45

SFP
LAN1
O&M

2x SFP+
10GE external ports
SFP+ 11, SFP+ 12

Alarm and sync interfaces,

not used by mcRNC

mcRNC Transport Introduction

BCN-B HW (RU40 / mcRNC3.0)

Interface type

Number
of interfaces

Printed
label

Backplane ports
(Internal 10GE)

SFP0 SFP6

External 1GE network connectivity:

External 1GE

10

SFP13
SFP22

1000Base-TX, electrical transmission via SFP with RJ-45 connector

1000Base-SX/LX, optical transmission via SFP with LC-type connector

O&M connectivity (two first BCN modules):

External 10GE

Trace port /
MegaMon

SFP+ 11
SFP+ 12

Trace /
SFP21 or
SFP22

on the following standards:

LAN1 (eth0)

External 10GE network connectivity is implemented based

10GBASE-SR acc. IEEE 802.3-2008 Clause 49 and 52.5

10GBASE-LR acc. IEEE 802.3-2008 Clause 49 and 52.6

Note: Either 1*10GE + 10*1GE or 2*10GE are supported simultaneously per BCN-B for external connectivity

The mcRNC high level functions

The mcRNC architecture consists of the following high level functions:

network interface functions
switching functions
control plane processing
user plane processing
carrier connectivity functions
O&M functions
The functions are distributed in entities of hardware and software. The main functional units of the RNC are
listed below.

Centralized Functions Processing Unit (CFPU)

Cell-Specific Processing Unit (CSPU)
UE-Specific Processing Unit (USPU)
External Interface Processing Unit / Network Processing unit (EIPU)
Data Base (DB)

mcRNC Transport Introduction

mcRNC Transport Solution

mcRNC supports IP transport option
Network connectivity and transport layer processing capacity is
aligned with the control plane and user plane processing capacity
mcRNC3.0 and BCN-B Octeon II HW: Both 1GE and 10GE
Ethernet connectivity supported
All network processing units (EIPU) process traffic at normal
conditions
Full transport redundancy is provided for the failure cases
Connectivity to separate physical router pairs is supported

Capacity step: S7

mcRNC Transport Introduction

8 * BCN available in

Capacity steps (mcRNC3.0 / BCN-B)

mcRNC3.0

Capacity step: S3

BCN-B / Octeon II

#BCN = 4
#EIPU = 8

RU50 EP1

Number
of EIPUs
BCN4: 2

Capacity step: S1

#BCN = 2

BCN3: 2

#EIPU = 4

BCN2: 2
BCN1: 2
BCN = Box Controller Node
EIPU = Network Processing Unit

mcRNC capacity limitations

Supported configurations Octeon II HW
mcRNC capacity step

S1-B2

S3-B2

S7-B2

CS BHCA

760 000

2 140 000

4 520 000

PS BHCA

1 400 000

3 500 000

7 920 000

PS Session BHCA

2 800 000

7 000 000

15 840 000

Smartphone BHCA

1 170 000

2 940 000

6 660 000

1850 / 790

5260/2260

14000/6000

19000

53500

113 000

520

1320

2 000

Carrier connectivity

2600

6600

10 000

RRC connected state UEs

352 000

1 000 000

1 000 000

30 000

75 000

170 000

1665

4734

12600

500

1420

5400

max Iub DL/UL throughput

[Mbps]
AMR/CS voice over HSPA
capacity [Erlangs]
BTS connectivity

Laptop HSPA active users per

RNC
IuPS HSDPA net bit rate [Mbit/s]
IuPS HSUPA net bit rate [Mbit/s]

S1-B2

S3-B2

S7-B2

2 BCN-B
modules,
OcteonII
processors

4 BCN-B
modules,
OcteonII
processors

8 BCN-B
modules,
OcteonII
processors

Always check the capacity figures with the latest mcRNC Product Description

mcRNC Transport Introduction

BCN-B

mcRNC BCN #2

EIPU-3
CSPU
CSPU

SFP+11

10GE

EIPU-1

USPU
USPU
USPU

MX240-1

CFPU-1

GE
GE
OMS

ToP
GE

GE
EIPU-2
CSPU
CSPU

MX240-2

SFP+11

10GE

EIPU-0
1GE
USPU
USPU
USPU

CFPU-0

mcRNC BCN #1

LAN1
(eth0)

Hosts O&M and centralized processing functions

Owns management Ethernet ports (LAN1)
Services with 2N redundancy
Contains IP networking and routing functions

Network Processing Unit (EIPU)

1GE
LAN1
(eth0)

Centralized Functions Processing Unit (CFPU)

Transport layer traffic termination for control plane and user plane
Owns external interfaces (SFP / SFP+)
All nodes process traffic in normal conditions
Services with 2N redundancy
Contains IP networking and routing functions

UE-Specific Processing Unit (USPU)

UE-specific control and user plane processing
Control/user plane resources of one UE are located to one USPU
No external transport termination

Cell-Specific Processing Unit (CSPU)

Cell-specific control and user plane processing
BTS/Cell resources are located to one CSPU
No external transport termination

mcRNC OSPF Site Solution

mcRNC OSPF Site Solution

- Iu User plane
- Iub user and control plane
- mcRNC Management Plane (Independent from the EIPU connectivity)

mcRNC OSPF Site Solution

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 OSPF Site Solution

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

mcRNC OSPF Site Solution

Iu/Iur user plane and Iub control and user plane
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)

mcRNC Iu/Iub User plane

mcRNC OSPF Site Solution

OSPF SiSo

EIPUs of one BCN are connected

to one site router; site routers are
interconnected

0 /0/ 2

DCN

VRF

IUPS3VL9 10.0.9.3/28
IUCS3VL10 10.0.10.3/28
IUR3 VL11 10.0.11.3/28
IUB3 VL12 10.0.12.3/28

10GE

VRF

R2

-O&M (default)
NetAct

- Iu/Iur control plane

- Iu-PS user plane
- Iu-CS/Iur user plane
-Iub

et h_r2

IUPS4VL13 10.0.13.3/28
IUCS4VL14 10.0.14.3/28
IUR4 VL15 10.0.15.3/28
IUB4
. VL16 10.0.16.3/28

e th _r1

EIPU -3
QNUP-2&QNIUB-2STANDBY)

VRFs are applied for separating the

routing processes
VRFs

S F P +11
e th _ b

IUR4 VL15 10.0.15.2/28

IUB4 VL16 10.0.16.2/28

et h_r2

IUPS4VL13 10.0.13.2/28
IUCS4VL14 10.0.14.2/28

L3 type of site solution with

dynamic routing

Supports 1GE and 10GE

interfaces

Backhaul Network

redundant
10GE

0 /0 /2

VRF

IUPS3VL9 10.0.9.2/28
IUCS3VL10 10.0.10.2/28
IUR3 VL11 10.0.11.2/28
IUB3 VL12 10.0.12.2/28

e th _r1

QNUP-0&QNIUB-0STANDBY)

QNUP-3(Act)
10.1.1.4 upsup
10.1.1.20iucsup
10.1.1.36iurup
10.1.0.4ubup
10.1.0.68iubcp(QNIUB3)

Base
Stations

R1

mcRNC BCN#2

EIPU-1
QNUP-1(Act)
10.1.1.2 upsup
10.1.1.18iucsup
10.1.1.34iurup
10.1.0.2ubup
10.1.0.66iubcp(QNIUB1)

two EIPUs in different BCNs form a

pair

VRF

OSPF with BFD (Single Hop) or

OSPF Fast Hello applied for fast
reaction to link failures

e t h_r2

IUPS2VL5_10.0.5.3/28
IUCS2VL6_10.0.6.3/28
IUR2 VL7 10.0.7.3/28
IUB2. VL8 10.0.8.3/28

et h_r1

VRF

QNUP-2(Act)
10.1.1.3 upsup
10.1.1.19iucsup
10.1.1.35iurup
10.1.0.3iubup
10.1.0.67iubcp(QNIUB2)

IUPS1VL1_10.0.1.3/28
IUCS1VL2_10.0.2.3/28
IUR1 VL3 10.0.3.3/28
IUB1 VL4 10.0.4.3/28

10GE

SF P +11
e th _ a

IUPS2VL5_10.0.5.2/28
IUCS2VL6_10.0.6.2/28
IUR2 VL7 10.0.7.2/28
IUB2 VL8 10.0.8.2/28

EIPU -2

QNUP-3&QNIUB-3(STANDBY)

IUPS1VL1_10.0.1.2/28
IUCS1VL2_10.0.2.2/28
IUR1 VL3 10.0.3.2/28
IUB1 VL4 10.0.4.2/28

e th _r2

QNUP-0(Act)
10.1.1.1upsup
10.1.1.17iucsup
10.1.1.33iurup
10.1.0.1iubup
10.1.0.65iubcp(QNIUB0)

VRF
VRF

Vl5V10.0.5.1
LAN_Iu2
Vl6
1010.0.6.1
.0. .33/28
Vl7V10.0.7.1
L
u
Vl8
1010.0.8.1
.0.1 5 8
Vl13
2
V 10.0.13.1
Vl14
1 .010.0.14.1
.33/2
Vl15 10.0.15.1
VLA Iub2
Vl16
10.0.16.1
10.0
. .65/ 8

QNUP-1&QNIUB-1(STANDBY)

e th _r1

EIPU -0
EIPU-0

_
Vl1 10.0.1.1
Vl2 10.0.2.1
. .
Vl3 10.0.3.1
Vl4
1 10.0.4.1
Vl9 10.0.9.1
I
Vl1010.0.10.1
Vl1110.0.11.1
Vl1210.0.12.1

OSPF areas:
mcRNC BCN#1

mcRNC Management Plane / O&M connectivity

Management plane is terminated in mcRNC CFPU node and it is protected by

Recovery Group based redundancy scheme
Routing
OSPF + BFD Single-Hop
Static routes + BFD Single-Hop
Routing instances (VRF / Virtual Routing and Forwarding)
O&M services are located to default VRF instance
Exception: The source IP address for BTS O&M messaging towards the BTS
can be located to other than default VRF

mcRNC Management Plane / O&M connectivity

WBTS and OMS O&M communication (BTS O&M messaging) can have either one
common or separated source IP addresses:
One source IP address, QNOMU
One IP address contains two role attributes
IP address with role btsom & role oms
Two source IP address, QNOMU
WBTS communication with IP address having role btsom
OMS communication with IP address having role oms
IP address for WBTS communication can be located to other than default VRF

mcRNC Management plane / OSPF

mcRNC BCN #1

OSPF area 10.10.0.0

VLAN_MP1
10.0.0.6/30

GE

VLAN_MP1
10.0.0.5/30

VLAN_MP
10.0.0.1/30

QNOMU
10.0.10.1/32 role bts
10.10.0.2/32 role oms

LAN1

oam_int, 10.0.10.4/30

0/0/10

CFPU-0
MX240 #1
Base
Stations

SSH
10.10.0.1/32 role ssh
Backhaul Network

mcRNC BCN #2
CFPU-1

VLAN_MP2
10.0.0.10/30

GE

VLAN_MP2
10.0.0.9/30

VLAN_MP
10.0.0.2/30

SSH standby

LAN1

QNOMU standby

0/0/10

oam_int, 10.0.10.5/30

NetAct

MX240 #2

mcRNC Management Plane / Static route

mcRNC BCN #1
VLAN_MP1
10.0.0.6/30

GE

VLAN_MP1
10.0.0.5/30

VLAN_MP
10.0.0.1/30

QNOMU
10.0.10.1/32 role bts
10.10.0.2/32 role oms

LAN1

cfeigw, 169.254.0.4

0/0/10

CFPU-0
MX240 #1
Base
Stations

SSH
10.10.0.1/32 role ssh
Backhaul Network

mcRNC BCN #2
CFPU-1

VLAN_MP2
10.0.0.10/30

GE

VLAN_MP2
10.0.0.9/30

VLAN_MP
10.0.0.2/30

SSH standby

LAN1

QNOMU standby

0/0/10

cfeigw, 169.254.0.5

NetAct

MX240 #2

mcRNC Iu/Iur control plane

(SCTP Multihoming)

mcRNC Iu/Iur control plane

OSPF 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

mcRNC Iu/Iur control plane

OSPF SiSo,
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

mcRNC Iu/Iur control plane

OSPF SiSo
Path To Control Plane 1 network

mcRNC BCN #1
SCTP -1

sctp2_1 10. 1. 8. 145/28

S F P + 11

VLAN _Iu _ C1
10 . 1. 8. 2 /2 8

sctp1_1 10 .1.8.17/ 28 (gw)

10GE

0/ 0/ 2

EIPU - 0

Static route to mcRNC

10. 1 .8 .16 / 28 via 10 . 1. 8. 2

VLAN _ Iu _C 1
10 .1 .8 .1 / 28
R1

MSC
Server/
MSS /
SGSN

EIPU - 2

SCTP -3

sctp1_1 10.1.8.19/28
sctp2_1 10.1.8.147/28
redundant
10GE

Backbone

mcRNC BCN #2
SCTP -2

sctp2_1 10 .1.8.146/ 28 (gw)

EIPU - 3

SCTP -4

S FP + 1 1

VLAN _Iu _ C2
10 .1 . 8. 130 / 28

sctp1_1 10.1.8.18/28

10 GE

0 /0 / 2

EIPU - 1

VLAN _ Iu _C 2
10 . 1. 8. 129 / 28
R2

Static route to mcRNC

10 . 1. 8. 144 / 28 via 10 . 1. 8. 130

sctp1_1 10.1.8.20/ 28
sctp2_1 10. 1. 8. 148/28

Path to Control Plane 2 network

mcRNC Redundancy cases

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
EIPU-0
EIPU-2

BCN-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
EIPU-0
EIPU-2

BCN-2
EIPU-1
EIPU-3

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
EIPU-0
EIPU-2
SCCP

BCN-2
EIPU-1
EIPU-3
SCCP
SCCP

SCCP
SCCP

SCCP

SCCP

SCCP
M3UA
SCTP
IP A1
IP A2

M3UA
SCTP
IP B1
IP B2

M3UA
SCTP
IP C1
IP C2

M3UA
SCTP
IP D1
IP D2

Multi-homed
SCTP
Association
#1

Multi-homed
SCTP
Association
#2

Multi-homed
SCTP
Association
#3

Multi-homed
SCTP
Association
#4

mcRNC Redundancy cases

1. EIPU failure (/BCN failure)

2. SW failure
3. Interface/link failure
4. Router failure (site switch)
Note: Failure cases are presented with one EIPU pair and with one QNUP recovery
group instance. In mcRNC deployment there are always two QNUP recovery group
instances per EIPU pair and all EIPU nodes have one active Recovery Unit present.

mcRNC OSPF Site Solution

OSPF Site Solution:
Normal operation
OSPF area

BCN 20

EIPU-1
QNUP-1 (Act)
IP.4.2 loopback

OSPF Site Solution:

1. EIPU failure (/BCN failure)

Router-2
IP.1.19/28 VL2
IP.1.3/28 VL1

VLAN 2

QNUP-1 (Standby)

Router-2
IP.1.19/28 VL2

VLAN 2
IP.1.17/28

IP.1.3/28 VL1

SWO

EIPU-0
QNUP-1 (Standby)

EIPU-1

IP.1.17/28

VL3

BCN 10

OSPF area

BCN 20

VL3

BCN 10

EIPU-0
IP.1.18/28 VL2
IP.1.2/28 VL1

IP.1.1/28
VLAN 1

Router-1

QNUP-1 (Act)
IP.4.2 loopback

IP.1.18/28 VL2
IP.1.2/28 VL1

IP.1.1/28
VLAN 1

LSA

Router-1

mcRNC OSPF Site Solution

OSPF Site Solution:
2. SW failure

OSPF Site Solution:

3. Interface/Link failure

OSPF area

BCN 20

Router-2

EIPU-1

QNUP-1 (Standby)

IP.1.19/28 VL2
IP.1.3/28 VL1

VLAN 2
IP.1.17/28

SWO

VL3

BCN 10

EIPU-0
QNUP-1 (Act)
IP.4.2 loopback

OSPF area

BCN 20

EIPU-1
QNUP-1 (Act)
IP.4.2 loopback

LOS

IP.1.19/28 VL2
IP.1.3/28 VL1

Router-2
VLAN 2
IP.1.17/28

VL3

BCN 10

EIPU-0
IP.1.18/28 VL2
IP.1.2/28 VL1

LSA

IP.1.1/28
VLAN 1

Router-1

IP.1.18/28 VL2
QNUP-1 (Standby)
IP.1.2/28 VL1

IP.1.1/28
VLAN 1

Router-1

mcRNC OSPF Site Solution

OSPF Site Solution:
4. Router / Site switch failure
OSPF area

BCN 20

EIPU-1
QNUP-1 (Act)
IP.4.2 loopback

LOS

Router-2

IP.1.19/28 VL2

The OSPF failure cases is the

same with 1GE and 10GE
shared crossed connectivity
model

VLAN 2
IP.1.17/28

IP.1.3/28 VL1

EIPU-3
EIPU-1

BCN 10

LSA

VL3

EIPU-2

EIPU-0
EIPU-0
IP.1.18/28 VL2
QNUP-1 (Standby)
IP.1.2/28 VL1

LSA

IP.1.1/28
VLAN 1

Router-1

10GE

mcRNC O&M L3
Static routes / OSPF
Redundancy cases
1. CFPU failure (/BCN failure)
2. SW failure
3. Interface/link failure
4. Router failure (site switch)
The similar redundancy principles apply for both static routes and OSPF
configuration options.

mcRNC O&M L3
O&M L3:
Normal operation

O&M L3:
1. CFPU failure (/BCN failure)

BCN 20

BCN 20

SSH-0 (Standby)

Router-2
IP.1.18/30 VL2

VLAN 2
IP.1.17/30

VL3

BCN 10

CFPU-0
SSH-0 (Act)
IP.10.10 loopback

CFPU-1

IP.1.2/30 VL1

VLAN 1

Router-1

IP.1.18/28 VL2

VLAN 2
IP.1.17/28

VL3

BCN 10

CFPU-0
IP.1.1/30

Router-2

SSH-0 (Act)
IP.10.10 loopback

SWO

CFPU-1

SSH-0 (Standby)

IP.1.1/28
IP.1.2/28 VL1

VLAN 1

Router-1

mcRNC O&M L3
O&M L3:
2. SW failure

O&M L3:
3. Interface/Link failure

BCN 20

BCN 20

CFPU-1

Router-2

SSH-0 (Act)
IP.10.10 loopback

IP.1.18/30 VL2

VLAN 1

SSH-0 (Act)
IP.10.10 loopback

SWO

IP.1.17/30

VL3

BCN 10

CFPU-0

LOS

CFPU-1

IP.1.18/30 VL2

Router-2
VLAN 1
IP.1.17/30

VL3

BCN 10

CFPU-0

SSH-0 (Standby)

IP.1.1/30
IP.1.2/30 VL1

VLAN 1

Router-1

IP.1.1/30
SSH-0 (Standby)

IP.1.2/30 VL1

VLAN 1

Router-1

mcRNC O&M L3
O&M L3:
4. Router / Site switch failure
BCN 20

EIPU-1
SSH-0 (Act)
IP.10.10 loopback

LOS
IP.1.18/30 VL2

Router-2
VLAN 1

IP.1.17/30

VL3

BCN 10

EIPU-0
IP.1.1/30
SSH-0 (Standby)

IP.1.2/30 VL1

VLAN 1

Router-1

Thank You !