NMS with multi-server change requests processing
First Claim
1. In a communication network of the type having a master database and a plurality of local databases at respective network nodes, an event processing system (EPS) comprising:
- a message processing client for placing a plurality of events sequentially in a plurality of event queues, an event queue per node;
a plurality of message processing servers, one server for processing at a given time an event from a particular event queue relating to a particular node, generating a certain change request for a certain event and transmitting said certain change request to a specified database; and
a dispatcher for selecting said one server based on availability of said message processing servers at said given time, so that no other server of said plurality of message processing servers processes another event from said particular event queue at said given time.
10 Assignments
0 Petitions
Accused Products
Abstract
An event processing system performs quickly processing of events in a communication network. The system comprises a client process that controls the sequencing of event processing, a plurality of servers that process the events with the help of a shared object library and a dispatcher that selects an available server so that no two servers process events from the same event queue at any given time. The client time-stamps the events and organizes them into event queues per node, using a node identification. An outstanding queue tracks the current events being processed for a node based on a message ID that is returned by the dispatcher when an event is sent to a server. Also, an overflow queue tracks the sequence of nodes to be serviced after a maximum outstanding limit of events being processed at a given time has been reached.
-
Citations
32 Claims
-
1. In a communication network of the type having a master database and a plurality of local databases at respective network nodes, an event processing system (EPS) comprising:
-
a message processing client for placing a plurality of events sequentially in a plurality of event queues, an event queue per node; a plurality of message processing servers, one server for processing at a given time an event from a particular event queue relating to a particular node, generating a certain change request for a certain event and transmitting said certain change request to a specified database; and a dispatcher for selecting said one server based on availability of said message processing servers at said given time, so that no other server of said plurality of message processing servers processes another event from said particular event queue at said given time. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18)
-
-
19. In a communication network of the type having a master database and a plurality of local databases at respective network nodes, a method of processing a plurality of database events comprising the steps of:
-
a) maintaining a plurality of event queues at a message processing client, a particular event queue being associated to a particular network node; b) dispatching said events from each of said event queues to a plurality of message processing servers; c) processing simultaneously said events at said message processing servers, one server for processing a certain event from said particular event queue, while no other server of said plurality of message processing servers processes another event from said particular event queue during the time said one server processes said event; and wherein said step b) comprises; selecting said one server based on the availability of said message processing servers; checking if all servers that are currently processing events do not process another event from said particular event queue; transmitting said certain event from said particular event queue to said one server for processing; and freeing said one server for processing another event from any of said plurality of event queues once said certain event has been processed. - View Dependent Claims (20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32)
-
Specification