Null packet replacement with bi-level scheduling
First Claim
1. A system for null packet replacement in a broadcast data stream comprising:
- a global scheduler for receiving data containing null packets from a broadcast source;
a plurality of self-managed queues in communication with said global scheduler;
means for implementing a data management policy for each self-managed queue in each of said plurality of self-managed queues wherein said policy has predefined rules for handling data to be communicated to said global scheduler, a predetermined self-managed queue identifies itself to said global scheduler as being available for service at said global scheduler when said predefined rules of said data management policy have been met;
means for implementing an order of service policy in said global scheduler for determining the order each self-managed queue that has presented itself to the global scheduler as being serviceable will be serviced by the global scheduler, said order of service policy for said global scheduler being separate and distinct from each of said data management policies for said self-managed queues, data from said predetermined queue will replace the null packets in the broadcast data stream with background data thereby defining a modified broadcast data stream upon service of said self-managed queues by said global scheduler;
a receiver serving at least one client and receiving said modified broadcast stream through said global scheduler from said predetermined self-managed queue.
1 Assignment
0 Petitions
Accused Products
Abstract
A system and method for null packet replacement having a global scheduler (12) select data from a plurality of self-managed queues (14) to insert in to the data stream in place of null packets. The queues (14) managed by the global scheduler have rules that are private to each queue Q1, Q2, . . . QN. The global scheduler (12) has a set of rules (16) for prioritizing the queues (14). The global scheduler (12) knows the average data rate for each queue (14) and has a priority assigned to each queue (14). Rules for the global scheduler policy (16) are limited to the order of service for the queues. The present invention is advantageous in that the order of service may be changed at the global scheduler (12) without affecting the independent queues (14).
58 Citations
14 Claims
-
1. A system for null packet replacement in a broadcast data stream comprising:
-
a global scheduler for receiving data containing null packets from a broadcast source; a plurality of self-managed queues in communication with said global scheduler; means for implementing a data management policy for each self-managed queue in each of said plurality of self-managed queues wherein said policy has predefined rules for handling data to be communicated to said global scheduler, a predetermined self-managed queue identifies itself to said global scheduler as being available for service at said global scheduler when said predefined rules of said data management policy have been met; means for implementing an order of service policy in said global scheduler for determining the order each self-managed queue that has presented itself to the global scheduler as being serviceable will be serviced by the global scheduler, said order of service policy for said global scheduler being separate and distinct from each of said data management policies for said self-managed queues, data from said predetermined queue will replace the null packets in the broadcast data stream with background data thereby defining a modified broadcast data stream upon service of said self-managed queues by said global scheduler; a receiver serving at least one client and receiving said modified broadcast stream through said global scheduler from said predetermined self-managed queue. - View Dependent Claims (2, 3, 4, 5)
-
-
6. A method for null packet replacement in a broadcast data stream comprising the steps of:
-
receiving data from a broadcast source at a global scheduler, the data containing null packets, the global scheduler being in communication with a plurality of self-managed queues; applying a data management policy in each self-managed queue, the data management policy being unique to each self-managed queue and having a set of predefined rules for determining a status of each self-managed queue, the self-managed queue assigning a “
ready-to-run”
status and a “
not-ready-to-run”
status to themselves depending on the set of predefined rules in its respective data management policy;communicating the status of each self-managed queue to the global scheduler; applying an order of service policy at said global scheduler for determining the order to service each self-managed queue presenting itself to said global scheduler with a “
ready-to-run”
status, thereby defining a queue available for service at said global scheduler;obtaining data from each queue available for service; replacing null packets in the broadcast data stream with data obtained from each queue available for service. - View Dependent Claims (7, 8, 9)
-
-
10. A method for replacing null packets in a broadcast data stream comprising the steps of:
-
checking the status of a self-managed queue in a plurality of self-managed queues at the self-managed queue; announcing a “
ready-to-run”
status of a self-managed queue by the self-managed queue to a global scheduler;considering a self-managed queue announced to the global scheduler as a “
ready-to-run”
status in a decision making analysis at said global scheduler for replacement of data;replacing null packets in the data stream with data in the “
ready-to-run”
self-managed queue considered by the global scheduler;announcing a “
not-ready-to-run”
status of a self-managed queue by the self-managed queue to a global scheduler;re-checking the status of the self-managed queue after a predetermined amount of time until the self-managed queue identifies itself to the global scheduler as “
ready-to-run.” - View Dependent Claims (11, 12, 13, 14)
-
Specification