Java in Telecommunications – Introduction

30 Mar, 2007

Why a blog on Java and telecommunications? There is no other industry for which the Java Community Process hosts so many specifications and I wonder if people are aware of this. Additionally, in May I’ll be doing a session on both JavaOne and Telemanagement World conferences. A nice trigger for a series of blog postings that starts with an overview of where Java plays a role in the telecommunications industry and with each subsequent post zoom in on the subject of the sessions: OSS/J Order Management and SOA.

As an aside, with the convergence of TV, Internet and telephony it is better to use the term Communication Service Providers (CSP) to capture the whole domain of TV, Internet and telephony.

Java Specification Requests (JSR) for CSP industry can be grouped as follows:

  • All JSRs targetted at the mobile devices (38)

  • The JAIN family of JSRs (28)

  • The OSS/J family of JSRs (12)

(Total number of JRSs 339, so more than 20% is related to CSPs).

Next to these specifications the CSP industry also makes heavy use of the better known parts of the Java platform like Java Standard Edition, Java Enterprise Edition, etc.

The first group of JSRs, Java on Mobile devices, is probably the best known use of Java in telecommunications industry. The enormous number of Java enabled devices consists for a large part of mobile phones and Sun will definitely highlight this again at JavaOne this year. The J2ME, MIDP, CLDC specifications are all targeted at these devices. They make it possible to create applications and games that run on many mobile devices. An example is GCalSync, which synchronizes Google Calendar with the calendar on your mobile).

Much less known is the use of Java in the core telecommunications network and in Operations Support Systems (OSS). The core telecommunications network is the network to which your (fixed or mobile) phone connects. This is the infrastructure needed to actually setup and complete a phone call from one device to another. The OSS systems are more in the IT side and take care of activating of services, billing etc. OSS systems often do not play an active role during a phone call. There is of course a connection between these the OSS systems and the core network. For example, for activating services an OSS Service Activation system will activate services on core network elements like switches.

The JAIN family of APIs is targeted at the core telecommunications network. These APIs define functionality to access core telco network protocols, do call routing, handle media and much more. Ax example of a protocol that many people might know is the Session Initiation Protocol (SIP). This protocol is used in many VoIP implementations and if you’ve played with VoIP on your computer you probably had to configure SIP Proxies etc. Within the JAIN domain there is even a special kind of application server, the JAIN Service Logic Execution Environment (JAIN SLEE).

Third, but not last, there is the OSS though Java (OSS/J) family of APIs. This family of APIs is targeted at the so called Operations Support Systems that all CSPs have to run their business. The Operation Support Systems cover functionality like activating services on the network, inventory management, fault management, trouble ticketing, order management and billing. One of te main goals of the OSS/J APIs is to slash the integration costs of OSS systems.

So much for the introduction, in the next post I will zoom in on parts of the work done by TeleManagement Forum and the basic ideas behind OSS/J.

Newest Most Voted
Inline Feedbacks
View all comments
15 years ago

[…] As promised in the first post in this series, we’ll now zoom in on the Telemanagement Forum (TMF) and OSS/J. This post will be a bit theoretical, but I promise that the next one will be more practical […]

Abdul Mannan
Abdul Mannan
15 years ago

I am a little bit onfused about the JAIN ann JCC implementations. Is this relly in use because I try to find resources related to JAIN and JCC, ISUP etc in Java but it seems that there is not much activity going on in this field.? I wish I am wrong 🙂

15 years ago

[…] In the previous two episodes in this series we described the position of Java in the Telecommunications industry, Telemanagement Forum and the basics of OSS/J. This episode focuses on the Order Management API (JSR 264), this is one of the OSS/J APIs being developed using the JCP process (proposed final draft 2 will be released May/June ‘07). It is also the API we covered during last weeks session at JavaOne. […]

15 years ago

[…] In the previous episodes in this series we started from a high level Java in the Telecommunications industry, zoomed in on Telemanagement Forum and the basics of OSS/J, described the basics of the Order Management API and now we’ll discuss why the Order Management API fits perfectly in an Service Oriented Architecture (SOA). Why is this a relevant question? Virtually any organization does with order management in one way or another and many organizations are currently evaluating or realizing SOAs. Reason enough to check if the Order Management API fits in an SOA. […]

14 years ago

Nice website.
According to you, which one is the ‘best’architectural approach for developing a scalable, extensable and highly available service delivery platform for hosting IMS services? OSA/Parlay or JAIN SLEE?
According to me, OSA/Parlay does not provide an ‘execution environment’like JSLEE does.
Just wanted to know your opinion on this issue, as SDP is a hot topic nowadays.

Explore related posts