US6289384B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
System and method for event notification through a firewall
Assignee: Blue Yonder Group Inc
•
Filing: 1998-09-18
•
Granted: 2001-09-11
•
Expires: 2018-09-18
Abstract
Abstract A system for providing client callbacks includes a client having a client application and a client firewall operable to block a client callback to the client application from a server. The server includes a server firewall and a server workspace. The server workspace has data protected by the server firewall and a permissibility framework associating a predefined type of the data with the client application. The server workspace is operable to generate a client callback for the client application in response to the presence of the predefined data type. A server-side proxy is operable to provide the client application access to the server workspace through the server firewall. The client application is operable to connect to the server workspace via the server-side proxy to receive the client callback.
Inventors
- 👤 Mark B. Whipple
- 👤 Ranjit N. Notani
- 👤 Abhay V. Parasnis
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-24 10:13
CPC Classifications
G; G06; G06Q; G06Q10/00; G06Q10/06; G06F; G06F9/00; G06F9/06; G06F9/46; G06Q10/10
Claims Analysis
Total Claims: 48
Claim 1
Independent Claim
136 words
An event notification system, comprising: a server comprising: a server firewall operable to protect data associated with the server; a register operable to associate predefined data criteria with a client application according to a data access framework in response to a subscription request from the client application, the client application executing at a client comprising a client firewall operable to block communication of at least some events to the client application; and an event manager operable to generate an event for the client application in response to the presence of data satisfying the predefined data criteria; and a server-side proxy operable to provide the client application access to the server through the server firewall, the client application operable to connect to the server using the server-side proxy to receive the event without establishing a client-side proxy.
Claim 2
Dependent Claim
136 words
An event notification system, comprising: a server comprising: a server firewall operable to protect data associated with the server; a register operable to associate predefined data criteria with a client application according to a data access framework in response to a subscription request from the client application, the client application executing at a client comprising a client firewall operable to block communication of at least some events to the client application; and an event manager operable to generate an event for the client application in response to the presence of data satisfying the predefined data criteria; and a server-side proxy operable to provide the client application access to the server through the server firewall, the client application operable to connect to the server using the server-side proxy to receive the event without establishing a client-side proxy.
Claim 3
Dependent Claim
36 words
The system of claim 1 , wherein the client application is operable to periodically connect to the server using the server-side proxy to receive events and to disconnect from the server in the absence of events.
Claim 4
Dependent Claim
21 words
The system of claim 2 , wherein the client application is operable to communicate with the server using the HTTP protocol.
Claim 5
Dependent Claim
37 words
The system of claim 1 , wherein the client application is operable to remain connected to the server using the server-side proxy and to download data satisfying the predefined data criteria in response to a subsequent event.
Claim 6
Dependent Claim
21 words
The system of claim 4 , wherein the client application is operable to communicate with the server using the TCP/IP protocol.
Claim 7
Dependent Claim
25 words
The system of claim 1 , wherein the client application comprises an application program interface (API) for connecting to the server using the server-side proxy.
Claim 8
Dependent Claim
22 words
The system of claim 1 , wherein the data access framework comprises a permissivity framework and the event comprises a client call-back.
Claim 9
Dependent Claim
171 words
An inter-enterprise event notification system, comprising: a first enterprise computer system comprising: a first enterprise firewall operable to protect data associated with the first enterprise computer system; a register operable to associate predefined data criteria with a second enterprise application according to a data access framework in response to a subscription request from the second enterprise application, the second enterprise application executing at a second enterprise computer system comprising a second enterprise firewall operable to block communication of at least some events to the second enterprise application; and an event manager operable to generate an event for the second enterprise application in response to the presence of data satisfying the predefined data criteria; and a proxy at the first enterprise computer system operable to provide the second enterprise application access to the first enterprise computer system through the first enterprise firewall, the second enterprise application operable to connect to the first enterprise computer system using the proxy to receive the event without establishing a proxy at the second enterprise computer system.
Claim 10
Dependent Claim
171 words
An inter-enterprise event notification system, comprising: a first enterprise computer system comprising: a first enterprise firewall operable to protect data associated with the first enterprise computer system; a register operable to associate predefined data criteria with a second enterprise application according to a data access framework in response to a subscription request from the second enterprise application, the second enterprise application executing at a second enterprise computer system comprising a second enterprise firewall operable to block communication of at least some events to the second enterprise application; and an event manager operable to generate an event for the second enterprise application in response to the presence of data satisfying the predefined data criteria; and a proxy at the first enterprise computer system operable to provide the second enterprise application access to the first enterprise computer system through the first enterprise firewall, the second enterprise application operable to connect to the first enterprise computer system using the proxy to receive the event without establishing a proxy at the second enterprise computer system.
Claim 11
Dependent Claim
42 words
The system of claim 8 , wherein the second enterprise application is operable to periodically connect to the first enterprise computer system using the proxy to receive events and to disconnect from the first enterprise computer system in the absence of events.
Claim 12
Dependent Claim
40 words
The system of claim 8 , wherein the second enterprise application is operable to remain connected to the first enterprise computer system using the proxy and to download data satisfying the predefined data criteria in response to a subsequent event.
Claim 13
Dependent Claim
22 words
The system of claim 8 , wherein the first enterprise is a supplier enterprise and the second enterprise is a customer enterprise.
Claim 14
Dependent Claim
22 words
The system of claim 8 , wherein the first enterprise is a hub enterprise and the second enterprise is a spoke enterprise.
Claim 15
Dependent Claim
18 words
The system of claim 8 , wherein the first and second enterprises are members of a supply chain.
Claim 16
Dependent Claim
22 words
The system of claim 8 , wherein the data accesses framework comprises a permissivity framework and the event comprises a client call-back.
Claim 17
Dependent Claim
114 words
An event notification system, comprising: an internal firewall separating a server and a client, the internal firewall operable to block communication of at least some events from the server to a client application of the client; the server comprising a register operable to associate predefined data criteria with the client application according to a data access framework in response to a subscription request from the client application; the server further comprising an event manager operable to generate an event for the client application in response to the presence of data satisfying the predefined data criteria; and the client application operable to connect to the server to receive the event without establishing a client-side proxy.
Claim 18
Dependent Claim
114 words
An event notification system, comprising: an internal firewall separating a server and a client, the internal firewall operable to block communication of at least some events from the server to a client application of the client; the server comprising a register operable to associate predefined data criteria with the client application according to a data access framework in response to a subscription request from the client application; the server further comprising an event manager operable to generate an event for the client application in response to the presence of data satisfying the predefined data criteria; and the client application operable to connect to the server to receive the event without establishing a client-side proxy.
Claim 19
Dependent Claim
32 words
The system of claim 15 , wherein the client application is operable to periodically connect to the server to receive events and to disconnect from the server in the absence of events.
Claim 20
Dependent Claim
21 words
The system of claim 16 , wherein the client application is operable to communicate with the server using the HTTP protocol.
Claim 21
Dependent Claim
34 words
The method of claim 15 , wherein the client application is operable to remain connected to the server and to download the data satisfying the predefined data criteria in response to a subsequent event.
Claim 22
Dependent Claim
21 words
The system of claim 18 , wherein the client application is operable to communicate with the server using the TCP/IP protocol.
Claim 23
Dependent Claim
21 words
The system of claim 15 , wherein the client application comprises an application program interface (API) for connecting to the server.
Claim 24
Dependent Claim
22 words
The system of claim 15 , wherein the data access framework comprises a permissivity framework and the event comprises a client call-back.
Claim 25
Dependent Claim
138 words
An inter-enterprise event notification system, comprising: an internal firewall separating a first enterprise computer system from a second enterprise computer system, the internal firewall operable to block communication of at least some events from the first enterprise computer system to an application of the second enterprise computer system; the first enterprise computer system operable to associate predefined data criteria with the second enterprise application according to a data access framework and in response to a subscription request from the second enterprise application; the first enterprise computer system further operable to generate an event for the second enterprise application in response to the presence of data satisfying the predefined data criteria; and the second enterprise application operable to connect to the first enterprise computer system to receive the event without establishing a proxy at the second enterprise computer system.
Claim 26
Dependent Claim
138 words
An inter-enterprise event notification system, comprising: an internal firewall separating a first enterprise computer system from a second enterprise computer system, the internal firewall operable to block communication of at least some events from the first enterprise computer system to an application of the second enterprise computer system; the first enterprise computer system operable to associate predefined data criteria with the second enterprise application according to a data access framework and in response to a subscription request from the second enterprise application; the first enterprise computer system further operable to generate an event for the second enterprise application in response to the presence of data satisfying the predefined data criteria; and the second enterprise application operable to connect to the first enterprise computer system to receive the event without establishing a proxy at the second enterprise computer system.
Claim 27
Dependent Claim
40 words
The system of claim 22 , wherein the second enterprise application is further operable to periodically connect to the first enterprise computer system to receive events and to disconnect from the first enterprise computer system in the absence of events.
Claim 28
Dependent Claim
36 words
The system of claim 22 , wherein the second enterprise application is operable to remain connected to the first enterprise computer system and to download data satisfying the predefined data criteria in response to an event.
Claim 29
Dependent Claim
22 words
The system of claim 22 , wherein the first enterprise is a supplier enterprise and the second enterprise is a customer enterprise.
Claim 30
Dependent Claim
22 words
The system of claim 22 , wherein the first enterprise is a hub enterprise and the second enterprise is a spoke enterprise.
Claim 31
Dependent Claim
18 words
The system of claim 22 , wherein the first and second enterprises are members of a supply chain.
Claim 32
Dependent Claim
22 words
The system of claim 22 , wherein the data access framework comprises a permissivity framework and the event comprises a client call-back.
Claim 33
Independent Claim
102 words
A method of providing event notification through a firewall operable to block communication of at least some events from a server to a client, comprising: according to a data access framework, associating predefined data criteria at the server with a client application of the client in response to a subscription request from the client application; generating an event for the client application in response to the presence of data satisfying the predefined data criteria; and communicating the event to the client application when the client application connects to the server to receive the event, the communication performed without establishing a client-side proxy.
Claim 34
Independent Claim
102 words
A method of providing event notification through a firewall operable to block communication of at least some events from a server to a client, comprising: according to a data access framework, associating predefined data criteria at the server with a client application of the client in response to a subscription request from the client application; generating an event for the client application in response to the presence of data satisfying the predefined data criteria; and communicating the event to the client application when the client application connects to the server to receive the event, the communication performed without establishing a client-side proxy.
Claim 35
Dependent Claim
32 words
The method of claim 29 , further comprising: periodically connecting the client application to the server to receive events; and disconnecting the client application from the server in the absence of events.
Claim 36
Dependent Claim
20 words
The method of claim 30 , further comprising communicating between the client application and the server using the HTTP protocol.
Claim 37
Dependent Claim
30 words
The method of claim 29 , further comprising: the client application remaining connected to the server; and downloading data satisfying the predefined data criteria in response to a subsequent event.
Claim 38
Dependent Claim
19 words
The method of claim 32 , further communicating between the client application and the server using the TCP/IP protocol.
Claim 39
Dependent Claim
21 words
The method of claim 29 , further comprising connecting the client application to the server using an application program interface (API).
Claim 40
Dependent Claim
23 words
The method of claim 29 , wherein the data access framework comprises a permissivity framework and the event comprises a client call back.
Claim 41
Independent Claim
127 words
A method of providing event notification through a firewall operable to block communication of at least some events from a first enterprise computer system to a second enterprise computer system, comprising: according to a data access framework, associating predefined data criteria at the first enterprise computer system with a second enterprise application of the second enterprise computer system in response to a subscription request from the second enterprise application; generating an event for the second enterprise application in response to the presence of data satisfying the predefined data criteria; and communicating the event to the second enterprise application when the second enterprise application connects to the first enterprise computer system to receive the event, the communication performed without establishing a proxy at the second enterprise computer system.
Claim 42
Independent Claim
127 words
A method of providing event notification through a firewall operable to block communication of at least some events from a first enterprise computer system to a second enterprise computer system, comprising: according to a data access framework, associating predefined data criteria at the first enterprise computer system with a second enterprise application of the second enterprise computer system in response to a subscription request from the second enterprise application; generating an event for the second enterprise application in response to the presence of data satisfying the predefined data criteria; and communicating the event to the second enterprise application when the second enterprise application connects to the first enterprise computer system to receive the event, the communication performed without establishing a proxy at the second enterprise computer system.
Claim 43
Dependent Claim
40 words
The method of claim 36 , further comprising: periodically connecting the second enterprise application to the first enterprise computer system to receive events; and disconnecting the second enterprise application from the first enterprise computer system in the absence of events.
Claim 44
Dependent Claim
33 words
The method of claim 36 , further comprising: the second enterprise application remaining connected to the first enterprise computer system; and downloading data satisfying the predefined data criteria in response to an event.
Claim 45
Dependent Claim
22 words
The method of claim 36 , wherein the first enterprise is a supplier enterprise and the second enterprise is a customer enterprise.
Claim 46
Dependent Claim
22 words
The method of claim 36 , wherein the first enterprise is a hub enterprise and the second enterprise is a spoke enterprise.
Claim 47
Dependent Claim
18 words
The method of claim 36 , wherein the first and second enterprises are members of a supply chain.
Claim 48
Dependent Claim
22 words
The method of claim 36 , wherein the data access framework comprises a permissivity framework and the event comprises a client call-back.
References Cited (Backward Citations)
US5430876A
Cited
US6073109A
Cited
US5430875A
Cited
US5706505A
Cited
US5724589A
Cited
US6029175A
Cited
WO1997019415A2
Cited
WO1998008177A1
Cited
US5884035A
Cited
US6023708A
Cited
US6073163A
Cited
WO1999010825A1
Cited
US6098172A
Cited
US5983267A
Cited
US6209018B1
Cited
US5963947A
Cited
US6157941A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2004-09-10 | 2005-03-12 | 2005-09-11 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2008-09-10 | 2009-03-12 | 2009-09-11 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2012-09-10 | 2013-03-12 | 2013-09-11 | $7700.00 | Window Closed / Lapsed |