BROADCAST CONTENT VIA OVER THE TOP DELIVERY

• US 20130276035A1
• Filed: 03/13/2013
• Published: 10/17/2013
• Est. Priority Date: 04/12/2012
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: WALKER, Gordon Kent, LO, Charles N., WANG, Jun, ZEILINGOLD, Daphna, BARONE, Joseph P., TIONGSON, Ed O.
• Granted Patent: US 9,009,764 B2
• Time in Patent Office: Days
• US Class Current: 725/62
• CPC Class Codes: H04L 65/00 Network arrangements, protocols or services for supporting real-time applications in data packet communication real-time or near real-time messaging, e.g. instant messaging [IM] H04L51/04; selective video distribution H04N21/00
• CPC Class Codes: H04N 21/235 Processing of additional data, e.g. scrambling of additional data or processing content descriptors
• CPC Class Codes: H04N 21/2381 Adapting the multiplex stream to a specific network, e.g. an Internet Protocol [IP] network transmission of MPEG streams over ATM H04L12/5601
• CPC Class Codes: H04N 21/24 Monitoring of processes or resources, e.g. monitoring of server load, available bandwidth, upstream requests monitoring of server performance or load G06F11/34; arrangements for observation, testing or troubleshooting for broadcast or for distribution combined with broadcast H04H20/12
• CPC Class Codes: H04N 21/2402 Monitoring of the downstream path of the transmission network, e.g. bandwidth available traffic monitoring in data switching networks H04L43/00; monitoring data switching networks utilization H04L43/0876
• CPC Class Codes: H04N 21/2407 Monitoring of transmitted content, e.g. distribution time, number of downloads arrangements for monitoring programmes for broadcast or for distribution combined with broadcast H04H20/14
• CPC Class Codes: H04N 21/25841 involving the geographical location of the client retrieval from the Internet by querying based on geographical locations G06F16/9537; arrangements for identifying locations of receiving stations in broadcast systems H04H60/51; location of the user terminal in data switching networks H04L67/52; services making use of the location of users or terminals in wireless networks H04W4/02; locating users or terminals in wireless networks H04W64/00
• CPC Class Codes: H04N 21/25875 involving end-user authentication restricting access to computer systems by authenticating users using a predetermined code G06F21/33; arrangements for secret or secure communication including means for verifying the identity or authority of a user of the system H04L9/32; networks authentication protocols H04L63/08; authentication in wireless network security H04W12/06
• CPC Class Codes: H04N 21/25891 being end-user preferences retrieval of video data in a video database based on user preferences G06F16/739; arrangements for recognizing users' preferences H04H60/46; user profiles in network data switching protocols H04L67/306; processing of user preferences or user profiles in wireless networks H04W8/18
• CPC Class Codes: H04N 21/41407 embedded in a portable device, e.g. video client on a mobile phone, PDA, laptop constructional details of equipment or arrangements specially adapted for portable computer application G06F1/1626; arrangements specially adapted for mobile receivers in broadcast systems H04H20/57
• CPC Class Codes: H04N 21/435 Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
• CPC Class Codes: H04N 21/44204 Monitoring of content usage, e.g. the number of times a movie has been viewed, copied or the amount which has been watched monitoring of user activities for profile generation for accessing a video database G06F16/739; protecting generic digital content where the protection is independent of the precise nature of the content G06F21/10; arrangements for monitoring the use made of the broadcast services in broadcast systems H04H60/31
• CPC Class Codes: H04N 21/4524 involving the geographical location of the client retrieval from the Internet by querying based on geographical locations G06F16/9537; systems specially adapted for using geographical information in broadcast systems H04H60/70; protocols in which the network application is adapted for the location of the user terminal in communication control or processing H04L67/52; services making use of the location of users or terminals in wireless networks H04W4/02; locating users or terminals in wireless networks H04W64/00
• CPC Class Codes: H04N 21/4532 involving end-user characteristics, e.g. viewer profile, preferences monitoring of user activities for profile generation for accessing a video database G06F16/739; user profiles in network data switching protocols H04L67/306; processing of user preferences or user profiles in wireless networks H04W8/18
• CPC Class Codes: H04N 21/6405 Multicasting data broadcast and multicast in packet switching networks H04L12/18
• CPC Class Codes: H04N 21/6408 Unicasting
• CPC Class Codes: H04N 21/64322 IP
• CPC Class Codes: H04N 21/647 Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless real-time session protocols H04L65/1101
• CPC Class Codes: H04N 21/64707 for transferring content from a first network to a second network, e.g. between IP and wireless
• CPC Class Codes: H04N 21/64723 Monitoring of network processes or resources, e.g. monitoring of network load traffic related reporting in data switching networks H04L43/062
• CPC Class Codes: H04N 21/64738 : Monitoring network characteristics, e.g. bandwidth, congestion level data switched network analysis H04L41/14; monitoring functioning in data switched networks H04L43/0817; flow control in packet networks H04L47/10
• CPC Class Codes: H04N 21/654 : Transmission by server directed to the client
• CPC Class Codes: H04N 21/812 : involving advertisement data advertising per se G06Q30/02
• CPC Class Codes: H04N 21/8456 : by decomposing the content in the time domain, e.g. in time segments
• CPC Class Codes: H04W 4/02 : Services making use of location information
• CPC Class Codes: H04W 4/021 : Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
• CPC Class Codes: H04W 4/029 : Location-based management or tracking services
• CPC Class Codes: H04W 4/06 : Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
• CPC Class Codes: H04W 4/21 : for social networking applications

Abstract

Systems, methods, and receiver devices enable broadcasters with restricted content license areas (e.g., Designated Market Areas (“DMAs”) to distribute content via Over the Top (“OTT”) IP networks. Embodiments enable client reporting and authentication as well as broadcast content encryption. In an embodiment, information from the client may be reported back to the broadcasters, such as a view history/use report. In an embodiment, hand off between DMAs may be enabled. In an embodiment, local advertisement insertion in network content may be enabled. Embodiments may enable Multicast-Broadcast Single Frequency Network (“MBSFN”) operation across DMA boundaries.

Claims

1. A method for delivering Over the Top (“

OTT”

) television content to one or more receiver devices, comprising;

broadcasting the OTT television content to the one or more of receiver devices;

determining a network traffic level for the OTT television content in a Designated Market Area (“

DMA”

);

determining whether the network traffic level exceeds a traffic level threshold; and

switching to evolved Multimedia Broadcast Multicast Service (“

eMBMS”

) for delivery of the OTT television content in response to determining that the network traffic level exceeds the traffic level threshold.

2. The method of claim 1, further comprising:

determining the Multicast/Broadcast Single Frequency Networks (“

MBSFNs”

) to turn on based at least in part on a distribution of the one or more receiver devices within the DMA.

3. The method of claim 1, further comprising:

determining the Multicast/Broadcast Single Frequency Networks (“

MBSFNs”

) to turn on based at least in part on a list of MBSFNs associated with the DMA.

4. The method of claim 1, wherein broadcasting the OTT television content to the one or more receiver devices further comprises broadcasting a unique ID associated with the broadcaster of the OTT television content.

5. The method of claim 4, wherein the unique ID is the broadcaster'"'"'s Federal Communications Commission (“

FCC”

) ID.

6. A method for delivering Over the Top (“

OTT”

) television content to a receiver device, comprising;

sending the OTT television content to the receiver device as a podcast;

receiving the podcast in the receiver device;

storing the podcast in a memory of the receiver device;

receiving a Designated Market Area (“

DMA”

) record corresponding to a licensed region in the receiver device;

determining the current location of the receiver device;

comparing the current location of the receiver device to the DMA record to determine whether the receiver device is located within the corresponding licensed region; and

displaying the podcast in response to determining that the receiver device is located within the corresponding licensed region.

7. The method of claim 6, further comprising:

monitoring content usage reports to determine OTT television content with low user satisfaction,

wherein sending the OTT television content to the receiver device as a podcast comprises sending the OTT television content to the receiver device as a podcast in response to determining that the OTT television content is OTT television content with low user satisfaction.

8. The method of claim 6, further comprising:

monitoring content usage reports to determine OTT television content with high user interest,

wherein sending the OTT television content to the receiver device as a podcast comprises sending the OTT television content to the receiver device as a podcast in response to determining that the OTT television content is OTT television content with high user interest.

9. The method of claim 6, further comprising:

comparing a location history log of the receiver device to any podcasts stored in the memory of the receiver device; and

deleting podcasts which do not correspond to recurring entries on the location history log.

10. The method of claim 6, further comprising:

generating a view history report including a DMA identifier of the corresponding licensed region upon displaying the podcast; and

sending the view history report to a server.

11. A method for delivering Over the Top (“

OTT”

) television content to a receiver device, comprising;

setting an availability time for the OTT television content media segments that is the same at two or more broadcast servers associated with adjacent Designated Market Areas (“

DMA”

s);

sending a Media Presentation Description (“

MPD”

) to the receiver device, the MPD including the availability time; and

sending the OTT television content to the receiver device in a Dynamic Adaptive Streaming Over HTTP (“

DASH”

) format.

12. A method for delivering Over the Top (“

OTT”

) television content to a receiver device, comprising;

sending the OTT television content to the receiver device in a Dynamic Adaptive Streaming Over HTTP (“

DASH”

) format; and

signaling to the receiver device a playout time for any segment of the OTT television content that is no earlier than a latest availability time for that segment among all Media Presentation Descriptions (“

MPDs”

) in a Designated Market Area (“

DMA”

).

13. A method for delivering Over the Top (“

OTT”

) television content to a receiver device, comprising;

receiving a first programming request from the receiver device corresponding to a first Designated Market Area (“

DMA”

);

providing a first OTT television content to the receiver device via a first Multicast-Broadcast Single Frequency Network (“

MBSFN”

);

receiving a second programming request from the receiver device corresponding to a second DMA;

providing a second OTT television content to the receiver device via a second MBSFN;

determining whether the first OTT television content and the second OTT television content are the same OTT television content; and

merging the first MBSFN and the second MBSFN into a single MBSFN in response to determining that the first OTT television content and the OTT second television content are the same OTT television content.

14. The method of claim 13, wherein determining whether the first OTT television content and the second OTT television content are the same OTT television content comprises inspecting packets of the first OTT television content and the second OTT television content.

15. The method of claim 13, wherein determining whether the first OTT television content and the OTT second television content are the same OTT television content comprises comparing the source uniform resource locator (“

URL”

) for the first OTT television content to the URL for the second OTT television content.

16. A method for delivering Over the Top (“

OTT”

) television content to a receiver device, comprising;

receiving a first programming schedule for a first Designated Market Area (“

DMA”

);

receiving a second programming schedule for a second DMA;

determining a period of time when programming scheduled for the first DMA and the second DMA is the same based at least in part on the received first and second programming schedules;

creating a combined Multicast-Broadcast Single Frequency Network (“

MBSFN”

) encompassing both the first and the second DMA during the determined period of time;

receiving a first report from a first receiver device in the first DMA during the determined period of time, the first report including an indication of an OTT television content received by the first receiver device during the determined period of time;

receiving a second report from a second receiver device in the second DMA during the determined period of time, the second report including an indication of an OTT television content received by the second receiver device during the determined period of time;

determining whether the indication of the OTT television content in the first report is the same as the indication of the OTT television content in the second report; and

splitting the combined MBSFN into a first MBSFN corresponding to the first DMA and a second MBSFN corresponding to the second DMA in response to determining that the indication of the OTT television content in the first report is not the same as the indication of the OTT television content in the second report.

17. The method of claim 16, wherein determining whether the indication of the OTT television content in the first report is the same as the indication of the OTT television content in the second report comprises comparing the source uniform resource locator (“

URL”

) for the first OTT television content to the URL for the second OTT television content.

18. The method of claim 16, wherein determining whether the indication of the OTT television content in the first report is the same as the indication of the OTT television content in the second report comprises comparing a content ID in the first report to a content ID in the second report.

19. The method of claim 16, further comprising:

sending, after receiving the first report and the second report, a shut off message to any receiver devices in the first DMA and second DMA, the shut off message including an indication for receiver devices to stop sending reports for a period of time.

20. A method for delivering Over the Top (“

OTT”

) television content to a receiver device, comprising;

receiving a subscription notification message from the receiver device at a server, the subscription notification message including an indication of a podcast requested by the receiver device;

determining whether the receiver device is an evolved Multimedia Broadcast Multicast Service (“

eMBMS”

) subscriber device based at least in part on the subscription notification message;

scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device;

generating an eMBMS schedule identifying a time at which the requested podcast will be broadcast via the eMBMS broadcast;

providing the eMBMS schedule to the receiver device; and

broadcasting the podcast via an eMBMS network.

21. The method of claim 20, wherein the subscription notification message is sent in response to a user subscription to a future podcast.

22. The method of claim 21, wherein the user subscription to a future podcast is a user subscription to an RSS feed or an Atom feed.

23. The method of claim 21, wherein the future podcast is a syndicated podcast, the method further comprising:

monitoring content usage reports for the syndicated podcast to determine a usage level for the syndicated podcast; and

discontinuing broadcast delivery of the syndicated podcast upon determining that the usage level is below a minimum usage level.

24. The method of claim 20, wherein the subscription notification message further includes a user identification, receiver device identification, and location information.

25. The method of claim 24, further comprising assigning view credit for the requested podcast based at least in part on the location information upon receiving the subscription notification in the server.

26. The method of claim 20, further comprising:

determining an IP address associated with the subscription notification message;

determining a probable location of the receiver device based at least in part on the IP address; and

determining whether the probable location of the receiver device corresponds to a Designated Market Area (“

DMA”

) in which eMBMS broadcasts of the requested podcast are licensed,

wherein scheduling the requested podcast for an eMBMS broadcast upon determining the receiver device is an eMBMS subscriber device further comprises scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device and determining that the probable location of the receiver device corresponds to a DMA in which eMBMS broadcasts of the requested podcast are licensed.

27. The method of claim 20, wherein determining whether the receiver device is an evolved Multimedia Broadcast Multicast Service (“

eMBMS”

) subscriber device based at least in part on the subscription notification message further comprises determining whether the receiver device is an eMBMS subscriber device and a user associated with the receiver device is an existing eMBMS subscriber based at least in part on the subscription notification message.

28. The method of claim 20, further comprising:

sending a subscription notification response to the receiver device indicating that the requested podcast is scheduled for eMBMS broadcast;

automatically subscribing the receiver device to the requested podcast in response to receiving the subscription notification response in the receiver device;

receiving the podcast in the receiver device; and

playing the podcast in the receiver device.

29. The method of claim 28, further comprising:

determining a location of the receiver device upon playing the podcast in the receiver device;

generating a view history report including the location of the receiver device upon playing the podcast;

sending the view history report to the server;

receiving the view history report in the server; and

assigning view credit for the podcast based at least in part on the location of the receiver device upon playing the podcast.

30. The method of claim 20, further comprising:

determining a location indication associated with the subscription notification message;

determining a probable location of the receiver device based at least in part on the location indication; and

determining whether the probable location of the receiver device corresponds to a Designated Market Area (“

DMA”

) in which eMBMS broadcasts of the requested podcast are licensed,

wherein scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device further comprises scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device and determining that the probable location of the receiver device corresponds to a DMA in which eMBMS broadcasts of the requested podcast are licensed.

31. The method of claim 30, wherein the location indication is one of a receiver device DMA designation, a receiver device latitude and longitude, a cell ID, and a Wi-Fi access point SSID.

32. A server, comprising:

means for broadcasting Over the Top (“

OTT”

) television content to one or more of receiver devices;

means for determining a network traffic level for the OTT television content in a Designated Market Area (“

DMA”

);

means for determining whether the network traffic level exceeds a traffic level threshold; and

means for switching to evolved Multimedia Broadcast Multicast Service (“

eMBMS”

) for the delivery of the OTT television content in response to determining that the network traffic level exceeds the traffic level threshold.

33. The server of claim 32, further comprising:

means for determining the Multicast/Broadcast Single Frequency Networks (“

MBSFNs”

) to turn on based at least in part on a distribution of the one or more receiver devices within the DMA.

34. The server of claim 32, further comprising:

means for determining the Multicast/Broadcast Single Frequency Networks (“

MBSFNs”

) to turn on based at least in part on a list of MBSFNs associated with the DMA.

35. The server of claim 32, wherein the means for broadcasting the OTT television content to the one or more receiver devices further comprise means for broadcasting a unique ID associated with the broadcaster of the OTT television content.

36. The server of claim 35, wherein the unique ID is the broadcaster'"'"'s Federal Communications Commission (“

FCC”

) ID.

37. A system, comprising:

a receiver device; and

a server, comprising;

means for sending Over the Top (“

OTT”

) television content to the receiver device as a podcast,

wherein the receiver device comprises;

means for receiving the podcast;

means for storing the podcast;

means for receiving a Designated Market Area (“

DMA”

) record corresponding to a licensed region;

means for determining the current location of the receiver device;

means for comparing the current location of the receiver device to the DMA record to determine whether the receiver device is located within the corresponding licensed region; and

means for displaying the podcast in response to determining that the receiver device is located within the corresponding licensed region.

38. The system of claim 37, wherein the server further comprises:

means for monitoring content usage reports to determine OTT television content with low user satisfaction, and

wherein means for sending the OTT television content to the receiver device as a podcast comprises means for sending the OTT television content to the receiver device as a podcast in response to determining that the OTT television content is OTT television content with low user satisfaction.

39. The system of claim 37, wherein the server further comprises:

means for monitoring content usage reports to determine OTT television content with high user interest, and

wherein means for sending the OTT television content to the receiver device as a podcast comprises means for sending the OTT television content to the receiver device as a podcast in response to determining that the OTT television content is OTT television content with high user interest.

40. The system of claim 37, wherein the receiver device further comprises:

means for comparing a location history log of the receiver device to any podcasts stored at the receiver device; and

means for deleting podcasts which do not correspond to recurring entries on the location history log.

41. The system of claim 37, wherein the receiver device further comprises:

means for generating a view history report including a DMA identifier of the corresponding licensed region upon displaying the podcast; and

means for sending the view history report to the server.

42. A server, comprising:

means for setting an availability time for Over the Top (“

OTT”

) television content media segments that is the same at two or more broadcast servers associated with adjacent Designated Market Areas (“

DMAs”

);

means for sending a Media Presentation Description (“

MPD”

) to a receiver device, the MPD including the availability time; and

means for sending the OTT television content to the receiver device in a Dynamic Adaptive Streaming Over HTTP (“

DASH”

) format.

43. A server, comprising:

means for sending Over the Top (“

OTT”

) television content to a receiver device in a Dynamic Adaptive Streaming Over HTTP (“

DASH”

) format; and

means for signaling to the receiver device a playout time for any segment of the OTT television content that is no earlier than a latest availability time for that segment among all Media Presentation Descriptions (“

MPDs”

) in a Designated Market Area (“

DMA”

).

44. A server, comprising:

means for receiving a first programming request from a receiver device corresponding to a first Designated Market Area (“

DMA”

);

means for providing a first Over the Top (“

OTT”

) television content to the receiver device via a first Multicast-Broadcast Single Frequency Network (“

MBSFN”

);

means for receiving a second programming request from the receiver device corresponding to a second DMA;

means for providing a second OTT television content to the receiver device via a second MBSFN;

means for determining whether the first OTT television content and the second OTT television content are the same OTT television content; and

means for merging the first MBSFN and the second MBSFN into a single MBSFN in response to determining that the first OTT television content and the OTT second television content are the same OTT television content.

45. The server of claim 44, wherein means for determining whether the first OTT television content and the second OTT television content are the same OTT television content comprises means for inspecting packets of the first OTT television content and the second OTT television content.

46. The server of claim 44, wherein means for determining whether the first OTT television content and the OTT second television content are the same OTT television content comprises means for comparing the source uniform resource locator (“

URL”

) for the first OTT television content to the URL for the second OTT television content.

47. A server, comprising:

means for receiving a first programming schedule for a first Designated Market Area (“

DMA”

);

means for receiving a second programming schedule for a second DMA;

means for determining a period of time when programming scheduled for the first DMA and the second DMA is the same based at least in part on the received first and second programming schedules;

means for creating a combined Multicast-Broadcast Single Frequency Network (“

MBSFN”

) encompassing both the first and the second DMA during the determined period of time;

means for receiving a first report from a first receiver device in the first DMA during the determined period of time, the first report including an indication of an Over the Top (“

OTT”

) television content received by the first receiver device during the determined period of time;

means for receiving a second report from a second receiver device in the second DMA during the determined period of time, the second report including an indication of an OTT television content received by the second receiver device during the determined period of time;

means for determining whether the indication of the OTT television content in the first report is the same as the indication of the OTT television content in the second report; and

means for splitting the combined MBSFN into a first MBSFN corresponding to the first DMA and a second MBSFN corresponding to the second DMA in response to determining that the indication of the OTT television content in the first report is not the same as the indication of the OTT television content in the second report.

48. The server of claim 47, wherein means for determining whether the indication of the OTT television content in the first report is the same as the indication of the OTT television content in the second report comprises means for comparing the source uniform resource locator (“

URL”

) for the first OTT television content to the URL for the second OTT television content.

49. The server of claim 47, wherein means for determining whether the indication of the OTT television content in the first report is the same as the indication of the OTT television content in the second report comprises means for comparing a content ID in the first report to a content ID in the second report.

50. The server of claim 47, further comprising:

means for sending, after receiving the first report and the second report, a shut off message to any receiver devices in the first DMA and second DMA, the shut off message including an indication for receiver devices to stop sending reports for a period of time.

51. A server, comprising:

means for receiving a subscription notification message from a receiver device, the subscription notification message including an indication of a podcast requested by the receiver device;

means for determining whether the receiver device is an evolved Multimedia Broadcast Multicast Service (“

eMBMS”

) subscriber device based at least in part on the subscription notification message;

means for scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device;

means for generating an eMBMS schedule identifying a time at which the requested podcast will be broadcast via the eMBMS broadcast;

means for providing the eMBMS schedule to the receiver device; and

means for broadcasting the podcast via an eMBMS network.

52. The server of claim 51, wherein the subscription notification message is sent in response to a user subscription to a future podcast.

53. The server of claim 52, wherein the user subscription to a future podcast is a user subscription to an RSS feed or an ATOM feed.

54. The server of claim 52, wherein the future podcast is a syndicated podcast, the server further comprising:

means for monitoring content usage reports for the syndicated podcast to determine a usage level for the syndicated podcast; and

means for discontinuing broadcast delivery of the syndicated podcast upon determining that the usage level is below a minimum usage level.

55. The server of claim 51, wherein the subscription notification message further includes a user identification, receiver device identification, and location information.

56. The server of claim 55, further comprising means for assigning view credit for the requested podcast based at least in part on the location information upon receiving the subscription notification in the server.

57. The server of claim 51, further comprising:

means for determining an IP address associated with the subscription notification message;

means for determining a probable location of the receiver device based at least in part on the IP address; and

means for determining whether the probable location of the receiver device corresponds to a Designated Market Area (“

DMA”

) in which eMBMS broadcasts of the requested podcast are licensed,

wherein means for scheduling the requested podcast for an eMBMS broadcast upon determining the receiver device is an eMBMS subscriber device further comprises means for scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device and determining that the probable location of the receiver device corresponds to a DMA in which eMBMS broadcasts of the requested podcast are licensed.

58. The server of claim 51, wherein means for determining whether the receiver device is an evolved Multimedia Broadcast Multicast Service (“

eMBMS”

) subscriber device based at least in part on the subscription notification message further comprises means for determining whether the receiver device is an eMBMS subscriber device and a user associated with the receiver device is an existing eMBMS subscriber based at least in part on the subscription notification message.

59. The server of claim 51, further comprising:

means for determining a location indication associated with the subscription notification message;

means for determining a probable location of the receiver device based at least in part on the location indication; and

means for determining whether the probable location of the receiver device corresponds to a Designated Market Area (“

DMA”

) in which eMBMS broadcasts of the requested podcast are licensed,

wherein means for scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device further comprises means for scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device and determining that the probable location of the receiver device corresponds to a DMA in which eMBMS broadcasts of the requested podcast are licensed.

60. The server of claim 59, wherein the location indication is one of a receiver device DMA designation, a receiver device latitude and longitude, a cell ID, and a Wi-Fi access point SSID.

61. A system, comprising:

a receiver device; and

a server, comprising;

means for receiving a subscription notification message from the receiver device, the subscription notification message including an indication of a podcast requested by the receiver device;

means for determining whether the receiver device is an evolved Multimedia Broadcast Multicast Service (“

eMBMS”

) subscriber device based at least in part on the subscription notification message;

means for scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device;

means for generating an eMBMS schedule identifying a time at which the requested podcast will be broadcast via the eMBMS broadcast;

means for providing the eMBMS schedule to the receiver device;

means for sending a subscription notification response to the receiver device indicating that the requested podcast is scheduled for eMBMS broadcast and

means for broadcasting the podcast via an eMBMS network,

wherein the receiver device comprises;

means for receiving the eMBMS schedule;

means for automatically subscribing the receiver device to the requested podcast in response to receiving the subscription notification response in the receiver device;

means for receiving the podcast; and

means for playing the podcast.

62. The system of claim 61, wherein the receiver device further comprises:

means for determining a location of the receiver device upon playing the podcast;

means for generating a view history report including the location of the receiver device upon playing the podcast; and

means for sending the view history report to the server, and

wherein the server further comprises;

means for receiving the view history report; and

means for assigning view credit for the podcast based at least in part on the location of the receiver device upon playing the podcast.

63. A server, comprising:

a network interface configured to communicate with a communication network; and

a processor coupled to the network interface, wherein the processor is configured with processor-executable instructions to perform operations comprising;

broadcasting Over the Top (“

OTT”

) television content to one or more of receiver devices via the network interface;

determining a network traffic level for the OTT television content in a Designated Market Area (“

DMA”

);

determining whether the network traffic level exceeds a traffic level threshold; and

switching to evolved Multimedia Broadcast Multicast Service (“

eMBMS”

) for the delivery of the OTT television content in response to determining that the network traffic level exceeds the traffic level threshold.

64. The server of claim 63, wherein the processor is configured with processor-executable instructions to perform operations further comprising:

determining the Multicast/Broadcast Single Frequency Networks (“

MBSFNs”

) to turn on based at least in part on a distribution of the one or more receiver devices within the DMA.

65. The server of claim 63, wherein the processor is configured with processor-executable instructions to perform operations further comprising:

determining the Multicast/Broadcast Single Frequency Networks (“

MBSFNs”

) to turn on based at least in part on a list of MBSFNs associated with the DMA.

66. The server of claim 63, wherein the processor is configured with processor-executable instructions to perform operations such that broadcasting the OTT television content to the one or more receiver devices further comprise broadcasting a unique ID associated with the broadcaster of the OTT television content.

67. The server of claim 66, wherein the processor is configured with processor-executable instructions to perform operations such that the unique ID is the broadcaster'"'"'s Federal Communications Commission (“

FCC”

) ID.

68. A system, comprising:

a receiver device, comprising;

a first network interface configured to communicate with a communication network; and

a receiver device processor coupled to the first network interface; and

a server, comprising;

a second network interface configured to communicate with the communication network; and

a server processor coupled to the second network interface, wherein the server processor is configured with processor-executable instructions to perform operations comprising;

sending Over the Top (“

OTT”

) television content to the receiver device as a podcast via the second network interface, and

wherein the receiver device processor is configured with processor-executable instructions to perform operations comprising;

receiving the podcast via the first network interface;

storing the podcast;

receiving a Designated Market Area (“

DMA”

) record corresponding to a licensed region via the first network interface;

determining the current location of the receiver device;

comparing the current location of the receiver device to the DMA record to determine whether the receiver device is located within the corresponding licensed region; and

displaying the podcast in response to determining that the receiver device is located within the corresponding licensed region.

69. The system of claim 68, wherein the server processor is configured with processor-executable instructions to perform operations further comprising:

monitoring content usage reports to determine OTT television content with low user satisfaction, and

wherein the server processor is configured with processor-executable instructions to perform operations such that sending the OTT television content to the receiver device as a podcast comprises sending the OTT television content to the receiver device as a podcast in response to determining that the OTT television content is OTT television content with low user satisfaction.

70. The system of claim 68, wherein the server processor is configured with processor-executable instructions to perform operations further comprising:

monitoring content usage reports to determine OTT television content with high user interest, and

wherein the server processor is configured with processor-executable instructions to perform operations such that sending the OTT television content to the receiver device as a podcast comprises sending the OTT television content to the receiver device as a podcast in response to determining that the OTT television content is OTT television content with high user interest.

71. The system of claim 68, wherein the receiver device processor is configured with processor-executable instructions to perform operations further comprising:

comparing a location history log of the receiver device to any podcasts stored at the receiver device; and

deleting podcasts which do not correspond to recurring entries on the location history log.

72. The system of claim 68, wherein the receiver device processor is configured with processor-executable instructions to perform operations further comprising:

generating a view history report including a DMA identifier of the corresponding licensed region upon displaying the podcast; and

sending the view history report to the server via the first network interface.

73. A server, comprising:

a network interface configured to communicate with a communication network; and

a processor coupled to the network interface, wherein the processor is configured with processor-executable instructions to perform operations comprising;

setting an availability time for Over the Top (“

OTT”

) television content media segments that is the same at two or more broadcast servers associated with adjacent Designated Market Areas (“

DMAs”

);

sending a Media Presentation Description (“

MPD”

) to a receiver device via the network interface, the MPD including the availability time; and

sending the OTT television content to the receiver device in a Dynamic Adaptive Streaming Over HTTP (“

DASH”

) format via the network interface.

74. A server, comprising:

a network interface configured to communicate with a communication network; and

a processor coupled to the network interface, wherein the processor is configured with processor-executable instructions to perform operations comprising;

sending Over the Top (“

OTT”

) television content to a receiver device in a Dynamic Adaptive Streaming Over HTTP (“

DASH”

) format via the network interface; and

signaling to the receiver device a playout time for any segment of the OTT television content that is no earlier than a latest availability time for that segment among all Media Presentation Descriptions (“

MPDs”

) in a Designated Market Area (“

DMA”

).

75. A server, comprising:

a network interface configured to communicate with a communication network; and

a processor coupled to the network interface, wherein the processor is configured with processor-executable instructions to perform operations comprising;

receiving a first programming request from a receiver device corresponding to a first Designated Market Area (“

DMA”

) via the network interface;

providing a first Over the Top (“

OTT”

) television content to the receiver device via a first Multicast-Broadcast Single Frequency Network (“

MBSFN”

) via the network interface;

receiving a second programming request from the receiver device corresponding to a second DMA via the network interface;

providing a second OTT television content to the receiver device via a second MBSFN via the network interface;

determining whether the first OTT television content and the second OTT television content are the same OTT television content; and

merging the first MBSFN and the second MBSFN into a single MBSFN in response to determining that the first OTT television content and the OTT second television content are the same OTT television content.

76. The server of claim 75, wherein the processor is configured with processor-executable instructions such that determining whether the first OTT television content and the second OTT television content are the same OTT television content comprises inspecting packets of the first OTT television content and the second OTT television content.

77. The server of claim 75, wherein the processor is configured with processor-executable instructions such that determining whether the first OTT television content and the OTT second television content are the same OTT television content comprises comparing the source uniform resource locator (“

URL”

) for the first OTT television content to the URL for the second OTT television content.

78. A server, comprising:

a network interface configured to communicate with a communication network; and

a processor coupled to the network interface, wherein the processor is configured with processor-executable instructions to perform operations comprising;

receiving a first programming schedule for a first Designated Market Area (“

DMA”

);

receiving a second programming schedule for a second DMA;

determining a period of time when programming scheduled for the first DMA and the second DMA is the same based at least in part on the received first and second programming schedules;

creating a combined Multicast-Broadcast Single Frequency Network (“

MBSFN”

) encompassing both the first and the second DMA during the determined period of time;

receiving, via the network interface, a first report from a first receiver device in the first DMA during the determined period of time, the first report including an indication of an Over the Top (“

OTT”

) television content received by the first receiver device during the determined period of time;

receiving, via the network interface, a second report from a second receiver device in the second DMA during the determined period of time, the second report including an indication of an OTT television content received by the second receiver device during the determined period of time;

determining whether the indication of the OTT television content in the first report is the same as the indication of the OTT television content in the second report; and

splitting the combined MBSFN into a first MBSFN corresponding to the first DMA and a second MBSFN corresponding to the second DMA in response to determining that the indication of the OTT television content in the first report is not the same as the indication of the OTT television content in the second report.

79. The server of claim 78, wherein the processor is configured with processor-executable instructions to perform operations such that determining whether the indication of the OTT television content in the first report is the same as the indication of the OTT television content in the second report comprises comparing the source uniform resource locator (“

URL”

) for the first OTT television content to the URL for the second OTT television content.

80. The server of claim 78, wherein the processor is configured with processor-executable instructions to perform operations such that determining whether the indication of the OTT television content in the first report is the same as the indication of the OTT television content in the second report comprises comparing a content ID in the first report to a content ID in the second report.

81. The server of claim 78, wherein the processor is configured with processor-executable instructions to perform operations further comprising:

sending via the network interface, after receiving the first report and the second report, a shut off message to any receiver devices in the first DMA and second DMA, the shut off message including an indication for receiver devices to stop sending reports for a period of time.

82. A server, comprising:

a network interface configured to communicate with a communication network; and

a processor coupled to the network interface, wherein the processor is configured with processor-executable instructions to perform operations comprising;

receiving a subscription notification message from a receiver device via the network interface, the subscription notification message including an indication of a podcast requested by the receiver device;

determining whether the receiver device is an evolved Multimedia Broadcast Multicast Service (“

eMBMS”

) subscriber device based at least in part on the subscription notification message;

scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device;

generating an eMBMS schedule identifying a time at which the requested podcast will be broadcast via the eMBMS broadcast;

providing the eMBMS schedule to the receiver device via the network interface; and

broadcasting the podcast via an eMBMS network.

83. The server of claim 82, wherein the processor is configured with processor-executable instructions to perform operations such that the subscription notification message is sent in response to a user subscription to a future podcast.

84. The server of claim 83, wherein the processor is configured with processor-executable instructions to perform operations such that the user subscription to a future podcast is a user subscription to an RSS feed or an ATOM feed.

85. The server of claim 83, wherein the processor is configured with processor-executable instructions to perform operations such that the future podcast is a syndicated podcast,

wherein the processor is configured with processor-executable instructions to perform operations further comprising:

monitoring content usage reports for the syndicated podcast to determine a usage level for the syndicated podcast; and

discontinuing broadcast delivery of the syndicated podcast upon determining that the usage level is below a minimum usage level.

86. The server of claim 82, wherein the processor is configured with processor-executable instructions to perform operations such that the subscription notification message further includes a user identification, receiver device identification, and location information.

87. The server of claim 86, wherein the processor is configured with processor-executable instructions to perform operations further comprising assigning view credit for the requested podcast based at least in part on the location information upon receiving the subscription notification in the server.

88. The server of claim 82, wherein the processor is configured with processor-executable instructions to perform operations further comprising:

determining an IP address associated with the subscription notification message;

determining a probable location of the receiver device based at least in part on the IP address; and

determining whether the probable location of the receiver device corresponds to a Designated Market Area (“

DMA”

) in which eMBMS broadcasts of the requested podcast are licensed, and

wherein the processor is configured with processor-executable instructions to perform operations such that scheduling the requested podcast for an eMBMS broadcast upon determining the receiver device is an eMBMS subscriber device further comprises scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device and determining that the probable location of the receiver device corresponds to a DMA in which eMBMS broadcasts of the requested podcast are licensed.

89. The server of claim 82, wherein the processor is configured with processor-executable instructions to perform operations such that determining whether the receiver device is an evolved Multimedia Broadcast Multicast Service (“

eMBMS”

) subscriber device based at least in part on the subscription notification message further comprises determining whether the receiver device is an eMBMS subscriber device and a user associated with the receiver device is an existing eMBMS subscriber based at least in part on the subscription notification message.

90. The server of claim 82, wherein the processor is configured with processor-executable instructions to perform operations further comprising:

determining a location indication associated with the subscription notification message;

determining a probable location of the receiver device based at least in part on the location indication; and

determining whether the probable location of the receiver device corresponds to a Designated Market Area (“

DMA”

) in which eMBMS broadcasts of the requested podcast are licensed,

wherein the processor is configured with processor-executable instructions to perform operations such that scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device further comprises scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device and determining that the probable location of the receiver device corresponds to a DMA in which eMBMS broadcasts of the requested podcast are licensed.

91. The server of claim 90, wherein the processor is configured with processor-executable instructions to perform operations such that the location indication is one of a receiver device DMA designation, a receiver device latitude and longitude, a cell ID, and a Wi-Fi access point SSID.

92. A system, comprising:

a receiver device, comprising;

a first network interface configured to communicate with a communication network; and

a receiver device processor coupled to the first network interface; and

a server, comprising;

a second network interface configured to communicate with the communication network; and

a server processor coupled to the second network interface, wherein the server processor is configured with processor-executable instructions to perform operations comprising;

receiving a subscription notification message from the receiver device via the second network interface, the subscription notification message including an indication of a podcast requested by the receiver device;

determining whether the receiver device is an evolved Multimedia Broadcast Multicast Service (“

eMBMS”

) subscriber device based at least in part on the subscription notification message;

scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device;

generating an eMBMS schedule identifying a time at which the requested podcast will be broadcast via the eMBMS broadcast;

providing the eMBMS schedule to the receiver device via the second network interface;

sending a subscription notification response to the receiver device via the second network interface indicating that the requested podcast is scheduled for eMBMS broadcast and

broadcasting the podcast via an eMBMS network,

wherein the receiver device processor is configured with processor-executable instructions to perform operations comprising;

receiving the eMBMS schedule via the first network interface;

automatically subscribing the receiver device to the requested podcast in response to receiving the subscription notification response in the receiver device;

receiving the podcast via the first network interface; and

playing the podcast.

93. The system of claim 92, wherein the receiver device processor is configured with processor-executable instructions to perform operations further comprising:

determining a location of the receiver device upon playing the podcast in the receiver device;

generating a view history report including the location of the receiver device upon playing the podcast; and

sending the view history report to the server via the first network interface, and

wherein the server processor is configured with processor-executable instructions to perform operations further comprising;

receiving the view history report via the second network interface; and

assigning view credit for the podcast based at least in part on the location of the receiver device upon playing the podcast.

94. A non-transitory server readable medium having stored thereon server-executable instructions configured to cause a server to perform operations comprising:

broadcasting Over the Top (“

OTT”

) television content to one or more of receiver devices;

determining a network traffic level for the OTT television content in a Designated Market Area (“

DMA”

);

determining whether the network traffic level exceeds a traffic level threshold; and

switching to evolved Multimedia Broadcast Multicast Service (“

eMBMS”

) for the delivery of the OTT television content in response to determining that the network traffic level exceeds the traffic level threshold.

95. The non-transitory server readable medium of claim 94, wherein the stored server-executable instructions are configured to cause a server to perform operations further comprising:

determining the Multicast/Broadcast Single Frequency Networks (“

MBSFNs”

) to turn on based at least in part on a distribution of the one or more receiver devices within the DMA.

96. The non-transitory server readable medium of claim 94, wherein the stored server-executable instructions are configured to cause a server to perform operations further comprising:

determining the Multicast/Broadcast Single Frequency Networks (“

MBSFNs”

) to turn on based at least in part on a list of MBSFNs associated with the DMA.

97. The non-transitory server readable medium of claim 94, wherein the stored server-executable instructions are configured to cause a server to perform operations such that broadcasting the OTT television content to the one or more receiver devices further comprise broadcasting a unique ID associated with the broadcaster of the OTT television content.

98. The non-transitory server readable medium of claim 97, wherein the stored server-executable instructions are configured to cause a server to perform operations such that the unique ID is the broadcaster'"'"'s Federal Communications Commission (“

FCC”

) ID.

99. A non-transitory server readable medium having stored thereon server-executable instructions configured to cause a server to perform operations comprising:

setting an availability time for Over the Top (“

OTT”

) television content media segments that is the same at two or more broadcast servers associated with adjacent Designated Market Areas (“

DMAs”

);

sending a Media Presentation Description (“

MPD”

) to a receiver device via the network interface, the MPD including the availability time; and

sending the OTT television content to the receiver device in a Dynamic Adaptive Streaming Over HTTP (“

DASH”

) format.

100. A non-transitory server readable medium having stored thereon server-executable instructions configured to cause a server to perform operations comprising:

sending Over the Top (“

OTT”

) television content to a receiver device in a Dynamic Adaptive Streaming Over HTTP (“

DASH”

) format; and

signaling to the receiver device a playout time for any segment of the OTT television content that is no earlier than a latest availability time for that segment among all Media Presentation Descriptions (“

MPDs”

) in a Designated Market Area (“

DMA”

).

101. A non-transitory server readable medium having stored thereon server-executable instructions configured to cause a server to perform operations comprising:

receiving a first programming request from a receiver device corresponding to a first Designated Market Area (“

DMA”

) via the network interface;

providing a first Over the Top (“

OTT”

) television content to the receiver device via a first Multicast-Broadcast Single Frequency Network (“

MBSFN”

);

receiving a second programming request from the receiver device corresponding to a second DMA;

providing a second OTT television content to the receiver device via a second MBSFN;

determining whether the first OTT television content and the second OTT television content are the same OTT television content; and

merging the first MBSFN and the second MBSFN into a single MBSFN in response to determining that the first OTT television content and the OTT second television content are the same OTT television content.

102. The non-transitory server readable medium of claim 101, wherein the stored server-executable instructions are configured to cause a server to perform operations such that determining whether the first OTT television content and the second OTT television content are the same OTT television content comprises inspecting packets of the first OTT television content and the second OTT television content.

103. The non-transitory server readable medium of claim 101, wherein the stored server-executable instructions are configured to cause a server to perform operations such that determining whether the first OTT television content and the OTT second television content are the same OTT television content comprises comparing the source uniform resource locator (“

URL”

) for the first OTT television content to the URL for the second OTT television content.

104. A non-transitory server readable medium having stored thereon server-executable instructions configured to cause a server to perform operations comprising:

receiving a first programming schedule for a first Designated Market Area (“

DMA”

);

receiving a second programming schedule for a second DMA;

determining a period of time when programming scheduled for the first DMA and the second DMA is the same based at least in part on the received first and second programming schedules;

creating a combined Multicast-Broadcast Single Frequency Network (“

MBSFN”

) encompassing both the first and the second DMA during the determined period of time;

receiving a first report from a first receiver device in the first DMA during the determined period of time, the first report including an indication of an Over the Top (“

OTT”

) television content received by the first receiver device during the determined period of time;

receiving a second report from a second receiver device in the second DMA during the determined period of time, the second report including an indication of an OTT television content received by the second receiver device during the determined period of time;

determining whether the indication of the OTT television content in the first report is the same as the indication of the OTT television content in the second report; and

splitting the combined MBSFN into a first MBSFN corresponding to the first DMA and a second MBSFN corresponding to the second DMA in response to determining that the indication of the OTT television content in the first report is not the same as the indication of the OTT television content in the second report.

105. The non-transitory server readable medium of claim 104, wherein the stored server-executable instructions are configured to cause a server to perform operations such that determining whether the indication of the OTT television content in the first report is the same as the indication of the OTT television content in the second report comprises comparing the source uniform resource locator (“

URL”

) for the first OTT television content to the URL for the second OTT television content.

106. The non-transitory server readable medium of claim 104, wherein the stored server-executable instructions are configured to cause a server to perform operations such that determining whether the indication of the OTT television content in the first report is the same as the indication of the OTT television content in the second report comprises comparing a content ID in the first report to a content ID in the second report.

107. The non-transitory server readable medium of claim 104, wherein the stored server-executable instructions are configured to cause a server to perform operations further comprising:

sending, after receiving the first report and the second report, a shut off message to any receiver devices in the first DMA and second DMA, the shut off message including an indication for receiver devices to stop sending reports for a period of time.

108. A non-transitory server readable medium having stored thereon server-executable instructions configured to cause a server to perform operations comprising:

receiving a subscription notification message from a receiver device, the subscription notification message including an indication of a podcast requested by the receiver device;

determining whether the receiver device is an evolved Multimedia Broadcast Multicast Service (“

eMBMS”

) subscriber device based at least in part on the subscription notification message;

scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device;

generating an eMBMS schedule identifying a time at which the requested podcast will be broadcast via the eMBMS broadcast;

providing the eMBMS schedule to the receiver device; and

broadcasting the podcast via an eMBMS network.

109. The non-transitory server readable medium of claim 108, wherein the stored server-executable instructions are configured to cause a server to perform operations such that the subscription notification message is sent in response to a user subscription to a future podcast.

110. The non-transitory server readable medium of claim 109, wherein the stored server-executable instructions are configured to cause a server to perform operations such that the user subscription to a future podcast is a user subscription to an RSS feed or an ATOM feed.

111. The non-transitory server readable medium of claim 109, wherein the stored server-executable instructions are configured to cause a server to perform operations such that the future podcast is a syndicated podcast,

wherein the stored server-executable instructions are configured to cause a server to perform operations further comprising:

monitoring content usage reports for the syndicated podcast to determine a usage level for the syndicated podcast; and

discontinuing broadcast delivery of the syndicated podcast upon determining that the usage level is below a minimum usage level.

112. The non-transitory server readable medium of claim 108, wherein the stored server-executable instructions are configured to cause a server to perform operations such that the subscription notification message further includes a user identification, receiver device identification, and location information.

113. The non-transitory server readable medium of claim 112, wherein the stored server-executable instructions are configured to cause a server to perform operations further comprising assigning view credit for the requested podcast based at least in part on the location information upon receiving the subscription notification in the server.

114. The non-transitory server readable medium of claim 108, wherein the stored server-executable instructions are configured to cause a server to perform operations further comprising:

determining an IP address associated with the subscription notification message;

determining a probable location of the receiver device based at least in part on the IP address; and

determining whether the probable location of the receiver device corresponds to a Designated Market Area (“

DMA”

) in which eMBMS broadcasts of the requested podcast are licensed, and

wherein the stored server-executable instructions are configured to cause a server to perform operations such that scheduling the requested podcast for an eMBMS broadcast upon determining the receiver device is an eMBMS subscriber device further comprises scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device and determining that the probable location of the receiver device corresponds to a DMA in which eMBMS broadcasts of the requested podcast are licensed.

115. The non-transitory server readable medium of claim 108, wherein the stored server-executable instructions are configured to cause a server to perform operations such that determining whether the receiver device is an evolved Multimedia Broadcast Multicast Service (“

eMBMS”

) subscriber device based at least in part on the subscription notification message further comprises determining whether the receiver device is an eMBMS subscriber device and a user associated with the receiver device is an existing eMBMS subscriber based at least in part on the subscription notification message.

116. The non-transitory server readable medium of claim 108, wherein the stored server-executable instructions are configured to cause a server to perform operations further comprising:

determining a location indication associated with the subscription notification message;

determining a probable location of the receiver device based at least in part on the location indication; and

determining whether the probable location of the receiver device corresponds to a Designated Market Area (“

DMA”

) in which eMBMS broadcasts of the requested podcast are licensed,

wherein the stored server-executable instructions are configured to cause a server to perform operations such that scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device further comprises scheduling the requested podcast for an eMBMS broadcast upon determining that the receiver device is an eMBMS subscriber device and determining that the probable location of the receiver device corresponds to a DMA in which eMBMS broadcasts of the requested podcast are licensed.

117. The non-transitory server readable medium of claim 116, wherein the stored server-executable instructions are configured to cause a server to perform operations such that the location indication is one of a receiver device DMA designation, a receiver device latitude and longitude, a cell ID, and a Wi-Fi access point SSID.