Real-time communication for resource content comprises selecting by a subscriber device, an event topic based on an event topic list, creating for the selected event topic, a topic path for receiving a notification event related to the selected event topic, and sending path information of the created topic path as part of identification information with the selected event topic to a resource content publishing device. Real-time communication also comprises receiving by the resource content publishing device, the identification information and the selected event topic, and adding the identification information and the selected event topic to an event topic subscription search table. Real-time communication also comprises, if new resource content is available, obtaining, based on the event topic subscription search table, identification information of a subscriber device subscribing to an event topic related to the new resource content and sending a notification event including the new resource content to the subscriber device.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A subscription management method for resource content, comprising: selecting an event topic based on an event topic list by a subscriber device, wherein the event topic selected by the subscriber device is a complex event topic set constituted by at least two separate event topics and a predefined rule describing a relation between the separate events related to the complex event topic set; creating for the selected event topic, by the subscriber device, a topic path for receiving a notification event related to the selected event topic; storing the selected event topic and a Web address of a resource content publishing device at the subscriber device, wherein the Web address of the resource content publishing device is for providing the notification event related to the event topic; creating, by the subscriber device, a reversed event, the reversed event comprising reversed event content edited by the subscriber device and an event topic which is stored by the subscriber device and is the same as that of a corresponding notification event; sending, by the subscriber device, the reversed event to the resource content publishing device according to the Web address of the resource content publishing device; sending, by the subscriber device, path information of the created topic path as part of identification information of the subscriber device, along with the selected event topic, to a resource content publishing device; and receiving, by the subscriber device, the notification event sent by the resource content publishing device to the subscriber device according to the identification information of the subscriber device.
A subscriber device subscribes to content updates by selecting an event topic (which can be a combination of events defined by a rule) from a list. It creates a unique path (topic path) for receiving notifications related to that topic and stores the topic and the publishing device's web address. The device can also create a "reversed event" (feedback), sending it to the publisher. It transmits the topic path information and the selected event topic to the content publishing device and receives notifications from the publisher to the specified path when updates are available.
2. The subscription management method for resource content according to claim 1 , wherein: the event topic list comprises an event topic to be selected and identification information of a resource content publishing device providing a notification event related to the event topic to be selected; the identification information of the resource content publishing device comprises a Web address of the resource content publishing device and path information of a topic path at the resource content publishing device for receiving a reversed event of a corresponding event topic; and selecting an event topic based on the event topic list further comprises obtaining identification information of the resource content publishing device providing the notification event related to the selected event topic; further comprising: creating, by the subscriber device, a reversed event, the reversed event comprising reversed event content edited by the subscriber device; and sending, by the subscriber device, the reversed event to the resource content publishing device according to the identification information of the resource content publishing device.
The subscription method of claim 1 includes an event topic list that contains selectable event topics along with resource content publishing device information that provides the notification event. This publishing device information includes a web address and topic path for receiving "reversed events" (feedback). The subscriber device selects an event topic from the list and obtains the resource content publishing device's information, creates a "reversed event" containing edited content, and sends the reversed event to the publishing device using the publisher's web address and the topic path information provided.
3. The subscription management method for resource content according to claim 1 , wherein receiving, by the subscriber device, the notification event, comprises: storing the received notification in a topic path directory folder created for the event topic, so as to receive each updated notification event related to the event topic as a corresponding new file in the topic path directory folder.
The subscription method of claim 1 receives notifications and stores each updated notification event related to a particular event topic as a new file within a dedicated directory folder created specifically for that event topic. Therefore, notifications are organized based on event topics in the form of files within dedicated folders.
4. The subscription management method for resource content according to claim 1 , wherein receiving, by the subscriber device, the notification event, comprises: using at least one field in at least one of: a document and a database, under the topic path related to the event topic such that each notification event related to the event topic is added to a corresponding part of the associated one of the document or database.
The subscription method of claim 1 receives notifications and stores each notification event related to a particular event topic by adding it to a designated location within a document or database. The location is determined by the topic path associated with that event topic. So, the notification is inserted into an existing document or database under the appropriate topic path.
5. The subscription management method for resource content according to claim 1 , wherein receiving, by the subscriber device, the notification event, comprises: receiving the notification at a default path; and performing at least one of: distributing the notification event to a corresponding topic path according to the event topic of the received notification event and a corresponding search table of topic paths; and consuming the notification event directly in the default path.
The subscription method of claim 1 receives notifications at a default path. Subsequently, the notification event can be distributed to a specific topic path based on the event topic and a lookup table of topic paths or the notification event can be directly consumed in the default path.
6. The subscription management method for resource content according to claim 1 , wherein: sending, by the subscriber device, path information of the created topic path comprises identifying path information by defining paths according to at least one rule, such that the resource content publishing device can derive the appropriate path for a corresponding event notification based upon obtaining the corresponding rule.
In the subscription method of claim 1, the subscriber device defines the path information by establishing paths based on rules. This enables the resource content publishing device to derive the appropriate path for a corresponding event notification by understanding these pre-defined rules.
7. The subscription management method for resource content according to claim 1 , further comprising: building, by the subscriber device subsequent to creating the topic path, a search table for the selected event topic and the corresponding topic path and sending the identification information constituted by a Web address of the subscriber device along with the selected event topic to the resource content publishing device; wherein: receiving, by the subscriber device, the notification event sent by the resource content publishing device, comprises: receiving, by the subscriber device, the notification event comprising the new resource content and the event topic sent by the resource content publishing device according to the Web address of the subscriber device; obtaining a topic path corresponding to the notification event with reference to the search table for the event topic and the corresponding topic path; and distributing the new resource content in the notification event to a corresponding topic path.
The subscription method of claim 1 involves the subscriber device building a search table that links selected event topics to corresponding topic paths after creating a topic path. The device then sends its web address and the selected event topic to the resource content publishing device. Upon receiving a notification event (including new content and the event topic) from the publisher to the subscriber's web address, the device consults the search table to determine the correct topic path for the event topic and distributes the new content to that path.
8. A real-time communication method for resource content, the method comprising: receiving from a subscriber device, by a resource content publishing device, identification information of the subscriber device and an event topic, wherein the identification information comprises path information defining a topic path for receiving a notification event related to the selected event topic and the event topic selected by the subscriber device is a complex event topic set constituted by at least two separate event topics; adding the identification information of the subscriber device and the selected event topic to an event topic subscription search table; determining, by the resource content publishing device, if new resource content is available, whether an event topic of the new resource content belongs to the complex event topic set; creating, by the resource content publishing device, if it is determined that the event topic of the new resource content belongs to the complex event topic set, a complex event by applying a predefined rule describing a relation between the separate events related to the complex event topic set onto the new resource content, so as to send the complex event to the subscriber device after obtaining the identification information of the subscriber device; obtaining by the resource content publishing device, the identification information of a subscriber device subscribing to an event topic related to new resource content, where the identification information is obtained from the event topic subscription search table, if new resource content is available; and sending, by the resource content publishing device, a notification event comprising the new resource content to the subscriber device according to the identification information of the subscriber device.
A content publishing device receives a subscriber's identification information and an event topic (which is a combination of events defined by a rule) from a subscriber device. This information includes the path the subscriber wants to use to receive notifications. The publisher adds this information to a subscription table. When new content is available, the publisher checks if the content's event topic matches any complex event topic sets. If so, the publisher creates a complex event based on the defined rule and sends a notification containing the new content to the subscriber based on the subscriber's information retrieved from the table.
9. The real-time communication method for resource content according to claim 8 , further comprising: creating a corresponding topic path for receiving a reversed event related to the event topic at the resource content publishing device, a path name of which is the same as that of the topic path of the subscriber device for receiving a notification event related to the same event topic; and receiving, by the resource content publishing device, a reversed event that was sent by the subscriber device according to a Web address of the resource content publishing device and corresponding topic path information, where the reversed event, created by the subscriber device, comprises reversed event content edited by the subscriber device.
The real-time communication method of claim 8 involves the resource content publishing device creating a topic path for receiving "reversed events" (feedback), where the path name is the same as the subscriber's topic path for receiving notifications. The publisher receives "reversed events," created and sent by the subscriber, which contain content edited by the subscriber. The events are sent to the publisher's web address and corresponding topic path.
10. The real-time communication method for resource content according to claim 8 , further comprising: using the event topic as at least part of the path name of the topic path at the subscriber device and the resource content device for receiving the event related to the same event topic.
In the real-time communication method of claim 8, the event topic is used as part of the topic path name on both the subscriber device and the resource content publishing device. This creates a consistent and easily identifiable path for related events on both ends.
11. The real-time communication method for resource content according to claim 8 , wherein, sending, by the resource content publishing device, a notification event comprises: using the notification event as feed information in RSS or Atom format, and sending the feed information to the subscriber device according to the RESTful protocol or the AtomPub protocol.
In the real-time communication method of claim 8, sending a notification event involves formatting the notification event as feed information (RSS or Atom) and sending the feed to the subscriber device using RESTful or AtomPub protocols.
12. The real-time communication method for resource content according to claim 11 , further comprising obtaining the new resource content by obtaining feed information in RSS or Atom format from an external resource content generator by at least one of: pulling and receiving, feed information in RSS or Atom format from an external resource content generator.
The real-time communication method of claim 11 obtains new content by either pulling or receiving RSS or Atom formatted feed information from an external resource content generator.
13. The real-time communication method for resource content according to claim 11 , further comprising: receiving, by the resource content publishing device, a reversed event created by the subscriber device, the reversed event comprising reversed event content edited by the subscriber device that has been converted into feed information in RSS or Atom format.
The real-time communication method of claim 11 involves the resource content publishing device receiving a "reversed event" (feedback) from the subscriber device. The reversed event contains content edited by the subscriber, and it has been converted into RSS or Atom feed format.
14. The real-time communication method for resource content according to claim 8 , further comprising: generating for a predetermined event topic, by the resource content publishing device, event change history information related to the predetermined event topic; and sending, by the resource content publishing device, a link to the event change history information to a subscriber device subscribing to the predetermined event topic, in order for the subscriber device to obtain the event change history information via the link.
The real-time communication method of claim 8 involves the resource content publishing device generating event change history information for a specific event topic. The publisher sends a link to this history information to subscribers who are subscribed to that topic, allowing them to access the history.
15. A computer program product to implement real-time communication for resource content, comprising: a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising: computer readable program code configured to receive, from a subscriber device, identification information of the subscriber device and an event topic, wherein the identification information comprises path information defining a topic path for receiving a notification event related to the selected event topic and the event topic selected by the subscriber device is a complex event topic set constituted by at least two separate event topics; computer readable program code configured to add the identification information of the subscriber device and the selected event topic to an event topic subscription search table; computer readable program code configured to determine, by the resource content publishing device, if new resource content is available, whether an event topic of the new resource content belongs to the complex event topic set; computer readable program code configured to create, by the resource content publishing device, if it is determined that the event topic of the new resource content belongs to the complex event topic set, a complex event by applying a predefined rule describing a relation between the separate events related to the complex event topic set onto the new resource content, so as to send the complex event to the subscriber device after obtaining the identification information of the subscriber device; computer readable program code configured to obtain, by the resource content publishing device, the identification information of a subscriber device subscribing to an event topic related to new resource content, where the identification information is obtained from the event topic subscription search table, if new resource content is available; and computer readable program code configured to send, by the resource content publishing device, a notification event comprising the new resource content to the subscriber device according to the identification information of the subscriber device.
A computer program product implements real-time communication for resource content. It receives subscriber identification and an event topic (a combination of events based on a rule) including a path for notifications. This information is added to a subscription table. The program determines if new content's topic matches a complex event set. If so, it creates a complex event using the defined rule and sends a notification with the content to the subscriber based on their information from the table.
16. The computer program product according to claim 15 , further comprising: computer readable program code configured to create a corresponding topic path for receiving a reversed event related to the event topic at the resource content publishing device, a path name of which is the same as that of the topic path of the subscriber device for receiving a notification event related to the same event topic; and computer readable program code configured to receive, by the resource content publishing device, a reversed event that was sent by the subscriber device according to a Web address of the resource content publishing device and corresponding topic path information, where the reversed event, created by the subscriber device, comprises reversed event content edited by the subscriber device.
The computer program product of claim 15 includes code to create a topic path for receiving "reversed events" (feedback) at the publisher, using the same path name as the subscriber's notification path. It also includes code to receive reversed events from the subscriber, which are sent to the publisher's web address and contain subscriber-edited content.
17. The computer program product according to claim 15 , wherein: the computer readable program code configured to send, by the resource content publishing device, a notification event, comprises computer readable program code configured to use the notification event as feed information in RSS or Atom format, and sending the feed information to the subscriber device according to the RESTful protocol or the AtomPub protocol; further comprising: computer readable program code configured to obtain the new resource content by obtaining feed information in RSS or Atom format from an external resource content generator by at least one of: pulling and receiving, feed information in RSS or Atom format from an external resource content generator.
The computer program product of claim 15 includes code to send notification events formatted as RSS or Atom feeds via RESTful or AtomPub protocols. It also includes code to obtain new content by pulling or receiving RSS or Atom feeds from external sources.
18. The computer program product according to claim 15 , further comprising: computer readable program code configured to receive, by the resource content publishing device, a reversed event created by the subscriber device, the reversed event comprising reversed event content edited by the subscriber device that has been converted into feed information in RSS or Atom format.
The computer program product of claim 15 includes code to receive "reversed events" (feedback) from the subscriber, where the reversed event contains content edited by the subscriber and formatted as an RSS or Atom feed.
19. The computer program product according to claim 15 , further comprising: computer readable program code configured to generate for a predetermined event topic, by the resource content publishing device, event change history information related to the predetermined event topic; and computer readable program code configured to send, by the resource content publishing device, a link to the event change history information to a subscriber device subscribing to the predetermined event topic, in order for the subscriber device to obtain the event change history information via the link.
The computer program product of claim 15 includes code to generate event change history for a specific event topic. It also includes code to send a link to this history to subscribers of that topic, enabling them to access it.
20. A method to implement an intermediate connected between a resource content publishing device and a subscriber device in a real-time communication for resource content, comprising: receiving, by the intermediate, identification information of a subscriber device from the subscriber device; receiving, by the intermediate, an event topic selected by the subscriber device based on an event topic list, wherein, the identification information comprises path information of a topic path created by the subscriber device for receiving a notification event related to the selected event topic, the event topic selected by the subscriber device is a complex event topic set constituted by at least two separate event topics, and the intermediate device comprises a complex event processing apparatus for processing a complex event; adding the identification information of the subscriber device and the selected event topic to an event topic subscription search table; determining whether an event topic of new resource content obtained by the resource content publishing device belongs to the complex event topic set; creating a complex event by applying a predefined rule describing a relation between the separate events related to the complex event topic set onto the new resource content if it is determined that the event topic of the new resource content belongs to the complex event topic set; obtaining based on the search table, the identification information of the subscriber device subscribing to an event topic related to the new resource content when new resource content is available; and sending a notification event including the event topic and the new resource content to the subscriber device.
A method uses an intermediary device between a publisher and subscriber. The intermediary receives the subscriber's identification information, including a path for notifications, and a selected event topic (a combination of events based on a rule). The intermediary has a complex event processor. The intermediary adds the subscriber's information and topic to a subscription table. It checks if new content's topic matches any complex event sets. If so, it creates a complex event based on the defined rule and sends a notification with the content to the subscriber.
21. The method according to claim 20 , further comprising: obtaining event change history information from the resource content publishing device; storing the obtained event change history information in a storage, and sending a link to the event change history information to a subscriber device subscribing to the predetermined event topic, in order for the subscriber device to obtain the event change history information via the link.
The method of claim 20 involves the intermediary obtaining event change history information from the publisher, storing it, and sending a link to this history to subscribers of that topic, enabling them to access it.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
March 26, 2010
September 24, 2013
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.