Asynchronous Messaging Using A Node Specialization Architecture in the Dynamic Routing Network

• US 20130060895A1
• Filed: 09/14/2012
• Published: 03/07/2013
• Est. Priority Date: 12/18/2000
• Status: Active Grant

• Current Assignee: Intellectual Ventures I LLC (Intellectual Ventures LLC)
• Original Assignee: Shaw Parsing LLC (Intellectual Ventures LLC)
• Inventors: Rumelhart, Karl E., TUTTLE, Timothy
• Granted Patent: US 9,071,648 B2
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• 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/1014 based on the content of a request
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A network routes update messages containing updates to properties of live objects from input sources to clients having the objects. When the clients receive live objects, the clients identify the object IDs associated with the objects and register the object IDs with the routing network. The routing network is adapted to selectively send update messages to nodes in the network and the nodes forward the messages to the clients. One implementation uses a hierarchy of registries to indicate which nodes and clients receive which update messages. Another implementation assigns update messages to one or more of N categories and nodes to one or more of M types, and the gateways maintain mapping between categories and types. To ensure that clients receive all of the update messages for which they register, the clients connect to client proxies that in turn connect to at least one node of each type.

Claims

1. A method comprising:

providing a live object to a client device; and

sending, using a processing device of an input source, different from the client device, an update message to a routing network identifying the live object and containing update data to update the live object at the client device,

wherein in response to determining that the client device is registered to receive update data for the live object, causing;

a category of the update message to be identified based on the input source,

a node type associated with the category be determined,

the update message to be routed from the gateway device to a node having the node type at the routing network, and

the node to route the update message to the client device.

2. The method of claim 1, further comprising:

causing the node to extract an object identifier (ID) from the update message, to establish a connection with the client, and to determine if the client has registered for updates of the live object based on the object ID.

3. The method of claim 2, further comprising:

causing the node to determine a client proxy with which the client communicates;

causing the node to route the update message to the client proxy; and

causing the client proxy to route the update message to the client to determine the connection.

4. The method of claim 3, further comprising causing the node to maintain client registration information concerning the client connection.

5. The method of claim 3, further comprising causing the node to maintain client registration information concerning the client connection at the client proxy.

6. The method of claim 1, wherein the live object is configured to cause the client device to register with a client proxy of the routing network.

7. The method of claim 1, wherein the live object is configured to cause the client device to register with the node of the routing network.

8. The method of claim 1, further comprising:

causing the client device to process the update message and to update a property of the live object.

9. The method of claim 8, wherein the property of the live object has:

a direct effect on a visual representation of the live object in a data representation, an effect on an internal aspect of the live object; and

no effect on the visual representation of the live object in the data representation, or

a direct effect on one aspect of the visual representation of the live object in the data representation and has no effect on other aspect of the visual representation of the live object in the data representation.

10. An apparatus comprising:

an input source arranged to provide;

a live object to a client device, different from the input source; and

an update message to a routing network identifying the live object and containing update data for updating the live object,

wherein the routing network is configured to identify a category of the update message based on the input source, determine a node type associated with the category, and to route the update message from a gateway device at the routing network to a node having the node type at the routing network, and

wherein the node is configured to route the update message to the client device if the client device is registered to receive the update data for the live object.

11. The apparatus of claim 10, wherein the node is further configured to:

extract an object identifier (ID) from the update message,

establish a connection with the client, and

determine if the client has registered for updates of the live object based on the object ID.

12. The apparatus of claim 11, wherein:

the node is further configured to determine at least one client proxy with which the client communicates, to route the update message to the client proxy; and

the client proxy is configured to route the update message to the client to determine the connection.

13. The apparatus of claim 12, wherein the node is further configured to maintain client registration information concerning the client connection.

14. The apparatus of claim 12, wherein the node is further configured to maintain client registration information concerning the client connection at the client proxy.

15. The apparatus of claim 10, wherein the live object is configured to cause the client device to register with a client proxy of the routing network.

16. The apparatus of claim 10, wherein the live object is configured to cause the client device to register with the node of the routing network.

17. The apparatus of claim 10, wherein the client device is configured to process the update message and to update a property of the live object.

18. The apparatus of claim 17, wherein the property of the live object has a direct effect on a visual representation of the live object in a data representation, has an effect on an internal aspect of the live object and has no effect on the visual representation of the live object in the data representation, or has a direct effect on one aspect of the visual representation of the live object in the data representation and has no effect on other aspect of the visual representation of the live object in the data representation.

19. A non-transitory computer readable storage medium having instructions stored thereon, the instructions comprising:

instructions for providing a live object to a client device; and

instructions for providing an update message from an input source, different from the client device, to a routing network identifying the live object and containing update data for updating the live object at the client device,

wherein a category of the update message is identified based on the input source, a node type associated with the category is determined, and the update message is routed from a gateway device at the routing network to a node having the node type at the routing network, wherein the update message is routed from the node to the client device in response to a determination that the client device is registered to receive the update data for the live object.

20. The non-transitory computer readable storage medium of claim 19, wherein the node extracts an object identifier (ID) from the update message, establishes a connection with the client, and determines if the client has registered for updates of the live object based on the object ID.

21. The non-transitory computer readable storage medium of claim 20, wherein the node determines at least one client proxy with which the client communicates, routes the update message to the client proxy, and the client proxy routes the update message to the client to determine the connection.

22. The non-transitory computer readable storage medium of claim 21, further comprising causing the node to maintain client registration information concerning the client connection.

23. The non-transitory computer readable storage medium of claim 21, further comprising causing the node to maintain client registration information concerning the client connection at the client proxy.

24. The non-transitory computer readable storage medium of claim 19, wherein the live object causes the client device to register with a client proxy of the routing network.

25. The non-transitory computer readable storage medium of claim 19, wherein the live object causes the client device to register with the node of the routing network.

26. The non-transitory computer readable storage medium of claim 19, wherein the client device processes the update message and updates a property of the live object.

27. The non-transitory computer readable storage medium of claim 26, wherein the property of the live object has a direct effect on a visual representation of the live object in a data representation, has an effect on an internal aspect of the live object and has no effect on the visual representation of the live object in the data representation, or has a direct effect on one aspect of the visual representation of the live object in the data representation and has no effect on other aspect of the visual representation of the live object in the data representation.