Location specific event broadcasting

• US 8,102,864 B2
• Filed: 01/30/2008
• Issued: 01/24/2012
• Est. Priority Date: 01/31/2006
• Status: Active Grant

• Current Assignee: DIRECTV, LLC (AT&T, Inc.)
• Original Assignee: Roundbox, Inc. (AT&T, Inc.)
• Inventors: Khivesara, Amit, Liu, Xiaofeng, Mataga, Peter Andrew, Slepchin, Igor, Torkelson, Cary, Valloppillil, Vinod, Villanueva, Edgar
• Primary Examiner(s): JAIN, RAJ K
• Application Number:
  US12/022,914
• Publication Number:
  US 20080137602A1
• Time in Patent Office: 1,455 Days
• Field of Search: None
• US Class Current: 370/401
• CPC Class Codes: H04L 12/1881 with schedule organisation, e.g. priority, sequence management
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation
• CPC Class Codes: H04L 47/15 in relation to multipoint traffic arrangements for broadcast or multicast in data networks H04L12/18
• CPC Class Codes: H04L 47/2475 for supporting traffic characterised by the type of applications
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 65/611 for multicast or broadcast systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• 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/90 Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
• CPC Class Codes: H04W 76/50 for emergency connections

Abstract

Applications in a broadcast environment distribute events in real-time to a large number of receivers within specified geographic locations while efficiently sharing bandwidth resources with other applications using the same broadcast network. Applications need not be aware of the other applications sharing the resources, nor of the methods, protocols, and other mechanisms used to actually broadcast the data over the broadcast medium. Server-side applications that serve data, send notifications, or distribute events to specific locations within the network use a broadcast location manager. Client applications that receive such data, notifications, or events use a client location filter to obtain events that are relevant based on the location of the device. The broadcast location manager and client location filter work together to reliably and efficiently transmit data, notifications, and events to specific locations over the broadcast network for all applications involved.

Claims

1. A method for filtering events, the method comprising:

receiving a plurality of events at a client device, wherein at least one event is associated with a location tag that identifies a physical location in a network, the physical location being smaller than an area served by the network;

determining a location of the client device;

forwarding the event to an application in the client device if the location of the client device is within the physical location identified by the location tag;

extracting from the location tag a client topology table identifier, a version number of a client topology table, and the physical location;

determining whether a client topology table corresponding to the client topology table identifier and the version number extracted from the location tag is stored on the client device;

accessing the client topology table from the client device if the client topology table is stored on the client device; and

if the client topology table is not stored on the client device, downloading a current version of the client topology table from a broadcast location manager.

2. The method of claim 1 further comprising:

determining whether the location tag is present in a received event; and

forwarding the received event to an application in the client device if the location tag is not present in the received event or if the location tag identifies all locations in the network.

3. The method of claim 1 further comprising:

receiving the client topology table, wherein the client topology table corresponds to the location of the client device.

4. The method of claim 3 further comprising:

determining a location change of the client device, wherein the client topology table does not correspond to a current location of the client device; and

obtaining another client topology table that corresponds to the current location of the client device.

5. The method of claim 3 further comprising:

forwarding the client topology table and the location tag to the application in the client device.

6. The method of claim 1 wherein the physical location is served by a plurality of networks.

7. The method of claim 1 wherein the physical location comprises a plurality of non-contiguous locations served by at least one network.

8. A method for broadcasting events to fine-grained locations in a network, the method comprising:

identifying a physical location in a network, wherein the physical location is smaller than an area served by the network;

mapping the physical location to a network address;

identifying a fine-grained location within the physical location, wherein an event is to be distributed to client devices within the fine-grained location;

tagging events to be distributed to the fine-grained location with a location restriction such that at least one event is associated with a location tag, the location tag including a client topology table identifier, a version number of a client topology table, and the fine-grained location;

broadcasting the events to the physical location via a broadcast distribution network;

filtering the events based on the location restriction such that only client devices located within the fine-grained location process the events; and

if the client topology table corresponding to the client topology table identifier and the version number of the location tag is not stored at a client device, providing a current version of the client topology table to the client device for access by the client device.

9. The method of claim 8 further comprising:

submitting the events that are to be transmitted to the same physical location to a carousel, wherein each event may be transmitted from the carousel at least once.

10. The method of claim 9 further comprising:

allocating bandwidth to the events on the same carousel based on an aggregate bandwidth available to the corresponding physical location.

11. A system for broadcasting events to fine-grained locations in a network, the system comprising:

a broadcast location manager installed on a server, the broadcast location manager comprising;

a policy manager configured to define a physical location in a network to which events are broadcast, wherein the physical location is smaller than an area served by the network, the policy manager being further configured to define a fine-grained location within the physical location, wherein an event is to be distributed to client devices within the fine-grained location;

a topology manager configured to generate a client topology table which includes a mapping of location tags to physical locations in the network, wherein each physical location is identified by a network address;

an intake manager configured to provide an event to be distributed to the fine-grained location with a location tag; and

a broadcast manager configured to broadcast events to the physical location; and

a client location filter installed on a client device and coupled to the broadcast location manager by a broadcast distribution network, the client location filter comprising;

a client topology table manager configured to, at least;

extract from the location tag a client topology table identifier, a version number of the client topology table, and the fine-grained location;

determine whether a copy of the client topology table corresponding to the client topology table identifier and the version number extracted from the location tag is stored on the client device;

access the copy of the client topology table from the client device if the copy of the client topology table is stored on the client device; and

if the copy of the client topology table is not stored on the client device, downloading a current version of the client topology table from the broadcast location manager; and

an event filter configured to determine whether the client device is located in the fine-grained location based on the location tag and the client topology table;

wherein the event is forwarded to the corresponding application in the client device when the client device is located in the fine-grained area of the network.

12. The system of claim 11 wherein the broadcast location manager further comprises:

a session manager configured to create a location-specific application carousel for each physical location in the network to which events are broadcast.

13. The system of claim 12 wherein each location-specific application carousel is associated with an allocated bandwidth.

14. The system of claim 13 wherein the broadcast manager is further configured to broadcast the events to the physical location by optimizing the bandwidth allocated for the location-specific application carousels.

15. The system of claim 11 wherein the policy manager is further configured to define a bandwidth allocation policy for each physical location in the network to which events are broadcast.

16. The system of claim 15 wherein the broadcast location manager further comprises:

an event scheduler configured to manage the rate at which events are broadcast to the same physical location by allocating bandwidth for each physical location based on the corresponding bandwidth allocation policy.

17. The system of claim 11 wherein the client topology table corresponds to the location of the client device.

18. The system of claim 17 wherein the event filter is further configured to determine a location change of the client device, the client topology table not corresponding to a current location of the client device.

19. The system of claim 18 wherein the client topology manager is further configured to obtain another client topology table that corresponds to the current location of the client device.

20. A method for broadcasting events to locations in a network, the method comprising:

identifying a physical location in a network, wherein the physical location is smaller than an area served by the network;

tagging events such that at least one event is associated with a location tag, the location tag including a client topology table identifier, a version number of a client topology table, and the physical location;

mapping the physical location to a plurality of network addresses; and

broadcasting events to client devises in the physical location via a broadcast distribution network; and

if the client topology table corresponding to the client topology table identifier and the version number of the location tag is not stored at a client device, providing a current version of the client topology table to the client device for access by the client device.

21. The system of claim 20 further comprising:

tagging the events to be distributed to a fine-grained location in the physical location with a location restriction; and

filtering the events based on the location restriction such that only client devices located within the fine-grained location process the events.

22. The system of claim 20 wherein the plurality of network addresses correspond to locations in more than one network.