Gives you the tools to you need to integrate and charge for your applications via Ericsson Charging System using the Diameter Credit Control interface.
Ericsson Compression Tools
Helps you implement the OpenGL standard image compression for creation of 2D and 3D graphics.
Enables application programmers to easily develop applications that can integrate with the IP Multimedia Subsystem (IMS).
Provides Java ME based devices effertless access to a set of essential IMS Communication Enablers
IP Multimedia Subsystem (IMS) is defined by 3GPP/3GPP2 as an architectural framework that delivers data, speech and network technology over an IP-based infrastructure. For users, IMS-based services enable communications in a variety of modes including voice, text, pictures and video, or any combination of these in a highly personalized and secure way.
The IMS architecture consists of an IMS core that can be extended with a range of different communication services. The core takes care of the fundamental parts of the connectivity, such as authorization of users and message routing.
JSR281 defines a Java API for IMS core services and basically lets a user register itself on the IMS network and initiate and receive basic IMS calls. On top of the core functionality, a number of communication services are defined, for example multimedia telephony, Presence and Instant Messaging. The communication services are implemented by applications on both the network (application servers) and on the terminals (for example JSR325 MIDlets). Open Mobile Alliance (OMA) has specified a number of service enablers to permit the deployment of interoperable applications.
JSR325 defines a high abstraction level API to facilitate the implementation of some standardized communication services on the terminal side. JSR325 defines APIs for three different IMS Communication Enablers:
The Presence enabler provides the possibility to handle presence functionality according to the OMA Presence SIMPLE Specification v 1.1. One of the main use cases for the Presence enabler is to subscribe to other people's presence information, for example their availability, location, activity, and currently preferred means of communication. The Presence enabler can also be used to subscribe to other kind of services like sports results, stock rates, weather information and news flashes.
The Presence enabler also handles authentication of users towards the different servers in the network. Watcher authorization policy, presence information content handling, and presence list administration is handled by the XDM enabler, see the package description of the XDM enabler.
The Instant Messaging enabler provides IM functionality according to the OMA Instant Messaging Specification v1.0.
IM can be divided into two different modes of messaging, instant messaging and session based messaging.
The instant messaging mode is suitable for one-way messages where a response is not necessary or may arrive at a later time. The recipient may still respond using the same messaging mode but the messages are regarded as separate. This messaging mode can be used for both small instant messages and larger, multimedia enriched messages, that can include any combination of for example text, images, audio or video. The communication can either be one-to-one or one-to-many.
In session based messaging, the senders and recipients join together for a period of time, and the exchanged messages are associated together in the context of the session. To set up session based messaging, functionality in the ConferenceManager is used. There are three different types of session based messaging within the IM enabler: chat, ad hoc conference and predefined conference. The chat is a one-to-one messaging session while the ad hoc session is set up with a list of IM users. The predefined conference is set up with a predefined IM group.
The IM service makes use of group management (functionality in XDM) for addressing multiple users simultaneously.
The XML Document Management (XDM) enabler provides XDM functionality according to the OMA XML Document Management Specification v2.0.
The XDM enabler specifies XDM documents that can be shared by different enablers, for example Presence and Instant Messaging. The main use case for the XDM enabler is to manipulate XDM documents located in repositories in the network, called XDM Servers (XDMS). The XDM documents are manipulated by using the IETF XML Configuration Access Protocol (XCAP).
Each XML document stored in an XDMS can be characterized by an XCAP Application Usage. The application usage describes how applications and application servers can use the information. The XML document also has an Application Unique ID (AUID) that is used in this enabler to identify the Application Usage.
Common usages for XDM documents are: