Difference between revisions of "About YateMMI"

From YateBTS
Jump to: navigation, search
(Subscriber Management)
(Subscriber Management)
Line 120: Line 120:
'''Note:''' The OSS/BSS services are not included in YateMMI, however it allows applying development APIs for OSS/BSS integration.
'''Note:''' The OSS/BSS services are not included in YateMMI, however it allows applying development APIs for OSS/BSS integration.

Revision as of 10:06, 21 July 2017


An introduction to YateMMI

YateMMI's purpose if that of allowing a swift and easy configuration of all the Yate-based products: YateUCN, YateHSS/HLR, SatSite and STP.

The configuration procedures are easy, without an excess of technical information. YateMMI does not demand special training or a dedicated network administrator to handle the overall configuration (especially not for the standard settings).

YateMMI is installed on the first product you purchased or can be installed on a separate equipment, and can be accessed remotely from any part of the world. It uses the JSON API of each equipment. The MMI was created with the purpose of aiding operators in typical configuration scenarios. For more special configuration scenarios, a dedicated extension will be provided.

YateMMI allows to set generic information about the network, the roaming partners settings, the interconnect settings, the equipment settings, as well as the subscriber management for YateHSS/HLR. All these configurations are done though wizards (link here).

Types of equipment


Our main RAN equipment is the SatSite Model 142, a complete 4G LTE eNodeB, containing both the radio and baseband functions. It can also be configured via software to operate as a 2.5G GSM/GPRS BTS+BSC.

For configuring and managing the SatSite via YateMMI, refer to the following pages:

1. [link SatSite YateMMI LTE Configuration]

2. [link SatSite YateMMI GSM Configuration]

Core Network

Our main core network equipment are:

  • YateUCN, a unified core network solution that implements the functions below in software, in a single, commodity hardware server:
    • all the functions and protocols of the LTE EPC (MME, S-GW, P-GW, PCRF, and PCEF)
    • all the functions and protocols of the LTE VoLTE IMS P-CSCF, I/S-CSCF, IWF, and BGW
    • all the functions and protocols of the GSM/GPRS core network (MSC/VLR/SGSN/GGSN/GMSC)
  • YateHSS/HLR, the subscriber server for GSM, UMTS, LTE, IMS, WiFi networks, using both Diameter and SS7 MAP for authentication
  • YateSTP

YateMMI Concepts

YateMMI is organized in various contexts:

  • Home
  • My Network
  • Equipment
  • Subscriber Management

Each context has multiple modules and each of these modules can be either enabled or disabled. Contexts use wizards for a step-by-step configuration. To find out more about each wizard's fields, read the explanations marked with the ? (question mark).


There are different wizards for each equipment type:

  • a wizard for YateHSS/HLR and YateUCN
  • a different wizard for base stations

Each wizard was designed with the purpose of generating all the necessary SS7, Diameter and equipment-specific settings.

After setting up the equipment the administrator has to confirm if he wants the settings applied. A chron (link) will apply the settings to the equipment and will notify the administrator if the configuration was successful or not.

My Network

This context allows the administrator to set general information about the network. All this information is necessary for the equipment he will later on add.

The administrator can start adding only one equipment, and later add more. In case he wants to configure multiple equipment, YateMMI will generate pools of IP addresses, point codes, global titles and more.

Pools are an essential concept used for setting up the network.

To setup more pieces of equipment of the same type, an administrator may use:

  • Pools of Global Titles that will be automatically associated to the network nodes if 'Automatically associate GT to equipment' is enabled.
  • Pools of Pointcodes that will be automatically associated to the network nodes if 'Automatically associate PC to equipment' is enabled.
  • Pools of IP addresses that will be automatically associated to equipment if 'Automatically associate IP to equipment' is enabled.

The administrator has to defined the pools depending on their purpose, be it Radio Network equipment, Core Network, other networks, management or SatSite.

An equipment uses multiple addresses depending on the equipment type.

Each YateUCN has a pool of IPs associated to each GTP-U tunnel.

If the 'Automatically associate pools to YateUCN' option is enabled then this pools are associated automatically to YateUCN.

The My Network context has various modules, as seen below.

Network Settings

Currently, the Network Settings tab has two setup types:

  • Just YateHSS/HLR
  • Extend a network

The first step is especially designed for MVNOs and allows adding and configuring only a YateHSS/HLR.

The second setup allows adding an new equipment to the already setup network.

Roaming Partners

BTS Templates

The BTS Templates included Rural and Urban templates for adding basestations and eNodeBs. Each template has a number of configuration settings tabs.


Subscriber Management

This context allows configuring SIM profiles, as well as CS, PS, IMS, EPC profiles for the subscribers' network services.

It's modules are:

  • Subscribers
  • Profiles

Note: The OSS/BSS services are not included in YateMMI, however it allows applying development APIs for OSS/BSS integration.