Orange Kenya RAN Presentation Ethio DAY TWO v1.0

Orange TKL - RAN
Meeting Orange TKL – Ethio Telecom

RAN presentation
Radio Access Network Department
17th of May, 2012
AGENDA
2 Orange TKL/ Ethio Telecom - RAN presentation

Agenda – DAY 2 - Morning
Swap Strategy
Swap procedure and guidelines
Specific QoS and KPIs follow-up for swap
Best Practices/Lessons learned

Agenda – DAY 2 - Afternoon
3G KPIs and dashboards

3G parameters templates
Dual Carrier Strategy
3G best practices

DAY 2 – MORNING SESSION

Swap Strategy
Specific QoS and KPIs follow-up for swap.

Swap Strategy
2G Swap 1:1 + preparation to introduction of 3G

– Preliminary surveys
– Swap of dual band antennas to tri-band antennas
– Installation of 3G RRU
– Transmission upgrade
Same number of BSC
Swap performed at night except hot swap locations (access
issues – security/landlord requirements…)

Swap Strategy: 3 Phases
Phase 0: pilot of 4 sites

Phase 1: sites constituting 3G footprint (211 sites – 4 BSCs)
– Greater Nairobi, East Coast, Kisumu
– 16 clusters defined and sequenced
– 15/20 sites max per cluster
– Sites within same cluster handled by same supplier and same BSC
– Classification of clusters through traffic profile (Low/Medium/High)
– Swap sequence within one BSC from Low to High traffic clusters.
– Swap achieved from 12.02.2011 to 29.04.2011
Phase 2 : Rest of the country (403 sites – 4 BSCs)

– 37 Clusters defined and sequenced: E// area, then ALU area
– Swap achieved from 14.07.2011 to 26.10.2011

2G Swap cluster sequence – Phase 0 - Pilot

2G Swap cluster sequence – Phase 1 sequence














RAN – 2G Swap cluster sequence - Coast

RAN – 2G Swap cluster sequence - Coast

Swap Strategy
Specific QoS and KPIs follow-up for swap.

Swap Strategy

Cluster lifecycle and milestones
RW: “Reference Week” 2 weeks reference to get target KPIs values from OSS and perform E2E drive test
CRR “Cluster Reference Report”: archive of all elementary counters to build required KPIs from former supplier
platform, as well as parameters, CRR with official Reference values ditributed every Monday of Swap week
SE: “Swap Event”
QC: “Quick check” reports: Daily follow-up of cluster and Site KPIs
OW: “Optimization week” : 1st complete week after Week of SE: Supplier to manage to reach KPIs targets for AW
AW: “Acceptance week”: All KPIs to be met on daily basis and on weekly value during this week. E2E drive test after is
done during this week.

Milestones and KPIs
KPIs follow-up includes KPIs subject to penalty (Px KPIs – contractual KPIs)
plus other KPIs
– Site QoS Daily KPIs follow-up up to 7 days after swap event
– Daily and weekly KPIs follow-up at cluster level till acceptance of cluster
– Worst cell list for each Px_KPIs
KPIs Network Element Granularity Target
P3_KPI: Cell downtime

Cell Minutes during SE <= 120 minutes
during swap event
1. At least one day with
CS CSSR > 99%
CS DCR < 1%
INterCelll HSR > 97%
P4_KPIs Site Daily, 48 hours after SE
Inter BTS HSR > 97%
Or
Each of P4_KPIs with max 20% degradation
compared to RW values
1. Not one day with at least one P5_KPIs
Daily and degraded
P5_KPIs Cluster
Weekly during AW 2. Weekly values for P5_KPIs not degraded
compared to RW values
1 DT during RW
P6_KPIs Cluster route DT KPIs not degraded
1DT during AW

Details of P5_KPIs – Daily objectives
Acceptance week
Cluster_XX Ref Values
2011-11-7 2011-11-8 2011-11-9 2011-11-10 2011-11-11 2011-11-12 2011-11-13
2G CSSR 98.30% 99.31% 99.12% 99.12% 99.33% 99.29% 99.19% 99.31%

2G DCR 1.50% 1.32% 1.48% 1.30% 1.29% 1.35% 1.52% 1.27%
Blockedcallrate(excludehandover) 0.10% 0.00% 0.00% 0.00% 0.00% 0.00% 0.00% 0.00%
2G Busy hour traffic (Erl) 14.2 16.7 14.4 16.1 16.8 15 14.4 14.6
2G Cumulated daily average (Erl) 176.1 202.9 186.8 195.5 212.7 192.3 167.2 149
2G HSR 94.70% 96.40% 96.42% 96.21% 96.53% 92.88% 95.71% 94.31%
2G Call Setup Success Rate – Data 93.00% 96.10% 96.83% 96.96% 97.09% 97.20% 97.28% 96.66%
UL data volume 44,518.30 96788.33 56758.88 43915.32 30316.43 39481.4 40802.12 45222.19
DL data volume 292,354.10 349248.9 318040.3 277550.32 245868.84 293111 253681.22 250713.5
DL EGPRS Throughput per TBF (LLC) 56.8 127.3 131.6 132.9 138 141.1 138.2 130.9
UL EGPRS Throughput per TBF (LLC) 19.6 74.6 57.6 54.7 55.1 60.9 55.4 61.4
DL GPRS Throughput per TBF (LLC) 35.2 40.1 40.9 39.4 39.2 39.9 41.6 42.1
UL GPRS Throughput per TBF (LLC) 12.9 16.8 12.6 15.2 14.8 13.3 15.1 16.9
P5: d d d d d

Details of P5_KPIs – Weekly objectives
Phase2_Cluster18_Phase2_Batch 18 RW OW AW PASSED?
2G CSSR CS 98.30% 99.18% 99.24% Y
2G DCR 1.50% 1.53% 1.36% Y
Blocked call rate(exclude handover) 0.10% 0.00% 0.00% Y
2G Busy hour Traffic (*) 14.2 16.4 16.8 Y
2G Cumulated Traffic (avg daily) (*) 176.1 186.6 186.6 Y
2G HSR 94.70% 97.24% 95.55% Y
2G Call Setup Success Rate – Data 93.00% 97.28% 96.80% Y
UL Data Volume (*) 44,518.3 82,592.0 50,469.2 Y
DL Data Volume (*) 292,354.1 423,178.9 284,030.6 Y
DL EGPRS Throughput per TBF (LLC) 56.8 138.4 133.9 Y
UL EGPRS Throughput per TBF (LLC) 19.6 72.2 62.5 Y
DL GPRS Throughput per TBF (LLC) 35.2 40.5 40.6 Y
UL GPRS Throughput per TBF (LLC) 12.9 16.8 14.9 Y
Number of KPIs degraded: None

Details of Cluster Drive test KPIs - CS
Metric BEFORE (RW) AFTER (AW)

Call Attempts (nb) 103 88
Call Setup failures (nb) 9 4
Call Succesful (nb) 94 84
Call Drops (nb) 4 2
Calls with Voice qual <=2.7 1 2
CBR (Call Blocking Rate) 8.74% 4.55% IMPROVED
DCR (Drop Call Rate) 4.26% 2.38% IMPROVED
E2E VOICE (voice indicator) 86.41% 90.91% IMPROVED
VQI DL MOS samples >= 3.3 92.47% 93.28% IMPROVED

Avg RxLev (dBm) -76.04 -72.97 IMPROVED
Avg RxQual 0.38 0.36 IMPROVED
Call Setup time (s) 7.77 6.94 IMPROVED

Details of Cluster Drive test KPIs - CS
Downlink Before After Delta Comments
Data Connections Attempts 38 52
Data Connections Successes 35 31
Data Connections Failures 3 21

Server is not stable lead to more connection
E2E Data Accessibility SR 92.11% 59.62% DEGRADE
failure to server
Avg.RLC throughput DL (kbit/s) 85.40 135.18 IMPROVED
83.08 127.99 IMPROVED

Avg.LLC throughput DL (kbit/s)
Uplink Before After Delta COMMENTS

Data Connections Attempts 38 52
Data Connections Successes 35 31

Data Connections Failures 3 21
Server is not stable lead to more connection
E2E Data Accessibility SR 92.11% 59.62% DEGRADE
failure to server
Avg.RLC throughput UL (kbit/s) 43.35 62.66 IMPROVED
42.11 60.86 IMPROVED

Avg.LLC throughput UL (kbit/s)

Swap Strategy

Best Practices/Lessons learned (1/2)
Preparation: > 2 months anticipation is recommended before first SE

– Poor or no templates proposed by ZTE to ensure Swap project follow-up and expected deliveries. All
deliveries to be generated
– Securisation of elementary counters to build KPIs of reference at cell level before swap to be included
in reports (CRR report). To exclude specific days with abnormal and massive degradation (fiber cuts,
power issues etc…)
– Securisation of Parameters reference archiving during RW. KEY: BDREF
– QoS tool and parameter check tool independent from Supplier is seen as mandatory, to avoid strain of
resources to ensure all deliveries. KEY: OSIRIS, BDREF.
– Parameter template: decision of which parameter to keep, or which to align to recommended values
– Provide Power TOC mapping from former supplier (done) Requirement for exact database (eesp. Pre-
SDR generation with combining, not combining issues)
– Impose Power measurement TOC former supplier (during SE) and new BTS pre-commissioned. Not
done. It would avoid debate on KPIs impacted for non exact matching of power steps.
– ZTE was requested for automatic OSS dumps generation with former supplier OSS dump and
parameters migration rules: NOT AVAILED.
– Dedicated Project Leader for swap project
– Impose Individual Site drive test to obtain reference of coverage.
– Secure Call tests template just after swap
– Mapping of KPIs done along with NAD.
– 1:1 scenario was the chosen scenario(same number of BSC even if newly introduced BSC present
much more capacity) : minimize reconfiguration and potential impact on KPIs from new Architecture

Best Practices/Lessons learned (2/2)
After Swap:
– Verification of parameters implementation. Key: BDREF
– Individual Site drive test just after swap: early detection of crossed sectors, early detection of loss of
coverage
– Only parameter tuning is allowed, no amendement of freqeuncy plan, or aerial design
KPIs impact observed:
– UL strong degradation after swap: Initial RSU deployed more sensitive to CDMA 850 DL by products.
Enhanced filtering RSU was introduced after, in line with introduction of IRC feature and AGC value
tuning
– Systematic MOS degradation. MOS was recovered by out-scope actions:
– Frequency plan and Design amendment was required to achieve same results as before swap.
– Handover per call increased with introduction of ZTE: mechanism to be further optimised.
No decisive conclusion up to today, PR still opened: ZTE products more sensitive to degraded
radio conditions(?)
KEY : OSIRIS: archive of all KPIs
– Systematic progress in PS KPIs: Introduction of new features (Dynamic Abis) + NAD formulas used
under review (Database allocation failure not accounted in CSSR PS….)
– Systematic progress in CS CSSR: SD drop formula validated by NAD under review (current
hypothesis: formula does not count SD drops after Error indication and after T200 expiry)
– ZTE : novice reaction to KPIs results and KPIs study. No notion of exclusions of specific days in AW.
– Delay in Cluster acceptance. E2E DT acceptance not yet pronounced for Phase 2.

DAY 2 – AFTERNOON SESSION


3G best practices
Q&A

3G KPIs and dashboards (1/2)
REPORT/DASHBOARD OCCURENCE NETWORK CONTENTS

ELEMENT
3G corporate KPIs Daily/weekly network NAD KPIs + specific IRAT PS for all services + Iu
CS/PS SCCP success rate (RNC level only)
3G detailed dashboard weekly RNC Accessibility/ Retainability/Traffic/
Mobility/Quality/Load/ Network availability
Split of NAD KPIs in elementary procedures and
metrics (success rate and number)
3G regional weekly follow up Daily/weekly Optimization region NAD KPIs + Main KPIs + failure causes + action
plan
3G worst cell list Daily/weekly Optimization region Failure types based on Accessibility/
Retainability/Traffic/ Mobility/RTWP/throughput
RRC Troubleshooting report On demand Cell All RRC related KPIs arranged in preparation and
execution phase.
Load and Capacity monitoring Weekly Cell/ Node B/ Iub/ Monitor keyressource usage
RNC/Iu Algorithm of threshold comparison to be fully
implemented in Osiris

3G KPIs and dashboards (2/2)
Contents and Focus:

– Articulated around main categories: Accessibility/ Retainability/Traffic/
Mobility/Quality/Load
– NAD KPIs + Self defined KPIs (Split of NAD KPIs in elementary procedures)
– Parallel presentation of Success Rate, failure rates, and number of
transactions/failures
– Ease correlation between different counters/KPIs evolution to quicken
troubleshooting
– All reports defined to be available for any Network element, or group of NE:
Easy TOP DOWN Approach.
Process of generation:
– All supporting templates predefined in Netnumen
– Export and Copy in tables
Adobe Acrobat Adobe Acrobat
– auto generated Pre-defined charts Document Document
3G corpo 3G WCL
KPIs

3G best practices
Q&A

3G Parameters template (1/2)
2 templates defined
– 3G Urban
– 3G border cell
Main differentiation: IRAT parameterization
2 Frequencies Strategy:
F1: R99+HSPA; F2: HSPA
Access layer F1
Cell reselection F1 <= F2
Load balance RRC connection setup
Service balance RRC connection setup

F1: CS+PS+HS Preferred
F2: HS Preferred
Inter-frequency The border cells of F2

Handover

3G Parameters template (2/2)
Neighbour plan Strategy

Example Site xxxMS having a
configuration S222-222-222
A 900 cell (or 1800) must be defined as
neighbour with all intra site 900 and 1800
cells, and also with all 900 and 1800
sectors
All adjacencies defined are bi-directional
intra technology
A carrier 1 cell must be defined with all
intra-site co-localised cells : 2G, carrier1
and carrier 2. The definition towards 2G is
unidirectional (outgoing).
No Carrier 2 is defined as neighbour with
2G cells.
The Carrier 1 to Carrier 2 flow is defined
only on an intra site basis.

Defined Axis of optimization of current parameter
templates
Indoor cell specific template

Improvement of Voice distortion experienced during Compressed mode
IRAT optimization: Test of Ec/Io and RSCP trigger, IRAT Based on Uplink
BLER, Uplink Transmit Power, Downlink Transmit Power
Review and optimization of bandwidth sharing, scheduling and reaction to
users numbers increase/decrease in BW sharing.
Dual Carrier parameter optimization
Power allocation optimization (RACH/FACH etc…)
3G: DRBC parameters fine tuning


3G best practices
Q&A

Dual Carrier HSDPA Dual Strategy
Feature validated with V2.4.2+ with BPK and CC16 board

Deployed in 2 clusters, 53 Node Bs
Some Requirements
– 42 Mbps guaranteed for Tx capacity to fully benefit from
feature
– Specific UE (See next slides)
F2 frequency defined as Primary, Co sector F1 defined as

secondary
Parameter template under optimization

DC-HSDPA UE categories
Max
number of MIMO, Code rate at
PROTOCOL 3GPP Release Category Modulation [Mbit/s]
HS-DSCH Dual-Cell max data rate
codes
HSDPA Release 5 1 5 16-QAM 0.76 1.2
HSDPA Release 5 11 5 QPSK 0.76 0.9
HSDPA Release 5 12 5 QPSK 0.76 1.8
HSPA+ Release 7 13 15 64-QAM 0.82 17.6
HSPA+ Release 7 14 15 64-QAM 0.98 21.1
HSPA+ Release 7 15 15 16-QAM MIMO 0.81 23.4
HSPA+ Release 7 16 15 16-QAM MIMO 0.97 28
Dual-Cell HSDPA Release 8 21 15 16-QAM Dual-Cell 0.81 23.4
Dual-Cell HSDPA Release 8 22 15 16-QAM Dual-Cell 0.97 28
Dual-Cell +
DC-HSDPA w/MIMO Release 9 25 15 16-QAM MIMO 0.81 46.7
Dual-Cell +
Dual-Cell +
Dual-Cell +


3G best practices
Q&A

3G Best practices – examples (1/2)
Review of initial settings F2 from HSDPA to HSPA

– Unnecessary transitions for R6+ UE in Upload:
– RRC service balance to F2
– Return to F1 at RAB assignment (HSUPA)
– No impact on DL throughput on F2 after change
“Share Cover” parameter impact: rules the Blind HO direction. Only reserved in inter-
freq or inter RAT of same sectors. Verified at each site integration
Specific Parameter template for Demo of maximal HSDPA throughput.
External interference identification in WCDMA UL band from CDMA DL1980 MHz
Usage of RACH access chip delay at FN8a stage to optimize overshooting
Change of SGSN parameter (Gb_N201-U_InitiateNegotiation from “1” to “0”) in line
with Skill center recommendation. Impact:
– 10% improvement in 3G2G HO PS - few % below target of 90%.
– 30% improvement in 3G2G Routing area update

3G Best practices – examples (2/2)
Base Band Processing board DSP overload detection through RRC and RAB failure
PS “due to Node B”
– Restrict coverage area
– Upgrade BPC 2 BPC or Upgrade BPC BPK
High Capitalization from 2G/3G migration KPIs follow-up following release upgrades:
product limitations, restrictions, counters usagete


3G best practices
Q&A

END OF DAY 2 SESSION

Asante, thanks

Orange Kenya RAN Presentation Ethio DAY TWO v1.0

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Orange Kenya RAN Presentation Ethio DAY TWO v1.0

Загружено:

Авторское право:

Доступные форматы

Orange TKL - RAN

Meeting Orange TKL – Ethio Telecom

2 Orange TKL/ Ethio Telecom - RAN presentation

3 Orange TKL/ Ethio Telecom - RAN presentation

3G KPIs and dashboards

4 Orange TKL/ Ethio Telecom - RAN presentation

5 Orange TKL/ Ethio Telecom - RAN presentation

6 Orange TKL/ Ethio Telecom - RAN presentation

2G Swap 1:1 + preparation to introduction of 3G

7 Orange TKL/ Ethio Telecom - RAN presentation

Phase 0: pilot of 4 sites

Phase 2 : Rest of the country (403 sites – 4 BSCs)

8 Orange TKL/ Ethio Telecom - RAN presentation

9 Orange TKL/ Ethio Telecom - RAN presentation

10 Orange TKL/ Ethio Telecom - RAN presentation

11 Orange TKL/ Ethio Telecom - RAN presentation

12 Orange TKL/ Ethio Telecom - RAN presentation

13 Orange TKL/ Ethio Telecom - RAN presentation

14 Orange TKL/ Ethio Telecom - RAN presentation

15 Orange TKL/ Ethio Telecom - RAN presentation

16 Orange TKL/ Ethio Telecom - RAN presentation

17 Orange TKL/ Ethio Telecom - RAN presentation

18 Orange TKL/ Ethio Telecom - RAN presentation

19 Orange TKL/ Ethio Telecom - RAN presentation

20 Orange TKL/ Ethio Telecom - RAN presentation

21 Orange TKL/ Ethio Telecom - RAN presentation

22 Orange TKL/ Ethio Telecom - RAN presentation

23 Orange TKL/ Ethio Telecom - RAN presentation

24 Orange TKL/ Ethio Telecom - RAN presentation

25 Orange TKL/ Ethio Telecom - RAN presentation

26 Orange TKL/ Ethio Telecom - RAN presentation

27 Orange TKL/ Ethio Telecom - RAN presentation

28 Orange TKL/ Ethio Telecom - RAN presentation

KPIs Network Element Granularity Target

P3_KPI: Cell downtime

29 Orange TKL/ Ethio Telecom - RAN presentation

2011-11-7 2011-11-8 2011-11-9 2011-11-10 2011-11-11 2011-11-12 2011-11-13

2G CSSR 98.30% 99.31% 99.12% 99.12% 99.33% 99.29% 99.19% 99.31%

30 Orange TKL/ Ethio Telecom - RAN presentation

31 Orange TKL/ Ethio Telecom - RAN presentation

Metric BEFORE (RW) AFTER (AW)

VQI DL MOS samples >= 3.3 92.47% 93.28% IMPROVED

32 Orange TKL/ Ethio Telecom - RAN presentation

Downlink Before After Delta Comments

Data Connections Attempts 38 52

Data Connections Successes 35 31

Data Connections Failures 3 21

Avg.RLC throughput DL (kbit/s) 85.40 135.18 IMPROVED

83.08 127.99 IMPROVED

Uplink Before After Delta COMMENTS

Data Connections Successes 35 31

42.11 60.86 IMPROVED

33 Orange TKL/ Ethio Telecom - RAN presentation

34 Orange TKL/ Ethio Telecom - RAN presentation

Preparation: > 2 months anticipation is recommended before first SE

35 Orange TKL/ Ethio Telecom - RAN presentation

36 Orange TKL/ Ethio Telecom - RAN presentation

37 Orange TKL/ Ethio Telecom - RAN presentation

3G KPIs and dashboards

38 Orange TKL/ Ethio Telecom - RAN presentation

REPORT/DASHBOARD OCCURENCE NETWORK CONTENTS

39 Orange TKL/ Ethio Telecom - RAN presentation

Contents and Focus:

3G KPIs and dashboards