INTELLIGENT EVENT QUERY PUBLISH AND SUBSCRIBE SYSTEM

• US 20100125584A1
• Filed: 11/19/2009
• Published: 05/20/2010
• Est. Priority Date: 11/20/2008
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Navas, Julio
• Granted Patent: US 8,296,303 B2
• Time in Patent Office: Days
• 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:

assigning a descriptive name identifier to event data associated with a object in an enterprise system, the descriptive name identifier identifying a data type and data contents of the object, the descriptive name identifier associated with a source of the event data, the object being a structured data object, the data source to store the object and indicate changes to the object as event data, the data source being a data source local to a node of the enterprise system;

storing the descriptive name identifier at the network node of the enterprise system;

indexing the descriptive name identifier at the network node with other descriptive name identifiers that define object contents and identify sources of event data within the enterprise network; and

routing queries for event data based on the indexing to the data sources to obtain the event data from the data sources in real time.

2. The method of claim 1, wherein assigning the descriptive name identifier comprises:

generating the descriptive name identifier based on a naming algorithm following a convention for describing the data type and data contents.

3. The method of claim 1, wherein assigning the descriptive name identifier further comprises:

generating a name including a string to identify the event data; and

hashing the string to generate the descriptive name identifier.

4. The method of claim 3, wherein hashing the string further comprises:

executing a one-way hash on the string, the hash having a certain bit-length;

executing multiple hashes on a result of the hash, where the multiple hashes have a bit-length that is shorter than the hash; and

combining results of the multiple hashes to generate the descriptive name identifier.

5. The method of claim 1, wherein the data source is the network node at which the descriptive name identifier is indexed, and wherein assigning the descriptive name identifier further comprises:

converting an identifier compliant with a local system of the network node to the descriptive name identifier generic to other nodes in the enterprise system.

6. The method of claim 1, wherein assigning the descriptive name identifier comprises:

assigning an identifier that indicates the data type and data contents via operation of a decoding equation, rather than indicating information as a one-bit-to-one element of information bit map.

7. The method of claim 1, further comprising:

making the indexed descriptive name identifier available from the network node via a publish and subscribe mechanism where the network node advertises the event data available from the data source associated with the descriptive name identifier, and the descriptive name identifier is subscribed to by zero or more additional network nodes to request event data.

8. The method of claim 1, wherein assigning the descriptive name identifier further comprises:

assigning a descriptive name identifier having one of multiple levels of precision in identifier data contents, where a descriptive name identifier with more bits has more precision, and different network nodes within the enterprise network index descriptive name identifiers having different levels of precision.

9. The method of claim 8, further comprising:

determining if the network node at which the descriptive name identifier is to be indexed is an edge node or a core node of the enterprise system, where an edge node is assigned descriptive name identifiers having higher levels of precision than descriptive name identifiers assigned to core nodes.

10. 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:

assigning a descriptive name identifier to event data associated with a object in an enterprise system, the descriptive name identifier identifying a data type and data contents of the object, the descriptive name identifier associated with a source of the event data, the object being a structured data object, the data source to store the object and indicate changes to the object as event data, the data source being a data source local to a node of the enterprise system;

storing the descriptive name identifier at the network node of the enterprise system;

indexing the descriptive name identifier at the network node with other descriptive name identifiers that define object contents and identify sources of event data within the enterprise system; and

routing queries for event data based on the indexing to the data sources to obtain the event data from the data sources in real time.

11. The article of manufacture of claim 10, wherein assigning the descriptive name identifier further comprises:

generating a name including a string to identify the event data; and

hashing the string to generate the descriptive name identifier, including executing a one-way, cipher and hash on the string, the cipher and hash having a certain bit-length, executing multiple hashes on a result of the cipher and hash, where the multiple hashes have a bit-length that is shorter than the cipher and hash, and combining results of the multiple hashes to generate the descriptive name identifier.

12. The article of manufacture of claim 10, wherein the content for assigning the descriptive name identifier comprises content for

assigning an identifier that indicates the data type and data contents via operation of a decoding equation, rather than indicating information as a one-bit-to-one element of information bit map.

13. The article of manufacture of claim 10, further comprising content to provide instructions for

making the indexed descriptive name identifier available from the network node via a publish and subscribe mechanism where the network node advertises the event data available from the data source associated with the descriptive name identifier, and the descriptive name identifier is subscribed to by zero or more additional network nodes to request event data.

14. The article of manufacture of claim 10, wherein the content for assigning the descriptive name identifier further comprises content for

assigning a descriptive name identifier having one of multiple levels of precision in identifier data contents, where a descriptive name identifier with more bits has more precision, and different network nodes within the enterprise network index descriptive name identifiers having different levels of precision;

and

further comprising content to provide instructions for

determining if the network node at which the descriptive name identifier is to be indexed is an edge node or a core node of the enterprise system, where an edge node is assigned descriptive name identifiers having higher levels of precision than descriptive name identifiers assigned to core nodes.

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

a memory device storing event routing index information, the event routing index information including an index having multiple descriptive name identifiers of event data associated with objects in the enterprise network, each descriptive name identifier identifying a data type and data contents of a object, the descriptive name identifier associated with a source of the event data, the object being a structured data object, the data source to store the object and indicate changes to the object as event data, the data source being a data source local to a node of the enterprise network;

an index engine to index the descriptive name identifier at the server node with other descriptive name identifiers that define object contents and identify sources of event data associated with objects;

a routing engine to route queries for event data based on the indexing to the data sources to obtain the event data from the data sources in real time; and

a network interface circuit to receive a query component from a query source requesting information about one or more events and route the query based on the index.

16. The server node of claim 15, wherein assigning the descriptive name identifier further comprises a hash of a string identifying type and content of the event data.

17. The server node of claim 16, wherein the hash comprises a result of multiple hash operations generated by:

executing a one-way cipher and hash on the string, the cipher and hash having a certain bit-length;

executing multiple hashes on a result of the cipher and hash, where the multiple hashes have a bit-length that is shorter than the cipher and hash; and

combining results of the multiple hashes to generate the descriptive name identifier.

18. The server node of claim 15, wherein the descriptive name identifier comprises a bit vector, and wherein

the index engine further indexes bit vectors from neighboring server nodes and builds a routing table based on bit vectors local to the server node and the bit vectors from the neighboring nodes.

19. The server node of claim 18, the index engine to further apply one or more decoding equations to bit vectors from the routing table to route the query component.

20. The server node of claim 15, further comprising:

a bit vector filter to reduce or expand a bit vector to change a level of precision in identifying data contents from descriptive name identifiers to adjust a routing behavior of the server node.