RNC 3820 in P7

 RNC 3820 – Key Requirements

 Requirements and Assumptions
 User Plane L2 Switching
 Algorithm Updates
 RNC 3820 Software Deployment
 RNC 3820 Hardware Deployment
 Software Impact
 RNC 3820 Building Practice
 Characteristics
 Summary

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 1 RNC 3820 in P7 2008-08-15
 RNC 3820
Key Requirements and Enablers

1. High capacity RNC with increased node throughput

 Prepared for high Mobile Broadband penetration and eHSPA
 Elimination of ISL bottleneck

2. Improved scalability
 Board by board expansion

3. Increased flexibility to adopt to different traffic models

 Free board type allocation to slot positions
 Cost efficient

4. High power subrack and high capacity boards

 Increased node throughput and traffic capacity
 New Product
 Future proof

5. Same software/functionality as is the current RNC 3810

 Software aligned with RNC 3810

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 2 RNC 3820 in P7 2008-08-15
 RNC3820 Characteristic Requirements in P7
Assumption: 3 subrack configuration

Requirement Value Comment

Architectural max Iub throughput 20 Gbit/s Throughput if processors has
infinite capacity
Subscriber capacity according to 515 000
P6 ETM std
Subscriber capacity according to 1 150 000
the CTM
Subscriber capacity according to 120 000
the ETM bb
Max Iub throughput 4 Gbit/s

Number of simultaneously active 40 000

users
Number of URA users 1 000 000

Connectivity, Iub Links / Cells 768 / 2 304

RNC 3820 HW support for higher 34 Mbit/s

bitrates

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 3 RNC 3820 in P7 2008-08-15
 RNC3820 Requirements in P7
Requirement Comment
Software alignment RNC 3810 and 3820 shall use one
software source system. Software for
RNC 3810 and 3820 shall be
distributed as one deliverable. The
customer shall not experience an
additional SW handling effort with the
introduction of RNC 3820.
Control plane, user plane, transmission Improved scalability
interfaces capacity and RBS/Cell
connectivity shall be scalable on board
level and not correlated in-between
Adaptable to different traffic models Improved flexibility

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 4 RNC 3820 in P7 2008-08-15
 RNC3820 Assumptions in P7
Assumption Comment
Optimized for IP But, ATM must be supported,...

High capacity subrack available Power feeding/cooling: 1 600 W

Introduction of high capacity and power
consuming boards
- SCB-DF
Dual backplane available

High capacity boards available Increased node throughput and

capacity
GPB6 with 4 GB RAM
SPB3 with HW acceleration
High capacity internal Ethernet switching Increased node throughput
infrastructure available C-MXB and ET-IPG

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 5 RNC 3820 in P7 2008-08-15
 RNC 3820
Increased Throughput

RNC 3810 throughput is ISL limited

RNC R320
 User Plane Layer 2 Switching between subracks
 Allocation of Iu/Iub/Iur terminations in all RNC subracks

 No user plane traffic over ISL (except common channels and MBMS)
 Allows Iub Link “black box” configuration since every Iub Link can be
switched to all RNC subracks (only for IP)

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 6 RNC 3820 in P7 2008-08-15
 ISL Load in RNC 3810
Extension
Extension
DCH/HS user plane Subrack Iub
Iu Subrack
data flow
Iub ET
Iur RBS n
Main
Subrack ISL
ET dcSP

CN pdrSP
Node i Extension
Extension
dcSP Extension
Subrack
Subrack
Subrack
ISL
RNC j
dcSP
RBS k

ET

Note: Only devicies within a path with major Max ISL capacity per link = 330 Mbit/s
contribution to ISL load are shown Max ISL capacity per SCB/SXB = 620 Mbit/s

RNC 3810 maximum throughput: ~ 1 200 Mbit/s

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 7 RNC 3820 in P7 2008-08-15
 Elimination of ISL Load
– Iu/Iur/Iub terminations in every subrack
Iu
Iub DCH/HS user plane Extension
data flow Subrack
Iur
ET Fixed in URA
CN
state
Main pdrSP
Node i Subrack Fixed in
ISL
ET dcSP DCH/HS
state
pdrSP

RBS k dcSP Extension

Subrack
dcSP
RNC j
pdrSP

ET

All external node must be connected to all subracks !!!

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 8 RNC 3820 in P7 2008-08-15
 Elimination of ISL Load
– IP/Ethernet solution in RNC 3820 /three subracks in P7

ISLx2 = 620 Mbit/s Extension

Iu ESL = 10 Gbit/s Subrack
Iub ipET AAL2U/ATM
Iur
Main IP/Eth
pdrSP
Subrack
ISL
dcSP

pdrSP
CN
Node i dcSP Extension
Subrack
RNC j ISL
ipET
dcSP
RBS k
ESL pdrSP

ipET
ESL
DCH/HS user plane
data flow
 Front-end Ethernet Switching
3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 9 RNC 3820 in P7 2008-08-15
 Elimination of ISL Load
– ATM solution in RNC 3820 /three subracks in P7
Iu
ISLx2 = 620 Mbit/s Extension
Iub ESL = 10 Gbit/s Subrack
Iur AAL2U/ATM
atmET
CN
Node i Main IP/Eth
IpET pdrSP
Subrack
ISL
atmET dcSP

pdrSP

dcSP Extension
Subrack
RNC j ISL
IpET
dcSP
Applicable use
RBS k ESL IpET pdrSP cases
- URA  DCH/HS
atmET - Mobility

DCH/HS user plane

data flow
 Back-end Ethernet Switching
3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 10 RNC 3820 in P7 2008-08-15
 IP/Ethernet
”Front-end” Ethernet Switching
– L2 switching in front of L3 termination (IP ) of external i/f (ipET)
– Ethernet switch domain seen as part of TN

RNC Subrack m
SP
ipET
Device

ESL
IP/ETH RNC Subrack n
ipET

Note: Iub black box configuration supported

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 11 RNC 3820 in P7 2008-08-15
 User Plane Communication Paths
IP/Ethernet / Iu-CS  Iub/Iur
L2 Switching Scenario: ”Front-end” Ethernet Switching

User Plane
RNC Subrack m
AAL2u AAL2u
ipET dcSP ipET

ESL ESL

ETH ETH

Iu-CS RNC Subrack n Iub/Iur

Prioritized path Ethernet Switch

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 12 RNC 3820 in P7 2008-08-15
 User Plane Communication Paths
IP/Ethernet / Iu-PS  Iub/Iur
L2 Switching Scenario: ”Front-end” Ethernet Switching

User Plane
RNC Subrack m AAL5 AAL5 AAL2u

ipET pdrSP dcSP ipET

ipET

ESL ISL ESL

ETH ETH
ipET pdrSP ipET
Iu-PS RNC Subrack n Iub/Iur

“Back-end” Ethernet switching of AAL5

not supported in P7
To be added in P8 or change bearer to AAL2?

Prioritized path Ethernet Switch

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 13 RNC 3820 in P7 2008-08-15
 ATM/SDH terminations
”Back-end” Ethernet Switching
– L2 switching behind L3 termination (AAL2 ) of external i/f (ATM-ET)
– 10 GE switch internal and used as complement to AMAX (ATM) switch

RNC Subrack m
SP
Device
ipET

ESL
RNC Subrack n

ATM ATM
ipET
ET

Note: Only used by AAL2

Same physical Eth infrastructure as in front-end case but
VLAN separated
3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 14 RNC 3820 in P7 2008-08-15
 User Plane Communication Paths
ATM/SDH / Iu-CS  Iub/Iur
L2 Switching Scenario: ”Back-end” Ethernet Switching

User Plane
RNC Subrack m
AAL2 AAL2u AAL2u
ATM ATM AAL2
dcSP
ET ETH ETH ET
ET ET

ESL ISL ESL

ISL

ATM AAL2u ETH ETH AAL2u ATM

ET ET ET ET
Iu-CS Iub/Iur
RNC Subrack n

Used if bandwidth per flow > x,

otherwise ISL
Note: M-MGw only have user plane terminations (AAL2 paths) in one subrack

Prioritized path Ethernet Switch

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 15 RNC 3820 in P7 2008-08-15
 User Plane Communication Paths
ATM/SDH / Iu-PS  Iub/Iur
L2 Switching Scenario: ”Back-end” Ethernet Switching

User Plane
RNC Subrack m
AAL5 AAL5 AAL2u
ATM AAL5 ATM AAL2
pdrSP dcSP
ET ETH ETH ET
ET ET

ESL ISL ESL

ATM AAL5 ETH ETH AAL2u ATM

pdrSP
ET ET ET ET
Iu-PS Iub/Iur
RNC Subrack n

Not supported in P7. Used if bandwidth per flow > x,

ISLs must be used, unless all otherwise ISL
SGSN nodes are connected to all
subracks
Change bearer to AAL2 in P8?

Prioritized path Ethernet Switch

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 16 RNC 3820 in P7 2008-08-15
 Ethernet Switching
– Deployment P7

ETH
RNC Subrack n
SP
ipET
Device

E S
C
T C
M
I B
X P D
B G F

ATM Backplane (legasy)

Dual Backplane
10 GE Backplane
1 GE for CMXB control

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 17 RNC 3820 in P7 2008-08-15
 Ethernet Switching
– Deployment P6

ETH
RNC Subrack n
SP
ipET
Device

S
E
T C
M B
F
X
D
F

ATM Backplane

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 18 RNC 3820 in P7 2008-08-15
 Improved Scalability and Flexibility

RNC 3820 architecture supports

 Initial node dimensioning on board level
 Board by Board expansions
 Free slot usage

,... however, not fully utilized in the first RNC 3820 release

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 19 RNC 3820 in P7 2008-08-15
 Improved Load Distribution and
Pooling Concepts
 Iub Link Soft Distribution
– Resource Handling of IubLink terminations and cell handling
instances
– Load distribution over module MPs (mMP/LmCell)
 UE Context Pooling
– Resource Handling of Ue Context handling instances
– Load distribution over module MPs (mMP/LmUe)
 dcSP Resource Pooling
– Resource Handling of MAC-d terminations
– Load distribution over dedicated channel devices (dcSP)
 pdrSP Pesource Pooled
– Resource Handling of GTP-U terminations
– Load distribution over GTP-U paths and packet data router devices
(pdrSP)
All resources pooled on Node Level

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 20 RNC 3820 in P7 2008-08-15
 Iub Link Soft Distribution
P6 RNC Node P7 RNC Node
Main subrack: 0 Main subrack: 0
OSS-RC Console OSS-RC Console
mMP mMP mMP mMP
Add RBS: RbsC
Add RBS: 104 108 atmUserPlaneTerm 104 108
PreferredSubrackRef: SubrackRef: 108
(Mandatory) (Optional)
Ext. Subrack: 1 Ext. Subrack: 1
mMP mMP mMP mMP
RbsC
116 120 116 120
120
Algorithm:
Algorithm: If atmUserPlaneTerminationSubrackRef is set then
select mMP with preferredSubrackRef with least same as in P6
IubLinks + UtranCells configured else
select mMP within the whole RNC with least
IubLinks + UtranCells configured

Consider mMP capacity

This “Black-box IubLink configuration is

possible for “IP RBSs” in both 3810 and 3820 Architecture
since both support front-end Ethernet switching for Iub

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 21 RNC 3820 in P7 2008-08-15
 UE Context Pooling
P6 P7
Sort Sort
Load 7 mMP 1 Load 7 mMP 1
Load 7 mMP 1 Load 7 mMP 1 No Redirect
because of Load 24 mMP 2 Load 17 mMP 10
Load 24 mMP 2 Load 12 mMP 4 threshold
10% Load 67 mMP 3 Load 24 mMP 2
Load 83 mMP 3 Load 19 mMP 6
Load 51 mMP 4 Load 39 mMP 6
Load 12 mMP 4 Load 24 mMP 2 Redirect
Load 55 mMP 5 Load 50 mMP 13
Load 50 mMP 5 Load 50 mMP 5
Load 39 mMP 6 Load 51 mMP 4
Load 19 mMP 6 Load 83 mMP 3 No Redirect
Load 83 mMP 7 Load 53 mMP 9 because of
threshold
Algorithm works on subrack level Load 79 mMP 8 Load 55 mMP 5 10%

Load 53 mMP 9 Load 57 mMP 12

Load 17 mMP 10 Load 57 mMP 15

Load 81 mMP 11 Load 59 mMP 14

Load 57 mMP 12 Load 67 mMP 3 Redirect

Load 50 mMP 13 Load 79 mMP 8 Redirect

Load 59 mMP 14 Load 81 mMP 11 Redirect

Load 57 mMP 15 Load 83 mMP 7 Redirect

Algorithm works on node level

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 22 RNC 3820 in P7 2008-08-15
 RNC 3820 Software Deployment
GPB Software Allocations
RNC 3810 RNC 3820
c c1MP
MP
4 GB RAM
GPB* GPB6

oam
MP

GPB*

rar c2MP
MP

GPB* GPB6

sccp
MP

GPB*

mMP mMP

GPB* GPB6

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 23 RNC 3820 in P7 2008-08-15
 RNC 3820 Software Deployment
SPB Software Allocations
RNC 3810 RNC 3820
DC
DC
DC DC
CC CC
PDR PDR

Notes:
SPB3

SPB3
Type A Type A 1. No co-location of ccSP
and dcSP devices
DC DC
DC
2. SPB3 – PPC GX with
DC DC 256 MB RAM
DC DC 3. HW accelaration in
CC CC
FPGA on dcSP
SPB3

SPB3
Type B Type B

DC DC DC DC
DC DC
DC DC DC DC
DC DC DC DC
PDR DC PDR DC
SPB3

SPB3

SPB3

SPB3

Type C Type D Type C Type D

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 24 RNC 3820 in P7 2008-08-15
 RNC 3820 Hardware Deployment
– Supported Node Configurations
Extension
Subrack 2

Extension Extension
Subrack 1 Subrack 1

Main Subrack Main Subrack Main Subrack

RNC 3820 Type A RNC 3820 Type B RNC 3820 Type C

Iub Max: ~ 1,2 Gbit/s ~ 3,0 Gbit/s ~ 4,8 Gbit/s
Subscriber capacity: ~ 330 ksubs ~ 790 ksubs ~ 1 250 ksubs
Simult. Active calls: ~ 3 500 Erl ~ 14 300 Erl ~ 25 000 Erl

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 25 RNC 3820 in P7 2008-08-15
 Subrack Layout Data centric
Mbps
200
Erl
150
# Subs
1 800
IP/Ethernet Example Voice centric 110 2 500 72 500

c-pack
Extension Subrack
mMP

mMP

mMP

mMP

mMP

mMP
DC DC DC DC DC DC DC DC DC DC DC DC DC
DC DC DC DC DC DC DC DC DC DC DC DC DC
DC DC DC DC DC DC DC DC DC DC DC DC DC
DC CC DC DC DC CC DC DC DC CC DC DC CC
SCB-DF *

SCB-DF *
DC PDR DC CC DC PDR DC CC DC PDR DC CC PDR

ET-IPG *
ET-IPG *

ET-IPG

ET-IPG
CMXB *

CMXB *
SPB *

SPB *

SPB *
GPB

GPB

GPB

GPB

GPB

GPB
SPB

SPB

SPB

SPB

SPB

SPB

SPB

SPB

SPB

SPB
t-pack/IP
Main Subrack
c1MP

c2MP
mMP

mMP

mMP

mMP

c2MP

mMP

c1MP
DC DC DC DC DC DC DC DC DC
DC DC DC DC DC DC DC DC DC
DC DC DC DC DC DC DC DC DC
DC CC DC DC CC DC DC DC CC
SCB-DF *

SCB-DF *
DC PDR DC CC PDR DC DC CC PDR
ET-IPG *

ET-IPG *
ET-IPG
GPB *
CMXB *

CMXB *
GPB *

GPB *
GPB *

GPB *

GPB *
TUB *

TUB *
SPB *

SPB *

SPB *
GPB

GPB

GPB
SPB

SPB

SPB

SPB

SPB

SPB

0 1 2
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8

* = Mandatory Slot, n = 10 GE slot

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 26 RNC 3820 in P7 2008-08-15
 Subrack Layout
ATM/SDH Example
Extension Subrack t-pack/ATM
mMP

mMP

mMP

mMP
DC DC DC DC DC DC DC DC DC
DC DC DC DC DC DC DC DC DC
DC DC DC DC DC DC DC DC DC
DC CC DC DC DC CC DC DC CC
ET-MF4/41

ET-MF4/41

ET-MF4/41

ET-MF4/41

ET-MF4/41

ET-MF4/41
SCB-DF *

SCB-DF *
DC PDR DC CC DC PDR DC CC PDR

ET-IPG *
ET-IPG *

ET-IPG
CMXB *

CMXB *

SPB *
GPB

GPB

GPB

GPB
SPB

SPB

SPB

SPB

SPB

SPB

SPB

SPB
Main Subrack
c1MP

c2MP
mMP

mMP

mMP

c2MP

mMP

c1MP
DC DC DC DC DC DC DC
DC DC DC DC DC DC DC
DC DC DC DC DC DC DC
DC CC DC DC CC DC CC
SCB-DF *

SCB-DF *
DC PDR DC CC PDR CC PDR
ET-IPG *

ET-IPG *

ET-IPG *
ET-MF4

ET-MF4

ET-MF4

ET-MF4
CMXB *

CMXB *
GPB *

GPB *
GPB *

GPB *

GPB *
GPB
TUB *

TUB *
SPB *
GPB

GPB
SPB

SPB

SPB

SPB

SPB

SPB

0 1 2
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8

* = Mandatory Slot, n = 10 GE slot

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 27 RNC 3820 in P7 2008-08-15
 RNC 3820 Hardware Architecture
- switched dual backplane supported
TN Infra Structure
1..1 GPS
IP/Ethernet ATM
Traffic IP/Ethernet
(e.g. Mub/Mut) CMXB SCB-DF
Node infrastructure
Mandatory
ATM VC CC ET-IPG TUB
Traffic ATM-ET TUB SCB-DF
(e.g. Mub/Mut) CMXB ATM backplane
GPB SPB
OSS-RC Mur
-48V/DC ET-IPG Ethernet
backplane
Ext. Mgmt Main Subrack
Sys
ESL ISL Central MP
Thin Client/ Mur Mandatory in Main Subrack
4 boards
Console
0..2 GPB
Iu
CN Module MP
CMXB SCB-DF At least 2 boards per node
Iur
RNC ET-IPG GPB
Iub ATM-ET
Module SP
RBS GPB SPB At least 2 boards per subrack

-48V/DC
SPB
Extension Subrack

ATM Support ATM-ET

RNC Optional

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 30 RNC 3820 in P7 2008-08-15
 Cabinet Layout
Extra Fan unit
BYB 501
Extension • 1 - 3 High Power Subracks with extra
Subrack 2 fan units
Fan unit • 2 Active Patch Panels including O/E
Air intake converter
Extra Fan unit

Extension
Subrack 1
Fan unit
Air intake
Extra Fan unit

Main
Subrack High Power Subrack
Fan unit (HPS)

Air intake
APP
APP Active Patch Panel (APP)
Cable shelf

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 31 RNC 3820 in P7 2008-08-15
 High Power Subrack (HPS)
Mechanical solution

Extra fan unit

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 32 RNC 3820 in P7 2008-08-15
 High Power Subrack (HPS)
Fan Unit • 8 small fan motors arranged in a 4*2
configuration so that each subrack slot
is serviced by two fan motors.
1 2 3 4
• Two equal and identical control units
control 4 fan motors each in such a way
5 66 7 8 that a single fan control unit failure only
affects one of the fans cooling a specific
slot.

• Pushing fan will press out dust

• Pluggable, no screws
• Normal air speed 3,5m/s
• Air speed 1,7-1,8 m/s at fan
motor failure
• Fulfils noise requirements

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 33 RNC 3820 in P7 2008-08-15
 Dual Backplane
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

Address
plug

(22 + 2) 10G Device Boards

4 6 8 10 12 14 15 17 19 21 23 25
Four Lane
Dual star
(10G Eth)

AMAX
Dual star

SCB-DF SCB-DF
TUB TUB
CMXB CMXB

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 34 RNC 3820 in P7 2008-08-15
 Active Patch Panel (APP)
Connector layout

KDU 137 557/2 O/E Converter unit.

Dimensions: H=25 mm W= 450 mm D= 100 mm.
Power consumption: Max 30W.

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22

6 SFP slots (1, 2, 4, 5, 7 and 8) for maximum 1 Gbps Ethernet

2 SFP slots (10 and 12) for maximum 10 Gbps Ethernet
4 RJ-45 connectors (14, 15, 17,18) for E1/T1, Ethernet and RS232
2 connectors for Supervision and control (20 and 21)
1 connector for power supply to the SFP slots (22)

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 35 RNC 3820 in P7 2008-08-15
 RNC – Software Impact
Algorithms
 RNC ICM impact
– Add, remove and replace ET, SPB amd mMP boards

 RNC UeContext Resource Handling

– Improved algorithm to spread load between mMP on node level

 RNC DDA
– mMP and SP capacity are considered (processor capacity and memory)
– SP allocation across subrack boarders

 RNC IubLink Soft Distribution

– New algorithm that enables black box configuration of IubLink
(transport option IP)
– mMP capacity is considered (16/32/32/64)

 RNC SP Resource Handling

– dcSP and pdrSP allocated in same subrack if possible. Central SP RH informed of Sp
availability per mMP and subrack
– Initially select dcSP in the same subrack as the Iub Link termination

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 36 RNC 3820 in P7 2008-08-15
 RNC – Software Impact
Algorithms, cont.
 RNC L2 Ethernet Back-end Switching
– Connection flow chart of dcSP to external node. IpHost selected in preferred subrack (IP
transport). ETH Switch used to offload ISL (ATM transport)

 RNC Improved Resource Layer

– Handle passed to requesting RH
– Architectural and capacity improvement

 RNC IuLink Load Information

– Consider available GTP-U path bandwidth in the pdrSP resource algorithm.
High loaded GTP-U paths shall be avoided when allocating PDR resources

 RNC Encapsulation of AAL2 NCI

– DRH takes care of AAL2 NCI
– Architectural improvement

 RNC System Parameter Support

– System parameters based on node variant and hardware release

 RNC System Upgrade

– Free slot usage adaptations in board-by-board upgrade

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 37 RNC 3820 in P7 2008-08-15
 RNC Characteristics
Capacity - CTM Optimized

2 500 000
Number of subscribers

2 000 000
RNC 3810 - Type C
1 500 000 RNC 3810 - Type F

1 000 000 RNC 3820 - Est.

RNC 3820 - P7 Req.
500 000

0
P6 P7 P8

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 38 RNC 3820 in P7 2008-08-15
 RNC Characteristics, cont’d
Iub Max Throughput - DTM Optimized

14 000
12 000
10 000 RNC 3810 - Type C
Mbit/s

8 000 RNC 3810 - Type F

6 000 RNC 3820 - Est.
4 000 RNC 3820 - P7 Req.

2 000
0
P6 P7 P8

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 39 RNC 3820 in P7 2008-08-15
 RNC Characteristics, cont’d
Throughput vs. Production Cost

4,00000
3,50000
3,00000
RNC 3810 - Type C
2,50000
RNC 3810 - Type F
2,00000
RNC 3820 - Est.
1,50000
RNC 3820 - Req.
1,00000
0,50000
0,00000
P6 P7 P8

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 40 RNC 3820 in P7 2008-08-15
 RNC 3820 FDIs in P7
Intro RNC 3820 Macro Architecture in Wiona RNC

Algorithms for Connection and Ue Context Resource Handling

RNC Macro Device and SP Resource Handling
Architectur
ICM 3820 impact
Soft Software Upgrade
System Parameter Support

Product Handling and Production: Configuration

Product Key and Commercial Product
Handling
Product Handling and Product Structure
Product Handling and Production: 3PP and Export
Licensing

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 41 RNC 3820 in P7 2008-08-15
 RNC 3820 FDIs
RNC 3820 Macro Architecture in Wiona RNC

Hardware HW and SW configurations

and
Production Node HW FDI for Wiona RNC 3820

Characteristics Traffic Characteristics

and O&M Characteristics
Dimensioning
RNC Resource Dimensioning
Measurement and Tuning
Memory Dimensioning

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 42 RNC 3820 in P7 2008-08-15
 RNC 3820 - Summary
• RNC design prepared for high Mobile Broadband penetration and eHSPA
• Cost efficient for all applicable traffic models and capacity requirements
• Same software/functionality in the evolved RNC as is the current RNC 3810
• Same circuit board types in the evolved RNC as is the current RNC 3810
Characteristic for a 3 subrack deployment in one cabinet
Initial Design Cabinet outline:
product issue Potential Ext Subrack 2 (optional)
S G C E S
Subscriber capacity 1 6 Msubs M T
C P X I P
Iub Throughput 2 20 Gbit/s B B B P B
G
• New subrack and subrack interconnect
• High power subrack (1500 W) to enable use of Ext Subrack 1 (optional)
S G C E S
high capacity processing components M T
C P P
• Node internal switched 10 GE network for high rate B I
B B X P B
data distribution G
• New node expansion principle Main Subrack (mandatory)
ISL
Support for board by board expansion with separate S T G 10GE
C E S
M T
dimensioning of: C U P B I
P
• Voice capacity B B B X P B
G
• Data capacity
• Transmission Iu, Iur, Iub
• RBS/Cell connectivity Mur
3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 43 RNC 3820 in P7 2008-08-15
3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 44 RNC 3820 in P7 2008-08-15
 Network Scenario - Generic
Core Network

Iu UP
Switch

OSS
RC IP/Eth and/or RNC
ATM/SDH Node
RNC
Node Iur UP
Switch

Transport
Iu/Iur/Iub L2 User Plane Switch Network
• AAL2 switch or Ethernet switch
• Iu/Iur/Iub UP terminations are dynamically allocated to
any RNC subrack Iub UP
 Iu, Iur and Iub terminations are allocated within the Switch
same subrack for a user plane path, i.e. no ISL UP traffic
• can be be a part of the RNC Node
 will hide RNC Iub/Iur interface allocations on subracks
 simplified RBS/TN deployment
• is optional (but recommended for high capacity nodes)

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 45 RNC 3820 in P7 2008-08-15
 Network Scenarios

 IP/Ethernet
– Front End Ethernet Switching
 ATM SDH
– Internal Ethernet Switching

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 46 RNC 3820 in P7 2008-08-15
 Network Scenario – IP/Ethernet
Ethernet Swiching (front end)
Core Network
IP/Ethernet

OSS
RNC Node
RC
IP/Eth
RNC Ethernet
Switch
Node

Node internal
Used mainly as Iu/Iub/Iur switch,
i.e. as a general ”front end switch”

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 47 RNC 3820 in P7 2008-08-15
 Network Scenario – IP/Ethernet
Ethernet Switching (front end)

RNC Node
Mur Mur
Mub Iu /cp+up IP/Ethernet
Mut Iur /cp+up
Iub /cp+up
Main
Control plane only
Iu Subrack

Ext.
Iur Ethernet Subrack
Iu /up [0..n]
Switch
Iur /up
Iub Iub /cp+up

Node internal

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 48 RNC 3820 in P7 2008-08-15
 Network Scenario – ATM/SDH
Internal Ethernet switching
Core Network

ATM/SDH

OSS
RNC Node
RC
ATM/SDH
Ethernet
RNC Switch

Node

Used as internal switch for inter

subrack communication, gateway for
AAL2/ATM  IP/Ethernet translation

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 49 RNC 3820 in P7 2008-08-15
 Network Scenario – ATM/SDH
Internal Ethernet switching

Mur RNC Node

Mub
Mut
Mur Iu /cp+up
Mub Iur /cp+up
ATM/SDH
Mut Iub /cp+up Main
Subrack

Iu

Extension
Iur Subrack Ethernet
[0..2] Switch
Iu /up
Iur /up Control plane only
Iub Iub /cp+up

3/2882-10/FCP 103 6503 Uen Rev C Ericsson Internal 50 RNC 3820 in P7 2008-08-15