System and method for load balancing MMEs and MME pools

• US 8,948,014 B2
• Filed: 09/28/2012
• Issued: 02/03/2015
• Est. Priority Date: 10/19/2011
• Status: Expired due to Fees

• Current Assignee: RPX Corporation
• Original Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Inventors: Furry, Jeffrey, VELAMATI, MURALI K., SELVAM, MEENA, Calippe, Joel R.
• Primary Examiner(s): Zhou, Yong
• Application Number:
  US13/631,264
• Publication Number:
  US 20130100813A1
• Time in Patent Office: 858 Days
• US Class Current: 370/237
• CPC Class Codes: H04W 36/0033 with transfer of context information
• CPC Class Codes: H04W 36/12 Reselecting a serving backbone network switching or routing node
• CPC Class Codes: H04W 36/22 for handling the traffic
• 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 92/24 between backbone network devices

Abstract

A system, method and apparatus for policy-driven load balancing of MMEs and MME pools by migrating eNodeBs service responsibilities among MMEs and/or MME processing components or modules.

Claims

1. A method for managing mobility management entities (MME) loading, comprising:

monitoring indicia of eNodeB loading at a source MME and individually at each of a plurality of processing elements in said source MME; and

in response to said loading indicia exceeding one or more of policy-defined threshold levels for said source MME and said plurality of processing elements in the source MME, migrating responsibility for one or more eNodeBs to one or more of;

a target MME and a target processing element of the source MME.

2. The method of claim 1, wherein said migrating comprises:

transmitting to the target MME a message adapted to cause the target MME to form links to the eNodeBs to be migrated;

converting existing links between the eNodeBs to be migrated and the source MME to standby links;

transmitting to the target MME state information associated with the eNodeBs to be migrated; and

preventing the acceptance of new services at the source MME associated with the eNodeBs to be migrated.

3. The method of claim 1, further comprising transmitting to the target MME user context information associated with the eNodeBs to be migrated.

4. The method of claim 3, wherein the user context information comprises, for each respective user, information related to one or more of a typical Service Gateway (SGW) used, a typical user data/call path, PCRF rules, authentication data, data plan parameters, roaming information, visiting information, home information and user call routing preferences.

5. The method of claim 1, wherein said source and target MMEs comprise different processing elements within a single MME.

6. The method of claim 1, wherein said source and target MMEs comprise different MMEs within a pool of MMEs.

7. The method of claim 1, wherein said source and target MMEs comprise MMEs within different pools of MMEs.

8. The method of claim 1, wherein said indicia of eNodeB loading and said threshold level are defined by policy information received from a network management system.

9. The method of claim 1, wherein a network manager (NM) is adapted to perform said monitoring of indicia of eNodeB loading at each of a plurality of MMEs within a network.

10. The method of claim 9, wherein said NM is further adapted to perform said determine if said loading indicia exceeding a policy-defined threshold.

11. The method of claim 10, wherein said MN adapts MME operation via a policy mechanism.

12. The method of claim 1, wherein a MME is adapted to perform said monitoring of indicia of eNodeB loading and determine if said loading indicia exceeds a policy-defined threshold.

13. The method of claim 12, wherein said MME communicates with one or more neighboring MMEs to negotiate a migration of eNodeBs thereto.

14. The method of claim 13, wherein said MME and said neighboring MMEs form a MME pool, wherein at least some of the MMEs within the pool operate to manage eNodeB loading associated with the MME members of the pool.

15. The method of claim 1, wherein the policy-defined threshold level for each MME is based upon one or more of subscriber type, service type and service level agreement (SLA) associated with users of respective supported eNodeBs.

16. The method of claim 1, wherein the policy defined threshold level is derived by processing multiple MME status indicators to predict thereby an imminent over utilization condition.

17. The method of claim 1, further comprising:

defining for each MME one or more target MMEs;

causing each MME to communicate “

keep alive”

information with each of its respective one or more target MMEs; and

adapting eNodeB migration according to a target MME priority sequence.

18. An apparatus for managing mobility management entities (MME) loading, the apparatus comprising:

a processor configured for;

monitoring indicia of eNodeB loading at a source MME and individually at each of a plurality of processing elements in said source MME; and

in response to said loading indicia exceeding one or more of policy-defined threshold levels for said source MME and said plurality of processing elements in the source MME, migrating responsibility for one or more eNodeBs to one or more of;

a target MME and a target processing element of the source MME.

21. The apparatus of claim 18, wherein said migrating comprises:

transmitting to the target MME a message adapted to cause the target MME to form links to the eNodeBs to be migrated;

converting existing links between the eNodeBs to be migrated and the source MME to standby links;

transmitting to the target MME state information associated with the eNodeBs to be migrated; and

preventing the acceptance of new services at the source MME associated with the eNodeBs to be migrated.

19. A non-transitory computer readable storage medium storing instructions which, when executed by a computer, cause the computer to perform a method for managing mobility management entities (MME) loading, comprising:

monitoring indicia of eNodeB loading at a source MME and individually at each of a plurality of processing elements in said source MME; and

in response to said loading indicia exceeding one or more of policy-defined threshold levels for said source MME and said plurality of processing elements in the source MME, migrating responsibility for one or more eNodeBs to one or more of;

a target MME and a target processing element of the source MME.

22. The non-transitory computer readable storage medium of claim 19, wherein said migrating comprises:

transmitting to the target MME a message adapted to cause the target MME to form links to the eNodeBs to be migrated;

converting existing links between the eNodeBs to be migrated and the source MME to standby links;

transmitting to the target MME state information associated with the eNodeBs to be migrated; and

preventing the acceptance of new services at the source MME associated with the eNodeBs to be migrated.

20. A non-transitory computer program product wherein computer instructions stored in a non-transitory computer readable memory, when processed by a computer, adapt the operation of the computer to provide a method for managing mobility management entities (MME) loading, comprising:

monitoring indicia of eNodeB loading at a source MME and individually at each of a plurality of processing elements in said source MME; and

in response to said loading indicia exceeding one or more of policy-defined threshold levels for said source MME and said plurality of processing elements in the source MME, migrating responsibility for one or more eNodeBs to one or more of;

a target MME and a target processing element of the source MME.

23. The non-transitory computer program product of claim 20, wherein said migrating comprises:

transmitting to the target MME a message adapted to cause the target MME to form links to the eNodeBs to be migrated;

converting existing links between the eNodeBs to be migrated and the source MME to standby links;

transmitting to the target MME state information associated with the eNodeBs to be migrated; and

preventing the acceptance of new services at the source MME associated with the eNodeBs to be migrated.