Architecture for balancing workload

• US 8,830,831 B1
• Filed: 01/04/2010
• Issued: 09/09/2014
• Est. Priority Date: 10/09/2003
• Status: Active Grant

• Current Assignee: Netcracker Technology Solutions Inc (NEC Corporation)
• Original Assignee: Netcracker Technology Solutions Inc (NEC Corporation)
• Inventors: Claridge, Philip Geoffrey, Shusta, Thomas Joseph, Clubb, Ian James, Miller, Jeffrey M.
• Primary Examiner(s): Ngo, Ricky
• Assistant Examiner(s): Samuel, Dewanda
• Application Number:
  US12/651,720
• Time in Patent Office: 1,709 Days
• Field of Search: 705/14.5, 370/231, 370/235, 370/389, 370/392, 370/351
• US Class Current: 370/231
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1403 Architecture for metering, charging or billing
• CPC Class Codes: H04L 12/1453 Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network

Abstract

Embodiments of an invention are disclosed which provide a framework to transition and re-partition information for event processing and downstream processing.

Claims

1. A computerized architecture for processing events comprising:

a first router;

a set of processors comprising two or more processors; and

at least one router/multiplexer;

wherein said first router is configured with a set of computer-executable instructions to determine which of said processors should process an event based upon a consumer identifier;

wherein said first router is configured to send an event to said determined processor;

wherein said determined processor is configured to initially process said event;

wherein said determined processor is further configured to embed a set of tags in a set of event data and to send said set of event data relating to said event to said router/multiplexer; and

wherein said router/multiplexer parses said set of event data and is configured to reorganize said set of event data according to an account identifier for further processing, wherein said router/multiplexer utilizes said set of tags to determine where to send said set of event data for further processing.

2. A computerized architecture as claimed in claim 1 wherein each of said processors is further configured to:

send said set of event data relating to said event to said router/multiplexer in a file further comprising a header;

embed said set of tags in said header;

wherein said router/multiplexer is configured to utilize said set of tags in said header to determine where to send said set of event data for further processing.

3. A computerized architecture as claimed in claim 1 wherein each of said processors from said set of processors are mapped to a particular router/multiplexer from said at least one router/multiplexer.

4. A computerized architecture for processing events as claimed in claim 1 wherein said router/multiplexer is configured to reorganize said set of event data for further processing by creating a file comprising a subset of said set of event data.

5. A computerized architecture for processing events comprising:

a first router;

a set of processors comprising two or more processors; and

at least one router/multiplexer;

wherein said first router is configured with a set of computer-executable instructions to determine which of said processors should process an event based upon a consumer identifier;

wherein said first router is configured to send an event to said determined processor;

wherein said determined processor is configured to initially process said event;

wherein said determined processor is further configured to embed a set of tags in a set of event data and to send said set of event data relating to said event to said router/multiplexer;

wherein said router/multiplexer parses said event data to create a file comprising a subset of said set of event data for additional processing, wherein said router/multiplexer utilizes said set of tags to determine where to send said subset of said set of event data for additional processing; and

wherein said router/multiplexer is configured to reorganize said subset of said set of event data according to an account identifier.

6. A computerized architecture as claimed in claim 5 wherein said set of tags designate said subset of said set of event data for evaluation by a settlement system.

7. A computerized architecture as claimed in claim 5 wherein said set of tags designate said subset of said set of event data for evaluation by a trend analysis system.

8. A computerized architecture as claimed in claim 5 wherein said router/multiplexer creates a plurality of said subsets.

9. A computerized architecture as claimed in claim 8 wherein an output stream is defined through an application programming interface and said determined processor is further configured to generate said output and send said output to said router/multiplexer.

10. A computerized method for processing events comprising the steps of

receiving an event on a first router;

identifying a consumer associated with said event;

determining a processor from a set of two or more processors that is associated with said identified consumer;

sending said event to said processor;

initially processing said event on said processor;

generating a set of event data related to said initial processing of said event;

sending said set of event data to said router/multiplexer;

parsing said event data on said router/multiplexer; and

reorganizing said event data for further processing on said router/multiplexer;

wherein said initial processing step includes checking a balance stored on a logical wallet on said processor to determine if said event may be approved and said reorganizing step includes reorganizing said event data for further processing on said router/multiplexer based on an account identifier associated with said identified consumer.

11. A computerized method for processing events comprising the steps of:

receiving an event on a first router;

identifying a consumer associated with said event;

determining a processor from a set of two or more processors that is associated with said identified consumer;

sending said event to said processor;

checking a balance stored on a logical wallet on said processor to determine if said event may be approved;

generating a set of event data related to said event on said processor;

defining, through an application programming interface, a subset of said event data;

creating at least one subset of said event data with a set of embedded tags indicating an external process;

sending said subset to said router/multiplexer;

parsing said subset on said router/multiplexer to determine said external process; and

sending said subset to said external process.