**5.4 Correction architecture**

The architecture of SLM& M consists of two layers: Assurance and Monitoring, by analogy with the previous architecture (distributed). The Monitoring layer is distributed and contains only two main processes of collection and processing of information.

New processes must be integrated in a centralized way; a distributed integration can overload collection agents in routers and. For example in a router memory is crucial,; collection agents and processes DRC & P and RPM are reasonable for just performance collection and data local treatment. However, the addition of another process could overload the router that needs its capacities for traffic conditioning and processing.

The Resource Trouble Management process (RTM) catches alarms that reflect a degradation of service resulting from a physical or logical related to equipment; this process then tries to make a preliminary correction of the service and notifies WS-Service.

The WS-synchronization process is located in the same server as WS-Resource, so that this server can synchronize incoming events and data collection, and decide either to perform a normal SLA verification, or to report a violation. Also, the Resource Provisioning process is responsible for making resource reservations with respect to solution recommendations provided by WS-Service. WS-Service adds to its repertoire Service Problem Management (SPM) processes.

The interaction between WS components of SLM&M is through SOAP/HTTP, whereas the interaction between Monitoring layer of SLM &M and IMS layers uses Java-based client / server communication, with a spare possibility of using XML/RPC (Mi-Jung et al., 2004) between the (Resource, IMS ASs) and WS-Resource modules.
