Miljenko Opsenica

Service broker architecture: Location business case and mashups

In recent years, costly and slow integration has created an unnecessary gap between the telephone companies (or telco) and IT worlds. However, collaboration between Internet and telecom standards is essential for future development. The service broker concept has been developed to fill this gap. Indeed, the service broker provides a flexible layer in the telecom architecture to bridge these two worlds. Such a concept is essential to coordinate the diverse future services and provide mashup opportunities through a single point of entry. In this article we present the concept and an actual implementation of a specific service broker: a location service broker. Moreover, we also present a sample mashup called MoPoint that we implemented to better demonstrate the functionality of the location service broker. MoPoint is a Web site where the user can see the current location of his or her mobile displayed on a map along with local weather and advertisements.

IMS service development API and testbed

The IP multimedia subsystem defined by the Third Generation Partnership Project is the architecture merging the Internet and telecom worlds. The IMS was designed to make it easy for third-party developers to make their applications available to all IMS users, and by doing so provide more than only the basic telecom services like voice, messaging, presence and contact management. However, good knowledge of the IMS network architecture and the underlying Internet protocols is still needed to develop IMS applications. In addition, telecom expertise is needed to deploy the application and provision users. To ease the development and deployment process, it is essential to provide application developers with APIs and similar tools available for Web 2.0 application development today. In this article we explore the architectural and protocol aspects that enable third-party IMS application development and deployment. We also study how the applications will coexist with other applications already deployed in the IMS. Moreover, we describe Java libraries exploiting the functionality of the IMS both in the terminal client and within the core network. We also show how these Java libraries can be used for developing and deploying new applications in an IMS testbed, which provides IMS functionality over commercial 3G networks.

Design and Implementation of a RESTful IMS API

Web 2.0 has been happening on the fixed Internet side for several years already. This phenomenon has forced traditional Telco operators to consider new business models. One of the possible models is to utilize the IP Multimedia Subsystem (IMS) network architecture. Using the IMS, Telco operators have more control over the data instead of becoming just bit pipes. In addition, operators interest in providing open Application Programming Interfaces (APIs) exposing IMS and network assets has grown. In this paper, a RESTful IMS API implementation, is represented. The design and implementation of the API exposing IMS functionality is shown. In addition, the implementation of a REST application using the API is described.

ImsInnovation - experiences of an IMS testbed

The IP Multimedia Subsystem (IMS) defined by the 3rd Generation Partnership Project (3GPP) is the architecture merging the Internet and mobile worlds. The IMS enables new business models and allows third-party developers to make their applications available to all IMS users. This paper introduces an IMS testbed called ImsInnovation, which was launched in Summer 2008. The objective of the testbed project is to ease the development of new third-party applications for the IMS. As part of this project we provide web developers with Java APIs (Application Programming Interfaces) that exploit the functionality of the IMS both for the Java Mobile Edition (ME) and the Java Enterprise Edition (EE). The provided APIs are based on existing SIP and IMS Java Specification Requests defined by the Java Community Process (JCP). In this paper we also discuss our experiences from the testbed project and describe a couple of applications deployed in the testbed.