Date post: | 19-Jan-2016 |
Category: |
Documents |
Upload: | shadin2014 |
View: | 117 times |
Download: | 14 times |
Duw Dimensioning
Mapping basebands
PlugInUnit
Slot
TxDeviceGroup
RaxDeviceGroup
DuiDeviceGroup
RXM
TXM
DBMs are NOT visible in MOM, may however be visible in MP SW for resource handling
Proposed mapping:
• One RaxDeviceGroup per RXM on DUW.
• One TxDeviceGroup for all TXMs
• Future possibility to distribute TXMs over two TxDeviceGroups
RaxDeviceGroup
RXM
RaxDeviceGroup
RXM
TXM
TXM
TXM
TXM
Ric
LogicalBoard
LogicalBoard
LogicalBoard
LogicalBoard
LogicalBoard
Managed Objects
/ fROs
Subsystem appl. HW
/SW
hW capability
Duw capacity
DUW 30 DUW 20 DUW 10
Channel Elements768 DL
512 UL
384 DL
384 UL
128 DL
128 UL
DL Peak/cc (Mbps)
DL Peak Throughput (Mbps)
42
252
42
126
42
42UL Peak/cc (Mbps)
UL Peak Throughput (Mbps)
12
48
12
36
12
12
Number HSPA users with CPC
Peak Users/cc
1152
256
576
256
192
192
Each DUW can control up to 6 ccEach RU 4 carriers (60w)
Resource_ID
› A resource_ID (TXM) on a DUW can be used for the following purposes
– Up to 6 cell carriers HSDPA with a maximum of 30 HS codes and up to 128 users (max 96 users per cell)
– R99 DCH with a capacity of 128CE– 6 cell carriers EUL with up to 96 users (max 48 users per cell carrier)
› We can treat one TXM on a DUW as HSPDA processing resource.
Resources per duw
DUW 10 01 = Low capacity = 128CE = 1 RXM + 3 TXM (at most 1 for DCH)
DUW 20 01 = Medium capacity = 384CE = 3 RXM + 5 TXM (3)
DUW 30 01 = High capacity = 768CE = 4 RXM + 8 TXM (6)
R99 HS EUL
DUW 10 3 1 1 1DUW 20 5 3 3 1DUW 30 8 6 4 1
Maximum Resource_ID that can be configured forDUW
Type
Total Resource_ID available in
DUW
Duw10
HS
EUL
R99
DUW10 (3 Resources Id)
1 HS Resource (128 CE)1 Eul Resource (128CE)1 R99 Resources (128 CE)
DUW TypeTotal Resources_ID available in DUW
Maximum Resource_ID configurable
R99 HS EUL
DUW 10 3 1 1 1
duw20
HS
EUL
R99/HS
R99
DUW20 (5 Resources Id)
1 HS Resource (128 CE)1 Eul Resource (128CE)3 R99 Resources (384 CE)
DUW TypeTotal Resources_ID available in DUW
Maximum Resource_ID configurable
R99 HS EUL
DUW 20 5 3 3 1
R99/HS
duw30
HS
EUL
R99/HS
DUW30 (8 Resources Id)
1 HS Resource (128 CE)1 Eul Resource (128CE)6 R99 Resources (768 CE)
R99/HSR99/HS
R99
R99R99
DUW TypeTotal Resources_ID available in DUW
Maximum Resource_ID configurable
R99 HS EUL
DUW 30 8 6 4 1
A-dch ce reservation
• A-DCH are dedicated channels, used for UL/DL signaling (SRB) when using HSDPA service.
• A-DCH channels consume CEs both for UL/DL, but in DL these CEs are reserved from the DL R99 CE pool.
• It is important to calculate the amount of R99 CE as this A-DCH reservation effectively reduces the CE capacity for R99.
A-DCHs for UL&DL
With W11B feature “SRB on HSDPA”, no A-DCH CEs reservation is necessary!!
A-dch ce reservation• The cost for 1 A-DCH in RBS6000 is 0.5CE.
• The amount of A-DCH resources is reserved by default in a Baseband pool the minimum of Criteria 1 and Criteria 2 below:
• Criteria 1
A-DCH CE reserved = 1.3 * sum of the lowest of the values of either the RBS License Key “Number of HSDPA users per Cell” or RbsLocalCell::maxNumHsdpaUsers, determined cell-by-cell * 0.5
For eg,
1st cell: RBS License Key “Number of HSDPA users per Cell” = 64 and MO parameter RBSLocalCell:: maxNumHsdpaUsers = 32
2nd cell: RBS License Key “Number of HSDPA users per Cell” = 64 and MO parameter RBSLocalCell:: maxNumHsdpaUsers = 64
Therefore, A-DCH CE reserved = (32 + 64) x 1.3 x 0.5 = 63 CE
• Criteria 2
A-DCH CE reserved = 1.3 * number of HS Resource_ID * 128 * 0.5
Therefore, A-DCH CE reserved = (32 + 64) x 1.3 x 0.5 = 63 CE
Example 1
HS
EUL
HS
R99
R99
DUW20 (5 Resources Id)
Example 1:DUW203 cc (32 HS users)2 HS resources1 EUL resource2 R99 resources
5 resources
numHScodesresources=2
numEulresources=1
2 R99 x 128 = 256 CE 63 CE required for A-DCH256-63 =193 CE for R99
Example 2
HS
EUL
HS
R99
R99
DUW20 (5 Resources Id)
Example 2:DUW206 cc (32 HS users)2 HS resources1 EUL resource2 R99 resources
5 resources
numHScodesresources=2
numEulresources=1
2 R99 x 128 = 256 CE A-DCH: min(2*128*1.3*0.5,32*6*1.3*0.5)= min(165,125)=125 for A-DCH 256-125 =131 CE for R99
Dual carrier
Example 4:For Dual Carrier:The two cells involved in the MC connection must be configured in the same HSDPA resource_ID. For a 3 sector site, ideally we should define 3 HS Resources.
DUW20
DUW30
2 HS Resources1 EUL Resource2 R99 Resources
3 HS Resources1 EUL Resource4 R99 Resources
1R99 x 128 = 128 CE 125 CE required for A-DCH256-125 =131 CE for R99
Not possible to define 3 HS resources with 32 HS users, just 3CEs
4R99 x 128 = 512 CE 125 CE required for A-DCH256-125 =387 CE for R99
Foa 3rd carrier
DUW20 (5 Resources Id) + DUW10 (3 Rerouces Id)
2 OSP Carriers and 1 VDF CarrierDual DUWDUW20 + DUW106 cc (32 HS users) 1st DUW (HS only on 2nd carrier)3 cc (32 HS users) 2nd DUW (HS)1 HS resource1 EUL resource3 R99 resources 1 HS resources 0 EUL resource
1 R99 resource
3R99 x 128 = 384 CE 63 CE required for A-DCH384-125 =321 CE for R99
1 R99 x 128 = 128 CE 63 CE required for A-DCH128-63 =65 CE for R99
CEs on different DUWs do not workas a pool!!
Dual duw legacy – mad0226
DUW20 (5 Resources Id) + DUW20 (5 Rerouces Id)
2 OSP CarriersDual DUWDUW20 + DUW203 cc (64 HS users) 1st DUW (HS)3 cc (non HS) 2nd DUW2 HS resource1 EUL resource2 R99 resources 0 HS resource 0 EUL resource
3 R99 resource
2R99 x 128 = 256 CE 125 CE required for A-DCH256-84=131 CE for R99
3R99 x 128 = 384 CE 0 CE required for A-DCH384 CE for R99
Even though there are two idle resource (not used for EUL), the Maximum number of R99 resource is 3.
Total DL = 131+384=515
Dual duw legacy – mad0226
Dual duw legacy – mad0226
Final comments
• In order to make a proper DUW dimensioning, it has to be taken into account:
• Number of HS Users per cell
• Number of HSDPA Resources
• Number of EUL Resources
• Number of Carriers per sector
• Number of sectors
• Number of necessary UL&DL CEs
• maxDlPowerCapability: The maximum downlink power capability for the cell. The attribute is calculated by the RBS and reported to the RNC.(maxDlPowerCapability = Nominal power (carrier) - ∑ dlattenuation )
• maximumtransmissionpower: This parameter allows the operator to limit the maximum used power in the cell. In normal cases this is not necessary.
appendix I power parameters
maximumtransmissionpower
* 1 carrier node
Maxdlpowercapability
dlattenuation
maxTotalOutputPower= 20W
appendix I power parameters
maxTotalOutputPower= 40W
Maxdlpowercapability for F1 cells
dlattenuation
dlattenuation
20W
Maxdlpowercapability for F2 cells
20W
Maxdlpowercapability
dlattenuation
maxTotalOutputPower= 20W 1 carrier node
2 carriers node
appendix II ce fract dual duw
Parameter ul/dlLicFractbbpool2 (DUW same capacity)Fraction (%) of licensed CE assigned to 2nd BaseBandpool
CE UL UL CE DL DLBbPool1 DUW10 128 0.5 128 0.5 ulLicFractBbPool2 50%BbPool2 DUW10 128 0.5 128 0.5 DlLicFractBbPool2 50%
256 256
CE UL UL CE DL DLBbPool1 DUW20 384 0.5 384 0.5 ulLicFractBbPool2 50%BbPool2 DUW20 384 0.5 384 0.5 DlLicFractBbPool2 50%
768 768
CE UL UL CE DL DLBbPool1 DUW30 512 0.5 768 0.5 ulLicFractBbPool2 50%BbPool2 DUW30 512 0.5 768 0.5 DlLicFractBbPool2 50%
1024 1536
*This parameter must be adjusted/optimized depending on the CE consumption per BBPool.
appendix II ce fract dual duw
Parameter ul/dlLicFractbbpool2 (DUW different capacity)
CE UL UL CE DL DLBbPool1 DUW20 384 0.75 384 0.75 ulLicFractBbPool2 25%BbPool2 DUW10 128 0.25 128 0.25 DlLicFractBbPool2 25%
512 512
CE UL UL CE DL DLBbPool1 DUW10 128 0.25 128 0.25 ulLicFractBbPool2 75%BbPool2 DUW20 384 0.75 384 0.75 DlLicFractBbPool2 75%
512 512
CE UL UL CE DL DLBbPool1 DUW10 128 0.2 128 0.142857 ulLicFractBbPool2 80%BbPool2 DUW30 512 0.8 768 0.857143 DlLicFractBbPool2 86%
640 896
CE UL UL CE DL DLBbPool1 DUW20 384 0.428571 384 0.333333 ulLicFractBbPool2 57%BbPool2 DUW30 512 0.571429 768 0.666667 DlLicFractBbPool2 67%
896 1152