HUAWEI 3G CAPACITY OPTIMIZATION

For internal use

DOCUMENT INFO
SOFTWARE RELEASE: R11 SCOPE:
• • •
RAN Capacity Monitoring RAN Capacity Optimization Transmission Network Monitoring

CONTENT:
• • •
BLOCKING: Counters expressing congestion and resource unavailability  Reactive Approach UTILIZATION: Counters and formulas expressing proximity to blocking conditions (Used vs. Total Available)  Proactive METHODOLOGY: Parameters dealing with specific resources. Best practices to improve capacity.

CONVENTION:
• • •
Raw counters are marked in BLUE. Parameters are marked in RED. Formulas are marked in GRAY.

For internal use

NETWORK ELEMENTS CAPACITY OVERVIEW
NodeB • UL/DL CEs MS/Client parameters • R99/ HSPA capability and release • Code Utilizat. • Power • Carriers • SW Licenses RNC • Boards (DPU, GCU/GCG, INT, SPU, XPU) • SW/Features Application Servers Gs RF Iub NodeB RF interface • Coverage • Interference • Traffic Iub interface • E1/T1s • UL/DL Bandwidth • ATM & AAL2 • IP • Traffic Iur/Iu interface RNC BSC Iur Iu-PS BSC 3G SGSN Gn IP/MPLS/IPoATM backbone RNC BSC MSC/VLR MSC/VLR HLR/AuC/EIR

Iu-CS

GGSN

Applicatio n Servers (colocated

• Mobility
• Channels • HSxPA
For internal use

• Iur
• ATM & AAL2

recalling CEs when user throughput decreases Service differentiation during network congestion to provide better services for high-priority users 3G/2G Common Load Management Intra-Frequency Load Balance Inter-Frequency Load Balance Inter-RAT Handover Based on Load Intra System Direct Retry Inter System Direct Retry Inter System Redirect WRFD-020310 WRFD-020104 WRFD-020103 WRFD-020306 WRFD-02040001 WRFD-02040002 WRFD-02040003 Transfer of load information between 2G and 3G during inter-RAT handover or inter-system direct retry For UEs is in SHO. some UEs are handed over to an inter-frequency co-coverage cell For cells in initial congestion state.CAPACITY FEATURES OVERVIEW BASIC FEATURES Admission Control Load Measurement Load Reshuffling Overload Control Dynamic Channel Configuration Control (DCCC) Code Resource Management Fast Power Congestion Control (FCC) BSC/RNC Resource Sharing License Management LOAD CONTROL Potential User Control CODE WRFD-020101 WRFD-020102 WRFD-020106 WRFD-020107 WRFD-021101 WRFD-020108 WRFD-010208 MRFD-210104 MRFD-210403 CODE WRFD-020105 DESCRIPTION It combines multiple resources to perform admission control over R99 service requests Load measurement for load control Multiple load reshuffling policies for cells in basic congestion. it can restrict user access based on the service class allowed by SIB The UE is handed over to the relevant hierarchical cell according to its moving speed Fast adjustment of CE allocation based on actual and GBR. to decrease cell load and increase accessibility Multiple load adjustment methods for cells in overloaded state to fast decrease the cell load Dynamic rate reallocation and UE state transition that can be triggered by multiple sources Allocation and reshuffling of downlink code tree resources Quickly rectifies system overload to prevent the output power from exceeding the max power allowed by HW Resource sharing of user and control plane in the MBSC. PCPICH power decrease can remove the cell from the Active Set. calls can be setup in an inter-RAT neighbor cell (hard handover) At admission failure of new calls (RRC). adopting intra/inter-subrack load sharing of boards MBSC and MBTS license control DESCRIPTION Cell selection/reselection of the UE to camp on an appropriate cell according to its load Access Class Restriction Hierarchical Cell Structure (HCS) Dynamic CE Resource Management Queuing and Pre-Emption WRFD-021103 WRFD-021200 WRFD-010638 WRFD-010505 When the cell or system is overloaded. so reducing the cell load For cells in initial congestion state. setup can be in an inter-RAT neighbor cell (inter-system cell reselect) For internal use . some UEs are handed over to an inter-RAT co-coverage cell At admission failure of new calls (RRC or RAB). calls can be setup in an inter-frequency neighbor cell At admission failure of new calls (RAB).

load balancing. and more traffic is admitted (opposed to max bandwidth allocation) The RNC adjusts the available transport bandwidth according to packet loss rate and jitter Load balancing between multiple CN nodes Multiplexing of FP packets on the IP network to improve TX efficiency Multiple RTP units are encapsulated in one UDP packet on the Iu-CS to improve TX efficiency For internal use . and traffic balancing between frequency bands Inter-freq measurement for HO decision of inter-freq HO based on traffic steering or load sharing TX diversity enables the NodeB to provide twice the number of RF DL channels compared with no TX diversity (in TX diversity mode. especially on Iub interface and when deploying HSDPA Iub Overbooking CAC algorithm: service actually occupied bandwidth is estimated through service active factor. and Iu-CS (basic feature) Accept or reject some access requests to maximize the utilization of TX resources (basic feature) It enables the Iub interface to be carried on the IP network It improves usage efficiency in ATM TX.CAPACITY FEATURES OVERVIEW LOAD CONTROL (CONTINUE) Rate Negotiation at Admission Control Service Steering and Load Sharing in RRC Connection Setup Traffic Steering and Load Sharing During RAB Setup RAB Quality of Service Renegotiation over Iu Interface Multi Frequency Band Networking Management Enhanced Multiband Management Transmit Diversity CODE WRFD-010507 WRFD-020120 WRFD-02040004 WRFD-010506 WRFD-020110 WRFD-020160 WRFD-010203 DESCRIPTION QoS negotiation and RAB downsizing on the Iu interface Service and load sharing between different frequencies. Iur. bands or systems based on service type and cell load Service load and required service type considered during RAB setup to implement traffic steering and load sharing between different frequencies or bands RNC renegotiation (decrease) on the Iu interface of MBR and GBR of PS real-time services Mobility management. the UE must support diversity reception) 4-Antenna Receive Diversity Control Channel Parallel Interference Cancellation (CCPIC) TRANSMISSION Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Call Admission Based on Used AAL2 Path Bandwidth IP Transmission Introduction on Iub Interface Overbooking on ATM Transmission Overbooking on IP Transmission Dynamic Bandwidth Control of Iub IP Iu Flex Load Distribution Management FP MUX for IP Transmission UDP MUX for Iu-CS Transmission WRFD-010209 WRFD-010210 CODE WRFD-05030104 WRFD-05030106 WRFD-050402 WRFD-050405 WRFD-050408 WRFD-050422 WRFD-021306 WRFD-050420 WRFD-050412 The NodeB provides twice the number of RF UL channels compared with 2-antenna RX diversity Reduced UL interference and improved network capacity DESCRIPTION Establishment of dynamic AAL2 connections on Iub.

thus improving demodulation signal-noise ratio (SNR) and increasing UL capacity DESCRIPTION Continuous Packet Connectivity (CPC) UL Discontinuous Transmission (DTX) / DL Discontinuous Reception (DRX) to reduce the interference between UEs and improve the HSPA+ user capacity It allows HS-DSCH not to be accompanied by HS-SCCH when sending predefined small transport blocks It enables a single HSDPA cell to support simultaneously 96 HSDPA VoIP or other low-rate users It enables a single HSUPA cell to support simultaneously 96 HSUPA VoIP or other low-rate users It enables a single HSDPA cell to support simultaneously 128 HSDPA VoIP or other low-rate users It enables a single HSUPA cell to support simultaneously 128 HSUPA VoIP or other low-rate users . admission and congestion control of TX resources for different HSUPA users It enables a single HSUPA cell to support 20 HSUPA users simultaneously It enables a single HSUPA cell to support 60 HSUPA users simultaneously Monitoring of Iub TX resources to dynamically adjust the uplink Uu throughput IC is performed to offset the interference of E-DPDCH data of other users. remaining power resources. Iub resources and service rate thresholds Dynamic code allocation on the NodeB side in each TTI Static or dynamic allocation of HS-PDSCH codes when R99 and HSDPA co-exist Power control mode of HS-SCCH It enables R99 and HSDPA services to share the cell power It enables different HSDPA services to be mapped onto different paths It enables a single HSDPA cell to support 16 HSDPA users simultaneously It enables a single HSDPA cell to support 32 HSDPA users simultaneously It enables a single HSDPA cell to support 64 HSDPA users simultaneously The NodeB allows the carrier carrying HSDPA services to share the unused power resources of another carrier carrying R99 services DESCRIPTION It improves the UL processing capability of the WBBPb board and makes HSUPA services occupy less CE resources (basic feature) It enables HSUPA and R99 services to simultaneously access the network Dynamically adjusts the HSUPA min SF based on user throughput and switch the UE state based on user traffic Mapping.HSDPA HSDPA Admission Control Dynamic Code Allocation Based on Node B HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation HSDPA Power Control HSDPA Dynamic Power Allocation HSDPA Transport Resource Management 16 HSDPA Users per Cell 32 HSDPA Users per Cell 64 HSDPA Users per Cell Dynamic Power Sharing of Multi-Carriers HSUPA Improved CE Mapping for E-DCH HSUPA Admission Control HSUPA DCCC HSUPA Transport Resource Management 20 HSUPA Users per Cell 60 HSUPA Users per Cell HSUPA Iub Flow Control in Case of Iub Congestion HSUPA UL Interference Cancellation HSPA+ CPC-DTX/DRX CPC-HS-SCCH Less operation 96 HSDPA Users per Cell 96 HSUPA Users per Cell 128 HSDPA Users per Cell 128 HSUPA Users per Cell CODE WRFD-01061003 WRFD-010631 WRFD-01061005 WRFD-01061004 WRFD-01061019 WRFD-01061014 WRFD-01061016 WRFD-010622 WRFD-010623 WRFD-020116 CODE WRFD-010212 WRFD-01061202 WRFD-01061208 WRFD-01061207 WRFD-01061211 WRFD-010634 WRFD-010637 WRFD-010691 CODE WRFD-010686 WRFD-010687 WRFD-010653 WRFD-010639 WRFD-010654 WRFD-010670 DESCRIPTION It considers number of HSDPA users. allocation.

Congstion.AttConnEstab. VS. VS.Cell)*100%.RAC.Congstion.RAB.Congstion.CS.Congstion.PS.CS.FailConnEstab. VS.LCC.RAB.RAC.RAB.PS.RAC.NewCallReq: Number of Cell Resource Requests for a new call.Loss. VS.Cell: Number of RRC Connection Attempts.RAB.CELL. • CALL RELEASE: • CS RAB Release Congestion Ratio(Cell) = (VS. For internal use .Norm)*100%. VS.CELL/VS.RAB.BLOCKING OVERVIEW The following KPIs can be used to trigger further analysis to investigate the need for capacity expansion: CALL ADMISSION: • RRC Attempt Congestion Ratio(Cell) = (RRC.NewCallReq)*100%.PS.RAB.Loss. OVERLOAD CONGESTION: • Congested Cell Ratio = [(Number of cells where VS. Call Admission Refused Ratio(Cell) = (1-VS.Loss.OverCongNumDL>0) / Number of cells in RNC)]*100%. VS.LCC. RRC.RAB.CS.CS.AttConnEstab.NewCallAcc: Number of Successful Cell Resource Requests for a new call.OverCongNumUL.PS.CELL: Number of released RABs due to cell congestion.Cong/VS.RAC.LCC.NewCallAcc/VS. VS.OverCongNumDL: Number of UL/DL Overload Congestions.RRC.Norm)*100%. PS RAB Release Congestion Ratio(Cell) = (VS.Cong: Number of RRC Connection Reject due to network congestion. VS.CELL/VS.RRC.Norm: Number of RABs normally released. VS.Loss.Loss.Loss.RAB.Loss.FailConnEstab.OverCongNumUL>0 or VS.LCC.Norm.Loss.

stadiums.METHODOLOGY OVERVIEW The following steps are recommended: • • Monitor constantly blocking and utilization of network elements and interfaces. • • The rest of the presentation will focus on how to increase NE/Interface capacity.). [Alarm Threshold is the Max Recommended Load. weekdays/weekends). azimuths. Check patterns of behaviour (hours of occurrence. Increase support from existing NEs (coverage. IF (Blocking > 0) OR (Utilization > Alarm Threshold) THEN Increment weekly counting of that specific NE/Interface. For internal use . etc. tilts. concert halls. typically around 80% ] IF (Weekly counting > 0) Every week of a month THEN Check duration of the problem.). Check blocking/utilization of adjacent elements (homogeneously spread or unbalanced). Introduce solution: Re-establish full availability. Add NEs. Increase NE/Interface capacity. shopping centres. etc. Check surroundings (theatres. Check unavailability of adjacent elements.

• IU Paging Congestion Ratio(RNC) =[(VS. VS.CsPaging.CsPaging.RANAP.CellPCHUEs: Number of UEs in CELL_PCH State. UTILIZATION: • VS.Loss: Number of Failures to Respond to PS-Oriented PAGING Messages from the CN.Loss: Number of Failures to Respond to CS-Oriented PAGING Messages from the CN.RANAP. especially during busy hours.CRNCIubBytesPCH.Loss.Cell/VS. FACH RACH.UTRAN.PsPaging. • VS.Cell: Number of losses of PAGING TYPE 1 message due to PCH congestion.Tx: DL bytes received by the CRNC (Controlling RNC) on the PCH over the Iub interface.Loss)/(VS.Loss.Att +VS. Traffic on the PCH: • VS.Loss+VS.MAC.RANAP.PsPaging.Att)]*100%. Consumption of PCCH bandwidth within IU interface can be monitored.Bandwidth: CRNC PCH Channel Bandwidth on the Iub interface (byte/s).PCH BLOCKING: • • • VS.AttPaging1)*100%.RANAP. FACH For internal use . Logical CH PCCH mapped into … Transport CH PCH BCCH CCCH … … BCH. VS.RRC. through: • IU Paging Congestion Ratio(Cell) = (VS.PCHCong.PCH.IUB.CsPaging.RRC.CRNC.Paging1.PsPaging.Paging1.RANAP.PCHCong.RANAP.

CRNC.RRC. • VS. Traffic on the RACH: • VS.AttConEst.CcchSrbKbps.CCH: Number of Successful RRC Connection Setups in CELL_FACH (VS.CcchSrbKbps. • VS.Dl: DL throughput of CRNC on the CCCH of the Iub interface (kbit/s). For internal use . Traffic on the FACH: • VS.Ul. • VS. CELL_FACH State: • VS.Tx: DL bytes sent by the CRNC on the FACH over the Iub interface.CRNCIubBytesFACH.IUB.OTHER CHANNELS UTILIZATION: Traffic on the BCCH: • VS.Dl: DL throughput of CRNC on the BCCH of the Iub interface (kbit/s).MAC.MAC. VS.RACH.CCH: Number of RRC Connection Attempts in CELL_FACH (compare with VS.CellDCHUEs).Bandwidth: CRNC RACH Channel Bandwidth on the Iub interface (byte/s).DCH).SuccConEst. • VS.IUB. Traffic on the CCCH: • VS.CellFACHUEs: Number of UEs in CELL_FACH state (compare with VS.RRC.CRNC.Rx: UL bytes sent by the CRNC on the RACH over the Iub interface.RRC.AttConEst.CRNCIubBytesRACH.DCH).RRC.Bandwidth: CRNC FACH Channel Bandwidth on the Iub interface (byte/s).BcchSrbKbps.SuccConEst.FACH.

Fail.ULMax.CELL.LDR.LCC.Cong: Number of RRC Connection Reject.ULCE.LC.RAC.RAB.ULCE: Duration in seconds of LDR State due to UL CE Resource Congestion. UL CE Utilization Ratio(NodeB) = (VS.Fail.Time.ULCE. VS.DCCC. VS.RAC.Fail.ULCreditAvailable. UTILIZATION: • • VS.LicenseGroup.SHO.ULCE: Number of times a cell is in LDR (Load Reshuffling) State due to UL CE Resource Congestion.UL.Shared: Number of UL CEs licensed.RAC.Shared / VS.ULCreditUsed.ULMax.Cong: Number of failures in the Channel Switch procedure. VS.Max: Maximum UL credit usage.Cong: Number of CS RABs unsuccessfully established.LDR.ULCE.LC.UL CE BLOCKING: • • • • • • • • • • VS.RAC.Shared)*100%.FailEstCs. VS.RAC. For internal use .LC.FailEstPs.Cong: Number of PS RABs unsuccessfully established.Cong: Number of failures in the SHO procedure.NewCallRequest.Num. VS.ULCE. VS.ULCE.Fail.ULCreditAvailable. VS.RRC.LCC.Fail.HHO.CE. VS.Cong: Number of failures in the DCCC procedure.Cong: Number of failures in the HHO procedure.LC.LicenseGroup. VS.Rej. VS.Cong: Number of failures in the RRC/RAB SETUP procedure.LC.RAB.TrChSwitch. VS.ULCE.Shared: Max usage of UL CEs.ULCE.

UL CE METHODOLOGY: • If congestion is spread among different hours and days.6 kbit/s SRB UL 64 1 2 12. UlRateDnAdjLevel (DCCC): Uplink Rate Decrease Adjust Level.5 3 32 kbps PS UL 16 3 6 64 kbit/s PS UL 8 5 10 128 kbit/s PS UL 4 10 20 384 kbit/s PS • For internal use . UlDcccRateThd (DCCC): Uplink Bit Rate Threshold for DCCC.4 kbit/s SRB UL 64 1 2 13. UlGBR (USERGBR): Uplink GBR for BE service.2 kbit/s AMR UL 16 3 6 64 kbit/s VP UL 32 1. and on the same NodeB. the following parameters can be used to decrease the usage of UL CEs (see table below): UlMidRateThd (DCCC): Uplink Mid Bit Rate Threshold. UlFullCvrRate (DCCC): Uplink Full Coverage Bit Rate. Additional options are: Decrease the Max Bit Rate Add more UL CEs Direction Spreading Number of Corresponding Typical Traffic Factor CEs Consumed Credits Class Consumed UL 256 1 2 3. UlRateUpAdjLevel (DCCC): Uplink Rate Increase Adjust Level. If set to 3_Rates can be reduced to 2_Rates. If set to 2_Rates can be increased to 3_Rates.

UL CE RB Reallocation based on Traffic Volume or Throughput (Throughput: only rate decrease) RB Reallocation based on Link Quality RB Reallocation based on Congestion Parameter UlRateDnAdjLevel UlRateUpAdjLevel MBR UlMidRateThd UlDcccRateThd UlFullCvrRate Value (Example) 3_Rates 3_Rates 384 kbit/s 144 kbit/s 64 kbit/s 64 kbit/s UlGBR 32 kbit/s For internal use .

FailEstPs.FailEstCs. VS.Cong: Number of CS RABs unsuccessfully established.HHO.DCCC.RAB.DLCE.LCC.Fail.RAC.Fail.Cong: Number of failures in the Channel Switch procedure. For internal use .CELL.LicenseGroup.Cong: Number of failures in the DCCC procedure.LC.RAC.Fail.LDR. VS.Cong: Number of RRC Connection Reject.LCC.LC.LC.Shared)*100%. UTILIZATION: • • VS.DLCE.Time.DLMax. VS.DLCreditAvailable.Fail.DLCE.RRC. VS.DLCE.RAC.Fail.Cong: Number of failures in the HHO procedure.DLCE.TrChSwitch.NewCallRequest.LC.Cong: Number of failures in the SHO procedure.Shared / VS.Max: Maximum DL credit usage.DLCE: Duration in seconds of LDR State due to DL CE Resource Congestion. VS.RAC.Num. VS.DLCreditUsed.DLCE.Rej.DLCreditAvailable.RAC.Shared: Max usage of DL CEs.CE. VS. VS. VS.DLCE.DLMax.LC.DL. VS. VS.LicenseGroup.SHO.LDR. DL CE Utilization Ratio(NodeB) = (VS.DLCE: Number of times a cell is in LDR State due to DL CE Resource Congestion.DL CE BLOCKING: • • • • • • • • • • VS.RAB.Cong: Number of failures in the RRC/RAB SETUP procedure.Shared: Number of DL CEs licensed.Cong: Number of PS RABs unsuccessfully established.

and on the same NodeB. If set to 2_Rates can be increased to 3_Rates.4 kbit/s SRB DL 128 1 1 13. DlRateUpAdjLevel (DCCC): Downlink Rate Increase Adjust Level. Additional options are: Decrease the Max Bit Rate Add more DL CEs Direction Spreading Number of Corresponding Typical Traffic Factor CEs Consumed Credits Class Consumed DL 256 1 1 3. the following parameters can be used to decrease the usage of DL CEs (see table below): DlMidRateThd (DCCC): Downlink Mid Bit Rate Threshold. If set to 3_Rates can be reduced to 2_Rates. DlDcccRateThd (DCCC): Downlink Bit Rate Threshold for DCCC.2 kbit/s AMR DL 32 2 2 64 kbit/s VP DL 64 1 1 32 kbps PS DL 32 2 2 64 kbit/s PS DL 16 4 4 128 kbit/s PS DL 8 8 8 384 kbit/s PS • For internal use . DlRateDnAdjLevel (DCCC): Downlink Rate Decrease Adjust Level.6 kbit/s SRB DL 128 1 1 12.DL CE METHODOLOGY: • If congestion is spread among different hours and days. DlFullCvrRate (DCCC): Downlink Full Coverage Bit Rate. DlGBR (USERGBR): Downlink GBR for BE service.

6RL)/(VS.Cong: Number of failures in the SHO procedure.Num.AS. VS.RRC. Code are occupied by the common channels.Code. VS.TrChSwitch.LCC.4RL+VS. NodeB Performance Counters: VS.SHO.SHO.Max: Maximum number of codes available for HS-PDSCHs in a cell during a measurement period. VS.Max: Maximum number of codes used by HS-PDSCHs in a cell during a measurement period.SHO.SHO.SHO.PdschCodeUsed.SHO.Cong: Number of failures in the DCCC procedure.AS. converted to the code number when SF = 256.OVSF.OVSF.1RL+VS.SHO.AS.2RL/2+VS.3RL+VS.LDR.6RL/6)-1]*100%. VS.SHO.DLCode: Duration in seconds of LDR State due to Code Resource Congestion. • For internal use .Rej.SFOccupy.Time.Cong: Number of RRC Connection Reject. VS.AS.Code.OVSF.RAB.CODE BLOCKING: • • • • • • • • • VS.FailEstCs.DLCode: Number of times a cell is in LDR State due to Code Resource Congestion.DCCC.RAC. VS.Fail.4RL/4+VS.AS.RAB.A S.SFOccupy.FailEstPs.RAB. UTILIZATION: • Code Utilization Ratio(Cell) = (VS.Code. VS. VS. VS.SHO.CodeAdj: Number of UEs for Code Adjustment in Basic Congestion. Optimal value is Soft Handover Overhead = 1.xRL: Mean Number of UEs with x RL.4.LCC.Fail.PdschCodeAvail.AS.AS.Cong: Number of CS RABs unsuccessfully established. R99 users and HS-DSCH.3RL/3+VS.RAC.SHO.Fail.5RL/5+VS. VS.AS.SHO.MAX / 256)*100%.Cong: Number of PS RABs unsuccessfully established.SHO. but it depends also on the area (urban/rural).5RL+VS.AS.RAB.Cong: Number of failures in the Channel Switch procedure.SHO. The code number is normalized to SF = 256.AS.LDR.1RL+VS.AS.LCC.AS.3 ~ 1. VS.2RL+VS.MAX: Maximum number of SFs codes in a cell.RAC. Soft Handover Overhead(Cell) = [(VS. that is.SHO. Code resources could be wasted because of too many cells in SHO.LDR.

In case of LDR based on code resources. [Code reshuffling could be triggered only when the minimum available SF of a cell is higher than this threshold ] ULLDRCREDITSFRESTHD. the codes with high priority are reserved during code reshuffling ] Other relevant LDR actions to control code shortage are Inter-Frequency Load Handover and BE Rate Reduction. Code Reshuffling is controlled through: MAXUSERNUMCODEADJ (CELLLDR): Max user number of code adjust. [Number of users selected in code reshuffling] LdrCodePriUseInd (CELLLDR): LDR code priority indicator.CODE METHODOLOGY: • In case of CAC based on code resources. DLLDRCREDITSFRESTHD(CELLLDR): UL/DL LDR Credit SF reserved threshold. Low value  Higher admission success rate but easier congestion status  Easier LDR action trigger] Many LDR actions can be performed. CELLLDRSFRESTHD). [If TRUE. [UL/DL credit LDR could be triggered only when the SF factor corresponding to the UL/DL reserved credit is higher than the UL or DL credit SF reserved threshold. • • • For internal use . triggering can be controlled through: CELLLDRSFRESTHD (CELLLDR): Cell LDR SF reserved threshold. [Quantity of DL code (SF) and CE resources reserved for handover UEs] Rule: DlHoCeCodeResvSf ≥ max(DLLDRCREDITSFRESTHD. Particularly for Code Basic Congestion. the only parameter controlling triggering is: DlHoCeCodeResvSf (CELLCAC): DL Handover Credit and Code Reserved SF.

SHO.FailEstPs.Cong: Number of failures in the Channel Switch procedure. For internal use .RAC.Power.POWER BLOCKING: • • • • • • • • • • • • • VS.DLLD.Cong.Num.DLPower: Number of times a cell is in LDR State due to Power (Equivalent Number of Users) Congestion.HHO.ULLD.Time.Cong: Number of failures in the HHO procedure. UL Interference Cell Ratio(RNC) = [(Number of Cells where VS.LDR.Cong: Number of failures in the DCCC procedure.ULPower.DLPower: Duration in seconds of LDR State due to Power (Equivalent Number of Users) Congestion.RAB. VS.HSUPA.LDR.LDR. VS.MeanRTWP: Mean Received Total Wideband Power (dBm).Fail.Fail. VS.ULLD.Fail.LCC.MeanRTWP>-98dBm)/Total Number Of Cells In RNC]*100%.SHO. VS.DCCC.Cong: Number of RRC Connection Reject.TrChSwitch.RAB.RAC. VS.DLLD.Cong.Rej.R99. UTILIZATION: • • • VS.Fail..Power. VS. VS.RAC.Fail.DCCC.ULPower.RAC.Cong: Number of admission failures due to HSDPA Power resource insufficiency.Cong.Power.MeanTCP: Mean Transmitted Carrier Power (dBm). VS.Cong: Number of failures in the SHO procedure.Power.Cong: Number of admission failures due to R99 Power resource insufficiency.Fail. VS. VS.LCC.Cong: Number of PS RABs unsuccessfully established. VS.Fail.HSDPA. VS. VS. VS.RRC.LCC.RAC.RAC.Cong: Number of admission failures due to Total Power resource insufficiency.DLLD.Total.RAC. VS.HHO.ULLD. VS.FailEstCs.LDR.Cong.LCC.Cong: Number of admission failures due to HSUPA Power resource insufficiency.Time.Power. VS.TrChSwitch.Cong: Number of CS RABs unsuccessfully established.MaxTCP: Max Transmitted Carrier Power (dBm).RAC.Power.DLLD. VS.RAC.RAC.Power.RAC.RAC.ULLD.Num. VS.Fail. VS.

the controlling parameters depend on the Algo used. [These thresholds are a percentage of the 100% downlink load. For internal use . UlNonCtrlThdForNonAMR) > UlNonCtrlThdForOther For Algo2: ULTOTALEQUSERNUM. DLTOTALEQUSERNUM (CELLCAC): UL/DL total equivalent user number. For Algo1&3: UlNonCtrlThdForAMR. DLHOTHD (CELLCAC): UL/DL Handover access threshold.MeanRTWP and VS. DLCONVNAMRTHD) > DLOTHERTHD UlNonCtrlThdForHo > max(UlNonCtrlThdForAMR. UlNonCtrlThdForOther. Check VS. DLCONVAMRTHD (CELLCAC): UL/DL threshold of Conv AMR.MaxTCP of the cell to determine whether the rejection is due to UL or DL congestion.POWER METHODOLOGY: • In case of CAC based on power resources. DLCONVNAMRTHD (CELLCAC): UL/DL threshold of Conv non_AMR. UlNonCtrlThdForHo. UlNonCtrlThdForNonAMR. DLOTHERTHD (CELLCAC): UL/DL threshold of other service. If the UL/DL load of a cell is higher than these thresholds after the access of a service. [Total equivalent user number corresponding to the 100% uplink load] • RRC connection request is rejected upon UL or DL admission decision by RRM. this service will be rejected ] Rules: DLHOTHD > max(DLCONVAMRTHD.

DLLDRTRIGTHD (CELLLDM): UL/DL LDR trigger threshold. Particularly for Power Basic Congestion.POWER METHODOLOGY: • In case of LDR based on power resources. [MBMS provides unidirectional point-to-multipoint multimedia services. • • For internal use . UL load reshuffling is stopped ] Many LDR actions can be performed. DLLDRRELTHD (CELLLDM): UL/DL LDR release threshold. MBMS (Multimedia Broadcast Multicast Service) Power Reduction is controlled through: MBMSDECPOWERRABTHD (CELLLDR): MBMS descend power RAB threshold. [If (UL Load / UL Capacity) of the cell is not lower than this threshold. BE Rate Reduction and InterRAT Handover in the CS Domain. triggering can be controlled through: ULLDRTRIGTHD. When the priority of the RAB of MBMS services exceeds this threshold. reconfigure the MBMS power to the minimum power ] Other relevant LDR actions to control power shortage are Inter-Frequency Load Handover. [If (UL Load / UL Capacity) of the cell is lower than this threshold. UL load reshuffling is triggered ] ULLDRRELTHD.

VS.HSDPA.BE.HSDPANum.UserRel: Number of UEs released due to Overload Congestion.OLC.HSDPA.InterRATPS: Number of HSDPA UEs that perform PS inter-RAT handover because of Basic Congestion.Cong: Number of failures in the HHO procedure.Mean.Fail. UTILIZATION: • VS.TrChSwitch.HSDPANum. • HSDPA Utilization Ratio(Cell) = [maxHours(VS.Fail. VS.LDR.RelReqPS.Cong.HSDPA.Mean. In case of CAC based on the number of HSDPA users.BE. WRFD-010622: 32 HSDPA Users per Cell.HSDPA.Cong: Number of failures in the Channel Switch procedure.HSDPA. VS. VS.RAB.HSDPANum. WRFD-010623: 64 HSDPA Users per Cell. For internal use .RAB.UE.BE.HHO.Fail. VS.RAB.Copper: Number of released PS BE RABs beared on HSDPA. VS.Cell) / MaxHsdpaUserNum]*100%.Cell: Number of UEs in CELL_HSDPA state in a cell.Cong.RelReqPS.Cong.NewCallRequest.HSDPA.HSDPA BLOCKING: • • • • • • • VS. Its value is related to the presence of the following features: WRFD-01061016: 16 HSDPA Users per Cell.UE.RAC.RAC. VS.RAC.Cong: Number of failures in the RRC or RAB SETUP procedure.Silver.HSDPA.Golden.InterFreq: Number of HSDPA UEs that perform inter-frequency handover because of Basic Congestion. VS.RelReqPS.LDR. the controlling parameter is: • MaxHsdpaUserNum (CELLCAC): Maximum HSDPA user number (based on cell type and available HSDPA power and code resources).HSDPA.

HSDPA METHODOLOGY: • If Basic Congestion is triggered. Basic Congestion is a ‘normal’ situation and the ideal LDR action for HSDPA users is inter -frequency handover to balance the load.InterRATPS (typically the PS inter-rat handover algorithm switch is disabled. DLOLCRELTHD (CELLLDM): UL/DL OLC release threshold. Overload Congestion instead requires the release of HSDPA users. DLOLCTRIGTHD (CELLLDM): UL/DL OLC trigger threshold. [If (UL Load / UL Capacity) of the cell is lower than this threshold. For internal use . and HSDPA calls are preferred dropping rather than handing over to 2G).LDR.LDR.InterFreq is incremented. [If (UL Load / UL Capacity) of the cell is not lower than this threshold. but not VS. Overload Congestion is triggered by: ULOLCTRIGTHD.HSDPA. UL overload is triggered ] ULOLCRELTHD. make sure that VS. • Specify a HSDPA-only carrier to avoid basic congestion conditions being triggered. UL overload is stopped ] • Additional actions to increase capacity: • Divide users between Gold. Silver and Copper and/or modify their priorities: UserPriority (SCHEDULEPRIOMAP). • Introduce an additional carrier.HSDPA.

VS. the controlling parameter is: • MaxHsupaUserNum (CELLCAC): Maximum HSUPA user number (based on cell type and available HSUPA power and code resources).Fail.HSUPA.NewCallRequest.HSUPA.Cell) / MaxHsupaUserNum]*100%.HSUPA.Cong: Number of failures in the SHO procedure. VS.RAC.Cong: Number of failures in the Channel Switch procedure. In case of CAC based on the number of HSUPA users.Fail.RAB. VS.RAC.HSUPA BLOCKING: • • • • • VS.UE.HHO.HSUPANum.Cong.TrChSwitch.HSUPA. VS.HSUPANum.Fail.Mean.HSUPANum.RelReqPS.UE. VS.HSUPANum.Cong: Number of failures in the RRC or RAB SETUP procedure. VS.Cong.Silver.SHO.Cong: Number of failures in the HHO procedure. Its value is related to the presence of the following features: WRFD-01061211: 20 HSUPA Users per Cell. For internal use .BE.HSUPA.Fail.RAB.Cell: Number of UEs in CELL_HSUPA state in a cell. WRFD-010634: 60 HSUPA Users per Cell.RAC. • HSUPA Utilization Ratio(Cell) = [maxHours(VS.Copper: Number of released PS BE RABs beared on HSUPA.RelReqPS.Cong.RAB.BE.RAC.Golden.RelReqPS.BE. UTILIZATION: • VS.Mean.

For internal use . Overload Congestion is triggered by: ULOLCTRIGTHD. • Specify a HSUPA-only carrier to avoid basic congestion conditions being triggered. DLOLCRELTHD (CELLLDM): UL/DL OLC release threshold. Silver and Copper and/or modify their priorities: UserPriority (SCHEDULEPRIOMAP). DLOLCTRIGTHD (CELLLDM): UL/DL OLC trigger threshold. Additional actions to increase capacity: • Divide users between Gold. • Introduce an additional carrier. ULOLCRELTHD. Overload Congestion instead requires the release of HSUPA users.HSUPA METHODOLOGY: • Basic Congestion is a ‘normal’ situation and the ideal LDR action for HSUPA users is inter -frequency handover to balance the load.

VS.1+VS.ULIub: Number of times a cell is in LDR State due to UL Iub Transmission Resource Congestion.HHO.ATMUlTotal.IPUlTotal.ULIUBBand.ATMUlAvgUsed.RAC.RAC.ATMUlAvgUsed.LDR.Cong: Number of failures in the HHO procedure. VS.x: Available UL bandwidth of an IP physical port during a measurement period.RAB.LCC.IPUlAvgUsed. For internal use .ATMUlTot al.LCC.x: Average used UL bandwidth on an ATM physical port during a measurement period.Num.Fail. VS. configured Iub bandwidth: • IUB UL Bandwidth Utilizing Ratio = [(VS.ATMUlAvgUsed.2+VS.x: Available UL bandwidth of an ATM physical port during a measurement period.3+VS. VS.ULIub.ATMUlTotal.ULIub: Duration in seconds of LDR State due to UL Iub Transmission Resource Congestion.1+VS.4)]*100%.IPUlTotal.ATMUlTotal.3+VS.ATMUlTotal.UL IUB BANDWIDTH BLOCKING: • • • • • • • • • VS.ULIub.Fail. UTILIZATION: Consumed vs.RAC.SHO.x: Average used UL bandwidth on an IP physical port during a measurement period. VS.LDR.FailEstab. VS.Cong: Number of failures in the SHO procedure. VS.Rej.2+VS.2+VS.ULIUBBand.ULIUBBandCong: Number of RRC Connection Reject.IUB.IPUlAvgUsed.1+VS.Cong: Number of failures in the Channel Switch procedure.Cong: Number of PS RABs unsuccessfully established. VS.4+VS.IPUlTotal.CongUL: Number of UL congestions on Iub Interface. VS.Fail.IPUlAvgUsed.ATMUlAvgUsed.3+VS.1+VS. VS.ATMUlAvgUsed.FailEstab.CS.ULIub. VS. VS.4)/(VS.IPUlAvgUsed.Cong: Number of CS RABs unsuccessfully established.IPUlA vgUsed.TrChSwitch.IPUlTotal.4+VS.RRC.2+VS.3+VS.Time.RAB.IPUlTotal.PS.

NodeB. Factor (%) [If the available forward/backward bandwidth is greater than this value. triggering can be controlled through: FWDCONGBW. AMR voice R99 CS conversational R99 CS streaming R99 PS conversational R99 PS streaming R99 PS interactive R99 PS background HSUPA SRB HSUPA IMS SRB HSUPA voice HSUPA conversational HSUPA streaming HSUPA interactive HSUPA background When Iub congestion counters are not null: • Control that NodeB was not unavailable during the period of congestion: VS. so its functionality is not controlled by LDR switches. BWDCONGBW: Forward/Backward congestion threshold.OM • Optimize triggering thresholds. • Eventually increase Iub capacity. forward/backward congestion control is triggered] Type of Service UL/DL Default Activity FWDCONGCLRBW.UnavailTime. For internal use . background) = GBR x Activity Factor Only GBR could be an option to avoid CAC being triggered.UL IUB BANDWIDTH METHODOLOGY: • In case of CAC based on Iub resources: Reserved BW for RT service (signalling. In case of LDR based on Iub resources. BWDCONGCLRBW: Fwd/Bwd congestion clear threshold. streaming) = MBR x Activity Factor Reserved BW for NRT service (interactive. voice. General common channel UL 70 forward/backward congestion control is stopped] IMS SRB UL 15 SRB UL UL UL UL UL UL UL UL UL UL UL UL UL UL UL 15 70 100 100 70 100 100 100 50 15 70 70 100 100 100 • • Iub congestion control is implemented in a separate processing module. [If the available forward/backward bandwidth is less than or equal to this value. • Optimize LDR actions. LDR actions are applied to congestion resolution. In the case of Iub congestion. however.

Cong: Number of CS RABs unsuccessfully established.2+VS.3+VS.2+VS.Cong: Number of failures in the SHO procedure.ATMDLAvgUsed.ATMDLAvgUsed.ATMDLTotal.3+VS.DLIUBBand.Fail.x: Average used DL bandwidth on an IP physical port during a measurement period.4)/(VS.RAC.DLIub. UTILIZATION: Consumed vs.1+VS.DLIUBBandCong: Number of RRC Connection Reject.4)]*100%.IP DLAvgUsed.Fail.2+VS.IPDLTotal.Cong: Number of failures in the Channel Switch procedure. For internal use . VS. configured Iub bandwidth: • IUB DL Bandwidth Utilizing Ratio = [(VS.x: Available DL bandwidth of an IP physical port during a measurement period.IPDLAvgUsed.1+VS.FailEstab.DLIub.1+VS. VS.IPDLTotal. VS.DLIub. VS.ATMDLAvgUsed.FailEstab.RAC.Time.Cong: Number of failures in the HHO procedure. VS. VS. VS.LCC.ATMDLAvgUsed.IPDLAvgUsed.DLIub: Duration in seconds of LDR State due to DL Iub Transmission Resource Congestion. VS.LDR.LCC.ATMDLTotal.TrChSwitch.1+VS.ATMDLTotal.IPDLAvgUsed. VS.x: Available DL bandwidth of an ATM physical port during a measurement period.4+VS.IPDLTotal.Rej.4+VS.RAB.ATMDLAvgUsed.HHO.Num.3+VS.A TMDLTotal.IPDLTotal.3+VS. VS.RAC.IPDLAvgUsed.Cong: Number of PS RABs unsuccessfully established.DL IUB BANDWIDTH BLOCKING: • • • • • • • • • VS.SHO.CongDL: Number of DL congestions on Iub Interface.LDR.IUB. VS.PS.Fail.DLIub: Number of times a cell is in LDR State due to DL Iub Transmission Resource Congestion. VS.DLIUBBand.x: Average used DL bandwidth on an ATM physical port during a measurement period.CS.ATMDLTotal.IPDLTotal.RRC.RAB.2+VS.

BWDCONGBW: Forward/Backward congestion threshold. In case of LDR based on Iub resources. however. so its functionality is not controlled by LDR switches. FWDCONGCLRBW.DL IUB BANDWIDTH METHODOLOGY: • In case of CAC based on Iub resources: Reserved BW for RT service (signalling.NodeB. streaming) = MBR x Activity Factor Reserved BW for NRT service (interactive. background) = GBR x Activity Factor Only GBR could be an option to avoid CAC being triggered.OM • Optimize triggering thresholds. MBMS common channel SRB AMR voice R99 CS conversational R99 CS streaming R99 PS conversational R99 PS streaming R99 PS interactive R99 PS background HSDPA SRB HSDPA IMS SRB HSDPA voice HSDPA conversational HSDPA streaming HSDPA interactive HSDPA background EFACH channel When Iub congestion counters are not null: • Control that NodeB was not unavailable during the period of congestion: VS. triggering can be controlled through: FWDCONGBW. In the case of Iub congestion.UnavailTime. For internal use . • Eventually increase Iub capacity. • Optimize LDR actions. LDR actions are applied to congestion resolution. • Type of Service General common channel UL/DL DL DL DL DL DL DL DL DL DL DL DL DL DL DL DL DL DL DL DL Default Activity Factor (%) 70 15 100 15 70 100 100 70 100 100 100 50 15 70 70 100 100 100 20 • IMS SRB Iub congestion control is implemented in a separate processing module. BWDCONGCLRBW: Fwd/Bwd congestion clear threshold. voice.

AAL2PATH. • VS.Cong.Cong.ATMLGCPRT. • VS.Fwd.Bwd. • VS.Cong.Dur: Duration of Forward Congestions on the ATM Logical Port.ATMLGCPRT.Dur: Duration of Forward Congestions on the AAL2 Path.Cong: Number of Backward Congestions on the AAL2 Path.ATM & AAL2 BLOCKING On the bandwidth assigned to an ATM logical port: • VS.Dur: Duration of Backward Congestions on the ATM Logical Port.Bwd.Bwd.AAL2PATH.Dur: Duration of Backward Congestions on the AAL2 Path. • VS.AAL2PATH.Cong: Number of Forward Congestions on the ATM Logical Port.Fwd.ATMLGCPRT. Feature: Dynamic AAL2 Connections in Iub/IuCS/Iur Interface Feature: Call Admission Based on Used AAL2 Path Bandwidth For internal use . On active AAL2 connections to an adjacent node: • VS. • VS.Cong: Number of Forward Congestions on the AAL2 Path.AAL2PATH.ATMLGCPRT.Cong.Bwd.Fwd.Cong: Number of Backward Congestions on the ATM Logical Port.Fwd. • VS.

IPPATH.Cong: Number of Backward Congestions on Logical Port.Cong: Number of Forward Congestions on Logical Port. • The sender calculates packet loss rate. Introduction on Iub • VS.LGCPRT.Dur: Duration of Backward Congestion on the IP Path.Fwd. On the bandwidth assigned to logical port: • VS.LGCPRT. • VS.IPPATH. Interface • VS.Cong.Bwd.Cong: Number of Backward Congestions on the IP Path. For internal use .Bwd.Cong.IP BLOCKING: On the IP Path: • VS. number of bytes.Fwd.Fwd.Cong: Number of Forward Congestions on the IP Path.Dur: Duration of Forward Congestion on the IP Path.IPPATH. • VS. Feature: IP Transmission • VS.FailResAllocForBwLimit: Number of Failed Resource Allocations due to insufficient bandwidth on the IP Transport Adjacent Node. • VS. the receiving time of PM message and the sending time of BR response. and sending time. • VS. • The peer responds with BR messages after receiving the FM message to report number of received packets.Dur: Duration of Forward Congestions on Logical Port. transmission delay and jitter according to the BR response from the receiver.IPPATH.LGCPRT.Bwd.Fwd.Cong.IP.Dur: Duration of Backward Congestions on Logical Port. Feature: Dynamic Bandwidth Control of Iub IP IP Performance Monitor (PM) uses Forward Monitoring (FM) and Backward Reporting (BR) to check packet loss over channels: • The monitor periodically sends FM messages to indicate number of outgoing packets.Cong.ANI.LGCPRT. number of received bytes.Bwd.

FailRLRecfgIur.FailRLSetupIur.SHO. For internal use .SHO.IUR BLOCKING: Related to DRNC: • VS. • VS. • VS.CongTx: Number of Failed Radio Link Setups for DRNC.SHO.SHO.Tx: Number of Failed Radio Link Additions for DRNC.FailRLRecfgIur. • VS.CongTx: Number of Failed Radio Link Synchronous Reconfigurations for DRNC.Cong.FailRLAddIur.CongRx: Number of Failed Radio Link Synchronous Reconfigurations for SRNC.Rx: Number of Failed Radio Link Additions for SRNC.SHO.FailRLAddIur.FailRLSetupIur.Cong. • VS.SHO.CongRx: Number of Radio Link Setup Failures for SRNC. Related to SRNC: • VS.

R99PSLoad.MaxDLThruput.MeanChThroughput.yyy. 256.R99PSLoad.Dl. 256.Thruput • VS.RB.MeanChThroughput.Equiv. Inter.RNC: R99.RNC: R99.xxx. 16. Inter.yyy. 144.RB. • VS.PS. Maximum Throughput of UL PS (kbit/s): • VS.RNC • VS.TotalBytes: HSDPA Tx DL.RNC: HSUPA.MBMSPSLoad.Thruput Number of bytes of Mac-d flow in the RLC Layer: • VS.yyy.RNC: MBMS. • VS.yyy. Bkg) Services with yyy (8.DLxxxPS.Thruput • VS.RNC: HSDPA.CSLoad.Ul. 128. • VS. 144.MaxDLThruput.MaxErlang. 16.DL.MaxDLThruput.MaxULThruput.HSUPA.MaxULThruput.Thruput Number of bits of UL/DL signaling on DCCH: • VS. 64. 32. 64. 128.UL.TRAFFIC COUNTERS: • VS.xxx. 32.DcchSrbKbps.PS. Number of UL/DL PS xxx (Str.RNC: Maximum Equivalent Erlang of CS Domain. Bkg) Services with yyy (8.HSDPA. 384) kbit/s: • VS. • VS. For internal use .ULxxxPS.HSDPAPSLoad.TotalBytes: HSUPA Rx UL.HSUPAPSLoad.RNC Number of bits of UL/DL PS xxx (Str. 384) kbit/s: • VS. Maximum Throughput of DL PS (kbit/s): • VS.DcchSrbKbps.

PDCP.CPULOAD.CPULOAD.LESS: Rate of the period in which the CPU Usage of the DPU is lower than the Alarm Threshold.DPU Board BLOCKING: • • VS. • EPS: DPU is installed in slots 8 to 19. FUNCTIONS: The DPU (Data Processing Unit) board is optional.DPU. and FP protocols.MAX: Maximum CPU Usage of the DPU. • Performs encryption.OVER: Rate of the period in which the CPU Usage of the DPU exceeds the Alarm Threshold. decryption. • Processes the MBMS at the RLC and MAC layer. and paging. • Performs the functions of the GTP-U. IUUP.RNC .DPU.DPU.CPULOAD.MEAN: Average CPU Usage of the DPU. The DPU board processes and distributes the UMTS user plane service data. • Processes frame protocols. UTILIZATION: • • VS.DPU. MAC. • MPS: DPU is installed in slots 8 to 11 and slots 14 to 19. RLC. • Selects and distributes data.CPULOAD. It performs the following functions: • Multiplexes and demultiplexes. For internal use . VS. VS.

LESS: Rate of the period in which the CPU Usage of the GCU is lower than the Alarm Threshold. VS.CPULOAD. UTILIZATION: • • VS.RNC .CPULOAD. • MPS: GCU/GCG is installed in slots 12 and 13. For internal use .GCU.GCU.GCU. VS.GCU/GCG Board BLOCKING: • • VS. FUNCTIONS: The GCU (General Clock Unit) / GCG (General Clock Unit with GPS) board is mandatory.GCU.CPULOAD.MAX: Maximum CPU Usage of the GCU.MEAN: Average CPU Usage of the GCU.CPULOAD. The GCU/GCG board extracts and provides the timing signals and the reference clock for the entire system.OVER: Rate of the period in which the CPU Usage of the GCU exceeds the Alarm Threshold.

supports channelized STM-1/OC-3 transmission based on IP protocol.LESS: Rate of the period in which the CPU Usage of the INT is lower than the Alarm Threshold. VS. provides E1/T1 transmission (MBSC). For internal use . optical support of IP over Ethernet.MAX: Maximum CPU Usage of the INT. supports E1/T1 transmission.INT.INT.OVER: Rate of the period in which the CPU Usage of the INT exceeds the Alarm Threshold.INT.CPULOAD. • FG2 board: Optional.CPULOAD. FUNCTIONS: The INT (Interface) board can be the: • EIU board: Optional. Ater. and Pb interfaces (MBSC).CPULOAD. VS.CPULOAD.INT.MEAN: Average CPU Usage of the INT. provides STM-1 transmission over A. Abis. provides IP over Ethernet. • POU board: Optional. • GOU board: Optional.INT Board BLOCKING: • • VS. • OIU board: Optional. UTILIZATION: • • VS.RNC . • PEU board: Optional.

For internal use . • Enables inter-subrack connections.SCU. • Distributes clock signals and RFN (Reduced TDMA Frame Number) signals for the BSC6900. The SCU board provides maintenance management and switching for the subrack where is located. VS.MAX: Maximum CPU Usage of the SCU. enabling complete connection between all modules of the BSC6900. It performs the followings: • Provides the maintenance management function. • Provides configuration and maintenance of a subrack or of the entire BSC6900.LESS: Rate of the period in which the CPU Usage of the SCU is lower than the Alarm Threshold.CPULOAD. • Monitors the power supply.SCU Board BLOCKING: • • VS.OVER: Rate of the period in which the CPU Usage of the SCU exceeds the Alarm Threshold.MEAN: Average CPU Usage of the SCU.RNC . VS. UTILIZATION: • • VS. • MPS/EPS: SCU is installed in slots 6 and 7.SCU.SCU. • Provides a total switching capacity of 60 Gbit/s. FUNCTIONS: The SCU (Switching Network and Control Unit) board is mandatory. fans and environment of the cabinet.CPULOAD.CPULOAD.CPULOAD.SCU.

UTILIZATION: • • VS.XPU. 8 to 11.XPU.MEAN: Average CPU Usage of the XPU. 8 to 13 and 14 to 27.CPULOAD.RNC .MAX: Maximum CPU Usage of the XPU.XPU. XPU board is functionally divided into: • Main control XPU board: used to manage the GSM user plane resources. • EPS: XPU is installed in slots 0 to 5. FUNCTIONS: It is found in the MBSC (Single RAN).OVER: Rate of the period in which the CPU Usage of the XPU exceeds the Alarm Threshold.XPU Board BLOCKING: • • VS.CPULOAD. 14 to 19 and 24 to 27.LESS: Rate of the period in which the CPU Usage of the XPU is lower than the Alarm Threshold.XPU. The XPU (eXtensible Processing Unit ) board is optional. For internal use . where counters related to service processing subsystems of GSM and UTMS are unified. and transmission resources in the system and process the GSM services on the control plane. VS. control plane resources. • Non-main control XPU board: used to process the GSM services on the control plane. • MPS: XPU is installed in slots 0 to 5.CPULOAD.CPULOAD. VS.

SCCP.Cong: Number of RLSD (Released) messages received by the SCCP because of network congestion.RAB.AttConnRelDCCH.Congestion: Number of RRC connection releases on DCCH for congestion.Att.Cong: Number of RRC connection releases due to congestion.FailModCS.Fail: Number of RRC Connection Reject due to RL setup failure (except because of CE congestion). 32.DL. DCCC: • VS.32.144. Int.AttConnRelCCCH.DCCC.FailModPS. VS.Rej.Cong: Number of CS RABs unsuccessfully modified. VS. Str.Cong: Number of CS RABs unsuccessfully established.Congestion: Number of RRC connection releases on CCCH for congestion RRC.RAB.CongDownsizing. For internal use .RAB.PS.DL. Mor384).yyy: Number of PS xxx (Conv.Block. 64.DCCC.FailEstabCS.Rx.xxx. Bkg) RABs unsuccessfully established with max DL bit rate in the range yyy (0. CALL RELEASE: • • • RRC.64.384.RLSD.Cong: Number of PS RABs unsuccessfully modified.RAB. VS.Succ: Number of DCCC attempts/successes to downsize the rate because of congestion on DL DCH. SCCP: • VS. 144.ANNEX . VS. RRC.RL. VS.FailConnReEstab.OTHER GENERAL INDICATORS CALL ADMISSION: • • • • • VS.RRC.CongDownsizing.

LCC.LDR.LCC. VS.LCC. VS.ANNEX .BERateUL. OVERLOAD CONGESTION: • • • • VS.LCC.LCC.FastBE: Number of UEs for BE Service TF (Transport Format) Control. VS.OTHER GENERAL INDICATORS BASIC CONGESTION: • • • • • • VS.LCC.LDR.UserRel. VS.UserRel: Number of HSDPA/HSUPA UEs released.DL.LCC.LDR.InterRATPS: Number of UEs that perform PS inter-RAT handover.LCC.RABRateDL: Number of UEs with Uncontrollable Real-Time Service QoS Renegotiation. VS.LDR. For internal use .FastBE.OLC. VS.LDR. VS.LDR.OLC.LDR.OLC.LCC.UserRel.UserRel: Number of UEs released because of UL/DL Overload Congestion.OLC.UL.LDR. VS. VS.HSDPA. VS.InterRATCS: Number of UEs that perform CS inter-RAT handover.OLC.LCC.LCC. VS.LCC.InterFreq: Number of UEs that perform inter-frequency handover. VS.LDR. VS.AMRRateDL: Number of UEs performing AMR rate decrease.DL.OLC.RABRateUL.LCC. VS.LCC.OLC.AMRRateUL.UL.BERateDL: Number of UEs for BE Service Downsizing.TCC: Number of UEs transferred to common channel.HSUPA.LCC.

Sign up to vote on this title
UsefulNot useful