Methods and systems for dynamic routing of content using a static playlist manifest

1. A system, comprising:

a computer device;

a network interface; and

non-transitory computer readable memory having program instructions stored thereon that when executed by the computing device cause the system to perform operations comprising:

populating, using a locator proxy service, a redirect data store with redirect locators, the redirect locators corresponding to a first set of media comprising one or more items of media;

receiving from a user device video player, via the network interface, a request for an item of video content;

accessing a file, the file comprising locators corresponding to:

one or more redirect data store entries storing redirect locators to the one or more items of media in the first set of media;

at least partly in response to the request for an item of video content, transmitting, using the network interface, the file comprising one or more locators corresponding to respective redirect data store entries storing redirect locators to the one or more items of media in the first set of media to the user device;

after transmitting the file comprising locators corresponding to redirect data store entries storing redirect locators to the one or more items of media in the first set of media, replacing a redirect locator to at least a first item of media in the first set of media in the redirect data store with a redirect locator corresponding to a second item of media different than the first item of media associated with the replaced redirect locator;

receiving a request from the user device video player for media, the request directed to a redirect database location storing the redirect locator corresponding to the second item of media; and

at least partly in response to receiving the request for media, the request directed to the redirect database location, the redirect database location storing the redirect locator corresponding to the second item of media, enabling the second item of media to be streamed to the user device.

2. The system as defined in claim 1 , wherein the system is configured to act as a proxy pass through system, wherein at least partly in response to receiving the request for a first item of video content directed to the redirect database the system is configured to:

request the first item of video content from a remote source;

receive the requested first item of video content from the remote source; and

provide the received first item of video content to the user device.

3. The system as defined in claim 1 , wherein the second item of media is streamed to the user device from a content distribution system without traversing the system.

4. The system as defined in claim 1 , the operations further comprising transmitting context data to potential sources of media, the context data comprising information regarding a user of the user device, wherein the file is transmitted to the user device before the context data is transmitted to the potential sources of media, wherein the context data is configured to be used to proposed media to be streamed to the user device as an interstitial during the request item of video content.

5. The system as defined in claim 1 , wherein the item of video content is automatically requested by the video player based at least in part on a comparison of a current time and a scheduled starting time for the item of video content.

6. The system as defined in claim 1 , wherein the file comprises an HLS, DASH, RTMP, HDS, or MSS manifest file.

7. The system as defined in claim 1 , the operations further comprising:

populating the redirect data store with redirect locators corresponding to one or more beacons;

receiving a request directed to the redirect database location storing the redirect locators corresponding to one or more beacons; and

at least partly in response to receiving the request directed to the redirect database location storing the redirect locators corresponding to one or more beacons, causing one or more corresponding HTTP GET requests to be generated.

8. The system as defined in claim 1 , the operations further comprising:

including, in the file, locators corresponding to decryption keys for respective segments of the requested item of video content that are encrypted.

9. The system as defined in claim 1 , the operations further comprising using server-side content insertion to trigger a proxy service and subsequent beacon calls.

10. The system as defined in claim 1 , wherein the file is not alterable by the system after the file is received by the user device.

11. The system as defined in claim 1 , wherein the locators included in the file comprise URLs.

12. A computer implemented method, the method comprising:

populating a redirect data store with redirect locators corresponding to a first set of media comprising one or more items of media;

receiving over a network at a first system comprising a computing device, from a remote user device video player, a request for video content;

accessing, using the first system, a file, the file comprising locators corresponding to:

one or more redirect data store entries storing respective redirect locators to the one or more items of media in the first set of media;

at least partly in response to the request for video content:

transmitting using the first system, over the network to the user device, the file, the file comprising locators corresponding to redirect data store entries storing redirect locators to the one or more items of media in the first set of media;

after transmitting the file comprising locators corresponding to redirect data store entries storing redirect locators to the one or more items of media in the first set of media, replacing a redirect locator to at least a first item of media in the first set of media in the redirect data store with a redirect locator corresponding to a second item of media different than the first item of media associated with the replaced redirect locator;

receiving at the first system a request from the user device directed to a redirect database location storing the redirect locator corresponding to second item of media; and

at least partly in response to receiving the request directed to the redirect database location storing the redirect locator corresponding to the second item of media, enabling the second item of media to be streamed to the user device.

13. The method as defined in claim 12 , the method further comprising:

in response to a receiving a request from the remote user device video player for a first item of media, requesting from a third party system the first item of media;

receiving the requested first item of media from the third party system at the first system; and

providing, via the first system, the received first item of media to the user device.

14. The method as defined in claim 12 , wherein the second item of media is streamed to the user device from a content distribution system without traversing the first system.

15. The method as defined in claim 12 , the method further comprising transmitting context data to potential sources of media, wherein the file is transmitted to the user device before the context data is provided to potential sources of media, wherein the context data is configured to be used by potential sources of media in determining media to be proposed for streaming to the user device.

16. The method as defined in claim 12 , wherein the video content is automatically requested by the user device video player based at least in part on a comparison of a current time and a scheduled starting time for the video content.

17. The method as defined in claim 12 , wherein the file comprises an HLS, DASH, RTMP, HDS, or MSS manifest file.

18. The method as defined in claim 12 , the method further comprising:

populating the redirect data store with redirect locators corresponding to one or more beacons;

receiving a request from the user device directed to the redirect database location storing the redirect locators corresponding to one or more beacons; and

at least partly in response to receiving the request directed to the redirect database location storing the redirect locators corresponding to one or more beacons, causing one or more corresponding HTTP GET requests to be generated.

19. The method as defined in claim 12 , the method further comprising:

including, in the file, locators corresponding to decryption keys for respective segments of the requested video content that are encrypted.

20. The method as defined in claim 12 , the method further comprising using server-side content insertion to trigger a proxy service and subsequent beacon calls.

21. The method as defined in claim 12 , wherein the file is not alterable by the system after the file is received by the user device.

22. The method as defined in claim 12 , wherein the locators included in the file comprise URLs.

23. Non-transitory computer readable data media that stores computer executable instructions that when executed by a computing device, cause the computing device to perform operations comprising:

receiving, from a user device video player, a request for a video content;

accessing a playlist, the playlist comprising locators corresponding to:

entries comprising redirect locators in a redirect data store to a first set of media comprising one or more items of media;

at least partly in response to the request for a video content, transmitting the playlist, comprising locators corresponding to entries comprising redirect locators in the redirect data store to the first set of media, to the user device;

replacing a redirect locator to a first item of media in the first set of media in the redirect data store with a redirect locator corresponding to a second item of media different than first item of media associated with the replaced redirect locator;

receiving from the user device a request directed to a redirect database location storing the redirect locator corresponding to the second item media associated with the replaced redirect locator; and

at least partly in response to receiving the request directed to the redirect database location storing the redirect locator corresponding to the second item of media, enabling the second item of media to be streamed to the user device.

24. The non-transitory computer readable data media as defined in claim 23 , the operations further comprising transmitting context data to potential sources of media, wherein the playlist is transmitted to the user device before the context data is provided to potential sources of media, wherein the context data is configured to be used by potential sources of media in determining media to be proposed for streaming to the user device in association with the requested video content.

25. The non-transitory computer readable data media as defined in claim 23 , wherein the request directed to the redirect database location storing the redirect locator corresponding to the second item of media is automatically generated based at least in part on a comparison of a current time and a scheduled starting time for the video content.

26. The non-transitory computer readable data media as defined in claim 23 , wherein the playlist comprises an HLS, DASH, RTMP, HDS, or MSS playlist.

27. The non-transitory computer readable data media as defined in claim 23 , the operations further comprising:

populating the redirect data store with redirect locators corresponding to one or more beacons;

receiving from the user device a request directed to the redirect database location storing the redirect locators corresponding to one or more beacons; and

at least partly in response to receiving the request directed to the redirect database location storing the redirect locators corresponding to one or more beacons, causing one or more corresponding HTTP GET requests to be generated.

28. The non-transitory computer readable data media as defined in claim 23 , the operations further comprising:

including, in the playlist, locators corresponding to decryption keys for respective segments of the requested video content that are encrypted.

29. The non-transitory computer readable data media as defined in claim 23 , the operations further comprising using server-side content insertion to trigger a proxy service and subsequent beacon calls.

30. The non-transitory computer readable data media as defined in claim 23 , wherein the locators included in the playlist comprise URLs.