About JCP
Get Involved
Community Resources
Community News
FAQ
Contact Us
|
|
Java EE (54 JSRs) | Java SE (76 JSRs) | Java ME (85 JSRs)
| OSS (13 JSRs) | JAIN (22 JSRs) | XML (18 JSRs)
JAIN
JAIN, Java APIs for Integrated Networks, is providing a set of APIs focused on emerging network protocols and architectures driven by convergence of traditional telecommunication and IP networks.
11 |
|
JAINTM TCAP Specification |
|
JAINTM TCAP JSR is a proposed Java specification for the TCAP layer of the Signaling System 7 (SS7) stack. |
|
Final
|
|
|
|
Phelim O'Doherty, Sun Microsystems, Inc. |
|
21 |
|
JAINTM JCC Specification |
|
JSR 21 focuses on the JAINTM Java Call Control (JCC) Specification. Any references seen below that refer to the JAIN Coordination and Transactions (JCAT) are addressed in JSR 122. |
|
Final
|
|
|
|
Christer Boberg, Ericsson AB |
|
22 |
|
JAINTM SLEE API Specification |
|
Descriptions of all interfaces, classes, exceptions and requirements to develop portable telecommunication services and application frameworks so that services once developed will run on any JAINTM SLEE-compliant execution environment. |
|
Final
|
|
|
|
David Ferry, Open Cloud Limited |
|
23 |
|
JAINTM MGCP API Specification |
|
This work will specify the JAINTM API through which access to protocol stacks that support the Media Gateway Control Protocol (RFC 2705) may be achieved. |
|
Final
|
|
|
|
Christer Boberg, Ericsson AB |
|
32 |
|
JAINTM SIP API Specification |
|
The JAINTM SIP API specification provides a standard portable interface to share information between SIP Clients and SIP Servers, providing call control elements enabling converged-network applications. |
|
Maintenance
|
|
|
|
Phelim O'Doherty, Oracle |
|
Mudumbai Ranganathan, NIST |
|
35 |
|
JAINTM INAP API Specification |
|
This JSR is to develop the JAINTM (Java APIs for Integrated Networks) INAP (Intelligent Network Application Protocol) specification for Intelligent Network Applications in the Telecommunications Industry. |
|
Final
|
|
|
|
Shankar Allimatti, Mahindra British Telecom Ltd. |
|
79 |
|
JAINTM MEGACO API Specification |
|
This work will specify the JAINTM API through which access to protocol stacks that support the MEGACO/H.248 protocol may be achieved. |
|
Final
|
|
|
|
Vikas Bajaj, Hughes Software Systems |
|
100 |
|
JAINTM Service Creation Environment |
|
JAINTM SCE will support and simplify the creation of portable telecommunication
services delivered primarily to the JAINTM Service Logic Execution Environment, while not restricted to this class of Execution Environments. |
|
Withdrawn
|
|
Withdrawn when the Spec Lead asked to withdraw and no one from the Expert Group was willing to become the new Spec Lead. |
|
Withdrawn |
|
Effective: 2006-12-04 |
|
|
|
John-Luc Bakker, Telcordia Technologies, Inc. |
|
116 |
|
SIP Servlet API |
|
The SIP Servlet API defines a high-level extension API for SIP servers. It enables SIP applications to be deployed and managed based on the
servlet model. |
|
Final
|
|
|
|
Anders Kristensen, Dynamicsoft, Inc |
|
122 |
|
JAINTM JCAT |
|
This develops the JavaTM Coordination and Transaction (JCAT) specification, which perceives Java Call Control (JCC) as its core package and extends it with concepts to model and control terminal capabilities. |
|
Withdrawn
|
|
We see no reason to keep it as there has be no development or interest for a long time and we do not intend to further evolve the standard. |
|
Withdrawn |
|
Effective: 2016-04-05 |
|
|
|
Christer Boberg, Ericsson AB |
|
125 |
|
JAINTM SIP Lite |
|
The JAINTM SIP Lite API defines a high level API to the SIP stack to allow for the rapid development of applications. |
|
Withdrawn
|
|
Withdrawn after no one on the Expert Group offered to take over the Spec Lead role. Because of the resourcing issues, Nortel had to withdraw from JSR125. Nortel was unable to provide the RI and the TCK, but believed that this is the right approach for a Proxy and small footprint SIP servers/Clients. |
|
Withdrawn |
|
Effective: 2006-03-14 |
|
|
|
David Tweedie, Nortel |
|
141 |
|
SDP API |
|
The IETF protocol SDP specifies messages that describe multi-media sessions and are included within other protocol messages as payload. The API will enable users to manipulate SDP messages. |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in May 2012. |
|
|
|
Kelvin R Porter, Cisco Systems |
|
161 |
|
JAINTM ENUM API Specification |
|
The JAINTM ENUM API Specification defines a standard, portable application programming interface to query and provision E.164 telephone numbers and
their service-specific Uniform Resource Identifiers (URI). |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in May 2012. |
|
|
|
Christopher John, NetNumber, Inc. |
|
164 |
|
SIMPLE Presence |
|
SIMPLE Presence provides a standard portable and secure interface to manipulate presence information between a SIMPLE client (watcher) and a presence server (presence agent). |
|
Final
|
|
|
|
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory |
|
165 |
|
SIMPLE Instant Messaging |
|
SIMPLE Instant Messaging provides a standard portable and secure interface to exchange messages between SIMPLE clients. SIMPLE is an extension of SIP to support presence and instant messaging. |
|
Final
|
|
|
|
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory |
|
180 |
|
SIP API for J2METM |
|
SIP API for J2ME defines a multipurpose SIP API for J2ME clients. It enables SIP applications to be executed in memory limited terminals, especially targeting to mobile phones. |
|
Final
|
|
|
|
Erkki Rysä, North Sixty-One Ltd |
|
Cheng Wang, Nokia Corporation |
|
182 |
|
JPay - Payment API for the JavaTM Platform |
|
This JSR requests the creation of the Payment API for the Java Platform (JPay) specification. The JPay API will support payments in an open, Web-like environment. |
|
Dormant
|
|
The Executive Committee voted to list this JSR as dormant in May 2012. |
|
Early Draft Review |
Download page |
Start: 2004-10-27 |
End: 2004-12-25 |
|
|
Marquart Franz, Siemens AG |
|
186 |
|
Presence |
|
Presence is a generic and protocol-agnostic API for Presence, providing a standard portable and secure interface to control, manage and manipulate Presence information between Presence clients and servers. |
|
Final
|
|
|
|
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory |
|
187 |
|
Instant Messaging |
|
A protocol-agnostic API for Instant Messaging, this provides a standard portable and secure interface to control, manage and manipulate instant messages between clients through the use of presence servers. |
|
Final
|
|
|
|
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory |
|
192 |
|
JAINTM Service Creation Environment - JavaTM PART |
|
This is the specification for the JavaTM API to support and simplify the creation of portable telecommunication services delivered primarily to the JAINTM
Service Logic Execution Environment (JAINTM SLEE). |
|
Withdrawn
|
|
There had not been much progress on this JSR since quite some time. The draft was floated for Expert Group review but there was no response even after several reminders. They then decided not to go ahead with this activity and hence requested the PMO to mark this JSR 192 as WITHDRAWN. |
|
Withdrawn |
|
Effective: 2004-09-22 |
|
|
|
Vishal Aggarwal, Hughes Software Systems |
|
240 |
|
JAINTM SLEE (JSLEE) v1.1 |
|
This JSR is a logical extension to address gaps in JSLEE v1.0 specification. The central area of focus is to specify the Resource Adaptor Architecture API and semantics. |
|
Final
|
|
|
|
David Ferry, Open Cloud Limited |
|
|