Content Aware Routing of Subscriptions For Streaming and Static Data

• US 20090204712A1
• Filed: 03/14/2007
• Published: 08/13/2009
• Est. Priority Date: 03/18/2006
• Status: Active Grant

• Current Assignee: Metafluent LLC
• Original Assignee: Metafluent LLC
• Inventors: MacGaffey, Andrew, Lankford, Peter
• Granted Patent: US 8,127,021 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/24 Multipath
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066

Abstract

The invention relates to integration of streaming data, and more specifically relates to subscription routing: distributing the load of streaming data subscriptions across multiple servers in a session-oriented client-server architecture. In one embodiment the invention provides, in a client-server architecture, a method of implementing the client-side architecture whereby a logical connection and session may be mapped to one or more physical connections and sessions. The invention provides mobility of subscriptions from one physical session/connection to another based on directives from a server; and further permit a client to blend multiple physical subscriptions for different data streams into a single logical data stream based on directives from a server.

Claims

1. A client-side architecture comprising:

connection to a network, said network including more than one server;

plurality of logical session supporting one or more logical subscriptions, enabled by said connection and manifested in physical sessions; and

mechanisms whereby, based on directives from a server, subscriptions for streaming responses within a logical session may be re-directed from one physical session to another such that an active logical session may be receiving streaming data for multiple logical subscriptions delivered via one or more physical sessions and connections.

2. A client-side architecture as in claim 1 wherein multiple physical subscriptions are combined, or joined or otherwise re-directed, based on directives from a server, into a single logical data stream.

3. A client-side architecture as in claim 1, wherein said mechanisms whereby, based on

directives from a server, subscriptions may be re-directed from one physical session to another, include a method, said method comprising the steps:

a) creating subscriber;

b) creating subscriber session;

c) subscribing to topic;

d) enabling consume;

e) processing enable consumemessage communicating with the server-side session through server and connection;

f) processing redirect consume message such that the redirect message from re-direct plug-in indicates to which server and context the consume request should be directed;

g) getting session recipient of the redirect message looks for existing session that satisfies the redirect message;

h) creating new physical session associated with logical session;

i) creating server-side session in response to new client-side session;

j) enabling consume such that the sessions are associated; and

k) enabling consume message causing delivery of message consistent with directives from the server.

4. A client-side architecture as in claim 3, wherein said mechanism whereby subscriptions may be re-directed from one physical session to another includes, in said method, the case where said redirect message is a Join Directive.

5. A client-side architecture as in claim 3, wherein said mechanism whereby subscriptions may be re-directed from one physical session to another includes, in said method, the case wherein said consume request is an “

enabled publish”

request.

7. A server-side routing mechanism that distributes subscription requests across multiple servers based on server load.

8. A server-side routing mechanism that distributes subscription requests across multiple servers based on the current or expected load of each server and the expected incremental load imposed by the subscription, where load includes the utilization of resources such as CPU, storage, and networks.

6. A server-side routing mechanism as in claim 8 that distributes subscription requests across multiple servers based on topic names.