Network Engineering Info (NEI) Feature Deep Dive Multicontroller
RNC
Network Engineering Info (NEI)Feature Deep Dive Multicontroller
RNCBartosz MaciejakMBB CS Network EngineeringPlease always check
the latest version of this document under the following link: hereR
255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G
113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:# Nokia Siemens
Networks 2012For internal useMBB Network Engineering# Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network EngineeringAgendamcRNC resource
managementBCN HW ArchitecturemcRNC Functional ArchitecturemcRNC
ProtectionHW terms and abbreviationsExternal physical connectivity
incl. backplane connection schemesTraffic FlowsmcRNC roadmapGeneral
introductionmcRNC Capacity limitsmcRNC dimensioning (incl. ANT_3G
user guidance)# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringAgendaHere is an example of what your agenda could look
like.
AgendamcRNC resource managementBCN HW ArchitecturemcRNC
Functional ArchitecturemcRNC ProtectionHW terms and
abbreviationsExternal physical connectivity incl. backplane
connection schemesTraffic FlowsmcRNC roadmapGeneral
introductionmcRNC Capacity limitsmcRNC dimensioning (incl. ANT_3G
user guidance)# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringAgendaHere is an example of what your agenda could look
like.
mcRNC introductionWhat is mcRNC ?NSNs next generation Radio
Network ControllerUsing Box based modular HWHas small footprint,
high density, low cost, highly efficient RNCBased on Scalable,
extensible, customizable, controllable SW Architecture.All IP
NE
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network Engineering
Most excellent solution for various trafficsOne processing
environment for all functionsBest resource optimization for
different traffic mixes including increased signaling
trafficPerfect fit in SingleRAN controller casesSame platform with
mcBSCLarge scalabilitySame HW for all functionsDistributed
functionality and redundancy over the HWPerfect fit to both heavily
centralized and distributed network topology including AC and DC
supply optionLow OPEXExtremely small size and low power
consumptionNo specific cooling requiredEasy installation, easy
capacity upgradeVery low number of sparesEasy traffic mix retuning
without HW changesmcRNC introductionWhy mcRNC ?
mcRNCmcRNCmcRNCmcRNCCore ntw# Nokia Siemens Networks 2012For
internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166
B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R
255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:MBB
Network Engineering6VGI-AAA123-20060724-mcRNC introductionmcRNC in
nutshell
Capacity upgradable to 8 modules (in RU40)6 x 10/1 Gbps and 16 x
1 Gbps Ethernet interfaces Only 2 ms 2-way packet latencyTraffic
profile retuning without HW changes and service breakFully HW
redundant and operator configurable with a min. 2 modulesModule
size 4U (177mm), fits in 19 rackPower consumption < 550 W
/module
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network
Engineering7VGI-AAA123-20060724-mcRNC introductionmcRNC
Architecture comparison with cRNCSFU NIP1 TBU MXU RRMU RSMU OMU WDU
FDU NEMU Iu Iu r Iub E1 / T1 / JT1 ATM IMA EHU WDU Ethernet MXU MXU
RSMU OMU WDU FDU NEMU Iu Iu r Iub E1 / T1 / JT1 ATM IMA EHU WDU
Ethernet MXU MXU DMCU A2SU ICSU GTPU NIS1 / NIS1P Iu Iu r Iub STM -
1 MSP1+1 ATM VC4 / VC3 Optional units: Basic units: Iu - BC Iu -
BC
only one module type only one add-in card type only one
processor type
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network Engineering Only
one HW module type Each card inside can be programmed to any
functionality
mcRNC IntroductionGeneral introduction
Option for AC or DC power modules
HDUBOC-AHDSAM-ABOC-ABOC-ABOC-ABOC-ABOC-ABOC-ABOC-A# Nokia
Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B
0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R
170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G
170 B 0Primary colors:MBB Network
Engineering9VGI-AAA123-20060724-AgendamcRNC resource managementBCN
HW ArchitecturemcRNC Functional ArchitecturemcRNC ProtectionHW
terms and abbreviationsExternal physical connectivity incl.
backplane connection schemesTraffic FlowsmcRNC roadmapGeneral
introductionmcRNC Capacity limitsmcRNC dimensioning (incl. ANT_3G
user guidance)# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringAgendaHere is an example of what your agenda could look
like.
mcRNC IntroductionWCDMA mcRNC Roadmap mcRNC HW Rel2100k Erl
AMR16Gbps DL+UL1000 BTSs6000 Cells1 000 000 RRC connected state
users8 800 000 BH call attempts
HSPA DL 168 Mbps Multi-Cell with MIMOHigh Speed Cell_FACH
(UL+DL)FeaturesAutomatic mcRNC Resource OptimizationSelective BTS
Resource Re-Balancing in mcRNC
HSPA HSDPA 336MbpsUL 23 Mbps Dual-Cell Multi-User MIMOFeatures
RNC PoolMulticontroller RNC Energy SavingZero DowntimeIntegrated
Local Breakout
1,2 Enhancement Package (EP)
RU30 RU40RU50 AvailableReady for ContractsStudy ItemsCapacity46
900 Erl AMR14.3 Gbps DL+UL1550 BTSs11 650 Cells1 440 000 RRC
connected state users14 500 000 BH call attempts1HSPADL 84 Mbps
Dual-Cell with MIMO2DL 42 Mbps 64QAM & MIMO1UL 11 Mbps
16QAM2FeaturesLocal BreakoutLatency mcRNC HSPA latency 2 ms
mcRNC2.0 with first HW release BCN-A1 module type with Octeon+
processor Two HW configurations supported (2 and 6 modules) Full
RU30EP2 feature parity by C5mcRNC3.0 with first and second HW
releases supported Second HW release (BCN-B2) bringing impoved
capacity via more powerful Octeon2 processor More HW configurations
supportedImproved/optimized capacity without new HW
Improved network level performance => Pooling of RNCs
(RNC2600 & mcRNC) for load sharing and redundancy
Impoved operability and maintenance
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringmcRNC
IntroductionWCDMA mcRNC Roadmap C1: initial content for program
defined C3: ready for contractCP: limited commercial
availabilityC5: full commercial availability Always check the dates
and feature content with the latest official roadmapC3: ready for
contract / CP: limited commercial availability / C5: full
commercial availability
2011201220132014Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4RU30 EP1RNC EP1 BTS
EP1
mcRNC2.0
RU30 EP2
Flexi Direct RU30
RU40mcRNC3.0Flexi Direct RU40
C5 06/13CP 03/13CP 08/12CP 06/11C5 11/12C5 09/11C5 06/12CP
05/12C5 09/12CP 04/12C5 06/12C3 09/11C5 10/13CP 06/13C5 10/13CP
06/13# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network Engineering
mcRNC Introduction mcRNC1.0 and 2.0 current status mcRNC1.0First
SW release finalized and piloted in Summer 2011With two module HW
configurationCommercial HW has been available since 2Q 2011With
RU20EP feature content mcRNC2.0Current SW release with increased
feature content and HW configurationmcRNC2.0 SW scheduleCP declared
in MarchC5 end of May 20122 and 6 module configurations supportedNo
changes in basic HW designCatch up with RU30EP2 feature content by
C5 # Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringmcRNC
Introduction Planned/agreed customer activities with mcRNC2.0
Activity and locationLive pilot ongoingCentral Europe, with two
module configurationSouth East Asia, with 6 module
configurationTest bedNorth AmericaEarly ProjectsParallel to R&D
customer pilots NSN is having early customers with special Early
Project support (EP)Typical EP customer cannot give R&D pilot
commitment or the pilot schedule is not suitable, but are willing
to start in test bed and/or field with limited amount of usersThe
EPs have access to the pilot SW and the R&D fault handling is
the same as in pilotsEP support planned with a number of customers
inCentral EuropeMiddle EastSouth America
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network Engineering
mcRNC Introduction mcRNC3.0 current statusmcRNC3.0 as part of
RU40 system releaseSW release with increased feature content and
more HW configurationNew processor version available in (BCN-B2)
module HWApprox. duplicated capacity in same sizemcRNC3.0 is part
of RU40 system releaseCP June 2013C5 October 20132, and 4 module
configurations in plansNew mcRNC specific features in
RU40:Co-Siting with RNC2600 (as a first step to RNC pooling
concept)Selective BTS Resource Re-Balancing10 Gbps external
interface support
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringAgendamcRNC resource managementBCN HW ArchitecturemcRNC
Functional ArchitecturemcRNC ProtectionHW terms and
abbreviationsExternal physical connectivity incl. backplane
connection schemesTraffic FlowsmcRNC roadmapGeneral
introductionmcRNC Capacity limitsmcRNC dimensioning (incl. ANT_3G
user guidance)# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringAgendaHere is an example of what your agenda could look
like.
BCN HW ArchitectureThe box
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringBCN HW
ArchitectureThe box
Fans and power supply units field replaceable and hot
swappableOptional air filterAdd-in cards# Nokia Siemens Networks
2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R
163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G
0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary
colors:MBB Network Engineering
BCN HW Architecture Motherboard and Processor Add-in
CardsProcessor Add-in CardMotherboardAll interfaces,
Interconnections and HW management on the Motherboard.Processing
elements and memory on the Add-in Cards.Two XAUI interfaces for
each Add-in card (20Gbps). 240Gbps switchPCIe and IPMI interfaces
for booting and controlEasy to upgrade new Processor Add-in Card,
when processor technology evolves.Flexible for any processor
architecture (x86, PPC, MIPS, DSP) in processor Add-in Cards and
mix them. Power SupplyAMC Slot~40mmDual Fan Module# Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network EngineeringBCN HW ArchitectureCabinet
installation19 cabinet with max. configuration8 pcs of modules with
cable trays in front2 pcs of PDU (either AC or DC) modules on the
top /
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringBCN HW
Architecture Processors RU30 EP2 Cavium Octeon+ CN5650 12x MIPS64
cores. 2MB of L2 cacheReplaces the dedicated processing
architectures used in the pastx86, TI DSP, PowerQuicc and APP
network processors. Big-endian, which is different compared to x86
hardware Minor impact on the current control plane SW.
RU40Introduction of Cavium Octeon II CN68xx processors32 x
cnMIPS II cores, 4MB L2 cache, 4xDDR3 slotsApproximately doubled
performance in comparison to CN5650
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringBCN HW
Architecture HW Architecture scheme22 x10GE + 20 x 1GEEthernet
Switch
DomainRS232ManagementEthernetSwitchFEUSB/PCIHDContr.USBPCIePrimaryOcteonUSBHUB1000Base-TLMPPQ
processorUARTPCIAMCBay 1Hard disc Cross
connectUARTFlashdiscSFPSFP10GigE10GigESFP+SFP+SFP+10GigE10GigE10GigE10GigESFP+SFP+SFP+AMCBay
2BIBIFIFI12PCIe
switchGigEGigE3434SFPSFPSFPSFPSFPSFPSFPSFPSFPSFPSFPSFPSFPSFPPayloadOcteonPayloadOcteonPayloadOcteonPayloadOcteonPayloadOcteonPayloadOcteonPayload/PrimaryOcteon10GigE10GigE10GigE10GigE10GigE10GigE10GigE10GigE10GigE10GigE10GigE10GigE10GigE10GigE10GigE10GigEUSBSFPSFP5MACMACPCIeRTCIPMB-L2MHz
sync.
inTelcosynch..Externalalarms76PCIe65USBGigEGigEGigEGigEGigEGigEGigEGigEGigEGigEGigEGigEGigEGigEGigE1GigEGigEGigE7VCMCUARTUARTPCIe#0FEUSBIPMB-LPCIe#1UARTPCIe#0FEUSBIPMB-LPCIe#1UARTPCIe#0FEUSBIPMB-L
UARTPCIe#0FEUSBIPMB-L
UARTPCIe#0FEUSBIPMB-L
UARTPCIe#0FEUSBIPMB-L
UARTPCIe#0FEUSBIPMB-L
UARTPCIe#0FEUSBIPMB-L
GigEGigE12GigE2MHz sync. outUSB# Nokia Siemens Networks 2012For
internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166
B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R
255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:MBB
Network EngineeringAgendamcRNC resource managementBCN HW
ArchitecturemcRNC Functional ArchitecturemcRNC ProtectionHW terms
and abbreviationsExternal physical connectivity incl. backplane
connection schemesTraffic FlowsmcRNC roadmapGeneral
introductionmcRNC Capacity limitsmcRNC dimensioning (incl. ANT_3G
user guidance)# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringAgendaHere is an example of what your agenda could look
like.
Network Element Module HW Parts
The size of the mcRNCnetwork element can bedescribed using
capacitysteps: either using S1 .. S7 or S1-A1 .. S7-B2For the BCN
modules thefollowing type of abbreviationscan be used: BCN-A, BCN-B
BCN-A1, BCN-B2
The letter d in the name can be used to indicate, that this
module includes hard disc (mandatory in two basic modules of the
network element), e can be used to indicate the extension role of
the module. E.g. : BCN-A1d, BCN-B2d BCN-A1e, BCN-B2eThese HW parts
abbreviations are visible also in CLI user interfaceBCNMB-A2 x
BMFU-ABAFU-ABAFI-A8 x BCNOC-A (BOC-A)2 x BCNAP-B
(BAFE-B)HDSAM-AmcRNC HW names and abbreviationsNaming hierarchy#
Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G
130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B
234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60
G 170 B 0Primary colors:MBB Network Engineering
S1S2S3S4S5S6S7Step 1 =2 modulesStep 2 =3 modulesStep 3 =4
modulesStep 4 =5 modulesStep 5 =6 modulesStep 6 =7 modulesStep 7 =8
modulesmcRNC HW names and abbreviationsCapacity step names used
ignoring module and processor type# Nokia Siemens Networks 2012For
internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166
B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R
255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:MBB
Network EngineeringSx-yz | | |_______ Processor type: | |1 =
Octeon+ (BCNOC-A add-in card) | |2 = OcteonII (BMPP2-A/B add-in
card) | | | |_________ BCN module type: |A = BCN-A |B = BCN-B |
|____________Capacity step number. Number of the modules in the
step = x+1mcRNC HW names and abbreviationsCapacity step names used
when BCN and processor type is indicated# Nokia Siemens Networks
2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R
163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G
0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary
colors:MBB Network EngineeringS1-A1S3-B2S5-A12
BCN-Amodules,Octeon+processors6
BCN-Amodules,Octeon+processorsSupported in RU30EP2 (mcRNC 2.0)
:Supported in RU40 (mcRNC 3.0) :S1-B22
BCN-Bmodules,OcteonIIprocessors4
BCN-Bmodules,OcteonIIprocessorsExamples:
mcRNC HW names and abbreviationsCapacity step names used when
BCN and processor type is indicated# Nokia Siemens Networks 2012For
internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166
B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R
255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:MBB
Network EngineeringBCN-ABCN-BBCN-A= current BCN module with six
10GigE portsBCN-B= modified BCN module with nine 10GigE portsThese
BCN module names include motherboard, mechanics, power supplies,
fans and air filter but NOT any add-in cardsmcRNC HW names and
abbreviationsBCN module names: BCN-A, BCN-B
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringBCN-xy |
|_______ Octeon type: | 1 = Octeon+ (BOC-A add-in card) | 2 =
OcteonII (BMPP2 add-in card) | |_________ BCN module type: A =
BCN-A B = BCN-BmcRNC HW names and abbreviationsBCN module names
used, if processor type needs to be shown
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringAgendamcRNC resource managementBCN HW ArchitecturemcRNC
Functional ArchitecturemcRNC ProtectionHW terms and
abbreviationsExternal physical connectivity incl. backplane
connection schemesTraffic FlowsmcRNC roadmapGeneral
introductionmcRNC Capacity limitsmcRNC dimensioning (incl. ANT_3G
user guidance)# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringAgendaHere is an example of what your agenda could look
like.
mcRNC Functional ArchitectureTerminologyFunctional unitA unit of
execution and deployment that relates to a node in the cluster.
Belongs to one of Control, User, Transport or Management planes.
Equivalent to a computer in the traditional sense. In a Linux based
node, the Functional unit has one-to-one mapping to the concept of
Recovery Unit. In a SE based node, the Functional unit has
one-to-one mapping to the SE based node itself.Processing UnitA
unit of deployment that spans one multi-core processor containing
one or more functional units. The functional units contained may
belong to any of the planes but are grouped together to ease
processing and communication.Interface card / Transport cardAn
add-in card containing one or more processing units (one in
mcRNC1.0) used to process network interface related functions and
transport layer services.Service cardAn add-in card containing one
or more processing units (one in mcRNC1.0) that are used for radio
layer services.BCN module 1 Box Controller Node hardware containing
8 add-in cards. Also referred to as the box. # Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network
Engineering10GigENetworkInterfaces10GigEHiGigBack-PlaneMGTlocalHW
Management1000Base-TLAN1 1 GigE(Element management)External
Interfaces part of Ethernet switchOct 1
Oct 3
Oct 2
PCIe HD FDLMPOct 4
Oct 5Oct 6
Oct 7
Oct 8
1GigENetworkInterfacesLAN2 1 GigE(Element management) Back-plain
part of Ethernet switchHW Management.Ethernet switch IPMB-L
VCMCUSBSERmcRNC Functional ArchitectureLogical View of BCN-A# Nokia
Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B
0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R
170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G
170 B 0Primary colors:MBB Network EngineeringNumber of 1GE and 10GE
ports modifiedNo dedicated Management portmcRNC Functional
ArchitectureLogical View of BCN-A
CFPUCSPUCSPUCSPUUSPUUSPUUSPUEIPUHDUPTU10GigENetworkInterfaces10GigEHiGigBack-PlaneMGTlocalHW
Management1000Base-TLAN1 1 GigE(Element management)External
Interfaces part of Ethernet switchOct 1CFPUOct 3CSPUOct 2CSPU PCIe
HD FDLMPOct 4CSPUOct 5USPUOct 6USPUOct 7USPUOct
8EIPU1GigENetworkInterfacesLAN2 1 GigE(Element management)
Back-plain part of Ethernet switchHW Management.Ethernet switch
IPMB-L VCMCUSBSERNote:Mapping of PUs is only an example# Nokia
Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B
0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R
170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G
170 B 0Primary colors:MBB Network EngineeringmcRNC Functional
ArchitectureHigh-level Functional Architecture
Service cards CFPU - Centralised Functions Processing UnitCSPU
Cell-Specific Processing UnitUSPU UE-Specific Processing
UnitInterface cards EIPU External Interface Processing Unit
Ethernet switches# Nokia Siemens Networks 2012For internal useR 255
G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringConceptually, the RNC (and hence mcRNC) can be thought
to comprise of 4 planes: Control Plane, User Plane, Transport Plane
and Management Plane.
User and Control Plane Functional UnitsCSCP Cell Specific
functions and services in Control PlaneUSCP UE Specific functions
and services in Control PlaneCFCP Centralized Functions and
services in Control PlaneCSUP Cell Specific functions and services
in User PlaneUSUP - UE Specific functions and services in User
Plane. This includes the dedicated and shared channel services
since they are relevant for a UE.
Transport Plane Functional UnitsSITP Signalling Transport
PlaneEITP External Interface functions in Transport Plane
Management Plane Functional UnitsOMU Operation and Maintenance
Unit for Management Plane
Processing Units are named as: CSPU, USPU, CFPU according to the
managed FUs.mcRNC Functional ArchitectureOverview# Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network EngineeringmcRNC Functional
ArchitectureCFPU-Centralized Functions Processing Unit
Contains OMU and CFCP Hosts critical services Redundancy : 2N
OMU Basic system maintenance functions CM, FM, PM, HW and SW
management Hosts RNW Database Plan management CFCP LCS services,
Iu-PC, SABP Centralized information maintenance Connectionless
protocols including paging# Nokia Siemens Networks 2012For internal
useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R
104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255
B 255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringmcRNC Functional Architecture USPU - UE Services
Processing Unit
Contains USCP and USUP Co-located user and control planes for UE
specific services Redundancy: SN+ (load shared) SCTP optional IP
used only by Flexi PF, not by RNC applications USUP Handles DCH,
HS-DSCH and E-DCH channels Hosts RTP,RTCP USCP Handles connection
oriented protocols Localized User plane resource manager # Nokia
Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B
0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R
170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G
170 B 0Primary colors:MBB Network EngineeringmcRNC Functional
ArchitectureCSPU Cell Specific Processing Unit
Contains CSCP and CSUP Co-located user and control planes for UE
specific services Redundancy: N+M SCTP optional IP used only by
Flexi PF, not by RNC applications CSUP Handles common channels and
BTSs Resources for a BTS allocated from the same unit. CSCP Handles
NBAP, RRC-c and RRC-s Admission control, load control and packet
scheduler# Nokia Siemens Networks 2012For internal useR 255 G 204 B
0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R
234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringmcRNC
Functional ArchitectureEIPU External Interface Processing Unit
Transport Network Layer unit Handles incoming packets Contains
SITP and EITP SITP Hosts the SIGTRAN stack and SCCP user level
distribution block EITP Hosts IP/IPSec/UDP and GTPu stack and GTPu
level distribution Provides QoS control, traffic shaping and
scheduling functions Performs IPSec encryption and decryption #
Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G
130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B
234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60
G 170 B 0Primary colors:MBB Network EngineeringAgendamcRNC resource
managementBCN HW ArchitecturemcRNC Functional ArchitecturemcRNC
ProtectionHW terms and abbreviationsExternal physical connectivity
incl. backplane connection schemesTraffic FlowsmcRNC roadmapGeneral
introductionmcRNC Capacity limitsmcRNC dimensioning (incl. ANT_3G
user guidance)# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringAgendaHere is an example of what your agenda could look
like.
mcRNC External physical connectivityBCN-A External physical
interfaces
Iu, Iur, Iub interfaces: 16x 1000BASE-T/SX/LX, SFP (RJ-45 or
LC-type)O&M connectivity: 1x 1000BASE-T/SX/LX, SFP (RJ-45 or
LC-type)2nd SFP reservered for future useLocal HW maintenance: 1x
1000BASE-T, RJ-45This interface must not be connected to network
(allows low level hardware debugging)!RNC internal backplane: 6x
10GBASE-SR/LR, SFP+ (LC-type connector)
6x SFP+(BCN interconnect)16x SFP(UTRAN interfaces)SFP(EM, DCN)1x
RJ-45(HW maintenance)2x USB(SW download)Debugginginterfaces2x
RJ-45(unused)2x RJ-45(ext. alarm input)1 3 5 7 9 11 13 15 17 19 212
4 6 8 10 12 14 16 18 20 22# Nokia Siemens Networks 2012For internal
useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R
104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255
B 255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
Engineering4U highEasier Temperature management. AMC extension
slots possible.Number and grouping of external interfaces6x10GE
ports in one group. Used as external 1/10GE ports or as
interconnection ports between nodes.16x1GE ports in one group. Used
as external 1GE portsNo dedicated 1GE port for network
management.AMC bays in vertical position.
mcRNC External physical connectivityRecommended site solution
incl. backplane connectivity S1-A1
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringmcRNC
External physical connectivityRecommended site solution incl.
backplane connectivity S5-A1
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringmcRNC
External physical connectivityBCN-B External physical
interfaces
10GEexternal port# Nokia Siemens Networks 2012For internal useR
255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G
113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
Engineering4U highEasier Temperature management. AMC extension
slots possible.Number and grouping of external interfaces6x10GE
ports in one group. Used as external 1/10GE ports or as
interconnection ports between nodes.16x1GE ports in one group. Used
as external 1GE portsNo dedicated 1GE port for network
management.AMC bays in vertical position.
AgendamcRNC resource managementBCN HW ArchitecturemcRNC
Functional ArchitecturemcRNC ProtectionHW terms and
abbreviationsExternal physical connectivity incl. backplane
connection schemesTraffic FlowsmcRNC roadmapGeneral
introductionmcRNC Capacity limitsmcRNC dimensioning (incl. ANT_3G
user guidance)# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringAgendaHere is an example of what your agenda could look
like.
mcRNC Traffic FlowsSRB setup on DCH Data Path
Eth SwitchEIPUUSPUNPGESFUMXUDMCUMXUSFUMXUICSUmcRNCIPA# Nokia
Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B
0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R
170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G
170 B 0Primary colors:MBB Network EngineeringmcRNC Traffic Flows
SRB setup on FACH Data Path
Eth SwitchEIPUCSPUNPGESFUMXUDMCUMXUSFUMXUICSUUSPUmcRNCIPA# Nokia
Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B
0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R
170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G
170 B 0Primary colors:MBB Network EngineeringmcRNC Traffic Flows CS
Call on DCH Data Path
mcRNCIPAEth SwitchEIPUEth
SwitchUSPUNPGESFUMXUDMCUDSPMXUSFUNPGEEIPU# Nokia Siemens Networks
2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R
163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G
0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary
colors:MBB Network EngineeringmcRNC Traffic Flows PS call setup on
DCH Data Path
mcRNCIPAEth SwitchEIPUEth
SwitchUSPUNPGESFUMXUDMPGDSPMXUSFUMXUNPGEEIPU# Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network EngineeringmcRNC Traffic Flows PS setup
on FACH/RACH data path
mcRNCIPAEth SwitchCSPUEth
SwitchUSPUNPGESFUMXUDMCUDSPMXUSFUMXUDMCUDSPMXUSFUNPGEEIPUEIPU#
Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G
130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B
234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60
G 170 B 0Primary colors:MBB Network EngineeringThe Iu resource is
same as the PS on DCH, just without the Iub resource setup which
already done when common channel setup.The Iu and Iub connect is
done by application itself.
mcRNC Traffic Flows PS on HSPA data path
mcRNCIPAEth SwitchEIPUEth
SwitchUSPUNPGESFUMXUDMPGDSPMXUSFUMXUNPGEEIPU# Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network EngineeringThe Iu resource is same as
the PS on DCH, just there are two Iub resources dedicated for
uplink and downlink.From call management point of view, 2 Iub leg
are some especially the MAC protocol are different and the handover
concept is different.
mcRNC Traffic Flows Soft handover intra-RNC
mcRNCIPAEth SwitchEIPUEth
SwitchUSPUNPGESFUMXUDMPGDSPMXUSFUMXUNPGEEIPU# Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network EngineeringAgendamcRNC resource
managementBCN HW ArchitecturemcRNC Functional ArchitecturemcRNC
ProtectionHW terms and abbreviationsExternal physical connectivity
incl. backplane connection schemesTraffic FlowsmcRNC roadmapGeneral
introductionmcRNC Capacity limitsmcRNC dimensioning (incl. ANT_3G
user guidance)# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringAgendaHere is an example of what your agenda could look
like.
mcRNC Resource ManagementDecoupled layers and servicesTransport
layer decoupled from the Radio LayerResourced from different
cardsEnables flexible and independent adaptation of Transport
requirementsEnables application of 1+1 redundancy for TNLCell
services and UE services in RNL decoupledResourced from different
cardsEnables specific addressing of CSPU redundancy (N+M)Control
Plane and User Plane in RNL co-locatedResourced from the same
cardEnables flexible resource allocation between CP and UPEnables
local resource management for UP resources
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringmcRNC
Resource Management Capacity allocationRNC can be viewed as a pool
of processing resourcesCoordinated capacity allocation from the
pool for various servicesCapacity allocation among Processing
UnitsBased on Traffic profileNo. of CSPUs : Depends on the number
of W-BTSs to be handledNo. of USPUs : Depends on the number of UEs
to be handledNo. of EIPUs : Depends on the traffic capacity and
needed servicesQoS, IPSecStatically allocated at commissioning
timeModification possibleManual, through service personnel
onlyRequires restart of units that have to change role
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringProvided
as inputs to RDTBalancing of units shall take these as high level
inputsActual number of units will vary based on balancingmcRNC
Resource Management Capacity allocationCapacity allocation within
Processing UnitResource sharing between co-located CP and UPBased
on the needs of traffic profileDifferent for CSPU and
USPUStatically configured at commissioning timeModification
possibleManual, through service personnel onlyRequires restart of
the system.
Automatic resource optimization under study# Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network EngineeringmcRNC Resource
ManagementWhat does it mean ?Resource Management - Load balancing
and distribution mechanisms:Different principles:Static
allocationRound RobinWeighted Round Robin
Different Planes:Transport PlaneUser PlaneControl PlaneDifferent
Service groups:Cell-specific servicesUE-specific servicesDifferent
layers:Transport Network LayerRadio Layer 2 Radio Layer 3# Nokia
Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B
0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R
170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G
170 B 0Primary colors:MBB Network EngineeringmcRNC Resource
ManagementLoad balancing and distribution in Transport Network
Layer
Iu / Iur interface Control Plane (SITP)SCTP association set is
held between RNC and each CN elementEach SCTP association binds to
a certain CP service IP address (preferably on different EIPU
units)For a new request , the SCTP association is selected based on
policy (e.g. Round Robin)The distribution of the Iu (and Iur)
signaling messages to the application protocol handlers (RANAP and
RNSAP) in service cards is handled by SITP (at SCCP level)
connectionless messages and connection oriented messages that do
not have a local reference allocated -> distributed to the least
loaded service card. connection oriented messages (UE specific)
having a valid local reference->forwarded to the relevant
service card
1212# Nokia Siemens Networks 2012For internal useR 255 G 204 B
0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R
234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringmcRNC
Resource ManagementLoad balancing and distribution in Transport
Network Layer
Iu / Iur interface User Plane (EITP)The USUP unit that handles a
certain traffic flow to a UE is determined by the RNC. The EITP to
be used for the traffic flow is selected by the TRM The address of
the User Plane entity that shall handle the traffic is provided to
the EITP.
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringThe User
Plane addresses used in the RNC are signaled and hence the USUP
unit that handles a certain traffic flow to a UE is determined by
the RNC. During the assignment of resources for user plane traffic,
the EITP to be used for the traffic flow is selected by the
transport resource manager and resources are reserved to handle the
Iu connection. The address of the User Plane entity that shall
handle the traffic is provided to the EITP. The GTP TEID is mapped
to the FaStDist address (DMX in mcRNC1.0) of the UP entity.It is
worth noting here that the IP and SCTP layers are terminated in the
SITP and the UDP in the EITP in the interface card. The SCCP user
adaptor (SAGPRO) communicates with the signalling application
protocol programs (RANAP and RNSAP) using the internal DMX based
messaging network. The Traffic Forwarder (TRF) communicates with
the user plane entities using the FaStDist protocol.
59mcRNC Resource ManagementLoad balancing and distribution in
Transport Network Layer
Iub interface Control Plane (SITP)No dynamic load balancing for
NBAP signalling messages. The CSCP units to handle BTS and cells
are selected using a policy e.g.round robin as part of RNW plan
download and configuration in RNC. The NBAP load distributor in
SITP only dispatches the signaling messages based on IP/SCTP level
information.
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringThe
centralized dispatching only serves to help in applying principles
of availability and redundancy without affecting the BTSs involved,
when possible.mcRNC Resource ManagementLoad balancing and
distribution in Transport Network Layer
Iub interface User Plane (EITP)EITP to be used for the Iub
traffic flow is selected by the TRM The address of the User Plane
entity that shall handle the traffic is provided to both the EITP.
The IP address and UDP port in EITP is mapped to the FaStDist
address of the user plane for the purpose of forwarding.
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringDuring
the assignment of resources for user plane traffic, the EITP to be
used for the Iub traffic flow is selected by the transport resource
manager and resources are reserved to handle the Iub connection.
The address of the User Plane entity that shall handle the traffic
is provided to both the EITP. The IP address and UDP port in EITP
is mapped to the FaStDist address of the user plane for the purpose
of forwarding.
The centralized dispatching only serves to help in applying
principles of availability and redundancy without affecting the
BTSs involved, when possible.mcRNC Resource ManagementCell Services
and UE Services - overviewCell ServicesAssignment of W-BTS to CSPUs
from Centralized unit at runtimeRound robin used, provision for
load based optimizationCommon channels for W-BTS handled in the
same CSPUCP UP co-location enables local resource management
UE ServicesAssignment of a call to the USPUs from CSPUsRound
robin usedAny USPU can handle calls from any W-BTSUP resources for
the call handled in the same boardCP UP co-location enables local
resource managementEligible set of USPUs determined based on
loadData pushed to the CSPUs from centralized resource manager
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringmcRNC
Resource ManagementCell Services CSPU selectionA BTS object is
added to the RNW DBThe BTS handler chooses the next available CSCP
by round robinThe eligible list is maintained based on existing
loadA unit in overload mode can ask to be made ineligibleThe CSCP
uses its own CSUP in same processor for user plane resourcesAll
resources needed for a BTS provided from the same processing unit
The Transport Resource Manager selects an EIPU Configures it with
the address and port information for the newly added BTS and the
address of the selected CSCPThe distribution table in EIPU is
updated.# Nokia Siemens Networks 2012For internal useR 255 G 204 B
0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R
234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringmcRNC
Resource ManagementUE Services - DefinitionsCell HomeAll Cell
Specific User Bearers (SRB / RAB) of particular type are located
into a designated Processing Unit (not Cell Services)
HSPA servicesA Processing Unit, where HSPA RAB services
(concentration of Bearers of certain cell) are allocatedHS Cell
FACHA Processing Unit, where HS CELL FACH Cell Services are
allocatedUE HomeA Processing Unit, where SRB of the particular UE
is located (It is preferred to keep the Bearers of a UE in its
UE-Home PU - in order to avoid cross PU signalling specific to the
UE.
Native Bearer in the Cell-HomeUser Bearer of a particular type
allocated in the Cell-HomeVisitor Bearer in the Cell-HomeUser
Bearer of a particular type allocated in the non Cell-Home PU#
Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G
130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B
234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60
G 170 B 0Primary colors:MBB Network EngineeringmcRNC Resource
ManagementUE Services - UE-home and Cell-Home concept
Cell 1 (C1) Capable of handling DCH + HSDPA RABsCell 2 (C2)
Capable of handling DCH + HSPA RABsCell 3 (C3) Capable of handling
HS Cell-FACH Service + DCH + HSDPA RABsUEsCellsPUsCell-Home for
HSDPA RABs of C3Cell-Home for HSDPA RABs of C1 and C2Cell-Home for
HS Cell-FACH service of C3# Nokia Siemens Networks 2012For internal
useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R
104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255
B 255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringmcRNC Resource ManagementUE-home and Cell-Home
concept
Connected to C1, having HSDPA RAB resource in USPU1 Native
Bearer for USPU1Connected to C2, having HSDPA RAB resource in USPU3
Visitor Bearer for USPU3Connected to C3, having HS Cell-FACH SL in
USPU2 Native Bearer for USPU2UEsCellsPUsCell-Home for HSDPA RABs of
C3Cell-Home for HSDPA RABs of C1 and C2Cell-Home for HS Cell-FACH
service of C3# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringmcRNC Resource ManagementUE Services USPU
selectionProcessing resource allocation for UE services dynamic
allocation, A call from a UE attached to any cell can be handled in
any of the USPUs.
Different policies defined for the distribution of SRBs and data
bearers to USPUs:When the SRB for a UE needs to be allocated, the
least loaded USPU in terms of both CP and UP load is selected and
the CP and UP resources are co-located in the unit. This USPU is
referred to as the UE home.When a radio bearer needs to be assigned
for a UE in CELL_DCH state, resource allocation from UE home is
checked and if not available, another unit with a lower unit load
is selected.When the UEs use shared channels, it is beneficial to
allocate resources for them in the same functional unit, so that
common limits and constraints can be enforced with ease. This
results in the definition of a Cell Home the USUP unit that handles
the HS bearers for the UEs in a given cell. # Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network EngineeringmcRNC Resource Management
Deployment of resource managers
Local resource management (LRM) for UP resources
(USPU/CSPU)mediates the allocation of resources in the USUP When
resources are not available in the local USUP, the LRM contacts the
CRM to get an alternate USUP for allocating the resourcesPer-call
resources managed locally in the USPUsNo need to use centralized
resource manager for each call
Centralized resource management (CRM) for exceptions (in
CFPU)Used in overload, fault situations etc.Distributes the load
information of USPUs to the CSCP which then, makes use of the data
in selecting the USPU unitWhen receives an indication from LRM
about resource unavailability, selects alternate handler for that
callBoard removed from the eligible list CS services dont assign
further calls to the overloaded boardBoard added to the eligible
list once load is below lower threshold# Nokia Siemens Networks
2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R
163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G
0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary
colors:MBB Network EngineeringLRMFast decisions on resource
allocation
mcRNC Resource ManagementService poolsNo.PoolPUU-Plane
ServicesManaged Resources1CCH (C)CSPURel 99 cellservicesRel 99 cell
specific:RLC/MAC-c RACH/FACH/BCCH/PCH2Non-CCH (nC)USPUUser-
specificservicesHS cell servicesUser Specific: RLC/OLPC/ Cipher
MAC-d/-HS/-es/-is MDC FP DCH/HS-DSCH/E-DCHHS Cell Specific:
MAC-c/-sh FP E-DCH/HS-DSCH# Nokia Siemens Networks 2012For internal
useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R
104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255
B 255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringThe U-Plane Services shall be grouped into Two
Statically separated Pools as
69mcRNC Resource ManagementNon-CCH pool in
USPUNo.PoolSubsectionsAllocation1Non-CCH (nC)DCH (SRB,AMR,
Rel99)HSCF (HS Cell_FACH)GBR service - X% allocation forDCH, nGBR
HSCF Cell/RABServices- Deterministic servicesHSPA (HSDPA,
HSUPA)nGBR service - HS - Y% allocationfor services
Non-deterministic ServicesExcess reservation0%# Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network EngineeringThe non-CCH pool can be
further logically divided into sub-pools for the different USUP
Services offered.
The allocations above are used by the Resource Manager to make
the decisions suchas UP Admission Control and Service
Prioritization in order to balance the load on differentPUs.
70Local resource management (LRM) functionality in USCP/CSCP
performs user plane admission control functionalities with
different policies for:Deterministic Services (DS) or Guaranteed
Bit Rate Service (GBRS), for which the cost of a U-Plane Service
can be can be evaluated up-front at the service admission; managed
by Capacity Counter mechanismLRM monitors the Fill Level of the
services with deterministic Load against the X% LimitWhen a
Deterministic Service is admitted, LRM shall increment the
appropriate Traffic Mix Counter till the Limit X% is reachedIf the
X% is reached, the LRM shall not admit the call by itself, but
escalate it to the CRM. CRM shall try to find a Processing Unit
with deterministic Load less than the X% Limit
non-Deterministic Services (nDS) - The Best Effort class
services and the HSPA services with various range of QoS during the
call that cannot be modeled as the deterministic services.
Admission is dynamically evaluated by measuring the PU Load to
provide the Best Effort Service.mcRNC resource managementAdmission
control# Nokia Siemens Networks 2012For internal useR 255 G 204 B
0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R
234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringmcRNC
Resource ManagementcRNC vs mcRNC - comparisonClassic
RNCMulticontroller RNCC-plane functionalities reside on ICSU and
RSMU functional unit.
C-plane functionalities are divided on the basis of cell
specific and UE specific functionalities and reside on different
functional units (CSCP/USCP) Centralized CP functionalities reside
on RSMU
Centralized CP functionalities reside on CFPU
C-plane FU and U-plane FU are deployed on different Processing
units (ICSU/DMCU)
C-plane and U-plane Fus are deployed on same processing
unit:CSCP and CSUP FUs on CSPU PU USCP and USUP FUs on USPU PU#
Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G
130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B
234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60
G 170 B 0Primary colors:MBB Network EngineeringAgendamcRNC resource
managementBCN HW ArchitecturemcRNC Functional ArchitecturemcRNC
ProtectionHW terms and abbreviationsExternal physical connectivity
incl. backplane connection schemesTraffic FlowsmcRNC roadmapGeneral
introductionmcRNC Capacity limitsmcRNC dimensioning (incl. ANT_3G
user guidance)# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringAgendaHere is an example of what your agenda could look
like.
mcRNC ProtectionIntroduction In mcRNC protection against
failures is provided by logical functional units redundancy.
Then compared to RNC-2600 theres no hardware protection with
hot-standby mechanism, except for some hw units as hard disk, power
supplies and fans.
Using this FU protection approach, its possible to manage single
points of failures, without impacts on the service, with the
appropriate traffic engineering.
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringmcRNC
Protection Protection MechanismsDepending on the Functional Unit
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.# Nokia Siemens Networks
2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R
163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G
0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary
colors:MBB Network EngineeringmcRNC ProtectionRecovery Group and
Recovery UnitResiliency and high availability is achieved with
following concepts:Recovery Unit (RU) Functional Unit participating
in the protection group.Recovery Group (RG) Containing Active and
Protecting RUs.
RG types configurable in mcRNC are :QNUP which can terminate
User Plane connections of both Iub and Iu.QNIUB which can terminate
Control Plane connection for Iub only (Iu Control Plane protection
is managed with SCTP Multihoming which terminates directly in
EIPU).QNOMU which terminates O&M connections and is bound to
CFPU nodes.QNCFCP which terminates Service Area Broadcast service
and is also bounded to CFPU.
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringmcRNC
ProtectionServices ProtectionActive / Standby Recovery Unit (RU),
Application IP terminationEgress: Traffic generated in the EIPUs is
forwarded with ECMP routing to both connected site routersIngress:
Incoming traffic from one router can access the service termination
on both BCN modules. Primary route points to the EIPU that is
primarily running the service. EIPU-0
EIPU-2
EIPU-1
EIPU-3
Application IP#1ACTApplication IP#1St-ByModule 2Module 1
Application IP#2St-ByApplication IP#2ACT10.0.0.30/30
(SFP16)10.0.0.2/30 (SFP7)10.0.0.18/30
(SFP8)10.0.0.1/3010.0.0.17/3010.0.0.9/3010.0.0.29/3010.0.0.10/30
(SFP7)10.0.0.6/30 (SFP15)10.0.0.22/30 (SFP16)10.0.0.26/30
(SFP8)10.0.0.14/30
(SFP15)10.0.0.5/3010.0.0.21/3010.0.0.13/3010.0.0.25/30Recovery
Group (RG)# Nokia Siemens Networks 2012For internal useR 255 G 204
B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R
234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringmcRNC
ProtectionExternal Links Protection mechanismProtection of the
mcRNC's external network connectivity is a very crucial aspect for
the customer, as a failure of e.g. a single Iu link may bring the
whole RAN area down, resulting in huge loss of revenues and bad
service experience.
Different protection mechanisms are available in mcRNC for
external connectivity:
EIPU protection
Ethernet Link protection
SCTP mutihoming# Nokia Siemens Networks 2012For internal useR
255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G
113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringSeveral means shall be implemented to protect the
network access. Mainly the following failure cases are
covered:Failure of certain SW or HW functionality in mcRNC (can be
a single SW process, but also a complete BCN), Failure of an
Ethernet link Failure of an mcRNC site router Failures in the
transport network Packet forwarding failures between mcRNC and the
transport network (transport link between mcRNC and network
physically operational, but still (e.g. due to router malfunction)
packets are not forwarded -> traffic blackholing)
mcRNC ProtectionBasic IP Layer RoutingTraffic is forwarded to
Application address using Primary routes and in case of failure,
Secondary routes are available as backup pointing to Stand By
Application address. EIPU-0
EIPU-2
EIPU-1
EIPU-3
Application IP#1ACT10.0.0.1 /28Application IP#1St-By10.0.0.1
/28BCN#1
Application IP#2St-By10.1.0.1 /28Application IP#2ACT10.1.0.1
/2810.0.0.30/30 (SFP16)10.0.0.2/30 (SFP7)10.0.0.18/30
(SFP8)10.0.0.1/3010.0.0.17/3010.0.0.9/3010.0.0.29/3010.0.0.10/30
(SFP7)10.0.0.6/30 (SFP15)10.0.0.22/30 (SFP16)10.0.0.26/30
(SFP8)10.0.0.14/30
(SFP15)10.0.0.5/3010.0.0.21/3010.0.0.13/3010.0.0.25/30BCN#210GE
BackplanePrimary Route (from Switch-1)Secondary Route (from
Switch-2)BackupRoute (from Switch-1)BackupRoute (from Switch-2)#
Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G
130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B
234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60
G 170 B 0Primary colors:MBB Network EngineeringmcRNC ProtectionEIPU
ProtectionApplications affected by the failure are moved to a
redundant unit, traffic flow continues there based on existing
routing definitions - no dynamic changes are required.Primary Route
(from Switch-1)Secondary Route (from Switch-2)BackupRoute (from
Switch-1)BackupRoute (from Switch-2) EIPU-0
EIPU-2
EIPU-1
EIPU-3
Application IP#1ACT10.0.0.1 /28Application IP#1St-By10.0.0.1
/28BCN#1
Application IP#2St-By10.1.0.1 /28Application IP#2ACT10.1.0.1
/2810.0.0.30/30 (SFP16)10.0.0.2/30 (SFP7)10.0.0.18/30
(SFP8)10.0.0.1/3010.0.0.17/3010.0.0.9/3010.0.0.29/3010.0.0.10/30
(SFP7)10.0.0.6/30 (SFP15)10.0.0.22/30 (SFP16)10.0.0.26/30
(SFP8)10.0.0.14/30
(SFP15)10.0.0.5/3010.0.0.21/3010.0.0.13/3010.0.0.25/30BCN#210GE
Backplane# Nokia Siemens Networks 2012For internal useR 255 G 204 B
0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R
234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network Engineering1. mcRNC
internal failuresIn case of SW or HW related failures in mcRNC,
sufficient redundancy needs to be provided by the system, e.g. by
relocating affected services to other (non-affected) parts of the
system.Obviously, mcRNC internal protective mechanisms should not
have an impact on the external network connectivity - in fact the
transport network should not even notice such events. Consequently,
a fundamental requirement of the network connectivity solution is
that each protected service in the mcRNC (regardless of the module
that it is physically running in) is able to use the network via
redundant interfaces. Furthermore, in case a protective action
(e.g. a switchover to a redundant processor) is really performed,
impacts on the transport network shall be minimized. Applications
affected by the failure are moved to a redundant unit, traffic flow
continues there based on existing routing definitions - no dynamic
changes are required.
mcRNC ProtectionEIPU Application FailureThe scenario looks
slightly different in case just a single application fails within
one EIPU Primary Route (from Switch-1)Secondary Route (from
Switch-2)BackupRoute (from Switch-1)BackupRoute (from Switch-2)
EIPU-0
EIPU-2
EIPU-1
EIPU-3
Application IP#1ACT10.0.0.1 /28Application IP#1St-By10.0.0.1
/28BCN#1
Application IP#2St-By10.1.0.1 /28Application IP#2ACT10.1.0.1
/2810.0.0.30/30 (SFP16)10.0.0.2/30 (SFP7)10.0.0.18/30
(SFP8)10.0.0.1/3010.0.0.17/3010.0.0.9/3010.0.0.29/3010.0.0.10/30
(SFP7)10.0.0.6/30 (SFP15)10.0.0.22/30 (SFP16)10.0.0.26/30
(SFP8)10.0.0.14/30
(SFP15)10.0.0.5/3010.0.0.21/3010.0.0.13/3010.0.0.25/30BCN#210GE
Backplane# Nokia Siemens Networks 2012For internal useR 255 G 204 B
0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R
234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringIn this
case, traffic will still be forwarded from site switches towards
EIPU #1 - but it needs to be forwarded internally as the
application was moved to the redundant unit. In RNC egress
direction existing route definitions in EIPU #1 are used.mcRNC
provides the following mechanisms to supervise Ethernet link
status:Physical link status, i.e. physical carrier status (e.g.
"lights on" in optical case),Remote fault status indication (i.e.
link status bit as defined in IEEE802.3-2005 clause 28 and clause
37)
In RU30 RAN2254 Ethernet Link OAM in RNC is introduced, which
can be used for Ethernet link faults discovery based on IEEE802.3
clause 57.
It's also possible to use Link Aggregation Group functionality
(IEEE802.3ad) grouping up to 8 Ethernet ports.
mcRNC ProtectionEthernet Link Protection# Nokia Siemens Networks
2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R
163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G
0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary
colors:MBB Network EngineeringmcRNC ProtectionEthernet link
protectionIn case of a recognized failure, mcRNC provides routing
of the affected traffic via redundant IP routes.Primary Route (from
Switch-1)Secondary Route (from Switch-2)BackupRoute (from
Switch-1)BackupRoute (from Switch-2) EIPU-0
EIPU-2
EIPU-1
EIPU-3
Application IP#1ACT10.0.0.1 /28Application IP#1St-By10.0.0.1
/28BCN#1
Application IP#2St-By10.1.0.1 /28Application IP#2ACT10.1.0.1
/2810.0.0.30/30 (SFP16)10.0.0.2/30 (SFP7)10.0.0.18/30
(SFP8)10.0.0.1/3010.0.0.17/3010.0.0.9/3010.0.0.29/3010.0.0.10/30
(SFP7)10.0.0.6/30 (SFP15)10.0.0.22/30 (SFP16)10.0.0.26/30
(SFP8)10.0.0.14/30
(SFP15)10.0.0.5/3010.0.0.21/3010.0.0.13/3010.0.0.25/30BCN#210GE
Backplane# Nokia Siemens Networks 2012For internal useR 255 G 204 B
0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R
234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network Engineeringif first
gateway becomes unavailable (e.g. total loss of connectivity for
the IP interface or lack of external routes induced by dynamic
routing protocol - OSPF), mcRNC will route affected traffic via the
other interface
mcRNC ProtectionmcRNC Site Router redundancyIn case of Site
Router failure, only the other available Primary Route will be used
to forward traffic.Primary Route (from Switch-1)Secondary Route
(from Switch-2)BackupRoute (from Switch-1)BackupRoute (from
Switch-2) EIPU-0
EIPU-2
EIPU-1
EIPU-3
Application IP#1ACT10.0.0.1 /28Application IP#1St-By10.0.0.1
/28BCN#1
Application IP#2St-By10.1.0.1 /28Application IP#2ACT10.1.0.1
/2810.0.0.30/30 (SFP16)10.0.0.2/30 (SFP7)10.0.0.18/30
(SFP8)10.0.0.1/3010.0.0.17/3010.0.0.9/3010.0.0.29/3010.0.0.10/30
(SFP7)10.0.0.6/30 (SFP15)10.0.0.22/30 (SFP16)10.0.0.26/30
(SFP8)10.0.0.14/30
(SFP15)10.0.0.5/3010.0.0.21/3010.0.0.13/3010.0.0.25/30BCN#210GE
Backplane# Nokia Siemens Networks 2012For internal useR 255 G 204 B
0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R
234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringIn
mcRNC, redundancy at SCTP layer is provided by multi-homing. It
enables network level redundancy.Similar to cRNC but here SCTP
connections are terminated in EIPU unit.
mcRNC ProtectionSCTP Multi-homing in mcRNC# Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network EngineeringIn mcRNC, redundancy at SCTP
layer is provided by multi-homing. It enables network level
redundancy (separate routes through network possible). Redundancy
for O&M connection is implemented through Active-Stby OMU
configuration on different modules.In case of failure of one of the
elements involved in O&M traffic forwarding, network
configuration should be able to forward traffic on a backup
path.
mcRNC ProtectionmcRNC O&M Connection Protection# Nokia
Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B
0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R
170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G
170 B 0Primary colors:MBB Network EngineeringmcRNC capacity limitsR
255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G
113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:# Nokia Siemens
Networks 2012For internal useMBB Network Engineering# Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network EngineeringAgendamcRNC resource
managementBCN HW ArchitecturemcRNC Functional ArchitecturemcRNC
ProtectionHW terms and abbreviationsExternal physical connectivity
incl. backplane connection schemesTraffic FlowsmcRNC roadmapGeneral
introductionmcRNC Capacity limitsmcRNC dimensioning (incl. ANT_3G
user guidance)# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringAgendaHere is an example of what your agenda could look
like.
mcRNC capacity stepsS1-A1S3-B2S5-A12
BCN-Amodules,Octeon+processors6
BCN-Amodules,Octeon+processorsSupported in RU30EP2 (mcRNC 2.0)
:Supported in RU40 (mcRNC 3.0) :S1-B22
BCN-Bmodules,OcteonIIprocessors4
BCN-Bmodules,OcteonIIprocessors
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringmcRNC PU
and FU cores amount Recommended amounts per mcRNC moduleCapacity
stepS1S5TotalCapacity stepS1S5Total#
BCN123456CFPU1100002CSPU22212110USPU33454524EIPU22222212Capacity
stepS1S3Total# BCN1234CFPU11002CSPU22127USPU336517EIPU22116Total
888832With Octeon+ HWWith Octeon II HWFunctional
unitsCFPUCSPUUSPUEIPUOMU1000EITP0006SITP0006CFCP11000CSCP0600USCP0050USUP0070CSUP0600Functional
unitsCFPUCSPUUSPUEIPUOMU2000EITP00016SITP00016CFCP30000CSCP01600USCP00140USUP00180CSUP01600#
Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G
130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B
234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60
G 170 B 0Primary colors:MBB Network EngineeringmcRNC capacity
limits RU30 EP2 (mcRNC2.0)Pre-defined configurations (Octeon+
HW)mcRNC capacity stepS1-A1 S5 A1CS BHCA340 0001 380 000PS BHCA485
0001942 000Smartphone BHCA327 0001310 000max Iub DL/UL throughput
[Mbps]910/3803660/1530AMR/CS vice over HSPA capacity [Erlangs]8500
/ 600034500 / 24500BTS connectivity400550Carrier
connectivity12003110RRC connected state UEs195000780000Laptop HSPA
active users per RNC1100044000Iu-ps HSDPA net bit rate
[Mbit/s]8193294Iu-ps HSUPA net bit rate [Mbit/s]246988# Nokia
Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B
0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R
170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G
170 B 0Primary colors:MBB Network EngineeringmcRNC capacity limits
RU40 (mcRNC3.0) Pre-defined configurations (Octeon+ HW)mcRNC
capacity stepS1-A1 S5 A1CS BHCA340 0001 380 000 PS BHCA485 0001 942
000Smartphone BHCA327 000 1 310 000 max Iub DL/UL throughput
[Mbps]910 / 3803660 /1530AMR/CS voice over HSPA capacity
[Erlangs]8500 34500 BTS connectivity4701037Carrier
connectivity14103110RRC connected state UEs195 000 780 000 Laptop
HSPA active users per RNC13 40053 300IuPS HSDPA net bit rate
[Mbit/s]8193294IuPS HSUPA net bit rate [Mbit/s]204984# Nokia
Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B
0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R
170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G
170 B 0Primary colors:MBB Network EngineeringmcRNC capacity limits
- RU40 (mcRNC3.0) Pre-defined configurations (Octeon II HW)mcRNC
capacity stepS1-B2S3-B2CS BHCA760 0002 140 000PS BHCA1 400 0003 500
000Smartphone BHCA1 170 0002 940 000max Iub DL/UL throughput
[Mbps]1850 / 7905260/2260AMR/CS voice over HSPA capacity
[Erlangs]1900053500BTS connectivity5201320Carrier
connectivity26006600RRC connected state UEs352 0001 000 000Laptop
HSPA active users per RNC20800 58900IuPS HSDPA net bit rate
[Mbit/s]16654734IuPS HSUPA net bit rate [Mbit/s]5001420# Nokia
Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B
0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R
170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G
170 B 0Primary colors:MBB Network EngineeringAgendamcRNC resource
managementBCN HW ArchitecturemcRNC Functional ArchitecturemcRNC
ProtectionHW terms and abbreviationsExternal physical connectivity
incl. backplane connection schemesTraffic FlowsmcRNC roadmapGeneral
introductionmcRNC Capacity limitsmcRNC dimensioning (incl. RAN DIM
user guidance)# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringAgendaHere is an example of what your agenda could look
like.
mcRNC Dimensioning ProcessOverviewFor each RNC type and/or
capacity stepCheck User Plane LimitationsCheck BTS Connectivity
LimitationsCheck Physical InterfaceConnectivity LimitationsSelect
the solution with thehighest number of RNCsNumber and type of RNCs
neededInputTraffic, NodeBs, Carriers, Iub, Iur,IuCS, IuPSCheck
Control PlaneLimitationsOutputs:Number of RNCs considering each
checkBottleneck in most networks due to Smartphones !Rarely a
limiting factor (normally a couple hundreds cells per RNC# Nokia
Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B
0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R
170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G
170 B 0Primary colors:MBB Network Engineering
RNC dimensioning- RNC selection in RAN DimDept. / Author /
DateRNC dimensioning algorithm selects the most optimal RNC
combination based on dimensioning inputs and selected RNCs For
expansion projects, define existing RNCs in the network When
Upgrade if possible is marked, then tool will automatically upgrade
the RNC to the maximum possible conf. Selection of RNC candidates,
which will be considered during dimensioning If Initial RNC
Configuration is not enough to handle all the traffic, then RNCs
selected here are considered to be added# Nokia Siemens Networks
2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R
163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G
0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary
colors:MBB Network EngineeringUser PlanemcRNC dimensioning (incl.
RAN DIM user guidance)R 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R
163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G
0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary
colors:# Nokia Siemens Networks 2012For internal useMBB Network
Engineering# Nokia Siemens Networks 2012For internal useR 255 G 204
B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R
234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringmcRNC
dimensioning based on User Plane
Total user traffic in the areaCalculate AMR LoadCalculate CS
Data loadCalculate NRT Data LoadSelect the highest result-Number of
RNCs neededApply traffic mix ruleCalculate HSDPALoadAdd protocol
OHCross-check PS UL traffic amountCalculate HSUPALoadAdd SHO and
protocol OHApply user amount formulaAdd SHO and protocol OHAdd SHO
and protocol OH# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringAMR limits are expressed explicitly in Erlangs for
RNCSHO is assumed to be taken already into account in the limit so
SHO is not added.Calculation example:4 000 000 subscribers with 25
mErl AMR
AMR Load = 4 000 000 * 25/1000 Erl = 100000 Erl
RNC dimensioning- User Plane
Calculate AMR LoadAMR Traffic Demand definition Service
definition
Subscriber amount definitionThe same calculation applies for CS
voice over HSPA AMR Traffic# Nokia Siemens Networks 2012For
internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166
B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R
255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:MBB
Network EngineeringRNC dimensioning- User PlaneCS Data Erlangs are
summed in the same manner as AMR Erlangs
The number of simultaneous connections at RNC can be calculated
by ErlangB with small blocking0.1% commonly used
Example:4 000 000 subscribers with 3,2 mErl of CS 64CS data Load
= 4 000 000 * 3,2/1000 Erl = 12800 ErlErlangB(12800;0.1) = 12984
channelsAdding 40% SHO we get 18178 channelsRNC load throughput:
18178 channels * 66.1 kbps FP bit rate = 1202 MbpsAdd SHO and
protocol overheadCalculate CS Data loadCS Data Traffic# Nokia
Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B
0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R
170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G
170 B 0Primary colors:MBB Network Engineering
RNC dimensioning- User PlaneSubscriber amount definitionCS 64
Traffic Demand definition In [mErl]Service definitionSHO definition
(in Expert Menu)Blocking Probability definition (Services step) CS
Data Traffic RAN Dim definition# Nokia Siemens Networks 2012For
internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166
B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R
255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:MBB
Network Engineering
RNC dimensioning- User PlaneNRT Data amount is summed over the
sites per traffic type
The traffic intensity per traffic type is calculated by the
following equation
The number of simultaneous connections at RNC can be calculated
by ErlangB with small blocking0.1% commonly used
Add the SHO to the simultaneous bearers
Apply the FP rate for the bearer by multiplying the amount of
required bearers by the FP rate of the bearer.Dimensioning is based
on the actual throughput, therefore the result should be multiplied
by Activity Factor at the end.
Add SHO and protocol overheadCalculate NRT Data loadPS Rel.99
Data traffic# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringRNC dimensioning- User PlaneExample480 kbps R99 NRT per
site 4000 sites40% NRT384 60% NRT128NRT activity factor 80%Traffic
intensitiesNRT128 = 4000*480*60%/(128*80%) = 11250 Erl NRT384 =
4000*480*40%/(384*80%) = 2500 ErlSimultaneous bearers 0.1%
blockingNRT128: ErlB(11250, 0.1%) = 11426 bearersNRT384: ErlB(2500,
0.1%) = 2603 bearersWith 40% SHONRT128: 11426*1.4 = 15996
bearersNRT384: 2603*1.4 = 3644 bearersRNC Throughput loadNRT128:
15996*136.7 = 2187 Mbps *0,8 = 1749 MbpsNRT384: 3644*408 = 1487
Mbps *0.8 = 1190 Mbps
Inputs:1000 subscribers per site480 kbps R99 NRT per site 40%
NRT384 60% NRT128Traffic demand calculation:NRT128:40%*(480 kbps /
1000) = 0.192 kbpsNRT384:60%*(480 kbps / 1000) = 0.288 kbps
Recalculation for RAN DIMPS Rel.99 Data traffic exampleAdd SHO
and protocol overheadCalculate NRT Data load# Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network Engineering
RNC dimensioning- User PlaneService definitionsTraffic Demand
definitionsActivity Factor automatically:AF= Average bearer rate /
Bearer peak ratePS Rel.99 Data traffic RAN Dim definitionAdd SHO
and protocol overheadCalculate NRT Data load# Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network EngineeringRNC dimensioning- User
PlaneThe HSDPA load is calculated separately from R99 NRT
Traffic
Note that HSDPA connections can not be in SHOThe protocol
overheads are variable depending on the HSDPA rate.
RNC is such a big aggregation point for the traffic that we can
use the average user traffic figures to determine the HSDPA traffic
load for the RNC
Calculate HSDPALoadApply FP Rate
HSDPA Traffic# Nokia Siemens Networks 2012For internal useR 255
G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
Engineering
RNC dimensioning- User PlaneExample:We have 4000 sites, 1000
users per site.
Traffic demand: 950 bps per user
It is recommeded to use 11% overhead over the payload rates to
include RLC and FP overheads.
FP OH = 11%
Rate above RLC [kbps]FP bit rate [kbps]FP overhead over
RLC647416%12814211%2562768%3844107%5125456%102410846%160016946%204821656%336035576%HSDPA
Traffic - exampleCalculate HSDPALoadApply FP Rate# Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network Engineering
RNC dimensioning- User PlaneService definitionTraffic Demand
definitionHSDPA Traffic RAM Dim definitionCalculate HSDPALoadApply
FP Rate# Nokia Siemens Networks 2012For internal useR 255 G 204 B
0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R
234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network EngineeringRNC Iub
throughput Mbps is the traffic in downlink direction defined in FP
level and it includes 40 % of SHO. 100 % activity factor is
assumed
Additionally 30 % traffic is supported in uplink direction (UL
Iub=0.3 DL Iu*fp overheads*SHO)The size of the Iur included in RNC
capacity is 8% from the Iub w/o SHO capacity.
Example with mcRNC S3-B2 (RU40) and 85% fill rate:
From throughput point of view, 5 mcRNC S3-B2 configs are
needed
RNC dimensioning- User PlaneApply traffic mix rule
Traffic Mix Rule# Nokia Siemens Networks 2012For internal useR
255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G
113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringThe maximum Iub PS DL throughput used in the Traffic Mix
Rule calculation needs to be modified according to the following
equation:
UL share can be simply calculatedby dividing user traffic in UL
direction by user traffic in DL direction:
Note: throughputs are on Iu-PS interface without FP and SHO
overheads.RNC dimensioning- User Plane Cross-check PS UL traffic
amount
If PS UL traffic is < 30% of DL, then it doesnt have any
affect on dimensioningIf the PS UL share is more than 30 %, then
one of following two rules can be used:
Values of summed PS traffic DL+UL on Iub can be used in the
Traffic Mix Rule instead of the DL only:
This approach is used in RAN DIMUplink dimensioning# Nokia
Siemens Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B
0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R
170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G
170 B 0Primary colors:MBB Network EngineeringControl PlanemcRNC
dimensioning (incl. RAN Dim user guidance)R 255 G 204 B 0R 255 G
130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B
234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60
G 170 B 0Primary colors:# Nokia Siemens Networks 2012For internal
useMBB Network Engineering# Nokia Siemens Networks 2012For internal
useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R
104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255
B 255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringCS BHCA and PS BHCA already defined for RNCCorresponding
Traffic Profile:
Traditional CS_BHCA and PS_BHCA approach:
Example for mcRNC S3-B2
RNC dimensioning- Control PlanePropertyValueProportion of
handovers 40%CS Mean Holding Time90 s hard handovers 0.1 per call
soft handovers6 per callMax AMR codec16 kbpsCS traffic per user 25
mErlPS traffic per user2 kbpsNAS BHCA per user 3.8PS RAB MHT 185
sSoft handovers per PS RAB 1.27Cell updates per PS RAB
2.9IDLE_ModeCell_DCH/Cell_FACHCell_PCH214356
Simplified approach# Nokia Siemens Networks 2012For internal
useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R
104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255
B 255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringInputs for aggregated CS and PS BHCA demand
calculation
RNC dimensioning- Control PlaneDept. / Author / DateRule for
simplified RNC CP dimensioningRNC maximum values, defined per each
RNC configuration in PD
This approach should be used, if NSN default Traffic Model is
used (customer Traffic Model is not known)Simplified approach RAN
Dim definition# Nokia Siemens Networks 2012For internal useR 255 G
204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B
122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringReality there is no such situation, where traffic model
is identical to NSN default TM
Solution use the rule for PS session attempts instead of PS
BHCA:
RNC dimensioning- Control PlaneDept. / Author / DateIntermediate
approachIDLE_ModeCell_DCH/Cell_FACHCell_PCH214356IDLE_ModeCell_DCH/Cell_FACHCell_PCH2145637PS
BHCAPS BHCA
PS session attempt: When the packet scheduler attempts to
allocate transport channel for the NRT RAB, and there are no
dedicated/shared channels that are already allocated for the RAB.
NSN Default traffic model 2 PS sessions per PS RAB max PS sessions
per RNC type = 2 * PS BHCA# Nokia Siemens Networks 2012For internal
useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R
104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255
B 255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
Engineering
RNC dimensioning- User and Control PlaneDept. / Author / DateRAN
Dim input values Traffic Demand can be defined in many different
units [Erlangs, kbps, kb, MB] and on different levels [per
subscriber, per area] RAN Dim automatically recalculates them to
the format appropriate for further calculations and aggregates the
traffic over all subscribers and areas connected to one RNC
RNC fill rate defines the maximum RNC utilization and is
applicable for each dimensioning rule # Nokia Siemens Networks
2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R
163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G
0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary
colors:MBB Network Engineering
RNC dimensioning- User and Control PlaneDept. / Author / DateRAN
Dim dimensioning results
Intermediate result Aggregated traffic demand These values are
directly used in nominators of Traffic Mix Rule and simplified
Control Plane formulas RNC fill rate calculated RNC utilization for
each dimensioning aspect separatelyFill rate for each limit will
never exceed configured RNC target fill rate# Nokia Siemens
Networks 2012For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:MBB Network EngineeringBTS/cell connectivitymcRNC
dimensioning (incl. RAN DIM user guidance)R 255 G 204 B 0R 255 G
130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B
234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60
G 170 B 0Primary colors:# Nokia Siemens Networks 2012For internal
useMBB Network Engineering# Nokia Siemens Networks 2012For internal
useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R
104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255
B 255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringRNC dimensioning - connectivityDimensioning process for
cells and NodeBs:Get the amount of sites and cells normally
available from radio network planningRetrieve the relevant limit
from the mcRNC capacity tables Define the filling ratio for the
limit Calculate number of mcRNCs based on the following
equations:
Select the highest result -> the number of RNCs needed
InputNodeBs, CarriersCheck Cell LimitationSelect highest number
from the received resultsNumber of RNCs neededCheck NodeB
Limitation
BTS / cell connectivity limits# Nokia Siemens Networks 2012For
internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166
B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R
255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:MBB
Network EngineeringInputs for BTS / Cell connectivity check
Dimensioning results:
RNC dimensioning - connectivityDept. / Author / Date
Number of sites and cells per site can be entered manually per
each Area or calculated automatically during E2E dimensioning
excerciseBTS / carrier connectivity RAN Dim definition
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G
234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting
colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringTransport PlaneValid for mcRNC2.0 HWmcRNC dimensioning
(incl. RAN Dim user guidance)R 255 G 204 B 0R 255 G 130 B 0R 110 G
6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B
30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B
0Primary colors:# Nokia Siemens Networks 2012For internal useMBB
Network Engineering# Nokia Siemens Networks 2012For internal useR
255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G
113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B
255Supporting colors:R 60 G 170 B 0Primary colors:MBB Network
EngineeringmcRNC IP TransportBasic functions and featuresIP
Transport basic functions and features in mcRNC1.0 RAN2222 IP
transport for mcRNCExternal connectivity: 1GE (and 10GE* interfaces
depending on the backplane connectivity)VLANStatic routingQoSIP
network supervision, BFD multi-hopRAN1711 mcRNC IP site
solutionRAN2256 Ethernet Link Aggregation (optional)RAN2197 VLAN
Traffic Differentiation (optional)RAN1510 OSPF for Redundancy
*) supported in future release
# Nokia Siemens Networks 2012For internal useR 255 G 204 B 0R
255 G 130 B 0R 110 G 6B 115R 163