[attachment=10093]
[attachment=10093]
Abstract
Service Level Agreement implementation for the Internet Service Provider will define the Service
Level Agreement for the Quality of Service Parameters like Latency etc. More bandwidth is required providing services like video conference but the bandwidth required for the normal internet browsing is less. The idea of the QoS system is to enable you to allot specific applications and Web sites with a set of service parameters. For example, if your server hosts a number of Web sites, you might want to tailor your performance parameters to give specific service levels and priorities to a given site so that you can provide a service level of quality.This involves fine-tuning the various systems so that you can allocate the site specific amounts of CPU time (or even specific CPUs), memory, and bandwidth.They are:
Limiting Connections Setting Connection Timeouts
Utilizing HTTP Compression
Throttling Bandwidth
Enabling HTTP Keep-alive
Enabling CPU Monitoring
Configuring Application Pool Queue Length Limits
System Requirement Specifications:
Hardware Requirements
Pentium IV 500 MHz
512 MB RAM
500 MB Free Hard disk space
Software Requirements
Java 2 platform (J2SE 1.6)
Servlets, JDBC, Java script, Html, Xml
Windows XP.
2.1 Introduction to Project.
SYSTEM STUDY DOCUMENT :
Our proposal is mainly based on, makes reference to the definition of an information document named Service Level Indication (SLI). Monitoring information, related to a specific
Service Level Agreement, are so retrieved from the network and provided to the user application, by collecting and appropriately combining performance metrics and measures in an SLI document instance.
Users can choose among different levels of Quality of Service in order to best meet their application and pricing constraints. The service and its delivery quality are negotiated through a contract, named Service Level Agreement (SLA), between a user and a service provider.
From the user’s point of view, SLA monitoring represents an important functionality as it allows getting information about the fulfillment of negotiated service parameters. By exploiting such a functionality, a user can identify possible violations of his SLA or trigger an SLA renegotiation
if the current level of QoS is not satisfactory.Similarly, the service provider can ask for SLA renegotiation in order to optimize resource utilization. Therefore, monitoring seems to offer excellent novel opportunities to service providers who do have the possibility to effectively engineer their network infrastructures. By this way, they can exploit at its best the unprecedented potential disclosed by dynamic service
creation and delivery. In this case, “SLA monitoring” may be seen in the light of a more general activity related to “Network monitoring”, and this is mainly due to the following objectives:
usage-based accounting
traffic profiling
traffic engineering
attack/intrusion detection
Definations, Acronyms & Abbreviations:
1. SLA:
A Service Level Agreement (SLA) is a contract between a network service provider and a customer that specifies, usually in measurable terms, what services the network service provider will furnish and what penalties will assess if the service provider cannot meet the established goals. Service provider’s differentiation will be driven by the reliability of the SLA Management and its monitoring during exploitation to contributing to the customers trust.
In order to guarantee customers the proper level of performance, service providers often offer services with SLAs, which provide customers with measurements of statistics like network availability, throughput, and latency.
2. SERVICE LEVEL SPECIFICATIONS
The Service Level Specifications (SLS) are the technical specifications deriving from the SLA. SLS can be a precise specification directly related to the SLA, but it can also be an interpretation of the SLA, an adaptation depending on the provider or on the service.
To propose an End-to-End solution to SLA/QoS management, it is necessary to define services, SLS parameters and a classification of these services depending on the SLS parameters. The focus on service level rather than on network level allows definition of service/SLA/QoS independently from the underlying network technology.
3. Services and SLS Parameters
Table 1 represents a non-exhaustive list of services giving a panel as large as possible (audio, video, data, and tunnel). Table 2 represents a list of SLS parameters. These parameters are network technology independent