Promoting innovative mobile applications via a third party IMS-enabled ecosystem


and network heterogeneity (the movement of the terminal through different radio technologies) [3]. To prevent the future IMS client from becoming fatter and less maintainable, a modular solution and application programming interface (API) was introduced to permit a graceful evolution of the terminal software. In order to enable new, innovative features as well as to benefit from third party applications development, a usable, flexible, and open client architecture is required. The API for Mobile IMS Client Applications (AMICAL) architecture, shown in Figure 1, was developed for the IMS client to satisfy these needs. It includes two major components: Introduction Bell Labs’ Client/Service IP Multimedia Subsystem (IMS) Architecture group is responsible for the development of innovative, engaging applications and services in an IMS network. One of the team’s first product concepts, released in 2005, was a full-featured IMS communication client now known as the AlcatelLucent 5440 IMS Windows Mobile* client. It provides, among other features, Session Initiation Protocol (SIP)-based Voice over Internet Protocol (VoIP), pushto-talk, instant messaging, presence services, and a synchronized network address book with advanced contact management. This client serves as a basis for many other product concepts, including adding more communication ◆ Promoting Innovative Mobile Applications via a Third Party IMS-Enabled Ecosystem Ryan Skraba, Olivier Le Berre, Patrick Legrand, and Johann Daigremont

DOI: 10.1002/bltj.20303

Extracted Key Phrases

9 Figures and Tables

Cite this paper

@article{Skraba2008PromotingIM, title={Promoting innovative mobile applications via a third party IMS-enabled ecosystem}, author={Ryan Skraba and Olivier Le Berre and Patrick Legrand and Johann Daigremont}, journal={Bell Labs Technical Journal}, year={2008}, volume={13}, pages={57-73} }