Dispatcher configurable linking of software elements

• US 20020021774A1
• Filed: 12/19/2000
• Published: 02/21/2002
• Est. Priority Date: 03/27/2000
• Status: Active Grant

• Current Assignee: Unify Patente GmbH & Co. KG (Atos SE)
• Original Assignee: Siemens Communications Incorporated (Siemens AG)
• Inventors: Korpi, Markku, Fieremans, Geert, Grosberg, Mark, Cripe, Jeff, Gilbert, Leroy, Cross, Kenton, Callaghan, Robert, Howe, Wyatt, Butcher, Kristin
• Granted Patent: US 7,496,924 B2
• Time in Patent Office: Days
• US Class Current: 375/354
• CPC Class Codes: H04Q 2213/1305 Software aspects
• CPC Class Codes: H04Q 2213/13103 Memory
• CPC Class Codes: H04Q 2213/13109 Initializing, personal profile
• CPC Class Codes: H04Q 2213/13376 Information service, downloading of information, 0800/0900 services
• CPC Class Codes: H04Q 2213/13396 Signaling in general, in-band signalling
• CPC Class Codes: H04Q 3/54516 Initialization, software or data downloading G06F9/445 takes precedence

Abstract

A telecommunications system having a software dispatcher is provided for delivering messages between dispatcher clients, i.e., software subsystems that may be in the same process, a different process, or on a different machine. The dispatcher manages a pool of threads to balance the workload. The dispatcher can process both synchronous and asynchronous messages by dispatching the message to all registered subsystems in order of their registered priority.

Claims

1. A system, comprising:

a software dispatcher adapted to maintain a list of message receivers; and

a plurality of message receivers, said message receivers adapted to identify to said software dispatcher particular messages for receiving;

said software dispatcher adapted to send messages synchronously and asynchronously.

2. A system in accordance with claim 1, wherein said software dispatcher is adapted to save asynchronous messages for later transmission in one or more logical message queues.

3. A system in accordance with claim 2, wherein messages are dispatched in order of their priority.

4. A system in accordance with claim 2, said messages being sent as flexible message parameters comprising name, type, and value fields.

5. A system in accordance with claim 4, wherein said value field can comprise another flexible message parameter.

6. A system in accordance with claim 1, wherein said software dispatcher maintains said list as a list of unique integers identifying which receivers are to receive particular messages.

7. A method, comprising:

maintaining a list of message receivers at a software dispatcher, said list comprising a list of integers identifying which receivers are to receive particular messages; and

dispatching messages to said message receivers synchronously and asynchronously.

8. A method in accordance with claim 7, said asynchronously dispatching messages comprising saving asynchronous messages for later transmission in one or more logical message queues.

9. A method in accordance with claim 8, comprising dispatching messages in order of priority.

10. A method in accordance with claim 9, said dispatching messages comprising dispatching messages as flexible message parameters comprising name, type, and value fields.

11. A method in accordance with claim 10, wherein said value field can comprise another flexible message parameter.