Content based data routing

• US 7,925,777 B2
• Filed: 12/09/2002
• Issued: 04/12/2011
• Est. Priority Date: 12/07/2001
• Status: Active Grant

• Current Assignee: Integra SP Limited (Tiger Telematics Incorporated)
• Original Assignee: Integra SP Limited (Tiger Telematics Incorporated)
• Inventors: Levett, David Lawrence
• Primary Examiner(s): Ismail; Shawki S
• Assistant Examiner(s): HUQ, FARZANA B
• Application Number:
  US10/497,125
• Publication Number:
  US 20050021838A1
• Time in Patent Office: 3,046 Days
• Field of Search: 709/236, 709/238, 709/242, 709/204, 709/205, 709/225, 709/227, 709/228, 709217-218, 709/240, 709/224, 370473-476, 707/100
• US Class Current: 709/238
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method of routing data from a source to one or more clients over a network, where the data conforms to a structured meta-language; in which the routing is performed by a server applying rules to the data itself, and not any address accompanying the data, to determine where to route that data to. The present invention is predicated on the counter-intuitive insight that data does not need to be concealed within a data envelope and given an address label in order to be routed effectively and efficiently. Instead, routing can be performed on the actual content of a message by applying simple routing rules to the data itself by intelligent ‘routing’ servers within the network which can unpack data from their message envelopes and intelligently filter/combine them with data unpacked from other messages to achieve a routing function.

Claims

1. A method of routing data from multiple sources to multiple clients over a network;

including the following steps;

(a) unpacking the data content of multiple incoming messages from their respective message data envelopes, with the data content conforming to a structured meta-language and including tagged fields that allow rule based filtering to be applied using those tagged fields; and

the routing being performed by a routing server applying rule-based filtering to the data, with;

(b) the routing server performing the rule based filtering using the tagged fields when querying the data content; and

(c) the routing server then combining the data content from multiple incoming messages previously sent for unpacking into a single outgoing network message;

and wherein the unpacked data is analysed by the routing server and the routing server applies the rule-based filtering which results in (a) only a sub-set of that data being packaged into one or more messages and then routed to a client and (b) a different sub-set of that data being packaged into one or more messages and then routed to a different client.

2. The method of claim 1 in which the structured meta-language is XML.

3. The method of claim 1 in which the rule-based filtering applied by the server is continuously updateable.

4. The method of claim 3 in which the rule-based filtering is continuously updateable by a message, or a sub-set of a message, being received and processed by the server.

5. The method of claim 4 in which the rule-based filtering is applied by the server in real time to the data.

6. The method of claim 5 in which the rule-based filtering is applied by the server in real time to the data depending on what needs to be rendered for viewing at a client, hence restricting updating data to what a client is actually looking at, rather than the entire set of things which the client might be able to look at.

7. The method of claim 1 in which multiple parallel servers can route from a single source to give scalability.

8. The method of claim 7 in which if one server from a group of multiple parallel servers fails, then another server in that group can take over.

9. The method of claim 1 in which multiple series connected servers can perform routing.

10. The method of claim 9 in which a server higher up the hierarchy of a series is insulated from needing to know the or each rule which will be applied by a server further down in the hierarchy.

11. The method of claim 1 in which the rule-based filtering is a member selected from the following group of rules:

(a) Route data based on a user'"'"'s unique identifier;

(b) Route data based on security privileges;

(c) Route data based on rules about client and network performance;

(d) Route data based on rules about performance, of the server supplying the data, so that if one or more of the servers supplying the data becomes overloaded, the routing server could be used to limit access to the busy server;

(e) Route data based on per-user customisation and security rules delegated by a legacy server;

(f) Route data following rules to divert certain content of an incoming message over an expensive but highly secure network whilst some or all of the remaining content is sent through the public network;

(g) Route data by selectively encrypting and/or digitally signing portions of a message before passing it on, reducing the CPU cost of the encryption process without unduly affecting the security of the message;

(h) Route data by selectively encrypting and/or digitally signing portions of a message with multiple keys before passing the message on to a broadcast network that would send the same encrypted message to all clients, but where each would only be able to decrypt certain portions of the message;

(i) Route data by holding a certain message until one or more other messages are received with matching content.

12. The method of claim 2 in which the rule-based filtering is structured as Xqueries comparing data against data held locally in the server.

13. The method of claim 1 in which the data is Instant Messaging personal communications.

14. The method of claim 1 in which the data is web services related data.

15. An apparatus comprising a processor and memory programmed, using program data stored on a computer readable medium, to route data from multiple sources to multiple clients over a network, wherein:

the apparatus applies rule-based filtering to the data;

the apparatus unpacks the data content of multiple, incoming network messages from their respective data envelopes, with the data content conforming to a structured meta-language and including tagged fields that allow rule based filtering to be applied using those tagged fields; and

the routing being performed by a routing server applying rule-based filtering to the data, wherein;

the apparatus performs the rule based filtering using the tagged fields, and constructs a single outgoing network message by combining data content of multiple incoming messages previously sent for unpacking;

and wherein the unpacked data is analysed and then the rule-based filtering is applied which results in (a) only a sub-set of that data being packaged into one or more messages and then routed to a client and (b) a different sub-set of that data being packaged into one or more messages and then routed to a different client.

16. The apparatus of claim 15 which enables the rule-based filtering to be continuously updateable.

17. The apparatus of claim 16 in which the rule-based filtering is continuously updateable by a message, or a sub-set of a message, which the apparatus stores and processes.

18. The apparatus of claim 17 in which the apparatus applies the rule-based filtering in real time to the data.

19. The apparatus of claim 15 in which the rule-based filtering is applied in real time to the data depending on what needs to be rendered for viewing at a client, hence restricting updating data to what a client is actually looking at, rather than the entire set of things which the client might be able to look at.

20. The apparatus of claim 15 when organised into multiple parallel servers which can route from a single source to give scalability.

21. The apparatus of claim 20 in which if one server from a group of multiple parallel servers fails, then another server in that group can take over.

22. The apparatus of claim 15 when organised into multiple series connected servers to perform routing.

23. The apparatus of claim 22 in which a server higher up the hierarchy of a series is insulated from needing to know the or each rule which will be applied by a server further down in the hierarchy.

24. The apparatus of claim 15 in which the rule-based filtering is a member selected from the following group of rules:

(a) Route data based on a user'"'"'s unique identifier;

(b) Route data based on security privileges;

(c) Route data based on rules about client and network performance;

(d) Route data based on rules about performance, of the server supplying the data, so that if one or more of the servers supplying the data becomes overloaded, the routing server could be used to limit access to the busy server;

(e) Route data based on per-user customisation and security rules delegated by a legacy server;

(f) Route data following rules to divert certain content of an incoming message over an expensive but highly secure network whilst some or all of the remaining content is sent through the public network;

(g) Route data by selectively encrypting and/or digitally signing portions of a message before passing it on, reducing the CPU cost of the encryption process without unduly affecting the security of the message;

(h) Route data by selectively encrypting and/or digitally signing portions of a message with multiple keys before passing the message on to a broadcast network that would send the same encrypted message to all clients, but where each would only be able to decrypt certain portions of the message;

(i) Route data by holding a certain message until one or more other messages are received with matching content.

25. The apparatus of claim 15 in which the rule-based filtering is structured as Xqueries comparing data against data held locally in the apparatus.