Please, can you elaborate if you would see presence information as part of the Network API. If so, please provide some examples for presence information
I’m not sure I fully understand your question, so feel free to correct me if you would like me to elaborate more; however, I think that application interactions with the PCC will be enabled through APIs. The specific functionality of the API set would be operator specific — enable service access, for example, or updating QoS parameters, etc.
For operators who are still offering volume based plans, the proposed tier structure, be it dynamic or static tier, usage or service bundle plans may work. For operators who are already offering all-you-can-eat type of plan, what is the best way to allocate resources efficiently while maintaining an acceptable level of experience?
Is there any operator deploying the policy control model advocated by 3GPP? Any experience to share by these operators?
I’m not sure that there is an easy way to accommodate all-you-can-eat plans and maintain an acceptable level of service. Certainly the most obvious strategy is to invest in infrastructure (and, for wireless operators, LTE and the like). And I think that many people assume that this strategy, especially LTE, will be a panacea that will solve these problems nicely without the need to change packaging and pricing. But I believe this is wrong. Technologies such as LTE will be a slow roll out, with legacy infrastructure in place for many years. Too, despite the added bandwidth LTE provides, I think that the increased demand will cause congestion issues anyway.
Even if infrastructure expansion and LTE deployment do somehow solve the congestion issues, they don’t solve the revenue issues caused by all-you-can-eat plans. Operators will need an improved ROI on infrastructure (and, more fundamentally, need to ensure the long term viability for their business).
So, net-net, I don’t think operators will ultimately have a choice but to innovate their pricing models. The all-you-can-eat plan will remain an option, but only one of many (and an expensive one at that, I suspect).
If mobile broadband is to substitute or to inroad into the fixed broadband market, flat rate plan is inevitable. Changing to flat, all-you-can-eat plan is a direction of no return, unless one can really find something meaningful to those who are willing to pay more. In the internet world, it seems to be very difficult to find. Radio resource is finite and an efficient/fair allocation is required, but how fair is fair? Bit tolerant type of applications are common and they may contribute around 50% of total traffic, should they be given lower priority in terms of resource allocation? These users are however paying the same charges as those using email/FTP or other browsing/streaming types of applications. Any idea on how to allocate the resource?
If all other variables were to remain the same, I’d agree that new pricing models would be a difficult sell. But things aren’t the same. No longer is this a world of WAP phones, with subscribers occasionally using data connectivity to check a stock price. Smartphones have introduced completely new wireless data behavior, congestion related to that is new, and services available wirelessly (such as video) are new. Usable location based functionality — anticipated for a decade — is new. Mobile VOIP applications are new. And so on.
So my feeling that innovations in the way that service access and bandwidth is packaged and sold is unlikely to be jarring or difficult to swallow — it’s part of a much broader evolution within the industry.
the presentation was hard to read as it was toooooo small. Can you please send me a copy of the presentation?
Sure, we can send along a copy.
Please send me a copy of the slides, it is very hard to follow the presentation due to the small text.
BR Monica
Please, can you elaborate if you would see presence information as part of the Network API. If so, please provide some examples for presence information
Hi Chris,
How do you see the user interface being enabled between the terminal and the PCC manager for real-time feature change?
e.g. Java-based app; “PCC widgets”; native client; other?
BR
Moray Barclay
Hi Moray,
I’m not sure I fully understand your question, so feel free to correct me if you would like me to elaborate more; however, I think that application interactions with the PCC will be enabled through APIs. The specific functionality of the API set would be operator specific — enable service access, for example, or updating QoS parameters, etc.
Chris Hoover
For operators who are still offering volume based plans, the proposed tier structure, be it dynamic or static tier, usage or service bundle plans may work. For operators who are already offering all-you-can-eat type of plan, what is the best way to allocate resources efficiently while maintaining an acceptable level of experience?
Is there any operator deploying the policy control model advocated by 3GPP? Any experience to share by these operators?
Hi CH ([email protected]),
I’m not sure that there is an easy way to accommodate all-you-can-eat plans and maintain an acceptable level of service. Certainly the most obvious strategy is to invest in infrastructure (and, for wireless operators, LTE and the like). And I think that many people assume that this strategy, especially LTE, will be a panacea that will solve these problems nicely without the need to change packaging and pricing. But I believe this is wrong. Technologies such as LTE will be a slow roll out, with legacy infrastructure in place for many years. Too, despite the added bandwidth LTE provides, I think that the increased demand will cause congestion issues anyway.
Even if infrastructure expansion and LTE deployment do somehow solve the congestion issues, they don’t solve the revenue issues caused by all-you-can-eat plans. Operators will need an improved ROI on infrastructure (and, more fundamentally, need to ensure the long term viability for their business).
So, net-net, I don’t think operators will ultimately have a choice but to innovate their pricing models. The all-you-can-eat plan will remain an option, but only one of many (and an expensive one at that, I suspect).
Chris Hoover
If mobile broadband is to substitute or to inroad into the fixed broadband market, flat rate plan is inevitable. Changing to flat, all-you-can-eat plan is a direction of no return, unless one can really find something meaningful to those who are willing to pay more. In the internet world, it seems to be very difficult to find. Radio resource is finite and an efficient/fair allocation is required, but how fair is fair? Bit tolerant type of applications are common and they may contribute around 50% of total traffic, should they be given lower priority in terms of resource allocation? These users are however paying the same charges as those using email/FTP or other browsing/streaming types of applications. Any idea on how to allocate the resource?
Users are quite accostumed to pay flat rates for internet access, do you believe that is possible now trying to push for other pricing models?
Hi Ari,
If all other variables were to remain the same, I’d agree that new pricing models would be a difficult sell. But things aren’t the same. No longer is this a world of WAP phones, with subscribers occasionally using data connectivity to check a stock price. Smartphones have introduced completely new wireless data behavior, congestion related to that is new, and services available wirelessly (such as video) are new. Usable location based functionality — anticipated for a decade — is new. Mobile VOIP applications are new. And so on.
So my feeling that innovations in the way that service access and bandwidth is packaged and sold is unlikely to be jarring or difficult to swallow — it’s part of a much broader evolution within the industry.
Chris Hoover