• 1
  • 2
  • 3
  • 4


  • NITOS Outdoor deployment consists of powerful nodes that feature multiple wireless interfaces and allow for experimentation with heterogeneous (Wi-Fi, WiMAX,

    Read More
  • The setup NITOS testbed is currently using is a fixed setup (employing no mobility between BSs) that does not require

    Read More
  • Towards the development of a remote accessible LTE testbed, where experimenters from all the word will be able to run

    Read More
  • NITOS facility provides remote access to OpenFlow switches (2 x Pronto 3290 , 2 x HP 3800 ), enabling the user to create

    Read More
  • NITlab developed a software defined radio (SDR) testbed that consists of 18 Universal Software Radio Peripheral (USRP) devices attached to

    Read More
  • NITOS is an Intelligent Transport System (ITS) compatible facility thanks to the implementation of the key components of the ITS

    Read More
  • NITOS cloud infrastructure is based on HP GEN8 blade servers and one HP DL380p GEN8 server. Cloud Infrastructure UTH Each blade server has

    Read More


The Future Internet Facility

  • Outdoor Testbed

    Experiments under real world environment Read More
  • Indoor Testbed

    Experiments in RF isolated environment Read More
  • Office testbed

    Experiments in an office environment Read More
  • 1
  • 2
  • 3

lterf OMF AM service

NITLab and WINLAB (Rutgers University) have developed the first version of an OMF Aggregate Manager service, ready to be installed at any similar to NITOS testbed, that enables controlling of the ip.access LTE 245F femtocells and of SiRRAN's EPC Network. Currently getting and setting values from the APs and getting values from SiRRAN's EPC are supported. The values that can be changed/reported are the ones that are visible to the testbed Operator and can be used for setting up an experiment. The setup we have followed is similar to the one used by the GENI WiMAX consortium in US (http://wimax.orbit-lab.org) .

We assume that the OMF AM service is running at a dedicated server for each AP. The setup is similar to the one illustrated in Figure 1.

LTE Architecture


Each lterf server instance is able to control one AP, as it is set by its configuration .yaml file. In order to install the lterf instance the following packages are required:

* ruby1.9.1

* rubygems

* the dm_sqlite_adapter gem

We suppose that the system is a x64 Ubuntu Server system. 

In order to install the lterf service, update your apt repositories with the following entry:

deb http://nitlab.inf.uth.gr/ubuntu precise/ 

Now you can issue the following commands to install the service:

sudo apt-get update && sudo apt-get install lterf

Some further configurations are needed for the configuration file in order for the service to run as expected. The OMF AM service configuration file can be found at /etc/omf-aggmgr-5.4/enabled/lterf.yaml. The file should look like the following:



    dbFile: 'db/lterf.db'

    type: ipaccess
    mgmt_if: eth1
    key: '/root/.ssh/key2'
        :omlServer: nitlab.inf.uth.gr
        :omlServer: nitlab.inf.uth.gr
    type: sirran
    db_user: omf
    db_pass: omf-pass
    db: lte_main
    user: root

    manage_interface: true

The important parameters are the LTE AP address and subnet mask, as well as the interface of the server that communicates with it. The Key entry should contain the path to the key needed to access the LTE AP via ssh. If you want to have access to the EPC, you need to have an account that is able to login with a mysql account on the EPC database.

By sending the appropriate commands to the LTE AM service, you can change parameters on the database. For instance, in order to list all available services you will hae to issue the following command:


 wget -qO- "http://lterf:5054/lterf/" | xml_pp 

The command should return all the available parameters that can be changed through this service. In order to query about a specific value of the LTE AP, you will have a command similar to the following one (for example the band number that is currently in use)

 wget -qO- "http://lterf:5054/lterf/bs/get?freqBandIndicator" 

The service replies with an XML formed reply. Similar to this, if the experimenter needs to change the current operating band, the command should look like:

 wget -qO- "http://lterf:5054/lterf/bs/set?freqBandIndicator=7" 

For every change to take effect, a reboot is required! The reboot command is:

 wget -qO- "http://lterf:5054/lterf/bs/restart" 


You can find more instructions on running the updated version of LTErf here.

What Our Experimenters Say

  • NITOS is a very reliable and well managed platform. The offered infrastructure and features are great. The management team is very supportive.

    Mustafa Al-Bado
    Postdoctoral researcher
    Insight centre, University College Cork (UCC)
  • 1
  • 2

Login Form