RIL – LTEToLTENeigh object

Use case examples

February 7th, 2017

CONFIDENTIAL INFORMATION, RESTRICTED TO MYCOM OSI

© 2017 MYCOM OSI
This document contains forward-looking statements based on current expectations, forecasts and assumptions of the Company that involve
risks and uncertainties. Forward-looking statements are subject to risks and uncertainties associated with the Company's business that could
cause actual results to vary materially from those stated or implied by such forward-looking statements.
% HO attempt >10% over the past 5 days
Main formula:
• If((!Neighbor
Check![LTEToLTENeigh,Time].TimeShift(1).Rollup(Time.CountFirstAboveOrEqual(10.0),5)>=3.0),
1.0, 0.0)
• Checks if the neighbor object contributed over 10% of the handover attempts consistently for
the 3 days out the 5 days.
• RIL is ONLY interested in neighbors that match this condition. In theory, RIL is ready to purge
all neighbor objects that do not fit this criteria.

© 2017 MYCOM OSI Confidential

VoLTE DCR Analysis ->
Action
Main formula:
If((Length(!VoLTE_DCR_Analysis_1![eCell,Ti
me])==0.0), "No correlation found check
Alarm/VSWR/Parameters",
!VoLTE_DCR_Analysis_1![eCell,Time])
 DSS type of KPI that analyzes each eCell
and provides an textual output of the
possible issue.
 Many of the main child KPIs (29) check
counters at LTEToLTENeigh level or use
the ExpandOnDest operator to check
conditions on target neighbor eCells.
 249 KPIs in total – 124 of them act on
LTEToLTENeigh objects
 28 use the ExpandOnDest operator
 Very complex conditions

© 2017 MYCOM OSI Confidential

Thank you

CONFIDENTIAL INFORMATION, RESTRICTED TO MYCOM OSI

© 2016 MYCOM OSI
This document contains forward-looking statements based on current expectations, forecasts and assumptions of the Company that involve
risks and uncertainties. Forward-looking statements are subject to risks and uncertainties associated with the Company's business that could
cause actual results to vary materially from those stated or implied by such forward-looking statements.