Adaptive usage of cellular and WiFi bandwidth: An optimal scheduling formulation

Ozlem Bilgir Yetim, Margaret Rose Martonosi

Research output: Chapter in Book/Report/Conference proceedingConference contribution

14 Scopus citations


Worldwide, mobile data connectivity is now widespread, but not yet ubiquitous due to coverage limits and cost concerns. Mobile data ofioading to WiFi-where available- could greatly decrease the usage of cellular data networks. In delay-tolerant applications, one could delay network communication in order to exploit free WiFi connections expected to appear soon. However, WiFi connectivity is limited, and even delay-tolerant applications must meet qualityof-service deadlines. To explore such bandwidth scheduling issues, we develop an optimal MILP-based scheduling framework. Our framework schedules multiple application data streams with varying size and delay tolerance, onto networks with varying coverage and bandwidth, in order to minimize cellular data usage. The ability to subdivide data streams into scheduling units is important, because it allows applications to exploit brief windows of WiFi coverage and it allows tradeofis between solution quality and solver runtime.

Original languageEnglish (US)
Title of host publicationCHANTS'12 - 7th ACM International Workshop on Challenged Networks
Number of pages4
StatePublished - 2012
Event7th ACM International Workshop on Challenged Networks, CHANTS 2012 - Istanbul, Turkey
Duration: Aug 22 2012Aug 22 2012

Publication series

NameProceedings of the Annual International Conference on Mobile Computing and Networking, MOBICOM


Other7th ACM International Workshop on Challenged Networks, CHANTS 2012

All Science Journal Classification (ASJC) codes

  • Software
  • Hardware and Architecture
  • Computer Networks and Communications


  • Cellular
  • DTN
  • Optimal scheduling formulation
  • Wireless


Dive into the research topics of 'Adaptive usage of cellular and WiFi bandwidth: An optimal scheduling formulation'. Together they form a unique fingerprint.

Cite this