**5.3 Distributed architecture and continuous monitoring**

To reduce SLM&M complexity, an enhanced architecture proposes to split the RDC&P into many smaller distributed and decentralized components. Additionally, continuous monitoring functionality has been added to the system (Figure 11).

Fig. 11. SLM&M distributed architecture.

However, the centralized web services that allow KPIs and KQIs monitoring are still relying on BPEL technology and still are very resource and time consuming. Indeed, the distribution of the Resource processes allows not only to share processes of KPIs but also to evaluate services locally. Thus, the distribution of EJB modules becomes necessary to incorporate mechanisms for monitoring locally but also to allow a local correction of QoS degradation and anomalies.

The new functional architecture of SLM&M (Figure 12) consists therefore of two main modules:


64 Telecommunications Networks – Current Status and Future Trends



• Show messages exchanged between web services (XML/SOAP) and modules.

• Monitor the activity and performance of physical resources such as network routers and logical entities such as CSCFs and the HSS (Home Subscribe Server).

• View the results of the audit and SLA verification, the customer class, and values of

To reduce SLM&M complexity, an enhanced architecture proposes to split the RDC&P into many smaller distributed and decentralized components. Additionally, continuous

However, the centralized web services that allow KPIs and KQIs monitoring are still relying on BPEL technology and still are very resource and time consuming. Indeed, the distribution of the Resource processes allows not only to share processes of KPIs but also to evaluate services locally. Thus, the distribution of EJB modules becomes necessary to

loads the customer profile and subsequently detects any SLA violation.

• List performance indicators collected from the network layer entity

• Check the provisioning chain of QoS management: PCRF, PCEF.

**5.3 Distributed architecture and continuous monitoring** 

monitoring functionality has been added to the system (Figure 11).

web services described above and synchronize their interaction.

a web interface that allows to:

Fig. 11. SLM&M distributed architecture.

KQIs.

responsible for SLA verification. It retrieves the KQIs of the currently delivered service,


Fig. 12. The main layer of SLM&M: Monitoring, Assurance.

eTOM-Conformant IMS Assurance Management 67



The implementation architecture features two sub-architectures for the service provisioning

**The Supply Architecture** which contains an IMS network that includes both the signalling and the media planes. The architecture includes three routers to transmit the media stream; a central router supports the IMS system. The PCRF (Policy and Charging Rule Function) is becoming an autonomous entity and includes other features such as policy management, and both edge routers include the PCEF (Policy and Charging Enforcement Function)


on which are connected an IMS terminal ad an Application Server;


in the core router Linux box;

Fig. 13. Centralized trial infrastructure.

**6.2 Trial infrastructure for SLA violation** 

and for service management and correction services.

functionality to receive and execute policies or PCC rules (Figure 14).

functionality of PCRF for QoS management and control.

Monitoring and management architecture: SLM & M is divided into two layers

The proposed functional architecture supports three communication channels between different modules:

