co psc example

Co-PSC issue: CNU5354x AND CNU5476ZSupporting slidesAlpesh shah

Slide title minimum 32 pt

(32 pt makes 2 rows

Text and bullet level 1 minimum 24 pt

Bullets level 2-5minimum 20 pt

!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵŶŷŸŹźŻżŽžƒȘșˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–—‘’‚“”„†‡•…‰‹›⁄€™−≤≥fifl

ĀĀĂĂĄĄĆĆĊĊČČĎĎĐĐĒĒĖĖĘĘĚĚĞĞĠĠĢĢĪĪĮĮİĶĶĹĹĻĻĽĽŃŃŅŅŇŇŌŌŐŐŔŔŖŖŘŘŚŚŞŞŢŢŤŤŪŪŮŮŰŰŲŲŴŴŶŶŹŹŻŻȘș

ΆΈΉΊΌΎΏΐΑΒΓΕΖΗΘΙΚΛΜΝΞΟΠΡΣΤΥΦΧΨΪΫΆΈΉΊΰαβγδεζηθικλνξορςΣΤΥΦΧΨΩΪΫΌΎΏ

ЁЂЃЄЅІЇЈЉЊЋЌЎЏАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯЁЂЃЄЅІЇЈЉЊЋЌЎЏѢѢѲѲѴѴҐҐәǽẀẁẂẃẄẅỲỳ№

Do not add objects or text in the footer area

Ericsson Internal | 2010-12-30 |

Overview

› This presentation highlights sudden degradation on Retainability performance of sectors in Half Moon Bay area for zone 10D.

Main reason for the drops was “Others”

› After ruling out regular site issues (alarms, RSSI, missing neighbors, neighboring site down, rehomes), the issue was identified to be due to launch of sector: CNU5354X sharing the PSC with one of the sectors:CNU5476Z in Half Moon Bay area.

› Retainability performance was improved by deleting neighbors involving the launched site (CNU5354) and locking the site until PSC change was made on it.

› This scenario could be used as one of the examples to identify sudden spike in drops due to “Others”.

› Tools used in analysis: Business Objects, RMAP


(32 pt makes 2 rows









Degradation on CNU5346Y, CNU5484Z and CNU5384Y coincides with launch of CNU5354X.

Increased drop rate: CNU5346Y, CNU5484Z, CNU5384Y


(32 pt makes 2 rows









PRACH data shows call setups on CNU5354X at distance of 18 miles

PRACH data: CNU5354X


(32 pt makes 2 rows









CNU5484Y has neighbors with CNU5476Z that has Co-PSC with CNU5354X. Though no RL failures were noticed on any of the impacted sites.

RL Attempts

CNU5346Y

CNU5354X

CNU5484Y


(32 pt makes 2 rows









Problem sectors: map view

Co-PSC issue:CNU5354X and CNU5384Z have same PSC:370

CNU5476Z has CNU5354X and CNU5384Z as neighbors .

PRACH data shows call setups on CNU5354X at distance of 18 miles.

RECOMMNEDATION:- Delete neighbors involving CNU5354X. - Lock CNU5354X and monitor the performance on CNU5346, CNU5484 and CNU5384.- Change SC for CNU5354X

18 miles

CNU5354 launched on 10/29.


(32 pt makes 2 rows









CNU5354X was locked at 1:35 pm

CNU5346: Retainability performance

CNU5346Y improved significantly after 1:35 pm after neighbor deletions involving CNU5354X and lock down of CNU5354X.


(32 pt makes 2 rows











CNU5346Y improved significantly after 1:35 pm after neighbor deletions involving CNU5354X and lock down of CNU5354X.


(32 pt makes 2 rows











CNU5384Z improved significantly after 1:35 pm after neighbor deletions and locking CNU5354X.

co psc example

Documents