Java APIs for Integrated Networks: Difference between revisions

Revision as of 15:27, 18 October 2005

Latest revision as of 01:00, 4 March 2020

(30 intermediate revisions by 25 users not shown)

Line 1:

{{Redirect|JAIN}}

'''JAIN''' is an activity within the [[Java Community Process]], developing APIs for the creation of [[telephony]] (voice and data) services. Originally, JAIN stood for ''[[Java programming language|Java]] [[Application Programming Interface|API]]s for [[Intelligent network|Intelligent Network]]''. The name was later changed to ''[[Java programming language|Java]] [[Application Programming Interface|API]]s for Integrated Networks'' to reflect the widening scope of the project. The JAIN activity consists of a number of "Expert Groups", each developing a single API specification.

{{inline|date=March 2012}}

'''Java APIs for Integrated Networks''' ('''JAIN''') is an activity within the [[Java Community Process]], developing APIs for the creation of [[telephony]] (voice and data) services. Originally, JAIN stood for ''[[Java (programming language)|Java]] [[Application Programming Interface|API]]s for [[Intelligent network|Intelligent Network]]''. The name was later changed to ''[[Java programming language|Java]] [[Application Programming Interface|API]]sAPIs for Integrated Networks'' to reflect the widening scope of the project. The JAIN activity consists of a number of "Expert Groups", each developing a single API specification.

==Trend==

JAIN is part of a general trend to open up service creation in the telephony network so that, by analogy with the [[Internet]], openness should result in a growing number of participants creating services, in turn creating more demand and better, more targeted services.

==Goal==

A major goal of the JAIN APIs is to abstract the underlying network, so that services can be developed independent of [[computer network|network]] technology, be it traditional [[PSTN]] or [[Next Generation Network]].

==API==

The JAIN effort has produced around 20 APIs, in various stages of standardization, ranging from Java APIs for specific [[network protocolsprotocol]]s, such as [[Session Initiation Protocol|SIP]] and [[Transaction Capabilities Application Part|TCAP]], to more abstract APIs such as for [[call control]] and [[Charging Data Function|charging]], and even including a non-Java effort for describing telephony services in [[XML]].

==Parlay X==

There is overlap between JAIN and [[Parlay X|Parlay]]/[[Open Services Architecture|OSA]] because both address similar problem spaces. However, as originally conceived, JAIN focused on APIs that would make it easier for network operators to develop their own services within the framework of [[Intelligent network|Intelligent Network]] (IN)]] protocols. As a consequence, the first JAIN APIs focused on methods for building and interpreting [[Signaling System 7|SS7]] messages and it was only later that JAIN turned its attention to higher-level methods for call control. Meanwhile, at about the same time JAIN was getting off the ground, work on Parlay began with a focus on APIs to enable development of network services by non-operator third parties.

==Standardized APIs==

From around 2001 to 2003, there was an effort to harmonize the not yet standardized JAIN APIs for call control with the comparable and by then standardized Parlay APIs. A number of difficulties were encountered, but perhaps the most serious was not technical but procedural. The Java Community Process requires that a reference implementation be built for every standardized Java API. Parlay does not have this requirement. Not surprisingly, given the effort that would have been needed to build a reference implementation of JAIN call control, the standards community decided, implicitly if not explicitly, that the Parlay call control APIs were adequate and work on JAIN call control faded off. Nonetheless, the work on JAIN call control did have an important impact on Parlay since it helped to drive the definition of an agreed-upon mapping of Parlay to the Java language.

==See External link also==

* [[NGIN]]

*[http://java.sun.com/products/jain/ The JAIN APIs].

* [[Parlay Group]]

==BooksExternal links==

* [http://java.sun.com/products/jain/ The JAIN APIs].

* Jain, Ravi; Bakker, John-Luc; & Anjum, Farooq (2004). ''Programming Converged Networks: Call Control in Java, XML and Parlay/OSA,'' Wiley Interscience, 2004. ISBN 0471268011

* [http://jain-sip.dev.java.net/ JAIN-SIP].

* Jepsen, Thomas C.; Anjum, Farooq; Bhar, Ravi Raj; Tait, Douglas (2001). "Java in Telecommunications: Solutions for Next Generation Networks" John Wiley & Sons, 2001. ISBN 0471498262

* [http://jsip.java.net/ JAIN-SIP (new site)].

* Mueller, Steve. ''APIs And Protocols For Convergent Network Services''. McGraw-Hill, 2002. ISBN 007138880X

== Books ==

* {{cite book|last=Jain|first=Ravi|title=Programming converged networks : call control in Java, XML, and Parlay.|year=2005|publisher=Wiley-Interscience|___location=Hoboken, N.J.|isbn=0-471-26801-1|author2=Anjum, Farooq|author3=Bakker, John-Luc|url-access=registration|url=https://archive.org/details/programmingconve0000jain}}

* {{cite book|last=Jepsen|first=Thomas C.|title=Java in telecommunications : solutions for next generation networks|year=2001|publisher=Wiley|___location=Chichester [u.a.]|isbn=0-471-49826-2|editor=Anjum, Farooq}}

* {{cite book|last=Mueller|first=Stephen M.|title=APIs and protocols for convergent network services : [JTAPI, JAIN, and PARLAY; SIP and PINT, XML, LDAP, CORBA, and SOAP]|year=2002|publisher=McGraw-Hill|___location=New York [u.a.]|isbn=0-07-138880-X}}

[[Category:Java device platform|Integrated Networks]]

[[Category:Computer_and_telecommunication_standardsTelecommunications standards]]

[[Category:Computer standards]]