LTE POST LAUNCH OPTIMIZATION Problem cause, counter pegging, solution & Case study a-z step WwCounters = MO Class Al the radio network counters from the EnodeB (and RBS) are reported from ane Managed Object (MO) Class. ‘TYPE OF COUNTERS Counters are used to collect PM statistics Data, Different types of Counters are used to collect observable data. ‘Thore are 9 different types of counters available; 4. Bex ~ A counter that is increased by tat each occurrence of a specific activity gi pmsadCovévalReport 2. Gauge A counter that con be increased or decreased depending an actvityinthe system. Eg:=rnPrbUsedICcch 3. Accumulator ~ A counter that is increased ly the value of a sample. It indicates the tatl sum of all sample values taken during: 2 certain time. The name of an accumulator counter begins either with mum or pmSumdjsama. g:-pmiArcConntevSum 44, Scan ~ A counter that is inereased! by 1 each time the corresponding accumulator is increased. Ht indicates haw many samples have been read, and added to the retated accumulator counter. A scan counter can therefore be considered a specific hind of peg counter. Due to these types of counters, it is possible to get the average value of ail samples by dividing the accumulator counter by the scan counter. The name of sean eoumter begins with pmSomples er praNoofSeme. Eq:-pmBreCannlevsorp 5. PDE alae of range values. A value is sampled (read) poriocally,W the value falls within 3 certain rahe, the ange ounter for that range is increased: All range counter values are collected and stored in ROP file atthe end of the each reperting period, For example, if SIR values ‘are spilt into three range : Ranget = [-12 48 toa dB}, Ronge2 = [4d to +4 48), Range’ = [+4 eB to #20 dB], and a value is read every 3 ‘irutes over 3 15 minutes period (values = -10, -3, +5, 45, +6), then the three Range Counters are reported a5 RangeCounterl = 1, RangeCounter2 = 2, RangeCounter3 = 3. Ea mRadfoRecaterferencePwr 5, Discrete Distributed Measurements [DM] ~ A series of values recorded during a renorting period. Eac series of values may be one of the following measurement types: 4. Accumulated over a measurement peried and reed at the end af each measurement peviad|a gauge or peg counts] 2. Averaged ever the duration of ameasurement pesiod 3. Road at asec time (the measurement tie, within the momsurement poriod fat soe rome) [At the end of 3 series of consecutive measurement periods (the reporting period) al measurement values ae collected and stored in a ROP file: Eg if SIR valve is read every 3 minutes over a 1S-minutes period [yohe = -10, -2, +5, +5, 46h then S DDM mesiurements ore ‘reported as Meas! =-10, Meas? =-5, Meas = 5, Meass =5, MeasS = 6, 7, Gallculated ~ A counter whose value is determined by ather counters. The calculation is performed in the RANGS Statistics database, The FOP fies. are opened in order to be transferred ints the databace and the calculations are made by the database itself during ths process, ‘This means that these counters are not available when the Statistics Database is not present, 8. TrigACC—A courier whose values the sum a all values accurnlated during the ROP ot the eccurrenct athe defined trigger. 9, TrigSCAN~A counter whose value isequal tothe number of occurrences of any defined trigger during an ROP: WACCESSIBILITY WACCESSIBILITY for the €-UTRAN is a measure af the ability of a user to obtain an E-RAB from the system. The Initial E-RAB Establishment process can be divided into the following phases: > RRC CONNECTION ESTABLISHMENT > SLSIGNALING CONNECTION ESTABLISHMENT > INITIAL E-RAS ESTABLISHMENT OR E-RAB ADDITION yy Teeter dausertoctens The abaiy ofa usor te attain a requestad sence from the tem requested sonice ein tho system ES aeraeten WwConnection Setup Cate Daten "se Ub S14? ica at Ud ULB AP meeare rman EarRRC connection & Si Signaling Z RRC CONNECTION ESTABLISHMENT $1 SIGNALING CONNECTION ESTABLISHMENT tiW SIGNALLING 4 SiAP E-RAB SETUP E-RAB ADDITIONMajor Reasons for accessibility Poor coverage % Check inter site distance with neighbors ste > Check value of pmBadCovEvelReport [if MCPC enabled, need to check pmeniticoiforderévolRepart). I this counter is pegging high in respect to RRC attempts, then wwe can say that more number af UEs arelling in bad coverage > Check counter mCriticalBorderEvalRegort (this means there is no LTE coverage, and UE wil do release with redirect_(AWA) with any Technology) & pmoRadioTosPwrestricted (Wf this counter is more (>70%), then for that sector, the UE is using more ower ta reach EnodeB, inthat case pacchutl salsa high) Change arxievmin (in Sprint the parameter value is changed from -120dBm to -110d8mn), so as to discard bad coverage / cell edge UES. Alarms Through 055 commands “ait” (Current / Active site alarms can be checked) & “iga " {nis an integer value) (Site atarms present far n days can be checked) High Load (igh Fraffte Check pmRrcConnéstabFailHighload & pmRrcConnEstabFaiCverioad counters If any sector is having high ‘traffic. These Counters could be high due to high traffic and impacting CFR % The command "we print -admitted” is used to find the na, of UEs currently latched to the site sector-wise ROP-wise & the counters "pmRrcConntax (maxy” & “pmfircConntax (sum are used to find out ‘max. active users/ day’ and ‘sum of all active users/day’, respectively. Sometimes, due to MOs are not synchronized property, prafrcConnEstabFaitOverioad is pegged high. in this case, the Servicetnavitable ($1 Connection failure) alarm ts observed in sites, even though RRC Cann Users remain to be same, H/W issue (Hard Reset on site / RRU Replacement, if required) % IFRRUS are disabled, in that case “HW fault” alarm is observed in sites = Command “st . au” shaws that the operational state of the auxilary unit/ RAUS is DISABLED. > Command “Iga” is used to find out transmission issue of site.Major Reasons for accessibility 5. High UL interference ‘High UL N+! is impacting to all KPIS, UL MI values {-119 .......-210 dBm) is considered to be good, % The cause may be Internal Sources (Check Tx & Rx antenna ports, fiber cables and connectors, All connection should be proper) and External Sources { like repeaters, airport, power plant etc. sources resulting in high EMW in the neighborhood). > pmBoadiorecinterforencePwr ic checked for ULNM values. Use pm -m 72-r6 -f | égrep +i Interference |Res_AvgNrOfRreConnectedUsers’ command to find out ROP-wise UL NI status of last 72 hours, along with corresponding no. of average users. 6 Pelcantflict > Two types of PCI conflict: ‘> Potconfusin, |e, UE confused Its geting two oF more target cells havingsare PCL > Peteoition (., UEK colon ue Yo source and trget having same PCI > Impacts all KPIs. Use “EUtianCellFDD .pciconfit” to find out PCI conte of cite 7. RACH Root Sequence Index plan need ta be reviewed — Based on ‘Zero Correlation Zero Canfiguration’ parameter RACH root Sequence index need to be planned, For N= 12, aliference of 101s recommended for RACH root Sequence index per cel 8 UE camping in the wrong cell. Ceil Reselection Parameters need to be tuned > — When UE is doing cell reselection if priorities are werongly defined, in that case, UE will connect with wrong technology. > InsSpeint, cel resalection priority are defined based an eapacity and technology whose range varies (0.7) (call reselection priority for LTE 2.5GHz is 7, LTE1900 is 5, LTESOO is 4, COMA2000 is 2 and COMA20001xRtt is 0) > The command celheselectionpririy is used to find out technology-wise priority fr cell re-selection 9. Wrong System constant setting(S¢-556) ‘© — We can set SC-556 from 10, 25, 35.8 45, based on traffic. 10, VSWR over threshold > The cobx command provides VSWR status Yor RLL & RL2 (Tor 2¥2R}, Both, RLL and RLE should be more than 14 with a difference of less than 5. 1, Cell availability > Call availabilty should be 200%, i avallability is less than 100%, then the site might be havieg transmission ieue and ako, the site may not be taking traffic,Counter-wise problem identification ¢ Steps N SSSR Phase based on Counter 1. RRC Setup: - The counters responsible are as follows pmereConnéstabatt. > pmitrcConnéstabattReatt > pmRrcConnéstabsuce 1, $1-Signalling Setup: - The counters responsible are as follows > pms1sigConnéstabAtt, > pmsiSigConnestabsuce 3. E-RAB Establishment: - The counters responsible are as follows pmErabEstabattinit pmérabestabSuccinit pmérobestabattadded * pmikrabEstabSuecAddedCounter-wise problem identification ¢ Steps - 1, Fallure at RRESetwp Stage = prnBreConnFitabroll is tobe checked. ‘pmAreConnéstobfall contributes 1 poor RRC Setup Success Rae; The irimering issues for penrConnetabFat are 3 follows 1 pmteConnstabalie: The total number of fied HAC Connection atabishments due talack of eannected users hearts. eahable Solutions ~ Upgrade the UR (eens Key File) by Upgrading SoRware Eg From L324 to 128 and L194 to L1RB.LEAA hoving tier of 2000 Connected uate per Enodeb. (Uicense/Software up-gradallon acy governs as per the agreement wi custome, ‘Curent HcerseCopexityComnectedUters as pat WEA for Sprint 190 Users por site -Y Gfisa the traffic by optimizing azimuth a th ofthe serving and neighbouring cls, By changing aPievisin (Oetait Valve -120880); can be melted 10-110 dm °Y Brmplemenning Hi-Cap Paramecer. 1 Max RAC Conn Users is more than 350/sector ano pdcchutia7O%k. Detailed parameters for Hi-Cap parameter levplemertation have been shared ater Mera loa is stil high after implementation of above solutions, plan For new ste to oload wr change LF {em 1000 to 7000. (2A 2; LIA 138-L148 ) is sumed, | pritcConAstbFoilighLesd: The fatal nunc f flied RR Connection EsbRahmeats one YORgh land. ‘rabable Sluions.- Same as above, | pmfieConnEstaballdverload: The foal numberof flled ARC Koariction Establishments duc to overload, Psaiabie Solitons Same as above. ‘4 pmfreConnEsiabFatActiveUsericenset ncoeded: The number of fae AAC establishments due to more active users than what license allows. ‘eabable Salutians:: Check Active user par eal through counter pmActivetiserO\Sum, pmetiveUserisum, © Trytotflass table, possi, by ehanging Atimuan/ Titer loading H-Cap pacameter or Load Sharing (in Sprint trafic lose sharing bf LTETBOO & {TEBOO eo nested ste activated. Check dstanes of UE them Enode UEts cennected te far away Enade8, Reece parameter canbe changed to protect e055 YW Eehanced cl 10 festure is enabled in NAW Ting Advance, then pm TiringAcvance counter can be used to chack the TA valve. 5. pmfireConnEstabFaliallureinRadioPrecedure; The number al fled PRC establishments due a fale radlo procedure ‘Peabable Solutions: - Same as above.Counter-wise problem identification = Steps - 6. pmreConnéstabFailBearerAdmissionRe}: The total number of faled establishment of RAC Connection due ta the fact that all the UE'S ‘bearers are rejected during bearer admission contro i °F lesplemant WiCap Parameter tow move ser. ‘Algo POCCH Admission control Threshld ean be changed Bore mosilvng ths parameter, MOCCH CCE Unzatlon need tobe chaced ia the counter [pmPdechCecUii it shouldbe mare than 20K) 7, pmfircConnfteestfalllicMitReest: The number of RAC Connection Reestabllshments attempts that failed due to feature "Multi Target ARC ‘Connection Reestablstment” not being enabled. ‘Probable Solutions: Not inelvded in any predefined scannet. So you have to activate Scanner 8. pmfrcconn€ stabFailtarkO (Resources: The numberof falled RRC establishments due to lack of resources. robabie lutions: 7 Check the cll uillation and try 4 offload try Implementing HE-Cap Parameter shift trafic onthe lest willed cells orig 8M and load balancing feature, 9. pmrcConnstabFaillunspecified: The nurmber at falled RRC establishments dve to unspecified cause, ‘Probable Solutions: Not includes in any predefined scanner. Soyou have toactivate Scanner.Counter-wise problem identification Steps - Failure at $1-Signalling Setup Stage : pmS1SigConnEstabFail is to be checked. Following issues could be the reason for having high pmSISigConnEstobFail which contributes to have poor $1 ‘Signalling Success Rate®. 1. TN (Transport Network issue): Check Fiber Issue from |PBH Team, 2. Wrongly Configured TAC: Configure Correct TAC as per Design ( Pre-RNDCIQ). 3, LAC-TAC mapping: Validate if LAC-TAC mapping is correct as per Design { Pre-RNDCIQ). Incorrect or missing TAl- LAI pairing could result in ‘Accessibitity Failures’ when UE attempts CS Fallback to UMTS (LTE Attach Request of type “Combined EPS/IMSI Attach”). The MME derives the LAI from the TAI of the current LTE cell, then MME sends the “Location Update Request” to the target MSC/VLR._Counter-wise problem identification ¢ Steps - 3. Failure at Initial E-RAB Establishment Stage : Following counters ere suggested tobe checked. |, pmerabEstabFallGhrDIEnB: The total number of filed F-RAM setup attempts due to dawnlink GBR overload for resources common to the Enodeb. ‘Beohabe Sohtions.- “7 Parrett ae required abe set are itnanGrRatio 0) rancho 1000 2, pmErabestabFallGbrVlEnb: The total number of falled E-RAB setup attempts due to uplink GBR ovetioad for resources common to the ‘node Probable Solutions. Parameters that are reed tobe sot are ManGoRatio(90} a areNwBandwidth{ 000), 4. pmErabestabFailaddedlic: The total numberof failed establishment of added E-RABs de to lcensé rejects (Multiple Rac Bearer per user ‘or RUC UMM), Added E-RABE are all F-RABE protent in Si message E-RAB Setup Request 4, pmerabEstabFallinitLic: the total numberof fale establishment of insial &-RABs duc to cense rejects (Multiple Radio Bearer pe user or FRAC Unt), nitia E-RABS ar a E-RABs prosent inthe $1 message Inia Context Setup Request ‘Apart from the above mentioned counters, following issues are suggested t0 be checked: 1. Security update Fall. % Vendor specific iste. 3. TNiTransport sue). NOTE) Coupte of CASE STUDIES are shared in the subsequent slides detailing parameter / counter level implementations that are undertaken fn ive projects to improve Accessitilty%.Introduction to hi-cap and its affect = in the network Z ‘The main purpose of the Hi CAP Settings is te alleviate POCCH scheduling congestion for DRB traffic by reducing ‘SRB traffic for jive events and in-venue sites. For EnadeBs under high load conditions without Hi Cap settings ACTIVATED, the SRB traffic is using majority of the scheduling opportunities thereby leaving very little opportunities for the ORB traffic. As 2 result, the EnadeBs are limited on CCEs resulting in low throughput. HI CAP Setting recommendation update for L14A addressing accessibility concern with ‘SystemConstants=1::aumninitialAccessAndincomiagHa(hicap)|SC5S6) The following KPis need to be closely monitored by the RF optimization engineers, once the required changes for HICAP Settings are implemented: RACH Success Rate. Accessibility and Retainability. ‘Max and Average RC Connected UEs. High/Over load. Handover performance. UL/DL Throughput. CCE utilization. RRRR ERRHi-cap parameters RadioBearerTable=default,DataRadioBearer=1::uiMaxRetxThreshold(hicap) anc cullMaxRetxThreshold(hicap) a wach set to & The parameter setting reduces the number of uplink RLC retransmissions for signaling radio bearer and data radio bearer. It will reduce SE/TT! ‘usage for retransmissions, and allaw more SE/TT1 to serve traffic, The change might cause Retainability to be same or slightly worse: RadioBearerTable=default,DataRadioBearer=1::tPallRetransmitDl(hicap) and RadioBeorerTable=defoult,SignalingRadioBeorer=1::tPoltRetransmitDi(hicap) are each set to 160 ms, it extendsthe ‘downlink time for new polit no status report is received for bath signaling radio bearer and data radio bearer. The changes. wil reduce SE/TT| usage for retransmissions, and allow more SE/TTI to serve traffic RadioBearerTable=default,DataRadioBearer=1::tPallRetransmitUW{hicap) and RadioBearerTable=default, SignalingRadioBearer=1::tPoltRetransmitUlifhicap) are each set to 160s. it extends th uplink time for new pollif no status reports received for both Signaling Radio Bearer and Data Radio Bearer. The changes will reduce SE/TT) usage for retransmissions, and allow more SE/TTI to serve traffic. ‘System Constants=2.:deltaPsdRs2Tx{hicap) RS power boost is eéluced fram a non_hicap value OF3 (248) to. value of 0 (0d) te reduce inter-ste/eellinterterenee under low Inter Site Distanee (150) RF radio environment, SystemConstants=1.:numinitialAccessAndincomingHohicap) is changed trom a Gioba} 10 to Local 10-oF 20, and that ‘esuitants inital acesses/incoming handavers 25/s or SO/s.ttradveas the maximum numberof initial aceesses and incoming hhandovers that are allowed during a time window without triggering the load contol mechanism. The reduction is designed to ‘ease the pressure en POCCH resources by reducing bursts of incoming users. Law value can result inereasing numbers of RAC high load rejections under high foad. There ' tradeoff between Accessibility and data throughput under the high foad by using values of 10.0F 20, Ifthe data throughput are-at acceptable tevels, 20 can be used. ‘SystemConstants=1,systConstants:;pdcchlaGinrMargin(hicap) is set ta 30 (348). This redhices POCCH link adaption -algorithrn from 10db 16-3 db. 10dB is 3 very conscevative value meaning that many users in medium radio.conditions may use & ‘€CEs when they could have used 4; this aggravates the PDCCH congestion. 3d8 isa reasonable compromise between saving CCE eS0uftes and ensuring reception of POCCH by the UE, Ww necnen irra | 20150048 1 Bape 18Accessibility - CASE study CASE 1; HIGH LOAD ‘Accessibiety is bad due to high toad relations, TION Offload the Traffic by changing Azimuth /Titt ¥ implementation of Hi-Cap Parameter ~ ifstill traffic load is more, new site integration and deployment plan is submittedNCCES sibility - C CASE sumly : HIGH TRAFFIC DUE TO SOME EVENT PASM E one oe a ee | idee ie es aeeieeeeeaeiin pe ae LION omer pene ee 26 D2 ‘Tralfic was pretty high in alpha sector and some ‘activity was going on 6% December which caused degradation in Accessibilty. Alpha sector is covering downtown [e958 2 | sas | ana 1 | 902 on 6 rence xin ee as cen avon sss —— 8 os ° S55 BRRRS5 EEEREEEEEEEEEES gage BRagas sezeeeeaseaagaes L Baad gag 444 Raga SaesagasagsAccessibility - CASE studhy s CASE 3 : PC| CONFLICT rd Accessibility is poor in CCL01851 is due to RRC failure due to high load at 09-29-2014 18:00 hr. Overall ERAB attempts following the trend or no inerease in the attempts. No UL RSSI, VSWR and alarms were present in the site. No other KPIs are impacted the site toeece TPT a% cutesy» ‘PCI cantnetimpacting accessibity 1140930-10:41:34 107,67.27,234 10.0) ERBS_NODE MODEL_D_1_189 COMPLETE stopfile=/smp/15124 Connecting to 107-67.27.234:56838 (CorbaSecurty=OFF, corba_classe2,javact.6.0_37, JacomseR794X07, jacorbrR7SXO1) Trying fle=/var/optfericsson/amos/moshell_logfiles/v06H92/o0gs_moshell/tempfiles/20140930-102053_14953/lor14953 Starting to retrieve active alarms rot active alarms are: Date & Time (Local) § specific Problem (Mo {cause/Additionalinto} 2014-09-30 03:12:44 M ExtemalAlarm He/Unit-SAU,AlarmPart=4 (RBS INTRUSION) >>>Total 1 Alarms (0Critiea, 1 Major)Accessibility - study CASE 4: WRONG SYSTEM CONSTANT SETTING(SC-556) ¥ Need to set proper SC-556 value.Accessibility - CASE study CASE 5 : RRC DEGRADATION DUE TO RRC REJECT H Parameters are defined as fellows: noOfPuechCqiUsers —640; noOfPucchSrUsers —900 and RAC Conn max user >160, then ARC can be rejected due to CA Resource Congestion, W CASE : SSSR DEGRADE DUE TO LOW S1 SIGNALING SUCCESS RATE Sometimes it has been observed that $1 Signaling Success. Rate gets degraded! due to Software up-gradation. SOLUTION :- The DULis given reset remotely After DUL Restart, it fs observed that the cell KPs have improved. CASE 7: SSSR DEGRADED DUE TO H/W ISSUE SOLUTION: - Replacement of faulty RRUs / Ausiliary Unit / Hardware units improves SSSR, CASES: Accessibility can also be improved by tuning the parameters -dIMaNRetaTh & ULMaxRetxTh of SRB-2 (1,2,4,8,16,32) CASE 9: If there would be coverage Kcsue then these caunters can be fetched pmRadioThsPwrRestricted, pmRadioUeRepCqiDist, pmbadcovevalreport. CASE 10: For high UL high RSS, these two parameters piZercNominalPucch and pZeroNaminalPusch can be increased to mitigate the Impact of high RSS! on the sector, Suggested parameter settings are as follows pzeroNominalPucch: From -120 10-117 pZeroNominalPusch: From -106.t0 -102.Accessibility - CASE study CASE 11: S1 FAILURE / MME ISSUE +S1_INITIAL_UE_MESSAGE is sent to MME *RRC_CONNECTION_COMPLETE +eNB is sending INTERINAL_PROG_RRG_CONN_SETUP to the MME. MME is not responding back probably the MME did not receive this message. (S1 link is the suspect in failing to send this message to MME). Leads to a failure in S1 link (VALUE_S1_INTERFAGE_DOWN). -An Attempt to reset S1 (EVENT_VALUE S1_RESET). Probably the MME is not getting the message from eNB and that’s due to S1 link loosing the message before it gets to MME. SOLUTION : Need S1 link investigation and confirmation from MME team.Accessibility - CASE study All sectors will be impacted IF MME issue -> Multiple sites in the NW will be impacted Bad HW (RRU, Combiner, Antenna, cabling...) Incorrect cabling RAKSARR = Issues & Solutions pmErabRetAbnormalénbActCdt~ the total numberof abnormal ERMB releases by the eNB per cell due cell down time (manual intervention} with the pre-condition thatthe Initial Context Establishment procedure must first have teen successfully completed and that there wos data in elther the Ut ar OL butter (.. active. Probable Solutions: Check Outage report or Fluctuation Report. pmErabRetAbnormalénbActHo ~ The total number of abnormal ERAB releases per cel by the eNB due to handover execution failure and that there was data in either the UL or DL buifer (ve. active). Probable Solutions: Check BC Panning is corrector hot, to avoid PC alison ile, Thoreshovld ot be any PCI re-use in nearby els (Te Ter @eighboure), Coverage issuelmake Ary PCI Dominant which shouldbe based on Clutter as per Coramon sense). Make EDT, Change Aalnuth © High UL interference fsue.on Target coll (PmRadiorecinterferencePwr).Check Connection b/w Antenna Connector & RRU Connector. © ‘lon Repeaters esponsisie sometimes for H-UL interference Might be du to Power Leakage pmErabRetAbnormalEnbActUeLost ~The total number of abnormal ERAS releases by the &NB per cell due that the contact with the UE is lost with the pre-condition thatthe Initial Context Establishment procedure must first have been successfully completed and that there was data in ether the UL or OL buffer (i.e. active). Probable Solutions: ‘Solve the Foor Coverage usue by chaning tt /auimuthor anoropcate parameter vaive setting .g.:+ part SectorPowe, ENB Power, PONominaucch PONominalPuseh or uplink Coverage). High ULI IswetAs per earer mentioned Alto make sure Nominal power Should rat sat very high otherwise ft wilereate interference neighbour el _pmErabRetAbnormalEnbLic The total number of abnormal E-RAB Releases initiated by the RBS due to license reject (per eel). _pmErabRetAbnormalEnbActTnFall ~ The tatal number of abnormal ERAB releases per cell due 101 interface down, "X2 interface down’ ac "Transpart Resource Unavailable", with the pre-condition thatthe Initial Canteat Establishment pracedure must fist have been successfully completed and that there was data in either the ULor OL butler fe. active). Probable Salutions :- issue can be resolved withthe help at NOC f IM Team by raising the required tickets. pmérabRetAbnormalénbActHpr ~The total number af abnormal ERAB releases by the eNB per cell due tohandover preparation and that there was data in either the UL.or DL buifer (ie. active). Ww Probable Solutions:- © MME missing issue-or MIME might be disabled, Transport issue suspected. © Ucensessue susnected, Site Coatiguravan issue. 'SARR — Session abnormal release rateretainability - CASE study (CASE 1. DL/UL MAXRETXTHDRE TRIAL v Current Scenarios : Change DRB di / ul MaxRetxThreshold value ~ Current Parameter Value : 8 ¥ Current Performance Trend : Poor CFR & CDR due to Congestion and Poor MAC HARQ Suce Rate. Any parameter or counter value can be changed : - ¥ di maxRetxthdrb from 8 to 32 Y_ ulmaxRetxthdrb from 8 to 32 Ww Description & Significance of Parameter Changes : - These parameters are useful for improving CDR where UE is facing poor RF condition and Gall drops are due to hitting maxRetxthdrb value before (310 timer expire. Useful for mid-cap site, where traffic is not too high. Once, we increase the value, it will also increase the drs utilization. So, we need to be cautious while increasing the value. 09m tore | RRC Atts one T BODO roo bom | 110000 Prosig Satt2tay ioe. 49 03-June) bette can ‘*Poatavg Stats(05- |] 200000 aticlhis 200% | fhinete'sune)” | sgon00 ol i008 | a 00% Praag Sut Post ang Connection Connection Drop May io dune) StaisOS-June to ‘en Fee Rae ie “iene muteretainability - CA (CASE 2: HIGH UL RSSI WHICH CAUSED RETAINABILITY DEGRADATION San Jove aiportretainability - CASE study CW102262_9C and increase Gellindiiduatoffset for CVLO0S12_98->CVL02534_9C fram 0 to 3, and need to increase celindividualyfsetto 5 from 3 for intra sectors.W morttse mor tt40 norte oe trso moe trae morta oz t190 8 nose —seeen retainability - CASE study CASE 7 : HO FAIL CAUSE RETAINABILITY ISSUEretainability - CASE study CASE 8 : RADIO LINK ISSUES W © From drive test analysis, it was observed that a large portion of the drop calls were due to poor radio environment (just before HO, it was observed that the UE SINR was poor and this caused the UE to drag the callin peor radia efwironment rather than HO faster to a neighbour cell with better SAP. ¥ inthis optimization project, 2 parameters are recommended to be tuned; a3offset and a2TresholdRsrpPrim. ¥ aloffset: Change from 310 248 ¥a2TiesholdRtepPrien: Change from 1206-11000. + -Attial was also conducted to evaluate the impact of changing the values below for a few sites with high DCR: ¥ DataRadioBearer diNtaxRebeThreshold/ ulMaxReteThreshold — Change from 8 to 32 + SignalingRasionesrer: aiMaxttetsTIveshold / ulMoaRetxThreshold— Change fromm 3 to 32 ~~ With current A3 setting, A3 event handover will be performed when neighbor cell is greater than a30ffset + hysteresis (ASAP) of the current serving cell. ¥-a30tset =3 dG, hysteresis 148 > Handover will only be performed ance Neighbor Cel RSRP> 4d of Serving Cell ASAP Thus, itis important to expedite the HO with reduction of a3Offset to 2 4B. After the parameter change, it was observed that the drop calls duc to call dragging was reduced in a cluster of 20 sites. AL Failure Timing ¥ tPolietcansenit = 4rvé (SRB, $$ (DAB) © retransmission limi increases frarn & to 32, RL falure due to.etransmisston limit reached: SRB: 360ms {8} to 1440ms (32) BRB: 400ms (8) to 1600ms (32)(CASE 9: CASE STUDY OF LR13XC102 MME DROP retainability - CASE study Ww Below are the steps to isolate if issue is related to site: SA ROR AR Verify sites configuration (vit, parameters. Verify alarms on the site ‘Check UL noise for the site ‘Check LTE traffic (# of UES) on site fron Cockpit/ENIQ Verity traffic (# of UES) make sense based on site location (Google) Compare UTE traffic with neighbor site in the same area ‘Compare UTE traffic for site with CDMAJEVDO traffic SA PPTTT EEE Ey Tiitiititt Alpha & Beta sector has high CDR Beta ‘sector has high MME drops Beta sector has high MME drop whereas Alpha/Gamma are nat bad RCA from team was 84/Core issue ¥ IF BH/Core issue > All sectors will be impacted © AFMNEissue > Multipte sites in the NW will be impacted Site with BH/Core issue “> gnoc.ericsson core tierl@ericsson.com If site get routed to core team then issue will not be resolved as RCA vas not accurateretainability - CASE study Verify sites configuration (tlt, parameters...) + LR13xC102 has correct parameter configuration: Changed the tilts > traffic not improved 3G iestll on MC (Legacy) Verify alarms on the site ¥ ntermittent VSWR alarm for Gamma © Intermittent STCP alarm + last alarm was mare than 2 weeks ago Y Check UL noise for the site ¥ ULnoise on all sectors was less than -116 4m La13XC102 ITE TRAFFIC Ww LR13XC102 LTE TRAFFIC VERIFICATION - GOOGLE ‘Trafic on Alpha/ Beta is very low > Coverage or Location ?? Based on neighbor sector providing coverage in the area there is good (TE traffic but LR13XC102 Alpha stil has wery love LTE traffic Based on neighbor sector providing coverage inthe area; (R13XC102 Alpha sector has comparable EVDO traffic (Legacy) compare to neighbor site Based on Voice/EVDO traffic this site carry high traffic so having very low trafficfor LTE indicate there is issue on this site.retainability - CASE study UR13XC102 ANALYSIS Based on the performance analysis dane on the site; results are pointing for site to have a weak coverage; probable cause: Bad HW'(RRU, Combiner, Antenna, cabling...) Incorrect cabling, As all sectors ave having low traffic issue so itis less likely to have bad HW on all the sectors; high probability i incorrect cabling (most likely due to Camscape camibiner) Will need to check what type combiner is installed on the site Y If cabling was wrong that may have damaged the combiner/ARU and we will need to replace HW Ww UR13XC102 COMBINER There are 2 types of combiner used and based on the combiner type cabling is different; check type of combiner installed on site using Antenna Asset form on Site handiex ¥ Comscope combiner serial # starts with “C* © RES combiner serial # starts with “RFS* BEIGOHG-t C2078 Pearse across SueEIZEST) RFS Combiner conTp,retainability - CASE study ‘TROUBLESHOOTING WITH CX TEAM YX team went to site and found incorrect combiner cabling ¥ — Fiting the cabling > didn't solve issue on this site ¥ Replacing the combiner ~ didn't salve issue on this site ¥ Majority of time fixing the cabling and/or replacing the combiner will solve the issue but far this site didn't, can be: ¥ Incorrect new combiner Cabling was not corrected Y Requested Cx team to bypass the combiner to see if traffic improve > Alpha sector # of UES increased fram 2 t0 50 I! © Bypassing combiner confirmed there was coverage issue Bypassing combiner confirmed the issue is on the tower not ground Gymassing combiner confirmed the issue is not due to 8H/Core LR13XC102 CFA/COR - POST Alpha Ww Gamma ulti ‘After bypassing combiner: CFR 8 COR improved forthe site cONTD. WOT MME dtops increased’én Gamma; but overall impact on CDR is low -> Should be able to improve with fine tuningretainability - CASE study s ‘COMBINER CABLING ISSUE - 2 ports to. connect Antenna ‘2 poniateonacet APU — Fert connect io RY Fort comnestie Antenna \ ) \ = 4 ports to connect RRU connectAntenna H Zport to connactRRU & 2 portsto ¥ RES combiner has 4 parts on one end that connects to RRU and 2 part on the other end connects to Antenna Comscope cambiner has 2 part an.ane end that connects ta AAU and 4 ports on other end {2 for RRU & 2 for Antenna) Y Most common issue is CX team connect 2 ports on one end that should be connected to RAU to the Antenna and connect RU to the 4 portsion the other end COMSCOPE COMBINER CABLING ripe f i ahmobility WwMobility - Intra (Preparation ow execution) Reporting — The UE sends the Source eNodeB an Event A3 that contains monitored neighbor cells Preparation — The Source eNodeB sends a request to the Target eNodeB, which performs admission control Execution — After successful preparation, the Source eNodeB sends a handover command to the UE eon Mobility Success Rate [9]: The ability to provide the requested service to the user with mobility /pmoPrepSuccLelntraF + pmHoPrepSuce telnterF pmHoExeSuceLtelntraF + pmHoExeSuecLtelnterF x 1001 -—~——rre—rr—S—EE’T eee See ees | ‘pmHoPrepAltLieintraF + pmHoPrepAttLteinter™ pmHoExeAtttelnraF + pmHoExeAtt.teinter= "| ese Handover Execution Handover PreparationMOBILITY X2 BASED HO PREPARATION MOBILITY X2 BASED HO EXECUTION |Mobility - Intra " jon / Z Fier outte inst arg Sacra Mesaremraiod |_| scale fitting biscl on ASRPoERSRO [7] herCoethcienUatap [*|_AnrcclindivduslOriscirancty serosa ~My a¥OMTt ‘heCoetFcientt VaryMobility = Intra (Pr eparation le execution) S X2 HANDOVER 2. HO DECISION Source eNB makes a HO decision based on Measurement Report. <—* LeesanMobility - S1 HANDOVER (Preparation / canon 2 - BRC mek Source ex Source Saw Source MMEon) S 2. HO DECISION Source eNB makes a HO decision based on Measurement Report. =e ‘Measurement Ri Aaacaperei Ho Wem i | cleat i ae its _retiloatenpsmite L_sCelltioa tempts [Best cut cet ¢ aMajor Reasons for poor mobil - ah (Preparation) ity S N ‘Typically, handover preparations fail if there is something wrong with the target cell. ¢ s 8 POLLS POSSIBLE CAUSES OF HANDOVER PREPARATION FAILURES MME pool should be same. if HO-Preparation fail = 100%, it might be due to MME pool different at source and tanget end. Y The command get. termpointmme can be used to find aut the MME pool is. different, set as per Market MME pool. SpidioWhitetist is active on the target, which has peimorypimnReserved set to true ‘Target cell is overloaded (High capacity): Need to offload target cell (already describe in accessibility part). ‘Target cell Unavailable: The target cel is down / disabled, PLAN Status is true but partOfSectorPower is set to maximum. ‘wlue. The cammand lgd can be used to check the site status, get . primarypimn is used to find out the PLMIN status and get power is used tofind out the site power status. ‘TAC not defined on site, as per network design : TAC onsite shauld be defined as per network design. If HO-Prep: fais not uniform for any cluster or market, then the command get. acs used to find out TAC status, License issue/Software issue. ‘Target cell has a fault (alarm, disabled cell, ete.) Site Configuration issue, POSSIBLE CAUSES OF HANDOVER EXECUTION FAILURES ANR PCI Conflict (Collision & Confusion)* Target exceeds cell range: The target cells more than 25km from the UE {or the current cll range setting) n that case Ho-Exec fail occur. Need to change cell range or cellindividualaftset b/w relation (as per required) Target is a sleeping cell ~ The target cel sleeping, noed fixed steeping on daly bass. ‘Target has high uplink interference® Poor RF conditions Due to radia deaf radio: if UL N+iis less than -119d8m, in that case Ho-Exec fall occurs iver) SiR taaes Buel ‘Abeady Mentioned in ApcossibiiyCounter-wise problem identification ¢ Steps a HANDOVER RELATED COUNTERS can be categorized as follows: - mHoPrepAttLteintrar IMHOEKeAttLtelntrar mHoPrepSuccLtelntraF [pmHoExesucelteintrak Primary imHoPrepRe|inLicMob Preparation Success Rate ~ pmHoPrepSuccttetntraf / pmHaPrepAttLteintraF Y Execution Success Rate “ pmHoExeSuccLteintraF / pmHoexeAttiteintra ¥ Handover Success Rate Preparation Success Rate x Execution Success Rate NOTE : Counters are pegged on the SOURCE!!!Paar eS for Intra LTE Z Tho titer longs, La mumbo of mansurgmants, wh | BOF SENG | Resta et eae ET tesco to on te tar where UE wis Een a ss rene sce fra eeasutament report to sowing, paramo, ange 0, 10, 20,40, €9, 80, 100, 130, 140, 160, 200. 260, $20, 40, 1280, 2860, 8120. Col lavel permaParameter tuning for Intra LTE HOSR Ww Some of the more commonly tuned / optimized parameters for improving intra LTE HOSR are as follows: 1. cellindividuatoffsetEutran 2. hysteresisA3 3, timeToTriggerA3 ‘The following table provides a brief description about the above three parameters for Ericsson systems (as defined in ALEX). waa) Puna deel Dra e RU RUN set value forthe neighbor jcell. Used when UE is in cellindividualOffsetéUtran connected mode. This terecy oe attribute can be modified by Bog yg IN functions. event The hysteresis value for hysteresisA3 ew (0.150 10 \dB I S 10.40,64,80, 100,128,160,258,3 | timeToTriggeras (The time totrigger value fOr 59 49 519 640,1024,1280,25, 640 ims. 160,5120 pressMobility - Inter ration obility preps fon / zZ IFHO FUNCTIONALITY FOR EVENT AS The IFHO functionality depends primarily on 6 parameters ‘aSThreshold2Rsrp: This determines the threshold below which the serving cell has to be. aThreshold2Rsrp: This determines the threshold above which the target cell has to be. ‘a5 Threshold2RsrpAnrDelta: This is added to aSThreshold1Rsrp. ‘aS Threshold2RsrpAnrDelte: This is subtracted from aSThreshald2Rsrp. ‘a2ThresholdRsrpPrim: This determines the level after which AS for IFHO should be triggered. ala2SearchThresholdRsrp: In case of MCPC, this parameter needs to be tuned. ‘a1 ThreshoidRsrpPrim: This determines if the UE has entered into good RF con cell and subsequently, event A1 is triggered. All A2 /.AS events will be cancelled. In order to understand IFHO lets consider the scenario with the different responsible parameters set to values as shown below for the source cell, eeu ee ns again for the serving Tararr Setingn:Mobility - Inter ratio ee ae Z IFHO FUNCTIONALITY FOR EVENT AS. sells ee emwucsom \ ES Seis aeeie SRP. &# . ASANRis Abis ’ ASIFHO is trogered trigger triggered ed Le le=s Time A- At this point, the source cell ASAP gets below aSanr] and target call ASRP gets better than aSanr2; therefore, AS ANR wil be triggered. ANR feature ‘oul now add neighbor relations /X2 inthe time duration between Point A and Point C. B — At this point, the source cell ASAP gets below ‘AStht and target cell ASAP gets better than aSth2; ‘then, the triggering condition for event AS is met; but iFHOwon't happen, since AZ is not yet triggered ‘Cane pint, vent a2 wiggued since the ‘source falls below a2thprim. D At this point, AS IFHO takes place; since event A2 ‘triggering condition is met as well as ASUh2 eriteria is also satisfied. NOTE: If. threshold is triggered between A2 ond AS trigger (between C and D}, then it cancels the handover measurements for IFHO and ‘he UE will nat be measuring other frequencies anymore. So, A1 threshold should be chosen more thon A2 threshold, in order to avoid this.Major poor mobility o (Preparation) Ss Typically, IFHO Handover (Prep & Exec) fails due to samething wrong with the target cell. Execution failure in POSSIBLE CAUSES OF HANDOVER PREPARATION FAILURES © IFHO Feature should be enabled at target e MME poo! should be same.** SpidHaWhitelist is active on the target, which has pimnfeserved set to true Target cell is overloaded (High capacity}. * ‘Target cell Unavailable.** TAC not defined on site, as per network design.** License issue/Software issue Target cell has a fault (alarm, disabled cell, etc) Site Configuration issue, BR RRRA SK “*Aroaidy Mentioned in int’a HOSR wma | 20180048 + Pape 0 “Already Mentioned in ApcossibiltyParameter tuning for Inter LTE HOSR W If MCPC enabled, then the following parameters are used : - - MACRO | DEFAULT moc PARAMETERNAME SITE | VALUE | PARAMETER TYPE ‘SPRINT CATEGORY heportcontigaS lasthresholdiRsRP | 107 | -140 | SprintGolden Parameter | Handover and Cell Reselection | IReportConfigas Lasthresholf2Rsne 5 | -136 | Sprint Golden Parameter | Handover and Cell Reselection ReportConfigaS. hysteresisAS 10 10 | Sprint Golden Parameter | Handover and Cell Reselection [ReportContigas imeToTriggers | 480 | 640 | Default Parameters | Handoverand Cell Reselection | SPRINT PARAMETER PARAMETER | VALUE-MACRO | DEFAULT moc NAME SITE VALUE [PARAMETER TYPE) SPRINT CATEGORY: al a2SearchThresh Sprint Golden Mobility Control At Poor Renortcomtigseareh inary | “103 |_ 734 Tiancine oT Grafie hysteresisA1A2Se Sprint Golden Mobility Control At Poor ReportConfigSearch larchftsrp 20 20 Feremeiee CoverageIRAT MCPC Feature Ww ¥ AT&T supports MCPC (Mobility Control at Poor Coverage}feature which is used to reduce IRAT HO triggering rate , keeping retainability intact. ¥ FGA (Field Guide Alert)56 used for single cartier site and FGA 50 is used for multi cartier site, ‘Here is the list of parameters for FGAS6: Permiss MoBCDIAtPOOT OF FoatuRO SITEOPT OY 1 ‘Global ‘MobCutAtPoorCav servceStatoMobCuAIPooray 1 ‘Giobal ‘EUtanc6tFDD ‘mODEIMARPOOrCOvACtVE TRUE ‘Global “RaporiContigSoarch ‘ala2Searchfhrosholofsm col TE 116 ‘iim | Ghobat ‘RepontContig Search ‘atadSearchTivesholdRatp TERAT_10 a2 Gm | _ Global ‘RoportConfigSeareh ‘ala2SearchThveshoiesmp inierRAT._S: =H10) am | Globot ReportConfigSaarch adCicalT wesholaitsrp a dm | Global TReparConfigSearch mmeTaTniggerAPCrtical 1200 ms_| Global ReeporConig@200 tie To Tnigger2 1280 ms_| Global Y — MobCtrlatPoorCov::featureStateStateMobCtriAtPoorCav (ENodeB, 1, boolean, Global} provides information about the licensed feature ~ Mobility Control At Poor Coverage. The feature needs to be set to 1 to activate it for single and multi carrier sites.Single carrier site ¥ MobCtriAtPaorCav.serviceStateStateMobCtriAtPoarCav (Enode8, 1, boolean, Global] indicates the licensed feature Mobility Control At Poor Coverage. The feature needs to be set to 1 (activated) for single and multi carrier sites. This is non operator configurable parameter. ¥ EUtranCellfOD::mobCtrlatPoorCovActive (Cell, TRUE, TRUE/FALSE, Global] Specifies if the feature Mability Control at Poor Coverage is enabled or disabled in the cell. The parameter nieetis to be set to TRUE for single and multi cartier sites. ¥ ReportCanfigSearch::0 12SearchThresholdRsrp (Cell, See Table, dBm , Global] The Reference Signal Received Power {RSRP) threshold value far events AlSearch and A2Search. Far single-carrier sites, ala2SearchThresholdAsrp replaces ‘a2ThresholdRsrpPrim parameter. it needs to be set to -116 for intra TE, -112 for interRAT_10 and -110 interRAT_S. Please refer to FGASO for the value on interLTE, mixedBW and multiCarrier sites. ¥ ReportCanfigSearch::a2CriticalThreshaldRsrp (Cell, See Table, dBm , Global] The Reference Signal Received Power {RSRP) threshold value far event A2Critical. The a2CniticalThreshaldRsrp parameter replaces a2ThresholdRsrpSec (it ‘was applied in single-carrier sites). The setting for a2CriticalThresholdRsrp is 122 for single and multi carrier sites. ¥ ReportCanfigSearch::timeToTriggerA2Critical (Cell, 1280, ms, Global] The time-to-trigger value for measurement in event A2Critical. This parameter is set to 1280ms for single and multi carrier sites. Y ReportConfigB2Utra::timeToTriggerB2 (Cell, 1230, ms, Global] The time to trigger value for the eventa2 measurement, This parameter is set to 1280ms for all sites. WPoor IRAT hosr - reasons & Ss solutions = Major reasons / causes behind poor IRAT handover success rate are as follows: - Y Coverage gap between LTE & 3G/Other Technology, Y — Iinproper parameter setting (ala2SearchThresholdRsrp, a2CriticalThresholdRSRP, b2ThresholdRscpUtra). ‘The Best way to optimize IRAT is doing physical optimization, We can use tilt meter to adjust the EDT. Antenna tilt can be checked through the command: get. electrical Antenna model no, can be checked through the command get. antennaWe can check following two counters to perform IRAT analysis. ¥ pmBadCovSearchEvaiReport ¥ pmCriticalBorderEvalRepart PROCESS TO FETCH THE COUNTERS: ‘STEP 1: Open ITK, Go ta Stats and then open PM Dyna View. STEP 2: Go to Additional Counter Select Node Type ENB and MO Class EUtranCellFDD and select the counter button as shown below: WwIf more samples are found under prtBadCovSearchEvalReport, we can change the values of the parameters — ala2SearchThresholdRsrp, b2Threshold2RscpUtra. We found that in WCLO1SS8, the gamma sector has high IRAT and also found very high samples under pmBadCovSearch€valReport. We, then, changed ( dBm and bz d tra fren t {Bim on 20/04 and found good improvement in IRAT as shown below. WeLo1sss_7¢_1IRAT improvement Solution Brocadiare Contd... Ww if mare samples are found under pmCriticalBorderEvalReport, we can change the value of the parameter — a2CriticalThresholdRssp. We found SCLO0197 Gamma sector has high IRAT and also faund very high samples under pmCriticalBorderévalfteport. AZI2015 00200 SCLOOIST FCA penflaaCov Search vsieepatt “24201 00-00 Scuvase7_70.8 ‘4252015 00:00 | ScLo0y#7_7C_4 26204 ODO | SCLOG “Wai048 oon | SCLUOTST_IC_4 ‘aez ‘aaeevs oo-o0 | scLoove7_7c_a 2580 We, then, changed the value of a2CriticalThresholdRsrp fram -122 dBm to -124dm on 04/29 and found good improvement in IRAT, freer ae coeshosr - CASE study se CASE 1: INTRA LTE HOSR (PREPARATION) Ss ‘Missouri LTE 800 HO-Piep Fail = 100% with a target cell; as the target cell is still not launched, buit FOO is unlocked/ enabled and primary PLMN status is TRUE (for a launch site primary PLMIN should be False). Probable solution: - © Target cell FOD should Be Locked ifthe site is ot launehed. the site is launched, in that cose Primary PLMIN status shauld be changed ta False. 5/3/2014 FVMGILOCBRULTEOIS474124 310170:354229-26 ° 1659 16859 5/3/2014 FVHGHLOCRBULTEO35474124 310120-354229-27 0 95250 ‘95250 FLEKMOIBBULTEOSSa0z7> at faa 240508-05:56:18 119.27.137.58 10.0rm Proxy Adm State Op,hosr - CASE study W CASE 2 : HO_PREP FAILURE DUE TO SECTOR DOWN EutranCellRelation —_% HO Fall Rate HO Prep Fail EUTRAN Cell Fd id Cascade 310120.434234.2 99.70% 56632 PTRCFLAHBBULTED43423421 ‘TaO3xCO6O Cellid #UE:s HBearers 100 200 anu ‘Note: Here we can see that 2nd sector not taking call as sectors down. Hence HO_Prep failure happening. CASE 3; HO_PREP FAILURE DUE TO SOFTWARE PACKAGE CORRUPTED EUtranceliRelation HO Fail Rate “HO Prep Fail Tampa Cascade 310120-434293-3. 93.08% 162382 ‘SPRGFLTEBBULTEO4S429331. ‘TAOBKCA2S 310120-434293-2 92.11% 151588 ‘SPOGFLTEBBLILTEO43429321 ‘TaO3KCI23 310120-434293-1. 92.86% 241738 ‘SPBGFLTEBBULTEDA3479311 ‘TAOBKCI23 Date & Time (Local}§ Specific Prablem MO (Cause/Addtianalinfo) {2013-11-21 19:35:20 M Disconnected ExternaiNode=2 (hubPosition: 6) 2013-11-22 45:17:20 M4 Upgrade Package Corrupt UpgradePickage=CxPI02051918_R230M (file_etrct) >>> Tatal: 2 Alarms (0 Critical, 2 Major OBSERVATION: In newly integrated sites, huge HO_Prep fall% have been observed, The main cause is found to be : - Softwar re package installed is getting corrupted.hosr - CASE study (CASE 4: ANR PCI CONFLICT en rer » Site A online in January ee i Site B online in February ~ Site A € > Site B neighbors » Site C online in March UE reports PCI, eNB executes HO to Site B instead of Site C W measResultlveighCells MheasesvItListe TRA (Sen) (=) MeasResuEUTRA #1 rely not CGIhosr - CASE study “ CASE 5 : HO PREPARATION FAILURE DUE TO INTRA LTE HANDOVER FEATURE DISABLED - Elrancelmoueon nt Pa ee ee HO Prep failures occurred in DXL23040 as IntralTEHandaver feature had been disabled. ouzanan ee ore od handover asot 1:67:16 199, 924.5.106 6.0€ eres MED MHL e152 toni en/tap/7a17 Wok SET Systeinct iol. Licensing-L. detion S422 Wok SET Spstaninetionaal_Laeensingel OptaenelFesturesct, In faLTeun We-2 wok SET SpeteaPumet iononl Halal Lgsnies moa Set Spsteafunctione-h Siul-os-20 Livseiae mid SET Spsteafunct ioneck 2649 Wek SET ue is Sstetinc iene Bubo5-37 19:21:05 a8