Network Publish/Subscribe System Incorporating Web Services Network Routing Architecture

• US 20080294794A1
• Filed: 02/01/2008
• Published: 11/27/2008
• Est. Priority Date: 01/24/2003
• Status: Active Grant

• Current Assignee: Akana, Inc. (Perforce Software Incorporated)
• Original Assignee: Blue Titan Software, Inc. (Perforce Software Incorporated)
• Inventors: Martinez, Frank, Darugar, Parand Tony, Toth, Paul Keith
• Granted Patent: US 7,788,403 B2
• Time in Patent Office: Days
• US Class Current: 709/238
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

Methods, apparatuses, and systems facilitating the deployment, configuration and maintenance of publication/subscription systems within the context of Web service networks. In one embodiment, the present invention provides Web services network system that presents a topic as a routing entity and includes functionality facilitating topic creation, subscription and publication in a manner consistent with the basic modes of Web services development and deployment, allowing such tasks to be approached in an intuitive, cost-effective and manageable manner. In a preferred embodiment, the publication/subscription system functionality according to the present invention is integrated into a distributed Web services network architecture as more fully described below. The Web services network architecture and integrated publication/subscription system according to the present invention can be implemented across any suitable computer network, including a local area network, an intranet or the Internet.

Claims

1-30. -30. (canceled)

31. An apparatus enabling deployment of a publish/subscribe system within the context of a Web services network, comprising:

a local routing table operable to store routing entries allowing for the routing of service action requests and responses over a computer network;

wherein at least one routing entry in the routing table corresponds to a topic routing entity and includes information allowing for publication of messages to the topic and the dissemination of the messages to at least one subscriber associated with the topic;

a Web services network routing module operative to

receive service action requests from remote hosts, wherein one or more of the service action requests identify a topic and include a message published to the topic;

access the routing table to identify subscribers to the topic,

transmit the messages to at least one subscriber;

transmit, responsive to a service action request requiring a routing entry not contained in the local routing table, a routing entity request to a parent routing node; and

receive a response from the parent routing node, wherein the response causes the Web services network module to add a routing entry included in the response to the local routing table.

32. An apparatus enabling deployment of a publish/subscribe system within the context of a Web services network, comprising:

a memory operative to store a first routing table, the first routing table including routing entries allowing for the routing of service action requests and responses across the computer network;

wherein at least one routing entry in the first routing table corresponds to a topic routing entity and includes information allowing for publication of messages to the topic and the dissemination of the messages to at least one subscriber associated with the topic; and

a parent routing node module operative to;

receive, responsive to a service action request requiring a routing entry not contained in a local routing table of a child node, a routing entity request from a child routing node; and

transmit a response to the child routing node, wherein the response causes the child routing node to add a routing entry included in the response to the local routing table of the child routing node in response to a routing entity request.

33. The apparatus of claim 32 wherein the parent routing node module is operative to receive and process updates to routing entries in the first routing table;

and wherein, in response to the updates, the parent routing node module is operative to update the local routing table(s) of one or more child nodes.

34. The apparatus of claim 32 wherein the parent routing node module is operative to route service action requests and service action responses across the computer network;

and wherein the parent node is further operative to access the first routing table, process messages published to a topic and transmit the messages to at least one subscriber associated with the topic across the computer network.

35. The apparatus of claim 32 wherein the parent node maintains a routing matrix in the memory, wherein the routing matrix facilitates maintenance of the local routing table(s) of the one or more child routing nodes.

36. The apparatus of claim 35 wherein the routing matrix facilitates identification of out-of-date routing entries in the local routing table(s) of the child routing nodes.

37. The apparatus of claim 36 wherein the routing matrix contains parent node update stamps for corresponding routing entries in the first routing table;

and wherein, for each child routing node, the routing matrix contains a routing node update stamp for each routing entry in the local routing table.

38. The apparatus of claim 36 wherein the parent routing node module is operative to update a routing entry in the local routing table of a chile routing node based on a comparison of the corresponding parent node update stamp and child routing node update stamp.

39. The apparatus of claim 32 wherein the local routing table is a subset of the first routing table.

40. The apparatus of claim 32 further comprising a Web services network management application providing a user interface facilitating configuration of the parent routing node module and one or more child routing nodes.

41. The apparatus of claim 40 wherein the Web services network management application transmits service action requests operative to change the configuration of the parent routing node module and/or one or more child routing nodes.

42. The apparatus of claim 32 wherein the parent routing node module includes platform services functionality allowing for configuration of the parent routing node module and one or more child routing nodes;

and wherein the platform services functionality is presented as a Web service accessible via a service action request.

43. The apparatus of claim 32 wherein the parent routing node module is operative to receive commands from a network management application to create a topic routing entity and instantiate the topic routing entity in the first routing table.

44. The apparatus of claim 43 wherein the parent routing node module is operative to receive commands from a network management application to create subscriptions to the topic and to modify of the topic routing entity in the routing table to effect the subscriptions.

45. The apparatus of claim 44 wherein the topic routing entity further includes a publisher access control list defining the publishing nodes authorized to publish messages to the topic.

46. The apparatus of claim 44 wherein the topic routing entity further includes a subscriber access control list defining the subscriber nodes authorized to subscribe to the topic.

47. The apparatus of claim 32 wherein the parent routing node module hosts at least one internal service action directed to the modification of topic routing entities in the routing table.