The jNetX Convergent Service Platform includes the following four functional blocks:
| Abstraction Layer:
Any SS7 or IP-based protocol can be directly integrated into the jNetX Convergent Service Platform.
jNetX provides a set of tools to facilitate this integration. Once integrated, protocols are abstracted to a set of APIs exposed either to the
JSLEE or to the set of supported Gateways. jNetX provides two levels of abstraction: Low-level (protocol level like SIP Servlet APIs) or Medium-level
(OSA/Parlay APIs). The abstraction layer also provides functions like load-balancing, overload protection, service selection, etc.
|
|
| Service Logic Execution Layer (SLEE):
Once created with the jNetX Telecom Service Studio or with any other Java IDE, applications (called SBB – Service Building Blocks)
can be deployed within the JAIN SLEE application server. This execution environment follows the JAIN SLEE specifications as defined by the Java Community Process (www.jcp.org). jNetX successfully achieved JSR 22 (JAIN SLEE 1.0) compliance in January 2005 (http://java.sun.com/products/jain/certprod_table.html). These specifications have been specifically defined to meet rigorous telecom constraints such as an asynchronous invocation model, high availability / fault tolerance, low-latency, and high-performance.
|
|
| Brokering (SCIM/IN Mediation)
The jNetX Service Brokering solution is archived by a set of components that perform service selection, service interaction / sequencing and service composition. IMS refers to this function as the
SCIM and within IN and OSA jNetX is calling it: IN Mediation.
|
|
| Exposure / Integration Layer:
The Exposure / Integration Layer includes a set of Gateways such as:
- OSA/Parlay GW
- Web Services GW (incl. Parlay X)
- IM-SSF
- proprietary exposures (JavaEE)
These Gateways generally use the same Service Enablers (API capabilities) as used by the JAIN SLEE container for delivering end-user applications.
|
|