EVENT BOOKING MECHANISM

• US 20120090012A1
• Filed: 10/03/2011
• Published: 04/12/2012
• Est. Priority Date: 11/09/1999
• Status: Active Grant

• Current Assignee: OpenTV, Inc. (Kudelski SA)
• Original Assignee: OpenTV, Inc. (Kudelski SA)
• Inventors: Pierre, Ludovic, Godin, Thierry, Kalluri, Rama, Nguyen, Jino
• Granted Patent: US 9,038,118 B2
• Time in Patent Office: Days
• US Class Current: 725/93
• 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/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/25808 Management of client data terminal profiles in network data switching protocols H04L67/303
• CPC Class Codes: H04N 21/25866 Management of end-user data customer care in data networks H04L41/5077
• 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/4431 characterized by the use of Application Program Interface [API] libraries
• CPC Class Codes: H04N 21/47 End-user applications
• CPC Class Codes: H04N 21/8545 for generating interactive applications

Abstract

A mechanism for booking events comprising an event broker, one or more event managers and one or more action handlers. In one embodiment, the event broker is configured to register a plurality of event bookings, each of which identifies an event and a corresponding action. For each event booking, the event broker notifies an event manager which is configured to detect the type of event identified in the event booking. When the event manager detects the identified event, it notifies the event broker. The broker then notifies an action handler which is configured to initiate the type of action identified in the event booking. The action handler then initiates the action. If the event booking is non-recurring and the action is complete, the event booking is unregistered by the event broker.

Claims

1. A system for booking events and initiating actions corresponding to said events, said system comprising:

an event broker, wherein said event broker is configured to register a plurality of event bookings in response to requests from one or more clients, wherein each said event booking identifies a corresponding event and a corresponding action;

one or more event managers, wherein each of said one or more event managers is configured to detect particular types of events; and

one or more action handlers, wherein each of said one or more action handlers is configured to initiate particular types of actions in response to detecting a corresponding event.

2. The system of claim 1 wherein for each said event booking:

said event broker is configured to notify one of said event managers which is configured to detect said event identified in said each event booking,

said one of said event managers is configured to notify said event broker of said event identified in said each event booking upon detecting said event identified in said each event booking,

said event broker is configured to notify one of said action handlers which is configured to initiate said action identified in said each event booking in response to said event being detected, and

said one of said action handlers is configured to initiate said corresponding action in response to said event broker notifying said one of said action handlers.

3. The system of claim 1 wherein said system is implemented as a framework comprising a software layer between an application layer and a driver layer.

4. The system of claim 3 wherein the framework is implemented in a receiver for a broadcast system.

5. The system of claim 1 wherein at least a portion of said events are associated with a broadcast signal.

6. The system of claim 3 wherein said event broker, said one or more event managers and said one or more action handlers comprise library extensions accessible by an operating system executing in said receiver.

7. The system of claim 1 wherein said event broker is configured to maintain said event bookings from a plurality of distinct clients.

8. The system of claim 1 wherein said events corresponding to said event bookings comprise a plurality of distinct event types.

9. The system of claim 1 wherein said actions corresponding to said event bookings comprise a plurality of distinct action types.

10. The system of claim 1 wherein each said event booking identifies an event manager configured to detect said corresponding event and an action handler configured to initiate said corresponding action.

11. The system of claim 1 wherein said event broker is configured to determine resources required by said actions and to resolve resource conflicts between said actions.

12. The system of claim 1 wherein said event broker is configured to maintain ranks corresponding to said event bookings and, if a plurality of said events have been detected, to initiate said corresponding actions in an order determined by said ranks.

13. The system of claim 1 wherein said event broker is configured to control accesses to said event bookings based on permissions associated with said accesses and said event bookings.

14. The system of claim 1 wherein each of said event bookings has a corresponding expiration time and wherein said event broker is configured to unregister ones of said event bookings which have passed said expiration time.

15. A method comprising:

registering a plurality of event bookings, wherein said plurality of event bookings are requested by a plurality of clients and wherein each said event booking describes a corresponding event and a corresponding action;

detecting one of said events; and

initiating one of said actions corresponding to said detected one of said events in response to detecting said detected one of said events.

16. The method of claim 15 wherein said plurality of event bookings are registered in a central location.

17. The method of claim 15 wherein said events corresponding to said plurality of event bookings comprise a plurality of event types, wherein said event types are detected by a plurality of event managers.

18. The method of claim 15 wherein registering one of said booking events comprises storing information identifying one of said plurality of event managers which is configured to detect said corresponding event.

19. The method of claim 15 wherein said actions corresponding to said plurality of event bookings comprise a plurality of action types, wherein said action types are initiated by a plurality of action handlers.

20. The method of claim 19 wherein registering one of said booking events comprises storing information identifying one of said plurality of action handlers which is configured to initiate said corresponding action.

21. The method of claim 20 wherein said action is selected from the group consisting of:

downloading an application;

launching an application;

launching a popup; and

notifying a running application of said one of said events.

22. A device comprising:

a signal receiver configured to receive a broadcast signal;

an event broker mechanism coupled to said signal receiver; and

a storage device coupled to said event broker mechanism and configured to store event bookings;

wherein each of said event bookings identifies a corresponding event and a corresponding action;

wherein said event broker mechanism is configured to operate as an event broker, and wherein said event broker mechanism is configured to execute one or more event managers and one or more action handlers; and

wherein said event broker mechanism is configured to register said event bookings, wherein said event managers are configured to detect said events corresponding to said event bookings and wherein said action handlers are configured to initiate said actions corresponding to said event bookings.

23. The device of claim 22 wherein said device comprises an interactive television system receiver coupled to receive said broadcast signal from a broadcast station and configured to provide an output signal to a television.

24. The device of claim 22 wherein said event broker mechanism comprises a processor executing computer software.

25. The device of claim 22 wherein said event broker mechanism comprises application specific circuitry.

26. The device of claim 22 wherein said storage device comprises memory.

27. The device of claim 22 wherein said storage device comprises non-volatile storage.