Abstract: A computing system determines if an event has occurred. A first window is defined that includes a subset of a plurality of observation vectors modeled as an output of an autoregressive causal system. A magnitude adjustment vector is computed from a mean computed for a matrix of magnitude values that includes a column for each window of a plurality of windows. The first window is stored in a next column of the matrix of magnitude values. Each cell of the matrix of magnitude values includes an estimated power spectrum value for a respective window and a respective frequency. A second matrix of magnitude values is updated using the magnitude adjustment vector. Each cell of the second matrix of magnitude values includes an adjusted power spectrum value for the respective window and the respective frequency. A peak is detected from the next column of the second matrix of magnitude values.

Abstract: A computing device manages a router. A manager engine is instantiated based on a manager engine definition and instantiates a manager ESPE based on a created manager ESP model. A router configuration file is created based on mapping information read from the manager configuration file that describes connectivity between an event publishing source and a source window of the manager ESPE. A router engine is instantiated based on the created router configuration file. A connector is started to receive an event based on the router configuration file. The event is received in the source window of the manager ESPE processed based on the manager ESP model. A third computing device is selected by the router engine based on a usage metric received from each window of a plurality of windows defined by a remote ESP model configured to further process the processed event when it is received.

Abstract: A computing device manages a router. A manager engine is instantiated based on a manager engine definition and instantiates a manager ESPE based on a created manager ESP model. A router configuration file is created based on mapping information read from the manager configuration file that describes connectivity between an event publishing source and a source window of the manager ESPE. A router engine is instantiated based on the created router configuration file. A connector is started to receive an event based on the router configuration file. The event is received in the source window of the manager ESPE processed based on the manager ESP model. A third computing device is selected by the router engine based on a usage metric received from each window of a plurality of windows defined by a remote ESP model configured to further process the processed event when it is received.

Abstract: A computing device manages a router to route events between a plurality of computing device based on a manager configuration file. A manager engine is instantiated based on a manager engine definition and instantiates a manager ESPE based on a created manager ESP model. A router configuration file is created based on mapping information read from the manager configuration file that describes connectivity between an event publishing source and a source window of the manager ESPE. A router engine is instantiated based on the created router configuration file. A connector is started to receive an event based on the router configuration file. The event is received in the source window of the manager ESPE defined by the manager ESP model and processed based on the manager ESP model. A third computing device is selected by the router engine. The processed event is published to the third computing device.

Abstract: A computing device manages a router to route events between a plurality of computing device based on a manager configuration file. A manager engine is instantiated based on a manager engine definition and instantiates a manager ESPE based on a created manager ESP model. A router configuration file is created based on mapping information read from the manager configuration file that describes connectivity between an event publishing source and a source window of the manager ESPE. A router engine is instantiated based on the created router configuration file. A connector is started to receive an event based on the router configuration file. The event is received in the source window of the manager ESPE defined by the manager ESP model and processed based on the manager ESP model. A third computing device is selected by the router engine. The processed event is published to the third computing device.

Abstract: A first computing device manages a cluster of event stream processing (ESP) engines (ESPEs). A local ESP model is created based on information read from a manager configuration file that includes first connection information to connect to the second computing device and second connection information to connect the third computing device. An ESPE is instantiated on the first computing device based on the created local ESP model. The event block object is received from the second computing device in a first source window of the instantiated ESPE. A remote ESP model is deployed to a remote third computing device. The manager configuration file includes an indicator of the remote ESP model. The third computing device to receive the processed event block object is selected. The processed event block object is published to a second source window defined by the remote ESP model deployed to the third computing device.

Abstract: A method of acknowledging receipt of an event block object is provided. First connection information for connecting to an event stream processing (ESP) engine executing at a first computing device is received. A first connection to the ESP engine is established using the received first connection information. Second connection information for connecting to a publishing client executing at a second computing device is received. A second connection to the publishing client is established using the received second connection information, wherein the first connection differs from the second connection. An event block object is received from the ESP engine using the established first connection, wherein the event block object includes a unique identifier for the event block object. Successful processing of the event block object is determined.

Abstract: A first computing device manages a cluster of event stream processing (ESP) engines (ESPEs). A local ESP model is created based on information read from a manager configuration file that includes first connection information to connect to the second computing device and second connection information to connect the third computing device. An ESPE is instantiated on the first computing device based on the created local ESP model. The event block object is received from the second computing device in a first source window of the instantiated ESPE. A remote ESP model is deployed to a remote third computing device. The manager configuration file includes an indicator of the remote ESP model. The third computing device to receive the processed event block object is selected. The processed event block object is published to a second source window defined by the remote ESP model deployed to the third computing device.

Abstract: In a system, a first status of a first ESP engine (ESPE) executing at a first computing device is determined as newly active; a last published event block object identifier is determined as an identifier uniquely identifying a last event block object published to an out-messaging network device; a next event block object having an event block object identifier greater than the determined last published event block object identifier is selected from a first computer-readable medium; and the selected next event block object is published to the out-messaging network device. A first event block object is received from a second ESPE executing at a second computing device. A first status of the second ESPE is determined as standby by the second computing device. The received first event block object is stored by the second computing device in a second non-transitory computer-readable medium.

Abstract: In a system, a first status of a first ESP engine (ESPE) executing at a first computing device is determined as newly active; a last published event block object identifier is determined as an identifier uniquely identifying a last event block object published to an out-messaging network device; a next event block object having an event block object identifier greater than the determined last published event block object identifier is selected from a first computer-readable medium; and the selected next event block object is published to the out-messaging network device. A first event block object is received from a second ESPE executing at a second computing device. A first status of the second ESPE is determined as standby by the second computing device. The received first event block object is stored by the second computing device in a second non-transitory computer-readable medium.

Abstract: In a computing device supporting a failover in an event stream processing (ESP) system, an event block object is received. A first status of the computing device as active or standby is determined. When the first status is active, a second status of the computing device as newly active or not newly active is determined. Newly active is determined when the computing device is switched from a standby to an active status. When the second status is newly active, a last published event block object identifier that uniquely identifies a last published event block object is determined. A next event block object is selected from a non-transitory computer-readable medium accessible by the computing device. The next event block object has an event block object identifier that is greater than the determined last published event block object identifier. The selected next event block object is published to an out-messaging network device.

Abstract: A method of acknowledging receipt of an event block object is provided. First connection information for connecting to an event stream processing (ESP) engine executing at a first computing device is received. A first connection to the ESP engine is established using the received first connection information. Second connection information for connecting to a publishing client executing at a second computing device is received. A second connection to the publishing client is established using the received second connection information, wherein the first connection differs from the second connection. An event block object is received from the ESP engine using the established first connection, wherein the event block object includes a unique identifier for the event block object. Successful processing of the event block object is determined.

Abstract: A method is provided in one example embodiment and includes receiving at a network element having a binding table a packet that is part of a flow, the binding table having an entry corresponding to the flow, the entry mapping the flow to a first one of a plurality of endpoints and recognizing that a state of the first one of the plurality of endpoints at the first network element is not active. The method further includes, determining that the state of the first one of the plurality of endpoints at a second network element mated with the first network element and having a binding table similar to the binding table of the first network element is active. The method still further includes, directing the flow to the first one of the plurality of endpoints via the second network element.

Abstract: A method is provided in one example embodiment and includes receiving at a network element having a binding table a packet that is part of a flow, the binding table having an entry corresponding to the flow, the entry mapping the flow to a first one of a plurality of endpoints and recognizing that a state of the first one of the plurality of endpoints at the first network element is not active. The method further includes, determining that the state of the first one of the plurality of endpoints at a second network element mated with the first network element and having a binding table similar to the binding table of the first network element is active. The method still further includes, directing the flow to the first one of the plurality of endpoints via the second network element.

Abstract: A method is provided in one example embodiment and includes receiving a packet that is part of a flow, and identifying parameters within the packet for mapping the packet to a selected endpoint amongst a plurality of endpoints. The method further includes generating a first binding table that reflects the packet being associated with the selected endpoint, and identifying that the selected endpoint has changed state. An update message is communicated to a peer network element, the update message directing the peer network element to rebuild a peer binding table to reflect the changed state. In more specific embodiments, the binding tables include matching entries for the selected endpoint and the flow. One of the parameters can be a Signaling System Number 7 (SS7) parameter within the packet.

Abstract: AVoice over IP network, having multiple application server processes (ASPs) and at least one signaling gateway, communicates with switched circuit network nodes using a prescribed point code. The ASPs are arranged into ASP groups, each ASP group identifying the ASPs configured for processing prescribed message signaling unit (MSU) types. The signaling gateway determines a congestion level for each ASP group. Upon receiving an SS7 message specifying the prescribed point code as the destination point code and carrying a MSU, the signaling gateway selects one of the ASP groups based on identifying a matching MSU type. If the signaling gateway determines that the priority of the MSU is less than the determined congestion level for the ASP group, the signaling gateway drops the MSU and sends back a Transfer Controlled message to the originating signaling node.