Upload
vickyparasar163
View
57
Download
0
Embed Size (px)
DESCRIPTION
a
Citation preview
URA_PCH
Deployment recommendations and results
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 2
Content
› Network Data› Introduction› Feature characteristics› Dimensioning› Configuration› Monitoring
– URA FNI report– Report for the rest of RNCs
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 3
Content
› Network Data› Introduction› Feature characteristics› Dimensioning› Configuration› Monitoring
– URA FNI report– Report for the rest of RNCs
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 4
Network data
RNC LAC # of cells
RNC1 8 832
RNC2T 11 538
RNC3 7 848
RNC4 9 719
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 5
Content
› Network Data› Introduction› Feature characteristics› Dimensioning› Configuration› Monitoring
– URA FNI report– Report for the rest of RNCs
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 6
What is URA-PCH?
› Utran Registration Area – Paging CHannel
› New state between CELL_FACH and IDLE.
› Only applies to Packet Interactive RABs.
› PDR Connected state where RAB is established but user activity is zero
› UE does not use any radio resources. Just listens to the paging channel.
› Optional Feature - Customer requires license for this feature
CELL_FACH
URA_PCH
IDLE
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 7
What is URA-PCH?
› Switch to URA_PCH @ inactivity on PS RAB for inactivityTimer sec (ChannelSwitching MO).
CELL_FACH
URA_PCH
IDLE
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 8
What is URA-PCH?
› Switch to URA_PCH @ inactivity on PS RAB for inactivityTimer sec (ChannelSwitching MO).
› Switch from URA_PCH to CELL_FACH if activity resumes.
CELL_FACH
URA_PCH
IDLE
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 9
What is URA-PCH?
› Switch to URA_PCH @ inactivity on PS RAB for inactivityTimer sec (ChannelSwitching MO).
› Switch from URA_PCH to CELL_FACH if activity resumes.
› Switch from URA_PCH to IDLE if inactivity persists for further inactivityTimerPch mins (ChannelSwitching MO). More information on timers is in the Configuration part of this presentation
CELL_FACH
URA_PCH
IDLE
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 10
Content
› Network Data› Introduction› Feature characteristics› Dimensioning› Configuration› Monitoring
– URA FNI report– Report for the rest of RNCs
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 11
Feature characteristics
› Can have 1URA/cell (max 2304/RNC)
› All cells in RNC can share the same URA
› One cell can have up to 4 distinct URAs
› URA over Iur isn’t supported
› URA won’t cross the RNC border
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 12
URA_PCH state
› In URA_PCH the UE keeps its reserved User Plane IP-address and a signaling connection in the CN, but no radio resources.
› The benefits with the feature are twofold: – Minimized service reactivation time for UEs
using a PS interactive RAB; and,– Less signaling and power consumption in
the UE as compared to CELL_FACH.
› The state transitions to and from URA_PCH are illustrated on the diagram.
› As can be seen in the diagram, the URA_PCH state is reachable only by channel switching from CELL_FACH.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 13
HSPA
FACH
IDLE
URA
Much less signaling from URA than from Idle
URA -> FACH› Only 3 signaling
messages over Uu
FACH -> HSPA› Around 12 signaling
messages over Uu and Iub
Idle -> HSPA› Around 30 signaling
messages over Uu, Iub and Iu
signaling improvements with URA
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 14
Content
› Network Data› Introduction› Feature characteristics› Dimensioning› Configuration› Monitoring
– URA FNI report– Report for the rest of RNCs
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 15
Technical BackgroundPaging Strategy› The Paging Strategy is the way of minimizing the paging failure rate whilst not loading the
network with too many pages. › The paging strategy is implemented via paging parameters in MSC, SGSN and RNC.
› CN CS initiated paging– The paging strategy is implemented through MSC parameters.– The choice of paging strategy might be different for pooled and non-pooled MSC
solutions
› CN PS initiated paging– The timers and parameters in SGSN is the basis for the CN PS paging strategy.
› UTRAN initiates pages in the following cases:– When a UE in state URA_PCH then RNC initiates a channel switch to CELL_FACH
because it has data to send. – When a UE in state URA_PCH change state to IDLE due to expiry of the timer
inactivityTimerPch.– When System Information has been modified. The PICH is then set to ensure all UEs
read the PCH. › The System information needs to be broadcasted after an RNC restart and after
parameter changes.– The UTRAN initiated paging procedure is time supervised
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 16
Technical BackgroundTime Supervision (UTRAN Initiated Paging Procedure)
› The RNC always repeats each paging message noOfPagingRecordTransm times, regardless of the response and regardless if congestion occurs.
› The default value of noOfPagingRecordTransm is 2. Hence, the paging message is re-transmitted twice.
› If there is no room in the paging message the RNC keeps a paging queue of five paging records per cell
› If the paging queue is full the next incoming paging record is discarded.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 17
Technical backgroundPaging structure
› Paging messages are mapped onto radio channels, and the records are coded into Paging Message Type 1 or Paging Message Type 2.
› Paging to UEs in IDLE and URA_PCH state is performed with Paging Message Type 1.
› As 3GPP standard (25.993, 34.108), the maximum payload size of SRB for PCCH (Paging Control Channel) is 240 bits.
› As a result, for each paging occasion, 240 bits of information can be handled.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 18
Technical backgroundPaging structure› Depending on the UE identity used (IMSI, TMSI, P-TMSI or U-RNTI), the
number of paging records per message can vary. The table below defines the UE identities and its payload size.
UE Identity Payload Size (bits)
IMSI 79
TMSI 47
P-TMSI 47
U-RNTI 47
240 bits
› As a result, the number of paging records per message could vary depending on the UE identity used. Typically 3 to 5 paging records.
IMSI IMSI IMSI IMSI IMSI
T/P
/U
T/P
/U
IMSI
T/P
/U
T/P
/U
T/P
/U
T/P
/U
T/P
/U
T/P
/U
T/P
/U
T/P
/U
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 19
Technical backgroundDiscontinuous Reception
› Discontinuous reception (DRX) makes the UE (either in idle mode or in URA_PCH mode listen to the PICH only at certain predefined times.
› The setting of DRX cycle parameters will determine the time period between consecutive paging instances from RNC to a certain UE.
› The DRX cycle length can be set different for CN CS, CN PS and UTRAN initiated pages.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 20
LA RA URAConfiguration rules
› There are restrictions in an RNC. The maximum number of LAs, RAs and URAs in an RNC is 47, 154 and 2304 respectively.
› LAs and RAs are identified by their Location Area Identification (LAI) and Routing Area Identification (RAI).
› An LAI is defined in the MSC up to a maximum of 65534.› LAs, and the RAI consist of 8 bits, meaning maximum 256 RAs per LA.
› A cell can belong to up to 4 URAs. But from the RNC perspective a UE in state URA_PCH can only have one valid URA. If a UE is in a cell belonging to several URAs the RNC will assign one of them.
› When the UE in URA_PCH passes an RNC border and initiates a URA update, the RNC will answer with a RRC Connection Release message, and the UE is switched to IDLE. If LA/RA is changed during the connected time, an LA- and/or RA update is done.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 21
LA/RA/URA DimensioningOverview
› Dimensioning the number of cells in a LA is a trade-off between LA/RA/URA signaling load and Paging load.
› The corresponding considerations apply:–Large LA/RA/URA low signaling load but high paging ⇒
load.–Small LA/RA/URA high signaling load but low paging ⇒
load.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 22
LA/RA/URA DimensioningPaging Capacity
› Pages arriving at the RNC are Poisson distributed.› They are put into a queue with 3-5 paging records› If the queue is full, the page is discarded.
› The probability that a page arriving to the RNC is never sent out is approximated by the equation below.
Where
pcong is the probability that a paging record is rejected to be sent at its intended paging occasion (TTI)
m is the number of paging records per TTI in each cell
x is the number of paging records per paging message
N The largest value of x, that is N, can be 3, 4 or 5 (refer to slides 17-18) .
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 23
LA/RA/URA DimensioningPaging Capacity
› The probability of congestion on PCH for:X =3,4,5 paging records per paging message type1
› Usually, PCH congestion probability higher than 1-2% is considered poor
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 24
LA/RA/URA DimensioningPaging Capacity› Latest PLM info› PROBLEM DESCRIPTION
– It has been observed in some networks that the paging load has been increasing. This is especially due to the effects of Smartphones which can result in increased PS paging in the network even if the traffic volume has not increased.
– The intention of this PLM Info is to make markets aware of possible detrimental effects due to increased paging load.
– With default setting of Paging::noOfPagingRecordTransm (value = 2), it is recommended to start planning actions if the Qpaging_air_interface exceeds 100 paging records/s/cell.
– Immediate actions are needed if the paging load exceeds 130-150 paging records/s/cell.
› RISK– The RNC may enter "Recovery Mode" where it rejects traffic, and un-predictable
incidents may occur as the RNC enters an overload state. As a result, RNC performance may degrade significantly.
100 paging records/s/cell will be used in the dimensioning as the main criterium.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 25
LA/RA/URA Dimensioningmeasuring paging load
› The paging load in the RNC can be measured as follows:
Where:– = noOfPagingRecordTransm
– is the measurement time in sec
› The paging congestion in the RNC can be measured as follows:
CellsofNumbert
nAttemptTypepmNoPaging rep
__*
1Q _interfacepaging_air
%1001
rep
cong nAttemptTypepmNoPaging
jectedReanAttemptUtrpmNoPagingP
trepn
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 26
LA/RA/URA Dimensioningestimating paging load increase
› To take full advantage of URA, it is recommended to combine activation of URA Handling Feature with a reduction of InactivityTimer (FACH -> URA) to 5 sec (current setting 20 sec).
– Details on the full recommended parameter set will be provided in the CONFIGURATION part of the document.
› It is expected that both URA Handling activation and reduction of the timer will bring significant Paging Load increase.
› Paging Load increase will be estimated using experience from the other networks with similar changes.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 27
LA/RA/URA Dimensioningestimating paging load increase
Paging Attempts, Type1
2,000,000,000
2,250,000,000
2,500,000,000
2,750,000,000
3,000,000,000
3,250,000,000
3,500,000,000
3,750,000,000
4,000,000,000
4,250,000,000
4,500,000,000
4,750,000,000
5,000,000,000
Time, [days]
[#]
Paging Attempts, Type1
URA + InactivityTimer (30 ->5 sec)
› InactivityTimer:– Reference NW: 30 -> 5 sec– EMT: 20 -> 5 sec
› Contribution to Paging Load increase:
– Timer change 80%– URA activation 20%
› Based on data above, expected worst case Paging Load Increase in EMT NW is:
Paging_Load_Increase = 80%
100 - 120%
Reference NW
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 28
LA/RA/URA Dimensioningputting it all togetherModeling actual paging intencity using statistics counter data from the network:
› Statistical measurements show, that Paging Intensity in RNC1 is high to start with (>100 pages/s)› URA activation + timer change may bring Paging Intensity in RNC1 to an extreme level (>220 pages/s)› Even in case of homogeneous LA plan, an average Paging Intensity may exceed recommended level
of 100 pages/s› Actions need to be taken to mitigate high Paging Intensity
Variable RNC1 RNC2 RNC3 RNC4Network average(Even LA plan)
PS Paging Attempts, Type1, pmNoPagingType1Attempt , week 2 30,806,956,113 5,207,638,995 10,696,068,070 9,439,641,773 56,150,304,951# of congested pages, pmNoPagingAttemptUtranRejected 24,359 0 0 41 24,400
Paging.noOfPagingRecordTransm, # n rep 2 2 2 2 2
Average paging intensity, [pages] 61,613,912,226 10,415,277,990 21,392,136,140 18,879,283,546 112,300,609,902Measurement period, =1 week, [s] t 604,800 604,800 604,800 604,800 604,800Number of Cells, # 832 538 848 719 2,937
Measured paging intencity per cell and second, [pages/s] Q paging_air_interface 122 32 42 43 63Measured paging congestion, [%] P cong 0.00004% 0.00% 0.00% 0.0000002% 0.00002%Probability for paging congestion, [%] 0.17% 0.0001% 0.0005% 0.0006% 0.005%Predicted paging intencity per cell and second after URA activation, [pages/s] 221 58 75 78 114Probability for paging congestion after URA activation, [%] 2.55% 0.003% 0.01% 0.02% 0.12%
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 29
Current LA/RA plan
Problem
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 30
Options for LA/RA optimization
Option 1:Extend LA 11
Option 2:Split LA 8
Option3:Several RA/URA
Per LA 8
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 31
LA/RA optimizationfurther details
Fraction of Paging types
0.000%
10.000%
20.000%
30.000%
40.000%
50.000%
60.000%
70.000%
80.000%
90.000%
100.000%
07-01-13 08-01-13 09-01-13 10-01-13 11-01-13
Date
%
Fraction of Global Fraction of MSC Fraction of SGSN
› Data from EMT NW:– Main contributor to
Paging Intensity is PS Domain Paging (90%)
› Based on data above, RA/URA split will bring the main reduction in Paging Intensity.
› Thus, one approach could be to have several RA/URA for LAC 8– Can be used if LA split is difficult
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 32
LA/RA optimizationfurther details
Area split benefit
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
110%
1 2 3 4 5 6
Number of split areas
10% of Total Paging Volume
15% of Total Paging Volume
20% of Total Paging Volume
30% of Total Paging Volume
40% of Total Paging Volume
50% of Total Paging Volume
60% of Total Paging Volume
70% of Total Paging Volume
80% of Total Paging Volume
90% of Total Paging Volume
100% of Total Paging Volume
Having 3 RA/URA per LAC 8 will bring Paging Intensity down by 60% to an acceptable level of < 100 pages per second.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 33
LA/RA optimizationways forward
› Long-term solution– PS paging contributes to 90% of total Paging Intensity– Review paging settings in the Core Network– Re-design and split LA 8 into 3 RAa and URAs
› Can be combined with splitting LA 8 into more LAs as well, but the main benefit will come from RA/URA split
› Short term workaround– LA/RA Redesign is a tedious job. To speed-up URA roll-out for RNC1, the following
steps can be proposed:› Initially activate URA in RNC1 without changing InactivityTimer› Initially have several URAs for LAC 8 – URA is only defined within the WRAN, so
no configuration in the Core NW needed› As an emergency workaround use noOfPagingRecordTransm = 1. This will
reduce the Paging Intensity by 50%.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 34
Content
› Network Data› Introduction› Feature characteristics› Dimensioning› Configuration› Monitoring
– URA FNI report– Report for the rest of RNCs
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 35
URA-PCHWRAN pre-requisites
› UTRAN Registration Area Handling requires– FAJ 121 148 Interactive RAB for up to 384 kbps
› License exists in all EMT RNCs
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 36
URA-PCHActivation and configuration (1)
› Feature Name: PS Interactive URA-PCH › Feature Designation: RabCombination021› Key Id: CXC 403 0521 › FAJ Number: FAJ 121 407
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 37
URA-PCHActivation and configuration (2)
› Introduce SP0 (Conv. CS Speech + PS Interactive 0/0,
RabCombination009) to avoid allocation of PS resources for speech calls when in URA_PCH state.
› If Multi-RAB SP0 is used, it is also important to change the default setting of the dlRlcBufUpswitchMrab parameter. The default value is 0, which means that no upswitches from SP0 will occur, irrespective of RLC buffer load. Initial recommendation is to set dlRlcBufUpswitchMrab = 5.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 38
URA-PCHActivation and configuration (3)
RNC configuration:With URA_PCH, more users are in connected state and the number of connections to the core network will increase. To support this the number of signaling connections, maxconn, is recommended to be set to a higher number.Note: This need to be configured in CN also.
Already set to 75000 per RNC
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 39
URA-PCHSetting of inactivity timers
› T2: (inactivityTimer) 5 seconds
› T3: (inactivityTimerPch) 29 minutes
– sets the maximum time in URA state before the UE is released to Idle
– For maximum URA_PCH benefit 29 min is recommended.(T3 shall not be set to the same value as T305, i.e T305 shall be longer than T3. Current T305 setting in EMT Network is 30 minutes.)
HSPA
FACH
Idle
URA
T1
T2
T3
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 40
URA-PCHSetting of DRX Cycles
› The DRX cycle length can be set different for CN CS, CN PS and UTRAN initiated pages using
– cnDrxCycleLengthCs– cnDrxCycleLengthPs– utranDrxCycleLength
› The recommended value for cnDrxCycleLengthPs and utranDrxCycleLength is increased to 640 ms from W11. This means that all 3 DrxCycle lengths are recommended to be 640 ms.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 41
URA-PCHPLM Info› PROBLEM DESCRIPTION
– If Cell Reselection interrupts an ongoing SM (Security Mode) procedure (i.e. CellUpdate is received while waiting for an RRC SMComplete), then the RNC legacy behaviour is to release the connection and issue an Exception Code EC946 to identify the collision triggering the drop. The affected KPIs are CS accessibility (since CS establishment attempt is aborted) and PS retainability (since existing PS RAB is dropped).
– The most important scenario for an EC946 collision to be triggered is that the UE is in FACH (or URA) state with an active PDP connection, and an speech call is started for the UE. The speech call always triggers a security procedure from CS Core NW (which is performed on FACH). At the same time as the speech call is started, and the security procedure on FACH is ongoing, the UE also often initiates a cell reselection procedure. Since the majority of UEs give priority to CellUpdate over other procedures (security in this case), there is a risk that an EC946 collision ("CellUpdate during Security") can occur.
– Similarly, an EC946 collision can be triggered when an SMS (CS) is sent from FACH (or URA) state
› SOLUTION– The current software release only handles the case where a cellUpdate interrupts the ongoing Security
Mode procedure. It also includes observability of other scenarios related to this area in general. The solution has been implemented with an On/Off switch (default Off).
– If CellUpdate interrupts an ongoing security procedure (i.e. RRC SMCommand sent but RRC SMComplete not yet received), then the new improved handling in RNC will:
› issue EC946 as in legacy, but now indicating that the connection will not be dropped› abort the ongoing security procedure, and roll back to previous security configuration› complete the CellUpdate procedure› perform an RLC re-establishment of SRB2-4 as part of CellUpdate procedure› then resend a new RRC SMCommand to restart a new security procedure › in order to distinguish the different security procedures, handling of RRC transaction ID (rrcTID) has
now been added to all RRC SM procedures
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 42
URA-PCHPLM Info (continued)› SOLUTION ACTIVATION
– The RncFunction spare parameter index 2 is used to activate the improvement, where:› Value 0 will mean that the new functionality is Off.› Value 3 will mean that the new functionality is On.› No value other than 0 or 3 is allowed.
– RncFunction spare 0,0,3,0,0,0,0,0,0,0
› SOLUTION IMPACT– RNC now attempts to recover EC946 (Cell Update during Security procedure). It is not possible to precisely
estimate the success rate, but field trials have shown that over 90% of all EC946 are now successfully recovered. Depending on factors like network characteristics and UE population, the actual success rate can vary.
– Since EC946 will no longer initiate a release of the connection, KPIs for CS NAS Accessibility and PS Retainability should improve. The expected improvement depends on the relative KPI contribution previously due to this EC946.
– With the introduction of URA-PCH and features like Fast Dormancy, as there are inherently more users on FACH, and therefore more occurrences of this EC946 scenario, the expected KPI improvement should be even greater with this solution
› RISK IF SOLUTION IS NOT IMPLEMENTED– Legacy behavior will prevail, i.e. EC946 will lead to immediate release of the connection.– Ericsson strongly recommends that this System Improvement shall be activated. This recommendation is
especially important in networks that have deployed URA_PCH state and is using the W11B feature Fast Dormancy Handling.
Requires at least W11.1.2.5. Needs to be implemented later
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 43
Content
› Network Data› Introduction› Feature characteristics› Dimensioning› Configuration› Monitoring
– URA FNI report– Report for the rest of RNCs
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 44
MonitoringPS Accessibility
› Overall Accessibility Success Rate PS Interactive
› Number of PS RAB Establishments, PS Interactive
› RAB Establishment Success Rate PS Interactive
nteractivemptPacketIablishAttepmNoRabEst
nteractiveessPacketIablishSuccpmNoRabEst100*
nteractivemptPacketIablishAttepmNoRabEst
nteractiveessPacketIablishSuccpmNoRabEst
*easePsNasSignRelpmNoSystemeasePsNasSignRelpmNoNormal
easePsNasSignRelpmNoNormal
*nnPsaringRrcCopmNoLoadShPsConnectReqpmTotNoRrc
PsSuccConnectReqpmTotNoRrc
100*
nteractiveessPacketIablishSuccpmNoRabEst
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 45
MonitoringSpeech Accessibility
› Overall Accessibility Success Rate Speech
ryAttpmNoDirRetmptSpeechablishAttepmNoRabEst
essSpeechablishSuccpmNoRabEst
*easeCsNasSignRelpmNoSystemeaseCsNasSignRelpmNoNormal
easeCsNasSignRelpmNoNormal
*nnCsaringRrcCopmNoLoadShCsConnectReqpmTotNoRrc
CsSuccConnectReqpmTotNoRrc
100*
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 46
MonitoringDrop Rate
› RAB Drop Rate PS Interactive
› RAB Drop Rate Speech
aSuccFachUrpmChSwitch
PacketUraRabReleasepmNoSystem
Packet-RabReleasepmNoSystem
PacketUraRabReleasepmNoNormal
Packet -RabReleasepmNoNormal
/PacketUra RabReleasepmNoSystem
Packet-RabReleasepmNoSystem100*
SpeechRabReleasepmNoSystem
Speech RabReleasepmNoNormal/SpeechRabReleasepmNoSystem100*
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 47
MonitoringChannel Switching
› Channel Switch Success Rate FACH-URA
› Channel Success Failure Rate URA-FACH
› URA Update Success Rate
hUraAttemptFacpmChSwitch
aSuccFachUrpmChSwitch100*
FachAttemptUrapmChSwitch
hSuccUraFacpmChSwitch100*
AttemptpmNoUraUpd
SuccesspmNoUraUpd100 *
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 48
MonitoringPaging
› The paging load in the RNC can be measured as follows:
Where:– = noOfPagingRecordTransm
– is the measurement time in sec
› The paging congestion in the RNC can be measured as follows:
CellsofNumbert
nAttemptTypepmNoPaging rep
__*
1Q _interfacepaging_air
%1001
rep
cong nAttemptTypepmNoPaging
jectedReanAttemptUtrpmNoPagingP
trepn
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 49
MonitoringPaging types contribution (1)
› Contribution of LA paging
› Contribution of RA paging
raUetPagingToUpmUtranIni
e+gingToUraUpmCnInitPa
UeRagingToldlepmCnInitPa
UeLagingToldlepmCnInitPa
Ue+gingToldlepmCnInitPa
/UeLagingToldlepmCnInitPa100*
raUetPagingToUpmUtranIni
e+gingToUraUpmCnInitPa
UeRagingToldlepmCnInitPa
UeLagingToldlepmCnInitPa
Ue+gingToldlepmCnInitPa
/UeRagingToldlepmCnInitPa100*
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 50
MonitoringPaging types contribution (2)
› Contribution of Global paging
› Contribution of URA paging
raUetPagingToUpmUtranIni
e+gingToUraUpmCnInitPa
UeRagingToldlepmCnInitPa
UeLagingToldlepmCnInitPa
Ue+gingToldlepmCnInitPa
/raUetPagingToUpmUtranIni
e+gingToUraUpmCnInitPa100*
raUetPagingToUpmUtranIni
e+gingToUraUpmCnInitPa
UeRagingToldlepmCnInitPa
UeLagingToldlepmCnInitPa
Ue+gingToldlepmCnInitPa
/UegingToldlepmCnInitPa100*
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 51
Monitoringusers
› Active Users SRNC
› Average Users URA
stCell ctiveUesBepmSamplesA
lleUesBestCepmSumActiv
abUra pmSamplesR
a pmSumRabUr
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 52
MonitoringProcessor’ load
› mMP load
› C2MP load
deasuredLoapmSamplesM
redLoadpmSumMeasuLoadmMP _
deasuredLoapmSamplesM
redLoadpmSumMeasuLoadMPC _2
URA FNI
RNC2T
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 54
Executive summary
› Paging Intensity has increased ~70% - as expected.› ~60% of Paging Load is to URA – very good potential in case area split is
required in the future (only URA split can be applied)› ~45% reduction in the number of PS RAB Establishments – much less
signalling.› ~50% of users reside in URA_PCH state – better user experience for PS users
(lower HS setup latency, positive impact on the battery etc)› No major degradation in Accessibility and Retainability.
– Some degradation in FACH retainability. But not user impacting, since extra drops are due to FACH -> URA failures during PS inactivity. UE related.
– Some degradation in IRAT HO Success Rate for Multi-RAB. Caused by higher usage of “Speech + PS 0/0”. Not critical, since general Speech Retainability is not degraded.
– IRAT HO Drop Rate degradation is not related to URA activation. Caused by 3 cells more than 24 H later.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 55
Overall Accessibility Success Rate PS Interactive
PS Accessibility
97.50%
98.00%
98.50%
99.00%
99.50%
100.00%
130125.0000
130125.1300
130126.0200
130126.1500
130127.0400
130127.1700
130128.0600
130128.1900
130129.0800
130129.2100
130130.1000
130130.2300
PS Data Interactive accessibility
URA Activated
No degradation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 56
PS RRC and RAB Accessibility
PS RRC and RAB Blocking
0.00%
0.05%
0.10%
0.15%
0.20%
0.25%
130125.0000
130125.1300
130126.0200
130126.1500
130127.0400
130127.1700
130128.0600
130128.1900
130129.0800
130129.2100
130130.1000
130130.2300
RRC blocking PS Interactive RAB blocking PS Interactive
URA Activated
No degradation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 57
Number of PS RAB Establishments
Call Distribution
0
10
20
30
40
50
60
130125.0000
130125.1300
130126.0200
130126.1500
130127.0400
130127.1700
130128.0600
130128.1900
130129.0800
130129.2100
130130.1000
130130.2300R
AB
Est
ablis
hm
ents
(#
per
sec
)
Voice CS Data R99 PS HS/A-DCH HS/EUL
URA Activated
~45% decrease
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 58
SPEECH Accessibility
Speech Accessibility
96.00%
96.50%
97.00%
97.50%
98.00%
98.50%
99.00%
99.50%
100.00%
130125.0000
130125.1300
130126.0200
130126.1500
130127.0400
130127.1700
130128.0600
130128.1900
130129.0800
130129.2100
130130.1000
130130.2300
CS Speech accessibility (load sharing excluded)
URA Activated
No degradation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 59
PS Retainability
PS Retainability
99.00%
99.20%
99.40%
99.60%
99.80%
100.00%
130125.0000
130125.1300
130126.0200
130126.1500
130127.0400
130127.1700
130128.0600
130128.1900
130129.0800
130129.2100
130130.1000
130130.2300
PS Interactive retainability
URA Activated
No degradation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 60
FACH retainability
FACH
0
5000
10000
15000
20000
25000
30000
35000
4000024
.01.
2013
14:
00
24.0
1.20
13 1
9:45
25.0
1.20
13 0
1:30
25.0
1.20
13 0
7:15
25.0
1.20
13 1
3:00
25.0
1.20
13 1
8:45
26.0
1.20
13 0
0:30
26.0
1.20
13 0
6:15
26.0
1.20
13 1
2:00
26.0
1.20
13 1
7:45
26.0
1.20
13 2
3:30
27.0
1.20
13 0
5:15
27.0
1.20
13 1
1:00
27.0
1.20
13 1
6:45
27.0
1.20
13 2
2:30
28.0
1.20
13 0
4:15
28.0
1.20
13 1
0:00
28.0
1.20
13 1
5:45
28.0
1.20
13 2
1:30
29.0
1.20
13 0
3:15
29.0
1.20
13 0
9:00
29.0
1.20
13 1
4:45
29.0
1.20
13 2
0:30
30.0
1.20
13 0
2:15
30.0
1.20
13 0
8:00
30.0
1.20
13 1
3:45
30.0
1.20
13 1
9:30
Date
FA
CH
Dis
con
nec
t N
orm
al
0
50
100
150
200
250
FA
CH
Dis
con
nec
t A
bn
orm
al +
FA
CH
to
U
RA
Fai
lure
s
pmNoCellFachDisconnectNormal pmNoCellFachDisconnectAbnorm FACH to URA failures
URA Activated
The difference between no URA and URA is that there is currently a transition from FACH>URA instead of FACH>Idle, where the extra drops originated from. No end-user impact
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 61
SPEECH Retainability
Speech Retainability
96.00%
96.50%
97.00%
97.50%
98.00%
98.50%
99.00%
99.50%
100.00%
130125.0000
130125.1300
130126.0200
130126.1500
130127.0400
130127.1700
130128.0600
130128.1900
130129.0800
130129.2100
130130.1000
130130.2300
CS Speech retainability
URA Activated
No degradation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 62
IRAT HO Success rate
IRAT
80.00%
82.00%
84.00%
86.00%
88.00%
90.00%
92.00%
94.00%
96.00%
98.00%
100.00%
130125.0000
130125.1300
130126.0200
130126.1500
130127.0400
130127.1700
130128.0600
130128.1900
130129.0800
130129.2100
130130.1000
130130.2300
IRAT HO success (GSM) Speech
URA Activated
No degradation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 63
IRAT HO Success rate for multi-rab
IRAT
70.00%
75.00%
80.00%
85.00%
90.00%
95.00%
100.00%
130125.0000
130125.1300
130126.0200
130126.1500
130127.0400
130127.1700
130128.0600
130128.1900
130129.0800
130129.2100
130130.1000
130130.2300
IRAT HO success (GSM) Multi-RAB
URA Activated
Slight degradation
Slight degradation is caused my a more extensive usage of “Speech + PS 0/0”. Not critical, since overall Call Dropped Call Rate is not impacted
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 64
PS Interactive RAB Drop Rate
PS RAB Drop Rate
0.00%
0.20%
0.40%
0.60%
0.80%
1.00%
1.20%25
.01.
2013
00:
00
25.0
1.20
13 0
5:00
25.0
1.20
13 1
0:00
25.0
1.20
13 1
5:00
25.0
1.20
13 2
0:00
26.0
1.20
13 0
1:00
26.0
1.20
13 0
6:00
26.0
1.20
13 1
1:00
26.0
1.20
13 1
6:00
26.0
1.20
13 2
1:00
27.0
1.20
13 0
2:00
27.0
1.20
13 0
7:00
27.0
1.20
13 1
2:00
27.0
1.20
13 1
7:00
27.0
1.20
13 2
2:00
28.0
1.20
13 0
3:00
28.0
1.20
13 0
8:00
28.0
1.20
13 1
3:00
28.0
1.20
13 1
8:00
28.0
1.20
13 2
3:00
29.0
1.20
13 0
4:00
29.0
1.20
13 0
9:00
29.0
1.20
13 1
4:00
29.0
1.20
13 1
9:00
30.0
1.20
13 0
0:00
30.0
1.20
13 0
5:00
30.0
1.20
13 1
0:00
30.0
1.20
13 1
5:00
30.0
1.20
13 2
0:00
Date
%
PS RAB Drop Rate
URA Activated
No degradation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 65
FACH to URA Success Rate
FACH to URA Sucess Rate
0.00%
20.00%
40.00%
60.00%
80.00%
100.00%
120.00%25
.01.
2013
00:
00
25.0
1.20
13 0
5:00
25.0
1.20
13 1
0:00
25.0
1.20
13 1
5:00
25.0
1.20
13 2
0:00
26.0
1.20
13 0
1:00
26.0
1.20
13 0
6:00
26.0
1.20
13 1
1:00
26.0
1.20
13 1
6:00
26.0
1.20
13 2
1:00
27.0
1.20
13 0
2:00
27.0
1.20
13 0
7:00
27.0
1.20
13 1
2:00
27.0
1.20
13 1
7:00
27.0
1.20
13 2
2:00
28.0
1.20
13 0
3:00
28.0
1.20
13 0
8:00
28.0
1.20
13 1
3:00
28.0
1.20
13 1
8:00
28.0
1.20
13 2
3:00
29.0
1.20
13 0
4:00
29.0
1.20
13 0
9:00
29.0
1.20
13 1
4:00
29.0
1.20
13 1
9:00
30.0
1.20
13 0
0:00
30.0
1.20
13 0
5:00
30.0
1.20
13 1
0:00
30.0
1.20
13 1
5:00
30.0
1.20
13 2
0:00
Date
%
FACH to URA Success Rate
URA Activated
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 66
URA to FACH Success Rate
URA to FACH Sucess Rate
0.00%
20.00%
40.00%
60.00%
80.00%
100.00%
120.00%25
.01.
2013
00:
00
25.0
1.20
13 0
5:00
25.0
1.20
13 1
0:00
25.0
1.20
13 1
5:00
25.0
1.20
13 2
0:00
26.0
1.20
13 0
1:00
26.0
1.20
13 0
6:00
26.0
1.20
13 1
1:00
26.0
1.20
13 1
6:00
26.0
1.20
13 2
1:00
27.0
1.20
13 0
2:00
27.0
1.20
13 0
7:00
27.0
1.20
13 1
2:00
27.0
1.20
13 1
7:00
27.0
1.20
13 2
2:00
28.0
1.20
13 0
3:00
28.0
1.20
13 0
8:00
28.0
1.20
13 1
3:00
28.0
1.20
13 1
8:00
28.0
1.20
13 2
3:00
29.0
1.20
13 0
4:00
29.0
1.20
13 0
9:00
29.0
1.20
13 1
4:00
29.0
1.20
13 1
9:00
30.0
1.20
13 0
0:00
30.0
1.20
13 0
5:00
30.0
1.20
13 1
0:00
30.0
1.20
13 1
5:00
30.0
1.20
13 2
0:00
Date
%
URA to FACH Success Rate
URA Activated
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 67
URA Update Success Rate
URA Update Sucess Rate
0.00%
20.00%
40.00%
60.00%
80.00%
100.00%
120.00%25
.01.
2013
00:
00
25.0
1.20
13 0
5:00
25.0
1.20
13 1
0:00
25.0
1.20
13 1
5:00
25.0
1.20
13 2
0:00
26.0
1.20
13 0
1:00
26.0
1.20
13 0
6:00
26.0
1.20
13 1
1:00
26.0
1.20
13 1
6:00
26.0
1.20
13 2
1:00
27.0
1.20
13 0
2:00
27.0
1.20
13 0
7:00
27.0
1.20
13 1
2:00
27.0
1.20
13 1
7:00
27.0
1.20
13 2
2:00
28.0
1.20
13 0
3:00
28.0
1.20
13 0
8:00
28.0
1.20
13 1
3:00
28.0
1.20
13 1
8:00
28.0
1.20
13 2
3:00
29.0
1.20
13 0
4:00
29.0
1.20
13 0
9:00
29.0
1.20
13 1
4:00
29.0
1.20
13 1
9:00
30.0
1.20
13 0
0:00
30.0
1.20
13 0
5:00
30.0
1.20
13 1
0:00
30.0
1.20
13 1
5:00
30.0
1.20
13 2
0:00
Date
%
URA Update Success Rate
URA Activated
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 68
Number of Paging type1 attempts
Paging Type 1
0
2000000
4000000
6000000
8000000
10000000
12000000
14000000
16000000
18000000
2000000025
.01.
2013
00:
00
25.0
1.20
13 0
5:15
25.0
1.20
13 1
0:30
25.0
1.20
13 1
5:45
25.0
1.20
13 2
1:00
26.0
1.20
13 0
2:15
26.0
1.20
13 0
7:30
26.0
1.20
13 1
2:45
26.0
1.20
13 1
8:00
26.0
1.20
13 2
3:15
27.0
1.20
13 0
4:30
27.0
1.20
13 0
9:45
27.0
1.20
13 1
5:00
27.0
1.20
13 2
0:15
28.0
1.20
13 0
1:30
28.0
1.20
13 0
6:45
28.0
1.20
13 1
2:00
28.0
1.20
13 1
7:15
28.0
1.20
13 2
2:30
29.0
1.20
13 0
3:45
29.0
1.20
13 0
9:00
29.0
1.20
13 1
4:15
29.0
1.20
13 1
9:30
30.0
1.20
13 0
0:45
30.0
1.20
13 0
6:00
30.0
1.20
13 1
1:15
30.0
1.20
13 1
6:30
30.0
1.20
13 2
1:45
Date
#
pmNoPagingType1Attempt
URA Activated
~70% increase
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 69
Paging Intensity
Paging Intesity
0.00
10.00
20.00
30.00
40.00
50.00
60.00
70.00
80.0025
.01.
2013
00:
00
25.0
1.20
13 0
5:00
25.0
1.20
13 1
0:00
25.0
1.20
13 1
5:00
25.0
1.20
13 2
0:00
26.0
1.20
13 0
1:00
26.0
1.20
13 0
6:00
26.0
1.20
13 1
1:00
26.0
1.20
13 1
6:00
26.0
1.20
13 2
1:00
27.0
1.20
13 0
2:00
27.0
1.20
13 0
7:00
27.0
1.20
13 1
2:00
27.0
1.20
13 1
7:00
27.0
1.20
13 2
2:00
28.0
1.20
13 0
3:00
28.0
1.20
13 0
8:00
28.0
1.20
13 1
3:00
28.0
1.20
13 1
8:00
28.0
1.20
13 2
3:00
29.0
1.20
13 0
4:00
29.0
1.20
13 0
9:00
29.0
1.20
13 1
4:00
29.0
1.20
13 1
9:00
30.0
1.20
13 0
0:00
30.0
1.20
13 0
5:00
30.0
1.20
13 1
0:00
30.0
1.20
13 1
5:00
30.0
1.20
13 2
0:00
Date
Pag
es p
er c
ell
per
sec
on
d
Paging Intensity
URA Activated
Peaks up to 75 pages per cell per second. Daily average ~50. Within expectations
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 70
Paging type contribution
Paging Type Contribution
0.00%
20.00%
40.00%
60.00%
80.00%
100.00%
120.00%25
.01.
2013
00:
00
25.0
1.20
13 0
5:00
25.0
1.20
13 1
0:00
25.0
1.20
13 1
5:00
25.0
1.20
13 2
0:00
26.0
1.20
13 0
1:00
26.0
1.20
13 0
6:00
26.0
1.20
13 1
1:00
26.0
1.20
13 1
6:00
26.0
1.20
13 2
1:00
27.0
1.20
13 0
2:00
27.0
1.20
13 0
7:00
27.0
1.20
13 1
2:00
27.0
1.20
13 1
7:00
27.0
1.20
13 2
2:00
28.0
1.20
13 0
3:00
28.0
1.20
13 0
8:00
28.0
1.20
13 1
3:00
28.0
1.20
13 1
8:00
28.0
1.20
13 2
3:00
29.0
1.20
13 0
4:00
29.0
1.20
13 0
9:00
29.0
1.20
13 1
4:00
29.0
1.20
13 1
9:00
30.0
1.20
13 0
0:00
30.0
1.20
13 0
5:00
30.0
1.20
13 1
0:00
30.0
1.20
13 1
5:00
30.0
1.20
13 2
0:00
Date
Co
ntr
ibu
tio
n i
n %
Global Pagings LA Pagings RA Pagings URA Pagings
URA Activated
URA paging constitutes ~60% during BH. Good potential.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 71
Number of users
User Distribution
-1000
0
1000
2000
3000
4000
5000
6000
7000
130125.0000
130125.1300
130126.0200
130126.1500
130127.0400
130127.1700
130128.0600
130128.1900
130129.0800
130129.2100
130130.1000
130130.2300C
on
nec
ted
Use
rs
Voice CS Data R99 PS HS/A-DCH HS/EUL FACH URA HS-FACH EUL-FACH
URA Activated
~50% of users in URA state – very positive result.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 72
Active users vs iub throughput
Iub Throughput vs Active Users
0
100
200
300
400
500
600
130125.0000
130125.1300
130126.0200
130126.1500
130127.0400
130127.1700
130128.0600
130128.1900
130129.0800
130129.2100
130130.1000
130130.2300
Iub
Th
rou
gh
pu
t (M
bp
s)
0.0
500.0
1000.0
1500.0
2000.0
2500.0
3000.0
3500.0
4000.0
Act
ive
Use
rs
Iub Throughput Active Users
URA Activated
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 73
Processor load overview
Processor Load Comparison
0%
5%
10%
15%
20%
25%
30%
35%
130125.0000
130125.1300
130126.0200
130126.1500
130127.0400
130127.1700
130128.0600
130128.1900
130129.0800
130129.2100
130130.1000
130130.2300
Module MP RANAP/C2 MP Load DC-SP CC-SP PDR-SP RNSAP/C2 MP Load
URA Activated
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 74
Mmp and ranap load
Processor Load Comparison
4%
6%
8%
10%
12%
14%
16%
18%
20%
130125.0000
130125.1300
130126.0200
130126.1500
130127.0400
130127.1700
130128.0600
130128.1900
130129.0800
130129.2100
130130.1000
130130.2300
Module MP RANAP/C2 MP Load
URA Activated
With URA we expect a reduction in mMP and RANAP load. Due to very low initial processor load this gain is not very pronounced.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 75
IRAT HO Drop Rateday
IRAT HO Drop Rate (Day level)
0.00
0.20
0.40
0.60
0.80
1.00
1.20
1.40
1.60
1.80
2.00
1/2
2/2
013
1/2
3/2
013
1/2
4/2
013
1/2
5/2
013
1/2
6/2
013
1/2
7/2
013
1/2
8/2
013
1/2
9/2
013
1/3
0/2
013
1/3
1/2
013
2/1
/2013
%
RNC2T
URA Activated
Degradation start
Not related to URA activation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 76
IRAT HO Drop Ratehour
IRAT HO Drop Rate (Hour Level)
0.00
1.00
2.00
3.00
4.00
5.00
6.00
7.00
8.00
9.00
1/2
2/2
013 0
.00
1/2
2/2
013 5
.00
1/2
2/2
013 1
0.0
0
1/2
2/2
013 1
5.0
0
1/2
2/2
013 2
0.0
0
1/2
3/2
013 1
.00
1/2
3/2
013 6
.00
1/2
3/2
013 1
1.0
0
1/2
3/2
013 1
6.0
0
1/2
3/2
013 2
1.0
0
1/2
4/2
013 2
.00
1/2
4/2
013 7
.00
1/2
4/2
013 1
2.0
0
1/2
4/2
013 1
7.0
0
1/2
4/2
013 2
2.0
0
1/2
5/2
013 3
.00
1/2
5/2
013 8
.00
1/2
5/2
013 1
3.0
0
1/2
5/2
013 1
8.0
0
1/2
5/2
013 2
3.0
0
1/2
6/2
013 4
.00
1/2
6/2
013 9
.00
1/2
6/2
013 1
4.0
0
1/2
6/2
013 1
9.0
0
1/2
7/2
013 0
.00
1/2
7/2
013 5
.00
1/2
7/2
013 1
0.0
0
1/2
7/2
013 1
5.0
0
1/2
7/2
013 2
0.0
0
1/2
8/2
013 1
.00
1/2
8/2
013 6
.00
1/2
8/2
013 1
1.0
0
1/2
8/2
013 1
6.0
0
1/2
8/2
013 2
1.0
0
1/2
9/2
013 2
.00
1/2
9/2
013 7
.00
1/2
9/2
013 1
2.0
0
1/2
9/2
013 1
7.0
0
1/2
9/2
013 2
2.0
0
1/3
0/2
013 3
.00
1/3
0/2
013 8
.00
1/3
0/2
013 1
3.0
0
1/3
0/2
013 1
8.0
0
1/3
0/2
013 2
3.0
0
1/3
1/2
013 4
.00
1/3
1/2
013 9
.00
1/3
1/2
013 1
4.0
0
1/3
1/2
013 1
9.0
0
2/1
/2013 0
.00
2/1
/2013 5
.00
2/1
/2013 1
0.0
0
%
RNC2T
URA Activated
Degradation start
Not related to URA activation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 77
IRAT HO Drop RateROP
IRAT HO Drop Rate (ROP level)
0.00
5.00
10.00
15.00
20.00
25.00
30.00
1/2
2/2
013 0
.00 0
.00
1/2
2/2
013 3
.00 4
5.0
01/2
2/2
013 7
.00 3
0.0
01/2
2/2
013 1
1.00 1
5.00
1/2
2/2
013 1
5.00 0
.00
1/2
2/2
013 1
8.00 4
5.00
1/2
2/2
013 2
2.00 3
0.00
1/2
3/2
013 2
.00 1
5.0
01/2
3/2
013 6
.00 0
.00
1/2
3/2
013 9
.00 4
5.0
01/2
3/2
013 1
3.00 3
0.00
1/2
3/2
013 1
7.00 1
5.00
1/2
3/2
013 2
1.00 0
.00
1/2
4/2
013 0
.00 4
5.0
01/2
4/2
013 4
.00 3
0.0
01/2
4/2
013 8
.00 1
5.0
01/2
4/2
013 1
2.00 0
.00
1/2
4/2
013 1
5.00 4
5.00
1/2
4/2
013 1
9.00 3
0.00
1/2
4/2
013 2
3.00 1
5.00
1/2
5/2
013 3
.00 0
.00
1/2
5/2
013 6
.00 4
5.0
01/2
5/2
013 1
0.00 3
0.00
1/2
5/2
013 1
4.00 1
5.00
1/2
5/2
013 1
8.00 0
.00
1/2
5/2
013 2
1.00 4
5.00
1/2
6/2
013 1
.00 3
0.0
01/2
6/2
013 5
.00 1
5.0
01/2
6/2
013 9
.00 0
.00
1/2
6/2
013 1
2.00 4
5.00
1/2
6/2
013 1
6.00 3
0.00
1/2
6/2
013 2
0.00 1
5.00
1/2
7/2
013 0
.00 0
.00
1/2
7/2
013 3
.00 4
5.0
01/2
7/2
013 7
.00 3
0.0
01/2
7/2
013 1
1.00 1
5.00
1/2
7/2
013 1
5.00 0
.00
1/2
7/2
013 1
8.00 4
5.00
1/2
7/2
013 2
2.00 3
0.00
1/2
8/2
013 2
.00 1
5.0
01/2
8/2
013 6
.00 0
.00
1/2
8/2
013 9
.00 4
5.0
01/2
8/2
013 1
3.00 3
0.00
1/2
8/2
013 1
7.00 1
5.00
1/2
8/2
013 2
1.00 0
.00
1/2
9/2
013 0
.00 4
5.0
01/2
9/2
013 4
.00 3
0.0
01/2
9/2
013 8
.00 1
5.0
01/2
9/2
013 1
2.00 0
.00
1/2
9/2
013 1
5.00 4
5.00
1/2
9/2
013 1
9.00 3
0.00
1/2
9/2
013 2
3.00 1
5.00
1/3
0/2
013 3
.00 0
.00
1/3
0/2
013 6
.00 4
5.0
01/3
0/2
013 1
0.00 3
0.00
1/3
0/2
013 1
4.00 1
5.00
1/3
0/2
013 1
8.00 0
.00
1/3
0/2
013 2
1.00 4
5.00
1/3
1/2
013 1
.00 3
0.0
01/3
1/2
013 5
.00 1
5.0
01/3
1/2
013 9
.00 0
.00
1/3
1/2
013 1
2.00 4
5.00
1/3
1/2
013 1
6.00 3
0.00
1/3
1/2
013 2
0.00 1
5.00
2/1
/2013
0.0
0 0.0
02/1
/2013
3.0
0 45.0
02/1
/2013
7.0
0 30.0
02/1
/2013
11.0
0 1
5.0
0
%
RNC2T
URA Activated
Degradation start
Not related to URA activation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 78
IRAT HO Drop Rateworst performing cells
IRAT HO Drop Rate, Worst Cells RNC2T
0
10
20
30
40
50
60
70
80
90
100
28-01-13 29-01-13 30-01-13 31-01-13 01-02-13 02-02-13 03-02-13
IRA
T D
rop
Rat
e, %
IRAT_DROP_PARKSU3
IRAT_DROP_PARKSX3
IRAT_DROP_VORKEU4
IRAT HO Drop Rate Contribution for RNC2T
0
5
10
15
20
25
30
35
40
45
50
28-01-13 29-01-13 30-01-13 31-01-13 01-02-13 02-02-13 03-02-13IR
AT
Dro
p R
ate
Co
ntr
ibu
tio
n,
%
Contribution_PARKSU3
Contribution_PARKSX3
Contribution_VORKEU4
IRAT HO Drop Rate degradation is not related to URA activation. Caused by 3 cells, that degraded on the 30th of January
URA activationRNC1
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 80
Executive summary
› Paging Intensity has increased ~60% as a result of RA / URA split - as expected.
› ~40% of Paging Load is to URA – lower that in other RNCs. Could be due to Fast Dormancy in UEs
› ~25% reduction in the number of PS RAB Establishments – much less signalling.
› ~30% of users reside in URA_PCH state – better user experience for PS users (lower HS setup latency, positive impact on the battery etc). Lower that in other RNCs. Could be due to Fast Dormancy in UEs
› No major degradation in Accessibility and Retainability.– Some degradation in FACH retainability. But not user impacting, since extra
drops are due to FACH -> URA failures during PS inactivity. UE related.– Slight degradation in PS Drop Rate.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 81
Accessibility
98.00%
98.50%
99.00%
99.50%
100.00%
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
PS Data Interactive accessibility
Overall Accessibility Success Rate PS Interactive
URA Activated
No degradation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 82
RRC and RAB Blocking
0.00%
0.05%
0.10%
0.15%
0.20%
0.25%
0.30%
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
RRC blocking PS Interactive RAB blocking PS Interactive
PS RRC and RAB Accessibility
URA Activated
PS RRC Accessibility slightly improved
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 83
Call Distribution
0
50
100
150
200
250
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
RA
B E
stab
lish
men
ts
Voice CS Data R99 PS HS/A-DCH HS/EUL
Number of PS RAB Establishments
URA Activated
~25% decrease
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 84
Accessibility
95.00%
96.00%
97.00%
98.00%
99.00%
100.00%
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
CS Speech accessibility
SPEECH AccessibilityURA Activated
No degradation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 85
PS RAB Drop Rate
0.00%
0.10%
0.20%
0.30%
0.40%
0.50%
0.60%
0.70%4.
02.2
013
00:0
0
4.02
.201
3 03
:00
4.02
.201
3 06
:00
4.02
.201
3 09
:00
4.02
.201
3 12
:00
4.02
.201
3 15
:00
4.02
.201
3 18
:00
4.02
.201
3 21
:00
5.02
.201
3 00
:00
5.02
.201
3 03
:00
5.02
.201
3 06
:00
5.02
.201
3 09
:00
5.02
.201
3 12
:00
5.02
.201
3 15
:00
5.02
.201
3 18
:00
5.02
.201
3 21
:00
6.02
.201
3 00
:00
6.02
.201
3 03
:00
6.02
.201
3 06
:00
6.02
.201
3 09
:00
6.02
.201
3 12
:00
6.02
.201
3 15
:00
6.02
.201
3 18
:00
6.02
.201
3 21
:00
7.02
.201
3 00
:00
7.02
.201
3 03
:00
7.02
.201
3 06
:00
7.02
.201
3 09
:00
Date
%
PS RAB Drop Rate
PS Interactive RAB Drop Rate
URA Activated
Slight increase during Busy Hours
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 86
FACH
0
20000
40000
60000
80000
100000
1200004.
02.2
013
00:0
0
4.02
.201
3 03
:15
4.02
.201
3 06
:30
4.02
.201
3 09
:45
4.02
.201
3 13
:00
4.02
.201
3 16
:15
4.02
.201
3 19
:30
4.02
.201
3 22
:45
5.02
.201
3 02
:00
5.02
.201
3 05
:15
5.02
.201
3 08
:30
5.02
.201
3 11
:45
5.02
.201
3 15
:00
5.02
.201
3 18
:15
5.02
.201
3 21
:30
6.02
.201
3 00
:45
6.02
.201
3 04
:00
6.02
.201
3 07
:15
6.02
.201
3 10
:30
6.02
.201
3 13
:45
6.02
.201
3 17
:00
6.02
.201
3 20
:15
6.02
.201
3 23
:30
7.02
.201
3 02
:45
7.02
.201
3 06
:00
7.02
.201
3 09
:15
Date
FA
CH
Dis
con
nec
t N
orm
al
0
100
200
300
400
500
600
700
800
900
FA
CH
Dis
con
nec
t A
bn
orm
al +
FA
CH
to
U
RA
Fai
lure
s
pmNoCellFachDisconnectNormal pmNoCellFachDisconnectAbnorm FACH to URA failures
FACH retainabilityURA Activated
The difference between no URA and URA is that there is currently a transition from FACH>URA instead of FACH>Idle, where the extra drops originated from. No end-user impact
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 87
Retainability
97.00%
97.50%
98.00%
98.50%
99.00%
99.50%
100.00%
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
CS Speech retainability
SPEECH RetainabilityURA Activated
No degradation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 88
FACH to URA Sucess Rate
0.00%
20.00%
40.00%
60.00%
80.00%
100.00%
120.00%4.
02.2
013
00:0
0
4.02
.201
3 03
:00
4.02
.201
3 06
:00
4.02
.201
3 09
:00
4.02
.201
3 12
:00
4.02
.201
3 15
:00
4.02
.201
3 18
:00
4.02
.201
3 21
:00
5.02
.201
3 00
:00
5.02
.201
3 03
:00
5.02
.201
3 06
:00
5.02
.201
3 09
:00
5.02
.201
3 12
:00
5.02
.201
3 15
:00
5.02
.201
3 18
:00
5.02
.201
3 21
:00
6.02
.201
3 00
:00
6.02
.201
3 03
:00
6.02
.201
3 06
:00
6.02
.201
3 09
:00
6.02
.201
3 12
:00
6.02
.201
3 15
:00
6.02
.201
3 18
:00
6.02
.201
3 21
:00
7.02
.201
3 00
:00
7.02
.201
3 03
:00
7.02
.201
3 06
:00
7.02
.201
3 09
:00
Date
%
FACH to URA Success Rate
FACH to URA Success Rate
URA Activated
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 89
URA to FACH Sucess Rate
0.00%
20.00%
40.00%
60.00%
80.00%
100.00%
120.00%4.
02.2
013
00:0
0
4.02
.201
3 03
:00
4.02
.201
3 06
:00
4.02
.201
3 09
:00
4.02
.201
3 12
:00
4.02
.201
3 15
:00
4.02
.201
3 18
:00
4.02
.201
3 21
:00
5.02
.201
3 00
:00
5.02
.201
3 03
:00
5.02
.201
3 06
:00
5.02
.201
3 09
:00
5.02
.201
3 12
:00
5.02
.201
3 15
:00
5.02
.201
3 18
:00
5.02
.201
3 21
:00
6.02
.201
3 00
:00
6.02
.201
3 03
:00
6.02
.201
3 06
:00
6.02
.201
3 09
:00
6.02
.201
3 12
:00
6.02
.201
3 15
:00
6.02
.201
3 18
:00
6.02
.201
3 21
:00
7.02
.201
3 00
:00
7.02
.201
3 03
:00
7.02
.201
3 06
:00
7.02
.201
3 09
:00
Date
%
URA to FACH Success Rate
URA to FACH Success Rate
URA Activated
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 90
URA Update Sucess Rate
0.00%
20.00%
40.00%
60.00%
80.00%
100.00%
120.00%4.
02.2
013
00:0
0
4.02
.201
3 03
:00
4.02
.201
3 06
:00
4.02
.201
3 09
:00
4.02
.201
3 12
:00
4.02
.201
3 15
:00
4.02
.201
3 18
:00
4.02
.201
3 21
:00
5.02
.201
3 00
:00
5.02
.201
3 03
:00
5.02
.201
3 06
:00
5.02
.201
3 09
:00
5.02
.201
3 12
:00
5.02
.201
3 15
:00
5.02
.201
3 18
:00
5.02
.201
3 21
:00
6.02
.201
3 00
:00
6.02
.201
3 03
:00
6.02
.201
3 06
:00
6.02
.201
3 09
:00
6.02
.201
3 12
:00
6.02
.201
3 15
:00
6.02
.201
3 18
:00
6.02
.201
3 21
:00
7.02
.201
3 00
:00
7.02
.201
3 03
:00
7.02
.201
3 06
:00
7.02
.201
3 09
:00
Date
%
URA Update Success Rate
URA Update Success RateURA Activated
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 91
Paging Type 1
0
10000000
20000000
30000000
40000000
50000000
60000000
70000000
800000004.
02.2
013
00:0
0
4.02
.201
3 03
:00
4.02
.201
3 06
:00
4.02
.201
3 09
:00
4.02
.201
3 12
:00
4.02
.201
3 15
:00
4.02
.201
3 18
:00
4.02
.201
3 21
:00
5.02
.201
3 00
:00
5.02
.201
3 03
:00
5.02
.201
3 06
:00
5.02
.201
3 09
:00
5.02
.201
3 12
:00
5.02
.201
3 15
:00
5.02
.201
3 18
:00
5.02
.201
3 21
:00
6.02
.201
3 00
:00
6.02
.201
3 03
:00
6.02
.201
3 06
:00
6.02
.201
3 09
:00
6.02
.201
3 12
:00
6.02
.201
3 15
:00
6.02
.201
3 18
:00
6.02
.201
3 21
:00
7.02
.201
3 00
:00
7.02
.201
3 03
:00
7.02
.201
3 06
:00
7.02
.201
3 09
:00
Date
#
pmNoPagingType1Attempt
Number of Paging type1 attempts
URA Activated
~60% reductiondue to RA / URA split
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 92
Paging Intesity
0.00
50.00
100.00
150.00
200.00
250.004.
02.2
013
00:0
0
4.02
.201
3 03
:00
4.02
.201
3 06
:00
4.02
.201
3 09
:00
4.02
.201
3 12
:00
4.02
.201
3 15
:00
4.02
.201
3 18
:00
4.02
.201
3 21
:00
5.02
.201
3 00
:00
5.02
.201
3 03
:00
5.02
.201
3 06
:00
5.02
.201
3 09
:00
5.02
.201
3 12
:00
5.02
.201
3 15
:00
5.02
.201
3 18
:00
5.02
.201
3 21
:00
6.02
.201
3 00
:00
6.02
.201
3 03
:00
6.02
.201
3 06
:00
6.02
.201
3 09
:00
6.02
.201
3 12
:00
6.02
.201
3 15
:00
6.02
.201
3 18
:00
6.02
.201
3 21
:00
7.02
.201
3 00
:00
7.02
.201
3 03
:00
7.02
.201
3 06
:00
7.02
.201
3 09
:00
Date
Pag
es p
er c
ell
per
sec
on
d
Paging Intensity
Paging IntensityURA Activated
Peaks up to 95 pages per cell per second. Daily average ~60. Within expectations. Has to be closely monitored.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 93
Paging Type Contribution
0.00%
20.00%
40.00%
60.00%
80.00%
100.00%
120.00%4.
02.2
013
00:0
0
4.02
.201
3 03
:00
4.02
.201
3 06
:00
4.02
.201
3 09
:00
4.02
.201
3 12
:00
4.02
.201
3 15
:00
4.02
.201
3 18
:00
4.02
.201
3 21
:00
5.02
.201
3 00
:00
5.02
.201
3 03
:00
5.02
.201
3 06
:00
5.02
.201
3 09
:00
5.02
.201
3 12
:00
5.02
.201
3 15
:00
5.02
.201
3 18
:00
5.02
.201
3 21
:00
6.02
.201
3 00
:00
6.02
.201
3 03
:00
6.02
.201
3 06
:00
6.02
.201
3 09
:00
6.02
.201
3 12
:00
6.02
.201
3 15
:00
6.02
.201
3 18
:00
6.02
.201
3 21
:00
7.02
.201
3 00
:00
7.02
.201
3 03
:00
7.02
.201
3 06
:00
7.02
.201
3 09
:00
Date
Co
ntr
ibu
tio
n i
n %
Global Pagings LA Pagings RA Pagings URA Pagings
Paging type contributionURA Activated
URA paging constitutes ~40% during BH.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 94
User Distribution
-2000
0
2000
4000
6000
8000
10000
12000
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
Co
nn
ecte
d U
sers
Voice CS Data R99 PS HS/A-DCH HS/EUL FACH URA HS-FACH EUL-FACH
Number of usersURA Activated
~30% of users in URA state – less that in other RNCs. Could be due to fast dormancy in UEs.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 95
Iub Throughput vs Active Users
0
200
400
600
800
1000
1200
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
Iub
Th
rou
gh
pu
t (M
bp
s)
0.0
1000.0
2000.0
3000.0
4000.0
5000.0
6000.0
7000.0
8000.0
9000.0
Act
ive
Use
rs
Iub Throughput Active Users
Active users vs iub throughput
URA Activated
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 96
Processor Load Comparison
0%
10%
20%
30%
40%
50%
60%
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
Module MP RANAP/C2 MP Load DC-SP CC-SP PDR-SP RNSAP/C2 MP Load
Processor load overviewURA Activated
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 97
Processor Load Comparison
0%
10%
20%
30%
40%
50%
60%
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
Module MP RANAP/C2 MP Load
Mmp and ranap loadURA Activated
~10% reduction in mMP load and ~5% reduction in RANAP load.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 98
0.00
0.10
0.20
0.30
0.40
0.50
0.60
1/26/2013 1/27/2013 1/28/2013 1/29/2013 1/30/2013 1/31/2013 2/1/2013 2/2/2013 2/3/2013 2/4/2013 2/5/2013 2/6/2013 2/7/2013
RNC1
IRAT HO Drop RateURA Activated
No degradation
URA activationRNC3
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 100
Executive summary
› Increased Paging Intensity and Channel Switching rate have revealed an ISL3 link problem
› ISL Load Control caused Iub Throughput degradation› InactivityTimer was rolled back to 20sec and URA
deactivated.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 101
RNC3 Iub throughput
0
200000
400000
600000
800000
1000000
1200000
2/7/
13 /
0 /
0
2/7/
13 /
0 /
30
2/7/
13 /
1 /
0
2/7/
13 /
1 /
30
2/7/
13 /
2 /
0
2/7/
13 /
2 /
30
2/7/
13 /
3 /
0
2/7/
13 /
3 /
30
2/7/
13 /
4 /
0
2/7/
13 /
4 /
30
2/7/
13 /
5 /
0
2/7/
13 /
5 /
30
2/7/
13 /
6 /
0
2/7/
13 /
6 /
30
2/7/
13 /
7 /
0
2/7/
13 /
7 /
30
2/7/
13 /
8 /
0
2/7/
13 /
8 /
30
2/7/
13 /
9 /
0
2/7/
13 /
9 /
30
2/7/
13 /
10
/ 0
2/7/
13 /
10
/ 30
2/7/
13 /
11
/ 0
2/7/
13 /
11
/ 30
2/7/
13 /
12
/ 0
2/7/
13 /
12
/ 30
2/7/
13 /
13
/ 0
2/7/
13 /
13
/ 30
2/7/
13 /
14
/ 0
2/7/
13 /
14
/ 30
2/7/
13 /
15
/ 0
2/7/
13 /
15
/ 30
2/7/
13 /
16
/ 0
2/7/
13 /
16
/ 30
2/7/
13 /
17
/ 0
2/7/
13 /
17
/ 30
2/7/
13 /
18
/ 0
2/7/
13 /
18
/ 30
2/7/
13 /
19
/ 0
2/7/
13 /
19
/ 30
2/7/
13 /
20
/ 0
2/7/
13 /
20
/ 30
2/7/
13 /
21
/ 0
2/7/
13 /
21
/ 30
2/7/
13 /
22
/ 0
Date / Hour / Min
RN
C_C
AP
AC
ITY
RNC1 / IubThroughput
RNC2T / IubThroughput
RNC3 / IubThroughput
RNC4 / IubThroughput
InactivityTimer5sec -> 20sec
URA OFF
URA activationRNC4
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 103
Executive summary
› Paging Intensity has increased ~75% - as expected.› ~60% of Paging Load is to URA – very good potential in case area split
is required in the future (only URA split can be applied)› ~45% reduction in the number of PS RAB Establishments – much less
signalling.› ~50% of users reside in URA_PCH state – better user experience for
PS users (lower HS setup latency, positive impact on the battery etc)› No major degradation in Accessibility and Retainability.
– Some degradation in FACH retainability. But not user impacting, since extra drops are due to FACH -> URA failures during PS inactivity. UE related.
– Improvement in PS Drop Rate.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 104
Accessibility
94.00%
95.00%
96.00%
97.00%
98.00%
99.00%
100.00%
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
PS Data Interactive accessibility
Overall Accessibility Success Rate PS Interactive
URA Activated
No degradation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 105
PS RRC and RAB Accessibility
RRC and RAB Blocking
0.00%
0.05%
0.10%
0.15%
0.20%
0.25%
0.30%
0.35%
0.40%
0.45%
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
RRC blocking PS Interactive RAB blocking PS Interactive
URA Activated
No degradation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 106
Call Distribution
0
10
20
30
40
50
60
70
80
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
RA
B E
stab
lish
men
ts
Voice CS Data R99 PS HS/A-DCH HS/EUL
Number of PS RAB Establishments
URA Activated
~45% decrease
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 107
Speech Accessibility
94.00%
95.00%
96.00%
97.00%
98.00%
99.00%
100.00%
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
CS Speech accessibility (load sharing excluded)
SPEECH AccessibilityURA Activated
No degradation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 108
PS RAB Drop Rate
0.00%
0.20%
0.40%
0.60%
0.80%
1.00%
1.20%4.
02.2
013
00:0
0
4.02
.201
3 03
:00
4.02
.201
3 06
:00
4.02
.201
3 09
:00
4.02
.201
3 12
:00
4.02
.201
3 15
:00
4.02
.201
3 18
:00
4.02
.201
3 21
:15
5.02
.201
3 00
:15
5.02
.201
3 03
:15
5.02
.201
3 06
:15
5.02
.201
3 09
:15
5.02
.201
3 12
:15
5.02
.201
3 15
:15
5.02
.201
3 18
:15
5.02
.201
3 21
:15
6.02
.201
3 00
:15
6.02
.201
3 03
:15
6.02
.201
3 06
:15
6.02
.201
3 09
:15
6.02
.201
3 12
:15
6.02
.201
3 15
:15
6.02
.201
3 18
:15
6.02
.201
3 21
:15
7.02
.201
3 00
:15
7.02
.201
3 03
:15
7.02
.201
3 06
:15
7.02
.201
3 09
:15
Date
%
PS RAB Drop Rate
PS Interactive RAB Drop Rate
URA Activated
~50% decrease
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 109
FACH
0
5000
10000
15000
20000
25000
30000
35000
40000
45000
500004.
02.2
013
00:0
0
4.02
.201
3 03
:00
4.02
.201
3 06
:00
4.02
.201
3 09
:00
4.02
.201
3 12
:00
4.02
.201
3 15
:00
4.02
.201
3 18
:00
4.02
.201
3 21
:15
5.02
.201
3 00
:15
5.02
.201
3 03
:15
5.02
.201
3 06
:15
5.02
.201
3 09
:15
5.02
.201
3 12
:15
5.02
.201
3 15
:15
5.02
.201
3 18
:15
5.02
.201
3 21
:15
6.02
.201
3 00
:15
6.02
.201
3 03
:15
6.02
.201
3 06
:15
6.02
.201
3 09
:15
6.02
.201
3 12
:15
6.02
.201
3 15
:15
6.02
.201
3 18
:15
6.02
.201
3 21
:15
7.02
.201
3 00
:15
7.02
.201
3 03
:15
7.02
.201
3 06
:15
7.02
.201
3 09
:15
Date
FA
CH
Dis
con
nec
t N
orm
al
-50
0
50
100
150
200
250
FA
CH
Dis
con
nec
t A
bn
orm
al +
FA
CH
to
U
RA
Fai
lure
s
pmNoCellFachDisconnectNormal pmNoCellFachDisconnectAbnorm FACH to URA failures
FACH retainabilityURA Activated
The difference between no URA and URA is that there is currently a transition from FACH>URA instead of FACH>Idle, where the extra drops originated from. No end-user impact
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 110
Retainability
95.00%
95.50%
96.00%
96.50%
97.00%
97.50%
98.00%
98.50%
99.00%
99.50%
100.00%
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
CS Speech retainability
SPEECH RetainabilityURA Activated
No degradation
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 111
FACH to URA Sucess Rate
0.00%
20.00%
40.00%
60.00%
80.00%
100.00%
120.00%4.
02.2
013
00:0
0
4.02
.201
3 03
:00
4.02
.201
3 06
:00
4.02
.201
3 09
:00
4.02
.201
3 12
:00
4.02
.201
3 15
:00
4.02
.201
3 18
:00
4.02
.201
3 21
:15
5.02
.201
3 00
:15
5.02
.201
3 03
:15
5.02
.201
3 06
:15
5.02
.201
3 09
:15
5.02
.201
3 12
:15
5.02
.201
3 15
:15
5.02
.201
3 18
:15
5.02
.201
3 21
:15
6.02
.201
3 00
:15
6.02
.201
3 03
:15
6.02
.201
3 06
:15
6.02
.201
3 09
:15
6.02
.201
3 12
:15
6.02
.201
3 15
:15
6.02
.201
3 18
:15
6.02
.201
3 21
:15
7.02
.201
3 00
:15
7.02
.201
3 03
:15
7.02
.201
3 06
:15
7.02
.201
3 09
:15
Date
%
FACH to URA Success Rate
FACH to URA Success Rate
URA Activated
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 112
URA to FACH Sucess Rate
0.00%
20.00%
40.00%
60.00%
80.00%
100.00%
120.00%4.
02.2
013
00:0
0
4.02
.201
3 03
:00
4.02
.201
3 06
:00
4.02
.201
3 09
:00
4.02
.201
3 12
:00
4.02
.201
3 15
:00
4.02
.201
3 18
:00
4.02
.201
3 21
:15
5.02
.201
3 00
:15
5.02
.201
3 03
:15
5.02
.201
3 06
:15
5.02
.201
3 09
:15
5.02
.201
3 12
:15
5.02
.201
3 15
:15
5.02
.201
3 18
:15
5.02
.201
3 21
:15
6.02
.201
3 00
:15
6.02
.201
3 03
:15
6.02
.201
3 06
:15
6.02
.201
3 09
:15
6.02
.201
3 12
:15
6.02
.201
3 15
:15
6.02
.201
3 18
:15
6.02
.201
3 21
:15
7.02
.201
3 00
:15
7.02
.201
3 03
:15
7.02
.201
3 06
:15
7.02
.201
3 09
:15
Date
%
URA to FACH Success Rate
URA to FACH Success Rate
URA Activated
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 113
URA Update Sucess Rate
0.00%
20.00%
40.00%
60.00%
80.00%
100.00%
120.00%4.
02.2
013
00:0
0
4.02
.201
3 03
:00
4.02
.201
3 06
:00
4.02
.201
3 09
:00
4.02
.201
3 12
:00
4.02
.201
3 15
:00
4.02
.201
3 18
:00
4.02
.201
3 21
:15
5.02
.201
3 00
:15
5.02
.201
3 03
:15
5.02
.201
3 06
:15
5.02
.201
3 09
:15
5.02
.201
3 12
:15
5.02
.201
3 15
:15
5.02
.201
3 18
:15
5.02
.201
3 21
:15
6.02
.201
3 00
:15
6.02
.201
3 03
:15
6.02
.201
3 06
:15
6.02
.201
3 09
:15
6.02
.201
3 12
:15
6.02
.201
3 15
:15
6.02
.201
3 18
:15
6.02
.201
3 21
:15
7.02
.201
3 00
:15
7.02
.201
3 03
:15
7.02
.201
3 06
:15
7.02
.201
3 09
:15
Date
%
URA Update Success Rate
URA Update Success RateURA Activated
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 114
Paging Type 1
0
5000000
10000000
15000000
20000000
25000000
30000000
35000000
400000004.
02.2
013
00:0
0
4.02
.201
3 03
:00
4.02
.201
3 06
:00
4.02
.201
3 09
:00
4.02
.201
3 12
:00
4.02
.201
3 15
:00
4.02
.201
3 18
:00
4.02
.201
3 21
:15
5.02
.201
3 00
:15
5.02
.201
3 03
:15
5.02
.201
3 06
:15
5.02
.201
3 09
:15
5.02
.201
3 12
:15
5.02
.201
3 15
:15
5.02
.201
3 18
:15
5.02
.201
3 21
:15
6.02
.201
3 00
:15
6.02
.201
3 03
:15
6.02
.201
3 06
:15
6.02
.201
3 09
:15
6.02
.201
3 12
:15
6.02
.201
3 15
:15
6.02
.201
3 18
:15
6.02
.201
3 21
:15
7.02
.201
3 00
:15
7.02
.201
3 03
:15
7.02
.201
3 06
:15
7.02
.201
3 09
:15
Date
#
pmNoPagingType1Attempt
Number of Paging type1 attempts
URA Activated
~75% increase
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 115
Paging Intesity
0.00
20.00
40.00
60.00
80.00
100.00
120.004.
02.2
013
00:0
0
4.02
.201
3 03
:00
4.02
.201
3 06
:00
4.02
.201
3 09
:00
4.02
.201
3 12
:00
4.02
.201
3 15
:00
4.02
.201
3 18
:00
4.02
.201
3 21
:15
5.02
.201
3 00
:15
5.02
.201
3 03
:15
5.02
.201
3 06
:15
5.02
.201
3 09
:15
5.02
.201
3 12
:15
5.02
.201
3 15
:15
5.02
.201
3 18
:15
5.02
.201
3 21
:15
6.02
.201
3 00
:15
6.02
.201
3 03
:15
6.02
.201
3 06
:15
6.02
.201
3 09
:15
6.02
.201
3 12
:15
6.02
.201
3 15
:15
6.02
.201
3 18
:15
6.02
.201
3 21
:15
7.02
.201
3 00
:15
7.02
.201
3 03
:15
7.02
.201
3 06
:15
7.02
.201
3 09
:15
Date
Pag
es p
er c
ell
per
sec
on
d
Paging Intensity
Paging IntensityURA Activated
Peaks up to 105 pages per cell per second. Daily average ~75. Within expectations. Has to be closely monitored.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 116
Paging Type Contribution
0.00%
20.00%
40.00%
60.00%
80.00%
100.00%
120.00%4.
02.2
013
00:0
0
4.02
.201
3 03
:00
4.02
.201
3 06
:00
4.02
.201
3 09
:00
4.02
.201
3 12
:00
4.02
.201
3 15
:00
4.02
.201
3 18
:00
4.02
.201
3 21
:15
5.02
.201
3 00
:15
5.02
.201
3 03
:15
5.02
.201
3 06
:15
5.02
.201
3 09
:15
5.02
.201
3 12
:15
5.02
.201
3 15
:15
5.02
.201
3 18
:15
5.02
.201
3 21
:15
6.02
.201
3 00
:15
6.02
.201
3 03
:15
6.02
.201
3 06
:15
6.02
.201
3 09
:15
6.02
.201
3 12
:15
6.02
.201
3 15
:15
6.02
.201
3 18
:15
6.02
.201
3 21
:15
7.02
.201
3 00
:15
7.02
.201
3 03
:15
7.02
.201
3 06
:15
7.02
.201
3 09
:15
Date
Co
ntr
ibu
tio
n i
n %
Global Pagings LA Pagings RA Pagings URA Pagings
Paging type contributionURA Activated
URA paging constitutes ~60% during BH. Good potential.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 117
User Distribution
0
1000
2000
3000
4000
5000
6000
7000
8000
9000
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
Co
nn
ecte
d U
sers
Voice CS Data R99 PS HS/A-DCH HS/EUL FACH URA HS-FACH EUL-FACH
Number of usersURA Activated
~50% of users in URA state – very positive result.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 118
Iub Throughput vs Active Users
0
200
400
600
800
1000
1200
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
Iub
Th
rou
gh
pu
t (M
bp
s)
0.0
1000.0
2000.0
3000.0
4000.0
5000.0
6000.0
7000.0
Act
ive
Use
rs
Iub Throughput Active Users
Active users vs iub throughput
URA Activated
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 119
Processor Load Comparison
0%
10%
20%
30%
40%
50%
60%
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
Module MP RANAP/C2 MP Load DC-SP CC-SP PDR-SP RNSAP/C2 MP Load
Processor load overviewURA Activated
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 120
Processor Load Comparison
0%
5%
10%
15%
20%
25%
30%
130204.0000
130204.0600
130204.1200
130204.1800
130205.0000
130205.0600
130205.1200
130205.1800
130206.0000
130206.0600
130206.1200
130206.1800
Module MP RANAP/C2 MP Load
Mmp and ranap loadURA Activated
With URA we expect a reduction in mMP and RANAP load. Due to very low initial processor load this gain is not very pronounced.
URA-PCH Deployment Recommendations | Commercial in confidence | 2013-02-08 | Page 121
IRAT HO Drop RateURA Activated
0.00
0.10
0.20
0.30
0.40
0.50
0.60
0.70
1/26/2013 1/27/2013 1/28/2013 1/29/2013 1/30/2013 1/31/2013 2/1/2013 2/2/2013 2/3/2013 2/4/2013 2/5/2013 2/6/2013 2/7/2013
RNC4
No degradation