Slide title In CAPITALS 50 pt Slide subtitle 32 pt Proactive fault management in mobile core network Niko Isotalo Instructor: Ira Antikainen Supervisor: Timo O. Korhonen

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network Agenda  Objectives  Designin the Equipment  Further development  Conclutions

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network Objectives of the thesis To design system which will...  Efficiently detect faults and configuration errors from the customer network  Help network operator in more difficult problems  Be available as many customers as possible  Create clear procedures what to do when error has been found  Be easy to use and maintain

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network Design process challenges/problems 1.What tasks are needed to effectively manage customer network? 2.How to help network vendor in more demanding tasks? 3.How product availability for the all the customers can be assured? 4.How to create user interface which is easy to use? 5.How to measure user interfaces usability?

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network Effective management of customer network  Regular health checks  Regular backups  In case of alarm/fault logs are created and health check is done

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network Advantages for network vendor  Collection of all necessary logs  Information about already know product problems  In case of alarm/fault logs are created and health check is done

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network Product availability for all customers Where to place equipment: -All the customers does not have remote access to their network -Product should be available to all the customers – system will be placed on the customer network Security policy: -Customers has different security policies and some are tighter than others. Because of this systems securtity policy is strict, but flexible.

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network Designing user interface Usability goals: -System should be easy to use -System should be logical to use -System should guide you towards wanted action -System should be efficient to use -Visual expression should be neutral

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network Designing user interface Usability goals are met by following nine principles of user Centric design 1.Design for the users 2.Involve users in the development process 3.Be consistent 4.Use simple and natural dialogue 5.Reduce unnecessary mental effort by the user 6.Provide feedback to the user 7.Use prototypes to evaluate ideas 8.Usability goals should control the development 9.User centric attitude

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network Measuring usability of user interface Test scenario: 1.Add different network elements and specify task to them 2.Change configuration information of the nodes 3.List and delete network elements 4.Totally 61 different tasks

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network Measuring usability of user interface Usability of the user interface was measured by monitoring following attributes Percentage of succesfully completed tasks Time needed to complete these tasks Number of errors made Users subjective satisfaction

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network Measuring usability of user interface Results: Average number of errors (%) Average time spent completing the tasks Average number of errors Average satisfactory level 1,67min 57sec14

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network Furher Delvelopment  Update the list of know problems and procedure how those problems are solved  Rule-based classification algorithm, –This algorithm will predict error behaviour by searching for eventsets before the target event –Can predict critical events with 70% accuracy

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network Conclutions  Fault management can be improved with already existing tools by using those more efficiently  Using these same tools, support for customer can be offered faster  Designed system saves time –more time can be spent on root cause analysis of the new problems  Customer networks will be in better shape which leads to a more stable networks

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network Questions?

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt © Ericsson AB 2007Proactive fault management in mobile core network