About JCP
Get Involved
Community Resources
Community News
FAQ
Contact Us

|
 |
Java EE (54 JSRs) | Java SE (79 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.
Description
JAINTM TCAP JSR is a proposed Java specification for the TCAP layer of the Signaling System 7 (SS7) stack.
Spec Lead
Phelim O'Doherty, Sun Microsystems, Inc.
Description
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.
Spec Lead
Christer Boberg, Ericsson AB
Description
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.
Spec Lead
David Ferry, Open Cloud Limited
Description
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.
Spec Lead
Christer Boberg, Ericsson AB
Description
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.
Spec Lead
Phelim O'Doherty, Oracle
Mudumbai Ranganathan, NIST
Description
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.
Spec Lead
Shankar Allimatti, Mahindra British Telecom Ltd.
Description
This work will specify the JAINTM API through which access to protocol stacks that support the MEGACO/H.248 protocol may be achieved.
Spec Lead
Vikas Bajaj, Hughes Software Systems
Description
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.
Reason
Withdrawn when the Spec Lead asked to withdraw and no one from the Expert Group was willing to become the new Spec Lead.
Spec Lead
John-Luc Bakker, Telcordia Technologies, Inc.
Description
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.
Spec Lead
Anders Kristensen, Dynamicsoft, Inc
Description
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.
Reason
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.
Spec Lead
Christer Boberg, Ericsson AB
Description
The JAINTM SIP Lite API defines a high level API to the SIP stack to allow for the rapid development of applications.
Reason
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.
Description
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.
Reason
The Executive Committee voted to list this JSR as dormant in May 2012.
Spec Lead
Kelvin R Porter, Cisco Systems
Description
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).
Reason
The Executive Committee voted to list this JSR as dormant in May 2012.
Spec Lead
Christopher John, NetNumber, Inc.
Description
SIMPLE Presence provides a standard portable and secure interface to manipulate presence information between a SIMPLE client (watcher) and a presence server (presence agent).
Spec Lead
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory
Description
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.
Spec Lead
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory
Description
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.
Spec Lead
Erkki Rysä, North Sixty-One Ltd
Cheng Wang, Nokia Corporation
Description
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.
Reason
The Executive Committee voted to list this JSR as dormant in May 2012.
Spec Lead
Marquart Franz, Siemens AG
Description
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.
Spec Lead
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory
Description
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.
Spec Lead
Tan Jek Thoon, Panasonic Information and Network Technologies Laboratory
Description
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).
Reason
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.
Spec Lead
Vishal Aggarwal, Hughes Software Systems
Description
This specification defines a protocol agnostic messaging API for composing, sending and receiving short messages and multimedia messages. The API shall work on the J2SE and J2EE.
Spec Lead
Hannu Mettala, Nokia Corporation
Description
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.
Spec Lead
David Ferry, Open Cloud Limited
|