according to the application/services network usage profiles. An example service package can be an email and basic web browsing package or access to social tools, for example, unlimited use of Facebook or alike. An example from the opposite end of the spectrum could be a peer-to-peer applications package. The idea is designed to enable end-users to decide for themselves what it is they want to use, as we all have different needs and thus a different perception of what the Web is.

Fig. 1 Web Enablement platform

CSP as a Web Enabler

The question, which may arise, is how to implement the idea without granting telecommunication operators too much power. If the only way to use applications and services was via an operator’s application store, it would probably mean that operators would have a monopoly -acting out the role of gate keepers. Being a true enabler must mean that third parties have a choice as to whether they want to leverage an operator’s application store or whether they prefer to use alternatives. In the case of the latter, the operators should only provide a network enablement, or more precisely, the discussed network QoS required by a third party service or application. This is expected to enable different business models as some developers

Selling User Experience– business models

Retailing QoS by operators will require the technical capabilities of traffic shaping and policy enforcement, which may be challenging. The envisioned practical approach is that when an end-user acquires a ‘basic browsing’ package and all online applications, which confine to the assumed ‘basic’ QoS, the providers of these applications will not require additional enablement. However, if the application is data intensive, for example video streaming, in order to guarantee appropriate user experience, the third party application will need the appropriate network QoS enablement. This, in fact, means that CSPs provide something more than a technical oriented network QoS, instead enabling good user experience.