Flexible load distribution and management in an MME pool

• US 10,548,140 B2
• Filed: 05/01/2018
• Issued: 01/28/2020
• Est. Priority Date: 05/02/2017
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Affirmed Networks, Inc. (Microsoft Corporation)
• Inventors: Qian, Haibo, Rink, Fred, Bieghler, Bret
• Primary Examiner(s): Moore, Ian N
• Assistant Examiner(s): Sampat, Rushil Parimal
• Application Number:
  US15/968,440
• Publication Number:
  US 20180324784A1
• Time in Patent Office: 637 Days
• CPC Class Codes: H04W 28/0215 based on user or device properties, e.g. MTC-capable devices services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51
• CPC Class Codes: H04W 28/0236 radio quality, e.g. interference, losses or delay
• CPC Class Codes: H04W 28/088 among core entities
• CPC Class Codes: H04W 36/22 for handling the traffic
• CPC Class Codes: H04W 72/51 based on terminal or device properties
• CPC Class Codes: H04W 72/52 based on load

Abstract

Systems and methods are disclosed for a method of assigning resources to eNodeBs in a mobility management entity (MME) pool, including determining a first relative capacity for a first eNodeB based on at least one of latency between the first eNodeB and a first MME and the location of the first eNodeB. A second relative capacity may be determined for a second eNodeB based on at least one of latency between the second eNodeB and the first MME and the location of the second eNodeB. The first and second relative capacities may be indicative of relative capacity values greater than zero. The relative capacities may be provided to the first and second eNodeBs, and a portion of traffic sent from the first and second eNodeBs to the first MME may be based on the first and second relative capacities, respectively.

Claims

1. A method of assigning resources to eNodeBs in a mobility management entity (MME) pool, comprising:

determining a first relative capacity for a first eNodeB based on at least one of latency between the first eNodeB and a first MME and a location of the first eNodeB, wherein the first relative capacity is associated with a first relative capacity value being greater than zero;

determining a second relative capacity for a second eNodeB based on at least one of latency between the second eNodeB and the first MME and a location of the second eNodeB, wherein the second relative capacity is associated with a second relative capacity value being greater than zero;

providing the first relative capacity to the first eNodeB in a first configuration update request, wherein a portion of traffic sent from the first eNodeB to the first MME is based on both the first relative capacity and the second relative capacity;

providing the second relative capacity to the second eNodeB in a second configuration update request, wherein a portion of traffic sent from the second eNodeB to the first MME is based on both the first relative capacity and the second relative capacity;

determining a third relative capacity for the first eNodeB based on at least one of latency between the first eNodeB and a second MME in a pool with the first MME and the location of the first eNodeB, wherein the third relative capacity is associated with a third relative capacity value being greater than zero; and

providing the third relative capacity to the first eNodeB in a third configuration update request, wherein a portion of traffic sent from the first eNodeB to the second MME is based on the third relative capacity.

2. The method of claim 1, wherein the first relative capacity value is different from the second relative capacity value.

3. The method of claim 1, further comprising offloading the second eNodeB from the first MME at a first time, wherein the offloading comprises:

providing a fourth relative capacity to the second eNodeB in a fourth configuration update request, wherein the portion of traffic sent from the second eNodeB to the first MME is reduced to zero based on the fourth relative capacity.

4. The method of claim 3, wherein at the first time, the portion of traffic sent from the first eNodeB to the first MME is greater than zero.

5. The method of claim 1, further comprising:

determining a fourth relative capacity for the second eNodeB based on at least one of latency between the second eNodeB and the second MME and the location of the second eNodeB, wherein the fourth relative capacity is associated with a fourth relative capacity value being greater than zero; and

providing the fourth relative capacity to the second eNodeB in a fourth configuration update request, wherein a portion of traffic sent from the second eNodeB to the second MME is based on the fourth relative capacity.

6. The method of claim 5, wherein at least one of:

the third relative capacity value is different from the fourth relative capacity value;

the first relative capacity value is different from the third relative capacity value; and

the second relative capacity value is different from the fourth relative capacity value.

7. A method of assigning resources to eNodeBs in a mobility management entity (MME) pool, comprising:

determining a first relative capacity for a first eNodeB based on at least one of latency between the first eNodeB and a first MME and a location of the first eNodeB, wherein the first relative capacity is associated with a first relative capacity value being greater than zero;

determining a second relative capacity for a second eNodeB based on at least one of latency between the second eNodeB and the first MME and a location of the second eNodeB, wherein the second relative capacity is associated with a second relative capacity value being greater than zero;

providing the first relative capacity to the first eNodeB in a first configuration update request, wherein a portion of traffic sent from the first eNodeB to the first MME is based on the first relative capacity;

providing the second relative capacity to the second eNodeB in a second configuration update request, wherein a portion of traffic sent from the second eNodeB to the first MME is based on the second relative capacity; and

providing the second relative capacity to a third eNodeB in a third configuration update request, wherein;

a portion of traffic sent from the third eNodeB to the first MME is based on the second relative capacity; and

the third eNodeB being located less than a threshold distance from the second eNodeB.

8. The method of claim 7, wherein the determining of the first relative capacity and the second relative capacity and the providing of the first relative capacity and the second relative capacity are performed by the first MME.

9. The method of claim 8, further comprising:

receiving, by the first MME, a portion of traffic from the first eNodeB based on the first relative capacity; and

receiving, by the first MME, a portion of traffic from the second eNodeB based on the second relative capacity.

10. A system for assigning resources to eNodeBs in a mobility management entity (MME) pool, the system comprising:

a processor; and

a memory coupled to the processor and including computer-readable instructions that, when executed by the processor, cause the processor to;

determine a first relative capacity for a first eNodeB based on at least one of latency between the first eNodeB and a first MME and a location of the first eNodeB, wherein the first relative capacity is associated with a first relative capacity value being greater than zero;

determine a second relative capacity for a second eNodeB based on at least one of latency between the second eNodeB and the first MME and a location of the second eNodeB, wherein the second relative capacity is associated with a second relative capacity value being greater than zero;

provide the first relative capacity to the first eNodeB in a first configuration update request, wherein a portion of traffic sent from the first eNodeB to the first MME is based on both the first relative capacity and the second relative capacity;

provide the second relative capacity to the second eNodeB in a second configuration update request, wherein a portion of traffic sent from the second eNodeB to the first MME is based on both the first relative capacity and the second relative capacity;

determine a third relative capacity for the first eNodeB based on at least one of latency between the first eNodeB and a second MME in a pool with the first MME and the location of the first eNodeB, wherein the third relative capacity is associated with a third relative capacity value being greater than zero; and

provide the third relative capacity to the first eNodeB in a third configuration update request, wherein a portion of traffic sent from the first eNodeB to the second MME is based on the third relative capacity.

11. The method of claim 10, wherein the first relative capacity value is different from the second relative capacity value.

12. The method of claim 10, wherein the processor is further caused to offload the second eNodeB from the first MME at a first time, wherein the offloading further causes the processor to provide a fourth relative capacity to the second eNodeB in a fourth configuration update request, wherein the portion of traffic sent from the second eNodeB to the first MME is reduced to zero based on the fourth relative capacity.

13. The method of claim 10, wherein the processor is further caused to:

determine a fourth relative capacity for the second eNodeB based on at least one of latency between the second eNodeB and the second MME and the location of the second eNodeB, wherein the fourth relative capacity is associated with a fourth relative capacity value being greater than zero; and

provide the fourth relative capacity to the second eNodeB in a fourth configuration update request, wherein a portion of traffic sent from the second eNodeB to the second MME is based on the fourth relative capacity.

14. The method of claim 10, wherein at least one of:

the third relative capacity value is different from the fourth relative capacity value;

the first relative capacity value is different from the third relative capacity value; and

the second relative capacity value is different from the fourth relative capacity value.

16. The method of claim 10, wherein the processor is part of the first MME, wherein the first MME is further configured to:

receive a portion of traffic from the first eNodeB based on the first relative capacity; and

receive a portion of traffic from the second eNodeB based on the second relative capacity.

15. A system for assigning resources to eNodeBs in a mobility management entity (MME) pool, the system comprising:

a processor; and

a memory coupled to the processor and including computer-readable instructions that, when executed by the processor, cause the processor to;

determine a first relative capacity for a first eNodeB based on at least one of latency between the first eNodeB and a first MME and a location of the first eNodeB, wherein the first relative capacity is associated with a first relative capacity value being greater than zero;

determine a second relative capacity for a second eNodeB based on at least one of latency between the second eNodeB and the first MME and a location of the second eNodeB, wherein the second relative capacity is associated with a second relative capacity value being greater than zero;

provide the first relative capacity to the first eNodeB in a first configuration update request, wherein a portion of traffic sent from the first eNodeB to the first MME is based on the first relative capacity; and

provide the second relative capacity to the second eNodeB in a second configuration update request, wherein a portion of traffic sent from the second eNodeB to the first MME is based on the second relative capacity;

provide the second relative capacity to a third eNodeB in a third configuration update request, wherein;

a portion of traffic sent from the third eNodeB to the first MME is based on the second relative capacity; and

the third eNodeB being located less than a threshold distance from the second eNodeB.