You are on page 1of 5

ULTRASITE: HIGH CAPACITY CONFIGURATIONS

Input data
Number of E1s
Number of Cells
1st BB subrack: WSPC in Primary WAM 2
WSPC in Secondary WAM 1
2nd BB subrack: WSPC in Primary WAM 4
WSPC in Secondary WAM 3
3rd BB subrack*: WSPC in Primary WAM 6
(see Note 7) WSPC in Secondary WAM 5

Content
6
6
3.0
0.0
3.0
0.0
0.0
0.0

VC46
VC47
VC48
VC49

UP
UP
UP
UP

DCH&HSPA
DCH&HSPA
DCH&HSPA
HSPA

DL VCC Bundle 1
VC33 CCH CNBAP
VC34 CCH DNBAP2
VC37 CCH DNBAP1
VC35 CCH DNBAP4
VC38 CCH DNBAP3

PCR

VCC in
DL
MDCR UBR Share Bundle

Path
Type

CDVT
(usec)
NIS

CDVT
(usec) NIP

AAL2
AAL2
AAL2
AAL2

CBR
CBR
CBR
UBR+

8529
8529
8529
25778

N/A
N/A
N/A
190

N/A
N/A
N/A
1

1
1
1
1

Stringent & Str Bi-level


Stringent & Str Bi-level
Stringent & Str Bi-level
Tolerant

250
250
250
250

250
250
250
250

AAL2
AAL5
AAL5
AAL5
AAL5
AAL5

N/A
CBR
CBR
CBR
CBR
CBR

25778
150
269
0
269
0

N/A
0
N/A
N/A
N/A
N/A

N/A

N/A

N/A

N/A
6667
3718
N/A
3718
N/A

N/A
11334
6320
N/A
6320
N/A

4
5
6
7
8

Guidelines for deployment

Note 1: This spreadsheet is not for general purpose Iub design deployment across the network
It should be used only on thise sites which have been flagged by Capacity Monitoring team for Iub congestio
This design should be used on those sites which have congestion due to any of the three reasons below:
1) high DCH VCC CID usage (70% and above)
2) high HS VCC CID usage (70% and above)
3) high DCH CAC Usage (70% and above)
This design increases capacity for all CID and CAC related congestion scenarios mentioned above even if only one
The reason for addressing all three types of congestions is to cover all possible congestions in one fix instead of doin
The 3 different congestions are related to each other and on some busy sites it is not uncommon to expect more tha
Note 2: It is not possible to increase number of VCCs on Ultrasites and that is why congestion due to high CID usage
However the CAC congestion can be alleviated using this spreadsheet by increasing the limit of DCH capacity from m
It should be possible to add extra VCCs for DCH and HS in Flexi NBs and therefore all three kinds of congestions in

ent across the network


Capacity Monitoring team for Iub congestion
e to any of the three reasons below:

n scenarios mentioned above even if only one of the above congestion has been triggered
l possible congestions in one fix instead of doing rework each time a new type of congestion is triggered
sy sites it is not uncommon to expect more than one type of congestion
hat is why congestion due to high CID usage cannot be addressed on Ultrasites.
t by increasing the limit of DCH capacity from max 4 E1s to 6 E1s
and therefore all three kinds of congestions in Flexi R1 and R2 can be solved by this spreadsheet

Version

Author

v1 Alok Tripathi
v1.1 Alok Tripathi
v1.2 Alok Tripathi
v1.3 Alok Tripathi
v1.4 Alok Tripathi
v1.5 Alok Tripathi

Changes
Ultra Site - Max DCH VCC bandwidth limit increased to 6E1s from
4E1 due to busy sites in the live network. No extra VCC for DCH or
HS
Flexi Site - Max DCH VCC bandwidth limit increased to 6E1s from
4E1 due to busy sites. Extra VCC for DCH and HS added to increase
CID capacity.
Guidelines for use' tab added to clarify the use of this design in
congestion facing sites only (such as high CID and CAC usage)
RU10 and RU20 designs tab included. Min E1s allowed set to 4
instead of 5 E1s in previous version
MDCR set to 250 for HSDPA and HSUPA for RU20 Iub ATM design
Tab 'RU20 Design' changed to have 2 HSPA VCCs instead of 1x
HSDPA and 1xHSUPA VCC
correction in 'RU20 Design'