Professional Documents
Culture Documents
W Access Problem Optimization Guide 20081115 A 3 - 3
W Access Problem Optimization Guide 20081115 A 3 - 3
Confidentiality level
WCDMA RNP
Product version
Total 134 pages
3.3
Prepared by
Dong Yan
Date
Reviewed by
Date
Reviewed by
Qin Yan
Date
Approved by
Date
2005-11-21
Revision Records
Date
Version
Description
Author
2004-08-23
2004-11-03
2004-12-20
2005-11-21
1.00
1.00
1.20
3.00
Guan Shiguo
Guan Shiguo
Guan Shiguo
Dong Yan
2006-05-19
3.10
2006-06-21
2006-10-23
3.11
3.12
2007-08-25
3.2
2007-12-5
3.3
2008-11-15
3.3
Outline
Initial transmittal
Revising according to review
According to V3.0 guide requirements, reorganizing and
updating V2.0 guide. The update includes:
l Modifying document structure
l Adding optimization objectives
l Adding delay optimization
l Adding some new cases and analysis
l Redrawing analysis flow chats
l Adding appendix which contain the background knowledge
about access.
l Adding analysis of traffic statistics data
V3.10 adds analysis of HSDPA with the following content
updated:
l Supplementing admission failure analysis and cases about
RRC connection, RAB assignment process in HSDPA service
l Adding HSDPA-related DT and traffic statistics values
l According to traffic statistics indexes of RNC version
1.6C01B064, adding some traffic statistics indexes
l Updating RRC connection analysis
Adding analysis of traffic statistics in paging problems
l Adding analysis of reasons for admission rejection
l Adding algorithms of admission rejection in V17
l Adding analysis of dualband access problems
l Adding analysis of impacts brought by dual-carrier direct
retry on the access delay
Adding HSUPA analysis, including:
l Introduction to HSUPA load control algorithms
l Description of key parameters in HSUPA load control
l Introduction to indexes of success rate of HSPA RAB setup
l Strategy of HSPA dualband networking
Adding analysis of MBMS service, including:
3.3.9 Analysis of MBMS service access problems
4.3.6 Analysis of low MBMS service setup success rate
Review yearly
Wang Dekai
Dong Yan
Wang Dekai
Gao Bo
Wang Dekai
Shan Weizhen /
Hu Wensu
Contents
1 Introduction ............................................................................................................................ 16
2 Evaluating Access Performance ........................................................................................... 17
2.1 Accessibility............................................................................................................................................. 17
2.2 System Availability................................................................................................................................... 18
2.3 Access Delay ............................................................................................................................................ 18
2008-11-17
Page 4 of 134
6 Summary ................................................................................................................................. 95
7 Appendix 1: Paging Process .................................................................................................. 96
7.1 Paging Origination ................................................................................................................................... 96
7.1.1 Paging by CN .................................................................................................................................. 96
7.1.2 Paging by UTRAN .......................................................................................................................... 96
7.2 Paging Flow ............................................................................................................................................. 96
7.2.1 Paging Type 1 .................................................................................................................................. 96
7.2.2 Paging Type 2 .................................................................................................................................. 98
7.3 Behaviors of UE after Receiving Paging ................................................................................................... 98
2008-11-17
Page 5 of 134
2008-11-17
Page 6 of 134
2008-11-17
Page 7 of 134
Figures
Figure 3-1 Overall flow for analyzing call failure problems in DT/CQT ......................................................... 22
Figure 3-2 Signaling flow of originated UE in locating paging problems ........................................................ 23
Figure 3-3 Flow for analyzing paging problems ............................................................................................. 24
Figure 3-4 Flow for analyzing RRC connection setup problem ....................................................................... 26
Figure 3-5 Authentication failure due to MAC Failure.................................................................................... 29
Figure 3-6 Authentication failure due to Synch Failure ................................................................................... 30
Figure 3-7 Security mode control ................................................................................................................... 30
Figure 3-8 Security mode reject ..................................................................................................................... 31
Figure 3-9 Dualband scenario 1 (f1: R99; f2: R99+HSPA) ............................................................................. 35
Figure 3-10 Dualband scenario 2 (f1: R99+HSPA; f2: R99+HSPA) ................................................................ 35
Figure 3-11 Functions and process of RRC direct retry and re-direction during setup of the RRC connection .. 36
Figure 3-12 Signaling for service-based direct retry of a HSDPA subscriber ................................................... 37
Figure 3-13 Signaling for direct retry of a R99 subscriber after admission rejection ........................................ 38
Figure 3-14 Flow chart of broadcast model in MBMS .................................................................................... 39
Figure 4-1 Flow for analyzing RNC-level traffic statistics data ....................................................................... 44
Figure 4-2 Flow for analyzing cell-level traffic statistics data ......................................................................... 45
Figure 4-3 Position for counting point by counter for paging loss by idle UE .................................................. 47
Figure 4-4 Position for counting point by counter for paging loss by UE in PCH state .................................... 48
Figure 4-5 Position for counting point by counter for RRC connection rejection ............................................. 50
Figure 4-6 Position for counting point by counter for CS RAB assignment failure in RNC traffic statistics
starting counting ............................................................................................................................................ 54
Figure 4-7 Position for counting point by counter for PS RAB assignment failure in RNC traffic statistics ...... 57
Figure 4-8 Position for counting point by counter for RB setup failure in traffic statistics ............................... 63
Figure 5-1 Originating signaling flow of paging failure due to UE location area update .................................. 66
Figure 5-2 Content of the Disconnect message in paging failure due to UE location area update..................... 67
Figure 5-3 Terminating signaling flow of paging failure due to UE location area update ................................. 67
Figure 5-4 Signaling of UE ............................................................................................................................ 69
2008-11-17
Page 9 of 134
Figure 5-5 Signal quality when the UE sends the RRC connection request message. ....................................... 70
Figure 5-6 Signal quality when the UE repeats to send the RRC connection request........................................ 71
Figure 5-7 Signaling of UE in a connection process ....................................................................................... 72
Figure 5-8 Single subscriber tracing signaling on RNC .................................................................................. 72
Figure 5-9 Quality of downlink signals .......................................................................................................... 73
Figure 5-10 Regular interference in cell 248................................................................................................... 73
Figure 5-11 Part of magnified chart of interference......................................................................................... 74
Figure 5-12 Signaling upon improper configuration of FACH power .............................................................. 75
Figure 5-13 Signal strength upon the first sending of RRC connection request ................................................ 76
Figure 5-14 Single subscriber tracing signaling by RNC................................................................................. 76
Figure 5-15 Signaling and signal strength upon the second sending of RRC connection request ...................... 77
Figure 5-16 Traced signaling at UE side......................................................................................................... 78
Figure 5-17 Traced signaling at RNC side ...................................................................................................... 78
Figure 5-18 BLER statistics at UE side .......................................................................................................... 79
Figure 5-19 BLER and RRC message at UE side ........................................................................................... 80
Figure 5-20 BLER and RRC message at UE side ........................................................................................... 81
Figure 5-21 Assignment of HSDPA code tree ................................................................................................. 82
Figure 5-22 RNC log for HSDPA admission rejection .................................................................................... 83
Figure 5-23 Signaling of Disconnect after completion of RB setup ................................................................ 84
Figure 5-24 Signaling of UE upon a connection failure .................................................................................. 85
Figure 5-25 Single subscriber tracing signaling by RNC................................................................................. 85
Figure 5-26 Signal strength before release of connection ................................................................................ 86
Figure 5-27 Rejection messages in security mode........................................................................................... 88
Figure 5-28 Content of the RANAP_SECURITY_MODE_REJECT message................................................. 88
Figure 5-29 ciphering mode information configured in previous security mode command............................... 89
Figure 5-30 Security mode message ............................................................................................................... 89
Figure 5-31 Content of the RANAP_SECURITY_MODE_COMMAND message .......................................... 90
Figure 5-32 Signaling of UE upon failure in receiving RRC Connection Setup message ................................. 91
Figure 5-33 Single subscriber tracing signaling by RNC................................................................................. 91
Figure 5-34 Signal strength upon occurrence of problems .............................................................................. 92
Figure 5-35 Signaling of UE .......................................................................................................................... 93
Figure 5-36 Downlink signal quality .............................................................................................................. 93
Figure 7-1 Flow chart of PAGING TYPE 1 message ...................................................................................... 97
2008-11-17
Page 10 of 134
2008-11-17
Page 11 of 134
Tables
Table 2-1 Indexes and recommended values for accessibility related to DT ..................................................... 17
Table 2-2 Indexes and reference values for accessibility related to traffic statistics .......................................... 17
Table 2-3 Indexes and reference for system availability .................................................................................. 18
Table 2-4 Indexes and reference for access delay related to DT ....................................................................... 18
Table 3-1 RB setup delay on the RNC with or without DRD ........................................................................... 42
Table 4-1 Counters related to paging loss for idle UE ..................................................................................... 46
Table 4-2 Counters related to paging loss for UE in PCH state ........................................................................ 48
Table 4-3 Counter related to paging loss due to flow control ........................................................................... 49
Table 4-4 Counters related to PCH congestion................................................................................................ 49
Table 4-5 Counters related to RRC connection request rejection due to lub interface failure ............................ 50
Table 4-6 Traffic statistics counters related to RRC connection request rejection due to network congestion .... 52
Table 4-7 Counter related to RRC connection failure due to no response......................................................... 53
Table 4-8 Counters related to RRC connection setup rejection due to redirection ............................................ 53
Table 4-9 Traffic statistics counters related to CS RAB assignment setup failure due to radio network problems
...................................................................................................................................................................... 54
Table 4-10 Traffic statistics counters related to CS RAB assignment setup failure due to insufficient capability
...................................................................................................................................................................... 55
Table 4-11 Counter related to CS RAB assignment setup failure due to transmission network problems .......... 56
Table 4-12 Traffic statistics counters related to PS RAB assignment setup failure due to radio network problems.
...................................................................................................................................................................... 58
Table 4-13 Traffic statistics counters related to PS RAB assignment setup failure due to insufficient capability
...................................................................................................................................................................... 59
Table 4-14 Counter related to PS RAB assignment setup failure due to transmission network problems .......... 60
Table 4-15 Counter related to PS RAB setup failure due to no resource available ............................................ 61
Table 4-16 Traffic statistics counters related to RB setup failure ..................................................................... 63
Table 4-17 Traffic statistics counter related to no response to RB setup ........................................................... 64
Table 4-18 Measurement of MBMS service setup time at IU interface ............................................................ 64
Table 4-19 Measurement of face-to cell MBMS service. ................................................................................. 65
2008-11-17
Page 13 of 134
2008-11-17
Page 14 of 134
Abstract
The document describes how to locate and solve access problems in WCDMA network
optimization, the definition of access problems, test methods, analysis flows, and solutions.
Finally, the appendix provides the fundamental knowledge necessary for analyzing access
problems by RNO engineers.
2008-11-17
Full Spelling
DT
Drive Test
CQT
RNC
RNP
RNO
GBR
GBP
Page 15 of 134
Introduction
This document aims to meet the requirements on solving access problems by on-site
engineers during RNO. It details the methods for evaluating network access performance, test
methods, data analysis methods, FAQs, and solutions. The appendix provides the fundamental
knowledge about access problems, description of principles, related parameters, and data
processing tools. It guides engineers to locate and solve access problems during optimizing
network KPI indexes and network O&M. The RRM algorithms and product implementation
in this document are for RNC V16, unless specified particularly. 3.3.7 , 3.3.8 , and 3.4.5 are
updated.
This document excludes the usage of tools.
It contains 10 chapters, with the structure as below:
l
Chapter 1: Introduction
Chapter 6: Summary
2008-11-17
Page 16 of 134
The access performance includes three aspects: accessibility, system availability, and access
delay. The specified indexes for measuring access performance are obtainable by DT and
traffic statistics. For the definition of indexes, see the UMTS Radio Network KPI Baseline
V3.3.
2.1 Accessibility
Table 2-1 lists the indexes and recommended values for accessibility in DT.
Table 2-1 Indexes and recommended values for accessibility related to DT
Index
Service
Statistics method
Reference
Voice
DT&CQT
96%
VP
DT&CQT
95%
Voice
DT&CQT
95%
VP
DT&CQT
94%
PS
DT&CQT
96%
HSDPA
DT&CQT
96%
Table 2-2 shows the indexes and reference values for accessibility related to traffic statistics.
Table 2-2 Indexes and reference values for accessibility related to traffic statistics
2008-11-17
Index
Service
Statistics method
Reference
N/A
Stat.
85%
N/A
Stat.
97%
Voice
Stat.
98%
VP
Stat.
98%
PS
Stat.
97%
HSDPA
Stat.
97%
Page 17 of 134
The values previously mentioned are just for reference. Determine the actual values according
to the detailed requirements of projects or requirements of commercial network contracts.
Service
Statistics method
Reference
All services
Stat.
2%
All services
Stat.
0.5%
All services
Stat.
1%
The values previously mentioned are just for reference. Determine the actual values according
to the detailed requirements of projects or requirements of commercial network contracts.
Service
Statistics method
Reference
Voice
CQT
7s
VP ring
CQT
7s
CQT
13s
PS
CQT
4s
HSDPA
CQT
2s (average)
< 4s (95%)
The values previously mentions are just for reference. Determine the actual values according
to the detailed requirements of projects or requirements of commercial network contracts.
2008-11-17
Page 18 of 134
Nastar CHR
VP call failure
According to the preset judgment conditions, the DT data analyzers can usually judge the
access failure problems during test. The analyzers include GENEX Assistant and Actix
Analyzer.
2008-11-17
Page 19 of 134
The originated UE waits for the CONNECT or ALERTING message until expiration, so
the call clearing process is originated. According to the protocols, after the UE sends the
CM SERVICE REQUEST message, the timer T303 starts. If the UE fails to receive the
CALLPROCEEDING, ALERTING, CONNECT, OR RELEASE COMPLETE message
before expiration of T303, the clearing process starts.
Before receiving alerting message, the UE enters the idle state and starts to receive
system information.
As strictly defined, after the MS enters the CELL_DCH state and before it receives the alerting message,
it must send the cell update message with the cause RLC unrecoverable error/ Radio link failure.
Take the greater value of the maximum waiting time configured at RLC layer as default and the
synchronization time as the judgment time. It is unclear that the UE can report the RLC layer message,
so the maximum waiting time is neglected.
----End
----End
2008-11-17
Page 20 of 134
It sends or receives the RRC Connection Release message after receiving RRC
Connection setup
The timer expires. Namely, a period (T300) after the UE sends the RRC Connection
Request message, it fails to receive the RRC Connection setup message
2008-11-17
Page 21 of 134
By DT data analyzing tool, such as Actix Analyzer and GENEX Assistant, determine the time
for Call Fail and obtain the following information:
l
Information about active set, monitor set, and signaling flow collected by UE
Match the signaling collected by UE and the time of single subscriber tracing by messages.
Meanwhile locate the points when problems occur in single subscriber tracing on RNC.
Based on signaling of single subscriber tracing on RNC and UE's signaling flow, determine
the point where call fails occurs according to Figure 3-1. Analyze and solve problems
according to following sub-flows. The problems include:
2008-11-17
Paging problems
Page 22 of 134
2008-11-17
Page 23 of 134
Cell Reselection by UE
If the signals of the cell where the UE camps are weak while the signals of monitored cell are
strong, the problem might be due to cell reselection. When the UE has its location area (LA)
or route area (RA) updated upon paging, the paging message is sent to the original LA or RA,
so the UE fails to receive paging message.
2008-11-17
Page 24 of 134
Congestion
Among previous problems, the uplink RACH problem, downlink FACH power allocation
ratio problem, cell reselection parameter problem, and abnormal equipment problem are
probable.
2008-11-17
Page 25 of 134
Figure 3-4 shows the flow for analyzing RRC connection setup problem.
Figure 3-4 Flow for analyzing RRC connection setup problem
After UE Send RRC Connection Request Message, the RNC Fails to Receive It
If the Ec/Io of downlink CPICH is over low, the problem is about coverage.
If the Ec/Io of downlink CPICH is not over low (such as higher than 14 dB), the problem is
about RACH, with the following causes:
l
If the power ramp of preamble is small, you can add the preamble ramp times. For example,
increase it from 8 to 20.
If the output power of UE is lower than required, there are no specific methods to solve it due
to the limitation of UE performance.
For NodeB problems, check whether there is standing wave alarm on NodeB.
2008-11-17
Page 26 of 134
If the parameter of cell radius is set over small, the NodeB cannot synchronize with the UEs
beyond cell radius. This causes access failure. This usually occurs in wide coverage scenarios
like rural and suburban areas.
After the RNC Receives the RRC Setup Request Message from UE, It Sends the
RRC Connection Setup Message Which Is Not Received by UE
The causes of this problem include:
l
Weak coverage
Check the CPICH Ec/Io. If it is lower than 12 dB (the default value is configured based on
Ec/Io as 12 dB) and
l
If there is no more qualified cell listed in the monitor set, the problem is about coverage.
If there is more qualified cell listed in the monitor set, the problem is about cell
reselection.
After the RNC Receives the RRC Setup Request Message from UE, It sends the
RRC Connection Reject Message
When the RRC Connection Reject message is present, check the cause values, which include
congestion and unspecified.
If the cause value is congestion, the network is congested. Check the network load conditions,
including utilization of power, code, and CE resources. Determine the type of resource that
causes congestion and provide ways of network expansion. For details, see W-Network
Expansion Guide.
2008-11-17
Page 27 of 134
The admission of RRC connection for HSDPA subscribers is consistent with that for R99
subscribers, including power, code, and CE resources. Pay special attention to code admission.
If the code word of HSDPA subscribers is statically assigned, and excessive codes are
assigned to HSDPA subscribers, the RRC connection of HSDPAor R99 subscribers fails
probably. This is due to that the codes of downlink signaling channel for HSDPA or R99
subscribers are inadequate.
If the cause value is unspecified, check the logs to determine causes of failure.
After Receiving RRC Connection Setup Message, the UE Does Not Send Setup
Complete Message
If the downlink signals are normal, the UE might be abnormal. Otherwise initial power of
downlink DCH is over low so the downlink cannot synchronize. You can solve the problem
by adjusting uplink Eb/No of the service.
After the UE Sends the RRC Setup Complete Message, the RNC Fails to Receive
It
It seldom occurs because uplink initial power control leads to increment of UE transmit power.
Upon presence of the problems, you can properly raise the Constant Value of DCH so that
the initial transmit power of uplink DPCCH of UE increases.
This problem is related to whether the initial target value of uplink SIR is rational and has
great impact on uplink initial synchronization at the beginning of link setup.
l
If it is set over large, the uplink interference from initial link setup of subscriber becomes
over large.
If it is set over small, the uplink synchronization time increases, and consequently the
initial synchronization fails.
2008-11-17
Page 28 of 134
MAC Failure
Check the AUTN parameter in the authentication request message send by network side upon
the authentication of network by UE. If the MAC information is incorrect, the UE send the
authentication failure message with the cause value MAC failure, shown as in Figure 3-5.
Figure 3-5 Authentication failure due to MAC Failure
2008-11-17
Unauthorized subscriber
USIM and HLR set different Ki and OP (OPc) for the subscriber
This problem occurs frequently when a subscriber uses a new USIM. To locate this
problem, check whether the Ki and OP (OPc) value of the IMSI are the same. The USIM
has default Ki and OP (OPc), but the USIM reader fails to obtain the value. Therefore,
the Ki and OP (OPc) of the USIM must be known upon defining a subscriber or the Ki
and OP (OPc) of USIM must be made the same value as in HLR.
Page 29 of 134
Sync Failure
When the UE detects that the SQN of AUTN message is incorrect, so the authentication fails.
The cause value is Synch failure (synchronization failure), as shown in Figure 3-6.
Figure 3-6 Authentication failure due to Synch Failure
Authorized subscribers
Equipment problems
2008-11-17
Page 30 of 134
The encryption model configuration of RNC does not match that of CN. For example,
the MSC configures the encryption algorithm UEA0 only but the RNC configures UEA1
only.
UE Capability Problems
To check the UE capability, refer to the RRC Connect Setup CMP message.
Currently the following UEs fail to support encryption algorithm:
l
NEC C606
NEC C616
Nokia 7600
Nokia 6650
Moto A835
Qualcomm 6200
Qualcomm 6250
Siemens U15
To solve the security mode reject problems due to UE capability, change the UE.
2008-11-17
Page 31 of 134
The RNC directly rejects RAB setup request due to incorrect parameter configuration.
Admission rejection
Admission Rejection
For non-HSDPA subscribers, when the system resource (power, code, channel code, Iub
transmission resource, and Credit) is inadequate, the admission is rejected and consequently
call setup fails. Now you must check the uplink and downlink load, code resource, Iub
transmission resource, and CE resource, determine the type of resource that causes congestion,
and provide corresponding expansion methods.
2008-11-17
When excessive codes are statically assigned to HSDPA subscribers, the admission fails
due to inadequate downlink channel code resource for non-HSDPA subscribers. When
the system resource is inadequate and admission fails, the V1.5 or higher RNC conducts
different operations according to RAB Downsizing Switch state. For details, see the
description of solving inadequate lub bandwidth.
If the cell does not support the HSDPA service, the admission of R99 subscribers
depends on the set R99 admission threshold. If the cell supports the HSDPA service and
the downlink power of HSDPA and R99 subscribers is statically assigned, the power
admission of non-HSDPA subscribers is judged by (total power of cell - the power
statically assigned to HSDPA) * admission threshold. When the power of HSDPA and
Page 32 of 134
If the bandwidth of the lub interface is inadequate, activation of R99 high-speed data
services fails due to the limited bandwidth. For example, the AAL2 bandwidth for
service on lub interfaces in many cells can support only a 384 Kbps service. If a 12.2
Kbps voice service already exists, the lub interface fails to provide enough bandwidth for
a 384 Kbps PS service. In the case of RNC V1.3, the RNC returns an SGSN RAB
assignment failure because the requested rate is unavailable. The SGSN then originates
RAB assignment through re-negotiation. In the case of RNC V1.5 or later versions, the
RNC lowers the rate first if the RAB Downsizing switch is on. If the lub resource is
available after the rate is down, the RNC sends a RAB assignment success message to
the SGSN. If the lub resource is not available even though the rate is down to 8 Kbps,
the RNC returns an SGSN RAB assignment failure. The SGSN then decides whether or
not to originate renegotiation based on its internal parameters. If the RAB Downsizing
Switch is off, the processing is the same as that in the case of RNC1.3.
The admission control of NodeB Credit resources is similar to the power admission
control. Whether the available Credit can support the currently requested service
depends on the spreading factor of the new subscriber. If the current Credit is not
adequate, the RNC performs different processing depending on state of the RAB
Downsizing switch in the case of RNC V1.5 or later versions. For details, see the
handling in the case of inadequate bandwidth of the lub interface as described earlier in
this document.
For the admission rejection of HSDPA subscribers, consider the following aspects:
l
In the method for statically assigning power of HSDPA and R99 subscribers, consider:
Whether the cell transmit power guaranteed bit rate exceeds the prescribed threshold
In the method for dynamically assigning power of HSDPA and R99 subscribers,
consider:
For HSDPA subscribers, when the configured bandwidth at lub interface is inadequate,
admission rejection will not occur, but the rate become lower. In addition, the AAL2PATH of
HSDPA and R99 is respectively configured, and HSDPA AAL2PATH must be configured to
HSDPA RT or HSDPA NRT type. If the HSDPA AAL2PATH is configured to R99
AAL2PATH RT or NRT type, RAB assignment will not fail, but the RNC will directly set up
HSDPA service to R99 384kbps.
For V17, strategies of the RRM admission algorithm change as follows:
l
2008-11-17
Downlink power admission control for HSDPA cells is supported. Only dynamic power
assignment is available. For the DCH service, consider whether load of the non-HSDPA
service (the R99 service) exceeds the admission threshold of the non-HSDPA service
(that is, the admission threshold of the original R99 service). In addition, consider
whether the non-HSDPA power and the HSDPA GBP (Power to meet GBR) exceed the
Page 33 of 134
threshold of total power of the cell. For the HSDPA service, check whether the HSDPA
throughput provided by the cell exceeds the threshold of sum of Guaranteed Bit Rates
(GBR) of all subscribers, or whether the GBP of stream services and background
services exceeds the HSDPA power of the cell. In addition, consider whether the
non-HSDPA power and the HSDPA GBP exceed the threshold of total power of the cell.
l
lub interface admission: For the DCH service, the admission depends on the peak bit rate
multiplied by the activation factor of the service. For the HSDPA service, the admission
depends on the GBR. If the lub interface reaches the congestion threshold, DCCC
downsizing occurs. If the RLC_AM re-transmission ratio exceeds the specified threshold,
run the SET CORRMALGOSWITCH command to enable lub Overbooking. In this
case, TF of the R99 occurs or rate of the HSDPA service decreases based on the related
factor. Run the ADD AAL2ADJNODE command to set the service activation factor and
the lub congestion threshold. Run the ADD TYPRABRLC command to set trigger and
release thresholds of RLC_AM re-transmission.
2008-11-17
Page 34 of 134
R99+HSPA
CELL 2
CELL4
R99+HSPA
R99+HSPA
R99+HSPA
R99+HSPA
CELL5
CELL1
CELL 3
CELL6
f2
f1
This section describes access process in the case of dualband networking only.
The access in the case of dualband networking involves direct retry and re-direction in the
RRC connection stage and RAB direct retry. RAB direct retry includes service-based direct
retry and that after admission failure. The direct retry and re-direction algorithms are used to
increase first put-through ratio of the UE.
The following figure shows functions and process of RRC direct retry and re-direction during
setup of the RRC connection.
2008-11-17
Page 35 of 134
Figure 3-11 Functions and process of RRC direct retry and re-direction during setup of the RRC
connection
If the RNC receives a RRC connection request, the admission algorithm decides whether a
RRC connection is allowed between the UE and the current cell based on the load over the
current cell.
l
If the RRC connection is allowed, the RNC sends a RRC CONNECTION SETUP
message to the UE, and then the UE sets up a RRC connection.
If the RRC connection is not allowed, the RNC direct retry algorithm module searches
for a cell that complies with the direct retry algorithm in the UE candidate list.
If a suitable target cell exists, the RNC sends the target cell data to the UE through a
RRC CONNECTION SETUP message.
If no suitable cell exists, the RNC re-direction algorithm selects another suitable
frequency or radio access system (such as GSM), and then notifies the UE of the
REDIRECTION cell through a RRC CONNECTION REJECT message. The UE
originates an access request in the specified frequency or system.
The RAB direct retry includes service-based direct retry and RAB direct retry after admission
failure.
l
2008-11-17
Page 36 of 134
If admission of the HSPA service fails and the direct retry fails in all cells, the service
returns to the DCH of the local cell and a RAB connection is set up on the DCH again.
In dualband scenario 1, the services are carried in R99 cells as the strategy. In this case, the
real-time services do not need inter-frequency direct retry during call setup. Thus, the impact
on real-time services decreases and the HSPA subscribers can access the cells that support
HSPA through service-based direct retry. To make the UE reside in F1, modify the cell
selection and reselection parameter Qoffset2,n of F1 to 50 dB and that of F2 to -50 dB, or bar
F2.
In dualband scenario 2, the strategy of random cell residence is used. The UE originates
service access in the serving cell. All cells that use two carriers adopt the default value of the
Qoffset2,n parameter.
In both scenarios, RRC or RAB direct retry is available for the R99 service and RAB direct
retry after admission rejection is available for the HSPA service. If the direct retry of the
HSDPA service fails, the service returns to the DCH of the local cell and an RAB connection
is set up on the DCH again.
Example 1: In scenario 1, the HSDPA data card resides in the R99 cell. If the PDP is activated,
the subscriber accesses the HSDPA cell through direct retry. Figure 3-12 shows the signaling
for a service-based direct retry.
Figure 3-12 Signaling for service-based direct retry of a HSDPA subscriber
2008-11-17
Page 37 of 134
Example 2: In scenario 1, the admission threshold of the R99 service is exceeded if several
R99 subscribers access the cell. If one more R99 subscriber tries to access the cell, the
admission is rejected in the R99 cells at F1. In this case, the subscriber accesses a
R99+HSDPA cell through direct retry. Figure 3-13 shows the signaling for direct retry after
admission rejection.
Figure 3-13 Signaling for direct retry of a R99 subscriber after admission rejection
2008-11-17
Page 38 of 134
If the MBMS cell is activated, UTRAN will transmit MBMS system information which
includes scheduling information of MCCH and configuration information of MCCH radio
bearer on BCCH repeatedly.
First, network announces UE by SMS or WEB that MBMS service will be broadcasted.
After UE decides to receive MBMS service, it will setup the radio bearer of MCCH
according to the MBMS system message received by UE (corresponding to Service
Announcement).
After RNC receiving the MBMS Session Start message from SGSN, it will setup IU
signaling bearer and service bearer related to MBMS (corresponding to Session Start).
RNC announces UE the change of MCCH information by MICH channel, UE gets the
information of available MBMS service and MTCH-related radio bearer from MCCH
channel (corresponding to MBMS Notification).
UE monitors MTCH, begins to receive data (corresponding to Data Transfer).
Judging that no data is transmitted in a period, BM-SC sends Session Stop message to
announce GGSN/SGSN/RNC to release the related network resource (corresponding to
Session Stop).
The causes that UE cant receive programs include:
1. MBMS service fails in RNC setup, the cause of this failure in current cells can be
searched by MML command: DSP CELLMBMSSERVICE.
This command can indicate the following causes for MBMS service failure:
Access Failure, Common Channel Fault, HPU Link Setup Failure, OLC Release,
Preempted, Adding cell to multigroup Failure, MCCH Scheduling Failure, PA Parameter
Invalid, RLC Parameter Invalid and Invalid value.
Besides, we can check whether RNC MBMS enable switch is on by MML command: LST
MBMSSWITCH.
2008-11-17
Page 39 of 134
2. If MBMS service is already setup in RNC, but theres no information in cell, using the
following steps to locate problem:
1) Check whether the cell is in corresponding SA(Service Area) by MML command:
LST CELLMBMASA and LST MBMSSA.
2) Check whether the MBMS is available in this cell by MML command: DSP
CELLMBMSSERVICE. If MBMS isnt activated, activate it by ACT CELLMBMS.
3) Check whether theres SCCPCH to carry this service and whether its activated, if
not activated, activate it by ACT SCCPCH.
3. Service is already setup in cell, but no data is seen sent down according to RNC HPU.
1) First, check out whether theres data in GGSN
2) Check whether the SGSN user plane address of service is correct.
4. UE keeps staying in CONNECTION state:
This indicates that UE doesnt read the data on MTCH. This may be caused by
TBSIZE configuration problem or incorrect MCCH configuration in SET
MTCHFACH.
5. The buffer of UE is 100%, but theres only voice without figure.
Usually it is because the rate of program resource is higher than the maximum bearer
rate of channel.
6. UE quits after several seconds of receiving normal program.
The common channel priority in SET MTCHFACH is configured improperly to
overlap that in ADD FACH.
2008-11-17
Page 40 of 134
For voice calls, the proceeding delay after enabling authentication and encryption flow is
0.6s longer than proceeding delay after disabling authentication and encryption.
For VP calls, the proceeding delay after enabling authentication and encryption flow is
0.74s longer than proceeding delay after disabling authentication and encryption.
For network security, combined ways of multiple authentications are used at the beginning of
network normal operation. For example, 1/2 authentication is used for location area update
authentication; some services, such as voice, VP, and short messages, use the synchronization
method based on 1/2 authentication; other services use the Always authentication method.
Late assignment
Terminating call
Originating call
Early assignment increases call completion rate. Late assignment avoids occupation of TCH
resource during ringing, so it increases the utilization of TCH resource.
According to test result, the UE receives Alerting message 1.28s earlier in early assignment
than in late assignment. Using late assignment helps to receive response signals (ringing)
from network more quickly, so it is more rational. However, the UE might fail to put through,
2008-11-17
Page 41 of 134
so late assignment affects call completion rate. You must balance the advantages and
disadvantages before using it.
2008-11-17
RAB_ASSIGNMENT
-> RB_SETUP(Avg.)
RB_SETUP ->
RB_SETUP_CMP(Avg.)
Total(Avg
.)
HSPA service
with DRD
80 ms
810 ms
890 ms
HSPA service
without DRD
80 ms
590 ms
670 ms
The data listed in the preceding table is measured when the activation time of high-speed link is set
to 400ms.
Page 42 of 134
This chapter addresses how to analyze traffic statistics data in the first situation. It first
provides a general flow for analyzing traffic statistics data, and then describers the
consideration and methods for analyzing major indexes.
The version of RNC used here for analyzing traffic statistics data is BSC6800V16C01B064.
Therefore, in RNC traffic statistics, the counters for failure cause type is usually cell-level. In
the following sections, priority is given to cell-level indexes.
2008-11-17
Page 43 of 134
After locating cell problems and carrying out solutions, analyze the new data of traffic
statistics
If the new indexes meet requirements, the analysis ends. If there are still problems,
continue the analysis until the indexes meet requirements.
2008-11-17
Page 44 of 134
For the methods and flow for analyze problematic cells, see the flow for analyzing cell-level
traffic statistics data.
The flow for analyzing cell-level traffic statistics data proceeds as below:
l
2008-11-17
If there are cells with unsatisfied indexes, analyze the detailed causes, find major causes
of indexes deterioration, and provide proper solutions.
After carrying out solutions, analyze the new data of traffic statistics until indexes meet
requirements.
Page 45 of 134
Flow control
PCH congestion
Counter description
VS.RANAP.Paging.Att.IdleUE
VS.RANAP.Paging.Succ.IdleUE
VS.RANAP.Paging.Fail.IdleUE
2008-11-17
Page 46 of 134
Figure 4-3 Position for counting point by counter for paging loss by idle UE
When the RNC receives the paging message from CN, and the paged UE is in idle state, the
RNC takes statistics of VS.RANAP.Paging.Att.IdleUE at the point B upon sending PAGING
TYPE 1 message to the cells in paged area.
When the RNC receives the RRC CONNECTION REJECT message from UE, the RNC takes
statistics of VS.RANAP.Paging.Succ.IdleUE at the point C if the RRC connection setup
request is due to one of the following causes:
l
Parameter configuration problem. For this problem, check the paging-related parameters
whether they are configured as the baseline parameters.
Weak coverage. For example, the RNC cannot page a UE in indoor UE without being
covered by signals, or a UE in blind elevator area.
2008-11-17
Page 47 of 134
Table 4-2 shows the counters related to paging loss for UE in PCH state.
Table 4-2 Counters related to paging loss for UE in PCH state
Counter name
Counter description
VS.UTRAN.Paging1.Att
VS.UTRAN.SuccPage1
VS.RRC.Paging1.Fail.PchUE
When the RNC sends the PAGING TYPE 1 message to the UE in CELL_PCH or URA_PCH
state, it takes statistics of VS.UTRAN.Paging1.Att at the point A.
When the UE in CELL_PCH or URA_PCH state receives the PAGING TYPE 1 message, it
sends RNC the CELL UPDATE message. The cause for cell update is paging response. When
the RNC receives the cell update message from UE, with the cause paging response, it takes
statistics of VS.UTRAN.SuccPage1 at the point B.
The RNC will not count the times of sending PAGING TYPE 1 message due to modification of system
information.
2008-11-17
Parameter configuration problem. For this problem, check the paging-related parameters
whether they are configured as the baseline parameters.
Weak coverage. For example, the RNC cannot page a UE in indoor UE without being
covered by signals, or a UE in blind elevator area.
Page 48 of 134
Flow Control
When the lu interface is in flow control state, it drops the paging messages from CN.
Table 4-3 shows the counter related to paging loss due to flow control.
Table 4-3 Counter related to paging loss due to flow control
Counter name
Counter description
VS.CN.Page.Loss.IUFC
When the RNC receives the paging message from CN, and the IU interface is in paging flow
control state, the IU interface drops the paging message and counts the time.
When paging messages are dropped due to flow control at IU interface, the traffic of network
must be heavy. Therefore, precaution to network expansion must be performed.
PCH Congestion
When the RNC receives paging message from CN, and the current paging flow exceeds the
maximum capacity of PCH, PCH is congested and paging messages are dropped.
Table 4-4 lists the counters related to PCH congestion.
Table 4-4 Counters related to PCH congestion
Counter name
Counter description
VS.CN.Page.Loss.PCHCong
VS.RRC.Paging1.Loss.PCHCong.Cell
VS.CRNC.IUB.PCH.Bandwidth
VS.MAC.CRNCIubBytesPCH.Tx
If paging messages are dropped in the cell due to PCH congestion, the paging traffic of the
cell must have reached the maximum traffic. Check the parameters related to repeated paging
and PCH. If this problem is due to heavy traffic volume, split the location area.
2008-11-17
Page 49 of 134
At the RNC side, the RRC connection setup failure includes two situations:
l
After the RNC receives the RRC Connection Request message from UE, it sends UE the
RRC Connection Reject message. This corresponds to the first two major causes listed
previously. The counter starts counting at the point A shown in Figure 4-5.
Figure 4-5 Position for counting point by counter for RRC connection rejection
After the RNC sends the RRC CONNECTION SETUP message, it fails to receive the
RRC CONNECTION SETUP COMPLETE or RRC CONNECTION SETUP FAILED
message from UE. This corresponds to the third cause listed previously.
Counter description
VS.RRC.Rej.RL.Fail
VS.RRC.Rej.AAL2.Fail
2008-11-17
Page 50 of 134
Restricted number of CEs on NodeB. When the estimation of NodeB credits are too
incorrect to actually reflect the usage conditions of NodeB CEs, the RNC judges that
the NodeB CEs are enough, so the RNC sends NodeB the RL setup message.
Consequently, the NodeB responds RL setup failure due to restriction of CEs.
When the RL setup failure leads to that RRC connection rejected times is unequal to
0, you must check the cell load to confirm that restriction on number of CEs is not
present. Check whether there are equipment alarms. Confirm that there is no failure
due to air-conditioner and power amplifier problems.
For example, in a period, for an operator's network, the RRC connection is rejected
hundreds of times due to this cause. According to the following analysis, there are
overheating alarms on NodeB and the causes might be load or ambient temperature,
such as air-conditioner failure. For these problems, contact NodeB maintenance
employees; otherwise, the problems will greatly affect access and handover success
rate.
2008-11-17
Others
Page 51 of 134
Table 4-6 lists the counters related to RRC connection request rejection due to network
congestion.
Table 4-6 Traffic statistics counters related to RRC connection request rejection due to network
congestion
Counter name
Counter description
RRC.FailConnEstab.Cong
VS.RRC.Rej.Power.Cong
VS.RRC.Rej.UL.CE.Cong
VS.RRC.Rej.DL.CE.Cong
VS.RRC.Rej.Code.Cong
Others
There are few such cases, and they are usually product problems. Therefore, this part
neglects it.
2008-11-17
Page 52 of 134
Counter description
RRC.FailConnEstab.NoReply
The UE fails to receive the RRC CONNECTION SETUP message from RNC. The cause
of the problem is irrational configuration of coverage, cell selection and cell reselection
parameters. For details, see 3.3.3 .
After the UE send the RRC CONNECTION SETUP COMPLETE message, but the RNC
does not receive it. Maybe the initial transmit power of uplink DCH is over low. For
solutions, see 3.3.3 .
Counter description
VS.RRC.Rej.Redir.Inter.Att
interfrequency cell
VS.RRC.Reject.Redir.Intrat
2008-11-17
Other problems
Page 53 of 134
When CS RAB assignment fails, the counter starts counting at the point B shown in Figure
4-6.
Figure 4-6 Position for counting point by counter for CS RAB assignment failure in RNC traffic
statistics starting counting
At the point B in Figure 4-6, when the RNC sends CN the RAB ASSIGNMENT RESPONSE
message with the cause failure, the corresponding counter starts working according to
specific failure causes. The RB SETUP process is marked in broken line and is optional.
Table 4-9 shows the traffic statistics counters related to CS RAB assignment setup failure due
to radio network problems.
Table 4-9 Traffic statistics counters related to CS RAB assignment setup failure due to radio
network problems
Counter name
Counter description
VS.RAB.FailEstabCS.RNL
2008-11-17
VS.RAB.FailEstCS.Relo
VS.RAB.FailEstCS.RIPFail
Page 54 of 134
The indexes listed in Table 4-9 are cell-level indexes. For detailed VS.RAB.FailEstCS.Unsp,
see Table 4-10.
l
CS RAB assignment setup fails due to insufficient capability when the cell is congested,
such as Requested Maximum Bit Rate not Available. Note that the causes of the indexes
include the following causes of failure due to radio resource congestion:
Others
Table 4-10 lists the traffic statistics counters related to CS RAB assignment setup failure due
to insufficient capability.
Table 4-10 Traffic statistics counters related to CS RAB assignment setup failure due to
insufficient capability
2008-11-17
Counter name
Counter description
VS.RAB.FailEstCs.Power.Cong
Page 55 of 134
VS.RAB.FailEstCs.ULCE.Cong
VS.RAB.FailEstCs.DLCE.Cong
VS.RAB.FailEstCs.Code.Cong
VS.RAB.FailEstCs.IUB.Band
Table 4-11 lists the counter related to CS RAB assignment setup failure due to transmission
network problems.
Table 4-11 Counter related to CS RAB assignment setup failure due to transmission network
problems
Counter name
Counter description
VS.RAB.FailEstabCS.TNL
Other Causes
The index seldom occurs, so this document neglects it.
2008-11-17
Page 56 of 134
No resource available
Other problems
Figure 4-7 shows the counter for PS RAB assignment failure starting counting in RNC traffic
statistics.
Figure 4-7 Position for counting point by counter for PS RAB assignment failure in RNC traffic
statistics
At the point B in Figure 4-7, when the RNC sends CN the RAB ASSIGNMENT RESPONSE
message with the cause failure, the corresponding counter starts working according to
specific failure causes. The RB SETUP process is marked in broken line and is optional.
Table 4-12 shows the traffic statistics counters related to PS RAB assignment setup failure
due to radio network problems.
2008-11-17
Page 57 of 134
Table 4-12 Traffic statistics counters related to PS RAB assignment setup failure due to radio
network problems.
Counter name
Counter description
VS.RAB.FailEstPS.Par
VS.RAB.FailEstPS.Relo
VS.RAB.FailEstPS.RIPFail
VS.RAB.FailEstPS.Unsp
The indexes listed in Table 4-12are cell-level indexes. For detailed VS.RAB.FailEstPS.Unsp,
see Table 4-14.
l
2008-11-17
Page 58 of 134
The index is present when the cell is congested. For detailed causes, such as Requested
Maximum Bit Rate not Available, see CDL. Note that the causes of the indexes include the
following causes of failure due to radio resource congestion:
l
Others
Table 4-13 lists the traffic statistics counters related to PS RAB assignment setup failure due
to insufficient capability.
Table 4-13 Traffic statistics counters related to PS RAB assignment setup failure due to
insufficient capability
Counter name
Counter description
VS.RAB.FailEstPs.Power.Cong
VS.RAB.FailEstPs.ULCE.Cong
VS.RAB.FailEstPs.DLCE.Cong
VS.RAB.FailEstPs.Code.Cong
VS.RAB.FailEstPs.IUB.Band
2008-11-17
Page 59 of 134
Table 4-14 lists the counter related to PS RAB assignment setup failure due to transmission
network problems.
Table 4-14 Counter related to PS RAB assignment setup failure due to transmission network
problems
Counter name
Counter description
VS.RAB.FailEstabPS.TNL
No Resources Available
No resource available causes PS RAB setup failure
2008-11-17
Page 60 of 134
Table 4-15 shows the counter related to PS RAB setup failure due to no resource available.
Table 4-15 Counter related to PS RAB setup failure due to no resource available
Counter name
Counter description
VS.RAB.FlEstPS.Str.NResAvail
Other Causes
The index seldom occurs, so this document neglects it.
For HSDPA service, the cause of low success rate of RAB assignment is the same as that of
R99 PS RAB assignment. The traffic statistics indexes of PS RAB involve R99 PS service
and HSDPA service.
HSDPA RAB Setup Success Ratio
This KPI can be used to evaluate the RAB setup success ratio of the PS service carried by
HSDPA.
KPI Name
Measurement
Cell
Scope
Formula
Associated
HSDPA _ RAB _ SR =
HSDPA _ RABSetupSuccess
100%
HSDPA _ RABSetupAttempt
VS.HSDPA.RAB.SuccEstab; VS.HSDPA.RAB.AttEstab
Counters
Notes
The RNC level KPI is calculated by aggregating all the cell counters.
2008-11-17
Page 61 of 134
KPI Name
Measurement
Cell
Scope
Formula
Associated
HSUPA _ RAB _ SR =
HSUPA _ RABSetupSuccess
100%
HSUPA _ RABSetupAttempt
VS.HSUPA.RAB.SuccEstab; VS.HSUPA.RAB.AttEstab
Counters
Notes
The RNC level KPI is calculated by aggregating all the cell counters.
RB setup failure
No response to RB setup
RB Setup failure
RB setup failure: after the RNC sends the RB Setup message, it receives the RB Setup Failure
message from UE.
The detailed causes of RB setup failure include:
2008-11-17
Unsupported configuration
Invalid configuration
Page 62 of 134
In traffic statistics of RNC, the counter for RB setup failure starts counting at the point A
shown in Figure 4-8.
Figure 4-8 Position for counting point by counter for RB setup failure in traffic statistics
At the point A shown in Figure 4-8, when the RNC receives the RADIO BEARER SETUP
FAILURE message from UE, it takes statistics according to various causes of RB setup
failure in the cell where UE camps.
Table 4-16 lists the traffic statistics counters related to RB setup failure.
Table 4-16 Traffic statistics counters related to RB setup failure
Counter name
Counter description
VS.FailRBSetup.CfgUnsup
VS.FailRBSetup.PhyChFail
VS.FailRBSetup.CellUpd
VS.FailRBSetup.IncCfg
Unsupported configuration
This is due to maloperations by subscribers. For example, when using downlink 128K
data service, a subscriber receives the RB setup request (originating or terminating VP)
of VP service, the UE directly responds RB setup failure due to unsupported
configuration, namely, most UEs fails to support using VP and high speed (>= 64K) PS
service simultaneously.
Invalid configuration
This is a common causes of RB setup failure. It is possible that: the 3G UE originates VP
service to an terminating MS that camps on GSM cells and that does not support VP
service, so after the RNC receives the RAB assignment request, the CN immediately
2008-11-17
Page 63 of 134
sends the Disconnect command with the cause Bearer capability not authorized after
call proceeding. Consequently, the UE receives the RB_SETUP message and has not
completed RB setup, so it responds RB setup failure upon receiving the Disconnect
message, and then the RNC responds RAB setup failure.
No response to RB Setup
Table 4-17 lists the traffic statistics counter related to no response to RB setup.
Table 4-17 Traffic statistics counter related to no response to RB setup
Counter name
Counter description
VS.FailRBSetup.NoReply
2008-11-17
Description of Index
VS.IU.MBMS.Start
VS.IU.MBMS.Succ
VS.IU.MBMS.Fail
VS.IU.MBMS.Fail.NoRsrc
VS.IU.MBMS.Fail.NNSF
VS.IU.MBMS.Fail.IuUpFail
VS.IU.MBMS.Fail.IuSigFail
IU
Page 64 of 134
Description of Index
VS.MBMS.MTCHSetupSucc.Cell
VS.MBMS.MTCHSetupFail.Cell
Current RNC support broadcast model only, and theres no alternation between UE and
UTRAN in broadcast model, so MBMS related traffic statistic can only obtained according to
MBMS service or cell statistic.
If MBMS service setup success rate at IU interface is low, the causes include:
1. No available resource in RNC
2. NAS Node Selection Function, for details, refer to 3GPP 23.236 4.4.
3. User plane failure at IU interface
4. Signaling connection failure at IU interface
If face-to cell MBMS service setup success rate is low, the causes include:
1. Power, code, transmission, CE admission failure;
2. Common channel problem.
2008-11-17
Page 65 of 134
2008-11-17
Page 66 of 134
According to Figure 5-1, the RNC receives the Disconnect message from CN.
Figure 5-2 shows the content of the Disconnect message.
Figure 5-2 Content of the Disconnect message in paging failure due to UE location area update
According to Figure 5-2, the cause value for the Disconnect message is no route to
destination. Therefore, the connection is released because the destination UE cannot be
paged.
Figure 5-3 shows the terminating signaling flow of paging failure due to UE location area
update.
Figure 5-3 Terminating signaling flow of paging failure due to UE location area update
According to Figure 5-3, the terminating UE has location area and route areas updated.
During the process, the UTRAN fails to page UE, so the call fails.
2008-11-17
Page 67 of 134
Solution
No general solution is for this problem. You can rationally configure the location area and
route area to avoid frequent location area update in hot spot areas.
2008-11-17
Page 68 of 134
The interval between two times of repeating to send request by UE is about 1.2s.
2008-11-17
Page 69 of 134
Figure 5-5 Signal quality when the UE sends the RRC connection request message.
Figure 5-5 Signal quality when the UE sends the RRC connection request message.
2008-11-17
Page 70 of 134
Figure 5-6 shows the Signal quality when the UE resends the RRC connection request.
Figure 5-6 Signal quality when the UE repeats to send the RRC connection request
Treselection = 1
Qhyst2 = 2 dB
Qoffset2 = 0 dB
Sintrasearch = 5
When the signals of target cell are stronger than the serving cell, completing reselection takes
1s. Therefore, the signal fluctuation of target cell and serving cell is similar to previous
description. There is little space to optimize the parameters of cell reselection. The minimum
Treselection is 1. If Treselection is set to 0, the reselection time will be 8*DRX, much longer
than 1s, because the minimum DRX is set to 0.64s. If Treselection is set to 0, the Ec/Io of
target cell must be 3 dB higher than that of serving cell according to protocols. After multiple
statistics, the time for cell reselection is between 1.2s and 1.4s.
Solution
To reduce the time for cell reselection as possible, modify Qhyst2 to 0, SintraSearch to 7.
During walking test, ping-pong cell reselection occurs without decrement of reselection time.
It is recommended that:
l
2008-11-17
Qhyst2 remains 2 dB
Page 71 of 134
After the table shown in Figure 5-9 is sorted by time order, you can see that the RNC
responds to the second RRC setup connection message from UE.
2008-11-17
Page 72 of 134
According to Figure 5-9, the downlink signals are strong, so the uplink signals should be
strong. Why does the first connection fail?
After static test, the problem reoccurs. The problem occurs every half hour. Sometimes, call
fails because repeating to send RRC connection request fails four times. According to analysis
of signaling for tracing TMSI by RNC, the RNC fails to receive the RRC Connection Request
message. The signal strength of the cell: RSCP ranges from 60 dBm to 70 dBm; Ec/No
ranges from 2 dB to 4 dB. According to previous interference analysis, regular interference
is present in the cell, as shown in Figure 5-10.
Figure 5-10 Regular interference in cell 248
2008-11-17
Page 73 of 134
Interference lasts for 40s each time. The last peak shown in Figure 5-10 is not the periodic interference
as previous ones. It lasts for a short time (a sampling point). The interference is present from 8:00 to
21:00. There is no interference in other time.
At first, engineers guess that the interference causes the problem. After sampling data, based
on RNC messages, UE messages, and recorded RTWP, there is no interference one minute
before and after call fails. Therefore the problem is irrelevant to interference.
The following tests are to locate the causes of problems:
2008-11-17
Test with Qualcomm handset (6200). During one-hour call, no similar phenomenon is
present, but the interference is still present. This proves that Qualcomm test handset is
normal.
To check that the problem is not due to AICH, raise the AICH power to 0 dB. Test with
Moto handset and the problem is still present. Namely, the problem is irrelevant to AICH
power.
Restore the AICH power to 7 dB, restore the retransmission times of preamble from 8
to 20. During the test more than one hour, the problem is not present.
Signals are stable and strong during indoor static test: Ec/Io is about 3 dB and RSCP is
about 50 dBm. So engineers doubt that the power of Moto handset is problematic in
areas with strong signals. After engineers lower the Ec/Io to 7 dB by increasing
downlink load, the RRC setup problem remains.
To further confirm that the problem is not caused by interference, test after 22:00.
According to the RTWP, there is no interference, but repeating to send request message
occurs fours times in the test longer than one hour, with two times of Call Fail.
According to comparative analysis of interference record by NodeB and system
information by UE, the interference value is changed. During repeating to send request
message, the interference before and after system information remain the same (105
Page 74 of 134
dB), which proves that the repeating to send request problem of Moto handset is
irrelevant to external interference.
According to previous test, a conclusion is drawn that the problem is irrelevant to uplink
interference and power configuration of AICH. Since the Qualcomm handset (6200) is normal
in the test, the problem must be with uplink RACH of Moto handset.
Solution
After engineers change the retransmission times of preamble from 8 to 20, the problem never
occurs again.
2008-11-17
Page 75 of 134
Figure 5-13 shows the signal strength upon the first sending of RRC connection request.
Figure 5-13 Signal strength upon the first sending of RRC connection request
In Figure 5-13,
l
The fourth and fifth column is the signal strength and scramble of the best monitored
cell.
Because the downlink coverage is weak, so the UE originates the RRC connection request
message. Consequently, the RNC receives the RRC connection request message and sends the
2008-11-17
Page 76 of 134
RRC connection setup message. However, the downlink signals are weak, so the UE fails to
receive the RRC connection setup message.
Figure 5-15 shows the signaling and signal strength upon the second sending of RRC
connection request after 2s.
Figure 5-15 Signaling and signal strength upon the second sending of RRC connection request
When the UE sends the RRC connection request message the second time, the downlink
signal strength is about 13, so the connection succeeds. According to the Figure 5-15, when
the Ec/Io of downlink signals is lower than 12 dB, it is not guaranteed that the UE can
correctly demodulate data from downlink FACH.
The current FACH power is 1 dB, which is provided based on the relationship curve of
FACH Ec/No and power allocation rate tested on field on the assumption that Ec/Io at cell
edge is 12 dB. To raise the receiving success rate when Ec/Io power is 14 dB, raising the
FACH power by 2 dB is recommended out of the consideration for the threshold for starting
inter-RAT measurement.
Solution
After the FACH power is set to 1 dB, the problem no longer exists that RRC connection fails
because the UE cannot receive RRC Setup message in downlink.
2008-11-17
Page 77 of 134
Figure 5-17 shows the traced signaling at RNC side. According to UE side, after the UE sends
the initial direct transfer message, it does not receive any message. Therefore, it repeats to
resend the RRC connection request message after 5s.
Figure 5-17 Traced signaling at RNC side
According to UU interface of RNC, after the RNC receives the initial direct transfer message,
it sends the authentication request message (probably there is no authentication, so the RNC
directly sends the Security mode command). But there is no response, so the RNC release
RRC connection after expiration.
2008-11-17
Page 78 of 134
By comparison of messages at UE side and RNC side, the UE fails to receive the
measurement control and authentication request message (sometimes Security mode
command). According to the BLER statistics at UE side, after the UE sends the initial direct
transfer message, the BLER with 32 as the Trch ID is 100%. Therefore decoding signaling
RB on downlink transport channel is all wrong, so the UE fails to receive any message from
downlink DCH. The RRC setup message is sent on CCH, so the UE can receive it.
From previous analysis, the downlink DCH might be problematic.
2008-11-17
Page 79 of 134
2008-11-17
Page 80 of 134
According to Figure 5-19, when the cell of PSC 205 is listed in active set and multiple
braches of SHO are combined, the BLER increases but call drop does not occur. When signals
of other cell are weak, call drops easily, as shown in Figure 5-20.
Figure 5-20 BLER and RRC message at UE side
The signals from the cell of SC 205 are strong, but the downlink BLER is 100%, so the call
drops. Therefore, the cell of SC 205 is problematic in downlink.
Meanwhile, another cell under the same NodeB is normal. Therefore engineers doubt that a
DSP of downlink NDLP board on NodeB is problematic. After connect a normal cell to the
DSP, the problem is still present. Therefore, the DSP must be problematic. After NDLP reset,
the DSP becomes normal. The DSP is fixed not after activation and deactivation, but after
reset.
2008-11-17
Page 81 of 134
CCH uses a code word (SF = 32) (PCPICH SF=256, PCCPCH SF=256, AICH SF=256,
PICH SF=256, and SCCPCH SF=64)
When an HSPDA subscriber accesses the network, a code word (SF = 128) is necessary for
13.6K signaling. However, no code word is available now, so the RRC connection is rejected.
Figure 5-21 shows the assignment of HSDPA code tree.
Figure 5-21 Assignment of HSDPA code tree
According to the assignment of HSDPA code tree in Figure 5-21, the number of codes
assigned for HSDPA subscribers is clear, as well as the rest codes and the occupation by R99
subscribers. Figure 5-21 shows a sample.
Besides tracing code tree, engineers can obtain the cause of admission failure from RNC logs
based on the time for admission rejection, and IMSI.
2008-11-17
Page 82 of 134
Solution
After engineers assign 14 codes for HS-PDSCH, the HSDPA subscriber succeeds in access
the network.
When codes are statically assigned to HSDPA subscribers, the admission is usually rejected
due to code word restriction. The PS 384Kbps R99 subscribers and other R99 subscribers in
the cell use most codes, so the admission of HSDPA subscribers in downlink is rejected
because the DCH obtains no code word when HSDPA subscribers connect to the network.
2008-11-17
Page 83 of 134
According to Figure 5-23, the UE receives the Disconnect message after completion of RB
setup. The CN releases the connection, so the connection fails. The cause value of Disconnect
is requested circuit channel not available.
The terminating UE is in the equipment room of RNC. There is indoor coverage system in the
equipment room, so the coverage is good. But excessive subscribers are using the network, so
the network is congested and the connection fails.
Solution
Solve access failure problems due to inadequate capacity by network expansion.
This failure occurs under a special background, because excessive subscribers use the
network in the equipment room. Therefore, the test becomes problematic. To guarantee
normal test, engineers must restrict the number of subscribers using the network in equipment
room. This problem must be noticed during optimization.
2008-11-17
Page 84 of 134
Figure 5-24 shows the signaling of UE upon a connection failure according to Analyzer
software.
Figure 5-24 Signaling of UE upon a connection failure
2008-11-17
Page 85 of 134
According to RNC signaling, the signals from the cell of SC 121 attenuate sharply. The cell of
SC 56 needs adding to the active set, the UE cannot receive the ActiveSet Update message
from RNC.
Solution
To solve the problem, adjust the SHO parameters to enable the target cell to be added to the
active set earlier as possible. For details, see guidebooks related to call drop analysis.
Configure 13 codes to HS-PDSCH when multiple subscribers connect to the network. When
the fifteenth HSDPA subscriber accesses the network, the RNC admission is rejected. The
first 14 subscribers is connecting to the network and downloading data. After engineers
change average HSDPA throughput per HS-PDSCH code to 300 kpbs, more than 16
subscribers can access the network.
The following information is from analysis of tracing log of RNC:
l
2008-11-17
Page 86 of 134
NBM_CraCacHsdpaAdm: Hsdpa Admission Failure Because Hsdpa Max Req Rate over
threshold
ulErrorID is 184944608
Obviously, the admission for the 15th subscriber is rejected because the HSPDA bit rate after
the access of 15th subscriber exceeded the HSPDA total bit rate, so the admission fails. The
analysis is as below:
Configure 13 codes to HS-PDSCH. The rate of each code is 200 kpbs. The multiplier factor of
HS-PDSCH transport channel is 10. Therefore, the maximum requested rate of a cell is
13*200Kbps*10=26000000bps. However, during test, after the 14th subscriber accesses the
network, the HSDPA admission is accepted. Therefore,
CellHsDschMaxReqRate=14*2048Kbps = 28672000bps, which exceeds the threshold.
Therefore, HSDPA admission of fifth subscriber fails.
Solution
After engineers change the average HSDPA throughput per HS-PDSCH code to 300 kbps, 16
subscribers can access the network. The problem is solved.
2008-11-17
Page 87 of 134
According to Figure 5-28, the cause of security mode rejection is conflict with already
existing integrity protection and or ciphering information. This cause means that the latest
integrity protection or ciphering information is inconsistent with the configuration.
2008-11-17
Page 88 of 134
Figure 5-29 shows the ciphering mode information configured in previous security mode
command.
Figure 5-29 ciphering mode information configured in previous security mode command
According to Figure 5-29, the encryption algorithm configured in the security mode command
is no encryption, namely, no encryption is conducted on the message.
According to previous command, another security mode command is found, as shown in
Figure 5-30.
Figure 5-30 Security mode message
2008-11-17
Page 89 of 134
According to Figure 5-31, there are two encryption methods: UEA1 and no encryption.
According to protocols, there are two encryption methods: encryption and no encryption,
engineers need select the algorithm to be encrypted. Namely, UEA1 is needed here.
By comparison of these two encryption mode commands, they are from different CN domain:
The CN domain No. of the successful command is 4669, while that of the failed one is 4666.
Namely, the CS and PS domain configures different encryption methods.
After the RNC receives the security mode command shown in Figure 5-31, it selects the
UEA1 as the encryption algorithm. It then receives the security mode command shown in
Figure 5-29 and this command requires no encryption. Therefore, the RNC rejects this
security mode command.
Solution
After setting the CS and PS encryption algorithm to the same, engineers solve the problem
successfully.
2008-11-17
Page 90 of 134
Figure 5-32 shows the signaling of UE upon failure in receiving RRC Connection Setup
message.
Figure 5-32 Signaling of UE upon failure in receiving RRC Connection Setup message
2008-11-17
Page 91 of 134
Figure 5-34 shows the normal signal strength upon occurrence of problems.
Figure 5-34 Signal strength upon occurrence of problems
The messages at IUB interface of NodeB and internal message are normal and without alarms
according to tracing. To further locate problem in the NodeB equipment room, by test, the UE
can sometimes access to the network by antenna where the Ec/Io is about 3 dB, but in rest
time it fails with the same phenomena. The RSCP is about 70 dBm. If the UE moves farther,
the Ec/Io is about 5 dB and the UE cannot connect to the network in a probability of 80%.
The phenomenon is that the UE fails to receive setup message in downlink. According to
detection of NodeB console, the output power of NodeB is 24 dBm, but the normal output
power is 36 dBm. Therefore the power amplifier is problematic.
Solution
After changing the power amplifier, engineers solve the problem successfully.
5.7.2 Abnormal UE
There are abundant phenomena about abnormal UE. The following paragraphs provide an
example.
2008-11-17
Page 92 of 134
In Figure 5-36,
2008-11-17
Page 93 of 134
The fourth and fifth column are the Ec/Io and scramble measured by scanner.
The quality of the signals measured by UE and the signals measured by scanner is much
different from each other during the unconnected time.
Solution
This problem is related to UE performance. There are no more solutions except changing UE.
2008-11-17
Page 94 of 134
Summary
Compared with V2.0, V3.0 addresses operability. It is closer to on-site engineers and can
guide on-site engineers to solve actual problems during network optimization. Therefore this
guidebook has more updated parts compared with the V2.0 guidebook and addresses the flow
for analyzing problems. It guides engineers to solve problem step by step. The fundamental
knowledge serves as appendix for reference by on-site engineers.
Compared with V3.0, the V3.1 guidebook adds the following content:
l
2008-11-17
Updating the methods for analyzing traffic statistics and detailed indexes according to
RNC version
Page 95 of 134
7.1.1 Paging by CN
The CN originates paging so that the CN can request UTRAN to connect to UE. The paging
process is the signaling process without connection at IU interface. The CN triggers paging by
sending paging messages. The UTRAN sends the paging message from CN to UE in the
paging process at UU interface so that the paged UE is connected to CN.
2008-11-17
Page 96 of 134
After the RNC receives the paging message from CN, the cell Non Searching
Indication is specified to non-searching (the RNC does not search whether the UE is in
the connected state) in the paging message.
After the RNC receives the paging message from CN, the cell Non Searching
Indication is specified to searching; but the UTRAN cannot find SRNTI (UE in idle
state) by IMSI.
If the paging message at IU interface contains LAI or RAI, the RNC will send the PAGING
TYPE 1 message to all cells in the specified location area or routing area.
If the paging message at IU interface contains no LAI or RAI, the RNC will send the
PAGING TYPE 1 message to all cells under the RNC.
Besides previous situations, the UTRAN sends the PAGING TYPE 2 message on DCCH,
which is called the cooperation paging.
Figure 7-1 shows the flow chart of PAGING TYPE 1 message.
Figure 7-1 Flow chart of PAGING TYPE 1 message
CN
RNC1
RNC2
NODEB1.1
NODEB2.1
UE
PAGING
RANAP
RANAP
RANAP
PAGING
RANAP
According to Figure 7-1, the CN originates paging in a location area which is distributed
under two RNCs. After the RNC receives the paging message, it searches for the matching
cells and calculates the paging occasion. It sends the PAGING TYPE 1 message to the cell on
PCCH at the paging occasion.
2008-11-17
Page 97 of 134
SRNC
UE
PAGING
RANAP
RANAP
DCCH:
PAGING TYPE 2
RRC
RRC
According to Figure 7-2, if the UTRAN judges that the paging is cooperation paging, the UE
must be in CELL_DCH or CELL_FACH state, so the UTRAN immediately sends the paged
UE the PAGING TYPE 2 message on DCCH.
If the UE is in CELL_PC or URA PCH state, the UTRAN sends the PAGING TYPE 1 to UE.
After the UE receives the PAGING TYPE 1 message, it originates the cell update process to
transit to CELL_FACH state.
Conclusion: If the UE is in CELL_DCH or CELL_FACH state, the network side sends the
PAGING TYPE 2 message. If the UE is in other state, the network side sends the PAGING
TYPE 1 message.
2008-11-17
Compare the IE type of UE identity type in CN IE and the identity of all assigned
UE.
Page 98 of 134
If one pair matches, this means that UE accepts the paging and forwards the IE CN
domain identity, UE identity, and Paging cause to upper layer.
If the IE Used paging identity is UTRAN, and the U-RNTI is the same as assigned
U-RNTI of UE:
If the Paging record does not contain the IE CN originated page to connected
mode UE, the UE starts cell update process with the cause paging response.
If the IE is Used paging identity is not UTRAN, the UE will neglects the paging record.
If the Paging record contains the IE BCCH modification info, the UE in idle mode,
CELL_PCH or URA_PCH state must read the system information again, without
reading content of Paging record.
Decode data on PICH periodically. Only when there is paging indicator, the UE will
decode associated data on SCCPCH, namely, DRX. The UE reduces power consumption
by using DRX.
2008-11-17
Page 99 of 134
The UE must monitors the frames (paging occasions) indicated by red dots in each paging
period, and then decode the qth PI. For the calculation of q, see the formula (3).
2008-11-17
b287 b288
b299
A 10ms (length) PICH consists of 300 bits (b0, b1 b299). Wherein, the first 288 bits (b0,
b1b288) are to carry paging indicator. The rest 12 bits is for following use.
Each PICH frame carries NP paging. NP is the number of paging indications per frame. It
defines the maximum paging indicators supported by each frame on PICH. The UE obtains
the value of NP in cell system information. The NP is 18, 36, 72, and 144; namely, the 288
bits are divided by NP, so each division has 288/NP bits. Each division is a paging indicator.
Table 7-1 describes the mapping relationship between {PI0, .., PIN-1} and PICH bits
{b0,..,b287}.
Table 7-1 Mapping relationship between PI and PICH
Number of PI
per frame (NP)
PIp = 1
PIp = 0
NP=18
NP=36
NP=72
NP=144
The UE determines by calculating its paging indicator suffix p that p is relevant to the qth bits
of PICH frame.
Np
Wherein,
l
SFN is the paging occasion for UE. It is the PCCPCH SFN when PICH is present.
From the formula (3), the UE can know the suffix of PI so that the UE can monitor relevant
bits on PICH only. Once the UE detects that the bits are set to 1, it knows that it is paged. It
starts receiving and decoding paging messages from 7680 chips after completion of PICH
radio frame.
2008-11-17
Figure 7-5 shows the time sequence relationship between PICH and SCCPCH.
Figure 7-5 Sequence relationship between PICH and SCCPCH
PICH frame containing paging indicator
The end of PICH radio frame is 7680 chips earlier than associated S-CCPCH frame.
After the UE receives the information, it calculates the paging occation, PI, and p.
The IMSI of a UE is 448835805669362, so the related parameters are calculated as below:
l
q = (14 + [((18 * (242 + [242 / 8] + [242 / 64] + [242 / 512])) mod 144) * 0.25]) mod 36
= 27
From previous data, each frame of the cell PICH carries 36 PIs. Each PI consists of 8 bits
(288/36). The UE must monitor the bit216 (27x 8) to bit223 of each PICH radio frame. If
2008-11-17
these 8 bits changes to 1, the UE knows that it might be paged, so it receives paging message
on SCCPCH.
2008-11-17
The UE has two basic operation modes: idle mode and connected mode. When the power is
on, the UE is in idle mode. It is identified by non-access layer identity, such as IMSI, TMSI,
or P-TMSI. The UTRAN does not save the information of UE in idle mode. It pages
respectively the UE that powers on and camps on a cell, or pages all UE in idle mode under
an RNC simultaneously. After UE completes RRC connection setup, UE transits from idle
mode to the CELL_FACH or CELL_DCH state of connected mode. After the RRC
connection is released, the UE transits from connected mode to idle mode.
According to access layer, the access process is the process of UE transiting from idle mode
to connected mode. It includes:
l
Cell search
Random access
Once the UE is in connected mode, it can carry out the following non-access layer activities:
l
l
l
Location registration
Service application
Authentication
2008-11-17
If the UE has no information about RF channel of UTRA carrier, it scans all frequency
bands within UTRA band to find the proper cell to camp on in the selected PLMN. In
each carrier, the UE searches for the cell with strongest signals.
If the UE has the saved information about UTRA carrier and cell parameters (such as
primary scramble of cell) obtained from previously received measurement control
information, the UE tries to camp on the saved cell. If it fails to camp, it scans all
frequency bands within UTRA band to find the proper cell to camp on in the selected
PLMN.
After the UE locks a frequency, it completes cell search by timeslot synchronization, frame
synchronization, and scramble synchronization.
Trigger Time
The UE starts cell selection in the following situations:
2008-11-17
The UE powers on
When the UE fails to find a cell for normal camp for cell reselection according to the cell
list provided by measurement control system information (TS25.133)
PLMN Selection
The UE obtains the PCCPCH scramble according to 8.1.3 . The channel code (SF (=256,1))
of PCCPCH is known, and it is unique in the whole UTRAN. Therefore the UE can read the
information on the broadcast channel.
First, the UE obtains SFN from system information sent on BCH (PCCPCH). The first
domain of the message is SFNprime. Its value is the initial SFN of the transport block, with
its range (0, 2, 4, 64094). The rage of SFNprime is (02047) after PER coding. The BCH
TTI is 20ms. It includes two radio frames, so the step of SFNprime is 2.
The scheduling information is known; namely, SIB_POS = 0 and SIB_REP = 8. After the UE
obtains SFN, it can read MIB in the radio frame (SFN = 0, 8, 16).
After reading MIB, the UE judges according to PLMN identity in MIB whether the current
PLMN is the needed PLMN.
l
If yes, the UE searches for other SIBs according to the scheduling information of other
SIBs contained in MIB, and obtain their content.
Qqualmin
Qrxlevmin
Other parameters
After obtaining previous parameters, the UE judge with the criterion S whether the current
cell is suitable to camp on.
The criterion S is:
If Srxlev > 0 and Squal > 0, the cell is suitable for UE to camp on.
Wherein,
2008-11-17
Table 8-1 lists the parameters and their description in the criterion S.
Table 8-1 Parameters and their description in the criterion S
Parameter name
Parameter description
Squal
Srxlev
Qqualmeas
Qrxlevmeas
Qqualmin
Qrxlevmin
Pcompensation
UE_TXPWR_MAX_RACH
P_MAX
If the cell meets the criterion S, the UE judges the cell as a suitable cell. Therefore it camps
on the cell, reads other needed system information, and originates location registration.
If the cell does not meet the criterion S, the UE searches for the cell meeting the criterion S in
the neighbor cells of the cell in the following procedures.
Cell info
Others
In the CPICH info, the UE obtains primary scrambling code. The channel code of CPICH is
unique in the entire UTRAN. The UE can measure Qqualmeas and Qrxlevmeas (timeslot
synchronization and frame synchronization are needed) according to primary scrambling code
and reference time difference to cell.
2008-11-17
In the Cell Selection and Re-selection info for SIB11/12, the UE obtains the following
parameters of neighbor cell:
l
Qqualmin
Qrxlevmin
After this, the UE can calculate the Squal and Srxlev of neighbor cells, and judges whether
the neighbor cell meets the previous criterion.
Cell info
Others
By previous information, the UE can calculate the Squal and Srxlev of neighbor cells, and
judges whether the neighbor cell meets the previous criterion.
If the UE finds that no cell meets the criterion S, it judges that there is no coverage. Therefore
it continues PLMN selection and reselection.
In addition, the UE in idle mode randomly monitors the signal quality of the serving cell and
neighbor cells to select a best cell for service. This is cell reselection.
If the UE finds a neighbor cell that meets the criterion S, the UE camps on the cell and reads
other needed system information. After this, the UE starts random access and originates
location registration.
Carry out cell measurement and provide data for evaluating cell reselection
The following paragraphs introduce the trigger time and measurement rule for cell reselection,
as well as the principle for evaluating cell reselection.
Trigger Time
UE reselects a cell in the following conditions:
l
2008-11-17
Idle mode time trigger (measured quality value of the serving cell is lower than that of
intra-frequency measurement threshold).
In idle mode, the serving cell in continuous Nserv DRX cannot meet the criterion S
(however the system information is configured).
Measurement Rules
The measurement rules when HCS is not used:
If the cell broadcast system information indicates not to use HCS, the UE decides to start the
corresponding measurement. In the CPICH Ec/Io measurement state, the Squal corresponds to
Sx. In CPICH RSCP measurement state, the Srxlev corresponds to Sx.
l
Intra-frequency measurement
If the system information does not provide Sintrasearch, the UE always starts
intra-frequency.
Inter-frequency measurement
If the system information does not provide Sintrasearch, the UE always starts
inter-frequency.
Inter-RAT measurement
2008-11-17
If Srxlevs <= SsearchHCS or if FDD and Sx <= Sintersearch, the UE measures all
inter-frequency and intra-frequency cells.
Else the UE measures on all intra-frequency and inter-frequency cells, which have
higher HCS priority level than the serving cell unless measurement rules for
fast-moving UEs are triggered.
Else, the UE measure on all intra-frequency and inter-frequency cells, which have
equal or higher HCS priority level than the serving cell unless measurement rules for
fast-moving UEs are triggered.
If Srxlevs <= SHCS,RATm or if FDD and Squal <= SSearchRATm, then the UE shall measure
on all inter-RATm cells.
Else if Sx > Slimit,SearchRATm, the UE need not measure neighbor cells in RAT "m"
Else the UE shall measure on all neighbor cells in RAT "m", which have equal or
higher HCS priority level than the serving cell unless measurement rules for
fast-moving UEs are triggered.
Measure the neighbor cells in RAT "m", which have an equal or lower HCS priority
than the serving cell
Prioritize re-selection of neighbor cells in RAT "m" on lower HCS priority level
before neighbor cells in RAT "m" on same HCS priority level.
When the number of cell reselections during time interval TCRmax no longer exceeds NCR, UE
shall
l
The following cell re-selection criteria are used for intra-frequency cells, inter-frequency cells
and inter-RAT cells:
The quality level threshold criterion H for hierarchical cell structures is used to determine
whether prioritized ranking according to hierarchical cell re-selection rules shall apply, and is
defined by:
Hs = Qmeas_LEV,s - Qhcss
Hn = Qmeas_LEV,n - Qhcsn TOn * Ln
If it is indicated in system information that HCS is not used, the quality level threshold
criterion H is not applied.
The cell-ranking criterion R is defined by:
2008-11-17
Rs = Qmap,s + Qhysts
Rn = Qmap,n - Qoffsets,n - TOn * (1 Ln)
Where:
if HCS_PRIOn = HCS_PRIOs
if HCS_PRIOn <> HCS_PRIOs
W(x) = 0
W(x) = 1
for x < 0
for x >= 0
2008-11-17
Parameter description
Sn
Qmap,n
Qmap,s
Qmeas_LEV
The UE shall perform ranking of all cells that fulfill the S criterion among:
l
All cells with highest HCS_PRIO meets criterion H, namely, the cells with H > = 0, Note
that this rule is not valid when UE high-mobility is detected.
All cells, not considering HCS priority levels, if no cell fulfil the criterion H >= 0. This
case is also valid when it is indicated in system information that HCS is not used, that is
when serving cell does not belong to a hierarchical cell structure.
In all cases, the UE shall reselect the new cell, only if the following conditions are met:
l
The new cell is better ranked than the serving cell during a time interval Treselection.
M than 1 second has elapsed since the UE camped on the current serving cell.
Table 8-3 Broadcast parameters and description of cell reselection in system information
2008-11-17
Parameter name
Parameter description
Qoffset1s,n
This specifies the offset between the two cells. It is used for TDD and
GSM cells and for FDD cells in case the quality measure for cell
selection and re-selection is set to CPICH RSCP.
Qoffset2s,n
This specifies the offset between the two cells. It is used for FDD
cells in case the quality measure for cell selection and re-selection is
set to CPICH Ec/No.
Qhyst1s
This specifies the hysteresis value (Qhyst). It is used for TDD and
GSM cells and for FDD cells in case the quality measure for cell
selection and re-selection is set to CPICH RSCP.
Parameter description
Qhyst2
This specifies the hysteresis value (Qhyst). It is used for FDD cells if
the quality measure for cell selection and re-selection is set to CPICH
Ec/No.
HCS_PRIOs,
HCS_PRIO
This specifies the HCS priority level (0-7) for serving cell and
neighbor cells.
Qhcss, Qhcsn
Qqualmin
This specifies the minimum required quality level in the cell in dB. It
is not applicable for TDD cells or GSM cells.
Qrxlevmin
PENALTY_TIME
2008-11-17
TEMPORARY_O
FFSET1n
This specifies the offset applied to the H and R criteria for a neighbor
cell for the duration of PENALTY_TIMEn. It is used for TDD and
GSM cells and for FDD cells in case the quality measure for cell
selection and re-selection is set to CPICH RSCP.
TEMPORARY_O
FFSET2n
This specifies the offset applied to the H and R criteria for a neighbor
cell for the duration of PENALTY_TIMEn. It is used for FDD cells in
case the quality measure for cell selection and re-selection is set to
CPICH Ec/No.
TCRmax
NCR
TCRmaxHyst
This specifies the additional time period before the UE can revert to
low-mobility measurements.
Treselections
SsearchHCS
SsearchRAT 1 SsearchRAT k
This specifies the RAT specific threshold in the serving cell used in
the inter-RAT measurement rules.
SHCS,RATm
Sintrasearch
This specifies the threshold (in dB) for intra frequency measurements
and for the HCS measurement rules.
Sintersearch
This specifies the threshold (in dB) for intra frequency measurements
and for the HCS measurement rules.
Parameter name
Parameter description
Slimit,SearchRATm
3GPP 25.211 defines that the timing relationship of frame structure and physical layer of
RACh, PRACH, and access channel.
3GPP 25.213 defines the modulation of preamble on access channel and the spreading
modulation of message part (data and control). It also defines the preamble, scramble, and
spreading code.
3GPP 25.213 defines the access process.
2008-11-17
Figure 8-1 shows the timing information and acquisition indicator of access timeslot, and the
interval between access timeslots and timeslot number. Whether the information of an access
timeslot in the serving cell is available is decided by upper-layer signaling.
Figure 8-1 Number and interval of access timeslots of RACH
radio frame: 10 ms
radio frame: 10 ms
5120 chips
Access slot
#0
#1
#2
#3
#4
#5
#6
#7
#8
#9
#10
#11
#12
#13
#14
The subscriber can originate random access transmission at the beginning of each access
timeslot. Figure 8-2 shows the structure of random access transmission. The structure includes
message part of 10ms or 20ms.
Figure 8-2 Structure of random access transmission
Preamble
Preamble
Preamble
4096 chips
Preamble
Message part
10 ms (one radio frame)
Preamble
Preamble
4096 chips
Message part
20 ms (two radio frames)
The preamble length of random access is 4096 chips. It includes a SIGNATURE. The
SIGNATURE is 16 chips and is repeated 256 times. In total there are 16 different
SIGNATURE.
The 10 ms message part radio frame is split into 15 slots, each of length Tslot = 2560 chips.
Each slot consists of two parts, a data part to which the RACH transport channel is mapped
and a control part that carries Layer 1 control information. The data and control parts are
transmitted in parallel. A 10 ms message part consists of one message part radio frame, while
a 20 ms message part consists of two consecutive 10 ms message part radio frames. The
message part length is equal to the Transmission Time Interval of the RACH Transport
channel in use. This TTI length is configured by higher layers.
2008-11-17
The data part consists of 10*2k bits, where k=0,1,2,3. This corresponds to a spreading factor
of 256, 128, 64, and 32 respectively for the message data part.
The control part consists of 8 known pilot bits to support channel estimation for coherent
detection and 2 TFCI bits. This corresponds to a spreading factor of 256 for the message
control part. The pilot bit pattern is described in 3GPP TS 25.211 table 8. The total number of
TFCI bits in the random-access message is 15*2 = 30. The TFCI of a radio frame indicates
the transport format of the RACH transport channel mapped to the simultaneously transmitted
message part radio frame. In case of a 20 ms PRACH message part, the TFCI is repeated in
the second radio frame.
The downlink AICH is divided into downlink access slots, each access slot is of length 5120
chips. The downlink access slots are time aligned with the P-CCPCH.
The uplink PRACH is divided into uplink access slots, each access slot is of length 5120
chips. Uplink access slot number n is transmitted from the UE p-a chips prior to the reception
of downlink access slot number n, n = 0, 1, , 14.
Transmission of downlink acquisition indicators may only start at the beginning of a downlink
access slot. Similarly, transmission of uplink RACH preambles and RACH message parts may
only start at the beginning of an uplink access slot.
Figure 8-3 shows the PRACH/AICH timing relation.
Figure 8-3 Timing relation between PRACH and AICH as seen at the UE
The preamble-to-preamble distance p-p shall be larger than or equal to the minimum
preamble-to-preamble distance
p-p,min, i.e. p-p p-p,min.
In addition to p-p,min, the preamble-to-AI distance p-a and preamble-to-message distance p-m
are defined as follows:
l
2008-11-17
Scramble of preamble
Value of AICH_Transmission_Timing (0 or 1)
The signature set and RACH subchannel set assigned for each ASC (access subchannel)
number
Preamble_Initial_Power
TFS parameter. It includes the power offset corresponding to each transmission format,
data part and control part of random access message.
Note that the upper-layer might update previous parameters before the UE starts physical
random access process.
In addition, before the UE starts physical random access process, the layer 1 shall receive the
following information from MAC layer:
l
2008-11-17
1.
Decide available RACH access subchannel set and available uplink access timeslot set of
next complete access timeslot set (SFN mod 2 = 0 and SFN mod 2 = 1, the former is
called the access timeslot set 1 while the latter is called the access timeslot set 2). Select
an uplink access timeslot randomly. The rule for random selection is to select by
equivalent probability. If there is no available uplink access timeslot in the current access
timeslot set, select one from next access timeslot set.
2.
According to provided ASC, select randomly the signature used by access in the
signature set.
3.
4.
of
PRACH
preamble
retransmission
counters
to
5.
If the parameter Commanded Preamble Power exceeds the maximum allowed value, set
the transmit power of preamble to maximum allowed transmit power. If it is lower than
the needed minimum value (prescribed by 3GPP TS 25.101), set the transmit power of
preamble to the current value to be calculated. This value might be larger or smaller than,
equal to Commanded Preamble Power. Otherwise, set the transmit power of preamble to
Commanded Preamble Power. Send the preamble with the selected uplink access
timeslot, signature, and preamble transmit power.
6.
The UE waits for confirmation signals corresponding to the used signature from NodeB.
If the UE fails not detect the +1 or 1 acquisition indicator in the downlink access
timeslot which has the same number of uplink access timeslot used by transit preamble
code, it randomly select the next available access timeslot. According to power ramp
step, it increases the Command Preamble Power, deduct the preamble code reset counter
by 1. If the Command Preamble Power is 6 dB larger than the maximum allowed power,
the UE report layer 1 state ("No ack on AICH") to MAC layer, and then quits the
physical random access process. If the retransmission counter value is larger than 0,
repeat the sixth step; otherwise, the UE reports layer 1 state ("No ack on AICH") to
MAC layer, and then quits physical random access process.
7.
8.
If the UE receives a +1 acquisition indicator, it sends the random access message part
after 3 or 4 uplink access timeslots before last transmission according to the value of
AICH_Transmission_Timing. The power for sending control part of random access
message is Pp-m higher than the power for sending preamble the last time. For the
transmit power of data part, see protocols.
According to previous operation flow for random access, when the UE accesses the network,
it first sends preamble, and then waits for the confirmation signals from NodeB in the fixed
downlink access timeslot. If the NodeB detects a preamble signal transmitted by UE, the
NodeB responds an acquisition indicator signal on downlink AICH. After sending preamble,
it detects acquisition indicator (AI) signal in the fixed downlink access timeslot. If the UE is
permitted, it keeps sending message part and completes a physical random access. If the UE
fails to receive AI, it keeps repeating the handshaking process of "sending preamble to
detecting AI" for preset times until permitted. Then it sends the message part and completes a
physical random access process. If the UE receives the signal indicating that access is
prohibited, it quits this random access process and reports the state. The message part of
random access carries the sign information of UE, the type of applicated service, and so on.
2008-11-17
Table 8-4 describes the relationship among the access subchannel, access timeslot, and SFN.
Table 8-4 Relationship among the access subchannel, access timeslot, and SFN
SFN modulo 8 of
corresponding
P-CCPCH frame
Sub-channel number
0
12
13
14
2
3
10
11
5
6
12
13
14
10
10
11
10
11
7
8
11
12
13
14
10
11
12
13
14
Figure 8-4 shows the definition of access timeslot set (taking the uplink and downlink access
timeslot fixed difference p-a = 7680 chips as example).
Figure 8-4 Definition of access timeslot set (taking the uplink and downlink access timeslot fixed
difference p-a 7680 chips as example)
AICH access
slots
SFN mod 2 = 0
p-a
#0
PRACH
access slots
#0
#1
#2
#1
#3
#2
#4
#3
#5
#4
#6
SFN mod 2 = 1
#5
#7
#6
#8
#7
#9
#8
#9
#10
#11
#11
#12
#13
#12
#13
#14
#14
10 ms
2008-11-17
#10
10 ms
The network checks the UE whether the UE is allowed to access the network.
The UE can calculate the integrity key (IK) related to network side.
Compared with the authentication flow of GSM networks, the authentication flow of 3G
networks adds consistency check and the authentication of network by UE. These features
further enhance the security of 3G networks.
Before the network side originates authentication, if the VLR has not authenticated the
authentication quintuple parameters, the network side first originates the process to HLR for
obtaining authentication set, and then waits for response of authentication quintuple
parameters. The authentication quintuple parameters include:
l
RAND
XRES
AUTN
CK
IK
When detecting that the authentication quintuple parameters are present, the network side
sends the authentication request message. This message contains the RAND and AUTN of
authentication quintuple parameters. After the UE receives the message, the USIM
authenticates AUTN. Namely, the UE authenticates the network. If the authentication passes,
the USIM calculates CK, IK, and signature XRES. If the USIM judges that the authentication
succeeds, the UE responds XRES in authentication response message.
2008-11-17
After the network side receives the authentication response message, it compares the XRES of
the message with the XRES of authentication quintuple parameters saved in VLR database.
This confirms whether the authentication succeeds. If yes, the flow proceeds. If no, an
abnormal processing flow starts. The flow releases the connection between network side and
UEs, and releases the occupied network resources and radio resources.
After successful authentication, the UE saves CK and IK to USIM card.
Sometimes, after the UE receives the authentication request message, it reports that the
authentication fails. Typical causes of authentication failure include:
l
When the UE authenticates the network, it checks the AUTN in authentication request
message sent by network side. If the MAC is faulty, the UE sends the authentication
failure message with the cause MAC Failure, as shown in Figure 9-2.
2008-11-17
When UE detects that the SQN of AUTN message is faulty, the authentication fails with
the cause Synch failure.
Now the VLR removes all authentication quintuple parameters and starts the process of
synchronization with HLR. This process requires HLR to reuse authentication quintuple
parameters and to start authentication process.
2008-11-17
10
Appendix 4: Description of
Access-related Parameters
Antenna azimuth
Antenna beamwidth
Antenna gain
To solve access problems caused by coverage, engineers consider adjusting these engineering
parameters. For example, constructing new sites in blind areas, increase the antenna gain of
serving cells, or decrease the down tilt of antennas in neighbor cells. Avoid the impact on
original coverage area by adjustment.
If it is set over small, the UE at the cell edge cannot correctly receive the signaling
carried by FACH. This impacts the downlink CCH coverage, and consequently impacts
the cell coverage.
If it is set over large, other channels will be impacted, downlink transmit power will be
used, and the cell capacity is impacted.
The default power of FACH is 1 dB, and it is based on that the CPICH Ec/Io of coverage cell
edge is 12 dB. If the field coverage is worse, raise the FACH power according to CPICH
Ec/Io.
2008-11-17
If it is set over small, the UE at the cell edge cannot correctly receive paging messages.
Therefore the paging delay increases, paging success rate drops, and access success rate
drops.
If it is set over large, power consumption increases and downlink interference increases.
If it is set over small, the UE at the cell edge cannot correctly receive paging indicator
information. Therefore, the paging delay increases, or mal-operation of reading PCH
data is probably performed, the UE consumes more power, the downlink CCH coverage
is affected, and finally the cell coverage is affected.
Because the PICH keeps sending paging indicator information, if the transmit power of
PICH is set over large, the PICH will interfere with other channels, consume downlink
transmit power, and affects cell capacity. So increasing transmit power of PICH is not
recommended. To increase the coverage by PICH signals, decrease NP to 18. Decreasing
NP will lead to decrement of paging capacity at UU interface. At the early stage of
network construction, setting NP to 18 keeps an adequate paging capacity and it is a
typical configuration in the industry.
2008-11-17
The previous parameters affect one another. Upon occurrence of PRACH problems, adjust the
retransmission times of preamble. The default configuration is 8. It is recommended to set
retransmission times of preamble to 20 to avoid PRACH problems.
2008-11-17
11
The HSUPA load control algorithm described in this chapter is based on UMTS 6.0.
Number of subscribers
Power resources
2008-11-17
Physical port: It is equivalent to a resource group. That is, different physical ports cannot
share lub resources.
Each path can belong to only one physical port, while several paths can share the same
physical port.
Physical ports in an ATM network cannot share lub resources with those in an IP
network.
To make full use of physical transmission resources of the lub interface, a path of any
type can be configured to the total bandwidth of the physical port where the path is.
For the DCH service, the consumption of lub resources equals to service bandwidth
multiplied by the configured activation factor.
For the HSPA service, the consumption of lub resources equals to GBR of the service
multiplied by the configured activation factor.
A path of any type can be configured to the total bandwidth of the physical port where
the path is. As a result, the sum of bandwidth of all paths on the same physical port
might exceed the physical bandwidth. For this reason, two levels of admission are
needed: Path-level admission and physical port level admission.
The lub congestion control must apply to both service congestion and bearer congestion.
As for admission, just consider whether lub resources for the related service are
adequate.
The primary path of the service is admitted whenever possible. If this admission fails, try
admission of the secondary path.
The admission requested by the handover has the highest priority, followed by that of new
services and that of reconfiguration in the case of rate increase. The admission threshold is set
to the reserved bandwidth of the lub interface.
l
In the case of handover, the admission uses 100% of the bandwidth by default. The
reserved bandwidth is 0 kbps. No new parameter is needed.
New services are configured on the basis of total bandwidth minus the reserved
bandwidth for handover.
The admission of a reconfiguration request in the case of rate increase is based on the
congestion threshold.
The preceding admission strategy of lub resources shows that the setting of activation factor
of the BE service greatly impact the number of admitted subscribers. If the activation factor is
set to 1.0, the transmission quality of the subscriber can be guaranteed, but the bandwidth of
lub interface is greatly wasted. If this parameter is set to a small value, the subscriber suffers
packet loss and the bandwidth utilization of the lub interface decreases.
Suppose the following problem occurs in the test: The bandwidth of the lub interface is
adequate to bear a 384 Kbps service. If two 384 kbps PS BE services access the lub interface
after the activation factor is modified, the traffic rate of both services can reach only 64 kbps
when the data source rate is sufficient. The efficient bandwidth usage is only 128 kbps. In this
case, the bandwidth of the lub interface is greatly wasted.
This problem occurs because the RLC retransmits the PDU due to random packet loss in the
lub transmission. In this case, the delay of transmission of the TCP data packet increases, the
TCP flow control is enabled, and the rate decreases. The Overbooking function of the lub
resources is adopted to improve bandwidth utilization of the lub interface. To be specific, this
function improves the bandwidth utilization by setting the activation factor and avoiding
packet loss in the transmission layer.
2008-11-17
Direction
Type
Number of Consumed
Credits
12.2kbps AMR
DL
Local Cell
Node B
Local Cell
Node B
Local Cell
Node B
Local Cell
Node B
Local Cell
Node B
Local Cell
1.5
1.5
Node B
1.5
UL
64kbps VP
DL
UL
32kbps PS
DL
UL
2008-11-17
Service
Direction
Type
Number of Consumed
Credits
64kbps PS
DL
Local Cell
Node B
Local Cell
Node B
Local Cell
Node B
Local Cell
Node B
Local Cell
Node B
Local Cell
10
10
Node B
10
UL
128kbps PS
DL
UL
384kbps PS
DL
UL
The admission decision should be made for the Local Cell, the Local Cell Group, and the
NodeB at the same time. The admission is accepted only if all these admissions succeed. The
admission threshold varies with admission requests.
2008-11-17
For handover, the admission is accepted only if the CE resources are allocated
successfully.
For a new service, the admission is rejected if the SF of the minimum codes supported
by the rest CE resources after the subscriber accesses exceeds the threshold of handover
reserved SF of the downlink CE resources. If the SF does not exceed the threshold, the
admission succeeds.
In the case of rate increase, the admission is rejected if the SF of the minimum codes
supported by the rest CE resources after the subscriber accesses exceeds the threshold of
congestion reserved SF of the downlink CE resources. If the SF does not exceed the
threshold, the admission succeeds.
11.1.5 LDR
Different types of channels choose LDR actions as listed in the following table:
LDR Action
Type of Channel
DCH
HSDPA
HSUPA
BE Rate Reduction
Inter-RAT Handover in CS
Domain
Inter-RAT Handover in PS
Domain
Iu QoS Negotiation
Code reshuffling
FACH
(MBMS)
LDR actions supported by the HSUPA subscribers include inter-frequency load handover and
inter-RAT handover in the PS domain. If primary congestion occurs in uplink of a HSUPA
cell, the HSUPA subscribers can be selected as candidate subscribers together with the DCH
subscribers when the inter-frequency load handover or inter-RAT handover in the PS domain
is executed. The specific principles for subscriber selection remain unchanged.
If the HSUPA cells adopt the ENU based admission, the uplink LDR is also based on the ENU.
2008-11-17
11.1.6 OLC
The HSUPA subscribers support only one OLC action: subscriber release. If overload
congestion occurs in uplink of a HSUPA cell, the HSUPA subscribers, together with the DCH
subscribers, are sorted by priority when the subscriber release is executed. Several subscribers
with the lowest priority are chosen for OLC processing.
MAXHSUPAUSERNUM
This parameter refers to the maximum number of subscribers supported by the HSUPA
channel of a cell. In the case of admission of a HSUPA subscriber, the number of subscribers
is check first. If the number of current accessed HSUPA subscribers is smaller than the value
of this parameter, the admission proceeds to the next step. If the number of current HSUPA
subscribers is larger than the value of this parameter, the admission is rejected. If the value of
this parameter is too high, the product is not able to support the accessed subscribers. If the
value of this parameter is too small, the HSUPA subscribers are rejected, though the related
resources are available.
DLHSUPARSVDFACTOR
This parameter reserves resources for the HSUPA downlink control channel. The larger the
value of this parameter is, the more resources are reserved for the HSUPA control channel.
This might cause waste of resources. If the value of this parameter is too small, the QoS of the
HSUPA subscribers is impacted in the case of resource shortage.
UlConvAMRThd
This parameter refers to the uplink threshold of the AMR voice service in conversational
services. It is used for uplink admission of AMR voice subscribers in conversational services.
The uplink admission control algorithm forecasts the load factor of the system after a new call
is accessed based on the load factor of the current system and the service features of the new
call. The algorithm then uses the sum of the forecasted load factor and the uplink load factor
on the common channel as the new forecasted load factor. At last, the algorithm compares the
forecasted load factor with the load factor threshold. If the forecasted load factor does not
exceed the load factor threshold, the call is accepted. If the forecasted load factor exceeds the
threshold, the call is rejected.
The uplink load threshold includes this parameter, UlConvNonAMRThd, UlOtherThd, and
ULHOThd. The relationship between these four parameters can be used to limit the ratio of
sessions to other services in the cell and to ensure priority of access of handover subscribers
and conversational services.
If the value of this parameter is too large, excessive load might exist over the system after
admission of the conversational service. In this case, congestions occur in the system. If the
2008-11-17
value of this parameter is too small, subscribers might be rejected though the related resources
are available.
Pay attention to the network planning when setting this parameter, UlConvNonAMRThd,
UlOtherThd, and ULHOThd. If the value of this parameter is too large, the target coverage
is impacted. If the value of this parameter is too small, the target capacity cannot be ensured.
UlConvNonAMRThd
This parameter refers to the uplink threshold of non-AMR voice service in conversational
services. It is used for uplink admission of non-AMR voice subscribers in conversational
services.
The uplink admission control algorithm forecasts the load factor of the system after a new call
is accessed based on the load factor of the current system and the service features of the new
call. The algorithm then uses the sum of the forecasted load factor and the uplink load factor
on the common channel as the new forecasted load factor. At last, the algorithm compares the
forecasted load factor with the load factor threshold. If the forecasted load factor does not
exceed the load factor threshold, the call is accepted. If the forecasted load factor exceeds the
threshold, the call is rejected.
The uplink load threshold includes this parameter, UlConvAMRThd, UlOtherThd, and
ULHOThd. The relationship between these four parameters can be used to limit the ratio of
sessions to other services in the cell and to ensure priority of access of handover subscribers
and conversational services.
If the value of this parameter is too large, excessive load might exist over the system after
admission of the service. In this case, congestions occur in the system. If the value of this
parameter is too small, subscribers might be rejected though the related resources are
available.
Pay attention to the network planning when setting this parameter, UlConvAMRThd,
UlOtherThd, and ULHOThd. If the value of this parameter is too large, the target coverage
is impacted. If the value of this parameter is too small, the target capacity cannot be ensured.
UlOtherThd
This parameter refers to the uplink threshold of services except the conversational services.
This parameter is used for uplink admission of other services.
If the value of this parameter is too large, excessive load might exist over the system after
admission of the service. In this case, congestions occur in the system. If the value of this
parameter is too small, subscribers might be rejected though the related resources are
available.
Pay attention to the network planning when setting this parameter, UlConvAMRThd,
UlOtherThd, and ULHOThd. If the value of this parameter is too large, the target coverage
is impacted. If the value of this parameter is too small, the target capacity cannot be ensured.
ULHOThd
This parameter refers to uplink threshold of handover for uplink admission of handover
subscribers. This parameter applies only to uplink inter-frequency handover.
The uplink admission control algorithm forecasts the load factor of the system after a new call
is accessed based on the load factor of the current system and the service features of the new
call. The algorithm then uses the sum of the forecasted load factor and the uplink load factor
2008-11-17
on the common channel as the new forecasted load factor. At last, the algorithm compares the
forecasted load factor with the load factor threshold. If the forecasted load factor does not
exceed the load factor threshold, the call is accepted. If the forecasted load factor exceeds the
threshold, the call is rejected.
The uplink load threshold includes this parameter, UlConvAMRThd, UlConvNonAMRThd,
and UlOtherThd. The relationship between these four parameters can be used to limit the
ratio of sessions to other services in the cell and to ensure priority of access of handover
subscribers and conversational services.
The value of this parameter should be lower than the uplink OLC trigger threshold of the
intelligent load control.
This parameter is used to reserve resources for handover and ensure quality of the handover.
The value of this parameter must exceed the values of UlConvAMRThd and
UlConvNonAMRThd. This parameter applies only to inter-frequency handover.
If the value of this parameter is too large, excessive load might exist over the system after
admission of the service. In this case, congestions occur in the system. If the value of this
parameter is too small, subscribers might be rejected though the related resources are
available. Pay attention to UlConvAMRThd, UlConvNonAMRThd, and UlOtherThd when
setting this parameter.
2008-11-17
List of Reference
1.
2.
3.
4.
5.
6.
7.
RAN Radio Performance Dept.. WCDMA RAN Radio Performance Call Access Delay
Optimization Test Report. 2004-02
8.
RAN Radio Performance Dept.. W-RAN Traffic Statistics analysis and Problem
Location Guidance-20050926-A-1.0.doc. 2005-09
9.
RAN Radio Performance Dept.. UMTS Radio Network KPI baseline (V3.3). 2006-01
10. RRNP. WCDMA RNO Network Event Definition Baseline 1.0. 2005-11
2008-11-17