http://www.lightreading.com/servsoftware/details.asp?sku_id=2162&skuitem_itemid=1082
Two strands for the telecom transformation – business transformation – identification of new business models and making money and other is the infrastructure transformation which involves making changes to the network and IT infrastructure so that it is ready to support new business models. I guess identification of such new business models and identifying changes in the infrastructure would both drive the existing operator for the transformation whereas for the greenfield operator it is the identification of business model that would drive the decision for the infrastructure selection.
However the whole transformation started with development of the all-IP networks that brought out new service providers who were part of the Internet. This forced the telecom operators to sit-up and take a look at emulating the Internet business model (i.e., a business model in which a network of different actors and their resources are linked together by the internet technology) to get share of revenue from IP services value chain. Now let me dissect the meaning of “Internet business model” for telecom service provider.
Business model is the product/services offered to creat revenue and hence value to the share holders. Now while doing so it should be cost effective and should provide differentiation with the competitors. Now for the telecom service providers, providing plain voice services is not the product/service. It should be providing always-on kind of link to connect with their work, friends & faimily, entertainment. Now how does this generate revenue; may be by becoming a trusted party who manages all the service providers providing different kind of service, providing a unified platform for storing their information, unified identity platform and offer flexibility for making payment. Since end user is getting the flexibility of anytime, anywhere access of these services, and is independent of devices, operator would have to collect for this service from the end user. To become cost effective, the service creation has to be flexible, get developed from internal/external developers to reduce cost of creation of service. To create competitive advantage, the service assurance and making the service available on any device from anywhere could be critical. Also close tracking of the consumer behavior and doing a targetted advertisement and upsaling of the other services could bring additional revenue. To handle the multiple service providers, have the business platform to support the required workflow and the charging – modification in the eTOM framework adopted?
For the service creation unified subscriber data view and service data view is essential where different services will have to be orchestrated to provide service to the end user. Since operator own the subscriber, orchestrating the service will become a critical service in their offering. In terms of services it should be able to offer independent of the access and things like voice call continuity and data call continuity between the access should become a reality. For voice operator can themselves offer the voice (with committed QoS) but also should allow other providers like Skype to offer the service.
Revenue model in this new world will have to be built around the affliate marketing model. In this model, a business rewards one or more affiliates for each customer brought about the affiliate’s marketing effort. But in the case of operator, this can be because customer using the service say from Google when compared to Microsoft. This model could also include the advertising to bring business for the other service providers operating using Internet. In this model operator can have a single web page which aggregates all other service provider. Then may be based on the content accessed (including Voice), it can be charged or a flat fee.
On the infrastructure side, since for each of the service providers the quality of service is delivered, the network infrastructure should be aware of the services (e.g., it should be able to give differential treatment based on the port, service type, URL etc).




