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.
– Software • 1 License will be equal to 16 CEs. – Hardware • Number of CEs will be vary upon the model of card. . • The monitor will be done at NodeB level. all cells connected to NodeB will share the same CE resource. • Truemove typically uses CE Card model WWBP2 (UL/DL128 CEs). • Number of UL/DL license can be assigned independently. CE is the pool resource at NodeB level.CE Resource Description • CE resource is consisting of hardware and software. • The monitor can be done separately for UL and DL.
OVSF Code Resource Description OVSF Code is the limit resource of each cell. OVSF Code will be limited only DL direction. 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. More OVSF code manually assigned to HSDPA is less OVSF code left for R99.
– Insufficient code license can degrade the throughput of HSDPA user as well. .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.
the increment in UL load can cause service rejection and slow down the data service. One is real load in term of RTWP. . • For Huawei. Hence.UL Power Resource Description • Even the UL power is not limit corresponding to each UE power. another one is equivalent load in term of ENU. but the noise raise will trig the rejection due to Call Admission Control as well. UL power resource can divided into 2 type.
distance. • The power consumption of each service will be different as well as the radio condition of each UE (e. the common control channel will consume about 20% of total power.DL Power Resource Description • DL Power Limit is considered at RRU total power. RSCP.g. • In general. Ec/Io) • HSDPA will use the remaining power left from R99 service. . Typical use of RRU power in Truemove is 20 and 40 watt.
Truemove deploys IP based Iub transmission. .UL and DL Iub Bandwidth Description • Iub is the pool resource at BBU. • • Typical configuration bandwidth of Iub is 10 and 20 Mbps. each RRU have to share same Iub resource.
• The user can’t get at the desire QoS (low throughput of data service) .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).
Power CAC Algorithm • Power CAC is applied on both DL and UL • We have to consider our selected algorithm. 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 . The monitoring method will be different.
• 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. .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. it may different in the capacity because of UE distribution in a cell. Although it’s the same RRU power. CPICH power + common channel will consume around 20% of total cell power. To overview the power setting in a cell. we can check parameter setting of total power and CPICH power.
NonHS .MeanTCP.MeanTCP.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.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.MaxTCP.NonHS Average of VS.MaxTCP.MaxTCP Average of VS.MeanTCP (R99+HSDPA) VS.NonHS (R99) VS.NonHS (R99) • Average of VS.MaxTCP (R99+HSDPA) VS.
RAC.TotalTrfFactor UL ENU DL ENU .Oversee cell load by ENU • Equivalent number of users (ENU) is the indicator from which maps each service type into one normalize cell load. Higher throughput infer the higher ENU value. VS.RAC. To get the UL and DL ENU we refer to these counters.DL.TotalTrfFactor VS.UL.
04 1.36 Sevice 3.4 + 8 kbps (PS) 3.4 + 64 kbps (PS) 3.61 10.15 3.4 + 256 kbps (PS) 3.45 5.78 1.36 14.42 1.6 kbps SIG 3.61 9.52 HSDPA 0.28 0.60 3.11 1.42 1.4 kbps SIG 13.17 HSUPA 1.78 6.79 4.4 + 384 kbps (PS) .25 5.4 + 12.89 2.11 1.Typical equivalent number of users (ENU) ENU DCH uplink 0.93 6.4 + 144 kbps (PS) 3.76 1.67 4.4 + 16 kbps (PS) 3.37 2.27 DCH downlink 0.62 2.19 3.49 15.35 1.92 5.14 4.46 9.87 6.44 1.70 2.26 2.4 + 32 kbps (PS) 3.74 0.2 kbps 3.18 14.11 1.25 2.44 1.4 + 128 kbps (PS) 3.41 10.
UL.TotalTrfFactor • Have a look UL ENU from counter VS.RAC.TotalTrfFactor Average of VS. •Total UL Load = 27.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.UL.62% .DL.TotalTrfFactor •UL ENU = 27.694/80 = 34.694 at 21:30 PM.RAC.RAC.
it may occupy between 5-10 codes.SFOccupy.RAB. 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 . Therefore.MAX .VS. the total code left for traffic channel is about (normalize at SF256) : 256 – (19+SF256 of HS-PDSCH(5. The rest of the code will be able to use by traffic channel.OVSF Code Allocation • In general.RAB.10)) = 157 – 77 codes at SF256 • OVSF code usage counter .VS.SFOccupy . OVSF Code is occupied by common channel and for HSDPA (HS-SCCH and HS-PDSCH) as well as HSUPA.
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.OVSF and CE Consumption for DL DCH service Rate (kbps) SF CE Consumption 3. .4 13.
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.5 3 5 5 10 10 .
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 3 3 5 10 10 32 32 48 5760 2SF2+2SF4 48 .5 1.
Maximum 256 code is available for 1 cell 200 160 is reserved for HS-PDSCH 150 100 50 0 Average of VS.8 = 69 Codes or about 34 AMR Voice. .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. 1 SF32 is reserved for handover during CAC process .OVSF Code Usage • 300 250 Example : BKD0040U3 Free code for traffic channel Total 179 codes is occupied. • • • Total 160 + 19 common channel = 179 codes are occupied and forbidden for traffic channel.SFOccupy.RAB. Free code left for traffic channel = 256-179 = 77 Codes However.SFOccupy Average of VS.RAB. The actual free left code should be about 77.
RNC check the network resources. If found insufficient resources for a new service. • The rejection may occur at RRC or RAB setup state. . RRC is more critical than RAB rejection as RRC CAC threshold (typical 95% load) is higher than RAB CAC threshold. CAC will reject the service. • To ensure the proper rejection due to lack of resource.Service rejection due to lack of resource • The rejection occurs at CAC phase. we can review the CAC threshold setting prior to perform further analysis.
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) .
LC.RRC.2 0 Sum of VS.LC.RRC.Power. .Rej.Shared Sum of VS.Shared Sum of VS.LC.Rej.DL.DLIUBBandCong Sum of VS. RAB setup will not initiate.ULIUBBandCong Sum of VS.2 160 UL CE Usage 140 120 100 1 0. Therefore RAB Setup congestion can not be seen.LicenseGroup.Code.Rej.Cong Sum of VS.Rej.RRC Setup Congestion Monitor Example : BKD0040U3 1.ULMean.4 80 60 40 20 0 Sum of VS.CE.8 0.RRC.Rej.6 0.CE.ULMax.Shared 0.Cong Found UL CE congestion associates with high UL CE Usage Note : When RRC Setup failure.ULCreditAvailable.UL.Cong Sum of VS.RRC.Rej.Cong Sum of VS.LicenseGroup.RRC.RRC.
DLIUBBand.Cong Sum of VS.Power.DL.Code.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.RAB.MeanTCP.Cong Sum of VS.NonHS 35 30 UL ENU 25 20 15 Sum of VS.DLCE.ULIUBBand.FailEstCs.RAB.Cong Sum of VS.FailEstCs.MaxTCP.Cong 0 Average of VS.RAC.RAB.CS. we can judge that power congestion should come from DL LOW ~ 25 ENUs .TotalTrfFactor Average of VS.FailEstab.RAB.FailEstCs.RAB.FailEstab.RAB.FailEstCs.RAC.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.Cong 10 5 Sum of VS.CS.UL.Cong Sum of VS.ULCE.NonHS Average of VS.
LC.LicenseGroup.ULMax.LC.DLMean.LC.DLMax. 140 120 100 80 60 40 20 0 Sum of VS.LicenseGroup.LicenseGroup.LicenseGroup.ULMean.Shared Sum of VS.LC.Shared Sum of VS.LC.Shared Sum of VS.Shared . From CE usage monitoring we can see sometimes the maximum usage touches all available CE.DLCreditAvailable.ULCreditAvailable.Shared UL CE Usage 160 As PS RAB congestion has been found in cause UL CE congestion.LC.UL and DL CE Usage Monitoring Example : BKD0040U3 DL CE Usage 120 100 80 60 40 20 0 Sum of VS.Shared Sum of VS.
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. • 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. .g. to realize the resource consumption of the cell. – 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).Observe the type of service • Except the resource usage and rejection.
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. VS.Mean.CellFACHUEs Typically.HSUPA.Mean. VS.Cell as UE which supports HSUPA shall support HSDPA.UE.HSUPA.CellDCHUEs VS.UE.UE.Mean.Mean.CellDCHUEs .UE.Cell VS.HSDPA.Cell <= VS.UE.CellPCHUEs VS.HSDPA.User number counter in a cell • We can roughly discover the number of users to imply the traffic density in a cell.HSDPA. VS.Mean.Cell is the subset of VS.
AMR.2 • UL/DL CE consumption for a AMR User = 1/1 .4+VS.9+ VS.DL12.2+VS.AMR user number counter in a cell • At the moment AMR user will utilize DL SF128/UL SF64 for each RL.Ctrl.DL6.Ctrl.DL5.AMR.DL4.Ctrl.DL10.Ctrl.AMR.Ctrl.DL5.AMR.DL7.15+VS.Ctrl.AMR.DL7.Ctrl.AMR.AMR.75+VS.95+ VS.AMR.Ctrl. • To sum up the number of AMR user we can calculate from Number of AMR users = VS.7+VS.
UE. DL will be HSDPA.HSUPA. Hence while UL is HSUPA.HSDPA+HSUPA user number counter in a cell • Assume that HSUPA user is HSDPA user as well.Mean. Number of HSDPA+HSUPA Users = VS.Cell • • A HSDPA User consume 1*SF256 (1 CE) in DL for A-DCH UL CE consumes up to bit rate of HSUPA .
HSUPA.Mean .HSDPA.HSDPA+R99 user number counter in a cell • Typical mobile in a market will support only HSDPA while using R99 in UL.VS.Cell • • A HSDPA User consume 1*SF256 (1 CE) in DL for A-DCH UL CE consumes up to bit rate of DCH . Number of HSDPA+R99 User = VS. Therefore.UE.UE.Mean.
256+VS.RB.RB.DLInterPS.DLStrPS.RB.DLInterPS.64+VS .DLStrPS.RB.DLInterPS.RB.DLBkgPS.128+VS.RB.DLInterPS.RB.RB.RB.8+VS.8 VS.8+VS.DLStrPS.DLConvPS.DLInterPS.144+VS.RB.R B.RB.128+VS.DLInterPS.32+VS.RB.DLStrPS.RB.DL+UL PS R99 user number counter in a cell • Assume that if the UE model supports only DL R99.DLInterPS.DLBkgPS.256+VS.384 • • DL CE consumes up to bit rate of DL DCH UL CE consumes up to bit rate of UL DCH .DLBkgPS.RB.RB.16+VS.144+VS.DLStrPS.DLConvPS.32+VS.16+VS.DLInterPS.RB.DLStrP S.128+VS.32+VS.64+VS.384+VS.RB.RB.RB.RB.256+VS.32+VS. the number of DL+UL R99 is equal to number of DL R99 User Number of DL+UL R99 User = VS.DLBkgPS.RB.RB.1 44+VS.64+VS.64+VS.RB.RB.RB.DLStrPS.8+VS.1 6+VS.DLBkgPS.DLBkgPS.DLConvPS.DLBkgPS.DLBkgPS.16+VS.RB.DLConvPS.
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 .
the admission accepted when code resource is sufficient for the service. . • For other R99 service. the admission accepted when code resource is sufficient for RRC Connection. • For handover. • Dl HandOver Credit and Code Reserved SF = SF32 • For HSDPA service. the admission accepted when code resource after admit the service is less than HandOver Credit and Code Reserved SF.Resource Threshold : DL OVSF Code • For RRC connection setup request. there is no code resource admission.
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] • For a new user. 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.
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. the admission accepted when CE resource is sufficient for the service. • 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 RRC Connection.Resource Threshold : CE (UL/DL) • For RRC connection setup request. • For other service. • For handover.
if code congest from Voice Increase fix HS-PDSCH code. 2. The optimizer should control coverage and parameter e. 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. 6. 5.g. 3. 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. these activities would be performed to increase or balance cell capacity (This is assumed that the site has been well optimization) 1. 7. 4.Capacity upgrade solution In resource expansion. . handover in order to balance between coverage and capacity of itself and surrounding cells. 8.
• If configure multi WBBP card into one DL BB Resource Group. CE is sum of CE from every WBBP cards. One DL BB Resource and UL BB Resource Group 128 UL/DL 128 UL/DL UL CE = 256 DL CE = 128 . 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. CE is CE of only one WBBP card.
The CE License is in 16 CE unit. – If DL CE is congestion. 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 card should be utilized at full license prior to add WBBP.WBBP and CE License up/down grade • Recommendation in CE up/down grade – Add/remove CE License on demand. adding new WBBP card is needed. Add or remove in term of 1 license (smallest unit) is recommended for highest efficiency. – If UL CE is congestion at full license.
2010-09-15 09:45:13 Board Configuration Information ------------------------------Cabinet No. Or using MML command LST BRD +++ BKA9042U O&M #190945 %%LST BRD: SRN=0. Slot No. 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 .%% RETCODE = 0 Succeed. 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.
of UL Process Unit 1 Cabinet No. of DL Process Unit 1 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. 2010-09-15 10:00:30 DL BB Resource Group Information -------------------------------DL BB Resource Group No.%% RETCODE = 0 Succeed. Cabinet No. of DL Process Unit 1 DL BB Resource Group No. of DL Process Unit 1 Slot No.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 UL Process Unit 1 Slot No. 2010-09-15 09:58:33 LST ULGROUP +++ BKA9042U O&M #191359 %%LST ULGROUP:. of UL Process Unit 2 Slot No. of UL Process Unit 1 Subrack No. 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 . of DL Process Unit 1 Subrack No.%% RETCODE = 0 Succeed. Cabinet No. of UL Process Unit 2 Subrack No. of DL Process Unit 1 Subrack No. Cabinet No.
1 . 0 while Local Cell 2 and 3 are sharing the DL BB Group No. Local Cell Configuration(Summary) --------------------------------Local Cell ID Cell ID Site No. 0 1 2 UL BB Resource Group No. 0 1 1 Local Cel Radius(m) l 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. 0 0 0 DL BB Resource Group No. 1 300 2 400 3 500 (Number of results = 3) --END 300 300 300 Sector No.%% RETCODE = 0 Succeed.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.
1dBm) Cell Number in 430(0.%% RETCODE = 0 Succeed.1dBm) Cell Number in 418(0.1dBm) Cell Number in 490(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) 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. CE License should be managed properly DSP License +++ BKA9042U O&M #193826 %%DSP LICENSE:.1dBm) Cell Number in 448(0.CE Configuration and License Information Using NodeB LMT to view UL/DL CE License.1dBm) Cell Number in 478(0.1dBm) Cell Number in 460(0.
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. Although. UL ENU can adjust ranging from 1 – 200 – The concern of increasing UL ENU is RTWP. call admission is success but it may lead to voice quality and drop call problem to itself or other UEs. • Only limit power resource on UL is ENU. .Power congestion solution • As we have analyzed the root cause of power congestion whether UL (ENU) or DL (RRU power). 1 dB step adjust is recommended. The solution would be different up to the type of power congestion. – The performance after increasing UL ENU should be closely monitored. we can slightly reduce the CPICH power. – If coverage is the main concern in the serving area. we can increase 1 dB step adjust is recommended. • If power is congested due to DL power – If coverage is not the issue of the cell.
The trade-off between AMR and HS-PDSCH code allocation is unavoidable according to limit of DL OVSF Code. However. Thus. • 1 SF16 of HS-PDSCH can convert to about 8 AMR (SF128).DL OVSF Code Congestion Solution • At the moment. 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. code congestion would be caused by insufficient code for AMR and PS R99. most of the service congestion due to code should be AMR. PS DL R99 should be very low as most of DL PS RB is HSDPA. Thus. 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.
.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?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.