jNetX components are designed as modular building blocks that can be used to build services in IMS, 2G, 3G, WiFi/Wimax or convergent networks.

The jNetX Convergent Service Platform allows operators and service providers to have control over the speed, flexibility and efficiency in rolling out their product roadmap. jNetX achieves this by breaking the operator’s reliance on costly, proprietary service platforms or “black boxes.” The jNetX platform provides a programmable approach in a standards-based execution environment that allows operators to own their own network services and maintain and change these services as the needs of their customer base evolves.

The jNetX Convergent Service Platform combines the flexible programmability of an IT application server with the robustness of a Telecom IN platform. It is a fully standardized solution that, for the first time, enables the creation of a developer community within the Telecom time-critical domain.

The jNetX Convergent Service Platform is based on a standards-based, Java application server specifically designed for the telecom market place (JAIN SLEE). The JAIN SLEE application server is an event driven, carrier class application server built to run low latency, high throughput services. The application server includes a wide set of integrated protocols mapped to Java APIs. Such protocol mapping includes the support of voice (SS7 and SIP) and Value Added Service (VAS) capabilities (presence, data, charging, location, etc…). Below is a subset of the service elements that have been integrated into the jNetX platform to provide simplified service creation.

Core Network Elements

• Typical elements: Switches, MSC, S/GGSN, HLR/HSS, S-CSCF, MGW, etc.
• Typical Vendors: TEMs like Nokia Siemens Network, Ericsson, Motorola, Nortel, etc.
•  Typical protocols: INAP, CAMEL, AIN, WIN, MAP, SIP, Diameter

Value-Added Services Elements (VASP)

• Typical elements: SMSC, MMSC, WAP GW, Video Streamer, Location Server, Presence Server, Media Server, etc.
• Typical Vendors: LogicaCMG, Redknee, Comverse, etc.
• Typical protocols: SMPP, MM7, PAP, POP3, SMTP, SOAP, SIP, etc.

IT domain (SOA and 3rd Party AS domain)

• Typical elements: EJB container based Application Servers, Service Orchestration engine (BPEL, Biztalk ), .NET, Billing Systems.
• Typical vendors: IBM, SUN, Microsoft, Oracle, Bea, etc.
• Typical protocols: Enterprise Service Bus/JMS, Web Services/SOAP, OSA/Parlay/Corba, etc.

As depicted above, the jNetX Convergent Service Platform harmonizes the core network, VAS and IT domains, exposing such functionality to enrich services. This approach saves operators significant CAPEX / OPEX and dramatically reduces time to market.

The jNetX Convergent Service Platform includes the following four functional blocks:

• A convergent Abstraction Layer,
• A telco-grade and standards-based application server or JAIN SLEE (Java for Advanced Integrated Network Service Logic Execution Environment),
• A telecom Service Mediation block,
• A set of Gateways and integration components to link with external application servers (SOA, 3rd party OSA/Parlay AS, Legacy IN).

To complement the jNetX Convergent Service Platform, jNetX provides the Telecom Service Studio, a powerful tool used for network integration, service design and testing.

The jNetX Convergent Service Platform is based on a set of configurable and reusable components. Every operator has different requirements. As such, partners can reuse different components to build the configuration needed to meet each project’s specific requirements. For example, an Intelligent Network (IN) project will most probably require INAP/CAP, MAP, the telecom container and a few others components but not necessary any Gateways.

The diagram below shows the main blocks of the Telecom Service Studio (TSS) and of the Convergent Service Platform.