Nokia KPI & Optimization

27& 28th Feb 2019

Bangalore, India
BASIC KPI Target

• SD Drop less than 2 %

• SD Blocking less than 1 %
• TCH drop less than 2%
• TCH assignment Success greater
than 95 %
• HOSR is greater that 95 %
• CSSR greater than 98%
• TCH Blocking less than 1%
Topics Covered

• How do we need to start Optimization

• KPI Analysis with All Raw Counters
• Root Cause
• Hardware Alarms
• Optimization ( Alarm Description & Analysis)

For escalating the Transmission and Hardware related issue we should be clear
why alarm persisting and what unit is faulty and we also first try with TRX Lock &
reset etc so that we can force to customer to replace it ASAP and For Transmission
we also need to know which KPI is affecting due to which alarm as so many alarm
persists on the BSC but only some affects the KPI and This is called Root Cause
analysis
Consistency Parameter Check
o Check cells in MSC vs cells in BSC
o Check external adjacencies in MSC
o Cells with co-channel frequencies
o Cells with adj-channel frequencies
o Non symmetrical adjacencies
o Neighbours with co-channel frequencies
o Neighbours with adj-channel frequencies
o Neighbours of a same cell with co-BSIC, co-BCCH
o Check BCCH-BSIC reuse distance
o Check BCCH reuse distance
o Check site with same MA List in different sectors and different HSN
o Check site with same MA List in different sectors and MAIO collision
o Synchronized HO
Parameter Audit
• Some major parameters might have big impact to KPI. We briefly review those parameter
to make sure at least we are not optimizing at the unreachable value.
TCH Drop
• RX diversity (RDIV) : enable/disable
• Radio Link Timeout (RLT) : higher value  less drop but more bad quality.
• Radio Link Timeout AMR (ARLT) : higher value less drop but more bad quality
SDCCH Drop and SDCCH Success Rate
• RxLev Access Minimum (RXP) : higher value  less drop and less traffic.
• C2 parameter
•  Cell reselection parameter Index (PI) – enable/disable
•  Cell barring qualify (QUA)
•  Cell reselect offset (REO) : less value  less drop and less traffic.
•  Temporary offset (TEO)
•  Penalty time (PET)
Parameter Audit-2
•RX lev min cell (SL)
• With this parameter you define the minimum signal level of an adjacent cell,
when a handover is allowed to one of them.
HO margin level (LMRG)
• Must consider HOC parameters
• threshold level downlink Rx level (LDR)
• threshold level uplink Rx level (LUR)
HO margin qual (QMRG)
• Must consider HOC parameters
• threshold qual downlink Rx qual (QDR)
• threshold qual uplink Rx qual (QUR)

Warning! You can reduce the LMRG and QMRG to allow quickly handover but make
sure the target cell signal strength and quality is good enough to avoid handover
failure and drop call.
Parameter Audit-3

• Design default sets

• Consistency Checks
1. Compare network design against network configuration
• Default Parameter Check
• Specific Parameter Check
2. Database check
• Check inconsistencies between TRX, BTS table with ADCE table:
• Check Adjacencies to non-existing cells
• Consistency parameter checking
3. Neighbour cells with co-BSIC, co-BCCH ...
• Review Neighbour Plan
• Review Frequency Plan
Examples of wrong parameter set with impact
on
network operation/performance – call setup,
qual,
• No calls happening in a cell
• 1. Cell Barred
bands
• 2. Non existent (LAC, Cell ID) in MSC
• 3. DMAX = 0
• Very few calls happening in a cell
• 1. RxLevAccesMin
• 2. Wrong MNC, MCC, LAC declaration
• Very low traffic in a cell
• 1. msTxPwrMax = 0, bsTxPwrMax = 30
• Bad quality in UL after rehoming because of RDIV parameter is not set YES
anymore.
• Few traffic in 1800 layer of a dual band 900/1800 network :-Idle Mode: C2
parameters not set properly (temporaryOffset, penaltyTime)
Examples of wrong parameter set with impact
on
network operation/performance – frequencies
1. Drop call rate increase after new frequency plan implementation
• Double BA List activated
2. Impossibility to unlock some BTS after a RF-frequency hopping
implementation
3. Impossibility to unlock some BTS after a frequency retune
• NON-EDGE TRX, with GTRX = Y
• TRX, with GTRX = Y, not attached to any EDAP pool
4. No handover happening after frequency retune between 2 cells from
different BSCs
• ADCE table has not been updated for other BSC
Set with impact on network
operation/performance–
Handover
• Example of Wrong Parameter Settings
1. No handover from a cell towards all its neighbours
• PLMN permitted = No
2. High Handover failures after implementation of new adjacency plan
SYNC = YES
3. No handover happening from an interfered cell
hoMarginQual set to 0
4. 100% of handover failures in an adjacency relation
Co-BSIC co-BCCH declaration
5. High number of handovers
hoThresholdsLevUL = hoThresholdsLevDL
6. Handover not happening when DL signal level of neighbour much greater than serving cell
POC DL activated
Examples of wrong parameter set with impact
on
network operation/performance – Background
Plan
1. Few handovers after implementation of new adjacency plan
• Only half of the plan has been downloaded. Half of the adjacencies
missing.
2. High drop call rate in some sites after frequency hopping
activation
• Some sites did not hop as some frequencies were not correctly set!

• Important to verify network parameters through MML command!

• In case not all parameters were changed correctly, use MML to
implement the changes!
Conclusion
Before suspecting anything, check the parameters
active in the network!!!

• Do consistency checks: verify network parameters are as planned.

• Check configuration!
• Verify differences between OSS template and BSC default parameters!
• In some cases recommended values should be used instead of default values (e.g.
msPeriodicLocationUpdate: 0.5 -> 6)
• Verify value of sensitive parameters (e.g. DMAX, RxLevAccessMin)
• Adjust parameters to balance traffic (e.g. C2 in idle mode)
• Inter-related parameters (e.g. New Frequency Plan + BA List)
/
KPI Evaluation Process
HOW DO WE NEED TO START
OPTIMIZATION
• Firstly we need to check the KPI of Cluster Level & BSC level
• After that Check the KPI of which BSC is going down and then find the cells due
to which KPI’s going worst
• Now check the Cells KPI ( Preferably CSSR, DCR & HOSR ) why it is going worst
• If CSSR KPI is worst then we need to check all the components of the CSSR (
TCH Blocking, SDCCH Blocking, SDCCH Drop, TCH Assignment success Rate)
& if DCR KPI worst check all the Raw counters also according to the formula and
same procedures for the HOSR.
CSSR KPI

• As we know CSSR depends on the 4 Components (TCH Blocking,

SDCCH Blocking, SDCCH Drop, TCH Assignment success Rate ) and if
any of the components KPI’s going worst than CSSR will be the worst.
• We will discuss these cases one by one
• For CSSR check we use ND Report 250 i.e for Cell by call Success ratio.
• For Hardware we will discuss later
CASE-1 CSSR BAD Due To High
SDCCH Drop Rate SDCCH Drop rate may be
high due to many reasons as
given below
• Hardware Problem in a Cell
• Overshooting
• Co-channel Interference
• Transmission issue
• Extra SDCCH
As the above KPI shows that CSSR is going worst due to
high SDCCH Drop Rate and Now we have to find out the ND report 166 SD Drop report
reason for High SDCCH Drop Rate
SDCCH Drop Call Rate (%)
SDCCH Drop Rate KPI Analysis

Now in the above KPI we can see the SDCCH drop rate is high due to SDCCH A
interface fail call is high as major drops are going only on this counter and it is
suspected due to Transmission issue so for root cause we need to check the all
counters.
SDCCH Drop Rate Analysis
Based on Several Reasons
• If SDCCH_Radio_fail counter value is high it means drops going may be
due to Overshooting, interference , Phantom RACH etc.
• If 7745 Channel Failure Rate Alarm persist on SDCCH then Shift the
SDCCH from that TRX to another TRX.
• If SD Drop is high we can also change some parameters RXP, PMAX,
DMAX (For international boundary facing) etc.
• SD Drop can also be high due to high UL or DL issue in that cell. For UL
we can put TMA and for DL we can provide tilt or re orient that antenna.
• For Extra SDCCH we need to check the SD Configuration as per Nokia
system 1 SDCCH can take 5000 SDCCH attempts, for this don’t consider
the daily KPI, please see the next slide for better explanation of this.
Extra SDCCH Analysis

According to KPI there should be only one

SDCCH timeslot but if I check the Database
configuration it has 4 SDCCH so we need to
remove the extra SDCCH from the TRX’s
CASE-2 CSSR BAD DUE TO
BAD TASR
TASR Bad due to Several Reasons
o Hardware Faulty
o Timer T10 Expired ( BSC Level)
o Due to Radio Problem
o Due to Hardware Issue
TASR Formula
TASR Analysis Counters

As in the above given counters shows that suddenly some the counters value (
ABIS interface fail, Radio fail etc) increased . Radio fail may be due to some
Radio problems as interference, overshooting etc and if ABIS fail call increased it
may be increased due to some Transmission alarm.
CASE-3 CSSR Bad Due TO
Blocking

CSSR is worst due to high

SDCCH & TCH blocking & this report is ND 135 Tch congestion.
What is TCH Blocking ?

When all timeslots ( 8 TS) are busy then it is called congestion and when
at the time of congestion any call come through that busy timeslot then it
is called blocking.
TCH Blocking Formula (%)

100 * [sum(a.tch_call_req - a.tch_norm_seiz) - sum(b.msc_o_sdcch_tch +

b.bsc_o_sdcch_tch + b.cell_sdcch_tch) + sum(a.tch_succ_seiz_for_dir_acc) –
sum {a.tch_rej_due_req_ch_a_if_crc -(b.bsc_i_unsucc_a_int_circ_type +
b.msc_controlled_in_ho + b.ho_unsucc_a_int_circ_type)} ]
_________________________________________
[sum(a.tch_call_req) – sum {a.tch_rej_due_req_ch_a_if_crc -
(b.bsc_i_unsucc_a_int_circ_type + b.msc_controlled_in_ho +
b.ho_unsucc_a_int_circ_type) } ]
TCH Blocking (%)
TCH Blocking (%)
TCH Blocking Reasons

• TCH availability
Check alarms (are TRXs & TSLs in Working State? ), check
availability
report and RxQuality report to verify whether there is a badly
functioning
TRX. Make Loop Tests on TRX. Fix hardware problem.
• TCH capacity
Bad TCH capacity dimensioning. Check number of TRXs.
Optimization TCH Blocking
 If hardware problem exist then need to escalate to the concerned person
 Increase dual Rate for reduce the TCH Blocking ( TCHF --TCHD, TCHH --TCHD)
 Check FRL & FRU setting ( BTS Level)
 Directed Retry Enable
 Remove Extra SDCCH Channel and convert in to TCHD in case of high TCH Traffic to reduce the blocking
 In case of Overshooting check RXP setting
 In case of very high traffic in clusters then we can reduce the power
 Traffic Sharing
• Add Extra TRX
• Add New Site
• Optimize the cell boundaries to share the traffic with surrounding cells
• Traffic Reason Handover enable
• BLT (BTS Load Threshold) can also be increased from 70 to 90 value.
SDCCH Blocking (%)
SDCCH BLOCKING REASONS

• LA border at crowded area ( Check HYS Setting)

• Abnormal SDCCH traffic
- “phantom” channel requests
- Inadequate LAC design, causing too much LU
- Redesign LAC
- Problem with neighbor cells belong to other LAC
SDCCH blocking
• SDCCH availability
– Check alarms (are TRXs & TSLs in Working State? ), check availability report
and RxQuality report to verify whether there is a badly functioning TRX. Fix
hardware problem.
• SDCCH capacity
– Check actual SDCCH configuration ( e.g. Combined BCCH/SDCCH, Number of
SDCCH channels). If there is insufficient SDCCH capacity and enough TCH
capacity, add SDCCH TSL. Other solution e.g. are to add TRX, activate
Dynamic SDCCH, activate FACCH Call Setup.
• SDCCH traffic
– Verify traffic distribution (LU, SMS and MOC in %);
– Cell is covering a region greater than planned. Verify TA statistics. May need to
change DMAX, or downtilt.
• SDCCH traffic due to location updates
– Bad location area setting (Check MCC, MNC and LAC
parameters)
– Bad Location area geographical configuration. Too small
LA definition will cause many LA updates. Border of LA in a
busy avenue will cause many LUs in both location areas!
– Low value for CellReselectHysteresis
– Verify if downtilt is needed or an increase in SDCCH
capacity (air and Abis interfaces).
• SDCCH traffic due to SMS
– Increase SDCCH capacity (air and Abis interfaces).
/
DCR FORMULA

sum(tch_radio_fail+ tch_rf_old_ho+ tch_abis_fail_call+ tch_abis_fail_old+

tch_a_if_fail_call+ tch_a_if_fail_old+ tch_tr_fail+ tch_tr_fail_old+
tch_lapd_fail
+ tch_bts_fail+ tch_user_act+ tch_bcsu_reset+ tch_netw_act+
tch_act_fail_call)
100 * ------------------------------------------------------------------- %
sum(a.tch_norm_seiz) ;(normal calls) + sum(c.msc_i_sdcch_tch +
c.bsc_i_sdcch_tch) ;(calls started via DR) +
sum(a.tch_seiz_due_sdcch_con)
;calls started as FACCH call setup
DCR ANALYSIS

As by the above counters you can directly say from what reasons drop
call rate is high as it may be due to RF reasons or may be due to
Transmission Issues so we need to know about all the counters
Optimization of Drop Call Rate
• If hardware problem exist then need to escalate to the concerned person.
• If tch_Radio_fail counter value is high it means drops because of RF
Issue for which there issue like Overshooting, interference , Neighbor
relation etc.
• To improve TCH drop we can parameters like:- RLT (Radio Link Time
Out) , RXP etc.
• If tch_rf_old_ho is high then check neighbor relation and do tuning
according to conditions.
• If tch_lapd_fail and tch_tr_fail is suddenly increased or its increasing then
this problem occurs due to Transmission issue i.e for this we have to
check ND report 522 and ZAHP Alarm history for Transmission problem.
• ND Report 160 and 163 used for analysis of drop call rate.
/
TCH Drop
Radio Fails
Check alarms and RxQuality report to verify whether there is a badly functioning TRX.
Fix hardware problem. Check antenna line.
Coverage. Verify TA report and planning tool.
Interference. Check Frequency Plan. Solution e.g. add sites, downtilt antennas, increase
RxLevAccessMin.
Lack of neighbours
Bad neighbour declaration
Transcoder Failure
Due to synchronisation problem. Synchronisation source set in BTS clock. Change to
BSC.
AIF Failure:
Interface failures: problem with ET cards. Solution: block the circuits connected to this
card and then change ET card when available.
Handover Success Rate

Known problems:
1) Calls that are cleared by MS user during the HO process increment the attempt-
counters but
can not be compensated in numerator.
2) HO that is interrupted due to other procedure (e.g. assignment) increments attempt-
counters
but can not be compensated in numerator.
HARDWARE ALARMS
There are several hardware alarms in NOKIA system which are badly
affecting the KPI
 BCCH Missing ( Site Down, Please refer Outage Report ND-023)
 BTS Faulty ( BTS Down)
 BTS Operation Degraded
 BCF Operation Degraded
 TRF Faulty ( Faulty TRX shows as BL-TRX Automatically)
 TRX Operation Degraded
 BTS With NO Transaction
 Channel Failure Rate Above Defined Threshold
 Mean Holding Time Below Defined Threshold
 Traffic Channel Activation Failure
 Transcoder Channel Failure
 BTS O&M Link Failure (OMU Block)
 CH Congestion In Cell Above Defined Threshold
 LAPD Failure
 PCM Failure

Some alarm I have explained in the next slides, please see the given
below slides
Channel Failure Rate Above
Defined Threshold
BTS O&M Link Failure

• Regarding this Alarm we just need to remember one thing if this alarm persists
the OMU of the site blocked and at the same case don’t reset the BCF, if we do
this reset BCF than after lock the BCF it will not be unlocked until OMU is not UP
and if OMU up then also site will be down because BCF is Locked so better when
this alarm comes don’t Reset the BCF.
• This above point is the main point regarding this Alarm, please remember it
always.
BTS With NO Transaction

• The BTS has had no successfully terminated calls or SDCCH transactions

during the supervision period.
The alarm is used for supervising the BTS traffic capacity.
Reason for the alarm
1 = no successful SDCCH seizures
2 = no successful TCH seizures
3 = no successful SDCCH nor TCH seizures
PCM Failure
• Alarm 7704 is BCF-specific. It is used by the RNW recovery part of the BSS system. This alarm (and
cancel) will cause radio network recovery actions concerning objects connected through the faulty
PCM (ET). Alarm 7704 does not occur alone. There are always some other alarms ( 7767, 2900, 2915,
7706, 7704) active at the same time.
• 7767 : BCCH Missing
• 2900: Incoming Signal Missing
• 2915: Fault Rate Monitoring ( the trunk network circuit supervision clears the calls that come
through the
ET(S) in question and directs new calls through trunk circuits which are in order )
• 7706: BTS O&M LINK FAILURE
TRX NOTIFICATION ALARM
STATUS
From this alarm only Common ABIS Cells are affected and major alarm description is SYNCHRONIZATION CHANGED
due to HOLDOVER MODE and this alarm persists after software upgrade
• This alarm persists when BTS is not able to synchronize with the BSC / Core Network and due to this alarm
persist synchronization changed due to holdover mode.
• May be this alarm persists sue to some error in Software upgrade for COMMON ABIS sites.
• We can check the BTS configuration setting as after software upgraded may be some setting change.
• Check the heater working properly or not if equipped.
Action Proposed to remove this alarm and you can try these given below steps also.
 check the sync with MGW and BSC, MGW and MSS.
 Just make the SYNC disconnect by the command ZDRD
 After disconnect SYNC remove the punching cable or optical path cord as per your connection
 After this run ZDRI and then state will be pleisochronous mode
 After 10-15 min just punch the cable or connect the fiber and connect the 2M1 or 2M2 by ZDRC and then make the
state to hierarchal SYNC
 After above all steps just restart the system
Transmission Alarm

There are lot of major alarms persists in the BSC but some of them are not
affecting the KPI’s but some really affecting the KPI’s, please see the given below
alarm status

 BTS & TC Unsynchronisation Clear calls due to A interface ( Affecting Drop Call Rate)
 BTS & TC Unsynchronisation Clear calls due to ABIS interface ( Affecting Drop Call Rate)
 Abnormal A interface Circuit Release ( Affecting Drop Call Rate)
 SCCP Disturbance ( Affecting SDCCH Drop Rate)
 AIS Received ( Site Fluctuates)
 Fault Rate Monitoring ( Site fluctuates)
 Telecom Link Overload
 Signaling Link Load Over threshold
 Adjacent Cell IDENTIFIER configuration error
Adjacent Cell IDENTIFIER
configuration error
• adjacent cell information has been defined incorrectly in the BSDATA
(BSS Radio Network configuration
Database). Either the MSC or the source BSC can detect the error
during an external handover. When
the error has been detected, the handover attempt is interrupted
BTS & TC Unsynchronisation Clear calls due to ABIS
interface
2993 ( BTS & TC UNSYNCHRONIZATION DUE TO CLEAR CALLS ON ABIS INTERFACE)
Calls have been cleared three successive times on the same ABIS interface channel due to BTS and Transcoder
unsynchronisation
Supplementary Information filed
 BTS Id on which calls are getting dropped
 TRX id of the above BTS id on which calls are getting dropped.
 Radio Timeslot number on which calls are getting dropped. This is Air Interface Timeslot number
 ET Number on which calls are getting dropped.
 ET Timeslot on which calls are getting dropped
 Sub Timeslot of ET on which calls are getting dropped
This alarm tells us the calls are getting cleared through the ABIS interface due to non Availability of the transmission on ABIS
interface and please make sure when this alarm is triggered means calls are getting thorough on the Air interface but gets
dropped on ABIS interface.
ZAHP : 643d 9d 04 1080d 10d 1d
It means BTS ID=643, TRX ID=9, Timeslot Number=04 , ET ID=1080, TRX ID=10, Sub Timeslot of ET=1
First identify the ABIS (ET) Timeslots on which calls are getting dropped. If calls are getting dropped on all the Timeslots of
TRX
this means either they are mapped differently on BSC & BTS or Timeslots are not bypassed correctly.
If calls are getting dropped on particular Timeslot only lock that Timeslot and recheck alarms after sometime.
SOLUTION:
• If calls are getting cleared by all the timeslot for the particular TRX firstly please lock the TRX and check the alarm after
sometime.
• We can try to change the Channel TSL also if there is any free mapping given.
Telecom Link Overload

• The alarm is used to supervise the traffic load of LAPD links and
BCSU units and to detect the possible
overload situations. The alarm may also be caused by short
breaks in the Abis interface.
Supplementary information fields
00: BCSU unit overloaded
01: LAPD link overloaded
ND Report Analysis
Adjacency definition(061)

Find all non symmetrical adjacencies: One Way Adjancies

• cell B is neighbor of Cell A
• cell A is not neighbor of Cell B
ZEAT Check
Adjacency Discrepancies (060) – Example
Undefined Adjacent Cell Measurement - Network Doctor Script 073 -
ND-074
ND-130 Cells Having SDCCH
Congestion
ND-135 Cells Having TCH
Congestion
ND-208 Analysis
ND Report 196
Important ND reports
Characters for Embedded characters:
!"#$%&'()*+,./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³
´¶·¸¹º»¼½ÀÁÂÃÄÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇňŌŐőŒœŔ
ŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵŶŷŸŹźŻżŽžƒȘșˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ‘’‚“”„†‡•…‰‹›⁄
€™ĀĀĂĂĄĄĆĆĊĊČČĎĎĐĐĒĒĖĖĘĘĚĚĞĞĠĠĢĢĪĪĮĮİĶĶĹĹĻĻĽĽŃŃŅŅŇŇŌŌŐŐŔŔŖŖŘŘŚŚŞŞŢŢŤŤŪŪŮŮŰŰŲŲŴŴŶŶŹŹŻŻȘș−≤≥fiflΆΈΉΊΌΎΏΐΑΒΓΕΖΗΘΙΚΛΜΝΞΟΠΡ
ΣΤΥΦΧΨΪΫΆΈΉΊΰαβγδεζηθικλνξορςΣΤΥΦΧΨΩΪΫΌΎΏЁЂЃЄЅІЇЈЉЊЋЌЎЏАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШ
ЩЪЫЬЭЮЯЁЂЃЄЅІЇЈЉЊЋЌЎЏѢѢѲѲѴѴҐҐәǽẀẁẂẃẄẅỲỳ№—–-

!"#$%&'()*+,./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³
´¶·¸¹º»¼½ÀÁÂÃÄÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇňŌŐő
ŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵŶŷŸŹźŻżŽžƒȘșˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ‘’‚“”„†‡•…‰‹›⁄
€™ĀĀĂĂĄĄĆĆĊĊČČĎĎĐĐĒĒĖĖĘĘĚĚĞĞĠĠĢĢĪĪĮĮİĶĶĹĹĻĻĽĽŃŃŅŅŇŇŌŌŐŐŔŔŖŖŘŘŚŚŞŞŢŢŤŤŪŪŮŮŰŰŲŲŴŴŶŶŹŹŻŻȘș−≤≥fiflΆΈΉΊΌΎΏΐΑΒΓΕΖΗΘΙΚΛΜΝΞ
ΟΠΡΣΤΥΦΧΨΪΫΆΈΉΊΰαβγδεζηθικλνξορςΣΤΥΦΧΨΩΪΫΌΎΏЁЂЃЄЅІЇЈЉЊЋЌЎЏАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯАБВГДЕЖЗИЙКЛМНОПРСТ
УФХЦЧШЩЪЫЬЭЮЯЁЂЃЄЅІЇЈЉЊЋЌЎЏѢѢѲѲѴѴҐҐәǽẀẁẂẃẄẅỲỳ№—–-

!"#$%&'()*+,./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³
´¶·¸¹º»¼½ÀÁÂÃÄÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃń
ŅņŇňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵŶŷŸŹźŻżŽžƒȘșˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ‘’‚“”„†‡•…‰‹›⁄
THANKS
€™ĀĀĂĂĄĄĆĆĊĊČČĎĎĐĐĒĒĖĖĘĘĚĚĞĞĠĠĢĢĪĪĮĮİĶĶĹĹĻĻĽĽŃŃŅŅŇŇŌŌŐŐŔŔŖŖŘŘŚŚŞŞŢŢŤŤŪŪŮŮŰŰŲŲŴŴŶŶŹŹŻŻȘș−≤≥fiflΆΈΉΊ
ΌΎΏΐΑΒΓΕΖΗΘΙΚΛΜΝΞΟΠΡΣΤΥΦΧΨΪΫΆΈΉΊΰαβγδεζηθικλνξορςΣΤΥΦΧΨΩΪΫΌΎΏЁЂЃЄЅІЇЈЉЊЋЌЎЏАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧ
ШЩЪЫЬЭЮЯАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯЁЂЃЄЅІЇЈЉЊЋЌЎЏѢѢѲѲѴѴҐҐәǽẀẁẂẃẄẅỲỳ№—–-

!"#$%&'()*+,./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³
´¶·¸¹º»¼½ÀÁÂÃÄÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽ
ľŁłŃńŅņŇňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵŶŷŸŹźŻżŽžƒȘșˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ‘’‚“”„†‡•…‰‹›⁄
€™ĀĀĂĂĄĄĆĆĊĊČČĎĎĐĐĒĒĖĖĘĘĚĚĞĞĠĠĢĢĪĪĮĮİĶĶĹĹĻĻĽĽŃŃŅŅŇŇŌŌŐŐŔŔŖŖŘŘŚŚŞŞŢŢŤŤŪŪŮŮŰŰŲŲŴŴŶŶŹŹŻŻȘș−≤≥fi
flΆΈΉΊΌΎΏΐΑΒΓΕΖΗΘΙΚΛΜΝΞΟΠΡΣΤΥΦΧΨΪΫΆΈΉΊΰαβγδεζηθικλνξορςΣΤΥΦΧΨΩΪΫΌΎΏЁЂЃЄЅІЇЈЉЊЋЌЎЏАБВГДЕЖЗИЙКЛМН
ОПРСТУФХЦЧШЩЪЫЬЭЮЯАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯЁЂЃЄЅІЇЈЉЊЋЌЎЏѢѢѲѲѴѴҐҐәǽẀẁẂẃẄẅỲỳ
№—–-