System Manual

BreezeCOMPACT System Manual
Chapter 1: System Description
BreezeCOMPACT Features
38
1.5.6
Multiple PLMN IDs
The PLMN ID is built by concatenating the Mobile Country Code (MCC) and the Mobile Network
Code (MNC). It provides the unique network identity. The same PLMN ID value must be
configured in both the EPC and the eNB. The BreezeCOMPACT can support multiple PLMN
IDs working with different MMEs/EPCs for multi-service networks and RAN sharing scenarios.
The eNodeB (BreezeCOMPACT) is configured with the list of MME IP addresses. When the UE
is initially attached, the eNodeB selects the relevant MME/EPC based on the PLMN ID.
For more details about this capability, contact Telrad.
1.5.7
EPC Redundancy and Load Balancing (Cluster)
The BreezeCOMPACT supports redundancy and load balancing between different
BreezeWAY2020 entities in an EPC cluster. The cluster organizes the EPC entities in order to
scale up the capacity and redundancy.
Figure 19: EPC Redundancy and Load Balancing
BreezeCOMPACT configuration enables multiple IP addresses to be configured for MMEs/EPCs
(as described for multiple PLMN IDs in Sections 1.5.5, Multiple PLMN IDs
When EPCs/MMEs are configured with the same PLMN ID, BreezeCOMPACT can select the
best EPC for load-balancing purposes.
Telrad BreezeCOMPACT eNB supports proportional-fair load-balancing mechanism for UE
sessions distribution between EPC (MME) entities it is associated with (S1 Flex topology). The
Load-balancing mechanism is applied during a new UE Attach procedure. eNB may be
provisioned with multiple EPCs (MMEs) in a load-balancing/ failover mode. BreezeCOMPACT
supports two pools of MMEs (EPCs) for load balancing
– Primary and Secondary.
EPC “balancing” is used within the pool – either Primary or Secondary. If no resources or no
available MME entities event occurs in the Primary pool, eNB will switch to the Secondary pool.
When resources of the Primary pool recover, eNB will switch back to use it (for a new-coming
UEs)
Note: In R6.9 BreezeCOMPACT with eEPC (BreezeWAY1010), can be configured to enable local
embedded EPC entity which can be set as one of EPC entities (either primary or secondary)