User Interface of a GSM Capacity Analysis Tool

1. User Interface of a GSM Capacity Analysis Tool Thesis work presentation 13.11.2007 Author: Rami Ertimo Supervisor: Patric Östergård Instructor: Nilmini Lokuge

2. Agenda • Introduction to the Study • Problem Setting, Objectives, Research Methods • Capacity Analysis • User Requirements • User Interface • Conclusions

3. Problem setting • Fractured data spread across operators’ OSS related to EGPRS Capacity Analysis • Different bodies of the organisation involved in fixing different domains of the EGPRS network • No view of the overall situation in the network • These causing inadequate network performance and loss of revenue.

4. Objectives • Gather and categorise user requirements • Analyse user requirement to build a conclusive workflow to support the needed functions in Capacity Analysis • From the user requirements and workflow build a easy to use User Interface that seamlessly supports the workflow and also individual user requirements

5. Research Methods • Literature study • Specification related to GSM, GPRS and EDGE (ITU, 3GPP) • Books related to usability, user-centered design, network optimisation, capacity analysis, EGPRS networks • Publications and web pages related to user interface creation and user-centered design. • Practical part • Gathering User Requirements (interviews, workshops) • Analysing User Requirements  Creating User Stories • Iterating over: • Prototyping • Collecting feedback • Revisiting design and prototype • Ensuring end product design

6. Agenda • Introduction to the Study • Problem Setting, Objectives, Research Methods • Capacity Analysis • User Requirements • User Interface • Conclusions

7. BSC GPRS/EDGE capacity analysis BSS Application Servers Application Servers in Internet 2GSGSN GGSN Gb PCU Abis/EDAP Radio Four Analysis Domains: Radio interface capacity analysis Abis interface EDAP pool size capacity analysis BSC/PCU capacity analysis Gb capacity analysis

8. Edge-2-Edge view for Capacity Analysis • Reliability in trouble shooting • Performance decrease is usually seen in BTS KPIs even though the actual problem is elsewhere. • Tool should help in identifying the correct root cause of the problem • Accuracy for dimensioning • When adding capacity see and understand the bottleneck domain and required size • Over dimensioning can be avoided and desired capacity can be ensured in whole chain • Speed and easiness of all steps • Offer one view to see all the elements and interfaces • Highlight the capacity bottle necks and guide the user to over come the problem • Help to identifying the changes in one place cause any bottlenecks elsewhere

9. Agenda • Introduction to the Study • Problem Setting, Objectives, Research Methods • Capacity Analysis • User Requirements • User Interface • Conclusions

10. User Requirements • User Stories • High-level definition of a requirement • Short description of a piece of functionality told from the user perspective • Focus on the user • Leaves enough room for design • Can typically be easily mapped to User Interface functionality • Problems with text formed requirements  They do not visualise the desired solutions in clear manner • Example: • “As a Network Planning Expert, I can modify the GPRS territory”

11. Workflow

12. Agenda • Introduction to the Study • Problem Setting, Objectives, Research Methods • Capacity Analysis • User Requirements • User Interface • Conclusions

13. User Interface • Demo about: • CM and PM Import • Visualisation features related to: • Navigator • Custom Labels, Capacity View • Browser • Profiles, CM and PM parameters • Map • Sites, Cell Icon, Cell Area, Parameters related to map • Preferences • Capacity Analysis • E-2-E Analysis • Different Domains

14. Import and Preferences

15. Overall User Interface

16. Agenda • Introduction to the Study • Problem Setting, Objectives, Research Methods • Capacity Analysis • User Requirements • User Interface • Conclusions

17. Conclusions • User Stories in addition with well defined workflow help in identifying missing features and gaps in the UI workflow • Truly user friendly and usable interface requires iteration over iteration over iteration • Centralised solution to analyse the whole BSS domain helps in the analysis capacity bottleneck and reduces operator OPEX and CAPEX. • Only the first step towards the right direction: • More automation needed • Need to be proactive rather than reactive • The radio domain is not sufficient for an End-2-End solution • EGRPS network are being complemented with UMTS networks • Many operators have multiple vendors

18. Thank youQuestions?