Method and system for scheduling requests in a non-first in first out (FIFO) order in a network
First Claim
1. A method for scheduling requests generated for a plurality of mobile devices in a communication network, the requests being generated for a transmission opportunity, the method comprising:
- computing a sort metric for each request based on an information update, wherein the sort metric represents a priority associated with each request;
computing a lead-time for each request based on the sort metric for a time slice wherein the lead-time is a time when each request is considered for allocation in the time slice before the beginning of a next time slice, the lead-time being computed with respect to a drop-dead time of the time slice, wherein the drop-dead time is a time before which scheduling has to be completed so that data can be transmitted during the time slice and wherein each request becomes eligible for processing after a unit of time determined by (T-S)/N where T is a duration of the time slice, S is the duration of a slack time during which a request is not eligible for processing and N is a number of requests; and
considering each request for allocation in the time slice before the beginning of a next time slice such that the request is considered for allocation within a time interval equal to a difference between the drop-dead time and the lead-time for the request.
4 Assignments
0 Petitions
Accused Products
Abstract
A method and a system for scheduling requests generated for a plurality of mobile devices in a communication network (100) has been disclosed. The requests are generated for a transmission opportunity. The method includes computing a sort metric (302) for each request, based on an information update. A lead-time is then computed (304) with respect to a drop-dead time for each request, based on the sort metric for a time slice. The drop-dead time for a given time slice is the time before which scheduling has to be done so that data can be transmitted during the given time slice. Each request may be considered (306) for allocation in the time slice before the beginning of a next time slice, based on the lead-time.
-
Citations
24 Claims
-
1. A method for scheduling requests generated for a plurality of mobile devices in a communication network, the requests being generated for a transmission opportunity, the method comprising:
- computing a sort metric for each request based on an information update, wherein the sort metric represents a priority associated with each request;
computing a lead-time for each request based on the sort metric for a time slice wherein the lead-time is a time when each request is considered for allocation in the time slice before the beginning of a next time slice, the lead-time being computed with respect to a drop-dead time of the time slice, wherein the drop-dead time is a time before which scheduling has to be completed so that data can be transmitted during the time slice and wherein each request becomes eligible for processing after a unit of time determined by (T-S)/N where T is a duration of the time slice, S is the duration of a slack time during which a request is not eligible for processing and N is a number of requests; and
considering each request for allocation in the time slice before the beginning of a next time slice such that the request is considered for allocation within a time interval equal to a difference between the drop-dead time and the lead-time for the request. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
- computing a sort metric for each request based on an information update, wherein the sort metric represents a priority associated with each request;
-
11. A method for scheduling requests generated for a plurality of mobile devices in a communication network, the request being generated for a transmission opportunity, the method comprising:
- forwarding each request to a plurality of Base Transceiver Stations (BTSs) in the communication network;
sending an information update to the plurality of BTSs;
computing a sort metric for each request based on the information update, wherein the sort metric represents a priority associated with each request;
computing a lead-time for each request based on the sort metric for a time slice wherein the lead-time is a time when each request is considered for allocation in the time slice before the beginning of a next time slice, the lead-time being computed with respect to a drop-dead time of the time slice, wherein the drop-dead time is a time before which scheduling has to be completed so that data can be transmitted during the time slice and wherein each request becomes eligible for processing after a unit of time determined b¥
(T-S)/N where T is a duration of the time slice, S is the duration of a slack time during which a request is not eligible for processing and N is a number of requests; and
considering each request for allocation in the time slice before the beginning of a next time slice such that the request is considered for allocation within a time interval equal to a difference between the drop-dead time and the lead-time for the request. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19)
- forwarding each request to a plurality of Base Transceiver Stations (BTSs) in the communication network;
-
20. A system for scheduling requests generated for a plurality of mobile devices in a communication network, the system comprising:
- a plurality of Base Transceiver Stations (BTSs) that are capable of receiving requests, the requests being generated for a transmission opportunity wherein the BTS comprise a time slice module that is capable of computing a lead-time for each request based on a sort metric and a scheduler capable of scheduling the requests based on the lead-time such that each request with a larger lead-time in a time slice is considered for allocation of a transmission opportunity ahead of each request with a lower lead-time in the time slice and within a time interval equal to a difference between a drop-dead time of the time slice and the lead-time of the requests such that the request is allocated before the drop-dead time and wherein the lead-time is a time when each request is considered for allocation in the time slice before the beginning of a next time slice and the drop-dead time is a time before which scheduling has to be completed so that data can be transmitted during the time slice, wherein a slack time is provided before processing the requests when at least one of the plurality of BTSs lacks required processing power, the plurality of BTSs further being capable of receiving an information update from the plurality of mobile devices and wherein each request becomes eligible for processing after a unit of time determined by (T-S)/N where T is a duration of the time slice, S is the duration of a slack time during which a request is not eligible for processing and N is a number of requests; and
a Base Station Controller (BSC) the BSC being capable of computing the sort metric based on the information update, wherein the sort metric represents a priority associated with each request, the information update being sent by the plurality of BTSs. - View Dependent Claims (21, 22, 23, 24)
- a plurality of Base Transceiver Stations (BTSs) that are capable of receiving requests, the requests being generated for a transmission opportunity wherein the BTS comprise a time slice module that is capable of computing a lead-time for each request based on a sort metric and a scheduler capable of scheduling the requests based on the lead-time such that each request with a larger lead-time in a time slice is considered for allocation of a transmission opportunity ahead of each request with a lower lead-time in the time slice and within a time interval equal to a difference between a drop-dead time of the time slice and the lead-time of the requests such that the request is allocated before the drop-dead time and wherein the lead-time is a time when each request is considered for allocation in the time slice before the beginning of a next time slice and the drop-dead time is a time before which scheduling has to be completed so that data can be transmitted during the time slice, wherein a slack time is provided before processing the requests when at least one of the plurality of BTSs lacks required processing power, the plurality of BTSs further being capable of receiving an information update from the plurality of mobile devices and wherein each request becomes eligible for processing after a unit of time determined by (T-S)/N where T is a duration of the time slice, S is the duration of a slack time during which a request is not eligible for processing and N is a number of requests; and
Specification