System and method for distributed call processing using a distributed trunk idle list

• US 6,862,453 B2
• Filed: 12/31/2001
• Issued: 03/01/2005
• Est. Priority Date: 12/31/2001
• Status: Expired due to Fees

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Collins, David Allan
• Primary Examiner(s): Trost, William
• Assistant Examiner(s): Le, Danh C
• Application Number:
  US10/039,186
• Publication Number:
  US 20030125032A1
• Time in Patent Office: 1,156 Days
• Field of Search: 455/453, 455/450, 455/426.1, 455/560, 455/452.2, 370/229, 370/400, 370/410, 370/244, 379/242, 379/221.03, 379/221.04, 379/221.07
• US Class Current: 455/453
• CPC Class Codes: H04M 3/367 Traffic or load control
• CPC Class Codes: H04W 88/14 Backbone network devices

Abstract

A controller that monitors usage status of trunk lines associated with a switch that operates to handle call connections between calling devices and called devices on trunk lines associated therewith. An exemplary controller comprises N call application nodes capable of executing trunk idle list server applications that allocate ones of the trunk lines to the call connections, wherein a first trunk idle list server application is executed on a first call application node and is associated with a second trunk idle list server application executed on a separate second call application node. The first and second trunk idle list server applications thereby form a first load sharing group server application, that operates to receive a trunk line allocation request from a call process being executed within the switch and selects either the first or second trunk idle list server application to allocate a trunk line to a call connection associated with the trunk line allocation request according to a load distribution algorithm.

Claims

1. A controller for monitoring usage status of trunk lines associated with a switch, said switch capable of handling call connections between calling devices and called devices on a plurality of trunk lines associated with said switch, said controller comprising N call application nodes capable of executing a plurality of trunk idle list server applications that allocate ones of said trunk lines to said call connections, wherein a first trunk idle list server application is executed on a first one of said N call application nodes and is associated with a second trunk idle list server application executed on a second one of said N call application nodes separate from said first call application node, said first and second trunk idle list server applications thereby forming a load sharing group server application, wherein said load sharing group server application receives a trunk line allocation request from a call process being executed in said switch and selects one of said first and second trunk idle list server applications to allocate a trunk line to a call connection associated with said trunk line allocation request according to a load distribution algorithm.

2. The controller as set forth in claim 1 wherein said first trunk idle list server application allocates trunk lines from at least one trunk group associated with said first trunk idle list server application and said second trunk idle list server application allocates trunk lines from at least one trunk group associated with said second trunk idle list server application.

3. The controller as set forth in claim 2 wherein said second trunk idle list server application comprises a second primary-backup group server application, wherein said second primary-backup group server application comprises a second primary trunk idle list server application executed on said second call application node and a second backup trunk idle list server application associated with said second primary trunk idle list server application.

4. The controller as set forth in claim 3 wherein state information associated with said second primary call process is mirrored to said second backup call process associated with said second primary call process.

5. The controller as set forth in claim 4 wherein said second backup trunk idle list server application resides on said second call application node.

6. The controller as set forth in claim 5 wherein said second backup trunk idle list server application resides on a call application node separate from said second call application node.

7. The controller as set forth in claim 2 wherein said load distribution algorithm distributes new trunk line allocation requests to said first and second trunk idle list server applications according to a trunk group associated with said trunk line allocation requests.

8. The controller as set forth in claim 2 wherein said first trunk idle server application comprises a first primary-backup group server application, wherein said first primary-backup group server application comprises a first primary trunk idle list server application executed on said first call application node and a first backup trunk idle list server application associated with said first primary trunk idle list server application.

9. The controller as set forth in claim 8 wherein trunk line state information associated with said first primary trunk idle list server application is mirrored to said first backup trunk idle list server application associated with said first primary trunk idle list server application.

10. The controller as set forth in claim 9 wherein said first backup trunk idle list server application resides on said first call application node.

11. The controller as set forth in claim 9 wherein said first backup trunk idle list server application resides on a call application node separate from said first call application node.

12. A wireless network comprising:

a plurality of base stations capable of communicating with a plurality of mobile stations in a coverage are of said wireless network; and

a mobile switching center coupled to said plurality of base stations and to a public switched telephone network by a plurality of trunk lines, wherein said mobile switching center is capable of handling call connections between calling devices and called devices on said plurality of trunk lines, said mobile switching center comprising;

a main processing unit capable of executing call process client applications, wherein each of said call process client applications is associated with one of said call connections; and

a controller comprising N call application nodes capable of executing a plurality of trunk idle list server applications that allocate ones of said trunk lines to said call connections, wherein a first trunk idle list server application is executed on a first one of said N call application nodes and is associated with a second trunk idle list server application executed on a second one of said N call application nodes separate from said first call application node, said first and second trunk idle list server applications thereby forming a load sharing group server application, wherein said load sharing group server application receives a trunk line allocation request from a call process being executed in said switch and selects one of said first and second trunk idle list server applications to allocate a trunk line to a call connection associated with said trunk line allocation request according to a load distribution algorithm.

13. The wireless network as set forth in claim 12 wherein said first trunk idle list server application allocates trunk lines from at least one trunk group associated with said first trunk idle list server application and said second trunk idle list server application allocates trunk lines from at least one trunk group associated with said second trunk idle list server application.

14. The wireless network as set forth in claim 13 wherein said second trunk idle list server application comprises a second primary-backup group server application, wherein said second primary-backup group server application comprises a second primary trunk idle list server application executed on said second call application node and a second backup trunk idle list server application associated with said second primary trunk idle list server application.

15. The wireless network as set forth in claim 14 wherein state information associated with said second primary call process is mirrored to said second backup call process associated with said second primary call process.

16. The wireless network as set forth in claim 15 wherein said second backup trunk idle list server application resides on said second call application node.

17. The wireless network as set forth in claim 16 wherein said second backup trunk idle list server application resides on a call application node separate from said second call application node.

18. The wireless network as set forth in claim 13 wherein said load distribution algorithm distributes new trunk line allocation requests to said first and second trunk idle list server applications according to a trunk group associated with said trunk line allocation requests.

19. The wireless network as set forth in claim 13 wherein said first trunk idle server application comprises a first primary-backup group server application, wherein said first primary-backup group server application comprises a first primary trunk idle list server application executed on said first call application node and a first backup trunk idle list server application associated with said first primary trunk idle list server application.

20. The wireless network as set forth in claim 19 wherein trunk line state information associated with said first primary trunk idle list server application is mirrored to said first backup trunk idle list server application associated with said first primary trunk idle list server application.

21. The wireless network as set forth in claim 20 wherein said first backup trunk idle list server application resides on said first call application node.

22. The wireless network as set forth in claim 20 wherein said first backup trunk idle list server application resides on a call application node separate from said first call application node.