I. Introduction
In wireless broadcasts, data items are disseminated cyclically via a set of wireless channels. Clients (or users) can access the available channels and download any data items of interests. Compared with point-to-point data communications, wireless data broadcasts allow a large number of mobile clients to access data simultaneously, and thus are more scalable and flexible [25]. Generally, there are two major performance concerns for wireless data broadcast systems. One is tuning time and the other is access time. Tuning time is the performance criterium to evaluate the energy efficiency; while access time, defined as the time duration from the moment a request is submitted to the moment all the requested data items are downloaded, reflects the response delay. In this study, we assume the broadcasting time of requested data items are known, and we study the data retrieval scheduling for multi-item requests from the clients' point of view. The objective is to minimize the access time of a given request. Actually, there are three factors that affect the access time of requests:
Consider the network's point of view, a straightforward way to minimize the average access time is to increase the system throughput. The Orthogonal Frequency-Division Multiplexing (OFDM) technique makes efficiently broadcasting data through multiple channels possible [27]. Over the past decade, multi-channel models gained more popularity for wireless data disseminations (see e.g. [9], [10], [12], [15], [16], [17], [19], [20], [21], [22], [23], [26], [27], [29]).
Consider the server's point of view, since all the data items are disseminated cyclically via a set of channels, different broadcasting schedules will result in different expected access time. There have been intensive research efforts on data scheduling at the server side with respect to minimizing the expected access time (see e.g. [2], [7], [9], [12], [15], [16], [17], [19], [21], [23]).
Consider the client's point of view, when downloading multiple data items from multiple channels, clients probably need switchings among channels, which will cause possible conflicts [20], [26]. Therefore, besides data scheduling at the server side, data retrieval scheduling at the client side is also an important issue [20], [26], [29], [30], [31], [32].