VOICEMAIL NOTIFICATION SERVER LOAD BALANCING

• US 20100322393A1
• Filed: 06/18/2009
• Published: 12/23/2010
• Est. Priority Date: 06/18/2009
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Xia, Wei, Jin, Zhiying, Hao, Jianxiu, Honma, Gerald, Kagawa, Jo Ann
• Granted Patent: US 8,411,826 B2
• Time in Patent Office: Days
• US Class Current: 379/88.12
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/101 based on network conditions
• CPC Class Codes: H04M 2201/38 Displays
• CPC Class Codes: H04M 3/537 Arrangements for indicating the presence of a recorded message , whereby the presence information might include a preview or summary of the message

Abstract

A device receives, from a management server, an optimal number of threads, generates a dynamic thread based on the optimal number of threads, and retrieves, from a message store, a message based on the dynamic thread and when the message store is not empty. The device receives a binding from a voicemail server associated with a voicemail user, generates a notification based on the retrieved message and based on the binding, and provides the notification to a user device associated with the voicemail user.

Claims

1. A computing device-implemented method, comprising:

receiving, from a management server and by the computing device, an optimal number of threads;

generating, by the computing device, a dynamic thread based on the optimal number of threads;

retrieving, from a message store and by the computing device, a message based on the dynamic thread and when the message store is not empty;

receiving, by the computing device, a binding from a voicemail server associated with a voicemail user;

generating, by the computing device, a notification based on the retrieved message and based on the binding; and

providing, by the computing device, the notification to a user device associated with the voicemail user.

2. The computing device-implemented method of claim 1, further comprising:

receiving, from the voicemail server, a plurality of messages associated with the voicemail user; and

providing, to the message store, the plurality of messages for storage in the message store.

3. The computing device-implemented method of claim 1, where generating the dynamic thread comprises:

providing, to the management server, information associated with a load of the computing device;

providing, to the management server, information associated with connections between the computing device and the message store;

receiving, from the management server, an instruction to generate the dynamic thread when one or more of the load is less than or equal to a particular load, a number of the connections is less than or equal to a particular number, or a size of the message store is greater than or equal to a particular size; and

generating the dynamic thread when the instruction is received.

4. The computing device-implemented method of claim 1, where generating the dynamic thread comprises:

providing, to the management server, information associated with a load of the computing device;

providing, to the management server, information associated with connections between the computing device and the message store;

receiving, from the management server, an instruction to prevent generation of the dynamic thread when one or more of the load is greater than or equal to a particular load, a number of the connections is greater than or equal to a particular number, or a size of the message store is less than or equal to a particular size; and

preventing generation of the dynamic thread when the instruction is received.

5. The computing device-implemented method of claim 1, where retrieving a message comprises:

checking a size of the message store with a particular frequency;

receiving, based on the check, information associated with the size of the message store; and

retrieving, from the message store, the message when the size information indicates that the message store is not empty.

6. The computing device-implemented method of claim 5, further comprising:

placing the dynamic thread in an idle mode when the size information indicates that the message store is empty; and

reducing the particular frequency for checking the size of the message store when the dynamic thread is in the idle mode.

7. The computing device-implemented method of claim 5, further comprising:

placing the dynamic thread in an active mode when the size information indicates that the message store is not empty; and

waiting a particular amount of time before retrieving the message, from the message store, when the dynamic thread is in the active mode.

8. The computing device-implemented method of claim 1, where the computing device comprises a notification server.

9. The computing device-implemented method of claim 1, where the retrieved message comprises one or more of:

a new voicemail,

an unheard voicemail, or

a voicemail identifier.

10. A computing device-implemented method, comprising:

receiving, by the computing device, a load associated with a notification server;

receiving, by the computing device, a number of connections between the notification server and a message store;

receiving, by the computing device, a size associated with the message store;

determining, by the computing device, an optimal number of dynamic threads based on the load, the number of connections, and the size associated with the message store; and

providing, by the computing device, the optimal number of dynamic threads to the notification server, where the optimal number of dynamic threads enables the notification server to balance the load.

11. The computing device-implemented method of claim 10, where the computing device comprises a management server.

12. The computing device-implemented method of claim 10, where the notification server comprises a voicemail notification server that provides voicemail notifications to one or more voicemail users.

13. The computing device-implemented method of claim 10, where the message store comprises one or more storage devices that store information associated with voicemails.

14. A device, comprising:

a memory to store a plurality of instructions; and

a processor to execute instructions in the memory to;

receive, from a voicemail server associated with a voicemail user, a plurality of messages associated with the voicemail user,

provide, to a message store, the plurality of messages for storage in the message store,

receive, from a management server, an optimal number of threads,

generate a dynamic thread based on the optimal number of threads,

retrieve, from the message store, one of the plurality of messages based on the dynamic thread and when the message store is not empty,

receive a binding from the voicemail server,

generate a notification based on the retrieved message and based on the binding, and

provide the notification to a user device associated with the voicemail user.

15. The device of claim 14, where the processor is further to execute instructions in the memory to:

provide, to the management server, information associated with a load of the device, and

provide, to the management server, information associated with connections between the device and the message store.

16. The device of claim 15, where the processor is further to execute instructions in the memory to:

receive, from the management server, a first instruction to generate the dynamic thread when one or more of the load is less than or equal to a particular load, a number of the connections is less than or equal to a particular number, or a size of the message store is greater than or equal to a particular size,

generate the dynamic thread when the first instruction is received,

receive, from the management server, a second instruction to prevent generation of the dynamic thread when one or more of the load is greater than or equal to a particular load, a number of the connections is greater than or equal to a particular number, or a size of the message store is less than or equal to a particular size, and

prevent generation of the dynamic thread when the second instruction is received.

17. The device of claim 14, where the processor is further to execute instructions in the memory to:

check a size of the message store with a particular frequency,

receive, based on the check, information associated with the size of the message store, and

retrieve, from the message store, the one of the plurality of messages when the size information indicates that the message store is not empty.

18. The device of claim 17, where the processor is further to execute instructions in the memory to:

place the dynamic thread in an idle mode when the size information indicates that the message store is empty, and

reduce the particular frequency for checking the size of the message store when the dynamic thread is in the idle mode.

19. The device of claim 17, where the processor is further to execute instructions in the memory to:

place the dynamic thread in an active mode when the size information indicates that the message store is not empty, and

wait a particular amount of time before retrieving the one of the plurality of messages, from the message store, when the dynamic thread is in the active mode.

20. The device of claim 14, where the device comprises a voicemail notification server.

21. The device of claim 14, where the retrieved message comprises one or more of:

a new voicemail,

an unheard voicemail, or

a voicemail identifier.

23. The system of claim 21, where the notification server is further to:

receive, from the voicemail server, the plurality of messages, and

provide, to the message store, the plurality of messages for storage in the message store.

24. The system of claim 21, where the notification server is further to:

receive, from the management server, a first instruction to generate the dynamic thread when one or more of the load is less than or equal to a particular load, the number of connections is less than or equal to a particular number, or the size associated with the message store is greater than or equal to a particular size,

generate the dynamic thread when the first instruction is received,

receive, from the management server, a second instruction to prevent generation of the dynamic thread when one or more of the load is greater than or equal to a particular load, the number of connections is greater than or equal to a particular number, or the size associated with the message store is less than or equal to a particular size, and

prevent generation of the dynamic thread when the second instruction is received.

25. The system of claim 24, where the notification server is further to:

check the size associated with the message store with a particular frequency,

receive, based on the check, information associated with the size of the message store, and

retrieve, from the message store, the one of the plurality of messages when the size information indicates that the message store is not empty.

22. A system, comprising:

a message store to;

receive, from a notification server, a plurality of messages associated with a voicemail user, and

store the plurality of messages;

a management server to;

receive a load associated with the notification server,

receive a number of connections between the notification server and the message store,

receive a size associated with the message store,

determine an optimal number of threads based on the load, the number of connections, and the size associated with the message store, and

provide the optimal number of threads to the notification server; and

the notification server to;

receive, from the management server, the optimal number of threads,

generate a dynamic thread based on the optimal number of threads,

retrieve, from the message store, one of the plurality of messages based on the dynamic thread and when the message store is not empty,

receive a binding from a voicemail server associated with the voicemail user,

generate a notification based on the retrieved message and based on the binding, and

provide the notification to a user device associated with the voicemail user.