MCRNC Configuration Principles

Multicontroller RNC
Ultimate power in pocket size
April 6th, 2010
Soc Classification level

1
Nokia Siemens Networks
mcRNC_07042010.ppt /
Why mcRNC?
Core ntw
Revolutionary RNC concept for WCDMA

High data capacity for mobile broadband traffic
mcRNC
High control plane capacity for smartphone traffic

IP based platform
High packing density solution
mcRNC
RNC2600 performance in 80% smaller size

mcRNC
Low OPEX
Plug and Play installation
mcRNC
Very small in size, minimized site space needed

Extremely low power consumption
No specific cooling required
Other major benefits

Co-siting with RNC2600 for additional capacity
Common platform with BSC

2
New RNC on Multicontroller Platform

Core ntw
mcRNC
Most excellent solution for Smartphone traffic
One processing environment for all functions
Best resource optimization for different traffic

mixes including increased signaling traffic
Large scalability
Same HW for all functions
mcRNC
Distributed functionality and redundancy over

the HW
mcRNC
Perfect fit to both heavily centralized and

distributed network topology including AC and
DC supply option
mcRNC

3
Low OPEX
Extremely small size and low power

consumption
No specific cooling required
Easy installation
Very low number of spares
Easy capacity upgrade
Easy traffic mix retuning without HW changes
mcRNC in a nutshell
Capacity upgradable to 35 Gbps
throughput in 8 modules
6 x 10/1 Gbps and 16 x 1 Gbps
Ethernet interfaces
Only 2 ms 2-way packet latency
No practical limit on simultaneous
HSPA users
Flexible capacity and connectivity
planning with common resource pool
Traffic profile retuning without HW
changes and service break
Fully HW redundant and operator
configurable with a min. 2 modules
Module size 4U (177mm), fits in 19
rack
AC and DC power supply options
Power consumption < 800 W /module
4
Future proof structure - full compatibility

with existing and new WCDMA/HSPA
networks
Full-blown RNC supporting without HW
changes all the standard 3GPP voice and
data services with any traffic mix
To be used with any existing or new
NSN Ultra- or Flexi-BTS with native IP
interface
Fits for any standard core network
elements with native IP connectivity
SW configurable internal resource
sharing provides the best flexibility and
support for new and upcoming services,
like Smartphone traffic

5
CS&PS
Core
Dimensioning basics for mcRNC
Only one processing environment for all the functions

Only one HW module type
Modules fully meshed
Full resource pooling for all the functionalities over the entire
network element of up to 8 modules
Resource allocations can be changed during the traffic
Impact/restart only on the resources, where the functionality is
changed
Resource reservation for redundancy as requested
Direct impact on overall capacity and/or connectivity

6
Module configuration principles
Option for AC or DC power modules

7
BOC-A
BOC-A
BOC-A
BOC-A
BOC-A
BOC-A
BOC-A
BOC-A
HDSAM-A
HD
U
Only one HW module
type
Each card inside can be
programmed to any
functionality
Flexible Dimensioning up to 50Gbps
RU40
Ultimate flexibility in capacity and connectivity planning

Unique type of processing resource servers all kind of RNC functionalities
SW defines mcRNC resource allocation in user plane, control plane,
management plane and transport plane
Flexible mcRNC dimensioning optimizes mcRNC capacity to meet best
real traffic load and profile requirements
Throughput evolution goes up to 50Gbps
Communities, presence,
browsing, email, maps,
gaming, TV, PC, video
SW Defined
Resource Allocation
Transport
Control
plane
SW Defined
Flexible Capacity
Connectivity
Management
User
Plane

8
Data
Voice

9
EIP
U
BOC-A
EIP
U
BOC-A
BOC-A
BOC-A
US
PU
EIP
U
BOC-A
BOC-A
EIP
U
US
PU
BOC-A
US
PU
BOC-A
BOC-A
US
PU
BOC-A
US
PU
US
PU
BOC-A
US
PU
BOC-A
BOC-A
US
PU
BOC-A
US
PU
US
PU
BOC-A
US
PU
BOC-A
BOC-A
CS
PU
BOC-A
US
PU
CS
PU
BOC-A
US
PU
BOC-A
BOC-A
CS
PU
BOC-A
CS
PU
CS
PU
BOC-A
CS
PU
BOC-A
CS
PU
BOC-A
CS
PU
BOC-A
CS
PU
BOC-A
CS
PU
BOC-A
CF
PU
BOC-A
CF
PU
BOC-A
HD
U
PT
U
BSAC-A
HDSAM-A
HDSAM-A HD
U
User specific services processing: The

rest of the processors (violet colour) are
shared between user specific UP and CP by
SW, (SN+)
PT
U
Control functions processing:

Mandatory for centralized functions,
one card in two modules (2N)
BSAC-A
External interface processing:

Min. two per configuration for
transport (SN+)
CS
PU
Cell specific services

processing: Number depends on
the coverage/connectivity, (N+M)
BOC-A
BOC-A
Physical units identical, functional

units SW definable with the
following principles
CS
PU
CS
PU
mcRNC HW configuration ( one example)
Standalone OMS with mcRNC

NetAct
Support for several
IPA2800-RNCs and/or
mcRNCs
Supports simultaneously up
to 10 RNCs
Less maintenance
Savings on HW & SW cost
OMS
Element Managers
GUI interface
Local user interface

Strong data aggregation
Commercial OMS HW
High capacity
High connectivity
Installation either on RNC
site or remotely (e.g. NetAct
site)

10
BTS
O&M
OMU
OMU
OMU
BTSs
BTSs
BTSs
Market leading asset and resource usage

lowest total cost of ownership
Unique site solutions
Green values
OPEX savings
Simple structure easy to install

reduced installation and site costs
Less HW parts
lower spare part costs
Single processing environment for all
functions
less HW reduced expansion
downtime
traffic profile retuning without HW
changes and service break
Secured network services

configurable redundancy according to
operator needs

11
Optimal transport for mcRNC

12
Multicontroller_RNC_0707909.ppt
mcRNC transport
mcRNC is designed for IP environment

direct IP/Eth interfaces in mcRNC front panels in each module
IP transport over PDH/TDM networks efficiently over E1/T1/JT1
Multilink-PPP (RAN1878)
support in BTS in RU30, aggregation in the IP router
improved transport efficiency for packet traffic over E1/T1/JT1
Efficient transport for small IP packets in RU30 (RAN1886)

Multiple IP interfaces from BTS in RU30 (RAN1317)
load sharing, traffic separation
ATM support only via co-siting solution together with

RNC2600
Direct ATM support from mcRNC under study (no decisions)
13
Hybrid Backhaul with IP Interfaces
RU30
End-to-End solution for decoupling cost from capacity

Enabling cost-efficient backhaul of HSPA peak rates
Solution consists of Flexi WCDMA BTS using
features
RAN74: IP based Iub

RAN1878: IP over ML-PPP on
Operator benefits
Savings of Hybrid Backhaul,
including synchronisation over TDM

network
E1/T1/JT1 Interfaces
IP is the single transport technology
RAN1317: BTS Backhaul over Multiple Protects previous investment in TDM
IP Interfaces
infrastructure (e.g. microwave radios)
and IP router terminating TDM layer and MLPPP
n x E1/T1
TDM Network
Ethernet
3G BTS
Ethernet

14
Ethernet
IP Router
Feature SW ID(s): RAN74, RAN1878, RAN1317
RNC
Efficient Transport for Small IP Packets
RU30
Transport bandwidth optimization for small IP packets,

e.g. in case of voice frames
With 3GPP compliant Iub/IP protocol stack each voice frame is transported in its
individual UDP/IP packet, resulting in low transport efficiency with a voice
dominated traffic mix
This feature introduces a multiplexing scheme in BTS and RNC, which allows
transporting multiple voice frames within the same IP packet on Iub & Iur
The multiplexing itself is transparent to the traversed transport network, i.e.
intermediate routers see only a normal UDP/IP packet
This allows to improve transport efficiency by up to 50%, leading to reduced
bandwidth needs and thus lower costs
standard
complian
t
IP
packets,
e.g.
Iub/IP
Payload
1
Payload 2
Payload 3
Mux
Payload 3
15
UD
P
IP
UD
P
IP
UD
P
IP
Demux
Payload 2
Payload
1
Feature ID(s): RAN1886
UD
P
IP
Common Multicontroller platform for

GSM and WCDMA/HSPA

16
Combined BSC, RNC Multicontroller

installation
Efficient Multicontroller BSC, RNC installation common transport for both
technologies
BSC, RNC Multicontroller

installation
GSM / EDGE
Site router
Packet
GSM / EDGE
Swtiched
WCDMA
network
BSC
RNC
WCDMA

17
Smooth
P RNC
capacity
C
upgrade
U
when need
for GSM TRX
or PCU
capacity
goes down
BSC and RNC in Multicontroller

Smooth capacity growth path for both directions
1
BSC basic module
BSC TRX extension module
BSC PS data extension module
RNC module
BSC in Multicontroller
RNC / BSC Multicontroller
1 100 TRX
2 048 Packet
Abis channels
for PS data
2 200 TRX
5 120 Packet
2 200 TRX
10 240 Packet
Abis channels
for PS data
Abis channels
for PS data
4
Standard 2
module
config.
capacity
Standard 3
at
p
th
w
ro
GStandard
3
or
f
h
module config.
capacity + 0.75 x
4th module
capacity
module
config.
capacity
RNC in Multicontroller
18
2200 TRX
26 624 Packet
Abis channels
for PS data
al
n
o
i
dit
d
a
ac
p
ca
Standard 4
ity
module config.
capacity + 0.875 x
5th module
capacity
One NetAct for both BSC and RNC in

Multicontroller
One NetAct for all Radio Technologies
OSS
Core Network
GSM / EDGE
Packet
Switched
network
Packet
Switched
network
BSC
Packet
Switched
network
RNC
WCDMA
Multicontroller
Seamless management of different radio access technologies with integrated tools

Single point for centralized management of root-cause failures, service quality
indicators and traffic information

19
Thank you!

20

MCRNC Configuration Principles

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

MCRNC Configuration Principles

Diunggah oleh

Hak Cipta:

Format Tersedia

Multicontroller RNC

Ultimate power in pocket size

April 6th, 2010

Soc Classification level

Revolutionary RNC concept for WCDMA

High control plane capacity for smartphone traffic

High packing density solution

RNC2600 performance in 80% smaller size

Very small in size, minimized site space needed

Other major benefits

Soc Classification level

New RNC on Multicontroller Platform

Most excellent solution for Smartphone traffic

One processing environment for all functions

Best resource optimization for different traffic

Same HW for all functions

Distributed functionality and redundancy over

Perfect fit to both heavily centralized and

Soc Classification level

Extremely small size and low power

No specific cooling required

Very low number of spares

Easy capacity upgrade

Easy traffic mix retuning without HW changes

Future proof structure - full compatibility

Soc Classification level

Dimensioning basics for mcRNC

Only one processing environment for all the functions

Soc Classification level

Module configuration principles

Option for AC or DC power modules

Soc Classification level

Only one HW module

Flexible Dimensioning up to 50Gbps

Ultimate flexibility in capacity and connectivity planning

Soc Classification level

Soc Classification level

User specific services processing: The

Control functions processing:

External interface processing:

Cell specific services

Physical units identical, functional

mcRNC HW configuration ( one example)

Standalone OMS with mcRNC

Support for several

Local user interface

Soc Classification level

Market leading asset and resource usage

Simple structure easy to install

Secured network services

Soc Classification level

Optimal transport for mcRNC

Soc Classification level

mcRNC is designed for IP environment

Efficient transport for small IP packets in RU30 (RAN1886)

ATM support only via co-siting solution together with

Hybrid Backhaul with IP Interfaces

End-to-End solution for decoupling cost from capacity

RAN74: IP based Iub

Savings of Hybrid Backhaul,

including synchronisation over TDM

Soc Classification level