On energy efficient wireless data access: Caching or not?

Mark Kai Ho Yeung, Yu Kwong Kwok

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

2 Citations (Scopus)

Abstract

We consider a typical wireless data access scenario: a number of mobile clients are interested in a set of data items kept at a common server. A client sends a request to inform the server of its desired data item while the server replies in the common broadcast channel. To study the energy consumption characteristics in such a scenario, we first define a power aware utility function. Based on the utility function, we propose a novel wireless data access scheme, which is a non-cooperative game - wireless data access (WDA) game. Although it does not rely on client caching (without-cache), our theoretical analysis shows that it is not always necessary for clients to send requests to the server. Simulation results confirm that our proposed scheme, compared with a simple always-request one, increases both the utility and lifetime of every client while reducing the number of requests sent, at the cost of slightly larger average query delay.

Original languageEnglish
Title of host publicationMobile Ad-hoc and Sensor Networks - First International Conference, MSN 2005, Proceedings
Pages528-537
Number of pages10
DOIs
Publication statusPublished - 2005
Externally publishedYes
Event1st International Conference on Mobile Ad-hoc and Sensor Networks, MSN 2005 - Wuhan, China
Duration: 13 Dec 200515 Dec 2005

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume3794 LNCS
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349

Conference

Conference1st International Conference on Mobile Ad-hoc and Sensor Networks, MSN 2005
Country/TerritoryChina
CityWuhan
Period13/12/0515/12/05

Fingerprint

Dive into the research topics of 'On energy efficient wireless data access: Caching or not?'. Together they form a unique fingerprint.

Cite this