2. Overview  Quick Round-table  Introduction of OAI team at EURECOM –People and roles  Overview of License and Copyright issues  Objectives –Next release  Focus on stability of codebase on EURECOM and Ettus devices –Roadmap  Discussion on development tools –svn vs. git –Twiki usage –Building, installing  Overview of OAI testbeds that are out there –Fill in twiki page for each user –What people want to do  Remaining questions/comments OAI Next Steps

3. EURECOM Development Team  Raymond Knopp –openair1,openair2, HW interfaces –L1/L2 LTE specifications,SIMD optimization, conformance testing, L1 unitary simulation  Florian Kaltenberger –openair1,openair2, HW interfaces –Channel modelling, conformance testing, simulation, abstraction, EMOS, L1 unitary simulation  Navid Nikaein –openair2,openair-CN –oaisim emulation, traffic generation, virtualization, cloudification, general code structuring, conformance testing  Lionel Gauthier –openair-CN, openair2 –L2/L3 LTE specifications, conformance testing, general code structuring,  Aikaterini TRILYRAKI –Cloudification, I/Q ethernet transport, more to come … –More to come  Dominique Nussbaum –RF integration –Project Management  Two new people in a month or so –Hardware interfaces OAI Next Steps

4. License and Copyright Issues  Currently GPLv3  Next Release will be Apache V2.0 –Motivation: make the codebase usable by major industrial players  Copyright –We’ll have to decide whether contributors keep their own copyright or relinquish to new OAI Alliance –Until Alliance really takes off with some strategic industrial partners (very likely quite soon), this decision will be put on hold  Main issue for contributors is losing IPR OAI Next Steps

5. Development Tools  svn vs. git –Opinions? –Git @ eurecom or github?  Twiki usage –We expect developers to help making twiki as clear and up-to-date as possible  Building, installing –Opinions?  Code beautifying + Doxygen –Need help with Doxygen  It will stimulate the mailing list if people get involved with this – many questions will be asked... and answered –Need a consensus for the look of the code (messages from S. Held) OAI Next Steps

6. Next Release (0.2)  Compilation/Build –cmake targets (removal of all Makefiles)  L1/L2 features –Multiple-users (at least 2) –RRC Measurement reporting –eNB RRH UE (1) –Full DL throughput (at least in 5 MHz, 14 Mbit/s TM1/2) –OAI eNB OAI UE  Bad Bugs/Issues –Radio link failure –Reconnection / Reestablishment –UE removal –TM2 (fix nb_antennas_tx_eNB) –DLSCH transmissions exhausted bug –Handle Paging in eNB (correct bug in S1AP, not L1/L2 procedure) –20 MHz bugs on ExpressMIMO2 –Current TCP traffic issue –MIMO on USRP –20 MHz MIMO 23.04 Ms/s / FFT1536 for USRP OAI Next Steps