Intelligent event query publish and subscribe system

• US 8,965,902 B2
• Filed: 10/22/2012
• Issued: 02/24/2015
• Est. Priority Date: 11/20/2008
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Navas, Julio
• Primary Examiner(s): LU, KUEN S
• Application Number:
  US13/657,719
• Publication Number:
  US 20130166569A1
• Time in Patent Office: 855 Days
• Field of Search: 707/747, 707/803
• US Class Current: 707/747
• CPC Class Codes: G06F 16/2255 Hash tables
• CPC Class Codes: G06F 16/24568 Data stream processing; Continuous queries
• CPC Class Codes: G06F 16/2471 Distributed queries
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Indexing and routing to event data is described. Event data is assigned an identifier that identifies the data type and the contents of event data within an enterprise system. The event data may be real-time event data. With the identifier, a source of the event data is determined, and the source can be queried for the event data in real-time. The identifier is indexed along with other event data identifiers. Based on the location of the event data, the system sends out a query toward the data source to obtain the information, but also to route the query to the data source, rather than attempting to pull data towards the query source and process it at the query source.

Claims

1. A computer-implemented method comprising:

receiving, by a routing node of an enterprise system, a query from a query source, including a subscription by the query source to a data event in the enterprise system, the enterprise system having multiple separate event data sources distributed among separate enterprise nodes, where the data event includes a change in one or more structured data objects at a respective data source;

receiving event data from one or more of the data sources indicating one or more data events;

filtering the received event data based on index information stored by the routing node and based on the subscription, the index information indicating a network location of the data events, the filtering including decoding a descriptive name index that indicates node connections to the routing node and respective data available via the node connections to the routing node, wherein decoding the description name index comprises decoding a descriptive name hash; and

publishing the filtered event data to the query source.

2. The method of claim 1, wherein receiving the query including the subscription further comprises:

parsing the query into multiple component parts, each related to a different data event of the enterprise system; and

generating a subscription to each of the data events related to the multiple component parts.

3. The method of claim 2, wherein filtering the received event data comprises determining what event data to publish to the query source based on the subscriptions to the component parts, including not publishing event data related to component parts the query source is not subscribed to.

4. The method of claim 2, wherein the query source is directly coupled to the routing node, and wherein filtering the received event data further comprises combining event data about multiple different component parts into a single event data notice to be published to the query source.

5. An article of manufacture comprising a machine-readable storage medium having content stored thereon to provide instructions to cause a machine to perform operations, including:

receiving, by a routing node of an enterprise system, a query from a query source, including a subscription by the query source to a data event in the enterprise system, the enterprise system having multiple separate event data sources distributed among separate enterprise nodes, where the data event includes a change in one or more structured data objects at a respective data source;

receiving event data from one or more of the data sources indicating one or more data events;

filtering the received event data based on index information stored by the routing node and based on the subscription, the index information indicating a network location of the data events, the filtering including decoding a descriptive name index that indicates node connections to the routing node and respective data available via the node connections to the routing node, wherein decoding the description name index comprises decoding a descriptive name hash; and

publishing the filtered event data to the query source.

6. The article of manufacture of claim 5, wherein receiving the query including the subscription further comprises:

parsing the query into multiple component parts, each related to a different data event of the enterprise system; and

generating a subscription to each of the data events related to the multiple component parts.

7. The article of manufacture of claim 6, wherein filtering the received event data comprises determining what event data to publish to the query source based on the subscriptions to the component parts, including not publishing event data related to component parts the query source is not subscribed to.

8. The article of manufacture of claim 6, wherein the query source is directly coupled to the routing node, and wherein filtering the received event data further comprises combining event data about multiple different component parts into a single event data notice to be published to the query source.

9. A server node of an enterprise network, comprising:

a network interface circuit coupled to a query source device to receive a query from the query source, including a subscription by the query source to a data event in the enterprise system, the enterprise system having multiple separate event data sources distributed among separate enterprise nodes, where the data event includes a change in one or more structured data objects at a respective data source;

the network interface circuit coupled to enterprise nodes, to receive event data from one or more of the data sources via the nodes coupled to the network interface circuit, the event data indicating one or more data events;

an index engine to filter the received event data based on index information stored by the routing node and based on the subscription, the index information indicating a network location of the data events, wherein the index engine to filter the received event data includes the index engine to decode a descriptive name index that indicates node connections to the routing node and respective data available via the node connections to the routing node, wherein the index engine to decode the description name index comprises the index engine to decode a descriptive name hash; and

a routing engine to publish the filtered event data to the query source.

10. The server node of claim 9, wherein in response to receiving the query including the subscription, the index engine is to parse the query into multiple component parts, each related to a different data event of the enterprise system, and generate a subscription to each of the data events related to the multiple component parts.

11. The server node of claim 10, wherein the index engine to filter the received event data includes the index engine to determine what event data to publish to the query source based on the subscriptions to the component parts, including the index engine to forego publication of event data related to component parts the query source is not subscribed to.

12. The server node of claim 10, wherein the query source is directly coupled to the server node, and wherein the index engine to filter the received event data includes the index engine to combine event data about multiple different component parts into a single event data notice to be published to the query source.