Difference between revisions of "Private:tethering-ideas"

From NMSL
(New page: Details go here == Links and References ==)
 
Line 1: Line 1:
Details go here
+
Until recently, the cellular dataplans in the North America were mostly unlimited. However, since late 2010, AT&T started implementing tiered dataplans: a subscriber gets 200 MB for $15/month, 2 GB for @25/month, and so on. With the increasingly popularity of smartphones (and thus the tremendous amount of data traffic),  we expect to see other cellular service providers moving away from unlimited dataplans. Under the new contracts, many subscribers can easily be charged an arm and a leg if they go above the limits. Meanwhile, some other subscribers may underutilize their quotas, which is another format of overpaying the cellular service providers.
 +
 
 +
To address this issue, we propose to capitalize the WiFI interfaces found on most modern smartphones to allow cellular subscribers reselling their un-used dataplan quotas. That is, the smartphones in proximity form an WiFi ad hoc network, which allow them to carry Internet traffic for each other. A micro billing platform is implemented to facilitate reselling un-used dataplan quotas among subscribers. The proposed platform covers several business use cases. First, subscribers who do not have enough dataplan quotas can purchase them from other subscribers at lower rate. Second, subscribers who have un-used quotas can sell them. Third, subscribers who need higher cellular bandwidth, e.g., for downloading a large file, can purchase the additional bandwidth on-demand from neighboring subscribers.
 +
 
 +
As a starting point, we are implementing an Android app to facility such collaboration using WiFi ad hoc mode. Later, we will implement servers on Linux to realize the micro-billing mechanisms.
 +
 
 +
An early todo list has been identified.
 +
Todo (updates are welcome):
 +
# Survey on multi-hop tethering on smartphones
 +
# Survey on micro-billing mechanisms
 +
# System architecture (without considering security issues)
 +
# Initial analysis on security concerns
 +
 
 +
A list of done tasks are given below.
 +
Done (updates are welcome):
 +
# None for now.
 +
 
 +
 
  
  
 
== Links and References ==
 
== Links and References ==

Revision as of 12:31, 21 January 2011

Until recently, the cellular dataplans in the North America were mostly unlimited. However, since late 2010, AT&T started implementing tiered dataplans: a subscriber gets 200 MB for $15/month, 2 GB for @25/month, and so on. With the increasingly popularity of smartphones (and thus the tremendous amount of data traffic), we expect to see other cellular service providers moving away from unlimited dataplans. Under the new contracts, many subscribers can easily be charged an arm and a leg if they go above the limits. Meanwhile, some other subscribers may underutilize their quotas, which is another format of overpaying the cellular service providers.

To address this issue, we propose to capitalize the WiFI interfaces found on most modern smartphones to allow cellular subscribers reselling their un-used dataplan quotas. That is, the smartphones in proximity form an WiFi ad hoc network, which allow them to carry Internet traffic for each other. A micro billing platform is implemented to facilitate reselling un-used dataplan quotas among subscribers. The proposed platform covers several business use cases. First, subscribers who do not have enough dataplan quotas can purchase them from other subscribers at lower rate. Second, subscribers who have un-used quotas can sell them. Third, subscribers who need higher cellular bandwidth, e.g., for downloading a large file, can purchase the additional bandwidth on-demand from neighboring subscribers.

As a starting point, we are implementing an Android app to facility such collaboration using WiFi ad hoc mode. Later, we will implement servers on Linux to realize the micro-billing mechanisms.

An early todo list has been identified. Todo (updates are welcome):

  1. Survey on multi-hop tethering on smartphones
  2. Survey on micro-billing mechanisms
  3. System architecture (without considering security issues)
  4. Initial analysis on security concerns

A list of done tasks are given below. Done (updates are welcome):

  1. None for now.



Links and References