Using JCC for Portable, Network Independent JAIN SLEE Services

Abstract

This paper presents an overview of an approach for creating portable services for JAIN SLEE using JAIN Java Call Control (JCC). The services built using this approach are protocol independent so they can be deployed in networks with different protocol variants or event completely different protocols.

Introduction

At a high level the requirements for portable services are as follows: A standard execution environment. Multiple op cos can chose the implementation of the execution environment which best suits their requirements. A standard abstract API for call control. Management of execution environment must be flexible so that it can be integrated into many different operator management infrastrutures. Service components should be reuseable in other services. Meet the performance and availability requirements for larger subscriber base carrier environments as well as smaller carrier environments. An environment which is financially viable for large and small operators.

These requirements must all be met if a service to be successfully deployed. In addition to these, services to be created by 3rd parties have the following requirements: A policy framework to manage access control for third parties. An open development environment which third parties can use to develop applications and which simulates the behaviour of the operator network. Deployable in the operators core network for mass market services. 3rd Party Management Portal to provide operator control over deployment and provisioning.

Ideally, a single architecture should be created to enable the following types of service redeployment: Operator core network deployment to operator core network deployment. From a third party deployment to third party deployment in another operator. From a third party deployment to an operator core network deployment. An operator core network deployment to a third party deployment.

What is JAIN JCC?

The JAIN Java Call Control (JCC) is an implementation standard for call control in Java. With the related protocol Java Coordinations and Transactions (JCAT) it provides all the capabilites required for the creation of common AIN services, converged voice/data and next generation services. JCC/JCAT is related to Parlay. The call state model used by JCC is the same as Parlay. However, the architecture presented in this document is a service oriented architecture and does not use Parlay's gateway model. The spec lead for JCC, Jean-Luc Bakker, is also the spec lead for Parlay MPCCS.

Portable, Network Independent Services using JCC and JAIN SLEE

A JAIN SLEE provides a standard execution environment for communications applications. Services developed to the JAIN SLEE standard are structured as collections of resuable object-oriented components. Portable services in this architecture are built to the JAIN SLEE programming model. These services can be deployed in any compliant JAIN SLEE implementation. To provide protocol portability, JCC is used to provide an abstract API for call control. Protocol support issues are delegated to the SLEE's resource adaptation framework. A resource adaptor built for this architecture presents a JCC interface to the service deployed within the SLEE and provides a translation layer to the target protocol.

JCC is more abstract than network protocols such as INAP, CAP and SIP. This means that it can be used as the interface for applications. Resource adaptors with the same JCC interface can be created for CAP, CAP v2, INAP variants, SIP and other protocols. The following diagrams shows the structure of a JCC RA built for this infrastructure.

Third party services are an extension of portable services in this architecture. They are built using JAIN SLEE programming model and JCC as in the portable services but in addition to this the JCC resource adaptors have a policy framework which allows the operator to apply controls to network access, deployment and services provisioning.

The policy framework for network access is invisible to the services. It is a layer of the Resource Adaptation Framework which controls access to network resources. A management interface allows an operator to configure the policies for the 3rd party. Both 3rd party and operator deployments are very similar. Neither uses a gateway model so the performance and availability of the service is largely depended on the JAIN SLEE cluster into which the service is deployed. For 3rd party services the cluster would provide typically host many services from many 3rd parties. This cluster would provide quality of service related to the agreement negotiated with the 3rd party for the application. For large subscriber base service deployments, another JAIN SLEE cluster would be used. This cluster would provide a higher level of performance and availability to meet more stringent quality of service requirements. Using this architecture the operator maintains control over the there key assets such as their subscriber base. All services are deployed within the operators environment. This hosting arrangement is another avenue for revenue generation for operators.

3rd Party Mangement Portal

The 3rd Party Management Portal provides a controlled access point for 3rd parties into the the service execution environment. Policy controls are set by the operator to manage access to the network, deployment and provisioning. The close alignment and interoperability with the J2EE enterprise application server environment allows JAIN SLEE to offer third party authenticated and authorised core network access via web services. As JAIN SLEE specifies a complete service logic execution environment, rather than a set of APIs, the carrier has complete control over what data and logic is exposed to third parties. A typical 3rd party company will be able to deploy a new service into the operator's infrastructure and access network resources, functions and, quality of service as defined by the agreement between the operator and the company. The agreement will be inforced by the policy framework within the Management Portal and within the JAIN SLEE Resource Adaptation Framework. The Management Portal can also be used to manage the process of moving services from test into production.

Meeting the Requirements for Portability and Network Independence

Summary

The architecture outlined in this document can be used to create services which satisfy the key requirements of portable and 3rd party services. The architecture not only satisfies the technical requirements of service portability but can be implemented with business models for large and small operators.