WCDMA IU Bandwidth Calculation Tool-20100629-A

Huawei U1211 Terminals APN Setting Guide

WCDMA IU Bandwidth Calculation Tool User ManualInternal Only

WCDMA IU Bandwidth Calculation ToolDrafted by:Kang Heng PuhDate:2010-06-29

Reviewed by:Date:

Approved by:Date:

User Guide

1. This template includes the work sheet of "RAN Traffic Model", "IUCS", "IUPS", "IuB", "IUR", "Converter", and "Reference".2. The user need to input the data in work sheet of "RAN Traffic Model", "IUCS", "IUPS", "IuB", and "IUR".3. This template will calculate the total bandwidth needed for each ATM- and IP-based interface; include IUCS, IUPS, IuB and IUR based on the RAN traffic model input at worksheet "RAN Traffic Model". Beside that, this template will calculate the bandwidth of user plane need to be configured for IUCS, IUPS and IUR.4. Firstly, input the data at worksheet "RAN Traffic Model" according to traffic model provided:

a) This template is design maximum used for 10 RNCs.

b) Input the RNC Name at the row of "RNC Name" . Without RNC Name provided, the template will ignore all the data input under this RNC.

c) Select/Specified the RNC version . This is to use to calculate some of recommended data used for each version of RNCs. Currently support for RAN10, RAN11, RAN11.1 and RAN12.

d) Input the RAN Traffic Model Parameters RNC by RNC (column by column), which highligted with .

e) All the Parameters have default value (Huawei experience/recommend value) which highlighted with . If user didn't input the value, the default value will take in place.

5. Secondly, input the data at worksheet "IUCS":

a) Most of the data related with Traffic Model parameter will auto fill in when user input in worksheet "RAN Traffic Model", which highlighted with .

b) User has to input parameters which highlighted with . If user didn't input the value, the Huawei recommend/default value will take in place.

c) In this section, the total bandwidth for IUCS control plane, user plane and total IUCS interface throughput will be calculated.

d) Beside that, this template also will calculate the total bandwidth for each signaling and AAL2Paths after user inputs total links would like to configure for signaling and AAL2Paths.

(The minimum bandwidth for each signaling is 256kbps)

e) For user plane data, user can choose to calculate how many paths to be configured by input the bandwidth of each path

(Huawei recommend value, 4 Mbps for each path).6. Thirdly, input the data at worksheet "IUPS":

c) In this section, the total bandwidth for IUPS control plane and user plane will be calculated.

d) This template also will calculate the total bandwidth for each signaling links after user input total links to be configured for IuPS signaling.

(The minimum bandwidth for signaling is 256kbps.)

e) If the total bandwidth of user plane throughput higher than 150Mbps, the cell will highlighted with indicates that 1 physical link is not enough to cover IuPS interface.

(Maximum physical bandwidth for 1 STM-1 is 155Mbps).7. Fourthly, input the data at worksheet "IUB":

c) In this section, IUB USER PALNE PAYLOAD THROUGHPUT, IUB USER PALNE PAYLOAD THROUGHPUT and IUB OAM THROUGHPUT will be calculated.

d) The value of IUB USER PALNE PAYLOAD THROUGHPUT and IUB USER PALNE PAYLOAD THROUGHPUT used for IUR (ATM) bandwidth calculation.

e) For the configured bandwidth of signaling links and user plane paths for each NodeB, please refer to worksheet "Reference" for details based on different scenarios.8. Lastly, input the data at worksheet "IUR":

a) This section is only applicable if there is relationship with cells in neighboring RNCs.

b) Most of the data related with Traffic Model parameter will auto fill in when user input in worksheet "RAN Traffic Model", which highlighted with .

c) User has to input parameters which highlighted with . If user didn't input the value, the Huawei recommend/default value will take in place.

d) In this section, IUR USER PALNE PAYLOAD THROUGHPUT and IUR CONTROL PALNE PAYLOAD THROUGHPUT will be calculated.

e) This template also will calculate the total bandwidth for each signaling after user inputs total links would like to configure for signaling links.

(The minimum bandwidth for each signaling is 256kbps)

f) Users have to input the max. bandwidth for 1 AAL2Path to be configured, otherwise the bandwidth of AAL2Path is same with the "Total IUPS User Plane Throughput (ATM Layer)".

g) The type and quantity of AAL2Path recommended for IUR: 2 Paths for RT, 2 Paths for NRT and 2 Paths for UBR. Therefore:

IF is 1, totally 6 Paths need to configure: 2 for RT, 2 for NRT and 2 for UBR with BW specified in .

IF is x, then, 6x Paths need to configure: 2x for RT, 2x for NRT and 2x for UBR with BW specified in .

In IP based (RAN 11 onward), if NRNC is Huawei RNC, it is recommend to configure 1 IPPath with type QoSPATH.

In IP based (RAN 11 onward), if NRNC is not Huawei RNC, it is recommend to configure 1 IPPath each for path type EF, AF43, AF23 and AF13.9. This template also provides a converter tool between CPS and KBPS conversion. Please refer to the worksheet "Converter".

a) User has to input the value of bandwidth at the cell highlighted with .

b) Select "CPS" or "KBPS". If user wants to convert from CPS to KBPS, please select "CPS", otherwise, select "KBPS".WCDMA IU BANDWIDTH CALCULATION TOOL

The WCDMA IU Bandwidth Calculation Tool is shown in the embedded file below:

Huawei Confidential. No disclosure without permission.Page 2 of 3

_1339336649.xlsRevision

Revision Record

VersionDateDescriptionPIC

1.026-May-10Initial versionKang Heng Puh

Instruction

User Guide

NoDescription

1This template includes the work sheet of "RAN Traffic Model", "IUCS", "IUPS", "IuB", "IUR", "Converter", and "Reference".

2The user need to input the data in work sheet of "RAN Traffic Model", "IUCS", "IUPS", "IuB", and "IUR".

3This template will calculate the total bandwidth needed for each ATM- and IP-based interface, include IUCS, IUPS, IuB and IUR based on the RAN traffic model input at worksheet "RAN Traffic Model". Beside that, this template will calculate the bandwidth of user plane need to be configured for IUCS, IUPS and IUR.

4Firstly, input the data at worksheet "RAN Traffic Model" according to traffic model provided:a) This template is design maximum used for 10 RNCs.b) Input the RNC Name at the row of "RNC Name" . Without RNC Name provided, the template will ignore all the data input under this RNC.c) Select/Specified the RNC version . This is to use to calculate some of recommended data used for each version of RNCs. Currently support for RAN10, RAN11, RAN11.1 and RAN12.d) Input the RAN Traffic Model Parameters RNC by RNC (column by column), which highligted with .e) All the Parameters have default value (Huawei experience/recommend value) which highlighted with . If user didn't input the value, the default value will take in place.

5Secondly, input the data at worksheet "IUCS":a) Most of the data related with Traffic Model parameter will auto fill in when user input in worksheet "RAN Traffic Model", which highlighted with .b) User has to input parameters which highlighted with . If user didn't input the value, the Huawei recommend/default value will take in place. c) In this section, the total bandwidth for IUCS control plane, user plane and total IUCS interface throughput will be calculated. d) Beside that, this template also will calculate the total bandwidth for each signaling and AAL2Paths after user inputs total links would like to configure for signaling and AAL2Paths. ( The minimum bandwidth for each signaling is 256kbps)e) For user plane data, user can choose to calculate how many paths to be configured by input the bandwidth of each paths (Huawei receommend value, 4 Mbps for each path).

6Thirdly, input the data at worksheet "IUPS":a) Most of the data related with Traffic Model parameter will auto fill in when user input in worksheet "RAN Traffic Model", which highlighted with .b) User has to input parameters which highlighted with . If user didn't input the value, the Huawei recommend/default value will take in place. c) In this section, the total bandwidth for IUPS control plane and user plane will be calculated. d) This template also will calculate the total bandwidth for each signaling links after user input total links to be configured for IuPS signaling. (The minimum bandwidth for signaling is 256kbps.)e) If the total bandwidth of user plane throughput higher than 150Mbps, the cell will highlighted with indicates that 1 physical link is not enough to cover IuPS interface. (Maximum physical bandwidth for 1 STM-1 is 155Mbps).

7Fourthly, input the data at worksheet "IUB":a) Most of the data related with Traffic Model parameter will auto fill in when user input in worksheet "RAN Traffic Model", which highlighted with .b) User has to input parameters which highlighted with . If user didn't input the value, the Huawei recommend/default value will take in place. c) In this section, IUB USER PALNE PAYLOAD THROUGHPUT, IUB USER PALNE PAYLOAD THROUGHPUT and IUB OAM THROUGHPUT will be calculated. d) The value of IUB USER PALNE PAYLOAD THROUGHPUT and IUB USER PALNE PAYLOAD THROUGHPUT used for IUR (ATM) bandwidth calculation.e) For the configured bandwidth of signaling links and user plane paths for each NodeB, please refer to worksheet "Reference" for details based on different scenarios.

8Lastly, input the data at worksheet "IUR":a) This section is only applicable if there is relationship with cells in neighbouring RNCs.b) Most of the data related with Traffic Model parameter will auto fill in when user input in worksheet "RAN Traffic Model", which highlighted with .c) User has to input parameters which highlighted with . If user didn't input the value, the Huawei recommend/default value will take in place. d) In this section, IUR USER PALNE PAYLOAD THROUGHPUT and IUR CONTROL PALNE PAYLOAD THROUGHPUT will be calculated. e) This template also will calculate the total bandwidth for each signaling after user inputs total links would like to configure for signaling links. ( The minimum bandwidth for each signaling is 256kbps)f) Users has to input the max. bandwidth for 1 AAL2Path to be configured, otherwise the bandwidth of AAL2Path is same with the "Total IUPS User Plane Throughput (ATM Layer)".g) The type and quantity of AAL2Path recommended for IUR: 2 Paths for RT, 2 Paths for NRT and 2 Paths for UBR. Therefore: ** IF is 1, totally 6 Paths need to configure: 2 for RT, 2 for NRT and 2 for UBR with BW specified in . ** IF is x, then, 6x Paths need to configure: 2x for RT, 2x for NRT and 2x for UBR with BW specified in .h) ** In IP based (RAN 11 onward), if NRNC is Huawei RNC, it is recommend to configure 1 IPPath with type QoSPATH.i) ** In IP based (RAN 11 onward), if NRNC is not Huawei RNC, it is recommend to configure 1 IPPath each for path type EF, AF43, AF23 and AF13.

9This template also provide a converter tool between CPS and KBPS conversion. Please refer to the worksheet "Converter".a) User has to input the value of bandwidth at the cell highlighted with .b) Select "CPS" or "KBPS". If user wants to convert from CPS to KBPS, please select "CPS", otherwise, select "KBPS".

Converter

CPS / KBPS Conversion Tool

Please input the value of Bandwidth:35000CPS

The converted value of Bandwidth:14840KBPS

14.84MPBS

Remark:

The conversion between the kbit/s and cell/s is as follows:

1 cell/s = ((1 x 53 x 8)/1000) kbit/s

1 kbit/s = ((1 x 1000)/(53 x 8)) cell/s

RAN Traffic Model

RNC Name :RNC 1

RNC Version :RAN 11

Total Subscribers of target network10000

Total NodeBs Amount of the RNC376

Total Cells Amount of the RNC10000

User plane traffic parameterUnitDefault ValueTraffic ValueTraffic ValueTraffic ValueTraffic ValueTraffic ValueTraffic ValueTraffic ValueTraffic ValueTraffic ValueTraffic Value

CS voice penetration ratio%100100100100100100100100100100100

CS data (Video Phone 64k) penetration ratio%50100100100100100100100505050

Voice Traffic per CS voice sub in BH(Erlang )Erl0.0180.0180.0180.0180.0180.0180.0180.0180.0180.0180.018

CS data traffic per CS data (Video Phone 64k) sub in BH (Erlang)Erl0.00180.00180.00180.00180.00180.00180.00180.00180.00180.00180.0018

CS voice call duration (sec.)sec6060606060606060606060

CS data (Video Phone 64k) call duration (sec.)sec6060606060606060606060

PS (Including R99 and HSPA) Penetration Ratio (% of Total Subscribers)%8080808080808080808080

PS throughput (Including R99 and HSPA, UL+DL) per PS sub in BH (bps)bps10001000100010001000100010001000100010001000

Proportion of DL PS(Including R99 and HSPA) throughput%8080808080808080808080

Proportion of UL PS(Including R99 and HSPA) throughput%20202020202020202020

R99 share of DL PS throughput per sub%2525252525252525252525

HSDPA share of DL PS throughput per sub%75757575757575757575

R99 share of UL PS throughput per sub%100100100100100100100100100100100

HSUPA share of UL PS throughput per sub%0000000000

Other related parametersUnitDefault ValueValueValueValueValueValueValueValueValueValueValue

MBMS penetration ratio (Cell)%00000000000

MBMS Iub throughput per cell (kbps)kbps00000000000

MBMS IuPS throughput (kbps)kbps00000000000

IuCS signaling throughput ratio%11111111111

IuPS signaling throughput ratio%11111111111

Iub CS signaling throughput ratio per site%1010101010101010101010

Iub PS signaling throughput ratio per site%1010101010101010101010

Iub OAM throughput per site(kbps)kbps6464646464646464646464

Traffic throughput ratio between Iur and Iub%1010101010101010101010

Iur signaling throughput ratio%1010101010101010101010

Control plane traffic parameterUnitDefault ValueOwner call modelOwner call modelOwner call modelOwner call modelOwner call modelOwner call modelOwner call modelOwner call modelOwner call modelOwner call model

CS voice active factor%6060606060606060606060

Proportion of soft Handover for Cs voice call (not including softer Handover)%3030303030303030303030

Proportion of soft handover for CS data call (not including softer hanover)%3030303030303030303030

Proportion of soft handover for PS call (not including softer handover)%3030303030303030303030

CS voice penetration ratio means the proportion of voice subs in total subs.CS

CS data(vedio phone 64k)penetration ratio means the proportion of Video phone subs in total subs.CS

Voice traffic per CS voice sub in bust hour (Erlang)ERL

CS data traffic per CS data sub in Busy Hour (Erlang)ERL

CS voice call duration (sec.) s

call duration (sec.) of CS data service(Video Phone 64k) CS datas

If R99 PS Subscribers include HSPA subscribers, Penetration Ratio of PS(Including R99 and HSPA) is equal with that of R99 PS subs.If R99 PS Subs do not include HSPA subs, Penetration Ratio of PS(Including R99 and HSPA) is equal with the summation of that of R99 PS subs and that of HSPA subs.R99 PSHSPAPSR99 PSHSPAPSR99 PSHSPAR99 PSPSR99 PSHSPA

It is bit rate of PS throughput per PS user in Busy hour,that is equal with the summation of R99 uplink throughput(bps), R99 downlink throughput(bps), HSDPA throughput(bps) and HSUPA throughput(bps).If customer supply bit rate of PS throughput per PS active user, you should fill the date after multiply it by active ratio and attach ratio. Usually, the figer here should not be beyond 2000bps.PSPS(bps)PSR99R99HSDPAHSUPA2000bps.

Proportion of UL PS(Including R99 and HSPA) throughput,It's equal the summation of UL R99 and HSUPA divided by the summation of UL+DL R99 , HSUPA and HSDPA.PSPSR99HSUPA)/(R99HSUPA+R99HSDPA)

It's equal with the summation of DL R99 and HSDPA divided by the summation of UL+DL R99, HSDPA and HSUPA.PSPSR99HSDPA)/(R99HSUPA+R99HSDPA)

It's equal with DL R99 divided by the summation of DL R99 and HSDPA.PSR99R99/(R99HSDPA)

It's equal with HSDPA divided by the summation of DL R99 and HSDPA.PSHSDPAHSDPA/(R99HSDPA)

It's equal with UL R99 divided by the summation of UL R99 and HSUPA.PSR99R99/(R99HSUPA)

It's equal with HSUPA divided by the summation of UL R99 and HSUPA.PSHSUPAHSUPA/(R99HSUPA)

Ratio of cells number with MBMS service compare with total cells number. For example, total 3000 cells and 300 MBMS cells thereinto, then MBMS penetration ratio is 10%.MBMS3000300MBMSMBMS10%.

MBMS Iub throughput per cell=MBMS Channel number per cell* throughput per channel. For example, per MBMS cell 2 channel (128kbps), then MBMS Iub throughput per cell is 256kbps. Maximal Bandwidth of total MBMS channels per cell is 1.75Mbps.

MBMSIubMBMSMBMS2128kbpsMBMSIub256kbps. MBMS1.75Mbps.

It is MBMS service throughput in IuPS interface. Because our MBMS adopt broadcast technology, MBMS IuPS throughput lies on throughput of network broadcast channel but not that of cell channelMBMS Iub throughput. If there are 1000 cells in netword, and every cell has two same 128kbps channel(That means there is 2 broadcast channel in network), MBMS IuPS throughput is 128kbps*2=256kbps. If every cell has two 128kbps channel, but there is 8 broadcast channel in network, then MBMS IuPS throughput is 128kbps*8=1024kbps. Max capacity of MBMS throughput in IuPS interface is 8192kbps.IuPSMBMSMBMSIuPSMBMSMBMS Iub throughput10002128kbpsIuPS MBMS128kbps*2=256kbps2128kbps8128kbpsIuPS MBSM128*8=1024kbpsIuPS MBSM8192kbps

OAM Throughput has two specification 32k per site and 64k per site. Usually 64k per site is choosed.OAM32k per site64k per site64k per site.

Default value is 10%.10%

Actually, it is few that two side of CS Voice talk simultaneously. So, active factor will be multiplied when calculating CS Voice throughput. CSCS Voice

IUCS (ATM / IP based) Bandwidth Calculation

Recommend ValueRNC 1000000000

RNC VERSIONRAN 11000000000

IUCS INTERFACE TYPEATM

Total Subscriber10000000000000

CS Voice penetration ratio100%100%0%0%0%0%0%0%0%0%0%

CS Data penetration ratio50%100%0%0%0%0%0%0%0%0%0%

Voice Traffic per CS voice sub in BH0.018Erl0.018Erlang0Erlang0Erlang0Erlang0Erlang0Erlang0Erlang0Erlang0Erlang0Erlang

CS data traffic per CS data sub in BH0.0018Erl0.0018Erlang0Erlang0Erlang0Erlang0Erlang0Erlang0Erlang0Erlang0Erlang0Erlang

IUCS USER PALNE PAYLOAD THROUGHPUT3348kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps

IuCS Signaling throughput ratio** Recommend: 1% (RAN10) or 3% (RAN11 onward)3%3%3%3%3%3%3%3%3%3%3%

IUCS CONTROL PLANE THROUGHPUT100.44kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps

Voice Traffic0.2196kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps

CS Data Traffic0.1152kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps

Voice Traffic of All Subscribers2.20Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

CS Data Traffic of All Subscriber1.15Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Total User Plane/RNC3.35Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Total Control Plane / RNC0.10Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

IUCS Interface Throughput / RNC3.45Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

% of IUCS signaling usage (ATM) ** Recommend: 42%42%42%42%42%42%42%42%42%42%42%42%

IUCS Signaling Throughput (ATM layer)239.14kbps0.00kbps0.00kbps0.00kbps0.00kbps0.00kbps0.00kbps0.00kbps0.00kbps0.00kbps

Total Signaling Links4links2links2links2links2links2links2links2links2links2links

Bandwidth of each Signaling links256kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps

604cps0cps0cps0cps0cps0cps0cps0cps0cps0cps

% of IUCS User Plane usage (ATM) for AMR ** Recommend: 64%64%64%64%64%64%64%64%64%64%64%64%

IUCS User Plane Throughput (ATM Layer)_AMR5.23Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

% of IUCS User Plane usage (ATM) for Video** Recommend: 79%79%79%79%79%79%79%79%79%79%79%79%

IUCS User Plane Throughput (ATM Layer)_CS Data1.46Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

% of IUCS User Plane usage (IP) for AMR ** Recommend: 41%41%41%41%41%41%41%41%41%41%41%41%

IUCS User Plane Throughput (IP Layer)_AMR8.17Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

% of IUCS User Plane usage (IP) for Video** Recommend: 67%67%67%67%67%67%67%67%67%67%67%67%

IUCS User Plane Throughput (IP Layer)_CS Data1.72Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Total IUCS User Plane Throughput (ATM/IP Layer)6.69Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

% of Redundancy ** Recommend: 20% (RAN10) or 50% (RAN11 onward)50%50%50%50%50%50%50%50%50%50%50%

Total IUCS User Plane Throughput (ATM/IP Layer)10.03Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Bandwidth of each AAL2Path4Mbps4Mbps4Mbps4Mbps4Mbps4Mbps4Mbps4Mbps4Mbps4Mbps4Mbps

Total AAL2Paths need with xx% Redundancy3Paths0Paths0Paths0Paths0Paths0Paths0Paths0Paths0Paths0Paths

Total AAL2Paths confifuredPathPathPathPathPathPathPathPathPathPath

Bandwidth per AAL2Path needed with xx% Redundancy0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

K76082:Huawei Recommend value:RAN10.0: 1%RAN11.0: 3%RAN11.1: 3%RAN12.0: 3%

K76082:Huawei Recommend Value:RAN10.0: 20%RAN11.0: 50%RAN11.1: 50%RAN12.0:50%

Traffic Model

IUPS (ATM / IP based) Bandwidth Calculation

IUPS INTERFACE TYPEATMATMATMATMATMATMATMATMATMATM

PS (R99+HSPA) penetration ratio80%80%0%0%0%0%0%0%0%0%0%

Total PS throughput per user per BH1000bps1000bps0bps0bps0bps0bps0bps0bps0bps0bps0bps

Proportion of DL PS throughput80%80%0%0%0%0%0%0%0%0%0%

Proportion of UL PS throughput20%20%0%0%0%0%0%0%0%0%0%

MBMS IuPS throughput (kbps)0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps

IUPS DL User Plane Payload Throughput6.40Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

IUPS UL User Plane Payload Throughput1.60Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

IUPS USER PALNE PAYLOAD THROUGHPUT6.40Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

IuPS Signaling throughput ratio** Recommend: 1%1%1%1%1%1%1%1%1%1%1%1%

IUPS CONTROL PLANE THROUGHPUT0.064Mbps0.000Mbps0.000Mbps0.000Mbps0.000Mbps0.000Mbps0.000Mbps0.000Mbps0.000Mbps0.000Mbps

% of IUPS signaling usage (ATM) ** Recommend: 44%44%44%44%44%44%44%44%44%44%44%44%

IUPS Signaling Throughput (ATM layer)145.45kbps0.00kbps0.00kbps0.00kbps0.00kbps0.00kbps0.00kbps0.00kbps0.00kbps0.00kbps

Total Number of signaling Links2links2links2links2links2links2links2links2links2links2links

% of IUPS user plane usage (ATM)** Recommend: 79%79%79%79%79%79%79%79%79%79%79%79%

% of IUPS user plane usage (IP)** Recommend: 91%91%91%91%91%91%91%91%91%91%91%91%

IUPS User Plane Throughput (ATM/IP Layer)8.10Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Total IUPS User Plane Throughput (ATM/IP Layer)12.16Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

k76082:(Consider 1% of User Plane)

k76082:IUPS signaling usage (ATM) = 44%

k76082:IUPS user plane usage (ATM) = 79%

k76082:Consider xx% Redundancy for IUPS

Traffic Model

IUB (ATM based) Bandwidth Calculation

CS voice penetration ratio100%100%0%0%0%0%0%0%0%0%0%

CS data penetration ratio50%100%0%0%0%0%0%0%0%0%0%

Voice Traffic per CS voice sub in BH(Erlang )0.018Erl0.018Erl0Erl0Erl0Erl0Erl0Erl0Erl0Erl0Erl0Erl

CS data traffic per CS data sub in BH (Erlang)0.0018Erl0.0018Erl0Erl0Erl0Erl0Erl0Erl0Erl0Erl0Erl0Erl

PS (R99+HSPA) penetration ratio80%80%0%0%0%0%0%0%0%0%0%

Total PS throughput per user per BH1000bps1000bps0bps0bps0bps0bps0bps0bps0bps0bps0bps

Proportion of DL PS throughput80%80%0%0%0%0%0%0%0%0%0%

Proportion of UL PS throughput20%20%0%0%0%0%0%0%0%0%0%

R99 share of DL PS throughput per sub25%25%0%0%0%0%0%0%0%0%0%

HSDPA share of DL PS throughput per sub75%75%0%0%0%0%0%0%0%0%0%

R99 share of UL PS throughput per sub100%100%0%0%0%0%0%0%0%0%0%

HSUPA share of UL PS throughput per sub0%0%0%0%0%0%0%0%0%0%0%

CS voice active factor60%60%0%0%0%0%0%0%0%0%0%

Proportion of SHO for CS voice call30%30%0%0%0%0%0%0%0%0%0%

Proportion of SHO for CS data call30%30%0%0%0%0%0%0%0%0%0%

Proportion of SHO for PS call30%30%0%0%0%0%0%0%0%0%0%

MBMS penetration ratio (Cell)0%0%0%0%0%0%0%0%0%0%0%

MBMS Iub throughput per cell (kbps)0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps

Iub OAM throughput per site(kbps)64kbps64kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps

Iub DL User Plane Payload Throughput for CS Voice1.72Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Iub UL User Plane Payload Throughput for CS Voice1.72Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Iub DL User Plane Payload Throughput for CS Data1.50Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Iub UL User Plane Payload Throughput for CS Data1.50Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Iub DL User Planepayload throughput for PS R992.08Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Iub DL User Plane payload throughput for PS HSDPA4.80Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Iub UL User Plane payload througput for PS R992.08Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Iub UL User Palne payload througput for PS HSUPA0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Iub MBMS throughput0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

IUB USER PALNE PAYLOAD THROUGHPUT10.10Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Iub CS signaling throughput ratio per site** Recommend: 10%10%10%10%10%10%10%10%10%10%10%10%

Iub PS signaling throughput ratio per site** Recommend: 10%10%10%10%10%10%10%10%10%10%10%10%

Iub CS Control Plane Throughput0.33Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Iub PS Control Plane Throughput0.69Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

IUB CONTROL PLANE SIGNALING THROUGHPUT1.02Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

IUB OAM THROUGHPUT24.06Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

OAM Throughput has two specification 32k per site and 64k per site. Usually 64k per site is choosed.OAM32k per site64k per site64k per site.

Voice traffic per CS voice sub in bust hour (Erlang)ERL

CS data traffic per CS data sub in Busy Hour (Erlang)ERL

Traffic Model

IUR (ATM / IP based) Bandwidth Calculation

IUR INTERFACE TYPEATMATMATMATMATMATMATMATMATMATM

Traffic throughput ratio between Iur and Iub10%10%0%0%0%0%0%0%0%0%0%

Iur signaling throughput ratio10%10%0%0%0%0%0%0%0%0%0%

Iur DL User Plane Payload Throughput1.01Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Iur UL User Plane Payload Throughput0.53Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

IUR USER PALNE PAYLOAD THROUGHPUT1.01Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

IUR CONTROL PLANE THROUGHPUT101kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps0kbps

% of IUR signaling usage (ATM) ** Recommend: 46%46%46%46%46%46%46%46%46%46%46%46%

IUR Signaling Throughput (ATM layer)219.57kbps0.00kbps0.00kbps0.00kbps0.00kbps0.00kbps0.00kbps0.00kbps0.00kbps0.00kbps

Total Signaling Links2links2links2links2links2links2links2links2links2links2links

% of IUR user plane usage (ATM)** Recommend: 66% (RAN10) or 76% (RAN11 onward)76%76%76%76%76%76%76%76%76%76%76%

% of IUR user plane usage (IP)** Recommend: 74% (RAN10) or 85% (RAN11 onward)85%85%85%85%85%85%85%85%85%85%85%

IUR User Plane Throughput (ATM/IP Layer)1.33Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Total IUR User Plane Throughput (ATM/IP Layer)2.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

Max Bandwidth of 1 AAL2Path2MbpsMbpsMbpsMbpsMbpsMbpsMbpsMbpsMbpsMbps

Total AAL2Path need to be configured.1Paths0Paths0Paths0Paths0Paths0Paths0Paths0Paths0Paths0Paths

Bandwidth of each AAL2Path2.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps0.00Mbps

** Remark:

The type and quantity of AAL2Path recommended for IUR (ATM):

-- AAL2PATH_RT: 2 Paths

-- AAL2PATH_NRT: 2 Paths

-- AAL2PATH_UBR: 2 Paths

** In ATM based, if above is 1, means totally 6 AAL2Paths need to be configured: 2 for RT, 2 for NRT and 2 for UBR with same bandwidth specified in

** In ATM based, if above is 2, means totally 12 AAL2Paths need to be configured: 4 for RT, 4 for NRT and 4 for UBR with same bandwidth specified in

** In IP based (RAN 11 onward), if NRNC is Huawei RNC, it is recommend to configure 1 IPPath with type QoSPATH, bandwidth specified in .

** In IP based (RAN 11 onward), if NRNC is not Huawei RNC, it is recommend to configure 1 IPPath each for path type EF, AF43, AF23 and AF13, bandwidth specified in .

IP Based

k76082:IUPS user plane usage (ATM) = 79%

k76082:Consider xx% Redundancy for IUPS

Traffic Model

Reference

REFERENCE

NoTitleAttachment

1WCDMA BSC6810 V200R010-20090414-A-1.1.rar

2WCDMA RAN11200900908-A-V1.0.rar

3WCDMA RAN1220100305_V1.0.rar

4UMTS RANV100R001V1.1.doc

5UMTS RANV100R002RAN11-20091103-A-1.5.doc

6UMTS RANV100R003RAN11.1.doc

7UMTS RANV100R003RAN12.doc

MBD001F4489/WCDMA RAN11200900908-A-V1.0.rar

WCDMA RAN11200900908-A-V1.0/Iu&Iur Configuration Recommendation-RAN 11/IU&IUR Configuration Recommendation ATM V211.xls

Traffic Model

1.Traffic Model Assumption

BHCA CS per subscriber1.3

BHCA PS per subscriber9

BHCA SMS per subscriber0.6

BHCA other Signalling per subscriber0.7

BHCA LAU per subscriber1.3

BHCA RAU per subscriber0.5

BHCA interRatReselection per subscriber4

BHCA IMSI Detach per subscriber0.001

BHCA GPRS Detach per subscriber0.001

BHCA CS interRat Relocation per subscriber0.5

BHCA CS Paging per subscriber0.6

BHCA PS Paging per subscriber0.45

Average Erl of voice users(Erl)0.02167

Average Erl of Video Phone users(Erl)0.000248

PS DL traffic per subscriber in Busy Hour(Bytes)100000

PS UL traffic per subscriber in Busy Hour(Bytes)30000

VAD0.7

The total subscribers50000

the total number of WRBS1

The coefficient of peak and average traffic for signalling plane1.00

The coefficient of peak and average traffic for user plane0.00

2IuCS Control Plane

Procedure NameMessage NameMessage length(MTP MSU length(Bytes)Messge length(ATM layer)(Bytes)DirectionBHCA for per messageUplink Message Throughput(Bytes/Hour)Downlink Message Throughput(Bytes/Hour)

MO-CALLCm service req97159Uplink0.65103.350

CC1453Downlink0.65034.45

Cm service accept31106Downlink0.65068.9

Auth req79159Downlink0.650103.35

Auth resp56106Uplink0.6568.90

Security cmd68106Downlink0.65068.9

Security comp2553Uplink0.6534.450

TMSI realloc comp2653Uplink0.6534.450

COMMON ID32106Downlink0.65068.9

Setup45106Uplink0.6568.90

Call proceeding31106Downlink0.65068.9

Rab assingment req173265Downlink0.650172.25

Qaal2 est request81159Uplink0.65103.350

Qaal2 est confirm1853Downlink0.65034.45

Rab assingment resp32106Uplink0.6568.90

Alerting35106Downlink0.65068.9

Connect31106Downlink0.65068.9

Connect ack2653Uplink0.6534.450

Disconnect34106Uplink0.6568.90

Release2653Downlink0.65034.45

Release comp31106Uplink0.6568.90

Qaal2 rel request1753Uplink0.6534.450

Qaal2 rel confirm1153Downlink0.65034.45

Iu rel cmd35106Downlink0.65068.9

Iu rel comp1953Uplink0.6534.450

RLSD1453Downlink0.65034.45

RLC1153Uplink0.6534.450

MT-CALLPaging68106Downlink0.65068.9

Paging resp97159Uplink0.65103.350

CC1453Uplink0.6534.450

Auth req79106Downlink0.65068.9

Auth resp56106Uplink0.6568.90

Security cmd68106Downlink0.65068.9

Security comp2553Uplink0.6534.450

TMSI realloc comp2653Uplink0.6534.450

COMMON ID3253Downlink0.65034.45

Rab assingment req173212Downlink0.650137.8

Rab assingment resp3253Uplink0.6534.450

Qaal2 est request81106Uplink0.6568.90

Qaal2 est confirm1853Downlink0.65034.45

Setup44106Downlink0.65068.9

Call confirmed3353Uplink0.6534.450

Alerting2653Uplink0.6534.450

Connect2653Uplink0.6534.450

Connect ack3153Downlink0.65034.45

Disconnect3453Uplink0.6534.450

Release2653Downlink0.65034.45

Release comp3553Uplink0.6534.450

Qaal2 rel request1753Uplink0.6534.450

Qaal2 rel confirm1153Downlink0.65034.45

RLSD1453Downlink0.65034.45

RLC1253Uplink0.6534.450

location updateInit UE msg(Loc upd req)104159Uplink69540

SCCP:CC1453Downlink60318

DT(Auth request)79106Downlink60636

DT(Auth Response)56106Uplink66360

Security mode command68106Downlink60636

Security mode complete2553Uplink63180

DT(loc update accept)44106Downlink60636

DT(TMSI realloc comp)2653Uplink63180

Iu rel cmd2453Downlink60318

Iu rel comp1953Uplink63180

SCCP:RLSD1453Downlink60318

SCCP:RLC1253Uplink63180

IMSI DetachInit UE msg(IMSI detach)93159Uplink0.0010.1590

SCCP:CC1453Downlink0.00100.053

SCCP:RLSD1453Downlink0.00100.053

SCCP:RLC1253Uplink0.0010.0530

Iu-CS Relocation (Orignated)Relocation required87159Uplink0.579.50

Relocation cmd132159Downlink0.5079.5

Iu rel cmd241318Downlink0.50159

Relocation (Target)Relocation req197265Downlink000

SCCPCC1453Uplink000

Relocation ack132159Uplink000

Relcoation detect3253Uplink000

Relocation complete3253Uplink000

MO-SMSInit UE msg (Cm service req )97159Uplink0.347.70

DT(Auth request)79106Downlink0.3031.8

DT(Auth. response)56106Uplink0.331.80

Security Mode Command44106Downlink0.3031.8

Security mode complete2553Uplink0.315.90

DT (Cm service accept)3153Downlink0.3015.9

Cp data(rp data(sms submit))41106Uplink0.331.80

Cp ack2653Downlink0.3015.9

Cp data(rp ack(sms delivery report))3153Downlink0.3015.9

Cp ack2653Uplink0.315.90

MT-SMSPaging68106Downlink0.3031.8

Init UE msg (paging response)97159Uplink0.347.70

DT (Auth request)56106Downlink0.3031.8

DT (Auth response)56106Uplink0.331.80

Security Mode Command2553Downlink0.3015.9

Security Mode Complete2553Uplink0.315.90

DT:Cp data(Rp data(sms delivery))44106Downlink0.3031.8

Cp ack2653Uplink0.315.90

DT:Cp data(Rp ack(sms deliver reporter))3253Uplink0.315.90

Sum484395404741.1155029.859

Uplink Signal Throuhgput per Subscriber(Kbps)0.0105358111

Downlink Signal Throuhgput per Subscriber(Kbps)0.0111774644

Uplink Signal Throughput(Mbps)1.06

Downlink Signal Throughput(Mbps)1.12

Alcap Uplink Signalling Throughput(Mbps)0.06

Alcap Downlink Signalling Throughput(Mbps)0.04

3.IuCS User Plane

Traffic typeTTI period(ms)IUUP Payload(bytes)Ratio of pack reuseTotal spending(No pack reuse)(bytes)Total Transport spending(full pack reuse)(bytes)Average Throughput(ATM layer)(Kbps)Total Throughput(ATM layer)(Kbps)

AMR(12.2Kbps)203980%148.318181818218.5514069.2475

Video Phone(64Kbps)108080%9975.97942.028

4.IuPS Control Plane

Procedure NameMessage NameMessage length(MTP MSU length(Bytes)Messge length(ATM layer)(Bytes)DirectionBHCA for per messageUplink Message Throughput(Bytes/Hour)Downlink Message Throughput(Bytes/Hour)

AttachAttach Request90159Uplink0.0010.1590

Attach Accept48106Downlink0.00100.106

Attach Complete45106Uplink0.0010.1060

Common ID2453Downlink0.00100.053

DetachDetach Request74106Uplink0.0010.1060

Detach Accept2053Downlink0.00100.053

Service RequestService Request56106Downlink90954

Service Accept2353Uplink94770

PDP ActivatePDP Activate Request103159Uplink914310

PDP Activate Accept68106Downlink90954

RAB Assignment Request51106Uplink99540

RAB Assignment Response34106Downlink90954

PDP DeactivatePDP Deactive Request45106Uplink99540

PDP Deactive Accept2453Downlink90477

RAB Release Request1553Downlink90477

RAB Release Response2553Uplink94770

PDP ModificationPDP Modification Request60106Downlink000

PDP Modification Accept39106Downlink000

RAB Modification Request65106Uplink000

RAB Modification Response38106Downlink000

PagingPaging64106Downlink0.45047.7

Iu ReleaseIu Release Command1653Downlink9.0010477.053

Iu Release Complete2753Uplink9.001477.0530

Routing Area UpdateRouting Area Update Request79159Uplink0.579.50

Routing Area Update Accept36106Downlink0.5053

Routing Area Update Complete46106Uplink0.5530

SRNC RelocationRelocation Required00000

Relocation Request01000

Relocation Command01000

Relocation Request ACK00000

Relocation Complete00000

Total109.9584902.9244393.965

Uplink Signal Throuhgput per Subscriber(Kbps)0.0108953867

Downlink Signal Throuhgput per Subscriber(Kbps)0.0097643667

Uplink Signal Throughput(Mbps)1.09

Downlink Signal Throughput(Mbps)0.98

5.IuPS User Plane

Average Packet Size(Bytes)420

Transport Spending1.27

Uplink Data Throughput per subscriber(kbps)0.0666666667

Downlink Data Throughput per subscriber(kbps)0.2222222222

Total Uplink Data Throughput(Kbps)3333.34

Total Downlink Data Throughput(Kbps)11111.12

&L&G&C&F&RSecurityFor Internal

&L&D&CConfidential Information of Huawei.No Spreading without Permission&RPage &P of &N

Liu Zheng:this column=columnD * columnF which is uplink

Liu Zheng:CEILING((C248+12+8)/48,1)*53

Liu Zheng:BHCA for per message = [Average number of call setups (MO+MT)] * [Ratio of CS Mobile Originated Attempts to total number of CS calls] , which in CS

Liu Zheng:CEILING((C248+12)/48,1)*53without 8

Liu Zheng:BHCA for per message = [Average number of call setups (MO+MT)] * [Ratio of CS Mobile Terminated Attempts to total number of CS calls] , which in CS

Liu Zheng:BHCA for per message = [Average number of IMSI attachments per subscriber(include location update)] , which in CS

Liu Zheng:BHCA for per message = [Average number of IMSI detachments per subscriber] in CS

Liu Zheng:BHCA for per message = [Average number of SRNS Relocations per call] * [Percentage of SRNS Relocations sourced by RNC per call] , which in CS

Liu Zheng:BHCA for per message = [Average number of SRNS Relocations per call] * [Percentage of SRNS Relocations targeted by RNC per call] , which in CS

Liu Zheng:BHCA for per message = [Average number of CS mobile originating short message per subscriber] , which in CS

Liu Zheng:BHCA for per message = [Average number of CS mobile terminating short message per subscriber] , which in CS

IU Configuration

Huawei RNC Configuration

IUCS ConfigurationThe recommended TRMMAP is same to the default TRMMAP Refer to MML ''ADD/MODTRMMAP.''

CS ServiceATM Service TypePCR(kbps)SCR(kbps)MBS(cell)CDVT(0.1us)TRMMAP(IuCS)ATM

Signal PlaneCS RANAP & ALCAP SignallingRTVBR67256010001024Service TypeDefaultRecommended

CS RANAP & ALCAP SignallingRTVBR67256010001024PrimaryPrimary

User PlaneAAL2PATH_SHARERTVBR4800400010001024AMR voiceRT_VBRRT_VBR

AAL2PATH_SHARERTVBR4800400010001024R99 CS conversationalRT_VBRRT_VBR

AAL2PATH_SHARERTVBR4800400010001024R99 CS streamingRT_VBRRT_VBR

AAL2PATH_SHARERTVBR4800400010001024

Note1The configuration is a template for one Subrack. 24 Signalling links are recommended when there are 2 subracks or more. 3The Signalling link bandwidth is recommended at least 256kbps.4The maximum bandwith 4Mbps for IUCS AAL2PATH is enough because of 248 cid of AAL2PATH and single AMR bandwidth 16Kbps.

IUPS ConfigurationThe recommended TRMMAP is following. Refer to MML ''ADD/MODTRMMAP.''

PS ServiceATM Service TypePCR(kbps)SCR(kbps)MBS(cell)CDVT(0.1us)TRMMAP(Iub)IP

Signal PlanePS RANAP SignallingRTVBR66255210001024Service TypeDefaultRecommended

PS RANAP SignallingRTVBR66255210001024PrimaryPrimary

User PlaneIPOAUBR1024IMS SRBEFEF

User PlaneIPOAUBR1024PS conversationalAF43AF43

User PlaneIPOAUBR1024PS streamingAF43AF43

User PlaneIPPATHQoS1024PS high PRI interactiveAF33AF23

User PlaneIPPATHQoS1024PS middle PRI interactiveAF33AF23

User PlaneIPPATHQoS1024PS low PRI interactiveAF33AF23

User Plane-RelocationIPPATHQoS1024PS backgroundAF13AF23

Note1The configuration is a template for one Subrack. 24 Signalling links are recommended when there are 2 subracks or more. 3The Signalling link bandwidth is recommended at least 256kbps. 4The QoS IPPATH of IuPS shouled be added according to the number of the IPoA PVC.5IUR relocation PATH is needed. The Local IP PATH addr is SRNC; The peer IP PATH is DRNC. The nexthop is to DRNC is SGSN IPoA IP address.

Note 5:

IUR Configuration

IUR ServiceATM Service TypePCR(kbps)SCR(kbps)MBS(cell)CDVT(0.1us)

Signal PlaneRNSAP & ALCAP SignallingRTVBR38432010001024

RNSAP & ALCAP SignallingRTVBR38432010001024

User PlaneAAL2PATH_SHARERTVBR3000250010001024

AAL2PATH_SHARENRTVBR3000250010001024

AAL2PATH_SHAREUBR1024

1The bandwidth of IUR signaling link should be based on the traffic of handover area between two RNC.which is recommended at least 256kbps.

2Two MTP3B links are recommended for each Iur interface.

Note :

The recommended TRMMAP is same to the default TRMMAP Refer to MML ''ADD/MODTRMMAP.''

TRMMAP(Iub)ATM

Service TypeDefaultRecommended

PrimaryPrimary

Common channelRT_VBRRT_VBR

IMS SRBRT_VBRRT_VBR

SRBRT_VBRRT_VBR

AMR voiceRT_VBRRT_VBR

R99 CS conversationalRT_VBRRT_VBR

R99 CS streamingRT_VBRRT_VBR

R99 PS conversationalRT_VBRRT_VBR

R99 PS streamingRT_VBRRT_VBR

R99 PS high PRI interactiveNRT_VBRNRT_VBR

R99 PS middle PRI interactiveNRT_VBRNRT_VBR

R99 PS low PRI interactiveNRT_VBRNRT_VBR

R99 PS backgroundNRT_VBRNRT_VBR

HSDPA SignalRT_VBRRT_VBR

HSDPA IMS SignalRT_VBRRT_VBR

HSDPA VoiceRT_VBRRT_VBR

HSDPA conversationalRT_VBRRT_VBR

HSDPA streamingRT_VBRRT_VBR

HSDPA high PRI interactiveUBRUBR

HSDPA middle PRI interactiveUBRUBR

HSDPA low PRI interactiveUBRUBR

HSDPA backgroundUBRUBR

HSUPA SignalRT_VBRRT_VBR

HSUPA IMS SignalRT_VBRRT_VBR

HSUPA VoiceRT_VBRRT_VBR

HSUPA conversationalRT_VBRRT_VBR

HSUPA streamingRT_VBRRT_VBR

HSUPA high PRI interactiveUBRUBR

HSUPA middle PRI interactiveUBRUBR

HSUPA low PRI interactiveUBRUBR

HSUPA backgroundUBRUBR

MBD00182D7F/TRMMAP(IuCS).rar

TRMMAP(IuCS).TXT

ADD TRMMAP: TMI=15, REMARK="Iucs-atm", ITFT=IUCS, TRANST=ATM, VOICEPRIPATH=RT_VBR, CSCONVPRIPATH=RT_VBR, CSSTRMPRIPATH=RT_VBR;ADD TRMMAP: TMI=16, REMARK="Iucs-ip", ITFT=IUCS, TRANST=IP, VOICEPRIPATH=EF, CSCONVPRIPATH=AF43, CSSTRMPRIPATH=AF43;

MBD0018615D/TRMMAP(Iur-atm).rar

TRMMAP(Iur-atm).TXT

ADD TRMMAP: TMI=13, REMARK="Iur-atm", ITFT=IUR, TRANST=ATM, CCHPRIPATH=RT_VBR, SIPPRIPATH=RT_VBR, SRBPRIPATH=RT_VBR, VOICEPRIPATH=RT_VBR, CSCONVPRIPATH=RT_VBR, CSSTRMPRIPATH=RT_VBR, PSCONVPRIPATH=RT_VBR, PSSTRMPRIPATH=RT_VBR, PSINTHGHPRIPATH=NRT_VBR, PSINTMIDPRIPATH=NRT_VBR, PSINTLOWPRIPATH=NRT_VBR, PSBKGPRIPATH=NRT_VBR, HDSRBPRIPATH=RT_VBR, HDSIPPRIPATH=RT_VBR, HDVOICEPRIPATH=RT_VBR, HDCONVPRIPATH=RT_VBR, HDSTRMPRIPATH=RT_VBR, HDINTHGHPRIPATH=UBR, HDINTMIDPRIPATH=UBR, HDINTLOWPRIPATH=UBR, HDBKGPRIPATH=UBR, HUSRBPRIPATH=RT_VBR, HUSIPPRIPATH=RT_VBR, HUVOICEPRIPATH=RT_VBR, HUCONVPRIPATH=RT_VBR, HUSTRMPRIPATH=RT_VBR, HUINTHGHPRIPATH=UBR, HUINTMIDPRIPATH=UBR, HUINTLOWPRIPATH=UBR, HUBKGPRIPATH=UBR;

MBD0019C49F/TRMMAP(IuCS-atm).rar

TRMMAP(IuCS-atm).TXT

ADD TRMMAP: TMI=15, REMARK="Iucs-atm", ITFT=IUCS, TRANST=ATM, VOICEPRIPATH=RT_VBR, CSCONVPRIPATH=RT_VBR, CSSTRMPRIPATH=RT_VBR;MOD TRMMAP: TMI=15, ITFT=IUCS, TRANST=ATM, VOICEPRIPATH=RT_VBR, CSCONVPRIPATH=RT_VBR, CSSTRMPRIPATH=RT_VBR;

MBD00184695/TRMMAP(Iups).rar

TRMMAP(Iups).TXT

ADD TRMMAP: TMI=17, REMARK="Iups-ip", ITFT=IUPS, SIPPRIPATH=EF, PSCONVPRIPATH=AF43, PSSTRMPRIPATH=AF43, PSINTHGHPRIPATH=AF23, PSINTMIDPRIPATH=AF23, PSINTLOWPRIPATH=AF23, PSBKGPRIPATH=AF23;MOD TRMMAP: TMI=17, ITFT=IUPS, SIPPRIPATH=EF, PSCONVPRIPATH=AF43, PSSTRMPRIPATH=AF43, PSINTHGHPRIPATH=AF23, PSINTMIDPRIPATH=AF23, PSINTLOWPRIPATH=AF23, PSBKGPRIPATH=AF23;

WCDMA RAN11200900908-A-V1.0/Iu&Iur Configuration Recommendation-RAN 11/IU&IUR Configuration Recommendation IP V211.xls

General Rules

General Rules of Iu&Iur Configuration

1. PHB Priority

The default mapping between PHB and DSCP value.

PHB(Per Hop Behavior)EFAF43AF42AF41AF33AF32AF31AF23AF22AF21AF13AF12AF11BE

DSCP(Differentiated Services CodePoint)463836343028262220181412100

Note 1:

The DSCP Value or VLAN priority used in RAN should be planned in Transmission Device, and make sure the Transmission Device will not change the Values

Note 1:

IU Configuration

IUCS ConfigurationThe recommended TRMMAP is same to the default TRMMAP Refer to MML ''ADD/MODTRMMAP.''

CS ServiceTx(kbps)Rx(kbps)DSCPTRMMAP(IuCS)IP

Signal PlaneCS RANAP signaling48Service TypeDefaultRecommended

CS RANAP signaling48PrimaryPrimary

User PlaneEFPhysical Link BWPhysical Link BW46AMR voiceEFEF

AF43Physical Link BWPhysical Link BW38R99 CS conversationalAF43AF43

R99 CS streamingAF43AF43

Note1The configuration is a template for one Subrack. 24 Signalling links are recommended when there are 2 subracks or more. 3The Physical Link BW is the minimum bandwidth of physical link connection between RNC and CN.

IUPS ConfigurationThe recommended TRMMAP is following. Refer to MML ''ADD/MODTRMMAP.''

PS ServiceTx(kbps)Rx(kbps)DSCPTRMMAP(IuPS)IP

Signal PlanePS RANAP signaling48Service TypeDefaultRecommended

PS RANAP signaling48PrimaryPrimary

User PlaneQOSPhysical Link BWPhysical Link BWIMS SRBEFEF

User Plane-RelocationQOSPhysical Link BWPhysical Link BWPS conversationalAF43AF43

PS streamingAF43AF43

PS high PRI interactiveAF33AF23

PS middle PRI interactiveAF33AF23

PS low PRI interactiveAF33AF23

PS backgroundAF13AF23

Note1The configuration is a template for one Subrack. 24 Signalling links are recommended when there are 2 subracks or more. 3The Physical Link BW is the minimum bandwidth of physical link connection between RNC and CN.4The nubmer of IuPS QoS PATH is decided by the device Ip address or IuPS board .5IUR relocation PATH is needed. The Local IP PATH addr is SRNC; The peer IP PATH is DRNC. The nexthop is to DRNC is SGSN IPoA IP address.

Note 4:

Note 5:

IUR Configuration

Scenario 1: The neighboring RNC is Huawei RNC

Tx(kbps)Rx(kbps)DSCP

Signal PlaneRNSAP signaling48

RNSAP signaling48

User PlaneQOSPhysical Link BWPhysical Link BW

Scenario 2: The neighbor RNC is not Huawei RNC

Tx(kbps)Rx(kbps)DSCP

Signal PlaneRNSAP signaling48

RNSAP signaling48

User PlaneEFPhysical Link BWPhysical Link BW46

AF43Physical Link BWPhysical Link BW38

Note1The Physical Link BW is the minimum bandwidth of physical link connection between RNC and the neighboring RNC.

Note 1

The recommended TRMMAP is following. Refer to MML ''ADD/MODTRMMAP.''

TRMMAP(IuR)IP

PrimaryPrimary

Common channelEFEF

IMS SRBEFEF

SRBEFEF

AMR voiceEFEF

R99 CS conversationalAF43AF43

R99 CS streamingAF43AF43

R99 PS conversationalAF43AF43

R99 PS streamingAF43AF43

R99 PS high PRI interactiveAF33AF23

R99 PS middle PRI interactiveAF33AF23

R99 PS low PRI interactiveAF33AF23

R99 PS backgroundAF13AF23

HSDPA SignalEFEF

HSDPA IMS SignalEFEF

HSDPA VoiceAF43AF43

HSDPA conversationalAF43AF43

HSDPA streamingAF43AF43

HSDPA high PRI interactiveAF23AF13

HSDPA middle PRI interactiveAF23AF13

HSDPA low PRI interactiveAF23AF13

HSDPA backgroundAF13AF13

HSUPA SignalEFEF

HSUPA IMS SignalEFEF

HSUPA VoiceAF43AF43

HSUPA conversationalAF43AF43

HSUPA streamingAF43AF43

HSUPA high PRI interactiveAF23AF13

HSUPA middle PRI interactiveAF23AF13

HSUPA low PRI interactiveAF23AF13

HSUPA backgroundAF13AF13

MBD00197A70/TRMMAP(Iur-ip).rar

TRMMAP(Iur-ip).TXT

ADD TRMMAP: TMI=14, REMARK="Iur-ip", ITFT=IUR, TRANST=IP, CCHPRIPATH=EF, SIPPRIPATH=EF, SRBPRIPATH=EF, VOICEPRIPATH=EF, CSCONVPRIPATH=AF43, CSSTRMPRIPATH=AF43, PSCONVPRIPATH=AF43, PSSTRMPRIPATH=AF43, PSINTHGHPRIPATH=AF23, PSINTMIDPRIPATH=AF23, PSINTLOWPRIPATH=AF23, PSBKGPRIPATH=AF23, HDSRBPRIPATH=EF, HDSIPPRIPATH=EF, HDVOICEPRIPATH=AF43, HDCONVPRIPATH=AF43, HDSTRMPRIPATH=AF43, HDINTHGHPRIPATH=AF13, HDINTMIDPRIPATH=AF13, HDINTLOWPRIPATH=AF13, HDBKGPRIPATH=AF13, HUSRBPRIPATH=EF, HUSIPPRIPATH=EF, HUVOICEPRIPATH=AF43, HUCONVPRIPATH=AF43, HUSTRMPRIPATH=AF43, HUINTHGHPRIPATH=AF13, HUINTMIDPRIPATH=AF13, HUINTLOWPRIPATH=AF13, HUBKGPRIPATH=AF13;MOD TRMMAP: TMI=14, ITFT=IUR, TRANST=IP, CCHPRIPATH=EF, SIPPRIPATH=EF, SRBPRIPATH=EF, VOICEPRIPATH=EF, CSCONVPRIPATH=AF43, CSSTRMPRIPATH=AF43, PSCONVPRIPATH=AF43, PSSTRMPRIPATH=AF43, PSINTHGHPRIPATH=AF23, PSINTMIDPRIPATH=AF23, PSINTLOWPRIPATH=AF23, PSBKGPRIPATH=AF23, HDSRBPRIPATH=EF, HDSIPPRIPATH=EF, HDVOICEPRIPATH=AF43, HDCONVPRIPATH=AF43, HDSTRMPRIPATH=AF43, HDINTHGHPRIPATH=AF13, HDINTMIDPRIPATH=AF13, HDINTLOWPRIPATH=AF13, HDBKGPRIPATH=AF13, HUSRBPRIPATH=EF, HUSIPPRIPATH=EF, HUVOICEPRIPATH=AF43, HUCONVPRIPATH=AF43, HUSTRMPRIPATH=AF43, HUINTHGHPRIPATH=AF13, HUINTMIDPRIPATH=AF13, HUINTLOWPRIPATH=AF13, HUBKGPRIPATH=AF13;

MBD0019A55F/TRMMAP(IuCS-ip).rar

TRMMAP(IuCS-ip).TXT

ADD TRMMAP: TMI=16, REMARK="Iucs-ip", ITFT=IUCS, TRANST=IP, VOICEPRIPATH=EF, CSCONVPRIPATH=AF43, CSSTRMPRIPATH=AF43;MOD TRMMAP: TMI=16, ITFT=IUCS, TRANST=IP, VOICEPRIPATH=EF, CSCONVPRIPATH=AF43, CSSTRMPRIPATH=AF43;

MBD001986CF/TRMMAP(Iups).rar

TRMMAP(Iups).TXT

ADD TRMMAP: TMI=17, REMARK="Iups-ip", ITFT=IUPS, SIPPRIPATH=EF, PSCONVPRIPATH=AF43, PSSTRMPRIPATH=AF43, PSINTHGHPRIPATH=AF23, PSINTMIDPRIPATH=AF23, PSINTLOWPRIPATH=AF23, PSBKGPRIPATH=AF23;MOD TRMMAP: TMI=17, ITFT=IUPS, SIPPRIPATH=EF, PSCONVPRIPATH=AF43, PSSTRMPRIPATH=AF43, PSINTHGHPRIPATH=AF23, PSINTMIDPRIPATH=AF23, PSINTLOWPRIPATH=AF23, PSBKGPRIPATH=AF23;

WCDMA RAN11200900908-A-V1.0/Iub TX Configuration Recommendation_RAN 11/Iub TX Configuration Recommendation_ATM V211.xls

General Rules

General Rules of Iub Tx Configuration

1.VCC Planning

VCC TYPENumber of VCCs supported by HuaweiNumber of VCCs recommended by HuaweiATM service type

Signal PlaneNCP11CBR or RTVBR

CCP1 to 121

ALCAP11

User PlaneAAL2PATH_SHARE1 to 161+INT((AMRUserNum*2+24)/248)RT_VBR

AAL2PATH_SHARE1 to 161NRT_VBR

AAL2PATH_SHARE1 to 161UBR

OAMIPOA11UBR+

Note 1: Number of CCPs

When Huawei RNC and Huawei NodeB connected, one CCP link is enough.To be consistent with the 3GPP protocol, Huawei RNC&NodeB also support multiple CCPs, but it is not recommended by Huawei.

Note 2: Comparison between CBR and RTVBR for NCP/CCP/ALCAP

CBR type is preferred because it can make NCP/CCP/ALCAP signal data have higher priority than RT-VBR service data. When congestion the RT-VBR type data is discarded prior to CBR type data. So CBR type is recommended.But in fact most of data at Iub interface are of NRT-VBR type. When congestion, the NRT-VBR data must be firstly discarded, while the CBR and RT-VBR can hardly be affected. So there is almost no difference between CBR and RT-VBR for NCP/CCP/ALCAP PVC.

Note 3: Configuration of R99 RT PATHs

The number of R99 RT AAL2 paths depends on the maximum number of online users. The R99 RT AAL2 path can be added according to the actual network capacity. In one R99 RT path, there are only 248 CIDs available for upper layer. These CIDs are used by common channels and R99 RT users. 4 CIDs is needed by common channels of each cell; 2 CIDs is needed by one AMR call, one for signaling and the other for AMR traffic. SoCID number for AMR users: 2 CID/user * AMRUserNum CID number for Common Channels: 4 CID/cell * 6 Cells = 24 cells;

Note 4: Solution for UBR Configuration

The following configuration of HSPA path is recommended: Huawei RNC end: UBRHuawei NodeB end: UBROperator's ATM network: UBRUnder this configuration, the HSPA traffic will have no impact on R99 traffic even when real downlink congestion occurs, since theres no limitation on receiving end, congestion always appears on transmission end for Huawei RNC(the interface boards in WRBS)&NodeB. So downlink congestion always appears on RNC; uplink congestion always on NodeB.

Note 5: Multiplex Configuration About the Middle Transmission Device

If the peer device of NodeB or RNC,for example,it is the ATM switch, can not support multiplex configuration, that is to say, all configured bandwidth can not be beyond the physical bandwidth. The equipment and the ATM Switch adopts different configuration policy as follows:1)if the local configuration is CBR/RTVBR, the peer configuration is CBR/RTVBR.2)if the local configuration is NRTVBR/UBR, the peer configuration is UBR.3)if the peer replaces RTVBR with CBR, the local may keep RTVBR configuration in case of that the difference is not so big between PCR and SCR.4)The bandwidth configuration of the ATM Switch should be consistent with NodeB and RNC. That means, the configured bandwidth of this table should be modified according to the ATM Switch configuration.Except this, another method may be applied. VP switch in the ATM Switch can be configred and only total bandwidth needs to be specified.

2.Bandwidth Planning

Scenario 1: CBR for NCP&CCP&ALCAP

ATM Service TypePCR(kbps)SCR(kbps)MCR(kbps)

Signal PlaneNCPCBRCalculated by Traffic Model

CCPCBRCalculated by Traffic Model

ALCAPCBRCalculated by Traffic Model

User PlaneAAL2PATH_SHARERTVBRSCR*1.1(BW_IMA - (PCR_NCP+PCR_CCP+PCR_ALCAP+OM))/the number of RT PATHs

AAL2PATH_SHARERTVBRSCR*1.1(BW_IMA- (PCR_NCP+PCR_CCP+PCR_ALCAP+OM)/the number of RT PATHs

AAL2PATH_SHARENRTVBRBW_IMABW_IMAorUNIorFRA - (PCR_NCP+PCR_CCP+PCR_ALCAP)

AAL2PATH_SHAREUBRBW_IMA

OAMIPOAUBR+64

Scenario 2: RTVBR for NCP&CCP&ALCAP

ATM Service TypePCR(kbps)SCR(kbps)MCR(kbps)

Signal PlaneNCPRTVBRSCR_NCP *1.1Calculated by Traffic Model

CCPRTVBRSCR_CCP *1.1Calculated by Traffic Model

ALCAPRTVBRSCR_ALCAP *1.1Calculated by Traffic Model

User PlaneAAL2PATH_SHARERTVBRSCR*1.1(BW_IMA - (SCR_NCP+SCR_CCP+SCR_ALCAP+OM))//the number of RT PATHs

AAL2PATH_SHARERTVBRSCR*1.1(BW_IMA - (SCR_NCP+SCR_CCP+SCR_ALCAP+OM))//the number of RT PATHs

AAL2PATH_SHARENRTVBRBW_IMABW_IMA - (PCR_NCP+PCR_CCP+PCR_ALCAP)

AAL2PATH_SHAREUBRBW_IMA

OAMIPOAUBR+64

Note 6: Bandwidth of NCP&CCP&ALCAP

The bandwidth of NCP&CCP&ALCAP is calculated by traffic model. For detailed information, please refer to sheet "Iub Dimensioning Tool".

Note 8: Bandwidth of OAM PVC

The bandwidth of OAM PVC should be guaranteed when Congestion, so UBR+ is recommended. The bandwidth of OAM should be configured as small as possible,64kbps bandwidth is adopted.

3.Tx related Algorithm

Configuration ItemValue

Switches

DCCCenable

Iub bandwidth CACenable

Iub congestion controlenable

Iub overbookingenable

HSDPA Flow Controlenable

Congestion Control Threshold90%

AAL2 factor

Common Channel AAL2 factor70%

R99 PS AAL2 factor100%

Note 1

Note 3

Note 2

Note 5

Note 6:

Overbooking Configuration

This configuration is applicable when the middle switch between RNC and NodeB support overbooking configuration. Otherwise, refer to the "FRAATM" & "multi-E1" sheets.

ATM Service TypePCR(kbps)SCR(kbps)MBS(cell)CDVT(0.1us)MCR(kbps)FACTOR

Signal PlaneNCPCBR512102410

CCPCBR512102410

ALCAPCBR128102410

User PlaneAAL2PATH_SHARERTVBRBW_IMAorUNIorFRABW_IMAorUNIorFRA / 1.110001024

AAL2PATH_SHARERTVBRBW_IMAorUNIorFRABW_IMAorUNIorFRA / 1.110001024

AAL2PATH_SHARENRTVBRBW_IMAorUNIorFRABW_IMAorUNIorFRA / 1.110001024

AAL2PATH_SHAREUBRBW_IMAorUNIorFRA1024

OAMIPOAUBR+10246410

Note1:This configuration is applicable when the middle switch between RNC and NodeB support overbooking configuration or the cell covers the hot spot.

(Overbooking:configured bandwidth can beyond the physical bandwidth.)

Scenario 1: It doesn't have the ATM Switch or other PVC exchange equipments between RNC and NodeB.

Scenario 2: The ATM Swtich of other euipments support overbooking.

Note2: The bandwidth of BW_IMAorUNIorFRA refers to the following table

Bandwidth of UNI Link1920kbps

Bandwidth of IMA Link1904kbps

FraATM64kbps/TS

Note3: Please use the "SET CTRLFACTOR" command to modify the Factors to the values shown as the table.

Note4: The number of the AAL2PATH R99 RT is based on the CE of the NodeB. The formula refer to "General Rules".

The following number is a reference:

E1 NumberAAL2PATH Number

Note5: If the middle ATM switch equipment doesn't support CBR or multiplexing, the ATM Service Type of Signal Plane can be confiured to RTVBR.

ATM Service TypePCR(kbps)SCR(kbps)MBS(cell)CDVT(0.1us)RCR(kbps)MCR(kbps)FACTOR

Signal PlaneNCPRTVBR563512102410

CCPRTVBR563512102410

ALCAPRTVBR140128102410

Note6: Generally speaking, the 512kbps bandwidth is enough for NCP and CCP. Because the bandwidth of this configuration is multiplex and Factor is 10, if the

bandwidth of the Signal Plane doesn't use, the rest bandwidth can be used by service.Also, the larger bandwidth can improve the alternate rate and reduce the

alternate time.

Note 7:

The recommended TRMMAP is same to the default TRMMAP. Refer to the Sheet "multi-E1"

Huawei NodeB Configuration

ATM Service TypePCR(kbps)SCR(kbps)MBS(cell)CDVT(0.1us)RCR(kbps)MCR(kbps)

CCPCBR512

ALCAPCBR128

User PlaneAAL2PATHRTVBRBW_IMAorUNIorFRABW_IMAorUNIorFRA / 1.1100010240BW_IMAorUNIorFRA / 1.1

AAL2PATHRTVBRBW_IMAorUNIorFRABW_IMAorUNIorFRA / 1.1100010240BW_IMAorUNIorFRA / 1.1

AAL2PATHNRTVBRBW_IMAorUNIorFRABW_IMAorUNIorFRA / 1.1100010240BW_IMAorUNIorFRA / 1.1

AAL2PATHUBRBW_IMAorUNIorFRABW_IMAorUNIorFRA - (PCR_NCP*active factor of NCP+PCR_CCP*active factor of CCP+PCR_ALCAP*active factor of ALCAP)

OAMIPOAUBR+51264

Note 1:

1. NodeB Resource group configuration is not recommended except needed.

Notes 4

Notes 5:

Notes 5

Notes 7:

Notes 6

Notes 1

Note 1:

multi-E1

This configuration is applicable when the middle switch between RNC and NodeB doesn't support overbooking configuration. Otherwise, refer to the "Overbooking Configuration" sheet.

For middle transmission device, Physical bandwidth=Control plane + OM + RTVBR Type PATH. UBR is used for NRTVBR PATH . While RNC and NodeB keep NRTVBR type PATH.

Scenario 1: UNI 1*E1

CCPCBR136102450

ALCAPCBR30102430

OAMIPOAUBR+10246410

Note1: Please use the "SET CTRLFACTOR" command to modify the Factor values shown as the table.

Scenario 2: IMA 1*E1

CCPCBR136102450

ALCAPCBR30102430

OAMIPOAUBR+10246410

CCPCBR208102450

ALCAPCBR32102430

OAMIPOAUBR+10246410

CCPCBR272102450

ALCAPCBR40102430

OAMIPOAUBR+10246410

CCPCBR408102450

ALCAPCBR64102430

OAMIPOAUBR+10246410

CCPCBR480102450

ALCAPCBR72102430

OAMIPOAUBR+10246410

CCPCBR544102450

ALCAPCBR80102430

OAMIPOAUBR+10246410

CCPCBR616102450

ALCAPCBR88102430

OAMIPOAUBR+10246410

CCPCBR680102450

ALCAPCBR104102430

OAMIPOAUBR+10246410

Note 2:

The recommended TRMMAP is same to the default TRMMAP Refer to MML ''ADD/MODTRMMAP.''

TRMMAP(Iub)ATM

PrimarySecondaryPrimarySecondary

Common channelRT_VBRNULLRT_VBRNULL

IMS SRBRT_VBRNULLRT_VBRNULL

SRBRT_VBRNULLRT_VBRNULL

AMR voiceRT_VBRNULLRT_VBRNULL

R99 CS conversationalRT_VBRNULLRT_VBRNULL

R99 CS streamingRT_VBRNULLRT_VBRNULL

R99 PS conversationalRT_VBRNULLRT_VBRNULL

R99 PS streamingRT_VBRNULLRT_VBRNULL

R99 PS high PRI interactiveNRT_VBRNULLNRT_VBRNULL

R99 PS middle PRI interactiveNRT_VBRNULLNRT_VBRNULL

R99 PS low PRI interactiveNRT_VBRNULLNRT_VBRNULL

R99 PS backgroundNRT_VBRNULLNRT_VBRNULL

HSDPA SignalRT_VBRNULLRT_VBRNULL

HSDPA IMS SignalRT_VBRNULLRT_VBRNULL

HSDPA VoiceRT_VBRNULLRT_VBRNULL

HSDPA conversationalRT_VBRNULLRT_VBRNULL

HSDPA streamingRT_VBRNULLRT_VBRNULL

HSDPA high PRI interactiveUBRNULLUBRNULL

HSDPA middle PRI interactiveUBRNULLUBRNULL

HSDPA low PRI interactiveUBRNULLUBRNULL

HSDPA backgroundUBRNULLUBRNULL

HSUPA SignalRT_VBRNULLRT_VBRNULL

HSUPA IMS SignalRT_VBRNULLRT_VBRNULL

HSUPA VoiceRT_VBRNULLRT_VBRNULL

HSUPA conversationalRT_VBRNULLRT_VBRNULL

HSUPA streamingRT_VBRNULLRT_VBRNULL

HSUPA high PRI interactiveUBRNULLUBRNULL

HSUPA middle PRI interactiveUBRNULLUBRNULL

HSUPA low PRI interactiveUBRNULLUBRNULL

HSUPA backgroundUBRNULLUBRNULL

Scenario 1: UNI 1*E1

CCPCBR136

ALCAPCBR30

User PlaneAAL2PATHRTVBR174415861000102401586

AAL2PATHNRTVBR192016501000102401650

AAL2PATHUBR19201791

OAMIPOAUBR+51264

CCPCBR136

ALCAPCBR30

AAL2PATHNRTVBR190416341000102401634

AAL2PATHUBR19041775

OAMIPOAUBR+51264

CCPCBR208

ALCAPCBR32

AAL2PATHRTVBR187017001000102401700

AAL2PATHNRTVBR380834641000102403464

AAL2PATHUBR38083642

OAMIPOAUBR+51264

CCPCBR272

ALCAPCBR40

AAL2PATHRTVBR191517411000102401741

AAL2PATHNRTVBR571252881000102405288

AAL2PATHUBR57125508

OAMIPOAUBR+51264

CCPCBR408

ALCAPCBR64

AAL2PATHRTVBR254923171000102402317

AAL2PATHNRTVBR761670161000102407016

AAL2PATHUBR76167328

OAMIPOAUBR+51264

CCPCBR480

ALCAPCBR72

AAL2PATHRTVBR321429231000102402923

AAL2PATHNRTVBR952088321000102408832

AAL2PATHUBR95209190

OAMIPOAUBR+51264

CCPCBR544

ALCAPCBR80

AAL2PATHRTVBR386335121000102403512

AAL2PATHNRTVBR114241060010001024010600

AAL2PATHUBR1142411028

OAMIPOAUBR+51264

CCPCBR616

ALCAPCBR88

AAL2PATHRTVBR452941171000102404117

AAL2PATHNRTVBR133281241610001024012416

OAMIPOAUBR+51264

CCPCBR680

ALCAPCBR104

AAL2PATHRTVBR518647151000102404715

AAL2PATHNRTVBR152321420810001024014208

OAMIPOAUBR+51264

Note 1:

The IMA Group parameters includeing ITC/CTC should be same with the directly connected peer device.

Note 2:

Note 1:

Note 2:

FRAATM

This configuration is applicable when the middle switch between RNC and NodeB doesn't support overbooking configuration. Otherwise, refer to the "Overbooking Configuration" sheet.

Scenario 1: FRAATM 12TS

CCPCBR40102450

ALCAPCBR30102430

OAMIPOAUBR+10246410

CCPCBR48102450

ALCAPCBR30102430

OAMIPOAUBR+10246410

CCPCBR64102450

ALCAPCBR16102430

OAMIPOAUBR+10246410

CCPCBR72102450

ALCAPCBR30102430

OAMIPOAUBR+10246410

Note2:The recommended TRMMAP is same to the default TRMMAP.Refer to the Sheet "multi-E1"

CCPCBR40

ALCAPCBR30

AAL2PATHNRTVBR768476100010240476

AAL2PATHUBR768703

OAMIPOAUBR+51264

CCPCBR48

ALCAPCBR30

AAL2PATHNRTVBR960670100010240670

AAL2PATHUBR960891

OAMIPOAUBR+51264

CCPCBR64

ALCAPCBR16

AAL2PATHNRTVBR140811591000102401159

AAL2PATHUBR14081335

OAMIPOAUBR+51264

CCPCBR72

ALCAPCBR30

AAL2PATHNRTVBR153612531000102401253

AAL2PATHUBR15361455

OAMIPOAUBR+51264

Note 1:

ATM logic Port

case 1 ATM Logic Port

Type of the virtual portForward bandwidth(kbps)Backward bandwidth(kbps)

Logic PortHub/LeafMin bandwidth from RNC to NodeBMin bandwidth from RNC to NodeB

Note1:

If the license(ATM IUB overbooking) is open in RNC, LP is recommend

ATM Logic port is introduced for traffic shaping, congestion detection and backpressure when the outlet port in RNC side is a large bandwidth port and the bandwidth of the link to remote peer is limited. (For

example, STM-1 in RNC side, E1 in NODEB side) . The Logic Port is cited by the SAALLNK, AAL2PATH, IPOAPVC or other LP.)

Scenario 1: The interface board of RNC is UOI board. RNC configures one LP Leaf Port for each NodeB.

Scenario 2: Several NodeBs converge. RNC configues the LP HUB Port for the converge point.

Note2:

If the Node is the last node, the type of the Logic port is Leaf Node. Otherwise, it is the Hub Node.

Note3:

If the ATM traffic shaping and congestion control functions or the user plane resource separation by operators in RAN sharing is already enabled by running the

ADD ATMLOGICPORT command, set The bearing type of the virtual port to ATMLOGICPORT , which indicates that the AAL2 path is used to carry the user plan resources of the specified operator.

Notes1

Notes2

Faq&Notice

1.How to use and refer to this configuration recommendation?

(1)If the Iub interface is IP transmission, please refer to document "Iub Tx configuration recommendation_IP"

2. When shall we use RAN11 configuration Recommendation?

1) RNC and NodeB are both RAN11 version and there are newly established. If the RNC is upgraded from RAN10 to RAN11, keep the RAN10 configuration unchangeable. The matched version rules is following

IFTHEN

RNCNodeBConfiguration

RAN10RAN10RAN10

RAN11RAN10RAN10

RAN10RAN11RAN10

RAN11RAN11RAN11

Revise

descriptiontimeReviser

1Create this file according to V17 configuration suggestion.zhangyong,wangzecai

2The uplink IPoA bandwidth is set to 144kbps4/10/07zhangyonggan

3The 6-8E1s configuration is added.4/30/07zhangyonggan

4CDVT value is modified.R99 NRT is same to R99 RT.5/8/07zhangyonggan

5Add VP shaping configuration10/8/07wangzecai

6Modify PCR=6760 limitation of NodeB with 15232kbps according to the specification modification after V18C01B07211/28/07zhangyonggan

71.R99 RT PATH bandwidth1)if the middle switch can not support overbooking configuration, the RT PATH will average the data plane bandwidth.The data plane bandwidth(SCR) = the physical bandwidth -the control plane bandwidth*active factorEach RT PATH bandwidth(SCR)=The data plane bandwidth(SCR)/the number of RT PATHs2.R99 NRT PATH bandwidth1)Each NRT PATH bandwidth(SCR) = the physical bandwidth -the control plane bandwidth*active factor2)if the middle switch can not support overbooking configuration, The NRT PATH in switch can be configuration to UBR3.H NRT PATH1)UBR is configured in the middle switch and NodeB,RNC.2)the H NRT PATH bandwidth is physical bandwidth.4.H RT PATH1)There is no application in current version, so H RT PATH may not be configured.11/29/07zhangyonggan

8If the middle switch support overbooking configuration:1)the NCP is set to 512K; the CCP is set to 512K the ALCAP is set to 128K2)R99 RT/NRT path bandwidth PCR=the physical bandwidth SCR=PCR/1.13)HNRT path bandwidth PCR=the physical bandwidth1/24/08zhushimin

9In BSC6810.:1)HSDPA_NRT PATH and HSUPA_NRT PATH need to configure separately;2)The CDVT is set to 1024 both Signal Plane and User Plane when RNC and NodeB is not connected directly.1/24/08zhushimin

10Modify general rule:RTVBR for NCP&CCP&ALCAP:signal plane PCR=SCR*1.11/26/08zhushimin

11Margin for Engineering Calculation in sheet "Iub dimensioning Tool" is changed from 80% to 120%3/3/08zhushimin

12ADD "Virtual Port" Sheet4/25/08liuli

13Remove the PCR parameter of UBR+.4/25/08liuli

14Remove the CELL configuraion impact to the AALPATH.4/25/08liuli

15Modify the Overbooking Factor of the Signal Plane and OM.4/25/08liuli

16Add the explanation of AAL2PATH number.4/25/08liuli

17Modify the Signal Plane of Overbooking from CBR to CBR/RTVBR.4/25/08liuli

18ADD the Scenario of Default Configuration and VP.4/25/08liuli

19ADD the explanation of BW_IMAorUNIorFRA.4/25/08liuli

20ADD the explanation of SCR of Signal Plane4/25/08liuli

21Separate two configuration table, one is RNC configuration table, the other is NodeB8/22/08zhushimin

22Modify OM recommendation configuration(NodeB PCR->512kbps,MCR->64kbps)1/12/09zhushimin

23Add RCR for RTVBR&NRTVBR for NodeB1/12/09zhushimin

24Delete the note about limitation of NodeB PCR1/20/09zhushimin

25Delete PCR parameter of UBR according to RNC V210B061 version1/21/09zhushimin

26Modify PATH type according to RAN 11 version.1).RNC cancel HSUPA PATH type. HSPA ,R99 or Share(R99 HSPA) is support. HSPA and R99 PATH Type is recommended.2).NodeB cancel HSPA PATH and R99 PATH type.4/3/09zhushimin

27In the situation of the middle switch can not support overbooking configuration,modify calculation formula of each RT PATH bandwidth :The data plane bandwidth(SCR) = the physical bandwidth -the control plane bandwidth4/3/09zhushimin

28Modify calculation formula of RCR parameter of HSPA PATH bandwidth in NodeB side :RCR = the physical bandwidth -the control plane bandwidth*active factor4/3/09zhushimin

29Change description about virtual port to ATM logic port4/3/09zhushimin

301.Modify calculation formula of SCR parameter of RT and NRT PATH bandwidth:RT: SCR = (the physical bandwidth -the control plane bandwidth-MCR(OM))/AAL2 RT PATH Number PCR=SCR*1.1NRT: SCR = the physical bandwidth -the control plane bandwidth PCR=physical bandwidth2.Add TRMMAP table3.add PCR of UBR for PVC congestion detect, if PVC is congestion, backpressure function will work.if RAN10 UBR PATH has no PCR configuration, keep it unchanged. For new established R10 and R11 RNC, PCR configuration is recommended .8/5/09zhangyonggan

Iub Dimensioning Tool

About this Tool

This tool can be applied to UMTS5.1 and later released version Iub Dimensioning.

It just estimates approximately the IUB interface flux because of varying signaling procedure and size of signaling.

The configuration principles mentioned below are based on that the total amount of bandwidth has already planned.

Notes for input

Can be input and modified

System Default Value

Semi-manufactured Data

Result

Description for Items

1.Traffic Model Assumption

Frequency of each subscribe for Attach,Detach,Location Updated, SMS etc.2/h

Average conversation time of CS subscriber60s

Average conversation time of PS (DCCC as 1 access)60s

Ratio of the subscribers of CS and PS2

Ratio of convergence of network25

Ratio of soft and Softer handover30.0%

Frequency of DPB request procedure1/s

Average time interval of Softer handover for one user60s

Average time interval of Soft handover for one user60s

Average number of RLs for user in macro diversity2.5

Margin for Engineering Calculation120%

The Maximum Number of Online User for Different E1s at the Same Time

Num. of E1Num. of Cells per NodeBThe Maximum Number of Online User

812500

The Maximum Number of Online User for Different E1s

Num. of TSNum. of Cells per NodeBThe Maximum Number of Online User

2.ATM Limitations and Constant/Default Values

Min. AAL5 Bandwidth for 3812E20kbps

Min. AAL5 Bandwidth PVC for DBS380030kbps

Max. Bandwidth PVC for NodeB15999kbps

Bandwidth of UNI Link1920kbps

Bandwidth of IMA Link1904kbps

MBS(Max. Burst Size)1000Cells

AAL5 CDVT1024000.1us

RTVBR AAL2 CDVT102400.1us

NRTVBR CDVT60000000.1us

Maximum Depth of Bulk of VBR +CDVT133693440.1us

NCP FACTOR0.5

CCP FACTOR0.5

ALCAP FACTOR0.3

IPOA0.1

Note 1: Limitation for VBR because of Bulk Depth

NRTVBR:

RTVBR:

3.NCP&CCP&ALCAP Flux Evaluation

Traffic Analysis of NCP&CCP&ALCAP

About the signaling of NBAP

The flux of CPs is estimated based on Iub signalling procedure 3GPP 25.433 8.2, the process of NBAP includes common and dedicated procedures. NCP bears the common procedure and CCPs bear the dedicated procedure. The common procedure is that one UE initiates the process of the NodeB communication which has nothing to do with special UE, such as:1)Common Transport Channel Setup, 2)Common Transport Channel Deletion, 3)Audit4)Common Measurement Initiation, 5)Common Me

WCDMA IU Bandwidth Calculation Tool-20100629-A

Documents

Transcript of WCDMA IU Bandwidth Calculation Tool-20100629-A

u Iu Iu Iu 111 SYNTHESIS, CHARACTERIZATION AND CATALYTIC ...

Alcatel WCDMA KPI Evaluation 3G WCDMA

Thesis Wcdma

Wcdma channels

WCDMA Tutorial

20100629 SS Eco Settlement Seminar Eco Plastered Bamboo Hou

Using IU or IU Foundation Funds

Iv Iu Iu 111 vu11111 - Universiti Malaysia Pahang

WCDMA Handbook

IU Building Telecommunications Design Guidelinesuao/docs/standards/IU Telecomm.pdf · IU Building Telecommunications Design Guidelines 11/18/2016 gls UNDER REVISION - IU Telecom Design

WCDMA Air Interface Training Part 6 WCDMA TDD Mode

Barracuda Web Filter Ip 20100629

l:>tIl' · '81~ ~ 62!.b~.g~o.::::;-s¡g~~ ó - "C - ,,¡ QI o .¡..¡ ~ .~ IU ~ ~ "C :g 8 > 'IU o .0 ~ ,5 p. QI ~ ~ ~ ~ QI .(/) IU u 'IU '";ü IU =' ~ IU QI

EXUBERANT LEARNING SERVICES CATALOG 2014exuberant-group.com/fb/Brochure1.pdf · WCDMA RAN Dimensioning WCDMA RAN Signaling WCDMA RAN Functionality WCDMA RAN Optimization WCDMA RAN

WCDMA HUAWEI WCDMA RNO Access Procedure Analysis Guidance

WCDMA Principles

Tems Wcdma

Introduction to WCDMA and WCDMA Dimensioning for … to WCDMA and WCDMA... · Introduction to WCDMA and WCDMA Dimensioning for UMTS. 2 ... WCDMA Air Interface. 36 RLC RLC LAC LAC

Barracuda Link Balancer Ip 20100629

Adaptive wcdma