This action might not be possible to undo. Are you sure you want to continue?
RAN Resource Monitoring and management
Capacity and resource analysis
• To figure out the WCDMA network, we have to associate the several information. As WCDMA blockage can occur at several part also the multiple-service will consume different resource in the network. Furthermore the congestion in WCDMA is consisting of soft and hard blocking. Hence we must gather this information for the analysis. The information will be collected is :
– Actual resource and configuration – Traffic and KPI statistic – Service distribution
• From these 3 components, we can create 3 dimensions relationship and give the result of enough or inadequate resources for desired service.
Resources and configuration
• In Huawei WCDMA network, to avoid the congestion and blockage of the service, we have to monitor the following resources :
NE Type NodeB Level Resource -CE card and license -NodeB HS-PDSCH code license -UL and DL Iub bandwidth -OVSF code -UL power -DL power Expansible Yes Yes Yes No Yes Yes
RAN Resource diagram
•DL total power/DL ENU •RTWP/UL ENU •OVSF Code (DCH/HS-PDSCH)
•DL total power/DL ENU •RTWP/UL ENU •OVSF Code (DCH/HS-PDSCH)
-CE card -CE license -HS-PDSCH code license
UL/DL Iub bandwidth
•DL total power/DL ENU •RTWP/UL ENU •OVSF Code (DCH/HS-PDSCH)
Traffic and KPI statistic
• To associate the actual situation of resource usage we have to consider in term of :
- CS and PS traffic - Congestion - Utilization
– AMR – VP – PS R99 DL – PS R99 UL – HSDPA – HSUPA .Service distribution • Each service type will occupy different resources. Hence we should divide the traffic volume corresponding to each service type to understand the characteristic of the cell.
• The monitor can be done separately for UL and DL. – Software • 1 License will be equal to 16 CEs. all cells connected to NodeB will share the same CE resource. • Truemove typically uses CE Card model WWBP2 (UL/DL128 CEs). CE is the pool resource at NodeB level. • The monitor will be done at NodeB level. . – Hardware • Number of CEs will be vary upon the model of card.CE Resource Description • CE resource is consisting of hardware and software. • Number of UL/DL license can be assigned independently.
More OVSF code manually assigned to HSDPA is less OVSF code left for R99. . The expansion can’t be possible in a single cell. • Typical usage of OVSF code – AMR : SF128 – SF256 – VP : SF32 – PS R99 DL : SF8 – SF128 – HSDPA : SF16 • Maximum is 15 * SF16 • HSDPA Code usage is depended on Manual or Automatic assignment.OVSF Code Resource Description OVSF Code is the limit resource of each cell. OVSF Code will be limited only DL direction.
.NodeB HSDPA Code License Description • Except the available number of free OVSF code. – HSDPA code license is a pool resource at BBU as same as CE. HSDPA is required the license. – Insufficient code license can degrade the throughput of HSDPA user as well.
. the increment in UL load can cause service rejection and slow down the data service. • For Huawei. One is real load in term of RTWP.UL Power Resource Description • Even the UL power is not limit corresponding to each UE power. but the noise raise will trig the rejection due to Call Admission Control as well. Hence. UL power resource can divided into 2 type. another one is equivalent load in term of ENU.
• The power consumption of each service will be different as well as the radio condition of each UE (e. Typical use of RRU power in Truemove is 20 and 40 watt. distance. RSCP. Ec/Io) • HSDPA will use the remaining power left from R99 service. • In general. the common control channel will consume about 20% of total power. .DL Power Resource Description • DL Power Limit is considered at RRU total power.g.
UL and DL Iub Bandwidth Description • Iub is the pool resource at BBU. each RRU have to share same Iub resource. . • • Typical configuration bandwidth of Iub is 10 and 20 Mbps. Truemove deploys IP based Iub transmission.
Total resource usage module Rejection -CS user -PS R99 User -HSDPA User -HSUPA User -Power -OVSF code -CE -Iub -Desire QoS -Congestion Service distribution Resources User experience 2 states of service interruption • The user can’t get the service (rejection). • The user can’t get at the desire QoS (low throughput of data service) .
Algorithm 1 or Algorithm 2 ? • • Huawei default for DL is Algorithm1 – Monitor TCP usage for load calculation Huawei default for UL is Algorithm2 – Monitor ENU for UL load calculation .Power CAC Algorithm • Power CAC is applied on both DL and UL • We have to consider our selected algorithm. The monitoring method will be different.
. To overview the power setting in a cell. Although it’s the same RRU power. CPICH power + common channel will consume around 20% of total cell power. we can check parameter setting of total power and CPICH power. • CPICH Power – MaxPCPICHPower (~ 10% of total cell power) – Default = 33 or 36 dBm • Total Power – MaxTxPower – Default = 43 or 46 dBm according to license By the way. it may different in the capacity because of UE distribution in a cell.Total RRU power setting • Total Carrier Power (TCP) is one of limited resource depending upon RRU total power output that impact directly to cell capacity and performance.
TCP Counter and monitoring 44 MaxTxPower 42 40 • Example : BKD0040U3 – MaxTxPower = 43 dBm – MaxPCPICHPower = 33 dBm PCPICH + Common channel 36 PCPICH 34 32 30 dBm 38 • We can monitor TCP usage from counter – – – – VS.MeanTCP (R99+HSDPA) VS.NonHS (R99) VS.MeanTCP We check parameter setting for RAB CAC 44 MaxTxPower 42 40 38 dBm – DL threshold of Conv AMR service[%] = 80 – DL threshold of Conv non_AMR service[%] = 80 – DL threshold of other services[%] = 75 – DL handover access threshold[%] = 85 – DL total power threshold[%] = 90 • RRC CAC considers OLC Trigger Threshold for admission – DL OLC trigger threshold[%] = 95 PCPICH + Common channel 36 PCPICH 34 32 30 Average of VS.MeanTCP.MaxTCP.NonHS (R99) • Average of VS.NonHS .NonHS Average of VS.MaxTCP Average of VS.MaxTCP (R99+HSDPA) VS.MeanTCP.MaxTCP.
Higher throughput infer the higher ENU value.Oversee cell load by ENU • Equivalent number of users (ENU) is the indicator from which maps each service type into one normalize cell load.DL. VS.UL.TotalTrfFactor VS.RAC.TotalTrfFactor UL ENU DL ENU . To get the UL and DL ENU we refer to these counters.RAC.
42 1.4 + 144 kbps (PS) 3.14 4.78 6.19 3.52 HSDPA 0.74 0.44 1.41 10.70 2.4 + 128 kbps (PS) 3.18 14.2 kbps 3.42 1.Typical equivalent number of users (ENU) ENU DCH uplink 0.04 1.87 6.62 2.11 1.89 2.6 kbps SIG 3.11 1.11 1.44 1.49 15.4 + 16 kbps (PS) 3.28 0.92 5.4 + 12.35 1.79 4.93 6.4 + 32 kbps (PS) 3.4 + 256 kbps (PS) 3.76 1.4 + 384 kbps (PS) .36 Sevice 3.17 HSUPA 1.26 2.4 + 8 kbps (PS) 3.25 5.25 2.60 3.4 kbps SIG 13.67 4.78 1.4 + 64 kbps (PS) 3.27 DCH downlink 0.15 3.46 9.61 9.36 14.61 10.45 5.37 2.
•Total UL Load = 27.UL.694 at 21:30 PM.TotalTrfFactor •UL ENU = 27.RAC.DL.UL.694/80 = 34.TotalTrfFactor • Have a look UL ENU from counter VS.UL ENU counter and monitoring • Take a look at parameter setting of maximum allowed equivalent user number – UL total equivalent user number = 80 (by default) • Example : BKD0040U3 35 30 25 20 15 10 5 •We check parameter setting for RAB CAC -UL threshold of Conv AMR service[%] = 75 -UL threshold of Conv non_AMR service[%] = 75 -UL threshold of other services[%] = 60 -UL handover access threshold[%] = 80 -UL total power threshold[%] = 83 •RRC CAC considers OLC Trigger Threshold for admission -UL OLC trigger threshold[%] = 95 0 Average of VS.62% .RAC.RAC.TotalTrfFactor Average of VS.
SF PS 8 PS 384 16 PS128 32 PS 64 64 128 AMR 0 0 1 0 2 1 3 0 256 Channel type 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 CPICH PCCPCH AICH PICH SCCPCH1 SCCPCH1 SCCPCH1 SCCPCH1 HS-SCCH HS-SCCH HS-SCCH HS-SCCH HS-SCCH HS-SCCH HS-SCCH HS-SCCH E-AGCH E-HICH/E-RGCH E-HICH/E-RGCH 4 2 5 1 6 3 0 4 2 7 8 9 10 5 11 1 12 6 13 3 14 7 15 • Upon the reservation of HS-PDSCH code parameter setting .RAB.SFOccupy. Therefore. it may occupy between 5-10 codes.OVSF Code Allocation • In general. The rest of the code will be able to use by traffic channel.10)) = 157 – 77 codes at SF256 • OVSF code usage counter .VS.MAX .SFOccupy .RAB. the total code left for traffic channel is about (normalize at SF256) : 256 – (19+SF256 of HS-PDSCH(5.VS. OVSF Code is occupied by common channel and for HSDPA (HS-SCCH and HS-PDSCH) as well as HSUPA.
OVSF and CE Consumption for DL DCH service Rate (kbps) SF CE Consumption 3.6 256 128 1 1 8 16 32 64 128 144 256 384 128 128 64 32 16 16 8 8 1 1 1 2 4 4 8 8 Note : Even HS-PDSCH will not utilize DL CE but A HSDPA User will consume 1*SF256 (1 CE) in DL for A-DCH.4 13. .
OVSF and CE Consumption for UL DCH service Rate (kbps) SF CE Consumption 3.6 256 64 1 1 8 16 32 64 128 144 256 384 64 64 32 16 8 8 4 4 1 1 1.4 13.5 3 5 5 10 10 .
5 3 3 5 10 10 32 32 48 5760 2SF2+2SF4 48 .OVSF and CE Consumption for HSUPA Rate (kbps) 8 16 32 64 128 144 256 384 608 1450 2048 2890 SF 256 64 64 64 32 8 4 4 4 2SF2 2SF2 2SF2+2SF4 CE Consumption 1 1 1.5 1.
OVSF Code Usage • 300 250 Example : BKD0040U3 Free code for traffic channel Total 179 codes is occupied.RAB.MAX •Check parameter setting •LST CELLHSDPA •Allocate Code Mode = MANUAL •Code Number for HS-PDSCH = 10 •By method of reservation by MANUAL then total 10*SF16 = 160 SF256 Code will be reserved for HSPDSCH Code only.RAB.8 = 69 Codes or about 34 AMR Voice. 1 SF32 is reserved for handover during CAC process . . Maximum 256 code is available for 1 cell 200 160 is reserved for HS-PDSCH 150 100 50 0 Average of VS. Free code left for traffic channel = 256-179 = 77 Codes However.SFOccupy. • • • Total 160 + 19 common channel = 179 codes are occupied and forbidden for traffic channel.SFOccupy Average of VS. The actual free left code should be about 77.
. • To ensure the proper rejection due to lack of resource. we can review the CAC threshold setting prior to perform further analysis. CAC will reject the service. RNC check the network resources. RRC is more critical than RAB rejection as RRC CAC threshold (typical 95% load) is higher than RAB CAC threshold. If found insufficient resources for a new service.Service rejection due to lack of resource • The rejection occurs at CAC phase. • The rejection may occur at RRC or RAB setup state.
Counter of RRC rejection due to lack of resource • RRC Connection Setup Rejection due to lack of resource .
Counter of CS RAB rejection due to lack of resource • Number of CS RAB Unsuccessfully Established due to Radio Resource Congestion (Cell) • Number of CS RAB Unsuccessfully Established due to Iub Bandwidth Congestion (Cell) .
Counter of PS RAB rejection due to lack of resource • Number of PS RABs Unsuccessfully Established due to Radio Resource Congestion (Cell) • Number of RABs Failing to Be Set Up in PS Domain due to Iub Bandwidth Congestion (Cell) .
Counter of PS RAB rejection due to lack of resource for different service • Number of Unsuccessful PS RAB Setups for Different Services due to Congestion (Cell) .
RRC.RRC.RRC.2 160 UL CE Usage 140 120 100 1 0.Cong Sum of VS.4 80 60 40 20 0 Sum of VS.Cong Sum of VS.Rej.RRC.LC.Shared Sum of VS. RAB setup will not initiate.DL.Rej.Rej.LC.Shared Sum of VS.DLIUBBandCong Sum of VS.ULMax.CE.ULIUBBandCong Sum of VS.Cong Found UL CE congestion associates with high UL CE Usage Note : When RRC Setup failure.RRC.RRC. Therefore RAB Setup congestion can not be seen.LicenseGroup.CE.Rej.LC.6 0.Rej.UL.Cong Sum of VS.ULCreditAvailable.Rej.Code.ULMean. .Power.2 0 Sum of VS.Shared 0.RRC Setup Congestion Monitor Example : BKD0040U3 1.LicenseGroup.8 0.
RAB.MaxTCP.Cong Sum of VS.MeanTCP.RAC.DL.Cong 0 Average of VS.RAB. we can judge that power congestion should come from DL LOW ~ 25 ENUs .FailEstab.Cong Sum of VS.FailEstCs.Cong Sum of VS.RAB.ULIUBBand.FailEstCs.Power.RAB.ULCE.FailEstab.DLIUBBand.Cong 10 5 Sum of VS.FailEstCs.RAB.TotalTrfFactor Average of VS.CS RAB Congestion monitoring Example : BKD0040U3 10 38 44 42 40 TCP 9 8 7 6 5 4 3 2 1 0 dBm Congestion but just quite small 36 34 32 30 Average of VS.Code.Cong Sum of VS.TotalTrfFactor • • Found some congestion of power and code -Code is DL OVSF Code -Power is either DL or UL power Associate with TCP and UL ENU.UL.CS.FailEstCs.DLCE.NonHS 35 30 UL ENU 25 20 15 Sum of VS.RAC.RAB.CS.NonHS Average of VS.
LicenseGroup.Shared Sum of VS.LC.LC.DLMean.Shared UL CE Usage 160 As PS RAB congestion has been found in cause UL CE congestion.ULMax.LC.DLMax.Shared .LicenseGroup.UL and DL CE Usage Monitoring Example : BKD0040U3 DL CE Usage 120 100 80 60 40 20 0 Sum of VS. 140 120 100 80 60 40 20 0 Sum of VS.Shared Sum of VS.LC. From CE usage monitoring we can see sometimes the maximum usage touches all available CE.LicenseGroup.LicenseGroup.Shared Sum of VS.DLCreditAvailable.ULCreditAvailable.LC.LC.Shared Sum of VS.ULMean.
• The service of a single user may be single-RAB or Multi-RAB • The service of a single user will consume balance or unbalance load between UL and DL e.Observe the type of service • Except the resource usage and rejection. to realize the resource consumption of the cell. we have to figure out the load of each service of a cell to see the distribution and judge which one consumes load the most. . – AMR user : UL CS AMR and DL CS AMR – Old Model mobile : DL+UL PS R99 – iPhone and BB user : UL PS R99 and DL HSDPA – Datacard user : UL HSUPA and DL HSDPA (all the equipment support HSUPA will support HSDPA).g.
Mean. VS. VS.User number counter in a cell • We can roughly discover the number of users to imply the traffic density in a cell.Cell VS.UE.UE.Cell Average no of HSDPA users Average no of HSUPA users Average no of users in CELL_PCH state Average no of users in CELL_DCH state Average no of users in CELL_FACH state VS.Mean.Cell <= VS.UE.Mean.Mean.HSUPA.CellPCHUEs VS.UE.CellDCHUEs VS.CellDCHUEs .HSDPA.Cell as UE which supports HSUPA shall support HSDPA.HSUPA.UE.Cell is the subset of VS.HSDPA.HSDPA.Mean.CellFACHUEs Typically. VS.
AMR.Ctrl.DL4.9+ VS.2 • UL/DL CE consumption for a AMR User = 1/1 .DL6.AMR.Ctrl.AMR user number counter in a cell • At the moment AMR user will utilize DL SF128/UL SF64 for each RL.Ctrl.DL7.Ctrl.Ctrl. • To sum up the number of AMR user we can calculate from Number of AMR users = VS.AMR.4+VS.AMR.2+VS.Ctrl.75+VS.7+VS.DL7.15+VS.AMR.95+ VS.DL5.DL12.DL5.AMR.DL10.AMR.Ctrl.Ctrl.AMR.
Hence while UL is HSUPA. DL will be HSDPA.Cell • • A HSDPA User consume 1*SF256 (1 CE) in DL for A-DCH UL CE consumes up to bit rate of HSUPA . Number of HSDPA+HSUPA Users = VS.Mean.HSUPA.HSDPA+HSUPA user number counter in a cell • Assume that HSUPA user is HSDPA user as well.UE.
Mean.Mean .Cell • • A HSDPA User consume 1*SF256 (1 CE) in DL for A-DCH UL CE consumes up to bit rate of DCH .HSDPA.VS.HSDPA+R99 user number counter in a cell • Typical mobile in a market will support only HSDPA while using R99 in UL. Number of HSDPA+R99 User = VS.UE. Therefore.HSUPA.UE.
DLInterPS.RB.RB.RB.384+VS.DLBkgPS.RB.DLBkgPS.256+VS.DLInterPS.DLInterPS.8 VS.32+VS.RB.RB.384 • • DL CE consumes up to bit rate of DL DCH UL CE consumes up to bit rate of UL DCH .256+VS.1 44+VS.DLStrPS. the number of DL+UL R99 is equal to number of DL R99 User Number of DL+UL R99 User = VS.DL+UL PS R99 user number counter in a cell • Assume that if the UE model supports only DL R99.RB.R B.32+VS.DLStrPS.DLBkgPS.DLConvPS.DLStrPS.RB.DLConvPS.DLConvPS.RB.DLBkgPS.DLStrPS.DLInterPS.RB.RB.DLBkgPS.RB.DLStrP S.144+VS.64+VS.RB.DLInterPS.DLInterPS.16+VS.DLStrPS.256+VS.DLStrPS.RB.8+VS.8+VS.RB.RB.RB.64+VS .1 6+VS.DLBkgPS.64+VS.32+VS.DLConvPS.128+VS.8+VS.RB.64+VS.RB.RB.16+VS.DLInterPS.128+VS.RB.RB.RB.16+VS.RB.128+VS.DLBkgPS.144+VS.RB.RB.32+VS.DLInterPS.DLBkgPS.
Resource threshold : DL Power Load Overload Congestion -> Overload Congestion Control MaxTxPower = 43 or 46 dBm RRC reject All RAB service reject Handover reject PS R99 RAB Service reject AMR RAB reject DL OLC Triggering threshold[%] = 95 DL total power threshold[%] = 90 DL handover access threshold[%] = 85 UL OLC Release threshold[%] = 85 DL threshold of Conv AMR service[%] = 80 DL threshold of Conv non_AMR service[%] = 80 DL threshold of other services[%] = 75 DL LDR Trigger Threshold[%] = 70 DL LDR Release Threshold[%] = 60 Basic Congestion-> LDR Basic Congestion-> LDR .
Resource threshold : UL Power Load Overload Congestion -> Overload Congestion Control UlTotalEqUserNum = 80 (case Algorithm2) RRC reject All RAB service reject Handover reject PS R99 RAB Service reject AMR RAB reject UL OLC Triggering threshold[%] = 95% UL OLC Release threshold[%] = 85% UL total power threshold[%] = 83 UL handover access threshold[%] = 80 UL threshold of Conv AMR service[%] = 75 UL threshold of Conv non_AMR service[%] = 75 UL threshold of other services[%] = 60 UL LDR Trigger Threshold[%] = 55 UL LDR Release Threshold[%] = 45 BackgroundNoise = -106 (Algorithm1) Basic Congestion-> LDR Basic Congestion-> LDR .
• For handover. • Dl HandOver Credit and Code Reserved SF = SF32 • For HSDPA service. there is no code resource admission. the admission accepted when code resource is sufficient for the service. . the admission accepted when code resource after admit the service is less than HandOver Credit and Code Reserved SF. the admission accepted when code resource is sufficient for RRC Connection.Resource Threshold : DL OVSF Code • For RRC connection setup request. • For other R99 service.
the admission accepted when [load of the path] + [bandwidth required by user] < [Total configured bandwidth of the path] • For a new user.Resource Threshold : Iub • For handover of a user. the admission accepted when [load of the path] + [bandwidth required by user] < [Total configured bandwidth of the path] – [congestion threshold] • • • • • • Forward handover reserved bandwidth[KBIT/S] = 0 Backward handover reserved bandwidth[KBIT/S] = 0 Forward congestion threshold[KBIT/S] = 0 Backward congestion threshold[KBIT/S] = 0 Forward congestion clear threshold[KBIT/S] = 0 Backward congestion clear threshold[KBIT/S] = 0 . the admission accepted when [load of the path] + [bandwidth required by user] < [Total configured bandwidth of the path] – [bandwidth reserved for handover] • For rate upsizing of a user.
• For other service. the admission accepted when CE resource is sufficient for RRC Connection. the admission accepted when CE resource after admit the service is not less than Ul HandOver Credit Reserved SF/Dl HandOver Credit and Code Reserved SF. • Ul HandOver Credit Reserved SF = SF16 (3 CE) • Dl HandOver Credit and Code Reserved SF = SF32 (2 CE) . the admission accepted when CE resource is sufficient for the service. • For handover.Resource Threshold : CE (UL/DL) • For RRC connection setup request.
2. 4. handover in order to balance between coverage and capacity of itself and surrounding cells. if low throughput on HSPDA Increase Iub bandwidth CE Power Code Iub Note : Capacity upgrade in term of optimization would be taken into account better in cell level. 5. 7. . The optimizer should control coverage and parameter e. 6. 8.Capacity upgrade solution In resource expansion. 3. these activities would be performed to increase or balance cell capacity (This is assumed that the site has been well optimization) 1.g. if code congest from Voice Increase fix HS-PDSCH code. WBBP upgrade/downgrade UL/DL CE upgrade/downgrade Increase UL ENU (if RTWP is normal) Increase total RRU power Reduce CPICH power Reduce fix HS-PDSCH code.
CE is CE of only one WBBP card. • If configure multi WBBP card into one DL BB Resource Group. CE is sum of CE from every WBBP cards. it will be defined as BB Resource Group separately for UL and DL – The main concern about the BB Resource Group is • If configure multi WBBP card into one UL BB Resource Group.WBBP and CE License up/down grade • Resource unit – WBBP : 128 UL/DL – CE License : 16 CE in UL or DL separately • CE resource configuration – To configure and use CE resource at NodeB. One DL BB Resource and UL BB Resource Group 128 UL/DL 128 UL/DL UL CE = 256 DL CE = 128 .
The CE License is in 16 CE unit. Reconfigure congested sector to separated WBBP Card can solve the problem prior to add new WBBP Sector1 DL BB Resource Group 0 UL BB Resource Group 0 128 UL/DL 128 UL/DL UL CE = 256 Sector2 Sector3 DL CE = 128 DL BB Resource Group 0 DL BB Resource Group 1 UL BB Resource Group 0 Sector1 128 UL/DL 128 UL/DL DL CE = 128 UL CE = 256 Sector2 Sector3 DL CE = 128 .WBBP and CE License up/down grade • Recommendation in CE up/down grade – Add/remove CE License on demand. – WBBP card should be utilized at full license prior to add WBBP. – If UL CE is congestion at full license. – If DL CE is congestion. adding new WBBP card is needed. Add or remove in term of 1 license (smallest unit) is recommended for highest efficiency.
Slot No. Subrack No.CE Configuration and License Information Using NodeB LMT to view Main Cabinet Topology and get info number of WBBP card WBBP card * Slot 01 is not configured yet. 2010-09-15 09:45:13 Board Configuration Information ------------------------------Cabinet No.%% RETCODE = 0 Succeed. Master 0 Master 0 Master 0 Master 0 Master 0 Master 0 Master 0 Master 0 Master 0 Master 0 Master 0 (Number of results = 11) --END 0 1 2 3 4 5 6 7 16 18 19 Configuration Status NO NO YES YES NO NO NO YES YES NO YES Board Type Unknown Unknown WBBP WBBP Unknown Unknown Unknown WMPT UBF Unknown UPEA . Or using MML command LST BRD +++ BKA9042U O&M #190945 %%LST BRD: SRN=0.
CE Configuration and License Information Using NodeB MML to list the BB Resource Group of DL/UL LST DLGROUP +++ BKA9042U O&M #191217 %%LST DLGROUP:. of DL Process Unit 1 Slot No. 2010-09-15 10:00:30 DL BB Resource Group Information -------------------------------DL BB Resource Group No. of UL Process Unit 1 Subrack No. of UL Process Unit 2 Subrack No. of DL Process Unit 1 Subrack No.%% RETCODE = 0 Succeed. of DL Process Unit 1 Slot No. Cabinet No. Cabinet No. of UL Process Unit 1 Cabinet No. of UL Process Unit 1 Slot No. of UL Process Unit 2 Slot No. of DL Process Unit 1 = = = = = = = = 0 Master 0 3 1 Master 0 2 UL BB Resource Group Information -------------------------------UL BB Resource Group No. of DL Process Unit 1 DL BB Resource Group No. Cabinet No.%% RETCODE = 0 Succeed. of DL Process Unit 1 Subrack No. 2010-09-15 09:58:33 LST ULGROUP +++ BKA9042U O&M #191359 %%LST ULGROUP:. of UL Process Unit 2 (Number of results = 1) = = = = = = = 0 Master 0 2 Master 0 3 (Number of results = 2) --END --- END DL Group is divided into 2 group while UL is set only 1 group .
0 0 0 DL BB Resource Group No. 0 while Local Cell 2 and 3 are sharing the DL BB Group No. 1 300 2 400 3 500 (Number of results = 3) --END 300 300 300 Sector No.CE Configuration and License Information Using NodeB LMT to view the BB DL/UL Resource Group allocated to each Local Cell LST LOCELL +++ BKA9042U 2010 -09-15 10:04:32 O&M #191658 %%LST LOCELL: MODE=ALLLOCALCELL.%% RETCODE = 0 Succeed. Local Cell Configuration(Summary) --------------------------------Local Cell ID Cell ID Site No. 0 1 2 UL BB Resource Group No. 0 1 1 Local Cel l Radius(m) 29000 29000 29000 Local Cell Inner Handover Radius(m) 0 0 0 Two Tx Way No No No • • All Local Cells are using the same UL BB Resource Group Local Cell 1 is using DL BB Resource Group No. 1 .
CE License should be managed properly DSP License +++ BKA9042U O&M #193826 %%DSP LICENSE:.1dBm) Cell Number in 430(0.1dBm) Multi-Mode BTS TS Ethernet Syn IP Clock Function Multi-Mode BTS = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 0xffff Shared Unlimited frequency Legal license 256 256 4 Yes 100 Yes 45 No Yes No Yes No Yes No 4 0 0 0 4 0 4 4 0 No No Yes No 2010-09-15 10:34:20 CE License would be pool resource for all the BB Resource Groups Local Local Local Local Local Local Local Emergency NodeB License ------------Emergency License Set Status (Number of results = 1) --END = Unset . Not only WBBP Card configuration.%% RETCODE = 0 Succeed.1dBm) Cell Number in 490(0.1dBm) Cell Number in 478(0.1dBm) Cell Number in 460(0.1dBm) Cell Number in 448(0. NodeB License ------------Operator Index Operator Name Downlink Frequencies License Status Max Uplink CE Max Downlink CE Max Local Cell HSDPA Function Max HSDPA User HSDPA RRM Package1 Max HS-PDSCH Code Number MBMS Function HSUPA Function PA Sharing Function HSUPA TTI Function CCPIC Function DYNAMIC CE DYNAMIC Voltage 64QAM NUM MIMO NUM Cell Number in 400(0.1dBm) Cell Number in 418(0.CE Configuration and License Information Using NodeB LMT to view UL/DL CE License.
we can increase 1 dB step adjust is recommended. – The performance after increasing UL ENU should be closely monitored. Note : please try to keep the ratio of CPICH power vs Max Transmit Power of Cell at 10% this would help to easily maintain CPICH Ec/No of the HSDPA carrier. • Only limit power resource on UL is ENU. . we can slightly reduce the CPICH power. The solution would be different up to the type of power congestion. – If coverage is the main concern in the serving area. • If power is congested due to DL power – If coverage is not the issue of the cell. call admission is success but it may lead to voice quality and drop call problem to itself or other UEs.Power congestion solution • As we have analyzed the root cause of power congestion whether UL (ENU) or DL (RRU power). UL ENU can adjust ranging from 1 – 200 – The concern of increasing UL ENU is RTWP. Although. 1 dB step adjust is recommended.
Thus. Thus.DL OVSF Code Congestion Solution • At the moment. code congestion would be caused by insufficient code for AMR and PS R99. most of the service congestion due to code should be AMR. The trade-off between AMR and HS-PDSCH code allocation is unavoidable according to limit of DL OVSF Code. • 1 SF16 of HS-PDSCH can convert to about 8 AMR (SF128). This would be equivalent to 1 TRX. the fix HS-PDSCH 1 code reduction step would recommend to avoid as much as possible impact to HSDPA throughput. the reduction of fix HS-PDSCH code would be the best solution at the moment. AMR (SF128) AMR (SF128) AMR (SF128) 1 HS-PDSCH (SF16) AMR (SF128) AMR (SF128) AMR (SF128) AMR (SF128) AMR (SF128) 1 2 3 4 5 6 7 8 . • To overcome this problem. However. PS DL R99 should be very low as most of DL PS RB is HSDPA.
Iub Congestion Solution • • The only available solution is to expand Iub bandwidth. the bandwidth limit should be omitted. Almost all of Iub is IP over MPLS. .
This action might not be possible to undo. Are you sure you want to continue?