• strict warning: Non-static method view::load() should not be called statically in /home/universe120/www/sites/all/modules/views/views.module on line 879.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home/universe120/www/sites/all/modules/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home/universe120/www/sites/all/modules/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter_node_status::operator_form() should be compatible with views_handler_filter::operator_form(&$form, &$form_state) in /home/universe120/www/sites/all/modules/views/modules/node/views_handler_filter_node_status.inc on line 14.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/universe120/www/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home/universe120/www/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.

New case study available! Case study Part 1 - Self-Diagnosis/Healing for IMS VoIP and VPN

News date: 
Mon, 2012-09-17

The UniverSelf project is proud to announce the release of the case study- Part 1: 

Use Case #1 - Self-diagnosis and self-healing for IMS VoIP and VPN

The case study can be accessed under the Dissemination/White papers section, or directly at the following link: http://www.univerself-project.eu/white-papers


This document presents a high level description of the UNIVERSELF project case study on Self-diagnosis and self-healing for IMS VoIP and VPN services, its methods, concepts and expected innovation. The specific functional, non-functional requirements and the associated problems of this case were presented in the deliverable D4.1 [3]. The prioritization of the problems and functional requirements were presented in deliverable D4.2 [4].

This case study considers self-diagnosis and self-healing features with two mains applications for a same network topology: Self-diagnosis and healing of IP networks and IMS services [5][6]and Self-diagnosis and healing of VPN networks [7].

Objectives are to enable proactive and improved reactive diagnosis and healing. Proactive diagnosis is important to prevent incident impact and it is not done today. An improved reactive diagnosis reduces the delay between incident, its detection and reparation. Then it improves customer experience.

Self-diagnosis and Self-healing must be based on reusable and flexible components to prevent the redesign from scratch of the process for new services or changes in network configuration.

Then Self-diagnosis and Self-healing must support an end to end service view facing multiple network domains and technologies which are currently managed by dedicated teams with dedicated & ossified tools. This end-to-end view is tightly related to the end-user service self-diagnosis and healing.