Avoid the Mashup Dead Zone with Integrated B/OSS

The most important competitive barrier for this version of multiservice is closed, or monopolistic, network access. The rules regarding network ownership have changed as a result of new federal regulations — the Telecom Act of 1996 was a dramatic example of this change writ large — and similar trends to open networks and create competition have played out in many large telecom markets around the world. In addition, without common standards and a common OSS, these bundles are more of a patchwork rather than services that easily can be made extensible to mobile devices and other means of access. Third, broadband mobile and other improvements in network technology, such as femtocell technology, are a constant threat. Finally, and very important, is that business support systems underlying the triple play are often a hodge-podge of legacy software and/or oversimplified tools that require significant investment to upgrade or specialize.

The Technology

There are four main components that will allow multiservices to extend beyond the triple play: (1) open access to best-of-breed systems through web services APIs; (2) intelligence and scalable middleware that provides pre-integrated subsystems; (3) ease of service creation across the properties of multiple vendors with a clear and equitable settlement system and; (4) the combination of all types of media into one packet-based infrastructure.

Here they are in more detail:

1. Web services programming interfaces — XML-based APIs calls over a common http infrastructure — have created an environment that facilitates the presentation of data and services wherever the Internet reaches. Mash-ups in every sector of software technology development have been the result. The possibilities grow each month as system manufacturers build better APIs with more access. Multiservice communications offerings can be deployed faster and with a degree of creativity that previously was not possible. Iperia, a provider of unified messaging software, is a prime example of a communications infrastructure provider that made the choice to switch platform architecture to allow for easier integration into multiservice bundles and vertically integrated software.

2. Middleware. Oracle Corp., with the former portfolio of BEA Systems Inc., is a leading example of middleware that can be used generically across many industry types and deployment scenarios. Its Oracle Fusion Middleware product provides out-of-the-box clustering, high availability architecture and a generic messaging bus for external integration. For systems that are more specific to VoIP and related subsystems — a fundamental building block of multiservice offerings — middleware such as VoIP Logic’s Cortex system that pre-integrates a range of leading platforms allows for a dramatically reduced time interval and cost to deploy a multiservice bundle. Currently, service providers offering advanced software-based services tend to spend a lot of their resources developing and maintaining cutting-edge service platforms. Ultimately, as the tool kit of software options becomes more robust, smart middleware should allow for the creation and sustainability of services and the underlying OSS/BSS without having to re-invent common processes and software integration.