Target MME Load Balancing During Handover

Feature Summary and Revision History

Summary Data

Applicable Product(s) or Functional Area

MME

Applicable Platform(s)

  • ASR 5500

  • VPC-DI

  • VPC-SI

Default Setting

Enabled - Always on

Related Changes in This Release

Not Applicable

Related Documentation

MME Administration Guide

Revision History

Revision Details

Release

With this release, this feature is fully qualified.

21.13

First introduced.

Important 

Target MME Load Balancing During Handover feature is not fully qualified in this release. It is available only for testing purposes.

21.12.2

Feature Description

MME can now configure multiple MME addresses for the same Tracking Area Identity (TAI) with the same priority. During the S1 handover procedure, MME selects the target MME based on the static configuration. If more than one MME is configured for the same TAI and priority then the round robin logic of selecting MMEs is used.

With this release, the limitation in configuring multiple MME addresses for the same TAI and priority is removed.

Consider an example where target MMEs with ip-address1, ip-address2 and ip-address3 are configured for the same TAI and priority. For the first handover to target TAI, the MME with address1 is used, for the second handover the MME address2 is used, and for the third handover the MME address3 is used. This sequence is repeated upon successive handovers to the same TAI. 

peer-mme tai-match  priority <val> mcc <val> mnc <val> tac <val> address <ip-address1> 
peer-mme tai-match  priority <val> mcc <val> mnc <val> tac <val> address <ip-address2> 
peer-mme tai-match  priority <val> mcc <val> mnc <val> tac <val> address <ip-address3>

Note

Each Session Manager independently load balances between the target MMEs.