Beruflich Dokumente
Kultur Dokumente
Confidential level
For internal use only
V100R001
Product name: WCDMA RNP
Total 39 pages
URNP -SANA
2003-10-08
Revision Record
Date 2003-10-08 2003-10-14 2003-11-11 Revision version 1.00 2.00 3.00 Change Description First draft completed Revision based on comments Revision based on review comments Author Jiao Anqiang Jiao Anqiang Jiao Anqiang
11-12-20
Confidential
Page 2 , Total 39
Table of Contents
1 Foreword 6 2 Access Problem Analysis Process...............................................................................................................6 2.1 Preparation before Analysis.....................................................................................................................6 2.2 Access Problem Analysis Methods.........................................................................................................7 2.2.1 Traffic Statistics Data Analysis.........................................................................................................8 2.2.2 Signaling Flow Analysis.................................................................................................................10 2.2.3 Equipment Analysis .......................................................................................................................19 2.2.4 Coverage Analysis...........................................................................................................................22 2.2.5 Power Control Information Analysis..............................................................................................22 2.2.6 Access Algorithm Parameter Analysis............................................................................................25 2.2.7 UE Characteristics Analysis............................................................................................................26 3 Analysis of Command Reasons for Access Problems...............................................................................26 3.1 Network Reasons...................................................................................................................................26 3.1.1 Dead Spot in Signal Coverage........................................................................................................26 3.1.2 Too Strong Uplink and Downlink Interference Signals Exist........................................................27 3.1.3 Access Problems Caused by Cell Load...........................................................................................27 3.2 Radio Parameter Settings.......................................................................................................................28 3.2.1 Too High Settings of Qqualmin and Qrxlevmin.............................................................................28 3.2.2 Improper Settings of Access Threshold..........................................................................................28 3.2.3 Inappropriate Setting of Preamble Power Ramp Step and Retransmission Times........................29 3.2.4 Inappropriate Setting of Adjacent Cells..........................................................................................30 3.2.5 Inappropriate Setting of Synchronization Parameters....................................................................30 3.2.6 Over-Low Power Allocation Ratio for Common Channel.............................................................31 3.2.7 Over-Low Initial Power of Uplink and Downlink Dedicated Channel..........................................32 3.2.8 Over-low Setting of Uplink Initial SIR Target Value of Dedicated Channel................................32 3.3 Equipment Reasons...............................................................................................................................33 3.3.1 Insufficient RAN Device Board Sources........................................................................................33 3.3.2 Abnormality of Equipment Clock...................................................................................................33 3.4 Data Configuration Cause.....................................................................................................................33 3.4.1 Insufficient IUB Bandwidth Resource............................................................................................33 3.4.2 PATH ID and NSAP Address Configuration Error of AAL2PATH..............................................34 3.4.3 Inconsistent Number of AAL2PATHs across IU/IUB Interface....................................................35 3.5 Other Reasons........................................................................................................................................35 3.5.1 Insufficient UE Access Class (AC).................................................................................................35 3.5.2 Inconsistent Security Data of UE, RNC and CN............................................................................36 3.5.3 UE not Registered in HLR..............................................................................................................37 4 Outstanding Issues.....................................................................................................................................37
11-12-20
Confidential
Page 3 , Total 39
List of Tables
Table 1Common Channel Power Allocation Ratio......................................................................................31 Table 2Overhead Proportion for Each Layer on IUB Interface ..................................................................34
List Figures
Figure 1 Traffic Statistics Analysis Flow.......................................................................................................9 Figure 2 Schematic Diagram of Radio Layer Signaling...............................................................................11 Figure 3 Schematic diagram of transport network layer signaling analysis.................................................12 Figure 4 Single User Fault Location Tool....................................................................................................13 Figure 5 Signaling Flow for RRC Setup in Each Layer of Dedicated Channel ..........................................14 Figure 6 Problem Analysis Flow of RRC Setup in Dedicated Channel.......................................................15 Figure 7 UE Air Interface Message Tracing.................................................................................................17 Figure 8 Access Problem Caused by Coverage Restriction.........................................................................24 Figure 9 Normal Access Process..................................................................................................................25 Figure 10 UE Authentication and Security Mode Process...........................................................................36
11-12-20
Confidential
Page 4 , Total 39
Key word: access process, problem analysis, cell searching, cell selection and reselection, random access Abstract: This document analyzes and describes the general steps of identifying access problems from the point of view of access stratum (AS), then analyzes the usual causes of access problems and presents the solutions. List of abbreviations: Omitted
11-12-20
Confidential
Page 5 , Total 39
1 Foreword
In WCDMA network operation, low call setup rate and difficult access are the hot complaints from subscribers, as well as the direct reflection of the quality of the radio network. This document analyzes mainly the general solution flow of access problems, causes of access failure and the solution measures, so as to improve the call completion rate and the network quality. The topic of this document is access process, so the concept of access process should be made understood first. From the wireless point of view, access process consists of a series of processes including searching network after subscriber power-on, random access, RRC setup and RAB setup. From the end user point of view, access process is the process from dialing to call completion. In this sense access process includes not only the wireless access process, but also many processes occurring in the fixed network. Radio network optimization cares mainly about the access process at the wireless side, and emphasizes on survey of cell search, cell selection and reselection, random access and RRC setup, which are also the emphases of this document. The reason to make such consideration is that the radio port performances such as network coverage are considered more during the network optimization phase. The cell pilot signals are measured with UE or drive test equipment, and UE is observed to see whether it can work normally in cell searching, selection and reselection, and whether is can initiate random access, attach and location registration/update, and accept normal service of the network, so that NodeB site adjustment (distance between NodeB sites, azimuth and down tilt of antennas, etc.) can be implemented. Compared with RAB setup, the success rate of RRC setup can reflect better the radio access performance, because the process of RRC connection setup is basically the process of cell searching, selection and reselection, initiation of random access, etc., which occur on the air interface, while the success rate of RAB setup has more relations with the network factors such as equipment, transmission, etc., which are much less likely to cause access problems.
11-12-20
Confidential
Page 6 , Total 39
For the network in service, it may have been optimized before. All optimization history records should be obtained so as to know all the adjustment processes and pending problems before the commencement of the current optimization.
If the complete planning report, capacity expansion report and optimization history records are not available due to some reasons, the latest reliable summary sheet of the engineering parameters must be obtained through other means. Cell parameter configuration sheet can be read online directly from the equipment configuration data.
Obtain the network traffic statistics and the subscriber complaint information of access about the access problems, and the traffic statistics information can be obtained through M2000.
Obtain the information about the radio parameter configuration, which includes the adjustments of the baseline parameter issued by the relative version, and whether the special algorithm (such as DRD) is applied.
Check whether the software and the hardware versions of the equipment are correct, identify whether the versions of various NodeBs and RNCs are consistent, and ensure whether the entire network version is consistent and whether all NodeBs are using the same version including patch releases.
In case of optimization before the network is put into service, identify whether dialing test has been carried out after each NodeB is put into service, whether the background noise of the NodeBs has been calibrated (calibrate the receiving channel gain), and whether the standing wave ratio of the antennas has been tested.
In case of optimization before the network is put into service, check the clock of each device of the system, emphasizing on checking whether the clock source of each device is rational, and whether they are consistent with the planning, and current clock status. s
11-12-20
Confidential
Page 7 , Total 39
methods for access problems can be flexibly applied during actual problem location processes according to the actual conditions, and it is unnecessary to stick to the orders.
Where,
RRCSetupSu ccRate = Number of RRCs set up in all four QoS s ervices 100 % Number of RRC reques ts in all four QoS s ervices Number of RABs set up in all four QoS s ervices 100 % Number of RAB reques ts in all four QoS s ervices
RABSetupSu ccRate =
In the same way, statistics of the calling setup success rate of each QoS can be implemented respectively. The sign of RRC connection setup success is the RRC Connection Setup Complete message. Therefore, the RRC connection setup success rate is calculated through statistics of the number of the RRC Connection Setup Complete messages and the number of the RRC Connection Request messages. The sign of RAB assignment is the RAB Assignment message (the content of the message is RAB assignment). Therefore, the RAB assignment success rate is calculated through the statistics of the number of successful RABs setup in the RAB Assignment Response message and the number of RAB Assignment Request messages. This index statistics is cell-oriented and it reflects the call setup situation of the network. Statistics can be either implemented together for the four QoS services of Conversation, Streaming, Interactive and Background, or implemented respectively. Analysis of traffic statistics data can give a rough direction to the solution of problems from the statistics point of view. Among traffic statistics data, in addition to the proportion data, the statistics the original counter data (i.e. the number of connection request messages received by RNC from RRC) should also be emphasized. Besides, we should be familiar with the corresponding relations between the original counter data and the proportion data, the meanings of these data and the position of these data in the setup process of signaling service. The calling setup success rate is obtained from the product of RRC setup success rate and RAB setup success rate. This can be simplified during the actual traffic statistics analysis process. Namely, RRC setup success rate and RAB setup success rate can be analyzed separately and even analysis specific to Conversation, Streaming, Interactive and Background can be performed separately. Through the analysis on the traffic statistics data related to RRC setup and RAB setup, we can locate the possible parts of access process where problems have occurred and determine the direction for further analyses. After all, traffic statistics analysis is an approximation analysis method in the sense of statistics. Traffic statistics analysis of access process is show in 2.2.1.
11-12-20
Confidential
Page 8 , Total 39
Figure 1
RRC setup success rate reflects the subscriber call success rate of the network to a great extent, because RRC setup is closer to the radio interface from the access point of view, and the probability of exceptions is higher than that of RAB. RRC setup success rate may have two opposite behaviors in traffic statistics: one is that traffic statistics shows high access rate, but the subscribers still complain about access difficulty. This is because the access process failed before RRC CONNECT REQUEST is sent. If RRC CONNECT REQUEST is added during creation of a performance statistics task, this value will be found much smaller than the normal statistics value (or the experience value). The reason is that traffic statistics cannot reflect this situation with the index of RRC setup success rate if UTRAN has not received RRC setup request message, but it only supports query of the statistics index of the number of RRC connection request messages. In this case, mainly analyze such processes as cell searching before RRC connection setup, cell selection and reselection, and random access. The other behavior is low RRC setup success rate, which reflects truly the problem of access difficulty. In this case, it is not certain that the access failure occurs after RRC connection setup. Number of RRC CONNECT REQUEST messages should be checked. If it is much lower than the normal statistics value, factors before RRC connection setup should be considered; if it is approximately the normal statistics value, it is time to emphasize on analyzing the flow after UTRAN received the RRC CONNECT REQUEST message. The key process of RAB setup is RB setup (having air interface message interchange with UE). When analyzing RB setup success rate, we analyze the RAB setup success rate as the main point, because the other processes except RB setup mainly include message interchange through ground interface and
11-12-20
Confidential
Page 9 , Total 39
within the equipment. The formula of RB setup is as follows. If RB setup success rate is high while RAB setup success rate is low, check the equipment condition and the transport layer configuration of the ground interface.
RB setup s uccess rat e = RB setup s uccess tim es RB setup r equest tim es
Among access-related traffic statistics data, in addition to RRC setup success rate and RAB setup success rate and related original counter data, other statistics data related to RRC and RAB can also be analyzed, for example, the ratio of RRC and RAB setup failure because of congestion. If the congestion ratio is high, it means that the cell is overloaded. For detailed descriptions, refer to the relevant document about traffic statistics indices, HUAWEI 3G WCDMA PART: Performance Management Indices - RNC.
11-12-20
Confidential
Page 10 , Total 39
reasons may be that UE has failed to send the message, and this can be observed from UE background printing and message; another possible reason may be pocket loss due to NodeB decoding error or packet loss due to IUB interface (can be observed with a network hawk).
Figure 2
11-12-20
Confidential
Page 11 , Total 39
Similarly, if sufficient signaling cannot be obtained through radio network signaling analysis, the following transport network layer should be analyzed.
Figure 3
11-12-20
Confidential
Page 12 , Total 39
Figure 4
11-12-20
Confidential
Page 13 , Total 39
U E
RRC
Figure 5 Signaling Flow for RRC Setup in Each Layer of Dedicated Channel For RRC setup in dedicated channel, , according to the signaling flow shown in Figure 5, problem analysis can be performed in the following steps, as shown in Figure 6. Site engineers can locate the rough range of the problem and collect the relevant on-site location information according to the flow chart. If it is necessary to make in-depth location on the site, refer to WCDMA Expert Group, WCDMA System Problem Location Manuel, 20030102 Edition.
11-12-20
Confidential
Page 14 , Total 39
N
1
Y N
RLsu ssfu cce lly se u ? t p
Y
A L P TH A2 A su ssfu se cce lly t u? p
N
3
Y
DCH FP su ssfu se cce lly t u? p
Y
UEre ive ce s RRC se p tu
N
5
Y
RNC re ive ce s RRC se p tu co p te m le
Y N
RN re ive RL C ce s RE TO S RE
Y
RR su ssfu se u C cce lly t p ind d te ch n e e ica d a n l
Figure 6
1 RNC fails to receive RRC CONNECT REQUEST messages: Through UU interface tracing of RNC, no RRC connect request message is found. Firstly, check with network hawk whether the RRC connect request message has been sent to the IUB interface. If it is found, analyze whether the problem is with cell search, random access or due to NodeB internal abnormality. This can be located with the help of UE background print and NodeB debugging console; if an RRC connect request message appears on the IUB interface, it is possibly because of pocket loss on the IUB interface or RNC internal abnormal processing. Check pocket loss on the IUB interface
11-12-20
Confidential
Page 15 , Total 39
with network hawk; for the abnormal RNC internal processing, view the RNC alarm subsystem, board serial port printing, board operation log and internal message tracing. 2 Radio link setup failure: It is not likely to occur. However, if it occurs, a possible reason is the internal abnormality of RNC or NodeB. View the alarm subsystem and perform radio link to establish message resolution. If it is necessary to make an in-depth location, the internal flow can be located by using the debugging console of RNC and NodeB. 3 AAL2 link setup failure of bearer air interface signaling: Check the data configuration of AAL2PATH of RNC and NodeB, emphasizing on VPI/VCI of AAL2PATH, ATM address of NodeB, ALL2PATH ID, PVC flow and type, AAL2PATH bandwidth and CID consumption. 4 DCH FP synchronization failure: The transmission channel of DCH FP is synchronized through the interaction of the uplink and the downlink synchronization frames. Observe these two control frames on the IUB interface with network hawk. If DCH FP synchronization fails, the possible reasons include inconsistent AAL2PATH configuration at the both sides, too long IUB interface delay or equipment clock abnormality. These reasons can be checked one by one. 5 UE fails to receive RRC CONNECT SETUP message: Check from RNC, following the sequence of UU interface tracing of RNC, IUB interface (with network hawk), AAL2 link of IUB interface, E1/T1 status and NodeB processing, to locate the problem. 6 RNC fails to receive RRC CONNECT SETUP COMPLETE message: Refer to Section Error: Reference source not found, Signaling Analysis Cases. 7 RNC fails to receive RL RESTORE message: If RNC fails to receive the RL RESTORE message within a certain period of time, NodeB uplink synchronization is considered to have failed, and RNC will initiate link removal. Check whether the configuration of uplink synchronization parameters such as N_INSYNC_IND, N_OUTSYNC_IND and T_RLFAILURE are reasonable.
11-12-20
Confidential
Page 16 , Total 39
If RNC fails to receive the RRC CONNECT SETUP COMPLETE message from UE, there are three possible reasons: UE fails to send the message, the message is lost during transmission, and UE fails to receive RRC CONNECT SETUP. UE fails to send the RRC Connect Setup Complete message. Location steps: There are two ways to identify whether UE has received the RRC CONNCET SETUP message: 1) Check whether the printed information is available on the HyperTerminal indicating that the RRC CONNECT SETUP message has been received. If such information is not available, the SETUP message has not been received. Open the air interface message reported by RRC, and check the RRC CONNECTION REQ message is followed by the RRC CONNECTION SETUP message. If so, check whether the UE IDs of these two messages are consistent. If they are not consistent, the SETUP message has not been received (After receiving the air interface message, UE will report to the background first before it processes the message, so the SETUP message seen at the background is not necessarily from this UE. It is necessary to compare the UE IDs for confirmation). The air interface message reported by RRC is as the follows:
Figure 7
2) After UE receives the SETUP message, it releases RB0 (random access channel), starts power control after the completion of release before the protection timer times out, and proceeds with establishing
11-12-20
Confidential
Page 17 , Total 39
downlink dedicated channel (configuration of radio link and transmission channel and MAC). After RRC receives all the configuration primitives of each layer before the protection timer times out, it starts the T312 timer, and stops this timer after it receives N312 CPHY_SYNC_IND primitives before the T312 timer times out. Then it starts establishing uplink dedicated channel (radio link) and configures RLC (RB1RB4). After RRC receives all the configuration primitives of each layer before the protection timer times out, it starts measurement, configures the maximum transmit power of the UE, and starts the SRB DELAY timer (waiting for NodeB to perform uplink synchronization). It sends the RRC CONNECTION SETUP COMPLETE message after the SRB DELAY timer times out. In each configuration stage, if RRC fails to receive all the configuration primitives of each layer before the protection timer times out, UE will fail to send out the RRC CONNECTION SETUP COMPLETE message. Mainly the primitives for instance creation, configuration and release sent by RLC, MAC and the physical layer are involved. The most common situation is that RRC fails to receive N312 CPHY_SYNC_IND primitives (indicating downlink synchronization failure) when the T312 timer times out, and this causes UEs failure to send the RRC CONNECTION SETUP COMPLETE message. In case of synchronization failure, we can enable Power Control Information Display of UE background to observe the measured values of downlink RSSI and SIR. If RSSI is smaller than -100dBm and the measured value of SIR has been all the time lower than the target value of Sir, check whether the setting range of NodeB transmit power is correct (observe through the radio link setup message of Iub). Note that corresponding options in Display Setting should be set before the information can be displayed. Packet loss caused by abnormality in NodeB Check the relevant statistics information of demodulating DSP and decoding DSP through the NodeB debugging console, and identify whether NodeB has received data packets at the new uplink DPDCH or whether the packets received are all wrong ones. For detailed operation, refer to the help document of NodeB debugging console. Packet loss on the IUB interface The RRC CONNECT SETUP COMPLETE message may have been lost on the IUB interface, which can be analyzed from lower layers to upper layers (E1->ATM->FP). Check whether there is an E1 alarm first by viewing whether there is E1 signal loss alarm in alarm subsystem, and then execute DSP E1T1 at RNC maintenance console to check the corresponding E1 state of AAL2PATH. In case of E1 link disconnection, carry out loop-back operation respectively at the RNC and NodeB ends, through which the problem can be basically located in RNC, NodeB or transmission. Bottom layer transmission is probably implemented in the IMA group mode. In this case, check that the IMA group numbers at both ends of each E1 in the IMA group are consistent. If E1s are in normal state, check whether AAL2PATH of the ATM layer is in normal state, and check the state of PATH with the MML command DSP AAL2PATH, with PATH ID, NASP address, E1 link No. and PVC as the major points to check.
11-12-20
Confidential
Page 18 , Total 39
If there is no abnormality in AAL2PATH, check the FP layer in user plane of IUB. Packet loss of FP layer will probably occur due to expiration time. For more about expiration time, refer to relevant documents. RNC receives the RRC CONNECT SETUP COMPLETE message after timeout. The timer times out 5 seconds after RNC stats to wait for a message. Check the timer setting with the MML command LST STATETIMER. If the configuration is improper, revise it with MOD STATETIMER. Confirm the timeout event through the printed information of RNC SPU board. In addition, too much UE printing or too much NodeB main control printing may also cause this problem. In this case, disable the printing function.
information of RNC, NodeB, UMSC and SGSN, viewing equipment operation logs and running corresponding MML command for automatic test of the equipment. The equipment analysis process is equivalent to a process of pre-diagnosis to exclude any problem about equipment that may influence access, so as to avoid doing useless work in the consequent problem location process and avoiding wasting lots of human and material resources. As equipment analysis can work twice the result with half the effort in the actual problem location process, so it is necessary at the early stage of problem location. For instance, detailed printed information of abnormality of RNC is available in the operation log. The operation log of RNC is in the directory of BSC6800\LoadData\FamLog\. The file name format is as follows: FNLOGyyyymmddhhnnss.log. FN: frame No., two-digit numeral string; yyyy: year; mm: month; dd: date; hh: hour; nn: minute; ss: second. The above-mentioned time refers to the moment when the log us uploaded. If there is no file that is after the above-mentioned time, the log buffer area is probably not full, and log files can be uploaded by means of the MML command for uploading log files. (ULD LOGFILE: FN = frame No.). Alarm information can be exported. Open the alarm window, select the alarm to be saved and save it with another name; or run the command exp tbldata to export the alarm information to the directory BSC6800/FTP. Alarms that affect access mainly include transmission alarms of the carrier signaling (E1/T1, SAAL, NCP/CCP, MTP3B, internal IPC and AAL2PATH) and equipment alarms (clock, CPU, DSP, etc.). If such alarms occur, find out the causes and eliminate these alarms thoroughly. Run the MML command TST SYS for equipment automatic test. The system can automatically detect equipment faults of the transport layer and link fault of transport signaling layer. The contents of the self-diagnosis are as follows: board status and subsystem status diagnosis; board auto-test results diagnosis; board clock state diagnosis; WMUX/WFMR board temperature diagnosis; transport layer link diagnosis within/between WRBS frames; transport layer link diagnosis between WRBS frame and WRSS
11-12-20
Confidential
Page 19 , Total 39
frame; DSP, HPI and TDM diagnosis of WFMR board; RFN status; internal PVC configuration. If the self-diagnosis function is successfully enabled, after a certain period of time, the diagnosis results will be reported and saved in the text format under the directory of BSC6800 installation\LOADDATA\ WRBSFAD of the BAM. If LMT and BAM are separated, query the information through FTP Client of operation and maintenance system on the LMT. The naming rule of the diagnosis result files is frame No. + FADRESULT + year month date hour minute. For instance, the diagnosis result file WRBS01FADRESULT2002-1101-10-49.TXT means the text file of fault diagnosis for WRBS frame 1 reported at 10:49, November 1, 2002. Now take the diagnosis result analysis for Subsystem 0 of SPU board of Slot 10 in Frame 3 as an example: *********************BOARD SPU10 DIAGNOSE BEGIN***************************** { [SPU10:(Board Enable)] //Board is normal } ------------------- Board Self-Test Diagnose { [SPU10 SubSystem0:(Chip Self-Test OK)] [SPU10 SubSystem1:(Chip Self-Test OK)] //Board chip self-test is normal } -------------------Board Clock Status Diagnose { [SPU10 Clk Status:(Clock 8K OK)] //Clock status normal } -------------------CPU Usage Diagnose { [SPU10 Cpu No0: (33%)] [SPU10 Cpu No1: (13%)] // Current CPU usage of two subsystems } -------------------------------------------------
11-12-20
Confidential
Page 20 , Total 39
WCDMA RNO Access Problem Analysis Guidance -------------------Intra Control-Plane IPC Status Diagnose----------------{ [Src-SubSystem(10,0) <-> Dest-SubSystem(1 ,0): (Dest-SubSystem Absent)] [Src-SubSystem(10,0) <-> Dest-SubSystem(3 ,0): (OK)] [Src-SubSystem(10,0) <-> Dest-SubSystem(5 ,0): (Dest-SubSystem Absent)] [Src-SubSystem(10,0) <-> Dest-SubSystem(9 ,0): (Dest-SubSystem Absent)]
[Src-SubSystem(10,0) <-> Dest-SubSystem(13,0): (Dest-SubSystem Absent)] [Src-SubSystem(10,0) <-> Dest-SubSystem(0 ,0): (OK)] [Src-SubSystem(10,0) <-> Dest-SubSystem(15,0): (Dest-SubSystem Absent)] [Src-SubSystem(10,0) <-> Dest-SubSystem(7 ,0): (OK)] [Src-SubSystem(10,0) <-> Dest-SubSystem(10,1): (OK)] //The IPC channels between SPU board to FMR, XIE and MUX of this frame is normal; the reason for the abnormality is that the board is not plugged } -------------------Inter SPU-SPU IPC Status Diagnose { [Src-SubSystem(3,10,0) <-> Dest-SubSystem(1 ,10,0):(Diagnose Fail!)] [Src-SubSystem(3,10,0) <-> Dest-SubSystem(1 ,10,1):(Diagnose Fail!)] [Src-SubSystem(3,10,0) <-> Dest-SubSystem(4 ,10,0):(Diagnose Fail!)] [Src-SubSystem(3,10,0) <-> Dest-SubSystem(4 ,10,1):(Diagnose Fail!)] //The IPC channels between SPU of Frame 3 and SPUs of Frame 1 and Frame 4 are not through because Frame 1 and Frame 4 are not configured. } -------------------Inter SPU-HPU IPC Status Diagnose { [Src-SubSystem(3,10,0) <-> Dest-SubSystem(2 ,1,1):(Diagnose Fail!)] [Src-SubSystem(3,10,0) <-> Dest-SubSystem(2 ,1,2):(Diagnose Fail!)] [Src-SubSystem(3,10,0) <-> Dest-SubSystem(2 ,2,1):(Diagnose Fail!)] [Src-SubSystem(3,10,0) <-> Dest-SubSystem(2 ,2,2):(Diagnose Fail!)] ---------------------------------
11-12-20
Confidential
Page 21 , Total 39
WCDMA RNO Access Problem Analysis Guidance [Src-SubSystem(3,10,0) <-> Dest-SubSystem(2 ,3,1):(Diagnose Fail!)] [Src-SubSystem(3,10,0) <-> Dest-SubSystem(2 ,3,2):(Diagnose Fail!)] [Src-SubSystem(3,10,0) <-> Dest-SubSystem(2 ,4,1):(Diagnose Fail!)] [Src-SubSystem(3,10,0) <-> Dest-SubSystem(2 ,4,2):(Diagnose Fail!)]
//Communication between SPU of Frame 3 and HPU of Frame 2 is not available because HPU of Frame 2 is not in position. } The document of common methods for NodeB V1.3 equipment analysis has not been outputted till now, so related contents are to be supplemented.
11-12-20
Confidential
Page 22 , Total 39
Preamble_Initial_Power has influences on random access, and the initial transmit power of dedicated channels has influences on uplink and downlink synchronization of radio links. If it is too low, the synchronization will fail. Inner loop power control: Control of the transmit powers of NodeB and UE through the target values of uplink and downlink SIR. We can view the UE transmit power, UE receiving power, uplink and downlink TPC values, and downlink test SIR and target SIR emulation. Mainly check whether UE transmit power is full, whether the uplink TPC is saturated and whether the receiving power of UE is low. Furthermore, uplink and downlink TPC values, uplink test SIR and target SIR emulation can also be observed on the NodeB debugging console. When establishing uplink and downlink dedicated channels, pay attention to the setting of the initial SIR target value, because there is a delay of outer loop power control compared with inner loop power control, and too low an initial SIR target value will lead to link out-of-synchronization. Outer loop power control: Control of the transmit power of NodeB and UE by correcting SIR target value. Currently, the BLER target value of signaling is 1%. Here is an example of UE access failure after coverage restriction. As shown in the diagram below, call drop occurs when the code transmit power of NodeB and UE uplink transmit power requested by uplink TPC both reach the maximum value, which occurs at the cell border or in case of coverage absence. However, after call drop, UE will conduct cell search and residing, read the system broadcast information, initiate random access and implement location update. As shown below, UE cannot obtain the complete information because of coverage restriction, and it is repeatedly reading the information without being able to get accessed.
11-12-20
Confidential
Page 23 , Total 39
Figure 8
After comparing the drive test results with planning results of the pilot coverage, it is found that this position is out of the planning area. Therefore, when getting into the covered area, UE performs cell residing, receives system information broadcast again normally and initiate location update, as shown below.
11-12-20
Confidential
Page 24 , Total 39
Figure 9
11-12-20
Confidential
Page 25 , Total 39
example, the preamble power ramp step, the maximum preamble retransmission times the synchronization counter and timer are interrelated with one another.
11-12-20
Confidential
Page 26 , Total 39
WCDMA RNP Special Subject Study - Pilot Receiving Strength Requirement Analysis under Given Power Allocation Ratio. doc. Adjustment recommendation: Plan the network appropriately to reduce the dead spots of network coverage. Consider adjusting the antenna azimuth and down tilt, adding repeaters and RRUs or adding micro cells.
11-12-20
Confidential
Page 27 , Total 39
be close to the system preset access threshold values. The uplink and downlink load factors of various services can be observed with MML commandLST CELLCAC. View the RNC traffic statistics data. You can find that the number of times of call failure caused by congestion is far higher than the normal statistics values. If these three conditions are met, we can be sure that the cause of UE access failure is cell overload. Call admission control (CAC) algorithm is to forecast the changes on system load brought by admission of call access request according to the current load of the system and call access request to judge whether the system can run normally with new load conditions. If the changed load has not exceeded the normal operation limit of the system, this access request will be permitted; otherwise, the access request will be rejected. Therefore, the call admission control algorithm is based on load forecast. For this reason, our algorithm always performs load forecast first, and then judges whether the forecast load value exceeds the preset system load threshold. If forecast does not exceed the preset threshold, the access will be admitted; otherwise, the access will be rejected. Adjustment recommendation: Allocate cell traffic appropriately; increase the capacity directly by adding NodeBs.
3.2 Radio Parameter Settings 3.2.1 Too High Settings of Qqualmin and Qrxlevmin
In this case, UE reads Qqualmin and Qrxlevmin from SIB3 during cell selection, and identify whether the current cell is suitable to reside in by the S Criteria: if the S Criteria is met, this cell is considered as a suitable cell for UE, and the UE will reside in this cell, and read other system information required. Then UE will initiate location registration process. If Qqualmin and Qrxlevmin settings are too high, on one hand, when the UE goes too far from the NodeB during the conversation, UE may fail to reside in the cell after off-hook. Power control can ensure that the link remains connected when UE is moving afar, and that UE can perform cell reselection after off-hook. Since the common pilot channel signal is already weak, if Qqualmin and Qrxlevmin are set too high, UE will hardly succeed in cell reselection. On the other hand, UE initial access will become difficult, and it can be seen from UE background of Beijing Institute of Huawei that the UE cannot complete cell residing. Adjustment recommendation: Set proper Qqualmin and Qrxlevmin values according to actual conditions, check system set values with MML CommandLST CELLSELRESEL and then modify them with , MOD CELLSELRESEL .
11-12-20
Confidential
Page 28 , Total 39
The preamble threshold defines the PRACH preamble test threshold, and RNC informs NodeB in common transmission channel setup signaling on the IUB interface (default configuration is 32, equivalent to -20dB). This preamble can be is acknowledged only when the ratio between the preamble power and the noise level received during the preamble cycle is larger than this threshold. If the parameter setting is too small, the random access preamble signal will be judged wrongly and false alarms will increase, which will lower the demodulation quality of random access, especially under the condition of lack of demodulation resources. False alarms can also lead to invalid data transmission of downlink AICH, which wastes downlink power and increases the downlink interference. False alarms probability can be viewed at debugging console. The criterion is one thousandth, and any value high than this figure means that the false alarm probability is too high; if the preamble threshold setting is too large, the access difficulty will increase, and the preamble signal capture probability will be reduced; if the UE uplink transmit power is too high, the PRACH uplink interference will increase. This parameter decides the demodulation quality of random access and subscriber access success rate, and has relations with access distance (access channel coverage radius 2), and different NodeB configurations (four-antenna diversity mode and OTSR mode). Processing recommendation: Adjust access threshold value appropriately, and default values of current system are: preamble threshold: 32, corresponding to -20.0dB.
3.2.3 Inappropriate Setting of Preamble Power Ramp Step and Retransmission Times
UE can obtain maximum preamble retransmission times and preamble power ramp step by receiving SIB3. If UE has not received AI at preset time slot after sending out Preamble, the preamble power will be increased by one step, and the retransmission counter will be reduced by 1, until the counter value becomes 0, when retransmission will be stopped. Setting of preamble power ramp step has influence on the increasing speed of access preamble transmit power. If it is set too small, the number of times of subscriber access attempts will increase, which increases the probability of preamble collision; if it is set too large, the access preamble power value may greatly exceeds the value required, which increases interference to the system. Generally, if the step remains unchanged, the larger the Preamble_Retrans_Max value is, the higher the success rate of random access will be, but the PRACH load will increase consequently. In cells of high traffic, if the maximum retransmission times value is too large, radio channel overload and congestion will be caused, and the probability of UE access collision will be increased greatly, which will reduce call completion rate and radio resource utilization. On the other hand, if the Preamble_Retrans_Max value is set too small, the preamble transmit power of the UE cannot rise to the required value, and the UE access success rate will be reduced. Therefore, an appropriate Preamble_Retrans_Max setting is an important means for making full use of network radio resources and improving call completion rate. Adjustment recommendation:
11-12-20
Confidential
Page 29 , Total 39
These two parameters jointly control the UE access preamble ramp process. When setting these parameters, pay attention to reduction of system uplink interference, improvement of access success rate and reduction access delay. Therefore, it is necessary to set appropriate values according to the actual situation.
N_OUTSYNC_IND, and T_RLFAILURE): In uplink synchronization, the radio link set remains in the initial state until it receives N_INSYNC_IND successive synchronization indications from L1. At this time, the NodeB triggers the radio link restoration process, indicating that the radio link set has been synchronized. Once the radio link restoring process is triggered, the radio link set will be considered to be in the synchronized state. When the radio link set is in the synchronized state, NodeB needs to start the timer T_RLFAILURE after receiving N_INSYNC_IND successive synchronization indications. After receiving N_INSYNC_IND successive synchronization indications, the NodeB needs to stop and reset the timer T_RLFAILURE. If the timer T_RLFAILURE times out, the NodeB will trigger the radio link failure process, and will indicate which radio link set is in the non-synchronized state.
11-12-20
Confidential
Page 30 , Total 39
Downlink synchronization and out-of-synchronization parameters (T312, N312, T313, N313, and N315): When UE starts to establish dedicated channels, it starts the T312 timer, and stops the T312 timer when UE detects N312 successive synchronization indications from L1. Once the timer times out, it means failure of physical channel setup. UE starts the T313 Timer when it detects N313 successive synchronization indications from L1, and it stops the T313 timer when UE detects N315 successive synchronization indications from L1. Once the timer times out, it means radio link failure. Adjustment recommendation: Adjust the parameters according to the actual situation (slow synchronization or fast out-of-sync). Pay attention to the balance between parameters. For uplink synchronization parameters, query them by the MML CommandLST CELLSETUP and modify the parameters by , MOD CELLSETUPafter cell setup. For downlink synchronization parameters, query them by the MML Command LST CONNMODETIMER, and modify the parameters byMOD CONNMODETIMER after cell setup.
Power relative to MAX BS power[dB] -13 -12 -13 -13 -10 -15 -15
Ratio of common channel power in total power (with 1 SCCPCH channel) Ratio of common channel power in total power (with 2 SCCPCH channels)
Adjustment recommendation:
11-12-20 Confidential Page 31 , Total 39
WCDMA RNO Access Problem Analysis Guidance Increase the power allocation ratio for the common channel appropriately.
3.2.8 Over-low Setting of Uplink Initial SIR Target Value of Dedicated Channel
Phenomenon: uplink out-of-synchronization occurs soon after UE initial link creation, and it can be seen from the IUB interface that link removal is caused by RL FAILURE reported by NodeB. If the initial uplink SIR target value is set too low, the uplink generating power of UE will decrease due to inner loop power control. Since there is a lag before outer loop power control functions, out-ofsynchronization may have occurred during this period. Adjustment recommendation: Increase the uplink and downlink initial SIR target values appropriately by MML CommandMOD TYPRABRLC.
11-12-20
Confidential
Page 32 , Total 39
11-12-20
Confidential
Page 33 , Total 39
interface, that is, the expiration time problem, which can be seen on the IUB interface with network hawk, and massive pocket loss alarms can be seen in the serial port printed information of equipment. In an AAL2PATH, distribution of 256 CIDs is admitted, each CID means an AAL2 CHANNAL, and each AAL2 LINK corresponds to an FP. For instance: a voice service, or a DCH, corresponds to an AAL2 CHANNAL identified by a CID. For an AMR voice service, two AAL2 Channels will be established, one of which bears signaling, and the other bears traffic. CIDs are dynamically allocated, and the total bandwidth of all AAL2 Channels must not exceed bandwidth of AAL2 PATH. The IUB interface bears the signaling plane, user plane and management plane. The signaling plane includes NCP, CCP and ALCAP; the plane includes AAL2 PATH, and the management plane is the IPOA operation and maintenance path of the NodeB. There is no problem with the capacity of signaling and management plane in actual applications, and the bottleneck is usually on AAL2 PATH. Micro paths are established dynamically on AAL2 PATH in each calling process. If the available bandwidth of AAL2 PATH (bandwidth mapped to E1) is insufficient, access failure will occur. The following paragraphs will describe the bandwidth allocation on AAL2 PATH, with a 64k data service as an example. On the IUB interface, for a 64k service, besides its own service traffic, the overheads also include FP overhead, AAL2 overhead, ATM overhead and E1 overhead. According to the calculation, the specific overhead proportion is as listed in Table 5. Table 2 Service 3.4K signaling 64K service FP 24% 4% Overhead Proportion for Each Layer on IUB Interface AAL2 12.2% 8.3% ATM 9.4% 9.4% E1 6.25% 6.25%
Data flow (64K data service) 64Kbps / (1-FP overhead) / (1-ATM overhead) /(1-AAL2 overhead) / (1-E1 overhead) + 3.4Kbps/ (1-FP overhead) / (1-ATM overhead) /(1-AAL2 overhead) / (1-E1 overhead) 64Kbps / 96% / 90.6%/ 91.7% / 93.75% + 3.4Kbps/ 76% / 90.6%/ 87.8% / 93.75% 91.60Kbps If the available bandwidth resource of E1 is smaller than 91.60Kbps, service can not access normally. Adjustment recommendation: Check the IUB interface bandwidth and increase transmission resources.
11-12-20
Confidential
Page 34 , Total 39
In addition, these two parameters are specially mentioned because the problem is somewhat concealed, not easily found without service access, and once there is service access, it will appear and make troubles. Adjustment recommendation: Check negotiated parameters by the MML commands LST AAL2PATHand DSP AAL2PATH . If the parameters of both sides are not consistent, remove the path with the related MML command and then create an AAL2PATH.
There are many similar data configuration errors, such as inconsistent signaling point codes of MTP3B layer, etc., which will not be listed here one by one. It is easy to locate such errors, and all we need are signaling flow and MML commands.
11-12-20
Confidential
Page 35 , Total 39
However, access is allowed for subscribers with special ACs. The AC of a subscriber is stored in the USIM. Adjustment recommendation: View the access control information in the cell system information and adjust the cell access control policy.
RNC
CN
Figure 10
1 In the RRC SETUP COMPLETE message, UE sends the START value, and the UE encryption ability (UEA) and UE integrity protection ability (UIA) information to RNC and simultaneously informs RNC about the GSM Classmark 2 and Classmark 3 information according to the requirement of RRC setup message. 2. UE carries the user identity and the KSI (Key Set Identifier) in the initial direct-transmission message (location update request, CM service request, location are update request, attach request and paging response) to inform CN. 3. CN decides on the IK/CK to be used according to the KSI. It performs authentication, and informs the UE about the new IK/CK. Meanwhile, CN decides on the UIAs and UEAs permitted for use. 4. CN sends the RANAP message SECURITY MODE COMMAND to RANAP to start encryption and integrity protection. 5. RNC selects an algorithm supportable by UE among the algorithms provided by CN, and generates a random number FRESH required by the integrity protection algorithm. RNC carries out judgment according to the ability reported by UE: if the UE ability cannot support these algorithms, RNC
11-12-20
Confidential
Page 36 , Total 39
sends the SECURITY MODE REJECT message to CN in response, and then RNC triggers the release flow. RNC sends an RRC message SECURITY MODE COMMAND to the UE. This message includes UE integrity protection ability, GSM encryption ability (optional, if received in the RRC setup complete message), UIA and FRESH. RNC performs integrity protection of this message. 6. After UE receives RRC message SECURITY MODE COMMAND, it compares the UE ability information in the message. If it is the same with the UE ability information saved locally, it will be deemed legal. UE performs integrity protection check on the SECURITY MODE COMMAND message received. If it is correct, UE sends an RRC message SECURITY MODE COMPLETE to RNC. This message also requires integrity protection. If the security mode configuration fails, UE sends the SECURITY MODE FAILURE message to RNC. 7. After receiving the success response message from UE, RNC performs integrity protection check. If it is correct, RNC sends an RNCAP response message SECURITY MODE COMPLETE to CN, which includes the algorithm selected. Then the flow ends. If RNC receives the SECURITY MODE FLILURE message, or if the security mode configuration fails, RNC sends the SECURITY MODE REJECT message to CN, and then triggers RRC release. Currently, all the security processes of equipment are provided with switches. If the support of authentication encryption by UE and network side is not consistent, UE access will surely fail. This problem can be identified through the RNC and CN messages. Adjustment recommendation: Adjust the security parameter configuration of the UE so that it can consistent with the network side.
4 Outstanding Issues
1. For the radio parameters that affect access, the influences are only qualitatively analyzed, and the reference values for various radio environments are not given. Such reference values can be available after further test and study.
11-12-20
Confidential
Page 37 , Total 39
2. Because there are many core network devices, the interface protocols are very complicated, and there are differences between R99 and R4 devices on the network (CS is replaced with MSC server and MGW), this document only presents the most common causes that affect access, so this part of contents are to be supplemented.
11-12-20
Confidential
Page 38 , Total 39
Lists of References [1] 3GPP R1999 25_series, 2002/09 [2] Chenqi, WCDMA RNP Special Technology Research Key Signaling Process Analysis Access Process,2003/06 [3] Zhou Xinjie, WCDMA RNP System Parameter Configuration Guidance,200/04 [4] Luo Biqun, CDMA 1X Call Drop Analysis GuidanceV1.0,2003/01 [5] Wang Dekai/Xie Zhibin/Wanpeng, WCDMA RNP V100R002 Downlink Common Channel Power Distribution Rate Outfield Test Report,2002/11 [6] Joint Test Group, GMCC-HUAWEI WCDMA Dongguan Test Office Second Phase Radio Network Optimization Report (Internal Version), 2003/4 [7] WCDMA Expert Team, WCDMA System Problem Location Manual 20030102 Version, 2003/1
11-12-20
Confidential
Page 39 , Total 39