Changes between Initial Version and Version 1 of Internal/CurrentDevelopment/LTE


Ignore:
Timestamp:
Sep 25, 2015, 5:23:46 PM (9 years ago)
Author:
msherman
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Internal/CurrentDevelopment/LTE

    v1 v1  
     1== LTE ==
     2
     3==== Main Tasks ====
     41. Make base image for open air interface (OAI)
     5 1. SB1
     6 1. Compile enodeb, ue, mme
     7 1. Put binaries in correct places
     81. write omf service to control lte basestation parameters
     9 1. amarisoft, openairlte, airspan?
     10 1. primary openairlte
     111. https://twiki.eurecom.fr/twiki/bin/view/OpenAirInterface/OpenAirDocumentation
     12
     13==== OAI Build ====
     14
     15openair lte image, svn based
     16new image, pull from git
     17
     18repo1
     19oai images
     20oa-trunk-full.ndz
     21
     22replace with git based version
     23
     24root home directory, git pull
     25compile, put binaries in /usr/bin
     26
     27
     283 important binaries
     29
     30enodeb (basestation)
     31ue (client)
     32mme  (component, mobility management, controller)
     33
     34difference in compilation settings for enodeb vs ue
     35vs cli switch
     36
     37create via shell / ruby
     38scripts to start server or client
     39
     40control ue via resource controller
     41control enodeb via rest?
     42
     43both via conf. file
     44
     45
     46bsc03out has bs controller
     47omf agg manager for conf, changes file, then controller
     48
     49has version of bscontrol, managing amarisoft (n210) and oai (b210) or (x310)
     50
     51bscontrol for (wimax airspan)
     52airspan via snmp, adapt wimax commands for lte airspan
     53
     54
     55openair lte image, svn based
     56new image, pull from git
     57
     58repo1
     59oai images
     60oa-trunk-full.ndz
     61
     62replace with git based version
     63
     64root home directory, git pull
     65compile, put binaries in /usr/bin
     66
     67
     683 important binaries
     69
     70enodeb (basestation)
     71ue (client)
     72mme  (component, mobility management, controller)
     73
     74difference in compilation settings for enodeb vs ue
     75vs cli switch
     76
     77create via shell / ruby
     78scripts to start server or client
     79
     80control ue via resource controller
     81control enodeb via rest?
     82
     83both via conf. file
     84
     85
     86bsc03out has bs controller
     87omf agg manager for conf, changes file, then controller
     88
     89has version of bscontrol, managing amarisoft (n210) and oai (b210) or (x310)
     90
     91bscontrol for (wimax airspan)
     92airspan via snmp, adapt wimax commands for lte airspan
     93
     94