Event booking mechanism
First Claim
1. A system for booking events and initiating actions corresponding to said events, said system comprising:
- an event broker configured to register a plurality of event bookings in response to requests from one or more clients, wherein each said event booking identifies an event which may occur in the future and an action to be taken should the identified event occur;
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;
wherein each of said event broker, said clients, said event managers, and said action handlers comprise distinct functional entities;
wherein a first event manager of said one or more event managers is configured to notify said event broker of a first event which corresponds to a first event booking, in response to detecting said first event;
wherein the event broker is configured to notify a first action handler which corresponds to the first event booking, in response to receiving notification from the first event manager of the detected first event; and
wherein the first action handler is configured to initiate a first action, in response to receiving notification from the event broker of the detected first event;
wherein a first request of the requests for an event booking identifies a first event which may occur in the future and a first action to be taken upon occurrence of said first event, wherein the first request includes a description of the first event using a syntax which is unintelligible to the event broker, but which is intelligible to a first event manager of the event managers, wherein subsequent to receiving notice of said event booking, said first event manager is configured to determine whether said event booking will be accepted by said first event manager, and provide a positive acknowledgement to said event broker in response to determining said event booking is accepted.
1 Assignment
0 Petitions
Accused Products
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. The event broker is configured to work in conjunction with a plurality of event managers which can detect different types of events and a plurality of action handlers which can initiate different types of actions. The event broker is configured to resolve resource conflicts between actions for which the corresponding events have been detected. The event broker is further configured to control access to event bookings through a security system which can use privileges or credentials to identify clients which are authorized to read, modify, delete or otherwise access information contained in the event bookings.
-
Citations
27 Claims
-
1. A system for booking events and initiating actions corresponding to said events, said system comprising:
-
an event broker configured to register a plurality of event bookings in response to requests from one or more clients, wherein each said event booking identifies an event which may occur in the future and an action to be taken should the identified event occur; 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; wherein each of said event broker, said clients, said event managers, and said action handlers comprise distinct functional entities; wherein a first event manager of said one or more event managers is configured to notify said event broker of a first event which corresponds to a first event booking, in response to detecting said first event; wherein the event broker is configured to notify a first action handler which corresponds to the first event booking, in response to receiving notification from the first event manager of the detected first event; and wherein the first action handler is configured to initiate a first action, in response to receiving notification from the event broker of the detected first event; wherein a first request of the requests for an event booking identifies a first event which may occur in the future and a first action to be taken upon occurrence of said first event, wherein the first request includes a description of the first event using a syntax which is unintelligible to the event broker, but which is intelligible to a first event manager of the event managers, wherein subsequent to receiving notice of said event booking, said first event manager is configured to determine whether said event booking will be accepted by said first event manager, and provide a positive acknowledgement to said event broker in response to determining said event booking is accepted. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
-
14. A method for brokering and managing event bookings, said method comprising:
-
receiving a request from a client for an event booking at an event broker, wherein said request identifies a first event which may occur in the future and a first action to be taken upon occurrence of said first event; registering said event booking request, wherein said event broker notifies a first event manager corresponding to said first event, and notifies a first action handler corresponding to said first action, wherein said event broker, said client, said first event manager, and said first action handler comprise distinct functional entities; detecting said first event by said first event manager; said first event manager notifying said event broker of said detection of said first event; said event broker providing notification to said first action handler of said detection of said first event; and initiating said first action by said first action handler in response to detecting said notification from said event broker; wherein the request includes a description of the first event using a syntax which is unintelligible to the event broker, but which is intelligible to the first event manager, wherein subsequent to receiving notice of said event booking from said mechanism, said first event manager is configured to determine whether said event booking will be accepted by said first event manager, and provide a positive acknowledgement to said event broker in response to determining said event booking is accepted. - View Dependent Claims (15, 16, 17, 18, 19, 20)
-
-
21. A device comprising:
-
a signal receiver configured to receive a broadcast signal; a first event manager, wherein said first event manager is configured to detect particular types of events; a first action handler, wherein said first action handler is configured to initiate particular types of actions; and an event broker mechanism, wherein said mechanism is configured to; receive a request for an event booking from a client, wherein said request identifies a first event which may occur in the future and a first action to be taken upon occurrence of said first event; register said event booking request, wherein said event broker notifies said first event manager and said first action handler; wherein each of said event broker mechanism, said client, said first event manager, and said first action handler comprise distinct functional entities; wherein said first event manager is configured to detect said first event and notify said event broker of said detection of said first event; and wherein said first action handler is configured to initiate said first action in response to receiving notice from said event broker that said first event has been detected; wherein the request includes a description of the first event using a syntax which is unintelligible to the event broker mechanism, but which is intelligible to the first event manager, wherein subsequent to receiving notice of said event booking from said mechanism, said first event manager is configured to determine whether said event booking will be accepted by said first event manager, and provide a positive acknowledgement to said mechanism in response to determining said event booking is accepted. - View Dependent Claims (22, 23, 24, 25, 26, 27)
-
Specification