Amazon Tech Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Wednesday, 4 August 2010

Device-specific data plans and policy management

Posted on 04:43 by Unknown
There is currently a clear shift among some operators towards device-specific data plans. In many ways, this is not new – 3G modem data for PCs has often had different price points to handset dataplans, for example. This has enabled operators to pitch 3G dongles against DSL competitors, reflecting typical higher monthly usage and so on. It has also reflected the lack of a voice plan sold concurrently, lack of (or lower) device subscriptions and so on. There have also been dedicated BlackBerry plans for many operators, incorporating BES / BIS email connectivity, or just reflecting the specific deals cut with RIM.

But increasingly, data plans are becoming more granular still – a trend likely to continue as we gain new device form factors. iPhone and iPad plans are specific to those products – and easily enforceable (for now) through the use of MicroSIMs which cannot be swapped around. MiFi products, which are inherently multi-device tethers, may also be subject to different plans.

As an example, take 3UK

- iPad MicroSIM only plans: 1GB @ £7.50 / month or 10GB @ £15 / month [1-month rolling]

- Laptop SIM-only plan : 5GB @ £15 / month

- Handset SIM-only Internet plan : 1GB @ £5 / month (which also includes circuit-based Skype calling)

With new devices using prepay and non-subscription models, we can expect to see even more granularity – a navigation device might come with a year’s free traffic reports including data, while a camera might be bundled with 1000 wireless photo uploads. Add in plans which include or exclude WiFi or femto data, and it gets murkier still.

The interesting thing here is that, in essence, we are getting a sort of blurry policy management and mobile traffic management by the back door. Although the correlations are not perfect, typical iPhone usage is different to typical BlackBerry usage, or assorted other products. Less / more video, less / more social networking , less / more web browsing, more / fewer notifications and so on. It’s quite easy to skew the prices and tiers to favour the less network-hungry products – or implicitly reward manufacturers for creating “non-aggressive” devices that don’t hammer the RNCs with signalling traffic so much.

What’s less clear is whether prioritising *device types* traffic is the same in terms of Net Neutrality as prioritising *application types*. Is it fair, reasonable or legal to distinguish between them? Even if they are not dynamically prioritised, it could be possible to rate-limit them - for example peak speeds of 1Mbit/s download vs. 3MBit/s. Under absolute purist views on Net Neutrality, it would probably also fall foul of the strict rule-making. But as we perhaps move towards some more negotiated, nuanced, intermediate arrangements, this is one particular Devil that should be included in the detail.

It's certainly much easier to distinguish between device types than application types in the network.

There are also some interesting wrinkles about what happens when users SIM-swap. I already do this, putting my dongle SIM into a vanilla phone when roaming as the prices are better, and I’m never going to run my laptop over 3G in a foreign country under any circumstances. There are also interesting issues about what happens when new apps are released that change consumption profile – or a major OS/firmware upgrade. In other words, there’s a policy management and enforcement angle as well.

Definitely an area to watch.
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Mobile social networking - how I'll know when it's going mainstream....
    This falls into the category of "amusing personal anecdotes" rather than "rigorous industry analysis". But it also refle...
  • Is it just me, or is 3G either really good or really bad, but rarely "OK"
    I've started noticing that my experience of mobile broadband (iPhone 3GS on Voda UK) is much more polarised than that of fixed broadband...
  • Multiple devices per account on WiMAX + also wholesale options
    I saw an interesting announcement this morning from Bridgewater Systems, about a solution to enable WiMAX operators to control the number ...
  • Telcos will find that API payments are a two-way street
    Various telecom operators are rolling out paid-for API programmes, typically for charging against a phone bill, sending an SMS and so forth....
  • 2011 events I'm attending or speaking at
    This is a quick post to list various conferences or other events I'm expecting to speak at or attend, primarily in H1 2011. Please let m...
  • Arbitrary "content control" from Vodafone
    I've just experienced an object lesson in why it's difficult to get any form of web/Internet application and content filtering ...
  • The Novatel MiFi - possibilities for new mobile broadband business models
    OK, I realise that I've been a bit grumpy and critical of some things recently. But before everyone assumes I'm getting more cantank...
  • Which operator app-level collaborations actually work?
    * Sign up for this blog's email list*     * Attend #TelcoOTT / Future of Voice workshops* I've just been having an email exchange w...
  • I'm picking a fight with a peer, about VoLTE and IMS
    It's quite rare for me to take direct pot-shots at other specific analysts. While I'm often confrontational, I try to avoid ad-homin...
  • The mobile industry buzzword of 2009 will be......
    OFFLOAD This year has been all about mobile broadband revenue and traffic growth. Dongles, iPhones, embedded PCs, Android, consumer BlackBer...

Blog Archive

  • ►  2013 (31)
    • ►  October (2)
    • ►  September (3)
    • ►  August (1)
    • ►  July (2)
    • ►  June (6)
    • ►  May (5)
    • ►  April (1)
    • ►  March (3)
    • ►  February (3)
    • ►  January (5)
  • ►  2012 (46)
    • ►  December (5)
    • ►  November (4)
    • ►  October (3)
    • ►  September (2)
    • ►  August (4)
    • ►  July (3)
    • ►  June (1)
    • ►  May (6)
    • ►  April (4)
    • ►  March (1)
    • ►  February (9)
    • ►  January (4)
  • ►  2011 (73)
    • ►  December (4)
    • ►  November (10)
    • ►  October (8)
    • ►  September (6)
    • ►  August (3)
    • ►  July (5)
    • ►  June (7)
    • ►  May (9)
    • ►  April (4)
    • ►  March (7)
    • ►  February (6)
    • ►  January (4)
  • ▼  2010 (130)
    • ►  December (4)
    • ►  November (10)
    • ►  October (10)
    • ►  September (6)
    • ▼  August (9)
      • Telcos: time to stop reporting "subscribers" and s...
      • Mobile traffic management - the Inter-technology w...
      • Is mobile voice being over-valued?
      • The Top 10 Unwarranted Assumptions in Telecoms
      • The hidden secret in the Google / Verizon statemen...
      • Work in Progress (comments welcome) - Code of Cond...
      • Device rental as a mechanism for mitigating roamin...
      • BlackBerry BBM intercept - workarounds probable?
      • Device-specific data plans and policy management
    • ►  July (7)
    • ►  June (19)
    • ►  May (19)
    • ►  April (11)
    • ►  March (18)
    • ►  February (7)
    • ►  January (10)
  • ►  2009 (126)
    • ►  December (4)
    • ►  November (14)
    • ►  October (9)
    • ►  September (8)
    • ►  August (9)
    • ►  July (10)
    • ►  June (21)
    • ►  May (14)
    • ►  April (2)
    • ►  March (11)
    • ►  February (15)
    • ►  January (9)
  • ►  2008 (94)
    • ►  December (24)
    • ►  November (26)
    • ►  October (25)
    • ►  September (19)
Powered by Blogger.

About Me

Unknown
View my complete profile