Distributed scheduling of media channel playout
Multiple scheduling producers such as content management systems, advertisement systems, and emergency broadcast systems can independently send scheduling events to scheduling consumers such as streaming servers, guide generators, and playlogs. The scheduling consumers maintain state machines with persistent storage to process scheduling events from scheduling producers and output media channel playlists, channel guides, and/or content. Scheduling producers can contribute independently to define a channel playout while information at scheduling consumers remains synchronized.
1. A method for distributed scheduling, the method comprising:
receiving, at a scheduling event messaging middleware, a plurality of scheduling events and their associated time-stamps from a plurality of scheduling producers, wherein the plurality of scheduling producers are separate devices connected to the scheduling event messaging middleware over a network and the scheduling event messaging middleware is configured to receive scheduling events from any number of different scheduling producers over the network;
dynamically prioritizing the scheduling events in a prioritized order as they are received at the scheduling event messaging middleware, wherein the priority is based on the context of the scheduling event;
sending, from the scheduling event messaging middleware, the plurality of scheduling events and their associated time-stamps in the prioritized order, that were received from the plurality of scheduling producers to a plurality of scheduling consumers, wherein the scheduling event messaging middleware is further configured to send scheduling events and their associated time-stamps to any number of different scheduling consumers;
wherein each of the plurality of scheduling consumers includes a state machine that turns the plurality of scheduling events into playouts for each channel in a plurality of channels, wherein each time-stamp identifies a time for a specific channel, from the plurality of channels, at which the specific channel is to play one or more of the plurality of scheduling events.
2. The method of claim 1 , wherein a playout comprises a timestamped sequence of clips to be played out for a particular channel.
3. The method of claim 1 , wherein each state machine maintains a variety of data structures in persistent storage, the variety of data structures maintaining one or more of the following information about: playlists, when/how each playlist is scheduled to play, and the availability interval of each clip in a playlist.
4. The method of claim 1 , wherein the plurality of scheduling events include one or more of the following: playlists, content identifiers, timing information, and actions.
5. The method of claim 1 , wherein the plurality of scheduling producers includes one or more of the following: content providers, content management systems, advertising systems, and emergency broadcast systems.
6. The method of claim 1 , wherein the plurality of scheduling consumers includes one or more of the following: guide generators that create continuously updated channel guides, playlogs that maintain a database of entire clip sequences played out for each channel, content provider management systems that allow content providers to analyze playout of content and advertisements, and streaming servers that use scheduling events to send clips to individual client devices.
7. The method of claim 1 , wherein each state machine is synchronized with other state machines.
8. A system, comprising:
processor;
memory; and
scheduling event messaging middleware configured for:
receiving a plurality of scheduling events and their associated time-stamps from a plurality of scheduling producers, wherein the plurality of scheduling producers are separate devices connected to the scheduling event messaging middleware over a network and the scheduling event messaging middleware is configured to receive scheduling events from any number of different scheduling producers over the network;
dynamically prioritizing the scheduling events in a prioritized order as they are received, wherein the priority is based on the context of the scheduling event;
sending the plurality of scheduling events and their associated time-stamps in the prioritized order, that were received from the plurality of scheduling producers to a plurality of scheduling consumers, wherein the scheduling event messaging middleware is further configured to send scheduling events and their associated time-stamps to any number of different scheduling consumers;
wherein each of the plurality of scheduling consumers includes a state machine that turns the plurality of scheduling events into playouts for each channel in a plurality of channels, wherein each time-stamps identifies a time for a specific channel, from the plurality of channels, at which the specific channel is to play one or more of the plurality of scheduling events.
9. The system of claim 8 , wherein a playout comprises a timestamped sequence of clips to be played out for a particular channel.
10. The system of claim 8 , wherein each state machine maintains a variety of data structures in persistent storage, the variety of data structures maintaining one or more of the following information about: playlists, when/how each playlist is scheduled to play, and the availability interval of each clip in a playlist.
11. The system of claim 8 , wherein the plurality of scheduling events include one or more of the following: playlists, content identifiers, timing information, and actions.
12. The system of claim 8 , wherein the plurality of scheduling producers includes one or more of the following: content providers, content management systems, advertising systems, and emergency broadcast systems.
13. The system of claim 8 , wherein the plurality of scheduling consumers includes one or more of the following: guide generators that create continuously updated channel guides, playlogs that maintain a database of entire clip sequences played out for each channel, content provider management systems that allow content providers to analyze playout of content and advertisements, and streaming servers that use scheduling events to send clips to individual client devices.
14. The system of claim 8 , wherein each state machine is synchronized with other state machines.
15. A non-transitory computer readable storage medium comprising instructions for executing a method, the method comprising:
receiving, at a scheduling event messaging middleware, a plurality of scheduling events and their associated time-stamps from a plurality of scheduling producers, wherein the plurality of scheduling producers are separate devices connected to the scheduling event messaging middleware over a network and the scheduling event messaging middleware is configured to receive scheduling events from any number of different scheduling producers over the network;
dynamically prioritizing the scheduling events in a prioritized order as they are received at the scheduling event messaging middleware, wherein the priority is based on the context of the scheduling event;
sending, from the scheduling event messaging middleware, the plurality of scheduling events and their associated time-stamps in the prioritized order, that were received from the plurality of scheduling producers to a plurality of scheduling consumers, wherein the scheduling event messaging middleware is further configured to send scheduling events and their associated time-stamps to any number of different scheduling consumers;
wherein each of the plurality of scheduling consumers includes a state machine that turns the plurality of scheduling events into playouts for each channel in a plurality of channels, wherein each time-stamp identifies a time for a specific channel, from the plurality of channels, at which the specific channel is to play one or more of the plurality of scheduling events.
16. The non-transitory computer readable storage medium of claim 15 , wherein a playout comprises a timestamped sequence of clips to be played out for a particular channel.
17. The non-transitory computer readable storage medium of claim 15 , wherein each state machine maintains a variety of data structures in persistent storage, the variety of data structures maintaining one or more of the following information about: playlists, when/how each playlist is scheduled to play, and the availability interval of each clip in a playlist.
18. The non-transitory computer readable storage medium of claim 15 , wherein the plurality of scheduling events include one or more of the following: playlists, content identifiers, timing information, and actions.
19. The non-transitory computer readable storage medium of claim 15 , wherein the plurality of scheduling producers includes one or more of the following: content providers, content management systems, advertising systems, and emergency broadcast systems.
20. The non-transitory computer readable storage medium of claim 15 , wherein the plurality of scheduling consumers includes one or more of the following: guide generators that create continuously updated channel guides, playlogs that maintain a database of entire clip sequences played out for each channel, content provider management systems that allow content providers to analyze playout of content and advertisements, and streaming servers that use scheduling events to send clips to individual client devices.