Patent US2258170A successfully refreshed from Google Patents.
Patent US3636706A successfully refreshed from Google Patents.
Patent US6438618B1 successfully refreshed from Google Patents.
← Back to Patent Explorer
US6438618B1 Expired / Lapsed US ⏱️ 0.0 years remaining

Method and device for filtering events in an event notification service

Assignee: Sony Corp of America
•
Filing: 1998-12-16
•
Granted: 2002-08-20
•
Expires: 2018-12-16
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

Abstract An event notification service in a Component Object Model (COM) system employs a server called an event provider service that operates as a separate layer between an event source and a client called an event subscriber. The notification service also includes event filtering so that an event subscriber only receives events that meet the conditions set by an event filter. A persistent notifier moniker allows an event subscriber client to receive events even if the client is not currently active because the moniker activates the client executing upon receipt of an event.

Inventors

  • 👤 Victor B. Lortz
  • 👤 Jonathan G. Ritchie

Bibliographic Details

Application Number —
Jurisdiction US
Data Source google_patents
Last Synchronized 2026-10-29 16:14
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/54; G06F9/542

Claims Analysis

Total Claims: 23
Claim 1
Independent Claim 88 words
An event notification system, constructed in a Component Object Model framework, to pass an event from an event source to an event subscriber, comprising: an event filter to represent a condition under which the event subscriber is to receive the event and; an event provider service for comparing the event to the event filter, wherein: the event source passes the event to the event provider service and; the event provider service passes the event to the event subscriber only if the condition of the event filter is met.
Claim 2
Dependent Claim 88 words
An event notification system, constructed in a Component Object Model framework, to pass an event from an event source to an event subscriber, comprising: an event filter to represent a condition under which the event subscriber is to receive the event and; an event provider service for comparing the event to the event filter, wherein: the event source passes the event to the event provider service and; the event provider service passes the event to the event subscriber only if the condition of the event filter is met.
Claim 3
Dependent Claim 18 words
The event notification system of claim 1 , wherein: the event source is in communication with a device.
Claim 4
Dependent Claim 19 words
The event notification system of claim 2 , wherein: the event source communicates with the device across a network.
Claim 5
Dependent Claim 32 words
The event notification system of claim 3 , wherein: the network comprises a home network including: at least one computer; at least one home device adapted to be controlled by a computer.
Claim 6
Dependent Claim 19 words
The event notification system of claim 1 , wherein: the event subscriber performs a function based on the event.
Claim 7
Dependent Claim 21 words
The event notification system of claim 5 wherein: the function based on the event includes changing a property of a device.
Claim 8
Dependent Claim 15 words
The event notification system of claim 1 , wherein: the filter includes a filter string.
Claim 9
Dependent Claim 17 words
The event notification system of claim 1 , wherein: the filter is expressed in a query language.
Claim 10
Dependent Claim 22 words
The event notification system of claim 1 , wherein: a syntax of the filter is compatible with a lightweight directory access protocol.
Claim 11
Dependent Claim 29 words
The event notification system of claim 1 , wherein: the event source comprises an object for passing a command to a device to control a property of the device.
Claim 12
Dependent Claim 38 words
The event notification system of claim 10 , wherein: the event source further comprises an object for receiving a message from the device, converting the message into the event, and forwarding the event to the event provider service.
Claim 13
Dependent Claim 31 words
The event notification system of claim 1 , further comprising a moniker to activate the client if the client is not currently active when the client is to receive an event.
Claim 14
Dependent Claim 23 words
The event notification system of claim 1 , wherein: the event filter is provided by the event subscriber to the event provider service.
Claim 15
Dependent Claim 17 words
The event notification system of claim 1 , wherein: the event provider service includes an event object.
Claim 16
Dependent Claim 34 words
The event notification system of claim 1 , further comprising a legacy client as an event subscriber, wherein: the event provider service passes all events received from the event source to the legacy client.
Claim 17
Independent Claim 89 words
A method for passing an event notification from an event source to an event subscriber implemented in a Component Object Model system comprising: subscribing the event subscriber to an event provider service; communicating a subscription filter condition to the event provider service; determining when an event is signaled from an event source; comparing the event to the subscription filter condition to determine whether the event should be passed to the event subscriber; passing the event to the event subscriber only when the condition of the event filter is met.
Claim 18
Independent Claim 89 words
A method for passing an event notification from an event source to an event subscriber implemented in a Component Object Model system comprising: subscribing the event subscriber to an event provider service; communicating a subscription filter condition to the event provider service; determining when an event is signaled from an event source; comparing the event to the subscription filter condition to determine whether the event should be passed to the event subscriber; passing the event to the event subscriber only when the condition of the event filter is met.
Claim 19
Dependent Claim 16 words
The method of claim 15 wherein: the event subscriber performs a function based on the event.
Claim 20
Dependent Claim 13 words
The method of claim 15 wherein: the event source comprises a control object.
Claim 21
Dependent Claim 28 words
The method of claim 15 further comprising the step of: activating the client if the client is not currently active when the client is to receive an event.
Claim 22
Dependent Claim 111 words
A storage medium including a set of instructions, said set of instructions capable of being executed by a processor to implement a method for event notification of an event subscriber by an event source implemented in a Component Object Model system, the instructions to: subscribe the event subscriber to an event provider service; communicate a subscription filter condition to the event provider service; determine that an event should be signaled from an event source; compare the event to the subscription filter condition to determine whether the event should be passed to the event subscriber; pass the event to the event subscriber, only if the condition of the event filter is met.
Claim 23
Dependent Claim 111 words
A storage medium including a set of instructions, said set of instructions capable of being executed by a processor to implement a method for event notification of an event subscriber by an event source implemented in a Component Object Model system, the instructions to: subscribe the event subscriber to an event provider service; communicate a subscription filter condition to the event provider service; determine that an event should be signaled from an event source; compare the event to the subscription filter condition to determine whether the event should be passed to the event subscriber; pass the event to the event subscriber, only if the condition of the event filter is met.

References Cited (Backward Citations)

US5682532A Cited
US5881315A Cited
US5870605A Cited
US6021443A Cited
US5857190A Cited
US6029092A Cited
US6038542A Cited

USPTO Annuity & Maintenance Windows

Annuity Stage Window Opens Payment Deadline Surcharge Period Until Estimated Fee Status
3.5 Years (Year 4) 2005-08-19 2006-02-18 2006-08-20 $2000.00 Window Closed / Lapsed
7.5 Years (Year 8) 2009-08-19 2010-02-18 2010-08-20 $3760.00 Window Closed / Lapsed
11.5 Years (Year 12) 2013-08-19 2014-02-18 2014-08-20 $7700.00 Window Closed / Lapsed

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag