Patent US6901447B2 successfully refreshed from Google Patents.
US6901447B2
Expired / Lapsed
US
⏱️ 0.0 years remaining
Event driven communication system
Assignee: Vitria Tech Inc
•
Filing: 2002-08-15
•
Granted: 2005-05-31
•
Expires: 2022-08-15
Abstract
Abstract A publish-subscribe communications system having a plurality of channels for transmitting data furnished by publishers of data to subscribers to data, each channel accepting data published to the channel and furnishing the data accepted to subscribers to the channel, a channel including facilities for accepting data for transmission by the channel from another channel.
Inventors
- 👤 Richard Koo
- 👤 Dale Skeen
- 👤 Alexander Siegel
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-30 21:42
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/54; G06F9/542; H; H04; H04L; H04L67/00; H04L67/01; H04L67/10; H04L67/50; H04L67/56; H04L67/567; H04L9/00; H04L9/40; H04L67/2866; H04L67/288; H04L69/00; H04L69/30; H04L69/32; H04L69/322; H04L69/329
Claims Analysis
Total Claims: 20
Claim 1
Independent Claim
133 words
A publish-subscribe communications system in which data is published in response to events, said system comprising: at least one data source serving as a publisher of data in response to events; at least one subscriber; and a plurality of software channels for storing and transmitting data furnished by selected ones of said at least one data source to selected ones of said at least one subscriber, each of said software channels defining a software protocol specifying how data sources publish to the channel and how subscribers subscribe to the channel whereby data published to a channel is made available to all subscribers subscribing to that same channel; wherein at least a first channel of said channels defines a software protocol for accepting data from a second channel of said channels as a publisher.
Claim 2
Dependent Claim
133 words
A publish-subscribe communications system in which data is published in response to events, said system comprising: at least one data source serving as a publisher of data in response to events; at least one subscriber; and a plurality of software channels for storing and transmitting data furnished by selected ones of said at least one data source to selected ones of said at least one subscriber, each of said software channels defining a software protocol specifying how data sources publish to the channel and how subscribers subscribe to the channel whereby data published to a channel is made available to all subscribers subscribing to that same channel; wherein at least a first channel of said channels defines a software protocol for accepting data from a second channel of said channels as a publisher.
Claim 3
Dependent Claim
20 words
A publish-subscribe communications system as claimed in claim 1 wherein each of the software channels is a named software object.
Claim 4
Dependent Claim
27 words
A publish-subscribe communications system as claimed in claim 2 , wherein the named software object is named to indicate a characteristic of the data in the channel.
Claim 5
Dependent Claim
31 words
A publish-subscribe communications system as claimed in claim 1 , wherein the protocol for accepting data from a second channel includes means for changing channels from which data is accepted dynamically.
Claim 6
Dependent Claim
92 words
A channel factory object for creating software channels within a publish-subscribe communications system in which data is published to channels in response to events, said channel factory object comprising: a software allocation method for allocating hardware and software resources for channels; a software protocol method specifying how data sources publish to channels and how subscribers subscribe to the channels whereby data published to a channel is made available to all subscribers subscribing to that same channel, said software protocol method including instructions for accepting data from a second channel as a publisher.
Claim 7
Dependent Claim
92 words
A channel factory object for creating software channels within a publish-subscribe communications system in which data is published to channels in response to events, said channel factory object comprising: a software allocation method for allocating hardware and software resources for channels; a software protocol method specifying how data sources publish to channels and how subscribers subscribe to the channels whereby data published to a channel is made available to all subscribers subscribing to that same channel, said software protocol method including instructions for accepting data from a second channel as a publisher.
Claim 8
Dependent Claim
20 words
A channel factory object as claimed in claim 5 , further comprising a software method for deleting a software channel.
Claim 9
Dependent Claim
27 words
A channel factory object as claimed in claim 5 , further comprising a naming service operative to allocate names for channels created by the software channel object.
Claim 10
Dependent Claim
31 words
A channel factory object as claim in claim 5 , further comprising an access control method for creating and managing access control lists of channels created by the channel factory object.
Claim 11
Dependent Claim
27 words
A channel factory object as claimed in claim 5 in which the software protocol method specifies that only channels are accepted as publishers to a created channel.
Claim 12
Dependent Claim
27 words
A channel factory object as claimed in claim 5 , wherein the software protocol method includes a method for changing channels from which data is accepted dynamically.
Claim 13
Independent Claim
65 words
A method for creating a software channel in a publish-subscribe communications system capable of executing event service software programs, said method comprising: allocating resources for accepting data published by publishers to the software channel; and specifying protocols for providing access to the software channel by publishers and subscribers, said protocols including protocols for providing access to the software channel by other software channels as publishers.
Claim 14
Independent Claim
65 words
A method for creating a software channel in a publish-subscribe communications system capable of executing event service software programs, said method comprising: allocating resources for accepting data published by publishers to the software channel; and specifying protocols for providing access to the software channel by publishers and subscribers, said protocols including protocols for providing access to the software channel by other software channels as publishers.
Claim 15
Dependent Claim
30 words
A method as claimed in claim 11 in which said step of specifying comprises specifying protocols providing access to the software channel only to publishers which are other transmission channels.
Claim 16
Dependent Claim
19 words
A method as claimed in claim 12 , further comprising recording publishers and subscribers having access to the channel.
Claim 17
Dependent Claim
21 words
A method as claimed in claim 12 further comprising recording access rights of publishers and subscribers having access to the channel.
Claim 18
Dependent Claim
21 words
A method as claimed in claim 12 , wherein said allocating step comprises allocating persistent storage resources to the software channel.
Claim 19
Dependent Claim
22 words
A method as claimed in claim 12 , wherein said allocating and specifying steps are accomplished by a channel factory software object.
Claim 20
Dependent Claim
32 words
A method as claimed in claim 11 , wherein the protocol for providing access to the channel by other software channels includes means for changing channels from which data is accepted dynamically.
References Cited (Backward Citations)
US5187787B1
Cited
US5557798A
Cited
US5187787A
Cited
US5257369A
Cited
US5295139A
Cited
US5649105A
Cited
US5844553A
Cited
US5913032A
Cited
US6594692B1
Cited
US5712980A
Cited
US6005561A
Cited
US5793365A
Cited
US5873084A
Cited
US5815663A
Cited
US5699365A
Cited
US5819032A
Cited
US5768528A
Cited
US5919247A
Cited
US6012083A
Cited
US6240444B1
Cited
US6279112B1
Cited
US6233318B1
Cited
US5935210A
Cited
US6012050A
Cited
US5913041A
Cited
US6067568A
Cited
US6128315A
Cited
US5794039A
Cited
US5946399A
Cited
US5995999A
Cited
US6704785B1
Cited
US5931900A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2008-05-30 | 2008-11-29 | 2009-05-31 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2012-05-30 | 2012-11-29 | 2013-05-31 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2016-05-30 | 2016-11-29 | 2017-05-31 | $7700.00 | Window Closed / Lapsed |