Professional Documents
Culture Documents
Mian Rizwan
1
1) 2) 3) 4) 5) 6) 7) 8)
An observation point is a PI which reflects a specific performance problem. The analysis based on an observation point is a process that goes deeper based on the familiarization of the UTRAN PI. Observation point analysis associates signaling process with performance index. Observation points are categorized as follows: RRC establishment analysis observation point RAB establishment analysis observation point Soft handover analysis observation point Call drop analysis observation point CS/PS intersystem handover analysis observation point Traffic analysis observation point Key interface process analysis observation point HSDPA analysis observation point
An in-depth performance analysis can be made only after you have gained a mastery of observation points. The Nastar tool provides special topic query of most observation points. We may also make special topic query of other observation points by means of customization. Special topic drilling analysis of basic observation point helps deepen the understanding of signaling processes and various PIs and strengthen the mastery of the Nastar tool.
2010-01-31
Mian Rizwan
Page 1 of 28
3G Optimization Guidelines
Mian Rizwan
2010-01-31
Mian Rizwan
Page 2 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Possible Cause
Analysis Idea service requests (accounting for over 10% of total connection establishment requests), we need to pay much attention to them. This is because when UE changes from DCH status into IDLE status, PS needs to transmit packets, then ps paging occurs and the corresponding RRC requests are streaming class called service requests. If there are too many requests of this type, it is possible that the timer from DCH status to IDLE status is not properly set. It is generally caused by insufficient
RRC types of RRC establishment connection requests establishment requests and their proportional distribution. If any abnormality, we need to give an early warning.
transmission resource or transmission fault. You may query the cell downlink throughput at the moment from associated traffic statistics indexes. If it is lower than 200 kbps, transmission fault may occur. It may be caused by NodeB fault or insufficient NodeB resource. You may
Number of RRC connection establishment RRC failures (>=5); establishment RRC connection failure establishment failure rate (>=10%)
RL establishment failure
query the maximum downlink CE of a cell from associated traffic statistics index. If the maximum uplink CE is less than 20, then traffic is not high and the problem lies in abnormal NodeB equipment. RRM admission decision cannot establish any new RRC connection due to too high radio load within a cell. In this case, you need to query the maximum RTWP and the maximum TCP of the cell to confirm uplink congestion or downlink congestion and judge whether any expansion is necessary. Meanwhile, we should check whether related admission strategy settings, such as DCCC, are proper. Uplink CE resource admission congestion
Power congestion
Uplink CE congestion
within an RNC. You need to query the number of uplink CEs of a cell from relevant parameters and judge whether to
2010-01-31
Mian Rizwan
Page 3 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Possible Cause
Analysis Idea expand CE. If the number of uplink CEs is less than 20, then traffic is not high and the problem may lie in abnormal NodeB equipment. At present, RNC does not make an accurate estimate of CE resource. It is quite possible that RNC judges CE to be sufficient, but actual NodeB CE resource is insufficient. In addition, inconsistent capability of RNC and NodeB may also lead to NodeB RL establishment failure. Downlink CE resource admission congestion within an RNC. You need to query the number of downlink CEs of a cell from relevant parameters and judge whether to expand CE. If the number of uplink CEs is less than 40, traffic is not high
Downlink CE congestion
and the problem may lie in abnormal NodeB equipment. At present, RNC does not make an accurate estimate of CE resource. It is quite possible that RNC judges CE to be sufficient, but actual NodeB CE resource is insufficient. In addition, inconsistent capability of RNC and NodeB may also lead to NodeB RL establishment failure. Code resource fails to be allocated during RRC connection establishment. Code congestion is generally caused by too many network users. It may be seen in high traffic scenarios with microcell coverage. You may query the effective utilization of codes from associated traffic statistics indexes. If the effective utilization of codes is lower than 30%, it is possible that the code distribution algorithm is abnormal. Generally the congestion caused by unknown insufficient resources. For example, license resource and high CPU
Code congestion
2010-01-31
Mian Rizwan
Page 4 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Analysis Idea utilization make flow control and FMR processing capacity insufficient. In addition, E1 fault also appears. This cause value is dotted. Transmission congestion is mainly caused by insufficient transmission resource. You may query the downlink cell throughput
Transmission congestion
from associated traffic statistics indexes. If the downlink cell throughput is lower than 200 kbps, it is possible that there is abnormal equipment. The power-down of a base station once led to transmission interruption, but the cause in traffic statistics is transmission congestion. Abnormal causes. We need to make
in-depth location based on RNC logs. The known problem is that the system redirection function of the network is enabled. During redirection, a mobile phone does not support GSM and thus failure rejection occurs.
No response from UE
This is generally caused by poor coverage. The downlink FACH and RACH have unbalanced coverage. This is generally caused by an RNC fault. At present, there is a problem with traffic statistics mode, which may lead to some wrong dotting of this cause.
There was a problem with the designated access DSP of node B. The RRC CONNECTION SETUP REQUEST message fails to be sent to RNC. The RACH packet decoding of this cell fails. We may make a judgment by checking whether the index VS.MAC.CRNCIubBytesRACH.Tx is abnormal.
2010-01-31
Mian Rizwan
Page 5 of 28
3G Optimization Guidelines
Mian Rizwan
Migration
Number of CS/PS RAB establishment failures (>=5); establishment CS/PS RAB failure establishment failure rate (>=10%) CS/PS RAB
Power congestion
Uplink CE congestion
2010-01-31
Mian Rizwan
Page 6 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Possible Cause
Analysis Idea Downlink CE resource admission congestion within an RNC. You need to query the number of downlink CEs of a cell from relevant parameters and judge whether to expand CE. If the number of uplink CEs is less than 40, then traffic is not high and the problem may lie in abnormal NodeB equipment. At present, RNC does not make an accurate estimate of CE resource. It is quite possible that RNC judges CE to be sufficient, but actual NodeB CE resource is insufficient. In addition, inconsistent capability of RNC and NodeB may also lead to NodeB RL establishment failure. Code resource fails to be allocated during RRC connection establishment. Code congestion is generally caused by too many network users. It may be seen in high
Downlink CE congestion
Code congestion
traffic scenarios with microcell coverage. You may query the effective utilization of codes from associated traffic statistics indexes. If the effective utilization of codes is lower than 30%, it is possible that the code distribution algorithm is abnormal. Transmission congestion is mainly caused by insufficient transmission resource. You may query the downlink cell throughput from associated traffic statistics indexes. If the downlink cell throughput is lower than 200 kbps, it is possible that there is abnormal equipment. The power failure of a base station once led to transmission interruption, but the cause in traffic statistics is transmission congestion. Abnormal causes. We need to make an in-depth location based on RNC logs. The air interface failure occurring during
Transmission congestion
2010-01-31
Mian Rizwan
Page 7 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Analysis Idea RB establishment is generally caused by poor coverage or mobile phone compatibility. The compatibility of a mobile phone itself becomes faulty in some unknown
scenarios. For example, when a Huawei mobile phone drops network abnormally, it may not release any RB. When PS RB is set up next time, this case may occur. This case also happens to the SE V800 mobile phone. This generally occurs when FACH migrates
to DCH and sets up RB. The downlink physical layer of a terminal is not synchronized, which leads to RB establishment failure. This is mainly caused by poor coverage. The Cell Update flow occurs during RB establishment. This nested flow leads to RB establishment failure. UE considers parameter configuration illegal. Network and terminals have an inconsistent understanding of parameter
Cell update
Illegal configuration
processing. If RB establishment failure occurs in the domain of CS, it is possible that a user dials a wrong telephone number and at once goes onhook. RB SETUP failure may also occur at this time. The cause is illegal configuration. Generally poor coverage makes UE unable to receive any RB establishment command.
No response from UE
RNC considers the parameter delivered by a core network invalid. You need further cell signaling tracing to determine the Parameter error cause. Among the known causes is that the uplink subscription and activation application information of user PS service exceeds the capacity of a mobile phone, or
2010-01-31
Mian Rizwan
Page 8 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Possible Cause
Analysis Idea that the network negotiation rate in PDP activation acceptance messages is less than the minimum guaranteed rate.
Call drop caused by operation and maintenance. For example, the execution OM intervention of TRG RABRel on LMT causes users to be released. High-priority users preempt low-priority users when admission is rejected. This RAB preemption causes a link to be released. This kind of call drop occurs in the case of load and insufficient resource. Determine whether expansion is necessary according to the number of occurrences. Within a cell, UTRAN leads to abnormal CS/PS call drop High CS/PS call drop rate UTRAN link release. This case generally corresponds to processing abnormality. We need to make a further analysis by means of CDL. Uplink or downlink signaling RB reaches the maximum retransmission times and Uplink/downlink RLC reset resets. This causes a link to be released. This case is mainly caused by poor coverage quality (including missing configuration of adjacent cells and small handover area). RNC receives RL Failure reported by NodeB, which causes a link to be abnormally released. In this case, poor coverage quality (including missing
2010-01-31
Mian Rizwan
Page 9 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Possible Cause
Analysis Idea configuration of adjacent cells and small handover area) makes UE abnormally shut down the transmitter, or uplink demodulation out-of-sync. Receive the Cell Update message reported by a mobile phone. The cause is downlink RL Failure, which makes a link abnormally released. In this case, poor coverage quality (including missing configuration of adjacent cells and small handover area) makes UE abnormally shut down the transmitter, or uplink demodulation out-of-sync.
RNC delivers a message and waits for the response from a mobile phone, but timeout The UU occurs. For example, waiting for RB interface makes reconfiguration completion message times no response. out and waiting for active set update completion times out. This case is generally caused by poor coverage. RF cause; due to poor coverage quality
Other RF causes
RNC finds that the AAL2 Path of the IU CS interface is abnormal and starts abnormal release. It is possible that the transmission Abnormal AAL2 equipment of the Iu interface is abnormal. link The known problem is that immediate normal release during RB establishment is classified by traffic statistics into abnormal release. RNC finds that the GTPU of the IU PS Abnormal GTPU interface is abnormal and starts abnormal release. The cause may be equipment fault or defect. Possibly the call drop (but traffic statistics Others does not dot) occurring during flow interaction or cell update, or abnormal call
2010-01-31
Mian Rizwan
Page 10 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Possible Cause
Analysis Idea drop and cell blocking caused by the transmission fault of the Iub interface, RNC internal cause, and Bug. There may be call drop for abnormal causes. We need to make an analysis based on RNC logs. The call drop caused by violent change (corner effect or driving out from the shadow area of a building) of uplink signal is known to be classified into this cause.
2010-01-31
Mian Rizwan
Page 11 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Analysis Idea a link is incompatible with other concurrent processes. RNC has guaranteed serial flow processing. Soft handover execution failure is mainly caused by the problematic processing of some mobile phones. UE considers that the content of the active set update of RNC adding/deleting a link is illegal. Generally, this scenario will not appear in commercial use.. RNC does not receive the active set update command response for adding/deleting a link. This is the main cause of softer/soft handover failure. This happens in the region with poor coverage or a small handover area. It needs RF optimization.
Illegal configuration
No response from UE
A target cell has no resource available, or there is some RNC parameter configuration error. We need to make an analysis based on RNC logs.
2010-01-31
Mian Rizwan
Page 12 of 28
3G Optimization Guidelines
Mian Rizwan
Condition and preparation failure rate (>=10%) of transition out of cell accompanied by hard handover
Possible Cause
Analysis Idea The problem often lies in CN parameter configuration or a related link connection. We need to make an analysis based on RNC logs.
Transition failure It generally corresponds to core network in the target CN/RNC or configuration error. system Transition in the target CN/RNC or system not supported Transition objective not allowed OM intervention Generally, RNC does not support some hard handover parameters. We need to make an analysis based on RNC logs. Often an MSC parameter configuration error. We need to check the parameter configuration of a core network. Failure caused by operation and maintenance Often an MSC parameter is configured incorrectly, or a target RNC has no resource available. Failure causes are not defined in traffic statistics. We need to make an analysis based on RNC logs. A core network does not return a Waiting for transition command timeout corresponding command of handover preparation request. In this case, there is some problem with the parameter configuration or related link connection of a core network. We need to analyze the cause according to the signaling trace of the core network and BSS.
No available resource
Undefined
Others Preparation Preparation failure of RNC-level foreign outgoing handover failures (>=5) of RNC-level CS/PS domain intersystem outgoing handover, preparation
2010-01-31
Mian Rizwan
Page 13 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Possible Cause
Analysis Idea Upon requesting handover preparation, RNC receives the release command from a core network. Two cases: intersystem handover request occurs during signaling process like location update. The location update flow has been finished before one flow is finished. The core network starts release; the user who sets up a call goes onhook during handover preparation, and the core network starts release. No handover is finished in either case, but either is normal flow nesting. It generally corresponds to core network configuration error. We need to analyze the cause according to the signaling tracing of a core network and a BSS. The problem often lies in the parameter configuration or related link connection of a core network. We need to analyze the cause according to the signaling tracing of a core network and a BSS. The problem often lies in an MSC parameter configuration error. That is, the LAC of the target cell fails to be configured. We need to check the parameter configuration of a core network. This case is often seen after the adjustment of 2 G network. The problem often lies in an MSC parameter configuration error, or BSC has no resource available. We need to analyze the cause according to the signaling tracing of a core network and a BSS. We need to analyze the cause according
Transition cancelled
Transition timeout
No available resource
Others
2010-01-31
Mian Rizwan
Page 14 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Possible Cause
Analysis Idea The problem often lies in the parameter configuration or related link connection of a core network. We need to analyze the cause according to the signaling tracing of a core network and a BSS.
Transition Preparation failures (>=5) of CELL-level CS domain intersystem outgoing handover and preparation failure rate (>=10%) of CS domain intersystem outgoing handover. timeout
It generally corresponds to core network Transition failure configuration error or BSS not supporting. in the target We need to analyze the cause according CN/RNC or to the signaling tracing of a core network system and a BSS. Transition in the target CN/RNC or system not supported In this case, a BSC does not support some parameters of intersystem handover requests. We need to analyze the cause according to the signaling tracing of a core network and a BSS. We need to analyze the cause according to the signaling tracing of a core network and a BSS. UE considers that the command for hard handover out of a cell is not supported. The problem generally lies in the compatibility of a mobile phone.
Others
Configuration not supported Outgoing hard handover failures within NODE B, between different NodeBs within RNC, and between RNCs Cell Updating Procedure
Failures (>=5) of hard handover out of a cell, failure rate (>=10%) of hard handover out of a cell
Physical channel Possibly poor coverage or severe failure interference UE gives the feedback that hard handover process is incompatible with other concurrent processes. The problem may lie in the compatibility of a mobile phone itself. Cell update happens during hard handover out of a cell. This flow nesting leads to the failure of hard handover out of a cell.
2010-01-31
Mian Rizwan
Page 15 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Possible Cause
Analysis Idea UE considers that the command for hard handover out of a cell is illegal. The problem generally lies in the compatibility of a mobile phone.
Illegal configuration
Others
We need to make a further analysis based on RNC logs. UE considers that the command for
transition out of a cell accompanied by hard handover is not supported. The problem generally lies in the compatibility of a mobile phone.
Execution
failures (>=5) of transition out of a cell accompanied Synchronization by hard reconfiguration handover, incompatible execution failure rate (>=10%) of transition out of a cell accompanied Illegal by hard handover configuration
Physical channel Possibly poor coverage or severe failure interference UE gives the feedback that the hard handover process of RNC adding a link is incompatible with other concurrent processes. The problem may lie in the compatibility of a mobile phone itself. UE considers that the command for transition out of a cell accompanied by hard handover is illegal. This case seldom occurs.
Configuration not finished Others CS/PS foreign handover failure CS/PS domain Configuration intersystem handover failures not supported (>=5), CS/PS We need to make a further analysis based on RNC logs. The handover command terminal in a network does not provide support. The problem generally lies in the compatibility of a mobile phone.
2010-01-31
Mian Rizwan
Page 16 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Possible Cause 1) 2)
Analysis Idea Poor 2 G signal or severe interference leads to UE access failure. The channel parameters, including the encryption mode sent from network to UE, are inconsistent with those of a BSC. We need to compare and confirm the parameters of a terminal and those of a BSC. Physical channel failure generally occurs in a network with partners equipment as the CN. We need to check the encryption algorithm configuration of an MSC and an SGSN. We need to make a further analysis according to RNC logs, together with the signaling tracing of a core network and a BSS. Improper service capability configuration of 2 G cell makes high-rate service unable to start a pressing mould, which leads to system PS handover failure.
Others
Lay an emphasis upon the analysis of average uplink CE resource occupied and the maximum uplink CE resource occupied.
Uplink CE
2010-01-31
Mian Rizwan
Page 17 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Analysis Idea Observe whether the maximum downlink CE resource occupied approaches 128. If it does, an early warning needs to be given to expansion. Normally, when the average downlink CE resource occupied is less than 60 CE Erlang, whole-network busiest-hour cell traffic is very small. If the average transmit power of a cell is large and there is small traffic, it indicates that there is poor downlink coverage.
Downlink CE
Lay an emphasis upon the analysis of average downlink CE resource occupied and the maximum downlink CE resource occupied
List the average TCP, Average transmit the maximum TCP and power of cell the minimum TCP of a cell. Maximum List the average TCP,
the maximum TCP and transmit power of the minimum TCP of a cell cell. Minimum Observe whether the transmit power of minimum transmit power cell of a cell is abnormal.
If the maximum transmit power of a cell is large and there is small traffic, it indicates that power peak shock may lead to power congestion. If the minimum transmit power of a cell is abnormal, the transmit channel may become faulty.
Average RTWP
List the average RTWP, the maximum RTWP, If the average RTWP of a cell is higher than -95 and the minimum RTWP dBm, there may be downlink interference. of a cell. Among various items, RTWP peaks, for example, -70 dBm, often appear. This may be caused by the power of access process or handover process. If the minimum RTWP is lower than -108 dBm, a channel fails to be corrected, or a base station encounters power-down. If the effective utilization of codes is not high (<= 30%), but code congestion leads to access failure, it is possible that the code distribution algorithm is abnormal. Observe whether the uplink throughput of a cell is great. If it amounts to 75% of the transmission capability of a base station, transmission expansion needs to be considered.
Observe whether there Maximum RTWP are many peaks. Observe whether the minimum RTWP is less than -105.5 dBm. Observe whether the code utilization is abnormal.
Minimum RTWP
2010-01-31
Mian Rizwan
Page 18 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Analysis Idea Observe whether the downlink throughput of a cell is great. If it amounts to 75% of the transmission capability of a base station, transmission expansion needs to be considered.. This is generally caused by transmission
interruption or intermittent transmission failure. Some offices are greatly influenced by weather due to the use of microwave transmission. Thunder storm always leads to intermittent transmission failure. If 1A events often happen within many consecutive days, there may be missing configuration of adjacent cells.
Missing configuration of adjacent cell Excess configuration of adjacent cells Pilot Pollution:
If 1C events often happen within many consecutive days, there may be pilot pollution.
2010-01-31
Mian Rizwan
Page 19 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Analysis Idea
RL failure of IUR interface caused by operation and maintenance This generally corresponds to equipment abnormality. We should first query related equipment alarm. This is caused by insufficient RNC internal resource. You need to query the quantity of related users to judge whether there is any equipment abnormality. UE considers that the RL configuration content of RNC establishment is not supported. The problem lies in the compatibility of a mobile phone. Abnormal causes. We need to make an analysis based on RNC logs. This generally corresponds to equipment abnormality. We need to query whether there is any power-down. The problem lies in the compatibility of a mobile phone itself in some unknown scenarios. Insufficient RNC internal resource or abnormal RNC equipment. You need to query cell CE resource from relevant parameters to judge whether there is any equipment abnormality. Equipment is known to encounter repeated power failure and air-conditioner fault due to thunder storm. As a result, high temperature leads to abnormality of various kinds. Besides, the NLPA board encounters shutdown.
RL establishment failure of the IUR interface RL synchronization configuration failure of the IUR interface RL addition failure of the IUR interface
List the number of RL establishment failures (>= 5) of RNC resource the Iur interface of unavailable the SRNC, RL establishment failure rate (>= 10%) of the Iur interface of the SRNC, and main failure causes. Configuration not supported
Others
No response
Configuration not supported RL establishment failure of the IUB interface RL reconfiguration failure of the IUB interface RL addition failure of the IUB interface List the number of RL establishment failures of the IUB interface, RL establishment failure rate of the No available Iub interface, and resource main failure causes.
2010-01-31
Mian Rizwan
Page 20 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Analysis Idea This generally corresponds to equipment abnormality. We should first query related equipment alarm. RL establishment failure caused by operation and maintenance (for example, cell blocking) The problem may lie in cell unavailability
OM intervention
or equipment fault. You need to query NodeB makes the cell unavailability duration from no response relevant parameters to judge whether there is any equipment fault. RL establishment failure caused by abnormal factors. We need to make an analysis based on RNC logs RL reconfiguration failure caused by abnormal factors. We need to make an analysis based on RNC logs. The known causes are that transmission congestion (Received Iub AAL2 type1 setup response message from AL but result is 5 not success!) and improper T314/T315 parameter setting make there not be any opportunity of RL reconfiguration. RL addition failure caused by abnormal factors. We need to make an analysis based on RNC logs. It is known that RL addition failure caused by restricted IUB transmission bandwidth will be classified into this cause value. The problem lies in the compatibility of a RB establishment failure RB reconfiguration failure RB deletion failure RB establishment failure generally corresponds to poor air interface coverage or a mobile phone compatibility problem. mobile phone itself in some unknown scenarios. For example, when a Huawei mobile phone drops network abnormally, it may not release any RB. When PS RB is reestablished next time, this case may occur. This case also happens to SE V800 mobile phone. Or when some UEs implement VP and high-speed (greater than or equal to 64K) PS service, failure
Others
2010-01-31
Mian Rizwan
Page 21 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Possible Cause
Analysis Idea may also due to unsupported capability. This generally occurs when FACH migrates to DCH and establishes RB. The downlink physical layer of a terminal is not synchronized, which leads to RB establishment failure. This is mainly caused by poor coverage. The Cell Update flow occurs during RB
Cell update
establishment. This nested flow leads to RB establishment failure. UE considers parameter configuration illegal. Network and terminals have an inconsistent understanding of parameter processing. If RB establishment failure occurs in the domain of CS, it is possible that a user dials a wrong telephone number and immediately goes onhook. RB SETUP failure may also occur at this time. The cause is illegal configuration. Or when a 3 G terminal as the caller implements VP service, the called party
Illegal configuration
resides in a GSM network and does not support VP service. Thus, after RNC receives an RAB assignment request, a core network immediately delivers the Disconnect command upon Call Proceeding (the cause is Bearer capability not authorized). But UE has just received an RB_SETUP command at this time and has no time to complete RB establishment. Upon receiving this Disconnect command, UE initiates a response RB establishment failure and RNC returns RAB establishment failure. Generally poor coverage makes UE unable to receive any RB command. In Hong Kong, the balance mechanism of IUB once made signaling established on one E1, but service was established on another E1. Thus, there has been no
No response from UE
2010-01-31
Mian Rizwan
Page 22 of 28
3G Optimization Guidelines
Mian Rizwan
Observation Point
Condition
Possible Cause
Analysis Idea problem with signaling, but RB establishment may fail. In this case, it is this cause value that is returned.
Observe whether the number of RB bearer various types of distribution of RB service bearer uplink/downlink and the service proportion are Uplink/downlink abnormal. If there RB bearer is any distribution of BE abnormality, an service early warning needs to be given
PS has a large amount of 128k, 144k, and 384k RB bearer. This will consume a large number of resources and there is poor coverage. We need to verify whether RB bearer is consistent with actual demands with first-line personnel. Observe whether the RB distribution of BE service is rational. According to the distribution, DCCC strategy and related system parameters can be adjusted.
2010-01-31
Mian Rizwan
Page 23 of 28
3G Optimization Guidelines
Mian Rizwan
query to get the general information about RNC-level RRC establishment. As shown in the following figure, RRC establishment success rate reaches 98.84%. Most of RRC establishment failure is because there is no response to RRC Setup command delivery (7,373 times). Eighteen failures are because of RRC Setup Reject.
Figure 2 General information about RRC setup The main cause of the exemplified RRC establishment failure is that there is no response to RRC Setup command delivery. It is unbalanced coverage of downlink FACH and uplink RACH. For an early network, coverage cannot be guaranteed, so there are a large number of areas with poor coverage quality. These areas with poor coverage always correspond to intersystem rerouting areas. On the other hand, where there are many users or equipment problems within a cell, RRC establishment rejection is also a major cause of RRC establishment failure. 2. Analysis of RRC establishment scenario One important reason for RRC establishment failure is poor coverage. We may make a further analysis by using the establishment cause distribution and success rate of different RRCs establishment. Get results by starting related query and selecting Scenario Analysis to present a selected RNC in the form of a pie chart and a bar chart.
2010-01-31
Mian Rizwan
Page 24 of 28
3G Optimization Guidelines
Mian Rizwan
Figure 4 Comparison of RRC setup scenario success rate Scenario Analysis makes a comparative analysis of several commonly used scenarios. The pie chart shows the RRC establishment distribution of a main scenario. The example in the chart indicates that RRC establishment requests mainly exist in network registration with REG as the cause. When an LAC area is not well planned or there is poor coverage (the margin of LAC division is in a prosperous area), there may be a lot of registration. On the other hand, the cause of RRC establishment during intersystem reselecting of this mobile phone is registration. A large number of mobile phones fail to be registered due to poor coverage and will try again and again. Thus, the cause of RRC establishment is registration in many cases. This indicates that there is poor network coverage in some areas.
2010-01-31
Mian Rizwan
Page 25 of 28
3G Optimization Guidelines
Mian Rizwan
As shown in Figure 4, the bar chart compares the RRC establishment success rates of various main scenarios. It can be seen from the examples in the figure that the called voice service has the highest RRC establishment success rate while the calling voice has the lowest success rate (which corresponds to a large amount of UENoRsp analyzed earlier). The RRC establishment success rate of registration is also relatively low. In Huawei networks, the present resident threshold is Ec/Io greater than -18 dB. The intersystem reselecting starting threshold is Ec/Io less than -14 dB. A low registration success rate indicates that some terminals have attempted to register at a network in the areas without good coverage (Ec/Io is between -14 dB and -18 dB). The called RRC establishment success rate is as high as 99.3%. If the called party starts RRC establishment, it indicates that he is covered by a PCH. From another point of view, this indicates that the RRC establishment success rate of expected network coverage area may be very high. 3. Analysis of RRC establishment rejection Another cause of RRC establishment failure is RRC establishment rejection. In the case of RRC establishment rejection, generally too many users lead to admission rejection, or cell equipment fault leads to access failure. RRC establishment rejection always corresponds to some areas instead of a large network area. RRC establishment rejection is generally analyzed based on problematic areas. In the query results of RRC Setup Analysis, start related query to make TOPN query of Cell RRC Analysis. Query results cover two pages, which respectively list 10 cells with the most VS.RRC.FailConnEstab.Cell and VS.RRC.SuccConnEstab.Rate.Cell. For the 10 cells with the most RRC establishment failures and the cells with the most Rej, start Cell RRC Reject Analysis of related query to analyze the causes for rejection.
2010-01-31
Mian Rizwan
Page 26 of 28
3G Optimization Guidelines
Mian Rizwan
According to the results of Cell RRC Reject Analysis, draw a pie chart of cause distribution for a selected cell. Figure 5 is an exemplified pie chart of cause distribution of RRC rejection. In this example, two RRC rejections of a cell are because of Power Congestion. The following shows the commonly seen causes of rejection: 1) Power Congestion: RRM makes an admission algorithm decision. Downlink admission decision occurs. Therefore, RRM starts RRC establishment rejection. This often occurs when heavy network load leads to congestion. Further, we may start Cell Traffic Load Analysis of related query, pay much attention to the maximum RTWP and the maximum TCP of this cell and make sure whether there is uplink congestion or downlink congestion. For congestion, we may check whether a threshold is properly set and judge whether there is any radio interference, whether expansion is necessary. 2) CE Congestion: This is mainly because RNC considers CE resource insufficient. CE congestion always corresponds to many users. These users exceed CE capacity and we need to expand the capacity of this area. Further, we may start Cell Traffic Load Analysis of related query, know about the quantity of DCH User and predict the required CEs according to the traffic model. RL Fail: During RRC establishment, NodeB considers establishment fails. This may be NodeB fault or insufficient NodeB resource. Further, we may start Cell Traffic Load Analysis of related query and know about the quantity of DCH users. Determine whether the problem lies in insufficient resource or equipment fault by analyzing the board configuration, CE configuration and logs of a corresponding NodeB. AAL2 Fail: This is mainly the AAL2 Path establishment failure of an Iub interface. It is generally caused by insufficient transmission resource or transmission problems. Further, we may start Cell Traffic Load Analysis of related query, know about the quantity of DCH users and compare it with the AAL2 Path bandwidth of transmission configuration. Thus, we can determine whether the problem lies in equipment or insufficient transmission resource. Redir.Inter.Att: Inter-frequency redirection failure starts rejection. Redir.Intrat: Foreign redirection failure starts rejection. Code Congestion: This is mainly because of insufficient resource. Insufficient code resource may be seen in high traffic scenarios with microcell coverage, and expansion is necessary. Cell OVSF Code Allocation Analysis of related query helps analyze the use of channel codes and clarify main services. Other: This is mainly an RNC internal processing problem. Its cause needs to be confirmed according to R&D logs.
3)
4)
5) 6) 7)
8)
1.3 Summary
Make a similar analysis of several other special topics according to the above-mentioned idea of the RRC connection analysis. Keep summarizing experiences in your analysis. Special topic analysis will help greatly improve basic skills of performance analysis.
2010-01-31 Mian Rizwan Page 27 of 28
3G Optimization Guidelines
Mian Rizwan
Basic special topic analysis practice contributes to the following aspects: 1) 2) 3) Consolidate signaling flow and deepen an understanding of each UTRAN PI. Performance analysis has a more definite object in view. Basic special topic analysis enables us to make a preliminary analysis of network performance and locate simple problem causes. Summarize the relationship between performance KPIs and network problems, and lay a foundation for the use of other Nastar functions and an in-depth analysis of network performance.
2010-01-31
Mian Rizwan
Page 28 of 28