Use Cases

Use Cases OSS4.1, Reporter 3.2 REP ESS

For public use – IPR applies 1 © Nokia Siemens Networks

Use Cases / Georg Steffen / 05-Jul-07 / 13-541730 v1.1

Nokia Siemens Networks Academy Legal notice Intellectual Property Rights All copyrights and intellectual property rights for Nokia Siemens Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Siemens Networks training material, are the exclusive property of Nokia Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individuals can use the Nokia Siemens Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Siemens Networks. The Nokia Siemens Networks training material cannot be used outside of an agreed Nokia Siemens Networks training session for development of groups without the prior written agreement of Nokia Siemens Networks.



Session Objectives After completing this learning element the participant will be able to: Name examples for reporting contents with OSS4 Describe the contents of some Nokia Default Reports Understand use cases of different technological areas Demonstrate, how to access Nokia FM Reports



Report Sets and Use Cases Reporting Content Default Report Sets FM Report Sets Report Types



Reporting content in OSS4.1

Default Report Sets



Reporting Suite

Default Reports Default Reports deliver Reporter Content predefined by Nokia They can be used to view reports or as templates for creating your own report definitions Default Reports are divided into network technology specific subsets which can be installed separately based on customer’s needs Default Reports are implemented with Report Builder (2G, 3G, GPRS, IN) or with On-Demand Report Toolkit (FM, 2G Observations)



Default Reports



Default Reports The default report sets offer pre-defined KPIs (Key Performance Indicators) to make it easier for the operator to optimise the performance of the network and perform troubleshooting tasks. The default report sets are designed for daily reporting needs at a regional level and they are included in every NetAct delivery.The reports meet the information need on traffic, resources and mobility. Most of the default reports are implemented as PLMN-Hourly level reports.



Default Reports for 3G (RAN) Allocated Dedicated Channel Capacity, PLMN - Hourly • Allocated DL Dedicated Channel Capacity • Allocated UL Dedicated Channel Capacity RAB Drop Ratio, PLMN – Hourly • RAB Drop Ratio, NRT Services • RAB Drop Ratio, RT Services other than Voice • RAB Drop Ratio, Voice RAB Setup and Access Complete Ratio, PLMN - Hourly • RAB Setup and Access Complete Ratio, RT Services other than Voice • RAB Setup and Access Complete Ratio, Voice



Default Reports for 2G (BSS) 1/2 TCH Traffic Sum, PLMN–Hourly • Average CS Traffic Handover Causes, PLMN-Hourly • Other HO Causes • Cause Down Lev • Cause Down Qual • Cause Intfer Dwn • Cause Intfer Up • Cause Pbdgt • Cause Up Level • Cause Up Qual

SDCCH & TCH Availability Reports • SDCCH & TCH Availability, PLMN–Hourly – SDCCH Availability – TCH Availability • Top-10 BTSs by SDCCH Unavailability – 10 BTS with least SDCCH availability • Top-10 BTSs by TCH Unavailability – 10 BTS with least TCH availability SDCCH Blocking Reports

Handover Success Reports

• Handover Success I/O, PLMN-Hourly – Incoming HO Success – Outgoing HO Success • Top-10 BTSs by Incoming HO Failure – Incoming HO Failure • Top-10 BTSs by Outgoing HO Failure – Outgoing HO Failure For public use – IPR applies 10 © Nokia Siemens Networks


• SDCCH Blocking, PLMN-Hourly – SDCCH Blocking • Top-10 BTSs by SDCCH Blocking – SDCCH Blocking

Default Reports for 2G (BSS) 2/2 Signal Quality Reports • Average UL/DL Signal Quality, PLMN-Hourly – DL Signal Quality – UL Signal Quality • Top-10 BTSs by Average DL Signal Quality – DL Signal Quality • Top-10 BTSs by Average UL Signal Quality – UL Signal Quality Signal Strength Reports • Average UL/DL Signal Strength, PLMN-Hourly – DL Signal Strength – UL Signal Strength • Top-10 BTSs by Average DL Signal Strength – DL Signal Strength • Top-10 BTSs by Average UL Signal Strength – UL Signal Strength


TCH Blocking Reports • TCH Blocking, PLMN–Hourly – TCH Blocking • Top-10 BTSs by TCH Blocking – TCH Blocking TCH Drop Rate, PLMN-Hourly • TCH Drop Rate Top-10 BTSs by Drops per Erlang • Drops per Erlang Traffic in Call Minutes, PLMN-Hourly • Call Minutes


Default Reports for 2G (NSS) 1/2 Average Call Minutes in Circuit Groups Reports • Average Call Minutes in Circuit Groups, CGHourly, CG-Hourly ¾ Average Call Minutes in Incoming CG ¾ Average Call Minutes in Outgoing CG • Average Call Minutes in Circuit Groups, MSC-Hourly, CG-Hourly ¾ Average Call Minutes in Incoming MSC ¾ Average Call Minutes in Outgoing MSC Average Call Minutes in Traffic Categories Reports • Average Call Minutes from and to Mobile Subscribers, MSC-Hourly, MSC-Hourly • Average Call Minutes from and to Mobile Subscribers, PLMN-Hourly ¾ average call minutes, i.e. calls from and to mobile subscribers on MSC or PLMN hourly level


• Average Call Minutes of MOC/MTC, MSC-Hourly • Average Call Minutes of MOC/MTC, PLMN-Hourly ¾ average call minutes of mobile originated and mobile terminated calls on MSC or PLMN hourly level Average Traffic in Circuit Groups Reports • Average Traffic in Circuit Groups, CGHourly ¾ Average amount of traffic in Incoming and outgoing CG in Erlang on CG hourly level • Average Traffic in Circuit Groups, MSCHourly ¾ Average amount of traffic in Incoming and outgoing CG in Erlang on MSC hourly level


Default Reports for 2G (NSS) 2/2 Average Traffic in Traffic Categories Reports • Average Traffic from and to Mobile Subscribers, MSC-Hourly, MSC-Hourly • Average Traffic from and to Mobile Subscribers, PLMN-Hourly – average amount of traffic, i.e. calls from and to mobile subscribers in Erlangs on MSC or PLMN hourly level • Average Traffic of MOC/MTC, MSC-Hourly • Average Traffic of MOC/MTC, PLMN-Hourly – average amount of traffic of MOC an MTC in Erlangs on MSC or PLMN hourly level Call Success in Circuit Groups Reports • Call Success in Circuit Groups, MSC-Hourly • Call Success in Circuit Groups, PLMN-Hourly – call success ratio in circuit groups on the MSC or PLMN hourly level for incoming and outgoing calls


• Top-10 Outgoing Circuit Groups by Call Unsuccess – Call Unsuccess of Outgoing CG • Top-10 Incoming Circuit Groups by Call Unsuccess – Call Unsuccess of Incoming CG Subscribers in HLR reports • Subscribers in HLR, HLR-Hourly • Subscribers in HLR, PLMN-Hourly – subscriber amount in HLR on HLR or PLMN hourly level Subscribers in VLR reports • subscribers in VLR, MSC-Hourly • Subscribers in VLR, VLR-Hourly – subscriber amount in VLR on MSC or PLMN hourly level


Top Management – use case (RAN example) Requirements for top management: • High level information easy at hand • Get an overview on the network operations at one glance • Weekly report (graphs only), with main KPIs and network outages of the last week and long history graph and brief text information for strange or unexpected results. • Trends are important • Most KPIs graphs will be on PLMN level Workflow: • Management usually selects a couple of KPIs and expects reports on these • Reports are either taken from Nokia content or created • Reports are published to manager group and can be accessed via web at any time, always using the latest data For public use – IPR applies 14 © Nokia Siemens Networks


Top management – example RAN 1 Call traffic (= allocated dedicated channels) mean money! Report can be discussed for example once a week in top management meeting: is the business growing? This report could be one information sources to decide about actions (marketing campaigns, weekend tariffs etc.)



Top management – example RAN 2 RAB Setup and Access completed -> 100% means quality. Check whether the planned network expansion has any effect on the quality of services. This should be constantly monitored by the management, corrective actions make sure that the impact is very small.



Technical Management – use case (BSS example) Requirements for technical management: • High level information as a starter • Fast drill down to problem areas • CM : Daily report (table only) with configuration data on cell level • PM : Daily KPI report (tables only) with failing network elements according to agreed thresholds on cell level for BSS/GPRS and MSC level for NSS. • FM : Daily report (table only) with the outage from network elements as lowest cell level. Daily report (table only) with most frequent alarms and most producing alarming objects. Workflow: • Daily check for important network counters / KPIs in a set of 10-30 reports • Sometimes on lower level than PLMN (per maintenance region, BSC, ...) • Top-X reports help to priorisation of the work • Usually own reports, set up by the requirements of the operator • Drill in needed to start root cause analysis easily For public use – IPR applies 17 © Nokia Siemens Networks


Technical Management – example BSS 1 First have a look at the TCH Usage in the BSS Traffic Reports Compare the Daily/Weekly values In general the values should be as high as possible



Technical Management – example BSS 2 Look into the TCH Blocking of the BSS Quality Reports: Does the TCH blocking increase? Check the different BSC level reports for TCH Blocking: Which BSC is in a city area? • Look into the TCH Blocking Top 10 reports: Which are the worst ones?



Technical Management – example BSS 3 In the TCH Drop Causes reports it becomes obvious that most of them are radio failures (for example somebody steps in an elevator while telephoning) On PLMN level the reports are not so informative, therefore check individual cells.

• For this look into the Top 10 BTS by Drops report to check which are the worst cells For public use – IPR applies 20 © Nokia Siemens Networks


Network Monitoring/Optimisation – use case (NSS Example) Requirements for Monitoring & Optimisation: • Low level information • Easy access to all the counters • Fast navigation in the data (drill in/out, switch to other counters etc.) Workflow: • Request reports in case of a problem • Daily check for important network counters • Usually for a certain network element, or a group of elements



Network Mon./Opt. – example NSS 1 Look a the Data Call Clear Code groups on an hourly level. Which phase of a call, ring, signal or speech, produce the highest level of clear codes at which time of the day. Further action: Drill into MSC and CG level to find out the reason for the clear increase.



Network Mon./Opt. – example NSS 2 Compare the Call Minutes of MOC and Call Minutes of MTC reports on PLMN-DAILY level. Are the call minutes increasing? How is the profile on weekends and working days? For example pricing for calls from the fixed network into the mobile network (and vice versa) affects this quite heavily For public use – IPR applies 23 © Nokia Siemens Networks


Report Set for Fault Management

Most frequent alarms in the network Most alarming network elements Alarm distribution for a selected network element Number of network elements that produced the selected alarm Number of occurrences for a selected alarm



Report Set for FM



Document change history Date

Versio n

Name

Change comment

12.05.07

1.0

Georg Steffen

Adaptation from technology specific NOCREP documents

05.07.07

1.1

Georg Steffen

New template



Use Cases

Recommend Documents