System and method for providing a subscriber database using group services in a telecommunication system

• US 6,917,819 B2
• Filed: 12/31/2001
• Issued: 07/12/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): Urban, Edward F.
• Assistant Examiner(s): CHOW, CHARLES CHIANG
• Application Number:
  US10/038,879
• Publication Number:
  US 20030125085A1
• Time in Patent Office: 1,289 Days
• Field of Search: 455/560, 455/550.1, 455/418, 455/424, 455/428, 455/433, 455/507, 455/554.1, 455/554.2, 455/533.1, 455/561, 455/556.1, 455/426.1, 455/426.2, 455/422.1, 709/224, 709/226, 709/245, 709/229, 709/203, 709/213, 709/100, 395/200.53, 395/200.56, 395/675, 395/674, 395/650, 395/200.59, 395/200.75, 395/822, 395/200.31, 395/700, 395/200.32, 395/200.48, 714/4, 379/57, 379/221, 379/222, 379/223, 379/309, 379/201.03, 379/229, 379/221.08, 379/352, 379/395.6
• US Class Current: 455/560
• CPC Class Codes: H04Q 2213/1302 Relay switches
• CPC Class Codes: H04Q 2213/1304 Coordinate switches, crossbar, 4/2 with relays, coupling field
• CPC Class Codes: H04Q 2213/1305 Software aspects
• CPC Class Codes: H04Q 2213/13098 Mobile subscriber
• CPC Class Codes: H04Q 2213/13103 Memory
• CPC Class Codes: H04Q 2213/13107 Control equipment for a part of the connection, distributed control, co-processing
• CPC Class Codes: H04Q 2213/13164 Traffic (registration, measurement,...)
• CPC Class Codes: H04Q 2213/13166 Fault prevention
• CPC Class Codes: H04Q 2213/13167 Redundant apparatus
• CPC Class Codes: H04Q 2213/13322 Integrated circuits
• CPC Class Codes: H04Q 2213/13396 Signaling in general, in-band signalling
• CPC Class Codes: H04W 24/04 Arrangements for maintaining operational condition
• CPC Class Codes: H04W 8/12 between location registers or mobility servers
• CPC Class Codes: H04W 88/14 Backbone network devices
• CPC Class Codes: H04W 88/16 Gateway arrangements

Abstract

A system for providing a subscriber database using group services in a telecommunication system. The system comprises a switch for executing call processing applications and N call application nodes for executing subscriber database server applications. A first subscriber database server application is executed on a first call application node and a second subscriber database server application is executed on a second call application node. The first and second subscriber database server applications form a subscriber database load sharing group server application. When a subscriber database service request is received, the subscriber database load sharing group server application selects one of the first and second subscriber database server applications to perform the subscriber database service request according to a load distribution algorithm.

Claims

1. A controller for providing a subscriber database 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, and said switch capable executing call processing applications, wherein each of said call processing applications is associated with one of said call connections, said controller comprising:

N call application nodes capable of executing a plurality of subscriber database server applications that connect a subscriber database to a call connection, wherein a first subscriber database server application is executed on a first one of said N call application nodes and is associated with a similar second subscriber database server application executed on a second one of said N call application nodes separate from said first call application node, said first and second subscriber database server applications thereby forming a subscriber database load sharing group server application, and

wherein said each call processing application sends a subscriber database service request to said subscriber database load sharing group server application and said subscriber database load sharing group server application selects one of said first and second subscriber database server applications to perform said requested subscriber database service request according to a load distribution algorithm, and wherein said first subscriber database server application comprises a first primary-backup group server application that includes a first primary subscriber database server application executed on said first call application node and a first backup subscriber database server application associated with said first primary subscriber database server application, said first backup subscriber database server application residing on a call application node separate from said first call application node.

2. The controller as set forth in claim 1 wherein said load distribution algorithm distributes new subscriber database service requests in an alternating manner between said first and second subscriber database server applications.

3. The controller as set forth in claim 1 wherein said load distribution algorithm distributes new subscriber database service requests according to a current call process load of said first subscriber database server application and a current call process load of said second subscriber database server application.

4. The controller as set forth in claim 3 wherein said load distribution algorithm distributes said new subscriber database service requests in order to maintain said current call process load of said first subscriber database server application at a level substantially equal to said current call process load of said second subscriber database server application.

5. The controller as set forth in claim 1 wherein state information associated with said first primary subscriber database server application is mirrored to said first backup subscriber database server application associated with said first primary subscriber database server application.

6. The controller as set forth in claim 1 wherein said second subscriber database server application comprises a second primary-backup group server application, wherein said second primary-backup group server application comprises a second primary subscriber database server application executed on maid second call application node and a second backup subscriber database server application associated with said second primary subscriber database server application.

7. The controller as set forth in claim 6 wherein state information associated with said second primary subscriber database server application is mirrored to said second backup subscriber database server application associated with said second primary subscriber database server application.

8. The controller as set forth in claim 7 wherein said second backup subscriber database server application resides on said second call application node.

9. The controller as set forth in claim 8 wherein said second backup subscriber database server application resides on a call application node separate from said second call application node.

10. A wireless network comprising:

a plurality of base stations capable of communicating with a plurality of mobile stations in a coverage area 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, and wherein said mobile switching center is capable of executing call processing applications, wherein each of said call processing applications is associated with one of said call connections, wherein said mobile switching center comprises;

a controller for providing a subscriber database associated with said mobile switching center, wherein said controller comprises;

N call application nodes capable of executing call process server applications, wherein a first subscriber database server application is executed on a first one of said N call application nodes and is associated with a similar second subscriber database server application executed on a second one of said N call application nodes separate from said first call application node, said first and second subscriber database server applications thereby forming a subscriber database load sharing group server application, and

wherein said each call processing application sends a subscriber database service request to said subscriber database load sharing group server application and said subscriber database load sharing group server application selects one of said first and second subscriber database server applications to perform said requested subscriber database service request according to a load distribution algorithm, and wherein said first subscriber database server application comprises a first primary-backup group server application that includes a first primary subscriber database server application executed on said first call application node and a first backup subscriber database server application associated with said first primary subscriber database server application, said first backup subscriber database server application residing on a call application node separate from said first call application node.

11. The wireless network as set forth in claim 10 wherein said load distribution algorithm distributes new subscriber database service requests in an alternating manner between said first and second subscriber database server applications.

12. The wireless network as set forth in claim 10 wherein said load distribution algorithm distributes new subscriber database service requests according to a current call process load of said first subscriber database server application and a current call process load of said second subscriber database server application.

13. The wireless network as set forth in claim 12 wherein said load distribution algorithm distributes said new subscriber database service requests in order to maintain said current call process load of said first subscriber database server application at a level substantially equal to said current call process load of said second subscriber database server application.

14. The wireless network as set forth in claim 10 wherein state information associated with said first primary subscriber database server application is mirrored to said first backup subscriber database server application associated with said first primary subscriber database server application.

15. The wireless network as set forth in claim 10 wherein said second subscriber database server application comprises a second primary-backup group server application, wherein said second primary-backup group server application comprises a second primary subscriber database server application executed on said second call application node and a second backup subscriber database server application associated with said second primary subscriber database server application.

16. The wireless network as set forth in claim 15 wherein state information associated with said second primary subscriber database server application is mirrored to said second backup subscriber database server application associated with said second primary subscriber database server application.

17. The wireless network as set forth in claim 16 wherein said second backup subscriber database server application resides on said second call application node.

18. The wireless network as set forth in claim 17 wherein said second backup subscriber database server application resides an a call application node separate from said second call application node.

19. A method for providing a subscriber database associated with a mobile switching center, for use in a wireless network comprising:

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

     2) a mobile switching center coupled to said plurality of said 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, and wherein said mobile switching center is capable of executing call processing applications, wherein each of said call processing applications is associated with one of said call connections, the method comprising the steps of;

providing N call application nodes within said mobile switching center, said N call application nodes capable of executing a plurality of subscriber database server applications;

executing a first subscriber database server application on a first one of said N call application nodes;

executing a second subscriber database server application on a second one of said N call application nodes separate from said first call application node, said first and second subscriber database server applications thereby forming a subscriber database load sharing group server application;

sending a subscriber database service request from a call processing application to said subscriber database load sharing group server application;

selecting in said subscriber database load sharing group server application one of said first and second subscriber database server applications to perform said requested subscriber database service request; and

performing said requested subscriber database service request according to a load distribution algorithm, wherein said first subscriber database server application comprises a first primary-backup group server application including a first primary subscriber database server application executed on said first call application node and a first backup subscriber database server application associated with said first primary subscriber database server application, said first backup subscriber database server application residing on a call application node separate from said first call application node.

20. The method as set forth in claim 19 further comprising the step of distributing new subscriber database service requests in an alternating manner between said first and second subscriber database server applications.

21. The method as set forth in claim 19 further comprising the step of distributing new subscriber database service requests according to a current call load process of said first subscriber database server application and a current call load process of said second subscriber database server application.

22. The method as set forth in claim 21 further comprising the step of distributing new subscriber database service requests in order to maintain said current call process load of said first subscriber database server application at a level substantially equal to said current call process load of said second subscriber database server application.

23. The method am set forth in claim 19 further comprising the step of mirroring state information associated with said first primary subscriber database server application to said first backup subscriber database server application associated with said first primary subscriber database server application.

24. The method as set forth in claim 19 wherein said second subscriber database server application comprises a second primary-backup group server application, wherein said second primary-backup group server application comprises a second primary subscriber database server application executed on said second call application node and a second backup subscriber database server application associated with said second primary subscriber database server application.

25. The method as set forth in claim 24 further comprising the step of mirroring state information associated with said second primary subscriber database server application to said second backup subscriber database server application associated with said second primary subscriber database server application.

26. The method as set forth in claim 25 wherein said second backup subscriber database server application resides on said second call application node.

27. The method as set forth in claim 26 wherein said second backup subscriber database server application resides on a call application node separate from said second call application node.