As a potential future BitCo customer - new high site and LOS permitting - I’ve been following the spirited FUP debate with interest.
With an uncapped product, I think most of us appreciate the need for a Fair Usage Policy, particularly on a wireless system. Unlike most other uncapped products, BitCo has done something unusual and decided to base the FUP on line utilisation over time (eg 100% utilisation for 1 hour), rather than an absolute quantity of data (eg 100GB per month). On that basis, you can ask yourself :
- Should 100% utilisation of peak speed for 24 hours constitute “unfair usage” ? Almost certainly.
- How about 100% utilisation for 1 hour ? I would think it should not.
- How about 100% utilisation for 4 hours ? Perhaps.
There are two points I’d like to make by way of my 2c worth :
Firstly, I think what is missing from BitCo is a clear, unambiguous statement of what the current FUP actually is. We all get the general idea about the “leaky bucket principle” and we know that 100% utilisation for one hour will trigger throttling under the current FUP. But what is needed is a clear description of how the FUP works, with proper, quantitative limits stated.
Personally I would think that a “moving average” or “moving window” type measurement is most suitable, and I would guess that an averaging period of something like 4 hours would be reasonable.
I don’t know whether BitCo counts both upstream and downstream traffic as contributing to the total line utilisation. I would think that they do, but in order to make the following example simpler, I’ll assume that only downlink traffic is counted.
So for example, a “proper” FUP statement might read something like this :
“
Throttling will be applied when the subscriber’s average downlink data rate, as measured over the preceding 4-hour period, exceeds 80% of the maximum line speed. The subscriber will then be throttled to half the maximum line speed until such time as the 4-hour moving average drops below 80% of the maximum line speed again.”
Then there is the question of the actual throttling threshold, given as 80% in the example above. Well that’s BitCo’s call, but we should all realise that whatever number is chosen, determines what the service actually is. If the threshold is (say) 80% average utilisation of a 5Mbps downlink, then the line would be able to sustain 4Mbps indefinitely without triggering the FUP. That is then NOT a “5Mbps service”, but rather a 4Mbps service with the ability to peak at 5Mbps.
With a FUP like the above, a subscriber would (for instance) be able to use the "5Mbps" line at 4Mbps for 1 hour, then 2 Mbps for 1h, then stream a movie at 5Mbps for 2 hours, and still be just under the 80% throttling limit : the “moving average” utilisation over that 4-hour period is exactly 4Mbps.
All of this is given from a customer perspective, and just one (potential) customer at that. The actual averaging period and utilisation threshold is for BitCo to make a call on, based on technical considerations.
Secondly, I think that trying to guarantee (or even quantify) a connection’s performance in terms of whether or not it can “stream” is asking for trouble - the data rates required for video streaming are simply too variable to serve as an absolute measure.
Consider that the data rate required for streaming video depends on a number of factors, namely : resolution, colour depth, frame rate, encoding algorithm, quality setting, fixed or adaptive encoding, type of video container, etc. There is also the question of whether the quoted bit rate is video only, or whether it includes audio, and if it does include audio, is it low quality monaural audio, high quality stereo, full 5.1 surround, etc ?
To illustrate the variability, consider that streaming "typical" HD AV (1920x1080) content could demand anything from 6Mbps (YouTube HD clip) to 15Mbps (Sky Sports HD), as discussed in
this article.
So, whether or not a customer is "able to stream” over a BitCo connection at any given time, is not an absolute Yes/No, but rather is determined by :
- The actual bitrate of the media stream
- The type of BitCo connection in use (2down/1up, 5down/1up, or 10down/2up on the "Home" packages)
- The guaranteed performance of that line, as per a stated FUP like the above
- The total traffic (all users and all sessions) being carried by the connection
- The current throttling status