ran16.0 rnc in pool configuration principles 02 (20140915)

Upload: miko-keren

Post on 01-Jun-2018

234 views

Category:

Documents


4 download

TRANSCRIPT

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    1/65

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    2/65

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    3/65

    &'1#0 &C in Pool Configuration Prin"iples Contents

    Contents

    1 Overview......................................................................................1

    2 RNC in Pool Features and Networking............................................3

    2#1 Introdu"tion####################################################################################################################################################################*

    2#2 Introdu"tion to &C in Pool ode &edundan"y############################################################################################################*2#* Introdu"tion to &C in Pool %oad +haring####################################################################################################################4

    2#4 Constraints on &C in Pool etwor,ing +"enarios#####################################################################################################10

    2#5 Configuration Constraints############################################################################################################################################1*

    2#5#1 &C in Pool etwor,ing Constraints and Configuration Prin"iples########################################################################1*

    2#5#2 Constraints on Iur-p Interfa"e Configuration############################################################################################################1

    3 RNC Capacity Dimensioning.........................................................1

    *#1 Planning i.ensions####################################################################################################################################################1/

    *#2 ey +teps for Planning &C in Pool i.ension Configurations################################################################################19

    *#2#1 Capa"ity Planning######################################################################################################################################################19

    *#2#2 i.ensioning Pro"ess for &C in Pool################################################################################################################### #21

    *#2#* Capa"ity Planning in a"h i.ension######################################################################################################################22

    *#* Capa"ity Planning Pro"edures for &C in Pool Configurations##################################################################################2/

    *#*#1 +C900####################################################################################################################################################################2/

    *#*#2 +C910####################################################################################################################################################################*

    ! "o#tware Con$guration Principles #or RNC in Pool Features...........%!

    4#1 +oftware and %i"ense Configuration Prin"iples for &C in Pool 3erall un"tions##################################################54

    4#2 %i"ense Configuration Prin"iples for a"h Physi"al &C on an &C in Pool etwor,############################################55

    4#* +oftware and %i"ense Configurations for &C in Pool %oad +haring########################################################################5

    4#4 +oftware and %i"ense Configurations for &C in Pool ode &edundan"y################################################################5/

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    ii

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    4/65

    &'1#0 &C in Pool Configuration Prin"iples igures

    Figures

    Figure 2-1&C in Pool ode &edundan"y############################################################################################################4

    Figure 2-2&C in Pool %oad +haring####################################################################################################################/

    Figure 2-3Control-plane and user-plane load sharing############################################################################################9

    Figure 2-4&esour"e pool for.ed 6y +C900s and a +C910########################################################################11

    Figure 2-5&esour"e pool for.ed 6y the +C910s (&'1#0)#########################################################################12

    Figure 2-6&esour"e pool oerlapping in one +C910 that supports a .a7i.u. of 4 logi"al &Cs(&'1#0)

    ###############################################################################################################################################################################1*

    Figure 3-1Planning di.ensions for &C hardware re8uire.ents#######################################################################1/

    Figure 3-2i.ensioning pro"edure for &C in Pool "onfigurations##################################################################21

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    iii

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    5/65

    &'1#0 &C in Pool Configuration Prin"iples !a6les

    &a'les

    Table 2-1Capa"ity spe"ifi"ations of the +C900 and +C910 that use and not use &C in Pool features######5

    Table 2-2&C in Pool networ,ing s"enarios supported in &'15#0 and &'1#0##########################################10

    Table 3-1Capa"ity di.ensions for the "ontrol plane$ user plane$ and trans.ission plane###################################1

    Table 3-2Hardware and hardware li"enses affe"ted 6y "apa"ity planning for the "ontrol plane$ user plane$ andtrans.ission plane##################################################################################################################################################1

    Table 3-3Capa"ity spe"ifi"ations in ea"h di.ension for node redundan"y#########################################################2*

    Table 3-4Capa"ity spe"ifi"ations of ea"h di.ension for load sharing################################################################ #24

    Table 3-5&C role in a resour"e pool and the "orresponding di.ensions##########################################################25

    Table 3-6Input "ontrol para.eters and "apa"ity re8uire.ent para.eters###########################################################2/

    Table 3-73utput para.eters related to "apa"ity transferred fro. the .aster &C to the 6a",up &C or

    oerflow &C(for ode &edundan"y)##################################################################################################################2

    Table 3-83utput para.eters related to "apa"ity transferred fro. the .aster &C to the 6a",up &C oroerflow &C(for %oad +haring)##########################################################################################################################*0

    Table 3-93utput para.eters related to hardware and hardware li"enses in the &C in Pool "onfiguration for a

    +C900################################################################################################################################################################*2

    Table 3-103utput para.eters related to software li"enses in the &C in Pool "onfiguration for a +C900# # #*

    Table 3-11Input "ontrol para.eters######################################################################################################################*

    Table 3-12Input para.eters when a +C910 seres as the .aster &C###########################################################*

    Table 3-133utput para.eters related to "apa"ity transferred to the 6a",up &C(for ode &edundan"y)#########*9

    Table 3-143utput para.eters related to "apa"ity transferred to the oerflow &C(for %oad +haring)##############40

    Table 3-153utput para.eters related to hardware and hardware li"enses when a +C910 seres as the .aster

    &C#######################################################################################################################################################################41

    Table 3-163utput para.eters related to software li"enses when a +C910 seres as the .aster &C############45

    Table 3-17Input para.eters (inter.ediate para.eters related to "apa"ity transferred fro. the .aster &C to

    the 6a",up &C) when a +C910 seres as the 6a",up &C and the "al"ulation results#################################45

    Table 3-18Input para.eters (inter.ediate para.eters related to "apa"ity transferred fro. the .aster &C)

    when a +C910 seres as the oerflow &C in load sharing#############################################################################4/

    Table 3-193utput para.eters related to hardware and hardware li"enses when a +C910 seres as the 6a",up

    &C or oerflow &C##########################################################################################################################################49

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    i

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    6/65

    &'1#0 &C in Pool Configuration Prin"iples !a6les

    Table 4-1Configuration s"enarios of the &C in Pool features###########################################################################5

    Table 4-2Configuration s"enarios of the &C in Pool features (the +C910 wor,s as .aster or oerflow

    &C)######################################################################################################################################################################5

    Table 4-3Configuration s"enarios of the &C in Pool features (the +C910 wor,s as 6oth the .aster andoerflow &C)######################################################################################################################################################5/

    Table 4-4Configuration s"enarios of the &C in Pool features###########################################################################5/

    Table 4-5Configuration s"enarios of the &C in Pool features (the +C910 wor,s as .aster or oerflow

    &C)######################################################################################################################################################################5

    Table 4-6Configuration s"enarios of the &C in Pool features (the +C910 wor,s as 6oth the .aster and

    oerflow &C)######################################################################################################################################################5

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    7/65

    &'1#0 &C in Pool Configuration Prin"iples 1 3eriew

    1 Overview!his do"u.ent des"ri6es the &C in Pool features$ networ,ing re8uire.ent$ and"onfiguration prin"iples$ and pro"edures and ,ey fa"tors for planning the "apa"ity re8uired for

    the &C in Pool features on an :;!+ networ, that "ontains the +C900 3:e repla"es the >3:"$ and the

    >C:6?>C>6 repla"es the >C:a?>C>a 6e"ause life "y"les of these 6oards in +C900s

    are due# &C in Pool "onfiguration prin"iples are also appli"a6le to the new 6oards#

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    1

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    8/65

    &'1#0 &C in Pool Configuration Prin"iples 1 3eriew

    In this do"u.ent$ +C900 and +C910 "onfigurations re8uired for the &C in Pool"onfigurations$ na.ely "hanged di.ensions a.ong &Cs due to introdu"tion of the &C in

    Pool features$ are proided only#

    or detailed +C900 and +C910 "onfigurations$ in"luding 6oard "onfiguration prin"iples

    appli"a6le to 6oth +C900 and +C910$ traffi" .odel$ "apa"ity and hardware 8uantity thatare deried fro. the traffi" .odels and target su6s"ri6ers$ seeSRAN9.0&GBSS16.0&RAN16.0 BSC6910 Configuration Principlesand

    SRAN9.0&GBSS16.0&RAN16.0 BSC6900 Configuration Principles. It is a good pra"ti"e for

    you to fa.iliari@e yourself with the two do"u.ents 6efore reading this do"u.ent#

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    2

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    9/65

    &'1#0 &C in Pool Configuration Prin"iples 2 &C in Pool eatures and etwor,ing

    2 RNC in Pool Features andNetworking

    ('out &)is C)apter2#1 Introdu"tion

    2#2 Introdu"tion to &C in Pool ode &edundan"y

    2#* Introdu"tion to &C in Pool %oad +haring

    2#4 Constraints on &C in Pool etwor,ing +"enarios

    2#5 Configuration Constraints

    2.1 *ntroduction

    &C in Pool inoles the following features=

    A&-150212 &C in Pool ode &edundan"y

    A&-150211 &C in Pool %oad +haring

    !he two features are independently "onfigured#

    Bou "an ena6le one or 6oth of the features#

    Ahen planning "apa"ity for the &C in Pool features$ "al"ulate the following 6ased on roles

    (.aster &C$ 6a",up &C$ or oerflow &C) of physi"al &Cs and the "apa"ity re8uired

    for i.ple.enting node redundan"y or load sharing=

    Hardware and hardware li"enses for the "ontrol plane$ user plane$ and trans.ission plane

    !arget "apa"ity that "an 6e proided 6y ea"h physi"al &C u.6er of re8uired

    software li"enses

    ' resour"e pool "onsists of 6oth +C900s and +C910s# !herefore$ this do"u.ent "oers

    6oth +C900s and +C910s#

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    *

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    10/65

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    11/65

    &'1#0 &C in Pool Configuration Prin"iples 2 &C in Pool eatures and etwor,ing

    2.3 *ntroduction to RNC in Pool +oad ")aring

    %oad sharing a.ong physi"al &Cs is i.ple.ented 6y adding physi"al &Cs$ there6yte.porarily in"reasing the traffi" a6sorption "apa6ility of logi"al &Cs and resisting traffi"

    6ursts#

    &'15#0 support "ontrol-plane load sharing only#

    &'1#0 supports the following load sharing .odes=

    Control-plane load sharing only

    :ser-plane load sharing 6inding with "ontrol-plane load sharing

    oth of the a6oe

    Capacity *mproved 'y RNC in Pool +oad ")aring

    'fter &C in Pool %oad +haring is ena6led$ the +C900 and +C910 use the +C910s to

    e7pand "apa"ity of the original logi"al &C# In "ontrol-plane load sharing only$ the HC' ofthe original logi"al &C i.proes to 1# ti.es the .a7i.u. spe"ifi"ations# In user-plane

    load sharing 6inding with "ontrol-plane load sharing$ "apa"ity of the original logi"al &C

    i.proes to 1#9 ti.es the .a7i.u. spe"ifi"ations# !he following ta6le lists detailed

    spe"ifi"ations#

    Table 1.1 Capa"ity spe"ifi"ations of the +C900 and +C910 that use and not use &C in Poolfeatures

    "cenario,"peci$cations

    Num'er o# -ase"tations,Cells

    -C( /0 P"&)roug)put/'it,s

    &C ot :sing the &C in Pool eatures and &C :sing ode &edundan"y

    +C900 *00?5100 1200 (+ee ote

    1#)

    40 (+ee ote 2#)

    +C910 (two "a6inets) 10000?20000 4000 (+ee ote1#)

    120 (+ee ote2#)

    +C910 (one "a6inet) 5000?10000 *2000 (+ee ote1#)

    0 (+ee ote 2#)

    &C :sing Control-Plane %oad +haring 3nly

    +C900 (.aster)D+C910 (oerflow)

    *00?5100 120071# 40

    +C910 (.aster)

    D+C910 (oerflow)(two "a6inets)

    10000?20000 400071# 120

    +C910 (.aster)D+C910 (oerflow)

    (one "a6inet)

    5000?10000 *200071# 0

    &C :sing :ser-Plane %oad +haring inding with Control-Plane %oad +haring

    +C900 (.aster) *00?5100 120071#9 4071#9

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    5

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    12/65

    &'1#0 &C in Pool Configuration Prin"iples 2 &C in Pool eatures and etwor,ing

    "cenario,"peci$cations

    Num'er o# -ase"tations,Cells

    -C( /0 P"&)roug)put/'it,s

    D+C910 (oerflow)

    +C910 (.aster)

    D+C910 (oerflow)

    (two "a6inets)

    10000?20000 400071#9 12071#9

    +C910 (.aster)D+C910 (oerflow)

    (one "a6inet)

    5000?10000 *200071#9 071#9

    NOTE

    ote 1= !he +C900 1200 HC' and +C910 4000?*2000 HC' are "al"ulated 6ased on

    the +.artphones !raffi" ;odel#

    ote 2= !he P+ throughput of the +C900 and +C910 is "al"ulated 6ased on the High-P+ ;odel#

    or details a6out Huawei typi"al +.artphones !raffi" ;odel and High-P+ ;odel$ see

    +&'9#0E>++1#0E&'1#0 +C910 Configuration Prin"iples and

    +&'9#0E>++1#0E&'1#0 +C900 Configuration Prin"iples#

    ControlPlane +oad ")aring

    ' .aster &C refers to a physi"al &C fro. whi"h "all pro"essing load is transferred toother &Cs# 'n oerflow &C refers to the &C to whi"h "all pro"essing load is transferred

    fro. a .aster &C# Calls oer the odes under a .aster &C is pro"essed on the .aster

    &C# Ahen "ontrol-plane load sharing "onditions are satisfied$ the .aster &C transfers

    partial "ontrol-plane "all load to oerflow &Cs#

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    13/65

    &'1#0 &C in Pool Configuration Prin"iples 2 &C in Pool eatures and etwor,ing

    Figure 1.1 &C in Pool %oad +haring

    In igure 2-2$ as an e7a.ple$ "alls oer the odes under &C P&C1 are pri.arilypro"essed on &C P&C1# Ahen "ontrol-plane "apa"ity of &C P&C1 is not enough for

    "alls oer the odes under &C P&C1$ the &C P&C1 transfers so.e "alls to &C

    P&C2 and the transferred "alls are then pro"essed on &C P&C2# or the &C$ thetransferred "alls are oerflow "alls# or the transferred "alls$ &C P&C1 is the .aster

    &C$ and &C P&C2 is an oerflow &C#

    In pra"ti"e$ hardware and hardware li"enses for re8uire.ents on user-"ontrol plane and

    trans.ission-plane need to 6e planned on the .aster &C$ and hardware and hardware

    li"ense for "ontrol-plane re8uire.ents need to 6e planned on the oerflow &Cs# In addition$

    so.e "alls .ay 6e 6eing transferred fro. &C P&C1 to &C P&C2 at the ti.e whenother "alls are 6eing transferred fro. &C P&C2 to &C P&C1# !herefore$

    oerflowing dire"tion needs to 6e "onsidered in planning "ontrol-plane "apa"ity#

    In "ontrol-plane load sharing$ only sharea6le load is transferred fro. the .aster &C to the

    oerflow &C$ and the unsharea6le load re.ains on the .aster &C#

    In addition$ when an oerflow "all is pro"essed on the two &Cs$ so.e "oordination and

    "ontrol .essages need to 6e transferred 6etween the two &Cs# !his "onsu.es e7tra "ontrol-

    plane resour"es and interfa"e 6andwidth$ whi"h needs to 6e "onsidered during "apa"ity

    planning=

    7tra resour"e "onsu.ption on the "ontrol plane= &esour"es "onsu.ed 6y an oerflow

    su6s"ri6er are a6out 5/F of those "onsu.ed 6y a non-oerflow su6s"ri6er on the .aster

    &C# &esour"es "onsu.ed 6y an oerflow su6s"ri6er are a6out *F of those "onsu.ed

    6y a non-oerflow su6s"ri6er on the oerflow &C# !herefore$ load sharing "onsu.es

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    /

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    14/65

    &'1#0 &C in Pool Configuration Prin"iples 2 &C in Pool eatures and etwor,ing

    an e7tra "ontrol-plane resour"e of a6out 10FG20F ("al"ulated 6y 5/FD*F-100F) on6oth the .aster &C and oerflow &C#

    Iur-p 6andwidth "onsu.ption= andwidth for "ontrol plane infor.ation on 6ear on Iur-p

    interfa"e#

    Iur-p "ontrol plane 6andwidth= 7tra 6andwidth is "onsu.ed oer the Iur-p interfa"ethrough whi"h "oordination and "ontrol .essages are transferred 6etween two &Cs$

    in"luding 10;6it?s of 6ase 6andwidth and 20,6it?s "onsu.ed 6y ea"h a"tie user during

    load sharing pro"ess# 'n a"tie user refers to the : in the C%%CH orC%%'CH state#

    4serPlane +oad ")aring

    :ser-plane load sharing is perfor.ed together with "ontrol-plane load sharing# oth user-

    plane data and trans.ission-plane data "an 6e transferred to the oerflow &C for pro"essing#!he following figure shows data flow on the "ontrol plane and user plane#

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    15/65

    &'1#0 &C in Pool Configuration Prin"iples 2 &C in Pool eatures and etwor,ing

    Figure 1.1 Control-plane and user-plane load sharing

    !herefore$ during "apa"ity planning for 6oth "ontrol-plane load sharing and user-plane load

    sharing$ the hardware and hardware li"enses need to 6e planned for the "ontrol plane$ user

    plane$ and trans.ission plane on the oerflow &C#

    Control-plane data of oerflow su6s"ri6ers oer the Iu$ Iur$ or Iu6 interfa"e is trans.itted to

    other s through the .aster &C in 6oth load sharing .odes#

    Ahen an oerflow "all is pro"essed on two &Cs$ so.e "oordination and "ontrol .essages

    need to 6e transferred 6etween the two &Cs# !his "onsu.es e7tra "ontrol-plane resour"es

    and interfa"e 6andwidth$ whi"h needs to 6e "onsidered during "apa"ity planning=

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    9

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    16/65

    &'1#0 &C in Pool Configuration Prin"iples 2 &C in Pool eatures and etwor,ing

    7tra resour"e "onsu.ption on the "ontrol plane= &esour"es "onsu.ed 6y an oerflow

    su6s"ri6er are a6out 5*F of those "onsu.ed 6y a non-oerflow su6s"ri6er on the .aster&C# &esour"es "onsu.ed 6y an oerflow su6s"ri6er are a6out 55F of those "onsu.ed

    6y a non-oerflow su6s"ri6er on the oerflow &C# !herefore$ load sharing "onsu.es

    an e7tra "ontrol-plane resour"e of a6out F ("al"ulated 6y 5*FD55F-100F) on 6oth the

    .aster &C and oerflow &C# !his is the sa.e as that in "ontrol-plane load sharingonly"ontrol plane load sharing only#

    Iur-p 6andwidth "onsu.ption= in"luding 6andwidth of "ontrol plane and user plane 6ear

    on Iur-p interfa"e#

    Iur-p "ontrol plane 6andwidth= 7tra 6andwidth is "onsu.ed oer the Iur-p interfa"ethrough whi"h "oordination and "ontrol .essages are transferred 6etween two &Cs$

    in"luding 10;6it?s of 6ase 6andwidth and 15,6it?s "onsu.ed 6y ea"h a"tie user during

    load sharing pro"ess# 'n a"tie user refers to the : in the C%%CH or

    C%%'CH state#

    Iur-p user plane 6andwidth= in"luding user plane throughput when load shared user inCell'CH state$ and when load sharing user using I: '!; trans.ission in 3erflow

    &C#

    2.! Constraints on RNC in Pool Networking"cenarios

    !he following ta6le lists the networ,ing s"enarios that support the &C in Pool features in

    &'15#0 and &'1#0#

    Table 1.1 &C in Pool networ,ing s"enarios supported in &'15#0 and &'1#0

    "cenario R(N1%.5 R(N16.5

    +"enario '=

    900D910

    1 to * +C900s and 1

    +C910

    1 to * +C900s and 1

    +C910

    +"enario =

    910D910

    1 +C910 and 1 +C910 1 to * +C910s and 1

    +C910

    +"enario C=

    n+C900sD2 +C910s

    ot supported 4 +C900s and 2

    +C910s

    ;a7i.u. nu.6er of logi"al

    &Cs that "an 6e"onfigured on a +C910

    4 4

    +"enario ' (1 to n+C900s and 1 +C910)= !he +C900 seres as the .aster &C in

    6oth node redundan"y and load sharing# !he +C910 seres as 6oth the 6a",up &C in

    node redundan"y and the oerflow &C in load sharing#

    &'15#0 and &'1#0 support s"enario ' where the .a7i.u. alue of nis *# ' +C910

    supports a .a7i.u. of four logi"al &Cs#

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    10

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    17/65

    &'1#0 &C in Pool Configuration Prin"iples 2 &C in Pool eatures and etwor,ing

    +"enario (1 to m+C910s and 1 +C910)= !he +C910 seres as 6oth the .aster &Cand 6a",up &C in node redundan"y$ and seres as 6oth the .aster &C and oerflow &C

    in load sharing#

    &'15#0 supports s"enario where mis 1# &'1#0 supports s"enario where mis *# In

    &'15#0 and &'1#0$ the +C910 supports a .a7i.u. of four logi"al &Cs#

    +"enario C (four +C900s and two +C910s)= In this s"enario$ one +C910 "an 6e

    "onfigured in resour"e pools in 6oth s"enario ' and s"enario #

    &'15#0 does not support s"enario C and one &C "annot 6e "onfigured in two &C pools#

    &'1#0 supports s"enario C#

    !ypi"al networ,ing s"enarios supported in &'1#0 for s"enario C are as follows=

    &esour"e pool 1= 1 to 2 +C900s and 1 +C910

    &esour"e pool 2= 1 to 2 +C900s and 1 +C910

    &esour"e pool *= 2 +C910s$ with one fro. resour"e pool 1 and the other fro.resour"e pool 2

    !he +C910 "an not only sere as an oerflow or 6a",up &C in a resour"e pool$ 6ut also 6e

    "onfigured with its own logi"al &C#

    Scenario A !S"6900# an$ a !S"6910 %or& a re#ource 'ool.

    &'1#0 supports the resour"e pool for.ed 6y one to three +C900s and one +C910#

    !he +C910 "an sere as the 6a",up &C and oerflow &C for all +C900s

    si.ultaneously# !he +C900 "annot sere as the 6a",up &C or oerflow &C for the+C910#

    Figure 1.2 &esour"e pool for.ed 6y +C900s and a +C910

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    11

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    18/65

    &'1#0 &C in Pool Configuration Prin"iples 2 &C in Pool eatures and etwor,ing

    Scenario ! !S"6910# %or& a re#ource 'ool.

    &'1#0 supports the resour"e pool for.ed 6y a .a7i.u. of four +C910s in the 1D1$

    2D1$ and *D1 networ,ing .odes# 's shown in the following figure$ the +C910 on the rightseres as the 6a",up &C and oerflow &C for the three +C910s on the left# ;eanwhile$

    one of the three +C910s on the left seres as the 6a",up &C and oerflow &C for the+C910 on the right#

    Figure 1.3 &esour"e pool for.ed 6y the +C910s (&'1#0)

    Scenario " One !S"6910 #er(e in )*o re#ource 'ool# +),e !S"6910 #u''or)# a

    &ai&u& o% %our logical N"#/.

    In &'15#0$ one &C "an 6e "onfigured in one resour"e pool only# In other words$ resour"epools "annot oerlap# In &'1#0$ one +C910 "an 6e "onfigured in two resour"e pools# In

    other words$ two resour"e pools oerlap in one +C910# In fa"t$ this is a "o.6ination of

    s"enario ' and s"enario #

    &esour"e pool oerlap is introdu"ed 6e"ause of the following reason= In a resour"e pool

    for.ed 6y +C900s and a +C910 in &'15#0$ the +C910 proides 6a",up and load

    sharing for logi"al &Cs of the +C900s$ 6ut the logi"al &C of this +C910 "annot 6e6a",ed up and its load "annot 6e shared# !herefore$ in &'1#0$ a +C910 "an for. a

    resour"e pool with another +C910 when it for.s another resour"e pool with +C900s# In

    this way$ this +C910 proides 6a",up and load sharing for +C900s$ and its logi"al &C

    proides 6a",up and load sharing for another +C910#

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    12

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    19/65

    &'1#0 &C in Pool Configuration Prin"iples 2 &C in Pool eatures and etwor,ing

    Figure 1.4 &esour"e pool oerlapping in one +C910 that supports a .a7i.u. of 4 logi"al&Cs(&'1#0)

    2.% Con$guration Constraints

    2.%.1 RNC in Pool Networking Constraints andCon$guration Principles

    7-"C 8orking mode9

    A&-150211 &C in Pool %oad +haring is only supported in ;+C :3 .ode$ not

    supported in >: and >3 .ode#

    A&-150212 &C in Pool ode &edundan"y is supported in ;+C :3 and >: .ode#

    Ahen in >: .ode$ 6oth A&-150212 &C in Pool ode &edundan"y and >-11*/25

    +C ode &edundan"y should 6e a"tiated#

    Directivity

    In a resour"e pool for.ed 6y the +C900s and +C910$ node redundan"y and load sharing

    "an 6e perfor.ed in one dire"tion# In other words$ only the +C910 "an sere as the 6a",up&C and oerflow &C for the +C900s#

    ' +C900 "annot sere as the 6a",up &C or oerflow &C for either the +C900 or+C910#

    In a resour"e pool for.ed 6y +C910s$ node redundan"y and load sharing "an 6e perfor.edin two dire"tions#

    Constraints on Networking

    ifferent resour"e pools "an oerlap in a +C910# ' +C910 supports a .a7i.u. of 4

    logi"al &Cs# 3ne +C910 "an for. a resour"e pool with a .a7i.u. of * +C900s# 3ne+C910 "an also for. a resour"e pool with a .a7i.u. of other three +C910s# 3ne

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    1*

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    20/65

    &'1#0 &C in Pool Configuration Prin"iples 2 &C in Pool eatures and etwor,ing

    +C910 "an for. two resour"e pools si.ultaneously# or details$ see se"tion 2#4Constraints on &C in Pool etwor,ing +"enarios#

    ControlPlane +oad ")aring

    &C in Pool %oad +haring has the following i.pa"ts on "ontrol-plane load of the .aster&C and oerflow &C=

    3nly sharea6le load is transferred fro. the .aster &C to the oerflow &C$ and un-

    sharea6le load re.ains on the .aster &C# uring load sharing$ an oerflow "all pro"essedon two &Cs "onsu.es e7tra "ontrol-plane resour"es for "oordination and "o..utation

    6etween the two &Cs# 's a result$

    or "ontrol plane load sharing only$ "ontrol-plane resour"es "onsu.ed 6y an oerflow

    su6s"ri6er are a6out 5/F of those "onsu.ed 6y a non-oerflow su6s"ri6er on the .aster

    &C# &esour"es "onsu.ed 6y an oerflow su6s"ri6er are a6out *F of those "onsu.ed 6y anon-oerflow su6s"ri6er on the oerflow &C##

    or user-plane load sharing perfor.ed together with "ontrol-plane load sharing$ "ontrol-planeresour"es "onsu.ed 6y an oerflow su6s"ri6er are a6out 5*F of those "onsu.ed 6y a non-oerflow su6s"ri6er on the .aster &C# &esour"es "onsu.ed 6y an oerflow su6s"ri6er are

    a6out 55F of those "onsu.ed 6y a non-oerflow su6s"ri6er on the oerflow &C#

    /Optional Constraints on -oards

    In &C in Pool ode &edundan"y$ if the .aster &C is "onfigured with the +':a?+':"$

    >C>$ or I:a?I:a$ the 6a",up &C .ust also 6e "onfigured with the +':a$ >C>$ or

    I:a$ respe"tiely#

    In "ontrol plane load sharing only$ if the .aster &C is "onfigured with the +':a?+':" or

    >C>$ the oerflow &C .ust also 6e "onfigured with the +':a or >C>#

    In user-plane load sharing 6inding with "ontrol-plane load sharing$ if the .aster &C is

    "onfigured with the +':a?+':"$ >C>$ or I:a?I:a$ the oerflow &C .ust also 6e

    "onfigured with the +':a$ >C>$ or I:a#

    Constraints on &ransmission /1

    Constraints on trans.ission in &C in Pool ode &edundan"y are as follows=

    Iu-C+?Iur interfa"e= !he Iu-C+?Iur interfa"es of the .aster &C and 6a",up &C .ust

    use the sa.e trans.ission .ode$ either IP or '!;# Ahen .ultiple .aster &Cs are6a",ed up 6y one +C910$ the Iu-C+?Iur interfa"es of these .aster &Cs and the

    6a",up &C (+C910) .ust use the sa.e trans.ission .ode$ either IP or '!;# Ahenthe Iu?Iur interfa"e uses the IP trans.ission .ode$ only the layer * trans.ission networ,supports &C in Pool ode &edundan"y#

    Iu-P+ interfa"e= &C in Pool ode &edundan"y is not supported when the Iu-P+

    interfa"e uses '!; trans.ission#

    Constraints on &ransmission /2

    Constraints on trans.ission in "ontrol-plane load sharing only"ontrol plane load sharing only

    are as follows=

    'll "ontrol-plane data is transferred 6a", to the .aster &C through the Iur-p interfa"e for

    intera"tion with other s# !herefore$ the Iu?Iur?Iu6 interfa"e does not need to 6e "onfigured

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    14

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    21/65

    &'1#0 &C in Pool Configuration Prin"iples 2 &C in Pool eatures and etwor,ing

    for the oerflow &C# 3nly the Iur-p and 3E; interfa"es need to 6e "onfigured for theoerflow &C#

    Constraints on &ransmission /3

    Constraints on trans.ission in user-plane load sharing 6inding with "ontrol-plane load sharingare as follows=

    Iu-C+?Iu-P+?Iur interfa"e= oth the .aster &C and oerflow &C .ust use the sa.e

    trans.ission .ode$ either IP or '!;# !he type of trans.ission ports is not spe"ified#

    (2) !he oerflow &C .ust 6e "onfigured with the Iu-C+ and Iu-P+ interfa"es for user-

    plane trans.ission# !he Iur interfa"e is re"o..ended# If the oerflow &C is not

    "onfigured with the Iur interfa"e$ the Iur interfa"e traffi" of an oerflow su6s"ri6er "an

    only 6e transferred 6a", to the .aster &C$ whi"h "onsu.es e7tra Iur-p 6andwidth#

    Iu6 interfa"e= !he oerflow &C .ust 6e "onfigured with the Iu6 interfa"e using IP

    trans.ission# !he type of port for IP trans.ission is not spe"ified# :ser-plane data of an

    oerflow su6s"ri6er "an only 6e pro"essed 6y the oerflow &C whose Iu6 interfa"euses IP trans.ission#

    Control-plane data oer the Iu?Iur?Iu6 interfa"e of an oerflow su6s"ri6er is trans.itted

    to other s through the .aster &C# 3nly the user-plane data is trans.itted to others through the oerflow &C#

    *urp *nter#ace -andwidt)

    Iur-p 6andwidth 6ase 6andwidth D "ontrol plane 6andwidth of load sharing D user planethroughput 6ear on Iur-p

    ase 6andwidth= 10;6it?s 6andwidth is should 6e planed for 6ase infor.ation e7"hange6etween ;aster &C and a",up?3erflow &C#

    Control plane 6andwidth of load sharing= for "ontrol plane load sharing only$ "al"ulate this

    alue a""ording to oerflow a"tie user nu.6er J 20,6it?s# or user-plane load sharingtogether with "ontrol-plane load sharing$ "al"ulate this alue a""ording to oerflow a"tie

    user nu.6er J 15,6it?s#

    :ser plane throughput 6ear on Iur-p '!; ode nu.6er ratio on 3erflow &C J

    3erflow su6s"ri6er J (Proportion of +H3 for C+

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    22/65

    &'1#0 &C in Pool Configuration Prin"iples 2 &C in Pool eatures and etwor,ing

    of 3erflow?a",up +C910$ the .a7i.u. "apa"ity as 10000odeE20000"ell of+C910)#

    or %oad +haring=

    +u.(odeE"ell nu.6er of ea"h .aster &C) D odeE"ells nu.6er "onfigured in the+C910 logi"al &C K the .a7i.u. "apa"ity as 10000odeE20000"ell of +C910#

    2.%.2 Constraints on *urp *nter#ace Con$guration

    !he Iur-p interfa"e is a Huawei proprietary interfa"e for trans.itting ne"essary dei"e data

    a.ong &Cs in a resour"e pool# +u"h data in"ludes dei"e load and heart6eat infor.ation# Inload sharing$ so.e "ontrol-plane data and user-plane data need to 6e trans.itted through the

    Iur-p interfa"e#

    Control-plane and user-plane data "an 6e trans.itted through the Iur-p interfa"e only in

    IP trans.ission#

    3n the +C900$ the >3:"?>3:e and >2" "an 6e "onfigured with the Iur-p interfa"e#

    3n the +C910$ the >3:"?>3:e$ >2"$ and L3:a "an 6e "onfigured with the Iur-p

    interfa"e#

    In a resour"e pool$ the Iur-p interfa"e "an 6e "onfigured only 6etween the +C900 and

    +C910 or 6etween +C910s#

    If only node redundan"y is used$ you are adised to "onfigure the Iur-p and Iur interfa"es

    on the sa.e interfa"e 6oard# If a +C900 or +C910 "onfigured with the Iur-p

    interfa"e is not "onfigured with the >3:"?>3:e$ >2"$ or L3:a interfa"e 6oard forthe Iur interfa"e$ an interfa"e 6oard needs to 6e "onfigured for independently

    i.ple.enting IP oer Iur-p#

    %oad sharing .ay generate heay "ontrol-plane and the user-plane traffi" oer the Iur-p

    interfa"e# Ahen this feature is ena6led$ you are adised to "onfigure the Iur-p interfa"e

    on an independent interfa"e 6oard# Howeer$ the Iur-p and Iur interfa"es "an 6e"onfigured on one L3:a#

    Iur-p trans.ission re8uire.ents in &C in Pool %oad +haring are as follows= the

    unidire"tional trans.ission delay is shorter than or e8ual to 10 .s$ the trans.ission Mitter

    is shorter than or e8ual to 5 .s$ and the pa",et loss rate is s.aller than 0#01F#

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    1

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    23/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    3 RNC Capacity Dimensioning('out &)is C)apter

    *#1 Planning i.ensions

    *#2 ey +teps for Planning &C in Pool i.ension Configurations

    *#* Capa"ity Planning Pro"edures for &C in Pool Configurations

    3.1 Planning Dimensions

    Planning di.ensions for &C hardware re8uire.ents are as follows=

    Figure 1.1 Planning di.ensions for &C hardware re8uire.ents

    's shown in igure *-1$ planning di.ensions for &C hardware re8uire.ents in"lude "ontrol

    plane$ user plane$ and trans.ission plane=

    !he "ontrol plane is di.ensioned 6y HC'$ nu.6er of odes?"ells$ nu.6er of a"tie

    users$ and nu.6er of online users#

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    1/

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    24/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    !he user plane is di.ensioned 6y C+ rl$ P+ throughput$ nu.6er of "ells$ and nu.6er of

    a"tie users#

    !he trans.ission plane is di.ensioned 6y C+ rl$ P+ throughput$ nu.6er of odes$

    nu.6er of a"tie users$ nu.6er of online users$ and nu.6er of Iu-P+ "onne"tions#

    ' resour"e pool differs fro. a "o..on &C in the following aspe"ts=

    !he Iur-p interfa"e trans.ission "apa"ity is planned for a resour"e pool$ in"luding Iur-p

    "ontrol-plane 6andwidth and Iur-p user-plane 6andwidth#

    !he "ontrol-plane load of an oerflow su6s"ri6er "onsists of sharea6le and unsharea6le

    parts that are pro"essed 6y the .aster &C and oerflow &C$ respe"tiely#

    Table 1.1 Capa"ity di.ensions for the "ontrol plane$ user plane$ and trans.ission plane

    Dimension 4ser Plane Control Plane &ransmissionPlane

    Co..oni.ension

    C+ rlangP+ !hroughput

    u.6er of and

    "ells

    u.6er of a"tie

    users

    HC'u.6er of Cells and

    odes

    u.6er of a"tie users

    u.6er of online :s

    C+ rlangP+ !hroughput

    u.6er of and odes

    u.6er of online :s

    u.6er of a"tie users

    &C in Pool-

    dedi"ated

    i.ension

    one HC' (unsharea6le

    part)

    HC' (sharea6le part)

    Iur-p !hroughput

    !he following ta6le lists "apa"ity planning o6Me"ties for &C in Pool#

    Table 1.2 Hardware and hardware li"enses affe"ted 6y "apa"ity planning for the "ontrol plane$

    user plane$ and trans.ission plane

    ardware andardware+icense

    4ser Plane ControlPlane

    &ransmissionPlane

    Hardware

    +C910 >P:a (:P)

    I:a

    >P:a (CP) Iu interfa"e 6oard

    Iu6 interfa"e 6oard

    Iur interfa"e 6oard

    Iur-p interfa"e6oard

    +C900 P:e

    I:a

    +P:6

    Hardw

    are%i"ens

    e

    +C910 &C !hroughput

    Hardware Capa"ity (per50;6ps)

    oled etwor,

    Intelligen"e !hroughput

    %i"ense(50;6ps)

    &C '"tie

    :ser HardwareCapa"ity(per

    1000 '"tie

    :sers)

    +C900 Hardware Capa"ity

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    1

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    25/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    ardware andardware+icense

    4ser Plane ControlPlane

    &ransmissionPlane

    %i"ense(15;6ps)

    Hardware Capa"ity

    %i"ense(*00;6ps)

    etwor, Intelligen"e

    !hroughput%i"ense(50;6ps)

    !he hardware and hardware li"enses are related only to physi"al &Cs$ and they do not transfer with

    logi"al &Cs#

    ollowing are li"enses related to the &C in Pool features=

    &C in Pool %oad +haring (per 500 '"tie :sers)

    &C in Pool ode &edundan"y (per ode)

    &C in Pool ;ultiple %ogi"al &Cs

    3.2 0ey "teps #or Planning RNC in PoolDimension Con$gurations

    3.2.1 Capacity Planning

    Node Redundancy

    !he 6a",up "apa"ity needs to 6e proided 6y the 6a",up &C (inoling the "ontrol plane$

    user plane$ and transport plane) is e8ual to the 6a",up "apa"ity re8uired 6y the .aster &C

    (inoling the "ontrol plane$ user plane$ and transport plane)#

    ControlPlane +oad ")aring Only

    ;aster &C "apa"ity=

    Control plane= :nsharea6le "ontrol-plane data re.ains on the .aster &C$ andperfor.ing load sharing a.ong &Cs "onsu.es e7tra "ontrol-plane resour"es#

    &esour"es "onsu.ed 6y the two parts are 5/F of one user the .aster &C#

    !rans.ission= ;ore Iur-p 6andwidths are re8uired# 'n oerflow a"tie user "onsu.es 20

    ,6it?s 6andwidth (:%D%)#

    3erflow &C "apa"ity=

    Control plane= +harea6le "ontrol-plane data of an oerflow su6s"ri6er is pro"essed 6y the

    oerflow &C$ and perfor.ing load sharing a.ong &Cs "onsu.es e7tra "ontrol-plane

    resour"es# &esour"es "onsu.ed 6y the two parts are *F of one user the .aster &C#

    !rans.ission= ;ore Iur-p 6andwidths are re8uired# 'n oerflow a"tie user "onsu.es 20

    ,6it?s 6andwidth (:%D%)#

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    19

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    26/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    4serPlane +oad ")aring -inding wit) ControlPlane +oad")aring

    ;aster &C "apa"ity=

    Control plane= :nsharea6le "ontrol-plane data re.ains on the .aster &C$ andperfor.ing load sharing a.ong &Cs "onsu.es e7tra "ontrol-plane resour"es#

    &esour"es "onsu.ed 6y the two parts are 5*F of one user the .aster &C#

    :ser plane= :ser-plane data on the "o..on "hannel re.ains on the .aster &C# :ser-

    plane data on the dedi"ated "hannel is transferred to the oerflow &C#

    !rans.ission=

    1# !he .aster &C pro"esses only the "ontrol-plane data of an oerflow su6s"ri6er on the

    Iu?Iur interfa"e$ 6ut does not pro"ess the user-plane data on the Iu?Iur interfa"e#

    2# Iu6 user-plane data on the dedi"ated "hannel is transferred to the oerflow &C# !he.aster &C pro"esses only the Iu6 user-plane data on the "o..on "hannel and "ontrol-

    plane data oer the Iu6 interfa"e#

    *# Iur-p "ontrol plane interfa"e= 15 ,6it?s 6andwidth is proided for ea"h oerflow a"tie

    user for trans.itting "ontrol-plane data during &C intera"tions and user-plane data#

    4# Iur-p user plane interfa"e= Iu6 user-plane data on the dedi"ated "hannel is transferred to

    the oerflow &C# !he .;aster &C pro"esses only the Iu6 user-plane data on the"o..on "hannel of oerflow user and dedi"ated "hannel data of oerflow user when

    '!; transport type is "onfigured on Iu6 6etween 3erflow &C and ode"ontrol-

    plane data oer the Iu6 interfa"e#

    3erflow &C "apa"ity=

    Control plane= +harea6le "ontrol-plane data of an oerflow su6s"ri6er is pro"essed 6y the

    oerflow &C$ and perfor.ing load sharing a.ong &Cs "onsu.es e7tra "ontrol-plane

    resour"es# &esour"es "onsu.ed 6y the two parts are 55F of one user the .aster &C# :ser plane= :ser-plane data of an oerflow su6s"ri6er on the dedi"ated "hannel is

    pro"essed 6y the oerflow &C#

    !rans.ission plane=

    1# Iu?Iur trans.ission-plane data is pro"essed 6y the oerflow &C#

    2# Iu6 trans.ission-plane data on the dedi"ated "hannel is pro"essed 6y the oerflow &C#

    *# Iur-p "ontrol plane interfa"e= 15 ,6it?s 6andwidth is proided for ea"h oerflow a"tie

    user for trans.itting "ontrol-plane data during &C intera"tions and user-plane data#

    4# Iur-p user plane interfa"e= 3erflow &C pro"esses the Iur?Iu user plane data$ the Iu6

    user plane data on IP#

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    20

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    27/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    3.2.2 Dimensioning Process #or RNC in Pool

    Figure 1.1 i.ensioning pro"edure for &C in Pool "onfigurations

    's shown in figure *-2$ the di.ension planning for &C in Pool "onfigurations in"ludes thefollowing pro"edures=

    "tep 1 eter.ine the &C types and networ,ing s"enarios within an &C pool#

    !he &C in Pool solution supports +C900

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    28/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    "tep 2 eter.ine the &C in Pool feature to 6e used#

    !he &C in Pool features in"lude A&-150212 &C in Pool ode &edundan"y and

    A&-150211 &C in Pool %oad +haring#

    "tep 3 eter.ine the role of ea"h &C in the &C pool#or A&-150212 &C in Pool ode &edundan"y$ deter.ine an &C wor,s as a .aster

    &C or 6a",up &C# or A&-150211 &C in Pool %oad +haring$ deter.ine an &C

    wor,s as a .aster &C or an oerflow &C#

    "tep ! eter.ine the target "apa"ity in gien di.ensions#

    or &C in Pool ode &edundan"y$ the initial target "apa"ity .eans the nu.6er of :s

    sered 6y the ode and the "ells under the ode that re8uires to 6e 6a",ed up on the6a",up &C#

    or &C in Pool %oad +haring$ the initial target "apa"ity .eans the nu.6er of :s of whi"hthe load needs to 6e shared on the oerflow &C and whether "ontrol-plane or user-plane

    load sharing is perfor.ed#

    "tep % Cal"ulate ea"h spe"ifi" "apa"ity di.ension 6ased on the traffi" .odel after i.porting theinitial target "apa"ity#

    "tep 6 eter.ine "apa"ity distri6ution on the .aster &C$ 6a",up &C$ and oerflow &C 6asedon the "hara"ters and re8uire.ents of the &C in Pool features#

    "tep Cal"ulate the nu.6er of re8uired hardware and hardware li"enses 6ased on the "apa"ityre8uire.ents of ea"h physi"al &C for ea"h feature and the a"tual hardware spe"ifi"ations#

    ----En$

    If a physi"al &C seres 6oth node redundan"y and load sharing$ the hardware?hardware li"ense

    "apa"ity of this &C depends on the greater "apa"ity a.ong those re8uired 6y the two features$

    instead of the su. of those re8uired 6y the two features#

    If a physi"al &C seres as the 6a",up &C and?or oerflow &C$ and it has its independent

    logi"al &C (irreleant to the &C in Pool features) and independent "apa"ity$ the

    hardware?hardware li"ense "apa"ity of this physi"al &C "onsists of two parts= one for the &C inPool features and the other for the non-&C in Pool features#

    ----En$

    3.2.3 Capacity Planning in :ac) Dimension

    F-150212 N" in ool No$e e$un$anc

    +our"e=

    1# ased on the traffi" .odel$ "al"ulate the 6a",up "apa"ity in ea"h di.ension for the.aster &C using the i.ported initial target "apa"ity#

    2# ased on the "al"ulation results of .ultiple .aster &Cs$ "al"ulate the "apa"ity that

    need to 6e proided 6y the 6a",up &C in ea"h di.ension#

    I.pa"t=

    !he hardware and hardware li"ense ta,e effe"t only on the 6a",up &C and only on the+C910#

    !he following ta6le lists "apa"ity spe"ifi"ations in ea"h di.ension for node redundan"y#

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    22

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    29/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    Table 1.1 Capa"ity spe"ifi"ations in ea"h di.ension for node redundan"y

    Description CapacityDimension

    /Calculated 'y t)e7aster RNC andt)en &rans#erred tot)e -ackup RNC

    *mpacted ardware(nd ardware+icense /-ackup

    RNC

    Iu6 traffi" "apa"ity$ whi"h

    i.pa"ts the user-plane and

    Iu6 interfa"e hardware$ anduser-plane hardware li"ense

    Iu6 C+ !raffi" (rl) >P:a (:P)$ Iu6 interfa"e

    6oard$ and I:a

    &C !hroughput Hardware

    Capa"ity(per 50;6ps)

    oled etwor,

    Intelligen"e !hroughput%i"ense(50;6ps)

    Iu6 P+ % Payload!hroughput (;6ps)

    Iu6 P+ :% Payload!hroughput (;6ps)

    Iu?Iur traffi" "apa"ity$ whi"h

    i.pa"ts Iu?Iur hardware

    Iu-C+ !raffi" (rl) Iu?Iur interfa"e 6oard

    Iu P+ % Payload

    !hroughput (;6ps)

    Iu P+ :% Payload

    !hroughput (;6ps)

    Iur % Payload !hroughput(;6ps)

    Iur :% Payload !hroughput

    (;6ps)

    Control-plane traffi"

    "apa"ity$ whi"h i.pa"ts

    "ontrol-plane hardware and

    hardware li"enses

    HC'

    HC' per >P:a

    >P:a (CP)

    '"tie :sers >P:a (CP)$ >P:a (:P)$

    and Iu6 interfa"e 6oard

    &C '"tie :ser HardwareCapa"ity (per 1000 '"tie

    :sers)

    u.6er of "onne"ted :s$whi"h has au7iliary

    "onstraints on hardware

    8uantities

    3nline :sers Iu interfa"e 6oard

    ode nu.6er >P:a (CP) and Iu6

    interfa"e 6oard

    Cell u.6er >P:a (CP?:P)

    F-150211 N" in ool oa$ S,aring

    +our"e=

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    2*

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    30/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    1# ased on the traffi" .odel$ "al"ulate the "apa"ity to 6e shared in ea"h di.ension for the.aster &C 6y i.porting the initial target "apa"ities#

    2# ased on the "al"ulation results of .ultiple .aster &Cs$ "al"ulate the "apa"ity that

    need to 6e shared 6y the oerflow &C in ea"h di.ension#

    I.pa"t=

    Iur-p interfa"e 6oards i.pa"t 6oth the .aster &C and oerflow &C# Control-plane

    hardware and hardware li"enses i.pa"t 6oth the .aster &C and oerflow &C#

    !he following ta6le lists "apa"ity spe"ifi"ations in ea"h di.ension for load sharing#

    Table 1.2 Capa"ity spe"ifi"ations of ea"h di.ension for load sharing

    Description CapacityDimension

    *mpactedardware and

    ardware+icenseon t)e7asterRNC

    *mpactedardware andardware+icense on t)e

    Over;ow RNC

    Control-plane "apa"ity$

    whi"h i.pa"ts the"ontrol-plane hardware

    and hardware li"enses of

    the .aster &C and

    oerflow &C

    3erflow +u6s"ri6ers

    +u6s"ri6ers Capa"ity

    per >P:a

    >P:a?+P

    :a?+P:6?+P:"

    >P:a (CP)

    &C '"tie :ser

    Hardware Capa"ity(per 1000 '"tie

    :sers)3erflow '"tie :sers

    Iu?Iur traffi" "apa"ity$

    whi"h i.pa"ts the user-

    plane 6oards$ Iu?Iurinterfa"e hardware$ and

    user-plane hardware

    li"enses of the oerflow&C

    Iu C+ !raffi" (rl) Iu?Iur interfa"e 6oard$

    >P:a (:P)$ and

    I:a

    &C !hroughputHardware Capa"ity

    (per 50;6ps)

    oled etwor,

    Intelligen"e!hroughput

    %i"ense(50;6ps)

    Iu P+ % Payload!hroughput (;6ps)

    Iu P+ :% Payload

    !hroughput (;6ps)

    Iur % Payload!hroughput (;6ps)

    Iur :% Payload

    !hroughput (;6ps)

    Iu6 traffi" "apa"ity$whi"h i.pa"ts Iu6

    hardware of the

    oerflow &C

    Iu6 C+ !raffi" (rl) Iu6 interfa"e6oard

    Iu6 interfa"e 6oard

    Iu6 P+ % Payload

    !hroughput (;6ps)

    Iu6 P+ :% Payload

    !hroughput (;6ps)

    Iur-p traffi"$ whi"h

    i.pa"ts the Iur-p

    interfa"e hardware of6oth the .aster &C

    and oerflow &C

    Iur-p throughout

    (;6ps)

    Iur-p

    interfa"e

    6oard

    Iur-p interfa"e 6oard

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    24

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    31/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    'fter the "apa"ity re8uire.ents in ea"h di.ension are o6tained$ "al"ulate the 8uantity of

    re8uired hardware and hardware li"enses 6ased on the hardware spe"ifi"ations# or detailsa6out hardware spe"ifi"ations and how to "al"ulate 8uantity of hardware and hardware

    li"enses$ seeSRAN9.0&GBSS16.0&RAN16.0 BSC6910 Configuration Principles andSRAN9.0&GBSS16.0&RAN16.0 BSC6900 Configuration Principles#

    Table 1.3 &C role in a resour"e pool and the "orresponding di.ensions

    *tem Node Redundancy +oad ")aring

    &C &ole ;aster &C a",up &C ;aster &C 3erflow &C

    'ppli"a6le

    Produ"t

    +C900 and

    +C910

    +C910 +C900 and

    +C910

    +C910

    u.6er of

    &Cs

    +C900= 1G*

    +C910= 1G*

    1 +C900= 1G*

    +C910= 1G*

    1

    Custo.er

    Input

    u.6er of

    redundan"yodes

    u.6er of oerflow

    su6s"ri6ers

    %oad sharing .ode("ontrol-plane load

    sharing or user-

    plane load sharing)

    Inter.ediat

    e

    Para.eter

    Capa"ity

    re8uire.ents

    (inoling the

    "ontrol plane$user plane$ and

    trans.ission

    plane)

    ;aster &C

    "apa"ity

    re8uire.ents

    Capa"ity

    re8uire.ents

    (inoling the

    "ontrol plane$ userplane$ trans.ission

    plane$ and Iur-p

    interfa"e)

    ;aster &C

    "apa"ity

    re8uire.ents for

    load sharing andIur-p 6andwidth

    +oftware

    eature

    %i"ense

    &C in Pool

    ode

    &edundan"y(per ode)

    &C in Pool

    ;ultiple

    %ogi"al &Cs(0G*)(

    &C in Pool %oad

    +haring (per 500

    '"tie :sers)

    &C in Pool

    ;ultiple %ogi"al

    &Cs (0G*)(

    Hardware - >P:a

    (CP?:P) andI:a

    Iu?Iur?Iu6interfa"e 6oard

    >P:a (CP)

    Iur-p interfa"e 6oard

    >P:a$ I:a$

    Iu?Iur?Iu6?Iur-pinterfa"e 6oard

    Hardware%i"ense

    - &C!hroughput

    Hardware

    Capa"ity (per50;6ps)

    &C '"tie

    :ser Hardware

    Capa"ity (per

    1000 '"tie

    :sers)

    +C910=

    &C !hroughputHardware Capa"ity

    (per 50;6ps)

    oled etwor,

    Intelligen"e!hroughput

    %i"ense(50;6ps)

    +C900=

    &C '"tie:ser Hardware

    Capa"ity (per

    1000 '"tie:sers)

    &C

    !hroughput

    Hardware

    Capa"ity (per

    50;6ps)

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    25

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    32/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    *tem Node Redundancy +oad ")aring

    *00;6ps?15;6ps

    li"ense

    etwor,Intelligen"e

    !hroughput%i"ense(50;6ps)

    oled

    etwor,

    Intelligen"e!hroughput

    %i"ense(50;6ps

    )

    Capa"ityChange

    - Capa"ity "hangealues refer to

    the "apa"ities

    proided 6y the

    6a",up &C to.aster &Cs

    :nsharea6le"apa"ity of oerflow

    su6s"ri6ers on the

    "ontrol plane

    Capa"ity of

    su6s"ri6ers e7"eptoerflow su6s"ri6ers

    on the "ontrol plane$

    user plane$ andtrans.ission plane

    Iur-p interfa"e

    traffi"

    Capa"ity "hangealues refer to

    the "apa"ities

    proided 6y this

    &C to theoerflow

    su6s"ri6ers on

    the "ontrol

    plane$ userplane$ and

    trans.ission

    plane

    Iur-p interfa"etraffi"

    ote=

    In node redundan"y$ if .ore than one .aster &C is "onfigured$ the following two

    6a",up .odes apply=

    1# 1D1= !he hardware$ hardware li"ense$ or "apa"ity "hange is e8ual to the su. of

    6a",up re8uire.ents of all .aster &Cs# !his .ode applies to s"enarios where all.aster &Cs .ay 6e"o.e faulty at the sa.e ti.e#

    2# D1= !he hardware$ hardware li"ense$ or "apa"ity "hange is e8ual to the .a7i.u.

    alue of 6a",up re8uire.ents in ea"h di.ension of all .aster &Cs# !his .ode

    applies to s"enarios where only one .aster &C 6e"o.es faulty at one ti.e#

    In load sharing$ the "apa"ity$ hardware$ or hardware li"ense needs to 6e proided 6y theoerflow &C is the su. of the "orresponding re8uire.ents of all .aster &Cs#

    If an &C seres as 6oth the 6a",up &C and oerflow &C$ the greater "apa"ity

    re8uire.ent a.ong the two is used for this &C#

    If the .aster &C is "onfigured with optional seri"e 6oards$ su"h as the

    I:?+':?>C>$ the 6a",up or oerflow &C also needs to 6e "onfigured with su"h

    6oard# In node redundan"y$ if the .aster &C is "onfigured with the I:?+':?>C>$the 6a",up &C also needs to 6e "onfigured with the I:?+':?>C># 3therwise$

    related optional fun"tions on the logi"al &C of this 6a",up &C are unaaila6le when

    the .aster &C .alfun"tions# !he nu.6er of re8uired 6oards is "al"ulated 6ased on the6a",up "apa"ity ratio# In user-plane load sharing$ if the .aster &C is "onfigured with

    the I:?+':?>C>$ the oerflow &C also needs to 6e "onfigured with the

    I:?+':?>C># 3therwise$ related optional fun"tions are unaaila6le for oerflow

    su6s"ri6ers# !he nu.6er of re8uired 6oards is "al"ulated 6ased on the oerflow ratio#!he oerflow &C needs to 6e "onfigured with su"h 6oards as +':?>C> in "ontrol-

    plane load sharing only"ontrol plane load sharing only#

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    2

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    33/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    3.3 Capacity Planning Procedures #or RNC inPool Con$gurations

    3.3.1 -"C6

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    34/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    *nput Parameter =alue Description

    6y "usto.ers#

    &edundan"y Cells 0G!otal Cells !he alue of this para.eter "an 6e planned

    6y the "usto.er$ or a default alue "an 6ederied fro. the ratio of e$un$ancNo$e!#to To)al No$e!##

    &edundan"y +u6s"ri6ers 0G!otal+u6s"ri6ers

    !he alue of this para.eter "an 6e planned6y the "usto.er$ or a default alue "an 6e

    deried fro. the ratio of e$un$anc

    No$e!#to To)al No$e!##

    Input Para.eters for the ;aster &C in %oad +haring

    !hey are re8uire.ent para.eters for load sharing and are displayed only when the %oad

    +haring para.eter is set to Bes#

    3erflow +u6s"ri6ers 0G!otal+u6s"ri6ers

    Indi"ates the nu.6er of su6s"ri6ers that needto 6e transferred to the oerflow &C#

    Iur-p Interfa"e Para.eter

    +haring oard with Iur Bes?o Indi"ates whether to share an interfa"e 6oard

    with the Iur interfa"e#

    It is re"o..ended that the interfa"e 6oard

    not 6e shared with the Iur interfa"e when load

    sharing is ena6led#

    Table 1.2 3utput para.eters related to "apa"ity transferred fro. the .aster &C to the 6a",up

    &C or oerflow &C(for ode &edundan"y)

    Output Parameter Calculation 7et)od

    &edundan"y Iu6 C+ !raffi"

    (in"luding +H3) (rl)

    !he alue of this para.eter is "al"ulated 6y the traffi"

    .odel used 6y the lo"al &C 6ased on the nu.6er ofredundan"y su6s"ri6ers# !he "al"ulation .ethod is si.ilar

    to that used in se"tion +ingle +C900 i.ensioning

    Pro"ess in SRAN9.0&GBSS16.0&RAN16.0 BSC6900Configuration Principles#

    &edundan"y Iu6 C+ traffi" (in"luding +H3) (rl) &edundan"y su6s"ri6ers 7 OC+ oi"e penetration ratio

    7 C+ oi"e traffi" per su6s"ri6er per H 7 (1 D

    Proportion of +H3 for C+ oi"e traffi") D C+ datapenetration ratio 7 C+ data traffi" per su6s"ri6er per

    H 7 (1 D Proportion of +H3 for C+ data traffi") 7 2

    &edundan"y Iu6 P+ % payload throughput (in"luding

    +H3) (;6ps) &edundan"y su6s"ri6es 7 P+(in"luding &99 and H+P') penetration ratio 7 !otal P+

    throughput (H+P' and &99$ :%D%) per su6s"ri6er 7

    Proportion of % P+ throughput 7 O&99 share of % P+

    throughput per su6s"ri6er 7 (1 D Proportion of +H3 for

    P+ "all) D H+P' share of % P+ throughput per

    &edundan"y Iu6 P+ %

    Payload !hroughput(in"luding +H3) (;6ps)

    &edundan"y Iu6 P+ :%Payload!hroughput(in"luding +H3)

    (;6ps)

    &edundan"y Iu-C+ !raffi"(rl)

    &edundan"y Iu-P+ %

    Payload !hroughput (;6ps)

    &edundan"y Iu-P+ :%

    Payload !hroughput (;6ps)

    &edundan"y HC'

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    2

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    35/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    Output Parameter Calculation 7et)od

    su6s"ri6er

    &edundan"y Iu6 P+ :% payload throughput (in"luding

    +H3) (;6ps) &edundan"y su6s"ri6ers 7 P+(in"luding &99 and H+P') penetration ratio 7 !otal P+

    throughput (H+P' and &99$ :%D%) per su6s"ri6er 7Proportion of :% P+ throughput 7 (1 D Proportion of

    +H3 for P+ "all)

    &edundan"y Iu-C+ traffi" (rl) &edundan"y

    su6s"ri6ers 7 (C+ oi"e penetration ratio 7 C+ oi"etraffi" per su6s"ri6er per H D C+ data penetration

    ratio 7 C+ data traffi" per su6s"ri6er per H 7 2)

    &edundan"y Iu-P+ % payload throughput (;6ps)

    &edundan"y su6s"ri6ers 7 P+ (in"luding &99 and

    H+P') penetration ratio 7 !otal P+ throughput (H+P'

    and &99$ :%D%) per su6s"ri6er 7 Proportion of %P+ throughput

    &edundan"y Iu-P+ :% payload throughput (;6ps)

    &edundan"y su6s"ri6ers 7 P+ (in"luding &99 andH+P') penetration ratio 7 !otal P+ throughput (H+P'

    and &99$ :%D%) per su6s"ri6er 7 Proportion of :%

    P+ throughput

    &edundan"y HC' &edundan"y su6s"ri6ers 7 OC+

    oi"e penetration ratio 7 C+ oi"e "all per su6s"ri6erDC+ data penetration ratio 7 C+ data "all per su6s"ri6er

    per HD P+ (in"luding &99 and H+P') penetration

    ratio 7 P+ "all per su6s"ri6er per H

    NOTE

    or how to "al"ulate HC' per >P:a$ see the HC' "apa"ity

    of >P:a (for Control Plane) 6ased on gien traffi" .odel in

    se"tion +ingle +C910 i.ensioning Pro"ess in

    SRAN9.0&GBSS16.0&RAN16.0 BSC6910 ConfigurationPrinciples#

    &edundan"y a"tie users &edundan"y Iu-C+ (rl) D

    &edundan"y su6s"ri6ers 7 P+ (in"luding &99 and

    H+P') penetration ratio 7 P+ "all per su6s"ri6er per

    H 7 ;ean holding ti.e (;H!) in CH?H?'CHstate per P+ "all ?*00)

    &edundan"y online users &edundan"y a"tie users D&edundan"y su6s"ri6ers 7 P+ (in"luding &99 and

    H+P') penetration ratio 7 P+ "all ti.es per su6s"ri6erin H 7 ;ean holding ti.e (;H!) in PCH per P+

    "all?*00

    &edundan"y "ontrol plane a"tie users (!otal

    su6s"ri6ers - 3erflow su6s"ri6ers) 7 O(C+ oi"e

    penetration ratio 7 C+ oi"e traffi" per su6s"ri6er perH D C+ data penetration ratio 7 C+ data traffi" per

    su6s"ri6er per H 7 2) D P+ (in"luding &99 and

    H+P') penetration ratio 7 P+ "all per su6s"ri6er per

    H 7 ;ean holding ti.e (;H!) in CH?H?'CH

    state per P+ "all?*00)

    HC' per >P:a

    &edundan"y '"tie :sers

    &edundan"y 3nline :sers

    &edundan"y Control Plane

    '"tie :sers

    &edundan"y Control Plane3nline :sers

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    29

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    36/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    Output Parameter Calculation 7et)od

    &edundan"y "ontrol plane online users &edundan"y

    "ontrol plane a"tie users D (!otal su6s"ri6ers -

    3erflow su6s"ri6ers) 7 P+ (in"luding &99 and H+P')penetration ratio 7 P+ "all ti.es per su6s"ri6er in H 7

    ;ean holding ti.e (;H!) in PCH per P+ "all?*00

    &edundan"y odes Input alue of the e$un$anc No$e!#para.eter

    &edundan"y Cells Input alue of the e$un$anc "ell#para.eter

    &edundan"y P+ !hroughput+upported 6y I: (;6ps)

    Indi"ates the I: "apa"ity that needs to 6e proided 6ythe 6a",up &C#

    !he alue of this para.eter is "al"ulated 6y &edundan"y

    Iu-P+ % data plane payload throughput (;6ps)

    D&edundan"y Iu-P+ :% data plane payload throughput

    (;6ps) when the following features are ena6led= A&-0201*2 Ae6 rowsing '""eleration$ A&-0201** P2P

    ownloading &ate Control during usy Hour$ A&-

    150252 P:a(CP)

    Indi"ates oerflow su6s"ri6ers on the "ontrol plane of ea"h

    >P:a on an oerflow &C$ whi"h is "al"ulated 6y thefollowing for.ula=

    3erflow su6s"ri6ers "apa"ity per >P:a (CP) +upportedsu6s"ri6er nu.6er per >P:a (for Control Plane)? $ where

    *F for "ontrol plane load sharing$ 55F for user plane

    6inding with "ontrol plane load sharing#

    NOTE

    or how to "al"ulate +upported su6s"ri6er nu.6er per >P:a (for

    Control Plane)$ see SRAN9.0&GBSS16.0&RAN16.0 BSC6910

    Configuration Principles.

    3erflow '"tie :sers !he following for.ulas are deried fro. the nu.6er of

    oerflow su6s"ri6ers and the traffi" .odel=

    3erflow a"tie users 3erflow su6s"ri6ers 7 (C+ oi"e

    penetration ratio 7 C+

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    37/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    OutputParameter

    Calculation 7et)od

    "all?*00)

    3erflow online users 3erflow a"tie users D 3erflowsu6s"ri6ers 7 P+ (in"luding &99 and H+P') penetration ratio

    7 P+ "all ti.es per su6s"ri6er in H 7 ;ean holding ti.e

    (;H!) in PCH per P+ "all?*00

    Iur-p throughout (;6ps) 10;6it?s for &C in Pool 6ase 6andwidth#

    or "ontrol plane load sharing$

    Iur-p throughout 10 D 3erflow a"tie users 7 20?1000#

    or user plane 6inding with "ontrol plane load sharing$

    Iur-p throughout 10 D 3erflow '"tie :sers 7 15?1000 D;aster &C Cell nu.6er 7 10?1000 7 3erflow

    su6s"ri6ers?!otal su6s"ri6ers D '!; ode ratio of

    3erflow &C 7 3erflow su6s"ri6er 7 (Proportion of +H3for C+

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    38/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    OutputParameter

    Calculation 7et)od

    su6s"ri6ers 7 P+ (in"luding &99 and H+P') penetration ratio7 !otal P+ throughput (H+P' and &99$ :%D%) per

    su6s"ri6er 7 Proportion of % P+ throughputQ

    3erflow Iu-P+ :% payload throughput (;6ps) 3erflow

    su6s"ri6ers 7 P+ (in"luding &99 and H+P') penetration ratio7 !otal P+ throughput (H+P' and &99$ :%D%) per

    su6s"ri6er 7 Proportion of :% P+ throughput

    u.6er of 3erflow

    odes

    !hese para.eters are alid only when user-plane load sharing

    6inding with "ontrol-plane load sharing is ena6led (when the

    #er-lane oa$ S,aring !in$ing *i), "on)rol-lane oa$

    S,aringpara.eter is set to e#)# 3therwise$ this para.eter is

    set to 0#

    u.6er of 3erflow odes u.6er of total odes ofthe .aster &C

    u.6er of 3erflow Cells u.6er of total "ells of the

    .aster &C

    u.6er of 3erflow

    Cells

    3erflow P+!hroughput +upported

    6y I: (;6ps)

    Indi"ates the P+ "apa"ity that needs to 6e proided 6y the I:of the oerflow &C#

    !he alue of this para.eter is "al"ulated 6y 3erflow Iu-P+ %

    payload throughput (;6ps)D3erflow Iu-P+ :% payload

    throughput (;6ps) when user-plane load sharing 6inding with

    "ontrol-plane load sharing is ena6led (when the #er-lane

    oa$ S,aring !in$ing *i), "on)rol-lane oa$ S,aring

    para.eter is set to e#) and the following features are ena6led=A&-0201*2 Ae6 rowsing '""eleration$ A&-0201**

    P2P ownloading &ate Control during usy Hour$ A&-150252 3:"?>3:e?>2" is "onfigured for the Iur interfa"e

    and no traffi" is pro"essed oer the Iur-p interfa"e#

    2# !he alue of this para.eter is 2when the

    >3:"?>3:e?>2" is "onfigured for the Iur interfa"e#

    Ahen load sharing is used=

    It is re"o..ended that the Iur-p and Iur interfa"es not share the

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    *2

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    39/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    OutputParameter

    Calculation 7et)od

    sa.e interfa"e 6oard#

    u.6er of Iur-p Interfa"e oards is "al"ulated 6y the followingu.6er of Iur-p Interfa"e oards Iur-p throughout

    (;6ps)?Interfa"e Iu6 throughput spe"ifi"ations

    !he spe"ifi"ations of a 6oard depend on the port type# or

    details a6out the Iu6 throughput of interfa"e 6oards$ see se"tionInterfa"e oards in SRAN9.0&GBSS16.0&RAN16.0BSC6900Configuration Principles#

    u.6er of the

    +P:6?+P:" oards

    If load sharing is not used$ the nu.6er of +P:s on the .aster

    &C is not affe"ted#

    If load sharing is used$ the unsharea6le part of an oerflowsu6s"ri6er needs to 6e pro"essed 6y the +P: on the .aster

    &C# !he nu.6er of re8uired +P:s is "al"ulated 6y thefollowing for.ula=

    u.6er of +P: 6oards 3erflow su6s"ri6ers 7 '?

    (+upported su6s"ri6er nu.6er per +P:)$ where ' is 5/F for"ontrol plane load sharing only$ 5*F for user plane 6inding

    "ontrol plane load sharing#

    !he nu.6er of total +P: 6oards re8uired on a .aster &C is

    "al"ulated 6y the following for.ula= u.6er of +P: 6oards &3::P O(!otal su6s"ri6ers - 3erflow

    su6s"ri6ers)?+upported su6s"ri6er nu.6er per +P: D

    3erflow su6s"ri6ers 7 '?+upported su6s"ri6er nu.6er per

    +P:#

    NOTE

    or how to "al"ulate +upported su6s"ri6er nu.6er per +P:$ see

    SRAN9.0&GBSS16.0&RAN16.0 BSC6900 Configuration Principles#

    u.6er of the P:e

    oards

    If user-plane load sharing 6inding with "ontrol-plane load

    sharing is not used$ the nu.6er of P:e 6oards on the

    .aster &C is not affe"ted#

    If user-plane load sharing 6inding with "ontrol-plane loadsharing is used$ the nu.6er of re8uired P:e 6oards

    de"reases on the .aster &C (or the nu.6er re.ains 6ut the

    .a7i.u. CP: load de"reases)# !he nu.6er of P:e6oards re8uired on the .aster &C after oerflow

    su6s"ri6ers are transferred is "al"ulated 6y the followingfor.ula (the target aerage CP: load is /0F)=

    1# Csun (Iu6 C+ rlang di.ension) OIu6 C+ traffi" -

    3erflow Iu6 C+ traffi" (in"luding +H3)?**50

    2# Psa (Iu6 P+ throughput traffi" ;6ps) (!otalsu6s"ri6ers - 3erflow su6s"ri6ers) 7 P+ (in"luding &99

    and H+P') penetration ratio 7 !otal P+ throughput

    (H+P' and &99$ :%D%) per su6s"ri6er 7 RProportion of% P+ throughput 7 O&99 share of % P+ throughput per

    su6s"ri6er 7 (1 D Proportion of +H3 for P+ "all) D

    H+P' share of % P+ throughput per su6s"ri6er D

    Proportion of :% P+ throughput 7 (1 D Proportion of

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    **

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    40/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    OutputParameter

    Calculation 7et)od

    +H3 for P+ "all)S

    *# Psun (P+ throughput di.ension) Psa ?'"tual P+throughput "apa6ility of the P:e

    4# 'uun ('"tie user di.ension) (!otal su6s"ri6ers -

    3erflow su6s"ri6ers) 7 (C+ oi"e penetration ratio 7 C+

    oi"e traffi" per su6s"ri6er per H D C+ data penetrationratio 7 C+ data traffi" per su6s"ri6er per H D P+

    (in"luding &99 and H+P') penetration ratio 7 P+ "all per

    su6s"ri6er per H 7 ;ean holding ti.e (;H!) in

    CH?H?'CH state per P+ "all (se") ?*00)?50

    5# Cun (Cell di.ension) !otal "ells?*00

    # P:eu.6er &3::PO;a7 (Csun D Psun$ 'uun$Cun)

    NOTE

    !otal su6s"ri6ers refer to those su6s"ri6ers that need to 6e pro"essed 6y

    the logi"al &C of the .aster physi"al &C# !otal su6s"ri6ers "onsist of

    two parts= oerflow su6s"ri6ers and su6s"ri6ers re.ained on the .aster&C# In user-plane load sharing 6inding with "ontrol-plane load sharing$

    the "ontrol-plane data and user-plane data of oerflow su6s"ri6ers are

    6oth pro"essed on the oerflow &C# 3nly data of those e7"ept the

    oerflow su6s"ri6ers is pro"essed on the .aster &C# !he nu.6er of

    su"h su6s"ri6ers is "al"ulated 6y dedu"ting oerflow su6s"ri6ers fro.

    total su6s"ri6ers# or the traffi" .odel related to the pre"eding for.ula$see SRAN9.0&GBSS16.0&RAN16.0 BSC6900 Configuration Principles.

    or how to ealuate the a"tual P+ throughput "apa6ility and for details

    a6out the traffi" .odel$ see SRAN9.0&GBSS16.0&RAN16.0 BSC6900

    Configuration Principles.

    >2" (Iu6) If user-plane load sharing 6inding with "ontrol-plane loadsharing is not used$ the nu.6er of Iu6 interfa"e 6oards on the

    .aster &C is not affe"ted#

    If user-plane load sharing 6inding with "ontrol-plane load

    sharing is used$ the nu.6er of re8uired Iu6 interfa"e 6oards

    de"reases on the .aster &C (or the nu.6er re.ains 6ut the.a7i.u. CP: load de"reases)# !he nu.6er of Iu6 interfa"e

    6oards for oerflow su6s"ri6ers on the user plane needs to 6e

    dedu"ted 6y the nu.6er of Iu6 interfa"e 6oards for totalsu6s"ri6ers on the +C910#

    1# Csn6nt (C+ rlang di.ension) OIu6 C+ traffi" -3erflow Iu6 C+ traffi" (in"luding +H3)?oard rlang

    spe"ifi"ations

    2# Psa Iu6 P+ throughput - 3erflow Iu6 P+ % payload

    throughput (in"luding +H3) - 3erflow Iu6 P+ :%payload throughput (in"luding +H3)

    *# Psn6nt (P+ throughput di.ension) P+a?oard Iu6 P+

    throughput

    4# '"t:sern6nt ('"tie user di.ension) (Iu6 a"tie users

    (CI?:P) - 3erflow a"tie users 7 (1 D Proportion of

    +H3 for C+ traffi") 7 *)?oard :PCI

    5# 6n6nt (ode di.ension) !otal odes ?oard

    >3:"?>3:e (Iu6)

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    *4

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    41/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    OutputParameter

    Calculation 7et)od

    ode spe"ifi"ations

    # +essn6nt ("onne"tion di.ension) (!otal su6s"ri6ers -3erflow su6s"ri6ers) 7 OC+ oi"e penetration ratio 7

    (C+ oi"e "all per su6s"ri6er 7 2 D C+ oi"e "all per

    su6s"ri6er 7 Handoer ti.es per C+ oi"e "all 7 1) D C+data penetration ratio 7 (C+ ata "all per su6s"ri6er 7 2 D

    C+ ata "all per su6s"ri6er 7 Handoer ti.es per C+

    ata "all 7 1) D P+ (in"luding &99 and H+P')

    penetration ratio 7 (P+ "all per su6s"ri6er per H 7 * DP+ "all per su6s"ri6er per H 7 Handoer ti.es per P+

    "all DP+ "all per su6s"ri6er per H 7 P+ "hannel swit"h

    per P+ "all 7 1 D P+ "all per su6s"ri6er per H 7 Cellupdate per P+ "all 7 1) D '+ signaling per su6s"ri6er

    per H 7 1?*00?oard sessions spe"ifi"ations

    /# I:I!u.6er ;a7(Csn6nt D Psn6nt$

    '"t:sern6nt$ 6n6nt$ sessn6nt)

    :3I" (Iu-C+$ Iu-P+$and Iur)

    If user-plane load sharing 6inding with "ontrol-plane loadsharing is not used$ the nu.6er of Iu?Iur interfa"e 6oards on

    the .aster &C is not affe"ted#

    If user-plane load sharing 6inding with "ontrol-plane load

    sharing is used$ the nu.6er of re8uired Iu6 interfa"e 6oardsde"reases on the .aster &C (or the nu.6er re.ains 6ut the

    .a7i.u. CP: load de"reases)# !he nu.6er of Iu?Iur

    interfa"e 6oards for oerflow su6s"ri6ers on the user plane

    needs to 6e dedu"ted 6y the nu.6er of Iu?Iur interfa"e6oards for total su6s"ri6ers on the +C900#

    1# Csn"nt (C+ rlang di.ension) OIu C+ traffi" -

    3erflow Iu-C+ !raffi" (in"luding +H3)?oard rlang

    spe"ifi"ations

    2# Psa Iu P+ throughput - 3erflow Iu-P+ % payload

    throughput (in"luding +H3) - 3erflow Iu-P+ :%payload throughput(in"luding +H3)

    *# Psnpnt (P+ throughput di.ension) P+a?oard P+

    throughput spe"ifi"ations

    4# 3n:sernpnt (3nline user di.ension) (3nline users -

    3erflow online users)?oard I:P+ online userspe"ifi"ations

    5# +essnpnt (I:P+ "onne"tion di.ension) OIu-P+ sessionset-up and release re8uire.ent in H - 3erflow

    su6s"ri6ers 7 P+ (in"luding &99 and H+P') penetration

    ratio 7 P+ "all ti.es per su6s"ri6er in H 7 (1 D P+"hannel swit"h per P+ "all 7 0#5 D Cell update per P+ "all

    7 0#5)?*00?oard sessions spe"ifi"ations

    # I:I!u.6er ;a7(Csn6nt D Psn6nt$

    '"t:sern6nt$ 6n6nt$ +essnpnt)

    >2" (Iu-C+$ Iu-P+$and Iur)

    >3:"?>3:e (Iu-C+$

    Iu-P+$ and Iur)

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    *5

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    42/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    OutputParameter

    Calculation 7et)od

    NOTE

    or "apa"ity para.eters related to !otal su6s"ri6ers$ see se"tion +ingle +C900 i.ensioning

    Pro"ess in SRAN9.0&GBSS16.0&RAN16.0 BSC6900 Configuration Principles#

    !he "al"ulation results are not the a"tual nu.6ers of 6oards to 6e "onfigured# !he "al"ulation results

    need to 6e dou6led in the 1D1 6a",up .ode and one .ore 6oard needs to 6e added in the D1 6a",up

    .ode#

    Table 1.5 3utput para.eters related to software li"enses in the &C in Pool "onfiguration for a

    +C900

    Feature "o#tware +icense*tem

    Calculation 7et)od

    &C in Pool ode &edundan"y (per

    ode)

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    43/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    Table 1.1 Input "ontrol para.eters

    *nputParameter

    =alue Description

    %ogi"al ;aster &C Capa"ity Para.eters

    !otal +u6s"ri6ers Indi"ates the nu.6er of su6s"ri6ers$ odes$ or

    "ells "onfigured on a logi"al .aster &C#

    NOTE

    !he logi"al .aster &C refers to the logi"al &C that

    6elongs to the .aster &C#

    !otal odes

    !otal Cells

    Control Para.eters

    Peer site &C !ype

    in the &esour"e Pool

    +C900?

    +C910?

    +C900E

    +C910

    Indi"ates the I of the peer &C that for.s a

    resour"e pool with the lo"al &C# ' +C910 "an

    for. a resour"e pool with +C900s$ +C910s$ or

    6oth +C900s and +C910s# Bou need to findout whi"h one of the pre"eding s"enarios is used#

    NPeer +C910

    &C1

    Peer &C

    I

    !his para.eter is alid when the eer Si)e N"

    T'e in ),e e#ource oolpara.eter is set to

    !S"6910or !S"6900!S"6910#

    NPeer +C910&C2

    Peer &CI

    !his para.eter is alid when the eer Si)e N"

    T'e in ),e e#ource oolpara.eter is set to

    !S"6910or !S"6900!S"6910and .ore than

    one peer +C910 is "onfigured#

    NPeer +C910

    &C*

    Peer &C

    I

    !his para.eter is alid when the eer Si)e N"

    T'e in ),e e#ource oolpara.eter is set to!S"6910or !S"6900!S"6910and .ore thantwo peer +C910s are "onfigured#

    NPeer +C900

    &C1

    Peer &C

    I

    !his para.eter is alid when the eer Si)e N"

    T'e in ),e e#ource oolpara.eter is set to

    !S"6900or !S"6900!S"6910#

    NPeer +C900&C2

    Peer &CI

    !his para.eter is alid when the eer Si)e N"

    T'e in ),e e#ource oolpara.eter is set to

    !S"6900or !S"6900!S"6910and .ore than

    one peer +C900 is "onfigured#

    NPeer +C900&C* Peer &CI !his para.eter is alid when the eer Si)e N"T'e in ),e e#ource oolpara.eter is set to

    !S"6900or !S"6900!S"6910and .ore than

    two peer +C900s are "onfigured#

    ode &edundan"y B+?3 Indi"ates whether node redundan"y is supported#

    N;aster &C inode &edundan"y

    B+?3 Indi"ates whether the lo"al &C seres as the.aster &C in node redundan"y# !his para.eter is

    alid when the eer Si)e N" T'e in ),ee#ource oolpara.eter is set to !S"6910or

    !S"6900!S"6910#

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    */

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    44/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    *nputParameter

    =alue Description

    Na",up &C inode &edundan"y

    B+?3 Indi"ates whether the lo"al &C seres as the6a",up &C in node redundan"y#

    NN&edundan"y ;ode

    in a",up &C

    1D1?D1 Indi"ates whether the 6a",up .ode is 1D1(+u.) or

    D1(;a7)# !his para.eter is alid only when .orethan one peer &C is "onfigured#

    %oad +haring B+?3 Indi"ates whether load sharing is supported#

    N;aster &C in

    %oad +haring

    B+?3 Indi"ates whether the lo"al &C seres as the

    .aster &C in load sharing# !his para.eter is alid

    when the eer Si)e N" T'e in ),e e#ource

    oolpara.eter is set to !S"6910or

    !S"6900!S"6910#

    NN:ser-Plane %oad+haring anding with

    Control-Plane %oad

    +haring(;aster &C)

    B+?3 Indi"ates whether the .aster &C supports user-plane load sharing 6inding with "ontrol-plane load

    sharing#

    N3erflow &C in%oad +haring

    B+?3 Indi"ates whether the lo"al &C seres as theoerflow &C in load sharing#

    NN:ser-Plane %oad+haring anding with

    Control Plane %oad

    +haring (3erflow

    &C)

    B+?3 Indi"ates whether the oerflow &C supports user-plane load sharing 6inding with "ontrol-plane load

    sharing#

    +haring oard with

    Iur

    B+?3 Indi"ates whether to share an interfa"e 6oard with

    the Iur interfa"e#

    It is re"o..ended that the 6oard 6e shared with the

    Iur interfa"e when 10 > 6oards are "onfigured forthe Iur interfa"e$ 6ut not 6e shared with the Iur

    interfa"e when 10 > 6oards are not used for the

    Iur interfa"e and when load sharing is used#

    2# ' +C910 seres as the .aster &C in node redundan"y or load sharing#

    Table 1.2 Input para.eters when a +C910 seres as the .aster &C

    *nputParameter

    =alue Description

    Input Para.eters &elated to the ;aster &C in ode &edundan"y

    &edundan"y odes 0G!otal odes Indi"ates the nu.6er of odes that need to 6e6a",ed up on the 6a",up &C$ whi"h is

    planned 6y "usto.ers#

    &edundan"y Cells 0G!otal Cells Indi"ates the nu.6er of "ells that need to 6e

    6a",ed up on the 6a",up &C$ whi"h "an 6e

    Issue 02 (2014-09-15) Huawei Proprietary and Confidential

    Copyright Huawei

    !e"hnologies Co#$ %td#

    *

  • 8/9/2019 RAN16.0 RNC in Pool Configuration Principles 02 (20140915)

    45/65

    &'1#0 &C in Pool Configuration Prin"iples * &C Capa"ity i.ensioning

    *nputParameter

    =alue Description

    planned 6y "usto.ers or 6e "al"ulated 6y thefollowing for.ula= !otal Cells 7 &edundan"y

    odes?!otal odes

    &edundan"y+u6s"ri6ers

    0G!otal+u6s"ri6ers

    Indi"ates the nu.6er of su6s"ri6ers that needto 6e 6a",ed up on the 6a",up &C$ whi"h "an

    6e planned 6y "usto.ers or 6e "al"ulated 6y

    the following for.ula= !otal +u6s"ri6ers 7

    &edundan"y odes?!otal odes

    NOTE

    !otal su6s"ri6ers refer to the total su6s"ri6ers on the

    lo"al logi"al &C#

    Input Para.eters &elated to the ;aster &C in %oad +haring

    3erflow +u6s"ri6ers 0G!otal+u6s"ri6ers

    Indi"ates the nu.6er of oerflow su6s"ri6ers$whi"h is planned 6y "usto.ers#

    Infor.ation proided in the pre"eding ta6le is the sa.e as that for +C900s#

    Table 1.3 3utput para.eters related to "apa"ity transferred to the 6a",up &C(for ode

    &edundan"y)

    Output Parameter Calculation 7et)od

    Para.eters &elated to Capa"ity !ransferred fro. the ;aster &C to the a",up &C inode &edundan"y

    &edundan"y Iu6 C+ !raffi"

    (in"luding +H3) (rl)

    !he alue of this para.eter is "al"ulated 6y the traffi"

    .odel used 6y the lo"al &C