Beruflich Dokumente
Kultur Dokumente
KTS UA08.1
Agenda
Part A Fast Dormancy Description
1. Feature overview.
2. Purpose of the feature and benefits.
3. Feature interactions.
4. General feature activation strategy
2
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Part A Fast
Dormancy
Description
3
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Feature
Overview
4
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
5
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
This behaviour is applicable to legacy UEs as well, meaning that a direct transition to PCH shall
be triggered to these mobiles, even if they do not insert the new Rel.8 cause
6
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Operator parameter
option
IE msg presence
UeVersionForScri
includes Ue 3gpp
Release
No
Yes
Yes
Yes
SCRI Cause IE is = UE
No
Requested PS Data
session end?
XX_PCH
Active
Yes
Yes
XX_PCH
Active
No
No
Abnormal Release
Yes
Yes
Yes
XX_PCH
Active
UeVersionForScri
includes Ue 3gpp Release
No
No
No
Abnormal Release
8
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Cell_DCH or
Cell_FACH
- Cell_DCH to Cell_PCH
URA_PCH
- Cell_FACH to Cell_PCH
- Cell_DCH to URA_PCH
- Cell_FACH to URA_PCH
Cell_PCH
Idle
Purpose of the
feature and
benefits
11
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
URA_PCH Active
before Fast Dormancy
Reduce the number of transition states changes with the traffic volume variation or resuming
The costs of the FD is the higher usage of URA PCH with the constrains that it can bring on
Higher CS call setup time for a higher amount of users
Higher call duration in FACH and in PCH where the ue mobility scenarios can produce some
degradation.
Summary of key attributes/benefits (and constraints) enumerated on sum up FD section
13
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Feature
Interaction
14
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Required Feature
15
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
16
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
General Feature
Activation Strategy
17
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
isFastDormancyAllowed = True
isExtendedFastDormancyAllowed = False
This strategy option allow to observe the global impact of the feature activation mainly other side effects beside the extra transition it causes; Also it allows to
observe the performance of FD for recent ues
- FD2 Step2: Activate FastDormancy with more impacted Ues and not affecting legacy SCRI (Without Cause
PSDataSessionEnd):
-
This will allow to include almost all ues supporting 3gppR8 IE specification
- FD3 Step3: Activate FastDormancy with all 3GPPR6 or later Ues including legacy SCRI (Without Cause PSDataSessionEnd):
-
This will include the remaining Ues with 3gppR6 and later version, for any SCRI proposed and allow to reach a high level of triggering of FD
- FD4 Step4: Activate FastDormancy with all UEs including all legacy SCRI (Without Cause PSDataSessionEnd)
-
This parameter tuning will allow to observe the remaining trigger of R5 UEs which are considered to be mainly driven by SCRI not supporting 3gppR8 compatible
IE
18
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
RNC
RadioAccessService
isFastDormancyAllowed
ueVersionForScri
isExtendedFastDormancyAllowed
UeTimerCstConnectedMode
t323
19
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
PART B Performance
assessment on
FFA/FOA
20
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Feature Activation
strategy used
21
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
- FD2 20th of July: Activation of fast dormancy(FD) at this stage without EFD UeVersionForSCRI = R6_R7_R8.
- FD3 27th of July: extended fast dormancy(EFD) is activated: isExtendedFastDormancyAllowed = True
- FD3off31st of July: extended fast dormancy(EFD) is deactivated: isExtendedFastDormancyAllowed = False
- 2nd of Aug: decrease RepThreshold to increase Direct Transition: RadioAccessService.AlwaysOnConf.AoFachParam.repThreshold = 512->256
- 3rd of Aug: Change TimeToTrigger to 100 ms
- 6th of Aug: change RBsetConf to AOMode ReleaseOnly (HSDPA) and also change RepThreshold from 256 to 128
- FD4 1/0 7th of August: modify UeversionForSCRI from R6_R7_R8 to Pre_R8 and modify isExtendedFastDormancyAllowed to True, then
back out 8 hours later due to TMU reset
22
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
- FD2 14th of August : Activation of fast dormancy(FD) at this stage without EFD UeVersionForSCRI = R6_R7_R8.
- FD3 15th of August extended fast dormancy(EFD) is activated at this stage just for 3 hours after all FD is deactivated:
isExtendedFastDormancyAllowed = True
- FD3 20th of Sept : Activation of extended fast dormancy EFD is activated at this stage isExtendedFastDormancyAllowed =True
- FD2_T323 24th of Sept: Deactivation of EFD and decreasing T323 isExtendedFastDormancyAllowed = False & t323=10 secs
- 25th of Sept enhanced Paging Release for Rel7+ devices [CRE128146] isDirectTransitionFromPchToIdleAllowed = true
- FD2 1st of Oct: by the last time Re-activation of fast dormancy(FD) at this stage without EFD UeVersionForSCRI = R6_R7_R8.
isFastDormancyAllowed=True isExtendedFastDormancyAllowed = False.
23
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Sum Up of Fast
Dormancy
24
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Description
At&t A1TA
Result
PS Latency
UE battery usage
TMU load
Processor Occupancy.
UTRAN paging
SGSN paging
CS setup latency
from URA
Increased by approx 1.0 secs for the setup from URA with DT
compared to a setup over FACH. However main result is the increase
of ~30% with FD2 of setups over DCH
mRAB penetration
25
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Description
At&t A1TA
Result
10
CS paging Success
11
DL Power, Codes
consumption; UCU;
RTWP
12
13
FACH Efficiency
26
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Description
At&t A1TA
Result
KPI11
CDR Voice
CS Retainability
Is not impacted by URA or FD, it remains constant thru URA and FD activation of both FOA/FFA.
KPI13
PS Retainability
For ATT It can be noticed an improvement overall due to global strategy including with URA.
CDR PS
3
KPI14
FD2 can produce small degradation observed on both FOA/FFA ranging from 0.03% to 0.08% (worse
observation in A1TA)
Global CSSR CS
Is affected by RRC accessibility, remaining components have no impact with URA or FD. The KPI35 cs is
affected by .09% of degradation which produces a kpi impact of 0.04% degradation in Kpi14. Applying
modified formulas allow to have a new baseline for KPi35CS in order to avoid impact on KPI14
Global CSSR PS
Degradation observed due to two components; KPI35PS and KPI33, the first one is rebase lined with the
modified formula to take into account the state transitions and will not produce any degradations. The
Kpi33 component will produce an overall degradation of 0.04% detailed below
CS RAB success
rate
PS RAB success
rate
Degradation produced by URA_PCH and FD are mainly due to a different distribution and mechanisms of
accessibility (using state transitions and not RAB establishment). The degradation is at most 0.1%
CSSR_CS
4
KPI16
CSSR_PS
KPI32
RABEstab
CS_SR
KPI33
RABEstab
PS_SR
27
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
State transitions
and RRC contexts
28
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
Aug23
The Global observations of State transition, show the main volume decrease of RRC and PS Releases due to SCRI,
while the overall state transitions tend to increase specially CellDCHtoPCH, PCHtoFACH, CellFachtoPCH. The FACHtoDCH
increase due to more UEs needing traffic in DCH
There is global increase of state transitions as result of some UEs triggering an upsize reconf to send an SCRI just
after (depending on T323).
The big increase on 1st of August is due to a normal traffic increase.
29
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
in
9.327
8.03
5.327
3.502
Before
out
9.322
7.8002
5.661
3.403
28-Jun
diff
0.005
0.2298
-0.334
0.099
0.00
drops
0.02
0.017
KC09
After
23-Aug
Millions in
out
diff
drops
dch
4.974
4.968
0.006
0.01
fach
5.784
5.623
0.161
0.015
idle
1.657
2.03 -0.373
pch
6.6
6.394
0.206
0.012
0.00
Success rate
Success events
Normalized events
0.007
URA Update
Confirm
Normalization due to PS
increase traffic on Aug 27%
URA_PCH
URA_PCH
99.98%
132K
RB Reconfig
(DBC)
99.46%
4.83M
Cell-DCH
4.34M**
RRC
Connection
Establish
99.57%
3.37M
99.42%
196K
RRC
Connection
Release
92.96%
3.47M RRC
Connection
Establish
5.661M
Cell Update
Confirm
99.8%
3.2MCell Update
RB Reconfig
(DBC)
1.62M**
37K FACH
voice setup
RRC
Connection
Establish
RRC
Connection
Release
99.8%
3.262M
96.32%
406
Cell-DCH
Cell_FACH
Cell Update/
Confirm
98.97%
598K
Confirm
RRC
Connection
Release
99.84%
5.784M
26K FACH
voice setup
2.346M RRC
Connection
Establish
Idle
Cell Update
Confirm
Cell_FACH
63.42%
2.030M
0.96M**
Idle
99.92%
3.338M
RRC
Connection
Release
0** 0.012K
Drops
Uon
1.8E+10
At&t
FD3
KC9
EDCH
FD1
1.6E+10
AO R HS;DT@128
FD4 I/0
FD3off
PagingRep
FD2
1.4E+10
1.2E+10
1E+10
8E+09
6E+09
4E+09
2E+09
TotalURA_PCH
31
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
TotalCell_FACH
13Sep
10Sep
7Sep
4Sep
1Sep
29Aug
26Aug
23Aug
20Aug
17Aug
14Aug
11Aug
8Aug
5Aug
2Aug
30Jul
27Jul
24Jul
21Jul
18Jul
15Jul
12Jul
9Jul
6Jul
3Jul
30Jun
27Jun
24Jun
21Jun
18Jun
0
15Jun
5000000
KC9
EDCH
4500000
AO_R_HS
0.8
FD3off
FD2
FD1
FD3
At&t
0.7
4000000
0.6
FD4 I/0
3500000
3000000
0.5
0.4
2500000
2000000
0.3
1500000
0.2
1000000
0.1
500000
VS_IuReleaseReqPs_UeGeneratedSignallingConnectionRelease(U599_5)(Event)
VS_UEReqDataSessionEnd_toPch(U2964)(Event)
13Sep
11Sep
9Sep
7Sep
5Sep
3Sep
1Sep
30Aug
28Aug
26Aug
24Aug
22Aug
20Aug
18Aug
16Aug
14Aug
12Aug
10Aug
8Aug
6Aug
4Aug
2Aug
31Jul
29Jul
27Jul
25Jul
23Jul
21Jul
19Jul
17Jul
15Jul
13Jul
9Jul
11Jul
7Jul
5Jul
3Jul
1Jul
29Jun
27Jun
25Jun
23Jun
21Jun
19Jun
17Jun
15Jun
%ofSCRI_PSDataSessionEnd
The several steps of Fast Dormancy have quite different impacts on, mainly Step 2 is addressing almost 60% of SCRi while step3
takes additional 10 % and Step 4 considers the remain 30% to reach the 100% of SCRI handled by RNC to reconfigure users in
URA_PCH
% of SCRI PSDataSessionEnd is the rate of PSDataSessionEnd/(PsDataSessionEnd+SCRI_IureleaserequestPS)
32
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
The Global observations of State transition, show the main volume decrease of RRC and PS Releases due to SCRI,
while the overall state transitions tend to increase specially CellDCHtoPCH, PCHtoFACH, CellFachtoPCH. The FACHtoDCH
increase due to more UEs needing traffic in DCH
There is global increase of state transitions as result of some UEs triggering an upsize reconf to send an SCRI just
after (depending on T323). Also this increase is a litle bit more noticeable for A1TA due to smaller URAToIdleTimer
(25min vs 720min on Att)
33
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
URA no FD
in
out
5.49E+06 5.40E+06
5.57E+06 5.51E+06
1.67E+06 1.58E+06
2.80E+06 3.03E+06
diff
-9.26E+04
-5.70E+04
-8.58E+04
2.35E+05
State
DCH
FACH
URAPCH
Idle
URA Update
Confirm
URA_PCH
99.98%
47.7K
98.98%
1.62M
99.34%
0.114M
RB Reconfig
(DBC)
99.70%
4.10M
Cell-DCH
99.20%
99.45%
RRC
Connection 2.35M
1.25M**
RRC
Connection
Establish
Release
3.03M
RB Reconfig
(DBC)
99.95%
0.313M
99.26%
2.74M
99.74%
3.86M
Cell-DCH
99.92%
2.67M
98.68%
RRC
Connection
Establish
Connection
Release
2.71M
2.04M
63.9K FACH
voice setup
RRC
Connection
Release
0.8M**
Idle
Cell Update
Confirm
Cell_FACH
0.76M** 99.47%
RRC
30.6K FACH
voice setup
RRC
Connection
Release
Cell Update/
Confirm
99.44%
0.227M
Confirm
1.54M**
Idle
URA_PCH
Cell Update
Confirm
Cell_FACH
diff
-4.89E+04
-2.38E+05
-1.91E+05
4.78E+05
URA Update
Confirm
Success rate
Success events
99.92%
1.47M
Cell Update
A1TA
35
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
A1TA
With FD R6R7R8 the SCRI with PSDataSessionEnd is almost 40%. The Extended FD increase it further to ~65% of all SCRI.
The usage of T323 reduced from 30secs to 10 secs make the PSDatasessionend SCRI increase as expected.
The usage of FD2 and FD3 produces a reduction on the global SCRi, while this is understood for the case of FD2 because of
T323 and correction of CR 729587 which ignores SCRI in case of State transition on going, the reduction for EFD (FD3) is still
under discussion (No AR open up to now).
36
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Performance assessment : RRC contexts & State transition sumup At&t A1TA
1.
Triggering of SCRI
For Att, the several steps of Fast Dormancy have quite different impacts on, mainly Step 2 is addressing almost 60% of SCRi
while step3 takes additional 10 % and Step 4 considers the remain 30% to reach the 100% of SCRI handled by RNC to
reconfigure users in URA_PCH
For A1TA, the amount of PS releases with SCRI is reduced ~40% with FD. It is further reduced to~64% with extended. The
reductions on total amount of SCRI is due to the observation of T323 and the scenario of SCRI ignored when happening at same
time of a Reconfiguration. Defining the T323 at a lower value is also producing more SCRI as expected.
2.
RRC Contexts
Att, show a reductions of ~70% overall (URA+FD) on both RNCs of RRC PS Attempts on the step2 of Fast Dormancy. On the
few days of FD step 3 we can observe ~80% reduction. For the CS it is also observed a reduction but less expressive it
ranges from 40% to 60% depending on the step of FD. With A1TA the gain is lower ~40% for PS and 15-20 % for CS
ATT strategy of AO release Only is put in place for HSDPA and EDCH channel types, the contribution of FACH becomes
only URA PCH these strategies also allow to keep a lower value of FACH usage while URA and FD is adding up on
FACH, release only is subtracting leaving the fach context almost the same.
A1TA, as no similar strategy was used, it increases the FACH context ~40%, the increase is a contribution of URA
incoming
AO release only mode have an effect of removing SDU In FACH/RACH while URA & FD have the contrary effect of
increase FACH usage and the traffic on these channels
As Observed before with URA PCH activation the FACH usage and FACh efficiency (SDU/ErlgFACH) increase with FD
Performance assessment : State transition & RRC Contexts sumup At&t A1TA
The Previous Sections continuations:
3.
State transitions
With FD the DT PCH to DCH increase 60% for A1TA and ~40% for Att (higher Repthreshold), the success rate is also
a bit better around 0.1%. The T323 change from 30 secs to 10 secs increase slightly the amount of DT due to higher
amount of ue entering in URA as well.
In ATT the increase on this transition is ~65%, mainly because of strategy of release only which takes already some
ues to PCH. For A1TA the increase is more visible as there is a more impact of SCRi. The DCH to URAPCH is degraded
as expected mainly in case of EFD.
A1TA FOA also reported User impacting, mainly related with Extended FD which was causing problems on some ue's
preventing them from receive call and send SMS.
The DCH to FACH is improved by 0.05% this is mainly attributed to changes on Code due to the race conditions in case
of Reconfigurations of AO and SCRi. The volume decrease less than 10%. However later on for ATT this transition is
removed
IN A1TA The success rate FACH to DCH decrease by 0.5%, this is produced by a higher amount of EDCH upsize
(+15%) which is mainly produced by EDCH which has a lower success rate. Looking at another indicator global for AO
upsize we can see actually a small gain of 0.02%. The volume increase as well around 20%. In Att the volume increase
closer to the 30% while the success rate have the same kind of effect only noticed to St005
A1TA FACH to PCH downsize increases almost up to 100% in case of EFD, while for ATT it goes up to 150%. The
success rate follows same changes on both, it is improved in case of single FD due to the fact that it is the ue
triggering the transition. however the EFD success rate is worse due to legacy ue's not responding well to SCRI.
The PCH to FACH upsize have an increase of 65% and 100% depending if FD or EFD is used respectively. the success
rate is more or less kept at a very high value.
The Cs setup over FACH is kept constant on both networks however the setup over URA increase on both cases 30%
38
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
Uon
KC9
EDCH
AO_R_HS
900000
FD4 I/0
FD2
6000000
FD1
FD3 FD3off
800000
700000
5000000
600000
4000000
500000
3000000
400000
300000
2000000
200000
1000000
100000
0
15Jun
17Jun
19Jun
21Jun
23Jun
25Jun
27Jun
29Jun
1Jul
3Jul
5Jul
7Jul
9Jul
11Jul
13Jul
15Jul
17Jul
19Jul
21Jul
23Jul
25Jul
27Jul
29Jul
31Jul
2Aug
4Aug
6Aug
8Aug
10Aug
12Aug
14Aug
16Aug
18Aug
20Aug
22Aug
24Aug
26Aug
28Aug
30Aug
1Sep
3Sep
5Sep
7Sep
9Sep
11Sep
13Sep
FirstRRCConnectionRequest_RRC015_CR_Ps(URRC015_CR_Ps)(Event)
FirstRRCConnectionRequest_RRC015_CR_Cs(URRC015_CR_Cs)(Event)
NumberofSMS_NAS001_CR(UNAS001_CR)(Event)
39
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
There is a reductions of ~40% overall (FD2) of RRC PS Attempts on the step2 of Fast Dormancy. On the few days of FD step 3 we can observe ~80%
reduction
For the CS it is also observed a reduction but less expressive it ranges from 15% to 20% depending on the step of FD. We can extrapolate that 60/70% of Ues
sue CS but not PS regularly so UraPchToIdleTimer is 25 min, allows that the typical larger intervals betweenCS calls make the calls escape from URA .
The success rate is also affected and it will be analyzed on non regression section.
FD RRC PS reduction is proportional to RRC SCRI ratio presented above
40
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
A1TA
At&t
The URA contexts increase nearly 100% for the step2 of FD (from R7_R8 to R6_R7_R8).
The main contribution is the usage of FD on Cell DCH ( increase of blue bars but above all the increase of FD on
FACH state is by far the main contributor for URAPCH state)
It can be notice the clear increments on the amount of SCCP connections active between RNC and SGSN
brought by FD step2 and Step4 (when enabled during a few hours).
The Contexts based on simultaneous number of SCCP connections reveal still a far away number from the
maximum limit of ~81K simultaneous contexts
43
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
The URA contexts increase more than 170% for the last step of FD (extended FD)
The majority of contexts contribution comes from the CellFACH state, the Cell DCH contributes with around
15% of total transitions triggered uniquely by SCRI, while for fach, both SCRI and inactivity contribute for
URAPCH contexts
The T323 @ 10 secs produces more SCRI and so more transitions, however the average amount of contexts is
just slightly increased.
44
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
The traffic usage is not changing as dramatically as URA state transitions, however it can be noticed an increase
mainly due to AO releaseOnly mode which will increase Cell DCH usage with some impact on resources
Apart from this configuration side effect, the URA and FD itself are not changing so much the amount of cell DC
usage even is slightly reduced (due to some traffic carried by Cell FACH).
45
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
46
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
47
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
UE misbehavior
The live tests of FD also revealed several ue issues specially associated with Extended FD
The main issues observed was inability to make/receive Calls and SMS while PS session is active.
Alu was able to get one of these devices on lab (Samsung Galaxy S i9000) and could observe that the usage
after the UE moved to uraPCH due to SCRI or Radio Bearer Release CS, it is not possible anymore to make CS
call or receive SMS.
There was also other type of ues reported with problems like reboots and loss of coverage indications. Because
there were other actions on network like the isDirectTransitionFromPchToIdleAllowed CRE128146, which also
caused problems on some UEs with call failing and loss of signal. There is no other confirmed correlation of EFD
and UE impacted
Several GM customers suggest to use a White list controlled at Oam Utran Level where we can filter based on
IMEI the UEs which are revealing missbehaviours with Fast Dormancy. This solutions is referred based on
implementation of other suppliers. There is already discussions internally in ALU on how to implement a similar
solution.
48
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
49
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
This failure can be related with the fact that edch usage
increases and as well the success rate is not as good as
the HSDPA only upsize success rate.
This means that the fact that we have more edch upsize
will explain the degradation observed on FACH to DCH
success rate
The edch success rate itself is not much changed with
FD and it is in fact quite unstable and difficult to
correlate with FD events
The remaining parameters options show no impact on
Success rate. However T323 have a lower value of
transitions which is a normal correlation. Nevertheless
the several modifications performed in small amount of
time do not provide a definite conclusion on this case.
50
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
At&t
52
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
53
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
CellUpdate - The Cell Update components have mainly 3 changes all related with more Ura usage and FD impact:
At&t A1TA
UlDataTx which is a direct consequence of more URA PCH users; UL Paging response due to more Ues in URA which will answer to paging
and Cell reselection is reducing mainly after Ao ReleaseONly parameter modification, this cause is mainly correlated with FACh usage
Paging Success rate
For Att the Total paging success rate is lower as URA PCH usage increase, The RNC point of view of Total success rate of paging decrease to
~75% when we increase the amount URA PCH with Extended FD, this is mainly attributed to PS Paging in URA PCH. However for A1TA this
change is not observed and this metric remains almost constant in some FD activations we can observe a degradation of almost 1% but this
metric has a big variability. There is a higher degradation observed when enhanced Paging Release for Rel7+ devices was enabled
On both NW there is an increase on Paging success rate of CS over URA after FD is enabled which is explained by a better DT behavior. The
EFD have an effect on loosing more ues which then generates more Enhanced paging of CS. since this type of paging is less efficient, it has
a slight decrease on CS normal paging success rate
On ATT the success rate of URA PS Paging indicator point of view is low as it can in some cases insist on paging a UE which is still failing to
respond to paging. The value is normally trending to 65% success rate. However for A1TA this value remains unchanged with a good
performance around 87%
Considering the amount of PS CN paging and URA PS Paging we can observe that only 25%(the highest with EFD) paging intended for RRC
which means that PCH PS Paging is the main driver for the global Paging006 degradation observed
Form CN, Paging success rate degradation of 1.5 to 2% but they maybe statistical due to the significant reduction in attempts where the
failures are now more illuminated
Cs+PS00 upsize - In A1TA the small degradation observed on the success rate of Cs+PS00 upsize is correlated with FD as the volume of Uspizes
of EDCH is also larger, However the success rate of this upsize transition is already presenting a very good performance? better than 99.95%.
MRAB - There is a normal increase of drops in mrab conditions but as well the amount of mrab usage is higher. Looking at Mrab drop per erlang of
mrab we can observe a normal evolution. In A1TA the Mrab CS over PS increased from 36% to a maximum of 44% while for Att the shift is not so
obvious but increase to 54%.
TMU PO - The calculation shows that the Capacity Gain of FD/DT feature (up to Phase 2) was ~+9% as compared with UA07.1.3 (URA_PCH ON),
~+17.8% as compared with UA07.1.3 (URA_PCH OFF) and ~+21.1% as compared with UA08.1 (URA_PCH OFF) and ~+10.3% as compared
with UA08.1 (URA_PCH ON without FD/DT). A1TA have a TMU PO reductions of 8% with FD and up to 15% with EFD the RAB memory is also
increased by 4 to 6%.
54
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
55
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
The RNC overall paging success rate presents some variation however a definite correlation with FD is difficult to establish as URA PCH usage increase
Depending on the reference we can observe a decrease on success rate around 1% however it recovers after 7 October to the same reference
values.
This can be partially explained due to PS normal Paging, as it have a small decrease as well even if it remains with a good success rate (more details
below). The CS normal paging does not show any special impact
Data from CN from A1TA Not available
There is a higher degradation observed when isDirectTransitionFromPchToIdleAllowed was enabled (25 and 26 Sept). There was also ues reporting several
problems like rebooting and becoming out of service.
56
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
PagingRep
DT@256
DT@256
AO_R_HS
DT@128
AO_R_HS
DT@128
FD4 1/0
FD4 1/0
57
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
PagingRep
58
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
At&t
Uon
Uon
FD2
FD3
1/0
59
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
FD2
FD3 1/0
A1TA
The URA PS Paging seems affected slightly once we use more URA but still the success rate is quite ok keeping a value
~87% of success rate
This can explain the small degradation and recovery observed with Paging006_URA
Also the ratio of CN originated paging vs the RNC originated paging is changing from 65% to 40% with FD (it goes down
to 25% with EFD) which can also explain some of the degradation of PS normal paging with more volume of URA
Paging Ps normal is also affected by the enhanced Paging Release for Rel7+ devices CRE128146
60
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
61
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
At&t
The calculation based RAB and TMU load shows that the feature could improve the RNC capacity, which also
shifted the limiting factor of KC RNC-09 from TMU limited back to RAB limited in UA08.1. we can also observe a
higher limit of the normalized variable the throughput
* Provided by Ching-Roung Chou
62
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
63
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
Non regression
analysis
64
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t A1TA
CDR PS /KPI13
For ATT the impact of FD was a degradation of 0.03% while for A1TA the CDR PS has an impact during the activation of FD and EFD on
September can go up to 0.08%. However the activation of FD2 only in October do reveal a much lower impact (0.01%).
1.
The main cause of these impacts are inn both cases the increase of FACh drops which were mainly caused by higher fach usage and Cell
Reselection failure which increase significantly with FD/URA AR 4153335
2.
There are more failures on the HHO 3g2g_PS correlate with the EFD activation, this scenario is rare and was not caught on traces
3.
the PS00 Drops it is correlated with the usage of CS+PS00 which drop the ps connection in case of HHO 3g2g
The CSSR Cs/KPI14 performance remains almost unchanged with FD, however there are a few small impacts
1.
RRC are reduced around and this can cause a small impact on the success rate the highest impacts observed on RRC013 were of 0.03% or
0.09% for ATT market where the decrease of RRC is more significative
2.
For A1TA the impact on IuSccp ConnSuc rate is deteriorated with FD due to more URA usage, but it is not the cause of it, the Paging Repetition
fallback reveal the source of this degradation together with URA usage this scenario is still under investigation : AR 1-4108755 under
investigation
3.
The RAB success rate RAB011_CS is not affected by FD and remains unchanged
The RRC can have impacts up to 0.08% (0.15% in Sept) of degradation however it was shown that this is a impact due to lower RRC attempts
and consequently a higher percentage of bad radio conditions ues forced this distribution to be slightly affected and produce this impact
2.
The Security mode command impact is transparent to FD as it is mainly caused by two Node B G895 and G552
3.
The RAb assignment stage is also affected in August and in September (0.1% at worse cases with EFD enabled), however no impact is seen in
October, because the concept of accessibility should be enlarged also to the PCH to FACH/DCH reconfigurations an additional accessibility
formula should be considered to evaluate URA/FD networks (RAB017_URA is available on our UA8 indicators and detailed in backup).
In terms of remaining impacts of non regression there was a slight improvement on UCU usage by using FD2, however the same observation was not
confirmed in A1TA. Other Resources metrics do not reveal any impact with FD2(CEM, Power, ULLOad, throughput , traffic, bler).
65
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
25000
Uon
EDCH
FD1
FD2
AO R HS;DT@128
FD4 I/0
KC9
FD3
FD3off
PagingRep
20000
15000
10000
5000
0
15Jun
18Jun
21Jun
24Jun
27Jun
30Jun
3Jul
6Jul
9Jul
12Jul
15Jul
18Jul
21Jul
24Jul
27Jul
30Jul
2Aug
5Aug
8Aug
11Aug
14Aug
17Aug
20Aug
23Aug
26Aug
29Aug
1Sep
4Sep
7Sep
10Sep
13Sep
At&t
VS_IuAbnormalReleaseRequestPs_DlAsCnfTrbCellFa
67
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
69
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
16000
FD2
FD3
FD2_T323 Fdoff
GQ07
FD2
A1TA
UA0813EP3
40000
14000
35000
12000
30000
10000
25000
8000
20000
6000
15000
4000
10000
2000
5000
VS_IuReleaseReqPs_DlRLCErrSRB(U599_8)(Event)
VS_IuReleaseReqPs_RadioCnxUeLost(U599_6)(Event)
VS_IuReleaseReqPs_ReleaseDueToUtranGeneratedReason(U599_14)(Event)
VS_IuReleaseReqPs_UlRLCErrSRB(U599_9)(Event)
16Oct
14Oct
15Oct
13Oct
12Oct
11Oct
9Oct
10Oct
8Oct
7Oct
6Oct
5Oct
4Oct
3Oct
2Oct
1Oct
30Sep
29Sep
28Sep
27Sep
26Sep
25Sep
24Sep
23Sep
22Sep
21Sep
20Sep
19Sep
18Sep
17Sep
16Sep
15Sep
14Sep
13Sep
12Sep
11Sep
0
10Sep
VS_IuReleaseReqPs_UnspecifiedFailure(U599_3)(Event)
Main causes of PS drops that are shifting with FD are ReleaseDueToUGR which increase this can be due to extra
reconfigurations failures after failing reconfiguration timer T361 this is mainly affected by EFD (+2K FD; +5K EFD)
Another high runner cause is the unspecified failures with high increase of 5 to 7K for the worse days with EFD
correlated with higher drops on irat HO to 2g of Cs+ps00
Then there are ULRLCSRBErr which have a an impact on Global RNC but after removing the Critical node Bs we have a
negligible increase (~+500 failures Also on the last activation of FD only, it was not observed an increase by comparing
with the reference days of 27 and 28 Sept
70
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
800
FD2
FD3
GQ07
FD2_T323 Fdoff
FD2
A1TA
UA0813EP3
3500
700
3000
600
2500
500
2000
400
1500
300
1000
200
500
100
0
VS_IuReleaseReqPs_RepeatedIntegrityCheckFailure(U599_4)(Event)
VS_IuReleaseReqPs_T360Expiry(U599_12)(Event)
VS_IuReleaseReqPs_UtranPageFail(U599_20)(Event)
VS_IuReleaseReqPs_UlRLCErrTRB(U599_11)(Event)
VS_IuReleaseReqPs_CellReselFail(U599_19)(Event)
VS_IuReleaseReqPs_DlRLCErrTRB(U599_10)(Event)
VS_IuReleaseReqPs_FailureInTheRadioInterfaceProcedure(U599_16)(Event)
16Oct
14Oct
VS_IuReleaseReqPs_AbnormalConditionTimerRelocExpiry(U599_7)(Event)
15Oct
13Oct
12Oct
11Oct
10Oct
9Oct
8Oct
7Oct
6Oct
5Oct
4Oct
3Oct
2Oct
1Oct
30Sep
29Sep
28Sep
27Sep
26Sep
25Sep
24Sep
23Sep
22Sep
21Sep
20Sep
19Sep
18Sep
17Sep
16Sep
15Sep
14Sep
13Sep
12Sep
11Sep
10Sep
For the remaining causes of PS drop we have more Cell reselection failures; There is a AR 4153335 to address some scenarios of
Cell reselections failures With priority for FD specifically but it should be evaluated for a general URA behavior compare with
589_7 on next slide, it increases around 800 to 1K
There is also more UL and DL err in TRB (specially DL and mainly affected by EFD) ~+ 500 so the nominal configuration was not
affected (FD only)
More Utran page fail associated with Fast Dormancy extended also seen on the Enhanced URA Paging feature ratio of RNTI success vs
TMSI Success (~+ 200) (see in backup)
There is still the case of VS_IuReleaseReqPs_AbnormalConditionTimerRelocExpiry(U599_7)(Event) which increases on a small amount of
samples
71
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
There are more failures on the HHO 3g2g_PS correlate with the EFD activation
The extra failures correspond to approx 600 events
This scenario does not have traces captured and so investigation can not proceed
72
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
A1TA
Regarding the PS00 Drops it is correlated with the usage of CS+PS00 vs HHO 3g2g. So in case of HHO to 2G of CS call the PS00 is
released
Below we can see the increase of drops on PS 00 correlated with the drop PS due to CS irat HHO. The missing gap between counters
#2680 and #589_0 corresponds to the gap between CS+PS_HS where the screening of #589_HSDPA should be pegged.
73
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
FD3
FD3off
99.70%
99.50%
99.30%
99.10%
98.90%
98.70%
RRCConnectionSuccessRateExcRep_RRC021_CR_Cs(URRC021_CR_Cs)(%)
Uon
CSSRBRetainability
13Sep
10Sep
7Sep
4Sep
1Sep
29Aug
26Aug
23Aug
20Aug
17Aug
14Aug
11Aug
kpi32a
KPI14w/nbr
FD4 I/0
KC09AO R HS;DT@128
EDCH
PagingRep
FD3
FD1
FD3off
FD2
0.995
8Aug
5Aug
2Aug
30Jul
27Jul
24Jul
21Jul
18Jul
15Jul
9Jul
12Jul
6Jul
3Jul
30Jun
27Jun
24Jun
21Jun
18Jun
15Jun
98.50%
0.99
0.985
0.98
0.975
0.97
KPI14UA8RRCModified
74
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
KPI14w/nbr
13Sep
10Sep
7Sep
4Sep
1Sep
29Aug
26Aug
23Aug
20Aug
17Aug
14Aug
11Aug
8Aug
5Aug
2Aug
30Jul
27Jul
24Jul
21Jul
18Jul
15Jul
12Jul
9Jul
6Jul
3Jul
30Jun
27Jun
24Jun
0.965
21Jun
FD4 I/0
KC09 AO R HS;DT@128
EDCH
FD1
FD2
99.90%
18Jun
Uon
15Jun
At&t
0.999
FD4 I/0
KC09 AO R HS;DT@128
EDCH
FD3off
FD2
0.9985
PagingRep
FD3
FD1
0.998
0.9975
0.997
0.9965
0.996
13Sep
10Sep
7Sep
4Sep
1Sep
29Aug
26Aug
23Aug
20Aug
17Aug
14Aug
11Aug
8Aug
5Aug
2Aug
30Jul
27Jul
24Jul
21Jul
18Jul
15Jul
12Jul
9Jul
6Jul
3Jul
30Jun
27Jun
24Jun
21Jun
18Jun
15Jun
0.9955
KPI32aUA81
Uon
600
EDCH
FD1FD2
FD3
FD3off
KC09 FD4 I/0
AO R HS;DT@128
PagingRep
20000
500
15000
400
300
10000
200
5000
100
RAB_FailEstab_CS_RBSetupExp(U2629_8)(Event)
RAB_FailEstab_CS_RLFailNodeBErr(U2629_4)(Event)
RAB_FailEstab_CS_RLFailOther(U2629_3)(Event)
RAB_FailEstab_CS_ULLoad(U2629_0)(Event)
RAB_FailEstab_CS_LackTranspRsrc_NeighbRnc(U2761)(Event)
RAB_FailEstab_PS_DLPwr(U2631_1)(Event)
75
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
RAB_FailEstab_CS_RBSetupFail(U2629_7)(Event)
RAB_FailEstab_CS_RLFailNodeBResource(U2629_5)(Event)
RAB_FailEstab_CS_RLReconfigExp(U2629_6)(Event)
RAB_FailEstab_CS_LackTranspRsrc(U2762)(Event)
RAB_FailEstab_PS_CodeStarv(U2631_2)(Event)
13Sep
10Sep
7Sep
4Sep
1Sep
29Aug
26Aug
23Aug
20Aug
17Aug
14Aug
11Aug
8Aug
5Aug
2Aug
30Jul
27Jul
24Jul
21Jul
18Jul
15Jul
12Jul
9Jul
6Jul
3Jul
30Jun
27Jun
24Jun
21Jun
0
18Jun
0
15Jun
Include
76
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
A1TA
PagingRep
FD3
FD3off
FD2
99.7%
99.5%
99.3%
99.1%
98.9%
98.7%
13Sep
7Sep
10Sep
4Sep
1Sep
29Aug
26Aug
23Aug
20Aug
17Aug
14Aug
11Aug
8Aug
5Aug
2Aug
30Jul
27Jul
24Jul
21Jul
18Jul
15Jul
12Jul
9Jul
6Jul
3Jul
30Jun
27Jun
24Jun
21Jun
18Jun
98.5%
RRCConnectionSuccessRateExcRep_RRC021_CR_Ps(URRC021_CR_Ps)(%)
Uon
EDCH
FD1
FD2
FD4 I/0
KC09AO R HS;DT@128
PagingRep
FD3
FD3off
0.999
0.998
0.997
0.996
KPI35psUA8RRCModified
78
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
KPI16UA8RRCModified
13Sep
10Sep
7Sep
4Sep
1Sep
29Aug
26Aug
23Aug
20Aug
17Aug
14Aug
11Aug
8Aug
5Aug
2Aug
30Jul
27Jul
24Jul
21Jul
18Jul
15Jul
12Jul
9Jul
6Jul
3Jul
30Jun
27Jun
24Jun
0.995
21Jun
99.9%
18Jun
FD4 I/0
KC09 AO R HS;DT@128
EDCH
FD1
15Jun
Uon
15Jun
At&t
Uon
FD4 I/0
KC09AO R HS;DT@128
EDCH
PagingRep
FD3
FD1
0.999
At&t
FD3off
FD2
0.997
0.989
0.987
UEStateTrans_UraPCH_CellDCH_Successrate
Uon
50000
13Sep
10Sep
7Sep
4Sep
1Sep
29Aug
26Aug
23Aug
20Aug
17Aug
14Aug
11Aug
8Aug
5Aug
2Aug
30Jul
UEStateTransSucc_PCH_FACHsuccessrate
Kpi33rabassignment_R
FD4 I/0
KC09AO R HS;DT@128
EDCH
PagingRep
FD3
FD1
45000
27Jul
24Jul
21Jul
18Jul
15Jul
12Jul
9Jul
6Jul
3Jul
30Jun
27Jun
24Jun
21Jun
18Jun
15Jun
0.985
FD3off
FD2
40000
35000
30000
25000
20000
15000
10000
5000
failures(attsuc)PCH2FACH
79
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Failures(Attsucc)URAPCH2DCH
13Sep
10Sep
7Sep
4Sep
1Sep
29Aug
26Aug
23Aug
20Aug
17Aug
14Aug
11Aug
8Aug
5Aug
2Aug
30Jul
27Jul
24Jul
21Jul
18Jul
15Jul
12Jul
9Jul
6Jul
3Jul
30Jun
27Jun
24Jun
0
21Jun
0.991
18Jun
0.993
15Jun
0.995
RABassignmentFailure C
A1TA
The PS Success rate is severely affected by FD and above all by EFD. By comparing with second Activation on 1st
October we can conclude that previous activations was also impacted by some degraded NodeBs
There is a degradation around 0.5% overall, however the next slides will breakdown this indicator to its
components while showing the impact of each one as well as some special Node B which contribute with more
degradation
80
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
The RRC degradation is quite clear for the PS (ranges from .1% to .15%) in september and 0.08% in F6, while it
reduces the number of attempts and failures it becomes difficult to prove the true reason for this degradation.
The hypothesis formulated here is that it is related with the different distributions of attempts which will experience
worse radio conditions (eventually calls dismissed from URAPCH state) which will now increase the number of poor radio
conditions set of calls for RRC. This can also affects the subsequent stages of call setup to prove this hypothesis will be
the objective of next slides
The same is not observed for Cs calls as they are much less affected by URA due to smaller RRC volume reduction
produced by PCH state
81
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
A1TA
A1TA
The quick repetition of the RRC Connection Setup is activated based on the P-CPICH Ec/No (bydefault) or
RSCP measurement received from the RRC Connection Request message reported by the UE. If these quality
measurements are below a given threshold (-10dB for A1)
The higher usage of Algorithm of RRCQuickRepetition provide another piece on the prove to sustain that the
radio conditions are degraded for the new amount of calls attempting to get a rrc connection PS
84
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
The bottom charts were taken from RRC connection request msgs containing the RF EC/No & the Propagation
delay Distribution of traces taken as reference (NO FD) and traces taken with FD & EFD activated
The results are pretty clear showing a wider PDF function when the FD & EFD are activated (or a slower rising
CDF function, which means that there are now more frequent samples with lower radio conditions
The charts below and the previous ones presented on above slides are enough to validate our Hypotehsis The
RRC lower success rate is a consequence of worse radio conditions UEs attempting on the PS RRC
85
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
A1TA
At&t
The EDCh optim has a big impact on UCU usage decreasing the 2ms and increasing the other configurations (R99; EDCH
10ms and HSDPA) this is expected.
The FDStep2 have decrease effect (R99; EDCH 10ms and HSDPA) due to more users going thru the FACH and less DCh
observed
The HSDPA ReleaseOnly will put back the effect of FDStep2 taking more UCU resources
25
Uon
KC09
EDCH
FD1
AO_R_HS;DT@128
FD4 I/0
PagingRep
FD3
FD2
FD3off
20
15
10
15Jun
17Jun
19Jun
21Jun
23Jun
25Jun
27Jun
29Jun
1Jul
3Jul
5Jul
7Jul
9Jul
11Jul
13Jul
15Jul
17Jul
19Jul
21Jul
23Jul
25Jul
27Jul
29Jul
31Jul
2Aug
4Aug
6Aug
8Aug
10Aug
12Aug
14Aug
16Aug
18Aug
20Aug
22Aug
24Aug
26Aug
28Aug
30Aug
1Sep
3Sep
5Sep
7Sep
9Sep
11Sep
13Sep
VS_RF_ChanElementUsageUCU_EDCH_10ms_Mean_ONB(U35094)(%)
VS_RF_ChanElementUsageUCU_EDCH_2ms_Mean_ONB(U35096)(%)
VS_RF_ChanElementUsageUCU_EDCH_Mean_ONB(U35064)(%)
VS_RF_ChanElementUsageUCU_HSDPA_Mean_ONB(U35066)(%)
VS_RF_ChanElementUsageUCU_R99_Mean_ONB(U35062)(%)
88
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
89
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
At&t
105.2
Uon
EDCH
FD1FD2
KC09
FD3
FD4 I/0
PagingRep
0.007
FD3off
AO_R_HS;DT@128
105.3
0.006
105.4
0.005
105.5
0.004
105.6
0.003
105.7
0.002
105.8
0.001
105.9
106
15Jun
17Jun
19Jun
21Jun
23Jun
25Jun
27Jun
29Jun
1Jul
3Jul
5Jul
7Jul
9Jul
11Jul
13Jul
15Jul
17Jul
19Jul
21Jul
23Jul
25Jul
27Jul
29Jul
31Jul
2Aug
4Aug
6Aug
8Aug
10Aug
12Aug
14Aug
16Aug
18Aug
20Aug
22Aug
24Aug
26Aug
28Aug
30Aug
1Sep
3Sep
5Sep
7Sep
9Sep
11Sep
13Sep
UplinkRSSI_ULOAD002_CR_Avg(UULOAD002_CR_Avg)(dBm)
PercentageMaximumWidebandReceivedPower_ULOAD018_CR_ONB(UULOAD018_CR_ONB)(%)
90
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
No impact observed on UL Load correlated with FD activation, the indicator have big variations
but not correlated with FD
91
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
Uon
FD4 I/0
KC09 AO R HS;DT@128
EDCH
24.0%
PagingRep
FD3
FD1
FD3off
FD2
22.0%
20.0%
18.0%
16.0%
14.0%
12.0%
13Sep
10Sep
7Sep
4Sep
1Sep
29Aug
26Aug
23Aug
20Aug
17Aug
14Aug
11Aug
8Aug
5Aug
2Aug
30Jul
27Jul
24Jul
21Jul
18Jul
15Jul
9Jul
12Jul
6Jul
3Jul
30Jun
27Jun
24Jun
21Jun
18Jun
15Jun
10.0%
AverageHSDPAPowerused_HSDPA010_CR_ONB(UHSDPA010_CR_ON
FD4 I/0
KC09AO R HS;DT@128
PagingRep
FD3
Percentage_NonHS_PowerUsed_Power001_B_Avg_ONB(UPower001_B_Avg_O
92
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
13Sep
10Sep
7Sep
4Sep
1Sep
29Aug
26Aug
23Aug
20Aug
17Aug
14Aug
11Aug
8Aug
5Aug
2Aug
30Jul
27Jul
FD3off
24Jul
21Jul
18Jul
15Jul
12Jul
9Jul
6Jul
3Jul
30Jun
EDCH
FD1
FD2
27Jun
21Jun
18Jun
24Jun
Uon
30
29
28
27
26
25
24
23
22
21
20
15Jun
93
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
At&t
Uon
0.33%
KC09
EDCH
PagingRep
FD3
FD1
0.31%
AO_R_HS;DT@128
FD4 I/0
FD3off
FD2
0.29%
0.27%
0.25%
0.23%
0.21%
0.19%
0.17%
CsVoiceUplinkBLER_BLER012_CR(UBLER012_CR)(%)
94
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
13Sep
11Sep
9Sep
7Sep
5Sep
3Sep
1Sep
30Aug
28Aug
26Aug
24Aug
22Aug
20Aug
18Aug
16Aug
14Aug
12Aug
8Aug
10Aug
6Aug
4Aug
2Aug
31Jul
29Jul
27Jul
25Jul
23Jul
21Jul
19Jul
17Jul
15Jul
13Jul
11Jul
9Jul
7Jul
5Jul
3Jul
1Jul
29Jun
27Jun
25Jun
23Jun
21Jun
19Jun
17Jun
15Jun
0.15%
95
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
Part C
Conclusions and
recommendation
for activation
96
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
The setting of Fast Dormancy feature providing more benefits and less constraints is the activation of R6R7R8 Fast
Dormancy (without extended fast Dormancy).
ExtendedFD proved to increase further the gains of FastDormancy but in A1TA there were impacted end users
affected KPIs The usage of a filtering procedure based on IMEI is currently under internal evaluation to answer
some customer requests.
The usage of AOMode=releaseOnly for EDCH & HSDPA confs, provide some benefits in terms of KPIs and FACH
usage but also prove to take more resources on NodeB.
Regarding the other related parameter tests executed in parallel with the feature:
1.
The T323 can be reduced to less than 30 secs. this will save some FACH usage and theoretically some DCH however this was very
hard to observe on A1TA FOA. On the other hand it can also increase the number of state transitions.
The gains in CPU are small but consistent it presnets a gain of 8% for A1TA and 9 % for ATT, while in ATT FD +URA
could produce combined gains up to 21%
Other gains are also observed on the Reduction of RRC and RAB establishment PS, reduction on PS Paging load from
SGSN and latency reduction for PS users
Although there are a long and complex non regression analysis , the feature is considered as validated even if there
are side effects produced by it, namely:
1.
Higher Ps drops in fach mainly produced by higher FACH usage and Cell reselection failure AR 4153335
2.
Iusccp connsuc rate CS affected due to a particular combination of features FD/URA and Paging repetition. This investigation is still
on going AR 1-4108755. However the issue is not related with FD even if it can be further increased by FD
3.
There are a much different distribution of RRC in PS and at a lower extend as well in CS which affect the Success rate metrics,
however without impact on user. Also for ATT some special metrics were proposed.
4.
Paging Evaluation should be closely monitored if possible with access to CN statistics under stable periods of operation in order to
have a reliable assessment.
97
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Reference Document
FD FSM:
https://wcdma-ll.app.alcatellucent.com/livelink/livelink.exe?func=ll&objId=64033308&objAction=browse&viewType=1
FD FA (ATT):
https://wcdma-ll.app.alcatellucent.com/livelink/livelink.exe?func=ll&objId=66463018&objAction=browse&viewType=1
FD FA (A1TA)
https://wcdma-ll.app.alcatellucent.com/livelink/livelink.exe?func=ll&objId=66349022&objAction=browse&viewType=1
SmartPhone features workgroup webpage
https://wcdma-ll.app.alcatellucent.com/livelink/livelink.exe?func=ll&objId=66326569&objAction=browse&sort=name
98
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Backup Slides
99
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
isFastDormancyAllowed
Object
RadioAccessService
RAN Path
RNC / RadioAccessService
Granularity
RNC
Customer, 3-a2
Value
100
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
ueVersionForScri
Object
RadioAccessService
RAN Path
RNC / RadioAccessService
Granularity
RNC
Customer, 3-a2
Value
R6_R7_R8 3GPP R6, R7, R8 and later UE versions are applicable for Fast Dormancy
pre_R8 3GPP R8 and earlier UE versions are applicable for Fast Dormancy
R7_R8 3GPP R7, R8 and later UE versions are applicable for Fast Dormancy
R8 3GPP R8 and later UE versions are applicable for Fast Dormancy
This parameter will not limit the extended Fast Dormancy, it is just needed to enforce the release of UE
under Fastdormancy domain of activity
101
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Parameter
t323
Object
RadioAccessService / UeTimerCstConnectedMode
RAN Path
RNC / RadioAccessService
Granularity
RNC
Customer, 3-a1
Value
T323_30
102
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
isExtendedFastDormancyAllowed
Object
RadioAccessService
RAN Path
RNC / RadioAccessService
Granularity
RNC
Customer, 3-a2
Value
pchRrcStates: Parameter for enabling Cell/URA_PCH (UA5), also defines the target RRC state
when a RRC transition triggered by Fast Dormancy occurs
103
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
The traffic in CellDCH is reducing slightly, this small reduction is typical of URA increase when some more UEs will remain between URA and FACH,
avoiding this way the usage of CellDCH.
The Amount of reduction observed on September activations is around 10%. The low Buffer thresholds will not allow much traffic being carried out
in FACH.
The main objective of T323 reduction was to check if we had any reduction on Cell DCH URA by triggering more frequently SCRI, however this is
not the case. Even if the DCHtoURAPCH increase, it is not impacting DCH usage, as we have lower T1, the call goes either to FACH or to URA
quickly.
104
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Counter
broken
@813tap2
UE misbehavior
INTERNAL
107
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
Uon
KC9
EDCH
FD3
FD1
FD2
FD4 I/0
PagingRep
At&t
120.%
AO_R_HS;DT@128
FD3off
100.%
200000
80.%
150000
60.%
100000
40.%
50000
20.%
0
15Jun
17Jun
19Jun
21Jun
23Jun
25Jun
27Jun
29Jun
1Jul
3Jul
5Jul
7Jul
9Jul
11Jul
13Jul
15Jul
17Jul
19Jul
21Jul
23Jul
25Jul
27Jul
29Jul
31Jul
2Aug
4Aug
6Aug
8Aug
10Aug
12Aug
14Aug
16Aug
18Aug
20Aug
22Aug
24Aug
26Aug
28Aug
30Aug
1Sep
3Sep
5Sep
7Sep
9Sep
11Sep
13Sep
.%
VS_UEStateTransSucc_FACH_CellDCH_CsCallSetup(U2808)(Event)
VS_UEStateTransSucc_PCH_CellDCH_CSsetup(estimation:#982#2948#2826)
StateTransitionSuccessRateFachToDch_ST005_CR(UST005_CR)(%)
StateTransitionSuccessRateFachToDch_ST005_CR(CScallsetup)
The global DT which increase in KC09 we can observe that the success rate decreases mainly after
Ua813 due to known AR 1-4036297
The global success rate however remains the same, we can even observe a small increase with more
triggering, but over all value is around 98.89%
108
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
The split of CS call setup from URA is also increase proportionally to the usage of URA
The success rate of ST005 referred to CS setup over FACH is also affected by the extra cac failure
referred before affecting the EDCH Upsize configuration.
109
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
The Cell Update components have mainly 4 changes all related with more Ura usage and FD impact:
UlDataTx which is a direct consequence of more URA PCH users
UL Paging response due to more Ues in URA which will answer to paging
Cell reselection is reducing mainly after Ao ReleaseONly parameter modification, this cause is mainly
correlated with FACH usage
Re-entered service Area is decreasing, but not entirely correlated with URA, it is more related with
FACH usage
KC9
EDCH
FD2
Uon
FD1
6000000
FD3
AO_R_HS;DT@128
FD4 I/0
PagingRep
FD3off
1
0.99
5000000
0.98
0.97
4000000
0.96
3000000
0.95
0.94
2000000
0.93
0.92
1000000
0.91
0
15Jun
17Jun
19Jun
21Jun
23Jun
25Jun
27Jun
29Jun
1Jul
3Jul
5Jul
7Jul
9Jul
11Jul
13Jul
15Jul
17Jul
19Jul
21Jul
23Jul
25Jul
27Jul
29Jul
31Jul
2Aug
4Aug
6Aug
8Aug
10Aug
12Aug
14Aug
16Aug
18Aug
20Aug
22Aug
24Aug
26Aug
28Aug
30Aug
1Sep
3Sep
5Sep
7Sep
9Sep
11Sep
13Sep
0.9
VS_NbrCellUpdates_CellReselection(U901_0)(Event)
VS_NbrCellUpdates_PagingResponse(U901_3)(Event)
110
VS_NbrCellUpdates_UplinkDataTransmission(U901_2)(Event)
CellUpdateSuccessRate_RL019_CR
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
111
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
112
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
113
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
60.%
40.%
FD3
FD4 I/0
PagingRep
AO_R_HS;DT@128
35.%
30.%
25.%
20.%
30.%
15.%
20.%
10.%
10.%
5.%
.%
RatioOfMultiRABCSPStoTotalCSTraffic_RL059_CR(URL059_CR)(%)
Uon
KC9
EDCH
FD1FD2
13Sep
10Sep
7Sep
4Sep
1Sep
29Aug
26Aug
23Aug
20Aug
17Aug
14Aug
11Aug
8Aug
5Aug
2Aug
30Jul
27Jul
24Jul
21Jul
18Jul
15Jul
12Jul
9Jul
6Jul
3Jul
30Jun
27Jun
24Jun
21Jun
18Jun
.%
RatioOfMultiRABCSPStoTotalPSTraffic_RL058_CR(URL058_CR)(%)
FD4 I/0
PagingRep
FD3 FD3off
AO_R_HS;DT@128
300000
1200
13Sep
10Sep
7Sep
4Sep
29
26
23
20
0
1Sep
VS_RABEstabPSWithCSPresent(U2707)(Event)
17
14
11
8Aug
VS_RABEstabCSWithPSPresent(U2706)(Event)
5Aug
2Aug
114
30Jun
27Jun
24Jun
21Jun
30Jul
200
27Jul
50000
24Jul
400
21Jul
100000
18Jul
600
15Jul
150000
12Jul
800
9Jul
200000
6Jul
1000
3Jul
250000
18Jun
FD3off
KC9
EDCH
FD2
FD1
50.%
15Jun
Uon
15Jun
expected behavior
At&t
VS_RABRelCSWithPSPresent(U2708)(Event)
A1TA
115
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Uon
KC9
FD3off
EDCH
FD3
FD4 I/0
At&t
PagingRep
100.0%
AO_R_HS;DT@128
FD1
200000
99.80%
FD2
150000
99.60%
100000
99.40%
50000
99.20%
99.0%
15Jun
17Jun
19Jun
21Jun
23Jun
25Jun
27Jun
29Jun
1Jul
3Jul
5Jul
7Jul
9Jul
11Jul
13Jul
15Jul
17Jul
19Jul
21Jul
23Jul
25Jul
27Jul
29Jul
31Jul
2Aug
4Aug
6Aug
8Aug
10Aug
12Aug
14Aug
16Aug
18Aug
20Aug
22Aug
24Aug
26Aug
28Aug
30Aug
1Sep
3Sep
5Sep
7Sep
9Sep
11Sep
13Sep
RBReconfigDataActivity_RB033_C_0kbpsToDchHsdsch(URB033_C_0kbpsToDchHsdsch)(Event)
RBReconfigDataActivity_RB033_C_0kbpsToEdchHsdsch(URB033_C_0kbpsEdchHsdsch)(Event)
RBReconfigDataActivity0kbps_URB038_C_0kbpsToDchHsdsch(URB038_C_0kbpsToDchHsdsch)(%)
RBReconfigDataActivity0kbps_URB038_C_0kbpsToEdchHsdsch(URB038_C_0kbpsToEdchHsdsch)(%)
On the PS00 we have more reconfigurations to HSDPA/R99 since the ues CS+EDCH is not active
At the activation of all features, also CS+EDCH is enabled and the reconfs from CS+PS00 towards CS+EDCH
increase
116
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
On the PS00 we have more reconfigurations to EDCH since the ues HSDPA are still not addressed on current UEVersionForSCRI of FD
The small degradation observed on the success rate of Cs+PS00 uspize is correlated with FD as the volume of Uspizes of EDCH is also
larger. Also there is an impact on the success rate depending on the activation of the Feature EDCH retain ability (PM125855).
However the success rate of this upsize transition is already presenting a very good performance better than 99.95%
It is also important to mention that not all of these failures will produce a call drop
117
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
118
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
DT .pc
fd1 2
Break
GQ07
F2.1F2.2F2.3
F2.4F3 F4F3offF5
F6
EP2
A1TA
0.25%
300000
0.20%
250000
0.15%
200000
150000
0.10%
100000
0.05%
50000
0
6Aug
7Aug
8Aug
9Aug
10Aug
11Aug
12Aug
13Aug
14Aug
15Aug
16Aug
17Aug
18Aug
19Aug
20Aug
21Aug
22Aug
10Sep
11Sep
12Sep
13Sep
14Sep
15Sep
16Sep
17Sep
18Sep
19Sep
20Sep
21Sep
22Sep
23Sep
24Sep
25Sep
26Sep
27Sep
28Sep
29Sep
30Sep
1Oct
2Oct
3Oct
4Oct
5Oct
6Oct
0.00%
RABAssignmentSuccessPerGrantedRABType_RAB022_R_Cs(URAB022_R_Cs)(Event)
_CallDropRate_IU007_R_Cs_Computed(UIU007_R_Cs_Computed)(%)
The global CDR was slightly higher on GQ07 RNC, the increase was around 0.006% for all RNC except 9 sites which were removed due to
a specific degradation identified.
The Node Bs excluded; G552; Gi01; G895 G75A; G700; G66B; G44A; G390; G915 had mainly problems of:
UL High RSSI: Gi01; G895
PS drops UL RLC SRB ERROR : G552
Leaks for EDCH & HSDPA codes / users: G75A G700 G66B G44A G390 G915
On the last activation on only FD there was no regression of CS CDR which remains stable
119
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
120
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
A1TA
In line with the previous chart we can observe here the main changes on drop contribution by detailing the components of
IuAbnormlaReleaseRequest of PS domain.
Main changes are
DLASCnfOther (PS00): however this component does not affect our users as no UP exist.
DLASCnfTRbFach: have a significant increase of drops, but quite less on last activation (only FD)
DLASCnfxPCH: this component is also not included as it is drops on PCH state
So our main increase on drop is related with more fach drops, however we already saw before that the FACH usage also increase
121
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
Looking on the drops per hour we can see that the main shift happening with EFD is the drops Per Hour on FACH.
The PS00 components have an increase with FD as well and this will be correlated with the usage of more HHO in case of
CS+PS00 (explained below)
The HSDPA drop per Erlang (only valid after EP2 where the counters 1666 were fixed) remains stable without EFD
The FACH drop is also correlated with any change on FD or EFD
122
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
At&t
The impact produced on RRC was considered as not user impacting but just a consequence of a different
failure distribution, ATT porpose to use different set of formulas to take that into account
RAB Success = RAB Succ / RAB Atts
SRB Retain = RAB Atts / (RAB Atts + (SRB Failure Rate * RRC Assigns))
RRC Success = (RAB Atts + (SRB Failure Rate * RRC Assigns)) / (RAB Atts + (SRB Failure Rate * RRC
Assigns) + RRC Fails)
Total Accessibility = RAB Succ / (RAB Atts + (SRB Failure Rate * RRC Assigns) + RRC Fails)
1
Uon
KC09
EDCH
FD1
FD2
AO_R_HS;DT@128
FD4 I/0
PagingRep
FD3
FD3off
0.998
0.996
0.994
0.992
15Jun
17Jun
19Jun
21Jun
23Jun
25Jun
27Jun
29Jun
1Jul
3Jul
5Jul
7Jul
9Jul
11Jul
13Jul
15Jul
17Jul
19Jul
21Jul
23Jul
25Jul
27Jul
29Jul
31Jul
2Aug
4Aug
6Aug
8Aug
10Aug
12Aug
14Aug
16Aug
18Aug
20Aug
22Aug
24Aug
26Aug
28Aug
30Aug
1Sep
3Sep
5Sep
7Sep
9Sep
11Sep
13Sep
0.99
123
KPI35 CS
KPI35csUA8RRCModified
The SMC seems affected by EFD and in some days of FD. However when looking on a longer time
scale there is no major impact attributed to FD settings. The total avg periods show a global
impact of less than 0.01%
There is one day of severe degradation on this indicator due to global problems on network at
1Am
124
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
A1TA
126
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
A1TA
The first chart on this slide refer to the signaling stage of the call establishment from the state PMM
idle.
It show a small degradation observed during the ExtendFD but not fully correlated as there were a few
sites with specific problems
Not reproduced after last activation
127
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
A1TA
The SMC SR for PS seems to be affected even if the impact is very small (0.02%)
The main impact observed is on the success rate during the Extended FD. The remaining period where simply FD is on going,
there is no obvious degradations specially when observing SRB retainability on the cluster without the high runner NBs.
The main culprit NODe Bs are G895 and G552
The degradation is not related with FD as it remains even on periods with FD off observed to be recovered after EP3
128
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION