LTE

Main Tasks

1. Make base image for open air interface (OAI)
   1. SB1
   2. Compile enodeb, ue, mme
   3. Put binaries in correct places
2. write omf service to control lte basestation parameters
   1. amarisoft, openairlte, airspan?
   2. primary openairlte
3. ​https://twiki.eurecom.fr/twiki/bin/view/OpenAirInterface/OpenAirDocumentation

OAI Build

openair lte image, svn based new image, pull from git

repo1 oai images oa-trunk-full.ndz

replace with git based version

root home directory, git pull compile, put binaries in /usr/bin

3 important binaries

enodeb (basestation) ue (client) mme (component, mobility management, controller)

difference in compilation settings for enodeb vs ue vs cli switch

create via shell / ruby scripts to start server or client

control ue via resource controller control enodeb via rest?

both via conf. file

bsc03out has bs controller omf agg manager for conf, changes file, then controller

has version of bscontrol, managing amarisoft (n210) and oai (b210) or (x310)

bscontrol for (wimax airspan) airspan via snmp, adapt wimax commands for lte airspan

openair lte image, svn based new image, pull from git

repo1 oai images oa-trunk-full.ndz

replace with git based version

root home directory, git pull compile, put binaries in /usr/bin

3 important binaries

enodeb (basestation) ue (client) mme (component, mobility management, controller)

difference in compilation settings for enodeb vs ue vs cli switch

create via shell / ruby scripts to start server or client

control ue via resource controller control enodeb via rest?

both via conf. file

bsc03out has bs controller omf agg manager for conf, changes file, then controller

has version of bscontrol, managing amarisoft (n210) and oai (b210) or (x310)

bscontrol for (wimax airspan) airspan via snmp, adapt wimax commands for lte airspan