JAIN SLEE architecture

The first and foremost thing to do before understanding the concept of JAIN SLEE is defining the term. SLEE stands for Service Logic Execution Environment. A SLEE is essential in the communications industry where it provides an event processing application environment with high throughput and low latency.

• Throughput - average rate of successful message delivery over a communication channel (in a communications network)
• Latency - Delay (how much time it takes for a packet of data to get from one designated point to another) 

Now back to the main topic; JAIN SLEE


JAIN SLEE/JSLEE is a Service Logic Execution Environment based on Java. The actual definition is Java APIs for Intelligent Networks Service Logic Execution Environment.

This is the only industry standard focusing on portable communications applications. Therefore it happens to be essential for mobile application providers. Since Java is also based on the concept 'Write Once, Run Anywhere', implementing JAIN SLEE enables communications applications to be written once and run on many different implementations of JAIN SLEE. A variety of companies including IBM, Motorola, Siemens, Vodafone, Sun Microsystems etc have contributed for the development of this specification.

   

So how does JAIN SLEE ensure the development of portable applications?

This is achieved by the combination of a programming language API, a clear technical specification, a Reference Implementation, and a variety of tests that a vendor must pass to ensure that the product is complies to the JAIN SLEE specification.

The advantage of JAIN APIs is that they enable the rapid development of Next Generation telecom products and services on the Java platform. JAIN SLEE provides the central component to these JAIN APIs. 

The specification includes a component model for structuring the application logic of communications applications as a collection of reusable object-orientated components, which ensures the rapid development of robust applications. In addition, it also specifies the way for composing these components into higher level, more sophisticated services. Furthermore it also defines the contract between these components and the container that will host these components at run-time.