Systems and methods for network virtualization
First Claim
1. An end-to-end publish/subscription messaging system with a middleware architecture, comprising:
- at least one or more than one messaging appliance comprising a processor and a memory, each messaging appliance being configured for receiving and routing to receive and route messages; and
an interconnect utilizing channel-based messaging that routes messages over a first messaging layer based on at least one channel, each channel mapped to a subscription topic, each channel assigned to a communication pathway of a second messaging layer; and
a provisioning and management system linked via the interconnect and configured for exchanging administrative messages with each messaging appliance,wherein messages are routed directly from sender to receiver with each messaging appliance configured to coordinate channel capacity among appliances.
2 Assignments
0 Petitions
Accused Products
Abstract
Message publish/subscribe systems are required to process high message volumes with reduced latency and performance bottlenecks. The end-to-end middleware architecture proposed by the present invention is designed for high-volume, low-latency messaging by, among other things, reducing intermediary hops with neighbor-based routing, introducing efficient native-to-external and external-to-native protocol conversions, monitoring system performance, including latency, in real time, employing topic-based and channel-based message communications, and dynamically optimizing system interconnect configurations and message transmission protocols.
-
Citations
44 Claims
-
1. An end-to-end publish/subscription messaging system with a middleware architecture, comprising:
-
at least one or more than one messaging appliance comprising a processor and a memory, each messaging appliance being configured for receiving and routing to receive and route messages; and an interconnect utilizing channel-based messaging that routes messages over a first messaging layer based on at least one channel, each channel mapped to a subscription topic, each channel assigned to a communication pathway of a second messaging layer; and a provisioning and management system linked via the interconnect and configured for exchanging administrative messages with each messaging appliance, wherein messages are routed directly from sender to receiver with each messaging appliance configured to coordinate channel capacity among appliances. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39)
-
-
40. A system with a publish/subscribe middleware architecture, comprising:
-
one or more namespace domains; and if more than one space domain exists, a physical domain interconnect medium for connecting between at least two of the namespace domains, wherein each namespace domains includes; at least one or more than one messaging appliance comprising a processor and a memory, each messaging appliance being configured to receive and route for receiving and routing messages; an interconnect utilizing channel-based messaging that routes messages over a first messaging layer based on at least one channel, each channel mapped to a subscription topic, each channel assigned to a communication pathway of a second messaging layer; and a provisioning and management system linked via the interconnect and configured for exchanging administrative messages with each messaging appliance, wherein messages are routed directly from sender to receiver with each messaging appliance configured to coordinate channel capacity among appliances.
-
-
41. An enterprise system with a publish/subscribe middleware architecture, comprising:
-
a market data delivery infrastructure having at least one or more messaging appliances for receiving and routing market data messages; a market order routing infrastructure having at least one or more messaging appliances for receiving and routing to receive and route transaction order messages; and an intermediate infrastructure in communication link with the market data delivery and market order routing infrastructures, respectively, wherein the intermediary infrastructure includes; at least one or more than one messaging appliance comprising a processor and a memory, each messaging appliance being configured for receiving and routing the market data and transaction order messages; and an interconnect utilizing channel-based messaging that routes messages over a first messaging layer based on at least one channel, each channel mapped to a subscription topic, each channel assigned to a communication pathway of a second messaging layer, a provisioning and management system linked via the interconnect and configured for exchanging administrative messages with each messaging appliance, including the messaging appliances in the market data delivery and market order routing infrastructures; wherein messages are routed directly from sender to receiver with each messaging appliance configured to coordinate channel capacity among appliances. - View Dependent Claims (42, 43, 44)
-
Specification