Again, the bottom line is simple.
They should set up a pricing schedule based on the usage of the pipes, not on who or what is being transmitted.
You set caps or meters in both directions, make them applicable to ALL that subscribe to certain programs.
Now, the problem occurs when a company uses another carrier to get onto the net. If Level 3 gets onto the net with, say, FiOS and then a bunch of people start streaming their stuff across Comcats, it should not fall directly back on Level 3 to pay.
So how can you set up a payment schedule that works, is fair, and that you can understand w/o a degree in Nonlinear Algebra?
Indirectly, maybe. How? Simple. Comcast says "Hey, Veri$on! You are streaming XX googlie-bytes over our network! You owe us a bajillion dollars for last month according to our scheduled rates!"
Veri$on gets billed by Cablevi$ion, Veri$on then bills Level 3.
You only charge whoever is responsible for dumping that traffic on your system, not the end users. Let their providers handle that end.
Also, do not promise what you cannot deliver. Start capping your rates and BW (maybe after that magic 250GB your speed goes down to old DSL rates...), but tell people what you are doing, why and when it will be enforced.
The problem is, it is not as simple as a BW cap. Just like tolls, some bridges charge less when you come in "off peak". I believe NYC did that for a bit too, but they may have reversed that (I will have to check). Prime time BW is the key here, not the torrent you are serving at 3am.....