Ericsson is engaged in all aspects of Java standardization and especially in defining the next version of the Java Enterprise Edition (EE) platform. Ericsson has participated in 25 completed Java Specification Requests (JSRs) and is participating in 22 active JSRs. We are leading the specification of JSR-281 (IMS Services API) and JSR-319 (Availability Management for Java).

In addition, Ericsson is a member of the Java Community Process Executive Committee for Java Micro Edition (ME) since 2002.

Ericsson is also contributing to the Java community in other ways. For example, Ericsson released its SIP-servlet container to the open-source community project GlassFish/SailFin in May 2007. With the SIP-servlet container, as a developer you can enhance your applications with telecom network capabilities. Java EE servers with SIP servlets enable quick development of new telecommunication services.

Ericsson is specification lead for Java Specification Request JSR-281, IMS Services API. The JSR enables application programmers to easily develop applications that can integrate with the IP Multimedia Subsystem (IMS).

JSR 281 is now in its final ballot, which expects to close in the end of May. Licensing will start immediately after the ballot has closed.

IMS is defines a generic architecture for offering Voice over IP and multimedia services. Services based on IMS will enable all-IP person-to-person and person-to-content communications in a variety of modes − including voice, text, pictures and video, or any combination of these − in a highly personalized way.

JSR-281 standardizes an API that allows you to develop advanced convergent multimedia services with your Java skills. In-depth knowledge about IMS technology or its underlying protocols is not required.

The API abstracts the underlying technology and at the same time provides you with maximum flexibility. It defines a set of high-level functions enabling Java ME applications to access IMS functionality, including:

• High-level support for the IMS registration mechanism                 
• Support for co-location of multiple IMS Services                  
• Use of IMS service sessions (based on SIP sessions)                  
• Use of media connections                  
• Addressing Quality of Service                  
• Hiding and encapsulating internal protocols managed and used by the IMS protocol stack.

The API ensures that your applications will avoid violations of SIP and IMS conventions. In particular, the authentication mechanism used by IMS is completely hidden from your application. This minimizes the security risks associated with application level handling of authentication.

While simplifying your IMS application development, the API allows low-level access to IMS functionality for more advanced development projects. The API can be extended as future IMS functionality becomes available.

The API has two parts, the Core API and the Service API.

The Core API
The Core API gives you access to service independent IMS primitives. The API includes the following highlights:

• Javax.microedition.ims
  • Entry point to IMS functionality
  • Select type of services
• Javax.microedition.ims.core
  • Create IMS calls (“sessions”) to a remote peer
  • Communicate with IMS application servers
  • Query capabilities of a remote peer
  • Send references
• Javax.microedition.ims.core.media
  • Define the media objects that carry content flows                 
  • Set up media players for streaming media                 
  • Quality of service

The Service API
The Service API gives you with access to service enablers, standardized by the Open Mobile Alliance (OMA). The service enablers are all optional. The API includes the following highlights:

• Javax.microedition.ims.poc
  • Push-to-talk over cellular (PoC) service enabler
• Javax.microedition.ims.presence
  • Presence service enabler
• Javax.microedition.ims.xdm
  • XML document manager service enabler

Read more about the IMS Services API at the Java Community Process page for JSR 281

Java SE/EE

JSR-8 Open Services Gateway Specification
JSR-12 Java Data Objects (JDO) Specification
JSR-17 JAIN ISUP Specification
JSR-18 JAIN OAM API Specification
JSR-29 JAIN MAP Specification
JSR-32 JAIN SIP API Specification
JSR-35 JAIN INAP API Specification
JSR-47 Logging API Specification
JSR-89 OSS Service Activation API
JSR-90 OSS Quality of Service API*
JSR-91 OSS Trouble Ticket API
JSR-103 JAIN User Interaction API
JSR-112 J2EE Connector Architecture 1.5
JSR-116 SIP Servlet API
JSR-117 J2EE APIs for Continuous Availability
JSR-121 Application Isolation API Specification
JSR-144 OSS Common API
JSR-192 JAIN Service Creation Environment - Java PART
JSR-289 SIP Servlet v1.1
JSR-303 Bean Validation
JSR-309 Media Server Control API
JSR-314 Java Server Faces 2.0
JSR-315 Java Servlet 3.0 Specification
JSR-316 Java Platform, Enterprise Edition 6 (Java EE 6) Specification
JSR-317 Java Persistence 2.0
JSR-318 Enterprise JavaBeans 3.1
JSR-319 Availability Management for Java*
JSR-322 Java EE Connector Architecture 1.6 

Java ME

JSR-82 Java APIs for Bluetooth
JSR-118 Mobile Information Device Profile 2.0
JSR-184 Mobile 3D Graphics API for J2ME
JSR-211 Content Handler API
JSR-238 Mobile Internationalization API
JSR-239 Java Binding for the OpenGL ES API
JSR 249 Mobile Service Architecture 2.0
JSR-253 Mobile Telephony API (MTA)
JSR-271 Mobile Information Device Profile 3
JSR-281 IMS Services API*
JSR-287 Scalable 2D Vector Graphics API 2.0 for Java ME
JSR-290 Java Language & XML User Interface Markup Integration
JSR-293 Location API 2.0
JSR-297 Mobile 3D Graphics API 2.0
JSR-300 DRM API for Java ME
JSR-304 Mobile Telephony API version 2
JSR-306 Towards a new version of the JCP
JSR-307 Network Mobility and Mobile Data API
JSR-320 Service Framework

* Ericsson as specification lead